Question about Reiser4
I know that this whole effort has been put in disarray by the prosecution of Hans Reiser, but I'm curious as to its status. Is Reiser4 going to be going into the Linus kernel anytime soon? Is there somewhere I should be looking to find this out without wasting bandwidth here?
I'm not an LKML subscriber.
Thanks,
Signature · 1 line
Eric Hopper (http://www.omnifarious.org/~hopper/)
Quoted 2 lines · Eric Hopper
I'm not an LKML subscriber.
Did you try searching LKML archives?
Lee
Quoted 2 lines · Eric Hopper
I know that this whole effort has been put in disarray by the prosecution of Hans Reiser, but I'm curious as to its status.
It was in disarray well before. Many of the reiser4 features, like filesystem plugins, make more technical sense in the Linux VFS, but made more business sense for Namesys as a reiserfs 4 thing. That lead to a stalemate.
Quoted 1 line
Is Reiser4 going to be going into the Linus kernel anytime soon?
I wouldn't count on it.
Quoted 9 lines
Quoted 2 lines · Eric Hopper
I know that this whole effort has been put in disarray by the prosecution of Hans Reiser, but I'm curious as to its status.
It was in disarray well before. Many of the reiser4 features, like filesystem plugins, make more technical sense in the Linux VFS, but made more business sense for Namesys as a reiserfs 4 thing. That lead to a stalemate.
Shouldn't it be a matter of stability though? Benchmarks suggest that reiser4 is a good file system; reiser4 is the successor to the already-accepted reiserfs; we've got experimental ext4 support but no reiser4 support, etc.
I don't see why something like plugins should matter. If it works enough to be marked as experimental, why shouldn't reiser4 support be included? It's a pain for me personally to have to patch any kernel with reiser4 support so I can use the reiser4 fs.
William Heimbigner
[email protected]
Quoted 10 lines · William Heimbigner
Quoted 9 lines
Quoted 2 lines · Eric Hopper
I know that this whole effort has been put in disarray by the prosecution of Hans Reiser, but I'm curious as to its status.
It was in disarray well before. Many of the reiser4 features, like filesystem plugins, make more technical sense in the Linux VFS, but made more business sense for Namesys as a reiserfs 4 thing. That lead to a stalemate.
Shouldn't it be a matter of stability though?
A lot of other things matter. Things like a willingness to maintain the code after it gets merged, or at least turning the code into something the community is willing to maintain if the original developers stop maintaining it.
Quoted 1 line
Benchmarks suggest that reiser4 is a good file system; reiser4 is the successor to the already-accepted reiserfs; we've got experimental ext4 support but no reiser4 support, etc.
Namesys kind of abandoned reiserfs after work on reiser4 started. Taking in a new code base on such a track record is not a good idea when the code is not in a shape where the community wants to maintain it.
Quoted 2 lines
I don't see why something like plugins should matter. If it works enough to be marked as experimental, why shouldn't reiser4 support be included? It's a pain for me personally to have to patch any kernel with reiser4 support so I can use the reiser4 fs.
You basically have three options:
1) keep patching every time you upgrade the kernel
2) use another filesystem
3) become the new reiser4 maintainer and turn the code into something that Linus is willing to accept
Signature · 3 lines
Politics is the struggle between those who want to make their country the best in the world, and those who believe it already is. Each group calls the other unpatriotic.
Quoted 31 lines
Quoted 10 lines · William Heimbigner
Quoted 9 lines
Quoted 2 lines · Eric Hopper
I know that this whole effort has been put in disarray by the prosecution of Hans Reiser, but I'm curious as to its status.
It was in disarray well before. Many of the reiser4 features, like filesystem plugins, make more technical sense in the Linux VFS, but made more business sense for Namesys as a reiserfs 4 thing. That lead to a stalemate.
Shouldn't it be a matter of stability though?
A lot of other things matter. Things like a willingness to maintain the code after it gets merged, or at least turning the code into something the community is willing to maintain if the original developers stop maintaining it.
Quoted 3 lines
Benchmarks suggest that reiser4 is a good file system; reiser4 is the successor to the already-accepted reiserfs; we've got experimental ext4 support but no reiser4 support, etc.
Namesys kind of abandoned reiserfs after work on reiser4 started. Taking in a new code base on such a track record is not a good idea when the code is not in a shape where the community wants to maintain it.
Quoted 4 lines
I don't see why something like plugins should matter. If it works enough to be marked as experimental, why shouldn't reiser4 support be included? It's a pain for me personally to have to patch any kernel with reiser4 support so I can use the reiser4 fs.
Quoted 8 lines
You basically have three options:
1) keep patching every time you upgrade the kernel
2) use another filesystem
3) become the new reiser4 maintainer and turn the code into something that Linus is willing to accept
I suppose. I have a feeling there's an underlying issue behind "code standards" (and even then, I think that code standards is ultimately an excuse for not integrating reiser4 support into the kernel, but that's just my opinion). However, is the code really in such a shape that the community doesn't want to maintain it? Obviously there's a significant number of people interested in reiser4 - if there weren't, questions like this wouldn't keep getting asked.
William Heimbigner
[email protected]
Quoted 1 line · William Heimbigner
However, is the code really in such a shape that the community doesn't want to maintain it? Obviously there's a significant number of people interested in reiser4 - if there weren't, questions like this wouldn't keep getting asked.
There are people interested in using it, yes.
However, nobody appears to have stepped up to maintain the code. If somebody really wanted to maintain the code, there would be a new maintainer already.
Signature · 3 lines
Politics is the struggle between those who want to make their country the best in the world, and those who believe it already is. Each group calls the other unpatriotic.
Quoted 7 lines · Rik van Riel
Quoted 4 lines · William Heimbigner
However, is the code really in such a shape that the community doesn't want to maintain it? Obviously there's a significant number of people interested in reiser4 - if there weren't, questions like this wouldn't keep getting asked.
Quoted 5 lines
There are people interested in using it, yes.
However, nobody appears to have stepped up to maintain the code. If somebody really wanted to maintain the code, there would be a new maintainer already.
On that note, what exactly is wanted for (assuming there was a maintainer) reiser4 to be suitable for inclusion in the kernel? To my knowledge (and I'll admit, I haven't looked in to it very far) the primary reason for rejection was that it broke coding standards.
If there was 1) a maintainer and 2) code that didn't break "coding standards", would it be included in the kernel?
William Heimbigner
[email protected]
Quoted 1 line · William Heimbigner
If there was 1) a maintainer and 2) code that didn't break "coding standards", would it be included in the kernel?
While I cannot speak for Linus and Andrew, code that fulfills these criteria (and is useful to have - reiser4 seems to have enough user interest) usually gets accepted.
http://kernelnewbies.org/UpstreamMerge has some hints.
Signature · 3 lines
Politics is the struggle between those who want to make their country the best in the world, and those who believe it already is. Each group calls the other unpatriotic.
Quoted 10 lines · Rik van Riel
Quoted 2 lines · William Heimbigner
If there was 1) a maintainer and 2) code that didn't break "coding standards", would it be included in the kernel?
While I cannot speak for Linus and Andrew, code that fulfills these criteria (and is useful to have - reiser4 seems to have enough user interest) usually gets accepted.
http://kernelnewbies.org/UpstreamMerge has some hints.
So in conclusion / to answer Eric's question,
1) reiser4 needs a maintainer
2) reiser4 needs the code quality cleaned up
3) Until those two things happen, it's extremely unlikely that it will be included in the kernel.
Correct?
William Heimbigner
[email protected]
Quoted 11 lines · On Mon, 23 Apr 2007 06:42:24 +0000 (GMT) William Heimbigner…
Quoted 9 lines · Rik van Riel
Quoted 2 lines · William Heimbigner
If there was 1) a maintainer and 2) code that didn't break "coding standards", would it be included in the kernel?
While I cannot speak for Linus and Andrew, code that fulfills these criteria (and is useful to have - reiser4 seems to have enough user interest) usually gets accepted.
Quoted 8 lines
Quoted 1 line
http://kernelnewbies.org/UpstreamMerge has some hints.
So in conclusion / to answer Eric's question,
1) reiser4 needs a maintainer
2) reiser4 needs the code quality cleaned up
3) Until those two things happen, it's extremely unlikely that it will be included in the kernel.
The namesys engineers continue to maintain reiser4 and I continue to receive patches for it.
Right now I'd say that the main blockages for reiser4 are a) the developers aren't presently asking for inclusion (afaik) and b) lack of reviewing effort from other kernel developers.
Here is something I don't understand...
It seems there is a maintainer, namesys people, which is what I was supposing, and probably it is the most qualified one for reiser4,
but it also seems you imply that they are not interested right now in kernel inclusion, since they are not asking "in this moment" for it.
Do I misunderstand? To me it seems they are implicitally interested in kernel inclusion since they are maintaining the code, and they alredy asked for this.
regards
Luigi
Quoted 13 lines · Andrew Morton
The namesys engineers continue to maintain reiser4 and I continue to receive patches for it.
Right now I'd say that the main blockages for reiser4 are a) the developers aren't presently asking for inclusion (afaik) and b) lack of reviewing effort from other kernel developers.
-
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/
Quoted 6 lines · Andrew Morton
The namesys engineers continue to maintain reiser4 and I continue to receive patches for it.
Right now I'd say that the main blockages for reiser4 are a) the developers aren't presently asking for inclusion (afaik) and b) lack of reviewing effort from other kernel developers.
If someone else started asking for it to be included and responded to requests for the various code changes required to increase its quality to the required level, wouldn't that be enough? Basically, if someone forked it.
Or does it specifically have to be namesys engineers?
Oh, two things really interest me about Reiser4. First, I despise having to care about how many tiny files I leave lying around when writing a program. Berkeley DB and its ilk are evil, evil programs that obscure data and make things harder. Secondly, the moves Reiser4 has made towards having actual transactions at the filesystem level also intrigue me.
I want to use the filesystem as a DB. IMHO, there is no reason that filesystems shouldn't be a DB sans query language. If there were a more DB-like way to deal with filesystems, I think that it would be that much easier to make something that was a decent replacement for NFS and actually worked.
Sadly, unless someone pays me to maintain it, I can't do the fork myself, and I likely wouldn't anyway as being a kernel hacker of something as important as a filesystem is a full-time job and I have other things that interest me a lot more.
Just curious,
Signature · 1 line
Eric Hopper (http://www.omnifarious.org/~hopper/)
Quoted 8 lines · On Mon, 23 Apr 2007 06:52:16 -0700 Eric Hopper <[email protected]> wrote:
Quoted 6 lines · Andrew Morton
The namesys engineers continue to maintain reiser4 and I continue to receive patches for it.
Right now I'd say that the main blockages for reiser4 are a) the developers aren't presently asking for inclusion (afaik) and b) lack of reviewing effort from other kernel developers.
Quoted 6 lines
If someone else started asking for it to be included and responded to requests for the various code changes required to increase its quality to the required level, wouldn't that be enough? Basically, if someone forked it.
Or does it specifically have to be namesys engineers?
That's not where the problem lies - the namesys guys are responsive and play well with others. But they haven't received any "requests for the various code changes" in over a year.
And I'm in the same boat as most everyone else: I haven't looked at the reiser4 code in ages. Right now I don't have anything like a list of outstanding technical issues.
To get it unstuck we'd need a general push, get people looking at and testing the code, get the vendors to have a serious think about it, etc. We could do that - it'd require that the namesys people (and I) start making threatening noises about merging it, I guess.
Or we could move all the reiser4 code into kernel/sched.c - that seems to get people fired up.
Quoted 5 lines · Andrew Morton
To get it unstuck we'd need a general push, get people looking at and testing the code, get the vendors to have a serious think about it, etc. We could do that - it'd require that the namesys people (and I) start making threatening noises about merging it, I guess.
My impression was that a lot of negative discussion came out of some of the user interface inventions in r4 (like sys_reiser4 and the
new incompatible EA interface).
I guess a good strategy to get it going would be to extract just a "core reiser4" out of it that is just a file system without any new interfaces like this.
I would expect that reviewing that would be much smoother because people could actually concentrate on the technical details.
-Andi
Quoted 8 lines · Andrew Morton
To get it unstuck we'd need a general push, get people looking at and testing
the code, get the vendors to have a serious think about it, etc. We could do
that - it'd require that the namesys people (and I) start making threatening noises about merging it, I guess.
Quoted 4 lines
Or we could move all the reiser4 code into
kernel/sched.c- that seems to get
people fired up.
-
Just an idea: And what about creating a new tree (like -r4), maintained by namesys people, tested by several people, with dedicated mailing list, etc.?
That way, the code could be patched, updated and cleaned over the time (without firing up people), it could be tested without pain, people would send more bug reports and every work would be centralized. Reiser4 would get much more attention.
Signature · 2 lines
Miguel Ojeda http://maxextreme.googlepages.com/index.htm
Quoted 7 lines · Eric Hopper
Oh, two things really interest me about Reiser4. First, I despise having to care about how many tiny files I leave lying around when writing a program. Berkeley DB and its ilk are evil, evil programs that obscure data and make things harder. Secondly, the moves Reiser4 has made towards having actual transactions at the filesystem level also intrigue me.
Quoted 5 lines
I want to use the filesystem as a DB. IMHO, there is no reason that filesystems shouldn't be a DB sans query language. If there were a more DB-like way to deal with filesystems, I think that it would be that much easier to make something that was a decent replacement for NFS and actually worked.
One of the big problems of using a filesystem as a DB is the system call overheads. If you use huge numbers of tiny files, then each attempt read an atom of information from the DB takes three system calls --- an open(), read(), and close(), with all of the overheads in terms of dentry and inode cache.
Hans of course had a solution to this problem --- namely the sys_reiser4 system call, where you download a program to the kernel to execute a open/read/close via a single system call, and which returns the combined results to userspace. But now you have more complexity since there is now a reseir4-specific interpreter embeddeed in the kernel, the userspace application needs to write the equivalent of an channel program such as what was found in an IBM/360 mainframe (need I mention this can be a rich source of security bugs), and then the userspace application *still* needs to parse the result returned by the sys_reiser4() system call?
So it adds a huge amount of complexity, and at the end of the day, given that you don't have the search capability, it is (a) less functional, (b) more complexitated, and (c) probably less performant than simply calling out to a database.
Quoted 4 lines
Sadly, unless someone pays me to maintain it, I can't do the fork myself, and I likely wouldn't anyway as being a kernel hacker of something as important as a filesystem is a full-time job and I have other things that interest me a lot more.
Unfortunately, the way OSS works is that you either (a) have to do the work yourself, (b) convince someone else to do the work, or (c) convince someone that it's worth paying you to do it.
Personally, if I controlled large budget for Linux filesystem development, I'd put a lot more money into something like Val's chunkfs idea than resier4. Being able to have filesystems designed for fast recovery given disks getting larger and larger (but not more reliable), is a whole lot more improtant than trying to create an alternate solution to an already solved problem --- namely that of a database. When you consider that a similar idea, WinFS, was partially responsible for delaying Vista by years due to the complexity of shoving a database where it has no place being, it's another reason why I personally think that chunkfs is a much more promising avenue for future filesystem investment than reiserfs.
But hey, the advantage of Open Source is that if *you* want to work on Reiser4, you're perfectly free to do so. My personal opinion is that it'd be a waste of your time, but you're free to spend your time whichever way that you want. What you don't get do is whine about how other people get to spend *their* time, or *their* money.
- Ted
Quoted 7 lines · Theodore Tso
One of the big problems of using a filesystem as a DB is the system call overheads. If you use huge numbers of tiny files, then each attempt read an atom of information from the DB takes three system calls --- an
open(),read(), andclose(), with all of the overheads in terms of dentry and inode cache.
Now, to be fair, there are probably a number of cases where open/lseek/readv/close and open/lseek/writev/close would be worth doing as a single system call. The big problem as far as I can see involves EINTR handling; such a system call has serious restartability implications.
Of course, there are Ingo's syslets...
-hpa
Quoted 9 lines · On Monday April 23, [email protected] wrote:
Quoted 7 lines · Theodore Tso
One of the big problems of using a filesystem as a DB is the system call overheads. If you use huge numbers of tiny files, then each attempt read an atom of information from the DB takes three system calls --- an
open(),read(), andclose(), with all of the overheads in terms of dentry and inode cache.
Quoted 6 lines
Now, to be fair, there are probably a number of cases where open/lseek/readv/close and open/lseek/writev/close would be worth doing as a single system call. The big problem as far as I can see involves EINTR handling; such a system call has serious restartability implications.
Of course, there are Ingo's syslets...
Our you could think outside the circle:
Store all your "small files" as symlinks, then use "symlink" to create them and "readlink" to read them. (You would probably end up use symlinkat and readlinkat).
Only one system call instead of three.
I guess you don't get meaningful permission bits then... I wonder if that really matters.
NeilBrown
Quoted 9 lines · Neil Brown
Our you could think outside the circle:
Store all your "small files" as symlinks, then use "symlink" to create them and "readlink" to read them. (You would probably end up use symlinkat and readlinkat).
Only one system call instead of three.
I guess you don't get meaningful permission bits then... I wonder if that really matters.
For some applications, oh yes it does.
-hpa
Quoted 11 lines · H. Peter Anvin
Quoted 8 lines · Neil Brown
Our you could think outside the circle:
Store all your "small files" as symlinks, then use "symlink" to create them and "readlink" to read them. (You would probably end up use symlinkat and readlinkat).
Only one system call instead of three.
I guess you don't get meaningful permission bits then... I wonder if that really matters.For some applications, oh yes it does.
Put them in a protected directory.
Jan
Quoted 9 lines · H. Peter Anvin
Quoted 7 lines · Theodore Tso
One of the big problems of using a filesystem as a DB is the system call overheads. If you use huge numbers of tiny files, then each attempt read an atom of information from the DB takes three system calls --- an
open(),read(), andclose(), with all of the overheads in terms of dentry and inode cache.
Quoted 4 lines
Now, to be fair, there are probably a number of cases where open/lseek/readv/close and open/lseek/writev/close would be worth doing as a single system call. The big problem as far as I can see involves EINTR handling; such a system call has serious restartability implications.
Sure, but Hans wants to change /etc/inetd.conf into /etc/inetd.conf.d, where you have: /etc/inetd.conf.d/telnet/port, /etc/inetd.conf.d/telnet/protocol, /etc/inetd.conf.d/telnet/wait, /etc/inetd.conf.d/telnet/userid, /etc/inetd.conf.d/telnet/daemon, etc. for each individual line in /etc/inetd.conf. (And where each file might only contains 2-4 characters each: i.e., "23", "tcp", "root", etc.)
So it's not enough just to collapse open/pread/close into a single system call; in order to gain back the performance squandered by all of these itsy-bitsy tiny little files. You want to collapse the open/pread/close for many of these little files into a single system call, hence Hans's insistence on sys_reiser4(); otherwise his scheme doesn't work all that well at all.
- Ted
Quoted 11 lines · Theodore Tso
Quoted 2 lines
Quoted 1 line
Now, to be fair, there are probably a number of cases where open/lseek/readv/close and open/lseek/writev/close would be worth doing as a single system call. The big problem as far as I can see involves EINTR handling; such a system call has serious restartability implications.
Sure, but Hans wants to change
/etc/inetd.confinto/etc/inetd.conf.d, where you have:/etc/inetd.conf.d/telnet/port,/etc/inetd.conf.d/telnet/protocol,/etc/inetd.conf.d/telnet/wait,/etc/inetd.conf.d/telnet/userid,/etc/inetd.conf.d/telnet/daemon, etc. for each individual line in/etc/inetd.conf. (And where each file might only contains 2-4 characters each: i.e., "23", "tcp", "root", etc.)
Quoted 7 lines
So it's not enough just to collapse open/pread/close into a single system call; in order to gain back the performance squandered by all of these itsy-bitsy tiny little files. You want to collapse the open/pread/close for many of these little files into a single system call, hence Hans's insistence on
sys_reiser4(); otherwise his scheme doesn't work all that well at all.
Heh. sys_read_tree() -- walk a directory tree and return it as a data structure in memory :)
-hpa
Quoted 2 lines · H. Peter Anvin
Heh.
sys_read_tree()-- walk a directory tree and return it as a data structure in memory :)
But maybe you don't want every single file in the directory, but some subset of the files in the directory tree. So before you know it:
sys_fs_sql("SELECT port,userid,daemon FROM /etc/inetd.conf.d "
"WHERE protocol=='tcp'", buf, sizeof(buf));
The question is where do you stop on the slippery slope, and is it really all that harder than simply parsing a /etc/gitconfig or /etc/e2fsck.conf file. There are plenty of parsers or database libraries already written, and many of them are quite efficient. And personally, I'd much rather edit a single /etc/gitconfig or /etc/e2fsck.conf file using emacs than have to cd through 3 or 4 levels of directories to edit each 2-3 byte file one at a time. But to each their own....
- Ted
Quoted 9 lines
Quoted 7 lines · Theodore Tso
One of the big problems of using a filesystem as a DB is the system call overheads. If you use huge numbers of tiny files, then each attempt read an atom of information from the DB takes three system calls --- an
open(),read(), andclose(), with all of the overheads in terms of dentry and inode cache.
Quoted 6 lines
Now, to be fair, there are probably a number of cases where open/lseek/readv/close and open/lseek/writev/close would be worth doing as a single system call. The big problem as far as I can see involves EINTR handling; such a system call has serious restartability implications.
Of course, there are Ingo's syslets...
I definitely would like open/readv/close syscall a lot. Actually, a set of four syscalls
open/readv/close
open/pread/close
open/writev/close
open/pwrite/close
will allow to reduce syscall overhead for a number of cases. --
vda
Quoted 7 lines · Theodore Tso
Sure, but Hans wants to change
/etc/inetd.confinto/etc/inetd.conf.d, where you have:/etc/inetd.conf.d/telnet/port,/etc/inetd.conf.d/telnet/protocol,/etc/inetd.conf.d/telnet/wait,/etc/inetd.conf.d/telnet/userid,/etc/inetd.conf.d/telnet/daemon, etc. for each individual line in/etc/inetd.conf. (And where each file might only contains 2-4 characters each: i.e., "23", "tcp", "root", etc.)
One interesting thing is that /proc already does this. You can often generate interesting behavior by writing something into a file in /proc. If the config file for inetd.conf.d/tellnet/port changed, inetd could automatically reconfigure that service, and just that service. No more re-reading a config file and trying to figure out what changed, you are notified as soon as it changes on the FS by the FS change detection code already in place.
It seems to me that being able to be more transparent about how your on-disk data structures are structured has many interesting implications and possible advantages. It should be able to be explored by the wider sphere of app developers. Perhaps you are right, and the performance implications of making all those system calls will be too much. Or maybe there's some good way nobody has thought of yet to handle that problem. But until the idea can be experimented on and played with, nobody will know.
And realistically for that to happen Reiser4 has to be available as an option in the kernels shipped by the major distributions. And this in turn requires that it be part of the mainline kernel.
Also, regardless of whether tiny files and on-disk datastructure transparency exist, I think filesystems should also support ACID. I would, in fact, be much happier with ACID support at the filesystem level than on-disk datastructure transparency. And while Reiser4 doesn't do this, as I understand it (and I might be wrong) there is some limited support for transactions built into it beyond simple lock handling.
Signature · 1 line
Eric Hopper ([email protected] http://www.omnifarious.org/~hopper/)
Quoted 10 lines · Eric M. Hopper
Quoted 9 lines · On Tue, 2007-04-24 at 17:12 -0700, [email protected] wrote:
On Sun, 22 Apr 2007 19:00:46 -0700, "Eric Hopper"
Quoted 5 lines
<[email protected]> said:
I did. That whole thread is some guy spouting off a ludicrous Bonnie++ benchmark showing that compressing long strings of 0s results in things taking up very little space and being very fast.
I think you are deliberately being stupid here.
Quoted 8 lines
Quoted 4 lines
You are claiming that REISER4's good speed results when using compression actually has a simple explanation and THEREFORE all good result for the filesystem, even those results that have nothing to do with compression, are negated.
I am claiming nothing of the sort. You are assuming that I'm claiming this for some random reason. And in so doing, you are hurting your cause and mine.
Yes you are. Your claim may have only been implicit, but it was also VERY clear.
You complain that Reiser4's excellent speed results when using compression might have a simple explanation.
You then implicitly write off the whole set of results on this basis, which is just plain dishonest.
You could have pointed out that most of the results did NOT use compression, but instead you just ignored them.
You could have asked by how much, bonnie++'s use of files that are mainly zeroes, affected the excellent speeds.
But you didn't, because you weren't really interested.
You ignored about 90% of the benchmarks and concentrated on a very small area that you could raise a question about.
That is not someone looking for the truth. That is a propagandist working against Reiser4.
Your conclusion was that of someone who is trying to destroy Reiser4, while PRETENDING to support it.
Well. At least that is what it looks like to me.
Quoted 2 lines
and ranting about how everybody is ignoring all the good parts of it and focusing on the bad parts makes things even worse.
Yes YOU are ignoring all the good parts of it and focusing on the (well not bad parts but) parts that seem too good to be true.
Signature · 4 lines
[email protected] -- http://www.fastmail.fm - A no graphics, no pop-ups email service
Quoted 1 line · William Heimbigner
Obviously there's a significant number of people interested in reiser4
Count me in.
Jeff.