From: Jon Masters <jonathan@jonmasters.org>
To: netdev <netdev@vger.kernel.org>
Subject: network interface *name* alias support?
Date: Wed, 21 May 2008 18:47:58 -0400 [thread overview]
Message-ID: <1211410078.27149.70.camel@perihelion> (raw)
Hi,
I would like to add support for network interface name aliases to the
kernel. For example, rather than simply "eth0", one might have:
eth0 -> eth_slot_0_0
And use either name for device configuration, etc. This should be pretty
easy, but I would like some comments - in particular, has this been done
already and I'm missing something?
Why is this useful? Say, for example that your a manufacturer building
machines using the latest DMI extension to SMBIOS that allows you to
specify what the physical ordering of interfaces is. Then, a
distribution might choose to configure based on the physical slot
ordering specified by the vendor - allowing for "rip and replace".
Jon.
next reply other threads:[~2008-05-21 23:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 22:47 Jon Masters [this message]
2008-05-23 13:07 ` network interface *name* alias support? David Woodhouse
2008-05-23 14:50 ` Jon Masters
-- strict thread matches above, loose matches on Subject: below --
2008-05-23 16:31 Jan Engelhardt
2008-05-23 17:14 ` Kok, Auke
2008-05-23 17:44 ` Rick Jones
2008-05-23 19:06 ` Jon Masters
2008-05-23 19:11 ` Jon Masters
2008-05-23 20:46 ` Jan Engelhardt
2008-05-23 20:55 ` Jon Masters
2008-05-23 22:54 ` Thomas Graf
2008-05-24 4:25 ` Jon Masters
2008-05-24 4:53 ` Jan Engelhardt
2008-05-24 5:16 ` Matt Domsch
2008-05-24 9:15 ` James Chapman
2008-05-24 9:33 ` David Woodhouse
2008-05-24 10:37 ` James Chapman
2008-05-24 20:31 ` Patrick McHardy
2008-05-24 20:54 ` Jan Engelhardt
2008-05-25 3:07 ` Patrick McHardy
2008-05-25 12:17 ` David Miller
2008-05-27 19:03 ` Matt Domsch
2008-05-27 21:49 ` Jan Engelhardt
2008-05-27 22:11 ` Thomas Graf
2008-05-24 18:12 ` Stephen Hemminger
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=1211410078.27149.70.camel@perihelion \
--to=jonathan@jonmasters.org \
--cc=netdev@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 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).