capella ~ # /etc/init.d/net.ra0 stop * Caching service dependencies ... [ ok ] * Stopping ra0 * Bringing down ra0 * Shutting down ra0 ... [ ok ] * Selecting best interface: br0 capella ~ # rmmod rt2500 capella ~ # modprobe rt2500 capella ~ # /etc/init.d/net.ra0 status * status: started At least thanks to bug 118419 I know this is by design (/etc/hotplug/net.agent). I can even see it might be useful (say when plugging in a WiFi PCMCIA card, or a Bluetooth dongle). However, when I'm setting up or debugging a network, I do not want Gentoo to go around configuring interfaces without asking or telling me. Ideally, this behaviour would occur in response to hardware insertion events and not to admin-originated module insertion. But I'd be happy just with a way to turn it off altogether; maybe a setting in /etc/conf.d/rc?
Yes, we already have this ability to not bring up network devices automatically by hotplug events. I see the code in the scripts, but can't find where a user can set this to prevent this from happening. Anyone else willing to point in the proper place?
You can always get blacklist the module in /etc/hotplug/blacklist With baselayout-1.12, you can do this in conf.d/rc (may work in 1.11, not sure) hotplug_ra0="no" We could always add a generic RC variable though RC_HOTPLUG_INTERFACE="yes|no"
(In reply to comment #2) > With baselayout-1.12, you can do this in conf.d/rc (may work in 1.11, not sure) > hotplug_ra0="no" Actually that belongs in conf.d/net
Isn't automagic connection to various networks ifplugd's role? That would leave it entirely up to the user without adding any additional flags, assuming of course that ifplugd can be coerced into playing nicely with interfaces that don't always exist...
(In reply to comment #4) > Isn't automagic connection to various networks ifplugd's role? That would leave > it entirely up to the user without adding any additional flags, assuming of > course that ifplugd can be coerced into playing nicely with interfaces that > don't always exist... > This has nothing todo with ifplugd. Infact if it's wired ethernet then baselayout 1.12 launches ifplugd or netplug as a controlling daemon.
*** Bug 122964 has been marked as a duplicate of this bug. ***
*** Bug 122982 has been marked as a duplicate of this bug. ***
baselayout-1.12.0_pre19-r2 should solve the initial bug report.
