From: Wolfgang Denk <wd@denx.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
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 09:09:11 +0200 [thread overview]
Message-ID: <20040628070916.706A6C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sun, 27 Jun 2004 18:46:20 EDT." <Pine.LNX.4.60.0406271836300.10210@localhost.localdomain>
In message <Pine.LNX.4.60.0406271836300.10210@localhost.localdomain> you wrote:
>
> with this configuration, it's obviously not possible to update files
> or directories in the bootable image individually -- it's just one big
> zImage.inited image.
What makes you think that this is not possible? If there is (for
example) a writable JFFS2 partition available, you can use this for
an overlay filesystem to store the updates.
See for example the "mini_fo" overlay filesystem on our FTP server
and the paper about it:
http://www.denx.de/PDF/Diplomarbeit-MK-1.0-net.pdf
> but is it feasible to redefine the layout of that flash chip and
> take, say, 4M of it and create a JFFS2 filesystem, then put the root
> filesystem in there uncompressed? (assuming, of course, that the
Standard JFFS2 code will always compress.
> is this possible? anyone done it this way, and can tell me what
> pitfalls i have to watch for? thanks.
This is a pretty standard setup. Although I don't really recommend to
use JFFS2 for root filesystem (for example, because with a big root
filesystem the boot time may deteriorate). Instead, we usually split
the stuff in a read-only partition (for example cramfs), a volatile
part (tmpfs), and a persistent storage partition (JFFS2).
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Generally speaking, there are other ways to accomplish whatever it is
that you think you need ... - Doug Gwyn
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-06-28 7:09 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 [this message]
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
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=20040628070916.706A6C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rpjday@mindspring.com \
/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).