Hunkeler Peter , KIUB 34 wrote:
Depends on what "release" and corresponding name you talk about.
If you go the the roots, both OSs were born in the mid 60s:
OS/360 came out in 1964.
MULTICS came out around 1965, which then became UNICS, then UNIX.
multics started about then. lots of early 545 tech sq folklore ...
mostly about cp67 and vm370 ... in melinda's history paper
http://www.princeton.edu/~melinda
but when multics (5th flr, 545 tech sq) didn't choose 360/67, but
instead GE machine ... the science center; 4th flr, 545 tech sq
http://www.garlic.com/~lynn/subtopic.html#545tech
started their own virtual memory project (which happened to also
included virtual machines) for 360/67. some of the (mit) ctss people
went to work on the 5th flr ... and some went to work on the 4th flr (so
both activities have some common heritage w/ctss).
since 360/67 hardware was not going to be immediately available, the
science center had a 360/40 modified with virtual memory hardware and
produced cp40 in 1966. when 360/67 became available in 1967, they ported
cp40 from custom modified 360/40 to 360/67 and renamed it cp/67.
cp67 was somewhat ahead of multics ... possibly because the
implementation was not as large or as complex.
multics web page
http://www.multicians.org/
there are even some cp67 stories by one of the people that worked on multics
http://www.multicians.org/thvv/360-67.html
and some ibm 7094/ctss stories
http://www.multicians.org/thvv/7094.html
some people from cambridge came out and installed cp67 at the univ the
last week in jan68 (third cp67 installation after cambridge and lincoln
labs). I did a bunch of work on cp67, especially mft and mvt running
under cp67 in virtual machine ... and was invited to spring SHARE in
houston where cp67 was announced. I then gave a talk on some of the work
at the fall68 SHARE meeting in boston. some old posts giving part of
that presentation
http://www.garlic.com/~lynn/93.html#1 360/67, was Re: IBM's Project F/S
http://www.garlic.com/~lynn/94.html#18 CP/67 & OS MFT14
http://www.garlic.com/~lynn/94.html#20 CP/67 & OS MFT14
Another item that I got to do for cp67 was adding TTY/ascii terminal
support (which plays in one of the cp67 stories from the multics site).
As part of that work, I tried to make the 2702 terminal controller do
something that it could actually do. Somewhat as a result, the univ.
started a project to build our own terminal controller; reverse engineer
ibm channel interface and build our own channel board for Interdata/3
... programmed to emulate 2702 (with some additional stuff the 2702
couldn't do). somewhere there was an article blaiming four of us for
spawning the plug compatible controller business
http://www.garlic.com/~lynn/subtopic.html#360pcm
later in POK ... getting ready for virtual memory announcement for 370,
there was an effort to basically integrate virtual memory (some of the
components from cp67) into mvt for os/vs2 SVS (instead of running mvt in
virtual machine ... ccwtrans and some other stuff from cp67 was hacked
into the side of a mvt kernel). basically mvt kernel where most of the
infrastructure thot it was running in a real 16mbyte address space ...
but was using virtual memory hardware to map the (single) 16mbyte
address space to the real machine memory.
then SVS (single virtual storage) was enhanced with multiple virtual
address space support and morped into os/vs2 mvs (multiple virtual
storage) which eventually was shortened to just mvs.
in the mid-70s, as part of getting ready for 370/xa that would come out
in the early 80s with 3081 ... work on mvs/xa was begun. up in
cambridge. the vm370 development group had grown out of the space in 545
tech sq and had moved out to the old service bureau corp. building in
burlington mall. POK convinced the corporation to shutdown burlington
mall location, kill vm370 product, and that all the vm370 development
people had to be moved to POK to support mvs/xa development (in order to
meet the mvs/xa product schedule).
some people didn't want to move ... and instead stayed in boston area,
many going to work for DEC (on things like vms). recent post referencing
16percent of vm370 group going to work for DEC (extracted from melinda's
paper)
http://www.garlic.com/~lynn/2006m.html#21
endicott managed to stave off vm370 product actually being killed and
got a few of the original development people moved to endicott ... there
is more detail in melinda's paper (however, large number of people did
move to POK as part of supporting mvs/xa development).
in some of the threads about the internal network
http://www.garlic.com/~lynn/subnetwork.html#internalnet
being larger than the arpanet/internet from just about the beginning
until possibly mid-85 ... i also slightly dig multics.
in the mid-70s, the number of vs2 and vs1 customer "batch" installations
were larger than the number of customer vm370 installations. the number
of customer vm370 installations was larger than the number of internal,
corporate vm370 installations (although in places like the internal
network ... the number of vm370 internal installations far outnumbered
any other operating system internal installations, mvs, jes2, jes3).
for a short period, while i was at the science center ... i also
personally built, distributed and supported highly modified vm370 for
small number of internal locations. however, that number was more than
the total number of all multics systems ever deployed.
also some past postings about the number of vax systems sold (by year,
us/non-us, model, etc) ... and that the number of vm 4331/4341 systems
were larger than the total number of vax systems
http://www.garlic.com/~lynn/2002f.html#0 Computers in Science Fiction
http://www.garlic.com/~lynn/2002f.html#5 Blade architectures
http://www.garlic.com/~lynn/2005f.html#37 Where should the type
information be: in tags and descriptors
http://www.garlic.com/~lynn/2005n.html#10 Code density and performance?
http://www.garlic.com/~lynn/2005n.html#11 Code density and performance?
http://www.garlic.com/~lynn/2006k.html#31 PDP-1
http://www.garlic.com/~lynn/2006l.html#17 virtual memory
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
