[nSLUG] Another debian issue resolved

Donald Teed donald.teed at gmail.com
Wed Jun 15 17:45:18 ADT 2005

My network was not coming up on boot up.  I believed
it had been set up in the interfaces file, but I forgot
the keyword 'auto' and didn't realize this for awhile.
I didn't have a quick tool to check on what inits are
set to start, and so I used update-rc.d to add networking.

Or perhaps I did have rcconf at that point and it showed
networking was missing, and then I decided to add it.
Now that I think about it, rcconf probably only shows
what is happening on the default run level or something like it.
That would explain what I saw.

It isn't clear when you need to, or you do not need
to add your inits after installing them.  From Gentoo,
I'm accustomized to running rc-update for everything,
since you build it from the base up.

Thanks for the correct sequences...

On 6/15/05, Ben Armstrong <synrg at sanctuary.nslug.ns.ca> wrote:
> On Wed, 2005-06-15 at 07:53 -0300, Donald Teed wrote:
> > By default, anything set up with update-rc.d gets
> > a sequence code of 20.  There are a bunch of network
> > related inits set as 20.  I probably added some of those
> > via the update-rc.d defaults.  I can't think of an distro I've
> > used before where I've ever had to play with the sequence
> > codes, except picking one for a package alien to that distro.
> Ah, again I am missing bits of what you said.  So, if *you* put the
> "networking" script at 20, that explains it.  You've broken your system.
> The "networking" script is supposed to be set up as follows:
> /etc/rc0.d/S35networking
> /etc/rc6.d/S35networking
> /etc/rcS.d/S40networking
> You need to really take care when running update-rc.d to change the load
> order.  As you guessed, you don't normally need to do this.
> Ben
> _______________________________________________
> nSLUG mailing list
> nSLUG at nslug.ns.ca
> http://nslug.ns.ca/cgi-bin/mailman/listinfo/nslug


More information about the nSLUG mailing list