From nobody Sat Mar 18 14:55:09 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 4Pf3vT0mwlz3yfXx for ; Sat, 18 Mar 2023 14:55:17 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 4Pf3vT0C0cz4KS0 for ; Sat, 18 Mar 2023 14:55:16 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ed1-x536.google.com with SMTP id ek18so31003134edb.6 for ; Sat, 18 Mar 2023 07:55:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20210112.gappssmtp.com; s=20210112; t=1679151315; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=yfAlfxqUZTi6nvTIytuVUfE1700OhzxwkGYFPzEP85k=; b=1Fd9H2ceVYku+Aqn0TeXbvEI8DrwNBuqH9LcqoUyQ/sAZgVLhLv3T3Qf4CYJ4wiNX8 iqAVcYs4vllc8UxF99tHDec3vn6kZd45tIm+lPVmVX2UdrPdj2IAVhoWEQYXIR9ubNQ9 wmH91uc3tk4RGWjyLqfuGqexZrJ0X0V8XffXjI+jIs0ZjdndC1HIBkSBWec1PLGxZN// WDjHs3qPI7PgNrAgLFyne7jNZknMTgHfvyLBnHIXc4l+OFeDTo0a09X/ivqPgbLi78MO ymV15eavE1R2bmKc3Uj5uTGXXBMCFcCLl4F5AmZE2RP8U7HfuYgf5hczg4mPkIrG5Rj8 S3Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679151315; 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=yfAlfxqUZTi6nvTIytuVUfE1700OhzxwkGYFPzEP85k=; b=acDO2NICWcVitWWwCinHcKi1Xt8pEVcYLB0K/OTu+JrdFJBRrbXGEbcjWn7yvstpuB rMszXZNAWz9th1AO2LJ+c44EcJuY/wO1crlvWqh09kbbQcmKvc8frwhoLQfZ+8+xju5q QU7EX2W7V6EFQM65KzYk/y6KdtQnt7+o9jVgdgWkRv08h85nsoa7lxGfdMKfMOOQ3aW5 KYet3lAc3SkJie15MWpGUTzh4tz8+t1En79z1ogCZOuYcObvUOCC0hY+bOia7zwNjGiB xuy4OeKFiVn6AisQz1TjQcI/I9O9JEGWF1fCa6SbPbpaFY4c2hBbSX+8d7lFl9G1rBG0 vp0A== X-Gm-Message-State: AO0yUKXvArZtc0Xp+c2zUWmF6n/fMBG/lLYrWpngRVpbzqiKHzZY6t8U iawsMgvf3URY7Uv/d2GkQFBAY7Sf3+JP8kKKWzDazGg6kWrtTYaK X-Google-Smtp-Source: AK7set9zzpmQWxmdGexFY6r4txeOUDYKK7zcunbWt179ldAz1/RuWpEbGl3xFnjIlKQPexEUfaXK4FggxcS1t9WriOg= X-Received: by 2002:a17:906:9c96:b0:931:f8b1:4472 with SMTP id fj22-20020a1709069c9600b00931f8b14472mr1323838ejc.2.1679151315550; Sat, 18 Mar 2023 07:55:15 -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> <91950753-BDE0-45D5-B0B9-42782BD75C47@yahoo.com> In-Reply-To: From: Warner Losh Date: Sat, 18 Mar 2023 08:55:09 -0600 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="000000000000b01d9e05f72de1ef" X-Rspamd-Queue-Id: 4Pf3vT0C0cz4KS0 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000b01d9e05f72de1ef Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Mar 17, 2023 at 9:53=E2=80=AFPM Mark Millard wr= ote: > This may all be fine. But it still leaves me expecting > that there should be man page(s) covering these hostid > and machine-id files and how they should be handled to > match the usages to which they are put, such as the nfs > use that was referenced. A note/reminder to look up > that material could also be relevant. > It would be great if we could document this. I too recently ran into a mismatch. If you load the /etc/hostid so that the code in jail0_init picks it up and sets the host uuid, then /etc/rc.d/hostid, enabled by default, will come along and see there's no smbios.system.uuid and generate a new uuid and smack that bad-boy into the kern.hostuuid sysctl unconditionally. It was easy enough for me to work around this by setting smbios.system.uuid in the boot env that I was booting from, though. Nothing to do with the upgrade, just that we have multiple mechanisms to specify this stuff, and the code we use today is somewhat less than robust to cover all the cases that should be supported, but wind up being buggy. Warner --000000000000b01d9e05f72de1ef Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Mar 17, 2023 at 9:53=E2=80=AF= PM Mark Millard <marklmi@yahoo.com<= /a>> wrote:
This may all be fine. But it still leaves me expecting
that there should be man page(s) covering these hostid
and machine-id files and how they should be handled to
match the usages to which they are put, such as the nfs
use that was referenced. A note/reminder to look up
that material could also be relevant.


=
Nothing to do with the upgrade, just that we have
multiple m= echanisms to specify this stuff, and the code
we use today is som= ewhat less than robust to cover all
the cases that should be supp= orted, but wind up being
buggy.

Warner
--000000000000b01d9e05f72de1ef--