1 |
On 07/27/2014 08:08 AM, Grand Duet wrote: |
2 |
> |
3 |
> If eth0 starts after lo, then I have the right /etc/resolv.conf |
4 |
> file, however if lo starts after eth0, then the DNS IPs in |
5 |
> resolv.conf file are overwritten with dummy instruction |
6 |
> for lo interface. |
7 |
> |
8 |
> But, now, after your suggestion, I have looked into |
9 |
> my /etc/rc.conf file, and have found there the option |
10 |
> rc_parallel="NO" |
11 |
> which softens my previous arguments a bit, but not completely: |
12 |
> may be lo and eth0 are brought up not in parallel but in different |
13 |
> order, anyway. |
14 |
> |
15 |
|
16 |
The first thing I do on any new build is disable network hotplugging in |
17 |
/etc/rc.conf, as I've run into lots of problems, especially if you have |
18 |
multiple network devices and need to bring them up in a specific order. |
19 |
udev processes these items and apparently brings the interfaces up on |
20 |
its own unless you tell it otherwise (the !net.* in rc.conf). I've just |
21 |
gotten used to disabling that automagic because I want things to start |
22 |
in a certain order and udev can mess that up. |
23 |
|
24 |
During boot, you'll see something like 'processing events' and that's |
25 |
when udev is automagically doing it's start. From what I recall, this |
26 |
happens before the boot runlevel. So yes, it can mess things up as |
27 |
you've seen. |
28 |
|
29 |
I've never had the issue you have, even though I use a static ip, routes |
30 |
and dns servers in /etc/conf.d/net, but I would presume that this is |
31 |
just udev. FYI it doesn't always process things in the same order, as |
32 |
I've experienced with udev and my TV tuner cards... it can be random. |
33 |
|
34 |
Dan |