Products › LamBoot › Roadmap

Roadmap

Shipping today at v0.15.2, then installer integration, filesystem coverage, and trust-baseline expansion

SHIPPING TODAY

v0.15.2

Published under Lamco Development LLC, GPG signed.

  • ✓Native ext4, btrfs, and FAT reading, including on LVM, with read-in-place /boot.
  • ✓Native PE loader. LamBoot verifies and loads the kernel itself.
  • ✓Trust-evidence log on every boot.
  • ✓Graphical menu with mouse, and a serial fallback.
  • ✓NVRAM crash-loop recovery.
  • ✓BLS plus UKI plus kernel-install plus distro hooks.
  • ✓Secure Boot via shim plus MOK and firmware db.
  • ✓Measured boot on PCR 4, 5, and 12.
  • ✓x86_64 and aarch64.
TIER 1 · IMMEDIATE

Installer integration

The strategic priority, because adoption gates capability: until distributions install LamBoot at OS-install time, it stays a retrofit.

  • •The lamboot-installer-protocol v1, already shipping in lamboot-install.
  • •An AUR lamboot package.
  • •An archinstall plugin.
  • •A Calamares upstream module.
  • •An openSUSE script-contract path.
TIER 2 · v1.0

Filesystem coverage, Proxmox depth, and health

  • •A native XFS read backend (xfs-view) to unblock the RHEL family.
  • •The Proxmox host-side sequence in depth.
  • •Health monitoring with expanded metrics and real NVMe SMART reporting.
TIER 3 · v1.1 AND LATER

Trust-baseline expansion

  • •The Microsoft shim-review submission (Path D), which removes the per-system MOK enrollment step.
  • •A WASMi diagnostic runtime as a separate lamboot-wasm.efi module, never in the core.
  • •TPM2_Quote remote attestation.
  • •ZFS read support, gated on a community contribution path (rzfs).
  • •Native f2fs and bcachefs.
SCOPE

Deliberately not building

Stating scope plainly is part of the roadmap.

  • →No legacy BIOS. UEFI only.
  • →No interactive rescue shell. The menu picks an entry, and diagnostic modules are chainloaded EFI applications.
  • →No GRUB-style config language.