anticapitalX
I’v installed the script on my frugal instance of antiX 26 , after a reboot on my installed antiX 26 instance , the script is fully working (without installing) .
I can verify it with these commands :
master@Master-PC:~
$ acpi -i 2>/dev/null
Battery 0: Not charging, 79%
Battery 0: design capacity 4686 mAh, last full capacity 3099 mAh = 66%
master@Master-PC:~
$ acpi -a
Adapter 0: on-line
So I concluded When you write threshold values to the ThinkPad battery controller chip, the values are written directly into the battery controller chip itself, where they are retained. This means the values live in the EC’s own non-volatile memory, not in your Linux filesystem. In many cases the charge thresholds are persistently stored in the hardware. They are retained when another operating system is started, provided they are not changed by software installed there and the hardware actually supports persistence. So your hard disk install inherited the setting from the hardware, not from any file on disk. The udev rule’s job is just to re-assert those values on boot as a safety net in case the EC ever loses them (battery removal, EC reset). But on ThinkPads it normally just finds what it already set.
Let's accept antiX as it is
Pure and Elegant by its nature