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: <20100214103226.64736ce5@hyperion.delvare>
Date:	Sun, 14 Feb 2010 10:32:26 +0100
From:	Jean Delvare <khali@...ux-fr.org>
To:	Phillip Lougher <phillip@...gher.demon.co.uk>
Cc:	"FTPAdmin Kernel.org" <ftpadmin@...nel.org>,
	lasse.collin@...aani.org, mirrors@...nel.org,
	linux-kernel <linux-kernel@...r.kernel.org>, users@...nel.org
Subject: Re: [kernel.org users] XZ Migration discussion

Hi Phillip,

On Sat, 13 Feb 2010 22:37:41 +0000, Phillip Lougher wrote:
> Embedded and enterprise distro users are usually stuck on ancient kernels that
> were downloaded from kernel.org and patched *years ago*.  The reason they're
> stuck on them is due to local modifications, and so they're not going to be
> downloading ancient vanilla kernels from kernel.org now.

They perfectly could. This is exactly what we're doing at Suse and I can
easily imagine other companies follow the same model. We store our
local changes as patches on top of the old kernel version. When a new
developer joins the team and needs to setup a working tree, our setup
script gets the patches from our internal repository, fetches the
relevant kernel tarball from kernel.org, unpacks it and applies all the
patches.

This is one of the reasons why others have been claiming in this
discussion: it would be weird if files which were previously available
would suddenly disappear. We can discuss the cost and benefits of any
change done to the tree structure, compression formats etc. but please
do not assume that nobody is downloading the old files from kernel.org.

Personally I wouldn't mind at all if old files would disappear and our
tools have to be adjusted accordingly, as long as it happens only once
in a long while and not on a regular basis by (broken) design.

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