From: steve jenkin <sjenkin@canb.auug.org.au>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: origin of null-terminated strings
Date: Sat, 17 Dec 2022 14:42:59 +1100 [thread overview]
Message-ID: <CF112B27-B714-4DC6-8B05-6E5FD7F77278@canb.auug.org.au> (raw)
In-Reply-To: <CAKH6PiUWY88BbJBiXoS4GKauv49qZTHvef5Rz3_qBn7v4ccX7A@mail.gmail.com>
> On 17 Dec 2022, at 09:26, Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:
>
>>
>> was any thought given to trying to get a 360 system?
>
> Very serious thought. However, virtual memory was a non-negotiable
> desideratum, to which Gene Amdahl was implacably opposed because
> demand paging would devastate hardware performance. Soon after GE got
> the nod, IBM revealed Gerrit Blaauw's skunk-works project, the 360/67,
> but by then the die had been cast. Michigan bought one and built a
> nice time-sharing system that was running well before Multics.
>
> Doug
Doug,
Thanks for the insight.
I've seen “MTS” mentioned, but never properly understood its significance.
Never looked into it, either :(
Brief search results below, w/o Wikipedia etc.
A process step of building new ’things’, skipped on all computing / I.T. projects I worked on,
is a “Post Mortem” a.k.a “Post Implementation Review”.
If MIT / Bell Labs / GE ever did a project review on Multics, I’d love to know if it’s been published,
and what insights they came away with,
and any changes made to their development & project management processes.
The MIT lead, Corbató / Corby, had demonstrated a high-level of competence & ability.
He'd built CTSS in 1961 and won the ACM Turing Award in 1990. Never given to "second best”.
It wasn’t a lack of talent, need, desire (for a product/service to sell) or funding that made Multics take years & years.
With the capability & experience of the people involved, it'd be simplistic and superficial to attribute
the project delays to “Second System Effect”.
Is it more akin to what we’re seeing now in the differences in approach to building Space Launch Systems & Vehicles?
I don’t have words/ concepts for the different approaches, but they seem to parallel how Multics & Unix were developed.
- NASA & Boeing et al have only just flown the Space Shuttle replacement, Artemis, the SLS pluse Orion capsule.
In 2005, a program to replace the Shuttle (retired in 2011) was begun.
This was replaced with the SLS / Artemis program in 2010 - reusing many of the Shuttle components, eg RS-25 engines.
Next flight, Artemis 2, due in 2024.
- Space-X is developing it’s second launch system, plus a Crew / Cargo vehicle (StarShip).
Falcon 9 has become the cheapest per kg/LEO, most reliable and most flown rocket in history.
They’ve already beaten 1 launch/week this year, lofting 150+ tons per quarter into LEO.
Which is more than two-times all other programs, public or private, put together.
steve j
========
David L. Mills, photo gallery & some comments
Michigan Terminal System (MTS)
<https://www.eecis.udel.edu/~mills/gallery/gallery8.html>
During much of the 1960s I was a staff member at the U Michigan Computing Center.
I worked with a bunch of other guys on various hardward and software projects,
one of which is described on this page.
========
Organization and features of the Michigan terminal system
Michael T. Alexander
16 November 1971
<https://dl.acm.org/doi/abs/10.1145/1478873.1478951>
ABSTRACT
This paper will explore some aspects of the Michigan Terminal System (MTS) developed at the University of Michigan.
MTS is the operating system used on the IBM 360/67 at the University of Michigan Computing Center,
as well as at several other installations.
It supports a large variety of uses ranging from very small student-type jobs to large jobs requiring several million bytes of storage and hours of processor time.
Currently at the University of Michigan there are about 13,000 users running as many as 86,000 jobs per month.
========
Time-sharing in the IBM system/360: model 67
Charles T. Gibson
IBM
<https://dl.acm.org/doi/abs/10.1145/1464182.1464190>
Fine detail of 360/67, differences to /50.
TSS mentioned
========
--
Steve Jenkin, IT Systems and Design
0412 786 915 (+61 412 786 915)
PO Box 38, Kippax ACT 2615, AUSTRALIA
mailto:sjenkin@canb.auug.org.au http://members.tip.net.au/~sjenkin
next prev parent reply other threads:[~2022-12-17 3:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 22:26 Douglas McIlroy
2022-12-17 2:03 ` James Frew
2022-12-17 3:42 ` steve jenkin [this message]
2022-12-17 17:11 ` Clem Cole
2022-12-17 18:15 ` Tom Lyon
2022-12-17 18:43 ` Clem Cole
2022-12-17 18:46 ` Clem Cole
2022-12-17 19:26 ` Tom Perrine
2022-12-19 4:26 ` Adam Thornton
-- strict thread matches above, loose matches on Subject: below --
2022-12-16 23:11 Noel Chiappa
2022-12-16 3:02 [TUHS] " Douglas McIlroy
2022-12-16 3:14 ` [TUHS] " Ken Thompson
2022-12-16 9:13 ` Dr Iain Maoileoin
2022-12-16 13:42 ` Dan Halbert
2022-12-16 16:10 ` Dan Cross
2022-12-16 16:22 ` Tom Lyon
2022-12-16 16:29 ` Jon Steinhart
2022-12-16 20:12 ` Dave Horsfall
2022-12-16 21:02 ` Warner Losh
2022-12-16 21:13 ` Clem Cole
2022-12-16 21:49 ` Clem Cole
2022-12-17 0:26 ` Phil Budne
2022-12-16 21:18 ` Luther Johnson
2022-12-16 21:20 ` Dan Halbert
2022-12-16 3:17 ` Steve Nickolas
2022-12-16 17:24 ` John P. Linderman
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=CF112B27-B714-4DC6-8B05-6E5FD7F77278@canb.auug.org.au \
--to=sjenkin@canb.auug.org.au \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=tuhs@tuhs.org \
/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).