| 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
| ||
|
Message-ID: <20070918203530.GC27836@uranus.ravnborg.org> Date: Tue, 18 Sep 2007 22:35:30 +0200 From: Sam Ravnborg <sam@...nborg.org> To: David Miller <davem@...emloft.net> Cc: hpa@...or.com, mchan@...adcom.com, vda.linux@...glemail.com, linux-kernel@...r.kernel.org, netdev@...r.kernel.org Subject: Re: bnx2 dirver's firmware images On Tue, Sep 18, 2007 at 01:08:10PM -0700, David Miller wrote: > From: "H. Peter Anvin" <hpa@...or.com> > Date: Tue, 18 Sep 2007 12:27:04 -0700 > > > Well, what I was referring to here, of course, was the initramfs > > integrated in the kernel image, so it all comes out of the kernel build > > tree and produces a single bootable image. The fact that part of it > > contains userspace code is in that way invisible. > > > > That was kind of the point here, and the only reason for pushing klibc > > into the kernel build tree at all. Under the "distros use external > > initrd anyway" school of thought, whatever libc used for that can be > > external anyway. > > Sounds good to me :) Except there seems to be great resistance to include userland code in the kernel as demonstrated at last KS. Or this is maybe just a single vocal person and the topic were brought up late? Anyway - if we again consider klibc I will do my best to make the build stuff as smooth as possible. Sam - 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