From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 23:46:06 2004 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 B190A16A4CE for ; Mon, 6 Dec 2004 23:46:06 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C0B343D54 for ; Mon, 6 Dec 2004 23:46:06 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id iB6NkrKE070460; Mon, 6 Dec 2004 18:46:53 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Mon, 6 Dec 2004 18:46:53 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: Matt Rowley In-Reply-To: Message-ID: <20041206183904.S88450@bahre.achedra.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/609/Fri Nov 26 15:20:39 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 5.3 and Adaptec raidutils (again) 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: Mon, 06 Dec 2004 23:46:06 -0000 On Mon, 6 Dec 2004, Matt Rowley wrote: > Sorry, I don't have a copy of the original message that went to current@... > A few other files have different license headers, copyrighted by Adaptec, > Distributed Processing Technology Corporation, and I2O Special Interest > Group. The files are: > But these licenses look identical to those in /usr/src/sys/dev/asr/i2o* in > FreeBSD's tree. > These two files: i2omodul.h i2odep.h, in raidutils-0.0.4/raideng/ have a > different I20 license that says "These header files are provided, pursuant to > your I2O SIG membership agreement"... it basically sounds like a no-warranty > disclaimer, but I don't know what the I20 SIG agreement is to which they > referring. I have to wonder at the validity of those licenses, actually. I was looking at them with relation to some i960 work I've been doing, and try as I might, the I2O SIG seems to no longer exist in any form. I'd love to find out otherwise, if only so the license can be clarified. -Ketrien I. Saihr-Kenchedra