All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Matt Domsch <Matt_Domsch@Dell.com>, 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 19:32:28 +0000	[thread overview]
Message-ID: <4CE18ACC.3020508@hp.com> (raw)
In-Reply-To: <1289841399.2586.18.camel@bwh-desktop>

>>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.

I think Sun (sorry, Oracle) push LOM for Lights-Out Management quite a lot - 
calling their service processor an iLOM IIRC.

>>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.

yes and no - that is the prefix for "ethernet" network interface names in HP-UX, 
going back decades.  so, there is precedent for that, and given the way HP-UX 
device name persistence works, 99 times out of ten, the "built-in" or "core" LAN 
interfaces ended-up being enumerated starting from zero - lan0, lan1, etc. 
(There are exceptions relating to certain modles of systems and a full 
re-install of the OS with add-on cards present but that is a story for another 
thread).

> - "mbe" = MotherBoard Ethernet. Looks a bit like "GbE" as some OEMs put
> on the port labels.

Collides with Multi-Bit Error.

> - "eom" = Ethernet On Motherboard

Collides with End of Message.

If there is indeed *no* way to get then named eth[1-N], and "lan" doesn't 
resonate well-enough, then my contribution to the bikeshed would be "cor" simply 
because I don't know the TLA with which that collides :)

Are folks sufficently confident that using anything other than "eth" won't cause 
some unpleasant "our app always ass-u-me-d interfaces started with 'eth'" 
situations?

rick jones

WARNING: multiple messages have this Message-ID (diff)
From: Rick Jones <rick.jones2@hp.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Matt Domsch <Matt_Domsch@Dell.com>, 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 11:32:28 -0800	[thread overview]
Message-ID: <4CE18ACC.3020508@hp.com> (raw)
In-Reply-To: <1289841399.2586.18.camel@bwh-desktop>

>>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.

I think Sun (sorry, Oracle) push LOM for Lights-Out Management quite a lot - 
calling their service processor an iLOM IIRC.

>>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.

yes and no - that is the prefix for "ethernet" network interface names in HP-UX, 
going back decades.  so, there is precedent for that, and given the way HP-UX 
device name persistence works, 99 times out of ten, the "built-in" or "core" LAN 
interfaces ended-up being enumerated starting from zero - lan0, lan1, etc. 
(There are exceptions relating to certain modles of systems and a full 
re-install of the OS with add-on cards present but that is a story for another 
thread).

> - "mbe" = MotherBoard Ethernet. Looks a bit like "GbE" as some OEMs put
> on the port labels.

Collides with Multi-Bit Error.

> - "eom" = Ethernet On Motherboard

Collides with End of Message.

If there is indeed *no* way to get then named eth[1-N], and "lan" doesn't 
resonate well-enough, then my contribution to the bikeshed would be "cor" simply 
because I don't know the TLA with which that collides :)

Are folks sufficently confident that using anything other than "eth" won't cause 
some unpleasant "our app always ass-u-me-d interfaces started with 'eth'" 
situations?

rick jones

  reply	other threads:[~2010-11-15 19:32 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       ` [PATCH 1/1] UDEV - Add 'udevlom' command line param to Ben Hutchings
2010-11-15 17:16         ` [PATCH 1/1] UDEV - Add 'udevlom' command line param to start_udev Ben Hutchings
2010-11-15 19:32         ` Rick Jones [this message]
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=4CE18ACC.3020508@hp.com \
    --to=rick.jones2@hp.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=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.