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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 22797 in the body.
You can then email your comments to 22797 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

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 #10 received at 22797-done <at> debbugs.gnu.org (full text, mbox):

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 1 (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 2 (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 3 (text/plain, inline)]

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

Thanks,
Ludo’.

Message #13 received at 22797-done <at> debbugs.gnu.org (full text, mbox):

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

Ludovic Courtès (2016-02-25 21:32 +0300) wrote:

> 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:

Ah, actually I thought it's expected as this is not a "normal" UUID.
Thanks for the clarification.

-- 
Alex

Previous Next

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