Am 28.11.2011 19:09, schrieb Marcelo Vanzin:
> On 11/24/2011 03:09 AM, Reindl Harald wrote:
> If you look at the master branch a few of these issues might have been fixed
> already. As our QA starts testing new distros / updates to existing distros,
> we'll fix things in the development branch, a
On 11/24/2011 03:09 AM, Reindl Harald wrote:
> why not patching the sources?
That's a side-effect of how VMware adds support for newer distros. Right now I
don't believe brand new distros (or recent distros that have had kernel
updates) are officially supported by the current released products; th
why not patching the sources?
there is nothing messing in fedora
devel-kernel 2.6.40 was renamed to 3.0 from linux
so fedoras 2.6.40 is 3.0 and fedoras 2.6.41 is 3.1
and since upstream > 2.6.39 was never released this is safe
the original comment above my changed line speaks about
3.1 and in the
Hi Reindl,
I have an update to 8.8.x open-vm-tools that should provide a fix for that;
but it will probably need adjustments since Fedora is messing with the kernel
version numbers.
I'm planning to post the update later today.
On 11/23/2011 06:55 AM, Reindl Harald wrote:
> hi
>
> currently ther
hi
currently there seems to be no way to get open-vm-tools
compiled with recent 2.6.41-kernels of Fedora 15 and
rpmfusion seems to have totally dropped there packages
F14 support is ending this month
so in december users are forced updating to F15 which is a disaster
without vmware-tools on recen
