public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: james <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Bug#354229 Disk & FS  Labels in Handbook
Date: Thu, 10 Feb 2011 15:39:22 +0000 (UTC)	[thread overview]
Message-ID: <loom.20110210T162952-896@post.gmane.org> (raw)
In-Reply-To: iiv7fu$mt9$1@dough.gmane.org

walt <w41ter <at> gmail.com> writes:


> 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.


Like I just posted in the previous thread, I think
the subject of disk labels and file system labels
*are related* and therefore a simple scheme should
be developed and explained in the handbook. All
sorts of advanced discussions, setup options and 
other related topics, like grub2 for now, should
be located in linked documents.

It's a simple subject that can easily become complicated
depending on what one intends to achieved with disks
and subsequent file systems located therein.

We have BTFRS and a host of new file systems,
not to mention CEPH and such coming down the pipe.
Those topic will need to be documented elsewhere, but,
imho, the mount point and currents explanations used
in the handbook to set up disks, partitions and file
systems, are very out-dated, again imho.

Hence this discussion, from a wide base of opinion
and experience will hopefully lead to a well written
bug report, complete with examples, so all the DOC
TEAM has to do is include it in the handbook.

All input is welcome!


James






      reply	other threads:[~2011-02-10 15:41 UTC|newest]

Thread overview: 3+ 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
2011-02-10 15:39           ` james [this message]

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=loom.20110210T162952-896@post.gmane.org \
    --to=wireless@tampabay.rr.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