From owner-freebsd-questions@FreeBSD.ORG Sun Feb 27 23:03:18 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 3C62216A4CE for ; Sun, 27 Feb 2005 23:03:18 +0000 (GMT) Received: from smtphost.cis.strath.ac.uk (smtphost.cis.strath.ac.uk [130.159.196.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73FB343D1D for ; Sun, 27 Feb 2005 23:03:17 +0000 (GMT) (envelope-from chodgins@cis.strath.ac.uk) Received: from [192.168.0.4] (chrishodgins.force9.co.uk [84.92.20.141]) j1RN374A006341 for ; Sun, 27 Feb 2005 23:03:07 GMT Message-ID: <422252E4.1010308@cis.strath.ac.uk> Date: Sun, 27 Feb 2005 23:08:20 +0000 From: Chris Hodgins User-Agent: Mozilla Thunderbird 1.0 (X11/20050204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org 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> <1536617123.20050227233612@wanadoo.fr> In-Reply-To: <1536617123.20050227233612@wanadoo.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-CIS-MailScanner-Information: Please contact support@cis.strath.ac.uk for more information X-CIS-MailScanner: Found to be clean X-CIS-MailScanner-SpamCheck: not spam, SpamAssassin (score=0, required 6) X-CIS-MailScanner-From: chodgins@cis.strath.ac.uk Subject: Re: Installation instructions for Firefox somewhere? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Feb 2005 23:03:18 -0000 Anthony Atkielski wrote: > 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). > If you have ssh running on your production machine you could build using ports on the other test machine and sftp the new package across. > >>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. > Well if you are doing all this you will carry out the updates to your test machine first and validate everything works fine. Once you are happy build a package from it and add it to your production server. I am not sure how you would verify a package as big as firefox or openoffice without doing this. Chris