| 1 |
Ian Lee wrote: |
| 2 |
> Dale wrote: |
| 3 |
>> Harry Putnam wrote: |
| 4 |
>>> Ian Lee <ian@×××××××××××××××××××.uk> writes: |
| 5 |
>>> |
| 6 |
>>> |
| 7 |
>>>> Ian Lee wrote: |
| 8 |
>>>> |
| 9 |
>>>>> Neil Bothwick wrote: |
| 10 |
>>>>> |
| 11 |
>>>>>> On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote: |
| 12 |
>>>>>> |
| 13 |
>>>>>> |
| 14 |
>>>>>>>> Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf |
| 15 |
>>>>>>>> |
| 16 |
>>>>>> |
| 17 |
>>>>>>> That's in /etc/conf.d/rc on mine. Has it moved? |
| 18 |
>>>>>>> |
| 19 |
>>>>>> It moved in the switch from baselayout1 to baselayout2/openrc. |
| 20 |
>>>>>> |
| 21 |
>>>>>> |
| 22 |
>>>>>> |
| 23 |
>>>>> This could be what four looking for |
| 24 |
>>>>> |
| 25 |
>>>>> http://bugs.gentoo.org/show_bug.cgi?id=206518 |
| 26 |
>>>>> |
| 27 |
>>>>> |
| 28 |
>>>>> |
| 29 |
>>>>> Ian |
| 30 |
>>>>> |
| 31 |
>>>>> |
| 32 |
>>>> try putting rc_coldplug="no" in conf.d/udev or /etc/rc.conf i would |
| 33 |
>>>> assume the udev init script checks both places |
| 34 |
>>>> |
| 35 |
>>> I can tell you from trying that just now... that is not a good |
| 36 |
>>> solution. |
| 37 |
>>> |
| 38 |
>>> First setting rc_coldplug="no" has some very bad effects: |
| 39 |
>>> 1) caused my KVM switch setup to be ignored completely, where as with |
| 40 |
>>> with the default "yes" the kvm is recognized soon as I get past |
| 41 |
>>> grub |
| 42 |
>>> |
| 43 |
>>> 2) Very strange behavior with the `screen' tool. I call screen and |
| 44 |
>>> get started but if I do `C-a c' (which should start another screen) |
| 45 |
>>> Instead it prompts me to login and then takes the original screen |
| 46 |
>>> so I can only get one screen, completely defeating the purpose of |
| 47 |
>>> `screen'. |
| 48 |
>>> |
| 49 |
>>> I'm also wondering about the wisdom introduciing some esoteric places |
| 50 |
>>> to control services. If someone needs sophisticated controls they can |
| 51 |
>>> set that up, but for the rest of us /etc/conf.d and rc-update should |
| 52 |
>>> be THE central tools to have basic services started at boot. |
| 53 |
>>> |
| 54 |
>>> There should be nothing scrolling thru the network softlinks |
| 55 |
>>> attempting to start anything it finds. |
| 56 |
>>> |
| 57 |
>>> |
| 58 |
>>> |
| 59 |
>>> |
| 60 |
>> |
| 61 |
>> If you check mine and Neils post, one of ours will do just what you want |
| 62 |
>> and still allow you to have hotplug set to yes. It just tells hotplug |
| 63 |
>> not to start networks itself and leave it to your own settings with |
| 64 |
>> rc-update. There may also be other things that you can set in there as |
| 65 |
>> well. |
| 66 |
>> Dale |
| 67 |
>> |
| 68 |
>> :-) :-) |
| 69 |
>> |
| 70 |
> |
| 71 |
> According to the comments hotplugging of services is not allowed by |
| 72 |
> default, so why do the net.* services get started? |
| 73 |
> |
| 74 |
> |
| 75 |
Because it does start them unless that line is in the correct file. I |
| 76 |
ran into this a good while back and had to add that line to mine as |
| 77 |
well. Some of my cards are not even connected to anything and during |
| 78 |
boot up it would wait until it timed out before going to the next one. |
| 79 |
I have three cards so that got on my nerves to say the least. I think |
| 80 |
it was set to timeout=forever or timeout=until-dale-is-pissed. o_O |
| 81 |
|
| 82 |
I would try it and just see if it helps. If not, nothing lost right? |
| 83 |
|
| 84 |
Dale |
| 85 |
|
| 86 |
:-) :-) |
Archives