public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Ford <ben@kalifornia.com>
To: Wayne.Brown@altec.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Current status of NTFS support
Date: Fri, 20 Apr 2001 19:35:37 -0700	[thread overview]
Message-ID: <3AE0F1F9.7020704@kalifornia.com> (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 noticed that it's
>still marked "Dangerous" in the kernel configuration.  This is important to me
>because it looks like I'll have to start using it next week.  My office laptop
>is going to be "upgraded" from Windows 98 to 2000.  Of course, I hardly ever
>boot into Windows any more since installing a Linux partition last year.  But
>our corporate email standard forces me to use Lotus Notes, which I run under
>Wine.   The Notes executables and databases are installed on my Windows
>partition.  The upgrade, though, will involve wiping the hard drive, allocating
>the whole drive to a single NTFS partition, and reinstalling Notes after
>installing Windows 2000 .  That means bye-bye FAT32 partition and hello NTFS.  I
>can't mount it read-only because I'll still have to update my Notes databases
>from Linux.  So how risky is this?
>
>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.
>
>I'd appreciate any advice or help anyone can give me.  There's just no way I can
>stand going back to using anything but Linux for my daily work.
>

Why not just use FAT?  Windows2k supports it . . .

-- 
Three things are certain:
Death, taxes, and lost data
Guess which has occurred.
- - - - - - - - - - - - - - - - - - - -
Patched Micro$oft servers are secure today . . . but tomorrow is another story!




  parent reply	other threads:[~2001-04-21  3:41 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
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 [this message]
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=3AE0F1F9.7020704@kalifornia.com \
    --to=ben@kalifornia.com \
    --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