| 1 | <?xml version='1.0' encoding="UTF-8"?> |
1 | <?xml version='1.0' encoding="UTF-8"?> |
| 2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/devfs-guide.xml,v 1.16 2007/11/16 10:28:01 jkt Exp $ --> |
2 | <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/devfs-guide.xml,v 1.17 2008/05/23 19:52:53 swift Exp $ --> |
| 3 | |
3 | |
| 4 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
4 | <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 5 | |
5 | |
| 6 | <guide link="/doc/en/devfs-guide.xml" disclaimer="obsolete"> |
6 | <guide link="/doc/en/devfs-guide.xml" disclaimer="obsolete"> |
| 7 | <title>Device File System Guide</title> |
7 | <title>Device File System Guide</title> |
| … | |
… | |
| 158 | <p> |
158 | <p> |
| 159 | Yet devfs does come with it's own problems; for the end users these issues |
159 | Yet devfs does come with it's own problems; for the end users these issues |
| 160 | aren't really visible, but for the kernel maintainers the problems are big |
160 | aren't really visible, but for the kernel maintainers the problems are big |
| 161 | enough to mark devfs <e>obsolete</e> in favor of <uri |
161 | enough to mark devfs <e>obsolete</e> in favor of <uri |
| 162 | link="udev-guide.xml">udev</uri>, which Gentoo supports and uses by default on |
162 | link="udev-guide.xml">udev</uri>, which Gentoo supports and uses by default on |
| 163 | most architectures since the 2005.0 release when using a 2.6 kernel. |
163 | most architectures since the 2005.0 release when using a 2.6 kernel. |
| 164 | </p> |
164 | </p> |
| 165 | |
165 | |
| 166 | <p> |
166 | <p> |
| 167 | For more information as to why devfs is marked obsolete, please read the <uri |
167 | For more information as to why devfs is marked obsolete, please read the <uri |
| 168 | link="http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ">udev |
168 | link="http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ">udev |
| … | |
… | |
| 189 | |
189 | |
| 190 | <p> |
190 | <p> |
| 191 | For instance, all IDE-related devices are inside the |
191 | For instance, all IDE-related devices are inside the |
| 192 | <path>/dev/ide/</path> device directory, and SCSI-related devices are inside |
192 | <path>/dev/ide/</path> device directory, and SCSI-related devices are inside |
| 193 | <path>/dev/scsi/</path>. SCSI and IDE disks are seen in the same way, |
193 | <path>/dev/scsi/</path>. SCSI and IDE disks are seen in the same way, |
| 194 | meaning they both have the same subdirectory structure. |
194 | meaning they both have the same subdirectory structure. |
| 195 | </p> |
195 | </p> |
| 196 | |
196 | |
| 197 | <p> |
197 | <p> |
| 198 | IDE and SCSI disks are controlled by an adapter (on-board or a seperate |
198 | IDE and SCSI disks are controlled by an adapter (on-board or a seperate |
| 199 | card), called the <e>host</e>. Every adapter can have several channels. |
199 | card), called the <e>host</e>. Every adapter can have several channels. |
| … | |
… | |
| 295 | <section> |
295 | <section> |
| 296 | <title>Removing compatibility symlinks</title> |
296 | <title>Removing compatibility symlinks</title> |
| 297 | <body> |
297 | <body> |
| 298 | |
298 | |
| 299 | <warn> |
299 | <warn> |
| 300 | Currently, Gentoo cannot live without the compatibility symlinks. |
300 | Currently, Gentoo cannot live without the compatibility symlinks. |
| 301 | </warn> |
301 | </warn> |
| 302 | |
302 | |
| 303 | <p> |
303 | <p> |
| 304 | If you want the compatibility symlinks that clutter up <path>/dev</path> |
304 | If you want the compatibility symlinks that clutter up <path>/dev</path> |
| 305 | removed from your Gentoo system (Gentoo activates it per default), edit |
305 | removed from your Gentoo system (Gentoo activates it per default), edit |
| … | |
… | |
| 346 | These instructions are valid as long as pam_console is disabled in |
346 | These instructions are valid as long as pam_console is disabled in |
| 347 | <path>/etc/pam.d/system-auth</path>. If you enabled pam_console there, then PAM |
347 | <path>/etc/pam.d/system-auth</path>. If you enabled pam_console there, then PAM |
| 348 | has the final word on permissions. You shouldn't be using pam_console anyway, as |
348 | has the final word on permissions. You shouldn't be using pam_console anyway, as |
| 349 | it has been <uri |
349 | it has been <uri |
| 350 | link="http://www.gentoo.org/proj/en/base/pam/upgrade-0.99.xml">removed from |
350 | link="http://www.gentoo.org/proj/en/base/pam/upgrade-0.99.xml">removed from |
| 351 | Portage</uri>. |
351 | Portage</uri>. |
| 352 | </impo> |
352 | </impo> |
| 353 | |
353 | |
| 354 | <p> |
354 | <p> |
| 355 | If you want to set permissions using <path>/etc/devfsd.conf</path>, |
355 | If you want to set permissions using <path>/etc/devfsd.conf</path>, |
| 356 | then use the syntax used in the following example: |
356 | then use the syntax used in the following example: |
Parent Directory
| 
Revision Log
| 
Patch