From: Martin Hicks <mort@bork.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: romieu@fr.zoreil.com, netdev@vger.kernel.org
Subject: Re: r8169 cardbus device naming weirdness
Date: Wed, 24 May 2006 15:13:06 -0400 [thread overview]
Message-ID: <20060524191306.GA23153@bork.org> (raw)
In-Reply-To: <20060523105108.7c0e2367@localhost.localdomain>
On Tue, May 23, 2006 at 10:51:08AM -0700, Stephen Hemminger wrote:
>
> Most likely some user space script is renaming it.
> Each distro seems to have it's own way of doing configuration, and most
> do something in response to the hotplug event from device registration.
> So it was eth1 until what ever ran in response to the hotplug event
> decide to change it.
of course you're right.
/me fist shakes at udev
mh
--
Martin Hicks || mort@bork.org || PGP/GnuPG: 0x4C7F2BEE
prev parent reply other threads:[~2006-05-24 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 17:44 r8169 cardbus device naming weirdness Martin Hicks
2006-05-23 17:51 ` Stephen Hemminger
2006-05-24 19:13 ` Martin Hicks [this message]
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=20060524191306.GA23153@bork.org \
--to=mort@bork.org \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).