From: David Jander <david.jander@protonic.nl>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: How reliable is jffs2 really (denx cvs devel kernel)?
Date: Wed, 20 Jul 2005 08:30:26 +0200 [thread overview]
Message-ID: <200507200830.27141.david.jander@protonic.nl> (raw)
In-Reply-To: <20050719183745.AD52A352671@atlas.denx.de>
On Tuesday 19 July 2005 20:37, you wrote:
>[...]
> You probably want to ask this on the MTD mailing list; don't forget
> to mention the exact version of the MTD / JFFS2 code you're using
> (see CVS history).
I already thought it might be a good idea to subscribe to that list.
Any hint about how I can figure out exactly which version of MTD code I have?
The version of linuxppc_2_4_devel I have is about 2 months old, do I have to
expect important changes concerning MTD since then?
While we are there, what other solution would you suggest for this problem: We
need to log data into flash. Right now I use an oversized jffs2 partition,
log via syslogd and logrotate on size. I am getting the impression that this
is not workable for mission critical things. At least not with the kernel and
MTD code I have. Others must have the same problem, so here's my question:
Which way to do such a thing? Write my own filesystem?
Greetings,
--
David Jander
next prev parent reply other threads:[~2005-07-20 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 8:21 How reliable is jffs2 really (denx cvs devel kernel)? David Jander
2005-07-19 12:57 ` David Ho
2005-07-19 18:42 ` Wolfgang Denk
2005-07-19 19:03 ` David Ho
2005-07-19 18:37 ` Wolfgang Denk
2005-07-20 6:30 ` David Jander [this message]
2005-07-20 8:37 ` Wolfgang Denk
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=200507200830.27141.david.jander@protonic.nl \
--to=david.jander@protonic.nl \
--cc=linuxppc-embedded@ozlabs.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).