Generated.

diff --git a/blog/The_life_and_death_of_a_laptop_battery.html b/blog/The_life_and_death_of_a_laptop_battery.html
index 0e0e3086b0297d16434703564749dd59637639c5..d7eaa3183a59492f486a97b652fee8c0a96a9973 100644 (file)
--- a/blog/The_life_and_death_of_a_laptop_battery.html
+++ b/blog/The_life_and_death_of_a_laptop_battery.html
@@ -50,8 +50,8 @@ available in Debian.</p>
 battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity.  My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity.  My
+collector shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -76,7 +76,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
        for f in $files; do \
            printf "%s," $(cat $f); \
@@ -111,7 +111,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
 </pre>
 
 <p>I wrote a small script to create a graph of the charge development
-over time.  This graph depicted above show the slow death of mylaptop
+over time.  This graph depicted above show the slow death of my laptop
 battery.</p>
 
 <p>But why is this happening?  Why are my laptop batteries always
@@ -145,6 +145,14 @@ speed change over time, or if this stay the same.  I did not yet try
 to write a tool to calculate the derivative values of the battery
 level, but suspect some interesting insights might be learned from
 those.</p>
+
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop.  I've done so now, but expect my existing battery is toast
+and need to be replaced.  The proposal is unfortunately Thinkpad
+specific.</p>
 </div>
       
       <div class="tags">Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.</div>

diff --git a/blog/archive/2015/09/09.rss b/blog/archive/2015/09/09.rss
index 4d3f6ab26eb122cbbbf61ef35b9514f9a3e68434..dae65431488bd9b98a7c28058781b7ffdd2f33b0 100644 (file)
--- a/blog/archive/2015/09/09.rss
+++ b/blog/archive/2015/09/09.rss
@@ -39,8 +39,8 @@ available in Debian.</p>
 battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity.  My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity.  My
+collector shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -65,7 +65,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
        for f in $files; do \
            printf "%s," $(cat $f); \
@@ -100,7 +100,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
 </pre>
 
 <p>I wrote a small script to create a graph of the charge development
-over time.  This graph depicted above show the slow death of mylaptop
+over time.  This graph depicted above show the slow death of my laptop
 battery.</p>
 
 <p>But why is this happening?  Why are my laptop batteries always
@@ -134,6 +134,14 @@ speed change over time, or if this stay the same.  I did not yet try
 to write a tool to calculate the derivative values of the battery
 level, but suspect some interesting insights might be learned from
 those.</p>
+
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop.  I've done so now, but expect my existing battery is toast
+and need to be replaced.  The proposal is unfortunately Thinkpad
+specific.</p>
 </description>
        </item>
        

diff --git a/blog/archive/2015/09/index.html b/blog/archive/2015/09/index.html
index 3200288c01875430a0049881b840eadabe997b7a..c153975f8d26e2df3ff8e8490d3bb263c5f848a5 100644 (file)
--- a/blog/archive/2015/09/index.html
+++ b/blog/archive/2015/09/index.html
@@ -57,8 +57,8 @@ available in Debian.</p>
 battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity.  My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity.  My
+collector shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -83,7 +83,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
        for f in $files; do \
            printf "%s," $(cat $f); \
@@ -118,7 +118,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
 </pre>
 
 <p>I wrote a small script to create a graph of the charge development
-over time.  This graph depicted above show the slow death of mylaptop
+over time.  This graph depicted above show the slow death of my laptop
 battery.</p>
 
 <p>But why is this happening?  Why are my laptop batteries always
@@ -153,6 +153,14 @@ to write a tool to calculate the derivative values of the battery
 level, but suspect some interesting insights might be learned from
 those.</p>
 
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop.  I've done so now, but expect my existing battery is toast
+and need to be replaced.  The proposal is unfortunately Thinkpad
+specific.</p>
+
       </div>
       <div class="tags">
         

diff --git a/blog/index.html b/blog/index.html
index 476598e320ca944b5cd66b637dc115fe73245b47..51aa92a4155e00a581692c018c7b998a0caf256d 100644 (file)
--- a/blog/index.html
+++ b/blog/index.html
@@ -50,8 +50,8 @@ available in Debian.</p>
 battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity.  My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity.  My
+collector shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -76,7 +76,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
        for f in $files; do \
            printf "%s," $(cat $f); \
@@ -111,7 +111,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
 </pre>
 
 <p>I wrote a small script to create a graph of the charge development
-over time.  This graph depicted above show the slow death of mylaptop
+over time.  This graph depicted above show the slow death of my laptop
 battery.</p>
 
 <p>But why is this happening?  Why are my laptop batteries always
@@ -145,6 +145,14 @@ speed change over time, or if this stay the same.  I did not yet try
 to write a tool to calculate the derivative values of the battery
 level, but suspect some interesting insights might be learned from
 those.</p>
+
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop.  I've done so now, but expect my existing battery is toast
+and need to be replaced.  The proposal is unfortunately Thinkpad
+specific.</p>
 </div>
       <div class="tags">
         

diff --git a/blog/index.rss b/blog/index.rss
index e9e3a29be8f192d1de0ad0c90b8ad1afdca58bb5..ccbf39e425f663459c7945bfe4305ef920a6eed2 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -39,8 +39,8 @@ available in Debian.</p>
 battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity.  My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity.  My
+collector shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -65,7 +65,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
        for f in $files; do \
            printf "%s," $(cat $f); \
@@ -100,7 +100,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
 </pre>
 
 <p>I wrote a small script to create a graph of the charge development
-over time.  This graph depicted above show the slow death of mylaptop
+over time.  This graph depicted above show the slow death of my laptop
 battery.</p>
 
 <p>But why is this happening?  Why are my laptop batteries always
@@ -134,6 +134,14 @@ speed change over time, or if this stay the same.  I did not yet try
 to write a tool to calculate the derivative values of the battery
 level, but suspect some interesting insights might be learned from
 those.</p>
+
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop.  I've done so now, but expect my existing battery is toast
+and need to be replaced.  The proposal is unfortunately Thinkpad
+specific.</p>
 </description>
        </item>
        

diff --git a/blog/tags/debian/debian.rss b/blog/tags/debian/debian.rss
index b9e70406dae170adca2670115e551fd28ac41325..71c98d4e1aec7eef45cf7b86318addf73579c1d9 100644 (file)
--- a/blog/tags/debian/debian.rss
+++ b/blog/tags/debian/debian.rss
@@ -39,8 +39,8 @@ available in Debian.</p>
 battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity.  My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity.  My
+collector shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -65,7 +65,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
        for f in $files; do \
            printf "%s," $(cat $f); \
@@ -100,7 +100,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
 </pre>
 
 <p>I wrote a small script to create a graph of the charge development
-over time.  This graph depicted above show the slow death of mylaptop
+over time.  This graph depicted above show the slow death of my laptop
 battery.</p>
 
 <p>But why is this happening?  Why are my laptop batteries always
@@ -134,6 +134,14 @@ speed change over time, or if this stay the same.  I did not yet try
 to write a tool to calculate the derivative values of the battery
 level, but suspect some interesting insights might be learned from
 those.</p>
+
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop.  I've done so now, but expect my existing battery is toast
+and need to be replaced.  The proposal is unfortunately Thinkpad
+specific.</p>
 </description>
        </item>
        

diff --git a/blog/tags/debian/index.html b/blog/tags/debian/index.html
index 268a5bfd6b11b31da21676b65b49002699264226..77da79ed852dd890ddf9293f1d8632286aa33455 100644 (file)
--- a/blog/tags/debian/index.html
+++ b/blog/tags/debian/index.html
@@ -56,8 +56,8 @@ available in Debian.</p>
 battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity.  My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity.  My
+collector shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -82,7 +82,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
        for f in $files; do \
            printf "%s," $(cat $f); \
@@ -117,7 +117,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
 </pre>
 
 <p>I wrote a small script to create a graph of the charge development
-over time.  This graph depicted above show the slow death of mylaptop
+over time.  This graph depicted above show the slow death of my laptop
 battery.</p>
 
 <p>But why is this happening?  Why are my laptop batteries always
@@ -152,6 +152,14 @@ to write a tool to calculate the derivative values of the battery
 level, but suspect some interesting insights might be learned from
 those.</p>
 
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop.  I've done so now, but expect my existing battery is toast
+and need to be replaced.  The proposal is unfortunately Thinkpad
+specific.</p>
+
       </div>
       <div class="tags">
         

diff --git a/blog/tags/english/english.rss b/blog/tags/english/english.rss
index a2fb0d3312a8570d2da514f220b3fdb7a2585617..85d697331b0457206aa11eb2d7d35232ddfb9ede 100644 (file)
--- a/blog/tags/english/english.rss
+++ b/blog/tags/english/english.rss
@@ -39,8 +39,8 @@ available in Debian.</p>
 battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity.  My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity.  My
+collector shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -65,7 +65,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
        for f in $files; do \
            printf "%s," $(cat $f); \
@@ -100,7 +100,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
 </pre>
 
 <p>I wrote a small script to create a graph of the charge development
-over time.  This graph depicted above show the slow death of mylaptop
+over time.  This graph depicted above show the slow death of my laptop
 battery.</p>
 
 <p>But why is this happening?  Why are my laptop batteries always
@@ -134,6 +134,14 @@ speed change over time, or if this stay the same.  I did not yet try
 to write a tool to calculate the derivative values of the battery
 level, but suspect some interesting insights might be learned from
 those.</p>
+
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop.  I've done so now, but expect my existing battery is toast
+and need to be replaced.  The proposal is unfortunately Thinkpad
+specific.</p>
 </description>
        </item>
        

diff --git a/blog/tags/english/index.html b/blog/tags/english/index.html
index 48fb45b75087aae7e1493f009d83eac5fe0057f9..e5f74e794a09e6d6a4e876df5a3913a5c80afb28 100644 (file)
--- a/blog/tags/english/index.html
+++ b/blog/tags/english/index.html
@@ -56,8 +56,8 @@ available in Debian.</p>
 battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
-when it is unable to charge above 7% of original capasity.  My
-colletor shell script is quite simple and look like this:</p>
+when it is unable to charge above 7% of original capacity.  My
+collector shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -82,7 +82,7 @@ fi
 
 log_battery() {
     # Print complete message in one echo call, to avoid race condition
-    # when several log processes run in parallell.
+    # when several log processes run in parallel.
     msg=$(printf "%s," $(date +%s); \
        for f in $files; do \
            printf "%s," $(cat $f); \
@@ -117,7 +117,7 @@ timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_fu
 </pre>
 
 <p>I wrote a small script to create a graph of the charge development
-over time.  This graph depicted above show the slow death of mylaptop
+over time.  This graph depicted above show the slow death of my laptop
 battery.</p>
 
 <p>But why is this happening?  Why are my laptop batteries always
@@ -152,6 +152,14 @@ to write a tool to calculate the derivative values of the battery
 level, but suspect some interesting insights might be learned from
 those.</p>
 
+<p>Update 2015-09-24: I got a top to install the packages
+acpi-call-dkms and tlp (unfortunately missing in Debian stable)
+packages instead of the tp-smapi-dkms package I had tried to use
+initially, and use 'tlp setcharge 40 80' to change when charging start
+and stop.  I've done so now, but expect my existing battery is toast
+and need to be replaced.  The proposal is unfortunately Thinkpad
+specific.</p>
+
       </div>
       <div class="tags">