All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Briggs <jbriggs@esoft.com>
To: Hubert Chan <hubert@uhoreg.ca>
Cc: Reiserfs mail-list <Reiserfs-List@namesys.com>
Subject: Re: another semantic storage system (in userspace)
Date: Thu, 13 Jul 2006 18:23:20 -0600	[thread overview]
Message-ID: <1152836600.6894.12.camel@localhost> (raw)
In-Reply-To: <87veq1z1qc.fsf@evinrude.uhoreg.ca>

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

On Thu, 2006-07-13 at 16:30 -0400, Hubert Chan wrote:
> On Thu, 13 Jul 2006 10:38:23 -0700, Hans Reiser <reiser@namesys.com> said:
> 
> > Clay Barnes wrote:
> 
> >> 1) Scope
> >> a) Should the semantic content of files be purely user-defined?
> 
> > Yes.
> 
> I guess this also raises the question of how multiple users on the same
> machine can define their own semantic content (e.g. if user A wants to
> index some new file format, but doesn't want to have to bug the
> administrator to add support for it).  Will the filesystem be talking to
> some userspace daemons?

I was thinking that the file system should only index its own meta-data
attributes.  A user-space daemon should read the file contents and
create these attributes.

Search directories would display selected parts of the indexes.  One of
these that would be highly useful for a user-space indexing daemon is a
timestamp search directory.  The indexer would begin with the timestamp
search set to (UID == my user and timestamp > 0).  After indexing a few
files it would update the search to (my user and > timestamp of last
indexed file).  Or possibly, if Reiser4 has something like a 64-bit
monotonic update ID, it could use that instead of a timestamp.

If the filesystem indexes are not going to be updated in real-time but
only at specific times, another search type that could list updated but
not yet indexed files would also be useful.
-- 
Jonathan Briggs <jbriggs@esoft.com>
eSoft, Inc.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-07-14  0:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-12 21:44 another semantic storage system (in userspace) Hubert Chan
2006-07-12 23:22 ` Clay Barnes
2006-07-13  7:30   ` Hans Reiser
2006-07-13 17:06 ` Clay Barnes
2006-07-13 17:38   ` Hans Reiser
2006-07-13 20:30     ` Hubert Chan
2006-07-14  0:23       ` Jonathan Briggs [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=1152836600.6894.12.camel@localhost \
    --to=jbriggs@esoft.com \
    --cc=Reiserfs-List@namesys.com \
    --cc=hubert@uhoreg.ca \
    /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.