However, I’m afraid if we implement this, the next suggestion to allow a custom .profile or custom rc.local or systemd unit or any other config file appears. All this will be then used by 1 to 2 users, okay let’s say 20 after a while, but the code overhead stays for hundreds of thousands of systems and the continued maintenance of this feature stays for us .
You have two ways to do customisation on first boot, aside of mounting and editing the image file directly of course (I know not possible on Windows due to ext4 file system…):
Create /boot/Automation_Custom_PreScript.sh which will be executed on very early first boot stage (before any network setup is done) to apply any customisation.
Create /boot/Automation_Custom_Script.sh which will be executed after first login during the setup steps when you optionally selected the first software to be installed, so network is assured to be there and all basic system setup has finished.
In dietpi.txt there is also explained how to use the related setting to download a script from web and have it executed: