and that seems
strange? ;-)
no, though in the past i have been amazed sometimes :-)
the -ac changelog. To me, it's trivial to
patch the rejects, but to
someone that isn't all that excited about it, it can be daunting.
sure, but getting the rejects to patch does not mean that the
patch is complete... i mean, new code paths might have been added
that require new stuff to be added in the patch, especially since
such a long time has passed between 2.4.20 and 2.4.21
anyway, i talked to andrew morton, and he suggests that it is better
to go for 2.5.x ...
i have been running 2.5 since patchlevel 68, and it has been working
great for me. i have made no comparative measurements with 2.4+lowlat,
but it "feels" good and is very stable - even most of linus' bitkeeper
snapshots have been ok.
disclaimer: mine is a scsi-only system...
i'd encourage people to try 2.5 to iron out audio-specific problems
before we go into 2.6-test and the developers get nervous...
jörn
--
All Members shall refrain in their international relations from
the threat or use of force against the territorial integrity or
political independence of any state, or in any other manner
inconsistent with the Purposes of the United Nations.
-- Charter of the United Nations, Article 2.4
Jörn Nettingsmeier
Kurfürstenstr 49, 45138 Essen, Germany