mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeroen van Disseldorp <jdizzl@xs4all.nl>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Detecting changes in a directory tree
Date: Thu, 16 Jan 2003 22:54:22 -0500	[thread overview]
Message-ID: <200301162254.22870.jdizzl@xs4all.nl> (raw)
In-Reply-To: <20030117005941.GT2333@fs.tum.de>

On Thursday 16 January 2003 19:59, Adrian Bunk wrote:
> with a kernel >= 2.4.19 dnotify [1] might do what you want.

Close, but is doesn't do it quite for me. I understand the problem of 
traversing inodes back up the tree, once they have changed, to see 
whether someone wants to receive an event. However I am not convinced 
that this is necessary. The idea I had was the following:

I would like to have a passthrough kind of filesystem (lets call is myfs 
for now) that can mount other parts of the filesystem and just maps 
everything to the original tree. For instance, I would mount /var on 
/mnt/var, using myfs. Everything from /mnt/var is directly mapped to 
/var.

The clue of this is that myfs *knows* about the notification, because it 
has to send notification to userspace for *every* inode. So if anything 
is written in /mnt/var, it can notify userspace. BTW for my app it 
would be acceptable that direct changes in /var don't lead to any 
events.

I haven't thought out the interface to userspace yet, but I think that 
can be worked out. Let me know if I'm making any sense here.

Regards,
  Jeroen                           mailto:jdizzl@xs4all.nl
-- 
Be the change that you want to see in the world    -- Gandhi

  reply	other threads:[~2003-01-17  3:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-16 18:58 Jeroen van Disseldorp
2003-01-17  0:59 ` Adrian Bunk
2003-01-17  3:54   ` Jeroen van Disseldorp [this message]
2003-01-17 12:58 Jon Burgess

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=200301162254.22870.jdizzl@xs4all.nl \
    --to=jdizzl@xs4all.nl \
    --cc=bunk@fs.tum.de \
    --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

all inboxes | Powered by JetHome®