public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lexington Luthor <lexington.luthor@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Which kernel is the best for a small linux system?
Date: Mon, 13 Mar 2006 08:00:51 +0000	[thread overview]
Message-ID: <dv38rn$430$1@sea.gmane.org> (raw)
In-Reply-To: <436c596f0603121640h4f286d53h9f1dd177fd0475a4@mail.gmail.com>

j4K3xBl4sT3r wrote:
> Hello all,
> 
> I've been seeing many Linux versions, with many features, some of them
> just for the newest branches (2.4.x and 2.6.x), I would like to know
> for which kind of system each kernel is recommended.

Hi,

I am not a kernel developer, so this is not an official recommendation, 
but exactly what kind of "small" system do you mean?

I build and maintain a Linux distribution geared for memory-constrained 
x86 systems, as old as 386s with 4MB of RAM, and the 2.6 kernel fairs 
very well there. I only do so as a hobby not officially supported, so I 
haven't tested the distribution with a very wide range of workloads, but 
for bootstrapping itself from sources and for general home LAN routing 
work, its great.

You might want to look into patch sets like the 2.6-tiny patches, which 
greatly reduce the memory footprint of the kernel: 
http://www.selenic.com/linux-tiny/

Also, you might want to look into the uclibc or dietlibc libraries, 
which are a much smaller and less memory hungry than glibc (which has 
become a memory pig in recent years).

Regards,
LL


  reply	other threads:[~2006-03-13  8:01 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-13  0:40 Which kernel is the best for a small linux system? j4K3xBl4sT3r
2006-03-13  8:00 ` Lexington Luthor [this message]
2006-03-15  1:35   ` Grant Coady
2006-03-15  1:46     ` Randy.Dunlap
2006-03-13  8:17 ` Arjan van de Ven
2006-03-13 18:03   ` Grant Coady
2006-03-13 18:06     ` Arjan van de Ven
2006-03-14  6:21       ` Willy Tarreau
2006-03-14  7:29         ` Ingo Molnar
2006-03-14  8:18           ` Mike Galbraith
2006-03-14  9:05           ` Mike Galbraith
2006-03-14 15:54             ` Willy Tarreau
2006-03-16 15:24             ` Mike Galbraith
2006-03-14 10:03         ` Grant Coady
2006-03-14 22:21           ` Russell King
2006-03-15  0:46             ` Grant Coady
     [not found]               ` <20060315080313.GC3166@flint.arm.linux.org.uk>
2006-03-15  9:37                 ` Grant Coady
2006-03-15 22:53             ` Jan Engelhardt
2006-03-15 23:32               ` Grant Coady
2006-03-16  4:19                 ` Mike Galbraith
2006-03-16  8:12                   ` Mike Galbraith
2006-03-16  8:31                     ` Lee Revell
2006-03-16  8:55                       ` Mike Galbraith
2006-03-16  9:20                         ` Mike Galbraith
2006-03-16  2:55               ` Valdis.Kletnieks
2006-03-13 18:27   ` Sam Ravnborg
2006-03-13 18:41     ` Lee Revell
2006-03-13 19:01       ` Adrian Bunk
2006-03-14  0:18         ` j4K3xBl4sT3r
2006-03-13 19:08     ` Diego Calleja
2006-03-13 22:00     ` Pantelis Antoniou
2006-03-13 22:01       ` j4K3xBl4sT3r
2006-03-13 22:20         ` Pantelis Antoniou
2006-03-13 22:33           ` j4K3xBl4sT3r
2006-03-16 12:03             ` Pavel Machek
2006-03-13 22:25         ` Lee Revell
2006-03-14  3:53           ` Grant Coady
2006-03-15 22:57     ` Jan Engelhardt
2006-03-15 23:10       ` Adrian Bunk
2006-03-16 13:39         ` linux-os (Dick Johnson)

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='dv38rn$430$1@sea.gmane.org' \
    --to=lexington.luthor@gmail.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