On 05/23/2014 07:35 PM, Chris Murphy
wrote:
OK. First of all, you do not need grubby to create the
initramfs files. The kernel rpm (or not kernel-core rpm) has
a valid initramfs as part of the rpm. This is what the
bootloaders see if new-kernel-pgm/grubby has yet to run.
new-kernel-pkg --mkinitrd --dracut calls dracut to build the
initramfs, the initramfs isn't in the RPM. And grubby is
supposed to get called, I think from within new-kernel-pkg, to
update any of the supported bootloader configuration files.
On Fedora 20 do:
rpm -ql kernel | grep boot
and on rawhide/Fedora 21 do:
rpm -ql kernel-core | grep boot
The rpm delivers a initramfs and then new-kernel-pkg rebuilds
initramfs depending on what is really on you system.
No. The RPM delivers a filename for the initramfs to handoff to dracut to build the file. It's accounted for in the RPM because the RPM is responsible for providing the file, but it's via dracut. During kernel install, the kernel file appears yet the initramfs doesn't, until well into the dracut process creating it.
Also, when I use rpm2cpio kernel-core-3.15.0-0.rc6.git0.1.fc21.x86_64.rpm | cpio -idmv there is no initramfs file extracted from the RPM.
Plus, that .rpm is only 18MB. When extracted with the above command, it's 23.4MB of files. A non-host-only initramfs for that kernel is 44MB, and is already gzipped. That can't be inside an 18MB RPM. Even a smaller host-only RPM can't fit, plus it's useless - it would't work on anything so there'd be no point to include it.
Chris |
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
