From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] SUN (Stanford University Network) was PC Unix
Date: Fri, 9 Apr 2021 11:18:24 -0400 [thread overview]
Message-ID: <CAC20D2MuXraLporqHpGashcuH4e4yLq=ZSep2bcCoEZWf9sRPg@mail.gmail.com> (raw)
In-Reply-To: <20210409144102.2926D18C08D@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
On Fri, Apr 9, 2021 at 10:41 AM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:
>
> The base software for the Cisco multi-protocol router was code done by
> William
> (Bill) Yeager at Stanford (it handled IP and PUP); I have a vgue memory
> that
> his initially ran on PDP-11's, like mine. (I think their use of that code
> was
> part of the scandal, but I've forgotten the details.)
>
It might have been 11/20's, but I thought he had LSIs at that point (but I
can be miss remember). It was much more sophisticated and was really
building a router, the CMU DFE was not. We wanted a terminal mux. So
were primarily interested in telnet. As I mentioned to Lars in another
thread, here is where I learned of SUPDUP for some of the LISPers. But
we
>
> > From: Tom Lyon
>
> > the design ... relied on CAD tools only extant on the Stanford
> PDP-10.
>
> Sounds like SUDS?
>
Yes -- SUDS ran on the CMU-10s and 3-River's GDPs (through the FE) -- it
was the CAD tool we used at CMU in the mid-late 1980s - the first tool I
learned.
ᐧ
[-- Attachment #2: Type: text/html, Size: 2125 bytes --]
next prev parent reply other threads:[~2021-04-09 15:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 14:41 Noel Chiappa
2021-04-09 15:18 ` Clem Cole [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-10 2:41 Jason Stevens
2021-04-09 15:34 Paul Ruizendaal via TUHS
2021-04-09 17:01 ` Dan Cross
2021-04-09 17:20 ` Lawrence Stewart
2021-04-09 18:32 ` Jon Steinhart
2021-04-09 22:28 ` Warner Losh
2021-04-10 3:16 ` Dave Horsfall
2021-04-10 12:06 ` David Arnold
2021-04-13 21:57 ` Dave Horsfall
2021-04-13 22:30 ` Bakul Shah
2021-04-15 5:01 ` Robert Brockway
2021-04-16 1:17 ` Brad Spencer
2021-04-09 5:31 Jason Stevens
2021-04-09 6:13 ` Jon Steinhart
2021-04-09 6:34 ` Rich Morin
2021-04-09 15:08 ` Clem Cole
2021-04-09 7:22 ` Lars Brinkhoff
2021-04-09 9:29 ` Lars Brinkhoff
2021-04-09 17:02 ` Al Kossow
2021-04-09 18:37 ` Lars Brinkhoff
2021-04-09 10:12 ` emanuel stiebler
2021-04-09 11:13 ` U'll Be King of the Stars
2021-04-09 17:22 ` Rob Gowin
2021-04-09 20:16 ` joe mcguckin
2021-04-10 2:22 ` Dave Horsfall
2021-04-09 14:08 ` Tom Lyon
2021-04-09 14:23 ` Jim Geist
2021-04-09 15:11 ` Clem Cole
2021-04-09 20:02 ` Earl Baugh
2021-04-09 20:08 ` Al Kossow
2021-04-09 20:46 ` Clem Cole
2021-04-10 1:30 ` Earl Baugh
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='CAC20D2MuXraLporqHpGashcuH4e4yLq=ZSep2bcCoEZWf9sRPg@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=jnc@mercury.lcs.mit.edu \
--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).