linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@Lichtvoll.de>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, info@fsf.org, office@fsfeurope.org,
	info@linuxfoundation.org
Subject: Replacing VFAT as filesystem on removeable media
Date: Tue, 31 Mar 2009 10:15:28 +0200	[thread overview]
Message-ID: <200903311015.29222.Martin@Lichtvoll.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]


Hi!

Now as TomTom appears to have surrendered to Microsoft and Microsoft seems 
to have accepted this deal probably in order to not find out that their 
patents are void, I think replacing VFAT as standard cross platform 
filesystem on removeable media would be an even better idea than before 
[1].

Granted I believe the patents will be made void one day, but even then I 
think it would make sense to replace VFAT for technical reasons.

Such a filesystem IMHO should have the following features:
- cross platform with implementations for Linux, Windows, Mac OS X at 
least, also the varios BSD variantes come to my mind
- open source
- probably some support for flash media without or with bad wear leveling
- some kind of journaling or other metadata consistency guarentee 

People use ext2 as an alternative, but that lacks journaling.

I could also think of UDF with write support, but I am not sure whether 
Windows and Mac OS X has write support.

Or probably even a new filesystem as long as people appear to write one 
filesystem after another these days.

Or some kind of FAT *without* compatibility hacks, but I think this would 
still be an inferior solution as long as it doesn't provide for metadata 
consistency.

Maybe this could become some kind of Linux Foundation or FSF joint effort? 
Together with advertising and advocacy of free software users this could 
probably really replace VFAT in the long term.

What do you think? What other features would make sense to for such a 
filesystem.

I am willing to test such a filesystem and help with documentation as well 
as advocacy. But for coding I better start with something easier ;-).

[1] 
http://www.h-online.com/open/TomTom-Microsoft-settle-patent-dispute--/news/112964

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-03-31  8:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31  8:15 Martin Steigerwald [this message]
2009-03-31 12:57 ` Replacing VFAT as filesystem on removeable media Mark Williamson
2009-03-31 13:47   ` Xavier Bestel
2009-03-31 15:02     ` Mark Williamson
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=200903311015.29222.Martin@Lichtvoll.de \
    --to=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 \
    /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).