From: Warner Losh <imp@bsdimp.com>
To: Holger Veit <hveit01@web.de>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: PCS Munix kernel source
Date: Wed, 10 Aug 2022 10:12:04 -0600 [thread overview]
Message-ID: <CANCZdfrt0du_p7U1HhdKhHY+n+x8Mon5q9U1k0wwBoMGK=BB9Q@mail.gmail.com> (raw)
In-Reply-To: <2b4956cb-228c-72db-8f0f-6e9907864b8c@web.de>
[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]
On Wed, Aug 10, 2022 at 4:29 AM Holger Veit <hveit01@web.de> wrote:
> Hi all,
>
> I have uploaded the kernel source of 32 bit PCS MUNIX 1.2 to
> https://github.com/hveit01/pcs-munix.
>
This is really cool!
> MUNIX was an AT&T SVR3.x implementation for the German PCS Cadmus
> workstations in the 80's. They were
> based on Motorola 68020 CPUs on a DEC QBUS.
>
Fun times that combination...
> The interesting feature of this kernel is the integration of the
> Newcastle Connection network
> (https://en.wikipedia.org/wiki/Newcastle_Connection) which I found,
> beyond a tech report https://assets.cs.ncl.ac.uk/TRs/175.pdf, no further
> references for.
>
> The kernel source was reverse engineered and verified (see readme in the
> distribution who this was done) from the binary tape at
> ftp.informatik.uni-stuttgart.de/pub/cm/pcs/sw/IS0371P.tap (Computer
> museum of the University of Stuttgart), and to my knowledge reveals the
> Newcastle connection code for the first time in a commercial Unix.
>
> The Github package includes the kernel sources, i/O drivers, several
> standard libraries, the disassembled boot ROM and for reference, two of
> my tools, a partial syscall emulator pcsrun which allowed me to run the
> C compiler and other native binaries outside the PCS hardware/Unix
> environment, and a disassembler pcsdis for the specific COFF dialect
> (note that IDA will produce garbage without a specific patch).
>
I love it. This is quite similar, though further along, than my on-again
off-again efforts to do the same with Venix 86/R for my Rainbow...
Warner
[-- Attachment #2: Type: text/html, Size: 2739 bytes --]
next prev parent reply other threads:[~2022-08-10 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 10:29 [TUHS] " Holger Veit
2022-08-10 16:12 ` Warner Losh [this message]
2022-08-10 17:15 ` [TUHS] " emanuel stiebler
2022-08-11 6:04 [TUHS] " Paul Ruizendaal via TUHS
2022-08-11 9:01 ` [TUHS] " Holger Veit
2022-08-13 20:40 ` Paul Ruizendaal
2022-08-11 13:32 ` Nelson H. F. Beebe
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='CANCZdfrt0du_p7U1HhdKhHY+n+x8Mon5q9U1k0wwBoMGK=BB9Q@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=hveit01@web.de \
--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).