/[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.17 Revision 1.18
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.17 2004/09/22 11:59:16 swift Exp $ --> 4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/udev-guide.xml,v 1.18 2004/09/30 11:27:35 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">
17This document explains what udev is and how you can use udev to fit your needs. 17This 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.13</version> 22<version>0.14</version>
23<date>September 22, 2004</date> 23<date>September 30, 2004</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>
370</pre> 370</pre>
371 371
372</body> 372</body>
373</section> 373</section>
374<section> 374<section>
375<title>No Consistent Naming between DevFS and udev</title>
376<body>
377
378<p>
379Even though our intention is to have a consistent naming scheme between both
380dynamical device management solutions, sometimes naming differences do occur.
381One reported clash is with a HP Smart Array 5i RAID controller (more precisely
382the <c>cciss</c> kernel module). With udev, the devices are named
383<path>/dev/cciss/cXdYpZ</path> with X, Y and Z regular numbers. With devfs, the
384devices are <path>/dev/hostX/targetY/partZ</path> or symlinked from
385<path>/dev/cciss/cXdY</path>.
386</p>
387
388<p>
389If this is the case, don't forget to update your <path>/etc/fstab</path> and
390bootloader configuration files accordingly.
391</p>
392
393</body>
394</section>
395<section>
375<title>Other issues</title> 396<title>Other issues</title>
376<body> 397<body>
377 398
378<p> 399<p>
379If device nodes are not created when a module is loaded from 400If device nodes are not created when a module is loaded from

Legend:
Removed from v.1.17  
changed lines
  Added in v.1.18

  ViewVC Help
Powered by ViewVC 1.1.20