Yup. SCO OpenServer 5.0.something, for some partner's accounting department. Neither the OS nor the application software have been updated since the late 1990s, but if it works, it works, I guess... (to be honest: the application software is only used to run reports in response to requests from the legal department, but apparently still can't be shut down -- I ask once a year, next upcoming 'query date' in my agenda…
Wow, I had the same setup with Compaq Proliant in another galaxy long time ago...
This is running Solaris. https://www.usa.philips.com/healthcare/solutions/radiation-o... Last I heard they were desperately trying to get it on Linux. Why it isn't is because its a huge legacy application with some very horrible hacks specific to the OS.
The last time I got an MRI, the control room had one of those iconic purple SGI O2 workstations on the desk. I guess they were pretty popular with medical imaging products.
Yes, because SGI could do the "3D stuff" before PCs
Active HP-UX admin here. the software being run is SAP R3/Oracle and there is plans to replace it, but that is not happening anytime soon due to the usual delays associated with ERP migrations. License cost is a red herring here especially when dealing with enterprise applications from the likes of like SAP, Oracle and IBM, heck were probably paying as much for our SAP on SUSE subscriptions as we do for our HPUX lice…
When we ran HP systems it was because they had PickBasic
> Access is the biggest issue, as the OS only supports telnet, and serial access. OpenSSH works on it. This page has links to precompiled packages: https://scosales.com/knowledge-base/how-to-install-ssh-for-s... links: ftp://ftp2.sco.com/pub/skunkware/osr5/vols/openssh-3.4p1-VOLS.tar ftp://ftp2.sco.com/pub/skunkware/osr5/vols/prngd-0.9.23-VOLS.tar ftp://ftp2.sco.com/pub/skunkware/osr5/vols/zlib-1.1.4-VOLS.tar Probabl…
Maintaining access to a 20 year old ssh server will not be trivial. A modern client would usually fail to agree on encryption protocols in my experience.
It's pretty trivial. Some things are disabled by default, but still available on the latest versions of clients. For the OpenSSH client, it will tell you what specifically the client and server failed to agree on, and you can just add the option to enable on the client one of the ciphers, kex algos, or whatever that the server accepts. I've had no trouble with neither the latest version of the OpenSSH client nor Putty to connect to such servers.
> Access is the biggest issue, as the OS only supports telnet, and serial access. OpenSSH works on it. This page has links to precompiled packages: https://scosales.com/knowledge-base/how-to-install-ssh-for-s... links: ftp://ftp2.sco.com/pub/skunkware/osr5/vols/openssh-3.4p1-VOLS.tar ftp://ftp2.sco.com/pub/skunkware/osr5/vols/prngd-0.9.23-VOLS.tar ftp://ftp2.sco.com/pub/skunkware/osr5/vols/zlib-1.1.4-VOLS.tar Probabl…
Maintaining access to a 20 year old ssh server will not be trivial. A modern client would usually fail to agree on encryption protocols in my experience.
Considering the other options you can add the deprecated ciphers and key exchange mechanisms with a few lines for the host in your SSH client config on the newer system.
I worked on a system deployed on AIX for a few years. We used it to distribute batch workloads in parallel across a cluster of machines - no other software and OS did such a thing, maybe still doesn't. The machines themselves were PowerPC RS6000's which only ran AIX. The company already had a close relationship with IBM because they'd been running mainframes for decades. They made tons of money so saving money on lic…
Hey there! It depends on exactly how transparent you're talking, but I rewrote some Fortran and Honeywell assembly to 'C' on lowest-cost-bidder unix workstations on behalf of NASA in 91 or 92? We used NQS [1] to distribute the workload across the nodes and it worked pretty well. Well enough for NASA to retire the mainframe. The idea is hardly unique or novel - I believe DEC's clustering software allowed something similar? [2]
Tangentially related since there has been a lot of talk about working with ancient systems: does anyone working with TXDOT know if they are still using mainframe systems to drive their core database and services? I worked with a quasi governmental agency about a decade ago and became pretty intimately familiar with their mainframe setup. Didn’t look like it was going away anytime soon when I was there.
Usually it's because there's a database license or something that costs even more than the OS. No one wants to be there, but it possible to get trapped.