From owner-freebsd-current Mon Apr 24 11:56:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E9E9437B85F for ; Mon, 24 Apr 2000 11:56:51 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA14103; Mon, 24 Apr 2000 11:57:44 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: "Rodney W. Grimes" Cc: n@nectar.com (Jacques A . Vidrine), rkw@dataplex.net (Richard Wackerbarth), freebsd-current@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility In-reply-to: Your message of "Mon, 24 Apr 2000 09:09:10 PDT." <200004241609.JAA11108@gndrsh.dnsmgr.net> Date: Mon, 24 Apr 2000 11:57:44 -0700 Message-ID: <14100.956602664@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Gee, is that perhaps because FreeBSD keeps breaking the ABI to modules > so every vendor that has ever tried to use them has been bitten by the > fact that they have to maintain N version for each branch of FreeBSD??? Can you list some specific examples? I'm not trying to be a wise-ass, I'm trying to figure out which vendors are using KLDs in general since I've still yet to actually bump into a real-life example of this kind of breakage in the field. I'm not saying that it's never happened, I'm simply saying that I've not seen it and would like some details on such incidents - company name and module type will do fine. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message