From owner-freebsd-chat@FreeBSD.ORG  Thu Aug 31 23:38:36 2006
Return-Path: <owner-freebsd-chat@FreeBSD.ORG>
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 E52FC16A4DF;
	Thu, 31 Aug 2006 23:38:36 +0000 (UTC)
	(envelope-from marco@dev.peereboom.us)
Received: from dev.peereboom.us (adsl-67-64-89-177.dsl.austtx.swbell.net
	[67.64.89.177])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1F57E43D45;
	Thu, 31 Aug 2006 23:38:35 +0000 (GMT)
	(envelope-from marco@dev.peereboom.us)
Received: from dev.peereboom.us (marco@localhost.peereboom.us [127.0.0.1])
	by dev.peereboom.us (8.13.6/8.13.4) with ESMTP id k7VNI1Ia004513;
	Thu, 31 Aug 2006 18:18:01 -0500 (CDT)
Received: (from marco@localhost)
	by dev.peereboom.us (8.13.8/8.13.4/Submit) id k7VNI0st032687;
	Thu, 31 Aug 2006 18:18:00 -0500 (CDT)
Date: Thu, 31 Aug 2006 18:18:00 -0500
From: Marco Peereboom <slash@peereboom.us>
To: "Marc G. Fournier" <scrappy@freebsd.org>
Message-ID: <20060831231759.GD12837@peereboom.us>
References: <20060830232723.GU10101@multics.mit.edu>
	<98f5a8830608301731s2b0663e3g94b0bd32f8a06a78@mail.gmail.com>
	<c6d37fe0608310259k12fe629eve59e59042fcfdb4c@mail.gmail.com>
	<Pine.BSM.4.64L.0608311312190.8977@odem.66h.42h.de>
	<950621ad0608310654h78ae0023g346abd108815ae72@mail.gmail.com>
	<20060831110112.J82634@hub.org>
	<f34ca13c0608310843p4e28b57eoec2f60737c034ddb@mail.gmail.com>
	<20060831184715.B82634@hub.org> <44F7619B.8010609@evilkittens.org>
	<20060831192632.T82634@hub.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060831192632.T82634@hub.org>
User-Agent: Mutt/1.5.12-2006-07-14
Cc: miros-discuss@mirbsd.org, misc@openbsd.org, netbsd-users@netbsd.org,
	Gilles Chehade <veins@evilkittens.org>, 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
	<freebsd-chat.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chat>
List-Post: <mailto:freebsd-chat@freebsd.org>
List-Help: <mailto:freebsd-chat-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Aug 2006 23:38:37 -0000

This is the most retarded thing I heard in weeks.

On Thu, Aug 31, 2006 at 07:28:29PM -0300, 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?
>