From: Nix <nix@esperi.org.uk>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Heerath bh <heerath.bh@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Rebuilding Linux kernel
Date: Mon, 30 Jan 2006 18:13:21 +0000 [thread overview]
Message-ID: <8764o1vb26.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <1138605742.2799.149.camel@mindpipe> (Lee Revell's message of "30 Jan 2006 07:24:08 -0000")
On 30 Jan 2006, Lee Revell said:
> On Mon, 2006-01-30 at 12:33 +0530, Heerath bh wrote:
>>
>> Basically I am trying to rebuild the kernel.I am trying to make two
>> types of kernel.I am using Redhat 2.4 version on intel x86 machine.
>> 1.Deployment level kernel
>> 2.development level kernel.
>>
>> Deployment Level kernel:This kernel has to be a Very vanilla kernel. I
>> mean to say, it wil be having basic kernel services like:preemptive
>> kernel,memory
>>
>> management,scheduling&synchronization,sysatem
>> timers,IPC,Interrupt handling,multitasking.
>>
>
> You will need 2.6 for this, 2.4 is inadeuate (no preemption). 2.6.14 or
> 2.6.15 is a good choice.
He wants it to fit in 300K (of RAM? final image size? he didn't say).
No way will normal Linux kernels get that trim, nor any Linux-like
kernel supporting all the features he wants.
--
`I won't make a secret of the fact that your statement/question
sent a wave of shock and horror through us.' --- David Anderson
prev parent reply other threads:[~2006-01-30 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 7:03 Rebuilding Linux kernel Heerath bh
2006-01-30 7:19 ` Moses Marimo
2006-01-30 7:22 ` Denis Vlasenko
2006-01-30 7:29 ` David S. Miller
2006-01-30 18:48 ` Greg KH
2006-01-30 7:22 ` Lee Revell
2006-01-30 18:13 ` Nix [this message]
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=8764o1vb26.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=heerath.bh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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.