linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Fw: Udev naming conventions.
@ 2007-06-12 19:47 Scott Farwell
  2007-06-12 22:31 ` Bryan Kadzban
  0 siblings, 1 reply; 2+ messages in thread
From: Scott Farwell @ 2007-06-12 19:47 UTC (permalink / raw)
  To: linux-hotplug

I want to control what Ethernet interfaces are named eth0, eth1, eth2, eth3, 
etc....based on MAC address but I don't want them named anything other than 
eth0 - ethx so that it remains backwards compatible with software written to 
check eth0.

So I'm not wanting to rename anything, I just want to bind each ethx device 
name to a specific hardware port based on MAC address.  That way if I 
physically lost eth1 for some reason (burned up chip) I wouldn't end up with 
my 3rd Ethernet port(eth2) renamed to eth1 on the next bootup.

I was told that udev is the way to enable device persistence, but it appears 
that it requires me to rename my interfaces something other than eth0 - 
ethx. 



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Fw: Udev naming conventions.
  2007-06-12 19:47 Fw: Udev naming conventions Scott Farwell
@ 2007-06-12 22:31 ` Bryan Kadzban
  0 siblings, 0 replies; 2+ messages in thread
From: Bryan Kadzban @ 2007-06-12 22:31 UTC (permalink / raw)
  To: linux-hotplug

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Scott Farwell wrote:
> So I'm not wanting to rename anything, I just want to bind each ethx 
> device name to a specific hardware port based on MAC address.
> 
> I was told that udev is the way to enable device persistence, but it 
> appears that it requires me to rename my interfaces something other 
> than eth0 - ethx.

Not anymore.  :-)  It used to require non-ethX names, because trying to
rename eth2 to eth1 while trying to rename eth1 to eth2 would fail
(because both target devices existed).  But a delay loop and temporary
target names were added to udevd when renaming NICs, so that renames
like that should eventually complete.  (Assuming a rule exists for both
NICs, of course.)

You need udev-095 or later (earlier versions didn't have the rename loop
code), but that shouldn't be too bad.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGbx6iS5vET1Wea5wRA0QeAJ9/B+xy8dJNGqdYddv6eCD5m6GCGwCg4944
pB1cucJ3OTHPit+V+6HyfKk=nvP2
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-06-12 22:31 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-12 19:47 Fw: Udev naming conventions Scott Farwell
2007-06-12 22:31 ` Bryan Kadzban

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).