All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamey Hicks <jamey.hicks@hp.com>
To: David Woodhouse <dwmw2@infradead.org>
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 08:12:20 -0400	[thread overview]
Message-ID: <3D623224.1090604@hp.com> (raw)
In-Reply-To: 32719.1029838865@redhat.com

David Woodhouse wrote:

>ch@murgatroid.com said:
>  
>
>> Do you need to unlock your flash before you can write to it?  That's
>>not done automatically by mtd or jffs2.  There's a diff in the ARM
>>patch system by me that might be applicable. 
>>    
>>
>
>I'm beginning to wonder if we should make JFFS2 unlock automatically if it 
>finds at least some JFFS2 nodes. Or put in the 'is_flash_locked' method and 
>make JFFS2 notice that it's locked _before_ trying to write to it, and 
>print an appropriate message and mount in read-only mode so it doesn't even 
>let you _try_ to write to it.
>  
>
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.  

Jamey

  reply	other threads:[~2002-08-20 12:00 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 [this message]
2002-08-20 12:19           ` David Woodhouse
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=3D623224.1090604@hp.com \
    --to=jamey.hicks@hp.com \
    --cc=ch@murgatroid.com \
    --cc=clark@esteem.com \
    --cc=dwmw2@infradead.org \
    --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.