From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: Help Wanted!
Date: Tue, 27 Sep 2005 21:13:51 +0100 [thread overview]
Message-ID: <200509272113.54472.dg@cowlark.com> (raw)
In-Reply-To: <1a19a18005092712103c1b1c0c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]
On Tuesday 27 September 2005 20:10, Isaque Galdino wrote:
> Well guys, I appreciate your efforts to bring elks back to life.
> I tried once to use elks in my hp200lx but with no luck at all.
> hp200lx still has a lot of users, if you could boot a hp200lx with
> elks I guess you would have a lot of guys trying elks for sure.
Have you tried ELKS' arch-rival, Minix? I'm not sure if Minix 2 will run on
the i86, but Minix 1.5 certainly does, and works reasonably well.
The big trouble with ELKS is that it only really runs on i86 machines, and
these are a right pain to deal with --- it's not just that they're really
old, decrepit machines which cost more in electricity to run than a pocket
calculator a thousand times more powerful does today, it's that no two are
the same. Standards were pretty fuzzy in those days, and there's a huge
variety of different kinds of hardware that needs supporting. Actually making
ELKS work reliably would be a rather large undertaking just for test
purposes...
(DOS gets away with it because, basically, DOS is crap. It relies on the BIOS
to do a lot of the work, which ELKS can't really do. Minix manages a bit
better but it's a bit picky on the kinds of hardware it'll support for just
this reason.)
Can ELKS be ported to *other* architectures that i86? Would it be feasible to
use it on a modern, flat architecture like ARM?
--
+- David Given --McQ-+ "Hydrogen fusion, the sun makes shine
| dg@cowlark.com | Vascular pressure makes the ivy twine.
| (dg@tao-group.com) | Because of Rayleigh, the sky's so blue.
+- www.cowlark.com --+ Hormonal fixation is why I love you." --- Zarf
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-27 20:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 5:30 Help Wanted! Miguel Bolanos
2005-09-24 9:35 ` Hans
2005-09-24 19:43 ` Rex Walburn
2005-09-27 18:38 ` Hans
2005-09-27 19:10 ` Isaque Galdino
2005-09-27 20:13 ` David Given [this message]
2005-09-27 20:30 ` Dan Olson
2005-09-27 21:06 ` Hans
2005-09-27 21:48 ` David Given
2005-09-28 2:32 ` Rex Walburn
2005-09-28 12:45 ` Javier Sedano
2005-09-27 19:30 ` Dan Olson
2005-09-28 9:29 ` jb1
2005-09-28 15:30 ` Gregg C Levine
2005-09-29 9:14 ` jb1
2005-09-28 9:51 ` Alexander van Heukelum
-- strict thread matches above, loose matches on Subject: below --
2005-09-28 16:33 hansydelm
2005-09-28 16:48 hansydelm
2006-02-01 22:33 Help Wanted? Cathal Mullaney
2006-02-01 22:57 ` Lee Revell
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=200509272113.54472.dg@cowlark.com \
--to=dg@cowlark.com \
--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 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.