On Sun, Dec 05, 2004 at 04:17:36PM -0300, Avi Alkalay wrote:
On Sun, 05 Dec 2004 12:57:30 -0500, Sean Middleditch
> Avi Alkalay wrote:
> >I'm having a look at inotify, which is the basis for gamin.
> Don't tie your code to inotify, tie it to something like gamin. Gamin
> can abstract away the different OS interfaces, so that machines without
> inotify will still have some form of notification (dnotify, polling,
> whatever). There's no good reason to reimplement that code yourself.
Yeah I know.... I'll try to stick in the high level, but I'm worried
about dependencies. It makes no sense to have /lib/libkdb.so depending
on libs under /usr/lib.
The 5 minutes I spent reading about inotify made me believe it is a
kernel module, but I couldn't find it, nor the /dev entry, nor the
dmesg messages in the FC2 machine I have close to me right now. Is
this stuff already included in regular distros kernels ?
Use gamin. If inotify is present it will use it, if not it will fallback
to whatever is available. And if you're on Solaris, you can still use FAM
to provide the equivalent API as gamin.
And gamin only dependancy on the client side is libc, you really have no
excuse to not use it :-)
Daniel Veillard | Red Hat Desktop team http://redhat.com/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
| Rpmfind RPM search engine http://rpmfind.net/