From: Jesper Juhl <juhl@eisenstein.dk>
To: Wayne.Brown@altec.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Current status of NTFS support
Date: Sat, 21 Apr 2001 00:31:41 +0200 [thread overview]
Message-ID: <3AE0B8CD.2040704@eisenstein.dk> (raw)
In-Reply-To: <86256A34.0079A841.00@smtpnotes.altec.com>
Wayne.Brown@altec.com wrote:
>
> Where does write support for NTFS stand at the moment?
>
I'll let someone who knows about that answer that part ;)
> Also, I'll have to recreate my Linux partitions after the upgrade. Does anyone
> know if FIPS can split a partition safely that was created under Windows
> 2000/NT? It worked fine for Windows 98, but I'm a little worried about what
> might happen if I try to use it on an NTFS partition.
>
Last time I checked (about 2 months ago) FIPS was not able to work with
NTFS partitions - you'll probably have to use Partition Magic or
something similar to modify the NTFS partition (but why not just create
the NTFS partition of a smaller size and then use the unpartitioned
space for a ext2 partition?).
Best regards,
Jesper Juhl - juhl@eisenstein.dk
next prev parent reply other threads:[~2001-04-20 22:25 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 [this message]
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
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=3AE0B8CD.2040704@eisenstein.dk \
--to=juhl@eisenstein.dk \
--cc=Wayne.Brown@altec.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox