public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "William Hubbs" <williamh@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/baselayout:master commit in: share.Linux/
Date: Thu, 25 Aug 2016 19:09:47 +0000 (UTC)	[thread overview]
Message-ID: <1472151444.89621f070195cab17d2f4ee6f7ac084946bba02a.williamh@gentoo> (raw)

commit:     89621f070195cab17d2f4ee6f7ac084946bba02a
Author:     Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Thu Aug 25 16:21:05 2016 +0000
Commit:     William Hubbs <williamh <AT> gentoo <DOT> org>
CommitDate: Thu Aug 25 18:57:24 2016 +0000
URL:        https://gitweb.gentoo.org/proj/baselayout.git/commit/?id=89621f07

share.Linux/fstab: update advice regarding labels and UUIDS

 share.Linux/fstab | 14 ++++++--------
 1 file changed, 6 insertions(+), 8 deletions(-)

diff --git a/share.Linux/fstab b/share.Linux/fstab
index 4c2782e..62dd22e 100644
--- a/share.Linux/fstab
+++ b/share.Linux/fstab
@@ -18,14 +18,12 @@
 # NOTE: Even though we list ext4 as the type here, it will work with ext2/ext3
 #       filesystems.  This just tells the kernel to use the ext4 driver.
 #
-# NOTE: You can use full paths to devices like /dev/sda3, but nowadays it is
-#       recommended to set labels in the filesystem and mount via that.  All
-#       modern Linux filesystems should support this functionality.  If your
-#       boot partition is /dev/sda1 and is ext4, you can set the label of it
-#       to "boot" by running:
-#         # e2label /dev/sda1 boot
-#       Then the LABEL example below will work for you.
+# NOTE: You can use full paths to devices like /dev/sda3, but it is often
+#       more reliable to use filesystem labels or UUIDs. See your filesystem
+#       documentation for details on setting a label. To obtain the UUID, use
+#       the blkid(8) command.
+
 #LABEL=boot		/boot		ext4		noauto,noatime	1 2
-#LABEL=root		/		ext4		noatime		0 1
+#UUID=58e72203-57d1-4497-81ad-97655bd56494		/		ext4		noatime		0 1
 #LABEL=swap		none		swap		sw		0 0
 #/dev/cdrom		/mnt/cdrom	auto		noauto,ro	0 0


             reply	other threads:[~2016-08-25 19:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 19:09 William Hubbs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-08-28 16:19 [gentoo-commits] proj/baselayout:master commit in: share.Linux/ William Hubbs
2016-08-26 16:53 William Hubbs
2015-09-10 14:54 William Hubbs
2015-01-07  2:24 William Hubbs
2015-01-07  2:24 William Hubbs
2014-08-07  3:35 William Hubbs

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=1472151444.89621f070195cab17d2f4ee6f7ac084946bba02a.williamh@gentoo \
    --to=williamh@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@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