Sponsored Content
Full Discussion: Mounting on boot up
Top Forums UNIX for Dummies Questions & Answers Mounting on boot up Post 14869 by mib on Thursday 7th of February 2002 09:12:07 AM
Old 02-07-2002
Quote:
Originally posted by nicfellows
Yeah sure - im running redhat linux (7.2) and basically want to mount my floppy + cdrom, and also mount a samba share to my win2000 machine so they are all available on boot up.

Here is my /etc/fstab

/dev/fd0 /fl auto defaults,user,noauto 0 0

/dev/cdrom /cd iso9660 defaults,ro,users,noauto 0 0


and when I want to mount CDROM or Floppy I just type mount /cd or mount /fl. option user in /etc/fstab alows anyone to mount the device.

BTW You can try to mount CD or floppy by bootup by replacing option 'noauto' with 'auto'. And mounting floppy and cdrom on boot is bad idea as system will hang for few minute(s) if tray is empty
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies

2. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

3. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

4. Solaris

Mounting disk at boot

Hi once more :p Yesterday I reinstalled Solaris OS and now I can not mount pcfs HDD SunOS unknown 5.10 Generic_142901-03 i86pc i386 i86pc and what has been added in /etc/vfstab is /dev/dsk/c1t0d0p1:c - /podaci - pcfs - yes rw But as I said , my disk is... (4 Replies)
Discussion started by: solaris_user
4 Replies

5. Ubuntu

mounting shared folder at boot

Hi All Everytime a reboot my machine "hostB" I have to mount a shared (with machine "hostA" ) NFS folder giving this command sudo mount hostA:/sharedFolder /sharedFolder How to use fstab in order to do this automatically? I should say hostA:/sharedFolder /sharedFolder ... (0 Replies)
Discussion started by: manustone
0 Replies

6. SCO

stage 1 boot failure: error loading hd (40)/boot

hi SCO Unix 5.0.6 doesn't boot due to this problem: not a directory boot not found cannot open stage 1 boot failure: error loading hd (40)/boot Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies

7. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies

8. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

9. Solaris

Help mounting nfs on boot on Solaris 11

Hello, I am looking for some assistance in mounting an nfs drive on boot, on a Solaris 11 machine. On my Solaris 9/10 machines, I have an entry for my nfs mount in /etc/vfstab, however when I add the same entry to my vfstab on Solaris 11, the drive will not mount on boot. After booting up, I... (5 Replies)
Discussion started by: bstring
5 Replies
updfstab(8)							   Red Hat Linux						       updfstab(8)

NAME
updfstab - update /etc/fstab to reflect removable devices SYNOPSIS
updfstab [-nt] [--usage] DESCRIPTION
updfstab is designed to keep /etc/fstab consistent with the devices plugged into your system. It looks for devices such as cdroms, zip and jaz drives, ls120 drives, and digital cameras on the SCSI and IDE buses. USB devices look like SCSI devices to user space, so those are supported as well, but are only added if they are currently attached to the system (having a scsi device assigned to them is not suffi- cient). Devices which updfstab adds to /etc/fstab are marked with the kudzu mount option to distinguish them from other devices. updfstab will not remove devices from /etc/fstab unless they are marked with the kudzu mount option. It also ignores devices that are already listed in /etc/fstab, or which have multiple partitions on the media currently inserted. OPTIONS
-c,--config=path Use the configuration specified by path, rather then /etc/updfstab.conf. -n,--normalize Normally, updfstab tries to touch /etc/fstab as little as possible. When this option is given, it will instead move all of the devices with the kudzu mount option to the end of the file, and will list the devices in the same order the internal probe returns. -t,--test When this option is specified, updstab does not update the /etc/fstab file. Instead, it displays the fstab entries it would use to standard out. If no changes need to be made, it outputs the string (nothing to do) rather then a full filesystem table. CONFIGURATION
The devices updfstab looks for are specified by its configuration file, /etc/updfstab.conf by default. It defines a number of devices which updfstab looks for on the system, along with various attributes of that device. If a single device name is given multiple times, later val- ues override those given earlier. However, match directives accumulate; all specified matches remain in effect for that device. The default value of flags may be changed by specifying a new value for that flag outside of any device section, which changes the default for all future devices. A simple configuration file looks like this: # sample updfstab configuration file symlink false device cdrom { symlink true match cdrom } device zip { match hd zip match floppy "zip" } Here two devices are specified, cdrom and zip. If a cdrom device is found on the system, a /dev/cdrom is created pointing to the /dev entry for the device, and /mnt/cdrom is added to /etc/fstab. The next entry looks for hard drive devices with zip in their description as well as floppy devices with zip in their description. If either is found /mnt/zip is added to /etc/fstab, but no symlink is created. Here is the complete list of directives which may be used: device name Set attributes for device name name. The name is used in the /etc/fstab entry and for any symbolic links which are created. include path Parsing of the current configuration file is stopped, and the file specified by path is read for current configuration information. Multiple include directives may be given, but they may not appear inside of device sections. match class string This directive adds a new rule for this device type; devices found on the system which match this rule are considered a device of the type whose section the match directive appears in. The class must be cdrom, floppy, or hd. If string appears, it must be a sub- string of the physical device's description for the rule to match. nofstab val If val is true, updfstab does not add a mount entry to /etc/fstab. This is mainly useful in conjunction with symlink. partition num Specifies a default partition number which should be mounted from this device. If 0 is used, no partition number appears. updfstab always scans /proc/partitions for the proper partition number before relying on this value. skip val The device entry is skipped. This lets a configuration file undefine a device that was defined earlier (such as in an included file). val should be true or false. symlink val If val is true, updfstab creates a symbolic link in the /dev directory pointing to the actual device. This symbolic link is then used in /etc/fstab. FILES
/etc/fstab /etc/updfstab.conf /proc/partitions SEE ALSO
kudzu(1) AUTHORS
Erik Troan <ewt@redhat.com> Red Hat, Inc. 29 Jan 2003 updfstab(8)
All times are GMT -4. The time now is 11:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy