• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Centos 4.x - from 7.5.4 to 8 topic

B

BoXie

Guest
Hi,

On CentOS 4.x most of us tricked Plesk's software as if CentOS was Redhat EL 4 (the redhat-release file mod) ...

But since Plesk now SUPPORTS Centos 4 ... what is to be expected on upgrades on these systems ?

Can we just restore the original 'Centos redhat-release file' and upgrade to Plesk 8 ?

Anyone has some experience yet ?
 
You'd be better continuing to use the RHEL releases in my opinion, as upgrading to CentOS builds could cause problems as it won't have been tested.
 
I have upgraded a Centos4.3 7.5.4 (cloaked as RHEL4) on Virtuozzo to 8.0.0. When I run the RHEL4 updater it gave the blacklist error. Then I changed the /etc/redhat-release file to Centos. Ran the same updater again and then it upgraded without problems with the Centos Plesk files.
 
Indeed .. i've done an update test on a virtual VMWare machine, while using standard CentOS' redhat-release file.

All RHEL4 psa rpms are overwritten. But some of them stay intact .. i guess because Plesk 8's version of those files are the same (like Frontpage extensions .. etc...).
 
correct. I wish Swsoft just make one version and check for two versions of redhat-release. This way it is much more transparant.
 
Back
Top