From owner-freebsd-stable@FreeBSD.ORG Wed Feb 28 14:08:05 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 754AD16A405 for ; Wed, 28 Feb 2007 14:08:05 +0000 (UTC) (envelope-from sbaskinger@lumeta.com) Received: from MAIL.corp.lumeta.com (zeus.lumeta.com [65.246.245.22]) by mx1.freebsd.org (Postfix) with ESMTP id 3400A13C49D for ; Wed, 28 Feb 2007 14:08:04 +0000 (UTC) (envelope-from sbaskinger@lumeta.com) Received: from [65.246.246.82] ([65.246.246.82]) by MAIL.corp.lumeta.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 28 Feb 2007 09:08:03 -0500 Message-ID: <45E58C52.3090001@lumeta.com> Date: Wed, 28 Feb 2007 09:06:10 -0500 From: Sam Baskinger Organization: Lumeta Corporation User-Agent: Thunderbird 1.5.0.9 (X11/20070212) MIME-Version: 1.0 To: Juergen Nickelsen References: <45E45AD4.7040005@lumeta.com> <20070227124644.U34426@n.cwu.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Feb 2007 14:08:03.0772 (UTC) FILETIME=[DCBCEFC0:01C75B41] Cc: freebsd-stable@freebsd.org Subject: Re: Problems installing JDK 1.5 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 14:08:05 -0000 Juergen Nickelsen wrote: > On Feb 27 2007, Chris Timmons wrote: > >> Don't forget that the linux JDK will want you to have linprocfs >> mounted. I recently had a similar build experience of jdk-1.5.0p4 >> which cleared up fine after I remembered about linprocfs. >> >> linprocfs /compat/linux/proc linprocfs rw 0 0 > > Hm. I cannot imagine how this could lead to the problems I saw, but > another thing to try. Thanks! Linux systems store tons of need-to-know data in the /proc file system. If you've ever installed a chrooted Linux environment you must 'mount -o bind' the /proc file system from the running system to the chroot for many OS functions to work correctly. I suspect that Java was looking for some process information in linprocfs and since it wasn't mounted, it blew up. :) Hope this clears up the "why" question. :) Sam Baskinger Lumeta - Securing the Network in the Face of Change www.lumeta.com