News for hackers. Stuff that matters.
Re:OpenVMS 9.2 for x86 is finally available for hobbyists by shrubble on Sunday April 09, 2023 @05:43PM (#35506759)
It's certainly a different take on operating systems... will be interesting to see if there is any interest now that you can spin it up as a VM on your KVM server box. Can't figure out the RAM needed to run it from the notes I have read, however...
Re:OpenVMS 9.2 for x86 is finally available for hobbyists by tyingq on Sunday April 09, 2023 @05:57PM (#35506852)
From "VMS Software / Documentation / x86-64 V9.2 Installation Guide"

https://docs.vmssoftware.com/vsi-openvms-x86-64-v92-installa...

  1.2.1. Recommended Settings for Virtual Machines
  VSI recommends that your OpenVMS virtual machine be configured with:

  Memory Minimum of 6 GB

  Minimum Number of CPUs: 2
Re:OpenVMS 9.2 for x86 is finally available for hobbyists by PopePompus on Sunday April 09, 2023 @09:14PM (#35508151)
How sad. VMS originally ran on a VAX 11/780 which maxed out at 8 MB. Now it apparently needs almost 1000 times more memory.
Re:OpenVMS 9.2 for x86 is finally available for hobbyists by Aloha on Sunday April 09, 2023 @10:01PM (#35508419)
VMS in 2020 is a vastly different beast than the VMS that ran on 11/780
Re:OpenVMS 9.2 for x86 is finally available for hobbyists by usr1106 on Monday April 10, 2023 @04:43AM (#35510359)
So what what has fundamentally changed?

I used VMS on various types of VAXen in the mid 1980s and I liked it because of its systematically designed command line interpreter. A Unix shell is a complete mess compared to that.

I switched to Unix in the late 1980s and to Linux later and found it technically more powerful. Lightweight processes, pipes and many more. Is there anything in OpenVMS that Linux is fundamentally lacking?

Re:OpenVMS 9.2 for x86 is finally available for hobbyists by lproven on Monday April 10, 2023 @07:52AM (#35511267)
> Is there anything in OpenVMS that Linux is fundamentally lacking?

File versioning. This is bodged on in all xNixes by embedding version numbers into filenames, then writing a multi-tens-of-thousands-of-lines shell scripts to track all the versions, make loads of symlinks so programs can find them if they don't need specific revisions, occasionally add new versions and remap hundreds of links, occasionally prune old libraries, carefully manage umpteen paths to where different libraries are kept... and this is considered normal and nobody sees anything wrong with it, when in fact it's a vast ugly kludge of a hack, now fossilised as package managers and so on.

All because it's a braindead filesystem.

Re:OpenVMS 9.2 for x86 is finally available for hobbyists by usr1106 on Monday April 10, 2023 @09:58AM (#35512376)
Linux does not have a single filesystem, but many of them. I guess you could create one that implements versioning. As a matter of fact around 2000 I used one (Unix, not Linux). It was a version control system where different file versions appeared under different POSIX paths. I liked it, but it was at least as complicated as git and most developers in our organization did not really understand it a complained when things went wrong.

For system administration I use etckeeper these days. That serves nearly the same purpose. But for programming VMS was superior unless you are disciplined and commit frequently enough.

Re:OpenVMS 9.2 for x86 is finally available for hobbyists by lproven on Monday April 10, 2023 @10:14AM (#35512543)
You could, but no normal Unix app will understand it or be able to use it, since this is one of the things that the Unix creators removed from the more complicated forerunners of Unix to make their smaller, simpler OS.

Sadly, this simplification was, IMHO, a step too far and a bad thing to remove. But Unix's namespace is much simpler, and doesn't really understand and incorporate extensions and things either. Which is a limitation but it makes it much simpler.

The fact that most Unix GUIs, from NeXTstep to KDE, put back in and use file extensions to associate files with applications shows that this is in fact important functionality.

Without extensions, having version numbering doesn't make as much sense.

But a Unix with file extensions and file numbers would be less like Unix than is, say, Plan 9 or Inferno.

Re:OpenVMS 9.2 for x86 is finally available for hobbyists by usr1106 on Monday April 10, 2023 @11:24AM (#35513442)
An application does not need to understand that the filesystem keeps a copy of the previous version of a file. Also in VMS if you use a file without version number it defaults to the newest one.
Re:OpenVMS 9.2 for x86 is finally available for hobbyists by lproven on Wednesday April 12, 2023 @06:05AM (#35537318)
I know. I ran clusters of VAX boxes, in production, in the mid-1990s.

An ordinary user app doesn't need to know. A file version control system does, though. Development environments need to know. IDEs and programmers' tools need to know.

Re:OpenVMS 9.2 for x86 is finally available for hobbyists by javitron on Tuesday April 11, 2023 @03:39PM (#35530354)
The file versioning in OpenVMS is really not that powerful. It also led to it's own set of issues, specially in terms of space waste.

Also VMS had their own issues when it came to it's filesystem(s).

Re:OpenVMS 9.2 for x86 is finally available for hobbyists by lproven on Wednesday April 12, 2023 @06:08AM (#35537338)
Sure it did, yes.

OTOH, the point here is that if facilities like this were available, tools like Git -- VCSes -- could be far simpler and easier to use, because a core part of the functionality they add is built into the filesystem.

Disk space is less of an issue now. This is a server OS for big systems. Terabytes are cheap.

All filesystems have issues.

Remember, all software sucks: http://harmful.cat-v.org/software/

Re:OpenVMS 9.2 for x86 is finally available for hobbyists by javitron on Tuesday April 11, 2023 @03:35PM (#35530291)
Yeah, and Unix originally ran on a PDP with 256KB of RAM. Alas...
Re:OpenVMS 9.2 for x86 is finally available for hobbyists by ch_123 on Monday April 10, 2023 @04:12AM (#35510210)
For what it's worth, when I boot my x86 VMS VM, it seems to only be using a few hundred megabytes of RAM. I believe I have read that they are still using unoptimized binaries as well, so I suspect memory usage may decrease in later releases.