From: ng0 <ng0@n0.is>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Iso image size
Date: Fri, 8 Dec 2017 08:37:44 +0000 [thread overview]
Message-ID: <20171208083744.tstydd574siv5ik4@abyayala> (raw)
In-Reply-To: <CAE4v=pgSUoawnq=Q=vmKqG7oqWoNpYVjWZ1PzAt=p1XtUTYEsg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
Gábor Boskovits transcribed 1.3K bytes:
> I don't know what we are currently doing to get the installer iso image
> sized down, but I caught some discussion yesterday on irc, that the image
> is actually very well compressible, and checking the sizes it really is.
>
> Might that be possible to do something like compressing the root filesystem
> image on the iso image, and decompress it from initrd before mounting?
>
> Or do we already do that?
>
> It might worth consideration, if that makes the image fit onto a CD.
Are there any reasons why we should really consider CDs a target
in 2017-almost-2018?
I threw away around 500 CDs + 100 floppy disks with backup data of the
last 20 years quiet recently (and only kept originals).
All I'm getting here (West Germany) are BluRays and similar opticals.
And I predict that even this will go away in the near future.
So why focus on the artifical size of optical disks, especially a
format that has been considered old by most if not all other distros
above the size of tiny distros?
If this may sound like harsh criticism: I'm only curious.
--
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://c.n0.is/ng0_pubkeys/tree/keys
WWW: https://n0.is
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-12-08 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 7:06 Iso image size Gábor Boskovits
2017-12-08 8:37 ` ng0 [this message]
2017-12-08 9:07 ` ng0
2017-12-08 9:14 ` Manolis Ragkousis
2017-12-08 9:34 ` ng0
2017-12-11 9:23 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171208083744.tstydd574siv5ik4@abyayala \
--to=ng0@n0.is \
--cc=boskovits@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.