linux-kernel - XZ Migration discussion

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-next>] [day] [month] [year] [list]

Message-ID: <4B744E13.8040004@kernel.org>
Date:	Thu, 11 Feb 2010 10:36:03 -0800
From:	"J.H." <warthog9@...nel.org>
To:	linux-kernel <linux-kernel@...r.kernel.org>, mirrors@...nel.org,
	users@...nel.org
CC:	lasse.collin@...aani.org,
	"FTPAdmin Kernel.org" <ftpadmin@...nel.org>
Subject: XZ Migration discussion

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey Everyone,

So as the subject states this is more a centralized discussion on
migration plans to using and providing xz for content on kernel.org.
Currently we provide gz and bz2, with gz acting as the original content
and kernel.org itself generating the resulting bz2 files.  There are a
couple of possible proposals and wanted to toss them out there, and get
feedback from everyone: the kernel community, the mirrors of kernel.org
and the direct users of kernel.org.

========================================================================

Option 1)

Leave gz as the master, and migrate bz2 to xz.  This will happen in
stages obviously. with bz2 ultimately being phased out.

	Migration option 1)

		All new content would be provided in .bz2 and .xz with
		an ultimate date set that the .bz2 files would stop
		being generated with new content.  This would leave all
		existing content alone and it would not be a migration
		of the current .bz2 files to xz

	Migration option 2)

		At some point there would be a mass conversion of all
		existing content to include .bz2 and .xz.  These would
		be run in parallel for a time period until it was
		determined that .bz2 was no longer needed and it would
		be removed from the servers leaving .gz and .xz

Option 2)

Convert the master data from gz to bz2 and use xz as the new file
format.  This has the downside of causing more tool churn as it means
the kernel developers will have to eventually convert from gz to bz2,
which means for a time there will be nag e-mails if you upload gz
instead of bz2 and such.  It would also mean that we (kernel.org) would
need to be able to support .gz and .bz2 as master data for a time.

Migration options are identical to Option 1 more or less, with either
just new content getting converted, or all content getting converted.

========================================================================

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.

So I'm inviting discussion, questions and comments on this so we know
which way to ultimately go.

- - John 'Warthog9' Hawley
Chief Kernel.org Administrator
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkt0ThMACgkQ/E3kyWU9dicQIwCggCACEHuEViVvnIiv42McbCQh
SmUAn049beEHPucEc7X+0hBQkW6A5oTt
=ugaX
-----END PGP SIGNATURE-----
--
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/