The name of the linux distribution you're using will change the response. For exemple in ubuntu, you have to look at the files in /etc/rc2.d/ Files named S01foo will be launched first, files S99bar and S99baz launched last, in this order, when your start. Files named K-something are here to shutdown services that were active before and not needed in the configuration of services composed by the directory. Have a look at the documentation on boot / init for your machine, this will be spelled. I found this brief introduction: http://en.wikipedia.org/wiki/Init
Back to the ubuntu case, if you simply rename a file from S12 to S99, you push it back to the end of initialization. However, reading fstab and executing the mounts is done very early in the boot process. So I doubt this is the problem, really. You could verify that your fstab lines pertaining the elusive drive do not contain the option noauto. Noauto blocks automatic execution. Remove noauto, or change it to auto. Another possibility I see is wrong ordering of your mounts in fstab: Line 1 - /dev/sda / Line 2 - /dev/sdb /foo/bar Line 3 - /dev/sdc /foo Will leave you with sdc mounted over sdb over sda (or sdb not mounted at all). You would not see the contents of dir "bar" as expected. Reissuing the mount afterwards would succeed. But this would work every time, as the mount order is correct: Line 1 - /dev/sda / Line 2 - /dev/sdc /foo Line 3 - /dev/sdb /foo/bar HTH -- epoch1970 ------------------------------------------------------------------------ epoch1970's Profile: http://forums.slimdevices.com/member.php?userid=16711 View this thread: http://forums.slimdevices.com/showthread.php?t=70344 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
