From: "Christopher Hoover" <ch@murgatroid.com>
To: "'Jamey Hicks'" <jamey.hicks@hp.com>,
"'David Woodhouse'" <dwmw2@infradead.org>
Cc: "'Conn Clark'" <clark@esteem.com>,
"'Jörn Engel'" <joern@wohnheim.fh-wedel.de>,
"'MTD Mailing List'" <linux-mtd@lists.infradead.org>
Subject: RE: How does one mount an existing jffs2 partition so it is writeable?
Date: Tue, 20 Aug 2002 09:34:12 -0700 [thread overview]
Message-ID: <000301c24867$6a81ad70$7800000a@derelict> (raw)
In-Reply-To: <3D623224.1090604@hp.com>
> I would much rather that JFFS2 not unlock blocks automatically. We
tend
> to lock blocks for a reason (e.g., so that we don't accidentally erase
> the boot loader with incorrect mount options).
You have a different flavor flash. My platform uses Intel C3
StrataFlash parts. The flash is completely locked after any power
cycle. If I don't unlock the jffs2 partition somehow someway, I can't
write to it.
I suppose we could add yet another mount option for this
("really_and_truly_rw"!).
-ch
ch@murgatroid.com
ch@hpl.hp.com
next prev parent reply other threads:[~2002-08-20 16:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 17:34 How does one mount an existing jffs2 partition so it is writeable? Conn Clark
2002-08-19 23:42 ` Jörn Engel
2002-08-20 0:01 ` Conn Clark
2002-08-20 0:25 ` Christopher Hoover
2002-08-20 10:21 ` David Woodhouse
2002-08-20 12:12 ` Jamey Hicks
2002-08-20 12:19 ` David Woodhouse
2002-08-20 13:12 ` Jörn Engel
2002-08-20 16:34 ` Christopher Hoover [this message]
2002-08-20 19:24 ` Jörn Engel
2002-08-20 21:45 ` Christopher Hoover
2002-08-20 21:46 ` David Woodhouse
2002-08-20 17:26 ` Conn Clark
2002-08-20 18:02 ` Conn Clark
2002-08-20 18:18 ` Christopher Hoover
2002-08-20 18:42 ` Conn Clark
2002-08-20 21:50 ` Christopher Hoover
2002-08-20 10:10 ` Jörn Engel
[not found] <000001c2489f$bf76d070$7c00000a@SNAGGLE>
2002-08-21 0:15 ` Conn Clark
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='000301c24867$6a81ad70$7800000a@derelict' \
--to=ch@murgatroid.com \
--cc=clark@esteem.com \
--cc=dwmw2@infradead.org \
--cc=jamey.hicks@hp.com \
--cc=joern@wohnheim.fh-wedel.de \
--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