Ian Lee wrote: > Dale wrote: >> Harry Putnam wrote: >>> Ian Lee <i...@leehouse.eclipse.co.uk> writes: >>> >>> >>>> Ian Lee wrote: >>>> >>>>> Neil Bothwick wrote: >>>>> >>>>>> On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote: >>>>>> >>>>>> >>>>>>>> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf >>>>>>>> >>>>>> >>>>>>> That's in /etc/conf.d/rc on mine. Has it moved? >>>>>>> >>>>>> It moved in the switch from baselayout1 to baselayout2/openrc. >>>>>> >>>>>> >>>>>> >>>>> This could be what four looking for >>>>> >>>>> http://bugs.gentoo.org/show_bug.cgi?id=206518 >>>>> >>>>> >>>>> >>>>> Ian >>>>> >>>>> >>>> try putting rc_coldplug="no" in conf.d/udev or /etc/rc.conf i would >>>> assume the udev init script checks both places >>>> >>> I can tell you from trying that just now... that is not a good >>> solution. >>> >>> First setting rc_coldplug="no" has some very bad effects: >>> 1) caused my KVM switch setup to be ignored completely, where as with >>> with the default "yes" the kvm is recognized soon as I get past >>> grub >>> >>> 2) Very strange behavior with the `screen' tool. I call screen and >>> get started but if I do `C-a c' (which should start another screen) >>> Instead it prompts me to login and then takes the original screen >>> so I can only get one screen, completely defeating the purpose of >>> `screen'. >>> >>> I'm also wondering about the wisdom introduciing some esoteric places >>> to control services. If someone needs sophisticated controls they can >>> set that up, but for the rest of us /etc/conf.d and rc-update should >>> be THE central tools to have basic services started at boot. >>> >>> There should be nothing scrolling thru the network softlinks >>> attempting to start anything it finds. >>> >>> >>> >>> >> >> If you check mine and Neils post, one of ours will do just what you want >> and still allow you to have hotplug set to yes. It just tells hotplug >> not to start networks itself and leave it to your own settings with >> rc-update. There may also be other things that you can set in there as >> well. >> Dale >> >> :-) :-) >> > > According to the comments hotplugging of services is not allowed by > default, so why do the net.* services get started? > > Because it does start them unless that line is in the correct file. I ran into this a good while back and had to add that line to mine as well. Some of my cards are not even connected to anything and during boot up it would wait until it timed out before going to the next one. I have three cards so that got on my nerves to say the least. I think it was set to timeout=forever or timeout=until-dale-is-pissed. o_O
I would try it and just see if it helps. If not, nothing lost right? Dale :-) :-)
