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; that reflects in open-vm-tools, since we sync the stable branch to those stable releases. 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, and in some cases the stable branch will pick up those changes. That will generally come out after some delay, since update releases have to go through our internal development and QA cycle. Sometimes, while preparing open-vm-tools updates, I'll cherry-pick a few changes from development that I consider "safe". But I'm not comfortable doing that for all types of changes. > 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 If, as your diff suggests, Fedora is changing the LINUX_VERSION_CODE macro, they are messing with the version number. So our checks, which are made for the official kernel versions, would have to be adjusted for Fedora's "unofficial version" kernels. That will happen once that Fedora / kernel combination becomes officially supported by VMware, but it doesn't seem to be the case now. Until then, you may keep your private patches, or also monitor changes to the master branch looking for fixes for newer kernels that might affect your Fedora kernel. -- - Marcelo ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ open-vm-tools-devel mailing list open-vm-tools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open-vm-tools-devel
