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>] [day] [month] [year] [list]
Date:	Tue, 16 Feb 2010 16:11:12 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	"Luck, Tony" <tony.luck@...el.com>
CC:	Jean Delvare <khali@...ux-fr.org>,
	"lasse.collin@...aani.org" <lasse.collin@...aani.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"mirrors@...nel.org" <mirrors@...nel.org>,
	"users@...nel.org" <users@...nel.org>,
	"FTPAdmin Kernel.org" <ftpadmin@...nel.org>
Subject: Re: [kernel.org users] XZ Migration discussion

On 02/16/2010 09:55 AM, Luck, Tony wrote:
> 
>>> How hard a requirement is this? It might be the right time to
>>> reconsider... Tony's plan may not be perfect but overall I think I like
>>> it.
>>>
>>
>> It's pretty darn hard.  It makes it particularly messy for the mirrors 
>> to ignore it.
> 
> Sometimes hard things are worth the effort though.  I would think that
> there would be considerable advantage to a mirror system that had a
> mechanism to mark entire subtrees as "archive only - no further changes".
> 

There are a couple of reasons to not do that.

a) the moment we do that, some mirrors will start purging those areas.
We have tried to keep our mirror system universally usable by keeping a
"whole mirrors only, please" policy, and it has worked really well so far.

b) it would prevent us from *ever* reorganizing those areas, as many be
required.

c) it complicates a lot of the machinery, including the bits that allow
mirrors to only carry some of the compression formats.  That includes
mirror-side configuration, which I'd really loathe to make anything more
than very simple; mirror admins want things to work as hands-off and
automatic as possible, with a minimum of setup.  Having to learn the
intricacies of each mirror target is just plain hell.

	-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