Date: Sat, 18 Mar 2023 08:55:09 -0600 From: Warner Losh <imp@bsdimp.com> To: Mark Millard <marklmi@yahoo.com> Cc: Colin Percival <cperciva@freebsd.org>, =?UTF-8?Q?T=C4=B3l_Coosemans?= <tijl@freebsd.org>, Current FreeBSD <freebsd-current@freebsd.org>, FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>, Baptiste Daroussin <bapt@freebsd.org> Subject: Re: I just updated to main-n261544-cee09bda03c8 based (via source) and now /etc/machine-id and /var/db/machine-id disagree ; more Message-ID: <CANCZdfqm4=RbY7viBJGZP9C1=qp0QgbfVTEe-8btDOQPsiHuWA@mail.gmail.com> In-Reply-To: <ADAA8C68-6154-4DAA-BDC9-BC8B8845E349@yahoo.com> References: <DCAD189B-1CBA-4D5B-B6DB-948A77AC723D@yahoo.com> <2cf7d953-2493-9673-5ea3-fba22c694015@freebsd.org> <20230317181547.4d75e897@hal.tijl.coosemans.org> <C18AED00-6CCF-4140-A0AE-B947521E422A@yahoo.com> <D8F42EA8-6105-4E0A-961F-916D61589B98@yahoo.com> <91950753-BDE0-45D5-B0B9-42782BD75C47@yahoo.com> <ADAA8C68-6154-4DAA-BDC9-BC8B8845E349@yahoo.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Fri, Mar 17, 2023 at 9:53 PM Mark Millard <marklmi@yahoo.com> 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. > 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 [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Mar 17, 2023 at 9:53 PM Mark Millard <<a href="mailto:marklmi@yahoo.com">marklmi@yahoo.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> This may all be fine. But it still leaves me expecting<br> that there should be man page(s) covering these hostid<br> and machine-id files and how they should be handled to<br> match the usages to which they are put, such as the nfs<br> use that was referenced. A note/reminder to look up<br> that material could also be relevant.<br></blockquote><div><br></div><div>It would be great if we could document this. I too recently</div><div>ran into a mismatch. If you load the /etc/hostid so that the</div><div>code in jail0_init picks it up and sets the host uuid, then</div><div>/etc/rc.d/hostid, enabled by default, will come along and</div><div>see there's no smbios.system.uuid and generate a new</div><div>uuid and smack that bad-boy into the kern.hostuuid sysctl</div><div>unconditionally. It was easy enough for me to work</div><div>around this by setting smbios.system.uuid in the boot</div><div>env that I was booting from, though. <br></div><div><br></div><div>Nothing to do with the upgrade, just that we have</div><div>multiple mechanisms to specify this stuff, and the code</div><div>we use today is somewhat less than robust to cover all</div><div>the cases that should be supported, but wind up being</div><div>buggy.</div><div><br></div><div>Warner<br></div></div></div>help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqm4=RbY7viBJGZP9C1=qp0QgbfVTEe-8btDOQPsiHuWA>