From: Mike Frysinger <vapier@gentoo.org>
To: Adrian McMenamin <adrian@newgolddream.dyndns.info>
Cc: Paul Mundt <lethal@linux-sh.org>,
"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 03:23:15 -0400 [thread overview]
Message-ID: <200904140323.19062.vapier@gentoo.org> (raw)
In-Reply-To: <1239693375.6538.5.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
On Tuesday 14 April 2009 03:16:15 Adrian McMenamin wrote:
> On Tue, 2009-04-14 at 16:03 +0900, Paul Mundt wrote:
> > Everything about the on-disk format is tied to the VMU. Until that sinks
> > in, don't bother sending me email, thanks.
>
> No, everything in the file system is dependent on the specification. The
> specification is not dependent on the hardware. Those are the facts.
i must be slow because i tend to agree with Adrian here. if the VMU is a
simple block device, then while the filesystem format may have been tailored
to the exact hardware layout of the VMU, it doesnt mean that the resulting
filesystem spec will only work on that hardware. then again, i didnt read the
entire source code from top to bottom ...
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-14 7:23 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
2009-04-14 7:03 ` Paul Mundt
2009-04-14 7:16 ` Adrian McMenamin
2009-04-14 7:23 ` Mike Frysinger [this message]
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=200904140323.19062.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=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).