Date: Thu, 2 Nov 2023 18:35:35 +0100 From: Kurt Jaeger <pi@freebsd.org> To: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: RELENG_13 to 14 upgrade fail Message-ID: <ZUPd5x1kqqw48g7w@fc.opsec.eu> In-Reply-To: <CAGMYy3tngcCt6Hn2D08CErdsocD%2BiPR3uZjxQALb5TCV%2Bq8wVA@mail.gmail.com> References: <0c19b8a6-119c-4f5d-af26-d625afc7afec@sentex.net> <CAGMYy3sL%2B2BikO%2BwGakues3aFnUCL=GoEG%2BLdMVF_0gZknpBEg@mail.gmail.com> <515d5ad4-9fc8-4f86-936b-b71d8f43d564@sentex.net> <CAGMYy3tngcCt6Hn2D08CErdsocD%2BiPR3uZjxQALb5TCV%2Bq8wVA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! [Xin LI wrote:] > It's generally a good idea to have access to the physical system, or via a > remote console that allows you to mount a .iso image, by the way. Depends on the application. If the box is at a remote site, and the cost of the box needs to be below 400 US$, the upgrade path should be possible without any of those requirements. It works like that right now, but I fear the day this is no longer possible. -- pi@FreeBSD.org +49 171 3101372 Now what ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZUPd5x1kqqw48g7w>