From: Doug McNaught <doug@wireboard.com>
To: lee@ricis.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Current status of NTFS support
Date: 20 Apr 2001 21:39:13 -0400 [thread overview]
Message-ID: <m34rvjuj3y.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <86256A34.0079A841.00@smtpnotes.altec.com> <01042101555600.03154@blackbox> <01042020185806.00845@linux>
In-Reply-To: Lee Leahu's message of "Fri, 20 Apr 2001 20:18:58 -0500"
Lee Leahu <lee@ricis.com> writes:
> 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?
It's dangerous because NTFS is a proprietary format, and the full
rules for updating it (including journals etc) are known only to
Microsoft and those that have signed Microsoft NDAs. If you update it
incorrectly it gets corrupted and you will lose data. It's certainly
possible to reverse-engineer these rules, but very difficult and
time-consuming.
-Doug
--
The rain man gave me two cures; he said jump right in,
The first was Texas medicine--the second was just railroad gin,
And like a fool I mixed them, and it strangled up my mind,
Now people just get uglier, and I got no sense of time... --Dylan
next prev parent reply other threads:[~2001-04-21 1:39 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
2001-04-21 1:39 ` Doug McNaught [this message]
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=m34rvjuj3y.fsf@belphigor.mcnaught.org \
--to=doug@wireboard.com \
--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