[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Bryan Stansell bryan@conserver.com
Tue, 1 May 2001 04:31:00 -0700 (PDT)
And one of the things I wanted to do was add an 'l2' escape sequence to send the <CR>~^b bits for you - it was suggested by a guy at the LISA conference - good idea, no? The only trick is there's a bit of timing you have to get right - I think it's a 0.5 second delay between each character, otherwise it could be a random sequence coming over, say a modem (why put a modem on the console port - ugh, I can see it being done, but haven't ever done it) transfering a file. Anyway, you don't really want to "lock up" conserver for a second or so while it's waiting the prerequisite amount of time...and the sequence could be changed or different for another device ('l3', 'l4', etc) so a real multi-threaded or alarm-based or something method needs to be put together. In the mean time, just type it by hand. One of these days all these things will be in the code. Bryan Quoting Iain Rae <iainr@dcs.ed.ac.uk>: > any suns which are patched should ignore any breaks sent via the > conserver menu > ( l1) but will halt if you type ~^b (quickly)at the terminal session. So > you > can use it without changing conserver, you just have to remember ~^b.