Boostrap a Pi 5 recipe.
For the time being, let's keep both Pi 3/Pi 4 and Pi 5 recipes separate, making it easy to modify the latter freely. Later on, it will probably make sense to have a common section.
This commit is contained in:
parent
a6f8c1fdf5
commit
d9fb46386f
36
raspberrypi/recipes/pi5.sh
Normal file
36
raspberrypi/recipes/pi5.sh
Normal file
@ -0,0 +1,36 @@
|
||||
# This recipe is sourced by the toaster, don't try to run it!
|
||||
|
||||
# shellcheck disable=SC2086
|
||||
toast_me() {
|
||||
echo "nameserver 1.1.1.1" > $MNT/etc/resolv.conf
|
||||
|
||||
# Install minimal tools
|
||||
chroot $MNT apt-get update
|
||||
chroot $MNT apt-get install -y wget sudo avahi-daemon
|
||||
chroot $MNT apt-get clean
|
||||
|
||||
# Ensure we have the pi user
|
||||
chroot $MNT adduser --disabled-password --gecos '' pi
|
||||
chroot $MNT adduser pi sudo
|
||||
chroot $MNT adduser pi plugdev
|
||||
echo "pi:raspberry" | chroot $MNT chpasswd
|
||||
|
||||
# Let's make sure we don't ship any SSH host keys. Also work around upstream
|
||||
# bug leading ssh.service to try and start before SSH host keys have been
|
||||
# generated (https://salsa.debian.org/raspi-team/image-specs/-/issues/72):
|
||||
# disable ssh.service here, and let the rpi-generate-ssh-host-keys.service
|
||||
# enable+start it when everything is ready.
|
||||
rm -f $MNT/etc/ssh/ssh_host_*
|
||||
chroot $MNT systemctl disable ssh.service
|
||||
sed '/^ExecStart=/a ExecStart=/usr/bin/systemctl enable --now ssh.service' \
|
||||
-i $MNT/etc/systemd/system/rpi-generate-ssh-host-keys.service
|
||||
|
||||
# Change the hostname
|
||||
echo "127.0.1.1 pirogue.local pirogue" >> $MNT/etc/hosts
|
||||
echo "::1 pirogue.local pirogue" >> $MNT/etc/hosts
|
||||
echo "pirogue" > $MNT/etc/hostname
|
||||
|
||||
# Add PTS PPA
|
||||
chroot $MNT wget -O /etc/apt/sources.list.d/pirogue.list https://pts-project.org/debian-12/pirogue.list
|
||||
chroot $MNT wget -O /etc/apt/trusted.gpg.d/pirogue.asc https://pts-project.org/debian-12/Key.gpg
|
||||
}
|
Loading…
Reference in New Issue
Block a user