Dear Rick, Thanks for your testing report!
On Sat, May 14, 2016 at 4:18 PM, Rick Thomas <[email protected]> wrote: > > Hi Roger, > > I got a chance to try it on my SheevaPlug. > > Executive summary: It worked as advertised and all the features you mentioned > seem to work (except I didn’t try disconnect and reconnect — see below for > details). I really liked being able to switch between VTs with a couple of > keystrokes! > > Here’s what I did and why I did it: > > First observation is that the way I normally do installations on this machine > (I keep it around for exactly this kind of testing, so I do a fair number of > installations on it) is to run screen as a terminal emulator on a desktop > machine that is connected to the Plug via a USB serial connection. If I did > that for this experiment, I’d wind up with screen running on the Plug inside > of screen running on the Desktop and the thought of keeping track of all the > levels of ctl-A gave me nightmares. Indeed. It will be messed up if running screen inside screen. If you have any suggestion to avoid this, just let me know. > So, I changed to using “cu” to run the USB serial connection. That worked > well enough. > > The installation proceeded smoothly while I experimented with the ctl-A <1-4> > options. It would have been nice to have the option of a more spacious > work-area — larger than 24x80 — but that’s a minor issue. I find this size of screen limitation, too. But I think this limitation is not introduced by GNU/screen, it exists before. > I didn’t try disconnecting, letting it run for a while un-attended, then > reconnecting because I didn’t have a clear idea of how to do that. > Specifically, what happens if I type ctl-A ctl-D? Do I get disconnected from > just the one window or all four of them? If I get disconnected from all of > them, what will I find myself talking to? Is it an interactive shell that I > can re-connect to the running disconnected screen by typing > “screen -R” > or something else? > > If I’m disconnected, can I drop the “cu” connection without causing havoc to > the running install? If I later re-instate the “cu”, what happens then? Do I > automatically get my screen session back again, or is there something I need > to do to to make that happen? Resume when re-connecting is mainly for network-console (via SSH). "screen -r" is done by debian-installer, user don't need anything extra. > These are all experiments I could have done during the install, but I > refrained because I wanted to verify that there weren’t any difficulties > associated with simply running the installer inside screen. Next time I get > a few hours, I’ll try installing again and experiment with dis-/re-connecting. I really appreciate you helping to confirm it working on other devices than I have on hand. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 17B3ACB1
