The v1.5.1 bugfix release of gentoo-on-rpi-64bit
- a full 64-bit (kernel + userland) OS for the RPi4B (and RPi3B/B+) - is now also available for download via PINN
(called gentoo64 there).
Also, as of this v1.5.1, the Pi-Top v1 specific image (gentoo64pt) has unfortunately had to be withdrawn (as, due to a hardware failure of my own Pi-Top chassis' hub, I can no longer test it).
On a happier note, a new, 'lite' Gentoo image (gentoo64lite), which boots to a CLI, has been added (find it under the 'Minimal' tab in PINN).
You can read more about the v1.5.1 release here
Given a compressed, full-disk image of an OS (such as one might use with Etcher), the creation of appropriate per-filesystem tarballs, and matching JSON metadata, sufficient to allow PINN
to install it, is a slightly tricky process.
For a while now, I've been using a simple, templated script called pinnify
to automate this. The basic workflow for using it is as follows:
- create a baseline template for your OS (once only, if it does not already exist);
- edit that template (ditto); then
- have pinnify automatically create a release from the template and a compressed release OS image.
Subsequent releases of the same OS generally only require you repeat the last step, significantly saving time (and reducing the potential for deployment errors).
pinnify allows you to use Bash variables and arithmetic
in your JSON metadata templates, and creates (and checksums) the PINN-compatible partition tarballs for you automatically.
Although likely to be of interest only to a vanishingly small percentage of the population ^-^ (those who would like to host their own PINN images, mostly), I have just released the pinnify script on GitHub, here
Its project page
contains a full worked example of creating and using an OS template, with embedded metadata variables etc.
Still very early days for this, and a bit rough round the edges, so feedback most welcome.