Date: Tue, 4 Aug 2015 09:29:55 -0400 From: Eric McCorkle <eric@metricspace.net> To: Ganael Laplanche <ganael.laplanche@corp.ovh.com>, Eric McCorkle <emc2@metricspace.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Boot loader arguments (was: ZFS support for EFI) Message-ID: <55C0BE53.4080406@metricspace.net> In-Reply-To: <201508031532.44478.ganael.laplanche@corp.ovh.com> References: <201508031532.44478.ganael.laplanche@corp.ovh.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --5Kl2dHXOuk2lmK1MPHMgfsTaW8jfmhrpM Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I had thought it would be necessary in order to point the loader at the correct ZFS partition (linux does require this), but apparently loader figures out what partition it should be dealing with just fine. I don't doubt it would be a good change, and loader could use some refactoring IMO, but I'd like to keep the changesets as small as possible= =2E On 08/03/2015 09:32 AM, Ganael Laplanche wrote: > Hi Eric, >=20 > I am replying to this -quite old now- post : >=20 > https://lists.freebsd.org/pipermail/freebsd-hackers/2015-March/047486.h= tml >=20 >> More importantly, the EFI loader doesn't seem to make use of its >> command-line arguments at all. But a ZFS-enabled loader would really >> need the ability to take arguments from boot1 (or grub, or whatever >> else). >=20 > where you were suggesting it would be interesting for the EFI loader to= make=20 > use of its arguments, which is still not the case. >=20 > We've faced a similar problem here, where we needed the EFI loader be a= ble to=20 > locally override the root-path offered through BOOTP. A quick fix would= have=20 > been to hardcode the root-path but instead we chose to pass it through = an=20 > argument to the loader (which then sets a new environment variable :=20 > dhcp.root-path.override). >=20 > Find attached the two -simple- patches that allow such an operation. I = don't=20 > know if they can be interesting for you or for upstream inclusion (thou= gh they=20 > are probably *not* ready for direct inclusion yet). >=20 > Best regards, >=20 --5Kl2dHXOuk2lmK1MPHMgfsTaW8jfmhrpM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJVwL5YAAoJECuREQPg1IcEGMsP/jdA8HT0haLvP3+VTdguQDLw CTRP8VTCrRxDT2mqCXVZN7Fx+wVUEfUKdU3nEsj4YYfLF0TR5uq5OVMKFwblmNE+ UausvlTvD7XHfgqrDjpzScwvMxSXHZeVEEwQ9cbJooEvn1tJq7EVGI/KKBk+LF5K wSeFezbbbLYY9xnt8IVGRPkH6YPsckJtyS5m1PMOgX0Kjvi6rCMbte5a4GkY/pVD 3OfFX3mKXoIdnIBm1DuS60JfquQbsz/Pt7ntKZmILqAbseFFG2kiOsSqFaxAFHND +ZpcbGjJi+LdCAD2Xnp3JMQtPKjqHnODXH4qz9ciUielXH15qYhfZhYafY0l/RAM bMm2NEWNW+bh6nDuXBejmWLNA7i849eamHvTraT6v9YBFnJB/1Stp7mu5B/DPg2n MApqC79VKtd4oZws+Y9H7D0tbo7xYETPhP/xejjj9cXaD9izIqbRiI01tFSNm3Kx tSpFSLJDvfEnLa03fgLOsFFxjAyZNpHEaBsYMW017a7M7StBSRw3V3zA9DXXWt4f 64BrASDiTBV62YJG+EwcK0ADbtAhHAW6G7Yss3SPH1XTqfq+gDb6W7MOq+SFeb4i 2FEh41MIFbh+biat6dbU9AemCRtYSDTct6NFpHvitaLvmgGhm3FPLjL7/XGtZlEF +gdquBfPp5dBvkt838l7 =Mvzu -----END PGP SIGNATURE----- --5Kl2dHXOuk2lmK1MPHMgfsTaW8jfmhrpM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55C0BE53.4080406>