linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Diego ." <eljedi@gmail.com>
To: "Andreas Dilger" <adilger@sun.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: BeFS
Date: Mon, 21 Jul 2008 08:51:49 +0200	[thread overview]
Message-ID: <530d01580807202351v36c6e47g4442205c963e5a0a@mail.gmail.com> (raw)
In-Reply-To: <20080721050510.GC3370@webber.adilger.int>

Hi!

thanks for all the info!!
I'm gonna start reading now!

thanks again,
Diego.



On Mon, Jul 21, 2008 at 7:05 AM, Andreas Dilger <adilger@sun.com> wrote:
> On Jul 18, 2008  10:10 +0200, Diego . wrote:
>> Can you point me to some web where i can get updated info about
>> fsdevel in general? ( kernel apis.. etc..)
>
> Reading linux/Documentation/filesystems/vfs.txt is a good start, along
> with other documents there.  Maybe kernenewbies has some wiki pages also.
>
>> On Thu, Jul 17, 2008 at 11:12 PM, Andreas Dilger <adilger@sun.com> wrote:
>> > On Jul 17, 2008  13:55 +0200, Diego . wrote:
>> >> My question comes when i tried to finish befs port ( write mode ) on
>> >> the kernel sources..
>> >> How can i make the extensible attributes and live queries available to
>> >> linux user/programs?
>> >>
>> >> Is there some way to register this services?
>> >
>> > I'm guessing that xattrs (via sys_{get,set,list}xattr(), used by
>> > user tools getfattr/setfattr/libattr) will get you much of what you
>> > want.
>> >
>> > In order to notify applications about "live queries" you may want to
>> > look at the dnotify or inotify mechanisms, having an application
>> > get a notification on a "virtual search" file, or similar.
>
> Cheers, Andreas
> --
> Andreas Dilger
> Sr. Staff Engineer, Lustre Group
> Sun Microsystems of Canada, Inc.
>
>

      reply	other threads:[~2008-07-21  6:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 11:55 BeFS Diego .
2008-07-17 12:30 ` BeFS Matthew Wilcox
2008-07-17 21:12 ` BeFS Andreas Dilger
2008-07-18  8:10   ` BeFS Diego .
2008-07-18 13:43     ` BeFS Leandro Dorileo
2008-07-21  5:05     ` BeFS Andreas Dilger
2008-07-21  6:51       ` Diego . [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=530d01580807202351v36c6e47g4442205c963e5a0a@mail.gmail.com \
    --to=eljedi@gmail.com \
    --cc=adilger@sun.com \
    --cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).