From owner-freebsd-questions@FreeBSD.ORG Tue Aug 31 15:25:07 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 D1FB510656BA for ; Tue, 31 Aug 2010 15:25:07 +0000 (UTC) (envelope-from jmc-freebsd2@milibyte.co.uk) Received: from relay.pcl-ipout02.plus.net (relay.pcl-ipout02.plus.net [212.159.7.100]) by mx1.freebsd.org (Postfix) with ESMTP id 689478FC26 for ; Tue, 31 Aug 2010 15:25:06 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAG67fExUXebj/2dsb2JhbACgZnG/K4U3BIki Received: from outmx01.plus.net ([84.93.230.227]) by relay.pcl-ipout02.plus.net with ESMTP; 31 Aug 2010 16:25:05 +0100 Received: from helix.plus.com ([84.92.153.232] helo=curlew.milibyte.co.uk) by outmx01.plus.net with esmtp (Exim) id 1OqSht-0007VB-Bj; Tue, 31 Aug 2010 16:25:05 +0100 Received: by curlew.milibyte.co.uk with local (Exim 4.72) (envelope-from ) id 1OqShs-0001DZ-1e; Tue, 31 Aug 2010 16:25:04 +0100 From: Mike Clarke To: freebsd-questions@freebsd.org Date: Tue, 31 Aug 2010 16:25:03 +0100 User-Agent: KMail/1.9.10 References: <20100831135619.GA37924@engr.uky.edu> In-Reply-To: <20100831135619.GA37924@engr.uky.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201008311625.03931.jmc-freebsd2@milibyte.co.uk> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-SA-Exim-Scanned: No (on curlew.milibyte.co.uk); SAEximRunCond expanded to false Cc: Kyle Dippery Subject: Re: freebsd-update newbie 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: Tue, 31 Aug 2010 15:25:07 -0000 On Tuesday 31 August 2010, Kyle Dippery wrote: > I've just installed 8.1 from distribution CDs and updated stable > with cvsup. I want to enable freebsd-update to keep the system, > well, updated. > > First try, 'freebsd-update fetch' yielded a number of failure > messages freebsd-update will only track the RELEASE branch. If you want to track STABLE you'll have to use csup and rebuild the entire system from source each time. Unless you really want to track the latest developments in STABLE you can stay with RELEASE and use freebsd-update to ensure that you get all the security patches. See section 24.5.2 in the FreeBSD Handbook to help you decide if you really need STABLE If you choose to stick with RELEASE then it's worth subscribing to the FreeBSD Security Advisories mailing list and only running freebsd-update after any updates have been announced. -- Mike Clarke