From: Linda Knippers <linda.knippers@hp.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: RFC deprecating the possible action
Date: Mon, 10 Apr 2006 15:55:02 -0400 [thread overview]
Message-ID: <443AB816.7010505@hp.com> (raw)
In-Reply-To: <200604101505.57763.sgrubb@redhat.com>
Steve Grubb wrote:
> We currently have 5 syscall rules in the capp.rules file and lspp.rules file
> that would be eliminated by this change. I could always delete them from the
> rule file, but other people will make the mistake of setting possible on some
> rules without studying the kernel code.
>
> What's people's thoughts on this?
I think if 'possible' no longer is needed, let's remove it. The only
reason I can think of for keeping it is if people want to have the
same rules file for RHEL4 as for RHEL5, in which case it could be
silently ignored or turned into a regular watch on a RHEL5 system.
- ljk
prev parent reply other threads:[~2006-04-10 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 19:05 RFC deprecating the possible action Steve Grubb
2006-04-10 19:55 ` Linda Knippers [this message]
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=443AB816.7010505@hp.com \
--to=linda.knippers@hp.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@redhat.com \
/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