Was deciding to upgrade my CentOS/7 (running KVM and multiple VM), awaiting upgrade to CentOS/8. A few months ago it came out, a month ago they decided its EOL will be 2021!

I decided to continue with the upgrade but convert to OpenSuSE, the last Linux I was using before striking out on my own. Very excited to be returning. As I'm reading and planning: how does OpenSuSE do things differently; anticipating to get my new machine by mid-January.

One thing is OpenSuSE seems to have its own VNC via YaST (based on TigerVNC).

I had been using RealVNC to get into my CentOS VMs from my MBP-laptop, my Win/10-PC, my colleague's computer in the other building, etc.

As the CentOS VMs will be hanging around for quite sometime, I'd rather continuing to use RealVNC and not have to put new software (have two VNCViewers) on all my Outer Machines.

As I'm yet unfamiliar with YaST, with the SuSE-way(s), etc.
If not, how do I ignore OpenSuSE's offering (and install RealVNC)?

Or, if I'm not asking the correct question correctly: What to do?

Thanks.

#1 any time you go outside the distro repo software set there is a risk. It is important to determine if the risk is worth the advantage.

#2 VNC is more than several kinds of software, it is a protocol. All versions of VNC have that protocol in common, and each has certain extensions to that protocol. Since the base protocol is the same there is a core of functionality that SHOULD work when the server and the client are not from the same software release.

Investigate the issues with installing your preferred server software for VNC on the new host. Make sure you have the proper files ready for that install, but hold off on doing the install.

I recommend installing the SUSE package and then connecting to it using your current client. Run some tests. If it will serve your purposes well enough then there is no real reason to take on the risk of a non-SUSE package. If it fails, you can uninstall the SUSE vnc server and install the other one.

#3 We often have different clients for different hosts is we work in a mixed environment. It should be simple enough to install both vnc clients and automate the firing up of the correct client for the specific host.

#4 I wish Rocky Linux were ready, as that would appear to be the most natural and direct replacement for CentOS, but that may be a couple of month away yet. Continuing your project with CentOS and then converting to Rocky Linux when it becomes available might be a solid option. This may be an option worthy of consideration.

Thanks, wpeckham

Was intrigued by Rocky Linux when the CentOS/8 EOL:2021 was annonced. Will keep watch, maybe even try it out, later.

Yes, VNC:client doesn't have to match the server, and in this case, they are both based on TigerVNC; I'd rather stay with the known devil rather than the unknown.

I'll continue the plan to install/convertTo SuSE rather than wait, will go with your sage advice and not contend with VNC until I'm satisfactorily on the new machine, and the new VMs also working satisfactorily. Who knows, it might work out fine.