🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.folklore.computers
Article #210889

Re: checking some myths.

#210889
From: Greg Pfister
Date: Mon, 30 Jul 2001 16:14
47 lines
3451 bytes
Anne & Lynn Wheeler wrote:
> 
> "Stephen Fuld" <s.f...@worldnet.att.net> writes:
> >
> > Since there have been lots of answers to number 1 and to you last paragraph,
> > but none to number 2, I'll take a shot at it.  I am far from an expert here,
> > but AFAIK you nailed one of the reasons but there are others.
> >
> > Some people run VM so thy can run lots of CMS users ...
> >
> > Some people run VM so they can take advantage of modern hardware ...
> >
> > Many independent software vendors run it to allow them to support several
> > versions of several different operating systems ...
> 
...

An important additional case was that people inside IBM ran VM so
they could more easily bring up the next version of the
"strategic" operating system - e.g., MVS (now zOS). Possibly more
than anything else, this ensured that VM would always be around.

An amusing related story: A friend of mine, who used to work on
VM in the mid-70s, particularly the Virtual Memory part (duelling
acronyms here), was having trouble getting system time on new
machines to bring up the latest version. The MVS (or whatever it
was then) folks were hogging all available machines. So one
night, he did a midnight anti-repair and sabotaged the system
console. MVS wouldn't come up without it. VM didn't care; it
could use anything able to do text I/O. Result: he got to put a
version of VM on the system, as a "favor" so the MVS folks could
continue work, using VM which provided a virtual console -- and
he could use that hardware too, to bring up the next VM release.

Related -- Once upon a time that same friend told me that you
actually have to be able to do three levels of virtualization of
memory to be general -- the top-level VM system just doing it is
not enough; you have to be able to nest a VM system virtualizing
what the top-level system is also virtualizing, and a third level
below that. I never did understand why the third level was
necessary, but this guy was very, very good and knew that code
intimately, so he was probably right.

(I knew that if I wanted long enough Lynn & Anne would fill in
lots of the other answers to the original question. :-))

Greg Pfister
Technical Details
Message-ID: <3B6587F1.96A32027@us.ibm.com>
Path: mbox-mo1.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!howland.erols.net!portc.blue.aol.com.MISMATCH!portc03.blue.aol.com!newsjunkie.ans.net!news.chips.ibm.com!newsfeed.btv.ibm.com!hanover.torolab.ibm.com!tornews.torolab.ibm.com!ausnews.austin.ibm.com!not-for-mail
References: <9ion0n$cfd$1@pyrite.mv.net> <uAY47.847$rc5.60851@news.cpqcorp.net> <rdeininger-1707011234020001@user-2iveacr.dialup.mindspring.com> <3B54A616.C42F79E7@videotron.ca> <9j48t8$dsn@web.nmti.com> <87snfqwgw6.fsf@bubulina.localdomain.localnet> <oq4rs5dkvz.fsf@premise.demon.co.uk> <uu204lxcc.fsf@earthlink.net> <oqae1uycow.fsf_-_@premise.demon.co.uk> <btP77.7402$LP2.735323@bgtnsc06-news.ops.worldnet.att.net> <uy9pcb0bb.fsf@earthlink.net>

Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!archiver1.google.com!newsfeed.google.com!sn-xit-02!supernews.com!newsfeed.direct.ca!look.ca!howland.erols.net!portc.blue.aol.com.MISMATCH!portc03.blue.aol.com!newsjunkie.ans.net!news.chips.ibm.com!newsfeed.btv.ibm.com!hanover.torolab.ibm.com!tornews.torolab.ibm.com!ausnews.austin.ibm.com!not-for-mail
From: Greg Pfister <pfi...@us.ibm.com>
Newsgroups: comp.os.vms,comp.unix.tru64,comp.arch,alt.folklore.computers
Subject: Re: checking some myths.
Date: Mon, 30 Jul 2001 11:14:41 -0500
Organization: IBM
Lines: 47
Message-ID: <3B6587F1.96A32027@us.ibm.com>
References: <9ion0n$cfd$1@pyrite.mv.net> <uAY47.847$rc5.60851@news.cpqcorp.net> <rdeininger-1707011234020001@user-2iveacr.dialup.mindspring.com> <3B54A616.C42F79E7@videotron.ca> <9j48t8$dsn@web.nmti.com> <87snfqwgw6.fsf@bubulina.localdomain.localnet> <oq4rs5dkvz.fsf@premise.demon.co.uk> <uu204lxcc.fsf@earthlink.net> <oqae1uycow.fsf_-_@premise.demon.co.uk> <btP77.7402$LP2.735323@bgtnsc06-news.ops.worldnet.att.net> <uy9pcb0bb.fsf@earthlink.net>
NNTP-Posting-Host: pfister.austin.ibm.com
Mime-Version: 1.0
X-Mailer: Mozilla 4.75 [en] (Windows NT 5.0; U)
X-Accept-Language: en,pdf
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit