{% extends "base.html" %}
{% import '_ui.html' as ui %}
{% block title %}Blancco releases - PXE Manager{% endblock %}
{% macro mb(n) -%}{{ "%.1f"|format((n or 0) / 1048576) }} MB{%- endmacro %}
{% macro prefs(r) -%}{{ r.prefs_version or '-' }}{% if r.vendor_prefs_version and r.vendor_prefs_version != r.prefs_version %} (vendor {{ r.vendor_prefs_version }}){% endif %}{%- endmacro %}
{% block extra_head %}
{% endblock %}
{% block content %}
Blancco releases
{{ job.log | join('\n') }}
Installs a new Blancco Drive Eraser release from the vendor ISO (or the vendor's USB image, .img or .img.gz). Staging extracts the release next to the live one, applies the same changes as scripts/prepare-boot-tools.sh (our preferences written into config.img, the initramfs network patch), and a test entry in the PXE boot menu boots the staged copy. Only Activate changes what the normal Blancco entry boots, and the files it replaces are kept as a backup you can roll back to.
Replaced in {{ current.path }}: arch/x86_64/airootfs.sfs, vmlinuz-bde-linux, initramfs-bde-linux.img (copytoram network patch), intel-ucode.img, amd-ucode.img, config.img (vendor cpio with our preferences written in at the same size), preferences.xml, config-clean.xml (the licence container from config.img) and, when the ISO has one, blancco-shim.efi. Never touched: vmlinuz-ubuntu*, kexec-initrd*, kmod*.tar.gz, grubx64.efi, shimx64.efi, blancco-progress.py.
Our preferences come from the live preferences.xml (the playbook deploys playbook/blancco-preferences.xml there). They are a merge onto one vendor release's file, so when a release's <version> differs, staging stops until a merged file is uploaded. After activating such a release, commit the merged file to the repo, or the next playbook run puts the old one back.
A playbook run also copies boot-tools/blancco/* from the USB over the live files. After activating a release here, refresh that copy (scripts/prepare-boot-tools.sh with the new ISO), or a playbook run puts the old release back.