From: David Woodhouse <dwmw2@infradead.org>
To: Amit D Chaudhary <amit@muppetlabs.com>
Cc: Werner Almesberger <Werner.Almesberger@epfl.ch>,
lermen@fgan.de, linux-kernel@vger.kernel.org
Subject: Re: /linuxrc query
Date: Fri, 23 Mar 2001 14:07:51 +0000 [thread overview]
Message-ID: <9118.985356471@redhat.com> (raw)
In-Reply-To: <3ABAF64A.1040106@muppetlabs.com>
In-Reply-To: <3ABAF64A.1040106@muppetlabs.com> <3ABAEED2.6020708@muppetlabs.com> <20010323075107.Q3932@almesberger.net>
amit@muppetlabs.com said:
> Also as a note, what we are doing is keeping our rootfs on flash as a
> tar.gz and reading it and mounting it on a ramfs in the /linuxrc
> before doing a pivot_root. To summarize, pivot_root has been a life
> saver as the earlier real_root_dev might not have been useful in this
> case. Not using the ramfs limits for now, will do soon.
If you're concerned about memory usage - why untar the whole of your root
filesystem into a ramfs? My preferred solution is to just mount the root
filesystem directly from the flash as cramfs (or JFFS2), with symlinks into a
ramfs for appropriate parts like /tmp and /var.
I suppose the best option is actually to union-mount the ramfs over the
root, rather than mucking about with symlinks. I just haven't got round to
doing that yet.
--
dwmw2
next prev parent reply other threads:[~2001-03-23 14:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 6:36 /linuxrc query Amit D Chaudhary
2001-03-23 6:51 ` Werner Almesberger
2001-03-23 7:00 ` Amit D Chaudhary
2001-03-23 11:18 ` Werner Almesberger
2001-03-23 17:46 ` Amit D Chaudhary
2001-03-23 7:07 ` Amit D Chaudhary
2001-03-23 11:24 ` Werner Almesberger
2001-03-23 14:07 ` David Woodhouse [this message]
2001-03-23 18:00 ` RAMFS, CRAMFS and JFFS2(was Re: /linuxrc query) Amit D Chaudhary
2001-03-23 19:37 ` David Woodhouse
2001-03-23 20:25 ` CRAMFS Bjorn Wesen
2001-03-23 22:01 ` CRAMFS Amit D Chaudhary
[not found] <985356959.24859@whiskey.enposte.net>
2001-03-24 7:33 ` /linuxrc query Stuart Lynne
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=9118.985356471@redhat.com \
--to=dwmw2@infradead.org \
--cc=Werner.Almesberger@epfl.ch \
--cc=amit@muppetlabs.com \
--cc=lermen@fgan.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.