On Mar 17, 2023, at 19:04, Mark Millard wrote:
> On Mar 17, 2023, at 18:24, Mark Millard wrote:
>
>> The 13.1-RELEASE (snapshot) to 13.2-RC3 freebsd-update's
>> upgrade sequence did not go well relative to my being
>> prompted to do the right thing to establish /etc/machine-id .
>> After the la
On Mar 17, 2023, at 18:24, Mark Millard wrote:
> The 13.1-RELEASE (snapshot) to 13.2-RC3 freebsd-update's
> upgrade sequence did not go well relative to my being
> prompted to do the right thing to establish /etc/machine-id .
> After the last reboot (kernel upgrade, presumably) it had me
> contin
The 13.1-RELEASE (snapshot) to 13.2-RC3 freebsd-update's
upgrade sequence did not go well relative to my being
prompted to do the right thing to establish /etc/machine-id .
After the last reboot (kernel upgrade, presumably) it had me
continue with. . .
# /usr/sbin/freebsd-update install
src compon
On Mar 17, 2023, at 10:15, Tijl Coosemans wrote:
> On Thu, 16 Mar 2023 16:48:40 -0700 Colin Percival
> wrote:
>> I think the current situation should be sorted out aside from potential
>> issues
>> for people who upgraded to a "broken" version before updating to the latest
>> code -- CCing bapt
