Slashdot Mirror


HP Discontinue OpenVMS

simpz writes "The register is reporting that 'the ancient but trustworthy server operating system' OpenVMS has been discontinued. From the article: 'HP never really promoted its acquisition and OpenVMS suffered from a lack of development compared to HP-UX, itself suffering from competition from Linux. It was only a matter of time, but it's a sad end. Many of its old-time fans, your correspondent included, cherished a hope HP would move it to x86-64 – but since development moved to India in 2009, OpenVMS has been living on borrowed time. Now, it's run out.'"

23 of 238 comments (clear)

  1. When will it be open-sourced? by Erbo · · Score: 4, Insightful

    There might be a few insights in that old code worth preserving...

    --
    Be who you are...and be it in style!
    1. Re:When will it be open-sourced? by mrr · · Score: 4, Insightful

      HP already put those into a new product: http://h17007.www1.hp.com/us/en/enterprise/servers/management/insight-control/index.aspx

    2. Re:When will it be open-sourced? by Anonymous Coward · · Score: 3, Informative

      I wonder too. Perhaps some of "Open"VMS can be ported into FreeVMS.
      http://en.wikipedia.org/wiki/FreeVMS

    3. Re:When will it be open-sourced? by ebno-10db · · Score: 5, Insightful

      Just look to Windows. Just as IBM(rot -1) = HAL, VMS(rot 1) = WNT. VMS and Windows NT were both developed by Dave Cutler (who hated UNIX).

      The original Windows NT (3.51?) was a pretty good OS. After the first release though it became Microsoftized. I don't know what Cutler's involvement with that was. However, the real beauty of VMS wasn't so much it's architecture (though that had a lot of good points) but the incredible quality of DEC's implementation. Bugs were for the competition.

      "Cutler hated Unix" probably sounds like Neanderthal blasphemy to most Slahsdotters, but there were plenty of reasons to hate Unix in the 80's. The big split (AT&T vs. BSD style), numerous other incompatibilities (later overcome to a large extent by GNU utilities), horribly inefficient, bad security even for (largely) pre-Internet days, and practically non-existent documentation. Take it from an old fart who was there - any Unix of the last 15-20 years is definitely not your father's Unix.

    4. Re:When will it be open-sourced? by el+borak · · Score: 3, Interesting

      However, the real beauty of VMS wasn't so much it's architecture (though that had a lot of good points) but the incredible quality of DEC's implementation. Bugs were for the competition.

      While I used VMS extensively and liked it in many ways, this is just silly.

      When VMS 4.0 was released (the first version to include DCL command line editing), we had some unexplained crashes in our cluster. We eventually tracked it down to a bug in the command line editor (yes, it ran at least partially in kernel space). We had a local "competition" to see who could find the shortest number of keystrokes that would crash the system. The winner: 4. Yes, you could crash VMS 4.0 by getting an unprivileged command prompt and typing 4 characters (didn't even need to hit RETURN).

      The bug was fixed in 4.1.

      --
      An imperfect plan executed violently is far superior to a perfect plan. -- George Patton
    5. Re:When will it be open-sourced? by ebno-10db · · Score: 3, Interesting

      IIRC 4.0 was a turkey. We waited until 4.1 because word had quickly gotten out about 4.0. Undoubtedly I exaggerate due to my nostalgic haze, but while DEC occasionally screwed up (e.g. 4.0) it was overall a very reliable OS. Certainly way better than any *nix variety of the day that I had the displeasure to work with.

    6. Re:When will it be open-sourced? by Trailer+Trash · · Score: 3, Interesting

      DCL didn't run in kernel space, it ran as supervisor code (the four levels were user, supervisor, exec, and kernel). DCL sat above the stack in the user's address space (the user had two address spaces) so when it ran a command the command code was loaded into the regular user heap and executed without starting a new process. The command would just "return" at the end and you'd be back to the command interpreter.

      Anyway, if you could crash the whole system with DCL the problem was likely in QIO, not in DCL.

    7. Re:When will it be open-sourced? by simishag · · Score: 3, Interesting

      It's been a while since I read it, but "Showstopper" is a pretty good history of Cutler & Windows NT: http://www.amazon.com/Showstopper-Breakneck-Windows-Generation-Microsoft/dp/0759285780/ref=sr_1_6?ie=UTF8&qid=1370920903&sr=8-6&keywords=showstopper

    8. Re:When will it be open-sourced? by Darinbob · · Score: 3, Informative

      I've seen VMS source code. It is not pretty stuff.

    9. Re:When will it be open-sourced? by Darinbob · · Score: 3, Interesting

      The real big difference I felt between Unix and VMS was the orientation. VMS was fully intended to be what we'd today call an enterprise system. It was for corporate office to run as a server, for database management, for batch processing, etc. Unix was oriented towards small departmental computing. Late 80s had Unix growing up a bit more but it still had a much looser feel to it whereas VMS felt like you needed a suit and tie. At that time too Unix was pretty efficient, it really depended on what you were doing though; lots of users or heavy duty I/O and VMS tended to win, whereas few users and Unix felt more responsive. Unix was also always more open; cheaper, more third party applications, free development tools, etc. It changed in early 90s though when Unix got that corporate feel and all the big players wanted a piece of the pie and started splitting into factions.

  2. Never hacked? by riverat1 · · Score: 3, Interesting

    Last time I heard VMS had never been hacked. Is that still the case?

    It was the best OS I ever worked with. It'd be nice if they open sourced it.

    1. Re:Never hacked? by Shirgall · · Score: 4, Informative

      VMS was hacked, but it is certainly rare. https://www.cert.org/advisories/CA-1989-04.html

    2. Re:Never hacked? by bobstreo · · Score: 3, Informative

      Last time I heard VMS had never been hacked. Is that still the case?

      It was the best OS I ever worked with. It'd be nice if they open sourced it.

      Umm Kevin Mitnick?

      http://www.openvms.org/faqs/OpenVMS-Hack-FAQ.html

    3. Re:Never hacked? by lophophore · · Score: 3, Interesting

      uhhh. no.

      Mitnick social engineered his way into VMS. he did not "hack in". He used the telephone and convinced a flunky to start a command interpreter on the modem line he was dialed into. Clever? yes. A skilled hack? only of humans.

      --
      there are 3 kinds of people:
      * those who can count
      * those who can't
    4. Re:Never hacked? by laughingskeptic · · Score: 3, Informative

      Ahhh user FIELD; password SERVICE. The good ol' days.

  3. Re:no by isopropanol · · Score: 4, Funny

    Indeed, what will their customer use now?

  4. India where projects come to die by Anonymous Coward · · Score: 4, Insightful

    Its always the same when a huge software project moves out of the EU or US to india its bound to die. India has some great engineers but 90% of those graduating have just memorized stuff and passed an exam which has a pass rate as long as you have 33/100. Obviously this creates a lot of worthless engineers.

    From personal experience: One our customers the ESA (European Space Agency) had some servers and storage arrays running on SUN hardware. We just managed the hardware and operating systems. The software/middleware was all responsibility of the customer who had outsourced this part of the job to Tech-Mahindra (and india based outsourcing giant). These guys would mail us asking us how to change their password and how to "copy" a file from the server while having ssh access (and this happend every few days). If you have such guys working on such important systems I don't even want to know whats happening on development level. Its true that in every team you have a few top-scorers but not knowing how to change your password on a unix system and "managing" that system day to day tells me there is something seriously wrong.

    1. Re:India where projects come to die by Darkness404 · · Score: 4, Insightful

      Yeah, it really seems like when it comes to India, their engineers are fine with low-level stuff but when it comes to doing something beyond what they learned in school, they've got no clue. They also don't seem to understand how it all "fits together" and how to actually innovate and make usable features for normal users.

      Indians are fine for grunt work, and there are some truly bright engineers there, but too many companies see that they can get 5 engineers for the price of one and think they'll get 5x the productivity... instead they find out they get 1/2 the productivity.

      --
      Taxation is legalized theft, no more, no less.
  5. Not surprised OpenVMS lasted this long by T5 · · Score: 5, Funny

    I'm not surprised that it took HP so long to figure out

    SYS$SYSTEM:SHUTDOWN.COM

    on the whole O/S.

    After all, it has a dollar sign in it and they're not particularly astute with cash lately.

  6. I sense a really insignificant disturbance... by Anonymous Coward · · Score: 5, Funny

    I sense a really insignificant disturbance in the force as if a few voices suddenly cried out in terror and then went back to stroking their beards.

  7. RIP VMS by Tore+S+B · · Score: 5, Interesting

    There were few operating systems that handled loose-clustered networking as elegantly as VMS. Want to centralize user credentials? Easy, just place SYSUAF.DAT on a shared volume. And since the files could have structure, you could lock individual user records for editing rather than the whole file.

    Another great feature was the concept of "quorum". Quorum, as in the organizational term of the number of people present at a meeting necessary for it to be an official meeting of an organization, was the number of reachable hosts necessary to conduct business. Say you had a redundant banking site - and the link between them would go down. If they are a redundant configuration, they would continue to process transactions - with their database quickly diverging. Using quorum nodes, you could set up three hosts on three sites - two major server setups and a simple workstation somewhere central - and voila, no single point of failure.

    Besides, there is a magnificent book, "OpenVMS Internals and Data Structures", which so elegantly and wonderfully describes operating system design.

    I really, really hope that OpenVMS could be open-sourced and this codebase might serve as the base for a community-written x86 port.

    --
    toresbe
    1. Re:RIP VMS by ebno-10db · · Score: 3, Insightful

      There are less illiterates than people who can't read.

      No, there are fewer illiterates than people who can't read.

  8. VMS was doomed when HP bought it by tyme · · Score: 4, Interesting

    When the amount of development your OS gets suffers "compared to HP-UX" you are in astonishingly deep trouble. I have had three run-ins with HP-UX, first in 1998, next in 2004, and finally in 2010 (when my current job retired all it's existing HP servers and moved to Solaris). When I encountered HP-UX the first time, in 1998, it seemed to be at least 10 years behind the times. Very little had changed in 2004, which meant that it was falling farther and farther behind each year. In 2010 it seemed little better than it had been in 2004, and I guess that management agreed, since we finally cut the cord and moved on to something that was, at least by comparison, more up to date.

    I also used OpenVMS in the early 2000s, and it was capable, but idiosyncratic (record structured files were a PITA, and the file versioning was no replacement for proper version control. I really liked logical names, however, and the global symbol table was useful). It had a head start on lots of other OS's with respect to clustering features (cluster wide file system, message queues, and distributed lock management was all built-in), but much of the userland was GNU stuff ported over on the POSIX layer. DEC seemed to have given up on the whole "innovation" thing and was just milking existing big contracts.

    --
    just a ghost in the machine.