From: ephrem@bensusan.net (Ephrem Hugh Bensusan)
Subject: [TUHS] So now that the source is finally out...
Date: Fri, 25 Jan 2002 10:19:58 -0500 (EST) [thread overview]
Message-ID: <Pine.GSO.4.21.0201251013350.610-100000@barclay> (raw)
In-Reply-To: <20020125111637.F5968@apple.ukc.ac.uk>
It seems that there is a distribution of Venix hanging about, but I
believe it is for the DEC PRO 350 or 380. So I don't know how useful
it might be in this context.
In any case, one can find it at:
http://www.os2site.com/sw/dec/pro/venix/
--
Ephrem Hugh Bensusan EMail: ephrem at bensusan.net
Phone: 352.687.3757
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT/CS d? s--:+ a C++++$ UB/L++++$ P++> L+++$ E W++(+++)$ N++> o? K++ w--
O M? V-- PS+++(--) PE Y+ PGP+ t++* 5- X++ R tv- b+++> DI-- D+
G++ e* h----(-)* r+++ y++++(+++(--))
------END GEEK CODE BLOCK------
On Fri, 25 Jan 2002, P.A.Osborne wrote:
> On Fri, Jan 25, 2002 at 03:27:25AM -0700, M. Warner Losh wrote:
> > Real as in 286 or as in 8088 :-).
>
> Yup, otherwise you start mucking around with the protected mode
> shuffle to 32 bits and I have been burnt by that before. The ix86
> chips are startup from cold in 16bit mode so it makes life easier.
>
> > 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.
>
> Oooh that would be so usefull and save so much mucking around.
>
> > 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.
>
> That makes things a challenge. Still the source of the kernel is
> around 10K lines IIRC and going through it in stages doesnt make life
> too painfull.
>
> I must be mad thinking about this again....
>
>
> paul
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> http://minnie.tuhs.org/mailman/listinfo/tuhs
>
next prev parent reply other threads:[~2002-01-25 15:19 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
2002-01-25 11:16 ` P.A.Osborne
2002-01-25 15:19 ` Ephrem Hugh Bensusan [this message]
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=Pine.GSO.4.21.0201251013350.610-100000@barclay \
--to=ephrem@bensusan.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).