From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: New Exherbo+musl stage: x86_64-pc-linux-musl-20160621
Date: Wed, 22 Jun 2016 12:37:01 -0400 [thread overview]
Message-ID: <20160622163700.GQ10893@brightrain.aerifal.cx> (raw)
In-Reply-To: <20160622122030.61bfcd2b@rafaela>
On Wed, Jun 22, 2016 at 12:20:30PM -0300, Matias A. Fonzo wrote:
> El Wed, 22 Jun 2016 14:01:17 +0200
> Shiz <hi@shiz.me> escribió:
> > > On 22 Jun 2016, at 01:22, Matias A. Fonzo <selk@dragora.org> wrote:
> > >
> > >> The latest musl stage can always be found at:
> > >> https://www.somasis.com/stages/exherbo-x86_64-pc-linux-musl-current.tar.xz
> > >
> > > Please, consider switching to another format, like lzip/clzip. See:
> > >
> > > http://www.nongnu.org/lzip/xz_inadequate.html
> >
> > Switching to a format almost nobody has a decompressor for,
> > especially for something like a stage3 that is often extracted in a
> > live environment with no options to extra install packages, doesn’t
> > seem like a good idea.
> >
> > - Shiz
>
> Distribute files and impose to your users in having xz, is a bad idea.
Decompressing xz is supported by busybox and internally by busybox tar
and gnu tar, so I don't see any practical risk of the user not having
support. On the other hand, nobody has ever heard of lzip or clzip and
they're certainly not supported in the widely available tools.
For a compression format (from the perspective of the party doing the
decompression), the only technical details that are relevant are the
compression ratios and the memory and time requirements for
decompressing.
Rich
next prev parent reply other threads:[~2016-06-22 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 22:26 Kylie McClain
2016-06-21 23:22 ` Matias A. Fonzo
2016-06-22 12:01 ` Shiz
2016-06-22 15:20 ` Matias A. Fonzo
2016-06-22 15:32 ` Shiz
2016-06-22 15:57 ` Matias A. Fonzo
2016-06-22 15:59 ` Luca Barbato
2016-06-22 16:45 ` Rich Felker
2016-06-22 16:37 ` Rich Felker [this message]
2016-06-22 17:13 ` Matias A. Fonzo
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=20160622163700.GQ10893@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).