On Mon, 2008-12-15 at 18:20 +0200, Gilboa Davara wrote: > On Sun, 2008-12-14 at 13:26 -0500, Claude Jones wrote: > > On Sunday 14 December 2008 12:08:44 Gilboa Davara wrote: > > > To be honest, AFAIR VMWare Server 1.0.x, beyond being EOL, doesn't > > > support kernels >= 2.6.26 - even with the latest any-to-any patch. > > > Though, AFAIK, it didn't have SELinux problem under both F8 and F9. > > > On the other side VMWare Server 2.x hass replaced the GTK console > > > application with a super-complex web-client which, coupled with VMWare's > > > known tendency to release half-broken RPMs, makes it an SELinux accident > > > waiting to happen... > > > > Let me be precise. I have VMWare server running right now on this laptop on > > which I'm typing this message. In 'About' it says it is version 1.0.7 > > build-108231; my running kernel is - > > # uname -r > > 2.6.27.7-134.fc10.i686 > > the patch I'm using to make it work is called vmware-update-2.6.27-5.5.7-2 > > which I found using Google - it has survived several kernel upgrades and > > supercedes the any-any patches > > A. I was unaware of the vmware-update-2.6.27-5.5.7-2 patch. Last time I > checked (~1.5 months ago) only the any-to-any patch was available and it > didn't support kernels >= 2.6.26. > B. Much like the any-to-any patch, (and at least according to google) > this patch is unofficial. > C. As I previously said, -officially-, VMWare doesn't support Fedora. > [1] > D. As you recall, the OP asked if can send a BZ about his SELinux > problems in bugzilla.redhat.com - my original answer was rather simple: > VMware is proprietary and closed source, and doesn't officially support > Fedora. > > [1] VMWare server, user's guide, page 26. As the OP, I would say your response was a little touchier than that. Moreover, it did not even approach being helpful. In the context I originally asked, it doesn't matter that VMware doesn't officially support Fedora. If it were, I would have escalated it with VMware, especially since I have access to special support that many who use VMware don't. Lots of stuff, both open source and proprietary, isn't supported on Fedora by their respective vendors, but that doesn't stop people on the Fedora team from figuring out how to make it work. That also goes for VMware. I also know that they would be interested in documenting a fix for this problem. The original question was if anyone on the Fedora team knew of status of any potential fix (BZ or not - but I didn't mention BZ). Fortunately, someone does care enough to look into it (thanks Daniel Walsh). I'll send what I find with F10 and the latest Server 2.0 build this weekend... -- ====================== "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." -- Albert Einstein -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
