linux-kernel - Re: patch for Documentation/initrd.txt?

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:	Thu, 27 Jul 2006 13:38:35 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Al Boldi <a1426z@...ab.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: patch for Documentation/initrd.txt?

Al Boldi wrote:
> H. Peter Anvin wrote:
>> Al Boldi wrote:
>>> Thanks for your very useful docPatch!
>>>
>>> OT, but your docPatch made me think of another way to init the kernel;
>>> via tmpfs, i.e. initTmpFS.
>>>
>>> Can anybody see how that could be useful?
>> Useful, yes, but this has turned out to be fairly complex.
> 
> Sounds like somebody tried this before?
> 

Several people, yes.

>> tmpfs needs
>> a *LOT* more of the system to be fully operational than ramfs, and the
>> rootfs is initialized very early on, since one of its purposes is to
>> eliminate special cases.
> 
> So would it be possible to remap rootfs from ramfs to tmpfs, once tmpfs is 
> initialized, without actually doing another cpio?

That sounds nasty.

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