lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100211202201.GA31110@1wt.eu>
Date:	Thu, 11 Feb 2010 21:22:01 +0100
From:	Willy Tarreau <w@....eu>
To:	"J.H." <warthog9@...nel.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>, mirrors@...nel.org,
	users@...nel.org, "FTPAdmin Kernel.org" <ftpadmin@...nel.org>,
	lasse.collin@...aani.org
Subject: Re: [kernel.org users] XZ Migration discussion

Hi John,

On Thu, Feb 11, 2010 at 10:36:03AM -0800, J.H. wrote:
(...)
> I'm personally leaning towards option 1, though personally don't really
> have a preference on the migration options, as both obviously offer
> different advantages, and again this e-mail is more to spur on the
> discussion and come to some general consensus across all of the groups
> concerned before moving forward with a more specific plan.

I too think option 1 is better for various reasons, one of them being
that gzip is present on every platform and OS right now, while bzip2
is orders of magnitude less common. Of course on Linux we all have both
of them, but I find it important to continue to provide the sources in
a standard format. Also, on the platforms where bzip2 is not installed
by default, switching to xz should not be that hard, because either bz2
is currently not used and that changes nothing, or the users managed to
install it themselves, and they'll simply have to do the same with xz.

I don't have much preference for any of the two migration options though.

Just my 2 cents,
Willy

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ