From: Mike Touloumtzis <miket@bluemug.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [CFT] initramfs patch
Date: Mon, 30 Jul 2001 13:29:57 -0700 [thread overview]
Message-ID: <20010730132957.A20284@bluemug.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0107300137550.16140-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0107300137550.16140-100000@weyl.math.psu.edu>
On Mon, Jul 30, 2001 at 02:05:55AM -0400, Alexander Viro wrote:
>
> The thing unpacks cpio archive (currently - linked into the kernel image)
> on root ramfs and execs /init. After that we are in userland code. Said
> code (source in init/init.c and init/nfsroot.c) emulates the vanilla
> 2.4 behaviour. You can replace it with your own - that's just the default
> that gives (OK, is supposed to give) a backwards-compatible behaviour.
One thing that would make embedded systems developers very happy
is the ability to map a romfs or cramfs filesystem directly from
the kernel image, avoiding the extra copy necessitated by the cpio
archive. Are there problems with this approach?
miket
next prev parent reply other threads:[~2001-07-30 20:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-30 6:05 [CFT] initramfs patch Alexander Viro
2001-07-30 16:25 ` Alon Ziv
2001-07-30 15:33 ` Keith Owens
2001-07-30 19:56 ` Anthony de Boer
2001-07-30 20:05 ` Alexander Viro
2001-07-30 20:29 ` Mike Touloumtzis [this message]
2001-07-30 20:49 ` Alexander Viro
2001-07-30 21:14 ` Mike Touloumtzis
2001-07-30 22:16 ` Bill Pringlemeir
2001-07-30 22:37 ` Mike Touloumtzis
2001-07-30 20:50 ` Jeff Garzik
2001-07-30 21:09 ` Mike Touloumtzis
2001-07-31 6:46 ` Eric W. Biederman
2001-08-11 0:27 ` David Woodhouse
2001-07-30 22:56 ` Jeff Garzik
2001-07-31 1:21 ` Keith Owens
2001-07-31 3:09 ` Alexander Viro
2001-08-02 22:46 ` [CFT] initramfs patch (2.4.8-pre3) Alexander Viro
2001-08-04 20:49 ` Ken Moffat
2001-08-05 7:07 ` Alexander Viro
2001-08-05 7:12 ` Alexander Viro
2001-08-05 20:39 ` Ken Moffat
2001-08-05 20:47 ` Alexander Viro
2001-08-06 20:16 ` Ken Moffat
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=20010730132957.A20284@bluemug.com \
--to=miket@bluemug.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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