The abbey's Raspberry Pi runs the Raspberry Pi OS desktop off an NVMe
SSD. A fresh install should go something like this:
-- Write the disk image, =2023-12-05-raspios-bookworm-arm64.img.xz=, to
- the SSD and plug it into the Pi. Leave the µSD card socket empty.
+- Write the disk image, =2025-12-04-raspios-trixie-arm64-full.img.xz=,
+ to the SSD and plug it into the Pi. If the SSD is not readily
+ accessible, write the disk image to a USB HD (thumb drive) or µSD
+ card and insert it.
- Attach an HDMI monitor, a USB keyboard/mouse, and the cloister
Ethernet, and power up.
- Answer first-boot installation questions:
+ Language: English (USA)
+ Keyboard: English (USA)
- + root password: <blank>
- + new user name: System Administrator
+ new username: sysadm
+ new password: <password>
- [[*Add to Core DHCP][Add to Core DHCP]]
- [[*Create Wired Domain Name][Create Wired Domain Name]]
-- Log in as ~sysadm~ on the console.
+- Launch the desktop.
+- If the desktop is running on a USB HD (thumb drive) or μSD card, use
+ the Raspberry Pi Imager app in Accessories in the main menu. Choose
+ to install the 64-bit OS on the inaccessible SSD. Rebooted without
+ the USB HD or μSD card inserted and then answer the first-boot
+ installation questions again.
+- Right click on the desktop (background) and choose Preferences. In
+ the Control Centre choose Interfaces in the left side bar and toggle
+ SSH on.
+
- Run ~sudo raspi-config~ and use the following menu items.
+ S4 Hostname (Set name for this computer on a network): new
+ I1 SSH (Enable/disable remote command line access using SSH): enable
PCs running Debian. The process of cloistering these machines
follows.
-- Write the disk image, e.g. =debian-12.11.0-amd64-netinst.iso=, to a
- USB drive and connect it to the PC.
+- Write the disk image, e.g. =debian-live-13.2.0-amd64-cinnamon.iso=,
+ to a USB drive and connect it to the PC.
- Connect an HDMI monitor, a USB keyboard/mouse, and the cloister
Ethernet, and power up. Choose to boot from the USB drive.
-- Answer first-boot installation questions as detailed in the
- preparation of [[file:Institute/README.org*A Test Machine][A Test Machine]] for a Small Institute.
- [[*Add to Core DHCP][Add to Core DHCP]]
- [[*Create Wired Domain Name][Create Wired Domain Name]]
+- Answer first-boot installation questions as detailed in the
+ preparation of [[file:Institute/README.org*A Test Machine][A Test Machine]] for a Small Institute.
- Log in as ~sysadm~ on the console.
- [[*Update From Cloister Apt Cache][Update From Cloister Apt Cache]]
-- Install OpenSSH, unless it already was when included in the initial
- Software selection during the Debian installation. Run the
- following if unsure.
+- Install ~openssh-server~, unless it was included in the
+ distribution. Run the following if unsure.
: sudo apt install openssh-server
- [[*Authorize Remote Administration][Authorize Remote Administration]]
- [[*Configure with Ansible][Configure with Ansible]]
IoT devices (IP cameras, HDTV tuners, etc.) often have their MAC
address printed on their case or mentioned in a configuration page.
-The MAC address /must/ also appear in the device's DHCP Discover
-broadcasts, which are logged to =/var/log/daemon.log= on Core. As a
-last (or first!) resort, the following command line should reveal the
-new device's MAC.
+The MAC address will also appear in the device's DHCP Discover
+broadcasts. The following command displays the last 5 messages logged
+by the DHCP daemon and then waits for more.
#+BEGIN_SRC sh
-tail -100 /var/log/daemon.log | grep DISCOVER
+journalctl -t dhcpd -n 5 -f
#+END_SRC
With the new device's Ethernet MAC in hand, a stanza like the
projects / Network.git / commitdiff