Richard Wackerbarth writes:
> > When we do a 'make install' on the kernel, it automatically copies
> > /kernel to /kernel.old, and copies the new kernel in ... is there no way
> > of extending this to the modules?
> >
> > The one thing I was thinking might be to have it so that if you
> > 'load kernel.old' (ie. kernel didn't boot properly, so you have to
> > revert), when it loads its modules, it loads <module>.old to go along with
> > it...
> >
> > Basically, the modules are tied to the kernel, so is there any way
> > of having them install along with the kernel ... ?
>
> Peter W. was working on this but it wasn't going to be ready in time for the 4.0
> freeze. Therefore it got put "on hold" until 4.0 gets released. Expect it soon
> thereafter.
How about solving a simpler problem: have kldload fail if the
module is not "compatible" with the currently running kernel.
For starters, we could define "compatible" as something simple, eg.:
- build date must be the same day
- Same OSRELDATE
- ??
-Archie
___________________________________________________________________________
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
