public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Piel <Eric.Piel@lifl.fr>
To: Imanpreet Arora <imanpreet@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux under 8MB
Date: Sat, 20 Aug 2005 02:18:48 +0200	[thread overview]
Message-ID: <430676E8.3070103@lifl.fr> (raw)
In-Reply-To: <c26b9592050818151154ff1a89@mail.gmail.com>

19.08.2005 00:11, Imanpreet Arora wrote/a écrit:
> 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
> 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.
> 

Last year, at the Realtime linux workshop, there was a paper about 
running Linux on a machine with 2Mb of RAM + 2Mb of Flash. They even 
manage to boot in 1 second! Nevertheless, they had to do several 
modifications to achieve this. Maybe with the new options in the 2.6 
kernel, it would be easier...

Check it here:
http://www.realtimelinuxfoundation.org/events/rtlws-2004/papers.html#PAPER_5795


Regards,
Eric

  parent reply	other threads:[~2005-08-20  0:18 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
2005-08-19  1:47 ` Pedro Venda (SYSADM)
2005-08-19  8:53 ` Ondrej Zary
2005-08-20  0:18 ` Eric Piel [this message]
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=430676E8.3070103@lifl.fr \
    --to=eric.piel@lifl.fr \
    --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