From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: DG UNIX History
Date: Sun, 13 Nov 2022 06:16:44 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2211130613290.43868@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC20D2PCSN74fFWPo5TYOw2gB+cZnNfUTRMRdBMVEgEsKYA8fA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
On Sat, 12 Nov 2022, Clem Cole wrote:
[ ... ]
> (the infamous 'NUIX' bug from the Series/1 port probably being my
> favorite tale).
That would be the "NUXI" bug (byte-swapped words).
> So to the hive mind, did anyone (DG themselves or a University) ever
> build 16 or 32-bit tools for the DG architectures and do a UNIX port,
> and if so, does anyone know what became of those efforts? Is this
> something that needs to be in the TUHS archives also?
I remember Tracey Kidder's "The Soul of a New Machine"... It ran some
proprietary system, though.
-- Dave
next prev parent reply other threads:[~2022-11-12 19:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-12 15:54 [TUHS] " Clem Cole
2022-11-12 16:09 ` [TUHS] " Larry McVoy
2022-11-12 16:52 ` arnold
2022-11-12 17:05 ` Larry McVoy
2022-11-12 17:09 ` Miod Vallat
2022-11-12 17:12 ` Warner Losh
2022-11-12 17:39 ` arnold
2022-11-12 17:13 ` David Barto
2022-11-12 17:37 ` Brad Spencer
2022-11-12 18:04 ` Clem Cole
2022-11-12 18:36 ` Larry McVoy
2022-11-12 19:36 ` Clem Cole
2022-11-13 1:56 ` Larry McVoy
2022-11-12 19:16 ` Dave Horsfall [this message]
2022-11-12 19:31 ` Clem Cole
2022-11-14 11:44 arnold
2022-11-14 22:11 Paul Ruizendaal
2022-11-14 22:31 ` Clem Cole
2022-11-14 23:54 ` Warner Losh
2022-11-15 6:03 ` Theodore Ts'o
2022-11-15 15:11 ` Larry McVoy
2022-11-15 15:48 ` Bakul Shah
2022-11-15 17:47 ` Warner Losh
2022-11-15 1:21 ` Stuff Received
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=alpine.BSF.2.21.9999.2211130613290.43868@aneurin.horsfall.org \
--to=dave@horsfall.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).