From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: /etc/dev.d/net/hotplug.dev
Date: Thu, 28 Oct 2004 21:45:55 +0000 [thread overview]
Message-ID: <20041028214555.GA9098@vrfy.org> (raw)
In-Reply-To: <048e01c4bd33$e2657c20$0a00000a@eugenia>
On Thu, Oct 28, 2004 at 02:19:59PM -0700, Eugenia Loli-Queru wrote:
> Hi,
> I am not happy with the way hotplug does the naming of my ethernet cards.
> It gives eth0 to my wireless pcmcia card, and eth1 to my normal onboard
> ethernet pci card. However, I want them the other way around, eth0 for my
> pci card and eth1 for my wifi one, because I don't like all the confusion
> of my main card becoming eth0 when my wifi card is not in the pcmcia slot.
>
> So, what I did is this, as supported by latest udev.rules, to try and force
> the system:
> KERNEL="eth*", SYSFS{address}="00:09:5b:c2:ce:01", NAME="eth1" # wifi
> KERNEL="eth*", SYSFS{address}="00:a0:cc:de:27:0c", NAME="eth0" # ethernet
>
> But hotplug and your /etc/dev.d/net/hotplug.dev script completely ignores
> this and again names them the other way around... Is there any way around
> it?
>
> I am using udev 0.42, latest hotplug, kernel 2.6.8.1 on Arch Linux 0.7+.
Your distributions network scripts may bring the interface up, before udev is
able to rename it?
Kay
-------------------------------------------------------
This Newsletter Sponsored by: Macrovision
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-10-28 21:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-28 21:19 /etc/dev.d/net/hotplug.dev Eugenia Loli-Queru
2004-10-28 21:45 ` Kay Sievers [this message]
2004-10-28 23:03 ` /etc/dev.d/net/hotplug.dev Eugenia Loli-Queru
2004-10-28 23:41 ` /etc/dev.d/net/hotplug.dev Kay Sievers
2004-10-29 0:36 ` /etc/dev.d/net/hotplug.dev Eugenia Loli-Queru
2004-10-29 10:58 ` /etc/dev.d/net/hotplug.dev Christian Zoz
2004-10-29 18:53 ` /etc/dev.d/net/hotplug.dev Eugenia Loli-Queru
2004-10-29 21:27 ` /etc/dev.d/net/hotplug.dev Olaf Hering
2004-10-29 22:03 ` /etc/dev.d/net/hotplug.dev Eugenia Loli-Queru
2004-10-29 22:05 ` /etc/dev.d/net/hotplug.dev Olaf Hering
2004-10-29 22:14 ` /etc/dev.d/net/hotplug.dev Marco d'Itri
2004-11-01 22:38 ` /etc/dev.d/net/hotplug.dev Greg KH
2004-11-01 22:43 ` /etc/dev.d/net/hotplug.dev Eugenia Loli-Queru
2004-11-01 22:53 ` /etc/dev.d/net/hotplug.dev Greg KH
2004-11-02 0:01 ` /etc/dev.d/net/hotplug.dev Mathieu Segaud
2004-11-02 0:09 ` /etc/dev.d/net/hotplug.dev Eugenia Loli-Queru
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=20041028214555.GA9098@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.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 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.