From: Helge Hafting <helgehaf@aitel.hist.no>
To: Tomasz Torcz <zdzichu@irc.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Large-FAT32-Filesystem Bug
Date: Mon, 08 Dec 2003 10:54:55 +0100 [thread overview]
Message-ID: <3FD44A6F.2060707@aitel.hist.no> (raw)
In-Reply-To: <20031207122034.GA17042@irc.pl>
Tomasz Torcz wrote:
> On Sun, Dec 07, 2003 at 01:26:50PM +0100, Helge Hafting wrote:
>
>>On Fri, Dec 05, 2003 at 05:17:00AM -0800, jdow wrote:
>>
>>>From: "Torsten Scheck" <torsten.scheck@gmx.de>
>>>
>>>>Dear friends:
>>>>
>>>>I already sent a message to the VFAT maintainer, but I decided
>>>>to additionally bother this list with a warning. This way some
>>>>readers might avoid data loss.
>>>
>>>This all may be moot. Microsoft is about to charge a royalty for
>>>use of the FAT file system. http://www.microsoft.com/mscorp/ip/tech/fat.asp
>>>
>>
>>The claim some patents, but aren't FAT so old that they have
>>expired?
>
>
> Patents for storing long names of files (which Microsoft is charging for)
> are from 1995 or something.
>
No problem then - long filenames on fat is something I only see a need for
when sharing a partition with windows - you then have a licence to use
fat through the windows licence.
Digital cameras and such simply don't need long names.
Helge Hafting
next prev parent reply other threads:[~2003-12-08 9:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 9:52 Large-FAT32-Filesystem Bug Torsten Scheck
2003-12-05 13:17 ` jdow
2003-12-07 12:26 ` Helge Hafting
2003-12-07 12:20 ` Tomasz Torcz
2003-12-08 9:54 ` Helge Hafting [this message]
2003-12-08 14:10 ` Gene Heskett
2003-12-08 16:19 ` Randy.Dunlap
2003-12-07 13:56 ` Gene Heskett
2003-12-05 15:26 ` Eduard Bloch
2003-12-05 16:07 ` Erik Andersen
2003-12-05 17:54 ` Torsten Scheck
2003-12-05 22:10 ` Erik Andersen
2003-12-05 22:45 ` Mike Fedyk
2003-12-05 23:26 ` Måns Rullgård
2003-12-06 0:04 ` Andreas Schwab
2003-12-06 0:44 ` Måns Rullgård
2003-12-06 1:10 ` Andreas Schwab
2004-02-06 14:43 ` Torsten Scheck
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=3FD44A6F.2060707@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=zdzichu@irc.pl \
/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).