From owner-freebsd-current@freebsd.org Fri Jan 18 14:14:11 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 696EA149F175 for ; Fri, 18 Jan 2019 14:14:11 +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 C8AEF918E3; Fri, 18 Jan 2019 14:14:10 +0000 (UTC) (envelope-from pi@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1gkUuR-000Ifq-As; Fri, 18 Jan 2019 15:14:11 +0100 Date: Fri, 18 Jan 2019 15:14:11 +0100 From: Kurt Jaeger To: Rebecca Cran Cc: FreeBSD Current Subject: Re: UEFI, loader.efi and /boot.config Message-ID: <20190118141411.GB54920@home.opsec.eu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 14:14:11 -0000 Hello, > 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? If the early boot messages are not displayed as Olivier mentioned, that would be fatal. On some systems no other output besides serial is useful. -- pi@opsec.eu +49 171 3101372 One year to go !