From: Hans Reiser <reiser@namesys.com>
To: "Maciej Sołtysiak" <pysiak.satriani@wp.pl>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: future r4 maintenance question
Date: Sun, 23 Jul 2006 00:07:47 -0600 [thread overview]
Message-ID: <44C31233.9080800@namesys.com> (raw)
In-Reply-To: <1287558327.20060722215128@wp.pl>
Maciej Sołtysiak wrote:
>Hello Hans,
>
>Saturday, July 22, 2006, 8:03:28 PM, you wrote:
>
>
>
>>We are going to give changing the paradigm a try. The difference
>>between 4.1-beta and 4.0 is that different plugins are the default, and
>>the experimental code is in the plugins you see when mounting with the
>>mount option 4.1-beta. Let's see if it works in practice.....
>>
>>
>I Understand. This is good news. Hm, do you think that reiser4's pluggability
>is enough to have this single kernel tree (fs/reiser4) for a longer period
>of time.
>
Yes, reiser4 will have a much longer lifetime, and improvements will
come out in small pieces rather than complete rewrites. I think we can
add the enhanced semantics one feature at a time. It was the storage
layer that was the big thing that had to be right before the rest could
proceed. Now, what remains are a whole lot of incremental improvements
I hope. If I can make enough money off the repacker or I get funding
from France or some other government and we are able to afford to keep
vs and zam working on the storage layer, and Nate working on VFS
changes and Peter Foldiak and others at St. Andrews doing semantic
enhancements and Gorazd doing user space browsers things could get very
interesting..... We need to get into the kernel, and money will
manifest, and programmers can get to work....
> I mean, can you predict a need of spawning something like reiser5
>in the forseeable future or would fs/reiser4 + plugins be enough to do
>away with the "future vision" and other "future *" stuff you've written
>about ? eg. I remember reading about very granular security ACLs like
>restricting a certain line in a file (like /etc/passwd)
>
>
Yes, I still want to do that stuff....
Hans
next prev parent reply other threads:[~2006-07-23 6:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 15:32 future r4 maintenance question Pysiak Satriani
2006-07-22 18:03 ` Hans Reiser
2006-07-22 19:51 ` Maciej Sołtysiak
2006-07-22 20:16 ` David Masover
2006-07-22 21:26 ` Maciej Sołtysiak
2006-07-23 6:23 ` Hans Reiser
2006-07-23 6:07 ` Hans Reiser [this message]
2006-07-22 18:53 ` Mike Benoit
2006-07-22 19:12 ` Matthias Barremaecker
2006-07-22 19:42 ` David Masover
2006-07-23 11:11 ` Sander Sweers
2006-07-22 20:04 ` Maciej Sołtysiak
2006-07-22 19:32 ` David Masover
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=44C31233.9080800@namesys.com \
--to=reiser@namesys.com \
--cc=pysiak.satriani@wp.pl \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.