Hello, From: Bouchard Louis <louis.bouchard@xxxxxxxxxxxxx> Subject: Re: [PATCH makedumpfile v2 0/4] LZO Compression Support Date: Wed, 28 Mar 2012 09:59:04 +0200 > Hello, > > Le 28/03/2012 09:50, HATAYAMA Daisuke a ?crit : >> >> Yes, I of course agree with the fact that makedumpfile for kdump 2nd >> kernel should always be built in statically linked way. >> >> But I think two problems are different, that is, the problem making >> users easily able to choose build option by autotools, and the problem >> guranteeing that the makedumpfile for kdump 2nd kernel be built always >> statically. >> > > I don't see why it should be statically linked. Debian & Ubuntu both use > a dynamically linked makedumpfile for the 2nd kdump kernel. > > Debian executes makedumpfile on the 'real' root FS while Ubuntu runs it > in the initramfs. It is simply a chroot on the root FS being mounted on > /root. > Thanks. I've noticed the fact on Debian for the first time. Root filesystem can be broken due to filesystem related bugs or disk crash. So, on fedora/RHEL environments, root filesystem is not mounted in kdump initrd/initramfs. Necessary resources in 2nd kernel, including makedumpfile, are all packed in kdump initrd/initramfs. Thanks. HATAYAMA, Daisuke
