Bug#844549: network-console broken: no screen to be resumed matching sh
Philip Hands, on Sun 20 Nov 2016 12:20:38 +0100, wrote:
> Martin Michlmayr <firstname.lastname@example.org> writes:
> > * Samuel Thibault <email@example.com> [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 screen in that case because you can
> > always open a second SSH connection and open a terminal, but I don't
> > have strong feelings either way if there's an advantage of having
> > screen in such cases.
> I'd think that the advantage is that one could start a serial install up
> to the point that the network comes up, and then hijack it onto the ssh
> session so that one gets to see the same install (as well as any other
> shells you might have started).
Mmm, that's a nice idea indeed. I've eventually uploaded the -x fix,
which gives us that behavior, and also allowing several people to follow
the installation, interact, etc.