From: imp@village.org (M. Warner Losh)
Subject: [TUHS] Porting Unix v6 to i386
Date: Tue, 29 Jan 2002 16:10:18 -0700 (MST) [thread overview]
Message-ID: <20020129.161018.09582254.imp@village.org> (raw)
In-Reply-To: <02012822034503.20290@g4klx>
In message: <02012822034503.20290 at g4klx>
Jonathan Naylor <jonathan.naylor at ggaweb.ch> writes:
: I would guess that VMWare would be a great host, or maybe its open source
: equivalents (Plex86 or Bochs) so that you could save the reboot cycles. I
: would also try porting V7 instead of V6, at least initially. With so much
: open source code out there, it'd be a relatively simple task to find C code
: for IDE disc access and such like. I would even suggest getting older Linux
: code from the 2.0.x days as its likely to be a little less complex, while
: still being stable.
There is a stripped down Linux port called Elks to the x86 right now.
It seems to work OK for these old 8088 machines (and newer ones in the
psion). But I'm still none-the-less drawn towards a v7 port :-)...
Warner
prev parent reply other threads:[~2002-01-29 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 16:10 Sven Dehmlow
2002-01-28 21:03 ` Jonathan Naylor
2002-01-29 13:47 ` Sven Dehmlow
2002-01-29 23:10 ` M. Warner Losh [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=20020129.161018.09582254.imp@village.org \
--to=imp@village.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;
as well as URLs for NNTP newsgroup(s).