On Mar 16, 2023, at 17:27, Mark Millard wrote:
> On Mar 16, 2023, at 16:48, 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 and tijl
On Mar 16, 2023, at 16:48, 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 and tijl just in case since they're more familiar with this
> than I
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 and tijl just in case since they're more familiar with this
than I am.
Colin Percival
On 3/16/23 15:55, Mark Millard wrote
On Mar 16, 2023, at 15:55, Mark Millard wrote:
> # cat /etc/hostid /etc/machine-id /var/db/machine-id
> a4f7fbeb-f668-11de-b280-ebb65474e619
> a4f7fbebf66811deb280ebb65474e619
> 7227cd89727a462186e3ba680d0ee142
>
> (I'll not be keeping these values for the example system.)
>
> # ls -Tld /etc/ho
# cat /etc/hostid /etc/machine-id /var/db/machine-id
a4f7fbeb-f668-11de-b280-ebb65474e619
a4f7fbebf66811deb280ebb65474e619
7227cd89727a462186e3ba680d0ee142
(I'll not be keeping these values for the example system.)
# ls -Tld /etc/hostid /etc/machine-id /var/db/machine-id
-rw-r--r-- 1 root whe
