Guys, when you see "2.6.25-gitN", coming out of Linus's tree, that's his "pre 2.6.26-rc1" code, which some people call "-rc0". I really do wish Linus would have renamed his tree "-rc0" right after he releases a stable kernel, and before the next release's -rc1 comes out (i.e., during the merge window). The name 2.6.25-gitN gets some people confused as if it's the pending code prior to the release of 2.6.25.1, i.e., the next stable kernel minor release.
Anyway, Linus's tree has VFS changes from Al Viro which prevent unionfs from compiling now (->umount_begin's prototype changed). I've got a small patch for it, if anyone's interested. But frankly, if anyone wants stability, I'd stay far away from any kernels during the merge window: they are a rapidly moving target. This particular longer-than-usual merge window (for 2.6.26) had resulted in a buggier than usual codebase, to which several people have complained bitterly on lkml; if you have the patience, read the long flame-thread on lkml entitled "Slow DOWN, please!" Cheers, Erez. _______________________________________________ unionfs mailing list: http://unionfs.filesystems.org/ unionfs@mail.fsl.cs.sunysb.edu http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
