From: Mathieu Segaud <matt@minas-morgul.org>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Greg KH <greg@kroah.com>,
Hotplug Devel <linux-hotplug-devel@lists.sourceforge.net>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 046 release
Date: Fri, 19 Nov 2004 15:49:25 +0100 [thread overview]
Message-ID: <87654199my.fsf@barad-dur.crans.org> (raw)
In-Reply-To: <1100875339.18701.3.camel@localhost.localdomain> (Kay Sievers's message of "Fri, 19 Nov 2004 15:42:19 +0100")
Kay Sievers <kay.sievers@vrfy.org> disait dernièrement que :
> On Fri, 2004-11-19 at 12:26 +0100, Mathieu Segaud wrote:
>> seems like these changes broke something in rules applying to eth* devices.
>> the rules put and still working with udev 045 have no effect, now....
>> not so inconvenient now that I've got just one card in my box, but I guess
>> it could be a show-stopper for laptop users.
>>
>> My rules which can be found at the end of /etc/udev/rules.d/50-udev.rules are:
>>
>> KERNEL="eth*", SYSFS{address}="00:10:5a:49:36:d8", NAME="external"
>> KERNEL="eth*", SYSFS{address}="00:50:04:69:db:56", NAME="private"
>> KERNEL="eth*", SYSFS{address}="00:0c:6e:e4:2c:81", NAME="dmz"
>
> This should fix it.
will report success as soon as I create the ebuild, test it and I submit it to
greg-kh.
btw, thanks for the quick answer.
--
... mindreading equipment is currently classified CIA property at
best (hello echelon!)
- Alan Cox on linux-kernel
next prev parent reply other threads:[~2004-11-19 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 22:44 [ANNOUNCE] udev 046 release Greg KH
2004-11-19 11:26 ` Mathieu Segaud
2004-11-19 14:42 ` Kay Sievers
2004-11-19 14:49 ` Mathieu Segaud [this message]
2004-11-19 15:45 ` Mathieu Segaud
2004-11-19 22:48 ` Greg KH
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=87654199my.fsf@barad-dur.crans.org \
--to=matt@minas-morgul.org \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@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 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).