瀏覽代碼

Fix explanation of udev rules for drivers that create multiple interfaces

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.2/BOOK@7720 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Bruce Dubbs 19 年之前
父節點
當前提交
3a234c0a82
共有 1 個文件被更改,包括 4 次插入5 次删除
  1. 4 5
      chapter07/network.xml

+ 4 - 5
chapter07/network.xml

@@ -90,12 +90,11 @@ EOF</userinput></screen>
     the bus position as a key.</para>
 
     <para>The second known non-working case is with wireless cards using the
-    MadWifi or HostAP drivers, because they create at least two interfaces
-    with the same MAC address and bus position. For example, the Madwifi driver
+    MadWifi or HostAP drivers, because they create at least two interfaces with
+    the same MAC address and bus position. For example, the Madwifi driver
     creates both an athX and a wifiX interface where X is a digit.  To
-    disambiguate these cases, add SYSFS{type}=="zzz" after SUBSYSTEM=="net" for
-    each interface that is handled by that driver, where zzz is the output of
-    <userinput>cat /sys/class/net/&lt;interface_name&gt;/type</userinput>.</para>
+    differentiate these interfaces, add an appropriate KERNEL parameter such as
+    KERNEL=="ath*" after SUBSYSTEM=="net".</para>
 
     <para>There may be other cases where the rules above don't work. Currently,
     bugs on this topic are still being reported to Linux distributions, and no