Re: Udev persistent net rules - how do they work?
- From: Liam O'Toole <liam.p.otoole@xxxxxxxxx>
- Date: Sat, 21 Apr 2007 11:53:59 +0100
On Sat, 21 Apr 2007 09:58:31 +0100
Alan Chandler <alan@xxxxxxxxxxxxxxxxxxxxx> wrote:
[...]
When interfaces apparently appear out of nowhere, I suspect
hotplug/udev, and in /etc/udev there is a script called
persistent-net-generator.rules
which in its comments says it is storing the created interfaces so
that they stay the same across reboots. But I can't figure out how
its supposed to work. Can someone explain what it is doing, and if
so how I can tell if this is the cause of my problem.
Thanks.
The script persistent-net-generator.rules generates the
file /etc/udev/rules.d/z25_persistent-net.rules. There you will see how
udev maps a hardware address to a logical interface name such as eth0.
Therefore you will need to swap around the names in that file just as
you have done in /etc/network/interfaces.
--
Liam
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: Udev persistent net rules - how do they work?
- From: Alan Chandler
- Re: Udev persistent net rules - how do they work?
- References:
- Udev persistent net rules - how do they work?
- From: Alan Chandler
- Udev persistent net rules - how do they work?
- Prev by Date: Make menuconfig errors
- Next by Date: Amarok and Last.FM: Works in 1.4.5 (experimental)
- Previous by thread: Udev persistent net rules - how do they work?
- Next by thread: Re: Udev persistent net rules - how do they work?
- Index(es):
Relevant Pages
|
