<link>http://people.skolelinux.org/pere/blog/</link>
<atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
+ <item>
+ <title>Making battery measurements a little easier in Debian</title>
+ <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
+ <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
+ <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
+ <description><p>Back in September, I blogged about
+<a href="http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html">the
+system I wrote to collect statistics about my laptop battery</a>, and
+how it showed the decay and death of this battery (now replaced). I
+created a simple deb package to handle the collection and graphing,
+but did not want to upload it to Debian as there were already
+<a href="https://tracker.debian.org/pkg/battery-stats">a battery-stats
+package in Debian</a> that should do the same thing, and I did not see
+a point of uploading a competing package when battery-stats could be
+fixed instead. I reported a few bugs about its non-function, and
+hoped someone would step in and fix it. But no-one did.</p>
+
+<p>I got tired of waiting a few days ago, and took matters in my own
+hands. The end result is that I am now the new upstream developer of
+battery stats (<a href="https://github.com/petterreinholdtsen/battery-stats">available from github</a>) and part of the team maintaining
+battery-stats in Debian, and the package in Debian unstable is finally
+able to collect battery status using the /sys/class/power_supply/
+information provided by the Linux kernel. If you install the
+battery-stats package from unstable now, you will be able to get a
+graph of the current battery fill level, to get some idea about the
+status of the battery. The source package build and work just fine in
+Debian testing and stable (and probably oldstable too, but I have not
+tested). The default graph you get for that system look like this:</p>
+
+<p align="center"><img src="http://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png" width="70%" align="center"></p>
+
+<p>My plans for the future is to merge my old scripts into the
+battery-stats package, as my old scripts collected a lot more details
+about the battery. The scripts are merged into the upstream
+battery-stats git repository already, but I am not convinced they work
+yet, as I changed a lot of paths along the way. Will have to test a
+bit more before I make a new release.</p>
+
+<p>I will also consider changing the file format slightly, as I
+suspect the way I combine several values into one field might make it
+impossible to know the type of the value when using it for processing
+and graphing.</p>
+
+<p>If you would like I would like to keep an close eye on your laptop
+battery, check out the battery-stats package in
+<a href="https://tracker.debian.org/pkg/battery-stats">Debian</a> and
+on
+<a href="https://github.com/petterreinholdtsen/battery-stats">github</a>.
+I would love some help to improve the system further.</p>
+</description>
+ </item>
+
<item>
<title>Creating, updating and checking debian/copyright semi-automatically</title>
<link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
</description>
</item>
- <item>
- <title>PGP key transition statement for key EE4E02F9</title>
- <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
- <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
- <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
- <description><p>I've needed a new OpenPGP key for a while, but have not had time to
-set it up properly. I wanted to generate it offline and have it
-available on <a href="http://shop.kernelconcepts.de/#openpgp">a OpenPGP
-smart card</a> for daily use, and learning how to do it and finding
-time to sit down with an offline machine almost took forever. But
-finally I've been able to complete the process, and have now moved
-from my old GPG key to a new GPG key. See
-<a href="http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt">the
-full transition statement, signed with both my old and new key</a> for
-the details. This is my new key:</p>
-
-<pre>
-pub 3936R/<a href="http://pgp.cs.uu.nl/stats/111D6B29EE4E02F9.html">111D6B29EE4E02F9</a> 2015-11-03 [expires: 2019-11-14]
- Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
-uid Petter Reinholdtsen &lt;pere@hungry.com&gt;
-uid Petter Reinholdtsen &lt;pere@debian.org&gt;
-sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
-sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
-sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
-</pre>
-
-<p>The key can be downloaded from the OpenPGP key servers, signed by
-my old key.</p>
-
-<p>If you signed my old key
-(<a href="http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html">DB4CCC4B2A30D729</a>),
-I'd very much appreciate a signature on my new key, details and
-instructions in the transition statement. I m happy to reciprocate if
-you have a similarly signed transition statement to present.</p>
-</description>
- </item>
-
</channel>
</rss>
projects / homepage.git / blobdiff