From: Dan Halbert <halbert@halwitz.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] non-UNIX timesharing at Bell Labs ca 1972?
Date: Thu, 11 Mar 2021 12:45:55 -0500 [thread overview]
Message-ID: <24f208ce-0050-884d-0799-d23b7f34704a@halwitz.org> (raw)
In-Reply-To: <32AC3AC9-1C57-49A0-8F94-742E9D06FAD9@blat.at>
On 3/11/21 12:00 PM, Mike Knell wrote:
>> On 11.03.2021, at 16:26, Dan Halbert <halbert@halwitz.org> wrote:
>>
>> In 1972, while in high school, I went to an Intel seminar on the 8008. There I met a Bell Labs scientist who gave me a sample 8008 and invited me for a visit at some NJ Bell Labs facility. That group had a timesharing system of some kind, but it was not Unix. I was also given a Bell Labs speech synthesis kit after meeting one of the speech scientists who happened to be in on the same Saturday. I have searched my attic but can't find further details. Would any of you alumni recall what this other timesharing system might have been?
> Not an alumnus of anything (alas, I am far too young and not clever enough), but maybe this was GECOS? (Origin of the name of the pw_gecos field in UNIX..)
>
> Mike
I do not think it was GECOS. I have a memory of him demonstrating a
FOCAL- or BASIC-esque language running on some commercial minicomputer,
but it was not one of those and I don't think it was a DEC machine.
Perhaps it was not timesharing, but he showed it to me from his office
terminal, I think, not in a lab.
prev parent reply other threads:[~2021-03-11 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 15:26 Dan Halbert
2021-03-11 17:00 ` Mike Knell via TUHS
2021-03-11 17:45 ` Dan Halbert [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=24f208ce-0050-884d-0799-d23b7f34704a@halwitz.org \
--to=halbert@halwitz.org \
--cc=tuhs@minnie.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).