From: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Request of news item review: 2013-03-29-udev-predictable-network-interface-names.en.txt
Date: Fri, 29 Mar 2013 11:46:10 +0100 [thread overview]
Message-ID: <515570F2.2030902@flameeyes.eu> (raw)
In-Reply-To: <51556C3A.1020803@gentoo.org>
On 29/03/2013 11:26, Samuli Suominen wrote:
> With the new predictable network interface naming scheme which upstream enabled
> by default you don't have to rename anymore because the names will be static
> and not randomly rename when you, for example, upgrade the kernel. This can be
> very important aspect, for example, security in mind.
You do know this is false, right? The names are supposed to be
predictable, not persistent. If you do happen to MOVE your network card
because the new videocard you add to your system does not fit otherwise,
the name _will_ change.
> If /etc/udev/rules.d/80-net-name-slot.rules is a empty file, or if it's a
> symlink to /dev/null, the new names will be disabled and kernel will do
> all the interface naming, which will be random.
Avoid spreading FUD about naming being random. Thanks.
--
Diego Elio Pettenò — Flameeyes
flameeyes@flameeyes.eu — http://blog.flameeyes.eu/
next prev parent reply other threads:[~2013-03-29 10:46 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ò [this message]
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)
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=515570F2.2030902@flameeyes.eu \
--to=flameeyes@flameeyes.eu \
--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