MichaIng
MichaIng
When you change the backup location, only a single new backup is created in one run. The configured amount of "slots" is not forcefully created. When the target drive is...
Ah nice, I totally forgot that the target path can be set/overridden via CLI 😅. Indeed your second solution looks best when you want a single iteration on the remote...
> The dietpi-backup function tried to backup all iterations It does only a single backup iteration per run, so that shouldn't be the issue.
Okay let's close it as you have a working solution. I'm also still not sure why the backup would hang on the dry run 🤔.
Any other change to this filesystem is persistent, e.g. when you create a test file just in the same directory? Can you show: ```sh ls -l /etc/systemd/timesyncd.conf ```
I'll mark this as closed for now. Feel free to reopen if the issue persists.
udev rules should be a clever way to assign GPIO states as fast as the device is detected by the kernel.
Like so, setting GPIO 21 of chip 0, as fast as GPIO chip 0 is added/detected: ```sh echo 'SUBSYSTEM=="gpio", KERNEL=="gpiochip0", ACTION=="add", RUN+="/usr/bin/gpioset gpiochip0 21=1"' > /etc/udev/rules.d/99-gpio.rules ```
I'll mark this as closed. Feel free to reopen if required.
I'll mark this as closed. Feel free to reopen if the issue persists.