GNU bug report logs - #22797
Using UUID for vfat file system is impossible

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: tracker <at> debbugs.gnu.org
Subject: bug#22797: closed (Using UUID for vfat file system is impossible)
Date: Thu, 25 Feb 2016 18:34:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Thu, 25 Feb 2016 19:32:52 +0100
with message-id <87vb5c3ajv.fsf <at> gnu.org>
and subject line Re: bug#22797: Using UUID for vfat file system is impossible
has caused the debbugs.gnu.org bug report #22797,
regarding Using UUID for vfat file system is impossible
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
22797: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22797
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Alex Kost <alezost <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Using UUID for vfat file system is impossible
Date: Wed, 24 Feb 2016 22:32:59 +0300

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

[Message part 3 (message/rfc822, inline)]

From: ludo <at> gnu.org (Ludovic Courtès)
To: Alex Kost <alezost <at> gmail.com>
Cc: 22797-done <at> debbugs.gnu.org
Subject: Re: bug#22797: Using UUID for vfat file system is impossible
Date: Thu, 25 Feb 2016 19:32:52 +0100

[Message part 4 (text/plain, inline)]

Alex Kost <alezost <at> 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:

[Message part 5 (text/x-patch, inline)]

@@ -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 <at> footnote{The
+@code{uuid} form expects 16-byte UUIDs as defined in
+@uref{https://tools.ietf.org/html/rfc4122, RFC <at> 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:
 

[Message part 6 (text/plain, inline)]

When we implement FAT UUIDs, we’ll either adjust the ‘uuid’ form or
introduce a separate ‘fat-uuid’ form.

Thanks,
Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.