The image creation currently silently fails on Fedora 33 because the
kernel scriptlet is unable to create the initramfs:
cp: error writing '/var/tmp/dracut.SqTiPj/initramfs/lib/libbrotlicommon.so.1.0.7': No space left on device
dracut-install: ERROR: failed to install '/lib/libbrotlicommon.so.1' for '/var/tmp/dracut.SqTiPj/initramfs/usr/sbin/rngd'
...
I'm not entirely sure how much space is actually needed. Hopefully not
more than 100M though.
This is a generic disk image that should be usable on any architecture with
imagefactory or live-media-creator (possibly with package tweaks). It creates a
minimal-common.ks to share as much as possible with the ARMv7 specific
fedora-arm-minimal.ks
Signed-off-by: Peter Robinson <pbrobinson@fedoraproject.org>
With e2fsprogs after 1.43 the 64bit and metadata_csum features are
enabled by default. These features are not currently supported in
u-boot and the 64bit feature introduces changes such that it cannot
be read by implementations that do not support it. U-Boot does not
support the functionality and hence now won't mount it just in case
it corrupts the filesystem, which is a reasonable response, this how
ever stops us from booting when we have a ext4 /boot file system
which means basically we end up with a pot plant. Go back to using
ext3 for the time being as the mkfs.ext3 option doesn't enable these
features and we get booting systems!! YAY \o/
initail-setup.service now handles running both the gui mode and text
mode running of initial-setup so just enable the one service and no
longer do any special handling rhbz#1296495
Signed-off-by: Dennis Gilmore <dennis@ausil.us>
remove vfat kickstarts, we are going to use u-boot in raw space
without needing two sets of images with different partitioning we
can remove the seperate partitioning snippets and put the
partitioning in base.
Peter Robinson
Paul Whalen
Lubomir Rintel
Paul Whalen
Kevin Fenzi
Dennis Gilmore
Peter Robinson
Peter Robinson