Potential Udev networking breakage in trunk

Matthew Burgess matthew at linuxfromscratch.org
Sun Dec 7 11:10:15 PST 2008


Hi all,

Regarding the following commit:

> Author: matthew
> Date: 2008-12-07 04:45:47 -0700 (Sun, 07 Dec 2008)
> New Revision: 8768
...
> Modified: trunk/BOOK/chapter07/network.xml
> ===================================================================
> --- trunk/BOOK/chapter07/network.xml	2008-12-07 11:43:26 UTC (rev 8767)
> +++ trunk/BOOK/chapter07/network.xml	2008-12-07 11:45:47 UTC (rev 8768)
> @@ -40,7 +40,7 @@
>      same devices at every boot, including the first:</para>
> 
>  <screen><userinput>for NIC in /sys/class/net/* ; do
> -    INTERFACE=${NIC##*/} udevadm test --action=add --subsystem=net $NIC
> +    INTERFACE=${NIC##*/} udevadm test --action=add $NIC
>  done</userinput></screen>

This was required as the '--subsystem' parameter is no longer recognized by
udevadm.  My testbox is a VirtualBox virtual machine which only makes one
'pcnet32' device available to the guest OS.  That said, the above command did
generate the correct rule for that interface.  Confirmation of others' test
results, especially those with multiple NICs, would be appreciated.

Additionally, as the comments in #2284 suggest, I have probably broken building
from hosts with a kernel < 2.6.18.  If anyone has ready access to such a host,
I'd appreciate you testing that command both with and without
'SUBSYSTEM=net' set in your environment and report your results.

Thanks,

Matt.




More information about the lfs-dev mailing list