From owner-freebsd-questions@FreeBSD.ORG Thu May 27 13:47:42 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 316CA1065675 for ; Thu, 27 May 2010 13:47:42 +0000 (UTC) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.freebsd.org (Postfix) with ESMTP id EE7658FC0C for ; Thu, 27 May 2010 13:47:41 +0000 (UTC) Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by hub.org (Postfix) with ESMTP id D47C53455915; Thu, 27 May 2010 10:47:39 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 47430-03; Thu, 27 May 2010 13:47:41 +0000 (UTC) Received: by hub.org (Postfix, from userid 1002) id 98F6334558ED; Thu, 27 May 2010 10:47:39 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by hub.org (Postfix) with ESMTP id 9884F34558E4; Thu, 27 May 2010 10:47:39 -0300 (ADT) Date: Thu, 27 May 2010 10:47:39 -0300 (ADT) From: "Marc G. Fournier" To: Mehmet Erol Sanliturk In-Reply-To: Message-ID: References: <4BF54704.20909@vetterberg.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Dan Naumov , freebsd-questions@freebsd.org, Roger Vetterberg Subject: Re: How long do you go without upgrading FreeBSD to a newer release? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 13:47:42 -0000 On Thu, 20 May 2010, Mehmet Erol Sanliturk wrote: > (i) install onto a new computer , test it , and if it is working very well > transfer data onto > new system , and keep old system for a new release/update cycle . > This step is most suitable for production systems exposed to outer > world . > (ii) attach a new hard disk to the computer , copy all of the present files > to the new > system , > update it , test it , if it is successful , use previous hard disk for a > new release/update > cycle , > (iii) back-up all of the data , and try update . Testing suitability may > take a long time . > > In steps (ii) and (iii) , do not load new data during tests , because at the > end , all of them may be destroyed . > ( No one of the above steps are suitable for a proprietary , activation > based operating system because they are not allowing so many computer and/or > hard disk changes . ) > > Therefore , the problem is a "system analysis and design" process . In my case, I have nagios setup to advise me when its been 60 days since last upgrade and perform an upgrade religiously when the alarm is sounded ... have had this policy for *years* now without regret ... ---- Marc G. Fournier Hub.Org Hosting Solutions S.A. scrappy@hub.org http://www.hub.org Yahoo:yscrappy Skype: hub.org ICQ:7615664 MSN:scrappy@hub.org