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: <20100212153522.39203cfa@hyperion.delvare>
Date:	Fri, 12 Feb 2010 15:35:22 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	"H. Peter Anvin" <hpa@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Pavel Machek <pavel@....cz>, mirrors@...nel.org,
	lasse.collin@...aani.org,
	linux-kernel <linux-kernel@...r.kernel.org>, users@...nel.org,
	"FTPAdmin Kernel.org" <ftpadmin@...nel.org>
Subject: Re: [kernel.org users] XZ Migration discussion

On Thu, 11 Feb 2010 14:22:35 -0800, H. Peter Anvin wrote:
> It would also be "just weird" to:
> 
> a) require that the end user knows the particular compression format
> used by a particular legacy file.

While we're here... I think it is weird that the testing files for the
latest kernel are in testing/ directly, while the older ones have their
own subdirectory. I have a script which is greatly confused by this,
and I can imagine that other tools (for example ketchup) appreciate
this inconsistency moderately too. It is probably not ideal for mirrors
either... I don't know if the mirroring system is smart enough to deal
with file moves? If not then it generates useless traffic.

So I would like to propose that testing files are placed directly in
their final location. This would be both more consistent and easier
for everyone.

Thanks,
-- 
Jean Delvare
--
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