Eelco Dolstra f2c2b7ace9 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
..
loader	Merge remote-tracking branch 'origin/systemd'	2013-01-21 12:45:50 +01:00
kernel.nix	Rename ‘system.build.systemd’ to ‘systemd.package’	2013-01-16 13:17:57 +01:00
luksroot.nix	LuksRoot: fix crypto module list. This one should finally work well.	2013-01-14 06:46:46 +02:00
modprobe.nix	systemd: Use the kernel modules from /run/booted-system	2012-08-14 17:09:44 -04:00
shutdown.nix	Rename ‘boot.systemd’ to ‘systemd’	2013-01-16 12:33:18 +01:00
stage-1-init.sh	Give our kernel parameters a common prefix ("boot.*")	2013-01-09 22:53:44 +01:00
stage-1.nix	Rename ‘system.build.systemd’ to ‘systemd.package’	2013-01-16 13:17:57 +01:00
stage-2-init.sh	Give our kernel parameters a common prefix ("boot.*")	2013-01-09 22:53:44 +01:00
stage-2.nix	Set uniqueness constraint on boot.devShmSize etc.	2012-10-23 07:50:23 -04:00
systemd-unit-options.nix	For some units, use "systemctl restart" rather than "systemctl stop/start"	2013-01-05 01:05:25 +01:00
systemd.nix	Don't start emergency mode on EC2 instances	2013-01-21 21:01:48 +01:00