From: Rudi Blom <rudi.j.blom@gmail.com>
To: rrigo@alchemistowl.org
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Old 386 Unix Versions, was: Re: PCC for the i386
Date: Sat, 20 Jul 2019 12:32:16 +0700 [thread overview]
Message-ID: <CAMYpm87MHk39qp0VuXv4qmdL9jNmwC7cAoqoh09E8ZzyhBuujg@mail.gmail.com> (raw)
>Does anyone have documentation or history for European efforts in the Unix-like operating systems? For example there was Bull’s Chorus which I seem to recall was based on Mach or a competing microkernel (it was a very long time ago and I used it for no mare than about two hours..).
>I am rather saddened by the fact that there is so much about all the Unix (and not only >Unix) history of computing in the USA and so very little in Europe. I wouldn’t even know >where to start, to be honest, all I have as a history is the Italian side from my father and his other mad friends and colleagues in Milan. So little of it is recorded, never mind written down.
In the 80-tisch I worked at Philips Data Systems in Apeldoorn, the
Netherlands. Not in Development, but in System Support. Philips was
working on a System V.3 based UNIX running on Motorola 68000 CPUs in a
P9X00 server. Called MPX as in Multi-Processor UNIX. The Multi part
refers to having an Ethernet, X25 and SDLC board running a tailored
version of the OS to offload the main CPU.
See for example
https://www.cbronline.com/news/better_late_philips_enters_the_uk_unix_market/
https://www.cbronline.com/news/philips_ready_with_68030_models_for_its_p9000_unix_workstation_family
Later Philips moved to i386 with a 'unknown version' based UNIX.
Division was bought by DEC (some say sold off by Philips) in 1991 and
we moved to DEC's choice of SCO UNIX. The 'intelligent comm boards
were ported and still running the separate OS though.
Unfortunately I never had any of that OS type of source and my paper
archive was left behind. Only have some small higher level test stuff
and my mail archive. For a while I was "rudi blom"
<blom@kiwi.idca.tds.philips.nl>, later rudi blom"@apd.mts
next reply other threads:[~2019-07-20 5:32 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-20 5:32 Rudi Blom [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-07-11 14:53 [TUHS] " Jason Stevens
2019-07-11 15:37 ` Clem cole
2019-07-11 15:50 ` Jason Stevens
2019-07-11 16:30 ` Clem cole
2019-07-11 16:50 ` A. P. Garcia
2019-07-17 7:37 ` [TUHS] Old 386 Unix Versions, was: " emanuel stiebler
2019-07-17 8:10 ` arnold
2019-07-17 9:28 ` Arrigo Triulzi
2019-07-17 10:09 ` Jason Stevens
2019-07-17 10:42 ` emanuel stiebler
2019-07-17 15:40 ` Adam Thornton
2019-07-17 18:01 ` Clem Cole
2019-07-17 12:32 ` Ben Greenfield via TUHS
2019-07-17 12:50 ` Dagobert Michelsen
2019-07-17 13:38 ` Arrigo Triulzi
2019-07-17 14:41 ` Clem Cole
2019-07-17 15:08 ` Ben Greenfield via TUHS
2019-07-17 21:09 ` Dagobert Michelsen
2019-07-18 8:56 ` Arrigo Triulzi
2019-07-17 16:04 ` William Pechter
2019-07-17 14:34 ` Clem Cole
2019-07-17 23:22 ` Bakul Shah
2019-07-18 0:04 ` Clem cole
2019-07-17 22:48 ` Chris Hanson
2019-07-18 8:39 ` Wesley Parish
2019-07-17 14:15 ` Clem Cole
2019-07-17 15:11 ` Larry McVoy
2019-07-17 15:31 ` Warner Losh
2019-07-17 15:36 ` Jason Stevens
2019-07-17 16:56 ` Larry McVoy
2019-07-24 1:04 ` Lyndon Nerenberg
2019-07-24 1:30 ` Arthur Krewat
2019-07-24 21:53 ` Kevin Bowling
2019-07-25 19:16 ` Lyndon Nerenberg
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=CAMYpm87MHk39qp0VuXv4qmdL9jNmwC7cAoqoh09E8ZzyhBuujg@mail.gmail.com \
--to=rudi.j.blom@gmail.com \
--cc=rrigo@alchemistowl.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).