From owner-freebsd-chat Sat Apr 5 08:50:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA16223 for chat-outgoing; Sat, 5 Apr 1997 08:50:41 -0800 (PST) Received: from mail.konnections.com (mail.konnections.com [192.41.71.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA16218 for ; Sat, 5 Apr 1997 08:50:38 -0800 (PST) Received: from castle (root@ip215.konnections.com [192.41.71.215]) by mail.konnections.com (8.8.3/8.8.3) with SMTP id JAA15683; Sat, 5 Apr 1997 09:49:55 -0700 (MST) Message-ID: <3347D2ED.638325A6@konnections.com> Date: Sun, 06 Apr 1997 09:44:29 -0700 From: mike allison Organization: Publisher -- Burning Eagle Book Company X-Mailer: Mozilla 3.0 (X11; I; Linux 2.0.0 i486) MIME-Version: 1.0 To: "Jordan K. Hubbard" CC: freebsd-chat@freebsd.org Subject: Re: Breaking the lkm DISPATCH macro References: <4365.860244136@time.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-chat@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > 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. Jordan: Does FreeBSD have a "registry" for commercial vendors? Some way that you can broadcast or post announcements on specific changes/potential changes that they can test and plan for for the next release? As you siad, there may well be a time that some "Killer App" may be so important to users that development might have to consider it's viability BEFORE changes are made. I realize that vendors have a responsibility, but as long as their aware of the changes (whether compatibility is guaranteed or not) then we can all work better together.