From: J Sloan <joe@tmsusa.com>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.5.6 Interactive performance
Date: Sat, 09 Mar 2002 20:55:23 -0800 [thread overview]
Message-ID: <3C8AE73A.7040807@tmsusa.com> (raw)
In-Reply-To: <NFBBKFIFGLNJKLMMGGFPKEPDCFAA.charles-heselton@cox.net> <1015734229.858.4.camel@phantasy>
Robert Love wrote:
>The 2.5 tree also has most of these toys, and is a better place for this
>development IMO. Personally, I'd stay away from these all-in-one silly
>patches that are floating around these days. Your safest bet is just
>stock 2.4.18 or whatever is latest, although the above addons are all at
>varying levels of "stable" and "safe".
>
Just my $.02 -
After futzing around with all the various patches
floating around, I've found the -aa releases to be
a pleasant surprise all around. I generally run -aa
on my home and office workstations, as well as
the web/mail/dns/squid/firewall servers I manage.
I find I get 95% of the benefits of the bleeding
edge, with 5% of the effort - for instance:
untar 2.4.18
apply 2.4.19-pre2 patch
apply 2.4.19-pre2aa1 patch *
configure, compile, boot and enjoy.
* for nvidia drivers, back out xfs and 20_pte-highmem patches
Joe
next prev parent reply other threads:[~2002-03-10 4:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 19:55 Kernel 2.5.6 Interactive performance Dieter Nützel
2002-03-10 1:00 ` Charles Heselton
2002-03-10 1:11 ` Dieter Nützel
2002-03-10 1:15 ` Charles Heselton
2002-03-10 4:23 ` Robert Love
2002-03-10 4:38 ` Mike Fedyk
2002-03-10 6:05 ` Robert Love
2002-03-10 6:18 ` Charles Heselton
2002-03-10 4:55 ` J Sloan [this message]
2002-03-11 1:05 ` Andrea Arcangeli
[not found] <003301c1c7fd$a67d08f0$bb187143@amer.cisco.com>
2002-03-10 7:23 ` Charles Heselton
-- strict thread matches above, loose matches on Subject: below --
2002-03-08 0:14 2.5.6-3 -- preempt_schedule unresolved in snd-pcm.o, snd-emu10k1-synth.o and snd-emu10k1.o Miles Lane
2002-03-09 18:55 ` Kernel 2.5.6 Interactive performance Dan Mann
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=3C8AE73A.7040807@tmsusa.com \
--to=joe@tmsusa.com \
--cc=linux-kernel@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