On 06/09/13 02:14, Scott Robbins wrote: > On Thu, Sep 05, 2013 at 11:04:51AM -0500, Les Mikesell wrote: >> On Thu, Sep 5, 2013 at 10:46 AM, <m.roth@xxxxxxxxx> wrote: >> >> >>> And yes, I'm well aware that ESXi is a modified version of, mmm, is it >>> still RHEL 3, or have they gone up yet? >> The linux components were just for the shell-level interaction and I >> think they are mostly gone now. In any case, they don't have >> security updates nearly as often as RHEL/Centos pushes a new kernel >> which is an advantage for uptime on the guests. > If I remember correctly (but I'm no longer at that job, so don't have > access to double check) around VMware 4.x or 5.x it no longer had a Linux > shell. Although there are still some commands that work, I _think_ that > it's now a very stripped down shell, as opposed to 3.5 which had all the > commands available in a Linux shell. So, if I am correct, then Les has > summed it up nicely. > > I believe ESXi since it's release has always been based on Busybox, ESX was based on RHEL - that's my understanding. I manage vSphere and a couple of ESXi (free) hosts and use the VMware CLI tools https://my.vmware.com/web/vmware/details?downloadGroup=VSP510-VCLI-510&productId=285 In addition I'm running a VirtualBox Windows VM to access the vSphere console. Getting the vSphere console working in wine has not been done, and I don't even think the Crossover guys have it working either, I looked into that a while ago. So I would also just load up a virtualbox win machine to access it. _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos