Let me start by saying I'm a long time fan, first time poster. I use DietPi as the base for a few varying projects.
And with that out of the way, I was wondering if there is there any chance of having the update tool identify (or provide enough info for the user to decide) is a reboot is actually required?
With many of the release updates consisting mainly of script updates,the generic prompt seems to suggest that an update is required. Since many of the scripts do not run as a daemon, why is a reboot required?
Secondly, has the link to the changelog been removed for any particular reason?
Suggestions for features and software you would like to see in DietPi, goes here.
2 posts • Page 1 of 1
Simple answer = Sometimesnoonereallycares wrote: is a reboot is actually required?
Its recommended to reboot after all updates, but its not required (hence we leave it down to the user). However, if for example we patch a dtoverlay entry, a reboot would be required.
A reboot will also ensure DietPi-Ramdisk saves the updated DietPi code to disk during reboot. Without the reboot, you are prone to issues should a power loss occur, as DietPi code wont be updated on disk.
Available here:Secondly, has the link to the changelog been removed for any particular reason?
https://github.com/Fourdee/DietPi/blob/ ... NGELOG.txt