Date: Wed, 28 Feb 2007 09:06:10 -0500 From: Sam Baskinger <sbaskinger@lumeta.com> To: Juergen Nickelsen <ni@jnickelsen.de> Cc: freebsd-stable@freebsd.org Subject: Re: Problems installing JDK 1.5 Message-ID: <45E58C52.3090001@lumeta.com> In-Reply-To: <Prayer.1.0.16.0702281417020.54865@oland.ni.w21.org> References: <x74pp8y50g.fsf@wittduen.ni.w21.org> <45E45AD4.7040005@lumeta.com> <20070227124644.U34426@n.cwu.edu> <Prayer.1.0.16.0702281417020.54865@oland.ni.w21.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45E58C52.3090001>