• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Up2date or Yum?

F

Fenice

Guest
I have a server with Plesk 7.5 Reloaded no RHEL 4. I wanted to know if you people suggesto to use up2date or yum with ART's repository for system updates.

Thanks!
 
I have the same conf. and use both of systems updates, but to me is much better yum with ART repository.

Have fun
 
Thanks a lot - won't there be conflicts between the two update systems?
 
Both systems are diferents and don't have problems, but they can share repository pages.

You can view/edit the conf files to add the repository pages, but be carefull because up2date consult the RedHat updates (by default) and yum the pages are in the conf (example: atomicrocketturtle.com)

up2date
edit /etc/sysconfig/rhn/sources

yum
edit /etc/yum.conf

Have fun and remember this is by your own risk.
 
Thanks a lot :) I have read many packages can break Plesk 7.5 and 8. So far, I have excluded spamassassin, sendmail, rpm, and squirrelmail. Anything else I should keep out in up2date?
 
Back
Top