linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Steffl <steffl@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Can't X be elemenated?
Date: Mon, 29 Sep 2003 14:16:57 -0700	[thread overview]
Message-ID: <3F78A149.9010505@bigfoot.com> (raw)
In-Reply-To: <200309291656.55428.france@handhelds.org>

George France wrote:
> Hello,
> 
> On Monday 29 September 2003 10:44 am, kartikey bhatt wrote:
> 
>><snip>
>>
>>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.
...

   running X does not prevent you from compiling kernel (I did it with a 
lot lower spec'd machines before). It's true that on low end machine the 
kernel compile prevents you from doing much else but that's true 
regardless of X. Some X apps eat quite a lot of memory and if you run 
openoffice and mozilla (and gnome or kde or enlightement) you end up not 
being able to do anything else. But that's not problem of X, it's a 
problem of specific applications. I have been using X (under linux) 
since times of 486 & 128MB RAM and it's been quite OK (=responsive), 
given that appropriate apps are chosen.

	erik



  parent reply	other threads:[~2003-09-29 21:17 UTC|newest]

Thread overview: 46+ 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 [this message]
2003-09-29 21:11 ` Diego Calleja García
2003-09-29 22:30 ` bill davidsen
2003-09-30  8:18 ` [OT ]Re: " Helge Hafting
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
2003-09-29 19:45 kartikey bhatt
2003-09-30  8:09 kartikey bhatt
2003-09-30  9:25 ` Matti Aarnio
2003-09-30  9:54 ` Paul Rolland
2003-09-30 13:34 ` Jesse Pollard
2003-09-30 17:50 kartikey bhatt
2003-10-01  4:32 kartikey bhatt
2003-10-01  5:00 ` Tupshin Harper
2003-10-01 15:12 ` Jesse Pollard
2003-10-01 18:27 ` Tomasz Rola
2003-10-02  8:57 ` Helge Hafting
2003-10-02 18:18   ` Herbert Poetzl
2003-10-03 14:30     ` Jesse Pollard
2003-10-02 18:37   ` Erik Steffl
     [not found] <BGWr.3eL.7@gated-at.bofh.it>
2003-10-01  8:19 ` Ihar 'Philips' Filipau

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=3F78A149.9010505@bigfoot.com \
    --to=steffl@bigfoot.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).