[gentoo-dev] why is net.eth0 started, even though it's not in any runlevel?

[Sven Köhler]

Hi,

when i load the module for my network-card, then baselayout thinks, that
it's a good idea to a) start net.eth0 even though it's not in any
runlevel and b) start net.eth0 in runlevel boot.

So that's something, that i don't really understand. I think, that the
following behaviour would be more more intuitive:

a) check if net.eth0 is really configured to be started within this boot
(for example it wouldn't be nice, if net.eth0 is started, even though
we're booting into runlevel "nonetwork")

b) schedule net.eth0 to be started later, when we really enter the
runlevel "default" for which net.eth0 is configured


I think, you will actually tell me to use "RC_PLUG_SERVICES" in
/etc/conf.d/rc to disable hotplug triggered started of net.eth0.

But does it really solve everything?