Hi all,
I just wanted to ask if anybody did a # up2date --upgrade-to-release=4.1 on CentOS 3.5 box?
I did it and I'm having a bit of problems. The box just dies... at intervals between half a day and a couple of days. Initially I considered it was a hw problem, so I had the tech support check it out, and they just switched the box with another, and put the harddisks back on the new box... Unfortunately the dying problem remaind so that's why I started considering that maybe something other that hw could be the problem. So did anybody on the list do such an upgrade, and was it all 100% ok ?
TIA, Alex
Alexandru E. Ungur wrote:
I just wanted to ask if anybody did a # up2date --upgrade-to-release=4.1 on CentOS 3.5 box?
I did it and I'm having a bit of problems. The box just dies... at intervals between half a day and a couple of days. Initially I considered it was a hw problem, so I had the tech support check it out, and they just switched the box with another, and put the harddisks back on the new box... Unfortunately the dying problem remaind so that's why I started considering that maybe something other that hw could be the problem. So did anybody on the list do such an upgrade, and was it all 100% ok ?
Its quite clearly indicated in the release notes that a cross Version upgrade from CentOS3 to CentOS4 is not supported. This issue has been covered in details previously on the list a few times, you might want to search the archives to see what people had to say.
In a nutshell, unless you really understand the implications of upgrading using up2date or yum, reinstall is the best option ( or in a pinch, use the upgradeany install option after you remove all third party rpm's and packages ).
- K
Good morning, Karanbir...
On Monday 26 September 2005 2:28 am, Karanbir Singh wrote:
In a nutshell, unless you really understand the implications of upgrading using up2date or yum, reinstall is the best option ( or in a pinch, use the upgradeany install option after you remove all third party rpm's and packages ).
Since I asked this question originally, and my good friend Bob Hanson more or less told me the same thing, it is good to see the logical outcome of trying after I was warned. 8) Let us hope that in future releases the developers at least allow us to do upgrades, but at the present time, it does NOT seem something one would recommend.
Dave
sender: "Dave Laird" date: "Mon, Sep 26, 2005 at 06:41:45AM -0700" <<<EOQ
Good morning, Karanbir...
On Monday 26 September 2005 2:28 am, Karanbir Singh wrote:
In a nutshell, unless you really understand the implications of upgrading using up2date or yum, reinstall is the best option ( or in a pinch, use the upgradeany install option after you remove all third party rpm's and packages ).
Since I asked this question originally, and my good friend Bob Hanson more or less told me the same thing, it is good to see the logical outcome of trying after I was warned. 8) Let us hope that in future releases the developers at least allow us to do upgrades, but at the present time, it does NOT seem something one would recommend.
Thank you all for advices. Too bad I didn't ask before actually going ahead with it. After all it all went beautifully in Slackware :) when doing a slapt-get --dist-upgrade from 9.1 to 10.0... I thought that I would have the same luck in CentOS... :) And in the end... I did. My problem arose from the fact that kernel* was in the up2date skip list, and thus wasn't updated. Once I got it updated too with --force, everything looks just fine.
Thanks all, Alex
} Since I asked this question originally, and my good friend Bob Hanson more } or less told me the same thing, it is good to see the logical outcome of } trying after I was warned. 8) Let us hope that in future releases the } developers at least allow us to do upgrades, but at the present time, it } does NOT seem something one would recommend. } } Dave
greetings,
my experience with it was ok.
as was discussed on the list ohhhhh so long ago... that the best possible "potential" way to upgrade was to boot with new CD's and do a
linux upgradeany
or was it a
linux text upgradeany
at the time i went from 3.3 to 3.4 via yum and then to 4.0 with the proposed _linux upgradeany_, as i had a test pre-production box... if that makes sense.
please note i recall there were some issues with yum at that time too plus yum was upgraded and it was also different in 3.x vrs 4.x... wasnt it? pitr stuff.
it worked great, yet i didnt like that after the upgrade some KDE settings were not as i expected and it just wasnt "fresh"... although it was a very functional server that was running the www.qmailrocks.org setup and it did not break it other than...
...i was not running SQL on the machine, mod_auth_sql or something like that had to be deal with after the fact and disabled... when i went to admin the box via http interface, i couldnt login.
what this all means is i would rather do a fresh install of 4.x and then make it a production box OR backup everything, make a new box and mnigrate/ restore
regards,
- rh
-- Robert Hanson - Abba Communications Computer & Internet Services www.abbacomm.net
-
Alexandru E. Ungur -
Dave Laird -
Karanbir Singh -
Robert