Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!foxhound.dsto.gov.au!fang.dsto.gov.au!myall.awadi.com.au!myall!blymn From: blymn@awadi.com.au (Brett Lymn) Newsgroups: comp.os.386bsd.questions Subject: Re: BIOS console (scroll lock) Date: 3 Apr 93 18:10:18 Organization: AWA Defence Industries Lines: 22 Message-ID: <BLYMN.93Apr3181018@mallee.awadi.com.au> References: <C4np3J.Jpx@veda.is> NNTP-Posting-Host: mallee.awadi.com.au In-reply-to: adam@veda.is's message of 29 Mar 93 15:16:31 GMT >>>>> On 29 Mar 93 15:16:31 GMT, adam@veda.is (Adam David) said: Adam> The scroll-lock key can be useful at the console to see what is going on Adam> when things are moving too fast, but there is an annoying side-effect. Adam> Not only does it freeze output to the console but all output freezes, Adam> even on remote telnet sessions. For all I know, the whole system is put Adam> on hold. Which console drivers allow scroll-lock to apply only to the Adam> console? What are their relative merits and pitfalls? Ahhh.... this brings back memories (no solution.... just some ramblings). I remember working on a Motorola sys V r2 system that would do a similar thing, if the console output was stopped with a control-s (these were all serial terminals) all output would stop. It took me a while to work out why my terminal would stop at random times for no apparent reason until I worked out that one of my work mates was using the console and looking at a file when the stoppages occurred. Seems like the bug is not just confined to sys V :-) -- Brett Lymn -- Brett Lymn