Sponsored Content
Special Forums Hardware Boot Loaders How to install grub on USB flash drive? Post 302463141 by Corona688 on Friday 15th of October 2010 11:10:33 PM
Old 10-16-2010
You may have to put it in your fstab, at least temporarily.
 

10 More Discussions You Might Find Interesting

1. Solaris

USB flash Drive

Hello all.. I have a Verbatim 2 GB flash drive. I also have Solaris 10 running on my workstation. If I am in the Windows environment, it detects the flash drive. But when I plug it while I am in solaris, nothing happens. How will solaris 10 detect my flash drive? What do I have to do? any... (4 Replies)
Discussion started by: vr76413
4 Replies

2. UNIX for Dummies Questions & Answers

USB flash drive is not mounting what to do...?

hello forum.. i am using RHEL 4.0 and my system is dual boot.normally the usb flash drive should be auto mount , but in my system i am unable to mount the drive plz help... i am a new user so plz give me in detail. thank u in advance. (5 Replies)
Discussion started by: manoranjan
5 Replies

3. SCO

mounting USB floppy drive /Flash drive in OSR 6.0

Can anybody help me out to mount USB flash /floppy drive in sco openserver 6.0 . (5 Replies)
Discussion started by: sureshdrajan
5 Replies

4. UNIX for Dummies Questions & Answers

Does HPUX 10.2 or 11.i support any USB flash drive?

Where can I get a driver that support usb flash drives for my unix machines. I need a solution to transfer data easily for techs. I am running C3750 and c8000 HP equipment. Or is there a way to mount them and use them without adding drivers? thanks! (0 Replies)
Discussion started by: jkend12
0 Replies

5. Solaris

removable usb flash drive

# rmformat Looking for devices... 1. Logical Node: /dev/rdsk/c0t0d0p0 Physical Node: /pci@0,0/pci-ide@1f,1/ide@0/sd@0,0 Connected Device: HL-DT-ST DVD+-RW GWA4164B E113 Device Type: DVD Reader/Writer 2. Logical Node: /dev/rdsk/c2t0d0p0 Physical Node:... (26 Replies)
Discussion started by: seyiisq
26 Replies

6. Ubuntu

USB flash drive/keyfob will not automount

I am working on an Ubuntu Linux 8.10 system that I do not want to reboot. For some reason, USB flash drives (mass storage devices) now no longer automount. I want to restore that functionality without rebooting. I can manually mount and unmount these things by doing: cd /media sudo mkdir thing... (4 Replies)
Discussion started by: ropers
4 Replies

7. UNIX for Dummies Questions & Answers

SCO 5.0.5 & USB flash drive

Can someone help me with instructions on how to access a USB flash drive in SCO Unix 5.0.5? I need to copy ASCII text files that have been zipped onto the USB drive for transfer to a Windows computer. (0 Replies)
Discussion started by: jlodata
0 Replies

8. Solaris

Installing Solaris 10 x86 from USB flash drive

Dear friends, I have the DVD image of solaris 10 but I don't have DVD writer to burn it onto a dvd R. I was wondering if I could install Solaris from my 4gb usb flash drive as my PC supports booting from usb. I have installed Windows 7 this way recently, I have no idea about Solaris. Could you... (2 Replies)
Discussion started by: gabam
2 Replies

9. UNIX for Advanced & Expert Users

how to increase cylinders on USB Flash Drive

Hello All, I faced a unique issue. I have written a script for transferring backup data on my host machine to a USB Flash drive. The Flash drive must be of 16GB size. So, my script creates two primary partitionon the USB flash drive. I require approx 5900 cylinders for the first partition on... (8 Replies)
Discussion started by: Pkumar Sachin
8 Replies

10. Linux

Repeated corruption running linux on USB flash drive

I have a HP Proliant N40L server and in the internal USB socket I have a 16GB HP v195b flash drive on which I have a full copy of Debian installed from a copy of the DVD1 ISO image. In as far as installation and operation goes my setup works okay, but I keep experiencing corruption of the file... (0 Replies)
Discussion started by: mij
0 Replies
SYSTEMD-FSTAB-GENERATOR(8)                                    systemd-fstab-generator                                   SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 06:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy