mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Rosmanith <kernel@wildsau.enemy.org>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: VIA EPIA EK: strange eth dev numbering
Date: Thu, 2 Aug 2007 12:42:56 +0200 (MET DST)	[thread overview]
Message-ID: <200708021042.l72AguIM008585@wildsau.enemy.org> (raw)
In-Reply-To: <46B1B160.8090906@msgid.tls.msk.ru>

> 
> Strange or not, correct or not - depends on the point of view.
> 
> The key word here is "udev" - check your udev rules.  Since some time
> ago udev on some distros comes with rules to give persistent device
> names for network interfaces.  Some time ago you had eth0 and eth1
> with different hardware, and udev remembered this fact somewhere.
> Now it sees new hardware, and gives it consecutive numbers, renaming
> kernel devices.

hu. where are the days when eth0 was eth0 ...

this means that, when I exchange a network card and replace it with a
new one, it will cost an "ethX" device name each time.

FYI, distribution is latest Gentoo.

as a friend of mine puts it:

    "Haha das is geil, das is wie bei Windows"
    "Wo er merkt, dass du ein neues Mainboard hast :)"

which translates:

    "Haha, that's randy, that's like in Windows, which
    notices that you've got a new mainboard"

Bad, bad Ferdl! How dare you compare this to M$Windows ;-)

well, Michael, thanks for the help,
herp


  reply	other threads:[~2007-08-02 10:43 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 10:20 Herbert Rosmanith
2007-08-02 10:26 ` Michael Tokarev
2007-08-02 10:42   ` Herbert Rosmanith [this message]
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
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=200708021042.l72AguIM008585@wildsau.enemy.org \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®