From: Yuri Per <yuri@acronis.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>,
Martin von Loewis <loewis@informatik.hu-berlin.de>
Cc: linux-kernel@vger.kernel.org,
Linux-ntfs@tiger.informatik.hu-berlin.de,
linux-ntfs-dev@lists.sourceforge.net
Subject: Re: [Linux-ntfs] Re: [Linux-NTFS-Dev] Re: ANN: NTFS new release available (1.1.15)
Date: Mon, 28 May 2001 17:08:39 +0400 [thread overview]
Message-ID: <3B124DD7.1060908@acronis.com> (raw)
In-Reply-To: <3B11E3F1.1090400@acronis.com> <5.1.0.14.2.20010526011903.00aab050@pop.cus.cam.ac.uk> <5.1.0.14.2.20010526000503.04716ec0@pop.cus.cam.ac.uk> <5.1.0.14.2.20010526011903.00aab050@pop.cus.cam.ac.uk> <5.1.0.14.2.20010527123154.00a96640@pop.cus.cam.ac.uk> <200105271253.OAA22557@pandora.informatik.hu-berlin.de> <3B11E3F1.1090400@acronis.com> <5.1.0.14.2.20010528125630.04729ba0@pop.cus.cam.ac.uk>
Anton Altaparmakov wrote:
> Does anyone know what NTFS version the NT 3.1 / 3.51 volumes had? If I
> know I can make sure we don't mount such beasts considering we know
> the driver would fail on them... - I am aware of only one person stil
> using NT 3.51 and he doesn't believe in the NTFS Linux driver any
> more, so I guess we can just say we support NT 4.0 and above only.
NT 3.51 uses exactly the same version of NTFS as NT 4.0 does.
Yuri
next prev parent reply other threads:[~2001-05-28 13:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-25 23:49 ANN: NTFS new release available (1.1.15) Anton Altaparmakov
2001-05-25 23:59 ` Jeff Garzik
2001-05-26 0:42 ` [Linux-NTFS-Dev] " Anton Altaparmakov
2001-05-27 11:23 ` [Linux-ntfs] " Martin von Loewis
2001-05-27 11:45 ` Anton Altaparmakov
2001-05-27 12:53 ` Martin von Loewis
2001-05-28 5:36 ` Yuri Per
2001-05-28 11:10 ` Martin von Loewis
2001-05-28 12:01 ` Anton Altaparmakov
2001-05-28 13:08 ` Yuri Per [this message]
2001-05-28 14:49 ` Anton Altaparmakov
2001-05-29 0:50 ` Jeff V. Merkey
2001-05-29 8:18 ` Martin von Loewis
2001-05-29 16:42 ` Jeff V. Merkey
2001-05-27 22:37 ` Anton Altaparmakov
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=3B124DD7.1060908@acronis.com \
--to=yuri@acronis.com \
--cc=Linux-ntfs@tiger.informatik.hu-berlin.de \
--cc=aia21@cam.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=loewis@informatik.hu-berlin.de \
/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.