The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] What happened with XENIX? (was Re: Unix/World Magazines)
Date: Thu, 9 Jan 2020 09:15:14 +1100 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.9999.2001090854000.40155@aneurin.horsfall.org> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2001081009090.40155@aneurin.horsfall.org>

On Wed, 8 Jan 2020, Dave Horsfall wrote:

> I was forced to use Xenix for a contracting job (and hated it, as it was 
> almost-but-not-quite-Unix, and the differences annoyed me).  Wouldn't 
> Linux have arrived at around that time?

OK, I was out by a few years...  That job was some time in the 70/80s, and 
my memory isn't the best these days.

Similarly, I have a Penguin laptop at home for porting purposes, otherwise 
I never use it.  The cycle goes something like: get it working on both 
FreeBSD and the Mac (fairly easy), try it on the Penguin to see what 
they've broken and make the appropriate changes, then back to the Mac and 
the FreeBSD box again; repeat as necessary.  If worse comes to worst, make 
the code conditional upon the architecture (and I hate doing that, because 
it breaks the logical flow of the code).

For the record, I was porting Unify (an early RDBMS, and quite a nice one) 
to a 386...  Those damned memory models drove me crazy!  I preferred the 
small model because it was fast, but some modules were so big I had to use 
the large model which meant modifying the build script in the appropriate 
directory (no "make" in those days), and there were dozens of them.

ObTrivia: I used to use the Unify demonstration to benchmark a machine, 
and used to joke that sometimes I needed a calendar, not a clock :-)

-- Dave

  parent reply	other threads:[~2020-01-08 22:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 10:56 [TUHS] Unix/World Magazines Warren Toomey
2020-01-07 22:22 ` [TUHS] What happened with XENIX? (was Re: Unix/World Magazines) reed
2020-01-07 23:12   ` Dave Horsfall
2020-01-07 23:27     ` Warner Losh
2020-01-07 23:36       ` Adam Thornton
2020-01-08  7:46         ` Thomas Paulsen
2020-01-08 12:40           ` Matt Rudge
2020-01-08 16:56           ` Heinz Lycklama
2020-01-08 22:46             ` CHARLES KESTER
2020-01-08  7:46         ` Thomas Paulsen
2020-01-08  0:44     ` [TUHS] XENIX and Linux (was: What happened with XENIX? (was Re: Unix/World Magazines)) Greg 'groggy' Lehey
2020-01-08 22:15     ` Dave Horsfall [this message]
2020-01-08 23:29       ` [TUHS] What happened with XENIX? (was Re: Unix/World Magazines) Harald Arnesen
2020-01-09  0:01         ` ron
2020-01-09  0:19           ` Heinz Lycklama
2020-01-09  0:19         ` Dave Horsfall
2020-01-09  3:25         ` David Arnold
2020-01-09  4:56           ` Adam Thornton
2020-01-07 23:21   ` Peter Cetinski
2020-01-08  0:50   ` [TUHS] IBM PC and XENIX (was: What happened with XENIX? (was Re: Unix/World Magazines)) Greg 'groggy' Lehey
2020-01-08  2:58     ` reed
2020-01-08 12:18   ` [TUHS] What happened with XENIX? Michael Kjörling
2020-01-08 21:55     ` [TUHS] Dating quotes (was: What happened with XENIX?) Greg 'groggy' Lehey
2020-01-08 23:48       ` reed

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.2001090854000.40155@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).