Hi,

I've done this many times before, but previously within the support period for a particular RPi OS Version.

The current Version available for download appears to be Trixie and the previous Version was Bookworm.  Upgrading from Bookworm to Trixie seems to be even easier than it was the last time I did a full upgrade on a Pi, but a direct upgrade from Bullseye to Trixie is not so straightforward.  The question is; is it worth it?

Here is the background.  This system is part of the Minster Bells and Music Player at Wimborne Model Town.  There are two Pis in the system; one for music and one for bells and chimes.  It was originally installed in 2022 when Buster was current and has run largely untouched since then.  However, during the last summer season it stopped working and I was asked to fix it and at the same time upgrade it to provide better music levels in the Model Minster Nave (which has been a bit quiet since the last lot of speakers were replaced with something more in keeping with the environment).  The hardware is largely complete, and includes a bigger powered speaker hidden from view on a shelf in the Nave. However, I'm assuming that the time will come when Bullseye will no longer be supported (June this year apparently).

The thing is that these Pis are not connected directly to the Internet; there is another Pi in the way which acts as a firewall.  There is yet another Pi on the network which provides a VPN server, so that staff (me mainly) can log into any of the twenty or so Pis on site, including this one.  This particular Pi includes a built-in Webserver to allow staff to monitor the system and change the music etc.  It is only possible to access that Webserver via the VPN or by connecting to the Model Town's private WiFI. The Minster Music and Bells Pis are also protected by passwords.

So.  What are your thoughts?

--
Terry Coles


--
 Next meeting: Online, Jitsi, Tuesday, 2026-03-03 20:00
 Check to whom you are replying
 Meetings, mailing list, IRC, ...  https://dorset.lug.org.uk
 New thread, don't hijack:  mailto:[email protected]

Reply via email to