On Monday 26 March 2007, Marco d'Itri wrote: > On Mar 26, Brian Cox <[EMAIL PROTECTED]> wrote: > > The subject about says it all. Rather than configuring the > > networking script in /etc/init.d to stop in runlevels 0 and 6, the > > postinst hook for netbase sets it up to start, as you can see from > > this snippet (starting at line 100): > > I am almost sure that there was a reason for this...
If it helps you remember the circumstances or timeline for why it is this way, I have a backup of my rc-links tree from 7 Sep 2005 that also shows S35networking in rc0.d and rc6.d, so it's been like this for at least 1.5 years (since version 4.21 or earlier). I can't find any reference in netbase's changelog that mentions this, although there is an entry from 23 Oct 2005 (version 4.23) about adding LSB data to the init script. The LSB data has the line "Default-Stop: 0 6" in it, which was clearly put into the script *after* it had already been set to start in runlevels 0 and 6 (assuming the timestamp on my rc-links backup is valid). Furthermore, version 4.27 on 1 Oct 2006 adds the Required-Stop field to the init script, presumably after the postinst change, which shouldn't be needed if the stop action is never called, right? Add it all together and it seems rather odd, especially when the "stop" logic is still in the script. Something else I found that may or may not be relevant: Bug #316615 was submitted on 2 Jul 2005 with the title '"Deconfiguring network interfaces" hangs while shutdown/reboot'. It makes explicit references to the script's "stop" section. The bug's reporter was an Ubuntu user, though, and had initially filed the bug against initscripts, so there's no telling without further investigation whether the version of netbase that person may have had was even remotely similar to unstable's netbase at the time. Other than that, I haven't found any other bug reports that relate to this or can help pinpoint a more precise timeline for when the change from "stop" to "start" happened. Cheers, Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
