From: Stephen Hemminger <shemminger@vyatta.com>
To: Bryan Kadzban <bryan@kadzban.is-a-geek.net>
Cc: Hannes Reinecke <hare@suse.de>,
Kay Sievers <kay.sievers@vrfy.org>,
Matt Domsch <Matt_Domsch@dell.com>, dann frazier <dannf@hp.com>,
linux-hotplug@vger.kernel.org, Narendra_K@dell.com,
netdev@vger.kernel.org, Jordan_Hargrave@dell.com,
Charles_Rose@dell.com, Ben Hutchings <bhutchings@solarflare.com>
Subject: Re: [PATCH] udev: create empty regular files to represent net interfaces
Date: Fri, 30 Oct 2009 09:34:06 -0700 [thread overview]
Message-ID: <20091030093406.05bb7e20@nehalam> (raw)
In-Reply-To: <4AEB12CC.1070300@kadzban.is-a-geek.net>
On Fri, 30 Oct 2009 09:22:36 -0700
Bryan Kadzban <bryan@kadzban.is-a-geek.net> wrote:
> Hannes Reinecke wrote:
> > And to throw in some bit of useless information;
>
> Stirring the pot a bit myself with this message...
>
> > The one reason I didn't to this was that a network interface is _not_
> > a file, but rather an abstract type which is known only internally in
> > the kernel (ie the one exemption from the 'everything is a file' UNIX
> > rule).
>
> Why? Why not make it a file? I've heard rumors of other Unix-like
> systems that do exactly that, FWIW.
>
> (Yes, I'm joking. Well, maybe half-joking... It'd be nice, but I don't
> expect it to happen.)
>
> > When I were to design this, I would be implementing network interface
> > _aliases_, so that a network interface could be accessed either by
> > name or by alias. This mechanism can then be managed by udev, much
> > like we (ie SUSE) is using it nowadays to assign the network
> > interface numbers.
>
> The problem with that, if I understand what you're suggesting, is the
> value of IFNAMSIZ, and the fact that it can't be made any bigger. All
> your aliases have to be IFNAMSIZ characters or less. And that's too
> short to be able to embed the same level of information as we get for
> e.g. disks. It's *barely* long enough to fit "mac-" plus 12 hex digits
> (for the MAC address), but is completely incapable of holding a USB bus
> path, for instance.
>
> (Not that you'd want to use path persistence for USB devices. But it is
> possible that you'd want it for some other setup, at which point it
> becomes impossible to use the same rules for USB.)
Not a big fan of multiple names, it is the wrong solution to the human
question of "what is eth0 really?". Router o/s use description field
for that kind of information.
I added ifalias to provide place to put user visible description information.
It is in latest kernels via sysfs and iproute utilities. Also plan to add
support for it in net-snmp.
--
next prev parent reply other threads:[~2009-10-30 16:34 UTC|newest]
Thread overview: 105+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDA0A4495861324DA2618B4C45DCB3EE5894ED@blrx3m08.blr.amer.dell.com>
2009-10-09 14:00 ` PATCH: Network Device Naming mechanism and policy Narendra K
2009-10-09 14:51 ` Matt Domsch
2009-10-09 16:23 ` Bryan Kadzban
2009-10-09 16:56 ` Marco d'Itri
2009-10-12 10:41 ` Scott James Remnant
2009-10-12 11:31 ` Ben Hutchings
2009-10-12 17:37 ` Bill Nottingham
2009-10-13 18:06 ` Dan Williams
2009-10-13 18:53 ` Ben Hutchings
2009-10-13 19:53 ` John W. Linville
2009-10-09 16:36 ` Greg KH
2009-10-09 17:17 ` Matt Domsch
2009-10-09 17:22 ` Greg KH
2009-10-09 21:09 ` Matt Domsch
2009-10-10 2:44 ` Stephen Hemminger
2009-10-10 4:40 ` Matt Domsch
2009-10-10 5:23 ` Greg KH
2009-10-10 8:17 ` Sujit K M
2009-10-10 16:27 ` Greg KH
2009-10-10 19:00 ` Ben Hutchings
2009-10-10 21:10 ` Greg KH
2009-10-10 12:47 ` Matt Domsch
2009-10-10 16:25 ` Greg KH
2009-10-10 17:34 ` Bryan Kadzban
2009-10-10 21:13 ` Greg KH
2009-10-12 6:21 ` Bryan Kadzban
2009-10-12 16:19 ` Bryan Kadzban
2009-10-11 16:40 ` David Zeuthen
2009-10-11 18:47 ` Greg KH
2009-10-10 18:11 ` Bill Fink
2009-10-10 18:35 ` Kay Sievers
2009-10-11 21:10 ` Rob Townley
2009-10-11 23:04 ` Matt Domsch
2009-10-12 3:00 ` Greg KH
2009-10-12 18:35 ` Rob Townley
2009-10-12 18:44 ` Matt Domsch
2009-10-12 17:45 ` Bill Nottingham
2009-10-12 17:55 ` Greg KH
2009-10-12 18:07 ` Bill Nottingham
2009-10-12 18:15 ` Greg KH
2009-10-10 18:32 ` Stephen Hemminger
2009-10-10 21:06 ` Greg KH
2009-10-13 18:02 ` Dan Williams
2009-10-13 18:53 ` Narendra_K
2009-10-12 7:30 ` Kurt Van Dijck
2009-10-11 0:37 ` Marco d'Itri
2009-10-13 15:08 ` dann frazier
2009-10-13 17:13 ` Narendra_K
2009-10-13 17:36 ` dann frazier
2009-10-16 0:32 ` dann frazier
2009-10-16 14:02 ` Narendra_K
2009-10-16 15:20 ` dann frazier
2009-10-16 15:33 ` Ben Hutchings
2009-10-16 15:41 ` dann frazier
2009-10-16 21:40 ` dann frazier
2009-10-19 11:30 ` Narendra_K
2009-10-19 16:14 ` Bryan Kadzban
2009-11-04 14:23 ` Narendra_K
2009-11-06 8:49 ` Marco d'Itri
2009-11-06 22:06 ` Matt Domsch
2009-11-06 22:35 ` Marco d'Itri
2009-11-06 23:17 ` dann frazier
2009-11-09 14:41 ` Narendra_K
2009-11-10 17:23 ` Stephen Hemminger
2009-11-11 6:31 ` Narendra_K
2009-11-06 22:05 ` Domsch, Matt
2009-10-22 6:36 ` [PATCH] udev: create empty regular files to represent net interfaces dann frazier
2009-10-27 20:55 ` Matt Domsch
2009-10-28 8:23 ` Kay Sievers
2009-10-28 13:03 ` Matt Domsch
2009-10-28 15:09 ` dann frazier
2009-10-28 16:09 ` Jordan_Hargrave
2009-10-28 16:09 ` Jordan_Hargrave
2009-10-28 16:11 ` Greg KH
2009-10-28 13:06 ` Ben Hutchings
2009-10-28 19:15 ` Narendra_K
2009-10-29 13:11 ` Matt Domsch
2009-10-29 14:25 ` Greg KH
2009-10-29 16:44 ` Narendra_K
2009-10-29 16:52 ` Greg KH
2009-10-29 17:22 ` [PATCH] udev: create empty regular files to represent netinterfaces Narendra_K
2009-10-29 17:50 ` dann frazier
2009-10-29 16:49 ` [PATCH] udev: create empty regular files to represent net interfaces Ben Hutchings
2009-10-29 16:55 ` Greg KH
2009-10-29 17:12 ` Ben Hutchings
2009-10-29 17:20 ` Greg KH
2009-10-29 17:46 ` dann frazier
2009-10-30 3:30 ` Marco d'Itri
2009-10-30 5:38 ` dann frazier
2009-10-30 6:22 ` Marco d'Itri
2009-10-30 15:00 ` dann frazier
2009-10-30 15:13 ` Narendra_K
2009-10-30 16:08 ` dann frazier
2009-10-30 16:53 ` [PATCH] udev: create empty regular files to represent netinterfaces Narendra_K
2009-10-30 17:05 ` dann frazier
2009-10-30 17:10 ` [PATCH] udev: create empty regular files to represent net interfaces Matt Domsch
2009-10-30 17:13 ` Greg KH
2009-10-30 7:45 ` Hannes Reinecke
2009-10-30 16:22 ` Bryan Kadzban
2009-10-30 16:34 ` Stephen Hemminger [this message]
2009-10-13 19:51 ` PATCH: Network Device Naming mechanism and policy Greg KH
2009-10-13 20:00 ` Jordan_Hargrave
2009-10-13 20:19 ` Greg KH
2009-10-13 22:05 ` Matt Domsch
2009-10-13 22:08 ` dann frazier
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=20091030093406.05bb7e20@nehalam \
--to=shemminger@vyatta.com \
--cc=Charles_Rose@dell.com \
--cc=Jordan_Hargrave@dell.com \
--cc=Matt_Domsch@dell.com \
--cc=Narendra_K@dell.com \
--cc=bhutchings@solarflare.com \
--cc=bryan@kadzban.is-a-geek.net \
--cc=dannf@hp.com \
--cc=hare@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.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).