| 1 |
swift 13/03/20 15:58:35 |
| 2 |
|
| 3 |
Modified: udev-guide.xml |
| 4 |
Log: |
| 5 |
Fix bug #462448 - Update udev guide, thanks to ssuominen for patch |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.57 xml/htdocs/doc/en/udev-guide.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.57&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.57&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.56&r2=1.57 |
| 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.56 |
| 18 |
retrieving revision 1.57 |
| 19 |
diff -u -r1.56 -r1.57 |
| 20 |
--- udev-guide.xml 25 Dec 2012 18:41:07 -0000 1.56 |
| 21 |
+++ udev-guide.xml 20 Mar 2013 15:58:35 -0000 1.57 |
| 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.56 2012/12/25 18:41:07 swift Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.57 2013/03/20 15:58:35 swift Exp $ --> |
| 27 |
|
| 28 |
<guide> |
| 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>12</version> |
| 35 |
-<date>2012-12-25</date> |
| 36 |
+<version>13</version> |
| 37 |
+<date>2013-03-20</date> |
| 38 |
|
| 39 |
<chapter> |
| 40 |
<title>What is udev?</title> |
| 41 |
@@ -93,7 +93,7 @@ |
| 42 |
|
| 43 |
<p> |
| 44 |
udev is meant to be used in combination with a 2.6 and 3.x kernel (like |
| 45 |
-<c>gentoo-sources</c> with the default 10.0 profile). If you're using such a |
| 46 |
+<c>gentoo-sources</c> with the default 13.0 profile). If you're using such a |
| 47 |
kernel then you just should have no issues whatsoever with using udev as the |
| 48 |
necessary support is built-in in all stable <c>sys-apps/baselayout</c> |
| 49 |
versions. Normally, udev should already be installed on your system, but if |
| 50 |
@@ -111,12 +111,19 @@ |
| 51 |
<pre caption="Required kernel options"> |
| 52 |
General Setup ---> |
| 53 |
<comment>(Make sure the following item is *not* enabled)</comment> |
| 54 |
- [ ] enable deprecated sysfs features to support old userspace tools |
| 55 |
+ [ ] Enable deprecated sysfs features to support old userspace tools |
| 56 |
|
| 57 |
File Systems ---> |
| 58 |
[*] Inotify support for userspace |
| 59 |
Pseudo filesystems ---> |
| 60 |
[*] Virtual memory file system support (former shm fs) |
| 61 |
+ |
| 62 |
+Device Drivers ---> |
| 63 |
+ <comment>(Make sure the following item is *not* enabled)</comment> |
| 64 |
+ < > ATA/ATAPI/MFM/RLL support (DEPRECATED) |
| 65 |
+ <comment>(This is *absolutely* necessary for /dev to populate)</comment> |
| 66 |
+ Generic Driver Options ---> |
| 67 |
+ [*] Maintain a devtmpfs filesystem to mount at /dev |
| 68 |
</pre> |
| 69 |
|
| 70 |
<p> |
| 71 |
@@ -131,73 +138,6 @@ |
| 72 |
<chapter> |
| 73 |
<title>Known Issues</title> |
| 74 |
<section> |
| 75 |
-<title>Missing device node files at boot</title> |
| 76 |
-<body> |
| 77 |
- |
| 78 |
-<p> |
| 79 |
-If you can't boot successfully because you get an error about |
| 80 |
-<path>/dev/null</path> not found, or because the initial console is missing, the |
| 81 |
-problem is that you lack some device files that must be available <e>before</e> |
| 82 |
-<path>/dev</path> is mounted and handled by udev. This is common on Gentoo |
| 83 |
-machines installed from old media. |
| 84 |
-</p> |
| 85 |
- |
| 86 |
-<p> |
| 87 |
-If you run <c>sys-apps/baselayout-1.8.12</c> or later, this problem is |
| 88 |
-alleviated since the boot process should still manage to complete. However, to |
| 89 |
-get rid of those annoying warnings, you should create the missing device nodes |
| 90 |
-as described below. |
| 91 |
-</p> |
| 92 |
- |
| 93 |
-<p> |
| 94 |
-To see which devices nodes are present before the <path>/dev</path> filesystem |
| 95 |
-is mounted, run the following commands: |
| 96 |
-</p> |
| 97 |
- |
| 98 |
-<pre caption="Listing device nodes available at boot"> |
| 99 |
-# <i>mkdir test</i> |
| 100 |
-# <i>mount --bind / test</i> |
| 101 |
-# <i>cd test/dev</i> |
| 102 |
-# <i>ls</i> |
| 103 |
-</pre> |
| 104 |
- |
| 105 |
-<p> |
| 106 |
-The devices needed for a successful boot are <path>/dev/null</path> and |
| 107 |
-<path>/dev/console</path>. If they didn't show up in the previous test, you have |
| 108 |
-to create them manually. Issue the following commands in the |
| 109 |
-<path>test/dev/</path> directory: |
| 110 |
-</p> |
| 111 |
- |
| 112 |
-<pre caption="Creating necessary device node files"> |
| 113 |
-# <i>mknod -m 660 console c 5 1</i> |
| 114 |
-# <i>mknod -m 660 null c 1 3</i> |
| 115 |
-</pre> |
| 116 |
- |
| 117 |
-<p> |
| 118 |
-When you're finished, don't forget to unmount the <path>test/</path> directory: |
| 119 |
-</p> |
| 120 |
- |
| 121 |
-<pre caption="Unmounting the test/ directory"> |
| 122 |
-# <i>cd ../..</i> |
| 123 |
-# <i>umount test</i> |
| 124 |
-# <i>rmdir test</i> |
| 125 |
-</pre> |
| 126 |
- |
| 127 |
-</body> |
| 128 |
-</section> |
| 129 |
-<section> |
| 130 |
-<title>udev and nvidia</title> |
| 131 |
-<body> |
| 132 |
- |
| 133 |
-<p> |
| 134 |
-If you use the proprietary driver from nVidia and the X server fails to start on |
| 135 |
-a udev-only system, then make sure you have the <c>nvidia</c> module listed in |
| 136 |
-<path>/etc/conf.d/modules</path>. |
| 137 |
-</p> |
| 138 |
- |
| 139 |
-</body> |
| 140 |
-</section> |
| 141 |
-<section> |
| 142 |
<title>No Consistent Naming between DevFS and udev</title> |
| 143 |
<body> |
| 144 |
|
| 145 |
@@ -238,62 +178,6 @@ |
| 146 |
</body> |
| 147 |
</section> |
| 148 |
<section> |
| 149 |
-<title>Block device renaming</title> |
| 150 |
-<body> |
| 151 |
- |
| 152 |
-<p> |
| 153 |
-For a couple of years, udev (104 and up) along with the Linux kernel (versions 2.6.19 |
| 154 |
-and up) may change your disc device names, due to a change in the kernel's |
| 155 |
-libata implementation. A CD-RW device at <path>/dev/hdc</path> may be changed to |
| 156 |
-<path>/dev/sr0</path>. While this is not normally a problem, it may cause issues |
| 157 |
-for some applications that are hardcoded to look for devices at other locations. |
| 158 |
-For example, <c>media-sound/rip</c> expects to find discs at |
| 159 |
-<path>/dev/cdrom</path>, which becomes a problem if you use a newer kernel and |
| 160 |
-udev renames your device to <path>/dev/cdrom1</path>. |
| 161 |
-</p> |
| 162 |
- |
| 163 |
-<p> |
| 164 |
-To work around these issues, you must edit |
| 165 |
-<path>/etc/udev/rules.d/70-persistent-cd.rules</path> and assign the correct |
| 166 |
-name to the device. |
| 167 |
-</p> |
| 168 |
- |
| 169 |
-<p> |
| 170 |
-For more information on writing udev rules, be sure to read Daniel Drake's <uri |
| 171 |
-link="http://www.reactivated.net/udevrules.php">guide</uri>. |
| 172 |
-</p> |
| 173 |
- |
| 174 |
-</body> |
| 175 |
-</section> |
| 176 |
-<section> |
| 177 |
-<title>Network device renaming</title> |
| 178 |
-<body> |
| 179 |
- |
| 180 |
-<p> |
| 181 |
-Sometimes unplugging and replugging a network device (like a USB WiFi card) can |
| 182 |
-rename your net device each time, incrementing the number by one. |
| 183 |
-</p> |
| 184 |
- |
| 185 |
-<p> |
| 186 |
-When this happens, you'll see it become <c>wlan0</c>, <c>wlan1</c>, |
| 187 |
-<c>wlan2</c>, etc. This is because udev is adding additional rules to its rules |
| 188 |
-file, instead of reloading the existing rules. Since udev watches its rules |
| 189 |
-directory via inotify, you need inotify support in your kernel config: |
| 190 |
-</p> |
| 191 |
- |
| 192 |
-<pre caption="Enabling inotify support in the kernel"> |
| 193 |
-File systems ---> |
| 194 |
- [*] Inotify file change notification support |
| 195 |
- [*] Inotify support for userspace |
| 196 |
-</pre> |
| 197 |
- |
| 198 |
-<p> |
| 199 |
-Now udev will retain proper names for your network devices. |
| 200 |
-</p> |
| 201 |
- |
| 202 |
-</body> |
| 203 |
-</section> |
| 204 |
-<section> |
| 205 |
<title>udev loads modules in an unpredictable order</title> |
| 206 |
<body> |
| 207 |
|
| 208 |
@@ -349,29 +233,6 @@ |
| 209 |
|
| 210 |
</body> |
| 211 |
</section> |
| 212 |
-<section> |
| 213 |
-<title>Other issues</title> |
| 214 |
-<body> |
| 215 |
- |
| 216 |
-<p> |
| 217 |
-Support for the framebuffer devices (<path>/dev/fb/*</path>) comes with the |
| 218 |
-kernel starting from version 2.6.6-rc2. |
| 219 |
-</p> |
| 220 |
- |
| 221 |
-<p> |
| 222 |
-For kernels older than 2.6.4 you have to explicitly include support for the |
| 223 |
-<path>/dev/pts</path> filesystem, although we <e>seriously</e> recommend you to |
| 224 |
-switch to a more recent kernel. |
| 225 |
-</p> |
| 226 |
- |
| 227 |
-<pre caption="Enabling the /dev/pts filesystem"> |
| 228 |
-File systems ---> |
| 229 |
- Pseudo filesystems ---> |
| 230 |
- [*] /dev/pts file system for Unix98 PTYs |
| 231 |
-</pre> |
| 232 |
- |
| 233 |
-</body> |
| 234 |
-</section> |
| 235 |
</chapter> |
| 236 |
|
| 237 |
<chapter> |
| 238 |
@@ -380,9 +241,8 @@ |
| 239 |
<body> |
| 240 |
|
| 241 |
<p> |
| 242 |
-The udev talk on the Linux Symposium (Ottawa, Ontario Canada - 2003) given by |
| 243 |
-Greg Kroah-Hartman (IBM Corporation) provided a solid understanding on the udev |
| 244 |
-application. |
| 245 |
+<uri link="http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames"> |
| 246 |
+Documentation for using the new predictable network interface names.</uri> |
| 247 |
</p> |
| 248 |
|
| 249 |
<p> |
Archives