Replies: 1 comment 2 replies
-
Noting for clarity, these scripts run exactly once: during the very first boot of the operating system. If you want something to run every boot of the system, you have to use one of the other methods: systemd, cron, etc. The correct script name pattern is 0*-*.sh, so they're both wrong. Will update the docs. You can also put scripts in /etc/sdm/0piboot/0*-*.sh. The key difference between 0piboot and 1piboot is that you can control whether the scripts in 1piboot are executed with the |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to sort out exactly how to set up a script to run after my fully customized and burned image has been booted in an RPi (e.g. perform a full image backup to a NAS). I think I may have it now, but thought I'd better clarify a couple of things in the docs.
https://github.com/gitbls/sdm/blob/master/Docs/Script-Details.md under 1piboot/* says "If enabled, the custom scripts in 1piboot/0*-.sh are run when the system first boots ..."
https://github.com/gitbls/sdm/blob/master/Docs/Command-Details.md under
--bootscripts
says "Directs sdm-firstboot to run the boot scripts in 1piboot/.sh."I suspect the custom scripts should go in /usr/local/sdm/1piboot not a further subdirectory named .sh. Is that correct? Is there any naming requirement for the scripts as might be implied by "0*-*.sh" ?
Beta Was this translation helpful? Give feedback.
All reactions