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
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
