Improve Your GNU/Linux Experience With -mm Patches

An anonymous reader writes "Anyone interested in squeezing maximum performance out of their GNU/Linux operating system and willing to compile a new kernel will be interested in this KernelTrap article about Andrew Morton's -mm patchset. The patchset currently offers better stability and performance than the mainline 2.6.0-test kernel, as well as containing numerous functionality enhancements. Much of the additional functionality is described, as well as providing simple step by step installation instructions. Reading this article, one can certainly understand why Linux creator Linus Torvalds has chosen Andrew to soon become the 2.6 maintainer."

Comments

Re:synaptics touchpad support

[Dave2 Wickham]

Erm... Because it is?

[dave@tc4 ~/linux-2.5.74]$ grep Synaptics drivers/input/mouse/Kconfig
compatible. Support for Synaptics TouchPads is also included.
For Synaptics TouchPad support in XFree86 you'll need this XFree86

(standard 2.6.0-test5)

Warning to XFS users

[Kaladis Nefarian]

2.6.0-test5-mm3 apparently has a bad snapshot of the XFS code in it. Here's the post from linux-kernel:

From: Steve Lord <lord at sgi dot com>
To: Walt H <waltabbyh at comcast dot net>
Cc: Linux Kernel <linux-kernel at vger dot kernel dot org>,
Linux XFS Mailing List <linux-xfs at oss dot sgi dot com>

On Sun, 2003-09-21 at 13:08, Walt H wrote:
>> Just a follow-up to my earlier post:
>>
>> I've put in the xfs code from mm2 into the mm3 tree and all files get
>> copied and I can manually copy the fstab.backup file afterward. I
>> realized that the "rebuilding directory inode 256" was the lost+found
>> directory, which contained 4 old zero length files. That was the key.
>> XFS under -mm2 doesn't care about old lost+found directories, while -mm3
>> does. If I removed the source lost+found/ and retried rsync's with -mm3,
>> it finishes fine and I can copy fstab files. Adding a bogus lost+found
>> dir with any file in it at the source, and retrying the rsync will lead
>> to a state where I can't overwrite the existing /etc/fstab file at the
>> end. So it doesn't look like there's actually any filesystem corruption,
>> just a strange bug. Hope that helps,
>>
>> -Walt
>>

If I am correct, test5-mm3 contains a bad version of the xfs code, there
was a bug where the i_flags field was setup from an uninitialized stack
variable. mm3 came out during the two days this was in Linus's tree.
I had some very odd behavior with this code base, rm -r -f would try and
cd into files and other bizzare things, files could appear to be
immutable or append only or things they were not. This sounds like
similar behavior you that you saw. It is fixed in the latest code Linus
has.

Steve

So XFS users should probably go with -mm2 for now.

Re:Hmm

[Anonymous Coward]

> Hmm.. I thought Linux was open source and anyone could damn well do what they please with it. What's stopping me from becoming the Linux 2.6 kernel maintainer?

Nothing at all is stopping you from becoming a 2.6 kernel maintainer, in the same way that Alan Cox, Dave Jones et al maintain well-respected 'unofficial', but important, variations on the 2.4 tree. You set up a 2.6 tree, incorporate patches that strike you as being particularly useful, and who knows? - others may feel the same, and your tree (and you!) get to the same point as a dj or mm tree.

No, yours won't be the 'official' (ie, the reference) 2.6 tree - just because you set up a 2.6 tree doesn't obligate Linus or his designated maintainer from accepting your patches - but neither can they/do they/would they prevent others from using your tree if they prove useful, and if your particular patch set does prove widely useful, you've got a good shot at getting them included in the main reference tree.

And, the more variations on a given kernel tree, the better. They're excellent labs for trying out things that the reference tree maintainers may not want to try just yet, and give good alternative kernel sources for those not up to such an ongoing project. So yes, I'd recommend you do exactly as you seem to be suggesting, and set up and maintain a 2.6 tree with whatever patch set you feel worthwhile.