Bug#98629: Selecting.../Unpacking... text messes up serial console

[Richard Hirst <rhirst@linuxcare.com>]

On Sun, May 27, 2001 at 06:04:05PM -0700, David Whedon wrote:
> Thu, May 24, 2001 at 11:54:50PM +0100 wrote:
> > On Thu, May 24, 2001 at 02:25:17PM -0700, David Whedon wrote:
> > > I may have an explanation, but am not sure of the solution.  When we inovke
> > > debotstrap we communicate with in through it's stdin and fd 3.  We redirect
> > > debootstrap's stdout and stderr to /dev/tty4.  stdout and stderr have those
> > > messages described below.  My guess is that when installing over a serial
> > > console tty4 goes to the console as well, possible?
> > 
> > Right,  from exec_debootstrap()
> > 
> >         /* redirect stdout and stderr to /dev/tty4 */
> >         freopen("/dev/tty4", "w", stderr);
> >         dup2(2,1);
> > 
> > I suppose the freopen fails, so stdout/stderr will remain on the console.
> > Maybe we could write it to /target/tmp/debootstrap.log on a serial
> > console system?
> 
> Will it ever get deleted from /target/tmp/ ?  I don't want it sitting around
> forever.  It is useful for diagnostic purposes, but that is it.  I just
> committed a patch that sticks it in /tmp/debootstrap.log. 
> 
> If it goes in /tmp/debootstrap.log is disappears once we reboot on the serial
> console system, just like on the non-serial console system.
> 
> Sound good?

Yes, fine with me.  I think the target system cleans its /tmp on reboot
anyway.

Thanks,
  Richard