Xref: utzoo comp.unix.xenix.sco:1664 comp.unix.sysv386:4775
Path: utzoo!mnetor!tmsoft!torsqnt!lethe!yunexus!ists!helios.physics.utoronto.ca!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!virtech!cpcahil
From: cpcahil@virtech.uucp (Conor P. Cahill)
Newsgroups: comp.unix.xenix.sco,comp.unix.sysv386
Subject: Re: stty:  Not a character device
Keywords: XENIX
Message-ID: <1991Feb08.140940.25283@virtech.uucp>
Date: 8 Feb 91 14:09:40 GMT
References: <1991Feb7.204212.28660@brolga.cc.uq.oz.au>
Reply-To: cpcahil@virtech.UUCP (Conor P. Cahill)
Organization: Virtual Technologies Inc., Sterling VA
Lines: 15

In article <1991Feb7.204212.28660@brolga.cc.uq.oz.au> exnirad@brolga.cc.uq.oz.au (Nirad Sharma) writes:
>What have I done wrong ? Is there something wrong with my /dev files ? I should

The problem is that you have an stty comand in your .cshrc or $(ENV) file 
depending upon the shell.  In each of the cases you described, your i/o
was being redirected to a non-tty hence the message.

The way to fix this is to put the stty commands into your .login file (or
the .profile file for ksh - assuming that $(ENV) is not .profile) and
the problems will go away.

-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170