7 ms·
OpenVMS has real asynchronous I/O supported directly by the kernel. Under Linux, all I/O is synchronous but possibly nonblocking, and all disk I/O is blocking.
by bitwize 7y ago
OpenVMS has real asynchronous I/O supported directly by the kernel. Under Linux, all I/O is synchronous but possibly nonblocking, and all disk I/O is blocking. OpenVMS also has a comprehensive, fine-grained security model involving a database of subjects, actions, and objects, giving administrators fine control over who may do what to what. In short, ACLs built into the OS from the ground up. In Linux, ACLs are a bag on the side; their inclusion in BSDs varies. OpenVMS also automatically logs all events, providing an audit trail for security incidents. OpenVMS clusters easily (called a VAXcluster in the VAX days); support for failover and load balancing is built into the OS. OpenVMS's command line interface is designed around a mistake-prone operator who hasn't had their coffee. It doesn't have, say, the 'rm -rf /' problem. Unix's CLI assumes a perfect operator who gets everything right the first time. "Fat fingering" a command could have disastrous consequences; in most cases on VMS, the command interpreter will raise a syntax error. OpenVMS also has file versioning built into the file system; again, this is a bag on the side (formerly: SCCS/RCS, today: git) in Unix.
Oh, and OpenVMS doesn't crash. Like, ever.
Windows Server has some of these features. The NT kernel has the same designer as VMS -- Dave Cutler, a man whose contempt for the Unix design philosophy is well documented.
- eej71 7y agoOpenVMS absolutely does crash. I was actively involved with a very large cluster - and with enough abuse - individual nodes will tip over - and if you aren't careful - you can take down an entire cluster. It was an interesting OS. Some different ideas in there. But the idea that it never crashes is simply false.
- technofiend 7y agoAnecdotally, VMS had a command to exclusively allocate resources which I learned on a predecessor OS RSTS/E. Predecessor in the sense that some command syntax carried over; I have no clue how much RSTS/E source if any made its way into VMS. Regardless, the idea was you would ALLOC the line printer or tape drive to prevent anyone else from stepping on you. At Digital's NCC booth in 1981 or 1982 (I forget) they were showing off clustered VAXes with the nodes named after colors. I jokingly typed ALLOC RED:: and discovered that allocating an entire node to yourself crashed the cluster.
- ithkuil 7y agoFWIW, linux got pretty decent true async IO with io_uring, at last.
- OrangeMango 7y agoCluster-wide batch queues built-in, a cluster-wide file system, etc. Samba support is awful, though.
- eej71 7y agoYes and TCP/IP support in general on VMS was not great. Performance was a consistent problem. It was clearly a second class citizen for a very long time.
- OrangeMango 7y agoPart of my day job is maintaining our home-grown data processing system on an old VMS (Itanium) cluster. We've been trying to get rid of it for close to 7 years now but don't seem much closer than when we started. For things that OpenVMS is good at, it is REALLY good at. Everything else... is pretty antiquated.
- cturner 7y agoDid VMS TCP/IP support suffer due to poor effort from Digital, or as an inherent side-effect of the kernel design? Could poor TCP/IP performance have been a consequence of 'real asynchronous I/O support'? Berkeley sockets is obnoxious [Example]. But the advanced user can get fine control over it. If you have a use-case that is vulnerable to back-pressure, with Berkeley sockets you can manage that away. Some friendlier API designs would have worse options. Berkeley sockets is ubiquitous, and there is not much to compare it to. Insights from VMS would be interesting. -- :Example. A selector indicates that a socket is ready for read/write. But what that actually means is contextual, depending on whether it was created as a client or server socket. You can't attach metadata to the socket to assist with that. Rather, you have to maintain parallel structures.
- eej71 7y agoIMO, one of the significant scaling bottlenecks for VMS was there were only a handful of spinlocks that governed kernel activity. The one that I remember was IOLOCK8 (sp?). Any ethernet frame handling would have to hold that for a period of time. The underlying code that those stacks use to manage their inbound ethernet frames is likely quite old and would require significant work to reduce contention around that lock. To put it differently, a modern 10 gig ethernet card likely generates too much traffic to be effectively handled by that code. And if you had more than one 10 gig card in a box, they would contend around that common spin lock.
- wicket 7y ago> OpenVMS's command line interface is designed around a mistake-prone operator who hasn't had their coffee. It doesn't have, say, the 'rm -rf /' problem. Unix's CLI assumes a perfect operator who gets everything right the first time. Funny you should say that. On a VMS build server, I was once cleaning up a build and ran a "DEL [...]* .OBJ;*" (HN auto-formatting doesn't allow me to display this properly without inserting a space after the first asterisk). I started to wonder why it was taking a very long time to complete when it hit me... I had run it from the root-level of DKA0:, not from the build directory. Needless to say, the entire OS had to be restored/rebuilt. This is easily the biggest mistake I have made in my 20-year career as a sysadmin (or system manager as we call it in the VMS world). Don't get me wrong, I love VMS for many of the reasons you've stated, and more; I wish it was more widely used in the industry. But don't be fooled; you don't need to be on a Unix system to make mistakes of disastrous consequences. They can happen anywhere!
- mongol 7y agoI remember when I developed Java for OpenVMS. On Unix you send a kill signal to get a thread dump from the Java process. On OpenVMS you sent a mail to the process! Something like a mail, it was not a SMTP mail but mail-like.
- ch_123 7y agoMailbox? http://h30266.www3.hpe.com/odl/axpos/opsys/vmsos84/BA554_90018/ch04s01.html http://h30266.www3.hpe.com/odl/axpos/opsys/vmsos84/BA554_900... This is the main VMS interprocess communication mechanism.
- jen20 7y ago> Under Linux, all I/O is synchronous but possibly nonblocking, and all disk I/O is blocking This is no longer true with io_uring.
- wtallis 7y agoIt wasn't entirely true even before io_uring. The previous Linux AIO API has too many caveats and pitfalls, but there were narrow use cases where it could do genuine non-blocking asynchronous disk IO.
- jen20 7y agoYup - assuming you had filesystem support anyway. Seastar has a useful tool named “fsqual” for determining whether a given filesystem is capable of using kernel async IO in a non-blocking fashion.
- JdeBP 7y agoActually, M. Cutler's contempt for Unix design philosophy is not well documented. It's an unsupported edit to Wikipedia, and lots of recycling of that. The subject came up on StackExchange recently, with someone asking for the meaning of the Wikipedia claim. No-one could find it actually documented. There's documentation of an incident where M. Cutler showed contempt for people who were connected to DEC Ultrix, calling them "sorry excuses for engineers". However the source for that is an anecdote, related in a book years later, told by one of the very people so addressed, who might have had an incentive to thumb xyr nose at M. Cutler.
- 1wd 7y agoThe book "Show-stopper!: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft" (1994, G. Pascal Zachary) quotes: "Unix is like Cutler's lifelong foe," said one team member who'd worked with Cutler for nearly two decades. "It's like his Moriarty. He thinks Unix is a junk operating program designed by a committee of Ph.D.s. There's never been one mind behind the whole thing, and it shows. So he's always been out to get Unix." (Why "M."?)
- JdeBP 7y agoNow contrast with https://en.wikipedia.org/wiki/Special:Diff/320402189 https://en.wikipedia.org/wiki/Special:Diff/320402189 , the widely recycled Wikipedia edit and the claim that had to be explained; which that does not even support, let alone explain. The Armando Stettner named in https://en.wikipedia.org/wiki/Special:Diff/320396668 https://en.wikipedia.org/wiki/Special:Diff/320396668 and other edits by the same person is the person who told the "sorry excuses for engineers" anecdote about xyrself, recorded in A Quarter Century of UNIX by Peter H. Salus. The irony is that there is better, more specific, documentation of M. Cutler's opinion of OS/2 (specifically its mutex mechanism) than there is of M. Cutler's opinion of Unix.
- pdonis 7y ago> G. Pascal Zachary I don't consider him a reliable source; he had a reputation for scandal mongering and misrepresentation.
- oneplane 7y agoNone of those things are helpful when it's a restrictive commercial endeavor. There are many things that are technically very fancy but simply unreachable by most people due to administrative restrictions. Those restrictions are a far bigger barrier to usage and success than the technical capabilities, especially in a dynamic, fast-moving and interconnected world. I suppose that is also why this was posted here on HN: being tied to the grace of some commercial entity isn't exactly pleasurable.
- djsumdog 7y agoBut there are high end applications where companies are willing to take that hit. OpenVMS is used in some nuclear power plants. When you have data coming in from tens or hundreds of thousands of sensors, and processing that data is vital to keep things from exploding, you want something that can process it all in real time and never crash. BASF's STOP is another example of a very specific purpose operating system geared entirely around security.
- runnerup 7y agoI can't find any info on BASF's STOP; can you link me to something relevant? It's up my alley personally, would love to learn more.
- djsumdog 7y agoThere's not much info out there publicly. Here's what I found: https://www.baesystems.com/en/product/stop-os https://www.baesystems.com/en/product/stop-os https://en.wikipedia.org/wiki/XTS-400 https://en.wikipedia.org/wiki/XTS-400
- oneplane 7y agoYes, but that doesn't have much to do with hobbyist or student licensing, does it. If you are an energy company you probably have some sub-sub-sub budget line somewhere for 'computer license' stuff.
- generatorguy 7y ago
- downerending 7y agoI cracked "root" on ours as an undergrad, so going to claim that the security wasn't all that, at least lacking a perfect operator. (And didn't they distribute it with vendor backdoors for a long time?) Beyond that, AFAIK it didn't have pipes, which was a real limitation for creating, well, pipelines to stream process data far larger than available RAM. I miss the days, but not the OS.
- dboreham 7y agoSomewhere I have a printout (green ruled 132-column line printer of course) of the SYS$SYSTEM:SYSUAF.DAT file showing my account with all 32 privilege bits set (including of course: "change mode to kernel"). This after spending the weekend writing a perfect VT-100 "trojan" that I left running on an operator terminal with some social engineering, grabbing the system user password which I then used to escalate my account's privileges. Coincidentally, a few minutes later, the 780 threw a fatal memory error and shut down. My 17 year old self assumed he had broken the VAX, returning to work (I was an intern) on Monday morning expecting to be fired. Writing the trojan, which had to correctly implement all the terminal timeouts, responses to ctl-y and so on, was quite a challenge. Required me to understand $QIO, by reading the microfiche copy of the terminal handler BLISS-32 source code.
- metaphor 7y agoPipes wasn't a thing until v7.something or other. A bunch of lexical functions weren't implemented until then too.
- monocasa 7y agoPipes very much existed before v7. At a bare minimum they're in v6 as I remember them from Lyon's, but I think they were as far back as v3.
- metaphor 7y agoYeah, sure...from § 11.13.2 of TFM[1]: > In OpenVMS Version 7.1, the DCL PIPE command was introduced. Ask me how I really know OpenVMS v6 doesn't have pipes. [1] http://h30266.www3.hpe.com/odl/axpos/opsys/vmsos84/6489/6489pro_029.html http://h30266.www3.hpe.com/odl/axpos/opsys/vmsos84/6489/6489...
- metaphor 7y ago> "Fat fingering" a command could have disastrous consequences; in most cases on VMS, the command interpreter will raise a syntax error. OpenVMS also has file versioning built into the file system For all this talk of fat fingering, you failed to mention that a simple purge is all it takes for all that file versioning to disappear...and you don't even have to type out the whole 5 letters. Besides, file versioning != revision control, and there are modern interoperability nuisances with it too. Perhaps the most annoying thing with VMS is it'll allow you to set default (equivalent to cd for those unfamiliar with VMS CLI) to a directory that doesn't exist without even a courtesy warning. It was so batshit annoying that I wrote my own implementation of cd in DCL to ensure that never happened, along with updating command prompt to reflect current directory (just like Windows cmd) and certain bashisms like ~ for home directory, etc. > Oh, and OpenVMS doesn't crash. Like, ever. Yeah, sure...not really.
- icedchai 7y agoThe VMS directory structure is bizarre when you first see it. dev:[dir1.dir2.dir3]file.ext;rev for a full path... Don't forget about [000000] for the root directory.
- deleted 7y ago[deleted]