Matthew Dillon wrote:
I think the last time I used screen was 20 years ago. I just leave all my xterms open. Sometimes I have upwards of 30 windows open across four virtual screens in X. When people were describing the NATA bugs I had an xterm open in an unsaved vi for over a week with all my notes My version of Mac stickies!I have about two dozen little FVWM2 buttons which run a remote ssh in an xterm, and use -e none so the ssh doesn't interpret control escapes: (Title Staid, Icon up, Back lightgreen, Action `Exec exec xterm -T TITLE -e ssh -a -e none HOSTNAME`) -Matt
Ditto, OS X or Xfce4 on (another)BSD. Sometimes several weeks, and HKG to Zurich or IAD to ZRH or HKG as well.
OTOH, more recent ssh DO want to time out if inactive, which I have not yet had reason to try to alter, as it seems a good thing, actually.
'screen' had been of quite recent value though as the ZRH-HKG link had pretty high latency, and dying in the middle of a make world was not nice back when slower machines (or our lowball VIA Samuel 2's) took the better part of a day to complete it instead of an hour or two per chunk the dual-core's now deliver.
That said, there is an old 'wish for' w/r remote access that I would still like to see made a 'standardized option':
That of configuring a machine to be able to drop into an ssh-receptive mode - perhaps limited to only a preset correspondent - if/as/when it stalls in single-user mode and cannot go multi.
In theory, of course this is no longer 'single' user mode... but it would be a useful fiddle for maintenance of remote servers that do not have an IP KVM, expensive 'lights out' module, or site technicians who speak anything but Winders. IOW - most of them.
JM2CW, Bill
