Daniel Hi :-) > I assume you worked it out, but the answer to your original question is: > > You need the kernel headers (and configuration) that match the kernel you are > building the module against. The "any-any" patch helps with newer kernels, > but doesn't change the equation: build VMWare against the same headers as the > kernel. > The reason for this is that different kernels, and different configuration > options, all change the layout of binary data structures that the module > refers to. > > Get that wrong and you can go direct to data corruption city, not passing go, > and not collecting anything but a lot of grief on the way.
I remember compiling headers couple of years ago on Potato/Etch (I think it was Etch. The machine doesn't live with me anymore). Anyway, the thing with vmware-config.pl is that it will _fail_ to compile a proper module if the kernel headers are wrong or missing anyway. So, although your statement might still be valid (the corruption bit... especially if you really intend to corrupt the data using special ABI magickery), I think in the OPs case, it will simply fail to compile+link if he/she gets the wrong headers. -- Regards, Ishwor Gurung -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
