All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Zarochentsev <zam@namesys.com>
To: reiserfs-list@namesys.com
Cc: Yoanis Gil Delgado <fred@uh.cu>
Subject: Re: Questions about pseudo plugins
Date: Fri, 31 Mar 2006 23:30:44 +0400	[thread overview]
Message-ID: <200603312330.44519.zam@namesys.com> (raw)
In-Reply-To: <442C3900.1060808@uh.cu>

Hello

On Friday 31 March 2006 00:01, Yoanis Gil Delgado wrote:
> Hi there:
> I've been working on the versioning plugin.
> I will like to know how can i add a pseudo file to a pseudo
> directory, dynamically. I mean whenever i detect a new version i want
> to create a pseudo file under /file.txt/versioning/version/s pseudo
> directory. Another question is about how can I iterate over
> directories pseudo files. 

IFAIK you need to define lookup and readdir methods for your pseudo 
plugins.

Unfortunately it is very low level API for exporting your dynamic 
structures.  Some API like procfs/sysctl would be much better but 
reiser4 does not have it yet.

> For example how i can iterate over the 
> files under
> /file.txt/versioning/version/s (remember the files under this
> directory are pseudo files which are generated dynamically).
> I know there is a way to add static pseudo files and directories, by
> adding them to pseudo_plugins array. Perhaps using the linkage field
> from pseudo_plugin. I've some more questions but i will come later
> with them.
> By the way I found this in the patch for kernel 2.6.15:
>     The function init_pseudo receives a _/const char* name  /_which
> is never used.
> That's all for now. Thanks a lot .............. yoanis

-- 
Alex.

      parent reply	other threads:[~2006-03-31 19:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-30 20:01 Questions about pseudo plugins Yoanis Gil Delgado
2006-03-30 21:16 ` Hans Reiser
2006-03-31 19:30 ` Alexander Zarochentsev [this message]

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=200603312330.44519.zam@namesys.com \
    --to=zam@namesys.com \
    --cc=fred@uh.cu \
    --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.