From: Dave Jones <davej@redhat.com>
To: Michael Clark <michael@metaparadigm.com>
Cc: rudi@lambda-computing.de, ivern@acm.org, linux-kernel@vger.kernel.org
Subject: Re: File change notification
Date: Thu, 1 Jan 2004 01:58:09 +0000 [thread overview]
Message-ID: <20040101015809.GA14930@redhat.com> (raw)
In-Reply-To: <3FF377A8.6040302@metaparadigm.com>
On Thu, Jan 01, 2004 at 09:28:08AM +0800, Michael Clark wrote:
> Have you had a look at dazuko. It provides a consistent file access
> notification mechanism (and also intervention for denying access) across
> linux and freebsd. It is currently being used by various on-access
> virus scanners. It is under active development and supports 2.6 (and 2.4)
Candidate for "Wackiest sys_call_table patching 2004".
In a word "ick". Code not to be read on a full stomach.
Dave
--
Dave Jones http://www.codemonkey.org.uk
next prev parent reply other threads:[~2004-01-01 1:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 16:42 File change notification Rüdiger Klaehn
2003-12-31 18:20 ` Javier Fernandez-Ivern
2003-12-31 18:48 ` Rüdiger Klaehn
2004-01-01 1:28 ` Michael Clark
2004-01-01 1:58 ` Dave Jones [this message]
2004-01-01 2:18 ` Michael Clark
2004-01-01 2:30 ` Javier Fernandez-Ivern
2004-01-01 13:11 ` Rüdiger Klaehn
2003-12-31 20:49 ` Javier Fernandez-Ivern
2004-01-01 9:02 ` Juergen Hasch
2004-01-01 10:47 ` jw schultz
2004-01-01 12:44 ` Rüdiger Klaehn
2004-01-03 6:32 ` Jan Harkes
-- strict thread matches above, loose matches on Subject: below --
2004-02-07 8:29 John Ogness
2004-02-07 14:01 ` Christoph Hellwig
[not found] <18PG9-4og-27@gated-at.bofh.it>
[not found] ` <18TgF-QJ-7@gated-at.bofh.it>
[not found] ` <18TJE-1qL-3@gated-at.bofh.it>
2003-12-31 19:30 ` René Scharfe
2002-11-01 21:31 file " Colin Burnett
2002-11-01 22:19 ` Chris Wright
2002-11-02 15:43 ` Jamie Lokier
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=20040101015809.GA14930@redhat.com \
--to=davej@redhat.com \
--cc=ivern@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@metaparadigm.com \
--cc=rudi@lambda-computing.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.