[makedumpfile] config file -- OSRELEASE
bwalle at suse.de
Thu May 31 04:57:57 EDT 2007
* Ken'ichi Ohmichi <oomichi at mxs.nes.nec.co.jp> [2007-05-30 13:13]:
> 2007/05/29 21:30:58 +0200, Bernhard Walle <bwalle at suse.de> wrote:
> >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?
> The reason is that makedumpfile gets a running kernel's page_size as
> a 1st-kernel's page_size. If they are different, makedumpfile cannot
> analyze /proc/vmcore and it fails. So I think a configuration file
> should be created while 1st-kernel is running.
I also didn't find a possibility to get the page size from a kernel
image without running the executable.
> >It's a big problem because my plan was to ship the configuration files
> >with the kernel RPMs in SLES. However, we don't build the kernels on
> >systems which run the kernel that is just built -- so that's not
> It is a good idea to ship the configuration files with the kernel RPMs.
> I think you can do it with current implementation, because you need
> only one configuration file for one kernel image.
> I think you can ship configuration files as follows:
> 1. Build a kernel file and a debuginfo file.
> 2. Boot the system with the above kernel file.
> 3. Generate a configration file from a debuginfo file.
> 4. Ship the configration file with the kernel RPM.
> Any problem to follow the method above ?
No, that's not possible because it would change our whole build
process. However, I just replace the OSRELEASE now after generating
the config file with the kernel that's built and change the page size
according to the .config on IA64. That works for now. I know it's not
the best solution, but the only practicable for now.
SUSE LINUX Products GmbH Tel. +49 (911) 74053-0
Maxfeldstr. 5 GF: Markus Rex
90409 Nürnberg, Germany HRB 16746 (AG Nürnberg)
OpenPGP DDAF6454: F61F 34CC 09CA FB82 C9F6 BA4B 8865 3696 DDAF 6454
More information about the kexec