Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!pipex!uknet!mcsun!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Newsgroups: comp.os.386bsd.bugs Subject: Re: iScreen 3.2 drops output after reattach from /dev/com* Message-ID: <C936Cu.13u@veda.is> Date: 23 Jun 93 18:07:26 GMT References: <C8u5Bu.7z0@veda.is> Organization: Veda Systems, Iceland Lines: 25 I just compiled screen 3.2.0b and output no longer disappears.. Guess this has been fixed then, Still curious about why this problem only manifested itself when connected via serial port. [the other problem, and a solution] In order to isolate the serial hardware from the current unix terminal, and thus prevent the serial input and output buffers from filling with garbage after invoking 'vi' on an actual serial tty, I have set up the system as follows: [last few lines of /etc/csh.login] set tty=`tty` if ($tty == /dev/com01 || $tty == /dev/com02) then source $HOME/.login exec /usr/local/bin/screen -R endif # this effectively forces the serial logins to use screen # unless .login uses exec or otherwise misbehaves # no doubt there is a better way of specifying all serial ports The same approach could be used in /etc/profile if anyone is using /bin/sh (or equivalents) as a login shell. -- adam@veda.is