| |
|---|
| | |
|---|
| | |
|---|
| | :Author: Tim Daneliuk (tundra@tundraware.com) |
|---|
| | |
|---|
| | :Version: ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.124 2013/11/01 04:28:33 tundra Exp $`` |
|---|
| | :Version: ``$Id: Deconstructing_Linux_udev_Rules.rst,v 1.125 2013/11/01 13:35:01 tundra Exp $`` |
|---|
| | |
|---|
| | |
|---|
| | Précis |
|---|
| | ====== |
|---|
| |
|---|
| | Let's symlink ``/dev/raw/raw1`` to ``/dev/rmy_fine_disk01``. |
|---|
| | It is a time honored ``Unix`` convention that the raw device |
|---|
| | name be the same as the actual device with an ``r`` prepended |
|---|
| | to it. You don't have to do this, but if you don't, people |
|---|
| | will hate youu, your dog will probably run away, and your |
|---|
| | will hate you, your dog will probably run away, and your |
|---|
| | ex-wife will show up again ... and no one wants that. |
|---|
| | |
|---|
| | The DBAs can then configure their database engines to look for the |
|---|
| | symlink name and never worry about what the underlying node |
|---|
| |
|---|
| | |
tundra
authored
on 1 Nov 2013