unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: GuixSD bootable ISO-9669 image
Date: Tue, 02 May 2017 23:11:05 +0200	[thread overview]
Message-ID: <871ss72cd2.fsf@gnu.org> (raw)
In-Reply-To: <20170502220904.3f27ce9f@scratchpost.org> (Danny Milosavljevic's message of "Tue, 2 May 2017 22:09:04 +0200")

Heya,

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> On Tue, 02 May 2017 14:37:04 +0200
> ludo@gnu.org (Ludovic Courtès) wrote:
>
>> Seems to work!
>
> Nice :)
>
>> Could you clarify the two “See grub” in here:
>> 
>> --8<---------------cut here---------------start------------->8---
>> (define (iso9660-superblock-uuid sblock)
>>   "Return the Volume ID of a iso9660 superblock SBLOCK as a 4-byte bytevector."
>>   ;; Note: The field is the volume creation time.
>>   ;; FIXME Use only certain parts (See grub).
>>   ;; FIXME treat "all 0" as invalid.
>>   (sub-bytevector sblock 813 17))
>
> Yeah.  If you check out grub, /dev/disk/by-uuid or blkid, you can see that for ISO9660 filesystems, it prints the "uuids" differently (because they are not uuids, they are timestamps...).

OK.  Are these “UUIDs” 160-bit long like the “real” ones?  If they are,
I’d suggest ignoring the problem for now.

>> Should ‘iso9660-uuid->string’ be different from ‘uuid->string’?
>
> From a purity standpoint I'd say no.  From a compatibility standpoint, yes.

Makes sense.

>> Anyway, I think we should polish and commit real soon.  :-)  Perhaps we
>> can add a note about endianness and assume little endian for now.
>
> Turns out that for the parts that we need we don't care about the endianness either way.  So I dropped the endianness now.

Cool.

Thanks,
Ludo’.

  reply	other threads:[~2017-05-02 21:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 14:17 GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements] ng0
2017-04-18 15:16 ` Chris Marusich
2017-04-19 20:59   ` Ludovic Courtès
2017-04-23  4:52     ` Chris Marusich
2017-04-24  5:11       ` GuixSD bootable ISO-9669 image (was: Re: GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements]) Chris Marusich
2017-04-27 13:42         ` GuixSD bootable ISO-9669 image Ludovic Courtès
2017-04-27 17:08         ` GuixSD bootable ISO-9669 image (was: Re: GuixSD on servers [Fwd: [rtracker.1984.is #131647] A question about VServer system specific requirements]) Danny Milosavljevic
2017-04-27 20:00           ` Danny Milosavljevic
2017-04-28  8:18             ` Danny Milosavljevic
2017-05-02 12:37               ` GuixSD bootable ISO-9669 image Ludovic Courtès
2017-05-02 12:53                 ` ng0
2017-05-03  6:26                   ` Mark H Weaver
2017-05-02 20:09                 ` Danny Milosavljevic
2017-05-02 21:11                   ` Ludovic Courtès [this message]
2017-05-07 19:37                     ` Danny Milosavljevic
2017-05-08 14:14                       ` Ludovic Courtès
2017-05-11 23:30                         ` Danny Milosavljevic
2017-05-12 15:33                           ` Ludovic Courtès
2017-05-14 21:25                             ` Danny Milosavljevic
2017-05-16  8:31                               ` Ludovic Courtès
2017-06-06  9:35                                 ` Danny Milosavljevic
2017-06-08 12:25                                   ` Ludovic Courtès
2017-05-02 20:12                 ` 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=871ss72cd2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@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.
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).