From: P.A.Osborne@ukc.ac.uk (P.A.Osborne)
Subject: [TUHS] So now that the source is finally out...
Date: Fri, 25 Jan 2002 09:42:18 +0000 [thread overview]
Message-ID: <20020125094218.C5968@apple.ukc.ac.uk> (raw)
In-Reply-To: <200201250045.KAA31838@guardian-ext.bond.edu.au>; from becker@ab.edu on Thu, Jan 24, 2002 at 01:39:50PM -0500
On Thu, Jan 24, 2002 at 01:39:50PM -0500, Rob Becker wrote:
> who is going to port 7th edition to the i386? (:
OK I know that the comment was a joke but...
Funnily enough I started looking at doing just that around 18 months
ago. Unfortunately (from that point of view) it ground to a halt when
wedding arrangements took priority.
Anyhow the wedding is out of the way - the missus is now a computing
student so I should get some sympathy from her (she likes Unix :-), so
hopefully I can resurrect my notes etc and start working on it again.
No promises mind as I havent touched C or assembly for around 18months
now so am getting increasily rusty. Not that my x86 assembler is
particulary good, or that the missus will allow me enough free time to
get my head back into coding at home...
So the following is what I can remember from quite a while ago...
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.
So you could either rewrite it as a process that runs as 16 bits and
so use it as an app under say Linux/FreeBSD/OS/2 (I wont mention the
people from Redmond :-), or as a 16 bit OS running native.
Either way the first skirmishes I made with the source lead me to
believe that in simple terms, the following would need to be completed:
- rewrite the assembler portion to x86 - memory management/interrupt
handlers/booting and initialisation etc etc
- rewrite the disk driver to run the floppy drive (1.4 MB should be
enough to demonstrate it works and boot a kernel etc)
- the tty stuff could conceivably be pointed at COM1 and you could
hang a console/teletype (for the sad) onto the back of a PC or
just produce suitable keyboard/screen drivers.
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.
Anyhow comments and sarcastic remarks are welcome.
Regards
Paul
------------
Paul Osborne
Computing Officer
University of Kent at Canterbury Computing Service
next prev parent reply other threads:[~2002-01-25 9:42 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 [this message]
2002-01-25 10:27 ` M. Warner Losh
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=20020125094218.C5968@apple.ukc.ac.uk \
--to=p.a.osborne@ukc.ac.uk \
/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).