You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An aarch64-linux SBC target machine (with USB/NVME, some sort of removable media that can be direct attached to the development machine)
A pre-built system NixOS topleve closure for the SBC target.
Today, installing NixOS directly onto media for the SBC is rather annoying.
These parts are "easy":
configure target media (assume removable media that can be mounted to dev machine) - aka, disk/partition setup
copy initial system closure
However, actually making it bootable is a pain. I have done some tricks in the past to get extlinux-compatible bootloader to dump a single generation configuration into a directory, which I can then manually install to the target /boot. Which, in the case of a u-boot system, is "'good enough".
Would it be possible to utilize lanzaboote to handle this cross-arch installation scenario?
I considered nixos-anywhere here, but there are a number of SBC boards, for example, where kexec does not work.
The text was updated successfully, but these errors were encountered:
Say that I have:
x86_64-linux
development machineaarch64-linux
SBC target machine (with USB/NVME, some sort of removable media that can be direct attached to the development machine)Today, installing NixOS directly onto media for the SBC is rather annoying.
These parts are "easy":
However, actually making it bootable is a pain. I have done some tricks in the past to get
extlinux-compatible
bootloader to dump a single generation configuration into a directory, which I can then manually install to the target/boot
. Which, in the case of a u-boot system, is "'good enough".Would it be possible to utilize
lanzaboote
to handle this cross-arch installation scenario?I considered
nixos-anywhere
here, but there are a number of SBC boards, for example, wherekexec
does not work.The text was updated successfully, but these errors were encountered: