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: ISO-9660 image working and ready
Date: Wed, 12 Jul 2017 23:20:26 +0200	[thread overview]
Message-ID: <87fue1bbdx.fsf@gnu.org> (raw)
In-Reply-To: <20170712192827.22b7c740@scratchpost.org> (Danny Milosavljevic's message of "Wed, 12 Jul 2017 19:28:27 +0200")

Hey hey!

(This is a followup to <https://bugs.gnu.org/27661>.)

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> If we want we can (in the future) provide only the iso9660 image on the homepage (for x86_64).
>
> 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?

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.)

> (Usually, ARM systems have a more involved boot process and will not work, neither from SD card nor from CD-ROM - and booting from USB flash drive is out of the question).
>
> Of course it would be nice if people could test the iso9660 image a bit (especially on UEFI systems of which I have none).
>
> To generate one, for example do this:
>
> guix system disk-image -t iso9660 foo.scm # will print the name of the directory that contains "guixsd.iso" in the end.

I’ve just built:

  ./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/

The image has this 2KiB /boot.catalog file; is that expected?

Otherwise the file names look alright as if Joliet extensions were used,
but maybe they are?  “guix gc --verify=contents” in the image is happy
(and surprisingly fast).

Anyway awesome work, and a great milestone.  Many users who had been
complaining about the lack of ISOs will thank you!  :-)

Ludo’.

       reply	other threads:[~2017-07-12 21:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87d195etic.fsf@gnu.org>
     [not found] ` <20170712134405.25274-1-dannym@scratchpost.org>
     [not found]   ` <87inixd9z1.fsf@gnu.org>
     [not found]     ` <20170712192827.22b7c740@scratchpost.org>
2017-07-12 21:20       ` Ludovic Courtès [this message]
2017-07-12 22:57         ` ISO-9660 image working and ready Danny Milosavljevic
2017-07-13  7:52           ` Ricardo Wurmus
2017-07-17 13:41           ` Ludovic Courtès
2017-07-17 17:54             ` Danny Milosavljevic
2017-07-17 18:30               ` Adam Van Ymeren
2017-07-18  2:34               ` Adam Van Ymeren
2017-07-18 10:06               ` Ludovic Courtès

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=87fue1bbdx.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).