-----Original Message-----
From: Greg KH [mailto:greg@kroah.com]
Sent: Tuesday, August 05, 2008 2:39 PM
To: Press, Jonathan
Cc: Arjan van de Ven; Eric Paris; linux-kernel@vger.kernel.org;
malware-list@lists.printk.net; linux-security-module@vger.kernel.org
Subject: Re: [malware-list] [RFC 0/5] [TALPA] Intro to a
linuxinterfaceforon access scanning
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
On Tue, Aug 05, 2008 at 02:34:26PM -0400, Press, Jonathan wrote:
a
thread.
register
That's an implementation issue, not a requirement. If it's a
requirement, it sure is a lazy one :)
[JON PRESS] I wouldn't call it lazy, actually. It's more like
"economical" or "ergonomic" -- or, dare I say it -- "user-friendly." In
this case, the users are the AV vendors who will have to write to the
API that will come out of this spec. We will be more inclined to
appreciate the SDK (for want of a better term) if it covers all the
bases, rather than force us to go elsewhere for some of our
requirements. When we write SDKs, we try to make sure that our users
will find whatever they need.
It
at.
So, if you hook glibc to catch all calls to close, is that sufficient?
[JON PRESS] Let's see...I'm going to use inotify for some events, glibc
for others, and this API for the rest. Would you really want to write
an application like that?
--
