Bug#844549: network-console broken: no screen to be resumed matching sh

Roger Shimizu, on Wed 30 Nov 2016 23:53:31 +0900, wrote: > Just one issue for SSH (network-console). > Since the SSH session shares the same screen with serial, the screen > size is limited to 80x25 (probably, I didn't count the number), which > is too small to most recent monitor devices. Sure.

Bug#844549: network-console broken: no screen to be resumed matching sh

On Tue, Nov 22, 2016 at 3:05 AM, Roger Shimizu wrote: > > I'll test the daily image on my Linkstation NAS. I tested the daily image on my armel devices. Both serial way and SSH way works fine. And if connect both serial and SSH (network-console), serial/SSH seems to share

Bug#844549: network-console broken: no screen to be resumed matching sh

Seems I'm late for the d-i/screen party, but .. On Thu, Nov 17, 2016 at 6:39 AM, Martin Michlmayr wrote: > > Oh, good point. > > I think that's what we want but I'm not sure. Maybe Roger can > comment. In his old code, there was also a $NETBOOT_SCREEN variable > which afaict

Bug#844549: network-console broken: no screen to be resumed matching sh

Hello, Philip Hands, on Sun 20 Nov 2016 12:20:38 +0100, wrote: > Martin Michlmayr writes: > > > * Samuel Thibault [2016-11-16 23:03]: > >> But AIUI the intent was to have screen in ssh connections too. > > > > I'm not sure what the intent was. I assume

Bug#844549: network-console broken: no screen to be resumed matching sh

Martin Michlmayr writes: > * Samuel Thibault [2016-11-16 23:03]: >> But AIUI the intent was to have screen in ssh connections too. > > I'm not sure what the intent was. I assume you're right because Roger > didn't exclude screen from the network-console

Bug#844549: network-console broken: no screen to be resumed matching sh

Hi, Martin Michlmayr (2016-11-16): > * Samuel Thibault [2016-11-16 23:03]: > > But AIUI the intent was to have screen in ssh connections too. > > I'm not sure what the intent was. I assume you're right because Roger > didn't exclude screen from the

Bug#844549: network-console broken: no screen to be resumed matching sh

* Samuel Thibault [2016-11-16 23:03]: > But AIUI the intent was to have screen in ssh connections too. I'm not sure what the intent was. I assume you're right because Roger didn't exclude screen from the network-console images. Personally, I'm not sure I see the point of

Bug#844549: network-console broken: no screen to be resumed matching sh

Hello, Martin Michlmayr, on Wed 16 Nov 2016 12:07:07 -0800, wrote: > I believe below is the right fix, i.e. start screen when screen exists and > when we're on serial or when we're NOT on network. But AIUI the intent was to have screen in ssh connections too. We could have the case where d-i is

Bug#844549: network-console broken: no screen to be resumed matching sh

* Ben Hutchings [2016-11-16 21:15]: > >   rm -f $font > > - if [ -x "$screen_bin" -a \( "$TERM_TYPE" = network -o "$TERM_TYPE" = > > serial \) -a "$TERM" != dumb ]; then > > + if [ -x "$screen_bin" -a \( "$TERM_TYPE" != network -o "$TERM_TYPE" = > > serial \) -a

Bug#844549: network-console broken: no screen to be resumed matching sh

On Wed, 2016-11-16 at 12:07 -0800, Martin Michlmayr wrote: > Package: rootskel > Version: 1.119 > Severity: serious > Tags: patch > > Several users have reported to me that the network-console images are > broken. > > Commit ec6d3c3d79 (Move screen support) moved the screen support > around and

Bug#844549: network-console broken: no screen to be resumed matching sh

Package: rootskel Version: 1.119 Severity: serious Tags: patch Several users have reported to me that the network-console images are broken. Commit ec6d3c3d79 (Move screen support) moved the screen support around and also changed the logic of when screen is used. Unfortunately, that change broke