public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Dow" <jdow@earthlink.net>
To: <lee@ricis.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Current status of NTFS support
Date: Fri, 20 Apr 2001 18:34:24 -0700	[thread overview]
Message-ID: <0aa401c0ca03$333fdd70$1125a8c0@wednesday> (raw)
In-Reply-To: <86256A34.0079A841.00@smtpnotes.altec.com> <01042101555600.03154@blackbox> <01042020185806.00845@linux>

From: "Lee Leahu" <lee@ricis.com>

> would somebody be kind enough to explain why writing to 
> the ntfs file system is extremely dangerous,  and what are the
> developers doing to make writing to ntfs filesystem safe?

My understanding of the situation is that writing to an NTFS volume is not
quite 100% guaranteed to destroy the disk directory structure. MS mutates it
faster than people can reverse engineer it in a proper "clean" manner. The
person who had been working the issue had access to MS information in support
of some other products. MS came down on him about supporting NTFS. So he has
surrendered such materials as he has rather than continue with the MS product
support and is concentrating on Linux. But until his NDA runs out he cannot
work on the NTFS code. Other people have picked up the ball. But as noted
MS mutates NTFS remarkably rapidly so I'd not look for support for NTFS in
the near future.

I have oversimplified the whole issue for which I hope others forgive me. I
see no benefit to a rehash of the issue so I am attempting to inject enough
information that it will be dropped.

{^_^}    Joanne Dow, jdow@earthlink.net


  reply	other threads:[~2001-04-21  1:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 22:08 Current status of NTFS support Wayne.Brown
2001-04-20 22:31 ` Jesper Juhl
2001-04-20 22:33 ` Thomas Dodd
2001-04-20 23:48 ` Anton Altaparmakov
2001-04-20 23:52 ` Anton Altaparmakov
2001-04-20 23:55 ` Robert Szentmihalyi
2001-04-21  1:18   ` Lee Leahu
2001-04-21  1:34     ` J. Dow [this message]
2001-04-21  1:39     ` Doug McNaught
2001-04-21  2:07       ` Lee Leahu
2001-04-21  2:30         ` Tom Leete
2001-04-21  9:23       ` Anton Altaparmakov
2001-04-21  2:35 ` Ben Ford
2001-04-21  9:53 ` Dan Podeanu
2001-04-21 10:35 ` lk
2001-04-22 14:42 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2001-04-20 23:23 Wayne.Brown
2001-04-21 12:19 ` mirabilos

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='0aa401c0ca03$333fdd70$1125a8c0@wednesday' \
    --to=jdow@earthlink.net \
    --cc=lee@ricis.com \
    --cc=linux-kernel@vger.kernel.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