| 1 |
nightmorph 09/01/26 09:28:37 |
| 2 |
|
| 3 |
Modified: udev-guide.xml |
| 4 |
Log: |
| 5 |
added info on network device renaming to udev guide, bug 255613 |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.49 xml/htdocs/doc/en/udev-guide.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.49&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.49&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.48&r2=1.49 |
| 13 |
|
| 14 |
Index: udev-guide.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v |
| 17 |
retrieving revision 1.48 |
| 18 |
retrieving revision 1.49 |
| 19 |
diff -u -r1.48 -r1.49 |
| 20 |
--- udev-guide.xml 7 Sep 2008 01:41:53 -0000 1.48 |
| 21 |
+++ udev-guide.xml 26 Jan 2009 09:28:37 -0000 1.49 |
| 22 |
@@ -1,6 +1,6 @@ |
| 23 |
<?xml version='1.0' encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.48 2008/09/07 01:41:53 nightmorph Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.49 2009/01/26 09:28:37 nightmorph Exp $ --> |
| 27 |
|
| 28 |
<guide link="/doc/en/udev-guide.xml"> |
| 29 |
<title>Gentoo udev Guide</title> |
| 30 |
@@ -23,8 +23,8 @@ |
| 31 |
<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> |
| 32 |
<license/> |
| 33 |
|
| 34 |
-<version>3</version> |
| 35 |
-<date>2008-09-06</date> |
| 36 |
+<version>4</version> |
| 37 |
+<date>2009-01-26</date> |
| 38 |
|
| 39 |
<chapter> |
| 40 |
<title>What is udev?</title> |
| 41 |
@@ -200,6 +200,8 @@ |
| 42 |
[*] Support for hot-pluggable devices |
| 43 |
|
| 44 |
File systems ---> |
| 45 |
+ [*] Inotify file change notification support |
| 46 |
+ [*] Inotify support for userspace |
| 47 |
Pseudo filesystems ---> |
| 48 |
[*] /proc file system support |
| 49 |
[*] Virtual memory file system support (former shm fs) |
| 50 |
@@ -371,7 +373,7 @@ |
| 51 |
</body> |
| 52 |
</section> |
| 53 |
<section> |
| 54 |
-<title>Device renaming</title> |
| 55 |
+<title>Block device renaming</title> |
| 56 |
<body> |
| 57 |
|
| 58 |
<p> |
| 59 |
@@ -399,6 +401,34 @@ |
| 60 |
</body> |
| 61 |
</section> |
| 62 |
<section> |
| 63 |
+<title>Network device renaming</title> |
| 64 |
+<body> |
| 65 |
+ |
| 66 |
+<p> |
| 67 |
+Sometimes unplugging and replugging a network device (like a USB WiFi card) can |
| 68 |
+rename your net device each time, incrementing the number by one. |
| 69 |
+</p> |
| 70 |
+ |
| 71 |
+<p> |
| 72 |
+When this happens, you'll see it become <c>wlan0</c>, <c>wlan1</c>, |
| 73 |
+<c>wlan2</c>, etc. This is because udev is adding additional rules to its rules |
| 74 |
+file, instead of reloading the existing rules. Since udev watches its rules |
| 75 |
+directory via inotify, you need inotify support in your kernel config: |
| 76 |
+</p> |
| 77 |
+ |
| 78 |
+<pre caption="Enabling inotify support in the kernel"> |
| 79 |
+File systems ---> |
| 80 |
+ [*] Inotify file change notification support |
| 81 |
+ [*] Inotify support for userspace |
| 82 |
+</pre> |
| 83 |
+ |
| 84 |
+<p> |
| 85 |
+Now udev will retain proper names for your network devices. |
| 86 |
+</p> |
| 87 |
+ |
| 88 |
+</body> |
| 89 |
+</section> |
| 90 |
+<section> |
| 91 |
<title>udev loads modules in an unpredictable order</title> |
| 92 |
<body> |
Archives