* bug#22797: Using UUID for vfat file system is impossible
@ 2016-02-24 19:32 Alex Kost
2016-02-25 18:32 ` Ludovic Courtès
0 siblings, 1 reply; 3+ messages in thread
From: Alex Kost @ 2016-02-24 19:32 UTC (permalink / raw)
To: 22797
Hello, unlike other file system types, FAT volumes have short UUIDs,
for example: "58D7-4FA5", but such an UUID cannot be used in an
operating system declaration:
(file-system
(device (uuid "58D7-4FA5"))
(title 'uuid)
(type "vfat")
;; ...
)
because (uuid "58D7-4FA5") errors.
--
Alex
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#22797: Using UUID for vfat file system is impossible
2016-02-24 19:32 bug#22797: Using UUID for vfat file system is impossible Alex Kost
@ 2016-02-25 18:32 ` Ludovic Courtès
2016-02-25 19:50 ` Alex Kost
0 siblings, 1 reply; 3+ messages in thread
From: Ludovic Courtès @ 2016-02-25 18:32 UTC (permalink / raw)
To: Alex Kost; +Cc: 22797-done
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
Alex Kost <alezost@gmail.com> skribis:
> Hello, unlike other file system types, FAT volumes have short UUIDs,
> for example: "58D7-4FA5", but such an UUID cannot be used in an
> operating system declaration:
>
> (file-system
> (device (uuid "58D7-4FA5"))
> (title 'uuid)
> (type "vfat")
> ;; ...
> )
>
> because (uuid "58D7-4FA5") errors.
That’s expected. :-) I’ve clarified this in 0767f6a:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 663 bytes --]
@@ -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:
[-- Attachment #3: Type: text/plain, Size: 141 bytes --]
When we implement FAT UUIDs, we’ll either adjust the ‘uuid’ form or
introduce a separate ‘fat-uuid’ form.
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 3+ messages in thread* bug#22797: Using UUID for vfat file system is impossible
2016-02-25 18:32 ` Ludovic Courtès
@ 2016-02-25 19:50 ` Alex Kost
0 siblings, 0 replies; 3+ messages in thread
From: Alex Kost @ 2016-02-25 19:50 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: 22797-done
Ludovic Courtès (2016-02-25 21:32 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> Hello, unlike other file system types, FAT volumes have short UUIDs,
>> for example: "58D7-4FA5", but such an UUID cannot be used in an
>> operating system declaration:
>>
>> (file-system
>> (device (uuid "58D7-4FA5"))
>> (title 'uuid)
>> (type "vfat")
>> ;; ...
>> )
>>
>> because (uuid "58D7-4FA5") errors.
>
> That’s expected. :-) I’ve clarified this in 0767f6a:
Ah, actually I thought it's expected as this is not a "normal" UUID.
Thanks for the clarification.
--
Alex
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-02-25 19:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-24 19:32 bug#22797: Using UUID for vfat file system is impossible Alex Kost
2016-02-25 18:32 ` Ludovic Courtès
2016-02-25 19:50 ` Alex Kost
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).