On Wed, Feb 26, 2003 at 02:19:40AM +0900, Fumitoshi UKAI wrote:
> At Sun, 23 Feb 2003 13:13:36 +1000,
> > > > what should happen, and how should it happen? Should:
> > > hotplug should tell ifup that it is calling it, perhaps by using
> > > a special option. Then ifup can decide what the policy is.
> > ifup can't be called before S39ifupdown has been run, which is the
> > problem here.
> Hmm, then should I fix at least hotplug should be activated
> after S39ifupdown? Maybe I should support blacklist (Bug#180521).
Blacklist seems like fairly awkward -- everytime you have a new network
module to autoload on boot, you need to specifically add it to the
blacklist.
My thought was to delay the execution of the hotplug stuff until later
in the boot cycle. Maybe simply adding something to hotplug like:
while [ -e /etc/nohotplug ]; do sleep 5; done
and having a "touch /etc/nohotplug" early in the boot sequence, and
"rm /etc/nohotplug" at the end of /etc/rcS.d would work okay.
The main thing is not to do hotplug for network stuff before S39ifupdown
is run -- delaying it is fine, there's no need to avoid it altogether.
Cheers,
aj
--
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.
``Dear Anthony Towns: [...] Congratulations --
you are now certified as a Red Hat Certified Engineer!''
Attachment:
pgp3SpQoa5g9I.pgp
Description: PGP signature