f2c2b7ace9
EC2 instances don't have a console, so it's pointless to start emergency mode if a mount fails. (This happened to me with an encrypted filesystem where the key wasn't sent on time using "charon send-keys".) Better to cross fingers and continue booting.
24 lines
634 B
Nix
24 lines
634 B
Nix
# Common configuration for headless machines (e.g., Amazon EC2
|
|
# instances).
|
|
|
|
{ config, pkgs, ... }:
|
|
|
|
with pkgs.lib;
|
|
|
|
{
|
|
sound.enable = false;
|
|
boot.vesa = false;
|
|
boot.initrd.enableSplashScreen = false;
|
|
services.ttyBackgrounds.enable = false;
|
|
|
|
# Don't start a tty on the serial consoles.
|
|
systemd.services."serial-getty@ttyS0".enable = false;
|
|
systemd.services."serial-getty@hvc0".enable = false;
|
|
|
|
# Since we can't manually respond to a panic, just reboot.
|
|
boot.kernelParams = [ "panic=1" "boot.panic_on_fail" ];
|
|
|
|
# Don't allow emergency mode, because we don't have a console.
|
|
systemd.enableEmergencyMode = false;
|
|
}
|