*BSD News Article 27657


Return to BSD News archive

Newsgroups: comp.os.386bsd.questions
Path: sserve!newshost.anu.edu.au!munnari.oz.au!yoyo.aarnet.edu.au!news.adelaide.edu.au!news.cs.su.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!europa.eng.gtefsd.com!howland.reston.ans.net!pipex!uknet!bcc.ac.uk!rs6-238.ucl-26.bcc.ac.uk!ucacdik
From: ucacdik@ucl.ac.uk (Dimitris Kogias)
Subject: Re: tcsh cannot access `tty'
Message-ID: <1994Feb24.180544.22226@ucl.ac.uk>
Date: Thu, 24 Feb 1994 18:05:44 GMT
References: <1994Feb24.143244@cs.utwente.nl>
Organization: University College London
Keywords: tcsh, tty, FreeBSD
Lines: 40

olah@cs.utwente.nl (Andras Olah) writes:

>--
>Hi,

>I've installed FreeBSD 1.0.2 on my PC last weekend, but when I start tcsh
>as my shell, I get the following message:

>	tcsh cannot access tty
>	thus no job control in this shell

exactly what I sometimes get with my NetBSD 0.9 system (pccons driver) and
tcsh.  Didn't have this problem when I was using 386BSD/codrv-1.2 though,
so I think the console driver is suspect (of course I might be wrong).
Another interesting (and apparently related) "feature" is that the
console locks up after using X, unless I have first logged in and then
out as root, at which point both the 'cannot access tty' and console
lockup problems disappear.  Sometimes the problem will re-appear after
I have exited X and logged out.  After login, I get the same message
from tcsh.


>Apart from job control, I cannot use line editing, filename expansion, etc.
>My setting is the default as FreeBSD comes `out of the box.' The only
>change I made was in /etc/ttys so that getty uses the vga device to log in
>(as suggested by the X installation package), and I installed tcsh from a
>binary package for FreeBSD.  In my .cshrc I use the same settings which
>work perfectly on SunOS 4.1 at work.

>I hope it's not a very stupid question, but I couldn't find anything in the
>FAQ, nor in the man pages.  Any help is greatly appreciated!

There doesn't seem to be an answer so far, apart from using a different
console driver (in NetBSD, I suppose it's the same for FreeBSD).

>-- 
>  Andras Olah                    	olah@cs.utwente.nl

Dimitris
d.kogias@cs.ucl.ac.uk