Bruce Perens writes ("Re: Dselect / dpkg interaction. "):
> In the case of the startup script running dselect, there is no interactive
> shell to take over when "dselect" gets a stop signal. Thus, you'd simply
> have to fork a shell at a lower level.
That's right. When the DPKG_NO_TSTP variable is set to `yes' dpkg
does exactly this.
Ian.