public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Matt Domsch <Matt_Domsch@Dell•com>
To: Greg KH <greg@kroah•com>
Cc: "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 10:47:14 -0600	[thread overview]
Message-ID: <20101115164714.GB7030@auslistsprd01.us.dell.com> (raw)
In-Reply-To: <20101105025848.GA14021@pws490.domsch.com>

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]" ?

And yes, they'd prefer that we keep "eth[0123]" for the onboard
devices, but I simply don't see how to do that without kernel changes,
due to the races in both naming them in the kernel vs udev renaming,
and simple races between two udev processes.

Thanks,
Matt

[1] http://lists.us.dell.com/pipermail/linux-poweredge/2010-November/043576.html

-- 
Matt Domsch
Technology Strategist
Dell | Office of the CTO

  parent reply	other threads:[~2010-11-15 16:47 UTC|newest]

Thread overview: 16+ 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 18:05 ` Greg KH
2010-11-03 18:32   ` Marco d'Itri
2010-11-04  8:37     ` Sujit K M
2010-11-05  2:58   ` Matt Domsch
2010-11-08  8:42     ` Sujit K M
2010-11-08 18:17       ` Matt Domsch
2010-11-15 16:47     ` Matt Domsch [this message]
2010-11-15 17:16       ` Ben Hutchings
2010-11-15 19:32         ` Rick Jones
2010-11-24 20:57           ` Loke, Chetan
2010-11-24 21:13           ` Loke, Chetan
2010-11-25  2:56             ` Bill Fink
2010-11-26  2:09               ` Matt Domsch
2010-11-10 16:32 ` 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=20101115164714.GB7030@auslistsprd01.us.dell.com \
    --to=matt_domsch@dell$(echo .)com \
    --cc=Charles_Rose@Dell$(echo .)com \
    --cc=Jordan_Hargrave@Dell$(echo .)com \
    --cc=Narendra_K@Dell$(echo .)com \
    --cc=greg@kroah$(echo .)com \
    --cc=linux-hotplug@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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