Bug#512067: debootstrap: sysvinit: init: timeout opening/writing control channel /dev/initctl
>> I: Unpacking the base system...
>> W: Failure while installing base packages. This will be re-attempted
up to five times.
>> W: Failure while installing base packages. This will be re-attempted
up to five times.
>> W: Failure while installing base packages. This will be re-attempted
up to five times.
>> W: Failure while installing base packages. This will be re-attempted
up to five times.
>
>> init: timeout opening/writing control channel /dev/initctl
>
> That should not be the problem here, as the behaviour is correct. When
> installing into the chroot, the currently running init should not be
> restarted during configuration of the sysvinit package; the package knows
> to ignore this error.
>
>> mount -o bind /dev /mnt/debinst/dev/
>> chroot /mnt/debinst/
>> unset LANG
>> dpkg --configure -a
>> dpkg-reconfigure sysvinit
>
> That's not a good idea; there is no guarantee that the outer system's init
> is compatible with the chroot's; also, there is no point in restarting the
> outer system's init process as it hasn't been changed.
>
> As an optimization, one might think about chroot detection in sysvinit's
> postinst so the restart isn't attempted. I'm not convinced this is the
> actual reason why configuration fails; rather, I think it might be some
> other package that is confused by not having a working /dev (such as a
> program in a postinst opening /dev/tty).
>
> Simon
Ok that sounds logical, the binding of the /dev is indeed not a good
idea. I tried it to see if I could get more info on the issue.
I don't know what to do next... Any ideas how to proceed?
Neil tolled me the issue does not come up on his system, so some info
about my test system:
I am using an debian sid updated installation on a usb stick with grub.
I use an eeepc 701 that boots completely from the usb sticks and I try
to debootstrap the installation on the ssd of the eeepc for testing.
Best regards,
Jelle
btw why is submit@bugs.debian.org in the cc field?
Reply to: