From owner-freebsd-current Mon Apr 24 14:29:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id D634D37BC41 for ; Mon, 24 Apr 2000 14:29:29 -0700 (PDT) (envelope-from rkw@dataplex.net) Received: from nomad.dataplex.net (24.28.73.209) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Mon, 24 Apr 2000 16:29:23 -0500 From: Richard Wackerbarth To: "Rodney W. Grimes" Subject: Re: SMP changes and breaking kld object module compatibility Date: Mon, 24 Apr 2000 16:29:22 -0500 X-Mailer: KMail [version 1.1.41] Content-Type: text/plain References: <200004242114.OAA11696@gndrsh.dnsmgr.net> In-Reply-To: <200004242114.OAA11696@gndrsh.dnsmgr.net> Cc: current@freebsd.org MIME-Version: 1.0 Message-Id: <00042416292202.09469@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Apr 2000, you wrote: > > On Mon, Apr 24, 2000 at 02:02:28PM -0500, Richard Wackerbarth wrote: > > > That is also partly why you are also lacking the respect and support of > > > a wider audience. If you act like FreeBSD is just a "developer's > > > sandbox", that's what it will be. If you want it to be something > > > greater than that, you must consider what you are doing to third party > > > developers and end users. > > > > Developers and early adopters are the ones tracking -STABLE. Users are > > installing binary snapshots and releases. > > Some users do install snapshots and/or releases. Snap shots occur on a > regular basis and are affected by this change in API. > > > No-one in their right mind would release a module for "4.0-STABLE > > sometime between april and may". They release for 4.0-RELEASE or > > 4.1-RELEASE, this would not cause problems for those people. > > Ahh.. the problem occurs with user Z running snap 4.0-stable 4/30 when > trying to use vendor X module for 4.0-release. Get it?? I certainly do. Your "attribute deamon" left out one level of identification. There are two problems here: 1) How often do the interfaces change? IMHO, too often. These sandboxers have no concept of third party issues. 2) How do we identify the version of the interface? Even if we ignore the number of "different interfaces", being able to readily recognize which one a customer has is important. Maybe the developers need to be sentenced to a tour on the customer service lines. It might open their eyes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message