-* When runlevel3.target is used to define dependencies on other units,
- then we don't pick it up currently, since nothing ever references
- runlevel3.target, and never figure out it actually is just an alias
- for multi-user.target. A hackish fix could be to add a .wants link
- from multi-user.target to runlevel3.target, if it is a symlink to
- it. Best would be to create this .wants/ symlink from
- sysv-generator. systemd would then load the referenced unit, figure
- out it is just an alias and that the dependency would be on itself
- and suppress it. Thus the alias and its deps would be loaded as
- desired.
+* .timer units should optionally support CLOCK_BOOTTIME in addition to CLOCK_MONOTONIC
+
+* rm_rf() should be able to remove subvolumes
+
+* systemd-run should support a mode where we wait for the unit to be started up
+
+* create a btrfs qgroup for /var/lib/machines, and add all container
+ subvolumes we create to it.
+
+* nspawn: add --overlay= to support overlay file systems, similar to
+ --tmpfs= and --bind=.
+
+* When logging about multiple units (stopping BoundTo units, conflicts, etc.),
+ log both units as UNIT=, so that journalctl -u triggers on both.
+
+* to allow "linking" of nspawn containers, extend --network-bridge= so
+ that it can dynamically create bridge interfaces that are refcounted
+ by the containers on them. For each group of containers to link together
+
+* journalctl --verify: don't show files that are currently being
+ written to as FAIL, but instead show that their are being written
+ to.
+
+* assign MESSAGE_ID to log messages about failed services
+
+* coredump: make the handler check /proc/$PID/rlimits for RLIMIT_CORE,
+ and supress coredump if turned off. Then change RLIMIT_CORE to
+ infinity by default for all services. This then allows per-service
+ control of coredumping.
+
+* generate better errors when people try to set transient properties
+ that are not supported...
+ http://lists.freedesktop.org/archives/systemd-devel/2015-February/028076.html