| 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 | |
3 | |
| 4 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.21 2004/11/26 22:13:36 swift Exp $ --> |
4 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.22 2004/11/28 14:50:37 swift Exp $ --> |
| 5 | |
5 | |
| 6 | <guide link="/doc/en/udev-guide.xml"> |
6 | <guide link="/doc/en/udev-guide.xml"> |
| 7 | <title>Gentoo udev Guide</title> |
7 | <title>Gentoo udev Guide</title> |
| 8 | |
8 | |
| 9 | <author title="Author"> |
9 | <author title="Author"> |
| … | |
… | |
| 17 | This document explains what udev is and how you can use udev to fit your needs. |
17 | This document explains what udev is and how you can use udev to fit your needs. |
| 18 | </abstract> |
18 | </abstract> |
| 19 | |
19 | |
| 20 | <license/> |
20 | <license/> |
| 21 | |
21 | |
| 22 | <version>0.17</version> |
22 | <version>0.18</version> |
| 23 | <date>2004-11-26</date> |
23 | <date>2004-11-28</date> |
| 24 | |
24 | |
| 25 | <chapter> |
25 | <chapter> |
| 26 | <title>What is udev?</title> |
26 | <title>What is udev?</title> |
| 27 | <section> |
27 | <section> |
| 28 | <title>The /dev Directory</title> |
28 | <title>The /dev Directory</title> |
| … | |
… | |
| 390 | <body> |
390 | <body> |
| 391 | |
391 | |
| 392 | <p> |
392 | <p> |
| 393 | Even though our intention is to have a consistent naming scheme between both |
393 | Even though our intention is to have a consistent naming scheme between both |
| 394 | dynamical device management solutions, sometimes naming differences do occur. |
394 | dynamical device management solutions, sometimes naming differences do occur. |
|
|
395 | </p> |
|
|
396 | |
|
|
397 | <p> |
| 395 | One reported clash is with a HP Smart Array 5i RAID controller (more precisely |
398 | One reported clash is with a HP Smart Array 5i RAID controller (more precisely |
| 396 | the <c>cciss</c> kernel module). With udev, the devices are named |
399 | the <c>cciss</c> kernel module). With udev, the devices are named |
| 397 | <path>/dev/cciss/cXdYpZ</path> with X, Y and Z regular numbers. With devfs, the |
400 | <path>/dev/cciss/cXdYpZ</path> with X, Y and Z regular numbers. With devfs, the |
| 398 | devices are <path>/dev/hostX/targetY/partZ</path> or symlinked from |
401 | devices are <path>/dev/hostX/targetY/partZ</path> or symlinked from |
| 399 | <path>/dev/cciss/cXdY</path>. |
402 | <path>/dev/cciss/cXdY</path>. |
| … | |
… | |
| 402 | <p> |
405 | <p> |
| 403 | If this is the case, don't forget to update your <path>/etc/fstab</path> and |
406 | If this is the case, don't forget to update your <path>/etc/fstab</path> and |
| 404 | bootloader configuration files accordingly. |
407 | bootloader configuration files accordingly. |
| 405 | </p> |
408 | </p> |
| 406 | |
409 | |
|
|
410 | <p> |
|
|
411 | The same happens with all-round symlinks that used to exist in |
|
|
412 | <path>/dev</path>, such as <path>/dev/mouse</path>, which <c>udev</c> doesn't |
|
|
413 | create anymore. Be certain to check your X configuration file and see if the |
|
|
414 | Device rule for your mice point to existing device files. |
|
|
415 | </p> |
|
|
416 | |
| 407 | </body> |
417 | </body> |
| 408 | </section> |
418 | </section> |
| 409 | <section> |
419 | <section> |
| 410 | <title>Other issues</title> |
420 | <title>Other issues</title> |
| 411 | <body> |
421 | <body> |
Parent Directory
| 
Revision Log
| 
Patch