From owner-freebsd-java@FreeBSD.ORG Mon Jun 28 23:00:24 2004 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CB1716A4CE for ; Mon, 28 Jun 2004 23:00:24 +0000 (GMT) Received: from goliath.nxlkhost.com (goliath.nxlkhost.com [207.155.252.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3332A43D54 for ; Mon, 28 Jun 2004 23:00:24 +0000 (GMT) (envelope-from dhockin@staffware-spokane.com) Received: from [127.0.0.1] (403254C2.ptr.dia.nextlink.net [64.50.84.194]) by goliath.nxlkhost.com id TAA25186; Mon, 28 Jun 2004 19:00:17 -0400 (EDT) [ConcentricHost SMTP Relay 1.17] Errors-To: Message-ID: <40E0A30E.1090701@staffware-spokane.com> Date: Mon, 28 Jun 2004 16:00:30 -0700 From: Doug Hockin User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a1) Gecko/20040520 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mriem@manorrock.org References: <200406260001.UAA15135@hood.nxlkhost.com> In-Reply-To: <200406260001.UAA15135@hood.nxlkhost.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-java@freebsd.org Subject: Re: jdk1.4 on FreeBSD 5.2.1 X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jun 2004 23:00:24 -0000 > Did you update your ports tree before attempting this? No. Thanks for the advice -- I'm new to FreeBSD. I started a 'portsupdate', but 5-6 times it's stopped asking for operator input. It puts out what is probably intended to be nicely formatted output, but in my emacs shell buffer ends up as a bunch of gobbledygook. I've typed 'ok' in response to each one and it's progressing, but slowly since I'm not at work to babysit it 24 hrs-a-day. I came in twice over the weekend to get it going again and had to start it again with an 'ok' this morning when I got in. I stopped it part way thru and tried the '-y' option that I found in the portsupdate man page, but that doesn't help -- it still sits and waits for my input. It would seem more reasonable to me to default to 'yes' rather that stopping to ask for input, but maybe I'm missing something. -- Doug