From owner-freebsd-java@FreeBSD.ORG Tue Jun 29 06:34:19 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 A904516A4CF for ; Tue, 29 Jun 2004 06:34:19 +0000 (GMT) Received: from diomedes.noc.ntua.gr (diomedes.noc.ntua.gr [147.102.222.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AE5143D31 for ; Tue, 29 Jun 2004 06:34:19 +0000 (GMT) (envelope-from past@noc.ntua.gr) Received: from ajax.noc.ntua.gr (ajax.noc.ntua.gr [147.102.220.1]) i5T6YHEr062460; Tue, 29 Jun 2004 09:34:17 +0300 (EEST) (envelope-from past@noc.ntua.gr) Received: from [147.102.220.45] (hal.noc.ntua.gr [147.102.220.45]) by ajax.noc.ntua.gr (8.12.11/8.12.11) with ESMTP id i5T6YGn0093602; Tue, 29 Jun 2004 09:34:16 +0300 (EEST) (envelope-from past@noc.ntua.gr) Message-ID: <40E10D68.4030701@noc.ntua.gr> Date: Tue, 29 Jun 2004 09:34:16 +0300 From: Panagiotis Astithas Organization: NTUA/NMC User-Agent: Mozilla Thunderbird 0.6 (X11/20040609) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Hockin References: <200406260001.UAA15135@hood.nxlkhost.com> <40E0A30E.1090701@staffware-spokane.com> In-Reply-To: <40E0A30E.1090701@staffware-spokane.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: mriem@manorrock.org 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: Tue, 29 Jun 2004 06:34:19 -0000 Doug Hockin wrote: >> 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. If by 'portsupdate' you mean 'portupgrade', then you can have an unattended operation by using the following option: portupgrade -m 'BATCH=yes' Cheers, -- Panagiotis Astithas Electrical & Computer Engineer, PhD Network Management Center National Technical University of Athens, Greece