All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Jeffrey Yasskin <jyasskin@mail.utexas.edu>
Cc: reiserfs-list@namesys.com
Subject: Re: Where are the plugins?
Date: Wed, 03 Sep 2003 02:19:44 +0400	[thread overview]
Message-ID: <3F551780.1030701@namesys.com> (raw)
In-Reply-To: <3F51080F.7060901@mail.utexas.edu>

Jeffrey Yasskin wrote:

> I've been looking at the reiser4 source code for a few days, and I 
> can't find any non-essential plugins. 

This is called the minimal functionality for first release project 
management style. ;-)

>
>
> For example: You say on the website that you've written several 
> security plugins for DARPA,

oh dear, if you send nikita (offlist) the lines he'll correct them.

> but the only files in fs/reiser4/plugin/security/ are acl.c and 
> perm.{c,h}, and acl.c is empty.
> On the website you also suggest writing a plugin so /etc/passwd can be 
> split in to individually-permissioned sub-files. Is that plugin 
> written yet, or is it just an idea? 

Umh, it is in our contract, so that makes it more than an idea;-), 
however the person working on file inheritance got put on encryption and 
hasn't finished that yet.  There exists some code somewhere that I need 
to review and....

>
>
> I'd like to write a few plugins to move mp3s' and oggs' meta-data into 
> the filesystem, and it'd be a lot easier if there were an example to 
> copy from. (Would it be better just to move that kind of plugin into a 
> userspace callback?)
>
> Thanks,
> Jeffrey
>
>
>
I agree that we need examples..... and more plugins.....;-)

-- 
Hans



      parent reply	other threads:[~2003-09-02 22:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-30 20:24 Where are the plugins? Jeffrey Yasskin
2003-09-02 11:54 ` Alexander Lyamin
2003-09-02 12:54 ` Nikita Danilov
2003-09-02 22:19 ` Hans Reiser [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=3F551780.1030701@namesys.com \
    --to=reiser@namesys.com \
    --cc=jyasskin@mail.utexas.edu \
    --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.