From owner-freebsd-hackers Fri Oct 19 9:19:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id C876137B407; Fri, 19 Oct 2001 09:19:37 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id KAA74999; Fri, 19 Oct 2001 10:36:11 -0700 (PDT) Date: Fri, 19 Oct 2001 10:36:09 -0700 (PDT) From: Julian Elischer To: Mike Smith Cc: babkin@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, msmith@mass.dis.org Subject: Re: FYI In-Reply-To: <200110190319.f9J3Jfo06174@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 18 Oct 2001, Mike Smith wrote: > > Well, honestly, FreeBSD makes the life of the developers of third-party > > binary-only drivers fairly difficult. > > It does? On the whole, actually, I'd say we do a pretty good job of > making it easy. > > > The reason is that there > > are a lot of API changes happening between the releases (take > > Julian Elisher's recent problem for example). > > It's a poor example. Drivers don't involve themselves in the sysinit > chain. welllllll it gets involved.. if you redefine the SYSINIT values, old drivers's aren't 'notified' (should be a module but the supplier didn't make one..) > > > So the driver writers > > are forced to at least recompile their drivers for each release. > > This isn't typically the case, actually. 4.x has in fact been very > good in this regard. with the above exception, I agree. though in userland, the library changes have caused us some grief. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message