Boot loader arguments (was: ZFS support for EFI)
Eric McCorkle
eric at metricspace.net
Tue Aug 4 13:29:53 UTC 2015
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.
On 08/03/2015 09:32 AM, Ganael Laplanche wrote:
> Hi Eric,
>
> I am replying to this -quite old now- post :
>
> https://lists.freebsd.org/pipermail/freebsd-hackers/2015-March/047486.html
>
>> 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).
>
> where you were suggesting it would be interesting for the EFI loader to make
> use of its arguments, which is still not the case.
>
> We've faced a similar problem here, where we needed the EFI loader be able to
> locally override the root-path offered through BOOTP. A quick fix would have
> been to hardcode the root-path but instead we chose to pass it through an
> argument to the loader (which then sets a new environment variable :
> dhcp.root-path.override).
>
> Find attached the two -simple- patches that allow such an operation. I don't
> know if they can be interesting for you or for upstream inclusion (though they
> are probably *not* ready for direct inclusion yet).
>
> Best regards,
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20150804/7ce11b80/attachment.bin>
More information about the freebsd-hackers
mailing list