swift 13/03/20 15:58:35 Modified: udev-guide.xml Log: Fix bug #462448 - Update udev guide, thanks to ssuominen for patch
Revision Changes Path 1.57 xml/htdocs/doc/en/udev-guide.xml file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.57&view=markup plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.57&content-type=text/plain diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.56&r2=1.57 Index: udev-guide.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v retrieving revision 1.56 retrieving revision 1.57 diff -u -r1.56 -r1.57 --- udev-guide.xml 25 Dec 2012 18:41:07 -0000 1.56 +++ udev-guide.xml 20 Mar 2013 15:58:35 -0000 1.57 @@ -1,6 +1,6 @@ <?xml version='1.0' encoding="UTF-8"?> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.56 2012/12/25 18:41:07 swift Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.57 2013/03/20 15:58:35 swift Exp $ --> <guide> <title>Gentoo udev Guide</title> @@ -23,8 +23,8 @@ <!-- See http://creativecommons.org/licenses/by-sa/2.5 --> <license/> -<version>12</version> -<date>2012-12-25</date> +<version>13</version> +<date>2013-03-20</date> <chapter> <title>What is udev?</title> @@ -93,7 +93,7 @@ <p> udev is meant to be used in combination with a 2.6 and 3.x kernel (like -<c>gentoo-sources</c> with the default 10.0 profile). If you're using such a +<c>gentoo-sources</c> with the default 13.0 profile). If you're using such a kernel then you just should have no issues whatsoever with using udev as the necessary support is built-in in all stable <c>sys-apps/baselayout</c> versions. Normally, udev should already be installed on your system, but if @@ -111,12 +111,19 @@ <pre caption="Required kernel options"> General Setup ---> <comment>(Make sure the following item is *not* enabled)</comment> - [ ] enable deprecated sysfs features to support old userspace tools + [ ] Enable deprecated sysfs features to support old userspace tools File Systems ---> [*] Inotify support for userspace Pseudo filesystems ---> [*] Virtual memory file system support (former shm fs) + +Device Drivers ---> + <comment>(Make sure the following item is *not* enabled)</comment> + < > ATA/ATAPI/MFM/RLL support (DEPRECATED) + <comment>(This is *absolutely* necessary for /dev to populate)</comment> + Generic Driver Options ---> + [*] Maintain a devtmpfs filesystem to mount at /dev </pre> <p> @@ -131,73 +138,6 @@ <chapter> <title>Known Issues</title> <section> -<title>Missing device node files at boot</title> -<body> - -<p> -If you can't boot successfully because you get an error about -<path>/dev/null</path> not found, or because the initial console is missing, the -problem is that you lack some device files that must be available <e>before</e> -<path>/dev</path> is mounted and handled by udev. This is common on Gentoo -machines installed from old media. -</p> - -<p> -If you run <c>sys-apps/baselayout-1.8.12</c> or later, this problem is -alleviated since the boot process should still manage to complete. However, to -get rid of those annoying warnings, you should create the missing device nodes -as described below. -</p> - -<p> -To see which devices nodes are present before the <path>/dev</path> filesystem -is mounted, run the following commands: -</p> - -<pre caption="Listing device nodes available at boot"> -# <i>mkdir test</i> -# <i>mount --bind / test</i> -# <i>cd test/dev</i> -# <i>ls</i> -</pre> - -<p> -The devices needed for a successful boot are <path>/dev/null</path> and -<path>/dev/console</path>. If they didn't show up in the previous test, you have -to create them manually. Issue the following commands in the -<path>test/dev/</path> directory: -</p> - -<pre caption="Creating necessary device node files"> -# <i>mknod -m 660 console c 5 1</i> -# <i>mknod -m 660 null c 1 3</i> -</pre> - -<p> -When you're finished, don't forget to unmount the <path>test/</path> directory: -</p> - -<pre caption="Unmounting the test/ directory"> -# <i>cd ../..</i> -# <i>umount test</i> -# <i>rmdir test</i> -</pre> - -</body> -</section> -<section> -<title>udev and nvidia</title> -<body> - -<p> -If you use the proprietary driver from nVidia and the X server fails to start on -a udev-only system, then make sure you have the <c>nvidia</c> module listed in -<path>/etc/conf.d/modules</path>. -</p> - -</body> -</section> -<section> <title>No Consistent Naming between DevFS and udev</title> <body> @@ -238,62 +178,6 @@ </body> </section> <section> -<title>Block device renaming</title> -<body> - -<p> -For a couple of years, udev (104 and up) along with the Linux kernel (versions 2.6.19 -and up) may change your disc device names, due to a change in the kernel's -libata implementation. A CD-RW device at <path>/dev/hdc</path> may be changed to -<path>/dev/sr0</path>. While this is not normally a problem, it may cause issues -for some applications that are hardcoded to look for devices at other locations. -For example, <c>media-sound/rip</c> expects to find discs at -<path>/dev/cdrom</path>, which becomes a problem if you use a newer kernel and -udev renames your device to <path>/dev/cdrom1</path>. -</p> - -<p> -To work around these issues, you must edit -<path>/etc/udev/rules.d/70-persistent-cd.rules</path> and assign the correct -name to the device. -</p> - -<p> -For more information on writing udev rules, be sure to read Daniel Drake's <uri -link="http://www.reactivated.net/udevrules.php";>guide</uri>. -</p> - -</body> -</section> -<section> -<title>Network device renaming</title> -<body> - -<p> -Sometimes unplugging and replugging a network device (like a USB WiFi card) can -rename your net device each time, incrementing the number by one. -</p> - -<p> -When this happens, you'll see it become <c>wlan0</c>, <c>wlan1</c>, -<c>wlan2</c>, etc. This is because udev is adding additional rules to its rules -file, instead of reloading the existing rules. Since udev watches its rules -directory via inotify, you need inotify support in your kernel config: -</p> - -<pre caption="Enabling inotify support in the kernel"> -File systems ---> - [*] Inotify file change notification support - [*] Inotify support for userspace -</pre> - -<p> -Now udev will retain proper names for your network devices. -</p> - -</body> -</section> -<section> <title>udev loads modules in an unpredictable order</title> <body> @@ -349,29 +233,6 @@ </body> </section> -<section> -<title>Other issues</title> -<body> - -<p> -Support for the framebuffer devices (<path>/dev/fb/*</path>) comes with the -kernel starting from version 2.6.6-rc2. -</p> - -<p> -For kernels older than 2.6.4 you have to explicitly include support for the -<path>/dev/pts</path> filesystem, although we <e>seriously</e> recommend you to -switch to a more recent kernel. -</p> - -<pre caption="Enabling the /dev/pts filesystem"> -File systems ---> - Pseudo filesystems ---> - [*] /dev/pts file system for Unix98 PTYs -</pre> - -</body> -</section> </chapter> <chapter> @@ -380,9 +241,8 @@ <body> <p> -The udev talk on the Linux Symposium (Ottawa, Ontario Canada - 2003) given by -Greg Kroah-Hartman (IBM Corporation) provided a solid understanding on the udev -application. +<uri link="http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames";> +Documentation for using the new predictable network interface names.</uri> </p> <p>
