I started with the "no gui Server" install option so I could tick a few things like samba, vsftpd etc.

Installed the latest 32 bit el-9 bin file , 7.0.1762.0 and overlaid the .4 bin file.

yum installs:

glibc.i686
libstdc++.i686
ncurses-libs.i686
pcre.i686

Updated to the latest ATE - 1762.6 . I had 1692.5 (what our customers mostly run) and that didn't connect at all (SSH error).

More extensive testing before using it in production but I can't see there being much issue as it looks to basically be Centos/RHEL.

Thanks for the feedback. And yes, Rocky 9 should be basically equivalent to CentOS/RHEL 9 as far as A-Shell is concerned (-el9). But testing is always advised.

As for the SSH error on the older ATE, many others have seen that problem, which is almost certainly due to the new SSH servers requiring updated SSH protocols (support for which is embedded in the ashnet2 library updates packaged with ATE). It's possible that you could just update that DLL, but I can't see any reason not to update the complete ATE package.

You inspired me to install my own Rocky Linux 9 VM. It all went pretty smoothly, except I think the first yum install in your list should be glibc.i686 (and not glibc++.i686).

As noted and expected, it runs the existing -el9 (CentOS 9) build, but the next step will be to actually build a new A-Shell in this environment. I'm not sure yet if we'll continue to refer to it as "-el9", as I'm not keen on adding yet another build variation that isn't really necessary. Probably this will become the new standard for the trio of not-quite identical triplets -- CentOS 9, Rocky Linux 9, Almalinux 9.

Yes, got too enthusiastic with my ++++s. Edited for my own use in future