Date: Sat, 14 Jan 2012 16:04:05 +0000 From: Mike Clarke <jmc-freebsd2@milibyte.co.uk> To: freebsd-questions@freebsd.org Cc: Dick Hoogendijk <dick@nagual.nl> Subject: Re: upgrade from 8.2 to 9.0 Message-ID: <201201141604.05725.jmc-freebsd2@milibyte.co.uk> In-Reply-To: <4F116F44.80901@nagual.nl> References: <4F1034AB.903@nagual.nl> <201201141137.44893.jmc-freebsd2@milibyte.co.uk> <4F116F44.80901@nagual.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201201141604.05725.jmc-freebsd2>