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: <4B75A5FE.8020408@zytor.com>
Date:	Fri, 12 Feb 2010 11:03:26 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jean Delvare <khali@...ux-fr.org>
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 users] XZ Migration discussion

On 02/12/2010 06:01 AM, Jean Delvare wrote:
> 1* Keep a single compression format. This saves almost 40% of the
> files.
> 
> 2* Move one of the compression formats somewhere else, so that it
> doesn't get in the way but is still available if needed.

Neither of these are feasible, sorry.

> 3* Create a new subdirectory for every 2.6.x kernel, and move all the
> related files there. This would shrink the main index drastically, and
> each subdirectory would have a reasonable size (except maybe 2.6.16 and
> 2.6.27.) Oddly enough this has been done for the files under testing/
> already, so I am curious why we don't do it for the release files (and
> the testing/incr/ files, while we're at it.)

Well, part of the reason why is that we're functionally "stuck" on 2.6;
a prefix which really has lost all meaning.

It might open up the question if we shouldn't just do a Solaris and drop
the leading 2 (so the next kernel would be 6.33) or call the kernel
after that 3.0 instead of 2.6.34, and then 3.1 instead of 2.6.35.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ