The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: LyricalNanoha@dosius.net (Lyrical Nanoha)
Subject: [TUHS] Redoing "V6on286" or porting V7...?
Date: Wed, 9 Nov 2005 12:26:32 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.62.0511091221220.6113@static-141-149-129-16.buff.east.verizon.net> (raw)

I've thought, since there doesn't seem to be a working "V6on286", maybe I 
should try porting it myself though I'm not very familiar with the Ancient 
Unix sources or with the ancient C used.  The oldest compiler I've got 
that will compile is Turbo C++ 1.01 from 1990 and it's an ANSI C compiler. 
(I do think it'll compile late K&R, but there's weirdnesses in the C used 
by V6.)

Having an emulator like QEMU handy is a nice plus.  I could prolly build 
everything onto a 1.44 MB disk image and boot it in emulation.  I'm 
thinking I'd want to create tools for transferring files into and out of 
disk images, and a bootloader to put on the first sector of the disk 
(though, 512 bytes is awful small...)

Any ideas?

-uso.



             reply	other threads:[~2005-11-09 17:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-09 17:26 Lyrical Nanoha [this message]
2005-11-09 21:54 ` M. Warner Losh
2005-11-09 22:03 ` Brantley Coile
2005-11-12  6:13   ` Albert Cahalan
2005-11-12 13:18     ` Brantley Coile
2005-11-13 20:16       ` Peter Jeremy
2005-11-14  9:38         ` Wesley Parish
2005-11-14 15:45         ` Brantley Coile
     [not found]         ` <8a61b612cf43394f33e6531339fe4263@coraid.com>
2005-11-14 19:49           ` Peter Jeremy
2005-11-14 20:31             ` Brantley Coile
2005-11-16 21:41             ` Lyrical Nanoha
     [not found]               ` <17277.62390.986234.433543@hod.localdomain>
2005-11-18 17:59                 ` Lyrical Nanoha
2005-11-19  4:17                   ` Brantley Coile
2005-11-15  3:08         ` Greg Haerr
2005-11-15  3:40           ` Peter Jeremy
2005-11-15 13:30             ` Brantley Coile
2005-11-14 21:34 Norman Wilson
2005-11-14 22:59 ` Brantley Coile

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=Pine.LNX.4.62.0511091221220.6113@static-141-149-129-16.buff.east.verizon.net \
    --to=lyricalnanoha@dosius.net \
    /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).