>
> > If that's not your way of conquering problem, switch distros. Gentoo for
> > example, compile everything with -O3 -march=i686 (might take a year with
>
> Ouch. That sounds like a painful solution. Just getting FC1
> installed/running from ISOs took a week (long story).
Hmmm, ok, this will lead you deep into the rabbit hole. It's much fun, but
there is much potential for annoyance as well. If you need a system to use
away without much fumbling, FC1 was not a bad idea at all, despite of certain
glitches (google is your friend).
> > If you are running KDE3.2, check for mem leaks with top. I had some
> > serious trouble there which made me go back to 3.1.5 for the moment.
>
> Thanks. I can run top, that much I can figure out, but how to interpret a
> memory leak is a bit beyond me. Any hints?
easy: run top in terminal, press shift+m to sort by mem usage. If things slow
down alot and some particular process rises dramatically in mem usage
(dramatically is 20-50% or even above - depending on program type, some just
need lots - and *keeps* rising tho you don't do anything, chances are there is
a mem leak. I could sit here and watch kdeinit happily hit the 90% and climb
on a 512MB machine.
BTW: somebody else noticed this? Slackware 9.1 here, used 3.2 packages from
-current branch.
Dex
___________________________________________________
.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
