almalinux/lorax
13
0
Fork 0
Code Issues Pull Requests Releases Activity
b7f651a631
lorax/share/x86.tmpl

113 lines
4.0 KiB
Cheetah
Raw Normal View History

Use a predictable ISO Volume Label (#732298) New images find their root device by looking at the CDLABEL. Since pungi is building ISO images separately from lorax, if it uses a different ISO Volume Label we'll end up with unbootable images. This changes the volume labels to match what pungi uses, so both should boot OK.
2011-10-13 00:08:31 +00:00
<%page args="kernels, runtime_img, basearch, outroot, product, isolabel"/>
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/x86"
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
SYSLINUXDIR="usr/share/syslinux"
PXEBOOTDIR="images/pxeboot"
BOOTDIR="isolinux"
KERNELDIR=PXEBOOTDIR
Move images/install.img to LiveOS/squashfs.img (#732298) Since pungi doesn't know that images/install.img needs to be moved to LiveOS/squashfs.img for images to be "live", they aren't bootable. This is the simple solution to the problem. Thanks to Karsten Hopp for the original patch.
2011-10-11 18:58:30 +00:00
LIVEDIR="LiveOS"
Update templates to use installimg for product and updates With these templates if a package has installed files in /usr/share/lorax/product or /usr/share/lorax/updates/ they will be used to create product.img and/or updates.img which will be included in the images/ directory of the iso and of the final output tree. These can be used to customize the installation environment or provide updates. See README.product for current documentation. Related: rhbz#1202278
2014-11-05 03:07:57 +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
%>
Move images/install.img to LiveOS/squashfs.img (#732298) Since pungi doesn't know that images/install.img needs to be moved to LiveOS/squashfs.img for images to be "live", they aren't bootable. This is the simple solution to the problem. Thanks to Karsten Hopp for the original patch.
2011-10-11 18:58:30 +00:00
mkdir ${LIVEDIR}
install ${runtime_img} ${LIVEDIR}/squashfs.img
Change the squashfs image section in .treeinfo Related: rhbz#782108
2012-02-09 15:59:15 +00:00
treeinfo stage2 mainimage ${LIVEDIR}/squashfs.img
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 and config files
mkdir ${BOOTDIR}
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
install ${SYSLINUXDIR}/isolinux.bin ${BOOTDIR}
install ${SYSLINUXDIR}/vesamenu.c32 ${BOOTDIR}
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 ${configdir}/isolinux.cfg ${BOOTDIR}
install ${configdir}/boot.msg ${BOOTDIR}
rename ANABOOTDIR to configdir
2011-08-09 00:35:35 +00:00
install ${configdir}/grub.conf ${BOOTDIR}
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 usr/share/anaconda/boot/syslinux-splash.png ${BOOTDIR}/splash.png
add memtest to the boot.iso for x86 (#787234)
2012-02-10 21:29:30 +00:00
install boot/memtest* ${BOOTDIR}/memtest
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
x86.tmpl/efi.tmpl fixups fix initrd hardlink splash.xml.gz should be splash.xpm.gz fix mkisofs args actually replace vars in isolinux.cfg
2011-05-10 22:21:18 +00:00
replace @VERSION@ ${product.version} ${BOOTDIR}/grub.conf ${BOOTDIR}/isolinux.cfg ${BOOTDIR}/*.msg
Fix product name replacing in templates (#799919) The product name may contain spaces, so it needs to be in quotes, otherwise the other words get stripped.
2012-03-07 10:27:11 +00:00
replace @PRODUCT@ '${product.name}' ${BOOTDIR}/grub.conf ${BOOTDIR}/isolinux.cfg ${BOOTDIR}/*.msg
use inst.stage2=hd:LABEL (#848641) The iso is able to autodetect the device and find stage2, but when they are written to USB via dd it needs to know where to find the install media.
2012-08-22 23:59:03 +00:00
replace @ROOT@ 'inst.stage2=hd:LABEL=${isolabel|udev}' ${BOOTDIR}/isolinux.cfg
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
## install kernels
mkdir ${KERNELDIR}
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
%for kernel in kernels:
%if kernel.flavor:
make templates install upgrade.img
2012-11-13 06:33:17 +00:00
## i386 PAE
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-xen ${kernel.path} ${KERNELDIR}/vmlinuz-${kernel.flavor}
installinitrd images-xen ${kernel.initrd.path} ${KERNELDIR}/initrd-${kernel.flavor}.img
Only run installupgradeinitrd if upgrade
2012-12-18 13:31:45 +00:00
%if doupgrade:
installupgradeinitrd images-xen ${kernel.upgrade.path} ${KERNELDIR}/upgrade-${kernel.flavor}.img
%endif
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
%else:
make templates install upgrade.img
2012-11-13 06:33:17 +00:00
## normal i386, x86_64
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}/vmlinuz
installinitrd images-${basearch} ${kernel.initrd.path} ${KERNELDIR}/initrd.img
Only run installupgradeinitrd if upgrade
2012-12-18 13:31:45 +00:00
%if doupgrade:
installupgradeinitrd images-${basearch} ${kernel.upgrade.path} ${KERNELDIR}/upgrade.img
%endif
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
%endif
%endfor
hardlink ${KERNELDIR}/vmlinuz ${BOOTDIR}
x86.tmpl/efi.tmpl fixups fix initrd hardlink splash.xml.gz should be splash.xpm.gz fix mkisofs args actually replace vars in isolinux.cfg
2011-05-10 22:21:18 +00:00
hardlink ${KERNELDIR}/initrd.img ${BOOTDIR}
Several 'doupgrade' fixes in the x86 template.
2012-12-19 09:04:06 +00:00
%if doupgrade:
hardlink ${KERNELDIR}/upgrade.img ${BOOTDIR}
%endif
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
%if basearch == 'x86_64':
treeinfo images-xen kernel ${KERNELDIR}/vmlinuz
treeinfo images-xen initrd ${KERNELDIR}/initrd.img
Several 'doupgrade' fixes in the x86 template.
2012-12-19 09:04:06 +00:00
%if doupgrade:
treeinfo images-xen upgrade ${KERNELDIR}/upgrade.img
%endif
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
%endif
## WHeeeeeeee, EFI.
Make 64-bit kernel on 32-bit firmware work for x86 efi machines This enables Baytrail and similar atom CPUs that typically ship with a 32-bit firmware, but have a 64-bit capable CPU. Resolves: rhbz#1310775 Signed-off-by: Peter Jones <pjones@redhat.com>
2015-04-13 17:30:24 +00:00
<% efiargs=""; efigraft=""; efihybrid=""; efiarch32=None; efiarch64=None %>
%if exists("boot/efi/EFI/*/gcdia32.efi"):
<% efiarch32 = 'IA32' %>
%endif
%if exists("boot/efi/EFI/*/gcdx64.efi"):
<% efiarch64 = 'X64' %>
%endif
%if efiarch32 or efiarch64:
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
<%
x86.tmpl: add eltorito alt boot entry for macboot.img This should allow us to boot the created image on Apple EFI systems.
2011-10-31 18:59:35 +00:00
efigraft="EFI/BOOT={0}/EFI/BOOT".format(outroot)
Add --nomacboot option Needed for systems without hfsplus support.
2012-05-17 15:27:28 +00:00
images = ["images/efiboot.img"]
if domacboot:
images.append("images/macboot.img")
for img in images:
x86.tmpl: add eltorito alt boot entry for macboot.img This should allow us to boot the created image on Apple EFI systems.
2011-10-31 18:59:35 +00:00
efiargs += " -eltorito-alt-boot -e {0} -no-emul-boot".format(img)
efigraft += " {0}={1}/{0}".format(img,outroot)
Use --mac for isohybrid only if doing macboot images
2012-05-18 10:48:43 +00:00
efihybrid = "--uefi --mac" if domacboot else "--uefi"
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
%>
Make 64-bit kernel on 32-bit firmware work for x86 efi machines This enables Baytrail and similar atom CPUs that typically ship with a 32-bit firmware, but have a 64-bit capable CPU. Resolves: rhbz#1310775 Signed-off-by: Peter Jones <pjones@redhat.com>
2015-04-13 17:30:24 +00:00
<%include file="efi.tmpl" args="configdir=configdir, KERNELDIR=KERNELDIR, efiarch32=efiarch32, efiarch64=efiarch64, isolabel=isolabel"/>
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
%endif
Update templates to use installimg for product and updates With these templates if a package has installed files in /usr/share/lorax/product or /usr/share/lorax/updates/ they will be used to create product.img and/or updates.img which will be included in the images/ directory of the iso and of the final output tree. These can be used to customize the installation environment or provide updates. See README.product for current documentation. Related: rhbz#1202278
2014-11-05 03:07:57 +00:00
# Create optional product.img and updates.img
<% imggraft=""; images=["product", "updates"] %>
%for img in images:
%if exists("%s/%s/" % (LORAXDIR, img)):
installimg ${LORAXDIR}/${img}/ images/${img}.img
<% imggraft += " images/{0}.img={1}/images/{0}.img".format(img, outroot) %>
%endif
%endfor
Add ability for external templates to graft content into boot.iso (#1202278) I originally added --add-template to support doing something similar to pungi, which injects content into the system to be used by default. However, this causes the content to be part of the squashfs, which means PXE installations have to download significantly more data that they may not need (if they actually want to pull the tree data from the network, which is not an unusual case). What I actually need is to be able to modify *both* the runtime image and the arch-specific content. For the runtime, I need to change /usr/share/anaconda/interactive-defaults.ks to point to the new content. (Although, potentially we could patch Anaconda itself to auto-detect an ostree repository configured in disk image, similar to what it does for yum repositories) For the arch-specfic image, I want to drop my content into the ISO root. So this patch adds --add-arch-template and --add-arch-template-var in order to do the latter, while preserving the --add-template to affect the runtime image. Further, the templates will automatically graft in a directory named "iso-graft/" from the working directory (if it exists). (I suggest that external templates create a subdirectory named "content" to avoid clashes with any future lorax work) Thus, this will be used by the Atomic Host lorax templates to inject content/repo, but could be used by e.g. pungi to add content/rpms as well. I tried to avoid code deduplication by creating a new template for the product.img bits and this, but that broke because the parent boot.iso code needs access to the `${imggraft}` variable. I think a real fix here would involve turning the product.img, content/, *and* boot.iso into a new template. Resolves: rhbz#1202278
2015-03-17 21:26:21 +00:00
# Inherit iso-graft/ if it exists from external templates
<%
import os
if os.path.exists(workdir + "/iso-graft"):
imggraft += " " + workdir + "/iso-graft"
%>
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
## make boot.iso
x86.tmpl/efi.tmpl fixups fix initrd hardlink splash.xml.gz should be splash.xpm.gz fix mkisofs args actually replace vars in isolinux.cfg
2011-05-10 22:21:18 +00:00
runcmd mkisofs -o ${outroot}/images/boot.iso \
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
-b ${BOOTDIR}/isolinux.bin -c ${BOOTDIR}/boot.cat \
x86.tmpl/efi.tmpl fixups fix initrd hardlink splash.xml.gz should be splash.xpm.gz fix mkisofs args actually replace vars in isolinux.cfg
2011-05-10 22:21:18 +00:00
-boot-load-size 4 -boot-info-table -no-emul-boot \
Use a predictable ISO Volume Label (#732298) New images find their root device by looking at the CDLABEL. Since pungi is building ISO images separately from lorax, if it uses a different ISO Volume Label we'll end up with unbootable images. This changes the volume labels to match what pungi uses, so both should boot OK.
2011-10-13 00:08:31 +00:00
${efiargs} -R -J -V '${isolabel}' -T -graft-points \
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}=${outroot}/${BOOTDIR} \
drop efidisk.img from boot.iso on x86
2011-05-12 17:34:02 +00:00
${KERNELDIR}=${outroot}/${KERNELDIR} \
Move images/install.img to LiveOS/squashfs.img (#732298) Since pungi doesn't know that images/install.img needs to be moved to LiveOS/squashfs.img for images to be "live", they aren't bootable. This is the simple solution to the problem. Thanks to Karsten Hopp for the original patch.
2011-10-11 18:58:30 +00:00
${LIVEDIR}=${outroot}/${LIVEDIR} \
Update templates to use installimg for product and updates With these templates if a package has installed files in /usr/share/lorax/product or /usr/share/lorax/updates/ they will be used to create product.img and/or updates.img which will be included in the images/ directory of the iso and of the final output tree. These can be used to customize the installation environment or provide updates. See README.product for current documentation. Related: rhbz#1202278
2014-11-05 03:07:57 +00:00
${efigraft} ${imggraft}
Build EFI hybrid (usb-bootable) images From: Matthew Garrett <mjg@redhat.com> If we're producing EFI bootable images then we should also support making them bootable from USB sticks. This adds support for doing so.
2011-08-29 20:29:43 +00:00
runcmd isohybrid ${efihybrid} ${outroot}/images/boot.iso
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} boot.iso images/boot.iso
Reference in New Issue Copy Permalink