Martin Michlmayr <tbm@cyrius.com> writes: > * Samuel Thibault <sthibault@debian.org> [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). That way, if you think you've preseeded all the pre-network stuff, there would be a session to look at via serial if it never gets to the network. Perhaps this is not a real scenario though (I've not played with SSH connections to d-i, so I don't know what happens when you log in and debconf is already active on the console) Cheers, Phil. -- |)| Philip Hands [+44 (0)20 8530 9560] HANDS.COM Ltd. |-| http://www.hands.com/ http://ftp.uk.debian.org/ |(| Hugo-Klemm-Strasse 34, 21075 Hamburg, GERMANY
Attachment:
signature.asc
Description: PGP signature