From: Marc Perkel <marc@perkel.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Jeff Mahoney <jeffm@suse.com>, Reiserfs List <reiserfs-list@namesys.com>
Subject: Re: WinFS beta out
Date: Wed, 31 Aug 2005 13:35:16 -0700 [thread overview]
Message-ID: <43161484.7080501@perkel.com> (raw)
In-Reply-To: <43160D8A.7010006@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 1753 bytes --]
Hans Reiser wrote:
>Jeff Mahoney wrote
>
>
>
>>The current implementation is hardly what I had envisioned ACLs and
>>xattrs being on reiserfs -- but was the only solution we could find to
>>still allow the filesystem to be mounted on an earlier kernel.
>>
>>An ideal solution would have been to introduce reiserfs v3.7 with a new
>>magic, and add feature versioning to the superblock, similar to the way
>>ext[23] does it. I felt that would have been met with much, much more
>>resistance than the implementation I ultimately presented.
>>
>>
>
>I understand that you meant well, and we just honestly disagree about
>when to code freeze a stable release and put all the new stuff in the
>next release. I would never release code that dramatically reduces
>performance to the point of eliciting the remarks in this thread by the
>users, and that too is an honest disagreement. I was offered money by
>more than one entity to do the design you did, and refused the money.
>
>All of what you wish you could have done differently is easily done in
>reiser4 because of plugins, and acls in reiser4 will happen when someone
>offers money (and they will, I am sure of it).
>
>
>
I have to question the decision to freeze existing code when the new
code isn't finished. For what it's worth I've switched to EXT3 because I
want ACLs. I hope to come back to ReiserFS some day but right now it
just doesn't have the features I need now. Abandoning Reiser 3 is going
to end up losing you part of market share because EXT3 has made a lot of
advances.
I'm still a fan and looking forward to Reiser 4. Just not sure what I
can do to help. I'll offer you free spam filterinf Hans if that hels a
little. I have the best spam filter on the planet.
[-- Attachment #2: Type: text/html, Size: 2164 bytes --]
next prev parent reply other threads:[~2005-08-31 20:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 4:36 WinFS beta out Gregory Maxwell
2005-08-30 5:42 ` Jake Maciejewski
2005-08-30 6:35 ` Hans Reiser
2005-08-30 13:39 ` LiFe
2005-08-30 15:45 ` Marc Perkel
2005-08-30 22:10 ` Lexington Luthor
2005-08-30 23:00 ` Christian Iversen
2005-08-31 1:06 ` Hans Reiser
2005-08-31 1:18 ` Christian Iversen
2005-08-31 10:44 ` LiFe
2005-08-31 13:45 ` michael chang
2005-09-01 8:24 ` LiFe
[not found] ` <b14e81f0050901070453f4d898@mail.gmail.com>
2005-09-01 14:04 ` michael chang
2005-08-31 0:59 ` Hans Reiser
2005-08-31 4:59 ` Marc Perkel
2005-08-31 5:46 ` David Masover
2005-08-31 7:13 ` Hans Reiser
2005-08-31 13:44 ` michael chang
2005-08-31 14:36 ` Fundind Reiser Development Marc Perkel
2005-08-31 19:54 ` Hans Reiser
2005-08-31 14:38 ` Funding " Marc Perkel
2005-08-31 21:44 ` WinFS beta out Hans Reiser
2005-08-31 14:32 ` Marc Perkel
2005-08-31 16:01 ` Jeff Mahoney
2005-08-31 17:32 ` changing label of disk Bedros Hanounik
2005-08-31 18:15 ` evilninja
2005-08-31 20:05 ` WinFS beta out Hans Reiser
2005-08-31 20:35 ` Marc Perkel [this message]
2005-08-31 17:45 ` Adrian Ulrich
[not found] ` <b14e81f00508301124ebf9ab9@mail.gmail.com>
2005-08-31 2:02 ` michael chang
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=43161484.7080501@perkel.com \
--to=marc@perkel.com \
--cc=jeffm@suse.com \
--cc=reiser@namesys.com \
--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.