From: Jamie Lokier <jamie@shareable.org>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Daniel Phillips <phillips@phunq.net>,
tux3@tux3.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Tux3] Tux3 report: A Golden Copy
Date: Sun, 4 Jan 2009 03:17:33 +0000 [thread overview]
Message-ID: <20090104031733.GB20929@shareable.org> (raw)
In-Reply-To: <495EDE04.5080703@gmail.com>
Justin P. Mattock wrote:
> Thats some crazy stuff!! and just think most of it is
> simply magnets.(but more complicated than that)
> >One feature we are kicking around to make life easier for SELinux:
> >sometimes the filesystem can run while SELinux is not running, and
> >security labels will be wrong when SELinux re-enters the picture. We
> >have in mind to provide a persistent log of filesystem events that the
> >security system can attach to on startup and find out what went on in
> >its absence.
> >
> >
> That sounds nice:
>
> find out what went on in
> its absence.
That sounds like a feature Windows had for many years now, (since
Windows 2000?). It complements the Windows equivlant of
dnotify/inotify/fsnotify.
It's used for file indexing too (think equivalent to Spotlight,
Beagle, etc.), and other types of security scanning (think equivalent
to Tripwire).
I wonder why the people writing file indexing tools for Linux never
made a fuss about this. Inotify is ok for indexing, but means quite a
few minutes of intensive disk activity after each boot to rescan /home.
-- Jamie
next prev parent reply other threads:[~2009-01-04 3:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 3:35 Tux3 report: A Golden Copy Daniel Phillips
2008-12-31 7:34 ` sniper
2008-12-31 8:00 ` [Tux3] " Daniel Phillips
2008-12-31 8:14 ` Justin P. Mattock
2008-12-31 10:09 ` Martin Steigerwald
2008-12-31 17:41 ` Justin P. Mattock
2009-01-02 20:17 ` Martin Steigerwald
2009-01-02 20:36 ` Justin P. Mattock
2009-01-02 22:45 ` Daniel Phillips
2009-01-02 23:11 ` Justin P. Mattock
2009-01-03 1:19 ` Daniel Phillips
2009-01-03 1:32 ` Justin P. Mattock
2009-01-03 3:03 ` Daniel Phillips
2009-01-03 3:39 ` Justin P. Mattock
2009-01-04 3:17 ` Jamie Lokier [this message]
2009-01-04 4:15 ` Daniel Phillips
2009-01-04 4:29 ` Justin P. Mattock
2009-01-04 13:04 ` Theodore Tso
2009-01-05 1:10 ` Daniel Phillips
2009-01-05 2:13 ` Jamie Lokier
2009-01-08 2:50 ` Daniel Phillips
2009-01-08 4:38 ` Evgeniy Polyakov
2008-12-31 8:16 ` sniper
2008-12-31 8:31 ` Dave Chinner
2008-12-31 9:40 ` Daniel Phillips
2008-12-31 14:26 ` Andi Kleen
2008-12-31 18:14 ` sniper
2008-12-31 18:18 ` sniper
2009-01-01 9:56 ` Daniel Phillips
2009-01-01 14:46 ` Daniel Phillips
2009-01-01 23:58 ` Dave Chinner
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=20090104031733.GB20929@shareable.org \
--to=jamie@shareable.org \
--cc=justinmattock@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@phunq.net \
--cc=tux3@tux3.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