Comment 7 for bug 1398148

------- Comment From <email address hidden> 2015-02-23 19:21 EDT-------
(In reply to comment #8)
> (In reply to comment #7)
> > My point was that the late_command can run in the target, where the tools
> > are available and installed, there's no reason to have the tools also in the
> > installer environment to make this workaround go.
>
> Tomo, can you verify if you run the late command in the chroot, that we
> don't need to install nvram?

Ah now I recall!

So the issue is multifold.

We need to save off the bootorder information from before the installer runs in a preseed_early script. No tools exist at that point (nvram, etc.). So that's one problem (we manually wget it there).

Then, once install is done, we need to fix-up the boot-order. Yes, we could do this from the chroot, but then we don't have access to the data saved off in the preseed_early script. We could run a non-chroot'd command to just cp it up to the chroot and then use the system-installed nvram in the chroot. Instead, we chose to just fix the boot order outside the chroot (which again lacks the nvram command).

So, to recap:

1) We need access to the boot-order manipulation/reading tools in the preseed_early script.

2) We can either manipulate that preseed_early data in a chroot/non-chroot preseed_late script, but it's a moot point -- either we do it in the chroot using the installed tools, or we do it in a non-chroot using the tools that are required by 1).