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]

Date:	Fri, 30 May 2008 16:14:47 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
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.

Alan Cox wrote:
>>>
>> 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.
> 

Obviously.  I'm equally obviously referring to klibc, which was designed 
so that the resulting vmlinux/bzImage/... file contains the necessary 
initramfs, regardless of issues like cross-compilation, draconian size 
restrictions(*), and so forth.

	-hpa

(*) Not saying that a klibc-based initramfs is necessarily smaller than 
the in-kernel code it replaces, but the total size is << than the size 
of the kernel proper, which isn't true when using a full-featured libc.
--
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/