Koozali.org: home of the SME Server

Legacy Forums => General Discussion (Legacy) => Topic started by: Mark Worley on June 03, 2003, 05:27:52 AM

Title: Downgrading to 5.1.2
Post by: Mark Worley on June 03, 2003, 05:27:52 AM

Hi,
I have been using 5.6 for a few months. I would like to downgrade to 5.1.2 for reliability reasons. I have performed a backup to desktop from the 5.6 box. Can I restore this to a freshly installed 5.1.2 box?
Any advice much appreciated.
Mark Worley

Title: Re: Downgrading to 5.1.2
Post by: Charlie Brady on June 03, 2003, 07:59:22 AM

Mark Worley wrote:

> I have been using 5.6 for a few months. I would like to
> downgrade to 5.1.2 for reliability reasons.

Have you reported any of your reliability problems. Please report all suspected bugs to smebugs@e-smith.com.

> Any advice much appreciated.

Don't re-install 5.1.2 unless you first ensure a reliable supplier of security updates.

Charlie

Title: Re: Downgrading to 5.1.2
Post by: Nathan Fowler on June 03, 2003, 08:26:22 AM

Mark, if you plan on rolling back to 5.1.2, be sure to update all errata packages for Redhat 7.1, http://rhn.redhat.com/errata and then mySQL from the Redhat 7.2 errata packages.

No offense to the E-Smith/Mitel team, Charlie, or any other developer, but the Redhat errata packages are often deployed much sooner and more frequently than those errata packages provided by Mitel/E-Smith, even those more severe packages, such as Apache, OpenSSL, MySQL, etc.  Most, if not all packages are compliant with E-Smith since E-Smith/SME is based off Redhat.

Those users reading this post that are post-5.1.2, be sure you apply only those packages for the version your SME build is based off.  I believe both 5.5 and 5.6 are based off RH 7.2, please correct me if I am wrong.  My success with the Redhat errata packages are limited to my experiences with the 4.1.x and 5.1.x series, I have not yet tested such errata packages with 5.5 or 5.6, therefore, proceed with caution and always test your errata packages first before you implement them in a production environment.

Don't use the xinetd errata package as it tends to break imap.

Mark, if you roll back to 5.1.2, be sure to apply the newest version of x-before-smtp (http://www.stickit.nu/pop-before-smtp), as it provides several performance enhancements and bug-fixes. (Noticed you were using it in a previous post)

Thanks,
Nathan