From: "Scott Farwell" <scott@iivip.com>
To: linux-hotplug@vger.kernel.org
Subject: Fw: Udev naming conventions.
Date: Tue, 12 Jun 2007 19:47:19 +0000 [thread overview]
Message-ID: <000701c7ad2a$7cd2cd10$32489dce@interact.nonreg> (raw)
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
next reply other threads:[~2007-06-12 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 19:47 Scott Farwell [this message]
2007-06-12 22:31 ` Fw: Udev naming conventions Bryan Kadzban
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000701c7ad2a$7cd2cd10$32489dce@interact.nonreg' \
--to=scott@iivip.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.