public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn Ervin" <GlennErvin@cableone.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: A computer issue, how should I deal with this? Best solution?
Date: Sun, 24 Jun 2007 11:16:27 -0500	[thread overview]
Message-ID: <007e01c7b67b$04e90080$b100a8c0@AveratecLaptop> (raw)
In-Reply-To: <006701c7b673$4f0d1460$ab00a8c0@tenstac>

As far as NTFS being more reliable than FAT32, I would argue on personal 
experience  that I have had more drives go bad that were running NTFS than 
those running FAT32.
I have owned more drives formatted with FAT32, so I should have experienced 
more FAT32 file system problems, yet I have experienced the opposite.
Now this can be due to mechanical problems un-related to the file system, 
but it is often unclear whether the hard-drive crash was due to an inability 
for the file system being able to repair itself.
Glenn
----- Original Message ----- 
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Sunday, June 24, 2007 10:21 AM
Subject: Re: A computer issue, how should I deal with this? Best solution?


FAT32 is also much more likely to be corrupted that NFTS
if you have a BSOD or something, and I never use it for the
windows partition. The reason I suggested FAT32 was
because I thought NTFS was still read only on linux but
Greg pointed out it's now possible

http://www.ntfs-3g.org/

I have had many a FAT32 file corruption over the years
but so far not one NTFS. OMG maybe microsoft did
something fairly decent. hehe

  -- Doug

_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Keith Hinton
 ` Willem van der Walt
 ` Doug Sutherland
   ` Gregory Nowak
   ` Glenn Ervin
     ` Gregory Nowak
       ` Gregory Nowak
         ` Butch Bussen
           ` Doug Sutherland
             ` Gaijin
             ` Butch Bussen
       ` Glenn Ervin
     ` Doug Sutherland
       ` Glenn Ervin
         ` Doug Sutherland
           ` Glenn Ervin
             ` Doug Sutherland
               ` Butch Bussen
                 ` Glenn Ervin
                 ` Doug Sutherland
                   ` Steve Holmes
                     ` Doug Sutherland
                       ` Glenn Ervin [this message]
                         ` Gregory Nowak
                           ` Glenn Ervin
                             ` Gregory Nowak
           ` Butch Bussen
       ` Butch Bussen
 ` John Heim
 ` Gaijin

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='007e01c7b67b$04e90080$b100a8c0@AveratecLaptop' \
    --to=glennervin@cableone.net \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).