Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Feb 2005 23:36:12 +0100
From:      Anthony Atkielski <atkielski.anthony@wanadoo.fr>
To:        freebsd-questions@freebsd.org
Subject:   Re: Installation instructions for Firefox somewhere?
Message-ID:  <1536617123.20050227233612@wanadoo.fr>
In-Reply-To: <422249ED.1050702@cis.strath.ac.uk>
References:  <20050226130211.4162005f.albi@scii.nl> <LOBBIFDAGNMAMLGJJCKNEEIMFAAA.tedm@toybox.placo.com> <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>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1536617123.20050227233612>