atom feed17 messages in org.freebsd.trustedbsd-auditHEADS UP: Audit integration into CVS ...
FromSent OnAttachments
Robert WatsonFeb 1, 2006 10:15 pm 
Kövesdán GáborFeb 1, 2006 10:22 pm 
Julian ElischerFeb 1, 2006 10:32 pm 
Robert WatsonFeb 1, 2006 10:32 pm 
Robert WatsonFeb 1, 2006 10:55 pm 
Mike JakubikFeb 2, 2006 12:03 am 
Robert WatsonFeb 2, 2006 12:35 am 
Kris KennawayFeb 2, 2006 12:40 am 
Robert WatsonFeb 2, 2006 12:50 am 
Mike JakubikFeb 2, 2006 12:54 am 
Kris KennawayFeb 2, 2006 12:57 am 
Robert WatsonFeb 2, 2006 1:17 am 
Tom RhodesFeb 2, 2006 2:13 am 
Mike JakubikFeb 2, 2006 3:15 am 
Peter JeremyFeb 2, 2006 9:02 am 
Doug BartonFeb 3, 2006 1:19 am 
Robert WatsonFeb 3, 2006 3:52 pm 
Subject:HEADS UP: Audit integration into CVS in progress, some tree disruption
From:Tom Rhodes (trho@FreeBSD.org)
Date:Feb 2, 2006 2:13:37 am
List:org.freebsd.trustedbsd-audit

On Thu, 2 Feb 2006 01:17:47 +0000 (GMT) Robert Watson <rwat@FreeBSD.org> wrote:

On Wed, 1 Feb 2006, Mike Jakubik wrote:

Kris Kennaway wrote:

On Wed, Feb 01, 2006 at 07:03:31PM -0500, Mike Jakubik wrote:

Personally, i would like to see less "experimental" code in 6.1. Perhaps it would be better to wait until everyone feels the code is ready?

Why do you care if code that is not enabled by default is present in the system? :-)

Well... While you, me, and other viewers of this list may be fully aware of the situation, some else who is either new to FreeBSD or missed out on this info may try it and possibly be disappointed. Which would ruin their experience and/or opinion of FreeBSD in general. I guess if it does make it in, it would be a good idea to clearly notify the user that it is still experimental, etc..

In the past, we've marked features as experimental using a man page note, e.g., in the mac(4) man page:

NAME mac -- Mandatory Access Control

SYNOPSIS options MAC

...

BUGS See mac(9) concerning appropriateness for production use. The TrustedBSD MAC Framework is considered experimental in FreeBSD.

And as such in the release notes. However, maybe we could add the following also:

- Dependence on defining "options EXPERIMENTAL" in the kernel configuration file -- if the kernel isn't compiled with the EXPERIMENTAL option, a compile error warning that it needs to be defined will be generated.

- When a kernel is configured with an experimental feature, config generates a warning, similar to the ones it currently generates about GPL'd components, etc.

And we should make sure there is a note in the handbook section as well.

There is, IIRC. I'll double check to make sure.