From: Matthias Andree <matthias.andree@gmx.de>
To: ivo welch <ivowel@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserFS?
Date: Sun, 16 Jul 2006 15:50:38 +0200 [thread overview]
Message-ID: <20060716135038.GA8850@merlin.emma.line.org> (raw)
In-Reply-To: <50d1c22d0607160545rd06c828n55ad9bbbd2f20bfd@mail.gmail.com>
On Sun, 16 Jul 2006, ivo welch wrote:
> dear linux geeks: may I ask why the "new" (many years old) reiser
> filesystem is not making it into the kernel? it does seem to have
> some advantages, if nothing else at least over the old reiser v3.
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?
Besides that, there had been technical discrepancies that prevented
reiser4 inclusion into the baseline kernel when it was suggested, search
the archives for details.
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.
--
Matthias Andree
next prev parent reply other threads:[~2006-07-16 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-16 12:45 reiserFS? ivo welch
2006-07-16 13:50 ` Matthias Andree [this message]
2006-07-16 15:29 ` reiserFS? Lexington Luthor
2006-07-16 16:55 ` reiserFS? grundig
2006-07-17 9:23 ` reiserFS? Arjan van de Ven
2006-07-17 16:32 ` reiserFS? Lexington Luthor
2006-07-17 14:56 ` reiserFS? Matthias Andree
2006-07-16 14:19 ` reiserFS? Joseph Le-Phan
2006-07-16 16:16 reiserFS? Xavier Roche
2006-07-16 16:28 ` reiserFS? Christian Trefzer
2006-07-16 16:56 ` reiserFS? Theodore Tso
2006-07-16 17:26 ` reiserFS? Lexington Luthor
2006-07-16 17:48 ` reiserFS? Theodore Tso
2006-07-16 17:46 ` reiserFS? Dr. David Alan Gilbert
2006-07-16 18:14 ` reiserFS? Theodore Tso
2006-07-17 15:01 ` reiserFS? Matthias Andree
2006-07-17 21:07 ` reiserFS? Helge Hafting
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060716135038.GA8850@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=ivowel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®