From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 28445@debbugs.gnu.org, help-guix <help-guix@gnu.org>
Subject: Re: Cannot boot GuixSD after system reconfigure
Date: Fri, 22 Sep 2017 18:41:55 +0200 [thread overview]
Message-ID: <87lgl6ptws.fsf@gnu.org> (raw)
In-Reply-To: <20170922162339.65cf2b79@scratchpost.org> (Danny Milosavljevic's message of "Fri, 22 Sep 2017 16:23:39 +0200")
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> On Fri, 22 Sep 2017 16:03:47 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> However, there’s one thing I’d like to double-check with Danny, which is
>> the word order. With this patch, I have:
>>
>> (fat32-uuid->string (string->fat32-uuid "aabb-ccdd"))
>> $7 = "CCDD-AABB"
>>
>> Danny: are you sure the most-significant 16-bit word comes last?
>
> See https://github.com/karelzak/util-linux/blob/master/libblkid/src/superblocks/vfat.c#L48
>
> blkid_probe_sprintf_uuid(pr, vol_serno, 4, "%02X%02X-%02X%02X",
> vol_serno[3], vol_serno[2], vol_serno[1], vol_serno[0]);
I see, thanks!
Roel, with commit 8a7d81a5e23c4d59fbabf2550db32d4ba5572e4b, you should
be able to write:
(uuid "abcd-1234" 'fat32)
in your config, and it should work.
Let me know if it doesn’t. :-)
Ludo’.
next prev parent reply other threads:[~2017-09-22 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 12:21 Cannot boot GuixSD after system reconfigure Roel Janssen
2017-09-21 19:04 ` Roel Janssen
2017-09-21 20:28 ` Ricardo Wurmus
2017-09-21 22:12 ` Ludovic Courtès
2017-09-22 0:24 ` bug#28445: " Roel Janssen
2017-09-22 14:03 ` Ludovic Courtès
2017-09-22 14:23 ` bug#28445: " Danny Milosavljevic
2017-09-22 16:41 ` Ludovic Courtès [this message]
2017-09-22 19:53 ` Roel Janssen
2017-09-25 7:33 ` Ludovic Courtès
2017-09-26 19:24 ` bug#28445: " Roel Janssen
2017-09-26 2:27 ` Danny Milosavljevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgl6ptws.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28445@debbugs.gnu.org \
--cc=dannym@scratchpost.org \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).