linux-kernel - Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of the kernel.

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: <20080530103107.4f71cfe3@core>
Date:	Fri, 30 May 2008 10:31:07 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Jeff Garzik <jeff@...zik.org>,
	David Woodhouse <dwmw2@...radead.org>,
	ksummit-2008-discuss@...ts.linux-foundation.org,
	linux-kernel@...r.kernel.org,
	James.Bottomley@...senpartnership.com,
	David Miller <davem@...emloft.net>
Subject: Re: [Ksummit-2008-discuss] RFC: Moving firmware blobs out of the
 kernel.

On Thu, 29 May 2008 16:39:48 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:

> Peter Zijlstra wrote:
> > 
> > I certainly agree, pushing more and more into initrd just annoys the
> > hell out of me.
> > 
> > I'd argue to include everything needed to build (and esp cross build) an
> > initrd into the kernel - up until that point initrds are useless.
> > 
> 
> I tried to push for that two years ago.  I'd be more than happy to pull 
> that out of the freezer.

Its kind of irrelevant if you need an initrd or not. The only question of
relevance is "does it get built when I type make all". Almost all Linux
users are using initrd without problem - because their distro ensures
"make install" and the packaged kernels do the right thing.

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