I'm confused by this thread. Is there a special behaviour of fstab specific to z/Linux? On every other UNIX or UNIX-clone system I have ever used including Linux on the x86 and powerpc platforms, the two integer values at the end of an fstab config line have nothing whatever to do with automatic mounting.
instead, all entries are automatically mounted at boot unless the NOAUTO keyword is given. the numbers, as best I understand, represent the following: field 5 (first integer field) specifies a dump frequency. for more info see man -s8 dump field 6 (second integer field) specifies fsck order. this is very very simple a value of zero means "do not examine this volume on boot" a value of one means "this volume must be checked first" this option should be used only for the root filesystem a value of two means "this volume may be checked at any time subsequent to the root volume" typically this means that logical volumes on the same physical volume are checked in series, volumes on distinct physical hardware will be checked concurrently, obviously because of hardware constraints. afaik it is possible to specify values >2 which would then indicate, these volumes should be checked only after all volumes with an fs-check value of 2, and so on and so forth. Please, if I am in some way in error, somebody let me know! I'd hate to discover that my *nix boxen were doing bizarre things at boot up. I can tell you this though, all my volumes mount at boot except for optical drives and one nfs mount (specifically /usr/home on my fileserver which automounts on my Linux and BSD boxen but not on my Mac, I do have an fstab entry on my mac, bearing the noauto keyword, as well as an fs-check value of zero (there should be no need to fsck network mounts as they are checked when the providing host boots. I don't even know if fsck works at all on network filesystems, as I believe it bypasses the typical VFS abstraction and works on the physical hardware directly.) Again, if I am in error, please let me know! Erik Johnson On Wed, Mar 18, 2009 at 2:05 PM, Scott Rohling <[email protected]> wrote: > Works fine from /etc/fstab.. just use the same format as the mount (not > sure what the colon was about): > > //192.168.20.2/Media /Media smbfs ro, blah blah > > Scott > > On Wed, Mar 18, 2009 at 12:18 PM, Mark D Vandale <[email protected]> wrote: > >> Can smbfs be mounted from /etc/fstab ? I can issue the cmd "mount -f >> smbfs //ipaddress/dirname /dirname username=testid,password=testpw" and >> get the smbfs mounted but I can't get this mounted by adding a line in >> the /etc/fstab . The format in the /etc/fstab is more like --> >> //ipadress:/dirname /dirname smbfs ro,username=testid,password=testpw 0 >> 0 Is this possible from /etc/fstab or do I need to do this from somewhere >> else ? This is SUSE SLES10. >> >> Thanks, >> >> Mark >> >> >> This is a PRIVATE message. If you are not the intended recipient, please >> delete without copying and kindly advise us by e-mail of the mistake in >> delivery. >> NOTE: Regardless of content, this e-mail shall not operate to bind CSC to >> any order or other contract unless pursuant to explicit written agreement >> or government initiative expressly permitting the use of e-mail for such >> purpose. >> >> ---------------------------------------------------------------------- >> For LINUX-390 subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO LINUX-390 or >> visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
