mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pawel Kot <pkot@bezsensu.pl>
To: Martin Olsson <mnemo@minimum.se>
Cc: linux-kernel@vger.kernel.org, linux-ntfs-dev@lists.sourceforge.net
Subject: Re: Why is proper NTFS-driver difficult?
Date: Sun, 30 May 2004 22:33:54 +0200	[thread overview]
Message-ID: <200405302233.55108.pkot@bezsensu.pl> (raw)
In-Reply-To: <40BA1FD5.9080902@minimum.se>

On Sunday 30 May 2004 19:54, Martin Olsson wrote:

Hi Martin,

> I was wondering why is there no Linux NTFS-driver which allows full
> writing etc? Is there something that makes this particular difficult to
> implement? I mean Linux supports so many file systems, why has proper
> NTFS support been neglected?

Because it is not easy. NTFS has very sophisticated structure, not documented 
anywhere but already reverse engineered and partially documented at 
linux-ntfs project page (http://linux-ntfs.sf.net/).

As I said this is not easy task and as such it is time consuming. All 
linux-ntfs developers are volunteers and not paid for this work. It means 
that all code is written in the free time. Much time was also spent on 
helping users (this will change now, see the manifest on the project page).

To summarize, the write support will appear sooner or later, if you volunteer 
to help, you are very welcome.

I'm ccing ntfs-dev list which is a better place to discuss such topics.

take care,
pkot
-- 
mailto:pkot@bezsensu.pl
http://www.gnokii.org/

  parent reply	other threads:[~2004-05-30 20:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30 17:54 Martin Olsson
2004-05-30 18:37 ` Felipe Alfaro Solana
2004-05-30 19:48   ` Denis Vlasenko
2004-05-30 20:17 ` Bernd Petrovitsch
2004-05-30 20:33 ` Pawel Kot [this message]
2004-05-30 20:54 ` Giuseppe Bilotta
2004-05-31  5:20 ` Dax Kelson
2004-06-01 20:01   ` Erik Andersen

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=200405302233.55108.pkot@bezsensu.pl \
    --to=pkot@bezsensu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-ntfs-dev@lists.sourceforge.net \
    --cc=mnemo@minimum.se \
    /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

all inboxes | Powered by JetHome®