[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
03/03: doc: Clarify the form of UUIDs we expect.
|
From: |
Ludovic Courtès |
|
Subject: |
03/03: doc: Clarify the form of UUIDs we expect. |
|
Date: |
Thu, 25 Feb 2016 18:34:00 +0000 |
civodul pushed a commit to branch master
in repository guix.
commit 0767f6a69e96185a9a8c6377ac946037b966d4c7
Author: Ludovic Courtès <address@hidden>
Date: Thu Feb 25 19:29:21 2016 +0100
doc: Clarify the form of UUIDs we expect.
Fixes <http://bugs.gnu.org/22797>.
Reported by Alex Kost <address@hidden>.
* doc/guix.texi (File Systems): Clarify which UUIDs we're talking
about.
---
doc/guix.texi | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/doc/guix.texi b/doc/guix.texi
index 2bebeed..004e50c 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
address@hidden -l} command) using the @code{uuid} form, like this:
address@hidden -l} command) using the @code{uuid} address@hidden
address@hidden form expects 16-byte UUIDs as defined in
address@hidden://tools.ietf.org/html/rfc4122, address@hidden 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