Re: [cbm4linux-users] Problems with cbm4linux

[Dirk J. <do...@cu...>]

> One could come to the conclusion that these always changing APIs do no
> good. It is the Linux' way to force people keeping up.

You'd better ask this on LKML and be prepared for tons of flames :-)

> Personally, I'd like it if you could try to keep them more separate. You
> want to remove things with a patch: Then make a patch which only does
> this, nothing more.

You're right at this point. I've now reworked all my changes and came up 
with 6 patches, which should do only one thing at a time, although some 
of them patch in the same areas and are therefore slightly dependand on 
each other.
I have updated the patches on
http://sourceforge.net/tracker/?group_id=45917&atid=444478

> As Michael has no means to test the Windows code, this "cross-testing"
> is mostly my task. As I do own some Linux machines, I want to be able to
> test the Linux code, too.

I have a machine which can boot linux 2.6 and XP. And I'm willing to 
help out.

> If the support for < 2.4 is dropped, it will be hard for me to be able
> to test both variants. Anyway, I would like to be able to do this, as

I don't insist on dropping support for old kernels if people want to 
keep it. I can live with the code present in the source, as it's 
#ifdef'ed anyway.

-- 
---> doj / cubic
----> http://cubic.org/~doj
-----> http://llg.cubic.org