Re: hotplug and ifup
On Sat, Mar 27, 2004 at 08:31:27PM +0100, Osamu Aoki wrote:
> On Sun, Mar 21, 2004 at 06:32:34PM +0100, Thomas Hood wrote:
> > On Sun, 2004-03-21 at 14:49, Fumitoshi UKAI wrote:
> > > At Sat, 20 Mar 2004 22:06:44 +0100,
> > > Thomas Hood wrote:
> > > > At Sat, 20 Mar 2004 14:37:45, Fumitoshi UKAI wrote:
> > > > > ... the latest version of hotplug ... finds pci devices at
> > > > > boot time, so if you configure to use "mapping hotplug" in
> > > > > /etc/network/interfaces, /etc/rcS.d/S39hotplug will load
> > > > > kernel drivers and will bring network interfaces up with
> > > > > "ifup ethN=hotplug".
> > > >
> > > > Too bad networking is only initialized at S40!
> > > >
> > > > This bug didn't exist when hotplug used the /etc/nohotplug
> > > > mechanism to delay the processing of hotplug events at boot.
> > > > Now that that mechanism has been eliminated, the bug would
> > > > seem to be back. Or is the race rectified in some other way?
> > Answering my own question ... What has been done is that the
> > hotplug link has been moved from S36 to S40 (not S39). The
> > question now is: Is that enough?
> On my system, I was relying hotplug started by discover probing to start
> network. I do not use auto stanza. This was working until recently.
> Last few weeks, the sytem was very erratic in booting. I usually booted
> to single user mode and configured network since I did not have any
> network other than lo or sometimes no lo.
> I think using auto stanza in /etc/network/interfaces is one solution but
> I miss probing with discover and getting network running.... was this
> non-supported way of using discover?
Bug #240363 was the reason of trouble.
modprobe was the root cause. I patched /sbin/discover-modprobe and now
Also init order seems OK now.