"the usual 32-bits"?

Just an opinion, but if you're running 32-bit CentOS on 32-bit hardware, you should stay with CentOS 5.6 for a while... it's scheduled to remain under full support until March 2014, and extended support for 3 more years after that. By that time, you should be upgraded to 64-bit hardware (or at least more than 4GB of RAM).

Now I don't just say that because I'm some kind of "64-bit snob" -- but because there is no supported upgrade from RHEL 5.x to 6 (just as there was no supported upgrade from RHEL 3.x to 4, or 4.x to 5). [Note: the jump from RHEL 3 to 4 was more significant than most because of the jump from the 2.4 to 2.6 in kernel versions]. In a perusal of several Linux and RedHat (as well as CentOS) user sites, I've seen numerous posts of people trying the old "burn a DVD & install it as an upgrade" method, only to find it just doesn't work.... probably because few things in software (much less OS software) works "by accident" -- and RedHat never had any intention of (and thus put no effort into) making an automatic upgrade path from RHEL 5 (CentOS 5) to version 6.

So where does that leave you (and why should you stay with CentOS 5.6 for now) 1) Some 3rd party will likely come up with an upgrade methodology for RHEL/CentOS 5 to 6 which will make your job relatively easy, or 2) You'll upgrade your hardware within the next 3 years, and upgrading to CentOS 6 (or 7) will be a necessity anyways (if only to access more than 4GB of RAM!)

Either way, if you try the upgrade now, it's gonna be time consuming and painful -- and a process that will likely have to be repeated when you want/need more than 4GB of RAM in the near future! So by holding off the jump into CentOS 6 for a while you'll save yourself the pain of having to do a complete re-build and data-copy more than once!

But there is an exception to my advise: If your hardware is already 64-bit and you're just not utilizing it, then I think you should rebuild with CentOS 6 64-bit now & get it over with.

Just my opinion -- before you complain, remember how much you paid for it!

Dan
IT4SOHO



On 7/26/2011 7:04 AM, User Qmail wrote:
Have you tried on the usual 32 bits? I wish to upgrade my centos 5.6 to centos 6.



On Tue, Jul 26, 2011 at 8:35 AM, Natalio Gatti <[email protected] <mailto:[email protected]>> wrote:

    I have just finished the installation of QT in a Centos 6 x64 box.
    I just wanted to my installation notes. It is not intended to be a
    Howto or a Step by Step instructions. Maybe they are usefull for
    someone else:

    _Centos 6 x64 Install Notes - Centos Minimal Installation_

    Dependencies Notes:

      * No installed: automake17 and compat-libgcc
      * Package compat-libf2c replaced by compat-libf2c-34
      * Package compat-libsdc++-33 replaced by compat-libstdc++-33
      * Centos 6 does not include sendmail, instead it includes
        postfix by default
      * When postfix is removed, it also removes "crontabs" and "mrtg"
        which I added later
      * When postfix is removed, it does not remove the user "postfix"
        with UID 89 which conflicts with vpopmail UID

    Command executed:

      * yum install make compat-libf2c-34 compat-libstdc++-33 aspell
      * yum remove postfix
      * userdel postfix

    Perl Dependencies Notes:

      * Install rpmforge manually:
          o rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt
          o rpm -Uvh
            
http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.2-2.el6.rf.x86_64.rpm

      * Install qtp
      * Run qtp-dependencies
      * Install perl SPF package manually:
          o yum install perl-Mail-SPF-Query

    Make Symbolic Link becouse centos 6 change the default rpmbuild
    directory

      * ln -s /root/rpmbuild/ /usr/src/redhat

    QmailToaster Installation Notes:

      * Execute install script cnt5064-install-script.sh
        <http://cnt5064-install-script.sh/>until installation of
        "qmailadmin-toaster"
      * Install mrtg and crontabs via yum
          o yum install mrtg crontabs
      * Continue with installation script

    Salutti,

    Natalio.


Reply via email to