From: Anton Altaparmakov <aia21@cam.ac.uk>
To: ntfsdev <linux-ntfs-dev@lists.sourceforge.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: NTFS driver 2.1.5a released for Linux kernel 2.4.23
Date: Tue, 02 Dec 2003 15:58:17 +0000 [thread overview]
Message-ID: <1070380697.7156.21.camel@imp> (raw)
The latest NTFS driver (2.1.5a) is now available for Linux kernel
2.4.23.
This updated release for Linux kernel 2.4.23 also includes a fix for a
problem encountered by at least two Windows XP users when accessing
certain fragmented files.
As always you can download a patch for the kernel from our website:
http://linux-ntfs.sf.net/downloads.html
Or you can pull the changes from our bitkeeper repository:
http://linux-ntfs.bkbits.net/ntfs-2.4
Note that the latest NTFS version (2.1.5) is also present in the current 2.6.0-test kernel and has been since 2.6.0-test9.
Happy NTFSing! (-:
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ &
http://www-stu.christs.cam.ac.uk/~aia21/
reply other threads:[~2003-12-02 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1070380697.7156.21.camel@imp \
--to=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
/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