| 1 |
On 02/09/2011 12:05 PM, Elaine C. Sharpe wrote: |
| 2 |
|
| 3 |
> I'm a little confused about use of the term "disk labels" in |
| 4 |
> this discussion. Isn't a disk label a fs level ID (I create |
| 5 |
> those when I make my fs)? Using UUID in fstab for quite awhile |
| 6 |
> here (due to multiple external drives), but those aren't disk |
| 7 |
> labels... are they? |
| 8 |
|
| 9 |
Correct, they are two different (but equivalent) ways of naming |
| 10 |
a filesystem (partition) for use in fstab. |
| 11 |
|
| 12 |
mkfs generates a UUID automatically when the fs is created, but |
| 13 |
it does *not* generate a "label" unless you give it one using the |
| 14 |
-L flag, or create one later using e2fslabel or some other utility. |
| 15 |
|
| 16 |
The syntax in fstab is either UUID=<foo> or LABEL=<bar>, but the |
| 17 |
idea is exactly the same. The whole point is to divorce the fs |
| 18 |
from the /dev/xxxx it happens to reside on at boot time. |
Archives