public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: brendan.simon@bigpond.com
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: DOC2000 partitiioning question
Date: Tue, 11 Jun 2002 09:45:01 +0100	[thread overview]
Message-ID: <22131.1023785101@redhat.com> (raw)
In-Reply-To: <3D05A8E5.9040808@bigpond.com>

brendan.simon@bigpond.com said:
> HUH ??? If I read this correctly, this means one can NEVER reformat a
> NFTL  device with kernel that boots from a DOC (since the driver must
> be built  in to the kernel).  Is this correct ?

Yes, although in practice you'll get away with it if the NFTL is not in use 
at the time and you reboot without starting to use it. In general, you 
should be using the M-Systems DFORMAT utility under DOS anyway, rather than 
the nftl_format program under Linux.

> This is obviously different for EXT2 and other filesystems, as they
> can  be reformatted anytime with the driver module loaded or built in
> to the  kernel.  Is there a technical reason why NFTL is not the same
> ???

You can't mount it in the same way as other file systems because it is not 
a normal file system. It doesn't provide a file system to the VFS, it 
provides a block device. It's only _like_ a file system.

We could feasibly add an ioctl or some other way to instruct the NFTL code 
to 'unmount' and 'remount' an NFTL. It wouldn't be that hard - we have the 
code there to deal with modular DiskOnChip drivers being loaded and going 
away. Nobody's cared enough to do it, though.

Reformatting the NFTL should be a rare occurrence.


--
dwmw2

  reply	other threads:[~2002-06-11  8:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11  3:53 DOC2000 partitiioning question Brendan J Simon
2002-06-11  7:06 ` David Woodhouse
2002-06-11  7:38   ` Brendan J Simon
2002-06-11  8:45     ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-11 20:44 Eric Nelson
2002-06-12 10:47 ` 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=22131.1023785101@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=brendan.simon@bigpond.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