From: Clem Cole <clemc@ccc.com>
To: Matthias Bruestle <m@mbsks.franken.de>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Thoughts on Licenses
Date: Sun, 3 Jul 2022 18:40:18 -0400 [thread overview]
Message-ID: <CAC20D2O5OZkfuUQXHeYDShS=PXsLoCsyWyQqUzxP2JPhROgfeQ@mail.gmail.com> (raw)
In-Reply-To: <YsII0xewN8ZtUVcL@mbsks.franken.de>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
Sorry for some of us old guys vax = 780
ᐧ
On Sun, Jul 3, 2022 at 5:30 PM Matthias Bruestle <m@mbsks.franken.de> wrote:
> On Sun, Jul 03, 2022 at 03:48:33PM -0400, Clem Cole wrote:
> > single custom application* that allows us to manage the server - as I
> said
> > to Larry think the LS1-11 on the Vax and the 11/40 on the KL processors)
>
> I have a MicroVAXII with a KMV1A. Are you refering to such a card with
> the "LSI-11 on the Vax"? Does this mean there is a V7 running on it?
> I really don't know much about that card. Might have been used for I/O with
> an IBM 3090 in this computer.
>
> Matthias
>
> --
> When You Find Out Your Normal Daily Lifestyle Is Called Quarantine
>
[-- Attachment #2: Type: text/html, Size: 1401 bytes --]
next prev parent reply other threads:[~2022-07-03 22:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 18:15 [TUHS] " Clem Cole
2022-07-02 19:07 ` [TUHS] " Marc Donner
2022-07-02 20:57 ` Warner Losh
2022-07-02 21:02 ` Larry McVoy
2022-07-02 23:54 ` Clem Cole
2022-07-03 2:03 ` Warner Losh
2022-07-03 2:27 ` Larry McVoy
2022-07-03 8:11 ` steve jenkin
[not found] ` <F579710B-5568-431D-92CC-88D49C3D9BE6@gmail.com>
2022-07-03 14:39 ` Larry McVoy
2022-07-03 14:59 ` Clem Cole
2022-07-03 15:30 ` Bakul Shah
2022-07-03 16:26 ` Clem Cole
2022-07-03 16:55 ` Kevin Bowling
2022-07-03 17:15 ` Clem Cole
2022-07-03 17:48 ` Bakul Shah
2022-07-03 19:48 ` Clem Cole
2022-07-03 21:23 ` Matthias Bruestle
2022-07-03 22:40 ` Clem Cole [this message]
2022-07-04 3:01 ` Norman Wilson
2022-07-04 12:33 ` Paul Winalski
2022-07-03 21:38 ` Jay Logue via TUHS
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='CAC20D2O5OZkfuUQXHeYDShS=PXsLoCsyWyQqUzxP2JPhROgfeQ@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=m@mbsks.franken.de \
--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).