Date: Fri, 18 Jan 2019 17:34:36 +0300 From: Lev Serebryakov <lev@FreeBSD.org> To: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= <olivier@freebsd.org> Cc: Rebecca Cran <bcran@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: UEFI, loader.efi and /boot.config Message-ID: <e7f8d4e3-4c4b-1a1a-ebc2-5d8ea7f81c7f@FreeBSD.org> In-Reply-To: <CA%2Bq%2BTcp2%2BsavH1g0q3b9YQ9SW76iXZ2PA6wvj2ok-cUOndZeWw@mail.gmail.com> References: <etPan.5c413a8a.7a8e2073.13b3@freebsd.org> <eb14f962-1c13-cc77-0e8c-575028f7c5d7@FreeBSD.org> <CA%2Bq%2BTcp2%2BsavH1g0q3b9YQ9SW76iXZ2PA6wvj2ok-cUOndZeWw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --DqnfNMdQ0nr0XsmdHLI2MNZ7sBhH1jrWY Content-Type: multipart/mixed; boundary="C2oUOA8K5k9t2Z9Tg3T4THPnhLssB7FUx"; protected-headers="v1" From: Lev Serebryakov <lev@FreeBSD.org> Reply-To: lev@FreeBSD.org To: =?UTF-8?Q?Olivier_Cochard-Labb=c3=a9?= <olivier@freebsd.org> Cc: Rebecca Cran <bcran@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Message-ID: <e7f8d4e3-4c4b-1a1a-ebc2-5d8ea7f81c7f@FreeBSD.org> Subject: Re: UEFI, loader.efi and /boot.config References: <etPan.5c413a8a.7a8e2073.13b3@freebsd.org> <eb14f962-1c13-cc77-0e8c-575028f7c5d7@FreeBSD.org> <CA+q+Tcp2+savH1g0q3b9YQ9SW76iXZ2PA6wvj2ok-cUOndZeWw@mail.gmail.com> In-Reply-To: <CA+q+Tcp2+savH1g0q3b9YQ9SW76iXZ2PA6wvj2ok-cUOndZeWw@mail.gmail.com> --C2oUOA8K5k9t2Z9Tg3T4THPnhLssB7FUx Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 18.01.2019 17:03, Olivier Cochard-Labb=C3=A9 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? > =C2=A0Please, not, please support /boot.config. loader.conf could b= e too late > in case of serial consoles. >=20 > =C2=A0I wonder, why EFI/UEFI and GPt booting (which should be more = advanced) > is more limited than classic MBR/boot0 + boot1 + loader scheme :-( >=20 > =C2=A0Serial console support is worse. Selection of boot partition = is not > supported (as opposide to very-simple-516-bytes boot0!), and so on = :-( >=20 >=20 >=20 > Hi, > As an heavy nanobsd user on headless (serial/IPMI SoL) appliances, bein= g > 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. My case exactly. --=20 // Lev Serebryakov --C2oUOA8K5k9t2Z9Tg3T4THPnhLssB7FUx-- --DqnfNMdQ0nr0XsmdHLI2MNZ7sBhH1jrWY Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE+W0coLX0MYtnSzMK6rA8WL/cR48FAlxB4/xfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY5 NkQxQ0EwQjVGNDMxOEI2NzRCMzMwQUVBQjAzQzU4QkZEQzQ3OEYACgkQ6rA8WL/c R49igBAAtXPBDifQiqpnz4LSoJK/iv0bgdT1Vq8h1OjOXYEoZcAWdfD45/ZsMBcW 8ll0FF63Ry8+dUt+RoUJdACent6v8+TdCSTiGu+KI8zewAB0ZI/XgsgSkaQHfFLk WxLib84nstUy/NarSSc1Cr4ygCsfmjT9VGA1yJPCfVWccqByZ6Rs9Fjy7GOKrnrC Q88mDiRPIPfcQU+WngqY5M2ZWEOAt9PBCBmncS71uJMnicQcStUDUmyUoYxEtkdE mxJqgPlh/ejBh318qCaM7UZd6wHAEi/oVKyKHqy+9Su6xoEsw3RMjU9mDdOi92x5 3pfIsyCEK6tjiJ40zuTmUVszMrgzmnPHiAsigUjS0d2Sf/zPOIqZ0EMmfyQxk6Dw aHdxH/5+Zqs28v5TWtKl8mpolBxlGI73O7jgw/6kRu5qbEDIPTkLRJzvPfI2cZL/ YF3K6n3MgH4nwZoX3Z5vh8I8moml67zVIg18M9Ytz7zh5HGZMzT1usKlbCKVp5Y8 65YGjoJGCXgLsrhQPqKWUyG2asf2Es5F+DIFsNFw1L46I32yx/cQq0F2LS8vbmN2 wJwdLGKVAcyoMdKAVb6PyfGVmDaJd2Lfr9DWJeMGhP3wsH3IVs5AEthJEXYKG7Ty 1cNRwPlSi9202gglMC7JL3Nd4E4GE0v/GtDhFmtMPMm+hzU0JUg= =Sc+R -----END PGP SIGNATURE----- --DqnfNMdQ0nr0XsmdHLI2MNZ7sBhH1jrWY--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e7f8d4e3-4c4b-1a1a-ebc2-5d8ea7f81c7f>