From owner-freebsd-arch@FreeBSD.ORG Thu Jan 6 04:18:25 2011 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0E63106564A for ; Thu, 6 Jan 2011 04:18:25 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3D26D8FC08 for ; Thu, 6 Jan 2011 04:18:24 +0000 (UTC) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.4/8.14.4/NETPLEX) with ESMTP id p064IO4t010799; Wed, 5 Jan 2011 23:18:24 -0500 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.2.6 (mail.netplex.net [204.213.176.10]); Wed, 05 Jan 2011 23:18:24 -0500 (EST) Date: Wed, 5 Jan 2011 23:18:24 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Garrett Cooper In-Reply-To: Message-ID: References: <20110103220153.69cf59e0@kan.dnsalias.net> <20110104082252.45bb5e7f@kan.dnsalias.net> <20110105124045.6a0ddd1a@kan.dnsalias.net> <20110105175926.GA2101@vniz.net> <20110106024403.GB22349@vniz.net> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-1307206911-1294287504=:11613" Cc: arch@freebsd.org, Scott Long Subject: Re: Linux kernel compatability X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jan 2011 04:18:25 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-1307206911-1294287504=:11613 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Wed, 5 Jan 2011, Garrett Cooper wrote: > On Wed, Jan 5, 2011 at 6:53 PM, Daniel Eischen wro= te: >> >> Has anyone asked, instead of putting Linux shims into FreeBSD, >> why aren't FreeBSD shims put into Linux? =A0If the FreeBSD ABI/KPI >> is supposedly more stable than Linux, then wouldn't it make >> more sense to do it that way? >> >> And I suppose part of the answer to that question is, it would >> not be acceptible to the Linux folks. > > Pretty sure it's because many hardcore Linux folks don't like the > BSD license (and the fact that it's business friendly, i.e. closed > source drivers are ok?). The OSS soundsystem was a prime example of > what happens when code that's BSD licensed gets put in the Linux > kernel (well, ok... there were other reasons but as I was reading that > was a big source of contention with the Linux crowd and that system, > despite the fact that it was better than ALSA for a long time, and is > still better in some ways [1]). Well, they would be shims that just implement the FreeBSD API using Linux APIs and some glue, so I don't see why they wouldn't or couldn't be GPL licensed. I'm assuming (perhaps incorrectly) that Jeff's proposed Linux shims are BSD licensed, so the converse should be doable as well. But regardless, Jeff's already done the work, so they should just get imported into FreeBSD someplace. --=20 DE ---559023410-1307206911-1294287504=:11613--