almalinux/lorax
13
0
Fork 0
Code Issues Pull Requests Releases Activity
22de8ed603
lorax/share/s390.tmpl

74 lines
2.5 KiB
Cheetah
Raw Normal View History

Add path to squashfs image to the treeinfo Related: rhbz#782108
2012-02-07 09:55:03 +00:00
<%page args="kernels, runtime_img, runtime_base, basearch, outroot"/>
treebuilder.py: uses templates to create trees/images TreeBuilder uses templates full of commands (like ramdisk.ltmpl) to create the output tree and boot images. There are 4 arch-specific templates, plus a bonus EFI template which can handle EFI image creation for any arch that implements EFI.
2011-05-09 14:47:25 +00:00
<%
clean up config_files dir (and fix templates to match) move arch-specific stuff to arch-specific subdirs and move all the common stuff to a subdir named 'common'. Also, rename '.profile' and '.bash_history' so you actually see them when you 'ls' the 'common' dir. also added some helpful(?) comments to the templates.
2011-10-21 20:12:12 +00:00
configdir="tmp/config_files/s390"
treebuilder.py: uses templates to create trees/images TreeBuilder uses templates full of commands (like ramdisk.ltmpl) to create the output tree and boot images. There are 4 arch-specific templates, plus a bonus EFI template which can handle EFI image creation for any arch that implements EFI.
2011-05-09 14:47:25 +00:00
BOOTDIR="images"
KERNELDIR=BOOTDIR
INITRD_ADDRESS="0x02000000"
Add product.img support for s390 templates (#1272359) (cherry picked from commit a2c2a4be280794dcb1355f867466c01fd8f3de89) Resolves: rhbz#1272359
2015-04-29 14:35:41 +00:00
LORAXDIR="usr/share/lorax/"
treebuilder.py: uses templates to create trees/images TreeBuilder uses templates full of commands (like ramdisk.ltmpl) to create the output tree and boot images. There are 4 arch-specific templates, plus a bonus EFI template which can handle EFI image creation for any arch that implements EFI.
2011-05-09 14:47:25 +00:00
# The assumption seems to be that there is only one s390 kernel, ever
kernel = kernels[0]
%>
arch templates: install runtime to /images/, put it on boot.iso make sure the arch templates (s390 excluded) copy the runtime image in to the /images/ dir, and make sure it gets grafted/copied into the boot.iso.
2011-06-23 00:22:24 +00:00
mkdir images
rename "runtime" template arg to "runtime_img" Mako uses "runtime" internally for things, and if you clobber it stuff will just break in weird ways. So don't do that.
2011-06-23 14:46:28 +00:00
install ${runtime_img} images
Change the squashfs image section in .treeinfo Related: rhbz#782108
2012-02-09 15:59:15 +00:00
treeinfo stage2 mainimage images/${runtime_base}
arch templates: install runtime to /images/, put it on boot.iso make sure the arch templates (s390 excluded) copy the runtime image in to the /images/ dir, and make sure it gets grafted/copied into the boot.iso.
2011-06-23 00:22:24 +00:00
clean up config_files dir (and fix templates to match) move arch-specific stuff to arch-specific subdirs and move all the common stuff to a subdir named 'common'. Also, rename '.profile' and '.bash_history' so you actually see them when you 'ls' the 'common' dir. also added some helpful(?) comments to the templates.
2011-10-21 20:12:12 +00:00
## install bootloader (such as it is) and bootloader config
rename ANABOOTDIR to configdir
2011-08-09 00:35:35 +00:00
install ${configdir}/redhat.exec ${BOOTDIR}
install ${configdir}/generic.prm ${BOOTDIR}
allow setting additional dracut parameters for DVD s390x installs (#1132050) The installation from DVD on s390x needs setting the target disks and network information that are usually set by editing the generic.prm file. By including the "rd.cmdline=ask" parameter dracut will open a simple dialog so the user can enter the required information. Resolves: rhbz#1132050 (cherry picked from commit e92ea262060160d5640dbb8fb8d3fbe5b1ddfb4a)
2014-08-21 07:53:14 +00:00
install ${configdir}/genericdvd.prm ${BOOTDIR}
Add creation of a bootable s390 iso (#1478448) Use mk-s390-cdboot to create a combined kernel+initrd and then build a boot.iso using it. Resolves: rhbz#1478448
2017-08-09 18:44:54 +00:00
install ${configdir}/cdboot.prm ${BOOTDIR}
rename ANABOOTDIR to configdir
2011-08-09 00:35:35 +00:00
install ${configdir}/generic.ins .
treebuilder.py: uses templates to create trees/images TreeBuilder uses templates full of commands (like ramdisk.ltmpl) to create the output tree and boot images. There are 4 arch-specific templates, plus a bonus EFI template which can handle EFI image creation for any arch that implements EFI.
2011-05-09 14:47:25 +00:00
clean up config_files dir (and fix templates to match) move arch-specific stuff to arch-specific subdirs and move all the common stuff to a subdir named 'common'. Also, rename '.profile' and '.bash_history' so you actually see them when you 'ls' the 'common' dir. also added some helpful(?) comments to the templates.
2011-10-21 20:12:12 +00:00
## configure bootloader
treebuilder.py: uses templates to create trees/images TreeBuilder uses templates full of commands (like ramdisk.ltmpl) to create the output tree and boot images. There are 4 arch-specific templates, plus a bonus EFI template which can handle EFI image creation for any arch that implements EFI.
2011-05-09 14:47:25 +00:00
replace @INITRD_LOAD_ADDRESS@ ${INITRD_ADDRESS} generic.ins
clean up config_files dir (and fix templates to match) move arch-specific stuff to arch-specific subdirs and move all the common stuff to a subdir named 'common'. Also, rename '.profile' and '.bash_history' so you actually see them when you 'ls' the 'common' dir. also added some helpful(?) comments to the templates.
2011-10-21 20:12:12 +00:00
## install kernel
treebuilder.py: uses templates to create trees/images TreeBuilder uses templates full of commands (like ramdisk.ltmpl) to create the output tree and boot images. There are 4 arch-specific templates, plus a bonus EFI template which can handle EFI image creation for any arch that implements EFI.
2011-05-09 14:47:25 +00:00
installkernel images-${basearch} ${kernel.path} ${KERNELDIR}/kernel.img
installinitrd images-${basearch} ${kernel.initrd.path} ${KERNELDIR}/initrd.img
clean up config_files dir (and fix templates to match) move arch-specific stuff to arch-specific subdirs and move all the common stuff to a subdir named 'common'. Also, rename '.profile' and '.bash_history' so you actually see them when you 'ls' the 'common' dir. also added some helpful(?) comments to the templates.
2011-10-21 20:12:12 +00:00
Missing semicolon
2012-12-19 07:53:08 +00:00
%if doupgrade:
Only run installupgradeinitrd if upgrade on s390x
2012-12-18 14:08:15 +00:00
## upgrader image
installupgradeinitrd images-${basearch} ${kernel.upgrade.path} ${KERNELDIR}/upgrade.img
%endif
make templates install upgrade.img
2012-11-13 06:33:17 +00:00
clean up config_files dir (and fix templates to match) move arch-specific stuff to arch-specific subdirs and move all the common stuff to a subdir named 'common'. Also, rename '.profile' and '.bash_history' so you actually see them when you 'ls' the 'common' dir. also added some helpful(?) comments to the templates.
2011-10-21 20:12:12 +00:00
## s390 needs some extra boot config
use internal implementation of the addrsize utility Anaconda dropped the addrsize utility in F-16, so we need to implement it directly in lorax.
2012-02-07 17:46:30 +00:00
createaddrsize ${INITRD_ADDRESS} ${outroot}/${BOOTDIR}/initrd.img ${outroot}/${BOOTDIR}/initrd.addrsize
clean up config_files dir (and fix templates to match) move arch-specific stuff to arch-specific subdirs and move all the common stuff to a subdir named 'common'. Also, rename '.profile' and '.bash_history' so you actually see them when you 'ls' the 'common' dir. also added some helpful(?) comments to the templates.
2011-10-21 20:12:12 +00:00
## s390 also has some special treeinfo data
use internal implementation of the addrsize utility Anaconda dropped the addrsize utility in F-16, so we need to implement it directly in lorax.
2012-02-07 17:46:30 +00:00
treeinfo images-${basearch} initrd.addrsize ${BOOTDIR}/initrd.addrsize
treebuilder.py: uses templates to create trees/images TreeBuilder uses templates full of commands (like ramdisk.ltmpl) to create the output tree and boot images. There are 4 arch-specific templates, plus a bonus EFI template which can handle EFI image creation for any arch that implements EFI.
2011-05-09 14:47:25 +00:00
treeinfo images-${basearch} generic.prm ${BOOTDIR}/generic.prm
allow setting additional dracut parameters for DVD s390x installs (#1132050) The installation from DVD on s390x needs setting the target disks and network information that are usually set by editing the generic.prm file. By including the "rd.cmdline=ask" parameter dracut will open a simple dialog so the user can enter the required information. Resolves: rhbz#1132050 (cherry picked from commit e92ea262060160d5640dbb8fb8d3fbe5b1ddfb4a)
2014-08-21 07:53:14 +00:00
treeinfo images-${basearch} genericdvd.prm ${BOOTDIR}/genericdvd.prm
treebuilder.py: uses templates to create trees/images TreeBuilder uses templates full of commands (like ramdisk.ltmpl) to create the output tree and boot images. There are 4 arch-specific templates, plus a bonus EFI template which can handle EFI image creation for any arch that implements EFI.
2011-05-09 14:47:25 +00:00
treeinfo images-${basearch} generic.ins generic.ins
Update the lorax templates to match what lorax provides lorax-creator doesn't ship these, but it uses them for running tests, so make sure they are current. Related: rhbz#1689314
2019-06-18 18:33:05 +00:00
treeinfo images-${basearch} redhat.exec ${BOOTDIR}/redhat.exec
Add product.img support for s390 templates (#1272359) (cherry picked from commit a2c2a4be280794dcb1355f867466c01fd8f3de89) Resolves: rhbz#1272359
2015-04-29 14:35:41 +00:00
s390 doesn't need to graft product.img and updates.img into /images (#1478448) The /images directory is already grafted into the iso, so it doesn't need a specific line for the .img files. Related: rhbz#1478448
2017-09-29 16:31:34 +00:00
# Create optional product.img and updates.img in /images/
Add product.img support for s390 templates (#1272359) (cherry picked from commit a2c2a4be280794dcb1355f867466c01fd8f3de89) Resolves: rhbz#1272359
2015-04-29 14:35:41 +00:00
<% imggraft=""; images=["product", "updates"] %>
%for img in images:
%if exists("%s/%s/" % (LORAXDIR, img)):
installimg ${LORAXDIR}/${img}/ images/${img}.img
%endif
%endfor
# Inherit iso-graft/ if it exists from external templates
<%
import os
if os.path.exists(workdir + "/iso-graft"):
imggraft += " " + workdir + "/iso-graft"
%>
Add creation of a bootable s390 iso (#1478448) Use mk-s390-cdboot to create a combined kernel+initrd and then build a boot.iso using it. Resolves: rhbz#1478448
2017-08-09 18:44:54 +00:00
## Make a combined kernel+initrd image for the iso
runcmd mk-s390-cdboot -i ${outroot}/${KERNELDIR}/kernel.img \
-r ${outroot}/${KERNELDIR}/initrd.img \
-p ${outroot}/${BOOTDIR}/cdboot.prm \
-o ${outroot}/${BOOTDIR}/cdboot.img
## make boot.iso
runcmd mkisofs -o ${outroot}/images/boot.iso \
-b ${BOOTDIR}/cdboot.img -c ${BOOTDIR}/boot.cat \
Remove -boot-info-table from s390 boot.iso creation (#1478448) It corrupts the kernel+initrd and isn't needed when booting on s390. Related: rhbz#1478448
2017-08-18 17:19:28 +00:00
-boot-load-size 4 -no-emul-boot \
Add creation of a bootable s390 iso (#1478448) Use mk-s390-cdboot to create a combined kernel+initrd and then build a boot.iso using it. Resolves: rhbz#1478448
2017-08-09 18:44:54 +00:00
-R -J -V '${isolabel}' -T -graft-points \
${BOOTDIR}=${outroot}/${BOOTDIR} \
${imggraft}
treeinfo images-${basearch} boot.iso images/boot.iso
Reference in New Issue Copy Permalink