David Baron wrote:
> Gene Heskett wrote:
> > >I have:
> > >/etc/rc0.d/S35networking
> > >/etc/rc2.d/S99networking
> > >/etc/rc3.d/S99networking
> > >/etc/rc5.d/S99networking
> > >/etc/rc6.d/S35networking
> > >/etc/rcS.d/S40networking
> > >
> > >S99 is what is being hit.
> >
> > And I would call ANY distro that starts networking in the S99files
> > terminally broken. Rename that link so it starts earlier than that.
> > Earlier and earlier till it complains about something it needs. Then go
> > rename that one too.
Those init.d files are not stock Debian. They have been modified.
However since the rc0.d and rcS.d files still exists with low numbers
then networking will start very early. Those S99 files are simply red
herrings for you distracting you from what is really happening.
> So I would assume either the S35 or the S40 should be OK. I will
> post the the Debian list and ask about this>
A stock Debian installation has the following:
/etc/rc0.d/S35networking
/etc/rc6.d/S35networking
/etc/rcS.d/S40networking
> > >This is Debian box originally set up from a Knoppix hd installation. I
> > > have not fiddled with any of these. I assume there is decent reason for
> > > the numbering schemes for these scripts.
KNOPPIX is not Debian. KNOPPIX is a different software distribution
that is based on Debian. It is a great live cdrom system. But I
would not recommend it for a hard drive installation. It had
different goals.
Reaching into the guts of things, if you wanted to reset everything to
package defaults the following should do it. However this is untested
and so should be double checked before firing for effect.
$ grep update-rc.d.*start /var/lib/dpkg/info/netbase.postinst
update-rc.d networking start 40 S . start 35 0 6 . > /dev/null
$ rm /etc/rc?.d/*networking
$ update-rc.d networking start 40 S . start 35 0 6 .
> Problem is that with every upgrade, those rc#.d files may be restored
> if I am not careful.
Actually they won't. Once you have modified the init.d symlinks the
Debian package scripts avoid modifying them further to avoid stomping
on top of your local changes. This is policy. Any package that does
not do this is in violation of the policy and warrents a serious bug
report.
Bob
