The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Derek Fawcus <dfawcus+lists-tuhs@employees.org>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Unix on Zilog Z8000?
Date: Mon, 16 Mar 2020 23:02:05 +0100	[thread overview]
Message-ID: <20200316220205.GA45265@clarinet.employees.org> (raw)
In-Reply-To: <CACNPpea-io1kTEW=UPSLg04=C_sNH0-7hciututMcU06zS0e1Q@mail.gmail.com>

On Mon, Mar 16, 2020 at 01:28:26PM +1300, Wesley Parish wrote:
> Is it still in existence?

> In the form of floppies?

https://www.autometer.de/unix4fun/coherent/ftp/distrib/Coherent-0.7/

Certainly disk2 looks like it has a filesystem on it, since there are
blocks which appear to be 16 byte directory entries, presumably
inode number and 14 char name.

> Any source?

I don't know about historical sources of the time.
The availale Coherent source has a few files with z8001 in their name:

$ gzip -dc ~/Downloads/mwc-COHERENT-Source.tgz|tar tvf - |fgrep -i z800
-rw-r--r--  0 steve  staff     6521  6 Feb  1991 romana/relic/d/lib/libc/sys/mch/z8001.tar.Z
drwxr-xr-x  0 steve  staff        0 14 Jun  2003 romana/relic/d/lib/libc/stdio/z8001/
-rw-r--r--  0 steve  staff      268  9 Nov  1984 romana/relic/d/lib/libc/stdio/z8001/fgetw.c
-rw-r--r--  0 steve  staff      169  9 Nov  1984 romana/relic/d/lib/libc/stdio/z8001/fputw.c
-rw-r--r--  0 steve  staff      340  9 Nov  1984 romana/relic/d/lib/libc/stdio/z8001/getw.c
-rw-r--r--  0 steve  staff      231  9 Nov  1984 romana/relic/d/lib/libc/stdio/z8001/putw.c
-rw-r--r--  0 steve  staff     4906  6 Feb  1991 romana/relic/d/lib/libc/gen/mch/z8001.tar.Z
drwxr-xr-x  0 steve  staff        0 14 Jun  2003 romana/relic/d/bin/diff/z8001/
-rw-r--r--  0 steve  staff     8445  2 Nov  1984 romana/relic/d/bin/diff/z8001/diff1.c
-rw-r--r--  0 steve  staff     7767 23 Mar  1990 romana/relic/d/bin/diff/z8001/diff2.c
-rw-r--r--  0 steve  staff       92  8 Jul  1985 romana/relic/d/bin/diff/z8001/Readme
-rw-r--r--  0 steve  staff    17512  7 Mar  1991 romana/relic/d/bin/db/mch/z8001.tar.Z
-rw-r--r--  0 steve  staff    13929  7 Mar  1991 romana/relic/d/bin/db/mch/z8002.tar.Z
-rw-r--r--  0 steve  staff    21823  6 Feb  1991 romana/relic/d/bin/as/mch/z8001.tar.Z
-rw-r--r--  0 steve  staff    19275  6 Feb  1991 romana/relic/d/bin/as/mch/z8002.tar.Z
-rw-r--r--  0 steve  staff     6521  6 Feb  1991 romana/relic/b/lib/libc/sys/mch/z8001.tar.Z
drwxr-xr-x  0 steve  staff        0 14 Jun  2003 romana/relic/b/lib/libc/stdio/z8001/
-rw-r--r--  0 steve  staff      268  9 Nov  1984 romana/relic/b/lib/libc/stdio/z8001/fgetw.c
-rw-r--r--  0 steve  staff      169  9 Nov  1984 romana/relic/b/lib/libc/stdio/z8001/fputw.c
-rw-r--r--  0 steve  staff      340  9 Nov  1984 romana/relic/b/lib/libc/stdio/z8001/getw.c
-rw-r--r--  0 steve  staff      231  9 Nov  1984 romana/relic/b/lib/libc/stdio/z8001/putw.c
-rw-r--r--  0 steve  staff     4906  6 Feb  1991 romana/relic/b/lib/libc/gen/mch/z8001.tar.Z

I looked inside the first one, and it gives this set of files, being the library for the syscalls:

$ ls z8001/
_brk.s		chroot.s	getegid.s	link.s		pause.s		signal.s	umount.s
access.s	close.s		geteuid.s	lock.s		pipe.s		sload.s		unique.s
acct.s		creat.s		getgid.s	lseek.s		profil.s	stat.s		unlink.s
alarm.s		dup.s		getpid.s	mknod.s		ptrace.s	stime.s		utime.s
bpt.s		execve.s	getuid.s	mount.s		read.s		suload.s	wait.s
chdir.s		fork.s		halt.s		mpx.s		sbrk.c		sync.s		write.s
chmod.s		fstat.s		ioctl.s		nice.s		setgid.s	times.s
chown.s		ftime.s		kill.s		open.s		setuid.s	umask.s

I've not explored any further, but if the kernel source isn't there, I rather suspect
the 286 kernel source could be beaten in to some sort of shape to work on the z8000.

There some RCS files in there if you wish to explore further.

That still leaves you with having to come up with drivers, but there do seem to be
(some) technical docs available for the machine.

DF

  reply	other threads:[~2020-03-16 22:09 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 [this message]
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
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=20200316220205.GA45265@clarinet.employees.org \
    --to=dfawcus+lists-tuhs@employees.org \
    --cc=tuhs@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).