From owner-freebsd-current@FreeBSD.ORG Wed May 28 09:50:07 2003 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 25EF837B401 for ; Wed, 28 May 2003 09:50:07 -0700 (PDT) Received: from smtpout.mac.com (A17-250-248-97.apple.com [17.250.248.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B01E43F3F for ; Wed, 28 May 2003 09:50:06 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h4SGnwNf008906 for ; Wed, 28 May 2003 09:50:06 -0700 (PDT) Received: from mac.com (mac6.mpi-softtech.com [67.33.6.42]) (authenticated bits=0) by mac.com (Xserve/MantshX 2.0) with ESMTP id h4SGluDI020527; Wed, 28 May 2003 09:47:57 -0700 (PDT) Date: Wed, 28 May 2003 11:48:00 -0500 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Paul Richards From: dave In-Reply-To: <20030528163555.GJ6015@survey.codeburst.net> Message-Id: <248EFE3A-912C-11D7-AD30-000393D6D7EE@mac.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) cc: Q cc: Scott Long cc: freebsd-current@freebsd.org Subject: Re: policy on GPL'd drivers? 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: Wed, 28 May 2003 16:50:07 -0000 > > I don't think anyone is talking about symbol versioning. The issue is > stamping the API at a particular point in time that shows it behaves in > a specified guaranteed way. > > The module system has all the hooks to deal with versioning. What's > missing is not the mechanism but the knowledge, i.e. we don't know that > module X won't work with kernel Y becuase we don't know what APIs > module > X may invoke and whether kernel Y supports them. > > The only true solution to this is to version the APIs in the kernel and > use the module versioning hooks to not load modules if the version > isn't > the right one. Will this require *any* new infrastructure to implement properly? Or is it simply a matter of maintaining API metadata regarding versions. I should probably try to understand the existing stuff more before asking too many more questions. > > -- > Tis a wise thing to know what is wanted, wiser still to know when > it has been achieved and wisest of all to know when it is unachievable > for then striving is folly. [Magician] > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" >