Date: Thu, 23 Mar 2017 16:25:09 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: freebsd 10.3 to 11 release upgrade on a vps Message-ID: <74a663d5-4ee6-8c2f-6d20-10ec571c8cea@FreeBSD.org> In-Reply-To: <26f53955-835e-6dae-5154-32ad2fe06228@infracaninophile.co.uk> References: <CAPORhP7QT=j9fkYs3_ymQAgd3KYRF53QQnGFPJKCzH%2BO5vLnPQ@mail.gmail.com> <58D3ECC0.1000001@gmail.com> <26f53955-835e-6dae-5154-32ad2fe06228@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --n0DMHWOkWKE41BsxCfnflEPfrbEiiltH8 Content-Type: multipart/mixed; boundary="d4fS1okJMqiHNKRP0Ip5okG0qBfvFm1Dq"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Message-ID: <74a663d5-4ee6-8c2f-6d20-10ec571c8cea@FreeBSD.org> Subject: Re: freebsd 10.3 to 11 release upgrade on a vps References: <CAPORhP7QT=j9fkYs3_ymQAgd3KYRF53QQnGFPJKCzH+O5vLnPQ@mail.gmail.com> <58D3ECC0.1000001@gmail.com> <26f53955-835e-6dae-5154-32ad2fe06228@infracaninophile.co.uk> In-Reply-To: <26f53955-835e-6dae-5154-32ad2fe06228@infracaninophile.co.uk> --d4fS1okJMqiHNKRP0Ip5okG0qBfvFm1Dq Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable 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)= =2E > 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: >=20 > # env UNAME_r=3D10.3-RELEASE freebsd-update -r 11.0-RELEASE upgrade >=20 > and then do all the usuall 'freebsd-update install' steps similarly. >=20 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 upgr= ade But for a 9.3 -> 10.3 upgrade of a jail: # env UNAME_r=3D9.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 --d4fS1okJMqiHNKRP0Ip5okG0qBfvFm1Dq-- --n0DMHWOkWKE41BsxCfnflEPfrbEiiltH8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQJ8BAEBCgBmBQJY0/brXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxOUYxNTRFQ0JGMTEyRTUwNTQ0RTNGMzAw MDUxM0YxMEUwQTlFNEU3AAoJEABRPxDgqeTnNEwP/j0iBD9huKRzz1oqafY+lm+a TvGFJJdaMtSH3i7StihfbWM4mB5YVfamNbkTIfhKU3LbSdKgPhvY0DnRMzwe+L1s 4p7JZfAuBSPJd/cMr4GtbqdXaXR1X93kZ9pWmdnBGUkyGIHBmdCn0A6HSxW4Z8P6 64+pELAoxjAG/Le9QEN2cOFNK+ShW1n9XPAb9GJXWaBJP1AtQlw5i/1IAEWZ3kpo PDMPMI62yMiaYpMrbBP3ivj2xDEAa8KpsbwffKDwtkyZKeuHCT05n1YRYfsagEIB 3IEAJL023YhbdM3uA35j2WviFu+vpsAcVD0FdMIyUYMj4cJv5fvzeqdqEFS2gP7z cY2Ia6/T0TQXZJ7St+UhoWE907Ph3hWSnqzKNhZqxkNEwvlZnfDrK6lQ33MznlKB PvP7FCQTCxJ0hwMwG1aincyxYJphtuIrUZx8yS4vvrv8zazblwagWjR4dMK6/Edw xZYCpQkghrtzBI1ENrsAq5XFULBFZZj99SPempY84SO0yfV3NlfjHLO29DT3PC02 K/GPtpEeo6kivjtIQvh5LoYZyhCKDg0RVMEdDNokPtc0mJ0sK0M5X2GpB/0aKys/ DB9FTanggHOMsaKHzSOSMVJ7ctsNIH56UhnTS3TQ+TEUq++TALzL0YoP+An5QAiM B6eXbA4LahEGDfGbrmG+ =iKEa -----END PGP SIGNATURE----- --n0DMHWOkWKE41BsxCfnflEPfrbEiiltH8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?74a663d5-4ee6-8c2f-6d20-10ec571c8cea>