From: David Woodhouse <dwmw2@infradead.org>
To: mike@bithead.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: JFFS1 vs JFFS2 compatibility
Date: Tue, 21 Dec 2004 11:40:20 +0000 [thread overview]
Message-ID: <1103629220.6111.57.camel@localhost.localdomain> (raw)
In-Reply-To: <20041213223652.50142.qmail@web54704.mail.yahoo.com>
On Mon, 2004-12-13 at 14:36 -0800, Mike Wellington wrote:
> Hi-
> I know some guys who have JFFS v1 running on their Linux platform.
>
> They want to know what (if anything) is liable to break when they
> try to go to JFFS2.
>
> They don't do anything fancy, just simple file operations
> (open, write, close).
>
> I told them there should be no problem, but they still
> want me to ask you experts.
There should be no problem. Obviously the on-medium format isn't
compatible and you'll need to recreate your file system, but anything
which worked on JFFS1 should continue to work on JFFS2 -- and more.
--
dwmw2
prev parent reply other threads:[~2004-12-21 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 22:36 JFFS1 vs JFFS2 compatibility Mike Wellington
2004-12-21 11:40 ` David Woodhouse [this message]
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=1103629220.6111.57.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mike@bithead.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