- 1) The Console-kit mismatch (Systemd#Early_start)
One central feature of systemd is dbus and socket activation, this causes services to be started when they are first accessed, and is generally a good thing. However, if you know that a service (like console-kit) will always be started during boot, then the overall boot time might be reduced by starting it as early as possible. This can be achieved (if the service file is set up for it, which in most cases it is) by issuing:
This will cause systemd to start console-kit as soon as possible, without causing races with the socket or dbus activation.
So the fix for the service starting as soon as possible is to start it as soon as possible?
- 2) The Autofs requirement (Systemd#What_kernel_options_do_I_need_to_enable_in_my_kernel_in_case_I_don.27t_use_the_official_Arch_kernel.3F)
It says: This is a partial list of required/recommended options, there might be more:
[...] CONFIG_AUTOFS4_FS=[y|m] [...]
Now why would a support for automounting remote filesystems be absolutely needed with Systemd?
Thanks for your time. --Det 14:34, 16 June 2011 (EDT)