| |
|---|
| | Why Bother With ``udev``? |
|---|
| | ========================= |
|---|
| | |
|---|
| | There are many clever uses for ``udev`` documented on the Web, but |
|---|
| | the most common use is to ensure that when you connect a device |
|---|
| | - disk, tape, usb thumbdrive, camera... whatever - to a ``Linux`` |
|---|
| | the most common use is to ensure that when you connect a device - |
|---|
| | disk, tape, usb thumbdrive, camera... whatever - to a ``Linux`` |
|---|
| | system, that device shows up with the same name every time. |
|---|
| | |
|---|
| | Original ``Unix`` derivatives had a static tree of devices the system |
|---|
| | could support. This was encoded in the ``/dev`` file tree hierarchy. |
|---|
| |
|---|
| | |
|---|
| | Document Revision Information |
|---|
| | ============================= |
|---|
| | |
|---|
| | ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.101 2013/10/31 21:40:42 tundra Exp $`` |
|---|
| | ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.102 2013/10/31 21:45:08 tundra Exp $`` |
|---|
| | |
|---|
| | You can find the latest version of this document at: |
|---|
| | |
|---|
| | http://www.tundraware.com/TechnicalNotes/Deconstructing-Linux-udev-Rules |
|---|
| | |
tundra
authored
on 31 Oct 2013