From owner-freebsd-questions@FreeBSD.ORG Wed Jan 22 02:49:09 2014 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2FF9BC07 for ; Wed, 22 Jan 2014 02:49:09 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.226]) by mx1.freebsd.org (Postfix) with ESMTP id E3EFA1307 for ; Wed, 22 Jan 2014 02:49:08 +0000 (UTC) Received: from [96.28.178.143] ([96.28.178.143:30335] helo=localhost) by cdptpa-oedge01 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 0A/C0-02594-E913FD25; Wed, 22 Jan 2014 02:49:02 +0000 Date: Wed, 22 Jan 2014 02:49:02 +0000 Message-ID: <0A.C0.02594.E913FD25@cdptpa-oedge01> From: "Thomas Mueller" To: freebsd-questions@FreeBSD.org References: <52DF088C.7040800@networktest.com> Subject: Re: freebsd-update and 10.0: Just checking X-RR-Connecting-IP: 107.14.168.118:25 X-Cloudmark-Score: 0 Cc: David Newman X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 02:49:09 -0000 from David Newman : > Just checking: Ate there any issues with upgrading a plain-vanilla > 9.2-RELEASE box to 10.0-RELEASE using freebsd-update? > The 10.0 release announcement contains scary warnings about upgrading > using freebsd-update, but the installation instructions look like the > usual procedure. > http://www.freebsd.org/releases/10.0R/announce.html > http://www.freebsd.org/releases/10.0R/installation.html > Errata 13:04 and 13:05 pertain to 10.0 release candidates, so I'm hoping > these issues got fixed before the final release. > Thanks! > dn I found a bug in one section (2.1) of installation.html: 2.1. Upgrading from Source The procedure for doing a source code based update is described in and . For SVN use the releng/10.0 branch which will be where any upcoming Security Advisories or Errata Notices will be applied. (end of quote) It looks like they copied from a template and forgot to fill in the blanks in the first sentence above. I would know to look in /usr/src/UPDATING or $SRCDIR/UPDATING . Tom