In message <[EMAIL PROTECTED]>,
Michael L Torrie <[EMAIL PROTECTED]> writes
>The problem would be solved if the win4lin patch was integrated into the
>official source tree, which would make any kernel compatibile. Of course
>we can't do that, the least of the reasons is that the kernel patch is
>property of netraverse and cannot (I'm presuming) be GPL'd nor is Linus
>likely to accept such a large, vertical patch, that may or may not have
>stability side effects.
er the patch is _more_ open than GPL - the patch is NOT the problem,
it's what the Merge VM module it hooks into does which would be the
unknown.
>
>I suggest a solution, though I don't know how feasible it is. VMWare
>installs its hooks as kernel modules, and actually builds them at install
>time. If ever upgrade my kernel, I just run this little configuration
>program and it rebuilds the modules for my new kernel. I can't think that
>VMWare reaches any deeper into the kernel than Win4Lin does.
Well I can (& & try reading the patch for an idea why)
win4lin is much faster and more compact a solution than vmware.
And the ultimate 'safe' relatively non-intrusive solution is bochs...
try it... if you can wait that long!
> Is this a
>viable alternative than patching or replacing people's kernels?
>
--
robert w hall
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
