17 messages in org.freebsd.trustedbsd-auditHEADS UP: Audit integration into CVS ...| From | Sent On | Attachments |
|---|---|---|
| Robert Watson | Feb 1, 2006 10:15 pm | |
| Kövesdán Gábor | Feb 1, 2006 10:22 pm | |
| Julian Elischer | Feb 1, 2006 10:32 pm | |
| Robert Watson | Feb 1, 2006 10:32 pm | |
| Robert Watson | Feb 1, 2006 10:55 pm | |
| Mike Jakubik | Feb 2, 2006 12:03 am | |
| Robert Watson | Feb 2, 2006 12:35 am | |
| Kris Kennaway | Feb 2, 2006 12:40 am | |
| Robert Watson | Feb 2, 2006 12:50 am | |
| Mike Jakubik | Feb 2, 2006 12:54 am | |
| Kris Kennaway | Feb 2, 2006 12:57 am | |
| Robert Watson | Feb 2, 2006 1:17 am | |
| Tom Rhodes | Feb 2, 2006 2:13 am | |
| Mike Jakubik | Feb 2, 2006 3:15 am | |
| Peter Jeremy | Feb 2, 2006 9:02 am | |
| Doug Barton | Feb 3, 2006 1:19 am | |
| Robert Watson | Feb 3, 2006 3:52 pm |
| Subject: | HEADS UP: Audit integration into CVS in progress, some tree disruption | |
|---|---|---|
| From: | Peter Jeremy (pete...@optushome.com.au) | |
| Date: | Feb 2, 2006 9:02:33 am | |
| List: | org.freebsd.trustedbsd-audit | |
On Wed, 2006-Feb-01 19:55:10 -0500, Mike Jakubik wrote:
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..
IMHO, once the API/ABI is stable, there is no reason why it can't be MFC'd as long as someone is willing to to do the work (including maintenance). The advantages are that the code is available to a larger group of users and therefore will (hopefully) get more testing. The more testing it gets, the sooner the "experimental" tag can be removed. The users for whom the audit framework is important will mostly not want to run bleeding edge code and so getting audit into -STABLE (and production quality) is important to this group.
Keep in mind that FreeBSD has shipped for years with utilities and kernel options that have "use at your own risk" warnings all over them. Looking at RELENG_4 LINT (the oldest I have readily to hand):
# NOTE 1: The options, CPU_BTB_EN, CPU_LOOP_EN, CPU_IORT, # CPU_LOOP_EN and CPU_RSTK_EN should not be used because of CPU bugs. # These options may crash your system. ... # Protocol families: # Only the INET (Internet) family is officially supported in FreeBSD. # Source code for the NS (Xerox Network Service) is provided for amusement # value. ... # Experimental IPsec implementation that uses the kernel crypto # framework. ... # NB: The NULL, PORTAL, UMAP and UNION filesystems are known to be # buggy, and WILL panic your system if you attempt to do anything with # them. They are included here as an incentive for some enterprising # soul to sit down and fix them. ... # apm: Laptop Advanced Power Management (experimental) ... # Note that this ACPI support is experimental and it's use may result in # machine hangs or kernel panics. ... # ihfc driver for Cologne Chip ISA chipsets (experimental!)
-- Peter Jeremy To Unsubscribe: send mail to majo...@trustedbsd.org with "unsubscribe trustedbsd-audit" in the body of the message