On Mon, 19 Mar 2001, John Nelson wrote:
> I'm not running a custom kernel nor have I rebuilt the kernel although I
> *have* upgraded to the latest version of the kernel using the "up2date"
> utility. If this isn't considered "stock" well ok, but it gets right back
> to what I was saying before ... all you have to do is upgrade to the
> latest kernel available from RedHat or any other vendor and suddenly you
> can't run Win4Lin.
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.
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. Is this a
viable alternative than patching or replacing people's kernels?
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
