The package called 'anaconda' is empty and only depends on two
things, anaconda-gui and anaconda-tui. Since anaconda 43.32,
anaconda runs the GTK UI if it's installed; it will only run the
web UI if anaconda-gui is not installed. So by including anaconda
we are forcing lives to run GTK UI and not really gaining
anything - we don't want anaconda-tui on lives anyway, I don't
think.
The anaconda-live package will pull in anaconda-webui, so all we
need to do is stop including anaconda. This will cause all live
images to use web UI, which was the intent of
https://github.com/rhinstaller/anaconda/pull/6530 . I guess if
any lives really want/need to use GTK UI, they can put
anaconda-gui into their profiles.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Per erofs upstream, this results in faster and more efficient build times
with improved runtime performance.
Signed-off-by: Neal Gompa <ngompa@fedoraproject.org>
This drastically reduces the content included in the embedded ESP
for live media, and avoids weird side-effects caused by extra EFI
binaries being present.
It seems the larger chunk size seems to slow the start of images in
low memory environments due to the ldconfig cache generator unit
eating gigabytes of memory from mapping the chunks into memory.
Attempt to work around this by lowering the chunk size while raising
the compression level to attempt to maintain image sizes.
This switches from SquashFS to EROFS using LZMA compression
with a 1M chunksize and fragement dedpulication for inodes enabled.
This attempts to match the defaults for SquashFS in kiwi and provides
a good balance for image compression and creation time.
Note that "-Ededupe" is not used because it is not multi-threaded and
is currently extremely slow.
Most of the changes are self-explanatory and just follow what's
already happening for existing architectures.
Two things are worth pointing out:
* we need to use shim-unsigned instead of shim-signed because
riscv64 is not fully integrated into Fedora yet and so we
can't do Secure Boot signing for the time being;
* we use ext4 as bootfilesystem since in most cases the
underlying firmware is going to be U-Boot, which needs to be
able to load the board's DTB from /boot and doesn't support
XFS.
Signed-off-by: David Abdurachmanov <davidlt@rivosinc.com>
As it currently stands, this doubles the size of the live ISOs,
which is completely unacceptable.
We will need to make the switch eventually, but we need to figure
out how to compress better first.
This reverts commit 1457e97008.
EROFS is newer, more performant filesystem that emphasizes speed
and integrity over SquashFS. It is also much better maintained and
friendlier for flash-based storage that live media is typically
run from these days.
We discovered Neal got the regex for this wrong in the Kiwi
schema upstream. While he fixes that up, let's just ditch the
spaces here for now so it passes validation.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
We want to be able to produce live ISOs for AArch64 and POWER with
the correct GRUB configuration. This also sets us up to handle any
quirks for each architecture platform as needed later.
This also includes a change to bump the EFI partition size for ISOs
to 30MB so everything fits.
Adam Williamson