From: arrigo@alchemistowl.org (Arrigo Triulzi)
Subject: [TUHS] Scot Hacker's 1999-2001 "BeView" columns for Byte.com (BeOS)
Date: Wed, 17 Jan 2018 19:54:19 +0100 [thread overview]
Message-ID: <507B30A4-6923-4DA3-A7CE-3E0AEE991791@alchemistowl.org> (raw)
In-Reply-To: <CAJfiPzycHUUnmWRDgsYRT1y5KqxMcriTG0bU=0x0_ROCwuhipA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
On 17 Jan 2018, at 19:32, Nemo <cym224 at gmail.com> wrote:
>
>> On 17 January 2018 at 05:26, Arrigo Triulzi <arrigo at alchemistowl.org> wrote:
>> Scot Hacker has re-published his BeOS columns for Byte. BeOS was an interesting
>> operating system with a clear Unix inheritance built for a dual-PowerPC system,
>> similar to the Macs of that era.
>
> Not just dual-PPC. I ran an early copy on my Motorola Apple-clone.
Should have clarified: the original BeBox was a dual-PPC system. BeOS also ran on PREP and other Mac clones (as did, briefly, MacOS…).
Arrigo
prev parent reply other threads:[~2018-01-17 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 10:26 Arrigo Triulzi
2018-01-17 18:32 ` Nemo
2018-01-17 18:54 ` Arrigo Triulzi [this message]
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=507B30A4-6923-4DA3-A7CE-3E0AEE991791@alchemistowl.org \
--to=arrigo@alchemistowl.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).