From owner-freebsd-security@FreeBSD.ORG Sun Sep 5 10:47:30 2010 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD67E1065697; Sun, 5 Sep 2010 10:47:30 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 91A728FC13; Sun, 5 Sep 2010 10:47:30 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id EA62046B5C; Sun, 5 Sep 2010 06:47:29 -0400 (EDT) Date: Sun, 5 Sep 2010 11:47:29 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Hans Petter Selasky In-Reply-To: <201009011902.06538.hselasky@c2i.net> Message-ID: References: <201009011653.o81Grkm4056064@fire.js.berklix.net> <201009011902.06538.hselasky@c2i.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Stable , Deb Goodkin , security-officer@freebsd.org, gljennjohn@googlemail.com, freebsd security , "Julian H. Stacey" Subject: Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Sep 2010 10:47:30 -0000 On Wed, 1 Sep 2010, Hans Petter Selasky wrote: >>> - Or whatever other method to get ISDN back in kernel ? >> >> It seems code exists :-) >> >> http://old.nabble.com/ISDN4BSD-on-8-current-td23919925.html >> ISDN4BSD package has been updated to compile on FreeBSD >> 8-current >> >> http://www.selasky.org/hans_petter/isdn4bsd/ >> >> Apparently needs massaging into main FreeBSD tree. > > I agree that my I4B code should be re-written somewhat before committed. > Possibly we should update the API's present too, to support IP-telephony > aswell. Just to clarify things a little for those following it: the original I4B code was removed for entirely practical reasons: it couldn't run without the Giant lock, and support for the Giant lock over the network stack was removed. I'm happy to see ISDN support reintroduced as long as it will see ongoing maintenance/etc. I'm not familiar with Hans's most recent code, but the integration of his USB stack and his recent receipt of a FreeBSD commit bit suggest a promising future. I would suggest trying to rope in a reveiwer and collaborator (perhaps someone like Bjoern Zeeb?) to work through it before considering a merge, however. This is especially important with projects like VIMAGE, network stack parallelism projects, etc, on-going to make sure that the new ISDN code will be able to support these new features rather than become a potential obstacle (as the old code did for the MPSAFEty work). Robert