public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Bug#354229 Disk Labels in Handbook
Date: Wed, 09 Feb 2011 15:20:24 -0800	[thread overview]
Message-ID: <iiv7fu$mt9$1@dough.gmane.org> (raw)
In-Reply-To: <20110209200516.GA21349@satcidananda>

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.




  reply	other threads:[~2011-02-09 23:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gkiKm-4rd-9@gated-at.bofh.it>
     [not found] ` <gkjdo-5mN-15@gated-at.bofh.it>
     [not found]   ` <gkl5v-c8-1@gated-at.bofh.it>
     [not found]     ` <gknh0-3Ri-23@gated-at.bofh.it>
2011-02-09 20:05       ` [gentoo-user] Re: Bug#354229 Disk Labels in Handbook Elaine C. Sharpe
2011-02-09 23:20         ` walt [this message]
2011-02-10 15:39           ` [gentoo-user] Re: Bug#354229 Disk & FS " james
2011-02-09 13:51 [gentoo-user] Disk " James
2011-02-09 14:16 ` Dale
2011-02-09 16:16   ` Jarry
2011-02-09 18:41     ` [gentoo-user] Re: Bug#354229 " James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='iiv7fu$mt9$1@dough.gmane.org' \
    --to=w41ter@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox