On Thu, Apr 17, 2014 at 01:42:23PM +0200, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Apr 17, 2014 at 10:40:37AM +0200, Jan Chaloupka wrote: > > On 04/17/2014 04:59 AM, Zbigniew Je;drzejewski-Szmek wrote: > > >On Thu, Apr 17, 2014 at 01:41:51AM +0100, Djalal Harouni wrote: > > >>BTW, I've a question, why there is this item in the TODO: > > >>"systemctl --root=container/ set-default ... is totally borked." > > >> > > >>Can someone please shed some light on this? > > >I added this, and I guess I should have been more specific, because I had > > >to test this again, to see what is wrong :) > > > > > >systemctl --root=/var/tmp/inst1 set-default multi-user.target > > > > > >creates a symlink /var/tmp/inst1//usr/etc/systemd/system/default.target -> > > >/var/tmp/inst1//lib/systemd/system/multi-user.target, i.e. leaks the > > >container name. > > If understood correctly, proper symlink should be > > > > /var/tmp/inst1//usr/etc/systemd/system/default.target -> > > /lib/systemd/system/multi-user.target Hmm, I really can't follow here, when I was fixing that bug I looked at the other switches running against a container and the origin of the --root patch: http://lists.freedesktop.org/archives/systemd-devel/2011-June/002708.html
And my understanding is that this should behave as we are inside a chroot IOW container...! and this is what the commit log suggests but not the man page :-/ So ? -- Djalal Harouni http://opendz.org _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
