Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA14080; Fri, 8 Dec 95 18:56:26 EST
Received: from pain.lcs.mit.edu by MIT.EDU with SMTP
	id AA04917; Fri, 8 Dec 95 18:55:12 EST
Received: (from daemon@localhost) by pain.lcs.mit.edu (8.6.12/8.6.9) id SAA25652; Fri, 8 Dec 1995 18:03:49 -0500
Received: from hal9000.apana.org.au by pain.lcs.mit.edu (8.6.12/8.6.9) with ESMTP id RAA25283 for <port-i386@netbsd.org>; Fri, 8 Dec 1995 17:45:19 -0500
Received: from hotdog.apana.org.au (hotdog.apana.org.au [203.14.159.234]) by hal9000.apana.org.au (8.7/8.7) with SMTP id JAA24494 for <port-i386@netbsd.org>; Sat, 9 Dec 1995 09:21:20 +1030 (CST)
Message-Id: <Chameleon.951209091336.wulf@hotdog.apana.org.au>
Date: Sat,  9 Dec 95 09:07:40 PST
Reply-To: wulf@hal9000.apana.org.au (Berndt Josef Wulf)
From: wulf@hal9000.apana.org.au (Berndt Josef Wulf)
To: Paulo Alexandre Pinto Pires <pappires@magma.leg.ufrj.br>
Cc: port-i386@netbsd.org
Subject: RE: Problems under 1.1
Sender: owner-port-i386@NetBSD.ORG
Precedence: list
X-Loop: port-i386@NetBSD.ORG


>I just installed 1.1 in my system (i486), but I am having problems with
>it.
>
>The first is a traditional: how to compile ELM so that it doesn't have
>that problem with mailbox locking?  Many friends reported this problem
>under many different systems (NetBSD 1.0, Linux, etc.) and they  all
>solved it by borrowing already compiled binaries from other friends.
>Unfortunately, nobody around has already installed 1.1, so I am unsure
>if my old working version from 1.0 will work (I'd have to download it
>from my backup).
>

I had the same problem first. During configuration the script ask which
method of locking to be used. Just hitting return on the default values
will give you the result your are getting now. On my second try I
selected the flock options only which worked for me.

>The other problem is that TALK isn't working.  I don't know why, it
>always display that "Checking for invitation on caller's machine", even
>when it's a local request.  Is there any change to be made to the 
startup
>files or I've just got a bad file from a (never before experienced) bad
>FTP or disk write?   Should ntalkd be explicitly called in rc or 
rc.local?

Talk worked for me. Check if you have mesg enabled (mesg y will do it).
I have put this command into my login procedure.

>
>Thanks in advance.
>

Your are welcome

>pappires@magma.leg.ufrj.br


cheerio Berndt
Name   : Berndt Josef Wulf
E-Mail : wulf@hotdog.apana.org.au
Sysinfo: IBM486DX2-66, 8MB

