From: Jon Masters <jcm@redhat.com>
To: Discussion of Development and Customization of the Red Hat Linux
Installer <anaconda-devel-list@redhat.com>
Cc: netdev@vger.kernel.org, shyam_iyer@dell.com,
matt_domsch@dell.com, jordan_hargrave@dell.com,
charles_rose@dell.com
Subject: Re: [PROPOSAL]: Support Alternate Network Device Naming Schemes
Date: Mon, 30 Nov 2009 12:07:24 -0500 [thread overview]
Message-ID: <1259600844.6978.35.camel@tonnant> (raw)
In-Reply-To: <20091127094257.GA24624@mock.linuxdev.us.dell.com>
On Fri, 2009-11-27 at 03:42 -0600, Narendra K wrote:
> We have been having discussions in the netdev list about creating multiple names for the network interfaces to bring determinism into the way network interfaces are named in the OSes. In specific, "eth0 in the OS does not always map to the integrated NIC Gb1 as labelled on the chassis".
>
> http://marc.info/?l=linux-netdev&m=125510301513312&w=2 - (Re: PATCH: Network Device Naming mechanism and policy)
> http://marc.info/?l=linux-netdev&m=125619338904322&w=2 - ([PATCH] udev: create empty regular files to represent net)
>
> As a result of those discussions, we propose an installer based solution.
Very cool. Thanks for your continued hard work on this stuff :) Do you
have proof of concept Anaconda patches available?
Jon.
next prev parent reply other threads:[~2009-11-30 17:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-27 9:42 [PROPOSAL]: Support Alternate Network Device Naming Schemes Narendra K
2009-11-30 17:07 ` Jon Masters [this message]
2009-11-30 18:34 ` Bill Nottingham
-- strict thread matches above, loose matches on Subject: below --
2009-11-27 9:11 Narendra K
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=1259600844.6978.35.camel@tonnant \
--to=jcm@redhat.com \
--cc=anaconda-devel-list@redhat.com \
--cc=charles_rose@dell.com \
--cc=jordan_hargrave@dell.com \
--cc=matt_domsch@dell.com \
--cc=netdev@vger.kernel.org \
--cc=shyam_iyer@dell.com \
/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).