Tim Fairchild wrote:
> Tho win4lin does work when it gets going, these first v1.0 and v2.0 Beta's
> we've been using have been an install nightmare unless you are running an
> absolute basic stock install of a distro they choose to support. If you use
> anything else or have even a slight custom kernel, like for sound support or
> scsi-emu - or a current kernel they haven't supported yet - then it's a big
> job to install.
>
Interesting. I've never had any problems patching the kernels, and my
kernels are heavily patched for all sorts of things - ipsec, pptp, raid,
etc. I am running right now on a 2.2.17 kernel with various patches.
Except for the very first release, when then-Trelos released a
dos-formatted patch file, I never had a problem with patching the
kernels.
I run RedHat, and on some machines I have all sorts of devel, beta, and
unstable stuff, and I've never glitched win4lin. And yes, I run sound,
scsi-emu, paride, all sorts of weird things I don't really expect to be
as well supported in Linux as they are.
Anyway, I have no pressing need to move to 2.4 except on one laptop
which is lacking sound support right now - so my win4lin 2.0 will remain
functional for a while yet.
--Yan
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
