linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Jennings <shentino@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Carlos Alberto Lopez Perez <clopez@igalia.com>,
	Dan Luedtke <mail@danrl.de>,
	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 23:07:32 -0700	[thread overview]
Message-ID: <1345442852.3906.0.camel@warfang.spyronet> (raw)
In-Reply-To: <20120820004705.GA3710@thunk.org>

On Sun, 2012-08-19 at 20:47 -0400, Theodore Ts'o wrote:
> On Mon, Aug 20, 2012 at 01:06:20AM +0200, Carlos Alberto Lopez Perez wrote:
> > 
> > > 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....
> > 
> > Think for example on consumer devices, for example on most moderns TV
> > you can plug a USB memory disk with videos and play them.
> 
> More and more consumer devices, including TV's, are network-enabled.
> I'm not at all convinced the USB memory disk model is the one which
> makes sense --- you can make a much better user experience work if you
> can rely on networking.  That way you don't have to move USB storage
> devices around, and USB storage devices are *slow* when the most
> common types are HDD's and crappy flash devices.  How many people are
> going to drop several hundred dollars for a USB-attached SSD, when
> using a networking transfer mechanism is much more convenient?
> 
> > And I doubt that the majority of this consumer devices are able to read
> > nothing more than FAT32 file-systems, so the 4GB limit is a big problem.
> > And here is where Microsoft is pushing their exFAT FS since it allows
> > working with 4GB+ files without the NTFS overhead.
> 
> We'll see how popular a heavily IP-encumbered file system will be,
> especially given that its main use case is for devices which are so
> constrained that they can't afford to use a "real file system" (like
> ntfs or ext4 or some other more sophisticated file system), but which
> nevertheless needs to be able to handle 4GB+ files.

My two cents:

After seeing microsoft's attack on TomTom over the vfat patents I
honesstly would consider it a good move to have an alternative free
format available.

> I'm sure there will be some use cases that might fit that niche, but
> it seems pretty tiny.  And this is completely ignoring what might
> happen if in the future people take 1gig fiber connections to the home
> (such as what many people in Kansas City will be enjoying very
> shortly) for granted....
> 
> > As a side note, it would be possible to write a driver for exFAT and get
> > it merged upstream on the Linux Kernel without "breaking any law"?
> > Goggling I found an attempt to write such driver but seems that never
> > got merged:  https://lkml.org/lkml/2009/2/8/24
> 
> You'll need to talk to a lawyer about that, since that's fundamentally
> a legal question.
> 
> Regards,
> 
> 						- Ted
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



  reply	other threads:[~2012-08-20  6:07 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
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 [this message]
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=1345442852.3906.0.camel@warfang.spyronet \
    --to=shentino@gmail.com \
    --cc=clopez@igalia.com \
    --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 \
    --cc=tytso@mit.edu \
    /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).