> On Dec 19, 2018, at 1:24 PM, Brian Neal wrote:
>
> Thanks, Matt. I did try the update procedure from the handbook and found the
> instance hanging on boot with a repeated socket error. If I have to rebuild
> from scratch, I’d prefer to find some jail/deployment-automation so I don’t
> have
On 12/18/18 10:50 PM, Brian Neal wrote:
Hello,
I’m looking for advice on doing a release upgrade of a running instance. It
looks like the normal procedure using freebsd-update requires a reboot between
invocations of the install command, but after the first reboot, most of the
userland is
Thanks, Matt. I did try the update procedure from the handbook and found the
instance hanging on boot with a repeated socket error. If I have to rebuild
from scratch, I’d prefer to find some jail/deployment-automation so I don’t
have to manually rebuild everything on each release. FWIW, I did ha
> On Dec 19, 2018, at 1:50 AM, Brian Neal wrote:
>
> I’m looking for advice on doing a release upgrade of a running instance. It
> looks like the normal procedure using freebsd-update requires a reboot
> between invocations of the install command, but after the first reboot, most
> of the us
Hello,
I’m looking for advice on doing a release upgrade of a running instance. It
looks like the normal procedure using freebsd-update requires a reboot between
invocations of the install command, but after the first reboot, most of the
userland is non-functional, including most importantly s
