On 4 Jun 2003, maillists (josef radinger) wrote: > you will have to rebuild your initrd, as soon as the modules in your old > initrd wont load on your new kernel. depends on your config.
i'm not actually changing the .config. i'm just downloading each new "bk" upgrade and rebuilding with the same .config file, strictly for personal testing purposes. so, technically, the modules themselves won't have changed, except for (as i wondered) some possible internal module versioning value that would cause problems. > you can compile your kernel (have not looked into 2.5, but i would bet a > lot that this feature is in the new series too) with module-versions. > modules wont load, if there is some version-mismatch between kernel and > module. > you could use strings and grep to see the version: > > [EMAIL PROTECTED] /]$ strings /lib/modules/2.4.9/kernel/drivers/block/loop.o > /lib/modules/2.4.20/kernel/drivers/block/loop.o |grep kernel_version > kernel_version=2.4.9 > kernel_version=2.4.20 i guess the easiest thing is just to test it and see what happens. rday -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
