nixpkgs-suyu/nixos/modules/profiles/headless.nix

# Common configuration for headless machines (e.g., Amazon EC2
# instances).

{ config, lib, pkgs, ... }:

with lib;

{
  sound.enable = false;
  boot.vesa = false;

  # Don't start a tty on the serial consoles.
  systemd.services."serial-getty@ttyS0".enable = false;
  systemd.services."serial-getty@hvc0".enable = false;
  systemd.services."getty@tty1".enable = false;
  systemd.services."autovt@".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;
}
* Disable stuff like ALSA and the splash screen in headless setups (like EC2 instances). svn path=/nixos/trunk/; revision=30192 2011-11-02 17:10:30 +01:00			`# Common configuration for headless machines (e.g., Amazon EC2`
			`# instances).`

Rewrite ‘with pkgs.lib’ -> ‘with lib’ Using pkgs.lib on the spine of module evaluation is problematic because the pkgs argument depends on the result of module evaluation. To prevent an infinite recursion, pkgs and some of the modules are evaluated twice, which is inefficient. Using ‘with lib’ prevents this problem. 2014-04-14 16:26:48 +02:00			`{ config, lib, pkgs, ... }:`
* On headless systems, disable the emergency shell and redirect mountall output to the standard Upstart job log file (/var/log/upstart/mountall). svn path=/nixos/trunk/; revision=34138 2012-05-16 17:08:44 +02:00
Rewrite ‘with pkgs.lib’ -> ‘with lib’ Using pkgs.lib on the spine of module evaluation is problematic because the pkgs argument depends on the result of module evaluation. To prevent an infinite recursion, pkgs and some of the modules are evaluated twice, which is inefficient. Using ‘with lib’ prevents this problem. 2014-04-14 16:26:48 +02:00			`with lib;`
* On headless systems, disable the emergency shell and redirect mountall output to the standard Upstart job log file (/var/log/upstart/mountall). svn path=/nixos/trunk/; revision=34138 2012-05-16 17:08:44 +02:00
* Disable stuff like ALSA and the splash screen in headless setups (like EC2 instances). svn path=/nixos/trunk/; revision=30192 2011-11-02 17:10:30 +01:00			`{`
			`sound.enable = false;`
			`boot.vesa = false;`
In headless deployments, don't start agetty on the console 2012-10-30 13:52:12 +01:00
			`# Don't start a tty on the serial consoles.`
Rename ‘boot.systemd’ to ‘systemd’ Suggested by Mathijs Kwik. ‘boot.systemd’ is a misnomer because systemd affects more than just booting. And it saves some typing. 2013-01-16 12:33:18 +01:00			`systemd.services."serial-getty@ttyS0".enable = false;`
			`systemd.services."serial-getty@hvc0".enable = false;`
Don't start getty@tty1 on headless machines (like EC2) Backport: 14.04 2014-05-05 15:54:38 +02:00			`systemd.services."getty@tty1".enable = false;`
			`systemd.services."autovt@".enable = false;`
* In EC2 instances, a kernel panic should cause a reboot, and a problem in stage 1 should cause a panic. (Actually, the latter should probably kill the instance since we can't repair it anyway...) svn path=/nixos/trunk/; revision=30215 2011-11-03 21:11:11 +01:00
			`# Since we can't manually respond to a panic, just reboot.`
Give our kernel parameters a common prefix ("boot.*") 2013-01-09 22:49:26 +01:00			`boot.kernelParams = [ "panic=1" "boot.panic_on_fail" ];`
Don't start emergency mode on EC2 instances 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. 2013-01-21 21:01:48 +01:00
			`# Don't allow emergency mode, because we don't have a console.`
			`systemd.enableEmergencyMode = false;`
* Disable stuff like ALSA and the splash screen in headless setups (like EC2 instances). svn path=/nixos/trunk/; revision=30192 2011-11-02 17:10:30 +01:00			`}`