I looked at the source but am not expert enough to investigate this
myself. Sorry.
The ideal behaviour, in my view, would be for
schroot -c ia32 -p any_program &
to be equivalent to logging in to the chroot, changing to the right
working directory, running
any_program &
and then logging out of the chroot. At the moment this is not the case.
If the termios restore is indeed the problem, one might ask whether this
ought to be the job of schroot. I don't understand why schroot feels it
has to fix problems caused by any_program? Would bash do something
equivalent? If so, it might be worth investigating the approach used
there.
I am way out of my depth here and don't know what I am talking about, so
I'll drop out of this discussion from now on. Sorry to have been
awkward.
Thanks again for your help. The enthusiasm of the Debian maintainers
never ceases to amaze me.
Matthew
--
******************************************************************
Matthew Foulkes
Department of Physics phone: (020) 7594 7607
Imperial College London fax: (020) 7594 7604
Prince Consort Road email: [EMAIL PROTECTED]
London SW7 2BW www: www.imperial.ac.uk/research/cmth
******************************************************************
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
