1 |
Ok, just read the new news item and the linked udev-guide wiki page, and |
2 |
the only thing left that I'm unsure/concerned about now is the |
3 |
persistent net rules changes... |
4 |
|
5 |
The very last line on the wiki page says: |
6 |
|
7 |
> 4. Known problems |
8 |
> |
9 |
> Stale 70-persistent-net.rules (or other network rules) in |
10 |
> /etc/udev/rules.d can prevent the predictable network naming from being |
11 |
> enabled. Both 70-persistent-net.rules and 70-persistent-cd.rules are |
12 |
> from the now deleted rule_generator |
13 |
|
14 |
These 'stale' 70- rules are all I have right now (again I'm still on |
15 |
udev-171-r10), and while the wiki page doesn't say what to do with/about |
16 |
them, it seems to hint that I could leave these in place and... they |
17 |
would still work as they did previously (prevent the predictable network |
18 |
naming from being enabled)? |
19 |
|
20 |
My system (8+ years old) has a Tyan motherboard (S2895) with dual Gb |
21 |
ethernet ports, with only one port currently used (but both are enabled |
22 |
in the BIOS so both are listed in my current rules file). |
23 |
|
24 |
Contents of rules.d: |
25 |
|
26 |
myhost : Sat Mar 30, 08:33:28 : ~ |
27 |
# ls -al /etc/udev/rules.d |
28 |
total 16 |
29 |
drwxr-xr-x 2 root root 4096 Feb 23 15:04 . |
30 |
drwxr-xr-x 4 root root 4096 Feb 23 15:04 .. |
31 |
-rw-r--r-- 1 root root 1187 Apr 11 2010 70-persistent-cd.rules |
32 |
-rw-r--r-- 1 root root 492 Feb 23 15:04 70-persistent-net.rules |
33 |
-rw-r--r-- 1 root root 0 Feb 23 15:04 .keep_sys-fs_udev-0 |
34 |
myhost : Sat Mar 30, 08:33:29 : ~ |
35 |
|
36 |
Contents of 70-persistent-net.rules: |
37 |
|
38 |
> # This file was automatically generated by the /lib/udev/write_net_rules |
39 |
> # program, probably run by the persistent-net-generator.rules rules file. |
40 |
> # |
41 |
> # You can modify it, as long as you keep each rule on a single line. |
42 |
> |
43 |
> # PCI device 0x10de:0x0057 (forcedeth) |
44 |
> SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:e0:81:54:9c:8b", KERNEL=="eth*", NAME="eth1" |
45 |
> |
46 |
> # PCI device 0x10de:0x0057 (forcedeth) |
47 |
> SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:e0:81:54:9c:8a", KERNEL=="eth*", NAME="eth0" |
48 |
|
49 |
So... after reading the new news item, am I right that all I need to do |
50 |
to make sure that my network comes up properly is... edit the 80-* |
51 |
rule(s) that are created after udev is updated to make sure the same |
52 |
adapters that were named eth0/1 are now named net0/1, and the kernel |
53 |
will now take care of naming net0/1 eth0/1? |
54 |
|
55 |
Also, is it critical to remove (or at least rename) the old 70- rules |
56 |
*before* the update, or just be sure to do so before I reboot after the |
57 |
update? |
58 |
|
59 |
Thanks - I'm sure I'm just being paranoid, but it has helped me to avoid |
60 |
lots of pain in the past with other major updates on this system over |
61 |
these last 8+ years. |
62 |
|
63 |
(I'm not concerned about the cd rule because obviously that won't affect |
64 |
the system booting, so I can come back and fix this one later if needed) |