bbaassssiiee/fedora-kickstarts
1
0
Fork 0
forked from srbala/fedora-kickstarts
Code Issues Pull Requests Releases Activity

Use reqpart in Fedora Atomic kickstart

Browse Source 
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 <sinny@redhat.com>
This commit is contained in:
Sinny Kumari 2017-09-14 16:30:09 +05:30
parent ca4d6f43e1
commit 7d2e4519d8
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
fedora-atomic.ks
View File

@ -31,10 +31,9 @@ clearpart --all
# Vagrant boxes come big and rely on thin provisioning). # Vagrant boxes come big and rely on thin provisioning).
# In both cases, it's simplest to just fill all the disk space. # 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 # Use reqpart to create hardware platform specific partitions
# waste of space with the 6GB layout. At some point we could investigate dropping the /boot partition, see # https://pagure.io/atomic-wg/issue/299
# https://github.com/ostreedev/ostree/pull/215 and https://github.com/ostreedev/ostree/pull/268 reqpart --add-boot
part /boot --size=300 --fstype="ext4"
part pv.01 --grow part pv.01 --grow
volgroup atomicos pv.01 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. # Start from 3GB as we did before, since we just need a size. But we do --grow to fill all space.