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.
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 On Wed, 2003-06-04 at 16:38, Robert P. J. Day wrote: > undoubtedly a simple question, but is there any compelling > reason to rebuild my initrd.img file if i'm just upgrading from > 2.5.70-bk8 to 2.5.70-bk9, and i can confirm that none of the > modules in the current initrd.img have changed as a result of > that kernel bk upgrade? > > in short, i've rebuilt my kernel and modules directories, > but do i need to build a new initrd.img? (yes, i know it's > easy, but i'm more curious about whether it's necessary -- > whether there's some versioning info implanted in the file). > > rday > > -- > > Robert P. J. Day > Eno River Technologies > Unix, Linux and Open Source training > Waterloo, Ontario > > www.enoriver.com -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
