Linux Newbie help
 help / color / mirror / Atom feed
From: Petre Bandac <g38@rdsbv.ro>
To: linux-newbie@vger.kernel.org
Subject: Re: Journaling File Systems...
Date: Thu, 24 Oct 2002 21:21:32 +0300	[thread overview]
Message-ID: <200210242121.32961.g38@rdsbv.ro> (raw)
In-Reply-To: <1035468047.15381.81.camel@zebra.vil.ite.mee.com>

use reiserfs - I use it since slackware 8.0 appeared and have no complaints

petre

On Thursday 24 October 2002 17:00 Anno Domini, Paul Furness wrote using one of 
his keyboards:
> Ext 3 has some slowness, I guess, but I use it without any real
> headaches for my workstation and a couple of servers (not particularly
> I/O intensive servers, mind you).
>
> Want to have a play with ReiserFS because of the speed. Don't know about
> the others.
>
> From what I've read, ReiserFS might be worth going for, depending on
> what you are doing on your workstation.
>
> P.
>
> On Thu, 2002-10-24 at 11:46, Bryan Simmons wrote:
> > When I first installed Linux in 1998, I don't remember there being any
> > other file system to use other than Ext2.  After 2000, I went a few
> > years without Linux.  This time around, when installing Linux, I noticed
> > I could use anything from Ext3 to ReiserFS to JFS etc... I steered clear
> > of these and chose Ext2 because it was all that I knew.  Now, after
> > reading an article on journaling file-systems in Linux Magazine, I am
> > convinced I need to use this technology on my next system (which should
> > arrive Friday).
> >
> > Here's my question:  what would you guys suggest as a good file system
> > for a client?  I use my system for programming, multimedia (home movies,
> > mp3s, pics, etc...).  So far, it seems good to go with Reiser.  JFS and
> > XFS seem like overkill for a client and Ext3 is not efficient enough.
> >
> > What are your opinions?
> > --
> > Regards,
> >
> > Bryan Simmons
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >
> >  On Integrity:
> >
> >  "I'm going to be as good as they let me and
> >   as mean as they make me, and they all know
> >   that.  I don't ever lie. If I tell you a
> >   rooster can fly, get the harness."
> >
> >    --Burl Cain, Louisiana State Pen Warden
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-newbie"
> > in the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.linux-learn.org/faqs

-- 
 21:19:41 up  2:32,  1 user,  load average: 0.08, 0.12, 0.18

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2002-10-24 18:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24 10:46 Journaling File Systems Bryan Simmons
2002-10-24 14:00 ` Paul Furness
2002-10-24 18:21   ` Petre Bandac [this message]
2002-10-24 21:15     ` problems with dual boot Abhijit Vijay
2002-10-24 21:24       ` Bryan Simmons
2002-10-25  1:45       ` lawson_whitney
2002-10-26  4:08         ` cr
2002-10-25 18:19 ` Journaling File Systems Bryan Whitehead

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=200210242121.32961.g38@rdsbv.ro \
    --to=g38@rdsbv.ro \
    --cc=linux-newbie@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