> /sbin/insmod -f cpqfc.o
> Warning: kernel-module version mismatch
> cpqfc.o was compiled for kernel version 2.2.12-32
> while this kernel is version 2.2.12-20
>
> cpqfc.o: init_module: Device or resource busy
There's an option to include kernel version info in modules. You can run
make xconfig
and turn it off; this is usually a good idea, and I suggest you do it. In
general, you're defended against loading the wrong modules by where
they're stored:
[summer@possum .etc]$ find /lib/modules/ -type d -maxdepth 1
/lib/modules/
/lib/modules/2.2.12-20
/lib/modules/2.2.13
/lib/modules/2.2.13J1
/lib/modules/2.2.14
/lib/modules/2.3.45
/lib/modules/2.3.47
/lib/modules/2.3.49
/lib/modules/2.3.99-pre1
/lib/modules/2.3.99-pre3
/lib/modules/2.3.99-pre5
[summer@possum .etc]$
If I build a new 2.3.99-pre5, I can be sure that any old 2.3.99-pre5
modules will work with the new one; probably all 2.3.99 modules will.
>
> In the kernel version number what does the number after the hyphen signify ?
Someone decided the spec needed repair and had twelve goes at it;-)
Depending on just what in the spec file was changed, the kernels may be
the same. Or very different.
However, individual modules will be the same, at least as far as the
interface goes; there could be differences in function arising from
configuration options.
--
Cheers
John Summerfield
http://os2.ami.com.au/os2/ for OS/2 support.
Configuration, networking, combined IBM ftpsites index.
--
To unsubscribe:
mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
