From owner-freebsd-questions@FreeBSD.ORG  Sat Jan 14 16:04:09 2012
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 A32F1106566C
	for <freebsd-questions@freebsd.org>;
	Sat, 14 Jan 2012 16:04:09 +0000 (UTC)
	(envelope-from jmc-freebsd2@milibyte.co.uk)
Received: from avasout08.plus.net (avasout08.plus.net [212.159.14.20])
	by mx1.freebsd.org (Postfix) with ESMTP id 010A88FC13
	for <freebsd-questions@freebsd.org>;
	Sat, 14 Jan 2012 16:04:08 +0000 (UTC)
Received: from curlew.milibyte.co.uk ([84.92.153.232]) by avasout08 with smtp
	id MU461i004516WCc01U47j5; Sat, 14 Jan 2012 16:04:07 +0000
X-CM-Score: 0.00
X-CNFS-Analysis: v=2.0 cv=Ybg/Fntf c=1 sm=1 a=lfSX4pPLp9EkufIcToJk/A==:17
	a=rLpCYgkgFLgA:10 a=YBe4BTGXXIYA:10 a=ZTb9aqGL9YkA:10 a=8nJEP1OIZ-IA:10
	a=knXGTJhMBhCLFVkGmcoA:9 a=djM9kGWAMdT8VCgjiXoA:7 a=wPNLvfGTeEIA:10
	a=lfSX4pPLp9EkufIcToJk/A==:117
Received: by curlew.milibyte.co.uk with local (Exim 4.77)
	(envelope-from <jmc-freebsd2@milibyte.co.uk>)
	id 1Rm65N-0000eS-Or; Sat, 14 Jan 2012 16:04:05 +0000
From: Mike Clarke <jmc-freebsd2@milibyte.co.uk>
To: freebsd-questions@freebsd.org
Date: Sat, 14 Jan 2012 16:04:05 +0000
User-Agent: KMail/1.9.10
References: <4F1034AB.903@nagual.nl>
	<201201141137.44893.jmc-freebsd2@milibyte.co.uk>
	<4F116F44.80901@nagual.nl>
In-Reply-To: <4F116F44.80901@nagual.nl>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201201141604.05725.jmc-freebsd2@milibyte.co.uk>
X-SA-Exim-Connect-IP: <locally generated>
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: Dick Hoogendijk <dick@nagual.nl>
Subject: Re: upgrade from 8.2 to 9.0
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 14 Jan 2012 16:04:09 -0000

On Saturday 14 January 2012, Dick Hoogendijk wrote:

> I had not heard of this project before. Sounds very nice if it works.
> Manging BE's is one of the main things I miss in the FreeBSD ZFS
> support. Coming from (open)Solaris this was quite a disappointment.
> BE's rock!

Yes, it's working fine here.

You can even upgrade a new environment while you continue working with 
the current one with

   manageBE create -n <newBE> -s <sourceBE> -p <pool>
   manageBE freebsd-upgrade -n <newBE> -p <pool> -r <release>
   manageBE activate -n <newBE> -p <pool>

Then reboot into the new BE and complete the upgrade with the 
final "freebsd-update install" step. But I needed to 
change "chroot /${bootfs}" near the end of the script 
to "chroot /${pool}/ROOT/${bootfs}" to get "manageBE freebsd-upgrade" 
command to work.

Along similar lines, if you need to do a massive ports upgrade which you 
suspect might go pear shaped then you can do it in a new BE without 
upsetting your working system:

   chroot /tank/ROOT/newBE mount -t devfs devfs /dev
   chroot /tank/ROOT/newBE portmaster -a
   chroot /tank/ROOT/newBE umount /dev

... then, if all went well,  activate the new BE and reboot.

-- 
Mike Clarke