The correct path, now that I'm properly online, is /usr/lib/raspberrypi-sys-mods/. The pre-config from the official imager should be firstrun.sh in the boot filesystem. The scripts in there also have experimental support for config via a custom.toml file in the boot filesytem. A comment from a RPi developer on github says "custom.toml is just an experimental thing in case cloud-init doesn't work out. There are no plans to support it and it will be removed after cloud-init is added." Nevertheless, it's there today, and might have some short term value for you.… There are also the backend scripts in something like /usr/lib/rpi-sys-mods, which you can potentially hook into or manipulate from the first boot script.
Apologies for the vague paths from memory, reading the forum on the go without convenient access to a Pi.
And, one more tip, for the care and feeding of multiple Pis; but less important if you have gigabit Internet. I have APT on all of my Pis and other Linux instances pointed to a Docker container running ubuntu/squid on my NAS. Updates only get downloaded from the net once, then served at up to 2.5Gbit/s to my LAN. It's just a nice quality of life thing, if you have the resources on your LAN to do it. You can just run Squid natively on a Pi (without Docker), if you prefer; I mainly use Docker because my NAS uses a very limited NAS Linux for its OS, but can run full Linux containers under Docker. Just add a file named /etc/apt/apt.conf.d/99proxy with the following contents:
Code:
Acquire { http::Proxy "http://nas-name.local-or-address:3128"; https::Proxy "DIRECT";};Statistics: Posted by Murph9000 — Mon Sep 09, 2024 8:38 pm