From: Adrian McMenamin <adrian@newgolddream.dyndns.info>
To: Paul Mundt <lethal@linux-sh.org>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-sh <linux-sh@vger.kernel.org>,
"Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [RFC][patch] filesystem: Vmufat filesystem, version 4
Date: Tue, 14 Apr 2009 08:00:29 +0100 [thread overview]
Message-ID: <1239692429.6538.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20090413215949.GD14847@linux-sh.org>
On Tue, 2009-04-14 at 06:59 +0900, Paul Mundt wrote:
> This file system is tied directly to the VMU. Assumptions about the
> on-disk format, block numbering limitations, etc. are all VMU
> constraints, and papering over that in the Kconfig text is not
> sufficient. This file system is and always will be tied to the VMU, and
> you really do not want to decouple the two. What you do in loopback mode
> for testing is your own business, but this will not work in the way
> people expect on a fixed disk. You are only making things harder on
> yourself by insisting that this is somehow generic.
>
> The file system at least wants a dependency on the VMU (and I suppose
> mtdblock) itself.
Why won't it work on a fixed disk "in the way people expect"? Granted
they'd be eccentric to format a disk in this way but there is no
inherent reason why this file system *has* to be tied to a VMU.
next prev parent reply other threads:[~2009-04-14 7:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 20:32 [RFC][patch] filesystem: Vmufat filesystem, version 4 Adrian McMenamin
2009-04-13 21:00 ` Paul Mundt
2009-04-13 21:36 ` Adrian McMenamin
2009-04-13 21:40 ` Adrian McMenamin
2009-04-13 22:28 ` Mike Frysinger
2009-04-13 21:59 ` Paul Mundt
2009-04-14 7:00 ` Adrian McMenamin [this message]
2009-04-14 7:03 ` Paul Mundt
2009-04-14 7:16 ` Adrian McMenamin
2009-04-14 7:23 ` Mike Frysinger
2009-04-14 7:38 ` Sam Ravnborg
2009-04-16 11:23 ` Al Viro
2009-04-24 22:14 ` Pavel Machek
2009-04-27 17:56 ` Mike Frysinger
2009-04-27 18:03 ` Pavel Machek
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=1239692429.6538.2.camel@localhost.localdomain \
--to=adrian@newgolddream.dyndns.info \
--cc=jeffpc@josefsipek.net \
--cc=lethal@linux-sh.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).