From: Mark Williamson <mark.williamson@cl.cam.ac.uk>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Martin Steigerwald <Martin@lichtvoll.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
info@fsf.org, office@fsfeurope.org, info@linuxfoundation.org
Subject: Re: Replacing VFAT as filesystem on removeable media
Date: Tue, 31 Mar 2009 16:02:39 +0100 [thread overview]
Message-ID: <200903311602.41272.mark.williamson@cl.cam.ac.uk> (raw)
In-Reply-To: <1238507227.27596.559.camel@skunk>
Hi Xav,
On Tuesday 31 March 2009 14:47:07 Xavier Bestel wrote:
> On Tue, 2009-03-31 at 13:57 +0100, Mark Williamson wrote:
> > Another approach which occurs to me would be to come up with a
> > "filesystem over USB" protocol so that the actual on-disk format is no
> > longer relevant.
>
> Look for MTP. It's what you want, made by Microsoft, and enables all
> sorts of DRM niceties.
Ah, thanks for that. It looks fairly close to what I had in mind, although I
think there are some differences (it transfers whole files at a time and
incorporates device control stuff - neither of which is really necessary in the
scheme I imagined).
According to Wikipedia it is now an official USB device class, which sounds
attractive. I've not heard of Linux providing an MTP responder ("server"),
which I find mildly surprising as it sounds like it would be useful,
particularly given the range of advanced filesystems Linux devices might like
to leverage under the hood. It seems odd if an embedded Linux company hasn't
already coded this up for a device ... ?
I can see how a file-based protocol would be "useful" in enforcing DRM-like
protections in a device implementation but I don't think that such protocols
fundamentally enables any nastiness that couldn't be enforced in other ways by
a motivated pro-DRM device manufacturer. Sounds like MTP is designed to
facilitate DRM if the communications endpoints want it; not something I'm keen
on but also not something that rules it out as a useful standard.
A file-based transfer protocol seems like it would be useful to have for
"sufficiently intelligent" devices, whether it's MTP or something else.
Cheers,
Mark
next prev parent reply other threads:[~2009-03-31 15:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 8:15 Martin Steigerwald
2009-03-31 12:57 ` Mark Williamson
2009-03-31 13:47 ` Xavier Bestel
2009-03-31 15:02 ` Mark Williamson [this message]
2009-03-31 15:21 ` Xavier Bestel
2009-03-31 15:53 ` Mark Williamson
2009-04-02 17:51 ` Bryan Henderson
2009-04-03 8:28 ` Martin Steigerwald
2009-04-05 6:34 ` H. Peter Anvin
2009-04-05 13:30 ` Alejandro Riveira Fernández
2009-04-05 20:05 ` H. Peter Anvin
2009-04-06 19:46 ` Nicholas Miell
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=200903311602.41272.mark.williamson@cl.cam.ac.uk \
--to=mark.williamson@cl.cam.ac.uk \
--cc=Martin@lichtvoll.de \
--cc=info@fsf.org \
--cc=info@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=office@fsfeurope.org \
--cc=xavier.bestel@free.fr \
/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
all inboxes | Powered by JetHome®