netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Rick Jones <rick.jones2@hp.com>,
	"Kok, Auke" <auke-jan.h.kok@intel.com>,
	Jan Engelhardt <jengelh@medozas.de>,
	johnathan@jonmasters.org, netdev@vger.kernel.org,
	dwmw2@infradead.org
Subject: Re: network interface *name* alias support?
Date: Sat, 24 May 2008 00:54:35 +0200	[thread overview]
Message-ID: <20080523225435.GT20815@postel.suug.ch> (raw)
In-Reply-To: <1211569604.11907.37.camel@perihelion>

* Jon Masters <jonathan@jonmasters.org> 2008-05-23 15:06
> My intention is to also allow for:
> 
> ifcfg-slot_<whatever>
> 
> Where the configuration is based entirely upon what vendor <XYZ> says is
> the first, second, or third card. Then, those who want to use the older
> names can continue to do so, but those who prefer to base their
> configuration upon the order the vendor states, can do so.

I'd propose to extend the netlink configuration interface, f.e. introduce a
new netlink attribtue IFLA_SLOT which can be provided to select the device
to be changed based on the slot number instead of the name/ifindex. That
would also make it trivial to write a small app using RTM_GETLINK to
translate a slot number to the corresponding interface name.

  parent reply	other threads:[~2008-05-23 22:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 16:31 network interface *name* alias support? 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2008-05-21 22:47 Jon Masters
2008-05-23 13:07 ` David Woodhouse
2008-05-23 14:50   ` Jon Masters

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=20080523225435.GT20815@postel.suug.ch \
    --to=tgraf@suug.ch \
    --cc=auke-jan.h.kok@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=jengelh@medozas.de \
    --cc=johnathan@jonmasters.org \
    --cc=jonathan@jonmasters.org \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.com \
    /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).