The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Heinz Lycklama <heinz@osta.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Unix on Zilog Z8000?
Date: Tue, 21 Jan 2020 13:07:07 -0800	[thread overview]
Message-ID: <85e9f90a-8ab2-2c43-f7a8-7a34e96bd9e8@osta.com> (raw)
In-Reply-To: <CAC20D2MuKVqDdosO8FMZ52H1=GY=ziMUsFJsFoyVa0TAGwCx8A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1923 bytes --]

That is correct. John Bass did contribute the lockf(2) system call
to the /usr/group standard. It is in the 1984 document.

Heinz

On 1/21/2020 10:28 AM, Clem Cole wrote:
> The Onyx box redated all the 68K and later Intel or other systems.  
>  John Bass brought one to USENIX to demo in early 1980 ru a V7 port 
> and everyone was blown away. Playing with it. It was a desktop (19" 
> rack) system that worked like a PDP-11.   I don't remember the bus, 
> but I would guess it was either custom or Multibus-I.
>
> Besides being one of the first non-PDP-11 'ports', the original 
> lockf(2) system call was defined for the database that they had built. 
> John would release the specs to /usr/group later.  I remember at one 
> meeting in the early 1980s discussing if file locking needed to be in 
> the original specification (Heinz probably remembers also as the chair 
> of that meeting).  I'm not at home, so I don't have the document to 
> see if it was picked up.  The argument was that serious computers like 
> VMS or the like ran real databases and without file locking UNIX would 
> never be considered a real OS that people could use.
>
> BTW: Joy would later use Bass's call as a model for the 4.2 call, but 
> Joy made the locks advisory, Bass's version was full / mandatory locks.
>
> FWIW: I think a search will pick up a number of other Z8000 based 
> systems, but Onyx was the first UNIX box.
>
> On Tue, Jan 21, 2020 at 12:53 PM Jon Forrest <nobozo@gmail.com 
> <mailto:nobozo@gmail.com>> wrote:
>
>     There's been a lot of discussion about early Unix on Intel, National
>     Semi, Motorola, and Sparc processors. I don't recall if Unix ran on
>     the Z8000, and if not, why not.
>
>     As I remember the Z8000 was going to be the great white hope that
>     would continue Zilog's success with the Z80 into modern times.
>     But, it obviously didn't happen.
>
>     Why?
>
>     Jon
>


[-- Attachment #2: Type: text/html, Size: 3715 bytes --]

  reply	other threads:[~2020-01-21 21:08 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21 17:52 Jon Forrest
2020-01-21 18:13 ` Steve Nickolas
2020-01-21 18:27   ` William Pechter
2020-01-21 18:15 ` Henry Bent
2020-01-21 18:20   ` Larry McVoy
2020-01-21 21:48     ` Nigel Williams
2020-01-21 22:00       ` Henry Bent
2020-01-21 22:36         ` Derek Fawcus
2020-01-21 22:35     ` Jason Stevens
2020-03-15 18:40       ` Cornelius Keck
2020-03-16  0:28         ` Wesley Parish
2020-03-16 22:02           ` Derek Fawcus
2020-01-21 18:32   ` William Pechter
2020-01-21 21:24   ` Jon Forrest
2020-01-21 18:28 ` Clem Cole
2020-01-21 21:07   ` Heinz Lycklama [this message]
2020-01-21 21:32   ` [TUHS] Onyx (was Re: Unix on Zilog Z8000?) Derek Fawcus
2020-01-22  8:18   ` [TUHS] Unix on Zilog Z8000? Arrigo Triulzi
2020-01-22 17:00 ` Mary Ann Horton
2020-01-22 21:04   ` [TUHS] Life at UC Berkeley (was Unix on Zilog Z8000?) Jon Forrest
2020-01-23  2:08   ` [TUHS] Unix on Zilog Z8000? Erik Fair
2020-01-22 19:55 ` Andreas Hein
2020-01-23 12:01   ` Oliver Lehmann
2020-01-25  1:46     ` [TUHS] Dhrystone Benchmark (was: Unix on Zilog Z8000?) Oliver Lehmann
2020-01-25  1:49       ` Oliver Lehmann
2020-01-25  2:29         ` Warner Losh
2020-01-22 10:56 [TUHS] Unix on Zilog Z8000? Paul Ruizendaal
2020-01-22 13:14 Paul Ruizendaal
2020-01-22 15:14 ` Clem Cole

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=85e9f90a-8ab2-2c43-f7a8-7a34e96bd9e8@osta.com \
    --to=heinz@osta.com \
    --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).