Difference between revisions of "Linux device management"
m (→Edit Log) |
m (cleaned up by copying directly from hypertwiki) |
||
| Line 1: | Line 1: | ||
| − | [[Linux]]: | + | [[Computing]]: [[Linux]]: [[Linux device management|device management]] |
| − | [[ | ||
==Notes== | ==Notes== | ||
| − | This text seemed like it might be useful information, even if it | + | This text seemed like it might be useful information, even if it contained some inaccuracies. Original document was published under [http://www.gnu.org/licenses/gpl.html GNU General Public License, Version 2], and those with appropriate knowledge should feel free to edit or expand the text. |
| − | contained some inaccuracies. Original document was published under | ||
| − | [http://www.gnu.org/licenses/gpl.html GNU General Public License, | ||
| − | Version 2], and those with appropriate knowledge should feel free to | ||
| − | edit or expand the text. | ||
==Edit Log== | ==Edit Log== | ||
| − | * '''2005-10-05''' Copied from | + | * '''2005-10-05''' Copied from http://www.reactivated.net/writing_udev_rules.html, with minor editing for clarity; the below was originally part of the udev article but seemed to belong here instead. The rest of the article should be checked to make sure it still makes sense without the introduction. |
| − | http://www.reactivated.net/writing_udev_rules.html, with minor editing | ||
| − | for clarity; the below was originally part of the udev article but | ||
| − | seemed to belong here instead. The rest of the article should be | ||
| − | checked to make sure it still makes sense without the introduction. | ||
==Text== | ==Text== | ||
A basic introduction only, might not be totally accurate. | A basic introduction only, might not be totally accurate. | ||
| − | On typical linux-based systems, the /dev directory is used to store | + | |
| − | file-like device nodes which refer to certain devices in the system. | + | On typical linux-based systems, the /dev directory is used to store file-like device nodes which refer to certain devices in the system. Each node points to a part of the system (a device), which might or might not exist. Userspace applications can use these device nodes to interface with the systems hardware, for example, XFree86 will "listen to" /dev/input/mice so that it can relate the users mouse movements to moving the visual mouse pointer. |
| − | Each node points to a part of the system (a device), which might or | + | |
| − | might not exist. Userspace applications can use these device nodes to | + | The original /dev directories were just populated with every device that might possibly appear in the system. /dev directories were typically very large because of this. devfs came along to provide a more managable approach (noticably, it only populated /dev with hardware that is plugged into the system), as well as some other functionality, but the system proved to have problems which could not be easily fixed. |
| − | interface with the systems hardware, for example, XFree86 will "listen | + | |
| − | to" /dev/input/mice so that it can relate the users mouse movements to | + | [[udev]] is the "new" way of managing /dev directories, designed to clear up some issues with previous /dev implementations, and provide a robust path forward. In order to create and name /dev device nodes corresponding to devices that are present in the system, udev relies on matching information provided by sysfs with rules provided by the user. |
| − | moving the visual mouse pointer. | + | |
| − | The original /dev directories were just populated with every device | + | [[sysfs]] is a new filesystem to the 2.6 kernels. It is managed by the kernel, and exports basic information about the devices currently plugged into your system. udev can use this information to create device nodes corresponding to your hardware. sysfs is mounted at /sys and is browsable. You may wish to investigate some of the files stored there before getting to grips with udev. Throughout this document, I will use the terms /sys and SYSFS interchangeably. |
| − | that might possibly appear in the system. /dev directories were | ||
| − | typically very large because of this. devfs came along to provide a | ||
| − | more managable approach (noticably, it only populated /dev with | ||
| − | hardware that is plugged into the system), as well as some other | ||
| − | functionality, but the system proved to have problems which could not | ||
| − | be easily fixed. | ||
| − | [[udev]] is the "new" way of managing /dev directories, designed to | ||
| − | clear up some issues with previous /dev implementations, and provide a | ||
| − | robust path forward. In order to create and name /dev device nodes | ||
| − | corresponding to devices that are present in the system, udev relies on | ||
| − | matching information provided by sysfs with rules provided by the user. | ||
| − | [[sysfs]] is a new filesystem to the 2.6 kernels. It is managed by the | ||
| − | kernel, and exports basic information about the devices currently | ||
| − | plugged into your system. udev can use this information to create | ||
| − | device nodes corresponding to your hardware. sysfs is mounted at /sys | ||
| − | and is browsable. You may wish to investigate some of the files stored | ||
| − | there before getting to grips with udev. Throughout this document, I | ||
| − | will use the terms /sys and SYSFS interchangeably. | ||
Revision as of 18:03, 14 October 2005
Computing: Linux: device management
Notes
This text seemed like it might be useful information, even if it contained some inaccuracies. Original document was published under GNU General Public License, Version 2, and those with appropriate knowledge should feel free to edit or expand the text.
Edit Log
- 2005-10-05 Copied from http://www.reactivated.net/writing_udev_rules.html, with minor editing for clarity; the below was originally part of the udev article but seemed to belong here instead. The rest of the article should be checked to make sure it still makes sense without the introduction.
Text
A basic introduction only, might not be totally accurate.
On typical linux-based systems, the /dev directory is used to store file-like device nodes which refer to certain devices in the system. Each node points to a part of the system (a device), which might or might not exist. Userspace applications can use these device nodes to interface with the systems hardware, for example, XFree86 will "listen to" /dev/input/mice so that it can relate the users mouse movements to moving the visual mouse pointer.
The original /dev directories were just populated with every device that might possibly appear in the system. /dev directories were typically very large because of this. devfs came along to provide a more managable approach (noticably, it only populated /dev with hardware that is plugged into the system), as well as some other functionality, but the system proved to have problems which could not be easily fixed.
udev is the "new" way of managing /dev directories, designed to clear up some issues with previous /dev implementations, and provide a robust path forward. In order to create and name /dev device nodes corresponding to devices that are present in the system, udev relies on matching information provided by sysfs with rules provided by the user.
sysfs is a new filesystem to the 2.6 kernels. It is managed by the kernel, and exports basic information about the devices currently plugged into your system. udev can use this information to create device nodes corresponding to your hardware. sysfs is mounted at /sys and is browsable. You may wish to investigate some of the files stored there before getting to grips with udev. Throughout this document, I will use the terms /sys and SYSFS interchangeably.