From: Tom Leete <tleete@mountain.net>
To: lee@ricis.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Current status of NTFS support
Date: Fri, 20 Apr 2001 22:30:34 -0400 [thread overview]
Message-ID: <3AE0F0CA.EE16AB3D@mountain.net> (raw)
In-Reply-To: <86256A34.0079A841.00@smtpnotes.altec.com> <01042020185806.00845@linux> <m34rvjuj3y.fsf@belphigor.mcnaught.org> <01042021072007.00845@linux>
Lee Leahu wrote:
>
> On Friday 20 April 2001 20:39, you wrote:
> > 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
>
> my boss rememebres reading a very indepth article in one of the msdn
> magazines. i could scan the articles in and compress them and send them to
> the developers. i want to help the ntfs movement on linux. would somebody be
> willing to teach me the ropes of reverse engineering of software. i am a
> faster learner, and very interested in reverse engineering of software.
Copyright interferes with that route, and I'm sure Microsoft would be happy
to
enforce that. Links to the msdn.microsoft.com library/kb articles would be
good.
> i have access to the msdn library and maganzies and have lot of free time for
> dedicated ntfs code hacking.
Also good.
Cheers,
Tom
--
The Daemons lurk and are dumb. -- Emerson
next prev parent reply other threads:[~2001-04-21 2:31 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
2001-04-21 2:07 ` Lee Leahu
2001-04-21 2:30 ` Tom Leete [this message]
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=3AE0F0CA.EE16AB3D@mountain.net \
--to=tleete@mountain.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.