[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091029172022.GA10558@kroah.com>
Date: Thu, 29 Oct 2009 10:20:22 -0700
From: Greg KH <greg@...ah.com>
To: Ben Hutchings <bhutchings@...arflare.com>
Cc: Matt Domsch <Matt_Domsch@...l.com>,
Kay Sievers <kay.sievers@...y.org>,
dann frazier <dannf@...com>, linux-hotplug@...r.kernel.org,
Narendra_K@...l.com, netdev@...r.kernel.org,
Jordan_Hargrave@...l.com, Charles_Rose@...l.com
Subject: Re: [PATCH] udev: create empty regular files to represent net
interfaces
On Thu, Oct 29, 2009 at 05:12:13PM +0000, Ben Hutchings wrote:
> On Thu, 2009-10-29 at 09:55 -0700, Greg KH wrote:
> > On Thu, Oct 29, 2009 at 04:49:35PM +0000, Ben Hutchings wrote:
> > > 3. Name assignment mechanism
> > > Disks: kernel suggests a name; udev can assign any number
> > > ???Net devices: kernel assigns a single name; udev can override it
> > >
> > > 4. Default name assignment policy
> > > Disks: names disk by device path (id), label and UUID
> > > ???Net devices: assigns arbitrary stable names per (MAC address, subtype)
> > >
> > > 5. Naming by users
> > > Disks: user can identify by any method without having to choose on a
> > > system-wide basis
> > > Net devices: user must identify by single name; policy can be overridden
> > > on a system-wide basis
> > >
> > > I fully understand the technical reasons for differences 3-5, but why
> > > should users have to put up with it?
> >
> > That is because network devices are not referred to by /dev/ nodes where
> > multiple symlinks would solve the naming problem.
>
> Did you even read the last sentence?
Yes, the technical reason is the reason why users have to put up
with it :)
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists