linux-kernel - Re: [kernel.org users] 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]

Date:	Thu, 11 Feb 2010 14:22:35 -0800
From:	"H. Peter Anvin" <hpa@...nel.org>
To:	Pavel Machek <pavel@....cz>
CC:	"J.H." <warthog9@...nel.org>,
	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

On 02/11/2010 12:51 PM, Pavel Machek wrote:
> Hi!
> 
>> 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
> 
> I believe this is cleanest. gzip has performance advantages, and old
> files suddenly disappearing would be just weird.
> 

It would also be "just weird" to:

a) require that the end user knows the particular compression format
used by a particular legacy file.
b) having to have the mirror system deal with a mix of .bz2 and .xz files.

	-hpa
--
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/