Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!news.intercon.com!udel!newsserv.cs.sunysb.edu!stark.UUCP!stark!stark!gene From: stark!gene@newsserv.cs.sunysb.edu (Gene Stark) Newsgroups: comp.os.386bsd.questions Subject: Re: tcsh woes again ... Date: 4 Jan 94 18:09:52 Organization: Gene Stark's home system Lines: 20 Message-ID: <STARK!GENE.94Jan4180952@stark.uucp> References: <CJ3BoJ.FCn@usenet.ucs.indiana.edu> NNTP-Posting-Host: stark.uucp In-reply-to: pitts@mimosa.astro.indiana.edu's message of Tue, 4 Jan 1994 05:38:43 GMT In article <CJ3BoJ.FCn@usenet.ucs.indiana.edu> pitts@mimosa.astro.indiana.edu (Jim Pitts) writes: Well, you might recall I posted about a problem I was having with tcsh some time ago. Basically when I start tcsh up on my FreeBSD system I get the following message: Warning: no access to tty (Operation not supported by device). Thus no job control in this shell. I have seen this problem result in certain situations from having a call to "stty" in your .login script. Under certain conditions, if the shell is invoked from a pty (I have seen this happen with Emacs shell mode) then the error message you see is displayed. I don't totally understand the reasons why this happens, so I haven't tried to track down and fix it. As a work around, see if you have "stty" in your .login or .cshrc and comment it out. Maybe that will work. - Gene Stark --