Live data from Hacker News

State of the OpenVMS Port to x86_64 [pdf]

vmssoftware.com

21–30 of 58 posts

Re: State of the OpenVMS Port to x86_64 [pdf]

#21
post #15

I have a bad habit where instead of doing something relevant I play with old stuff I read about but didn't have access to as a kid. VMS always interested me since I first read about it in the jargon file. I recently found an alphaserver on craigslist and I just requested an openvms hobbyist license so I could play with it. An octane running irix is another expression of this problem.

You would have liked Snakebite. (http://web.archive.org/web/20121031190851/http://www.snakebi...)

Re: State of the OpenVMS Port to x86_64 [pdf]

#23
I work with an old DEC guy who co-wrote a book about the BLISS compiler back in the day. He thought it made a much better "portable assembly language" than C.

He also likes to talk about the binary compatibility on VMS; e.g., VAX binaries that run unchanged on Itanium. Unfortunately, that commitment to compatibility has wavered a bit since HP offshored VMS maintenance. We've had to work around some breaking changes recently.

If I'm understanding these slides correctly, AMD64 VMS would require recompiling VAX, Alpha, and Itanium applications from source. I kind of see a chicken-and-egg problem: application vendors won't port without demand, and customers won't adopt without applications.

Re: State of the OpenVMS Port to x86_64 [pdf]

#24
post #15

I have a bad habit where instead of doing something relevant I play with old stuff I read about but didn't have access to as a kid. VMS always interested me since I first read about it in the jargon file. I recently found an alphaserver on craigslist and I just requested an openvms hobbyist license so I could play with it. An octane running irix is another expression of this problem.

Nothing wrong with that, you simply suffer from retrocomputing. Careful about the power bill though. Large SGI stuff (e.g. Onyx) can go in the kilowatt range under load, and an AlphaServer idles at around 200W last time I checked. IT was no green back then :)

My ES40 (4 x 667MHz 21264s) consumes 16A @ 110V. Most 110V US circuits are 10A.

I blew at least three fuses between that and the RX5670 (4 x Itanium), which consumed a similar amount of power @ 110V.

Re: State of the OpenVMS Port to x86_64 [pdf]

#26
long live DEC OpenVMS, it's really rare to see an article on hacker news about OpenVMS, but it has happened before. long live DCL, ASTs. i started work in 2000, but was still able to play around with vax and alpha clusters, sometimes if i recall correctly, a mix of vax and alpha nodes in the same cluster. OpenVMS was such a stable operating system, by 2000, most of the good DEC engineers had left already for companies like Microsoft (Dave Cutler, etc), but that legacy code was still quite amazing. long live ZKO and DEC, i learned a lot from that job, great to see this coming, but not sure if it's still relevant these days with all my development on linux. could you imagine running this port on aws, like some customer migrating to the cloud all their legacy infrastructure? that would be such a niche market.

Re: State of the OpenVMS Port to x86_64 [pdf]

#27

I work with an old DEC guy who co-wrote a book about the BLISS compiler back in the day. He thought it made a much better "portable assembly language" than C. He also likes to talk about the binary compatibility on VMS; e.g., VAX binaries that run unchanged on Itanium. Unfortunately, that commitment to compatibility has wavered a bit since HP offshored VMS maintenance. We've had to work around some breaking changes r…

DEC had a tool called VEST which was used to take native VAX binaries and convert them to run on Alpha AXP. It was very cool technology. A fair amount of the system utilities for OpenVMS on AXP were VESTed VAX binaries. I'm pretty sure the EDT editor was one of these.

The VEST technology could possibly be used to convert native VAX binaries to run on X86_64, I don't know for sure how the endian-ness would be dealt with.

Re: State of the OpenVMS Port to x86_64 [pdf]

#28
post #18
post #8

ugh. i switched from vms to unix in '88 because the telnet in vms was crappy. other than the wonderful help system, I never found VMS attractive.

VMScluster still blows away anything else. 20 years ago it was doing what you can only now do with vMotion now... And being able to set a working set per job... And a coherent story for cross-language libraries... I could go on. VMS was a technological tour de force that has yet to be rivalled.

What cluster features were in VMScluster that weren't also in TruCluster? To me the interesting part of TruCluster was the shared filesystem and the application failover. That said, I work for a company now that eschews that kind of tight coupling, because it's expensive to scale the hardware.

Re: State of the OpenVMS Port to x86_64 [pdf]

#29
post #15

I have a bad habit where instead of doing something relevant I play with old stuff I read about but didn't have access to as a kid. VMS always interested me since I first read about it in the jargon file. I recently found an alphaserver on craigslist and I just requested an openvms hobbyist license so I could play with it. An octane running irix is another expression of this problem.

Nothing wrong with that, you simply suffer from retrocomputing. Careful about the power bill though. Large SGI stuff (e.g. Onyx) can go in the kilowatt range under load, and an AlphaServer idles at around 200W last time I checked. IT was no green back then :)

> you simply suffer from retrocomputing

I love the way you phrase that! (I do suffer from that condition, too, in a way, if "suffer" is the word I want - but in my case it is select pieces of obsolete equipment sitting on my bookshelf. My favorite is an ancient IBM ISDN adapter (it still says 1TR6 instead of EDSS1 somewhere on the case) that once hooked up a mainframe to the outside world... ;-)

Re: State of the OpenVMS Port to x86_64 [pdf]

#30

Earlier quoted context omitted.

Nothing wrong with that, you simply suffer from retrocomputing. Careful about the power bill though. Large SGI stuff (e.g. Onyx) can go in the kilowatt range under load, and an AlphaServer idles at around 200W last time I checked. IT was no green back then :)

My ES40 (4 x 667MHz 21264s) consumes 16A @ 110V. Most 110V US circuits are 10A. I blew at least three fuses between that and the RX5670 (4 x Itanium), which consumed a similar amount of power @ 110V.

On the upside, depending on where you live, you probably save a lot of money on heating... ;-)
Post reply on HN