Technical plugin details

Technical plugin details

[Peter van Hardenberg]

Hans,

I am having trouble modifying a file to use our new plugin. I've tried writing 
various values into "foo/.^4/plugin/file" but it won't stick. The code is 
rather sparse on comments in this part of the tree, and this is really 
something I would hope is documented somewhere.

Can you point me in the right direction?

-pvh

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

Re: Technical plugin details

[Hans Reiser]

Peter van Hardenberg wrote:

>Hans,
>
>I am having trouble modifying a file to use our new plugin. I've tried writing 
>various values into "foo/.^4/plugin/file" but it won't stick. The code is 
>rather sparse on comments in this part of the tree, and this is really 
>something I would hope is documented somewhere.
>
>Can you point me in the right direction?
>
>-pvh
>
>  
>
share your plugin code with vs, and he will comment on monday Russian time.

Re: Technical plugin details

[Edward Shishkin]

Peter van Hardenberg wrote:

>Hans,
>
>I am having trouble modifying a file to use our new plugin. I've tried writing 
>various values into "foo/.^4/plugin/file" but it won't stick.
>

This is a business of plugin->h.pops->change() method.
And for regular file plugin this method (change_file) does nothing.

> The code is 
>rather sparse on comments in this part of the tree, and this is really 
>something I would hope is documented somewhere.
>
>Can you point me in the right direction?
>
>-pvh
>
>  
>

Re: Technical plugin details

[Peter van Hardenberg]

On November 12, 2005 12:32 pm, you wrote:
> Peter van Hardenberg wrote:
> >Hans,
> >
> >I am having trouble modifying a file to use our new plugin. I've tried
> > writing various values into "foo/.^4/plugin/file" but it won't stick.
>
> This is a business of plugin->h.pops->change() method.
> And for regular file plugin this method (change_file) does nothing.
>

Thanks. That was exactly what we were trying to find. We did find it 
eventually, after experimenting with some other plugin types to determine 
what the problem was.

Of course, we are still trying to figure out how to actually create a file 
with a different file plugin. I guess I will have to read the reiser4("...") 
function as I can see no way to specify these things from a standard bash 
shell.

-pvh

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

Re: Technical plugin details

[Hans Reiser]

Peter van Hardenberg wrote:

>On November 12, 2005 12:32 pm, you wrote:
>  
>
>>Peter van Hardenberg wrote:
>>    
>>
>>>Hans,
>>>
>>>I am having trouble modifying a file to use our new plugin. I've tried
>>>writing various values into "foo/.^4/plugin/file" but it won't stick.
>>>      
>>>
>>This is a business of plugin->h.pops->change() method.
>>And for regular file plugin this method (change_file) does nothing.
>>
>>    
>>
>
>Thanks. That was exactly what we were trying to find. We did find it 
>eventually, after experimenting with some other plugin types to determine 
>what the problem was.
>
>Of course, we are still trying to figure out how to actually create a file 
>with a different file plugin. I guess I will have to read the reiser4("...") 
>function as I can see no way to specify these things from a standard bash 
>shell.
>
>-pvh
>
>  
>
If you want to document the learning process for plugins, we will be
happy to put it on the website.....

Re: Technical plugin details

[Edward Shishkin]

Peter van Hardenberg wrote:

>On November 12, 2005 12:32 pm, you wrote:
>  
>
>>Peter van Hardenberg wrote:
>>    
>>
>>>Hans,
>>>
>>>I am having trouble modifying a file to use our new plugin. I've tried
>>>writing various values into "foo/.^4/plugin/file" but it won't stick.
>>>      
>>>
>>This is a business of plugin->h.pops->change() method.
>>And for regular file plugin this method (change_file) does nothing.
>>
>>    
>>
>
>Thanks. That was exactly what we were trying to find. We did find it 
>eventually, after experimenting with some other plugin types to determine 
>what the problem was.
>
>Of course, we are still trying to figure out how to actually create a file 
>with a different file plugin.
>

You can write to "..../plugin/regular" of parent directory: this is a
place where reiser4_create (*) looks for a file plugin of target child,
just add a new plugin id of REISER4_REGULAR_PLUGIN_TYPE for your files.
However, this interface is not finally approved and can be changed.
Hans, is it okay, or..?

(*) in the latest versions of reiser4 this is a plugin->inode_ops->create()
(create_common)

Edward.

> I guess I will have to read the reiser4("...") 
>function as I can see no way to specify these things from a standard bash 
>shell.
>
>-pvh
>
>  
>