Reiser4 Plugin Developer Wiki

Reiser4 Plugin Developer Wiki

[Ryan Nordman]

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

The Weekend Warriors would like to announce the launch of the Reiser4
Programmer's Wiki at http://pvh.ca/trac/wiki/reiser4. We have included much
of the information we uncovered in the last four months, and we hope this
will continue to grow as more plugin developers join the effort to
understand, document and extend Reiser4. Your comments and contributions are
of course, most welcome.

Sadly, we must also note that it is unlikely we will be submitting a patch
for user-defined attributes any time soon. Our time has run out and we will
no longer be able to spend as much time working on the project.  We want to
thank all of you who helped us in our efforts.

-Ryan Nordman
Victoria, BC, Canada

[-- Attachment #2: Type: text/html, Size: 775 bytes --]

Re: Reiser4 Plugin Developer Wiki

[Hans Reiser]

Ryan Nordman wrote:

> The Weekend Warriors would like to announce the launch of the Reiser4
> Programmer's Wiki at http://pvh.ca/trac/wiki/reiser4. We have included
> much of the information we uncovered in the last four months, and we
> hope this will continue to grow as more plugin developers join the
> effort to understand, document and extend Reiser4. Your comments and
> contributions are of course, most welcome.
>
> Sadly, we must also note that it is unlikely we will be submitting a
> patch for user-defined attributes any time soon. Our time has run out
> and we will no longer be able to spend as much time working on the
> project.  We want to thank all of you who helped us in our efforts.
>
> -Ryan Nordman
> Victoria, BC, Canada

I am sorry that this turned out to be more work than your budget allowed
for, and I also regret that I think there was some deeper disagreement
over the appropriate fundamental semantics, as the discussion with Peter
Foldiak and I revealed.

Hans

Re: Reiser4 Plugin Developer Wiki

[Peter van Hardenberg]

On December 19, 2005 12:39 pm, Hans Reiser wrote:
> I am sorry that this turned out to be more work than your budget allowed
> for, and I also regret that I think there was some deeper disagreement
> over the appropriate fundamental semantics, as the discussion with Peter
> Foldiak and I revealed.
>
> Hans

Eh, we weren't being paid and we didn't have a customer, so we'll be alright 
in that regard. Still, I think the issue of user-defined attributes vs. 
file-as-dir still needs more work and I look forward to extending the debate 
some time.

Let us assume that I am wrong about keeping attributes in a separate @ 
directory and continue from there. Perhaps after the "resource fork" 
implementation is complete the case for more options might be clearer.

So, let us find a way to store standard files within files, as we can all 
agree on that!

$ ./myScript
Running myScript...
$ cd myScript; ls;
internal
file
contents
$

Our existing research is still very much valid, but I don't think a 
pseudo-plugin is the way to implement this. Perhaps the best way to handle 
the issue would be to write a new directory plugin?

Hans, I remember you described how you thought it would work in a sentence or 
two. Could you perhaps flesh out the idea to a paragraph or three? With that 
much guidance, I think we could go further without feeling like we are 
wasting effort.

-pvh

-- 
Peter van Hardenberg (pvh@pvh.ca)
Victoria, BC, Canada