From owner-freebsd-questions@FreeBSD.ORG Sun Feb 27 22:36:13 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8CCA16A4CE for ; Sun, 27 Feb 2005 22:36:13 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F12F43D5C for ; Sun, 27 Feb 2005 22:36:13 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1103.wanadoo.fr (SMTP Server) with ESMTP id 9AF591C00093 for ; Sun, 27 Feb 2005 23:36:12 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1103.wanadoo.fr (SMTP Server) with ESMTP id 6F2DC1C0008F for ; Sun, 27 Feb 2005 23:36:12 +0100 (CET) X-ME-UUID: 20050227223612455.6F2DC1C0008F@mwinf1103.wanadoo.fr Date: Sun, 27 Feb 2005 23:36:12 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <1536617123.20050227233612@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: <422249ED.1050702@cis.strath.ac.uk> References: <20050226130211.4162005f.albi@scii.nl> <1262756249.20050226141419@wanadoo.fr> <20050226142726.M5182@reiteration.net> <43908349.20050226154151@wanadoo.fr> <20050227045510.M67328@reiteration.net> <956914133.20050227100144@wanadoo.fr> <20050227210242.M8232@reiteration.net> <173258071.20050227231351@wanadoo.fr> <422249ED.1050702@cis.strath.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Installation instructions for Firefox somewhere? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 22:36:14 -0000 Chris Hodgins writes: > It should be trivial to update your kernel config and rebuild and > install the new kernel. Remember to reboot when you are done. It's trivial in principle, but this is a production server. The golden rule for production servers is never to change anything unless you have to. I don't know that assisting with my testing justifies the risk of rebuilding the kernel on the production machine (not to mention trying to get NFS to work). > Not installing and deinstalling, but updating. I use cvsup and > portupgrade about once a week to keep my system up to date. If you are > running a production system and don't, then you are putting yourself > and your users at risk (especially on systems running lots of > applications). I am not running a production system btw this is just > for my home system. One doesn't do this on production systems. Any kind of automatic or regular change or updating of the server is an invitation to catastrophe. Changes to production servers must be explicitly and carefully carried out and exhaustively tested for regressions and compatibility. I'd never have anything automatically updated on a production machine; I want to see and verify every change before it goes into production, and I need a Plan B to back out any change if something goes wrong. -- Anthony