mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.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: VIA EPIA EK: strange eth dev numbering
Date: Fri, 03 Aug 2007 00:49:39 +0200	[thread overview]
Message-ID: <1186094979.3443.35.camel@lov.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0708030039300.495@fbirervta.pbzchgretzou.qr>


On Fri, 2007-08-03 at 00:39 +0200, Jan Engelhardt wrote:
> On Aug 3 2007 00:00, Kay Sievers wrote:
> >On 8/2/07, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> >> I know I have seen my kernel outputting "A renamed to B". Since you two
> >> however wanted that information in the first place, I grepped a bit
> >> around, and actually found, (drumroll), that the SUSE kernel has had a
> >> proper patch for [I can't remember how long] quite some time. (At least
> >> one distro which does the right thing.) I copied it below.
> >
> >> e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection
> >> dev_change_name: about to rename 'eth3' to 'eth0'
> >> dev_change_name: about to rename 'eth3' to 'ethxx3'
> >> eth3 renamed to ethxx3
> >
> >I just made udev when it successfully renamed an interface to write
> >that to the kernel log, so dmesg will show:
> >  <6>udev: renamed network interface eth0 to eth1
> 
> I think it is helpful to integrate the suse patch rather than to patch udev
> alone. This way, renames that do not involve udev also show up.

But if you need to swap interface names, you will see the useless
temporary device names. On SUSE, nothing else renames network interfaces
these days, so we'll probably just remove that patch. :)

Kay


  reply	other threads:[~2007-08-02 22:47 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
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 [this message]
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=1186094979.3443.35.camel@lov.localdomain \
    --to=kay.sievers@vrfy.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 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®