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

[Sven Köhler]

>> 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.
>
> yes, the default behavior is to do hot/cold plugging

That is not a problem. The problem is, that the admin loses control over
the runlevels.

> if you dont like that, you're free to:
>> 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?
>
> i disable hot/cold plugging completely myself

i see, another sollution could be:

instead of having tweo states per service and runlevel (enabled,
disabled), gentoo could introduce a tristate-logic:

services can be disabled, enabled or they can be set to auto.

These states have the following meaning:
disabled: the service does not start and will not be started by any
hot/coldplugging
enabled: the service is started on boot (and maybe not by hot/cludplugging)
auto: the service started by hot/coldplugging things