freebsd 10.3 to 11 release upgrade on a vps

[Matthew Seaman]

On 2017/03/23 16:01, Matthew Seaman wrote:
>  That's why there is a
> '--currently-running /release/' option in more recent freebsd-update(8).
>  If you haven't got a recent-enough freebsd-update then there's a trick
> -- so upgrading a 10.3 jail to 11.0 would looks like:
> 
>    # env UNAME_r=10.3-RELEASE freebsd-update -r 11.0-RELEASE upgrade
> 
> and then do all the usuall 'freebsd-update install' steps similarly.
> 

Just to clarify, and for the sake of anyone tempted to take this too
literally from the archives: 10.3-RELEASE actually does have the
'--currently-running' option.  The example I made up above is
unnecessary (although it will work).

For a 10.3 -> 11.0 upgrade of a jail:

   # freebsd-update --currently-running 10.3-RELEASE -r 11.0-RELEASE upgrade

But for a 9.3 -> 10.3 upgrade of a jail:

   # env UNAME_r=9.3-RELEASE freebsd-update -r 10.3-RELEASE upgrade

Also, one thing I forgot.  When upgrading either the host or the jails,
make sure that you're on the latest 10.3-RELEASE patchlevel before
trying the upgrade to 11.0.  There were changes in freebsd-update(8)
itself that are required to upgrade to 11.0.  If you're running older
than 10.3-RELEASE, I believe the best advice is to upgrade to
10.3-RELEASE first, and then to 11.0-RELEASE.

	Cheers,

	Matthew


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 972 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20170323/1df69f49/attachment.sig>