Go to file

Cyril Brulebois 773c67d6ba Add script to build images and a list of files to publish. Given a RASPBERRYPI_IMG_URL, this automates downloading the image and its checksum, validating it, then modifying it to generate two images: - PiRogue-OS-12-Pi3_and_Pi4 - PiRogue-OS-12-Pi5-Experimental Those are then compressed, checksums are generated, and the resulting 4 files are listed in a MANIFEST.txt file at the top-level, making it trivial to publish the relevant files. At least for the time being, no clean-up is performed. That means the original image can be used to run ./toaster again if a new development iteration is required.	2024-07-20 20:42:30 +02:00
raspberrypi	Deploy and clean rpi-resizerootfs hook and script.	2024-07-20 18:38:39 +02:00
build-images	Add script to build images and a list of files to publish.	2024-07-20 20:42:30 +02:00
README.md	Initial commit.	2024-07-20 07:22:44 +02:00

Cyril Brulebois 773c67d6ba Add script to build images and a list of files to publish.

Given a RASPBERRYPI_IMG_URL, this automates downloading the image and
its checksum, validating it, then modifying it to generate two images:
 - PiRogue-OS-12-Pi3_and_Pi4
 - PiRogue-OS-12-Pi5-Experimental

Those are then compressed, checksums are generated, and the resulting
4 files are listed in a MANIFEST.txt file at the top-level, making it
trivial to publish the relevant files.

At least for the time being, no clean-up is performed. That means the
original image can be used to run ./toaster again if a new development
iteration is required.

2024-07-20 20:42:30 +02:00

raspberrypi

Deploy and clean rpi-resizerootfs hook and script.

2024-07-20 18:38:39 +02:00

build-images

Add script to build images and a list of files to publish.

2024-07-20 20:42:30 +02:00

README.md

Initial commit.

2024-07-20 07:22:44 +02:00

README.md

PiRogue images

This repository contains the tools required to build “historical” PiRogue images, targeting Raspberry Pi 3 and Raspberry Pi 4.

Experimental support for the Raspberry Pi 5 is provided as well. As of July 2024, it is brand new, and further upgrades of packages like raspi-firmware (on the Debian side), or linux-image-* and firmware-brcm80211 (on the Raspberry OS side) might be problematic.

It operates by turning pristine Debian-provided images for Raspberry Pi into images ready to deploy PiRogue Tool Suite packages. In the future the same might happen for Debian-provided cloud images.