From: Rik van Riel <riel@redhat.com>
To: Al Boldi <a1426z@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch for Documentation/initrd.txt?
Date: Thu, 27 Jul 2006 16:19:56 -0400 [thread overview]
Message-ID: <44C91FEC.1020309@redhat.com> (raw)
In-Reply-To: <200607272026.57695.a1426z@gawab.com>
Al Boldi wrote:
> Tom Horsley wrote:
>> +Compressed cpio images
> 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?
That is exactly what Tom describes, except it is called initramfs
and goes into ramfs - which is mostly the same as tmpfs.
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
next prev parent reply other threads:[~2006-07-27 20:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 17:26 patch for Documentation/initrd.txt? Al Boldi
2006-07-27 18:52 ` H. Peter Anvin
2006-07-27 20:35 ` Al Boldi
2006-07-27 20:38 ` H. Peter Anvin
2006-07-28 13:58 ` Al Boldi
2006-07-27 20:19 ` Rik van Riel [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-27 13:17 Tom Horsley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44C91FEC.1020309@redhat.com \
--to=riel@redhat.com \
--cc=a1426z@gawab.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox