From: Dave Mills <dave@webshed.org>
Cc: linux-8086@vger.kernel.org
Subject: Re: Minimum RAM for ELKS?
Date: Wed, 17 May 2006 11:05:54 +0100 [thread overview]
Message-ID: <446AF582.2090304@webshed.org> (raw)
In-Reply-To: <20060515195230.66257.qmail@web51307.mail.yahoo.com>
Tom McCabe wrote:
>
> --- Vikas Kumar <walburn@gmail.com> wrote:
>
>> Hey Dave
>> Use Bochs emulator. Set the RAM to how much ever
>> your target machine
>> has, and use an elks image and see if it works. iF
>> it works on this
>> setting, it should work on your target hardware as
>> well.
>>
>> Vikas
>
> I remember there being an option in the ELKS
> configuration about how many 64 KB memory pages were
> necessary, and the minimum was 4 (256 KB). Also, I've
> noticed that even on a modern system with the full 640
> KB possible, the ash and rc shells don't run (if sash
> isn't linked to /bin/sh, it crashes on bootup).
Thanks Vikas & Tom. I'll give the bochs idea a try. I'm really just
trying to get the smallest kernel running that I can.
cheers,
Dave
prev parent reply other threads:[~2006-05-17 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 16:18 Minimum RAM for ELKS? Dave Mills
2006-05-15 16:34 ` Vikas Kumar
2006-05-15 19:52 ` Tom McCabe
2006-05-17 10:05 ` Dave Mills [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=446AF582.2090304@webshed.org \
--to=dave@webshed.org \
--cc=linux-8086@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