All of lore.kernel.org
 help / color / mirror / Atom feed
From: jlnance@unity.ncsu.edu
To: linux-kernel@vger.kernel.org
Subject: Re: Unbloating the kernel, was: :mem=16MB laptop testing
Date: Tue, 14 Oct 2003 10:30:47 -0400	[thread overview]
Message-ID: <20031014143047.GA6332@ncsu.edu> (raw)
In-Reply-To: <Pine.LNX.4.44.0310140917540.3754-100000@chimarrao.boston.redhat.com>

On Tue, Oct 14, 2003 at 09:24:17AM -0400, Rik van Riel wrote:
> On Tue, 14 Oct 2003, Marco Fioretti wrote:
> 
> > 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.

Let me concur with the sentiments on this thread.

When I started using Linux, it was on a 40 MHz 386 with 8Megs of ram and
a 200 Meg HD.  This was a reasonably typical machine for the time (1993).
I ran X on this machine, and it was fine running several Xterms and you
could play the X version of Tetris or gnuchess.  I used this machine to
write the program I was working on for my Masters degree.

Today, a machine with specs like I quoted above seems hopelessly slow.
However, I was able to do useful work on it in 1993, and the same sort
of work would still be useful today.  You of course are not going to be
able to run mozilla and KDE on it, but lynx, slrn, mutt, and fvwm will
work fine.  There are many people who will never be able to afford
to buy a computer but could find someone to give them one of these
"hopelessy outdated" machines for nothing.  If we can ensure that
Linux keeps working on these machines, it will be a good thing.

Thanks,

Jim

  reply	other threads:[~2003-10-14 14:30 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
2003-10-14 13:24 ` Rik van Riel
2003-10-14 14:30   ` jlnance [this message]
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=20031014143047.GA6332@ncsu.edu \
    --to=jlnance@unity.ncsu.edu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.