OT(?) -- Should the net.agent script cause "ifup lo" to be run?

[Miles Lane <miles@megapathdsl.net>]

I am wondering how much of the work that is
currently handled by init scripts like
/etc/rc.d/init.d/network ought to migrate into
the hotplug scripts.  If the answer is "almost
none," then how should running of "ifup lo"
get triggered when "ifup ethN" is getting run
from /etc/hotplug/net.agent?  I ask because
I have been experimenting with relying more
on the /etc/rc.d/init/hotplug init script to
get my PCI, net and USB device drivers loaded
and the devices configured.  To this end, I
disabled /etc/rc.d/init/network.  The result
is that booting my system worked great, except
/dev/lo wasn't enabled.  For some reason, mozilla
doesn't finish initializing if /dev/lo isn't
activated.

I suppose this is all stuff that can get sorted
out later by distribution developers, but I
thought there might be some value in sorting out
as much of this boot process stuff as possible
during the hotplug development process.

I hope this isn't too far off topic.

	Miles


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel