From owner-freebsd-doc@FreeBSD.ORG Sat Mar 20 11:48:34 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 0775216A4CE for ; Sat, 20 Mar 2004 11:48:34 -0800 (PST) Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id F36EB43D31 for ; Sat, 20 Mar 2004 11:48:33 -0800 (PST) (envelope-from pepper@reppep.com) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id E4A31554F3 for ; Sat, 20 Mar 2004 11:48:33 -0800 (PST) (envelope-from pepper@reppep.com) Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0F6A16A4CE for ; Sat, 20 Mar 2004 11:48:33 -0800 (PST) Received: from www.reppep.com (www.reppep.com [66.92.104.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id A541943D31 for ; Sat, 20 Mar 2004 11:48:33 -0800 (PST) (envelope-from pepper@reppep.com) Received: from [66.92.104.201] (g4.reppep.com [66.92.104.201]) by www.reppep.com (Postfix) with ESMTP id 87F00FE02; Sat, 20 Mar 2004 14:48:32 -0500 (EST) Mime-Version: 1.0 X-Sender: pepper@mail.reppep.com Message-Id: Date: Sat, 20 Mar 2004 14:46:04 -0500 To: freebsd-doc@lists.freebsd.org From: Chris Pepper Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: Bjorn Dittmer-Roche Subject: http://www.reppep.com/~pepper/freebsd/install/ 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: Sat, 20 Mar 2004 19:48:34 -0000 Docs, I've written up a guide for installing a FreeBSD 4 system with a variety of useful ports, and specific suggested tweaks. I think it might be a useful article for recent converts, or helpful external reference for folks bringing up their own services on FreeBSD and looking for tips. What do y'all think? I've run through it a few times, and everything seems to work, except localhost access for /server-status & /server-info (I assume IPv4 only, and 4.9 seems to ship with IPv6 on by default). Also, I'll probably abstract out most of the 'vi' instructions into a pre- step, and tell users to save their customizations for later rebuilds, but that's a detail. Does this look worthwhile to anyone? Thanks, Chris Pepper PS-"Upgrade Source, Kernel & World" provides an 'express' recipe for upgrading a whole system after initial install. My original goal was to prepare everything so "portupgrade -a" was likely to work properly... -- Chris Pepper: Rockefeller University: