From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 58760@debbugs.gnu.org
Subject: bug#58760: Guix System iso too big for cdrom again
Date: Mon, 24 Oct 2022 20:17:35 +0200 [thread overview]
Message-ID: <87r0yxkrf7.fsf@nckx> (raw)
In-Reply-To: <87tu3tjjbc.fsf@pelzflorian.de>
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
Heyo,
pelzflorian (Florian Pelz) 写道:
> From what Tobias (Cc) wrote, he used the highest
> compression settings.
>
> So it seems nothing can be done to make the install iso smaller
Well… I used the highest compression setting *for zisofs*.
Zisofs is an ancient (and non-standard :-) little hack that Linux
supports, and it just happened to be enabled on our kernels
already. Plus it's fully transparent to the operating system.
That's why I wrote that quick little patch: it was an amusing—to
me—way to shrink our ISO basically for free.
We're the only distro that I've ever seen use it.
But we can go deeper if we choose to, by dropping zisofs and going
for something like squashfs, which achieves higher compression
through higher block sizes and better algorithms like XZ.
This is what other distributions with a compressed root file
system do.
However, it's marginally more work as you have to loop-mount the
image early during boot, and it doesn't involve obscure kernel
arcana (boo), and CDs are even more obsolete than they were when I
wrote that patch (yay), so don't wait for me to do it.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2022-10-24 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 16:08 bug#58760: Guix System iso too big for cdrom again pelzflorian (Florian Pelz)
2022-10-24 17:51 ` Csepp
2022-10-24 18:14 ` Maxime Devos
2022-10-24 18:17 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2022-11-02 15:27 ` pelzflorian (Florian Pelz)
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=87r0yxkrf7.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=58760@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=pelzflorian@pelzflorian.de \
/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).