On Friday 19 July 2002 19.11, Helgi Örn wrote:
On Fri, 2002-07-19 at 14:55, Richard wrote:
This may be what I saw also: the standard installation does not install the kernel sources but only a compiled kernel for your system. Look in /usr/src/ to see if the the files are there. I went back to the CD's and installed the kernel sources by Yast. Everything else went fine then. Note the 850M RAM limit: if you have more than 850M RAM you must add a line to lilo at boot to limit to 850M or VM won't run. This is documented on SuSE support site.
Yes, all this I know. But the version you installed was the VmWare 3.0 one from the SuSE -ROM right? This worked fine on my system too but I would like to run version 3.1.1 of VmWare which I consider being a much better one. When I try to upgrade it using the rpm packet with -Uvh I now get all these conflicts error messages: --- # rpm --test -Uvh VMware-workstation-3.1.1-1790.i386.rpm package VMwareWorkstation-3.1.1-1790 is already installed file /etc/vmware/installer.sh from install of VMwareWorkstation-3.1.1-1790 conflicts with file from package vmware-3.0.0-121 file /usr/bin/vmnet-natd from install of VMwareWorkstation-3.1.1-1790 conflicts with file from package vmware-3.0.0-121 ...etc... --- So the question is; anyone here who's managed to install/upgrade to 3.1.1 and in that case what's the secred??
I don't know of a way to make rpm understand that two rpms with different rpm names are actually the same. I also don't understand why SuSE/vmware can't use the same rpm name (note: rpm name is not the same as the file name) as each other. An answer to either question would be greatly appreciated. I just did "rpm -e vmware" and "rpm -ivh VMware*.rpm". Your local config shouldn't be touched by this, so after running vmware-config.pl I was able to run the vmware sessions I had set up in 3.0 just fine. Also note that SuSE's default SMP kernel seems to be unusable together with vmware. I had to recompile and turn of 64GB memory support before I could get it to run. //Anders