Go to file

Pratham Patel 2d2ee0a676 start the first partition with a 32MiB "offset" Since Kickstart no longer has the '--start' and '--end' options for the partition command, we need to do this manually. `3e655d4c5d` Why do we need to do this at all? Well, because some SoCs read U-Boot from the boot media at a particular offset. Normally, the first partition starts at 2048 (with fdisk) or at 8192 (if using Kickstart) which means that something from the first partition will be erased, or data written here will eventually overwrite U-Boot if U-Boot is greater than 2MiB. Looking at the biggest file in 'uboot-images-armv8' package, the biggest file is ~12 MiB so the double of closest 2's exponent results in 32MiB.		2023-10-16 09:21:42 +05:30
includes	revert from two images to only a single image (GPT)	2023-10-16 08:08:05 +05:30
scripts	expand-rootfs.sh: revert from xfs to ext4	2023-10-04 13:04:52 +05:30
create-image.sh	start the first partition with a 32MiB "offset"	2023-10-16 09:21:42 +05:30
LICENSE	init commit	2023-09-13 06:59:56 +05:30
README.md	init commit	2023-09-13 06:59:56 +05:30
Rocky.ks	revert from two images to only a single image (GPT)	2023-10-16 08:08:05 +05:30

README

Expanding the rootfs

sudo /usr/local/bin/expand-rootfs.sh
sudo systemctl reboot

You need the packages appliance-tools perl-Digest-SHA pykickstart zstd (some packages are from the EPEL repository).
You can only build aarch64 images if your host is aarch64. I have not hardcoded a particular $basearch in the repositories