From owner-freebsd-current@freebsd.org Fri Jan 18 14:03:55 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 22BC3149EBFA for ; Fri, 18 Jan 2019 14:03:55 +0000 (UTC) (envelope-from olivier@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 B96169116A; Fri, 18 Jan 2019 14:03:54 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: from mail-pl1-f172.google.com (mail-pl1-f172.google.com [209.85.214.172]) (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: olivier/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 54D0F29E9; Fri, 18 Jan 2019 14:03:54 +0000 (UTC) (envelope-from olivier@freebsd.org) Received: by mail-pl1-f172.google.com with SMTP id e11so6395723plt.11; Fri, 18 Jan 2019 06:03:54 -0800 (PST) X-Gm-Message-State: AJcUukeDboiakRohwC2pi1k87THvaiFAmdvk5NQXdvMbVnTCeHUjOOQo c6ASwfFyy1CRmEIBcaKXWzx1H0XgstF6onoUA08= X-Google-Smtp-Source: ALg8bN4MixJVi01MvqkkrxvksCfbgQwx4rlO323fkb1l/O1rQIG+gkUBNHCsM8akmTlAnzbqTgWol5GysBn2GVhSzVQ= X-Received: by 2002:a17:902:8306:: with SMTP id bd6mr19387640plb.217.1547820233229; Fri, 18 Jan 2019 06:03:53 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= Date: Fri, 18 Jan 2019 15:03:41 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: UEFI, loader.efi and /boot.config To: lev@freebsd.org Cc: Rebecca Cran , FreeBSD Current X-Rspamd-Queue-Id: B96169116A X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[freebsd.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.99)[-0.987,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] Content-Type: text/plain; charset="UTF-8" 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 14:03:55 -0000 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 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? > Please, not, please support /boot.config. loader.conf could be too late > 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 early message redirection (with boot.config) is very useful. Not being able to do the same with GPT/EFI is the feature preventing me to 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. Regards, Olivier