linux-kernel - Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)

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: <1360588699.7383.52.camel@shinybook.infradead.org>
Date:	Mon, 11 Feb 2013 13:18:19 +0000
From:	David Woodhouse <dwmw2@...radead.org>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Pekka Enberg <penberg@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Randy Dunlap <rdunlap@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	David Rientjes <rientjes@...gle.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Sasha Levin <levinsasha928@...il.com>,
	"H. Peter Anvin" <hpa@...or.com>, Michal Marek <mmarek@...e.cz>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: kvmtool tree (Was: Re: [patch] config: fix make kvmconfig)

On Mon, 2013-02-11 at 13:56 +0100, Ingo Molnar wrote:
> To use another, perhaps more applicable analogy:
> 
> If one has the choice to start a new business in the U.S., it 
> would be reasonable to do that. There's a lot of supporting 
> infrastructure, trust, distribution, standards, enforcement 
> agencies and available workers.
> 
> Could the same business succeed in Somalia as well? Possibly - 
> if it's a bakery or something similarly fundamental. More 
> complex businesses would likely not thrive very well there.
> 
> *That* is how I think the current Linux kernel tooling landscape 
> looks like currently in a fair number of places: in many aspects 
> it's similar to Somalia - disjunct entities with not much 
> commonality or shared infrastructure.

That's complete nonsense. If you want to use pieces of the kernel
infrastructure, then just *take* them. There are loads of projects which
use the kernel config tools, for example. There's no need to be *in* the
kernel repo.

And for code-reuse it's even easy enough to automatically extract parts
of kernel code into a separate repository. See the ecos-jffs2 and
linux-headers trees, for example, which automatically tracked Linus'
tree with a certain transformation to make them sane for just pulling
into the relevant target repositories.

-- 
dwmw2


Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (6171 bytes)