linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: loading the kernel and root FS separately from flash?
Date: Mon, 28 Jun 2004 06:50:13 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.60.0406280642220.4278@localhost.localdomain> (raw)
In-Reply-To: <20040628104159.87EEDC109F@atlas.denx.de>


On Mon, 28 Jun 2004, Wolfgang Denk wrote:

> In message <Pine.LNX.4.60.0406280600140.3259@localhost.localdomain> you wrote:

>> that it could be read-only).  how hard would it be to automatically
>> have that root FS copied from JFFS2 to RAM and mounted from there?
>
> This makes just no sense to me.

ok, i'm probably getting confused about something fundamental here.
what i'm after is to have my root filesystem in persistent storage and
available for updates on the fly, hence the notion of partitioning off
a part of the system flash for the JFFS2 version of the root
filesystem.  i've done that, so i've solved that problem -- i have a
root filesystem i can mount from a running system and modify.

now, i could just mount that JFFS2 version of the root fs straight out
of flash, but i get the impression that that would cause a performance
hit.  so i was wondering about the feasibility about copying that
entire flash FS into RAM at boot time, and running out of RAM.  this
would mean, of course, that if i wanted to make mods to the root FS,
i'd do them in flash and they'd only take effect at the next reboot,
which is fine with me.

or am i just hopelessly confused about what is and is not a reasonable
option here?  i get the feeling i'm missing something important.

rday

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-28 10:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27 22:46 loading the kernel and root FS separately from flash? Robert P. J. Day
2004-06-28  3:58 ` Eugene Surovegin
2004-06-28 10:00   ` Robert P. J. Day
2004-06-28  7:09 ` Wolfgang Denk
2004-06-28  9:42   ` David Woodhouse
2004-06-28 10:19     ` Robert P. J. Day
2004-06-28 10:48       ` Wolfgang Denk
2004-06-28 10:52         ` Robert P. J. Day
2004-06-28 10:23     ` Robert P. J. Day
2004-06-28 10:36     ` Wolfgang Denk
2004-06-28 10:40       ` David Woodhouse
2004-06-28 10:13   ` Robert P. J. Day
2004-06-28 10:41     ` Wolfgang Denk
2004-06-28 10:50       ` Robert P. J. Day [this message]
2004-06-29  9:31         ` David Woodhouse
2004-06-29 12:09           ` Robert P. J. Day
  -- strict thread matches above, loose matches on Subject: below --
2004-06-28 11:33 Gerhard TAEUBL
     [not found] <s0e01d9a.092@mail.frequentis.com>
2004-06-28 12:11 ` Robert P. J. Day

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=Pine.LNX.4.60.0406280642220.4278@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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;
as well as URLs for NNTP newsgroup(s).