From owner-freebsd-current@FreeBSD.ORG Fri Sep 21 10:33:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53E2E16A468 for ; Fri, 21 Sep 2007 10:33:28 +0000 (UTC) (envelope-from fergus@cobbled.net) Received: from mail1.slb.deg.dub.stisp.net (mail1.slb.deg.dub.stisp.net [84.203.253.98]) by mx1.freebsd.org (Postfix) with SMTP id A056113C467 for ; Fri, 21 Sep 2007 10:33:27 +0000 (UTC) (envelope-from fergus@cobbled.net) Received: (qmail 8676 invoked from network); 21 Sep 2007 10:06:40 -0000 Received: from unknown (HELO holyman.cobbled.net) (84.203.180.117) by mail1.slb.deg.dub.stisp.net with SMTP; 21 Sep 2007 10:06:40 -0000 Received: by holyman.cobbled.net (Postfix, from userid 16385) id AEF3F16530; Fri, 21 Sep 2007 10:06:30 +0000 (UTC) Date: Fri, 21 Sep 2007 10:06:30 +0000 From: ttw+bsd@cobbled.net To: freebsd-current@freebsd.org Message-ID: <20070921100630.GA10718@holyman.cobbled.net> Mail-Followup-To: freebsd-current@freebsd.org, John Birrell , Olivier Warin , Darren Reed References: <6385B28C-01D1-459A-9543-E36C89C7F36E@xview.net> <20070920203413.GA13737@what-creek.com> <46F367E0.4000300@freebsd.org> <20070921070347.GA17990@what-creek.com> <46F38B59.9070707@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F38B59.9070707@freebsd.org> Cc: Darren Reed , Olivier Warin , John Birrell Subject: Re: Dtrace port status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 21 Sep 2007 10:33:28 -0000 On 21.09-02:14, Darren Reed wrote: [ ... ] > >Only if it is clean-room coded. > > So find someone who hasn't read that email, write up a spec for the missing > fields that dtrace requires and ask them to implement and commit the change > to the dtrace branch on freebsd.org ? :) this has merit. to be honest, within copyright (UK and EU), i think you could reasonably use structure definitions as they are fundamental to the interaction, not the operation of the code. this has support, though it's not been specifically ruled on in court (certainally not that i'm aware of). there is a much bigger problem around patents and no amount of clean room coding is going to avoid those. ... having said that, nethier is adding some secondary structure -- that is not how patent coverage works, only copyright.