From: ng0 <contact.ng0@cryptolab.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: GuixSD bootable ISO-9669 image
Date: Tue, 2 May 2017 12:53:02 +0000 [thread overview]
Message-ID: <20170502125302.kczt4pflooesikx4@abyayala> (raw)
In-Reply-To: <87efw7igen.fsf@gnu.org>
Ludovic Courtès transcribed 5.2K bytes:
> Hi!
>
> I just tested your patch, Danny (last version attached): I took the
> image at
> <http://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-8.7.1-amd64-netinst.iso>
> and then did:
>
> --8<---------------cut here---------------start------------->8---
> scheme@(guile-user)> ,m (gnu build file-systems)
> scheme@(gnu build file-systems)> (define sb (read-iso9660-superblock "/tmp/debian-8.7.1-amd64-netinst.iso.part"))
> scheme@(gnu build file-systems)> (iso9660-superblock-volume-name sb)
> $2 = "Debian 8.7.1 amd64 1"
> scheme@(gnu build file-systems)> (iso9660-superblock-uuid sb)
> $3 = #vu8(50 48 49 55 48 49 49 54 49 49 48 49 48 49 48 48 0)
> scheme@(gnu build file-systems)> (bytevector-length $3)
> $4 = 17
> scheme@(gnu build file-systems)> (uuid->string $3)
> $5 = "32303137-3031-3136-3131-303130313030"
> --8<---------------cut here---------------end--------------->8---
>
> Seems to work!
>
> 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))
>
> ;; FIXME make result human-readable (See grub).
> ;(define (iso9660-uuid->string uuid)
> --8<---------------cut here---------------end--------------->8---
>
> Should ‘iso9660-uuid->string’ be different from ‘uuid->string’?
>
> Anyway, I think we should polish and commit real soon. :-) Perhaps we
> can add a note about endianness and assume little endian for now.
Excuse me if I didn't pay much attention to the thread, I just flipped
through all of it. Isn't that (little endian) the most common assumption
most operation system have? I know that Gentoo defaults to little endian.
https://packages.gentoo.org/useflags/search?q=big-endian
And we don't support SuperH or similar Big Endian hardware. Or am I
thinking about different reasons why the endianness here matters?
> Thank you Danny!
>
> Ludo’.
>
--
https://pragmatique.xyz
PGP: https://people.pragmatique.xyz/ng0/
next prev parent reply other threads:[~2017-05-02 12:53 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 [this message]
2017-05-03 6:26 ` Mark H Weaver
2017-05-02 20:09 ` Danny Milosavljevic
2017-05-02 21:11 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170502125302.kczt4pflooesikx4@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.