Sponsored Content
Operating Systems Linux Debian Hardlink on wheezy by default for usb-stick? Post 302939342 by 1in10 on Tuesday 24th of March 2015 09:08:49 PM
Old 03-24-2015
Hardlink on wheezy by default for usb-stick?

May somebody can give me a hint. I am still using my old squeeze and it works the way I want. But my recent post about changing the owners rights, e.g. 777 or 755 anyway, it could be 644 as well. While configuring a new pc, just by chance I discovered how to enter the BIOS. And here it comes. I want to install from an usb-stick the debian-7.8.0-amd64-netinst.iso.
Allright, there should be no obstacle so far. But this usb-stick was formatted in ext4 on another debian 7.8 machine and this very usb-stick now is refusing me as root on squeeze to unpack even in the terminal the package. No matter if I try chmod, chown 644 -d name-of-the-file. I don't have permission to do so. That would mean for my humble understanding that this device has won a hardlink to the other machine, I truly don't have a clue. Is there someone out there who could give me a hint. Thanks a lot in advance, I keep gouging my way through this. Maybe I am wrong, and there is no hardlink, but only root can act as rwx, the rest is set to r.

Code:
debian-7.8.0-amd64-netinst.iso is not RAR archive

this is what I get, after typing as root.

Code:
root@rechenknecht2:/media/usb0# unrar e debian-7.8.0-amd64-netinst.iso
root@rechenknecht2:/media/usb0# unrar l debian-7.8.0-amd64-netinst.iso
root@rechenknecht2:/media/usb0# unrar y debian-7.8.0-amd64-netinst.iso

but it is such a package to be unpacked, I did it before, earlier version of wheezy, and where I am doing wrong?

maybe something like this:

Code:
mount -o loop -t iso9660 debian-7.8.0-amd64-netinst.iso /media/usb0/

yep, luky strike...it worked.



but after solving this, on rebooting after the changes of the BIOS, there comes up, the real grewsome two aspects.
changes to the American Megatrends Bios version 2.15.1236 in the boot sequence are not saved, even clicking so. I switches back to EFI or UEFI and furhtermore it tells me that there is no BIOS fils in this usb key. Where the hack do I slam in to that usb key any bios file. After rebooting the screen tells me about grub rescue. So the BIOS itself saves the BIOS to the storage device with a strange name, that means...never use a large usb-device for that, unless you have to much of them. But grub rescue> after rebooting continues. So any hints to that. Thanks in advance!!!

Last edited by 1in10; 03-24-2015 at 11:56 PM.. Reason: solved and new problem on the horizon, grub rescue
 

10 More Discussions You Might Find Interesting

1. Linux

Booting Linux from an USB stick

I got Puppy linux and installed it on a usb stick. In the BIOS i selected to boot from USB-FDD but it goes to my HD and ignores the USB stick, What going on ?? (2 Replies)
Discussion started by: perleo
2 Replies

2. Linux

bootable USB Stick || Fedora 8

Hello Everybody I am planning to install Fedora core 8 on an extra PC I have; what I wanna do is to boot from a USB stick then install Fedora from an ISO image I already have via FTP. Could any one tell me how to create bootable USB Stick for Fedora as I already found how to install from FTP... (0 Replies)
Discussion started by: ahmed_nasr2001
0 Replies

3. UNIX for Dummies Questions & Answers

Aix usb stick

I have a P-Series Machine running AIX 5.3, it has a USB Port on the front of the server, can I use a USB Stick on AIX platforms?? if so how..:rolleyes: (2 Replies)
Discussion started by: BEVAN
2 Replies

4. Filesystems, Disks and Memory

Mount USB stick...

Dummies questions, perfect for this. I cannot mount my idiotic usb stick on Slackware, I input the following on non-graphic mode as root: Mount -t vfat /dev/sdc1/usbstick usbstick is the folder i created for mounting my USB, the file system is FAT, and everytime I input that I get some kind... (2 Replies)
Discussion started by: Dax01
2 Replies

5. BSD

Mounting a USB stick in FreeBSD

When mounting a USB stick or pen drive on a FreeBSD machine I always issue the following command: mount -t msdosfs /dev/da0s1 /mnt Something I have always wondered is what the option msdosfs stands for and more importantly, why it is necessary. (7 Replies)
Discussion started by: figaro
7 Replies

6. Shell Programming and Scripting

1 usb stick -> 2 mounted devices

Hello, i am using a solaris thinclient that tries to connecting to a terminalserver. (RDP) Everything works fine, but the usb redirection. If i put in a usb stick i always get 2 usb-drives mounted. If i look in /tmp/SUNWut/mnt/<name of the host> i see 2 devices. One with the name of the... (2 Replies)
Discussion started by: anarcy
2 Replies

7. Ubuntu

Ubuntu on USB stick?

Hey Guys I have an Ubuntu CD and I was thinking of creating like a bootable hard drive with various OS so that I can just boot OSs with t drive and not require the CDs. I was just wondering is there a way I can do this, like have Ubuntu boot from a USB stick? If yes how is that possible(even if I... (3 Replies)
Discussion started by: rbansal2
3 Replies

8. SCO

Mount USB stick

hi Howto mount an USB stick under SCO 5.0.7? BTW ist it possible to mount USB stick in the command line using 'tools' at the Boot: prompt from OpenServer Release 5.0.7 installation CD? (1 Reply)
Discussion started by: ccc
1 Replies

9. SCO

How to use USB Stick in UNIXware?

I am trying to use a USB (Pen?) drive on Unixware 7.1.4. The USB stick is in the machine and the machine recognises it when I enter usbprobe as follows: Path - Address Description ----------------------------- +++++++ BUS #2 0 - 1 - HUB "UHCI Root Hub" 1 - 2 - HID "Chicony Wireless Device"... (1 Reply)
Discussion started by: BernP
1 Replies

10. BSD

Bootable usb-stick, need help, sos

I would probably set all my rubber points here to get some real help for creating a boot device on a usb-stick. There is no CD-drive on this machine, thats why I need to use a usb-stick. And scrumming in a CD-drive to fuddle around in the fstab or something like that is out of reach. My wisdom so... (9 Replies)
Discussion started by: 1in10
9 Replies
MKRESCUE(8)						      System Manager's Manual						       MKRESCUE(8)

NAME
mkrescue - make rescue floppy or CD SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf. DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= spec- ification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso). OPTIONS
--append <string> Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append ""). --debug Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses. --device <device> Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created. --fast Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk. --fs [ ext2 | msdos | minix ] Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels. --help Print a short usage synopsis, including a list of command options. --image <label> Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken. --initrd <filepath> and --kernel <filepath> These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname. --install [ text | menu ] Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media. --iso Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed. --nocompact For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omit- ting the lilo -c switch. --noformat Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2). --root <device> Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification. --size [ 1440 | 1200 | 2880 | HD ] The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifi- cations are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loop- back devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option. --version Print the version number of mkrescue, then terminate. SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8) 6 Mar 2011 MKRESCUE(8)
All times are GMT -4. The time now is 03:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy