2020-09-22 06:27:11 UTC
There have been a few post from Mark Daniel on the WASD mailing
list and I thought this could be of general interest to c.o.v.
From Marks post on the WASD mailing list:
"Late last week the core server code was brought over to a VMS V9.0-D EAK
system supported by Jeremy Begg of VMS Software Systems. It built with a
minimum of fuss and invested time, and was up running in demonstration mode.
A full WASD source kit (essentially v11.5.1) UNZIP and installation has now
been performed. Of course the object modules needed to be cross-compiled
on an Itanium, taken to the x86 system, and the @WASD_ROOT:INSTALL
performed as a link-only build. Voila!
As this is written it's pretty much an all-singing, all-dancing WASD server
(to further mix the metaphors).
You are welcome to have a look around.
Explanation: it seems a network stack bug has been encountered. When
attempting to bind to the privileged ports 80 and 443 an insufficient
privilege status is returned. A simple reproducer using BSD sockets and
bind() has the same issue. This has been reported to VSI.
Further temporal expenditure; perhaps 8 hours. Some of this is the
cross-compiling and moving objects onto the system. An x86-64 UNZIP built
by Jeremy (after me b&m about the lack) is a much appreciated tool. There
is probably an additional 8 hours that I'll quite happily attribute to my
own fumbles. All in all, WASD has progressed much further on the EAK that
I imagined it might. It seems WASD is all-but ported. A moderately large
and complex VMS application. Now just waiting for the lurking gremlins."