On a stable system, installing systemd, and unmasking everything indicated by emerge, will currently result in a broken systemd which is unable to start any login terminals. localhost ~ # systemctl start systemd-logind.service Failed to issue method call: Unit dbus.socket failed to load: No such file or directory. See system logs and 'systemctl status dbus.socket' for details. The cause of this is that the stable dbus (1.6.8) does not install a systemd unit file, so the login service, which depends on dbus, fails to load. For the unit file to be installed, it is sufficient to have >=sys-apps/dbus-1.6.8-r1, systemd USE flag is not necessary (enabling it creates a circular dependency between systemd and dbus). Reproducible: Always Steps to Reproduce: 1. Start with a stable system. 2. Unmask: virtual/udev sys-fs/udev-init-scripts sys-apps/kmod sys-fs/udev sys-apps/systemd 3. Emerge systemd 4. Boot with systemd Actual Results: Error starting the login service, terminals don't work.
Thanks for the report, fixed.
