From: Ben Hutchings <bhutchings@solarflare.com>
To: Matt Domsch <Matt_Domsch@Dell.com>
Cc: Greg KH <greg@kroah.com>, "K, Narendra" <Narendra_K@Dell.com>,
"linux-hotplug@vger.kernel.org" <linux-hotplug@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Hargrave, Jordan" <Jordan_Hargrave@Dell.com>,
"Rose, Charles" <Charles_Rose@Dell.com>
Subject: Re: [PATCH 1/1] UDEV - Add 'udevlom' command line param to
Date: Mon, 15 Nov 2010 17:16:39 +0000 [thread overview]
Message-ID: <1289841399.2586.18.camel@bwh-desktop> (raw)
In-Reply-To: <20101115164714.GB7030@auslistsprd01.us.dell.com>
On Mon, 2010-11-15 at 10:47 -0600, Matt Domsch wrote:
> On Thu, Nov 04, 2010 at 09:58:48PM -0500, Matt Domsch wrote:
> > On Wed, Nov 03, 2010 at 11:05:00AM -0700, Greg KH wrote:
> > > On Wed, Nov 03, 2010 at 10:25:25PM +0530, Narendra_K@Dell.com wrote:
> > > > Hello,
> > > >
> > > > This patch allows users to specify if they want the onboard network
> > > > interfaces to be renamed to lomN by implementing a command line param
> > > > 'udevlom'.
> > >
> > > Ick ick ick.
> > >
> > > Why not do this in some other configuration file? Don't rely on udev
> > > being started with a different option, that is only ripe for abuse by
> > > everyone else who wants their pet-project to get into the udev
> > > environment.
> > >
> > > Please, surely there's a different way to do this.
> >
> > At Linux Plumbers Conference today, this problem space was discussed
> > once again, and I believe concensus on approach was reached. Here
> > goes:
> >
> > * If a 70-persistent-net.rules file sets a name, honor that. This
> > preserves existing installs.
> >
> > * If BIOS provides indexes for onboard devices, honor that.
> > ** Rename onboard NICs "lom[1-N]" as BIOS reports (# matches chassis labels)
> > ** No rename for all others "ethX" (no change for NICs in PCI slots/USB/others)
>
> I'm getting a lot of pushback from Dell customers on our
> linux-poweredge mailing list (thread starts [1]) that the choice of
> name "lomX" is poor, due to HP's extensive use of LOM meaning Lights
> Out Management, rather than my intended meaning of "LAN on
> Motherboard". Gotta hate TLA collisions.
>
> So, I'm open to new ideas for naming these. At LPC, Ted noted that
> 2- and 3-letter names are expected. "nic[1234]" or "en[1234]" ?
[...]
I would suggest avoiding "nic" since some people use "NIC" to mean
specifically an add-in card rather than LOM. In addition there is some
ambiguity with multi-port cards/controllers of whether NIC means a
controller or a port.
Other options for the prefix:
- "lan". Maybe too generic.
- "mbe" = MotherBoard Ethernet. Looks a bit like "GbE" as some OEMs put
on the port labels.
- "eom" = Ethernet On Motherboard
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
WARNING: multiple messages have this Message-ID (diff)
From: Ben Hutchings <bhutchings@solarflare.com>
To: Matt Domsch <Matt_Domsch@Dell.com>
Cc: Greg KH <greg@kroah.com>, "K, Narendra" <Narendra_K@Dell.com>,
"linux-hotplug@vger.kernel.org" <linux-hotplug@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Hargrave, Jordan" <Jordan_Hargrave@Dell.com>,
"Rose, Charles" <Charles_Rose@Dell.com>
Subject: Re: [PATCH 1/1] UDEV - Add 'udevlom' command line param to start_udev
Date: Mon, 15 Nov 2010 17:16:39 +0000 [thread overview]
Message-ID: <1289841399.2586.18.camel@bwh-desktop> (raw)
In-Reply-To: <20101115164714.GB7030@auslistsprd01.us.dell.com>
On Mon, 2010-11-15 at 10:47 -0600, Matt Domsch wrote:
> On Thu, Nov 04, 2010 at 09:58:48PM -0500, Matt Domsch wrote:
> > On Wed, Nov 03, 2010 at 11:05:00AM -0700, Greg KH wrote:
> > > On Wed, Nov 03, 2010 at 10:25:25PM +0530, Narendra_K@Dell.com wrote:
> > > > Hello,
> > > >
> > > > This patch allows users to specify if they want the onboard network
> > > > interfaces to be renamed to lomN by implementing a command line param
> > > > 'udevlom'.
> > >
> > > Ick ick ick.
> > >
> > > Why not do this in some other configuration file? Don't rely on udev
> > > being started with a different option, that is only ripe for abuse by
> > > everyone else who wants their pet-project to get into the udev
> > > environment.
> > >
> > > Please, surely there's a different way to do this.
> >
> > At Linux Plumbers Conference today, this problem space was discussed
> > once again, and I believe concensus on approach was reached. Here
> > goes:
> >
> > * If a 70-persistent-net.rules file sets a name, honor that. This
> > preserves existing installs.
> >
> > * If BIOS provides indexes for onboard devices, honor that.
> > ** Rename onboard NICs "lom[1-N]" as BIOS reports (# matches chassis labels)
> > ** No rename for all others "ethX" (no change for NICs in PCI slots/USB/others)
>
> I'm getting a lot of pushback from Dell customers on our
> linux-poweredge mailing list (thread starts [1]) that the choice of
> name "lomX" is poor, due to HP's extensive use of LOM meaning Lights
> Out Management, rather than my intended meaning of "LAN on
> Motherboard". Gotta hate TLA collisions.
>
> So, I'm open to new ideas for naming these. At LPC, Ted noted that
> 2- and 3-letter names are expected. "nic[1234]" or "en[1234]" ?
[...]
I would suggest avoiding "nic" since some people use "NIC" to mean
specifically an add-in card rather than LOM. In addition there is some
ambiguity with multi-port cards/controllers of whether NIC means a
controller or a port.
Other options for the prefix:
- "lan". Maybe too generic.
- "mbe" = MotherBoard Ethernet. Looks a bit like "GbE" as some OEMs put
on the port labels.
- "eom" = Ethernet On Motherboard
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-11-15 17:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 16:55 [PATCH 1/1] UDEV - Add 'udevlom' command line param to start_udev Narendra_K
2010-11-03 16:58 ` Narendra_K
2010-11-03 18:05 ` [PATCH 1/1] UDEV - Add 'udevlom' command line param to Greg KH
2010-11-03 18:05 ` [PATCH 1/1] UDEV - Add 'udevlom' command line param to start_udev Greg KH
2010-11-03 18:32 ` [PATCH 1/1] UDEV - Add 'udevlom' command line param to Marco d'Itri
2010-11-03 18:32 ` [PATCH 1/1] UDEV - Add 'udevlom' command line param to start_udev Marco d'Itri
2010-11-04 8:37 ` Sujit K M
2010-11-04 8:49 ` Sujit K M
2010-11-05 2:58 ` Matt Domsch
2010-11-05 2:58 ` Matt Domsch
2010-11-08 8:42 ` Sujit K M
2010-11-08 8:54 ` Sujit K M
2010-11-08 18:17 ` Matt Domsch
2010-11-08 18:17 ` Matt Domsch
2010-11-15 16:47 ` Matt Domsch
2010-11-15 16:47 ` Matt Domsch
2010-11-15 17:16 ` Ben Hutchings [this message]
2010-11-15 17:16 ` Ben Hutchings
2010-11-15 19:32 ` Rick Jones
2010-11-15 19:32 ` Rick Jones
2010-11-24 20:57 ` Loke, Chetan
2010-11-24 20:57 ` Loke, Chetan
2010-11-24 21:13 ` Loke, Chetan
2010-11-24 21:13 ` Loke, Chetan
2010-11-25 2:56 ` [PATCH 1/1] UDEV - Add 'udevlom' command line param to Bill Fink
2010-11-25 2:56 ` [PATCH 1/1] UDEV - Add 'udevlom' command line param to start_udev Bill Fink
2010-11-26 2:09 ` Matt Domsch
2010-11-26 2:09 ` Matt Domsch
2010-11-10 16:32 ` Harald Hoyer
2010-11-10 16:32 ` Harald Hoyer
2010-11-10 16:37 ` Harald Hoyer
2010-11-10 16:37 ` Harald Hoyer
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=1289841399.2586.18.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.