Bernhard Walle wrote: > Hi, > > is there any reason why the kernel version saved in the configuration > file is the version of the running kernel and not the version for > which the config file is for? Yep, i figured that was my problem. I copied my vmlinux, which is a 2.6.18-8.el5, to my disk server, which is a 2.6.16.43-0.5-default. I would think the OSRELEASE of the CONFIGFILE generated from 'makedumpfile -g CONFIGFILE -x VMLINUX' would be the version of VMLINUX. Instead, it said: OSRELEASE=2.6.16.43-0.5-default, which caused 'makedumpfile -i' to complain about: CONFIGFILE and VMCORE don't match I think it is a bug? You would want to ensure the version of the VMLINUX and VMCORE match. > > It's a big problem because my plan was to ship the configuration files > with the kernel RPMs in SLES. I love this idea! Thanks, - jay > However, we don't build the kernels on > systems which run the kernel that is just built -- so that's not > possible. > > I think from implementation point of view it's not a problem, that's > why I ask and didn't create a patch. > > > Thanks, > Bernhard >
