Date: Fri, 19 Jan 2018 14:08:04 -0800 From: Michael Sinatra <michael+lists@burnttofu.net> To: freebsd-stable@freebsd.org Subject: Re: Ancient FreeBSD update path Message-ID: <fd27fabb-ec98-9814-b253-c83c67ccce20@burnttofu.net> In-Reply-To: <1c0b0fb4-c324-b58f-3f2a-51a1272ce26b@bsquare.com> References: <03c972a8f098b1b547da690efaad771f@schema31.it> <1c0b0fb4-c324-b58f-3f2a-51a1272ce26b@bsquare.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/19/18 4:59 AM, Mike Pumford wrote: > I've just done a 9.3 to 10.3 upgrade with freebsd-update and pkg. > Networking wasn't avalable when the system was running 10.3 kernel with > 9.3 userland so I did that part of the update on the console. I have run into this problem with 9.3 -> 10.x upgrades. Basically, the old 9.3 ifconfig(8) breaks with the new 10.x kernel. Even though it's not the supported method, I have had good luck running freebsd-update on a 9.3 system, installing the kernel and then immediately (no reboot) running `freebsd-update install` again to install userland. *Then* reboot. You should be able to complete the update (removing old files and updating ports/packages) without having to go to the console. This method does not appear to be necessary for any upgrades other than 9.3 -> 10.x. michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fd27fabb-ec98-9814-b253-c83c67ccce20>