[Voyage-linux] Re: Problem mounting nfs disk at boot time with fstab.
curlynostrill
(spam-protected)
Mon Feb 14 12:10:58 HKT 2011
I'm not currently using voyage but I'm subscribed for when I do start to use
it so I'm not very familiar with the specifics of voyage but it is basically
debian so most of this should apply, even if somewhat loosely.
The "K" in K75netfs stands for "Kill". The "S" in S96netfs stands for
"Start". Usually runlevels are defined in /etc/inittab (#cat /etc/initttab)
and your default runlevel should be defined there as well. You can also get
your current runlevel by typing "runlevel" (without quotes) at the command
prompt. You might have to use "sudo" or be root if you don't have sudo
installed for that command.
/etc/rcS.d/ holds the links to essential services and one of my Debian
installs has S17portmap and S18nfs-common in rcS.d but also in rc2.d, rc3.d,
rc4.d and rc5.d. You might not have that many runlevels. Scripts are
processed in numerical order so S17 starts before S18. rc0.d and rc6.d will
have "K" links since those are shutdown runlevels and rc1.d is for single
user where you get a very basic system for maintenance, etc. YMMV.
If you reorder something or change a K to an S you should probably run
'update-rc.d <scriptname> defaults'. You might also have a README in each
rcx.d/ directory giving some info for that directory.
--
View this message in context: http://voyage-linux.34677.n3.nabble.com/Problem-mounting-nfs-disk-at-boot-time-with-fstab-tp2488225p2489580.html
Sent from the Voyage Linux mailing list archive at Nabble.com.
More information about the Voyage-linux
mailing list