I've googled a bit and found a recent (the end of April) discussion on LKML. Briefly put, it turns out the main reasons for not including Reiser4 in the kernel are that its code is not compatible with the kernel's coding standards and that functionality Reiser4 provides as plugins would make more sense as VFS extensions. Andrew Morton said guys from Namesys didn't ask for inclusion. Edward Shishkin of Namesys replied that they still had some things to do.
Anyway, there was nothing about Reiser4 breaking other things in the kernel. And noone is required to use Reiser4. If someone doesn't consider it stable, then just don't use it. Let's be honest, there are many things in the kernel that we could call unstable, especially with the current development model. And even kernel developers say Reiser4 doesn't have to be bugless to be included. -- Jaroslaw Swierczynski <[EMAIL PROTECTED]> www.archlinux.org | www.juvepoland.com _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
