Is there some other solution than disabling the initctl? I use initrds that deploy vmware/quemu/bare instances via network, where most of the initial installation operation is done using debootstrap (reports error when rsyslog is configured) and chroot to the target disk (install, update fails) before the instance is really booted.
At the moment I move initctl to tmpfile at start of target setup and move it back afterwards. Does this have any side effects on functionality of installed packages?
Is there some other solution than disabling the initctl? I use initrds that deploy vmware/quemu/bare instances via network, where most of the initial installation operation is done using debootstrap (reports error when rsyslog is configured) and chroot to the target disk (install, update fails) before the instance is really booted.
At the moment I move initctl to tmpfile at start of target setup and move it back afterwards. Does this have any side effects on functionality of installed packages?