linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Dan Luedtke <mail@danrl.de>
Cc: Jochen Striepe <jochen@tolot.escape.de>,
	Marco Stornelli <marco.stornelli@gmail.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	lanyfs@librelist.com
Subject: Re: [PATCH] fs: Introducing Lanyard Filesystem
Date: Sun, 19 Aug 2012 17:04:55 -0400	[thread overview]
Message-ID: <20120819210455.GA9208@thunk.org> (raw)
In-Reply-To: <1345390432.2716.34.camel@tunafish>

On Sun, Aug 19, 2012 at 05:33:52PM +0200, Dan Luedtke wrote:
> 
> Poorly crafted example:
> Let's say you have a 6GB video file you want to give somebody (e.g. a
> video cutter) on a thumb drive. The cutter wants to edit the file, so he
> needs read and write access to it. After cutting the file is to be
> played on a TV screen with USB-port. What if the cutter does use two
> different, major, non-Linux operating systems, let's say one for cutting
> and the other one for adding visual effects? Now imagine the cutter (and
> of course the TV screen vendor) don't care much about filesystems as
> they are just generating costs (implementation), so it will only come
> with minimal compatibility.
> - What filesystem would you recommend to share that video file?

So the problem with using interoperability as your prime driver is
that other operating systems won't have implemented your LanyFS, and
because of licensing issues, it will be very hard to get even a
shareware distribution of LanyFS for Windows (because of licensing
issues around Window's IFS SDK).

In practice, the solution of using either FAT for most cases as the
interchange format works well enough for most purposes.  Granted it
doesn't in the case of your example of a 6GB video file (which I'd
probably transmit using a networking protocol, since a thumb drive
would be really slow.)  What I would do if I needed to transfer such a
file, and I didn't have access to high speed networking, would be to
use ext2, and then either use the ext2 FUSE driver with FUSE for
Windows or Macintosh --- or, I would port the userspace e2tools
package to the target OS, and use that to access the ext2 file ssytem.
And I'd do that because the software is available today, right now,
without having to figure out how to port LanyFS to the operating
system.

> There is a small niche which LanyFS tries to fit in. It is for those who
> do not want to bother about how to use a fs when they are in a hurry or
> when they just want to listen to music in the car.  It is for the
> it-must-be-easy-enough-for-my-gradma fraction. 

Music doesn't require > 4GB files, and there are plenty of very easy
to use solutions that utilize streaming over the network.  That is
*always* going to be easier than figuring out ahead of time which
files you want, and then manually copying them onto a thumb drive, and
then taking the thumb drive to the car....  Somehow I can't quite
imagine your grandma manually copying files over using LanyFS.  :-)

I also seriously question the niche of people who want to use a thumb
drive to transfer > 4GB files.  Try it sometime and see what a painful
user experience it is....

Regards,

						- Ted

  parent reply	other threads:[~2012-08-19 21:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-18 23:38 [PATCH] fs: Introducing Lanyard Filesystem Dan Luedtke
2012-08-18 22:06 ` Alan Cox
2012-08-18 22:16 ` richard -rw- weinberger
     [not found]   ` <c925f795-28d8-4e6d-8131-9a14d6e83659@email.android.com>
2012-08-18 22:27     ` richard -rw- weinberger
2012-08-19 10:12   ` Dan Luedtke
2012-08-19 10:14     ` Marco Stornelli
2012-08-19 13:34       ` Dan Luedtke
2012-08-19 12:02         ` Jochen Striepe
2012-08-19 15:33           ` Dan Luedtke
2012-08-19 14:07             ` Jochen Striepe
2012-08-19 14:27             ` Al Viro
2012-08-19 16:53               ` Dan Luedtke
2012-08-19 15:12                 ` Al Viro
2012-08-19 15:24                 ` Marco Stornelli
2012-08-20 17:36                   ` Dan Luedtke
2012-08-19 21:04             ` Theodore Ts'o [this message]
2012-08-19 21:20               ` Andi Kleen
2012-08-19 23:06               ` Carlos Alberto Lopez Perez
2012-08-20  0:47                 ` Theodore Ts'o
2012-08-20  6:07                   ` Raymond Jennings
2012-08-20  6:49                     ` Oliver Neukum
2012-08-20  9:12                   ` Alexander Thomas
2012-08-20 13:21                     ` Theodore Ts'o
2012-08-22  8:38                       ` Arnd Bergmann
2012-08-20 11:36                   ` Pavel Machek
2012-08-20 12:49                     ` Ronnie Collinson
2012-08-20 17:48               ` Dan Luedtke
2012-08-19 13:25         ` Marco Stornelli
2012-08-19 15:45           ` Dan Luedtke
2012-08-22  9:53         ` Jan Engelhardt
2012-08-21  6:09 ` Vyacheslav Dubeyko
2012-08-23 17:29 ` Eric W. Biederman
2012-08-24 11:50 ` Prashant Shah

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=20120819210455.GA9208@thunk.org \
    --to=tytso@mit.edu \
    --cc=jochen@tolot.escape.de \
    --cc=lanyfs@librelist.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@danrl.de \
    --cc=marco.stornelli@gmail.com \
    /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).