unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: [PATCH 1/1] doc: Explain significance of partition labels.
Date: Sat, 19 Dec 2015 22:00:50 -0500	[thread overview]
Message-ID: <cdfaa2c4f29b1ecc061af6c4e10049188766eb9d.1450580065.git.leo@famulari.name> (raw)
In-Reply-To: <cover.1450580065.git.leo@famulari.name>
In-Reply-To: <cover.1450580065.git.leo@famulari.name>

* doc/guix.texi (Preparing for Installation): Point out relationship
between partition labels and the file-system configuration.
---
 doc/guix.texi | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/doc/guix.texi b/doc/guix.texi
index 06d70ba..53a5fd3 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -5456,6 +5456,13 @@ reliably refer to them in @code{file-system} declarations (@pxref{File
 Systems}).  This is typically done using the @code{-L} option of
 @command{mkfs.ext4} and related commands.
 
+Be sure that your partition labels match the value of their respective
+@code{device} fields in your @code{file-system} configuration, if your
+@code{file-system} configuration sets the value of @code{title} to
+"label", as do the example configurations found on the USB installation
+image under @code{/etc/configuration} (@pxref{Using the Configuration
+System}).
+
 @c FIXME: Uncomment this once GRUB fully supports encrypted roots.
 @c A typical command sequence may be:
 @c
-- 
2.6.2

  reply	other threads:[~2015-12-20  3:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20  3:00 [PATCH 0/1] Add some notes about setting up GuixSD filesystems Leo Famulari
2015-12-20  3:00 ` Leo Famulari [this message]
2015-12-20 22:16   ` [PATCH 1/1] doc: Explain significance of partition labels Ludovic Courtès
2015-12-21  4:29     ` Leo Famulari

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=cdfaa2c4f29b1ecc061af6c4e10049188766eb9d.1450580065.git.leo@famulari.name \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).