From: Warner Losh <firstname.lastname@example.org>
To: Dan Cross <email@example.com>
Cc: Jonathan Gray <firstname.lastname@example.org>,
Computer Old Farts Followers <email@example.com>
Subject: [COFF] Re: [TUHS] Re: project athena (was Re: Setting up an X Development Environment for Mac OS)
Date: Fri, 10 Feb 2023 11:44:32 -0700 [thread overview]
Message-ID: <CANCZdfpnOWLHAuFjWCrn+v7mw8ukE4fvgiTxBdn1XX1j2FS8_Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2967 bytes --]
On Fri, Feb 10, 2023 at 10:20 AM Dan Cross <firstname.lastname@example.org> wrote:
> On Fri, Feb 10, 2023 at 10:44 AM Clem Cole <email@example.com> wrote:
> > On Fri, Feb 10, 2023 at 10:34 AM Dan Cross <firstname.lastname@example.org> 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.
The original sup was on the 4.4BSD tapes, and was written in C' It may
have come from Mach.
> 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:
Yes. FreeBSD didn't offer anoncvs because CVS was so terrible at handling
high rate of change for the FreeBSD project. I don't think any of the other
BSD projects ever used it officially, but I have a vague memory of there
unofficial NetBSD and OpenBSD mirrors. The latter two projects focused on
using anoncvs, to the present day (though both now have git and other
DragonFlyBSD used it briefly since it started with CVS and then
git, when it stopped using it entirely.
> `csup` was a reimplementation in C (without the GUI part, I imagine)
> because the Modula-3 dependency was a pain.
Yes. The compilers were slow to update, the old ones stopped working
due to the compilers heavy knowledge of threads, which were undergoing
flux in the base FreeBSD system, so updates were always tricky. Plus
there were issues with different upstreams accepting FreeBSD patches
for various reasons that I have only a vague recollection of. There were two
or three compilers, IIRC: The original DEC one, then an egcs based one
and then a gcc one when egcs and gcc "reunited"... This was an unbelievable
pain, with few people knowing how to properly do a bringup and John retiring
or becoming semi-retired in this time period.
> >> 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.
[-- Attachment #2: Type: text/html, Size: 4534 bytes --]
next prev parent reply other threads:[~2023-02-10 18:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
[not found] ` <3h5FEAegoTs6FrhHODiW-rBdB59dt_Rmr4G0PIw7flqaJLsmorgPsilm4f2aJkDud-qEljDjnCJcE1uY05Iw4HNQcyNG4W3wzVlLD0UZfLgfirstname.lastname@example.org>
[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+Rfo2QQf9vcsemail@example.com>
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
2023-02-10 18:33 ` Lars Brinkhoff
2023-02-10 18:43 ` Lars Brinkhoff
2023-02-10 18:44 ` Warner Losh [this message]
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
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).