From owner-freebsd-doc@FreeBSD.ORG Fri Nov 19 19:37:49 2004 Return-Path: Delivered-To: freebsd-doc@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFEB616A4CE for ; Fri, 19 Nov 2004 19:37:49 +0000 (GMT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2CF343D1F for ; Fri, 19 Nov 2004 19:37:45 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 392A531C; Fri, 19 Nov 2004 13:37:45 -0600 (CST) Date: Fri, 19 Nov 2004 13:37:45 -0600 From: Tillman Hodgson To: freebsd-doc@www.freebsd.org Message-ID: <20041119193745.GD61766@seekingfire.com> References: <419E4747.6070001@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419E4747.6070001@FreeBSD.org> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.6i Subject: Re: Proposal regarding security chapter X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 19:37:50 -0000 On Fri, Nov 19, 2004 at 08:19:35PM +0100, Remko Lodder wrote: > my thoughts: > > Split security into security and firewall > update book.sgml to have firewall below security > (and before mac) and update other references as well. > > I would like to hear your opinions about this :) "Firewall", by itself, doesn't feel like an intuitive place to split topics to me (aside from the convenience of its size). However, I can see a natural split between network security and host security. In that scenario, MAC would become the largest portion of the host security chapter. That still leaves security with 2 chapters, unfortunately. It only addressed the page count balance between the two chapters. -T -- CP/M-86 *screams* on a PII/400. -- Dave Brown, a.s.r. I would think so. The whole floppy image will fit in the L-II cache. -- Mark Atwood, in reply