From owner-freebsd-current Tue Apr 1 19:47:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA02600 for current-outgoing; Tue, 1 Apr 1997 19:47:30 -0800 (PST) Received: from palrel1.hp.com (palrel1.hp.com [15.253.72.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA02595 for ; Tue, 1 Apr 1997 19:47:28 -0800 (PST) Received: from fakir.india.hp.com (fakir.india.hp.com [15.10.40.3]) by palrel1.hp.com with ESMTP (8.7.5/8.7.3) id TAA24233 for ; Tue, 1 Apr 1997 19:47:22 -0800 (PST) Received: from localhost by fakir.india.hp.com with SMTP (1.37.109.20/15.5+ECS 3.3) id AA124144681; Wed, 2 Apr 1997 09:18:01 +0500 Message-Id: <199704020418.AA124144681@fakir.india.hp.com> To: freebsd-current@freebsd.org Subject: Re: Kernel Module System Date: Wed, 02 Apr 1997 09:18:01 +0500 From: "A JOSEPH KOSHY" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A suggestion for Doug: how about adding a version number in the LKM which can be compared against that expected by the kernel. The idea is to warn and/or disallow loading of older LKMs into the kernel. The version number would be changed whenever say, a binary incompatibility is introduced. Do we have an ``approved set'' of kernel routines (a Driver Development API) that are callable by drivers? Koshy My Personal Opinions Only