mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Robert Love <rml@novell.com>
Cc: Timothy Chavez <chavezt@gmail.com>,
	Chris Wright <chrisw@osdl.org>,
	linux-kernel@vger.kernel.org, sds@epoch.ncsc.mil,
	ttb@tentacle.dhs.org
Subject: Re: [audit] Upstream solution for auditing file system objects
Date: Thu, 9 Dec 2004 20:59:14 -0800	[thread overview]
Message-ID: <20041209205914.A2357@build.pdx.osdl.net> (raw)
In-Reply-To: <1102650138.6052.228.camel@localhost>; from rml@novell.com on Thu, Dec 09, 2004 at 10:42:18PM -0500

* Robert Love (rml@novell.com) wrote:
> What we both need, ultimately, is a generic file change notification
> system.  This way inotify, dnotify, your audit thing, and whatever else
> can hook into the filesystem as desired.

Yup, makes sense.  From my handwavy perspective inotify was the generic
file event notifcation mechanism, but I agree with your point.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  parent reply	other threads:[~2004-12-10  4:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10  0:02 Timothy Chavez
2004-12-10  1:46 ` Chris Wright
2004-12-10  2:50   ` Timothy Chavez
2004-12-10  3:42     ` Robert Love
2004-12-10  4:38       ` Timothy Chavez
2004-12-10  4:45         ` Robert Love
2004-12-10  4:59       ` Chris Wright [this message]
2004-12-10  5:22       ` John McCutchan
2004-12-10  7:36   ` Jan Engelhardt
2004-12-10  2:28 ` James Morris
2004-12-10  5:41 ` John McCutchan
2004-12-10 13:00 ` Paul Rolland
2004-12-10 14:29 ` Valdis.Kletnieks
2004-12-10 16:35   ` Timothy Chavez

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=20041209205914.A2357@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=chavezt@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.com \
    --cc=sds@epoch.ncsc.mil \
    --cc=ttb@tentacle.dhs.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

Powered by JetHome