From: Michael Whapples <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Finding a suitable filesystem
Date: Mon, 07 Jan 2008 15:54:36 +0000 [thread overview]
Message-ID: <1199721276.4478.22.camel@localhost> (raw)
In-Reply-To: <20080107000425.GA14602@localhost.localdomain>
>From a lot of googling about I was coming to the ext2 conclusion.
Out of interest why would a journaling FS wear out the drive quicker? I
haven't seen comment of this in my searches.
Thanks
Michael Whapples
On Sun, 2008-01-06 at 17:04 -0700, Gregory Nowak wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I think that ext2 would be your best bet. The projects I'm about to
> mention, can work with ext2, but aren't able to work with the journal
> part of ext3. Also, you don't want a journaling file system on a flash
> drive, since that would make the drive wear out faster.
>
> http://ext2fsd.sourceforge.net/
> This is free, as in free source, but I haven't used it, due to the
> fact that it was still unstable beta software back when I was needing
> to access ext2 partitions under the other popular os. Things may have
> changed there since.
>
> http://www.fs-driver.org/
> This is what I personally use, and I've found it to be very stable and
> reliable. It's freeware, but isn't free source, which doesn't bother
> me, though I realize it might bother some. It runs under nt4, 2000, as
> well as x86 versions of xp, and 2003. I don't know about vista.
>
> I also remember there was a set of tools which could read ext2
> partitions, and do very limited write operations. These ran under dos,
> win95, 98, and me. I however don't have the url for that bookmarked,
> and am unable to find it. If it's something you're interested in, then
> maybe someone else will post the url for that. Hth.
>
> Greg
>
>
>
> On Sun, Jan 06, 2008 at 05:46:15PM +0000, Michael Whapples wrote:
> > Hello,
> > I am wondering what filesystem is best for a USB memory stick. The
> > problem is that fat/fat32 is very poor on the permissions, but most
> > systems can read/write it, whereas ntfs is poorly supported under Linux
> > (and I am not certain about how good the permission support is) and
> > things like ext3, reiserfs and other unix FSs aren't supported on
> > windows. So is there mount options for fat/fat32 which improves the case
> > somewhat under Linux, or might ntfs be a good compromise as most of the
> > Linux systems I will be using it on will be mine so I can install
> > ntfs-3g or other drivers (and windows 9x seems to have disappeared
> > sufficiently that I won't have too many of those), or is there a windows
> > driver for one of the unix filesystems (and if I want to be able to use
> > it on more than just my machine I suppose I could make a small fat32
> > partition where I could have the driver available should a windows
> > machine not have it).
> >
> > Thanks for any pointers to information or advice people can give.
> >
> > From
> > Michael Whapples
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> - --
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
>
> - --
> Free domains: http://www.eu.org/ or mail dns-manager@EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFHgWyJ7s9z/XlyUyARAvHsAKClF1IQERzdKPyAJnXcUOiO4yU6RQCgiWkv
> VHPWSxkua7KSwkA55i/C5pI=
> =dZI1
> -----END PGP SIGNATURE-----
>
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Michael Whapples
` Gregory Nowak
` Michael Whapples [this message]
` Joseph C. Lininger
` Joseph C. Lininger
` Alex Snow
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=1199721276.4478.22.camel@localhost \
--to=mwhapples@aim.com \
--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).