From owner-freebsd-current@freebsd.org Fri Jan 18 14:11:20 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 B3C73149F05A for ; Fri, 18 Jan 2019 14:11:20 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 5A5AE91599; Fri, 18 Jan 2019 14:11:20 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f48.google.com (mail-lf1-f48.google.com [209.85.167.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id E6E1329EA; Fri, 18 Jan 2019 14:11:19 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f48.google.com with SMTP id i26so10623750lfc.0; Fri, 18 Jan 2019 06:11:19 -0800 (PST) X-Gm-Message-State: AJcUukdtcYWKM4Fk3JFqRRBRjJ9BlaMlRTKlcRCMlu8VSkv7Vs33bGZx lOm0GrgbtvUdZHV1QyFu8yJdKD6Z7OKfOH8RfCw= X-Google-Smtp-Source: ALg8bN5sMtxLTLAE7fz3gUmoa9MtIy1HyRsMPJqzwzNJYsgDNCnJ8SQE7VJBsELflavgWeyC+lpxu0V9YUMHBtYS6Hg= X-Received: by 2002:a19:cd50:: with SMTP id d77mr12612598lfg.125.1547820678299; Fri, 18 Jan 2019 06:11:18 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Kyle Evans Date: Fri, 18 Jan 2019 08:10:56 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: UEFI, loader.efi and /boot.config To: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Cc: lev@freebsd.org, Rebecca Cran , FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 5A5AE91599 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.984,0]; NEURAL_HAM_LONG(-1.00)[-0.999,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US] 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:11:20 -0000 On Fri, Jan 18, 2019 at 8:04 AM Olivier Cochard-Labb=C3=A9 wrote: > > On Fri, Jan 18, 2019 at 2:10 PM Lev Serebryakov wrote: > > > On 18.01.2019 5:31, Rebecca Cran wrote: > > > > > > > I was wondering if people will expect /boot.config to still be read a= nd > > 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 forgott= en > > about? > > Please, not, please support /boot.config. loader.conf could be too lat= e > > in case of serial consoles. > > > > I wonder, why EFI/UEFI and GPt booting (which should be more advanced) > > is more limited than classic MBR/boot0 + boot1 + loader scheme :-( > > > > Serial console support is worse. Selection of boot partition is not > > supported (as opposide to very-simple-516-bytes boot0!), and so on :-( > > > > > > > Hi, > As an heavy nanobsd user on headless (serial/IPMI SoL) appliances, being > able to early select the boot partition by MBR/boot0 and configuring earl= y > message redirection (with boot.config) is very useful. > Not being able to do the same with GPT/EFI is the feature preventing me t= o > upgrade my nanobsd image scheme. > So if there is a way of displaying EFI boot loader messages over > serial/IPMI SoL and selecting boot partiton, I've no objection to remove > boot.config support. > There's some UEFI var that's supposed to serve the same kind of purpose as /boot.config -- early boot parameters. I think we had discussed implementing this at some point, but this hasn't been done yet as far as I've seen. Would this be usable on your appliances?