From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: u-vpoa@aetey.se
Cc: linux-8086@vger.kernel.org
Subject: Re: We have a whole new ton of goodies to investigate...
Date: Mon, 27 Apr 2015 00:31:28 +0100 [thread overview]
Message-ID: <20150427003128.0c61965e@www.etchedpixels.co.uk> (raw)
In-Reply-To: <20150426212223.GT8197@example.net>
> I wonder, if Fuzix is sufficiently portable to run on 8086, could it
> happen to offer a possibly even more suitable foundation for a usable
> system, than the linux-derived code in ELKS?
I'm not sure where the changeover point would be. ELKS supports
asynchronous disk I/O properly, something FUZIX avoids. On an 8bit micro
its pretty much pure overhead. On a PC/XT it's less clear.
> > plenty of stuff in ELKS that was taken from 386 Linux and is perhaps
> > somewhat over-engineered for the job (buffer cache is perhaps one bit
> > still)
>
> I guess so. Sigh. The original V7's or even V6's quite basic design might
> possibly suit 8086 better (I did not look at the ELKS kernel but I saw
> V6/7 sources and also pieces of Venix/86 kernel which were apparently
> build from literally the same C code, this seemed to work well).
ELKS is not that bloated to be honest. It's got a few areas that would
probably save a chunk of memory if fixed but the basic architecture is
pretty sound including basic 286 mode support.
Some of the utilities are a bit brain-dead or buggy and might benefit
from being pulled from elsewhere instead, and there are things lacking
(like the real bourne shell should fit fine and is nowdays available)
Alan
next prev parent reply other threads:[~2015-04-26 23:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 21:22 We have a whole new ton of goodies to investigate u-vpoa
2015-04-26 23:31 ` Alan Cox [this message]
2015-04-27 7:06 ` u-vpoa
2015-04-27 10:53 ` Alan Cox
2015-04-27 12:30 ` u-vpoa
2015-04-27 13:35 ` Alan Cox
2015-04-27 14:44 ` u-vpoa
-- strict thread matches above, loose matches on Subject: below --
2015-04-16 11:14 LM
2015-04-16 11:39 ` Alan Cox
2015-04-03 20:40 Alan Cox
2015-04-15 17:10 ` MFLD
2015-04-15 21:41 ` Alan Cox
2015-04-16 7:35 ` MFLD
2015-04-16 11:49 ` Alan Cox
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=20150427003128.0c61965e@www.etchedpixels.co.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-8086@vger.kernel.org \
--cc=u-vpoa@aetey.se \
/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