summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2016-02-25 19:29:21 +0100
committerLudovic Courtès <ludo@gnu.org>2016-02-25 19:29:21 +0100
commit0767f6a69e96185a9a8c6377ac946037b966d4c7 (patch)
tree1ebd3229f1e83897209bc440e7dde2a26b9b3ccd
parenta4e7083da32395dd434970725df0bc15601d202a (diff)
doc: Clarify the form of UUIDs we expect.
Fixes <http://bugs.gnu.org/22797>. Reported by Alex Kost <alezost@gmail.com>. * doc/guix.texi (File Systems): Clarify which UUIDs we're talking about.
-rw-r--r--doc/guix.texi7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/guix.texi b/doc/guix.texi
index 2bebeeddf7..004e50c86b 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -6302,7 +6302,12 @@ is interpreted as a partition label name; when it is @code{uuid},
@code{device} is interpreted as a partition unique identifier (UUID).
UUIDs may be converted from their string representation (as shown by the
-@command{tune2fs -l} command) using the @code{uuid} form, like this:
+@command{tune2fs -l} command) using the @code{uuid} form@footnote{The
+@code{uuid} form expects 16-byte UUIDs as defined in
+@uref{https://tools.ietf.org/html/rfc4122, RFC@tie{}4122}. This is the
+form of UUID used by the ext2 family of file systems and others, but it
+is different from ``UUIDs'' found in FAT file systems, for instance.},
+like this:
@example
(file-system