From: Paul Winalski <firstname.lastname@example.org>
To: Warner Losh <email@example.com>
Cc: segaloco <firstname.lastname@example.org>, COFF <email@example.com>
Subject: [COFF] Re: VAX/VMS 4.4 Source Listing?
Date: Tue, 7 Feb 2023 11:40:36 -0500 [thread overview]
Message-ID: <CABH=_VSLsYd6tBe_VsD23zK41ZGg=pgKdT3WDobyPqCtAwR3GA@mail.gmail.com> (raw)
On 2/6/23, Warner Losh <firstname.lastname@example.org> wrote:
> On Mon, Feb 6, 2023, 1:25 PM Clem Cole <email@example.com> wrote:
[quoting a VMS developer friend of his]
>> *I had a complete copy of the master source pack in Marlborough during
>> Aquarius development/debug time; I know I put backup tape of that into
>> CHM. That has the CMS library which would go back to at least V1. (That
>> would be c.a. 1987-9.) But the master*
>> V1 is 77-79... or is the CMS from that time?
I worked at one of the VAX-11/780 hardware beta test sites back in
1977-79. The machine ran VAX/VMS verison X0.5 at first, later
upgraded to V1.0.
I joined DEC in 1980 in the Methods & Tools software engineering
group. At that time they were working on a tool called the System for
Tracking the Evolution of Programs (STEP). This was a version control
system using ideas from Unix's SCCS. The name STEP had trademark
issues and so it was rechristened Code Management System (CMS). I
think it was first released by DEC as a product in 1982.
STEP would have been in early stages of development during the time
that VMS 1.0 was being developed. The VMS group at that time used a
tool called SLP as the core of their configuration management system.
SLP could compare two versions of a text file and create a patch file
(these were called "slipper packets") to convert one into the other.
Configuration management consisted of keeping collections of slipper
The VMS development group converted to CMS ca. 82/83. I don't know
which version of VMS was the base version for their CMS library. They
probably started with the archived V1.0 release sources. But their
CMS library would not have recorded the development history of V1.0.
prev parent reply other threads:[~2023-02-07 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 17:37 [COFF] " segaloco via COFF
2023-02-06 20:23 ` [COFF] " Clem Cole
2023-02-06 20:36 ` Warner Losh
2023-02-07 16:40 ` Paul Winalski [this message]
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).