love1 was the test bed, Since i'm a little new to the whole kernel development field love1 was the platform in which we tested on and love2 is full release._________________ArchLinux 64 Dev | 2.6.14 AMD64

Nicks scheduler is slower atm, and doesn't want to patch onto rc4 although i could hack it in, it would be dirty, and sluggish. So i'm not going there. And teaming up that's not up to me._________________ArchLinux 64 Dev | 2.6.14 AMD64

Well it doesn't work for me...
Mounting my reiser4 partitions on boot burps out hundreds of syscalls and errors

I get the same... the initial read-only mount of reiser4 root works correctly, and passes the fsck. However, when init tries to remount r/w, it oopses and core dumps with a NULL pointer dereference somewhere in reiser4/inode.c, can't remember exactly which function. 2.6.8-rc2-love3 works fine with the same settings.

I also got the compile error regarding 4K stacks and Reiser4. I was able to use 4K stacks and Reiser4 with nitro-sources, and also with 2.6.8-rc2-love3 (although that was unstable, so I backed out 4K stacks). But neither kernels gave a compile error abour reiser4/4K incompatibilities._________________If tugboats were bigger, they'd be the ones getting tugged.

I got the same message about 4k stacks with a patched mm-sources I was playing with recently. The stacks were on by default, so caught me out...
But it seems not to be specific to this version of love-sources anyway.

I can do without 4k stacks, they aren't really necessary for desktops (and these patchsets are, quite frankly, far from ready for servers). However, I do want to figure out why the reiser4 patch is broken in the this love-sources.

Did reiser4 patch cleanly on this release? Did you need to remove a line referring to desc.buf in order to get it to compile? They were having some similar problems over in the nitro-sources camp today.

I have to say, it is interesting to see love and nitro converging to just about the same patchset. IMHO nitro is faster, but love has a better history of stability. Perhaps a little collaboration between the projects would be mutually beneficial?_________________If tugboats were bigger, they'd be the ones getting tugged.