public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: sl@whiskey.fireplug.net (Stuart Lynne)
To: linux-kernel@vger.kernel.org
Subject: Re: /linuxrc query
Date: 23 Mar 2001 23:33:00 -0800	[thread overview]
Message-ID: <99hijc$8p5$1@whiskey.enposte.net> (raw)
In-Reply-To: <985356959.24859@whiskey.enposte.net>

In article <985356959.24859@whiskey.enposte.net>,
David Woodhouse <dwmw2@infradead.org> wrote:
>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.

Union would be fine. But until then I prefer ramfs as root with symlinks
to cramfs for anything that doesn't need to be writeable. 

-- 
                                            __O 
Lineo - For Embedded Linux Solutions      _-\<,_ 
PGP Fingerprint: 28 E2 A0 15 99 62 9A 00 (_)/ (_) 88 EC A3 EE 2D 1C 15 68
Stuart Lynne <sl@fireplug.net>       www.fireplug.net        604-461-7532

       reply	other threads:[~2001-03-24  7:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <985356959.24859@whiskey.enposte.net>
2001-03-24  7:33 ` Stuart Lynne [this message]
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

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='99hijc$8p5$1@whiskey.enposte.net' \
    --to=sl@whiskey.fireplug.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sl@fireplug.net \
    /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