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 14:14:27 -0700 [thread overview]
Message-ID: <20010730141427.E20284@bluemug.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0107301646050.19391-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0107301646050.19391-100000@weyl.math.psu.edu>
On Mon, Jul 30, 2001 at 04:49:15PM -0400, Alexander Viro wrote:
>
> On Mon, 30 Jul 2001, Mike Touloumtzis wrote:
>
> > 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?
>
> a) IIRC, both are read-only.
Hmmm, maybe we need ramfs-backed-by-romfs :-). But a lot of people
in the embedded/consumer electronics space could get by just fine
with a read-only / and a ramfs or ramdisk on /tmp.
> b) what stops you from doing initramfs + romfs-on-initrd? It works.
-- Having the FS image compiled into the kernel allows a linker script
to specify the alignment requirements for the FS.
-- initrd is a yucky special case. What I'm advocating is just a
standard way of addressing compiled-in filesystems using the normal
/dev namespace.
miket
next prev parent reply other threads:[~2001-07-30 21:14 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
2001-07-30 20:49 ` Alexander Viro
2001-07-30 21:14 ` Mike Touloumtzis [this message]
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=20010730141427.E20284@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