Ny post.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 4cd9a718d23fe180183f0e7f8dc01ff98a58bde7..bdf390a54ad42b203593a978c0588ba8b432317b 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -6,6 +6,104 @@
                 <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" />
        
                 <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>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
+               <link>http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</guid>
+                <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
+               <description>&lt;p&gt;In April we
+&lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html&quot;&gt;started
+to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
+how to set up and administrate a Debian system.  Today I am happy to
+report that the first draft is now publicly available.  You can find
+it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
+Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages).  The first
+eight chapters have a first draft translation, and we are working on
+proofreading the content.  If you want to help out, please start
+contributing using
+&lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
+hosted weblate project page&lt;/a&gt;, and get in touch using
+&lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
+translators mailing list&lt;/a&gt;.  Please also check out
+&lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
+contributors&lt;/a&gt;.  A good way to contribute is to proofread the text
+and update weblate if you find errors.&lt;/p&gt;
+
+&lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
+electronic form.&lt;/p&gt;
+</description>
+       </item>
+       
+       <item>
+               <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
+               <link>http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
+                <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
+               <description>&lt;p&gt;This summer, I read a great article
+&quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
+This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
+how to profile multi-threaded programs.  It presented a system for
+profiling software by running experiences in the running program,
+testing how run time performance is affected by &quot;speeding up&quot; parts of
+the code to various degrees compared to a normal run.  It does this by
+slowing down parallel threads while the &quot;faster up&quot; code is running
+and measure how this affect processing time.  The processing time is
+measured using probes inserted into the code, either using progress
+counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END).  It
+can also measure unmodified code by measuring complete the program
+runtime and running the program several times instead.&lt;/p&gt;
+
+&lt;p&gt;The project and presentation was so inspiring that I would like to
+get the system into Debian.  I
+&lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
+a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
+system ready for Debian by sending patches.  The build process need to
+be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
+to include the JavaScript web page used to visualize the collected
+profiling information included in the source package.
+But I expect that should work out fairly soon.&lt;/p&gt;
+
+&lt;p&gt;The way the system work is fairly simple.  To run an coz experiment
+on a binary with debug symbols available, start the program like this:
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+coz run --- program-to-run
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;This will create a text file profile.coz with the instrumentation
+information.  To show what part of the code affect the performance
+most, use a web browser and either point it to
+&lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
+or use the copy from git (in the gh-pages branch).  Check out this web
+site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like.  To make the
+profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
+COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
+code, rebuild and run the profiler.  This allow coz to do more
+targeted experiments.&lt;/p&gt;
+
+&lt;p&gt;A video published by ACM
+&lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
+Coz profiler&lt;/a&gt; is available from Youtube.  There is also a paper
+from the 25th Symposium on Operating Systems Principles available
+titled
+&lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
+finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
+for Coz is available from github.  It will only build with clang
+because it uses a
+&lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
+feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
+&lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
+it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
+
+&lt;p&gt;Please get in touch if you, like me, would like to see this piece
+of software in Debian.  I would very much like some help with the
+packaging effort, as I lack the in depth knowledge on how to package
+C++ libraries.&lt;/p&gt;
+</description>
+       </item>
+       

        <item>
                <title>Sales number for the Free Culture translation, first half of 2016</title>
                <link>http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html</link>
        <item>
                <title>Sales number for the Free Culture translation, first half of 2016</title>
                <link>http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html</link>


@@ -517,124 +615,5 @@ want to help the military in USA (and everyone else), use Tor. :)&lt;/p&gt;
 </description>
        </item>
        
 </description>
        </item>
        

-       <item>
-               <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
-               <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
-                <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
-               <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
-system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
-related packages.  The idea is to have a database of mappings between
-hardware and packages, and pop up a dialog suggesting for the user to
-install the packages to use a given hardware dongle.  Some use cases
-are when you insert a Yubikey, it proposes to install the software
-needed to control it; when you insert a braille reader list it
-proposes to install the packages needed to send text to the reader;
-and when you insert a ColorHug screen calibrator it suggests to
-install the driver for it.  The system work well, and even have a few
-command line tools to install firmware packages and packages for the
-hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
-
-&lt;p&gt;The system was initially written using aptdaemon, because I found
-good documentation and example code on how to use it.  But aptdaemon
-is going away and is generally being replaced by
-&lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
-so Isenkram needed a rewrite.  And today, thanks to the great patch
-from my college Sunil Mohan Adapa in the FreedomBox project, the
-rewrite finally took place.  I&#39;ve just uploaded a new version of
-Isenkram into Debian Unstable with the patch included, and the default
-for the background daemon is now to use PackageKit.  To check it out,
-install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
-and see if it is recognised.&lt;/p&gt;
-
-&lt;p&gt;If you want to know what kind of packages isenkram would propose for
-the machine it is running on, you can check out the isenkram-lookup
-program.  This is what it look like on a Thinkpad X230:&lt;/p&gt;
-
-&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
-% isenkram-lookup 
-bluez
-cheese
-fprintd
-fprintd-demo
-gkrellm-thinkbat
-hdapsd
-libpam-fprintd
-pidgin-blinklight
-thinkfan
-tleds
-tp-smapi-dkms
-tp-smapi-source
-tpb
-%p
-&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
-
-&lt;p&gt;The hardware mappings come from several places.  The preferred way
-is for packages to announce their hardware support using
-&lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
-cross distribution appstream system&lt;/a&gt;.
-See
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
-blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
-</description>
-       </item>
-       
-       <item>
-               <title>Discharge rate estimate in new battery statistics collector for Debian</title>
-               <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
-                <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
-               <description>&lt;p&gt;Yesterday I updated the
-&lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
-package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
-enterprising users.  There were some nice user and visible changes.
-First of all, both desktop menu entries now work.  A design flaw in
-one of the script made the history graph fail to show up (its PNG was
-dumped in ~/.xsession-errors) if no controlling TTY was available.
-The script worked when called from the command line, but not when
-called from the desktop menu.  I changed this to look for a DISPLAY
-variable or a TTY before deciding where to draw the graph, and now the
-graph window pop up as expected.&lt;/p&gt;
-
-&lt;p&gt;The next new feature is a discharge rate estimator in one of the
-graphs (the one showing the last few hours).  New is also the user of
-colours showing charging in blue and discharge in red.  The percentages
-of this graph is relative to last full charge, not battery design
-capacity.&lt;/p&gt;
-
-&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-rate.png&quot;/&gt;&lt;/p&gt;
-
-&lt;p&gt;The other graph show the entire history of the collected battery
-statistics, comparing it to the design capacity of the battery to
-visualise how the battery life time get shorter over time.  The red
-line in this graph is what the previous graph considers 100 percent:
-
-&lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-history.png&quot;/&gt;&lt;/p&gt;
-
-&lt;p&gt;In this graph you can see that I only charge the battery to 80
-percent of last full capacity, and how the capacity of the battery is
-shrinking. :(&lt;/p&gt;
-
-&lt;p&gt;The last new feature is in the collector, which now will handle
-more hardware models.  On some hardware, Linux power supply
-information is stored in /sys/class/power_supply/ACAD/, while the
-collector previously only looked in /sys/class/power_supply/AC/.  Now
-both are checked to figure if there is power connected to the
-machine.&lt;/p&gt;
-
-&lt;p&gt;If you are interested in how your laptop battery is doing, please
-check out the
-&lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
-in Debian unstable, or rebuild it on Jessie to get it working on
-Debian stable. :) The upstream source is available from &lt;a
-href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
-Patches are very welcome.&lt;/p&gt;
-
-&lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
-activities, please send Bitcoin donations to my address
-&lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
-</description>
-       </item>
-       

         </channel>
 </rss>
         </channel>
 </rss>