9163d0a4e7
Currently some of the code base check for the variable presence before removing it, and some do not. More so, in all cases (being updated) we're dealing with non-volatile variables where changing those attribute to NVRAM wear out. From what information I could find, there is no definitive answer if the UEFI implementation will write to the NVRAM even when the variable is missing. So add a simple helper that checks for the variable presence before removing it. While also having a bit cleaner API than the current efivar_set(..., NULL, ...); efivar_unset() follows the design from efivar_set*() where it returns an EFI_STATUS even though its (presently) unused. v2: - add inline comment, use early return v3: - typos? typos! Signed-off-by: Emil Velikov <emil.velikov@collabora.com> (cherry picked from commit 5ee3c914a4e904567e66654177b07777dde0d100) (cherry picked from commit 917569e3c1e1361d2c7bac584b99e075a4cb0b0d)
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.