From owner-freebsd-questions@FreeBSD.ORG Sat Nov 1 22:35:34 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0C2E7A24 for ; Sat, 1 Nov 2014 22:35:34 +0000 (UTC) Received: from avasout08.plus.net (avasout08.plus.net [212.159.14.20]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 62D4AE6B for ; Sat, 1 Nov 2014 22:35:32 +0000 (UTC) Received: from curlew.milibyte.co.uk ([84.92.153.232]) by avasout08 with smtp id ANbN1p002516WCc01NbPDP; Sat, 01 Nov 2014 22:35:23 +0000 X-CM-Score: 0.00 X-CNFS-Analysis: v=2.1 cv=XuZ0OD19 c=1 sm=1 tr=0 a=lfSX4pPLp9EkufIcToJk/A==:117 a=lfSX4pPLp9EkufIcToJk/A==:17 a=D7rCoLxHAAAA:8 a=0Bzu9jTXAAAA:8 a=GIpPufGBusUA:10 a=8nJEP1OIZ-IA:10 a=SDPOm_EyW2g6QYvAOlkA:9 a=wPNLvfGTeEIA:10 Received: from sedbergh.lan ([192.168.1.13] helo=curlew.lan) by curlew.milibyte.co.uk with esmtp (Exim 4.84) (envelope-from ) id 1XkhGT-00037M-AZ for freebsd-questions@freebsd.org; Sat, 01 Nov 2014 22:35:22 +0000 From: Mike Clarke To: freebsd-questions@freebsd.org Date: Sat, 01 Nov 2014 22:35:20 +0000 Message-ID: <4424214.PdRTGivWqz@curlew.lan> User-Agent: KMail/4.14.2 (FreeBSD/10.1-RC1-p1; KDE/4.14.2; amd64; ; ) In-Reply-To: <5454B500.5030501@infracaninophile.co.uk> References: <545409E0.9030809@bluerosetech.com> <5454B500.5030501@infracaninophile.co.uk> MIME-Version: 1.0 X-SA-Exim-Connect-IP: 192.168.1.13 X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on curlew.lan X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 Subject: Re: Root-on-ZFS upgrade question Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="iso-8859-1" X-SA-Exim-Version: 4.2 X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Nov 2014 22:35:34 -0000 On Saturday 01 Nov 2014 10:25:04 Matthew Seaman wrote: > If your original system had been maintained via freebsd-update(8) > you could just use that to upgrade to 10.1-RELEASE in place -- when > it tells you to reboot, just run freebsd-update again. I think the second run of freebsd-update needs to be applied after booting into the new environment so do it after the beadm activate step. An alternative approach is to activate the new environment immediately after creating it and then reboot and upgrade the new environment to rev. 10 in the "conventional" way. The chroot approach means that you can sort out upgrading the OS and reinstalling all the ports at leisure without disrupting your working system until you're ready for the final switch over. I normally use this approach for major port upgrades and dot level system upgrades within the same release level but I had problems with upgrading from 9.1 to 10.0 due, I assune, to incompatibilities between the 10.0 applications and the running 9.1 kernel. If you want to keep the option of reverting to your 9.x system after the upgrade then you need to make sure that all OS release level dependant directories like most of /usr and /usr/local are contained in the boot environment. On the other hand you can save disk space and download time by placing /usr/ports/distfiles outside of the boot environment. You will probably also want to keep /var/log, /var/mail and application databases, e.g. /var/db/mysql, outside of the boot environment. -- Mike Clarke