News for hackers. Stuff that matters.
Re:OpenVMS: state of the x86 port by snagglegaggle on Tuesday October 15, 2019 @06:11PM (#21264500)
A lot of modern Windows kernel API looks exceedingly familiar to Unix. I would think perhaps early Windows was close to VMS, but as they tried to bolt on a POSIX layer it seems it has drifted.

Features of VMS like transparent clustering are missing, for example.

Re:OpenVMS: state of the x86 port by pjmlp on Wednesday October 16, 2019 @01:32AM (#21267346)
Window kernel APIs have nothing UNIX like beyond sockets.

POSIX personality was the place for them.

Modern Windows follows mainframe's footsteps by providing UNIX compatibility via a VM environment.

Re:OpenVMS: state of the x86 port by abotsis on Wednesday October 16, 2019 @01:22AM (#21267302)
Which api’s specifically? VMS was always (and still is?) posix compliant, as was nt. VMS even ran x11!
Re:OpenVMS: state of the x86 port by wbl on Wednesday October 16, 2019 @02:05AM (#21267522)
The I/O model in the kernel is very similar and utterly unlike Unix.
Re:OpenVMS: state of the x86 port by snagglegaggle on Wednesday October 16, 2019 @02:25AM (#21267618)
As you move up the stack it looks more Unixy. The core is VMS-like and I can see the similarity, but it seems to me the majority of the code actually written exists in a middleware layer that is maybe not as far from VMS as Linux, but not quite VMS.

Names can be quite different. I remember looking at the disk stack and thinking it looked quite similar, save for completion ports.

Re:OpenVMS: state of the x86 port by wbl on Wednesday October 16, 2019 @11:59PM (#21278793)
Softirq and taskqueue change the model to be more VMS like.