From: Dan Cross <crossd@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: Jonathan Gray <jsg@jsg.id.au>,
Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: project athena (was Re: Setting up an X Development Environment for Mac OS)
Date: Fri, 10 Feb 2023 12:19:25 -0500 [thread overview]
Message-ID: <CAEoi9W6-XmdFWCB4gXRDLCBhOAc=ZejA94G7VYBDcojK92EdVA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2N3Qx+iHBxPZT-h8b_ppCRWSytk7ZvcH1qQYrhSsjWjtA@mail.gmail.com>
On Fri, Feb 10, 2023 at 10:44 AM Clem Cole <clemc@ccc.com> wrote:
> On Fri, Feb 10, 2023 at 10:34 AM Dan Cross <crossd@gmail.com> wrote:
>> If I recall correctly (and it's been a while...) csup, CVSup, et al
>> were based on `sup`, which was a file distribution tool somewhat like
>> `rdist`, which came from CMU. csup/cvsup was optimized for moving
>> source code deltas (a la CVS repositories) around. I recall a
>> graphical client written in Modula-3?
>
> Right -- ??maybe?? Bob Baron or one of the Mach guys did it - used the DEC Modula-3 IIRC.
That sounds right for `sup`. I vaguely remember it being associated
with Coda, as well? I believe the BSDs used it to distribute source
code (in addition to or instead of anoncvs?) in the 90s.
It looks like CVSup was done by John Polstra in Modula-3. It was being
used for FreeBSD in at least 1996, but I don't know when they started
using it. It's mostly disappeared, but archive.org has a snapshot of
its old web site:
https://web.archive.org/web/20060103034312/http://www.cvsup.org/faq.html
`csup` was a reimplementation in C (without the GUI part, I imagine)
because the Modula-3 dependency was a pain.
>> The SUPDUP protocol used by ITS hosts was a "Display Protocol" based
>> on TELNET: https://www.rfc-editor.org/rfc/rfc734
>
> Exactly - popular with the LISP hackers. I started to implement it in the CMU Distributed Front-End years ago but never finished it - I don't know if it was ever completed.
Oh yeah, I imagine it was implemented on Lisp machines, probably for
connecting to ITS. Lars, do you know?
- Dan C.
next prev parent reply other threads:[~2023-02-10 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3e272d72-b77a-d347-b5c3-7ed19482e5af@gmail.com>
[not found] ` <3h5FEAegoTs6FrhHODiW-rBdB59dt_Rmr4G0PIw7flqaJLsmorgPsilm4f2aJkDud-qEljDjnCJcE1uY05Iw4HNQcyNG4W3wzVlLD0UZfLg=@protonmail.com>
[not found] ` <CAFH29trXu_SGp-7xv6xqMc49tTeEuyJdKwP-Fyfe6BCrpGZ9nQ@mail.gmail.com>
[not found] ` <Y9GIus/Iw21uvkFb@mit.edu>
[not found] ` <Y+QeTCCJf3UHagiP@largo.jsg.id.au>
[not found] ` <Y+Rfo2QQf9vcs+l1@mit.edu>
2023-02-10 6:19 ` Lars Brinkhoff
[not found] ` <Y+X1ulTtZRoKHCRO@largo.jsg.id.au>
2023-02-10 10:12 ` Lars Brinkhoff
2023-02-10 15:25 ` Warner Losh
2023-02-10 15:33 ` Dan Cross
2023-02-10 15:44 ` Clem Cole
2023-02-10 17:19 ` Dan Cross [this message]
2023-02-10 18:33 ` Lars Brinkhoff
2023-02-10 18:43 ` Lars Brinkhoff
2023-02-10 18:44 ` Warner Losh
2023-02-10 18:53 ` Warner Losh
2023-02-10 18:21 ` Lars Brinkhoff
2023-02-10 20:21 ` Lars Brinkhoff
2023-02-10 18:34 ` Warner Losh
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='CAEoi9W6-XmdFWCB4gXRDLCBhOAc=ZejA94G7VYBDcojK92EdVA@mail.gmail.com' \
--to=crossd@gmail.com \
--cc=clemc@ccc.com \
--cc=coff@tuhs.org \
--cc=jsg@jsg.id.au \
/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).