From owner-freebsd-java Wed Jul 10 16:48:22 2002 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 8E28037B400 for ; Wed, 10 Jul 2002 16:48:20 -0700 (PDT) Received: from gnuppy.monkey.org (wsip68-15-8-100.sd.sd.cox.net [68.15.8.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54EEA43E09 for ; Wed, 10 Jul 2002 16:48:20 -0700 (PDT) (envelope-from billh@gnuppy.monkey.org) Received: from billh by gnuppy.monkey.org with local (Exim 3.35 #1 (Debian)) id 17SRBz-0000rk-00; Wed, 10 Jul 2002 16:48:19 -0700 Date: Wed, 10 Jul 2002 16:48:14 -0700 To: freebsd-java@freebsd.org Cc: Bill Huey Subject: Re: 1.3.1 patchset 7 not quite ready Message-ID: <20020710234814.GE2394@gnuppy.monkey.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i From: Bill Huey Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [A snippet from a private mail I wrote] More comments... I've been using -current pretty heavily and it's definitely stable enough to use everyday. There's build issues, but I've been able to get around all of them so far without too much effort. Who knows, somebody could commit something that'll complete break the system tomorrow. That why I kept the old pre-KSE kernel during the recent roughness with that commit. You just have to update the machine intelligently. "How it's running" 1) The Java2Demo is running rather slow and it has me worried. 2) The SIGUSR1 delivery problem is gone now when I run under -current. 3) The only thing that's left is testing out the signal/exception framework (stack yellow/red zoning). Hopefully, that won't be completely broken. bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message