From: Tobias Pflug <tobias.pflug@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: fs indexing/ querying on meta-data
Date: Tue, 07 Nov 2006 20:12:58 +0100 [thread overview]
Message-ID: <4550DABA.40600@gmx.net> (raw)
Hi everyone,
At university I am currently dealing with file indexing/query features
as they exist in the BeFS or SkyFS. In BeFS you could commit a query like:
(name == "*.c" || name == "*.h" ) && size > 20000
API functions were available to commit such queries which would use some
attribute b-tree to find matching files.
Now to get to the point: I would like to implement such functionality on
a very basic level (Only very simple queries) for a fs in the linux
kernel. I thought of parsing files in userland, extracting any usable
meta-data (such as id3 tags) and storing them as extended attributes of
the respective
files.
My problem is that I am not sure on which approach I should take on
this. Should I attempt to hack such functionality into an existing fs ?
If so, which one would be suited best? Maybe the much discussed
reiser4-plugin-interface could actually be useful for this one?
I also considered using FiST (http://www.am-utils.org/project-fist.html,
stackable filesystem language)
but the development seems to be stalled, I am having issues with
compilation, the author doesn't respond
and I read about people having major issues with it (segfaults etc..)
Finally there is the option of using FUSE, but I have to admit I haven't
had a closer look at it yet.
I hope this posting isn't so clueless&chaotic that people can't be
bothered to answer :) I'd be thankful
for any word of advice and/or pointers on this topic.
regards,
Tobi
PS: please CC to tobias.pflug@gmx.net , I am not subscribed to lkml.
Thank you!
next reply other threads:[~2006-11-07 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 19:12 Tobias Pflug [this message]
2006-11-15 19:23 ` fs indexing/ querying on meta-data Josef Sipek
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=4550DABA.40600@gmx.net \
--to=tobias.pflug@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/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.