On Tue, 18 Apr 2006 04:54 am, Florian Kulzer wrote:
[...]
> > > I always had trouble when I tried to assign ethX names with the udev
> > > rules, so I use a slightly modified approach:
> > > http://lists.debian.org/debian-user/2006/01/msg03434.html
[...]
[...]
> >
> > I just tried using this /etc/udev/rules.d/10_local_rules (a link
^^^^^^^^^^
> > to /etc/udev/local_rules):
> >
> > KERNEL=="eth*", SYSFS{address}=="00:40:ca:c0:d9:a6",
> > NAME="ethernet"
> > KERNEL=="eth*", SYSFS{address}=="00:0c:f1:15:c6:e3",
> > NAME="wireless"
> > KERNEL=="eth*", SUBSYSTEM=="ieee1394", NAME="firewire"
> >
> > however, it does not succeed in renaming the interfaces as I expected.
> >
> > Is there something I'm missing?
>
> Your rules look OK to me. I checked my laptop again and mine are
> equivalent, but I have now linked them as "025_local_rules". I would not
^^^^^^^^^^^
> expect that to make any difference and I don't remember why I changed
> it.
>
> So let's compare a few more things.
[...]
> $ udevtest /class/net/eth0
> main: looking at device '/class/net/eth0' from subsystem 'net'
> wait_for_sysfs: file '/sys/class/net/eth0/address' appeared after 0 loops
> udev_rules_get_name: rule applied, 'eth0' becomes 'lan'
> rename_net_if: changing net interface name from 'eth0' to 'lan'
> udev_add_device: renamed netif to 'lan'
Instead of the last three lines, I got:
udev_rules_get_name: no node name set, will use kernel name 'eth0'
and likewise for the other interfaces, which made me think my rules were
dodgy; I rechecked them, they were fine.
Then I realized it wasn't the rules themselves, but the name of the link:
025_local_rules should have been 025_local.rules (which I'm sure yours is
really called also) - obviously udev only reads files named this way.
Thanks for a very thorough reply to a problem that was just a silly typo!
The udevtest command will be very useful.
Cheers,
John
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
