From: peter@rulingia.com (Peter Jeremy)
Subject: [TUHS] Early Clones / Rewrites for TUHS archives
Date: Mon, 18 Dec 2017 21:10:55 +1100 [thread overview]
Message-ID: <20171218101055.GA46385@server.rulingia.com> (raw)
In-Reply-To: <CAC20D2O=8BNUkxF6C3-T+EydQAjp-sCo=MTkcFvmxwFx3CKVOg@mail.gmail.com>
On 2017-Dec-12 09:40:31 -0500, Clem Cole <clemc at ccc.com> wrote:
>My question about SOL got me thinking a bit. It would be nice to have
>section in TUHS of any early clones that could be collected.
One thing I haven't seen mentioned is QNX - I didn't directly use it but a
colleague was using it in the mid-1980s on PC-AT class hardware. ISTR one
of my colleague's whinges was the 256-byte command-line limit.
My earliest exposure would have been Xenix on a 286 - my main recollections
are:
1) The Pascal compiler that didn't ignore comments (changing a comment
could make the code fail to compile with an obscure error.
2) The fork() system call could sometimes return -1 to the parent, even when
it succeeded - that caused a lot of head-scratching.
3) Hacking one of the Emacs clones (I no longer recall which) to use "far"
pointers for the buffers, so I could edit files >64K without paying the
performance penalty of writing "large model" code. (286 protected-mode
performance was abyssmal if it needed to do segment descriptor loads)
Unfortunately, I no longer have that code.
--
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171218/19138453/attachment.sig>
next prev parent reply other threads:[~2017-12-18 10:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 14:40 Clem Cole
2017-12-12 16:29 ` Random832
2017-12-12 16:41 ` Random832
2017-12-13 4:16 ` Jason Stevens
2017-12-13 21:22 ` Nemo
2017-12-14 0:26 ` Robert Swierczek
2017-12-18 10:10 ` Peter Jeremy [this message]
2017-12-18 15:46 ` Larry McVoy
2017-12-18 15:57 ` Steve Nickolas
2017-12-18 15:59 ` Larry McVoy
2017-12-18 16:13 ` Steve Simon
2017-12-18 16:18 ` Arthur Krewat
2017-12-18 16:15 ` Henry Bent
2017-12-18 16:34 ` Andy Kosela
2017-12-18 16:39 ` Gregg Levine
2017-12-18 17:35 ` Steve Simon
2017-12-18 17:41 ` Toby Thain
2017-12-18 18:41 ` Brad Spencer
2017-12-18 16:37 ` Gregg Levine
2017-12-18 18:32 ` Bakul Shah
2017-12-18 16:53 ` Clem Cole
2017-12-18 17:08 ` Kurt H Maier
2017-12-12 15:16 Noel Chiappa
2017-12-12 16:01 ` Warner Losh
2017-12-13 2:15 ` Nigel Williams
2017-12-13 13:46 ` Clem Cole
2017-12-13 16:58 ` Larry McVoy
2017-12-13 19:03 ` Clem Cole
2017-12-16 4:50 ` Dave Horsfall
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=20171218101055.GA46385@server.rulingia.com \
--to=peter@rulingia.com \
/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).