From: "Bao C. Ha" <baoha@sensoria.com>
To: <linux-mtd@lists.infradead.org>
Subject: JFFS2 destroys CRAMFS!
Date: Tue, 23 Oct 2001 11:52:14 -0700 [thread overview]
Message-ID: <014d01c15bf3$d4ff82a0$456c020a@SENSORIA> (raw)
We are using RedBoot and have several MTD partitions.
One of the partitions has our minimal CRAMFS. The
other contains JFFS2. I made a mistake of compiling
a kernel with jffs2 built-in, but not cramfs. The
bootup process tells the kernel to mount the cramfs
partition as the root device. It just goes through
and erased everything there, then it panics!
This behavior is not consistent with all other Linux
filesystems. I would like to propose changes to the
designs of jffs2 as follows:
- Only make.jffs2 can create a jffs2 filesystem
- Unless jffs2 detects its MAGIC, it can't make
changes to the MTD partition.
It will save a lot of griefs later. I know that
there are many work-arounds. But, I had a mental
block that had refused to believe that a read-only
cramfs can be destroyed that easily.
Thanks.
Bao
next reply other threads:[~2001-10-23 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 18:52 Bao C. Ha [this message]
2001-10-24 8:48 ` JFFS2 destroys CRAMFS! Jörn Engel
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='014d01c15bf3$d4ff82a0$456c020a@SENSORIA' \
--to=baoha@sensoria.com \
--cc=linux-mtd@lists.infradead.org \
/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