From: Martin Rode <martin.rode@programmfabrik.de>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Callbacks to userspace from VFS ?
Date: 17 Apr 2002 16:40:27 +0200 [thread overview]
Message-ID: <1019054427.8745.114.camel@marge> (raw)
In-Reply-To: <15549.34936.502136.339319@laputa.namesys.com>
Hi Nikita,
I did not look deeper into F_NOTIFY, but if I only get a SIGNAL I don't
know _what_ has happened (or better on what file something has
happened). But to process the new / updated files I need the filename.
If I only learn which directory was updated I still have to find out
_which_ file is new or was changed.
Regards,
;Martin
--
Dipl.-Kfm. Martin Rode
Managing Director
martin.rode@programmfabrik.de
Programmfabrik GmbH Fon +49-(0)30-4281-8001
Frankfurter Allee 73d Fax +49-(0)30-4281-8008
10247 Berlin Funk +49-(0)163-5321400
http://www.programmfabrik.de/
next prev parent reply other threads:[~2002-04-17 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 14:21 Callbacks to userspace from VFS ? Martin Rode
[not found] ` <15549.34936.502136.339319@laputa.namesys.com>
2002-04-17 14:40 ` Martin Rode [this message]
2002-04-17 17:09 ` Jamie Lokier
2002-04-17 14:45 ` Alex Riesen
2002-04-18 1:22 ` Keith Owens
2002-04-18 14:10 ` Michael Clark
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=1019054427.8745.114.camel@marge \
--to=martin.rode@programmfabrik.de \
--cc=Nikita@Namesys.COM \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox