On Thu, Sep 18, 2014 at 03:48:03PM +0200, Thomas Jarosch wrote: > Hi Dmitry, > > On Monday, 15. September 2014 08:28:33 Dmitry Torokhov wrote: > > >> As Christoph says...no, there's no way that we'll revert that. > > >> > > >> Those functions have hooks into the audit layer and 3rd party modules > > >> almost universally got their usage wrong. > > > > > >thanks for the explanation, especially about the audit layer part. > > > > You do not need neither vmsync nor vmblock on kernels past 3.0 so just > > hack around vmware-coonfig-tools.pl (or whatever the install script is > > called) and do not compile them. > > thanks for the hint, that makes things a lot easier. > > Probably a lot of people on the web could stop to publish > compiling-but-more-or-less-working patches to port > those modules to recent kernels ;) Yeah. Well, it is hard for VMware to go back and adjust already released tools packages ;). I believe this issue is fixed in newer versions and in open-vm-tools. BTW, more and more distributions package open-vm-tools and I believe most of the needed kernel drivers are now in mainline so things should be getting better. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
