From: "Victor Tsaran" <tsar@sylaba.poznan.pl>
To: <speakup@braille.uwo.ca>
Subject: Re: RH 6.2 Versus RH 7.2
Date: Wed, 30 Jan 2002 20:41:40 +0100 [thread overview]
Message-ID: <004101c1a9c8$aa093cd0$0100a8c0@Cybertsar> (raw)
In-Reply-To: <00ae01c1a9ab$f06d9620$0100a8c0@tward>
NTFS works in the same way as Ext3 does. Let's not take away from Ms$
whatever is good in their OS.
Vic
----- Original Message -----
From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, January 30, 2002 5:26 PM
Subject: Re: RH 6.2 Versus RH 7.2
> Well, ext3 has many other advantages than just proformence. It supports
> journaling, and is much more stable to boot.
> I actually switched off my computer a number of times to see if I could
kill
> the file system, and it remained in tact. Try that with a MS fs or the
ext2
> file system, and it would be screwed.
> Anyone wants to stay with older technology when there is improved
technology
> can go ahead. Another man's loss is another man's gain.
>
> ----- Original Message -----
> From: Kirk Wood <cpt.kirk@1tree.net>
> To: <speakup@braille.uwo.ca>
> Sent: Wednesday, January 30, 2002 7:58 AM
> Subject: Re: RH 6.2 Versus RH 7.2
>
>
> > > Well, I've noticed that slow down in spead myself. One way to help
spead
> > > things up is to use the ext3 fs which works much better than ext2.
> > > One major difference between 6.2 and 7.2 is that 7.2 comes with the
> kudzu
> > > pnp hardware maniger. Kudzu tracks new and removed hardware, and
> attempts to
> > > configure it for you.
> >
> > Oh please tell me that this is not a representation of what is in store
> > for the linux comunity. Switching to an more effecient file system for
> > poor OS performance sounds like a m$ thing.
> >
> > As for Kudzu, from what I have seen it is more of a boot thing. You can
> > certainly turn it off and I would do so if you aren't adding and
> > subtracting hardware. I mean why run it? I suppose so that you could
avoid
> > a reboot after 65 days of adding no new hardware and deciding you wanted
> > something. Oh wait, you had to shut it down to connect it anyway. Or if
> > not, you could always restart the service midstream anyway.
> >
> > =======
> > Kirk Wood
> > Cpt.Kirk@1tree.net
> >
> > Nowlan's Theory:
> > He who hesitates is not only lost, but several miles from
> > the next freeway exit.
> >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Amanda Lee
` Thomas Ward
` Richard Villa
` Thomas Ward
` Mitchell
` William F. Acker WB2FLW +1-303-777-8123
` Kirk Wood
` Thomas Ward
` Victor Tsaran [this message]
` Darrell Shandrow
Dawes, Stephen
Dawes, Stephen
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='004101c1a9c8$aa093cd0$0100a8c0@Cybertsar' \
--to=tsar@sylaba.poznan.pl \
--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).