| 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: <m3slb4xyrc.fsf@maximus.localdomain> Date: Fri, 13 Apr 2007 14:08:39 +0200 From: Krzysztof Halasa <khc@...waw.pl> To: Al Viro <viro@....linux.org.uk> Cc: linux-kernel@...r.kernel.org Subject: Re: RFC: initramfs unpack point and rules Al Viro <viro@....linux.org.uk> writes: > Nope. The point is to have it as early as possible, so that we had more > or less normal environment when drivers, etc. are being initialized. But traditionally the "normal environment" is a root fs not yet mounted. Do the drivers need initramfs? Which drivers? In both cases it's a bit before /sbin/init (or /init) is launched, udevd isn't running and firmware can't be loaded. OTOH when something goes wrong before console drivers are initialized, nothing can be seen. And with initramfs (especially with the external one) it's easy to screw something. -- Krzysztof Halasa - 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