From owner-freebsd-java@FreeBSD.ORG Sat Jan 4 01:23:54 2014 Return-Path: Delivered-To: freebsd-java@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 430C2238 for ; Sat, 4 Jan 2014 01:23:54 +0000 (UTC) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2519D1346 for ; Sat, 4 Jan 2014 01:23:53 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VzFxr-00067s-0R for freebsd-java@freebsd.org; Fri, 03 Jan 2014 17:23:47 -0800 Date: Fri, 3 Jan 2014 17:23:47 -0800 (PST) From: ari To: freebsd-java@freebsd.org Message-ID: <1388798626990-5873612.post@n5.nabble.com> In-Reply-To: <52C58E85.8030501@freebsd.org> References: <21189.33585.949509.38005@jerusalem.litteratus.org> <52C58E85.8030501@freebsd.org> Subject: Re: open jdk7 marked "FORBIDDEN" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-java@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting Java to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Jan 2014 01:23:54 -0000 > The 'nasty FreeBSD bug' is that running the latest OpenJDK 6 or 7 will > cause pretty much all version of FreeBSD back to 8.0 to instantly > reboot. This is actually a FreeBSD kernel bug. > Watch the freebsd-announce@... list -- there will be at least an Errata > notice for all supported releases. I understand the desire to protect people from bad effects, but this lockout of every Java port (since everything pretty much depends on openjdk) is quite extreme. Can we please have some more information about: * the nature of the bug * how far back do we have to revert openjdk7 to avoid the problem I've got a huge reliance on Java on production servers and this makes me very nervous. I also had planned an upgrade from FreeBSD 9.0 to 9.2 on a server today and this can't go ahead since I cannot install an updated openjdk. If this is an obscure bug which is in all versions of the openjdk against all versions of freebsd, could someone please revert the FORBIDDEN flag on these ports, since its only effect is to: * make users believe that FreeBSD is not a good platform for Java * stop users from upgrading from any previous versions of Java, or otherwise update systems If this is a serious problem only in the latest version of Java (eg. 1.7.0_45) then can we revert the port to a known working version? At any rate, more information would be great since I've already got 1.7.0_45 in production on a couple of machines and I need to know what to look out for. Thanks Ari -- View this message in context: http://freebsd.1045724.n5.nabble.com/open-jdk7-marked-FORBIDDEN-tp5873171p5873612.html Sent from the freebsd-java mailing list archive at Nabble.com.