From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Race condition for udev/persistent-net
Date: Wed, 24 Jan 2007 10:08:27 +0000 [thread overview]
Message-ID: <200701241108.27162.zzam@gentoo.org> (raw)
In-Reply-To: <200701181131.55452.zzam@gentoo.org>
On Thursday 18 January 2007 11:31, Matthias Schwarzott wrote:
>
> It seems that DRIVERS is not always set when trying this rule. Removing it,
> or adding next rule to 05-udev-early.rules helped:
> ACTION="add", SUBSYSTEM="net", WAIT_FOR_SYSFS="device/driver"
>
>
> But the problem with this rule is: udev now waits also for a driver entry
> for loopback/bridge devices. This gives ugly log/console output.
>
> Is there a better place to put such a wait-rule?
>
Inbetween we found an even better rule to force udev waiting for device/driver
entry to appear:
ACTION="add", SUBSYSTEM="net", ENV{PHYSDEVDRIVER}="?*",
WAIT_FOR_SYSFS="device/driver"
Perhaps something like this should be added to rules contained in
udev-tarball, or at least meantioned in documentation.
Greetings
Matthias Schwarzott
--
Matthias Schwarzott (zzam)
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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:[~2007-01-24 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 10:31 Race condition for udev/persistent-net Matthias Schwarzott
2007-01-18 12:08 ` Bryan Kadzban
2007-01-24 10:08 ` Matthias Schwarzott [this message]
2007-01-24 10:22 ` Kay Sievers
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=200701241108.27162.zzam@gentoo.org \
--to=zzam@gentoo.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.