I have read the news item and still have questions. The news item
covers several points.
1. remove udev-postmount:
I did this but worry that I now cannot reboot until I upgrade
udev. Is that correct?
2. Add CONFIG_DEVTMPFS=y. Easy. Kernel rebuilt and installed
in /boot (but have not rebooted).
3. Predictable network interface names.
I have the problematic udev rule.
Specifically 70-persistent-net.rules has (on one line)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:1e:c9:48:f9:a0", ATTR{type}=="1",
KERNEL=="eth*", NAME="eth0"
I read the bug report, but it is not as clear as I would like.
Is it true that I can change my file to simply
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="00:1e:c9:48:f9:a0", ATTR{type}=="1",
KERNEL=="eth*", NAME="net0"
That is just change the NAME from eth0 to net0 ?
4. No support for kernels older than 2.6.39. No problem.
5. Separate /usr not affected. Good.
The news item does not mention the problem of moving files
from /usr/lib/udev/rules.d to /lib/udev/rules.d. Am I correct in
believing that we still need one of the equivalents of
equery belongs -n /usr/lib/udev | xargs emerge -pv
I used that successfully when one of my testing systems went to
udev-197. I would think it is needed (before reboot) on my stable
systems as well so I am surprised it is not in the news item.
thanks,
allan
