unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Leo Famulari <leo@famulari.name>, Alexandre Oliva <lxoliva@fsfla.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: ISO image: to xz or not to xz?
Date: Mon, 03 May 2021 10:30:03 -0700	[thread overview]
Message-ID: <87bl9ru3ms.fsf@yucca> (raw)
In-Reply-To: <YJAt6WCncCd5wd/Y@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

On 2021-05-03, Leo Famulari wrote:
> On Mon, May 03, 2021 at 01:47:02PM -0300, Alexandre Oliva wrote:
>> Indeed, install ISOs normally hold already-compressed filesystems or
>> files, so recompressing the .iso doesn't gain much if at all.
>
> To quote the introductory message of this thread:
>
> "The xz-compressed image is 23% smaller, which is not negligible."

Well, the suggestion to use squashfs does bear merit; it would require
having some type of writeable filesystem on top, such as using overlay
fs to mount the installer rootfs with squashfs for the readonly bits,
and tmpfs for the writeable bits.

As a bonus, using a tmpfs overlay would solve the issue brought up
recently by someone who tried using the same installer image multiple
times, and /gnu/store and /var/guix got out of sync due to the cow-store
only writing to the newly installed system, so that the second install
failed.

Another angle might be to use a compressable but writeable filesystem
(btrfs?).

Obviously, it requires someone to do the work to get there!


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2021-05-03 17:55 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 [this message]
2021-05-03 19:12       ` Tobias Geerinckx-Rice
2021-05-03 19:57         ` Vagrant Cascadian
2021-05-03 17:41   ` Tobias Geerinckx-Rice

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=87bl9ru3ms.fsf@yucca \
    --to=vagrant@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --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).