public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John McCutchan <ttb@tentacle.dhs.org>
To: Martin Schlemmer <azarah@nosferatu.za.org>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
	nautilus-list@gnome.org
Subject: Re: [PATCH] inotify 0.5
Date: Sun, 18 Jul 2004 16:22:12 -0400	[thread overview]
Message-ID: <1090182131.9290.2.camel@vertex> (raw)
In-Reply-To: <1090181465.5281.41.camel@nosferatu.lan>

On Sun, 2004-07-18 at 16:11, Martin Schlemmer wrote:
> 
> Right, but kde also works with fam, and I assume the gamin support
> will only be in 2.[78] gnome-vfs?  Also, it would be nice to test
> currently with fam enabled stuff, as I want to remember inotify
> do not have issues with locking mounts like dnotify have?  Or is
> it rather a fam-related issue ?

Gamin is a API/ABI stable replacement for FAM. Just dropping in gamin
instead of fam should just work with all current software. Inotify does
not have the umount blocking problem. In fact it lets FAM/Gamin no that
a particular directory has been unmounted and is no longer available.
This will let konquerer/nautilus provide more user friendly clues to
users. 

John

  reply	other threads:[~2004-07-18 20:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-18 19:49 [PATCH] inotify 0.5 John McCutchan
2004-07-18 19:53 ` Martin Schlemmer
2004-07-18 20:02   ` John McCutchan
2004-07-18 20:11     ` Martin Schlemmer
2004-07-18 20:22       ` John McCutchan [this message]
2004-07-18 23:37 ` Davide Libenzi
2004-07-19  1:42   ` John McCutchan
2004-07-19  8:43     ` Ian Kent
2004-07-19 13:33       ` Chris Friesen
2004-07-19 21:31         ` John McCutchan
2004-07-20  2:59           ` Eric Lammerts
2004-07-20  3:24             ` John McCutchan
2004-07-20  1:33         ` Ian Kent
2004-07-19  3:37 ` Daniel Veillard

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=1090182131.9290.2.camel@vertex \
    --to=ttb@tentacle.dhs.org \
    --cc=azarah@nosferatu.za.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nautilus-list@gnome.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