For those of you who are going to do the update from the centos5 beta to centos 5 proper despite the warnings, this is a(n incomplete) list of instructions for how to accomplish this
1. Get yourself into runlevel 3 (telinit 3 from terminal) as the dbus update will die if you're in X. 2. Setenforce 0 # turn off selinux as there have been some unconfirmed reports that it will interfere with the updates. 3. yum update 4. rpm -qa release="*fc6*" # this will let you find and identify the packages which had the release string changed from fc6 to el5. 5. manually update these rpms to the corresponding proper versions for centos5 proper. I'm not sure how many of these there actually are, so follow-ups to this post are welcomed.
If these instructions need to be modified, or are incorrect, please reply with corrections and/or additions.
On 4/12/07, Jim Perrin jperrin@gmail.com wrote:
For those of you who are going to do the update from the centos5 beta to centos 5 proper despite the warnings, this is a(n incomplete) list of instructions for how to accomplish this
- Get yourself into runlevel 3 (telinit 3 from terminal) as the dbus
update will die if you're in X. 2. Setenforce 0 # turn off selinux as there have been some unconfirmed reports that it will interfere with the updates. 3. yum update 4. rpm -qa release="*fc6*" # this will let you find and identify the packages which had the release string changed from fc6 to el5. 5. manually update these rpms to the corresponding proper versions for centos5 proper. I'm not sure how many of these there actually are, so follow-ups to this post are welcomed.
If these instructions need to be modified, or are incorrect, please reply with corrections and/or additions.
I presume these notes apply to the *yum* updates, but not to the upgrade through booting from CD. Is this correct?
Akemi
On 4/12/07, Akemi at gmail amyagi@gmail.com wrote:
I presume these notes apply to the *yum* updates, but not to the upgrade through booting from CD. Is this correct?
Correct. I've not attempted or heard of anyone doing an upgradeany via disk from beta to final. Someone else who has is welcome to follow up.
On 4/12/07, Jim Perrin jperrin@gmail.com wrote:
On 4/12/07, Akemi at gmail amyagi@gmail.com wrote:
I presume these notes apply to the *yum* updates, but not to the upgrade through booting from CD. Is this correct?
Correct. I've not attempted or heard of anyone doing an upgradeany via disk from beta to final. Someone else who has is welcome to follow up.
Please check out my earlier e-mail at:
http://lists.centos.org/pipermail/centos/2007-April/078843.html
I booted from a boot CD and did the upgrade from 4.92 via NFS. Where should I report any issues encounterd? CentOS bugzilla?
Akemi
Please check out my earlier e-mail at:
http://lists.centos.org/pipermail/centos/2007-April/078843.html
I booted from a boot CD and did the upgrade from 4.92 via NFS. Where should I report any issues encounterd? CentOS bugzilla?
It was always stated that this update would be 'best effort' and not supported. For right now (and others may disagree with me) I consider this thread to be 'best effort'. It was beta. Deal with the breakage.
Hopefully that doesn't sound too cold-hearted and uncaring.
On 4/12/07, Jim Perrin jperrin@gmail.com wrote:
Please check out my earlier e-mail at:
http://lists.centos.org/pipermail/centos/2007-April/078843.html
I booted from a boot CD and did the upgrade from 4.92 via NFS. Where should I report any issues encounterd? CentOS bugzilla?
It was always stated that this update would be 'best effort' and not supported. For right now (and others may disagree with me) I consider this thread to be 'best effort'. It was beta. Deal with the breakage.
Which is why I did the upgrade as a test case. After a real install on the same machine, I will report back with anything I find.
Hopefully that doesn't sound too cold-hearted and uncaring.
Not at all. You are the person with the warmest heart. Right, everyone? :-)
Akemi
Jim Perrin spake the following on 4/12/2007 10:55 AM:
Please check out my earlier e-mail at:
http://lists.centos.org/pipermail/centos/2007-April/078843.html
I booted from a boot CD and did the upgrade from 4.92 via NFS. Where should I report any issues encounterd? CentOS bugzilla?
It was always stated that this update would be 'best effort' and not supported. For right now (and others may disagree with me) I consider this thread to be 'best effort'. It was beta. Deal with the breakage.
Hopefully that doesn't sound too cold-hearted and uncaring.
Suck it up and go on! ;-D In the time it would take to write up a bugzilla entry, you could backup and restore.
I fortunately was only playing with the beta in VMWare to see what things looked like.
On 4/12/07, Scott Silva ssilva@sgvwater.com wrote:
Suck it up and go on! ;-D In the time it would take to write up a bugzilla entry, you could backup and restore.
I've just found the source of the problems I encountered upon upgrading my test machine from 4.92 to 5.0 via anaconda. Actually there were two things, both are peculiar to my machine, but not something general. This box refuses to boot if I use grub (a long story by itself). So I have been using lilo to boot. The installation recognized that lilo was in use. However, after the first boot, I should have run /sbin/lilo which I didn't. That was problem #1. The other problem had to do with udev. This was caused by the instlled kino. It was a known problem and the fix was available. Guess for the majority of people these are non issues. My test system is chugging along now.
I fortunately was only playing with the beta in VMWare to see what things looked like.
I have CentOS4.4 in vmware. Maybe I should try upgrading this one to see how it goes. :)
Akemi
I did this:
1. Update kernel-PAE and kernel-xen manually (download and install rpm) 2. Update yum* manually 3. Update centos-release manually 4. Update dbus, dbus-devel and dbus-x11 manually 5. yum update xorg* 6. Rename /etc/yum.repos.d/CentOS-Base.repo.rpmnew to CentOS-Base.repo 7. yum update xorg* 8. yum update *python* 9. yum update *virt* *kernel* 10. yum update
I didn't reboot after step 9, and there was no problem till now.
-
Akemi at gmail -
Jim Perrin -
Leonardo Pinheiro -
Scott Silva