All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jamey Hicks <jamey.hicks@hp.com>
Cc: "Christopher Hoover" <ch@murgatroid.com>,
	"'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 13:19:14 +0100	[thread overview]
Message-ID: <12777.1029845954@redhat.com> (raw)
In-Reply-To: <3D623224.1090604@hp.com>

jamey.hicks@hp.com said:
>  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).  I think it
> would be  reasonable for JFFS2 to query whether flash is locked
> beforehand and to  mount read-only.  I think it would also be
> reasonable to provide a mount  option directing it to unlock flash.  

Yeah -- you're probably right. That's the reason I refused to do the 
automatic unlock when it was originally suggested. We are fairly good about 
aborting a mount attempt if it really doesn't look like a JFFS2 partition, 
but if you have the partitioning wrong so that the range we try to mount 
includes some JFFS2 _and_ something important, that's still going to break.


--
dwmw2

  reply	other threads:[~2002-08-20 12:19 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 [this message]
2002-08-20 13:12             ` Jörn Engel
2002-08-20 16:34           ` Christopher Hoover
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=12777.1029845954@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=ch@murgatroid.com \
    --cc=clark@esteem.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.