| 1 |
Ian Stakenvicius wrote: |
| 2 |
> > WilliamH wants everyone using /dev/disk/by-label/<name> |
| 3 |
> > paths in fstab to instead use LABEL=<name> , to avoid issues if udev |
| 4 |
> > doesn't create the symlinks before localmount tries to use them. |
| 5 |
.. |
| 6 |
> UUID is the same situation in this case -- in fstab you can do it by |
| 7 |
> UUID=<uuid> or you can do it by /dev/disk/by-uuid/<uuid>. The latter |
| 8 |
> form depends on udev finishing up and would have the same issue. |
| 9 |
|
| 10 |
It seems that the former form may also depend on udev having settled. |
| 11 |
|
| 12 |
--8<-- mount(8) |
| 13 |
The device indication. |
| 14 |
.. |
| 15 |
The recommended setup is to use tags (e.g. LABEL=<label>) rather |
| 16 |
than /dev/disk/by-{label,uuid,partuuid,partlabel} udev symlinks |
| 17 |
in the /etc/fstab file. The tags are more readable, robust and |
| 18 |
portable. The mount(8) command internally uses udev symlinks, so |
| 19 |
use the symlinks in /etc/fstab has no advantage over the tags. |
| 20 |
For more details see libblkid(3). |
| 21 |
-->8-- |
| 22 |
|
| 23 |
Oops. Let's look further: |
| 24 |
|
| 25 |
--8<-- libblkid(3) |
| 26 |
The high-level part of the library supports two methods to evaluate |
| 27 |
LABEL/UUID. It reads information directly from a block device or read |
| 28 |
information from /dev/disk/by-* udev symlinks. The udev is preferred |
| 29 |
method by default. |
| 30 |
-->8-- |
| 31 |
|
| 32 |
..so when is the non-default method (querying devices) used? |
| 33 |
|
| 34 |
|
| 35 |
//Peter |
Archives