From: imp@village.org (M. Warner Losh)
Subject: [TUHS] So now that the source is finally out...
Date: Fri, 25 Jan 2002 03:27:25 -0700 (MST) [thread overview]
Message-ID: <20020125.032725.51748274.imp@village.org> (raw)
In-Reply-To: <20020125094218.C5968@apple.ukc.ac.uk>
In message: <20020125094218.C5968 at apple.ukc.ac.uk>
"P.A.Osborne" <P.A.Osborne at ukc.ac.uk> writes:
: Also from what I did look at, I rapidly came to the conclusion that
: a "real" mode i386 port was the more straight forward as that keeps
: everything in 16 bits and saves a lot of mucking around.
Real as in 286 or as in 8088 :-). I've love to have a v7 port to my
DEC Rainbow 100, which isn't too IBM-PC-like other than the fact that
both have an 8088. There was a 8088 port of V7 (or maybe it was v6)
to the Rainbow marketed under the name of venix, but no one seems to
be able to find a distribution anymore.
: With any joy if the assembler level can be done correctly (device drivers
: aside) you could theoretically leave the bulk of the C source intact - which
: could possibly make it a purer port, assuming you can get gcc to compile
: K&R C - I havent tried yet.
gcc can compile K&R, but the language has evolved some since the v7
days. =*, =+, etc became *=, +=, etc. There are some other subtle
things too that I don't recall off the top of my head, but which vexed
the comp.lang.c news groups in the early 1980's.
Warner
next prev parent reply other threads:[~2002-01-25 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 18:39 Rob Becker
2002-01-25 9:42 ` P.A.Osborne
2002-01-25 10:27 ` M. Warner Losh [this message]
2002-01-25 11:16 ` P.A.Osborne
2002-01-25 15:19 ` Ephrem Hugh Bensusan
2002-01-25 15:52 ` M. Warner Losh
2002-01-25 21:08 ` David C. Jenner
2002-01-25 16:24 ` Wolfgang Rupp
2002-01-29 6:17 ` M. Warner Losh
2002-01-25 16:30 ` Wolfgang Rupp
2002-01-25 17:30 ` Jeffrey S. Sharp
2002-01-25 19:18 Carl Lowenstein
2002-01-26 14:50 Ken Wellsch
2002-01-27 23:58 ` Greg Lehey
2002-01-31 0:29 ` Joerg Micheel
2002-01-27 19:03 norman
2002-01-30 1:40 Ken Wellsch
2002-01-31 1:03 John Holden
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=20020125.032725.51748274.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).