Date: Mon, 24 Apr 2000 14:03:41 -0700 (PDT) From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> To: jkh@zippy.cdrom.com (Jordan K. Hubbard) 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 Message-ID: <200004242103.OAA11668@gndrsh.dnsmgr.net> In-Reply-To: <14100.956602664@zippy.cdrom.com> from "Jordan K. Hubbard" at "Apr 24, 2000 11:57:44 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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. I have never been able to keep our ET Inc based routers any where near up to date as far as kernels go, no, they don't use kld's, they use .o's, but it is caused by the same set of problems. I do know from interacting with Dennis at ET Inc that the changes in the interfaces of the FreeBSD kernel have kept him from even trying to be very up to date with driver code. I also have a kld from a source I can't say, to support hardware I can't tell about... (No, this is not a straw man, it's called NDA red tape :-(). -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004242103.OAA11668>