From owner-freebsd-current@freebsd.org Fri Jan 18 02:31:46 2019 Return-Path: Delivered-To: freebsd-current@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 DF895148A559 for ; Fri, 18 Jan 2019 02:31:46 +0000 (UTC) (envelope-from bcran@freebsd.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 591CE6BCB5 for ; Fri, 18 Jan 2019 02:31:46 +0000 (UTC) (envelope-from bcran@freebsd.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id C563285CB2 for ; Thu, 17 Jan 2019 19:32:35 -0700 (MST) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id EbYOSienp7PI for ; Thu, 17 Jan 2019 19:32:35 -0700 (MST) Received: from macbex.int.bluestop.org.mail (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA for ; Thu, 17 Jan 2019 19:32:35 -0700 (MST) Date: Thu, 17 Jan 2019 19:31:38 -0700 From: Rebecca Cran To: FreeBSD Current Message-ID: Subject: UEFI, loader.efi and /boot.config MIME-Version: 1.0 X-Rspamd-Queue-Id: 591CE6BCB5 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.98 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.977,0]; ASN(0.00)[asn:7922, ipnet:96.64.0.0/11, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2019 02:31:47 -0000 With a recent change I made for UE=46I, we now install loader.efi onto th= e ESP and don=E2=80=99t run boot1. That means that /boot.config is no lon= ger read, and so console settings need to be put in /boot/loader.conf.=C2= =A0 I was wondering if people will expect /boot.config to still be read and s= o code should be added to loader to continue to parse it, or if loader.co= nf can be considered the correct place and boot.config forgotten about=3F= =E2=80=94=C2=A0 Rebecca Cran From owner-freebsd-current@freebsd.org Fri Jan 18 03:02:52 2019 Return-Path: Delivered-To: freebsd-current@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 42BF0148B668 for ; Fri, 18 Jan 2019 03:02:52 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 37A426D110; Fri, 18 Jan 2019 03:02:50 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id x0I32kBa026508; Fri, 18 Jan 2019 03:02:46 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id x0I32kTp026507; Thu, 17 Jan 2019 19:02:46 -0800 (PST) (envelope-from david) Date: Thu, 17 Jan 2019 19:02:46 -0800 From: David Wolfskill To: Rebecca Cran Cc: FreeBSD Current Subject: Re: UEFI, loader.efi and /boot.config Message-ID: <20190118030246.GV1142@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org, Rebecca Cran , FreeBSD Current References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Mm7SuNQsQ9gs8/y1" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.2 (2019-01-07) X-Rspamd-Queue-Id: 37A426D110 X-Spamd-Bar: --------- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of david@catwhisker.org designates 198.144.209.73 as permitted sender) smtp.mailfrom=david@catwhisker.org X-Spamd-Result: default: False [-9.11 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[current@freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:198.144.209.73]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[catwhisker.org]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-3.71)[ip: (-9.77), ipnet: 198.144.192.0/19(-4.82), asn: 7961(-3.86), country: US(-0.08)]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: mx.catwhisker.org]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[73.209.144.198.list.dnswl.org : 127.0.10.0]; NEURAL_HAM_SHORT(-0.99)[-0.993,0]; SIGNED_PGP(-2.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+]; ASN(0.00)[asn:7961, ipnet:198.144.192.0/19, country:US]; RCVD_TLS_LAST(0.00)[] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jan 2019 03:02:52 -0000 --Mm7SuNQsQ9gs8/y1 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 17, 2019 at 07:31:38PM -0700, Rebecca Cran wrote: >=20 > With a recent change I made for UEFI, we now install loader.efi onto the = ESP and don=E2=80=99t run boot1. That means that /boot.config is no longer = read, and so console settings need to be put in /boot/loader.conf.=C2=A0 > I was wondering if people will expect /boot.config to still be read and s= o code should be added to loader to continue to parse it, or if loader.conf= can be considered the correct place and boot.config forgotten about? > .... Does the above only apply to UEFI booting, or also to booting from BIOS/MBR? If the latter, I'd be OK with the change as long as it's adequately publicized ahead of time (e.g., a src/UPDATING entry & -- ideally -- a "heads-up" in current@). If the former, I'm less opinionated: none of my personal machines boot UEFI. I'd tend to assume that changing to UEFI will involve some (other) changes to how I do things anyway. (My build machine uses /boot.config to default to "verbose" booting, dual-console.) Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is more of an "existential" than "potential" threat to US security. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --Mm7SuNQsQ9gs8/y1 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAlxBQdZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 PclJNAf/aN/+CBgcmAy55d20KSVQfoDHzjqn8jwxjEc8bo+66OlpNMrp2ujXi/UX ZWwb9qiQkXoQtAL1Pjp4kY9AHYxxNAeNpkeySNds0blhJ/KXGoLLDjTmelZVwFSd NigiSnITqdRFKDZr9a0iJcCfxKo4vfJBIc5KTqHwSxxwDqMOboRkKb2mX2bAlAbG Fk+EJb9AVI63nIT2xzU13MprZewSk7f2HE4ymUBVC/KhHnCa+uwN4qeZL1z5mbm3 VLrwKYkVpBXQ8NBYNWZwfStUjjmCpaEL+/YKBHrVIX9te1IQMNmMvcRzFBGcQXan xyegpBY34Uacb79CA1AzohxwCdfjBA== =A1/A -----END PGP SIGNATURE----- --Mm7SuNQsQ9gs8/y1--