On 4/26/2010 1:01 PM, Rainer Duffner wrote:
>> There's the glibc issue that's still unresolved. There's another
>> issue with using Firefox as the admin client. It *might* let you in,
>> but the console plugin doesn't appear to be working again. Only client
>> that works for me is InternetExploder.
>
>
> I switched to ESX4i and use a Windows VM with VI-Client to manage it -
> there's no other way to do it, unfortunately.
> For something that works on Windows exclusively (Dot-Net...), it's
> horribly slow and buggy.
> I don't see how a Java-solution would have been slower.
>
For what it's worth, I was still able to download and install the 1.x
version of VMware server (1.0.10) on an up to date Centos 5.4. The only
down side to an 'unsupported' host is that you have to have the kernel
headers and a compiler installed so the vmware-config.pl script can
build the kernel module. And the remote console client is nicer than
the web based access in the 2.x versions. But, for anything other than
pretending to keep some old and dying host running for a service that
would be hard to port, I'd start with ESXi instead. I did just run
across an odd problem with ESXi, though. Running the VMware converter
tool from an old Dell Win2k server with an IDE disk to produce an ESXi
image went through the motions but the image wouldn't boot - but doing
the same thing to a vmware server (v1) image file over a network share
worked. Has anyone seen that before?
--
Les Mikesell
lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
