Heya, A few things to note:
a) change of behaviour: before yesterday it was possible to pull in a native service via a symlink on the sysv init script in /etc/rcN.d/. This is no longer the case: native services are now pulled in exclusively by native dependencies (for example symlinks in .wants/), and legacy SysV services may be pulled in by both ways. This change allows us to do a few things we couldn't do before, for example, make sure that ssh is started lazily via a socket when the system is booted via systemd, and start it normally when booted without. This also should be useful to deal with the weird way recent Debian system do late shutdown. This change requires you to create .wants/ symlinks for all native services that were previously pulled in via rcN.d/ symlinks! b) I renamed systemd-install's --start switch to --realize, because it was a bit confusing to run a command line like "systemd-install --start disable". All 3rd party packages using this switch in the .spec file (or equivalents) need to be fixed for this change. c) If you package systemd for a distribution, you might want to look into these two Fedora bug requests, and do the same for your distro: https://bugzilla.redhat.com/show_bug.cgi?id=612712 https://bugzilla.redhat.com/show_bug.cgi?id=612728 Have fun, Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
