{"action":"reopened","issue":{"url":"https://api.github.com/repos/debian-pi/raspbian-ua-netinst/issues/314","labels_url":"https://api.github.com/repos/debian-pi/raspbian-ua-netinst/issues/314/labels{/name}","comments_url":"https://api.github.com/repos/debian-pi/raspbian-ua-netinst/issues/314/comments","events_url":"https://api.github.com/repos/debian-pi/raspbian-ua-netinst/issues/314/events","html_url":"https://github.com/debian-pi/raspbian-ua-netinst/issues/314","id":118288068,"number":314,"title":"How to setup a chroot for use during installation","user":{"login":"netdesk","id":6189441,"avatar_url":"https://avatars.githubusercontent.com/u/6189441?v=3","gravatar_id":"","url":"https://api.github.com/users/netdesk","html_url":"https://github.com/netdesk","followers_url":"https://api.github.com/users/netdesk/followers","following_url":"https://api.github.com/users/netdesk/following{/other_user}","gists_url":"https://api.github.com/users/netdesk/gists{/gist_id}","starred_url":"https://api.github.com/users/netdesk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/netdesk/subscriptions","organizations_url":"https://api.github.com/users/netdesk/orgs","repos_url":"https://api.github.com/users/netdesk/repos","events_url":"https://api.github.com/users/netdesk/events{/privacy}","received_events_url":"https://api.github.com/users/netdesk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-11-22T20:58:07Z","updated_at":"2015-11-26T09:59:59Z","closed_at":null,"body":"I tried to find a solution the whole weekind, but I don't find any way to do additional setup stuff after the installation. That is installing nodejs and pilight from third-party repositories (nodejs.org and pilight.org) and installing wiringPi (git clone and then build). chrooting into /rootfs in the post-install.txt doesn't work properly, errors occouring and I don't think the unbooted chrooted environment is not really suited for this tasks. Then I tried a cronjob \"@reboot root /testscript\". But the job is executed in the background, the user doesn't see that there is still something going on. As installing nodejs, pilight and building wiringPi takes some time, I want to inform the user about that, he should see the process like the initial installation. I also tried a systemd service or a init.d script which should delete itself after it's done, but no success at all, they stay in the background too.\r\n\r\nIs there a preferred way to execute additional tasks on the first boot, which isn't forked invisibly to the background? Did I miss an option of raspbian-ua-netinst?"}}