Re: [gentoo-user] Re: udev upgrade and non-working eth0

[Richard Fish]

On 11/27/06, Mrugesh Karnik <mrugeshkarnik@×××××.com> wrote:
> On Tuesday 28 November 2006 07:31, Richard Fish wrote:
> > > can see a 75-persistent-net-generator.rules file in there..
> >
> > Hmm, not sure how I got a 70-persistent-net.rules.  There is some
> > interaction between that and 75-persistent-net-generator.rules (and
> > the /lib/udev/write_net_rules script), but I'm a bit too tired to
> > figure it out ATM.  It looks like 70-... should be created by the
> > write_net_rules script...
>
>
> RULES_FILE='/etc/udev/rules.d/70-persistent-net.rules'
>
> That's the first line of write_net_rules.

Right.  I just wasn't able to figure out why you didn't already have
this file created, nor why my laptop had it but not my desktop.

So the story is that 75-persistent-net-generator.rules will call the
script when ethernet devices are added, and it is up to the
write_net_rules script to generate 70-persistent-net.rules.  The
problem is that when udev starts very early in the boot process, your
root filesystem may still be mounted read-only, preventing this file
from being created.

This worked on my laptop, because I added module aliases to prevent
udev from coldplugging the ipw3945 driver, since it requires a daemon
to be running in order to work and that required /var to be mounted.
The module is loaded later in the boot process, after all of the
filesystems are mounted read-write, and that allowed udev to create
the rules file for me, but only for that adapter.

The upshot of this is this: by far the easiest way to solve the
net-naming problem is to run

/lib/udev/write_net_rules all_interfaces

This will generate the rules for all interfaces, and then you can just
edit the file to change the names as you like.  So I guess I'll know
that for the next person that asks. :-P

-Richard
-- 
gentoo-user@g.o mailing list