*BSD News Article 31447


Return to BSD News archive

Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!DIALix!not-for-mail
From: datacrft@perth.DIALix.oz.au (Datacraft Technology)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: Major problems with FreeBSD-1.1
Date: 9 Jun 1994 22:09:47 +0800
Organization: DIALix Services, Perth, Western Australia
Lines: 54
Sender: datacrft@perth.DIALix.oz.au
Message-ID: <2t77rb$7cu$1@perth.dialix.oz.au>
References: <2t37es$h6j$1@perth.dialix.oz.au> <Cr2w1z.Mw8@world.std.com>
NNTP-Posting-Host: perth.dialix.oz.au
X-Newsreader: NN version 6.5.0 #5 (NOV)

In <Cr2w1z.Mw8@world.std.com> hd@world.std.com (HD Associates) writes:

>In article <2t37es$h6j$1@perth.dialix.oz.au>,
>Datacraft Technology <datacrft@perth.DIALix.oz.au> wrote:
>>I found three major problems with FreeBSD-1.1-Release:

>(...)

>>
>>2) I had X up and running (started with xinit) using twm. In one window I
>>   received a large file via zmodem. In a second window I just did a 
>>   "make depend" after I reconfigured the kernel. I a third window I
>>   was typing "ls" and got no echo back. From this point on no keyboard
>>   input was possible. The system was happy otherwise. I was able to use
>>   mouse and twm's menu. Also "make depend" run to completion and the
>>   zmodem receive also finished and I was back at the kermit prompt.
>>   At this time I used the twm menu to shut X down and got my keyboard
>>   back.
>>
>>   WHAT happened to my keyboard?

>This sounds like the problems I had with syscons in earlier versions of
>-current, and, presumably, in 1.1-Release.  I used pccons with a hack
>to keep the keyboard  from hanging on boot up.  If you can rebuild and
>are using syscons, try pccons instead.  You may then have the "keyboard
>hang during boot up bang on caps lock key" problem instead.
>The new syscons in -current has solved all my keyboard problems.


Sorry, but I'm using the standard GENERICAH kernel with pccons.


>>
>>3) Next I used xinit to fire up X, used twm to start an xterm, xterm
>>   comes up with the normal shell prompt.
>>
>>   NOW I hit return and I'm back at my original kermit session which
>>   I used for my zmodem transfer!?!?!? :(
>>
>>   How did I get my old kermit (which I assumed to be dead) back on
>>   a brand new xterm session.
>>

>You got the same pty and the kermit was still running.  I don't know
>why.

>>Tibor Sashegyi
>>


>-- 
>Peter Dufault               Real Time Machine Control and Simulation
>HD Associates, Inc.         Voice: 508 433 6936
>hd@world.std.com            Fax:   508 433 5267