public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john slee <indigoid@higherplane.net>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: Colonel <klink@clouddancer.com>, linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: Thrashing WITHOUT swap.
Date: Tue, 26 Jun 2001 22:36:04 +1000	[thread overview]
Message-ID: <20010626223604.O30872@higherplane.net> (raw)
In-Reply-To: <01062518321604.01008@starship>

On Mon, Jun 25, 2001 at 06:32:16PM +0200, Daniel Phillips wrote:
> On Monday 25 June 2001 18:16, Colonel wrote:
> > Had you tried fvwm-1.24r (the original) ?  It was designed long ago to
> > be lean and fast on the desktop.  I know it whips KDE.
> 
> Yes, I did.  It's even faster than xfce but there's one problem: it just
> isn't very much like a modern desktop.  xfce is, to a surprising degree, like
> a modern desktop.  It's roughly equivalent to W95 I'd say - more
> sophisticated in some areas, less in others.  Oh, did I mention I haven't run
> into a bug yet?  It's true.

firstly, i better have at least one paragraph related to the kernel ;)
2.4 is a *much* better desktop than 2.2 for me.  make -j32 bzImage and
other large amounts of processes/io don't destroy the interactivity of
my X session anymore.

(wearing asbestos suit)

i have run, as full-time desktops, kde-1.x, enlightenment, windowmaker
and fvwm-* on 10baseT switched networks with Tektronix XP400 terminals
hosted on linux (and of course on xfree86-based normal linux desktops)

in both cases the better and "more interactive" window manager was not
fvwm or wmaker.  sure, E can be a pig with the right theme, but with a
nice lightweight theme it is great. E certainly seems lots better over
ethernet than the other two...

kde 1.x of course was absolutely ghastly over a network (gnome not too 
prominent in those days, so i didn't get a chance to try it)

lately i have been trying to make kde2 run smooth like my E setup, but
there are some niggles, and i wouldn't bother if i had less than 256mb
ram.

j.

-- 
"Bobby, jiggle Grandpa's rat so it looks alive, please" -- gary larson

  reply	other threads:[~2001-06-26 12:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-24 19:47 Thrashing WITHOUT swap Maciej Zenczykowski
2001-06-24 20:07 ` Jonathan Morton
2001-06-24 21:36 ` Alan Cox
2001-06-25  8:13   ` Xavier Bestel
2001-06-25 16:14     ` Mike Galbraith
2001-06-25  9:21 ` Helge Hafting
2001-06-25 16:02   ` [OT] " Daniel Phillips
     [not found]   ` <9h7ne1$1bn$1@ns1.clouddancer.com>
2001-06-25 16:16     ` Colonel
2001-06-25 16:32       ` Daniel Phillips
2001-06-26 12:36         ` john slee [this message]
2001-06-27 12:52 ` Ookhoi

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=20010626223604.O30872@higherplane.net \
    --to=indigoid@higherplane.net \
    --cc=klink@clouddancer.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillips@bonn-fries.net \
    /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