pouze X spravci:
http://www.linux.cz/mailing-list/archive/199909/msg00771.html.cz
Lepsi by bol fvwm v minimalistickej konfiguracii.

netscape je prasa - tam si prilis nepomozete. Snad nainstalovat
niektoru zo starsich verzii a este k tomu len navigator
a nie communicator.
 
Namiesto xtermu pouzit rxvt (ale aktualne verzie maju
myslim zase problem s mrtvymi klavesami). V tom baliku
je aj rclock.

Pokial ide o X vseobecne, pomoze aj minimalizacia poctu
pouzitych fontov, zakazanie backing store a save under
(-bs, -su). Vykaslat sa na truecolor a pouzivat 8-bitovu
farbu. Pochopitelne si tiez nedavat ako background
nejaky obrazok.

Vo vseobecnosti sa treba vyvarovat gnome / kde aplikacii.

Najma sa ale sustredte na system ako taky - vyhadzte
nepotrebne demony (ja som svojho casu caroval aj
so sendmailom - na dialup masine nemusi bezat stale :-))
Da sa tiez pohrat s jadrom - drivery pre diskety,
CD-ROM, filesystem na CD, tlaciaren, ... sa nepouzivaju
stale a mozu sa pokojne dat ako moduly. Aj ked takato
optimalizacia uz je pri 32 MB asi zbytocna.

Nezabudnite na disky - swapovat sa obcas bude a overte
si, ci bezia v DMA rezime. Na novych jadrach to
treba bud explicitne zapnut, alebo nastavovat
niekde v rc.local cez hdparm. Swap particiu je
dobre mat blizko zaciatku disku (na vonkajsom
okraji) - tam je prenos rychlejsi.

No a ked budete nieco vacsieho kompilovat, oplati
sa X odstavit a robit to z command-line ...
***
-march optimizes for the specified processor while staying compatible
with lower architectures. -mcpu optimizes for the specified processor.
Both lower and higher processors might not be able to execute it.
<presne naopak:>
Actually, it's the other way 'round. It's more evidently so if you
remember that high -march declarations imply the corresponding -mcpu.
(i.e. "-march=athlon-xp" implies "-mcpu=athlon-xp")

"-march=i686" generates code with i686 instructions. Obviously, this
will not run on older processors. It will run with no problems though on
newer processors (including Pentium4 and AthlonXP).

"-mcpu=i686" generates code that has the instructions placed in such an
order as to be executed very fast on i686. But the instructions
themselves are i386-compatible (so the code still runs on older
processors, albeit less efficiently). In fact, the code will remain
compatible with any Intel-like CPU.

hey all talk "i386". The newer processors just learned a
few new words for very specific purposes. Like you will learn new words
if you become, say, a gardener. For talking about gardening you will
need these new words, but you will never use them (at least ideally)
while talking about any other topic. To get back to processors, if you
don't do vector graphics, you have *absolutely no* use for the MMX
instructions. Similar is true for the other new instruction sets.

i586 is special in the fact that it's timings and such are so different from
other arches that things optimized for i586 will run slower on non i586
platforms than those thing that are optimized for i386.

This horse is beaten to a bloody pulp by now...
***