Hello, I figured out the problem here, so thought I'd share it for the record. The problem was that the mkinitrd package was not getting included by pungi. The log I quoted below which shows an initrd being created is actually pungi creating the initrd for the anaconda installer itself, not the installed system. I added mkinitrd to the manifest and voila it worked. Cheers Sean Sean Langford wrote: > Hello, > > I'm using pungi to spin a custom distribution with some installation > automations using the anaconda kickstart mechanism. This mailing list > has been invaluable to accomplish what I have thusfar. > > However, I have a need to include a patched fedora kernel. I've > followed the guide here: > > http://fedoraproject.org/wiki/Docs/CustomKernel > > and included the resulting kernel rpm in the build manifest and in my > local repo, tagged with my own invented distro tag;. Pungi correctly > packages and then anaconda installs and boots this kernel but pungi does > not seem to include an initrd. The logs seem to indicate that it > created one: > > >From pungi log: > >> Found keymap override, using it >> No i586 kernel, trying i686... >> unpacking >> /opt/build/work/analyzer-os/src/uos/output/7/Everything/i386/os/g4k/kernel-2.6.22.9-3268.il8.i686.rpm.i686 >> Building initrd.img >> Wrote /tmp/makebootdisk.initrdimage.19125 (3528k compressed) >> Building isolinux directory >> > however anaconda does not seem to be installing it. Its not clear to me > how the pungi-anaconda-kernel-initrd relationship is all mapped out. > Can anyone point me in the right direction? > > Thanks > > Sean > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
