Gentoo Archives: gentoo-user

From: "Nuno J. Silva (aka njsg)" <nunojsilva@×××××××.pt>
To: gentoo-user@l.g.o
Subject: [gentoo-user] Re: Udev update and persistent net rules changes
Date: Sat, 30 Mar 2013 16:29:46
Message-Id: kj73sj$c96$1@ger.gmane.org
In Reply to: [gentoo-user] Udev update and persistent net rules changes by Tanstaafl
1 On 2013-03-30, Tanstaafl <tanstaafl@×××××××××××.org> wrote:
2 > Ok, just read the new news item and the linked udev-guide wiki page, and
3 > the only thing left that I'm unsure/concerned about now is the
4 > persistent net rules changes...
5 >
6 > The very last line on the wiki page says:
7 >
8 >> 4. Known problems
9 >>
10 >> Stale 70-persistent-net.rules (or other network rules) in
11 >> /etc/udev/rules.d can prevent the predictable network naming from being
12 >> enabled. Both 70-persistent-net.rules and 70-persistent-cd.rules are
13 >> from the now deleted rule_generator
14 >
15 > These 'stale' 70- rules are all I have right now (again I'm still on
16 > udev-171-r10), and while the wiki page doesn't say what to do with/about
17 > them, it seems to hint that I could leave these in place and... they
18 > would still work as they did previously (prevent the predictable network
19 > naming from being enabled)?
20 >
21 > My system (8+ years old) has a Tyan motherboard (S2895) with dual Gb
22 > ethernet ports, with only one port currently used (but both are enabled
23 > in the BIOS so both are listed in my current rules file).
24
25 (And, more importantly, they're seen and handled by the running kernel.)
26
27 [...]
28 > Contents of 70-persistent-net.rules:
29 >
30 >> # PCI device 0x10de:0x0057 (forcedeth)
31 >> SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:e0:81:54:9c:8b", KERNEL=="eth*", NAME="eth1"
32 >>
33 >> # PCI device 0x10de:0x0057 (forcedeth)
34 >> SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:e0:81:54:9c:8a", KERNEL=="eth*", NAME="eth0"
35 >
36 > So... after reading the new news item, am I right that all I need to do
37 > to make sure that my network comes up properly is... edit the 80-*
38 > rule(s) that are created after udev is updated to make sure the same
39 > adapters that were named eth0/1 are now named net0/1, and the kernel
40 > will now take care of naming net0/1 eth0/1?
41
42 You can either remove it and get what udev gives you (a bit more
43 cryptic, but it is supposed to be somewhat persistent unless the cards
44 are moved around, or there are major kernel changes), or you can give
45 them the names you want, as far as it's not ethX.
46
47 But you will always have to update other config files (firewall, init
48 scripts, etc.) to have the new names.
49
50 > Also, is it critical to remove (or at least rename) the old 70- rules
51 > *before* the update, or just be sure to do so before I reboot after the
52 > update?
53
54 No idea, I'd expect it to be only needed for the reboot, but I don't
55 know udev *that* well.
56
57 > Thanks - I'm sure I'm just being paranoid, but it has helped me to avoid
58 > lots of pain in the past with other major updates on this system over
59 > these last 8+ years.
60 >
61 > (I'm not concerned about the cd rule because obviously that won't affect
62 > the system booting, so I can come back and fix this one later if needed)
63
64 --
65 Nuno Silva (aka njsg)
66 http://njsg.sdf-eu.org/