Date: Thu, 24 Mar 2016 08:08:16 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: FreeBSD and updating to new release Message-ID: <56F3A070.2030502@FreeBSD.org> In-Reply-To: <CALfReydbN-4tcz%2BfVdrJqKXKkk2OHmmTyZ%2Bf9Z-F9=Z9m7SBOg@mail.gmail.com> References: <BLU437-SMTP82575DBFFE44ACB681BE9380800@phx.gbl> <86wpoutjnn.fsf@WorkBox.Home> <BLU436-SMTP144850FE4066A24814D884780800@phx.gbl> <86lh5at8e9.fsf@WorkBox.Home> <CALfReydbN-4tcz%2BfVdrJqKXKkk2OHmmTyZ%2Bf9Z-F9=Z9m7SBOg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --2pavhMRhkhdH1djqNjCKMT851kKhLms9F Content-Type: multipart/mixed; boundary="JIUPMcFbEF9WgnwbLv2T2bVpDAhwAVqtT" From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Message-ID: <56F3A070.2030502@FreeBSD.org> Subject: Re: FreeBSD and updating to new release References: <BLU437-SMTP82575DBFFE44ACB681BE9380800@phx.gbl> <86wpoutjnn.fsf@WorkBox.Home> <BLU436-SMTP144850FE4066A24814D884780800@phx.gbl> <86lh5at8e9.fsf@WorkBox.Home> <CALfReydbN-4tcz+fVdrJqKXKkk2OHmmTyZ+f9Z-F9=Z9m7SBOg@mail.gmail.com> In-Reply-To: <CALfReydbN-4tcz+fVdrJqKXKkk2OHmmTyZ+f9Z-F9=Z9m7SBOg@mail.gmail.com> --JIUPMcFbEF9WgnwbLv2T2bVpDAhwAVqtT Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 24/03/2016 07:50, krad wrote: > Are you sure this is correct? You could upgrade from 9-10 via freebsd > update, and the OP did say when 11 is released, so the whole developmen= t > case is not relevant in his case. It would also seem odd users would be= > left hanging with a missing step from 10-11 with binary updates. Sure > freebsd-update wont be there in 11, but you are running freebsd 10 when= you > do the actual upgrade, and have freebsd-update available. The binary upgrade path from 10.x to 11.0 will consist of installing the pkg's for 11.0, not by use of freebsd-update. If you're installing from source, you now get some extra steps in the compilation process: 'make packages' creates not just the set of packages but builds a local repository, and you then use 'pkg install' to deploy the packages from that repository. Cheers, Matthew --JIUPMcFbEF9WgnwbLv2T2bVpDAhwAVqtT-- --2pavhMRhkhdH1djqNjCKMT851kKhLms9F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJW86B3XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT6QgP/jwavoFzC9e79cBm3DFG8zLl SOfoVuRwhDWxMvB75jVyELiez7kbWZsZYvXf64TQTECl40lSEmv1awNhiHUETmdg r4HpbmvDvWSm1YFYZVYxNREwfhB6ydzMi4B75iS6f9GxQPiWv3LlYTiSW2Dopx1E vz9Qi/Y2Xa3Z4hWTyU8zzWKqWXwAVYED4ODIIc3hqQN7axw8fpgwPMe29Fft1s/V wl5qqocVXKBeDLGMQKGGkAjHgZyFpkeFpJ1nClpiaQQyG4JWlcqFckbEv6lcRwXN m1cnEjBmtuy5dbH1uo5bizNIcj53YtClSM9b7JjCjXQ6tgFis2gIxtbMX5E9BkXV ctCPIfGEm0mPR+/eZRidFe+y/fKWxpaS7A7n+f6O6OIKd6VNubs4I+0OdmyC++zg aK5KkK7RMyZeQXNb+pnFBKrVXB4p5/3n/khlbrgiY84KirWaPmRETerDiOI0CvPf p16z9PsYNbtK/3nGifHO2Py8+98BaC3TRBtQAVOHl1i8oOnw8bF4pvEo412PG2GG BATPtsWCk74Vn0rrlAxK6CgiU+QMlrhEDtZYPRavOkwKpisjHHXEdV5V9sB9JWt/ 4ma/kwjmm5MqeMUVIeNVuY/5JByQe/6shbArX8WNnYNwOhvia3Iqb72KDkLNR6y0 VozWfptBhbz6CDzs6UDL =Uz9y -----END PGP SIGNATURE----- --2pavhMRhkhdH1djqNjCKMT851kKhLms9F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56F3A070.2030502>