linux-kernel - Re: [kernel.org mirrors] 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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <19316.40321.624092.859225@fisica.ufpr.br>
Date:	Thu, 11 Feb 2010 22:14:57 -0200
From:	carlos@...ica.ufpr.br (Carlos Carvalho)
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"J.H." <warthog9@...nel.org>,
	"FTPAdmin Kernel.org" <ftpadmin@...nel.org>, users@...nel.org,
	lasse.collin@...aani.org,
	linux-kernel <linux-kernel@...r.kernel.org>, mirrors@...nel.org
Subject: Re: [kernel.org mirrors] XZ Migration discussion

H. Peter Anvin (hpa@...or.com) wrote on 11 February 2010 11:48:
 >On 02/11/2010 10:36 AM, J.H. wrote:
 >> 
 >> 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.
 >
 >My personal recommendation would be for Option 1, Migration option 2.

Agreed (speaking for the ftp.br.kernel.org mirror).
--
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/