Date: Sat, 1 Jul 2017 08:03:47 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: Alejandro Imass <aimass@yabarana.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Upgrade from 10.1-RELEASE to 10.3-RELEASE went wrong, pls. help! Message-ID: <398f92a2-e38a-05e9-89fa-8d7d53eb498d@FreeBSD.org> In-Reply-To: <CAHieY7RfKRnUYJf6CLjac503m6kktG48Yd%2B=Ok2qP=XQ5VJS7g@mail.gmail.com> References: <CAHieY7QUbWdbK4Px0Dsgs-mfsTz7y2S3Qi0SZGixqhsFaE29MQ@mail.gmail.com> <f7d8b9ca-bcd8-2cd6-db52-f4ae4700ff00@FreeBSD.org> <CAHieY7RfKRnUYJf6CLjac503m6kktG48Yd%2B=Ok2qP=XQ5VJS7g@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) --jKSr1N4KjRp2JpeasM2ITKxcAuv7s2I9x Content-Type: multipart/mixed; boundary="uEH9IqT9lfAdHp7TmCMK8unHxP256XuDJ"; protected-headers="v1" From: Matthew Seaman <matthew@FreeBSD.org> To: Alejandro Imass <aimass@yabarana.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Message-ID: <398f92a2-e38a-05e9-89fa-8d7d53eb498d@FreeBSD.org> Subject: Re: Upgrade from 10.1-RELEASE to 10.3-RELEASE went wrong, pls. help! References: <CAHieY7QUbWdbK4Px0Dsgs-mfsTz7y2S3Qi0SZGixqhsFaE29MQ@mail.gmail.com> <f7d8b9ca-bcd8-2cd6-db52-f4ae4700ff00@FreeBSD.org> <CAHieY7RfKRnUYJf6CLjac503m6kktG48Yd+=Ok2qP=XQ5VJS7g@mail.gmail.com> In-Reply-To: <CAHieY7RfKRnUYJf6CLjac503m6kktG48Yd+=Ok2qP=XQ5VJS7g@mail.gmail.com> --uEH9IqT9lfAdHp7TmCMK8unHxP256XuDJ Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: quoted-printable On 30/06/2017 18:17, Alejandro Imass wrote: > Any idea what went wrong? I have upgraded FBSD since 6.x and never had > it go so badly !! Not really. Clearly something went wrong with the process for executing a binary, but quite what I couldn't say. The whole way an executable is run hasn't changed significantly since the switch between a.out and elf around 3.0-RELEASE, so it's not as if you've some half-implemented change screwing things up. One of the problems with freebsd-update(8) is dealing with when things go wrong. Thankfully this is a pretty rare occurrence, but even something as trivial as running out of space in a partition in the middle of an upgrade can leave you with an incomplete upgrade, and no reasonable way of fixing it. Cheers, Matthew --uEH9IqT9lfAdHp7TmCMK8unHxP256XuDJ-- --jKSr1N4KjRp2JpeasM2ITKxcAuv7s2I9x Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQJ8BAEBCgBmBQJZV0laXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkATbHgP/1KqTmJyPITRpnJJ++rBwTuB lXhLu5W7M7to9NTusM5xFdqG4WHdOQQousVoIZ7/jD1EQPLTNwsJ2EIVEKHZZu8O XfqKo5uRy7pRm5vgUAFC+fAxQHb07Q94zEEzKPApoGxrJHXIb6+uXEZH4zA7WJaC C5SvnmQ65q0nOyAF6DmNWCMGUHythFAbnSt/qmflO0l7S4I53/KrnkwIn0DplThc IOoXSgyXD5v5PQ2cs7tf0avH1aqYu33ITpX7VjO3ZiPRLXvnEkSBtyPnMV1ejTIb mjWr8FR0Y80vtqcyMS53XAOIMEtIk1HSlcn2EjVtsXYHuFwVLn8z1BZv7AtYObGt D6izWkMdR2EOMDaM1YW7+S2nBKR4KSAvRtED2afPRN+sDuy2DVYgj1GnXIO7Uzn8 R4YVsm3NEwOsQ+ksKXGBsIzfG06ANFVW7SdjItf6GUpS99uPpRYrM1Jr+Hv9E7Km YBGVnpsstza24pcF0Uze1+2eUWWnajPdwDy/9MY76Yd0W0cPYe0E6YFu010tfYJw NPe0s6l5kleHHzsK/Mf/VMtXOlwyxN5tnxbqyTZocH0CidfDwKjCDDCWk8XSdsaz u51W6KxxNr0izAuJ6IiKOFzlEJirsG2QWttdZKNthfNnljf7mhE13K7D/LKqG5VD amAotRIOVEuruGsHbXJZ =YPTr -----END PGP SIGNATURE----- --jKSr1N4KjRp2JpeasM2ITKxcAuv7s2I9x--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?398f92a2-e38a-05e9-89fa-8d7d53eb498d>