Matthias Andree wrote:
Why would anyone want ReiserFS in the kernel that is discontinued by its
developers when it's just started to become stabile and useful, with
bugs (hashing) remaining, as happened with 3.6? Who is going to make
guarantees this won't happen again with reiser4?
I looked at the reiser4 patch, and it does very little outside of the
fs/reiser4 directory. If it is no longer supported by namesys, why can't
it just be removed from the kernel like all the other bits that are
obsoleted?
I am just saddened that kernel decisions are motivated by politics and a
personal dislike of Hans Reiser rather than technical merit. :(
There's ext3, you can set the dir_index option (either for mke2fs, or
afterwards with tune2fs, then unmount and run e2fsck -fD) and you're set.
I am not arguing for the inclusion of reiser4 in the kernel, but you
should know it has its uses. There are very many things that reiser4 can
do that will make ext3 blow up. It simply the best filesystem for many
kinds of usage patterns.
Regards,
LL
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
