All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Peter van Hardenberg <pvh@uvic.ca>
Cc: reiserfs-list@namesys.com
Subject: Re: Implementing an attribute directory.
Date: Sun, 20 Nov 2005 23:47:05 -0800	[thread overview]
Message-ID: <43817B79.6010707@namesys.com> (raw)
In-Reply-To: <200511201317.12598.pvh@uvic.ca>

Peter van Hardenberg wrote:

>We have an implementation plan for the attribute plugin. We plan to base it 
>around the plugin.c so that it can be available for all files, directory or 
>otherwise.
>
>Every file which has a pseudo will gain a new user-attributes pseudofile. This 
>pseudofile will essentially wrap a standard directory. 
>
Usage examples please.

>In order to provide 
>support for this directory, this plugin will include a new field on the inode 
>which points to a standard dir_file.
>
>When a new file is created, this inode will be created as well, and when a 
>file is deleted, this one must be removed (with children) as well. Future 
>versions should provide the optimization of only creating the inode once it 
>becomes needed and otherwise simulating an empty directory.
>
>Namesys folks, does this seem like a good course of action?
>
>-pvh
>
>  
>


  reply	other threads:[~2005-11-21  7:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20 21:17 Implementing an attribute directory Peter van Hardenberg
2005-11-21  7:47 ` Hans Reiser [this message]
2005-11-23  8:57   ` Two usage examples for attribute directories Peter van Hardenberg
2005-12-03  0:25     ` Peter Foldiak
2005-12-03  0:49       ` Peter van Hardenberg
2005-12-03 10:54         ` Peter Foldiak
2005-12-04  7:04           ` Hans Reiser
2005-12-04 15:04           ` Alexander G. M. Smith
2005-12-05  4:27           ` Peter van Hardenberg
2005-12-08 14:12             ` Peter Foldiak
2005-12-08 20:40               ` Hubert Chan
2005-12-10  1:11                 ` Nate Diller
2005-12-10  1:46                   ` Hans Reiser
2005-12-10  3:11                   ` Hubert Chan
2005-12-09  8:25               ` Hans Reiser

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=43817B79.6010707@namesys.com \
    --to=reiser@namesys.com \
    --cc=pvh@uvic.ca \
    --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.