On Wed, Feb 15, 2012 at 02:18:59PM +0200, pageexec@... wrote:
> > I can't try gentoo-sources and hardened-sources with exactly same
> > vmware-modules, because of extra patches needed for vmware-modules to make
> > it compatible with hardened, and these patches incompatible with non-hardened.
> what error do you get with the patched vmware modules under non-hardened?
> they simply move some structure initialization around, that should not be
> affected by the toolchain.
Actually there is no error anymore. I've replaced my previous
3.2.0-compatibility patch with similar patch from main portage, and now
vmware-modules with these 3 hardened-compatibility patches was compiled
without errors both for hardened kernel and 3.2.1-gentoo-r2.
So, I've just tested hardened vs non-hardened kernels using exactly same
vmware-modules. Result is same: on hardened kernel vmware reset host,
on gentoo kernel vmware works ok.
If you've any ideas how to debug/fix this issue - I'm ready to test
anything you need. VMware is critical tool for my work, so without it
chances are I'll have to convert my system back to x86. :(
> > +CONFIG_IA32_AOUT=y
> btw, i don't think you need/want a.out support anywhere these days ;)
Who knows. It shouldn't make any harm, anyway. I can remember about two
cases in last ~2-3 years when I did something with a.out. Don't remember
details, and that was surely very strange tasks, but it happens.