linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Marco Fioretti <m.fioretti@inwind.it>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Unbloating the kernel, was: :mem=16MB laptop testing
Date: Tue, 14 Oct 2003 05:02:43 -0700	[thread overview]
Message-ID: <20031014120243.GO16158@holomorphy.com> (raw)
In-Reply-To: <HMQWM7$61FA432C2B793029C11F4F77EEAABD1F@libero.it>

At some point in the past, I wrote:
>> So I tried mem=16m on my laptop (stinkpad T21). I made the following
>> potentially useless observations:
[snip]
>> I guess the upshot is "unbloating" the kernel wouldn't do much good
>> anyway, since luserspace isn't in any kind of shape to run in this kind
>> of environment anymore either.

On Tue, Oct 14, 2003 at 01:44:31PM +0200, Marco Fioretti wrote:
> Wrong. (please read till the end, this is not academic, but a real
> call to arms!) Have a look at http://www.rule-project.org/en/,
> specifically the pages: http://www.rule-project.org/en/sw/kdrive.php
> (how we do without X, solving half of the problem)

Hearing this is about the happiest I can be to be proven wrong.


On Tue, Oct 14, 2003 at 01:44:31PM +0200, Marco Fioretti wrote:
> http://www.rule-project.org/en/test/ (the kind of machines we must
> work with) There are still a *lot* of lightweight applications giving
> real functionality without bloat. Of course, they can make little in
> these conditions if constantly swapped out from > the Kernel and/or X.
> With 16 or 24 MB or RAM even half a meg less is very important. We at
> RULE are doing what we can to select light GUI applications and test
> them with kdrive, but have no expertise to look after the kernel.
> Any help whatsoever in keeping 2.6 as light as possible, and to
> recompile stock 2.4 kernels to lighten them is really needed.
> The most important part of this is that it is not a programming
> contest, just for the sake of it.
> There are literally thousands of schools, all over the world, which simply
> cannot afford any money on computers. The "HW is cheap" slogan is
> very cruel when recited in places where 64 MB of RAM are one month's
> salary. I am not kidding. All these schools have is donated computers
> 5+ years old: even if they had the money they could not find spare parts
> from them. After food, medicines and shelter a good education is
> essential to make a decent living.
> It is extremely embarassing to tell these students "you can do
> without expensive MS SW, just find the money for a PC almost as
> expensive as those which will run Windows". A lightweight Linux is
> needed to many more people than the full featured one Thank you in
> advance for any support,
>              Marco Fioretti, RULE project coordinator
> PS: Oh, and while I'm at it, I'll even dare to ask for RULE network volunteers, see
> http://www.rule-project.org/en/rule_by_email.php

"$FOO is cheap" is a copout for sure; in the wrong country or for the
wrong people the limitation to "performant" hardware is a lethal blow
to usability. I'm not sure how to say how glad I am to hear of a direct
attack on this issue.

If you and/or your cohorts could inform us of kernel usability issues,
especially with 2.6, I would be much obliged (all the more so for a cc:).


-- wli

  reply	other threads:[~2003-10-14 11:59 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 11:44 Unbloating the kernel, was: :mem=16MB laptop testing Marco Fioretti
2003-10-14 12:02 ` William Lee Irwin III [this message]
2003-10-14 13:24 ` Rik van Riel
2003-10-14 14:30   ` jlnance
2003-10-14 14:54     ` Richard B. Johnson
2003-10-14 16:27     ` Maciej Zenczykowski
2003-10-14 17:33       ` John Bradford
2003-10-14 17:51         ` Richard B. Johnson
2003-10-15 12:43         ` Jan-Benedict Glaw
2003-10-15 13:06           ` William Lee Irwin III
2003-10-15 16:52             ` H. Peter Anvin
2003-10-15 13:08           ` Nick Piggin
2003-10-17 11:50             ` Jan-Benedict Glaw
2003-10-17 23:21               ` Nick Piggin
2003-10-14 18:35       ` tabris
2003-10-14 21:11       ` Roger Larsson
2003-10-15 11:45       ` Jan-Benedict Glaw
2003-10-15 13:06         ` William Lee Irwin III
2003-10-15 13:22           ` Jan-Benedict Glaw
2003-10-24 15:47       ` bill davidsen
2003-10-15  6:06     ` Sandy Harris
2003-10-24 15:59       ` bill davidsen
2003-10-24 16:55         ` M. Fioretti
2003-10-24 17:14           ` bill davidsen
2003-10-25 17:42             ` Geert Uytterhoeven
2003-10-28  9:12           ` Rob Landley
2003-10-14 21:43 ` Unbloating the kernel, action list M. Fioretti
2003-10-14 22:30   ` Martin J. Bligh
2003-10-14 22:56     ` cliff white
2003-10-15 12:48       ` Jan-Benedict Glaw
2003-10-15 13:10         ` William Lee Irwin III
2003-10-15 15:05           ` Jan-Benedict Glaw
2003-10-19 11:21             ` Adrian Bunk
2003-10-21  8:04               ` Jan-Benedict Glaw
2003-10-15 18:16           ` Gabriel Paubert
2003-10-16  5:19             ` Jan-Benedict Glaw
2003-10-16  8:16               ` Gabriel Paubert
2003-10-16 16:16                 ` Jan-Benedict Glaw
2003-10-17 20:26         ` M. Fioretti
2003-10-17 20:10     ` M. Fioretti

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=20031014120243.GO16158@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.fioretti@inwind.it \
    /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).