The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Mike Haertel <tuhs@ducky.net>
To: The Unix Heritage Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Blit source
Date: Wed, 18 Dec 2019 19:47:02 -0800	[thread overview]
Message-ID: <201912190347.xBJ3l2sF064230@ducky.net> (raw)
In-Reply-To: <CAKzdPgz37wwYfmHJ_7kZx_T=-zwNJ50PhS7r0kCpuf_F1mDkww@mail.gmail.com>

Norman wrote:
> The V8 tape was made in late 1984 (I know that for sure
> because I helped make it).  It is unlikely to have anything
> for the MC68000 Blit, only stuff for the Mac-32 Jerq.

The V8 tape has the Blit stuff in /usr/blit, and the 5620 stuff
in /usr/jerq.  The Blit stuff looks somewhat older, and doesn't
have exactly the same graphics library functions as the 5620.

It would be interesting to see a chronology of the evolution of
these window systems.

Rob wrote:
> If 5620s were called Jerqs, it was an accident. All the software with that
> name would be for the original, Locanthi-built and -designed 68K machines.

That's amusing, considering that the 5620 stuff was in /usr/jerq on
Research systems!  Apparently the accident became institutionalized.

	Mike

  reply	other threads:[~2019-12-19  4:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-19  0:16 Norman Wilson
2019-12-19  0:26 ` Rob Pike
2019-12-19  3:47   ` Mike Haertel [this message]
2019-12-19  6:49     ` Angelo Papenhoff
2019-12-19  5:12   ` Dan Cross
2019-12-19  6:54     ` Rob Pike
2019-12-19  8:03       ` arnold
2019-12-19 15:32       ` Chet Ramey
  -- strict thread matches above, loose matches on Subject: below --
2020-01-06 21:01 Norman Wilson
2019-12-19  9:09 Paul Ruizendaal
2019-12-15 20:45 Paul Ruizendaal
2019-12-15 21:17 ` Angelo Papenhoff
2019-12-16  6:25 ` emanuel stiebler
2019-12-16 11:06   ` Paul Ruizendaal
2019-12-17  6:04     ` emanuel stiebler
2019-12-18  3:53   ` Paul Ruizendaal
2019-12-18  4:30     ` Rob Pike
2019-12-18 10:43     ` Julius Schmidt
2019-12-18 12:11       ` Angelo Papenhoff
2019-12-18 15:53         ` Dan Cross
2019-12-18 12:19       ` Paul Ruizendaal
2019-12-19  0:20   ` Paul Ruizendaal

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=201912190347.xBJ3l2sF064230@ducky.net \
    --to=tuhs@ducky.net \
    --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).