From: Adrian Bunk <bunk@stusta.de>
To: Imanpreet Arora <imanpreet@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux under 8MB
Date: Fri, 19 Aug 2005 00:53:12 +0200 [thread overview]
Message-ID: <20050818225312.GG3822@stusta.de> (raw)
In-Reply-To: <c26b9592050818151154ff1a89@mail.gmail.com>
On Fri, Aug 19, 2005 at 03:41:30AM +0530, Imanpreet Arora wrote:
> Hi all,
>
> For the last couple of days, I have been trying to set
> up linux kernel under 8MB. So far I have set up a linux 2.4.31, which
> just works under 8MB. However, I would be grateful if someone could
> help with the following queries
>
> a) Is linux2.4 just the right option? What about linux 2.0.x?
> Or for that matter even <2.0
The more interesting case would ne a recent 2.6 kernel with
General setup
Configure standard kernel features (for small systems)
enabled and appropriate options below this option selected.
> b) What are the specific issues that are to be considered
> while compiling an old kernel on a newer setup? I ask this because I
> compiled my current setup on a 2.6.11 machine and while doing "make
> modules_install", I got errors from depmod[%], complaining about
> depmod.old. I had to kludge my way through by setting up a link from
> depmod.old to depmod.
What userspace do you want to use on the 8MB machine?
You need a userspace that supports such an old kernel.
> [%] Not to mention that on a FC4 machine, gcc 4,x meowed while
> compiling the kernel.
gcc 4.0 is not a working compiler for _any_ kernel below 2.6.12.
> TIA,
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-08-18 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 22:11 Linux under 8MB Imanpreet Arora
2005-08-18 22:53 ` Adrian Bunk [this message]
2005-08-19 1:47 ` Pedro Venda (SYSADM)
2005-08-19 8:53 ` Ondrej Zary
2005-08-20 0:18 ` Eric Piel
2005-08-21 19:21 ` Eric W. Biederman
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=20050818225312.GG3822@stusta.de \
--to=bunk@stusta.de \
--cc=imanpreet@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