Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!cs.utexas.edu!swrinde!menudo.uh.edu!uuneo.NeoSoft.com!nobody From: smace@metal.neosoft.com (Scott Mace) Newsgroups: comp.os.386bsd.questions Subject: Re: Help: tcsh doesn't work with FreeBSD Date: 3 Feb 1994 22:33:04 -0600 Organization: NeoSoft (Katy Research Center) Lines: 31 Message-ID: <2isj6i$nq@metal.neosoft.com> References: <ghGh_3u00WB9Mfv3Yj@andrew.cmu.edu> <g89r4222.760173574@kudu> <2ioo4j$ge0@pdq.coe.montana.edu> NNTP-Posting-Host: metal.neosoft.com In article <2ioo4j$ge0@pdq.coe.montana.edu>, Nate Williams <nate@bsd.coe.montana.edu> wrote: >In article <g89r4222.760173574@kudu>, >Geoff Rehmet <g89r4222@kudu.ru.ac.za> wrote: >>In <ghGh_3u00WB9Mfv3Yj@andrew.cmu.edu> "N. R. Natraj" <nn07+@andrew.cmu.edu> writes: > >>>Warning: no access to tty (Operation not supported by device). >>>Thus no job control in this shell. >> >> >>I have seen this problem before (but haven't ever tried to trace >>the cause). Generally logging out and logging in again sets >>things to rights again..... > >This is a classic symptom of the 'hanging console' where it doesn't hang >but just screws up the settings. > >This is fixed in the most current syscons now distributed in >FreeBSD-current. (Thanks S'ren!) I think that is is caused by the fact that tcsh excepts to use the NTTYDISC terminal discipline which was broken in 1.0.2... The fix is to either get a newer kernel, or recompile tcsh to use TTYDISC instead of NTTYDISC. ie, change all occurances of NTTYDISC in the tcsh soources to TTYDISC, and it will work fine... This problem in the kernel was fixed shortly after 1.0.2 went out... Scott