aszlig a333f7212e systemd: Fail if kernel features are missing. ... This has rendered my system unbootable, because I forgot to enable AUTOFS4 in my custom kernel. In addition to AUTOFS4, this includes (hopefully) all other kernel features needed by systemd, as listed in the README: REQUIREMENTS: Linux kernel >= 2.6.39 with devtmpfs with cgroups (but it's OK to disable all controllers) optional but strongly recommended: autofs4, ipv6 Autofs4 is not a requirement here, but in our case it turns out that the system is not able to boot properly with a LUKS-enabled system (or at least not on _my_ system). Signed-off-by: aszlig <aszlig@redmoonstudios.org>		2012-11-06 11:25:43 +01:00
..
loader	The efi boot stub code should only be run if it is enabled	2012-08-09 10:37:43 -04:00
kernel.nix	Ignore systemd-modules-load errors	2012-10-12 17:39:06 -04:00
luksroot.nix	LUKS root: Fix key file check	2012-08-02 11:39:31 +02:00
modprobe.nix	systemd: Use the kernel modules from /run/booted-system	2012-08-14 17:09:44 -04:00
shutdown.nix	Fix a hang during shutdown	2012-08-14 16:45:50 -04:00
stage-1-init.sh	Merge remote-tracking branch 'origin/master' into systemd	2012-09-28 11:35:27 -04:00
stage-1.nix	Turn fileSystems into an attribute set	2012-11-02 18:02:12 +01:00
stage-2-init.sh	Remove outdated comment about EC2 booting into stage-2 directly	2012-11-02 17:07:53 +01:00
stage-2.nix	Set uniqueness constraint on boot.devShmSize etc.	2012-10-23 07:50:23 -04:00
systemd-unit-options.nix	In the tests, don't start agetty on /dev/ttyS0	2012-10-29 21:10:00 +01:00
systemd.nix	systemd: Fail if kernel features are missing.	2012-11-06 11:25:43 +01:00