From owner-freebsd-current Mon Apr 24 2:46:58 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 1F21B37B9D3 for ; Mon, 24 Apr 2000 02:46:54 -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 04:46:44 -0500 From: Richard Wackerbarth To: Matthew Dillon Subject: Re: SMP changes and breaking kld object module compatibility Date: Mon, 24 Apr 2000 04:46:43 -0500 X-Mailer: KMail [version 1.1.41] Content-Type: text/plain Cc: freebsd-current@FreeBSD.ORG References: <200004231909.MAA09128@gndrsh.dnsmgr.net> <00042315420301.24082@nomad.dataplex.net> <200004240605.XAA66216@apollo.backplane.com> In-Reply-To: <200004240605.XAA66216@apollo.backplane.com> MIME-Version: 1.0 Message-Id: <00042404464300.09955@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Apr 2000, Matthew Dillon wrote: > : However, I consider your SMP changes VERY destablizing; they BREAK > : lots of modules :-( > > Huh? No they don't. They simply require recompiling the modules. If > they actually broke the modules I wouldn't be trying to MFC it to > -stable. From the USER's perspective, anything that requires me to as much as reload a module/program that I have already installed "breaks" it. The fact that it is only necessary to recompile it in order to fix it only means that it is easy to fix IF I have the source code. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message