{"action":"created","issue":{"url":"https://api.github.com/repos/systemd/systemd/issues/3958","repository_url":"https://api.github.com/repos/systemd/systemd","labels_url":"https://api.github.com/repos/systemd/systemd/issues/3958/labels{/name}","comments_url":"https://api.github.com/repos/systemd/systemd/issues/3958/comments","events_url":"https://api.github.com/repos/systemd/systemd/issues/3958/events","html_url":"https://github.com/systemd/systemd/pull/3958","id":171050752,"number":3958,"title":"systemctl: switch-root: align behaviour with manual","user":{"login":"esmil","id":13502,"avatar_url":"https://avatars.githubusercontent.com/u/13502?v=3","gravatar_id":"","url":"https://api.github.com/users/esmil","html_url":"https://github.com/esmil","followers_url":"https://api.github.com/users/esmil/followers","following_url":"https://api.github.com/users/esmil/following{/other_user}","gists_url":"https://api.github.com/users/esmil/gists{/gist_id}","starred_url":"https://api.github.com/users/esmil/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/esmil/subscriptions","organizations_url":"https://api.github.com/users/esmil/orgs","repos_url":"https://api.github.com/users/esmil/repos","events_url":"https://api.github.com/users/esmil/events{/privacy}","received_events_url":"https://api.github.com/users/esmil/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-08-14T09:38:09Z","updated_at":"2016-08-17T12:59:18Z","closed_at":"2016-08-17T12:59:17Z","pull_request":{"url":"https://api.github.com/repos/systemd/systemd/pulls/3958","html_url":"https://github.com/systemd/systemd/pull/3958","diff_url":"https://github.com/systemd/systemd/pull/3958.diff","patch_url":"https://github.com/systemd/systemd/pull/3958.patch"},"body":"The manual says no state will be passed from one systemd to the next if the path of the next init\r\nis specified on the command line. However systemctl tries to detect if the next init\r\nis systemd and then pass it's state anyway. Just delete this code.\r\n\r\nThe specific problem this solves for me is that sometimes systemd in my initrd will pass a state to systemd on my rootfs that says local-fs.target is up. However local-fs.target on my root filesystem has more dependencies than in the initrd, so some filesystems are not mounted before systemd-tmpfiles is run to create files on them.\r\n\r\nThis patch at least let me work around the problem by specifically telling the initrd to not pass any state to systemd in the rootfs."},"comment":{"url":"https://api.github.com/repos/systemd/systemd/issues/comments/240403102","html_url":"https://github.com/systemd/systemd/pull/3958#issuecomment-240403102","issue_url":"https://api.github.com/repos/systemd/systemd/issues/3958","id":240403102,"user":{"login":"poettering","id":2130732,"avatar_url":"https://avatars.githubusercontent.com/u/2130732?v=3","gravatar_id":"","url":"https://api.github.com/users/poettering","html_url":"https://github.com/poettering","followers_url":"https://api.github.com/users/poettering/followers","following_url":"https://api.github.com/users/poettering/following{/other_user}","gists_url":"https://api.github.com/users/poettering/gists{/gist_id}","starred_url":"https://api.github.com/users/poettering/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/poettering/subscriptions","organizations_url":"https://api.github.com/users/poettering/orgs","repos_url":"https://api.github.com/users/poettering/repos","events_url":"https://api.github.com/users/poettering/events{/privacy}","received_events_url":"https://api.github.com/users/poettering/received_events","type":"User","site_admin":false},"created_at":"2016-08-17T12:59:17Z","updated_at":"2016-08-17T12:59:17Z","body":"No, this really should stay. We should pass all matching state from the initrd to the main system. After all it's highly relevant whether for example an fsck on the root fs failed or not, and \"systemctl status\" should show that after the system is up. \r\n\r\nUnits in the initrd and on the host that have the same meaning should not really change meaning. It's OK if they change config slightly, but they really should semantically have the same meaning. If they change meaning they should really change name too. Specifically this means in your case local-fs.target should not be used in the initrd (unless you know for sure that no further file systems shall be mounted during runtime, before the services are up). There's initrd-fs.target specifically in order to have a different target for file systems mounted in the initrd.\r\n\r\nI am pretty sure we should continue to pass as much state as we can, if we know that the destination init system is actually systemd. \r\n\r\nI hope this makes sense, closing hence."}}
{"actor":{"display_login":"poettering"}}