On Wednesday 25 July 2007, Bob Proulx wrote: > David Baron wrote: > > > /etc/rc0.d/S35networking > > > /etc/rc6.d/S35networking > > > /etc/rcS.d/S40networking > > > > Is not the final run level 5. > > The default runlevel is 2 in Debian. Unless otherwise modified all > run levels have the same configuration and are identical to each other > in Debian. You are free to configure runlevels 2-5 for any purpose > that you wish however. Any changes that are made will be thereafter > preserved across upgrades. > * * * > The runlevel S is used to initialize the system at system boot time. > Normally a system boots to runlevel S, runs all of the S* scripts, > then proceeds to the default runlevel 2, and runs all of the S* > scripts. The /etc/rcS.d/S40networking should typically start > networking quite early in the boot cycle. > * * * > > My network does not start up until the very end so other "99" > > scripts may not have a connection which was the problem. > > That does seem to indicate that something is amiss. > > > It would be simple enough to get rid of the other symlinks and see > > what happens. > > I would definitely try that. But it does not make sense to me that it > would actually change things. But KNOPPIX may have made changes to > better facilitate a live cdrom boot system. I don't know.
I tried it. Works OK. "Networking" startup place did not, as you suggested it would not, change. There are more pieces to the puzzle. There is "networking", "inetd super-server" and whatever actually logs on to my provider. The networking is S40 or S35, the inetd is S20 though its startup message appears AFTER networking's. The actual logon -- I am not sure where this is done and thar's the rub :-)
