public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Nuno J. Silva (aka njsg)" <nunojsilva@ist.utl.pt>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt
Date: Fri, 29 Mar 2013 16:21:48 +0000 (UTC)	[thread overview]
Message-ID: <kj4f2s$45o$2@ger.gmane.org> (raw)
In-Reply-To: 51557DB2.1090202@flameeyes.eu

On 2013-03-29, Diego Elio Pettenò <flameeyes@flameeyes.eu> wrote:
> On 29/03/2013 12:34, Chí-Thanh Christopher Nguyễn wrote:
>> Diego Elio Pettenò schrieb:
>>> > If my desktop only has one Ethernet interface, no matter how many kernel
>>> > changes happen, it'll always be eth0.
>> That was not true with the old persistent naming. One example which we
>> encountered in #gentoo IRC was the split between e1000 and e1000e drivers
>> which caused interfaces to change names.
>
> Okay let me re-qualify the statement:
>
> "If my desktop only has one Ethernet interface, and I don't mess up with
> it in userspace at all, no matter how many kernel changes happen, it'll
> always be eth0".
>
> Yes, the previous persistent rules for udev would have messed that one
> up when e1000e got split, or if you switched between the
> Broadcom-provided driver to the kernel one or vice-versa. The deathforce
> drivers come in mind as well.

IMHO this is really relevant. It is annoying seeing how many people go
"oh you *must not* use the old scheme, because it won't work".

The new naming scheme does *not* prevent you from using eth0, users
should really just be told they can *disable* udev rules (and told how
to do it) if they are happy with the kernel name of their sole network
card, instead of being told that they *must* upgrade to the new rules.

The messages so far seem to imply that you can't have eth0. You *can*,
but udev won't be able to do anything if the device appears as
something else and there's already another eth0. If you don't already
have eth0, the udev rules *will* work, even if your card is named in
the eth namespace.

The *only* thing that breaks is renaming network devices to names that
are already in use inside the kernel namespaces.


-- 
Nuno Silva (aka njsg)
http://njsg.sdf-eu.org/



  reply	other threads:[~2013-03-29 16:22 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29  8:09 [gentoo-dev] Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt Samuli Suominen
2013-03-29 10:24 ` [gentoo-dev] " Duncan
2013-03-29 10:26   ` Samuli Suominen
2013-03-29 10:46     ` Diego Elio Pettenò
2013-03-29 10:50       ` Samuli Suominen
2013-03-29 11:01         ` Diego Elio Pettenò
2013-03-29 11:29           ` Samuli Suominen
2013-03-29 11:38             ` Diego Elio Pettenò
2013-03-29 12:20               ` Samuli Suominen
2013-03-29 12:33                 ` Diego Elio Pettenò
2013-03-29 12:47                 ` Michael Mol
2013-03-29 13:24                 ` Andreas K. Huettel
2013-03-29 13:30                   ` Rich Freeman
2013-03-29 13:44                     ` Samuli Suominen
2013-03-29 14:35                       ` Rich Freeman
2013-03-29 14:45                         ` Samuli Suominen
2013-03-29 14:55                           ` Rich Freeman
2013-03-31  8:41                           ` Walter Dnes
2013-03-31 10:21                             ` Nuno J. Silva (aka njsg)
2013-03-29 19:20                 ` Ian Stakenvicius
2013-03-29 20:03                   ` Diego Elio Pettenò
2013-03-31  1:06                 ` Philip Webb
2013-03-31  1:17                   ` Samuli Suominen
2013-03-31  1:20                     ` Diego Elio Pettenò
2013-03-31 10:18                     ` Nuno J. Silva (aka njsg)
2013-03-31 11:36                     ` Andreas K. Huettel
2013-03-31 14:22                     ` Philip Webb
2013-04-01  1:56                       ` [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt : SOLVED Philip Webb
2013-04-01  9:23                         ` Markos Chandras
2013-04-01 15:32                           ` Philip Webb
2013-04-01 17:06                             ` Markos Chandras
2013-04-01 19:53                               ` Michael Mol
2013-04-01 20:14                                 ` Markos Chandras
2013-03-29 11:34           ` [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt Chí-Thanh Christopher Nguyễn
2013-03-29 11:40             ` Diego Elio Pettenò
2013-03-29 16:21               ` Nuno J. Silva (aka njsg) [this message]
2013-03-29 16:40                 ` Markos Chandras
2013-03-29 17:38                   ` Rich Freeman
2013-03-29 22:27                     ` Walter Dnes
2013-03-29 18:03                 ` Samuli Suominen
2013-03-29 18:59                   ` Nuno J. Silva (aka njsg)
2013-03-29 11:13 ` [gentoo-dev] " Ulrich Mueller

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='kj4f2s$45o$2@ger.gmane.org' \
    --to=nunojsilva@ist.utl.pt \
    --cc=gentoo-dev@lists.gentoo.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