| |
|---|
| | for software to use when referencing this disk. Say I'm writing |
|---|
| | an application. I don't have to know where the disk is mounted. |
|---|
| | I just have to always refer to ``/dev/my_fine_disk01`` and let all |
|---|
| | this ``udev`` magic do the hard stuff. Remember, it's our job as |
|---|
| | Snotty Systems Engineers to relieve applications programmers of as |
|---|
| | Snotty Systems Engineers to relieve Applications Programmers of as |
|---|
| | much thinking as possible. Really, it is. Look in the job |
|---|
| | description. |
|---|
| | |
|---|
| | |
|---|
| |
|---|
| | we just did that at the end of the previous rule. |
|---|
| | |
|---|
| | - ``SYMLINK+="rmy_fine_disk01"`` |
|---|
| | |
|---|
| | Let's symlink ``/dev/raw/raw1`` to ``/dev/rmy_fine_dis01``. |
|---|
| | Let's symlink ``/dev/raw/raw1`` to ``/dev/rmy_fine_disk01``. The |
|---|
| | DBAs can then configure their database engines to look for the |
|---|
| | symlink name and never worry about what the underlying node |
|---|
| | mapping is for the raw device. Just as with Applications |
|---|
| | Programmers, we Snotty Systems Engineers are required - by law - |
|---|
| | to make things as easy as possible for DBAs. Again, I refer you |
|---|
| | to the job description. |
|---|
| | |
|---|
| | |
|---|
| | - ``OWNER:="3009", GROUP:="421", MODE:="0600`` |
|---|
| | |
|---|
| | And finally, as before, we set ownership and permission, this |
|---|
| | time for the raw character device, not the associated block |
|---|
| | device (which we took care of in the first rule). |
|---|
| | |
|---|
| | |
|---|
| | |
|---|
| | |
|---|
| |
|---|
| | |
|---|
| | Document Revision Information |
|---|
| | ============================= |
|---|
| | |
|---|
| | ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.110 2013/11/01 01:56:06 tundra Exp $`` |
|---|
| | ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.111 2013/11/01 02:00:13 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