From 0767f6a69e96185a9a8c6377ac946037b966d4c7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ludovic=20Court=C3=A8s?= Date: Thu, 25 Feb 2016 19:29:21 +0100 Subject: [PATCH] doc: Clarify the form of UUIDs we expect. Fixes . Reported by Alex Kost . * doc/guix.texi (File Systems): Clarify which UUIDs we're talking about. --- doc/guix.texi | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) 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