Date: Mon, 24 Apr 2000 11:30:58 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Linux emulation scripting fix to be committed to 5.x and 4.x wednesday Message-ID: <Pine.BSF.4.21.0004241129230.62105-100000@salmon.nlsystems.com> In-Reply-To: <200004231855.LAA63309@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 23 Apr 2000, Matthew Dillon wrote: > There's another good reason to MFC the linux patch on wednesday... > that is, to do it at the same time the SMP cleanup is MFC'd, and that > is because both patch sets require the linux kernel module to be > recompiled and I'd rather not force people to do that twice. > > The SMP patchset, in fact, requires that all kernel modules be > recompiled due to the locks that were removed from the spl*() macros. > This is something I would contemplate doing for 4.0->4.1, but not > something I would consider for 4.1 onward. Even though 4.0 is the > most stable .0 release we've ever had, it's still a .0. > > I wonder if it makes sense to add a release id to the module header > and have the module loader refuse (unless forced) to load modules that > are out-of-date with the kernel? This sounds quite reasonable. Perhaps you should commit the linux patch to -current right now and then merge it on Wednesday. That would give plenty of time for any teething problems to show up. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 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?Pine.BSF.4.21.0004241129230.62105-100000>