From owner-freebsd-current@FreeBSD.ORG Wed Jan 12 17:26:18 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1E6016A4CE for ; Wed, 12 Jan 2005 17:26:18 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 773B243D1D for ; Wed, 12 Jan 2005 17:26:18 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j0CHQANJ016301; Wed, 12 Jan 2005 09:26:10 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j0CHQ8DF016300; Wed, 12 Jan 2005 09:26:08 -0800 (PST) (envelope-from sgk) Date: Wed, 12 Jan 2005 09:26:08 -0800 From: Steve Kargl To: Richard Coleman Message-ID: <20050112172608.GB16201@troutmask.apl.washington.edu> References: <41DF253C.5040705@fer.hr> <20050108005540.GB93568@troutmask.apl.washington.edu> <20050108030707.GA3656@frontfree.net> <20050108034424.GA94365@troutmask.apl.washington.edu> <41E54C51.4000300@fer.hr> <20050112164022.GD28786@odin.ac.hmc.edu> <41E553EB.10809@criticalmagic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E553EB.10809@criticalmagic.com> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Ivan Voras Subject: Re: MFC wishlist X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 17:26:18 -0000 On Wed, Jan 12, 2005 at 11:44:27AM -0500, Richard Coleman wrote: > Brooks Davis wrote: > > > >No, because the project has no ability to "assign > >priority/resources". If someone who has is intrested and capable time > >to work on it, does so in time, then it may be done, if not, it > >won't. > > > > Should we take this to mean that none of the developers are interested > in ULE any more? That's the general feeling I get these days. Just > curious. > As Brooks stated, Jeff is busy. He works on it when he can. My problem is that system simply freezes. I can't get a kernel dump, so its hard to provide more info. I'll also note that I believe that there are recent KSE/pthread changes in -current that may be exposing a latent bug in ULE. Jeff's recent ULE changes may actual work on 5.3. No one is stopping you from backport the changes. -- Steve