On Fri, Sep 08, 2006 at 11:36:12 -0400, Scott Reese wrote:
> Florian Kulzer wrote:
>
> > That might be caused by a missing S36udev-mtab link in rcS.d.
> >
> > The root of the problem seems to be a bug in sysv-rc, which made
> > update-rc.d remove existing links in rcS.d. Details are in bug #386500.
> >
> > For me it was enough to run "dpkg-reconfigure udev" to have both
> > symlinks generated again, as proposed in the discussion of the bug.
> > Other services might also be affected, if their packages were upgraded
> > while the bug was present in sysv-rc.
> >
>
> Greetings Florian:
>
> Did the dpkg-reconfigure udev recreate two links for you in /etc/rcS.d
> or just the S36udev-mtab link? If it created a udev link, what did that
> look like?
Hi Scott,
As Morten has already posted, it should be:
$ ls -l /etc/rc?.d/*udev*
lrwxrwxrwx 1 root root 14 2006-09-08 16:46 /etc/rcS.d/S03udev -> ../init.d/udev
lrwxrwxrwx 1 root root 19 2006-09-08 16:46 /etc/rcS.d/S36udev-mtab ->
../init.d/udev-mtab
If you are in this situation again you can check out the /etc/init.d/...
scripts. Many of them have something like this in the header:
### BEGIN INIT INFO
# Provides: udev
# Required-Start: mountkernfs
# Required-Stop:
# Default-Start: S
# Default-Stop:
# Short-Description: Start udevd, populate /dev and load drivers.
### END INIT INFO
This tells you that the service has to be started after mountkernfs, so
it has to be S03 or higher. When in doubt I would always use the lowest
possible number.
--
Regards,
Florian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
