Bug#98629: Selecting.../Unpacking... text messes up serial console
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#98629: Selecting.../Unpacking... text messes up serial console
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? David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#98629: Selecting.../Unpacking... text messes up serial console
Package: boot-floppies Version: 2.4.3 I am using a serial console, on hppa. When deboostrap is installing the debs, I get text scrolling up my screen like this: Unpacking ppp (from .../archives/ppp_2.4.1-1_hppa.deb) ... Selecting previously deselected package sysklogd. Unpacking sysklogd (from .../sysklogd_1.4.1-2_hppa.deb) ... Selecting previously deselected package tasksel. Unpacking tasksel (from .../tasksel_1.1-1_hppa.deb) ... Apart from looking a mess, this has the effect of scrolling any dialog boxes off the top of the screen. I havn't tried a woody install on a graphical console, so I don't know where the text goes in that case. Richard On Thu, May 24, 2001 at 09:45:20AM -0600, Matt Kraai wrote: On Thu, May 24, 2001 at 04:33:34PM +0100, Richard Hirst wrote: A worse problem, IMHO, is that the warning box gets scrolled off the screen by all the Unpacking ..., Setting up messages that scroll up my screen staircase fashion. Maybe that is a feature of a serial console install, and output goes somewhere else on a graphical install. Could you file a bug against the boot-floppies about this. This sounds pretty gross. Does anyone know what happens with the stdout/stderr messages from other programs when installing via a serial console? Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
