From: Wolfgang Denk <wd@denx.de>
To: shawnxjin@gmail.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Which way to store log in flash on mpc8xx?
Date: Mon, 19 Sep 2005 21:29:15 +0200 [thread overview]
Message-ID: <20050919192915.B482E353BF3@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 19 Sep 2005 11:40:05 PDT." <c3d0340b050919114040d0a0fe@mail.gmail.com>
In message <c3d0340b050919114040d0a0fe@mail.gmail.com> you wrote:
>
> What's the trouble caused by log files when using a JFFS2? I'm not
> aware of that. Any pointers to where I should look into are much
> appreciated.
Please see the linux-mtd web site and/or MTD mailing list archives
for details. JFFS2 works excellent with files that are written once
(or with only a few write() calls. Logfiles typically grow forever,
by many, many small chunks of data appended in many write()
operations - this is kind of killer application for JFFS2.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"I find this a nice feature but it is not according to the documen-
tation. Or is it a BUG?" "Let's call it an accidental feature. :-)"
- Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
next prev parent reply other threads:[~2005-09-19 19:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 9:55 Which way to store log in flash on mpc8xx? David Jander
2005-09-19 15:09 ` Frank
2005-09-19 15:37 ` Wolfgang Denk
2005-09-19 17:26 ` David Jander
2005-09-19 19:21 ` Wolfgang Denk
2005-09-20 9:17 ` David Jander
2005-09-20 18:07 ` Wolfgang Denk
2005-11-29 1:06 ` David Ho
2005-11-29 14:17 ` David Jander
2005-09-19 18:40 ` Shawn Jin
2005-09-19 19:07 ` Jörn Engel
2005-09-19 19:29 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-20 20:25 Eli Brin
2005-11-29 15:37 Fillod Stephane
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=20050919192915.B482E353BF3@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=shawnxjin@gmail.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).