From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Schwarzott Date: Wed, 24 Jan 2007 10:08:27 +0000 Subject: Re: Race condition for udev/persistent-net Message-Id: <200701241108.27162.zzam@gentoo.org> List-Id: References: <200701181131.55452.zzam@gentoo.org> In-Reply-To: <200701181131.55452.zzam@gentoo.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Thursday 18 January 2007 11:31, Matthias Schwarzott wrote: > > It seems that DRIVERS is not always set when trying this rule. Removing i= t, > or adding next rule to 05-udev-early.rules helped: > ACTION=3D"add", SUBSYSTEM=3D"net", WAIT_FOR_SYSFS=3D"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/dri= ver=20 entry to appear: ACTION=3D"add", SUBSYSTEM=3D"net", ENV{PHYSDEVDRIVER}=3D"?*",=20 WAIT_FOR_SYSFS=3D"device/driver" Perhaps something like this should be added to rules contained in=20 udev-tarball, or at least meantioned in documentation. Greetings Matthias Schwarzott --=20 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=3Djoin.php&p=3Dsourceforge&CID=DEVD= EV _______________________________________________ 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