The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@nose.cs.utoronto.ca (Norman Wilson)
Subject: [pups] History of 32-bit UNIX (was History of 2 BSD)
Date: Mon, 10 Nov 2003 12:28:57 -0500	[thread overview]
Message-ID: <20031110172933.B05311F1B@minnie.tuhs.org> (raw)

Mario Premke:

  but I wonder when the step from
  16bit to 32bit was made in BSD.

Michael Sokolov:

  It was not made in BSD.  It was made at Ma Bell: the step from V7 to 32V (VAX
  port of V7).

You're a little late: researchers at Bell Labs ported UNIX to the 32-bit
Interdata 8/32 in 1977.  I don't think the resulting system was widely used,
but the lessons learned greatly influenced V7.  In particular typedef and
unsigned were added to C, the compiler became more honest about type checking,
and system-interface data structures like struct stat were installed in standard
include files rather than being copied into every program.

Others ported the system in those carefree days as well, in particular Richard
Miller at the University of Wollongong, but I don't know much about the other
efforts.  But the VAX was by no means the first 32-bit port.

Norman Wilson
Toronto ON


             reply	other threads:[~2003-11-10 17:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 17:28 Norman Wilson [this message]
2003-11-10 22:04 ` Greg 'groggy' Lehey

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=20031110172933.B05311F1B@minnie.tuhs.org \
    --to=norman@nose.cs.utoronto.ca \
    /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).