Line 1:
Line 1:
−
For ease of server maintenace it is sometimes preferable to use a human readable symlink to a device rather than refer to the some what cryptic computer device names. For example /dev/ups is easier to understand that this device has a UPS attached to it rather than /dev/ttyS0. However any manually entered symlinks do not survive a reboot as udev creates the /dev structure at boot time.
+
For ease of server maintenace it is sometimes preferable to use a human readable symlink to a device rather than the some what cryptic computer device names. For example /dev/ups is easier to understand that this device has a UPS attached to it rather than /dev/ttyS0. However any manually entered symlinks do not survive a reboot as udev creates the /dev directory structure at boot time.
You have to get udev to create the symlinks for you. This is straightforward with the use of a custom template.
You have to get udev to create the symlinks for you. This is straightforward with the use of a custom template.
Line 5:
Line 5:
<ol></li><li>Create the directory /etc/e-smith/templates-custom/etc/udev/rules.d/10-local.rules and change to it.
<ol></li><li>Create the directory /etc/e-smith/templates-custom/etc/udev/rules.d/10-local.rules and change to it.
−
</li><li>Using your favorite text editor create a file with a suitable mnemonic name with content similar to:
+
</li><li>Using your favorite text editor create a file with a suitable mnemonic name and content similar to:
# For <description of symlink>
# For <description of symlink>