From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Alexandre Oliva <lxoliva@fsfla.org>
Cc: guix-devel@gnu.org
Subject: Re: ISO image: to xz or not to xz?
Date: Mon, 03 May 2021 19:41:14 +0200 [thread overview]
Message-ID: <877dkf4sw5.fsf@nckx> (raw)
In-Reply-To: <oreeenix2x.fsf@lxoliva.fsfla.org>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
Alexandre Oliva 写道：
> Consider using something like a loopback-mounted squashfs for
> the bulk
> of the data in the install media for a future release.
Read <https://issues.guix.gnu.org/40514>.
I did play with the obvious alternative, but got so bored --
squashfs is no forgotten 1990s Linux-only extension to iso9660! --
that saving a mere 20% more was not worth it.
By this I hope to trick you into thinking it is, and submitting a
patch, because to do so you'd have to fix one of the Forever Bugs
that *is* worth fixing: separate /boot support. :-)
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2021-05-03 17:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 20:18 ISO image: to xz or not to xz? Ludovic Courtès
2021-04-28 20:39 ` Vincent Legoll
2021-04-28 20:41 ` Simon Josefsson via Development of GNU Guix and the GNU System distribution.
2021-05-02 21:16 ` [PATCH] maint: Do not xz-compress ISO images Ludovic Courtès
2021-05-03 0:15 ` [bug#48173] " Julien Lepiller
2021-05-03 7:50 ` François
2021-05-03 15:39 ` bug#48173: " Ludovic Courtès
2021-05-03 16:35 ` Julien Lepiller
2021-05-04 3:35 ` Maxim Cournoyer
2021-05-03 15:54 ` Ludovic Courtès
2021-04-28 21:16 ` ISO image: to xz or not to xz? Christopher Baines
2021-04-28 21:18 ` Leo Famulari
2021-05-03 16:47 ` Alexandre Oliva
2021-05-03 17:07 ` Leo Famulari
2021-05-03 17:30 ` Vagrant Cascadian
2021-05-03 19:12 ` Tobias Geerinckx-Rice
2021-05-03 19:57 ` Vagrant Cascadian
2021-05-03 17:41 ` Tobias Geerinckx-Rice [this message]
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=877dkf4sw5.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=lxoliva@fsfla.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).