linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: kartikey bhatt <kartik_me@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: [OT ]Re: Can't X be elemenated?
Date: Tue, 30 Sep 2003 10:18:31 +0200	[thread overview]
Message-ID: <3F793C57.10403@aitel.hist.no> (raw)
In-Reply-To: LAW11-F18b4SaFMwr9y00007564@hotmail.com

kartikey bhatt wrote:
> Hi Linus.
> 
> I read your reply to a person worried about the future of linux. It was a
> satisfactory reply; I hope to get a satisfactory reply for this one also.
> 
> Can't X be elemenated?

Trivially.  X is a stand-alone app, this is as easy as not running
it.  (Or not installing it, if you don't want to spend the disk space.)
That means no GUI apps, but there are plenty of programs that
don't need the GUI.

> I mean to say kernel level support for graphics device drivers and special
> routines for accessing it directly; rest will be done by user space widget
> libraries (or say a kernel space light widget library which can be 
> customized
> by user space libraries).
> 
Then you move the "bloat" to the kernel, where it does more
damage than were it is now.  No real win, but definitely loss.

> Why am I asking this?
> 
> 1st. X is bloat. Though it's good for server environments. For desktop pcs
> it's too heavy. On my machine (PIII500 with 128MB RAM) I have to choose 
> from
> either to run X or compile 2.6.0-test6.

You're wrong.  X is lightweight.  I remember running it on a 386
with 8M RAM - much faster than windows 3.1 of that time.

I guess you're merely running some very heavy apps.
1. Get a lightweight window manager.  There are many
    to chooce from, such as icewm, fwwm, twm, openbox,...
    Don't run heavy stuff like enlightenment.  It looks good,
    but it is meant for bigger machines than yours.
2. Avoid gnome and kde whenever possible.  These two wants more
    than 128M.  And possibly more cpu too.
3. Make sure you have a x server that uses acceleration
    (Check the x server log) and make sure you aren't
    running an IDE disk in pio mode and without
    interrupt unmasking. (take a look at hdparm)

You should now have a lean fast system compared to windows.

> 
> 2nd. It's process based client/server architecture is a bottleneck. It's 
> not
> as interactive as is supposed to be.
Likely some other problem, see above.


> 3rd. Most important. I can't impress or convince my window(crash)(TM) user
> friends, relatives (who saw X running on my pc) to use Linux.
> 
Can't do that with an ill-configured system.  Oh, and make sure
the comparison is sensible - are they running windows on
128M 500MHz machines too?

> 4th. I want to see desktop being ruled by Linux.
> 
Linux is good enough for that already.  Companies are changing
to linux on the desktops as a cost-cutting measure - no
licences and slightly lower demands for hardware. And there
is enough apps too!  (Not as many as for windows, but _enough_,
more is coming.)

Now, "good enough" is no reason to stop getting better.  But
integrating X into the kernel is not the way to go, particularly because
it don't buy us much.

X not in the kernel means a fault in X don't take out the kernel
(crashing the machine) either.  Seems you like that aspect of
it. Also, X supports networking as is.  Try running apps
remotely with windows - you'll have to buy third party
software first and it isn't as good.
I routinely log in to my office pc from home, and run GUI apps
over and ADSL line.  It just works.

> "Present" is in our hands; we are ruling servers.
> You said "Linux, world domination fast".
> If my wish is fulfilled, I am sure, one day, You (Mr. Linus) and I will
> be saying "Linux, world domination completed".
:-)

Helge Hafting



  parent reply	other threads:[~2003-09-30  8:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29 14:44 Can't X be elemenated? kartikey bhatt
2003-09-29 14:51 ` Leonard Milcin Jr.
2003-09-29 15:05   ` Gábor Lénárt
2003-09-29 15:10 ` Erik Hensema
2003-09-29 15:11 ` Valdis.Kletnieks
2003-09-29 20:56 ` George France
2003-09-29 21:04   ` Erik Bourget
2003-09-29 21:16   ` Erik Steffl
2003-09-29 21:11 ` Diego Calleja García
2003-09-29 22:30 ` bill davidsen
2003-09-30  8:18 ` Helge Hafting [this message]
2003-09-30 18:48 ` Paul Jakma
2003-09-30 19:30   ` Krishna Akella
2003-09-30 20:21     ` David Lang
2003-09-30 20:46       ` Krishna Akella
2003-09-30 20:45         ` David Lang
2003-10-07  4:04       ` Pavel Machek
2003-10-07  8:23         ` Giacomo A. Catenazzi
2003-10-07 12:18           ` Pavel Machek
2003-10-07 12:46             ` [OT] " Giacomo A. Catenazzi
2003-10-07 12:52             ` Måns Rullgård
2003-10-07 14:34               ` Valdis.Kletnieks
2003-10-07 14:47             ` Jesse Pollard
2003-10-07 15:37               ` Pavel Machek
2003-10-07 19:07                 ` David Lang
2003-10-07 19:16                   ` Pavel Machek
2003-10-07 20:09                   ` jlnance
2003-10-07 18:52             ` David Lang
2003-09-30 21:51     ` J.A. Magallon
2003-10-01 14:54     ` Jesse Pollard
2003-10-01  8:27   ` John Bradford

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=3F793C57.10403@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=kartik_me@hotmail.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;
as well as URLs for NNTP newsgroup(s).