From: Dan Cross <email@example.com>
To: Warner Losh <firstname.lastname@example.org>
Cc: Jonathan Gray <email@example.com>,
Computer Old Farts Followers <firstname.lastname@example.org>
Subject: [COFF] Re: [TUHS] Re: project athena (was Re: Setting up an X Development Environment for Mac OS)
Date: Fri, 10 Feb 2023 10:33:22 -0500 [thread overview]
Message-ID: <CAEoi9W4aQTWRiYMZwXLwczaxurZYS26Y6tfN_ti7cdv=ZXVYXw@mail.gmail.com> (raw)
On Fri, Feb 10, 2023 at 10:26 AM Warner Losh <email@example.com> wrote:
> On Fri, Feb 10, 2023, 3:12 AM Lars Brinkhoff <firstname.lastname@example.org> wrote:
>> Jonathan Gray wrote:
>> >> Any chance this DOS supdup software is still around?
>> > https://web.mit.edu/Saltzer/www/publications/pcip-1985.pdf
>> > http://www.bitsavers.org/bits/MIT/pc-ip/
>> Great, thanks!
>> It's a bit sad to read in supdup.mss "Unfortunately, very few machines
>> have TCP/Supdup servers. The only servers known to us are on Mit-MC and
>> Su-AI, and 4.2 Unix machines running a server we distribute." At this
>> point, three old ITS machines had recently fallen over, one after the
>> other, and MC was the only one left standing. But not long after, four
>> new ones would appear. One of which is still up and running!
> I wonder if this was the same supdup that the early BSDs used to distribute their source in the 90s ..
I believe they are entirely different.
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?
The SUPDUP protocol used by ITS hosts was a "Display Protocol" based
on TELNET: https://www.rfc-editor.org/rfc/rfc734
I think the similarity in naming was just a coincidence.
- Dan C.
next prev parent reply other threads:[~2023-02-10 15:34 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 [this message]
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
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).