From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: RH 6.2 Versus RH 7.2
Date: Tue, 29 Jan 2002 23:03:12 -0500 [thread overview]
Message-ID: <008101c1a943$09f2e1e0$0100a8c0@tward> (raw)
In-Reply-To: <002a01c1a936$a1b97aa0$0100a8c0@mshome.net>
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.
A second change is the X-Windows server ois much newer, but on my 1.2 GHZ
box the little drop in spead is worth getting all the new tools. At least
for me.
----- Original Message -----
From: Amanda Lee <amanda@shellworld.net>
To: Speakup@Braille.Uwo.Ca <speakup@braille.uwo.ca>
Sent: Tuesday, January 29, 2002 9:18 PM
Subject: RH 6.2 Versus RH 7.2
>
> Hmmm I know that it is likely that RH 6.2 with Speakup enabled does not
have
> the most current version of Speakup patched into the Kernel but here's an
> interesting comment from a friend whose judgement I respect a good deal.
>
> So to the other experts herein, please share your thoughts.
>
> He prefers RH 6.2 for the following reason:
> RH 7.2 seems to be significantly slower, with lots more disk thrashing,
and
> it's
> not just X Windows (although it's also significantly slower).
>
> So my question is... What is enabled in RH 7.2 that you won't see in RH
6.2
>
> Amanda Lee
> Alexandria, VA
>
>
>
>
> _______________________________________________
> 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 [this message]
` Richard Villa
` Thomas Ward
` Mitchell
` William F. Acker WB2FLW +1-303-777-8123
` Kirk Wood
` Thomas Ward
` Victor Tsaran
` 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='008101c1a943$09f2e1e0$0100a8c0@tward' \
--to=tward@bright.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).