From owner-freebsd-hackers Thu Oct 23 07:52:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA01381 for hackers-outgoing; Thu, 23 Oct 1997 07:52:42 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA01375 for ; Thu, 23 Oct 1997 07:52:38 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id AAA00606; Fri, 24 Oct 1997 00:18:53 +0930 (CST) Message-Id: <199710231448.AAA00606@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Archie Cobbs cc: freebsd-hackers@freebsd.org Subject: Re: Broken device LKM in 2.2 In-reply-to: Your message of "Mon, 20 Oct 1997 17:00:23 MST." <199710210000.RAA11140@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Oct 1997 00:18:51 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I guess nobody makes device type LKM's in 2.2.. but sys/lkm.h is > broken with respect to them. Here's a hack that fixes this. Perhaps > the "name ## _module", which is different from the other module > types, is there for some reason (?) IIRC it's there to avoid symbol conflicts with statically loaded versions. Could be wrong of course; there's nothing in the CVS log. > Anyway, it's incompatible with the DISPATCH macro defined later in > the file, and this fixes it... Has anyone looked at this? Should we buy it? mike