Jarry <mr.jarry <at> gmail.com> writes:


> So I agree there should be at least some basic info about
> disk-labels in the handbook.

OK guys let's all chime on on the bug with
ideas and verbiage, or we just need one
really smart admin, to post some
text and we're off to the races.

Me, I still struggle with Disk labels
and UUIDs and such, so I'm looking for
leadership here..... You know one
of those smart kids or elder (older than me)
linux gentlemen types.......

Don't be shy!
bug 354229

James

In linux.gentoo.user, you wrote:
> Jarry <mr.jarry <at> gmail.com> writes:
>
>
>> So I agree there should be at least some basic info about
>> disk-labels in the handbook.
>
> OK guys let's all chime on on the bug with
> ideas and verbiage, or we just need one
> really smart admin, to post some
> text and we're off to the races.
>
> Me, I still struggle with Disk labels
> and UUIDs and such, so I'm looking for
> leadership here..... You know one
> of those smart kids or elder (older than me)
> linux gentlemen types.......
>
> Don't be shy!
> bug 354229
>
> James


I'm a little confused about use of the term "disk labels" in
this discussion. Isn't a disk label a fs level ID (I create
those when I make my fs)? Using UUID in fstab for quite awhile
here (due to multiple external drives), but those aren't disk
labels... are they?

It seems there are two subjects here, one to address in the
section of preparing disks and one for setting up fstab.

Unless of course I'm missing something, which is entirely
possible...

--
caveat utilitor
♫ � ♫ � ♫ � ♫

On 02/09/2011 12:05 PM, Elaine C. Sharpe wrote:


I'm a little confused about use of the term "disk labels" in
this discussion. Isn't a disk label a fs level ID (I create
those when I make my fs)? Using UUID in fstab for quite awhile
here (due to multiple external drives), but those aren't disk
labels... are they?


Correct, they are two different (but equivalent) ways of naming
a filesystem (partition) for use in fstab.

mkfs generates a UUID automatically when the fs is created, but
it does *not* generate a "label" unless you give it one using the
-L flag, or create one later using e2fslabel or some other utility.

The syntax in fstab is either UUID=<foo> or LABEL=<bar>, but the
idea is exactly the same. The whole point is to divorce the fs
from the /dev/xxxx it happens to reside on at boot time.