From: Ondrej Zajicek <santiago@crfreenet.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Herbert Rosmanith <kernel@wildsau.enemy.org>,
linux-kernel@vger.kernel.org
Subject: Re: renaming kernel devices [was: VIA EPIA EK: strange eth dev numbering]
Date: Thu, 2 Aug 2007 16:51:52 +0200 [thread overview]
Message-ID: <20070802145152.GB19346@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0708021346300.24572@fbirervta.pbzchgretzou.qr>
On Thu, Aug 02, 2007 at 01:47:23PM +0200, Jan Engelhardt wrote:
> It does not rename ethX to the "next free" one, but to a _persistent_ one.
> If it were a "next free" thing, then removing a card would shuffle all
> your eth around again (and invalidate your iptables rules at the same
> time, to note).
It is questionable what is _persistent_ . MAC-based names are persistent
with regard to adding and removing of other cards, 'Plain' names are persistent
with regard to replacing that card with different item (of a same kind).
I am very happy that (using 'plain' names) i can send technician to
replace broken NIC in our routers without need for configuration
change.
--
Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
next prev parent reply other threads:[~2007-08-02 14:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 10:20 VIA EPIA EK: strange eth dev numbering Herbert Rosmanith
2007-08-02 10:26 ` Michael Tokarev
2007-08-02 10:42 ` Herbert Rosmanith
2007-08-02 10:49 ` Jan Engelhardt
2007-08-02 10:56 ` Herbert Rosmanith
2007-08-02 11:23 ` renaming kernel devices [was: VIA EPIA EK: strange eth dev numbering] Michael Tokarev
2007-08-02 11:47 ` Jan Engelhardt
2007-08-02 12:56 ` Michael Tokarev
2007-08-02 13:30 ` Jan Engelhardt
2007-08-02 13:36 ` Michael Tokarev
2007-08-02 14:37 ` Ondrej Zajicek
2007-08-02 13:43 ` Herbert Rosmanith
2007-08-02 14:51 ` Ondrej Zajicek [this message]
2007-08-03 4:45 ` david
2007-08-03 15:12 ` Stefan Richter
2007-08-04 4:33 ` david
2007-08-04 9:16 ` Stefan Richter
2007-08-04 17:06 ` david
2007-08-02 11:47 ` VIA EPIA EK: strange eth dev numbering Jan Engelhardt
2007-08-02 12:00 ` Herbert Rosmanith
2007-08-02 12:06 ` Jan Engelhardt
2007-08-02 13:07 ` Michael Tokarev
2007-08-02 13:38 ` Jan Engelhardt
2007-08-02 18:37 ` Jan Engelhardt
2007-08-02 22:00 ` Kay Sievers
2007-08-02 22:39 ` Jan Engelhardt
2007-08-02 22:49 ` Kay Sievers
2007-08-03 7:46 ` Jan Engelhardt
2007-08-02 11:12 ` Herbert Rosmanith
2007-08-02 10:44 ` Jan Engelhardt
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=20070802145152.GB19346@localhost.localdomain \
--to=santiago@crfreenet.org \
--cc=jengelh@computergmbh.de \
--cc=kernel@wildsau.enemy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
/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.