From: Nicholas Miell <nmiell@gmail.com>
To: Robert Love <rml@novell.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Bill Davidsen <davidsen@tmr.com>, Jan Kara <jack@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH] inotify 0.9
Date: Thu, 16 Sep 2004 20:08:20 -0700 [thread overview]
Message-ID: <1095390499.2878.2.camel@entropy> (raw)
In-Reply-To: <1095388176.20763.29.camel@localhost>
On Thu, 2004-09-16 at 19:29, Robert Love wrote:
> I think we want a solution that works well for both cases.
>
> E.g., we have a few different needs:
>
> - Stuff like Spotlight-esque automatic Indexers.
> - File manager notifications
> - Other GUI notifications (desktop, menus, etc.)
> - To prevent polling (e.g. /proc/mtab)
> - Existing dnotify users
>
> dnotify is pretty lame for any of the above situations. Even for
> something as trivial as watching the current open directory in Nautilus,
> look at the hoops we have to just through with FAM.
>
> And dnotify utterly falls apart on removable media or for any "large"
> sort of job, e.g. indexing.
Isn't this the problem that XDSM/DMAPI is supposed to solve? Or is that
one of those specs that's too ugly to be implemented?
next prev parent reply other threads:[~2004-09-17 3:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 15:52 [RFC][PATCH] inotify 0.9 John McCutchan
2004-09-15 18:00 ` Robert Love
2004-09-16 15:07 ` Bill Davidsen
2004-09-16 16:27 ` Chris Friesen
2004-09-16 22:48 ` Bill Davidsen
2004-09-16 16:39 ` Robert Love
2004-09-20 20:16 ` Bill Davidsen
2004-09-20 21:05 ` Robert Love
2004-09-20 22:59 ` Bill Davidsen
2004-09-21 0:02 ` Robert Love
2004-09-16 16:46 ` Jan Kara
2004-09-16 22:34 ` Bill Davidsen
2004-09-16 22:57 ` David Lang
2004-09-16 23:22 ` Robert Love
2004-09-16 23:35 ` Alan Cox
2004-09-17 2:29 ` Robert Love
2004-09-17 3:08 ` Nicholas Miell [this message]
2004-09-17 14:39 ` Alan Cox
2004-09-17 15:48 ` Robert Love
2004-09-17 14:51 ` Alan Cox
2004-09-17 15:55 ` Robert Love
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=1095390499.2878.2.camel@entropy \
--to=nmiell@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
/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