[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ISO-9660 image working and ready
From: |
Ludovic Courtès |
Subject: |
Re: ISO-9660 image working and ready |
Date: |
Mon, 17 Jul 2017 15:41:26 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux) |
Hi Danny,
Danny Milosavljevic <address@hidden> skribis:
> On Wed, 12 Jul 2017 23:20:26 +0200
> address@hidden (Ludovic Courtès) wrote:
>
>> > It will work from CD and USB flash drive - that should cover all the
>> > options.
>>
>> Are you saying that the same image could be either dd’d to a USB key or
>> burnt on an actual CD?
>
> Yes.
Awesome!
Would you like to update the ‘release’ Makefile.am target as well as
“System Installation” in guix.texi to reflect that?
>> Are there any downsides to using ISO9660 as the file system for the
>> media, like limitations on file names or file name lengths, restrictions
>> on the type of files, etc.? (That doesn’t seem to be the case, but I
>> vaguely remember ISO9660 as having annoying limitations.)
>
> It uses the Rock Ridge extension. That means basenames are limited to 255
> characters at most, allowed are all characters except NUL and "/".
Cool.
>> ./pre-inst-env guix system disk-image -t iso9660 gnu/system/install.scm
>>
>> on v0.13.0-1321-gc96ed0091 (current master), booted it with QEMU,
>> worked fine with ‘lsblk’ showing only /dev/{fd0,sr0}. Woohoo! \o/
>
> Now try qemu ... -hda thesamefile.iso :)
Incredible. :-)
>> The image has this 2KiB /boot.catalog file; is that expected?
>
> Yeah, that's the El Torito specification for the first-stage bootloader. It
> contains what system architectures are supported and what kind of weird boot
> emulation the BIOS is supposed to use (look like a floppy drive, look like a
> hard drive, just be yourself etc).
OK.
>> Otherwise the file names look alright as if Joliet extensions were used,
>> but maybe they are?
>
> Rock Ridge :)
Oh right, Rock Ridge. Thanks for explaining!
Ludo’.