From nobody Sat Mar 18 15:50:29 2023 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Pf57X6LDTz3yjW0; Sat, 18 Mar 2023 15:50:48 +0000 (UTC) (envelope-from chargen@gmail.com) Received: from mail-oa1-x33.google.com (mail-oa1-x33.google.com [IPv6:2001:4860:4864:20::33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Pf57X3YHNz3CKt; Sat, 18 Mar 2023 15:50:48 +0000 (UTC) (envelope-from chargen@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-1755e639b65so8881910fac.3; Sat, 18 Mar 2023 08:50:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679154647; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=1xsoAJM3hHUG6C7aam0t0wIIZBau6GntZ99PEqsfl/8=; b=WnUN54EVhVUSeFoDXGwNFEXCxGRB6tv0ou9j/Mr6j5wVht+SqsaFQqqth2nxgc6h2x Is6lK9iL6DJh+KFlVKKAPAVrrwW0BT94Feq+MkWeIXkSY3PZLDGYUIXSZzDSGATjb5Jz gMzBUSMtozFicqGjtju8tsCkKPQDMv3HoAb4OV+TOchu7HJRrEXkbVDj4yqpZhiIP6KV kDWEwp5BmkJOeoIIUrI8iHF/iRUZ9ZnNZQscCv9y949EQoS6pCQHeYHYbpTbpaax5SWn j3iT3KBaje3nn8Z3G6ll03kCArzGsehvypV1j/aMNs2f3i/W5EIofXxNx8Kng/oJl7Xe O90g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679154647; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=1xsoAJM3hHUG6C7aam0t0wIIZBau6GntZ99PEqsfl/8=; b=JDtQQUvU6O7QU2tosMt+lpj1tftkxdCGShjQI2YQ2WxXylX9aKG2BF4rYeVDbkgaks BKX9k9jWVpdXwRsI0dUk6nJECuN1YHbYMdywF3YUacvy2v6C+nGRSgkoKrS5K37IG7p8 8JLvfiEK9dK7HPNWZKCLYOISiVFIuGeJ+O225u6oSh8w4KODv1Xil3xvSj73DGFoK6XC 8mYSjbm1e3xnhwv6ZUFAciZ7NMB28pIxMuBns0Q/cgxdfv/Yw0Gh+Sy/l9N1de5Ns9q2 f9Sthlt+PsIq2oY/HCE51ZGjVh6b1+n2VmG8Q3Rfv3e0WY8V2kxhwadn3Jq+XIkx7Poj KqTQ== X-Gm-Message-State: AO0yUKW5nkDVpbBb6ShAHPyqzYBWELA5sEHCSoaz3nH9O9pPCIO+1ke8 loi/4Nchp8IO2T0BK8OflipFwcJ6vaEXqhXl9a9V9UqXydcrmg== X-Google-Smtp-Source: AK7set/cmyIrfD1yGzZK2rHlA2lE6eH0IZ1pOpHiD+vN3Hr2wkQMohE2Q0mwjznxPn+CMTZD+27GGHnxDDtUP4yduiY= X-Received: by 2002:a05:6870:13d1:b0:17a:d3d2:dc75 with SMTP id 17-20020a05687013d100b0017ad3d2dc75mr503106oat.3.1679154647410; Sat, 18 Mar 2023 08:50:47 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <2cf7d953-2493-9673-5ea3-fba22c694015@freebsd.org> <20230317181547.4d75e897@hal.tijl.coosemans.org> In-Reply-To: From: Chargen Date: Sat, 18 Mar 2023 16:50:29 +0100 Message-ID: Subject: Re: I just updated to main-n261544-cee09bda03c8 based (via source) and now /etc/machine-id and /var/db/machine-id disagree ; more To: Mark Millard Cc: Colin Percival , =?UTF-8?Q?T=C4=B3l_Coosemans?= , Current FreeBSD , FreeBSD-STABLE Mailing List , Baptiste Daroussin Content-Type: multipart/alternative; boundary="000000000000482b7205f72ea882" X-Rspamd-Queue-Id: 4Pf57X3YHNz3CKt X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2001:4860:4864::/48, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000482b7205f72ea882 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable oh, just timekeeping && tell me that uniqueid is oracled with /dev/random Well it's not that there are Great many things depending on synchronizing Jit, wit,NTP cloudcovered Just in case, anything can happen to stratum0 and however unlikely it seems, there is a future imagined for it, that has a protocollair White Rabbit node to node PTP for QKD whatever, I don't use the Q-word that often until the anticipated phenomena is witnessed. Till then none time progressing in any base will not leave this orbit from a QKD critical node topology. At least Not that wabbit, if it's to me. In the future, satellite nodes will have a passive addressing modes, it's covered in a transform, so many grants, ip Thanks, _ _ (_)(_) (,,) =3D()=3D ((__)\ _|L\_______/ Save The Math Lab Rats On Sat, Mar 18, 2023 at 2:25=E2=80=AFAM Mark Millard wr= ote: > 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 component not installed, skipped > ZFS filesystem version: 5 > ZFS storage pool version: features support (5000) > Installing updates... > install: ///var/db/etcupdate/current/etc/rc.d/growfs_fstab: No such file > or directory > install: ///var/db/etcupdate/current/etc/rc.d/var_run: No such file or > directory > install: ///var/db/etcupdate/current/etc/rc.d/zpoolreguid: No such file o= r > directory > Scanning //usr/share/certs/blacklisted for certificates... > Scanning //usr/share/certs/trusted for certificates... > rmdir: ///usr/tests/usr.bin/timeout: Directory not empty > done. > root@generic:~ # cat /etc/hostid /etc/mach* > cat: No match. > > It did not indicate the need for another reboot to > end up with a /etc/machine-id file. > > I tried "shutdown -r now" anyway. It did establish > an /etc/machine-id file during the reboot: > > # ls -Tld /etc/hostid /etc/machine-id > -rw-r--r-- 1 root wheel 37 May 12 08:46:21 2022 /etc/hostid > -rw-r--r-- 1 root wheel 33 May 13 09:46:56 2022 /etc/machine-id > > So the basic implementation is operational but just > lacks an indication of the need to reboot again. > > The date/time is because it is a RPi4B context (no > time of its own) and time is not automatically being > established via ntp, apparently. (I did not make such > adjustments to the snapshot before starting the > upgrade.) > > I do not know if any of the "install: ///var/db/etcupdate/ . . . " > lines or the rmdir line are important. > > It earlier indicated 5708 patches were fetched and that 377 > files were as well. > > =3D=3D=3D > Mark Millard > marklmi at yahoo.com > > > --000000000000482b7205f72ea882 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
oh, just = timekeeping && tell me that uniqueid is oracled with /dev/random Well it's not that there are Great many things depending on synchroni= zing=C2=A0Jit, wit,NTP cloudcovered=C2=A0Just in case, anything can happen = to stratum0 and however unlikely it seems, there is a future imagined for i= t, that has a=C2=A0protocollair=C2=A0White Rabbit =C2=A0node= to node PTP for QKD whatever, I don't use the Q-word that often until = the anticipated phenomena is witnessed. Till then none time = progressing in any base will not leave this orbit from a QKD critical node = topology. At least Not that wabbit, if it's to me.=C2=A0 In the future,= satellite nodes will have a passive addressing modes, it's covered=C2= =A0in a transform, so many grants, ip=C2=A0

Thanks,
=C2=A0 =C2=A0_=C2=A0 = _
=C2=A0 (_)(_)
=C2=A0 =C2=A0(,= ,)
=C2=A0 =C2=A0=3D()=3D
=C2=A0= ((__)\
=C2=A0 =C2=A0_|L\_______/
Save The Math Lab Rats


On = Sat, Mar 18, 2023 at 2:25=E2=80=AFAM Mark Millard <marklmi@yahoo.com> wrote:
The 13.1-RELEASE (snapshot) to 13.2-RC3 fr= eebsd-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 component not installed, skipped
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Installing updates...
install: ///var/db/etcupdate/current/etc/rc.d/growfs_fstab: No such file or= directory
install: ///var/db/etcupdate/current/etc/rc.d/var_run: No such file or dire= ctory
install: ///var/db/etcupdate/current/etc/rc.d/zpoolreguid: No such file or = directory
Scanning //usr/share/certs/blacklisted for certificates...
Scanning //usr/share/certs/trusted for certificates...
rmdir: ///usr/tests/usr.bin/timeout: Directory not empty
=C2=A0done.
root@generic:~ # cat /etc/hostid /etc/mach*
cat: No match.

It did not indicate the need for another reboot to
end up with a /etc/machine-id file.

I tried "shutdown -r now" anyway. It did establish
an /etc/machine-id file during the reboot:

# ls=C2=A0 -Tld /etc/hostid /etc/machine-id
-rw-r--r--=C2=A0 1 root=C2=A0 wheel=C2=A0 37 May 12 08:46:21 2022 /etc/host= id
-rw-r--r--=C2=A0 1 root=C2=A0 wheel=C2=A0 33 May 13 09:46:56 2022 /etc/mach= ine-id

So the basic implementation is operational but just
lacks an indication of the need to reboot again.

The date/time is because it is a RPi4B context (no
time of its own) and time is not automatically being
established via ntp, apparently. (I did not make such
adjustments to the snapshot before starting the
upgrade.)

I do not know if any of the "install: ///var/db/etcupdate/ . . . "= ;
lines or the rmdir line are important.

It earlier indicated 5708 patches were fetched and that 377
files were as well.

=3D=3D=3D
Mark Millard
marklmi at yahoo.com


--000000000000482b7205f72ea882--