Date: Mon, 24 Apr 2000 09:02:53 -0500 From: Richard Wackerbarth <rkw@dataplex.net> To: "Jeroen C. van Gelderen" <jeroen@vangelderen.org> Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP changes and breaking kld object module compatibility Message-ID: <00042409025301.09317@nomad.dataplex.net> In-Reply-To: <39044A19.F6F4E479@vangelderen.org> References: <200004231909.MAA09128@gndrsh.dnsmgr.net> <00042404464300.09955@nomad.dataplex.net> <39044A19.F6F4E479@vangelderen.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 24 Apr 2000, Jeroen C. van Gelderen wrote: > I don't think it was ever recommended that you upgrade your kernel > without upgrading and rebuilding the modules (better still, world) at > the same time. So this wouldn't really have an adverse effect, would it? Such a policy is totally unacceptable for "released" systems. Pre-release, I can accept it because the interfaces are still being tested and redesigned as needed. However, once a system is released, the users MUST have the ability to upgrade parts of the system without rebuilding everything. In fact, the user may be unable to rebuild parts of the system because he lacks the resources, be they hardware or source code. In particular, I, as a user, need to be able to purchase proprietary code and expect to be able to run it on a system. I further expect to be able to upgrade the kernel or shared libraries within the same release series and still use the same binary of the proprietary program. If this were not the case, we could argue that there is no need for the "linux compatability modes. Every Linux binary could just be recompiled into the FreeBSD format. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00042409025301.09317>