*BSD News Article 29737


Return to BSD News archive

Xref: sserve comp.os.386bsd.questions:9926 comp.os.386bsd.bugs:2197
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!zip.eecs.umich.edu!panix!ddsw1!news.cic.net!magnus.acs.ohio-state.edu!csn!att-in!att-out!cbnewsj!rudy
From: rudy@cbnewsj.cb.att.com (avram.r.vener)
Subject: Returning from X and running ksh
Organization: AT&T
Date: Wed, 20 Apr 1994 02:36:39 GMT
Message-ID: <CoJDx5.FH5@cbnewsj.cb.att.com>
Lines: 28

I just installed FreeBSD 1.0 on my 486 system.  I have X running 
and can bring it up with startx. No problem.  However when I select the
twm Exit option, instead of returning to my original shell I am returned
to what looks like my original character based screen (with all the original
X startup messages ) and left in some sort of mode where I can type 
and see my text, but it is not being interpreted by a shell.  I cannot
break out of this by any method I have tried (^D, ^X, ^C, <ESC>, etc). 

Can anyone tell me how to return to my login shell?

My .xinitrc is the sample one from the xinit manual page that starts up
the xclock, an xterm window or two all in background and then the twm in the 
foreground.  I also tried running twm in the background as the first task
and ending with an exec xterm .... as the last task run in the foreground.
Same results in both cases. 


On a cmpletely different problem,  has anyone else experienced the 
bugs I found in ksh?  When I redirect a simple ls command from the ksh to
a file the files is filled with garbage characters. The output of the ls
redirected into the file, but after all that garbage. Also, hitting the 
escape key in ksh does not place me in the command lind editor, and yes I have 
FCEDIT defined.   Any words of wisdom here?

Thanks

--
Rudy Vener  salt@shell.portal.com   rudy@mtqua.att.com