> 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?
We actually have a whole module dependancy and versioning system more or
less ready to go into -current. It could have gone in for 4.0, but we
wouldn't have had time to test it. I would avoid rolling anything
half-assed at this point in time.
BTW; whilst I think Poul was entirely the wrong person to raise the
issue, I agree that you probably want to hang back on MFCing the linux
scripting changes for a week or so. This is really just common sense.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
