* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2008-05-23 19:44 Sven Vermeulen (swift)
0 siblings, 0 replies; 12+ messages in thread
From: Sven Vermeulen (swift) @ 2008-05-23 19:44 UTC (permalink / raw
To: gentoo-commits
swift 08/05/23 19:44:06
Log:
--
gentoo-commits@lists.gentoo.org mailing list
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2008-08-19 12:51 Sven Vermeulen (swift)
0 siblings, 0 replies; 12+ messages in thread
From: Sven Vermeulen (swift) @ 2008-08-19 12:51 UTC (permalink / raw
To: gentoo-commits
swift 08/08/19 12:51:16
Log:
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2008-09-07 1:41 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 12+ messages in thread
From: Joshua Saddler (nightmorph) @ 2008-09-07 1:41 UTC (permalink / raw
To: gentoo-commits
nightmorph 08/09/07 01:41:54
Log:
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2009-01-26 9:28 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 12+ messages in thread
From: Joshua Saddler (nightmorph) @ 2009-01-26 9:28 UTC (permalink / raw
To: gentoo-commits
nightmorph 09/01/26 09:28:45
Modified: udev-guide.xml
Log:
added info on network device renaming to udev guide, bug 255613
Revision Changes Path
1.49 xml/htdocs/doc/en/udev-guide.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.49&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.49&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.48&r2=1.49
Index: udev-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- udev-guide.xml 7 Sep 2008 01:41:53 -0000 1.48
+++ udev-guide.xml 26 Jan 2009 09:28:37 -0000 1.49
@@ -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.48 2008/09/07 01:41:53 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.49 2009/01/26 09:28:37 nightmorph Exp $ -->
<guide link="/doc/en/udev-guide.xml">
<title>Gentoo udev Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>3</version>
-<date>2008-09-06</date>
+<version>4</version>
+<date>2009-01-26</date>
<chapter>
<title>What is udev?</title>
@@ -200,6 +200,8 @@
[*] Support for hot-pluggable devices
File systems --->
+ [*] Inotify file change notification support
+ [*] Inotify support for userspace
Pseudo filesystems --->
[*] /proc file system support
[*] Virtual memory file system support (former shm fs)
@@ -371,7 +373,7 @@
</body>
</section>
<section>
-<title>Device renaming</title>
+<title>Block device renaming</title>
<body>
<p>
@@ -399,6 +401,34 @@
</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>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2010-05-14 22:37 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 12+ messages in thread
From: Joshua Saddler (nightmorph) @ 2010-05-14 22:37 UTC (permalink / raw
To: gentoo-commits
nightmorph 10/05/14 22:37:43
Modified: udev-guide.xml
Log:
Remove unnecessary bit about enabling hot-pluggable device support. This is already enabled by default in modern kernels, since the option 'configure standard kernel features for small systems' is deselected by default, meaning everything under it is already activated. This includes hot-pluggable device support. bug 308453
Revision Changes Path
1.51 xml/htdocs/doc/en/udev-guide.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.51&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.51&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.50&r2=1.51
Index: udev-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- udev-guide.xml 5 Aug 2009 15:44:08 -0000 1.50
+++ udev-guide.xml 14 May 2010 22:37:43 -0000 1.51
@@ -1,8 +1,8 @@
<?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.50 2009/08/05 15:44:08 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.51 2010/05/14 22:37:43 nightmorph Exp $ -->
-<guide link="/doc/en/udev-guide.xml">
+<guide>
<title>Gentoo udev Guide</title>
<author title="Author">
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>5</version>
-<date>2009-08-05</date>
+<version>6</version>
+<date>2010-05-14</date>
<chapter>
<title>What is udev?</title>
@@ -196,9 +196,6 @@
</p>
<pre caption="Required kernel options">
-General setup --->
- [*] Support for hot-pluggable devices
-
File systems --->
[*] Inotify file change notification support
[*] Inotify support for userspace
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2010-12-26 19:21 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 12+ messages in thread
From: Joshua Saddler (nightmorph) @ 2010-12-26 19:21 UTC (permalink / raw
To: gentoo-commits
nightmorph 10/12/26 19:21:44
Modified: udev-guide.xml
Log:
the 'pcimodules' command doesn't exist anymore. 'lspci -k' is what i've always used to determine which module runs what bit of hardware, so i updated the guide to reflect this.
Revision Changes Path
1.52 xml/htdocs/doc/en/udev-guide.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.52&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.52&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.51&r2=1.52
Index: udev-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- udev-guide.xml 14 May 2010 22:37:43 -0000 1.51
+++ udev-guide.xml 26 Dec 2010 19:21:44 -0000 1.52
@@ -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.51 2010/05/14 22:37:43 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.52 2010/12/26 19:21:44 nightmorph Exp $ -->
<guide>
<title>Gentoo udev Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>6</version>
-<date>2010-05-14</date>
+<version>7</version>
+<date>2010-12-26</date>
<chapter>
<title>What is udev?</title>
@@ -457,8 +457,8 @@
module load order. First, you must stop udev from autoloading the modules by
blacklisting them. Be sure to use the exact name of the module being loaded.
For PCI devices, you'll need to use the module names obtained from the output of
-<c>pcimodules</c>, available in the <c>pciutils</c> package. The following
-example uses DVB modules.
+<c>lspci -k</c>, available in the <c>pciutils</c> package. The following example
+uses DVB modules.
</p>
<pre caption="Blacklisting modules">
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2011-03-12 5:44 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 12+ messages in thread
From: Joshua Saddler (nightmorph) @ 2011-03-12 5:44 UTC (permalink / raw
To: gentoo-commits
nightmorph 11/03/12 05:44:15
Modified: udev-guide.xml
Log:
update udev guide to remove sysfs, add uevents and rules.d, new profiles, and remove conf.d-rc; patch from swift on bug 358409
Revision Changes Path
1.53 xml/htdocs/doc/en/udev-guide.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.53&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.53&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.52&r2=1.53
Index: udev-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- udev-guide.xml 26 Dec 2010 19:21:44 -0000 1.52
+++ udev-guide.xml 12 Mar 2011 05:44:14 -0000 1.53
@@ -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.52 2010/12/26 19:21:44 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.53 2011/03/12 05:44:14 nightmorph Exp $ -->
<guide>
<title>Gentoo udev Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>7</version>
-<date>2010-12-26</date>
+<version>8</version>
+<date>2011-03-11</date>
<chapter>
<title>What is udev?</title>
@@ -71,103 +71,14 @@
</ul>
<p>
-To provide these features, udev is developed in three separate projects:
-<e>namedev</e>, <e>libsysfs</e> and, of course, <e>udev</e>.
-</p>
-
-</body>
-</section>
-<section>
-<title>namedev</title>
-<body>
-
-<p>
-Namedev allows you to define the device naming separately from the udev program.
-This allows for flexible naming policies and naming schemes developed by
-separate entities. This device naming subsystem provides a standard interface
-that udev can use.
-</p>
-
-<p>
-Currently only a single naming scheme is provided by namedev; the one provided
-by LANANA, used by the majority of Linux systems currently and therefore very
-suitable for the majority of Linux users.
-</p>
-
-<p>
-Namedev uses a 5-step procedure to find out the name of a given device. If the
-device name is found in one of the given steps, that name is used. The steps
-are:
-</p>
-
-<ul>
- <li>label or serial number</li>
- <li>bus device number</li>
- <li>bus topology</li>
- <li>statically given name</li>
- <li>kernel provided name</li>
-</ul>
-
-<p>
-The <e>label or serial number</e> step checks if the device has a unique
-identifier. For instance USB devices have a unique USB serial number; SCSI
-devices have a unique UUID. If namedev finds a match between this unique number
-and a given configuration file, the name provided in the configuration file is
-used.
-</p>
-
-<p>
-The <e>bus device number</e> step checks the device bus number. For
-non-hot-swappable environments this procedure is sufficient to
-identify a hardware device. For instance PCI bus numbers rarely change in the
-lifetime of a system. Again, if namedev finds a match between this position and
-a given configuration file, the name provided in that configuration file is
-used.
-</p>
-
-<p>
-Likewise the <e>bus topology</e> is a rather static way of defining devices as
-long as the user doesn't switch devices. When the position of the device matches
-a given setting provided by the user, the accompanying name is used.
-</p>
-
-<p>
-The fourth step, <e>statically given name</e>, is a simple string replacement.
-When the kernel name (the default name) matches a given replacement string, the
-substitute name will be used.
-</p>
-
-<p>
-The final step (<e>kernel provided name</e>) is a catch-all: this one takes
-the default name provided by the kernel. In the majority of cases this is
-sufficient as it matches the device naming used on current Linux systems.
-</p>
-
-</body>
-</section>
-<section>
-<title>libsysfs</title>
-<body>
-
-<p>
-udev interacts with the kernel through the sysfs pseudo filesystem. The libsysfs
-project provides a common API to access the information given by the sysfs
-filesystem in a generic way. This allows for querying all kinds of hardware
-without having to make assumptions on the kind of hardware.
-</p>
-
-</body>
-</section>
-<section>
-<title>udev</title>
-<body>
-
-<p>
-Every time the kernel gets an event in the device structure, it asks udev to
-take a look. udev follows the rules in the <path>/etc/udev/rules.d/</path>
-directory. udev then uses the information given by the kernel to perform the
-necessary actions on the <path>/dev</path> structure (creating or deleting
-device files).
+Every time a change happens within the device structure, the kernel emits a
+<e>uevent</e> which gets picked up by udev. udev then follows the rules as
+declared in the <path>/etc/udev/rules.d</path> and
+<path>/lib/udev/rules.d</path> directories. Based on the information contained
+within the uevent, it finds the rule or rules it needs to trigger and performs
+the required actions. These actions can be creating or deleting device files,
+but can also trigger the loading of particular firmware files into the
+kernel memory.
</p>
</body>
@@ -182,9 +93,11 @@
<p>
udev is meant to be used in combination with a 2.6 kernel (like
-<c>gentoo-sources</c> with the default 2007.0 profile). If you're using such a
-kernel then you just have to make sure that you have a recent
-<c>sys-apps/baselayout</c> version. That's all you need.
+<c>gentoo-sources</c> with the default 10.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
+this is not the case, then it is easy to install:
</p>
<pre caption="Installing udev">
@@ -196,11 +109,13 @@
</p>
<pre caption="Required kernel options">
-File systems --->
- [*] Inotify file change notification support
- [*] Inotify support for userspace
+General Setup --->
+ <comment>(Make sure the following item is *not* enabled)</comment>
+ [ ] enable deprecated sysfs features to support old userspace tools
+
+File Systems --->
+ [*] Inotify support for userspace
Pseudo filesystems --->
- [*] /proc file system support
[*] Virtual memory file system support (former shm fs)
</pre>
@@ -211,43 +126,6 @@
</body>
</section>
-<section>
-<title>Configuration</title>
-<body>
-
-<p>
-If you want to use the udev settings Gentoo provides to make your life
-comfortable, then read no more. Gentoo will use udev but keep a static
-<path>/dev</path> so that you will never have any missing device nodes.
-The Gentoo init scripts won't run the devfsd daemon and will deactivate devfs
-when you boot up.
-</p>
-
-<p>
-But if you are a die-hard and want to run a udev-only, unmodified system as is
-intended by the udev development (including the difficulties of missing device
-nodes because udev doesn't support them yet), by all means, read on :)
-</p>
-
-<p>
-We'll deactivate the rules that save the device file nodes: edit the
-<c>RC_DEVICE_TARBALL</c> variable in <path>/etc/conf.d/rc</path> and set it to
-<c>no</c>:
-</p>
-
-<pre caption="/etc/conf.d/rc">
-RC_DEVICE_TARBALL="no"
-</pre>
-
-<p>
-If you have included devfs support in your kernel, you can deactivate it in
-the bootloader configuration: add <c>gentoo=nodevfs</c> as a kernel parameter.
-If you want to use devfs and deactivate udev, add <c>gentoo=noudev</c> as kernel
-parameter.
-</p>
-
-</body>
-</section>
</chapter>
<chapter>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2012-12-25 18:41 Sven Vermeulen (swift)
0 siblings, 0 replies; 12+ messages in thread
From: Sven Vermeulen (swift) @ 2012-12-25 18:41 UTC (permalink / raw
To: gentoo-commits
swift 12/12/25 18:41:07
Modified: udev-guide.xml
Log:
Fix bug #448443 - Update to reflect recent kernels, reword a bit as well since 2.6.6 is not a "recent kernel" anymore. Thanks to Francesco Turco for reporting.
Revision Changes Path
1.56 xml/htdocs/doc/en/udev-guide.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.56&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.56&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.55&r2=1.56
Index: udev-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- udev-guide.xml 26 Dec 2011 15:22:40 -0000 1.55
+++ udev-guide.xml 25 Dec 2012 18:41:07 -0000 1.56
@@ -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.55 2011/12/26 15:22:40 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.56 2012/12/25 18:41:07 swift Exp $ -->
<guide>
<title>Gentoo udev Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>10</version>
-<date>2011-12-26</date>
+<version>12</version>
+<date>2012-12-25</date>
<chapter>
<title>What is udev?</title>
@@ -73,8 +73,8 @@
<p>
Every time a change happens within the device structure, the kernel emits a
<e>uevent</e> which gets picked up by udev. udev then follows the rules as
-declared in the <path>/etc/udev/rules.d</path> and
-<path>/lib/udev/rules.d</path> directories. Based on the information contained
+declared in the <path>/etc/udev/rules.d</path>, <path>/run/udev/rules.d</path>
+and <path>/lib/udev/rules.d</path> directories. Based on the information contained
within the uevent, it finds the rule or rules it needs to trigger and performs
the required actions. These actions can be creating or deleting device files,
but can also trigger the loading of particular firmware files into the
@@ -92,7 +92,7 @@
<body>
<p>
-udev is meant to be used in combination with a 2.6 kernel (like
+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
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>
@@ -242,7 +242,7 @@
<body>
<p>
-Recent versions of udev (104 and up) along with newer kernel versions (2.6.19
+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
@@ -360,7 +360,8 @@
<p>
For kernels older than 2.6.4 you have to explicitly include support for the
-<path>/dev/pts</path> filesystem.
+<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">
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2013-03-20 15:58 Sven Vermeulen (swift)
0 siblings, 0 replies; 12+ messages in thread
From: Sven Vermeulen (swift) @ 2013-03-20 15:58 UTC (permalink / raw
To: gentoo-commits
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>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2013-03-20 20:44 Sven Vermeulen (swift)
0 siblings, 0 replies; 12+ messages in thread
From: Sven Vermeulen (swift) @ 2013-03-20 20:44 UTC (permalink / raw
To: gentoo-commits
swift 13/03/20 20:44:10
Modified: udev-guide.xml
Log:
Further fix bug #462488 - Updates on udev guide
Revision Changes Path
1.58 xml/htdocs/doc/en/udev-guide.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.58&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.58&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.57&r2=1.58
Index: udev-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- udev-guide.xml 20 Mar 2013 15:58:35 -0000 1.57
+++ udev-guide.xml 20 Mar 2013 20:44:09 -0000 1.58
@@ -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.57 2013/03/20 15:58:35 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.58 2013/03/20 20:44:09 swift Exp $ -->
<guide>
<title>Gentoo udev Guide</title>
@@ -23,7 +23,7 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>13</version>
+<version>14</version>
<date>2013-03-20</date>
<chapter>
@@ -136,113 +136,12 @@
</chapter>
<chapter>
-<title>Known Issues</title>
-<section>
-<title>No Consistent Naming between DevFS and udev</title>
-<body>
-
-<p>
-Even though our intention is to have a consistent naming scheme between both
-dynamical device management solutions, sometimes naming differences do occur.
-</p>
-
-<p>
-One reported clash is with a HP Smart Array 5i RAID controller (more precisely
-the <c>cciss</c> kernel module). With udev, the devices are named
-<path>/dev/cciss/cXdYpZ</path> with X, Y and Z regular numbers. With devfs, the
-devices are <path>/dev/hostX/targetY/partZ</path> or symlinked from
-<path>/dev/cciss/cXdY</path>.
-</p>
-
-<p>
-If this is the case, don't forget to update your <path>/etc/fstab</path> and
-bootloader configuration files accordingly.
-</p>
-
-<p>
-The same happens with all-round symlinks that used to exist in
-<path>/dev</path>, such as <path>/dev/mouse</path>, which <c>udev</c> doesn't
-create anymore. Be certain to check your X configuration file and see if the
-Device rule for your mouse points to an existing device file.
-</p>
-
-<p>
-Another issue is the difference in naming of terminals between devfs and udev.
-While devfs calls its terminals <c>tty</c>, udev calls them <c>vc</c> and
-<c>tty</c>. This could lead to a problem in case you are restricting root
-logins from consoles using <path>/etc/securetty</path>. You will need to make
-sure that both <c>tty1</c> and <c>vc/1</c> are listed in
-<path>/etc/securetty</path> to ensure that root can login using the console.
-</p>
-
-</body>
-</section>
-<section>
-<title>udev loads modules in an unpredictable order</title>
-<body>
-
-<p>
-Sometimes udev loads modules in an undesired, unpredictable, or seemingly random
-order. This is especially common for systems that have multiple devices of the
-same type, as well as multimedia devices. This can affect the assigned numbers
-of devices; for example, sound cards may sometimes swap numbers.
-</p>
-
-<p>
-There are a few solutions to fix device numbers and/or module load order.
-Ideally, you can just use module parameters to specify your desired device
-number. Some modules, such as ALSA, include the "index" parameter. Modules that
-use the index parameter can be adjusted as shown. This example is for a system
-with two sound cards. The card with an index of 0 is designated as the first
-card. Once the parameters are changed, the module config files must be updated.
-</p>
-
-<pre caption="Specifying module parameters">
-# <i>echo "option snd-ice1724 index=0" >> /etc/modprobe.d/alsa.conf</i>
-# <i>echo "option snd-ymfpci index=1" >> /etc/modprobe.d/alsa.conf</i>
-# <i>update-modules</i>
-</pre>
-
-<p>
-The above example is the preferred solution, but not all modules support
-parameters such as index. For these modules, you'll have to force the correct
-module load order. First, you must stop udev from autoloading the modules by
-blacklisting them. Be sure to use the exact name of the module being loaded.
-For PCI devices, you'll need to use the module names obtained from the output of
-<c>lspci -k</c>, available in the <c>pciutils</c> package. The following example
-uses DVB modules.
-</p>
-
-<pre caption="Blacklisting modules">
-# <i>echo "blacklist b2c2-flexcop-pci" >> /etc/modprobe.d/dvb</i>
-# <i>echo "blacklist budget" >> /etc/modprobe.d/dvb</i>
-# <i>update-modules</i>
-</pre>
-
-<p>
-Next, load the modules in the correct order. Add them to
-<path>/etc/conf.d/modules</path> <e>in the exact order you want
-them loaded</e>.
-</p>
-
-<pre caption="Loading modules in the correct order">
-# <i>nano -w /etc/conf.d/modules</i>
-
-modules="<i>budget b2c2-flexcop-pci</i>"
-</pre>
-
-</body>
-</section>
-</chapter>
-
-<chapter>
<title>Resources & Acknowledgements</title>
<section>
<body>
<p>
-<uri link="http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames">
-Documentation for using the new predictable network interface names.</uri>
+Documentation for using <uri link="http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames">the new predictable network interface names.</uri>
</p>
<p>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2013-03-29 19:32 Sven Vermeulen (swift)
0 siblings, 0 replies; 12+ messages in thread
From: Sven Vermeulen (swift) @ 2013-03-29 19:32 UTC (permalink / raw
To: gentoo-commits
swift 13/03/29 19:32:27
Modified: udev-guide.xml
Log:
Fix bug #463778 - Updated udev guide with recent information thanks to Ssuominen
Revision Changes Path
1.59 xml/htdocs/doc/en/udev-guide.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.59&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.59&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.58&r2=1.59
Index: udev-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- udev-guide.xml 20 Mar 2013 20:44:09 -0000 1.58
+++ udev-guide.xml 29 Mar 2013 19:32:27 -0000 1.59
@@ -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.58 2013/03/20 20:44:09 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.59 2013/03/29 19:32:27 swift Exp $ -->
<guide>
<title>Gentoo udev Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>14</version>
-<date>2013-03-20</date>
+<version>15</version>
+<date>2013-03-29</date>
<chapter>
<title>What is udev?</title>
@@ -123,12 +123,13 @@
< > 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
+ [*] Maintain a devtmpfs filesystem to mount at /dev (NEW)
</pre>
<p>
-If you use <c>genkernel</c>, you don't need to do anything special. Genkernel
-sets up udev by default.
+If you use <c>sys-kernel/genkernel</c>, you don't need to do anything special.
+Genkernel sets up udev by default. You can also try <c>sys-kernel/dracut</c>
+which is quite well integrated into Gentoo.
</p>
</body>
@@ -141,18 +142,39 @@
<body>
<p>
-Documentation for using <uri link="http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames">the new predictable network interface names.</uri>
+Documentation for using <uri
+link="http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames">the
+predictable network interface names</uri> introduced in 197, replacing the now
+deleted rule_generator's /etc/udev/rules.d/70-persistent-net.rules
</p>
<p>
-<uri link="http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html">Decibel's
-UDEV Primer</uri> is an in-depth document about udev and Gentoo.
+<uri link="http://github.com/gentoo/eudev">Fork of the systemd git tree without
+systemd itself</uri> at github, with aims like longterm stable API, more POSIX
+than GNU, aimed much for minimal embedded but works on anything else too.
+You decide if it's up to date by looking at the repository's history, since
+this documentation might not be.
+</p>
+
+</body>
+</section>
+</chapter>
+
+<chapter>
+<title>Known problems</title>
+<section>
+<body>
+
+<p>
+Stale <c>70-persistent-net.rules</c> (or other network rules) in
+<path>/etc/udev/rules.d</path> can prevent the predictable network naming from
+being enabled. Both <c>70-persistent-net.rules</c> and
+<c>70-persistent-cd.rules</c> are from the now deleted rule_generator
</p>
<p>
-<uri link="http://www.reactivated.net/udevrules.php">Writing udev rules</uri> by
-fellow Gentoo developer Daniel Drake is an excellent document to learn how to
-customize your udev installation.
+Init script called 'udev-postmount' should be removed from runlevels if it's
+still there.
</p>
</body>
^ permalink raw reply [flat|nested] 12+ messages in thread
* [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml
@ 2013-04-06 11:40 Sven Vermeulen (swift)
0 siblings, 0 replies; 12+ messages in thread
From: Sven Vermeulen (swift) @ 2013-04-06 11:40 UTC (permalink / raw
To: gentoo-commits
swift 13/04/06 11:40:53
Modified: udev-guide.xml
Log:
Fix bug #453322 - Remove 2.6 kernel reference, recent udev requires 3.x
Revision Changes Path
1.60 xml/htdocs/doc/en/udev-guide.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.60&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?rev=1.60&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/udev-guide.xml?r1=1.59&r2=1.60
Index: udev-guide.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- udev-guide.xml 29 Mar 2013 19:32:27 -0000 1.59
+++ udev-guide.xml 6 Apr 2013 11:40:52 -0000 1.60
@@ -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.59 2013/03/29 19:32:27 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.60 2013/04/06 11:40:52 swift Exp $ -->
<guide>
<title>Gentoo udev Guide</title>
@@ -23,8 +23,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>15</version>
-<date>2013-03-29</date>
+<version>16</version>
+<date>2013-04-06</date>
<chapter>
<title>What is udev?</title>
@@ -92,7 +92,7 @@
<body>
<p>
-udev is meant to be used in combination with a 2.6 and 3.x kernel (like
+udev is meant to be used in combination with a 3.x kernel (like
<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>
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2013-04-06 11:40 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-06 11:40 [gentoo-commits] gentoo commit in xml/htdocs/doc/en: udev-guide.xml Sven Vermeulen (swift)
-- strict thread matches above, loose matches on Subject: below --
2013-03-29 19:32 Sven Vermeulen (swift)
2013-03-20 20:44 Sven Vermeulen (swift)
2013-03-20 15:58 Sven Vermeulen (swift)
2012-12-25 18:41 Sven Vermeulen (swift)
2011-03-12 5:44 Joshua Saddler (nightmorph)
2010-12-26 19:21 Joshua Saddler (nightmorph)
2010-05-14 22:37 Joshua Saddler (nightmorph)
2009-01-26 9:28 Joshua Saddler (nightmorph)
2008-09-07 1:41 Joshua Saddler (nightmorph)
2008-08-19 12:51 Sven Vermeulen (swift)
2008-05-23 19:44 Sven Vermeulen (swift)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox