This commit distinguishes the files that should be installed inside
the image dracut only than the ones installed in both, in install initrd
and image initrd.
Fixes#858
The image description now allows an optional file named:
config-cdroot.tar[.compression_postfix]. The file gets
unpacked as user data for live and install ISO images.
This allows users to add e.g license files or reference
documentation to the ISO image. This Fixes#737
The extra isohybrid call is only needed if the mkisofs
tool category is used. Thus it should be only visible
at the place where the isofs is created and not as an
extra step in the builder tasks. Additionally the handling
of extra options was mkisofs specific and should be
better done as a common meta_data record. The tool
specific options should only appear in the tool specific
class implementations
The variable is set to a boolean value or None. If set to
False due to a configuration of oem-multipath-scan this
will cause the dracut multipath module to be omitted.
In any other case the presence of the multipath module
decides whether it will be included into the dracut
generated initrd or not.
As the kiwi build dracut initrd is a generic one which
includes all installed dracut modules we missed a way to
exclude modules from beeing incorporated even if we know
it would not be needed. One example is the multipath module
which would only be useful if the oem multipath scan is
configured in the image description
Once the image has been deployed on the target and the
system is up and running some of the kiwi dracut modules
used for deployment are no longer needed and should not be
taken into account when another dracut call happens on the
system.
Use get_boot_names from BootImage instance to ask for
the name of the initrd instead of constructing this
information from static values. The name of the initrd
is different per distro and toolkit
Provide the capabilities of the oem install code as
dracut module. The implementation covers the result
of the installiso="true" configuration. Installation
from remote sources still needs to be done and will
follow in an extra pull request. This addresses
Issue #576
isohybrid errors printed on stderr were not treated as fatal
but should be treated as such. In addition isohybrid should
distinguish for efi setup according to the efi setup of the
image itself
In order to put grub data to boot/grub2 or boot/grub a check for
the grub2-tool vs. grub-tool name is performed. This requires
access to the image root directory on a file basis which is not always
applicable. When setting up the grub bootloader for e.g EFI boot on
an iso image the rootfs can't be directly accessed because the iso
image contains the rootfs in a compressed format. This commit
refactors the check to be generic for all image types
nose is no longer maintained, thus we have to move to another
testing system. This commit updates the tox setup and all tests
to use pytest instead of nose.
