public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: elf@buici.com
To: linux-mtd@lists.infradead.org
Subject: Unclear about unwriteprotecting
Date: Sat, 4 May 2002 17:25:18 -0700	[thread overview]
Message-ID: <20020505002518.GA3665@buici.com> (raw)

I've built the mtd driver into a 2.2.17 kernel using the mtd-20000704
version.  I am accessing a DOC 2000 (24MB) that was created using the
M-Systems's doc driver.  It has two partitions, one formatted for
ext2.

The NFTL driver sees the partitions find and I can mount them.
However, I cannot write.  Nothing in the code or on the list has
enlightened me.  What am I missing?

             reply	other threads:[~2002-05-05  0:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020507152652.GA30979@buici.com>
     [not found] ` <20020507022357.GC17041@buici.com>
2002-05-05  0:25   ` elf [this message]
2002-05-05 16:04     ` Building from CVS for 2.2.x elf
2002-05-06 20:07     ` Unclear about unwriteprotecting David Woodhouse
     [not found]       ` <25429.1020783875@redhat.com>
     [not found]         ` <27957.1020785387@redhat.com>
2002-05-07 15:50           ` Latest CVS and 2.2.x elf
2002-05-07 15:55             ` David Woodhouse

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=20020505002518.GA3665@buici.com \
    --to=elf@buici.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