netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: <Narendra_K@Dell.com>
Cc: <be-mail2009@lina.inka.de>, <jengelh@medozas.de>,
	<net-tools@lina.inka.de>, <netfilter-devel@vger.kernel.org>,
	<jgarzik@users.sourceforge.net>, <Matt_Domsch@Dell.com>,
	<Charles_Rose@Dell.com>, <Jordan_Hargrave@Dell.com>,
	<Sandeep_K_Shandilya@Dell.com>, <Shyam_Iyer@Dell.com>
Subject: Re: [PROPOSAL]: Alias names for network interfaces
Date: Mon, 21 Dec 2009 09:36:21 -0800	[thread overview]
Message-ID: <20091221093621.0470d637@nehalam> (raw)
In-Reply-To: <EDA0A4495861324DA2618B4C45DCB3EE5898CC@blrx3m08.blr.amer.dell.com>

On Mon, 21 Dec 2009 22:58:09 +0530
<Narendra_K@Dell.com> wrote:

> > On Fri, 18 Dec 2009 18:49:15 +0530
> > <Narendra_K@Dell.com> wrote:
> > 
> > > The installer solution involved renaming the network interface names
> > > from ethN to something else based on the naming convention that the
> > user
> > > specified. For example, if the user chose "smbios names" as the the
> > > naming convention then all ethN would be renamed to Embedded_NIC_N.
> > > ifconfig would show Embedded_NIC_N instead of ethN.
> > 
> > Renaming away from ethN causes some applications like net-snmp to get
> > confused,
> > and others have special sorting rules based on existing model (like
> > quagga).
> > 
> > I would argue that the "ethN" convention is part of existing system
> > ABI and should not get changed in a visible way to applications.
> 
> Stephen,
> 
> Thanks. What are your views on the current proposal we are making where
> ethN names are not changed (or renamed) and libnetdevname would suggest
> alias names for the ethN names ( and also alias to ethN names) in user
> space. Applications like ip, ethtool etc can use these aliases, make
> calls to libnetdevname and get the ethN name. 
> 
> Libnetdevname would read from sysfs the smbios names of the network
> interface devices as Jordan mentioned
> (/sys/class/net/ethX/device/smbiosname). Would this be acceptable ?

I have no need or use for them, but if it doesn't break other things
then sure.

  reply	other threads:[~2009-12-21 17:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-17 13:54 [PROPOSAL]: Alias names for network interfaces Narendra_K
2009-12-17 14:48 ` Jan Engelhardt
2009-12-18  2:02   ` Bernd Eckenfels
2009-12-18 13:19     ` Narendra_K
2009-12-18 13:42       ` Jan Engelhardt
2009-12-18 14:02         ` Domsch, Matt
2009-12-18 14:08         ` Domsch, Matt
2009-12-18 14:15           ` Jan Engelhardt
2009-12-20  0:12             ` Jordan_Hargrave
2009-12-18 17:38       ` Stephen Hemminger
2009-12-21 17:28         ` Narendra_K
2009-12-21 17:36           ` Stephen Hemminger [this message]
2009-12-23 17:11             ` Narendra_K
     [not found] <EDA0A4495861324DA2618B4C45DCB3EE5899AC@blrx3m08.blr.amer.dell.com>
2010-01-12 19:49 ` Narendra K
2010-01-13  0:11   ` Jan Engelhardt
2010-01-13  6:47     ` [PROPOSAL]: " Narendra_K
2010-01-13 11:04       ` Bernd Eckenfels
2010-01-13 17:22         ` John Haxby
2010-01-13 17:46           ` Domsch, Matt
2010-01-13 18:11             ` Bernd Eckenfels
2010-01-13 18:21             ` Jan Engelhardt
2010-01-14  8:44               ` Patrick McHardy
2010-01-14  9:35                 ` Jan Engelhardt
2010-01-15 19:14               ` Narendra_K
2010-01-18 17:07                 ` Marco Innocenti
2010-01-19 17:32                   ` Narendra_K
2010-01-19 22:31                     ` Stephen Hemminger
2010-01-20  1:02                       ` Bernd Eckenfels
2010-01-20 16:42                       ` Narendra_K
2010-01-13 17:54           ` Stephen Hemminger
2010-01-13 13:24   ` Patrick McHardy
2010-01-13 13:43     ` Jan Engelhardt
2010-01-13 16:27       ` Stephen Hemminger
2010-01-13 17:00         ` Narendra_K
2010-01-14  8:41           ` Patrick McHardy

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=20091221093621.0470d637@nehalam \
    --to=shemminger@linux-foundation.org \
    --cc=Charles_Rose@Dell.com \
    --cc=Jordan_Hargrave@Dell.com \
    --cc=Matt_Domsch@Dell.com \
    --cc=Narendra_K@Dell.com \
    --cc=Sandeep_K_Shandilya@Dell.com \
    --cc=Shyam_Iyer@Dell.com \
    --cc=be-mail2009@lina.inka.de \
    --cc=jengelh@medozas.de \
    --cc=jgarzik@users.sourceforge.net \
    --cc=net-tools@lina.inka.de \
    --cc=netfilter-devel@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).