Go to file

Cyril Brulebois a9332126bb Work around longstanding bug regarding SSH host keys. The original image leads to repeated failures to start for sshd.service since there are no host keys initially. Make sure the unit in charge of getting those keys generated runs before sshd. The following block gets repeated otherwise: systemd[1]: Starting ssh.service - OpenBSD Secure Shell server... sshd[795]: sshd: no hostkeys available -- exiting. systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE systemd[1]: ssh.service: Failed with result 'exit-code'. systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server. systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1. systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.	2024-07-20 14:06:47 +02:00
raspberrypi	Work around longstanding bug regarding SSH host keys.	2024-07-20 14:06:47 +02:00
README.md	Initial commit.	2024-07-20 07:22:44 +02:00

Cyril Brulebois a9332126bb Work around longstanding bug regarding SSH host keys.

The original image leads to repeated failures to start for sshd.service
since there are no host keys initially. Make sure the unit in charge of
getting those keys generated runs before sshd.

The following block gets repeated otherwise:

    systemd[1]: Starting ssh.service - OpenBSD Secure Shell server...
    sshd[795]: sshd: no hostkeys available -- exiting.
    systemd[1]: ssh.service: Control process exited, code=exited, status=1/FAILURE
    systemd[1]: ssh.service: Failed with result 'exit-code'.
    systemd[1]: Failed to start ssh.service - OpenBSD Secure Shell server.
    systemd[1]: ssh.service: Scheduled restart job, restart counter is at 1.
    systemd[1]: Stopped ssh.service - OpenBSD Secure Shell server.

2024-07-20 14:06:47 +02:00

raspberrypi

Work around longstanding bug regarding SSH host keys.

2024-07-20 14:06:47 +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.