From owner-freebsd-chat@FreeBSD.ORG Fri Sep 1 05:06:48 2006 Return-Path: X-Original-To: freebsd-chat@freebsd.org Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45DFF16B1B3 for ; Fri, 1 Sep 2006 05:06:35 +0000 (UTC) (envelope-from sgeorge.ml@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7078243D49 for ; Fri, 1 Sep 2006 05:06:33 +0000 (GMT) (envelope-from sgeorge.ml@gmail.com) Received: by qb-out-0506.google.com with SMTP id a10so126425qbd for ; Thu, 31 Aug 2006 22:06:32 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MuhKVnDA+IIMsIO/NhEP9hWHxnsYC6B/vnoSfbsJacIMRaoNumevnihmldfiGXw6dogWUcACGG4G2x+7/1TYgjKfc/uDeaSg2Fsib52KzKWGE0r/IfokkdCdeF/vJtIhqD+0xkesrwyyfateH7t4kw55ie+GOkzfMUwQ0q2TevU= Received: by 10.35.87.8 with SMTP id p8mr2186607pyl; Thu, 31 Aug 2006 22:05:00 -0700 (PDT) Received: by 10.35.51.18 with HTTP; Thu, 31 Aug 2006 22:04:52 -0700 (PDT) Message-ID: Date: Fri, 1 Sep 2006 10:34:52 +0530 From: "Siju George" To: "Marc G. Fournier" In-Reply-To: <20060831192632.T82634@hub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060830232723.GU10101@multics.mit.edu> <98f5a8830608301731s2b0663e3g94b0bd32f8a06a78@mail.gmail.com> <950621ad0608310654h78ae0023g346abd108815ae72@mail.gmail.com> <20060831110112.J82634@hub.org> <20060831184715.B82634@hub.org> <44F7619B.8010609@evilkittens.org> <20060831192632.T82634@hub.org> Cc: miros-discuss@mirbsd.org, misc@openbsd.org, netbsd-users@netbsd.org, Gilles Chehade , freebsd-chat@freebsd.org Subject: Re: The future of NetBSD X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Sep 2006 05:06:48 -0000 On 9/1/06, Marc G. Fournier wrote: > On Fri, 1 Sep 2006, Gilles Chehade wrote: > > > Marc G. Fournier wrote: > >>> > >>> I doubt that'll be productive -- NetBSD, FreeBSD and OpenBSD have all > >>> different goals... > >> > >> Even at the kernel level? Look at device drivers and vendors as one > >> example ... companies like adaptec have to write *one* device driver, for, > >> what, 50+ distributions of linux ... for us, they need to write one for > >> FreeBSD, one for NetBSD, one for OpenBSD, and *now* one for DragonflyBSD > >> ... if we had *at least* a common API for that sort of stuff, it might be > >> asier to get support at the vendor level, no? > >> > > > > How would a common API provide more support from the vendor ? What does the > > API have to do with releasing documentation ? > > I'd rather have Adaptec provide a source code driver for their cards > directly, then have Scott Long have to fight with unavailability of > documentation itself ... if the driver works, what do we need > documentation for? > Marc, Some time back we ( OpenBSD community and some others in other BSD/Linux communities ) had mailed Adaptec to release the Documentation for their RAID Chipsets. One of the mail's from the adaptec personnel said. "We have a disclaimer because there may be corner cases" Which adaptec would not have encountered before releasing the drivers. A *working* driver doesnot mean much when you bring to the picture things like these. Forget Corner cases if you want to use your card on newer hardwre that comes out everyday you will find that the driver needs to be worked on. And it is very important if you are interested in the Stability and Security of your System. Forget about the vendor giving you a fix for every problem you face. The would most probably tell you to upgrade your hardware. But if you had the documentation available for all if not you some one who knows to Code could fix it for you. The vendor loses nothing by freeing the docmentation of their hardware. On the contrary by doing so they ensure their is supported on wider OS platforms and work together well with other hardware. This helps in selling more of their hardware and also since it is used by more people the corner cases will be less because there is a chance that people would encounter them more quiclky and since the documentation is free it will be fixed more quickly. And there is no real reason ( in my opinion ) in exerting some pressure on vendors to release the documentation. Actually it is for their benefit :-) Hope this Helps Kind Regards Siju