From owner-freebsd-ports  Tue May  6 19:59:01 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA26147
          for ports-outgoing; Tue, 6 May 1997 19:59:01 -0700 (PDT)
Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA26142
          for <ports@freebsd.org>; Tue, 6 May 1997 19:58:59 -0700 (PDT)
Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM)
	id AA18791; Tue, 6 May 1997 19:58:54 -0700
Date: Tue, 6 May 1997 19:58:54 -0700 (PDT)
From: "Brian N. Handy" <handy@sag.space.lockheed.com>
To: Neil David Adams <N.Adams@bom.gov.au>
Cc: ports@freebsd.org
Subject: Re: pine port
In-Reply-To: <336FE1E3.167E@bom.gov.au>
Message-Id: <Pine.OSF.3.96.970506195652.11418I-100000@sag.space.lockheed.com>
X-Files: The truth is out there
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Any clues as to how I can fix this  so it works ? since it leaves me
>with a system that looks like it is runnig pine 3.96 but which still
>locks up eventually if I am running any telnet sessions.

Just curious here...Pine locks up my telnet sessions when I'm logged in
over a laggy network link.  I'm not sure what your problem is (sounds like
you've got an old system trying to install a new port), but if you have
the pine problem you are suggesting...Pine 3.96 doesn't fix it.

Sigh.  (If I had an idea how to chase this one down, I would.)

Brian