From owner-freebsd-current@freebsd.org  Fri Jan 18 07:48:06 2019
Return-Path: <owner-freebsd-current@freebsd.org>
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 09D771492AE4
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 18 Jan 2019 07:48:06 +0000 (UTC) (envelope-from pi@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::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 54F038206D;
 Fri, 18 Jan 2019 07:48:05 +0000 (UTC) (envelope-from pi@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD))
 (envelope-from <pi@opsec.eu>)
 id 1gkOsk-000ICw-Cv; Fri, 18 Jan 2019 08:48:02 +0100
Date: Fri, 18 Jan 2019 08:48:02 +0100
From: Kurt Jaeger <pi@opsec.eu>
To: Rebecca Cran <bcran@freebsd.org>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: UEFI, loader.efi and /boot.config
Message-ID: <20190118074802.GA54920@home.opsec.eu>
References: <etPan.5c413a8a.7a8e2073.13b3@freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <etPan.5c413a8a.7a8e2073.13b3@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Jan 2019 07:48:06 -0000

Hi!

> With a recent change I made for UEFI, we now install loader.efi onto the ESP and don???t run boot1. That means that /boot.config is no longer read, and so console settings need to be put in /boot/loader.conf

Which change is that ?

> I was wondering if people will expect /boot.config to still be read and so 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?

I have quite a few systems using /boot.config, but can cope if I know about this.

-- 
pi@opsec.eu            +49 171 3101372                    One year to go !