Skip to content
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

nixos/kexec: don't clobber existing kexec-loaded kernel #60237

Merged
merged 2 commits into from May 6, 2019

Conversation

lheckemann
Copy link
Member

Motivation for this change
Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

Copy link
Contributor

@nh2 nh2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change is very welcome; I did not even know until now that systemctl kexec on NixOS had thrown away all the kernels I had manually loaded with kexec -l before!

@@ -13,6 +13,9 @@
path = [ pkgs.kexectools ];
script =
''
# Don't load the current system profile if we already have a kernel loaded
[[ 1 = "$(</sys/kernel/kexec_loaded)" ]] && exit
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if that's important here, but the below uses sh style ifs using [ ] instead of bash [[ ]]; you may want to use the same.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two parts to this:

  • https://mywiki.wooledge.org/BashFAQ/031 I generally prefer [[ except in contexts where the shell might not be bash (in this case it is!), because it's easier to use correctly
  • When it's a single command that's being run conditionally and it behaves correctly with set -e, I prefer && (or || as the case may be) over if because (IMHO) if results in unhelpful visual noise.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no opinion about what's better, my comment was only for the case that script does not imply bash.

nixos/modules/system/boot/kexec.nix Outdated Show resolved Hide resolved
@lheckemann lheckemann merged commit 864f4f0 into NixOS:master May 6, 2019
@lheckemann lheckemann deleted the kexec-no-clobber branch May 6, 2019 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants