4 ms·
That's an interesting path to think about. Minus UNIX, I'm curious where MVS, OS/400, VMS, MPE, DOS/Windows, etc, would have all played out.
by tyingq 9y ago
That's an interesting path to think about. Minus UNIX, I'm curious where MVS, OS/400, VMS, MPE, DOS/Windows, etc, would have all played out.
- Taniwha 9y agowell VMS still exists .... both as itself and as the underpinnings of WindowsNT (and modern windows)
- ghaff 9y agoMany are still around to some degree. OS/400 is now IBM i. MVS is now z/OS (for IBM mainframes). OpenVMS as you say. Most of the operating systems that were originally written for minicomputers aren't radically different in fundamental design from Unix and Windows NT. My suspicion is that, absent Unix or something that followed a similar historical trajectory, these OSs would have had a longer run as non-legacy products, the landscape would have been even more fractured than it was with the Unix wars, and Windows would have become more dominant in the server space than it eventually became. The question I really don't know the answer to is whether, given the rise of the mainstream Internet, an open source operating system and infrastructure software necessarily would have followed. Or would the world look very very different.
- bitwize 9y agoWhile it's true that Dave Cutler incorporated many ideas from VMS into Windows NT... they are very different beasts with very different code bases. Not even related in the same way that, say, Unix and Linux are.
- dredmorbius 9y agoVM/CMS (another mainframe variant) may have played a stronger role. It in many aspects resembles Unix, far more than MVS.
- skissane 9y agoWhat specific features of VM/CMS are you thinking of when you say that? If anything, I would say it is the other way around. The classic MVS filesystem is more hierarchical than the classic CMS filesystem (when I say "classic", I mean ignoring newer innovations such as SFS, BFS, HFS and zFS). The components of MVS dataset names resemble directories, even though they are mostly (but not entirely) just a naming convention. By contrast, the classic CMS filesystem (pre-SFS/BFS) has an essentially flat namespace on each minidisk – its file naming is closer to PC-DOS 1.0 than to Unix. So, even though both filesystems are quite remote from Unix, the MVS filesystem is a little bit closer to Unix's than the CMS filesystem is. Also, if you compare the support for multitasking on MVS to VM/CMS, I think you'll find that MVS is closer to Unix. A single MVS operating system image has multiple address spaces (processes) each containing one or more tasks (threads). By contrast, VM/CMS works by running a single-tasking operating system (CMS) in separate virtual machines on top of a hypervisor (although more recent CMS versions have added "application multitasking" which is roughly equivalent to threads). Although neither is exactly the same as the Unix model of processes and threads, MVS is much closer to Unix than VM/CMS is in this area. Given that, it is actually much easier to implement the Unix process model on top of MVS than on top of CMS, which I suspect is why MVS OpenEdition / z/OS Unix System Services comes with a full-featured fork() implementation (which passes the Unix conformance test suite), while CMS OpenExtensions' fork() isn't really fork() at all, it is actually vfork() pretending to be fork().
- dredmorbius 9y agoI've not used CMS, though I have used, long ago, MVS. My understanding is that CMS followed in its genesis and development spirit a bit more of the Unix development mode. It was more popular among (at least some) users, and as I understood it, a bit of an ugly stepchild / embarrassment to IBM, who considered MVS the more buttoned down, business-oriented, product. This is based on some long-ago, hazy, second-hand accounts, mind.
- skissane 9y agoI agree with your recollections in that VM/CMS had culturally more in common with Unix, even though technically they had very little in common at all. In the 1970s through 1980s, VM/CMS saw a lot of use as a research computing platform, there was a lot of scientific software available for it. VM/CMS was used as a development platform by many groups within IBM, when some other platform was the target–for example, developers writing the AS/400 operating system, OS/400, wrote their code and compiled it under VM/CMS and then transferred it to AS/400 for execution/testing. (Later they moved to AIX instead; OS/400 is somewhat unusual in being an operating system that has never been self-hosting, never been able to compile itself.) VM/CMS tended to get new features added to it organically, because some user or team felt the need and just implemented it; the product direction of MVS was much more tightly controlled by IBM management. So VM/CMS was the birthplace of IBM's mainframe email products, peer-to-peer networking (used for the BITNET academic network), the REXX programming language, pipelines (inspired by Unix pipelines but different), etc. Many of those features were later ported to MVS. In the early 1980s, IBM planned to ship workstations running VM/CMS, hoping that academic/scientific users and developers used to VM/CMS on a central mainframe would like to run it on their desks. This plan never really took off, in part because a lot of those users were already moving to Unix, and Unix workstations had a better price-performance ratio; if Unix wasn't around, maybe IBM's plan would have been more successful.