public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Re: call for testers: udev predictable network interface names
Date: Mon, 14 Jan 2013 13:06:43 -0600	[thread overview]
Message-ID: <20130114190643.GA17645@linux1> (raw)
In-Reply-To: <20130114060401.GA1422@rathaus.eclipse.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

On Mon, Jan 14, 2013 at 06:04:01AM +0000, Steven J. Long wrote:
> On Sat, Jan 12, 2013 William Hubbs wrote:
> > Steven J. Long wrote:
> > > If you're certain that every user with a current simple setup, who
> > > uses the kernel default names, and has such a firewall setup isn't
> > > going to suddenly find their interface name changed when they reboot,
> > > fair play to you. If not, allow the admin to opt-in, rather than force
> > > them to opt-out when something breaks.
> > 
> > The following is taken from the wiki:
> > 
> > You basically have three options: 
> <3 options that all require an admin opt-in to keep their existing
>  config running>
> 
> There you go: the exact wrong way to do it. As Poettering might say:
> "C'mon man, seriously? (whiny voice and pleading looks)"

If you have read this thread at all, you see that when you upgrade to
udev-197, I create a file, /etc/udev/rules.d/80-net-name-slot.rules on
your system.

Now, go and compare that fact to the wiki page and tell me if I'm not
setting you up to be opted out of this by default.

There is a separate issue, which is new installs. I have a bug opened
with the docs team and release engineering to discuss whether we want
the new names for new installs.

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2013-01-14 19:06 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 22:13 [gentoo-dev] call for testers: udev predictable network interface names William Hubbs
2013-01-09 22:59 ` Christopher Head
2013-01-10  0:13   ` William Hubbs
2013-01-10  0:46     ` Christopher Head
2013-01-12  2:11       ` [gentoo-dev] " Steven J. Long
2013-01-12 17:55         ` Alec Warner
2013-01-12 18:03         ` William Hubbs
2013-01-14  6:04           ` [gentoo-dev] " Steven J. Long
2013-01-14 14:39             ` Peter Stuge
2013-01-14 18:35               ` Kevin Chadwick
2013-01-15  9:29                 ` Debian patching KDE to use /etc for configuration (was: Re: [gentoo-dev] Re: Re: call for testers: udev predictable network interface names) Samuli Suominen
2013-01-15 10:25                   ` Kevin Chadwick
2013-01-15 11:00                     ` Rich Freeman
2013-01-15 16:19                       ` Alec Warner
2013-01-15 19:43                         ` Kevin Chadwick
2013-01-15 20:19                           ` Maxim Kammerer
2013-01-15 21:26                             ` Kevin Chadwick
2013-01-16  6:33                           ` Alec Warner
2013-01-16 20:34                             ` Kevin Chadwick
2013-01-17  5:36                               ` Alec Warner
2013-01-17 15:02                                 ` [gentoo-dev] Re: Debian patching KDE to use /etc for configuration Ian Stakenvicius
2013-01-17 15:21                                   ` Maxim Kammerer
2013-01-17 18:01                                 ` Debian patching KDE to use /etc for configuration (was: Re: [gentoo-dev] Re: Re: call for testers: udev predictable network interface names) Kevin Chadwick
2013-01-14 19:06             ` William Hubbs [this message]
2013-01-15  0:25               ` [gentoo-dev] Re: Re: call for testers: udev predictable network interface names Peter Stuge
2013-01-15  2:48                 ` William Hubbs
2013-01-15 13:35                   ` Ian Stakenvicius
2013-01-13 22:24         ` [gentoo-dev] " Kevin Chadwick
2013-01-14  6:17           ` [gentoo-dev] " Steven J. Long
2013-01-10  4:21 ` [gentoo-dev] " Daniel Campbell
2013-01-10  4:33   ` Rich Freeman
2013-01-10  4:36     ` Daniel Campbell
2013-01-10  6:15     ` William Hubbs
2013-01-10  9:22   ` [gentoo-dev] " Nuno J. Silva
2013-01-10 14:01   ` [gentoo-dev] " Ian Stakenvicius
2013-01-15  8:42 ` Michael Weber
2013-01-15 14:03   ` Ian Stakenvicius
2013-01-15  9:16 ` Michael Weber
2013-01-15 13:58   ` Ian Stakenvicius
2013-01-15 18:58     ` Greg KH
2013-01-15 23:08       ` Rich Freeman
2013-01-16  3:42         ` Peter Stuge
2013-01-16 11:36           ` Rich Freeman
2013-01-17  2:49             ` Greg KH
2013-01-17  2:55               ` Rich Freeman
2013-01-17 14:51                 ` Ian Stakenvicius
2013-01-21 13:50                   ` Rich Freeman
2013-01-17  8:48               ` Samuli Suominen
2013-01-16 15:19       ` Tobias Klausmann
2013-01-16 16:25         ` Mike Gilbert
2013-01-16 16:37           ` vivo75
2013-01-16 16:38           ` Michael Weber
2013-01-17 16:48         ` Peter Stuge
2013-01-17 18:44           ` Tobias Klausmann
2013-01-17 22:25             ` William Hubbs
2013-01-18 12:24 ` vivo75
2013-01-18 13:33   ` Ian Stakenvicius
2013-01-18 14:54     ` William Hubbs
2013-01-18 15:07       ` Ian Stakenvicius
2013-01-19 18:20         ` William Hubbs
2013-01-19 23:13           ` Francesco Riosa

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=20130114190643.GA17645@linux1 \
    --to=williamh@gentoo.org \
    --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