https://bugzilla.novell.com/show_bug.cgi?id=798295
https://bugzilla.novell.com/show_bug.cgi?id=798295#c1
--- Comment #1 from Marcus Schaefer 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.
