From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Article on the history of cat(1)
Date: Wed, 14 Nov 2018 10:14:49 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.1811140957280.60610@aneurin.horsfall.org> (raw)
In-Reply-To: <20181113224952.GA29973@minnie.tuhs.org>
On Wed, 14 Nov 2018, Warren Toomey wrote:
>> Didn't know that cat(1) was still written in assembly on Edition 6...
>
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=V6/usr/source/s1/cat.s
Thanks; then again, I never had a reason to poke around cat(1) (but I do
remember adding a "-h" flag to pr(1) for a sub-header or something).
In fact, the only assembler stuff I remember modifying was deep in the
kernel, to take advantage of Unibus timing (on the /40 at least), where
the "obvious" code was sub-optimal; can't remember the details, but it
saved a bus cycle or two.
Hell, I wish I still had that "CSU Tape"; it was Edition 6 with as much of
Edition 7 (and AUSAM) that I could shoe-horn in, such as XON/XOFF for the
TTY driver. I was known as "Mr Unix 6-1/2" at the time...
Completely rewrote the 200-UT driver so that it actually worked (IanJ's
driver was a horrible mess) and worked around an egregious bug on the
Kronos side which they said was baked-in so deep that it couldn't be
fixed.
Rewrote the plotter driver and Versatec LV-11 driver to use the buffer
pool instead of the character queues, so they went like a bat out of hell.
Etc.
-- Dave
next prev parent reply other threads:[~2018-11-13 23:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 21:55 Warren Toomey
2018-11-13 22:44 ` Dave Horsfall
2018-11-13 22:49 ` Warren Toomey
2018-11-13 23:10 ` Arthur Krewat
2018-11-13 23:14 ` Dave Horsfall [this message]
2018-11-13 23:21 ` Rob Pike
[not found] ` <20181114004018.GA23816@minnie.tuhs.org>
2018-11-14 2:51 ` Dave Horsfall
2018-11-13 23:27 Norman Wilson
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.1811140957280.60610@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).