From: Sujit K M <sjt.kar@gmail.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, 8 Nov 2010 14:12:56 +0530 [thread overview]
Message-ID: <AANLkTin_rswTZn5RxH375u4xsoftQzMSPMRfUvy77fdX@mail.gmail.com> (raw)
In-Reply-To: <20101105025848.GA14021@pws490.domsch.com>
> At Linux Plumbers Conference today, this problem space was discussed
> once again, and I believe concensus on approach was reached. Here
> goes:
Was the patch a starting point for the discussion.
> * 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)
>
> * If neither are true, do not rename at all.
I would like to know what is the difference in the nomenclature for this.
>
> * Implementation will be:
> ** Udev rules to be included in upstream udev will read the index
> value from sysfs (provided by SMBIOS 2.6 info on kernels >= 2.6.36,
> PCI DSM info at some future point) if present, and rename LOMs
> based on that index value. Distros will use these rules by default
> (Ubuntu and Fedora maintainers on board with the concept; I have
> not spoken with other distros yet.)
> ** Legacy distros with older udev rules will invoke biosdevname on
> kernels < 2.6.36 to get the same information, if present, and will
> rename LOMs based on index value.
How will you manage these scenarios.
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-08 8:42 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 [this message]
2010-11-08 18:17 ` Matt Domsch
2010-11-15 16:47 ` Matt Domsch
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=AANLkTin_rswTZn5RxH375u4xsoftQzMSPMRfUvy77fdX@mail.gmail.com \
--to=sjt.kar@gmail.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 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).