Re: fresh compile, "unresolved symbols" complaints
On Sun, Apr 02, 2000 at 03:33:21PM -0400, Jeff Gordon wrote:
> > ----- message from George Bonser <grep@shorelink.com> -----
> > If so, did you possibly forget to move the old modules dir out of
> > the way before installing the new modules? If you compiled some things
> > into the kernel that used to be modules, modutils may still be trying to
> > load the module and seeing the old module that was not built with the new
> > kernel, you may be getting all kinds of unresolved symbols.
>
> (Ah so.) Didn't "forget", George; but never knew to do it. :-) "make
> modules" doesn't cover it, then...?
If you use make-kpkg, the resulting debian kernel-image package will
warn you about exactly this and ask you if you want to abort the
installation to let you move it safely out of the way.
Debian packagers can make more informed decisions about the filesystem
arrangement than the kernel developers and this will always be the case,
so use the "smart" tools provided with debian to ease the brain strain.
Unless you're doing strange things to modify your kernel, I'd vote for
make-kpkg.
--
Regards,
Paul
Reply to: