MichaIng
MichaIng
Probably I can do that today (not rewrite DietPi-Imager but creating an RPi F2FS image manually), but have two other tasks in the pipeline.
Image for testing up (I didn't find time to test it myself): **EDIT: REMOVED INVALID LINK** There is some more work to do to add full support, as well to...
Just flash it with any method you usually do, `dd` or Rufus or Etcher or RPi Imager (which I never used so far, but plan to suggest/commit 7z support to...
Does running `resize.f2fs /dev/mmcblk0p2` manually work? What does the log say? ``` cat /var/tmp/dietpi/logs/fs_partition_resize.log ```
Ahh, dammit, it cannot be used on a mounted device? Hmm, how to achieve that... Probably on a read-only mounted rootfs at least? ``` mount -o remount,ro / resize.f2fs /dev/mmcblk0p2...
Yes that is the reason why it needs to be done very early. I'm not sure how to reliably determine the process that "blocks" the fs, sometimes `lsof` shows not...
Many thanks for testing. Within the Node-RED environment you need to call DietPi scripts with full paths, e.g. `/boot/dietpi/dietpi-services`. The aliases are only created for interactive bash shells. And actually...
It should be actually set to `noindex, nofollow`, which equals to `none` for Google but is also respected by Bing and other search engines (which do not understand `none`). Changed...
Closing this in favour of https://github.com/nextcloud/server/issues/37409, since the warning is produced by the server, not by the Docker container setup.
Is it the same when you switch to `ondemand` CPU governor?