[gentoo-user] Re: udev-197: what to do -- S0LVED

On 2013-02-15, Stefan G. Weichinger wrote:

> Am 28.01.2013 00:00, schrieb Allan Gottlieb:
>
>> 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
>
> As I prepare/consider to upgrade a remote gentoo server later this
> evening I prefer to ask twice:
>
> the running kernel 3.5.7 does not have CONFIG_DEVTMPFS=y
>
> I built a new kernel (upgrading it to 3.6.11 btw) with CONFIG_DEVTMPFS=y
> and plan to reboot the server at first.
>
> After a hopefully correct reboot (can't access that server physically) I
> plan to upgrade udev ... (I won't enable the new networking naming, btw).

If you depend in the network device order in any way, and you used names
like the ones the kernel uses, you *have* to do something about the
network device naming.

For example, if you have eth0 and eth1 and you rely on eth0 being A and
eth1 B, you can't  do that anymore with plain udev, even if the rules
are still in place. eth0 may become B and eth1 A.

> Right now I upgrade lvm2 in advance as it doesn't pull in udev yet.
>
> Pls comment or correct my plans ;-)  thanks, Stefan
>
>
>

-- 
Nuno Silva (aka njsg)
http://njsg.sdf-eu.org/