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 11:19:52 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2001091116100.40155@aneurin.horsfall.org> (raw)
In-Reply-To: <0813f7fb-dd3d-e5a1-299e-42b9c34cdcf8@gmail.com>
On Thu, 9 Jan 2020, Harald Arnesen wrote:
> In my experience, macOS breaks more things these days.
Fortunately my Mac never progressed beyond Sierra due to memory
limitations or something; its other major job is as a client into my
FreeBSD server.
Slowly getting into COFF territory now, I think...
-- Dave
next prev parent reply other threads:[~2020-01-09 0:20 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 ` [TUHS] What happened with XENIX? (was Re: Unix/World Magazines) Dave Horsfall
2020-01-08 23:29 ` Harald Arnesen
2020-01-09 0:01 ` ron
2020-01-09 0:19 ` Heinz Lycklama
2020-01-09 0:19 ` Dave Horsfall [this message]
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.2001091116100.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).