From owner-freebsd-arch@freebsd.org Wed Mar 27 14:25:23 2019 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2E201551722 for ; Wed, 27 Mar 2019 14:25:22 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 78A5A76EA4 for ; Wed, 27 Mar 2019 14:25:22 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3904D155171F; Wed, 27 Mar 2019 14:25:22 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2644D155171E; Wed, 27 Mar 2019 14:25:22 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BFB8176EA1; Wed, 27 Mar 2019 14:25:21 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f181.google.com (mail-lj1-f181.google.com [209.85.208.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 57E7713696; Wed, 27 Mar 2019 14:25:21 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f181.google.com with SMTP id j89so14594153ljb.1; Wed, 27 Mar 2019 07:25:21 -0700 (PDT) X-Gm-Message-State: APjAAAUurQXbdqP8vJjYgjo+EPMGzPWVq49BKkrq6waT/sAy1XqFwxpJ EpRQCEjUOyPqZ613EXeKguaL0KFVZRUJfyRoz2c= X-Google-Smtp-Source: APXvYqwS1CUpIdeO07lEN+q/BuhbrAmHzYjuARonsVxmYhE0IVjEdR+5kv0YMJ/ASPqH1AUJhrDBCWQvzlzcnMIKxo0= X-Received: by 2002:a2e:5c7:: with SMTP id 190mr19336874ljf.108.1553696719850; Wed, 27 Mar 2019 07:25:19 -0700 (PDT) MIME-Version: 1.0 References: <0828a41a-c25d-37a2-25b3-82c35c9a5c5d@bluestop.org> <201903270847.x2R8lMxc088823@gndrsh.dnsmgr.net> In-Reply-To: <201903270847.x2R8lMxc088823@gndrsh.dnsmgr.net> From: Kyle Evans Date: Wed, 27 Mar 2019 09:25:05 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Adding a new efi-update-loader script: need help understanding Makefile.inc1 for "make installworld" To: "Rodney W. Grimes" Cc: Rebecca Cran , Konstantin Belousov , "freebsd-arch@freebsd.org" , FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: BFB8176EA1 X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.97)[-0.966,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Mar 2019 14:25:23 -0000 On Wed, Mar 27, 2019 at 3:47 AM Rodney W. Grimes wrote: > > > On 3/26/19 12:21 AM, Rodney W. Grimes wrote: > > > > > > > > The current BTX 1.1 is bit rot, that value has not changed in ages > > > and tells me nothing about what boot code I am running, why do we > > > even output it? > > > > > > Sure, but the fact it shows up as "FreeBSD/amd64 EFI loader, Revision > > 1.1" in "strings /boot/loader.efi" shows one way we could easily embed a > > useful version number. > > Please go implement the placing of the version that is used to > cause uname -U to output 1200086 or whatever from /usr/sbin/uname > at build time, which is not an issue at all as far as reproducabile > builds as that version number is the same no mater how many times you > run the build. > > This is the current defining value that says your kernel is compatible > with userland and should also be the defining value for if your boot > code is also compatible. > This feels slightly wrong/misleading. We change loader -> kernel handoff far, far, far less frequently than we change userland <-> kernel compatibility. I don't have any constructive feedback otherwise, though, and it does at least provide an indicator of how old your boot bits are relative to the rest of the world.