On Sat, Jan 26 2013, Allan Gottlieb wrote:
> 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
Thanks for all the suggestions. I did the following, which worked.
1. Built and installed kernel with CONFIG_DEVTMPFS=y
2. Moved udev-postmount back to /etc/init.d (I had moved it to /tmp).
rc-update add udev-postmount default.
3. Reboot with new kernel (udev unchanged). Success.
4. Changed NAME=eth0 to NAME=net0 in 70-persistent-net.rules and
eliminated clauses so have only (on one line)
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:1e:c9:48:f9:a0",
NAME="net0"
Corresponding changes to /etc/init.d /etc/runlevels/default
5. Emerge update world to get new udev (just -1 udev has blocks)
6. Change kernel configs as per udisks emerge output
7. /usr/lib/udev already empty (due to make world?) so nothing to do
8. Reboot with new kernel. Success
allan
