mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: ANN: New NTFS driver (2.0.0/TNG) now finished.
Date: Mon, 25 Mar 2002 02:26:41 +0000	[thread overview]
Message-ID: <5.1.0.14.2.20020325013452.03e53630@pop.cus.cam.ac.uk> (raw)

Hi,

This is to announce that the new NTFS Linux kernel driver 2.0.0 (formerly 
NTFS TNG) is now finished (read-only). It is for kernel 2.5.7 only and will 
be submitted to Linus for inclusion in the 2.5 kernel series when Linus 
returns from his holiday.

The driver has been tested extensively and has survived all tests so far.

It is fully compatible with kernel preemption and SMP. And it should work 
on both little endian and big endian architectures, and both on 32 and 64 
bit architectures. Note, only ia32 has actually been tested and there may 
be problems with architectures not supporting unaligned accesses. Any 
volunteers for non-ia32 architectures?

The new driver is significantly faster than the old driver (~20% in my 
tests), uses less CPU time and generally is superior to the old driver. (-:

The driver can be compiled both with gcc-2.95 and gcc-2.96. gcc-3.x has not 
been tested. (If anyone experiences compilation problems especially with 
gcc-2.95 please let me know and they will be fixed ASAP!)

To try the driver either use BitKeeper to obtain a clone from the repository:

         bk clone -q http://linux-ntfs.bkbits.net/ntfs-tng-2.5

Or if you already have a clone derived from an official kernel repository 
you only need to pull in the changes:

         bk pull http://linux-ntfs.bkbits.net/ntfs-tng-2.5

And then checkout all the files using bk -r co -q from within the 
repository directory.

For people not using BitKeeper patches for the standard 2.5.7 kernel are 
available here:

http://www-stu.christs.cam.ac.uk/~aia21/linux/linux-2.5.7-ntfs-2.0.0.patch.bz2 
(151kiB)

http://www-stu.christs.cam.ac.uk/~aia21/linux/linux-2.5.7-ntfs-2.0.0.patch.gz 
(199kiB)

http://www-stu.christs.cam.ac.uk/~aia21/linux/linux-2.5.7-ntfs-2.0.0.patch 
(796kiB)

Finally, for people wanting to browse the source code on-line, point your 
web browser at:

         http://linux-ntfs.bkbits.net:8080/ntfs-tng-2.5

Please everyone courageous enough to use a bleeding edge kernel and who is 
also an NTFS user give this a try and let me know if you encounter any 
problems! - Thanks!

Best regards,

Anton


-- 
   "I've not lost my mind. It's backed up on tape somewhere." - Unknown
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS Maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/


             reply	other threads:[~2002-03-25  2:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25  2:26 Anton Altaparmakov [this message]
2002-03-25  8:32 ` David Woodhouse
2002-03-25 11:50   ` Brad Boyer
2002-03-25 12:32     ` Alan Cox
2002-03-25 12:52   ` Jeff Garzik
2002-03-25  8:38 ` Christoph Hellwig
2002-03-25 17:17 ` Grogan
2002-03-25 19:13   ` Anton Altaparmakov
2002-03-25 19:47   ` Bill Davidsen

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=5.1.0.14.2.20020325013452.03e53630@pop.cus.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=linux-fsdevel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®