The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Ruizendaal <pnr@planet.nl>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] V8, V9 and V10 now in the "Unix Tree"
Date: Sun, 12 Apr 2020 10:51:58 +0200	[thread overview]
Message-ID: <E0E588AB-C9E6-4ECC-AC9E-BF7F3DC9F562@planet.nl> (raw)
In-Reply-To: <CAKzdPgzc3Z816FLUPLd-RE2C41kPeTZXuR5wkDA=PgGsVg3V9Q@mail.gmail.com>

Below an update with comments reflected.

===

After the Seventh Edition, the VAX became the base machine for further Unix development. The initial code base was the 32V port, enhanced with selected elements from 4.1BSD, such as support for virtual memory and later the TCP/IP stack. From there the code further evolved and an Eighth Edition manual was completed by Bell Laboratories in February 1985, six years after 7th Edition. The 8th Edition source code was not as widely distributed as the 6th and 7th Edition sources had been.

The file system in 8th Edition was rewritten to work with a bitmapped free list and allocation clusters of 4KB (8 blocks); it also supported the V7 filesystem for backwards compatibility with disk clusters of 1, 2 or 4 blocks.

Key innovations in the 8th Edition kernel include ‘streams’ and the 'file system switch’, which allowed the “everything is a file” approach to be extended to new areas. Three notable developments built on these were the ‘/proc’ file system and new debugger API, a unified approach to networking over Datakit, TCP/IP and phone lines, and a network file system.

Eighth Edition is also at the root of graphical user interfaces on Unix, being the platform used for the development of the ‘Blit’ graphical terminal.

Several of the new ideas from Eighth Edition found their way into the 3rd release of System V, although in a much modified form.

===

> On Sat, Apr 11, 2020 at 1:35 AM Paul Ruizendaal <pnr@planet.nl> wrote:
>> 
>> Warren has been nice enough to put 8th, 9th and 10th edition on the TUHS “Unix Tree” web page.
>> 
>> There is the following question on each entry web page: “Who wants to write something here?”
>> 
>> Below my suggested draft text for Eight Edition. All suggestions for improvement welcome.
>> 
>> ===
>> 
>> Shortly after the release of 7th Edition, the VAX became the base machine for further Unix development. The initial code base was the 32V port, enhanced with selected elements from 4.1BSD, such as support for virtual memory and later the TCP/IP stack. From there the code further evolved: Eighth Edition of Unix was released by Bell Laboratories in February 1985, six years after Seventh Edition.
>> 
>> Key innovations in 8th Edition include ‘streams’ and the 'file system switch’, which allowed the “everything is a file” approach to be extended to new areas. Three notable applications built on these were the ‘/proc’ file system and new debugger API, a unified approach to networking over Datakit, TCP/IP and phone lines, and a network file system.
>> 
>> Eighth Edition is also at the root of graphical user interfaces on Unix, being the platform used for the development of the ‘Blit’ graphical terminal.
>> 
>> Several of the new ideas from Eigth Edition found their way into the 3rd release of System V, although in a much modified way.
>> 
>> ===
>> 


  reply	other threads:[~2020-04-12  8:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 15:34 Paul Ruizendaal
2020-04-10 20:50 ` Rob Pike
2020-04-12  8:51   ` Paul Ruizendaal [this message]
2020-04-11 14:47 Doug McIlroy
2020-04-11 15:24 Norman Wilson
2020-04-11 18:49 ` arnold
2020-04-11 15:38 Norman Wilson
2020-04-11 15:44 ` Larry McVoy
2020-04-11 18:52 ` arnold
2020-04-12  9:26 Paul Ruizendaal
2020-04-12  9:30 Paul Ruizendaal
2020-04-12 10:00 ` Rob Pike

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=E0E588AB-C9E6-4ECC-AC9E-BF7F3DC9F562@planet.nl \
    --to=pnr@planet.nl \
    --cc=tuhs@minnie.tuhs.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).