Hello, I'm trying to take a box from 4.4 to 5.0 and doing it via binary yum upgrade. I'm following the procedure at:
http://lists.centos.org/pipermail/centos-announce/2007-April/013660.html
for taking a 4.x box to 5. I've removed any unneeded rpms, and confirmed the state of the system. I downloaded and installed centos-notes-5 and ran an rpm -Uvh centos-release-5 which worked. I imported the centos 5 gpg key and confirmed the status of my yum. Then i ran:
yum upgade
this didn't work, yum didn't recognize that as a valid option. Is that a mistype? Or is there another step i have to do? Thanks. Dave.
Dave wrote:
Hello, I'm trying to take a box from 4.4 to 5.0 and doing it via binary yum upgrade. I'm following the procedure at:
http://lists.centos.org/pipermail/centos-announce/2007-April/013660.html
for taking a 4.x box to 5. I've removed any unneeded rpms, and confirmed the state of the system. I downloaded and installed centos-notes-5 and ran an rpm -Uvh centos-release-5 which worked. I imported the centos 5 gpg key and confirmed the status of my yum. Then i ran:
yum upgade
this didn't work, yum didn't recognize that as a valid option. Is that a mistype? Or is there another step i have to do? Thanks. Dave.
The proper command is "yum upgrade".
Hello Dave,
Sunday, May 6, 2007, 4:54:26 PM, you wrote:
yum upgade
this didn't work, yum didn't recognize that as a valid option. Is that a mistype? Or is there another step i have to do? Thanks.
Looks like a typo to me, should have been:
yum ypgrade
I think
jer
On Sun, 2007-05-06 at 17:27 -0700, Jerry57 (GMail) wrote:
Hello Dave,
Sunday, May 6, 2007, 4:54:26 PM, you wrote:
yum upgade
this didn't work, yum didn't recognize that as a valid option. Is that a mistype? Or is there another step i have to do? Thanks.
Looks like a typo to me, should have been:
yum ypgrade
I think
jer
any word on this upgrade? I've given it a try and it failed all crazyness style!
here is some information and things I did.
I killed all services that were not needed I disabled the other repos other then installed and installed these packages
I then ran an yum clean all I then ran the yum upgrade
It complained about a not having the kernel it needed to install and some other packages that the kernel needed... so I forced installed using rpm's these..
e2fsprogs-1.39-8.el5.i386.rpm e2fsprogs-devel-1.39-8.el5.i386.rpm initscripts-8.45.14.EL-1.el5.centos.1.i386.rpm iptables-1.3.5-1.2.1.i386.rpm kernel-2.6.18-8.el5.i686.rpm kernel-devel-2.6.18-8.el5.i686.rpm mkinitrd-5.1.19.6-1.i386.rpm mkinitrd-devel-5.1.19.6-1.i386.rpm procps-3.2.7-8.1.el5.i386.rpm selinux-policy-targeted-2.4.6-30.el5.noarch.rpm udev-095-14.5.el5.i386.rpm
after putting them in.. I still get this at the end of the upgrade run...
Error: kernel conflicts with procps < 3.2.5-6.3 Error: kernel conflicts with e2fsprogs < 1.37-4 Error: kernel-PAE conflicts with e2fsprogs < 1.37-4 Error: initscripts conflicts with kernel < 2.6.12 Error: kernel conflicts with udev < 063-6 Error: kernel conflicts with iptables < 1.3.2-1 Error: kudzu conflicts with initscripts < 8.40-1 Error: kernel-PAE conflicts with selinux-policy-targeted < 1.25.3-14 Error: kernel-PAE conflicts with iptables < 1.3.2-1 Error: kernel-PAE conflicts with procps < 3.2.5-6.3 Error: kernel-PAE conflicts with udev < 063-6 Error: kernel conflicts with selinux-policy-targeted < 1.25.3-14 Error: Unable to satisfy dependencies Error: Package kudzu needs initscripts < 8.40-1, this is not available. Error: Package kernel-PAE needs iptables < 1.3.2-1, this is not available. Error: Package kernel needs selinux-policy-targeted < 1.25.3-14, this is not ava ilable. Error: Package hal needs kernel < 2.6.17, this is not available. Error: Package kernel needs procps < 3.2.5-6.3, this is not available. Error: Package autofs needs kernel < 2.6.17, this is not available. Error: Package kernel needs udev < 063-6, this is not available. Error: Package kudzu needs kernel < 2.6.13, this is not available. Error: Package kernel-PAE needs e2fsprogs < 1.37-4, this is not available. Error: Package kernel-PAE needs selinux-policy-targeted < 1.25.3-14, this is not available. Error: Package kernel needs iptables < 1.3.2-1, this is not available. Error: Package kernel needs e2fsprogs < 1.37-4, this is not available. Error: Package kernel-PAE needs udev < 063-6, this is not available. Error: Package lksctp-tools needs kernel < 2.6.10, this is not available. Error: Package initscripts needs kernel < 2.6.12, this is not available. Error: Package kernel-PAE needs procps < 3.2.5-6.3, this is not available.
anyone got any ideas?
I just downloaded vmware version 1.03 the .tar download. There were no problems installing it however, only when I'm logged as the root user am I able to create new virtual machine. Does anyone know how to correct this problem?
Later
_________________________________________________________________ PC Magazines 2007 editors choice for best Web mailaward-winning Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migr...
On 5/10/07, Barton Callender b14wc@hotmail.com wrote:
I just downloaded vmware version 1.03 the .tar download. There were no problems installing it however, only when I'm logged as the root user am I able to create new virtual machine. Does anyone know how to correct this problem?
http://pubs.vmware.com/server1/admin/wwhelp/wwhimpl/common/html/wwhelp.htm?c...
Virtual machines are just files on your disk. Everyone who is to be allowed to create a virtual machine needs write permission on the directory where those files will be stored.
From: "Bart Schaefer" barton.schaefer@gmail.com Reply-To: CentOS mailing list centos@centos.org To: "CentOS mailing list" centos@centos.org Subject: Re: [CentOS] Vmware version 1.03 Date: Thu, 10 May 2007 19:32:40 -0700
On 5/10/07, Barton Callender b14wc@hotmail.com wrote:
I just downloaded vmware version 1.03 the .tar download. There were no problems installing it however, only when I'm logged as the root user am I able to create new virtual machine. Does anyone know how to correct this problem?
http://pubs.vmware.com/server1/admin/wwhelp/wwhimpl/common/html/wwhelp.htm?c...
Virtual machines are just files on your disk. Everyone who is to be allowed to create a virtual machine needs write permission on the directory where those files will be stored. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Thanks for your help, it gave me some insight but prior to reading that when I installed vmware the second time, I created a folder in my home directory for the virtual machines. However, I still got the error message that I am not authorized to do that. I added myself to the disk group so I could have full permissions to the hard drive.
The passage did not tell me how to allow an ordinary user to create a new virtual machine.
Later
_________________________________________________________________ More photos, more messages, more storageget 2GB with Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migr...
On 5/10/07, Barton Callender b14wc@hotmail.com wrote:
I added myself to the disk group so I could have full permissions to the hard drive.
The passage did not tell me how to allow an ordinary user to create a new virtual machine.
"Ordinary" users generally won't have access to disk devices. The assumption is that you're going to create a virtual disk file, not use a raw disk or partition directly.
Adding yourself to grup disk is OK, but leaves you open to accidentally doing violence to your host OS's disks. It might be better to chgrp the specific disk devices that you want to use for vmware to some new group (perhaps "vmware") and put yourself in *that* group.
Barton Callender wrote:
I just downloaded vmware version 1.03 the .tar download. There were no problems installing it however, only when I'm logged as the root user am I able to create new virtual machine. Does anyone know how to correct this problem?
Is the directory where the image files would be created writable by the user trying to do it?
From: Les Mikesell lesmikesell@gmail.com Reply-To: CentOS mailing list centos@centos.org To: CentOS mailing list centos@centos.org Subject: Re: [CentOS] Vmware version 1.03 Date: Thu, 10 May 2007 22:21:13 -0500
Barton Callender wrote:
I just downloaded vmware version 1.03 the .tar download. There were no problems installing it however, only when I'm logged as the root user am I able to create new virtual machine. Does anyone know how to correct this problem?
Is the directory where the image files would be created writable by the user trying to do it?
-- Les Mikesell lesmikesell@gmail.com _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yes it is writable by the user.
Later
_________________________________________________________________ More photos, more messages, more storageget 2GB with Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migr...
Barton Callender wrote:
I just downloaded vmware version 1.03 the .tar download. There were no problems installing it however, only when I'm logged as the root user am I able to create new virtual machine. Does anyone know how to correct this problem?
Is the directory where the image files would be created writable by the user trying to do it?
Yes it is writable by the user.
I was able to create a new VM as a non-root user without any problem using the same version but the rpm install. Do you have SElinux enabled?
From: Les Mikesell lesmikesell@gmail.com Reply-To: CentOS mailing list centos@centos.org To: CentOS mailing list centos@centos.org Subject: Re: [CentOS] Vmware version 1.03 Date: Fri, 11 May 2007 16:20:22 -0500
Barton Callender wrote:
I just downloaded vmware version 1.03 the .tar download. There were no problems installing it however, only when I'm logged as the root user am I able to create new virtual machine. Does anyone know how to correct this problem?
Is the directory where the image files would be created writable by the user trying to do it?
Yes it is writable by the user.
I was able to create a new VM as a non-root user without any problem using the same version but the rpm install. Do you have SElinux enabled?
-- Les Mikesell lesmikesell@gmail.com
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
In reponse to creating a group called vmware, I tried that but was unsuccessful.
SElinux is disabled. I have the rpm for it I will uninstall the tar and try the rpm.
thanks
_________________________________________________________________ PC Magazines 2007 editors choice for best Web mailaward-winning Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migr...
On Thu, 2007-05-10 at 10:28 -0400, Gregg wrote:
On Sun, 2007-05-06 at 17:27 -0700, Jerry57 (GMail) wrote:
Hello Dave,
Sunday, May 6, 2007, 4:54:26 PM, you wrote:
yum upgade
this didn't work, yum didn't recognize that as a valid option. Is that a mistype? Or is there another step i have to do? Thanks.
Looks like a typo to me, should have been:
yum ypgrade
I think
jer
any word on this upgrade? I've given it a try and it failed all crazyness style!
here is some information and things I did.
I killed all services that were not needed I disabled the other repos other then installed and installed these packages
I then ran an yum clean all I then ran the yum upgrade
It complained about a not having the kernel it needed to install and some other packages that the kernel needed... so I forced installed using rpm's these..
e2fsprogs-1.39-8.el5.i386.rpm e2fsprogs-devel-1.39-8.el5.i386.rpm initscripts-8.45.14.EL-1.el5.centos.1.i386.rpm iptables-1.3.5-1.2.1.i386.rpm kernel-2.6.18-8.el5.i686.rpm kernel-devel-2.6.18-8.el5.i686.rpm mkinitrd-5.1.19.6-1.i386.rpm mkinitrd-devel-5.1.19.6-1.i386.rpm procps-3.2.7-8.1.el5.i386.rpm selinux-policy-targeted-2.4.6-30.el5.noarch.rpm udev-095-14.5.el5.i386.rpm
after putting them in.. I still get this at the end of the upgrade run...
Error: kernel conflicts with procps < 3.2.5-6.3 Error: kernel conflicts with e2fsprogs < 1.37-4 Error: kernel-PAE conflicts with e2fsprogs < 1.37-4 Error: initscripts conflicts with kernel < 2.6.12 Error: kernel conflicts with udev < 063-6 Error: kernel conflicts with iptables < 1.3.2-1 Error: kudzu conflicts with initscripts < 8.40-1 Error: kernel-PAE conflicts with selinux-policy-targeted < 1.25.3-14 Error: kernel-PAE conflicts with iptables < 1.3.2-1 Error: kernel-PAE conflicts with procps < 3.2.5-6.3 Error: kernel-PAE conflicts with udev < 063-6 Error: kernel conflicts with selinux-policy-targeted < 1.25.3-14 Error: Unable to satisfy dependencies Error: Package kudzu needs initscripts < 8.40-1, this is not available. Error: Package kernel-PAE needs iptables < 1.3.2-1, this is not available. Error: Package kernel needs selinux-policy-targeted < 1.25.3-14, this is not ava ilable. Error: Package hal needs kernel < 2.6.17, this is not available. Error: Package kernel needs procps < 3.2.5-6.3, this is not available. Error: Package autofs needs kernel < 2.6.17, this is not available. Error: Package kernel needs udev < 063-6, this is not available. Error: Package kudzu needs kernel < 2.6.13, this is not available. Error: Package kernel-PAE needs e2fsprogs < 1.37-4, this is not available. Error: Package kernel-PAE needs selinux-policy-targeted < 1.25.3-14, this is not available. Error: Package kernel needs iptables < 1.3.2-1, this is not available. Error: Package kernel needs e2fsprogs < 1.37-4, this is not available. Error: Package kernel-PAE needs udev < 063-6, this is not available. Error: Package lksctp-tools needs kernel < 2.6.10, this is not available. Error: Package initscripts needs kernel < 2.6.12, this is not available. Error: Package kernel-PAE needs procps < 3.2.5-6.3, this is not available.
anyone got any ideas?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Well. I ended up using a cd upgrade. It worked without issue. Still sorta testing things out. Sorta annoying it required all 6 cd's.
I think I upgraded my kernel from a standard centos base to the plus repo its possible thats why my yum upgrade failed.
Gregg
-
Bart Schaefer -
Barton Callender -
Dave -
Gregg -
Gregg McClintic
-
Ioannis Vranos -
Jerry57 (GMail) -
Les Mikesell