From: "Andreas K. Huettel" <dilfridge@gentoo.org>
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: Sun, 31 Mar 2013 13:36:31 +0200 [thread overview]
Message-ID: <201303311336.38009.dilfridge@gentoo.org> (raw)
In-Reply-To: <51578EC0.60004@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 895 bytes --]
Am Sonntag, 31. März 2013, 03:17:52 schrieb Samuli Suominen:
> Nothing is stopping you from leaving out the symlink either and
> migrating to the new name despite using only 1 network card either,
> it's still more reliable than the kernel names
Why should I?
Kernel behaviour is traditionally way more stable than udev behaviour. If my
driver for my only one network card has always produced eth0 as device name,
chances are good it will do so still in a few years, after re-shuffling the
cards in my casing, and even after exchanging the whole motherboard.
Whereas with udev I can probably expect random things at random times for each
of these events.
Also, should I have problems with a new kernel, I can always just boot back
into an old one without much ado.
--
Andreas K. Huettel
Gentoo Linux developer
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-03-31 11:36 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 [this message]
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=201303311336.38009.dilfridge@gentoo.org \
--to=dilfridge@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