https://bugzilla.novell.com/show_bug.cgi?id=798295 https://bugzilla.novell.com/show_bug.cgi?id=798295#c1 --- Comment #1 from Marcus Schaefer <ms@suse.com> 2013-01-14 09:04:28 UTC --- when kiwi creates a new root tree as part of the kiwi prepare step it happens that mkinitrd is called as consequence to the post script of the kernel package. within that environment I agree it's questionable if mkinitrd should be called at all because it doesn't make sense in most cases. But this would be more targeted to the kernel packaging and post script for kiwi it doesn't matter because the kiwi code creates a correct bootloader and splash configuration as part of the image creation step (kiwi --create) which uses the former created new root tree as the root tree and doesn't expect any valid boot or splash configuration in it on first boot of the kiwi created appliance the kiwi initrd is active and calls at the end mkinitrd within an environment which provides all the required data to operate correctly. At that point the mkinitrd call makes sense and is even mandatory to replace the kiwi first boot code by the result of mkinitrd In short, you cannot expect a valid bootloader/splash configuration to be present in the kiwi unpacked root tree. The root tree kiwi creates is the result of the installation of packages and not more. It doesn't contain any system configuration other than those added by the author of the appliance. just my 2cents -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=798295 https://bugzilla.novell.com/show_bug.cgi?id=798295#c3 --- Comment #3 from Marcus Schaefer <ms@suse.com> 2013-01-14 15:18:43 UTC --- sorry I can't do anything with that question maybe you explain separately (not on bugzilla) what you are doing right now mkinitrd is a tool which assumes it runs on the target system it never was designed to run inside a chroot environment which is _not_ the target system. Building images is exactly that, creating an OS on a build machine and deploy it to other/different machines Thus using the result of mkinitrd while in the chroot on the build machine is a bad idea. If we accept that mkinitrd acts like this then there is no bug because it's allowed to check proc/cmdline and other parameters if we say all that must happen on the target machine If this is not accepted I fear a pretty big rewrite of mkinitrd is the consequence and that is also not a bug but a feature :) So my suggestion is to close this one -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=798295 https://bugzilla.novell.com/show_bug.cgi?id=798295#c5 --- Comment #5 from Jan Engelhardt <jengelh@inai.de> 2013-01-14 19:55:47 CET --- But I need to call mkinitrd -s somehow in the first place, inside the tree that will be used for the cpio (oem-iso-install/boot-VMX.hTx4zW/kiwi-VMXboot-26596/). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=798295 https://bugzilla.novell.com/show_bug.cgi?id=798295#c7 --- Comment #7 from Jan Engelhardt <jengelh@inai.de> 2013-07-12 17:44:39 CEST --- What I want is a bootsplash for the installer ISO image that KIWI generates, not the final final system that the kiwi-produced ISO installs. So, to get bootsplash in the installer, I need to run a custom command (mkinitrd -s) in a kiwi hook script that late – or by means of your suggestion:

an option so that mkinitrd is called a second time with custom options.

-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.