/[gentoo]/xml/htdocs/doc/en/udev-guide.xml
Gentoo

Diff of /xml/htdocs/doc/en/udev-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.44 Revision 1.45
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 2<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.44 2007/10/30 20:31:27 nightmorph Exp $ --> 3<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.45 2008/05/23 19:44:06 swift Exp $ -->
4 4
5<guide link="/doc/en/udev-guide.xml"> 5<guide link="/doc/en/udev-guide.xml">
6<title>Gentoo udev Guide</title> 6<title>Gentoo udev Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
51 51
52<p> 52<p>
53Think about hotpluggable devices like USB, IEEE1394, hot-swappable PCI, ... What 53Think about hotpluggable devices like USB, IEEE1394, hot-swappable PCI, ... What
54is the first device? And for how long? What will the other devices be named when 54is the first device? And for how long? What will the other devices be named when
55the first one disappears? How will that affect ongoing transactions? Wouldn't it 55the first one disappears? How will that affect ongoing transactions? Wouldn't it
56be fun that a printing job is suddenly moved from your supernew laserprinter to 56be fun that a printing job is suddenly moved from your supernew laserprinter to
57your almost-dead matrix printer because your mom decided to pull the plug of the 57your almost-dead matrix printer because your mom decided to pull the plug of the
58laserprinter which happened to be the first printer? 58laserprinter which happened to be the first printer?
59</p> 59</p>
60 60
61<p> 61<p>
115and a given configuration file, the name provided in the configuration file is 115and a given configuration file, the name provided in the configuration file is
116used. 116used.
117</p> 117</p>
118 118
119<p> 119<p>
120The <e>bus device number</e> step checks the device bus number. For 120The <e>bus device number</e> step checks the device bus number. For
121non-hot-swappable environments this procedure is sufficient to 121non-hot-swappable environments this procedure is sufficient to
122identify a hardware device. For instance PCI bus numbers rarely change in the 122identify a hardware device. For instance PCI bus numbers rarely change in the
123lifetime of a system. Again, if namedev finds a match between this position and 123lifetime of a system. Again, if namedev finds a match between this position and
124a given configuration file, the name provided in that configuration file is 124a given configuration file, the name provided in that configuration file is
125used. 125used.
132</p> 132</p>
133 133
134<p> 134<p>
135The fourth step, <e>statically given name</e>, is a simple string replacement. 135The fourth step, <e>statically given name</e>, is a simple string replacement.
136When the kernel name (the default name) matches a given replacement string, the 136When the kernel name (the default name) matches a given replacement string, the
137substitute name will be used. 137substitute name will be used.
138</p>
139
140<p> 138</p>
139
140<p>
141The final step (<e>kernel provided name</e>) is a catch-all: this one takes 141The final step (<e>kernel provided name</e>) is a catch-all: this one takes
142the default name provided by the kernel. In the majority of cases this is 142the default name provided by the kernel. In the majority of cases this is
143sufficient as it matches the device naming used on current Linux systems. 143sufficient as it matches the device naming used on current Linux systems.
144</p> 144</p>
145 145
146</body> 146</body>
147</section> 147</section>
219 219
220<p> 220<p>
221If you want to use the udev-tweaks Gentoo added to make your life 221If you want to use the udev-tweaks Gentoo added to make your life
222comfortable, then read no more. Gentoo will use udev but keep a static 222comfortable, then read no more. Gentoo will use udev but keep a static
223<path>/dev</path> so that you will never have any missing device nodes. 223<path>/dev</path> so that you will never have any missing device nodes.
224The Gentoo init scripts won't run the devfsd daemon and will deactivate devfs 224The Gentoo init scripts won't run the devfsd daemon and will deactivate devfs
225when you boot up. 225when you boot up.
226</p> 226</p>
227 227
228<p> 228<p>
229But if you are a die-hard and want to run a udev-only, no-tweaked system as is 229But if you are a die-hard and want to run a udev-only, no-tweaked system as is
230intended by the udev development (including the difficulties of missing device 230intended by the udev development (including the difficulties of missing device
231nodes because udev doesn't support them yet), by all means, read on :) 231nodes because udev doesn't support them yet), by all means, read on :)
232</p> 232</p>
233 233
234<p> 234<p>
235We'll deactivate the rules that save the device file nodes: edit the 235We'll deactivate the rules that save the device file nodes: edit the
236<c>RC_DEVICE_TARBALL</c> variable in <path>/etc/conf.d/rc</path> and set it to 236<c>RC_DEVICE_TARBALL</c> variable in <path>/etc/conf.d/rc</path> and set it to
237<c>no</c>: 237<c>no</c>:
238</p> 238</p>
239 239
240<pre caption="/etc/conf.d/rc"> 240<pre caption="/etc/conf.d/rc">
241RC_DEVICE_TARBALL="no" 241RC_DEVICE_TARBALL="no"
242</pre> 242</pre>
243 243
244<p> 244<p>
245If you have included devfs support in your kernel, you can deactivate it in 245If you have included devfs support in your kernel, you can deactivate it in
246the bootloader configuration: add <c>gentoo=nodevfs</c> as a kernel parameter. 246the bootloader configuration: add <c>gentoo=nodevfs</c> as a kernel parameter.
247If you want to use devfs and deactivate udev, add <c>gentoo=noudev</c> as kernel 247If you want to use devfs and deactivate udev, add <c>gentoo=noudev</c> as kernel
248parameter. 248parameter.
249</p> 249</p>
250 250
251</body> 251</body>
334<section> 334<section>
335<title>No Consistent Naming between DevFS and udev</title> 335<title>No Consistent Naming between DevFS and udev</title>
336<body> 336<body>
337 337
338<p> 338<p>
339Even though our intention is to have a consistent naming scheme between both 339Even though our intention is to have a consistent naming scheme between both
340dynamical device management solutions, sometimes naming differences do occur. 340dynamical device management solutions, sometimes naming differences do occur.
341</p> 341</p>
342 342
343<p> 343<p>
344One reported clash is with a HP Smart Array 5i RAID controller (more precisely 344One reported clash is with a HP Smart Array 5i RAID controller (more precisely
495Greg Kroah-Hartman (IBM Corporation) provided a solid understanding on the udev 495Greg Kroah-Hartman (IBM Corporation) provided a solid understanding on the udev
496application. 496application.
497</p> 497</p>
498 498
499<p> 499<p>
500<uri link="http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html">Decibel's 500<uri link="http://webpages.charter.net/decibelshelp/LinuxHelp_UDEVPrimer.html">Decibel's
501UDEV Primer</uri> is an in-depth document about udev and Gentoo. 501UDEV Primer</uri> is an in-depth document about udev and Gentoo.
502</p> 502</p>
503 503
504<p> 504<p>
505<uri link="http://www.reactivated.net/udevrules.php">Writing udev rules</uri> by 505<uri link="http://www.reactivated.net/udevrules.php">Writing udev rules</uri> by

Legend:
Removed from v.1.44  
changed lines
  Added in v.1.45

  ViewVC Help
Powered by ViewVC 1.1.20