[Info-vax] relaunch or legacy
Stephen Hoffman
seaohveh at hoffmanlabs.invalid
Tue Feb 1 19:17:05 EST 2022
On 2022-02-01 18:51:59 +0000, Gérard Calliet said:
> ...text expurgated...
The OpenVMS VAX V5.5 version you've mentioned elsewhere is ~thirty
years old and ~three architectures back, so there's clearly been no
hurry to upgrade.
Y'all are seemingly unhappy that no one is willing to spend their money
to allow y'all to stay in your server happy place. But aside from walls
of unhappy text and of deferring the port to x86-64, I'm not even sure
what you would prefer to happen here.
What to do for your particular affiliated sites? Do your own app due
diligence, figure out where your apps should be in five or ten years,
and figure out what's involved upgrading out of this or with porting
out of this, or what's involved with paying an entity to dig y'all out,
and present that to your management. Both plans with and without
dependencies on VSI. Present that to your management. As one of the
potential options... You could write a proposal with a sufficiently
large payment dangled, and see if VSI is interested. (I'd suggest
having somebody else edit the proposal, though.)
Your desire for (support of?) (blessing for?) (back-porting to?) (not
sure) OpenVMS VAX V5.5 aside, I'd suspect that any substantial delays
around the arrival of a viable x86-64 port will doom VSI. If your
affiliates do decide to stay on OpenVMS and do decide to upgrade,
you're going to be a whole lot more interested in x86-64 hardware, too.
--
Pure Personal Opinion | HoffmanLabs LLC
More information about the Info-vax
mailing list