mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Herbert Rosmanith <kernel@wildsau.enemy.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Michael Tokarev <mjt@tls.msk.ru>, linux-kernel@vger.kernel.org
Subject: Re: VIA EPIA EK: strange eth dev numbering
Date: Thu, 2 Aug 2007 13:12:10 +0200 (MET DST)	[thread overview]
Message-ID: <200708021112.l72BCAW0008626@wildsau.enemy.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0708021246200.24572@fbirervta.pbzchgretzou.qr>


> > cards around), eth0 would also suddenly become a different one. There never
> > *were* days when eth0 remained eth0 across such changes.
> 
> but there *were* days when eth0 was eth0, if the kernel reports it as such.
> now there is no eth0 at all. if I see an "eth0" from dmesg, I expect
> it to be present.

hm, well, a thought, maybe udev should report what is doing, like
printinig "renamed eth0 to eth2", or such.

the problem with this device renaming in my case was that other software,
in particular dhcpcd, didnt get any lease, because (obviously?) dhcpcd
on the other hand _still_ seemed to look for eth0, and thus, after
booting, there was no network configured at all.

Maybe the name "eth0" is hardcoded in the gentoo init scripts, I dont know.

Can this be considered a distrubtion bug?

cheers,
herp

  parent reply	other threads:[~2007-08-02 11:12 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
2007-08-03  7:46                       ` Jan Engelhardt
2007-08-02 11:12       ` Herbert Rosmanith [this message]
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=200708021112.l72BCAW0008626@wildsau.enemy.org \
    --to=kernel@wildsau.enemy.org \
    --cc=jengelh@computergmbh.de \
    --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®