From: Bill Nottingham <notting@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 13:34:37 -0500 [thread overview]
Message-ID: <20091130183435.GC15213@nostromo.devel.redhat.com> (raw)
In-Reply-To: <20091127094257.GA24624@mock.linuxdev.us.dell.com>
Narendra K (Narendra_K@dell.com) said:
> Installers as of now allow the discovered network interfaces to be configured. This solution proposes to provide an option for the users to either retain the default naming convention that the kernel now has, i.e ethN names or rename the network interfaces based on the chassis label, MAC addresses, Driver name and any other naming convention. Here is how the modified network configuration wizard would look during the os installation process -
>
>
> ---------- Network Configuration ------------------------
>
> Default [ ] | SMBIOS Names [x] | Driver Names [] | MAC Names []
> -----------------------------------------------------------------------
> eth0 | Addin_NIC_1 | ice0 |
> -----------------------------------------------------------------------
> eth1 | Embedded_NIC_1 | bce0 |
> -----------------------------------------------------------------------
> eth2 | Embedded_NIC_2 | bce1 |
> -----------------------------------------------------------------------
> eth3 | Embedded_NIC_3 | bce2 |
> -----------------------------------------------------------------------
> eth4 | Embedded_NIC_4 | bce3 |
> -----------------------------------------------------------------------
>
> ------------
> | Next |
> ------------
>
> [ ice0 - Intel Controller 0, bce0 - Broadcom Controller 0 ]
>
> 1. In addition to the default ethN names the user can check against the available naming conventions and the wizard would show the names the interfaces will be renamed to.
> 2. The moment the user hits the Next button all interfaces are renamed as per the Naming convention they have selected.
> 3. Any further network communication would be using the new names.
> 4. Ifconfig would show names like "Embedded_NIC_1" and not eth0 etc.
That's a horrible interface to show the user when a large portion of
them do not care at all. (Also, not sure why netdev@vger cares about the
implementation details of OS installers.)
Bill
next prev parent reply other threads:[~2009-11-30 18:34 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
2009-11-30 18:34 ` Bill Nottingham [this message]
-- 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=20091130183435.GC15213@nostromo.devel.redhat.com \
--to=notting@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 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.