Date: Sat, 05 Apr 1997 04:42:16 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Doug Rabson <dfr@nlsystems.com> Cc: Peter Dufault <dufault@hda.com>, current@freebsd.org Subject: Re: Breaking the lkm DISPATCH macro Message-ID: <4365.860244136@time.cdrom.com> In-Reply-To: Your message of "Sat, 05 Apr 1997 13:14:18 %2B0100." <Pine.BSF.3.95q.970405131343.8538E-100000@herring.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Does this mean that my OSS module will stop working? Sigh.. That brings up a very good point, which is that we need to start thinking about contacting vendors when we do stuff which will cause their stuff to break. I realize that everyone can't keep track of every single commercial product available for FreeBSD (not that it's exactly *hard* right now though :) and its dependencies, so all I'm asking is that if a user (like Doug here) raises an advance concern or we start getting bug reports from our early BETA customers WRT some commercial product, that should raise a *really big red flag* with us. The commercial sector contains some of our best current and potential allies, and the last thing we need to do is alienate them by breaking interfaces without at least trying to contact their developers in advance or working out *some* sort of arrangement. Don't make their customers be the first ones to tell them that FreeBSD busted their software, eh? ;-) In this case it's not such a big deal since OSS is not currently guaranteed to run under 3.0, nor is 3.0 mentioned as supported in any way, so one could argue that user of it were on thin ice anyway. What *would* be a big deal, however, would be if it took Hannu until the actual release day of 3.0 to find out about the incompatibility! :-) Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4365.860244136>