-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manipulate efivars when installing via lzbt
#126
Comments
I didn't understand this part very well. |
If lzbt always manipulates efivars, we cannot run our rust test suite anymore. So we need to be able to disable manipulating efivars to have easy and quick tests for the rest of the system. |
This makes sense. Note that we have EFIVARS manipulation in our NixOS tests. :) |
Should we fork to |
Although there is some charm to re-implementing systemd functionality (because we can upstream it) I think we can and should use bootctl for now. I'll implement something. However I don't know how `bootctl can help with an A/B system for bootloaders. |
Awesome, I will let you do it then.
Not really, but it's okay :) |
We should manipulate the efivars when we install Lanzaboote to point the standard boot entry to the systemd-boot path. This should be implemented via a command line flag
that is disabled by default.OtherwiseWithout being able to disable manipulating efivars, testing becomes annoying (i.e. our rust unit tests) and it also makes building disk images much harder.The text was updated successfully, but these errors were encountered: