+* change default container location from /var/lib/container to /var/lib/machines
+
+* nspawn: when start a container "foobar" look for its configuration in a file "foobar.nspawn" in /etc/systemd/nspawn/ as well as next to the actualy directory or image to boot
+
* Port various tools to make use of verbs.[ch], where applicable
* Check all invocations of access() and consider turning them into laccess()
* Port various tools to make use of verbs.[ch], where applicable
* Check all invocations of access() and consider turning them into laccess()
-* "machinectl run" that works like systemd-run, but allocates a pty in the container and attached the service to it
+* "machinectl history"
-* "machinectl start/enable/disable foo" as aliases for "systemctl start/enable/disable systemd-nspawn@foo.service"
+* "machinectl diff"
-* "machinectl list-images" for showing a list of container trees collected from /var/lib/containers
+* "machinectl commit" that takes a writable snapshot of a tree, invokes a shell in it, and marks it read-only after use
-* "machinectl snapshot" to make a snapshot of a tree or container into /var/lib/containers
+* "machinectl status" should show 10 most recent log lines of both the host logs of the unit of the machine, plus the logs generated in the machine
-* "machinectl rm" to remove a container tree from /var/lib/containers
+* add transparent btrfs pool in a loopback file in /var if btrfs operations (such as systemd-import pull-dkr) are used and /var is not a btrfs file system
-* "machinectl history"
-
-* "machinectl diff"
-
-* machined: open up certain commands to unprivileged clients via polkit
+* systemd-nspawn -x should support ephemeral instances of gpt images
* systemd --user should issue sd_notify() upon reaching basic.target, not on becoming idle
* systemd --user should issue sd_notify() upon reaching basic.target, not on becoming idle
-* configure.ac pretends dbus was optional but actually hardcodes use of dbus' pkg-config file to determine various dbus dirs such as policy and activation dirs
-
* consider showing the unit names during boot up in the status output, not just the unit descriptions
* dhcp: do we allow configuring dhcp routes on interfaces that are not the one we got the dhcp info from?
* consider showing the unit names during boot up in the status output, not just the unit descriptions
* dhcp: do we allow configuring dhcp routes on interfaces that are not the one we got the dhcp info from?