From: dann frazier <dannf@hp.com>
To: Narendra_K@Dell.com
Cc: netdev@vger.kernel.org, linux-hotplug@vger.kernel.org,
Matt_Domsch@Dell.com, Jordan_Hargrave@Dell.com,
Charles_Rose@Dell.com
Subject: Re: PATCH: Network Device Naming mechanism and policy
Date: Thu, 15 Oct 2009 18:32:45 -0600 [thread overview]
Message-ID: <20091016003245.GD29672@ldl.fc.hp.com> (raw)
In-Reply-To: <20091013173638.GE1119@ldl.fc.hp.com>
On Tue, Oct 13, 2009 at 11:36:38AM -0600, dann frazier wrote:
> 1;2202;0cOn Tue, Oct 13, 2009 at 10:43:49PM +0530, Narendra_K@Dell.com wrote:
> >
> > >> These device nodes are not functional at the moment - open() returns
> > >> -ENOSYS. Their only purpose is to provide userspace with a kernel
> > >> name to ifindex mapping, in a form that udev can easily manage.
> > >
> > >If the idea is just to provide a userspace-visible mapping
> > >(and presumably take advantage of udev's infrastructure for
> > >naming) does this need kernel changes? Could this be a
> > >hierarchy under e.g. /etc/udev instead, using plain text
> > >files? It still means we need something like libnetdevname for
> > >apps to do the translation, but I'm not seeing why it matters
> > >how this map is stored. Is there some special property of the
> > >character devices (e.g. uevents) that we're not already
> > >getting with the existing interfaces?
> >
> > Yes. The char device by itself doesn't help in any way. But it provides
> > a flexible mechanism to provide multiple names for the same device, just
> > the way it is for disks.
>
> Right - so any reason this couldn't be implemented completely in
> userspace by having udev manipulate plain text files under say
> /etc/udev/net/?
>
> I do agree that it would be nice for admins/installers to tweak/use
> nic names in a similar way to storage names (udev rules), and it might
> let us take advantage of a lot of the existing udev code.
Is there interest in this approach?
- modify udev to manage network devices names as regular (non-device)
files (stored in /etc/udev, /dev/netdev, or wherever)
- use the existing udev rules to manage symlinks to these files
- point libnetdevname at these text files for its name resolution
I've started prototyping this, and it certainly looks possible w/o any
kernel changes. However, I could probably use some advice from a udev
person to do a proper implementation.
--
dann frazier
next prev parent reply other threads:[~2009-10-16 0:34 UTC|newest]
Thread overview: 120+ 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 [this message]
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
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
[not found] <EDA0A4495861324DA2618B4C45DCB3EE58964E@blrx3m08.blr.amer.dell.com>
2009-10-28 13:06 ` Narendra K
[not found] <EDA0A4495861324DA2618B4C45DCB3EE589541@blrx3m08.blr.amer.dell.com>
2009-10-12 18:47 ` Narendra K
2009-10-12 19:09 ` Greg KH
2009-10-12 19:41 ` Karl O. Pinc
2009-10-13 18:17 ` Dan Williams
2009-10-13 18:56 ` Ben Hutchings
2009-10-12 19:48 ` Matt Domsch
[not found] <EDA0A4495861324DA2618B4C45DCB3EE58953F@blrx3m08.blr.amer.dell.com>
2009-10-12 18:07 ` Narendra K
[not found] <EDA0A4495861324DA2618B4C45DCB3EE5894F6@blrx3m08.blr.amer.dell.com>
2009-10-09 16:04 ` Narendra K
2009-10-09 16:12 ` Stephen Hemminger
2009-10-09 16:25 ` Matt Domsch
[not found] <5DDAB7BA7BDB58439DD0EED0B8E9A3AE011CD92D@ausx3mpc102.aus.amer.dell.com>
2009-08-19 18:56 ` Jordan_Hargrave
2009-08-19 19:26 ` Ben Hutchings
2009-08-19 19:40 ` Jordan_Hargrave
2009-08-20 4:41 ` 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=20091016003245.GD29672@ldl.fc.hp.com \
--to=dannf@hp.com \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=Narendra_K@Dell.com \
--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).