j4m3z0r

Yeah, I'm not crazy about startup scripts that then modify other startup scripts. I've just tried chattr +i on it, so I guess I'll see if it breaks the next time there's an update (at least I'll know about it if it breaks). However, as a less bad solution, what about adding a "PERSIST_ON_UPGRADE" flag to that file, which the dpkg scripts check for? If it's set, then the upgrade shouldn't overwrite the file.

Hi all, Fairly new to Armbian, and loving it so far. I'm running on a FriendlyElec NanoPi Neo Core 2 for a project I'm working on. I want to use the "conservative" cpufreq governor and set the max frequency to around 800MHz (battery and heat dissipation concerns). I've been able to do this by editing the /etc/defaults/cpufrequtils file, however (and there's a warning to this effect in the file) it gets overwritten whenever the linux-root package gets upgraded. I can think of some hacks to workaround this (eg re-setting those settings in /etc/rc.local), but I figured I'd check in here to see if there's a more robust, less hacky way to fix this. Is there a configuration flag to prevent this overwriting? Will something like chattr +i work, or will that break future upgrades? Would appreciate any pointers on a good way to solve this. Thanks!