From 7d2e4519d87e07f4048bb5c4171d82f5d6260ec0 Mon Sep 17 00:00:00 2001 From: Sinny Kumari Date: Thu, 14 Sep 2017 16:30:09 +0530 Subject: [PATCH] Use reqpart in Fedora Atomic kickstart Building Fedora Atomic CloudImage on architectures like aarch64 and ppc64le needs platform specific partitions as well. Issue - https://pagure.io/atomic-wg/issue/299#comment-449243 Signed-off-by: Sinny Kumari --- fedora-atomic.ks | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/fedora-atomic.ks b/fedora-atomic.ks index 1bd2984..4566fa7 100644 --- a/fedora-atomic.ks +++ b/fedora-atomic.ks @@ -31,10 +31,9 @@ clearpart --all # Vagrant boxes come big and rely on thin provisioning). # In both cases, it's simplest to just fill all the disk space. # -# For /boot, we currently diverge from the Fedora default of 1GB here since it really feels like a huge -# waste of space with the 6GB layout. At some point we could investigate dropping the /boot partition, see -# https://github.com/ostreedev/ostree/pull/215 and https://github.com/ostreedev/ostree/pull/268 -part /boot --size=300 --fstype="ext4" +# Use reqpart to create hardware platform specific partitions +# https://pagure.io/atomic-wg/issue/299 +reqpart --add-boot part pv.01 --grow volgroup atomicos pv.01 # Start from 3GB as we did before, since we just need a size. But we do --grow to fill all space.