Ny blogpost.

[homepage.git] / blog / index.rss

diff --git a/blog/index.rss b/blog/index.rss
index 5f85e3d855f4822accd0503a6efdb8cd5da9938b..b8f9c7a1a8bffe705aa67c608f3122b64a04076b 100644 (file)
--- a/blog/index.rss
+++ b/blog/index.rss
@@ -7,149 +7,59 @@
                 <atom:link href="http://people.skolelinux.org/pere/blog/index.rss" rel="self" type="application/rss+xml" />
        
        <item>
                 <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&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 in 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>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sales_number_for_the_Free_Culture_translation__first_half_of_2016.html</guid>
-                <pubDate>Fri, 5 Aug 2016 22:45:00 +0200</pubDate>
-               <description>&lt;p&gt;As my regular readers probably remember, the last year I published
-a French and Norwegian translation of the classic
-&lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free Culture book&lt;/a&gt; by the
-founder of the Creative Commons movement, Lawrence Lessig.  A bit less
-known is the fact that due to the way I created the translations,
-using docbook and po4a, I also recreated the English original.  And
-because I already had created a new the PDF edition, I published it
-too.  The revenue from the books are sent to the Creative Commons
-Corporation.  In other words, I do not earn any money from this
-project, I just earn the warm fuzzy feeling that the text is available
-for a wider audience and more people can learn why the Creative
-Commons is needed.&lt;/p&gt;
-
-&lt;p&gt;Today, just for fun, I had a look at the sales number over at
-Lulu.com, which take care of payment, printing and shipping.  Much to
-my surprise, the English edition is selling better than both the
-French and Norwegian edition, despite the fact that it has been
-available in English since it was first published.  In total, 24 paper
-books was sold for USD $19.99 between 2016-01-01 and 2016-07-31:&lt;/p&gt;
+               <title>Updated sales number for my Free Culture paper editions</title>
+               <link>http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html</guid>
+                <pubDate>Mon, 12 Jun 2017 11:40:00 +0200</pubDate>
+               <description>&lt;p&gt;It is pleasing to see that the work we put down in publishing new
+editions of the classic &lt;a href=&quot;http://www.free-culture.cc/&quot;&gt;Free
+Culture book&lt;/a&gt; by the founder of the Creative Commons movement,
+Lawrence Lessig, is still being appreciated.  I had a look at the
+latest sales numbers for the paper edition today.  Not too impressive,
+but happy to see some buyers still exist.  All the revenue from the
+books is sent to the &lt;a href=&quot;https://creativecommons.org/&quot;&gt;Creative
+Commons Corporation&lt;/a&gt;, and they receive the largest cut if you buy
+directly from Lulu.  Most books are sold via Amazon, with Ingram
+second and only a small fraction directly from Lulu.  The ebook
+edition is available for free from
+&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;Github&lt;/a&gt;.&lt;/p&gt;

 
 &lt;table border=&quot;0&quot;&gt;
 
 &lt;table border=&quot;0&quot;&gt;

-&lt;tr&gt;&lt;th&gt;Title / language&lt;/th&gt;&lt;th&gt;Quantity&lt;/th&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;Culture Libre / French&lt;/a&gt;&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Fri kultur / Norwegian&lt;/a&gt;&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;&lt;/tr&gt;
-&lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;Free Culture / English&lt;/a&gt;&lt;/td&gt;&lt;td align=&quot;right&quot;&gt;14&lt;/td&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;th rowspan=&quot;2&quot; valign=&quot;bottom&quot;&gt;Title / language&lt;/th&gt;&lt;th colspan=&quot;3&quot;&gt;Quantity&lt;/th&gt;&lt;/tr&gt;
+&lt;tr&gt;&lt;th&gt;2016 jan-jun&lt;/th&gt;&lt;th&gt;2016 jul-dec&lt;/th&gt;&lt;th&gt;2017 jan-may&lt;/th&gt;&lt;/tr&gt;
+
+&lt;tr&gt;
+  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;Culture Libre / French&lt;/a&gt;&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;3&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;6&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;15&lt;/td&gt;
+&lt;/tr&gt;
+
+&lt;tr&gt;
+  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Fri kultur / Norwegian&lt;/a&gt;&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;7&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;1&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;0&lt;/td&gt;
+&lt;/tr&gt;
+
+&lt;tr&gt;
+  &lt;td&gt;&lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;Free Culture / English&lt;/a&gt;&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;14&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;27&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;16&lt;/td&gt;
+&lt;/tr&gt;
+
+&lt;tr&gt;
+  &lt;td&gt;Total&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;24&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;34&lt;/td&gt;
+  &lt;td align=&quot;right&quot;&gt;31&lt;/td&gt;
+&lt;/tr&gt;
+

 &lt;/table&gt;
 
 &lt;/table&gt;
 

-&lt;p&gt;The books are available both from Lulu.com and from large book
-stores like Amazon and Barnes&amp;Noble.  Most revenue, around $10 per
-book, is sent to the Creative Commons project when the book is sold
-directly by Lulu.com.  The other channels give less revenue.  The
-summary from Lulu tell me 10 books was sold via the Amazon channel, 10
-via Ingram (what is this?) and 4 directly by Lulu.  And Lulu.com tells
-me that the revenue sent so far this year is USD $101.42.  No idea
-what kind of sales numbers to expect, so I do not know if that is a
-good amount of sales for a 10 year old book or not.  But it make me
-happy that the buyers find the book, and I hope they enjoy reading it
-as much as I did.&lt;/p&gt;
-
-&lt;p&gt;The ebook edition is available for free from
-&lt;a href=&quot;https://github.com/petterreinholdtsen/free-culture-lessig&quot;&gt;Github&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;A bit sad to see the low sales number on the Norwegian edition, and
+a bit surprising the English edition still selling so well.&lt;/p&gt;

 
 &lt;p&gt;If you would like to translate and publish the book in your native
 language, I would be happy to help make it happen.  Please get in
 
 &lt;p&gt;If you would like to translate and publish the book in your native
 language, I would be happy to help make it happen.  Please get in


@@ -158,460 +68,587 @@ touch.&lt;/p&gt;
        </item>
        
        <item>
        </item>
        
        <item>

-               <title>Vitenskapen tar som vanlig feil igjen - relativt feil</title>
-               <link>http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Vitenskapen_tar_som_vanlig_feil_igjen___relativt_feil.html</guid>
-                <pubDate>Mon, 1 Aug 2016 16:00:00 +0200</pubDate>
-               <description>&lt;p&gt;For mange år siden leste jeg en klassisk tekst som gjorde såpass
-inntrykk på meg at jeg husker den fortsatt, flere år senere, og bruker
-argumentene fra den stadig vekk.  Teksten var «The Relativity of
-Wrong» som Isaac Asimov publiserte i Skeptical Inquirer i 1989.  Den
-gir litt perspektiv rundt formidlingen av vitenskapelige resultater.
-Jeg har hatt lyst til å kunne dele den også med folk som ikke
-behersker engelsk så godt, som barn og noen av mine eldre slektninger,
-og har savnet å ha den tilgjengelig på norsk.  For to uker siden tok
-jeg meg sammen og kontaktet Asbjørn Dyrendal i foreningen Skepsis om
-de var interessert i å publisere en norsk utgave på bloggen sin, og da
-han var positiv tok jeg kontakt med Skeptical Inquirer og spurte om
-det var greit for dem.  I løpet av noen dager fikk vi tilbakemelding
-fra Barry Karr hos The Skeptical Inquirer som hadde sjekket og fått OK
-fra Robyn Asimov som representerte arvingene i Asmiov-familien og gikk
-igang med oversettingen.&lt;/p&gt;
-
-&lt;p&gt;Resultatet, &lt;a href=&quot;http://www.skepsis.no/?p=1617&quot;&gt;«Relativt
-feil»&lt;/a&gt;, ble publisert på skepsis-bloggen for noen minutter siden.
-Jeg anbefaler deg på det varmeste å lese denne teksten og dele den med
-dine venner.&lt;/p&gt;
-
-&lt;p&gt;For å håndtere oversettelsen og sikre at original og oversettelse
-var i sync brukte vi git, po4a, GNU make og Transifex.  Det hele
-fungerte utmerket og gjorde det enkelt å dele tekstene og jobbe sammen
-om finpuss på formuleringene.  Hadde hosted.weblate.org latt meg
-opprette nye prosjekter selv i stedet for å måtte kontakte
-administratoren der, så hadde jeg brukt weblate i stedet.&lt;/p&gt;
+               <title>Release 0.1.1 of free software archive system Nikita announced</title>
+               <link>http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html</guid>
+                <pubDate>Sat, 10 Jun 2017 00:40:00 +0200</pubDate>
+               <description>&lt;p&gt;I am very happy to report that the
+&lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita Noark 5
+core project&lt;/a&gt; tagged its second release today.  The free software
+solution is an implementation of the Norwegian archive standard Noark
+5 used by government offices in Norway.  These were the changes in
+version 0.1.1 since version 0.1.0 (from NEWS.md):
+
+&lt;ul&gt;
+
+ &lt;li&gt;Continued work on the angularjs GUI, including document upload.&lt;/li&gt;
+ &lt;li&gt;Implemented correspondencepartPerson, correspondencepartUnit and
+   correspondencepartInternal&lt;/li&gt;
+ &lt;li&gt;Applied for coverity coverage and started submitting code on
+   regualr basis.&lt;/li&gt;
+ &lt;li&gt;Started fixing bugs reported by coverity&lt;/li&gt;
+ &lt;li&gt;Corrected and completed HATEOAS links to make sure entire API is
+   available via URLs in _links.&lt;/li&gt;
+ &lt;li&gt;Corrected all relation URLs to use trailing slash.&lt;/li&gt;
+ &lt;li&gt;Add initial support for storing data in ElasticSearch.&lt;/li&gt;
+ &lt;li&gt;Now able to receive and store uploaded files in the archive.&lt;/li&gt;
+ &lt;li&gt;Changed JSON output for object lists to have relations in _links.&lt;/li&gt;
+ &lt;li&gt;Improve JSON output for empty object lists.&lt;/li&gt;
+ &lt;li&gt;Now uses correct MIME type application/vnd.noark5-v4+json.&lt;/li&gt;
+ &lt;li&gt;Added support for docker container images.&lt;/li&gt;
+ &lt;li&gt;Added simple API browser implemented in JavaScript/Angular.&lt;/li&gt;
+ &lt;li&gt;Started on archive client implemented in JavaScript/Angular.&lt;/li&gt;
+ &lt;li&gt;Started on prototype to show the public mail journal.&lt;/li&gt;
+ &lt;li&gt;Improved performance by disabling Sprint FileWatcher.&lt;/li&gt;
+ &lt;li&gt;Added support for &#39;arkivskaper&#39;, &#39;saksmappe&#39; and &#39;journalpost&#39;.&lt;/li&gt;
+ &lt;li&gt;Added support for some metadata codelists.&lt;/li&gt;
+ &lt;li&gt;Added support for Cross-origin resource sharing (CORS).&lt;/li&gt;
+ &lt;li&gt;Changed login method from Basic Auth to JSON Web Token (RFC 7519)
+   style.&lt;/li&gt;
+ &lt;li&gt;Added support for GET-ing ny-* URLs.&lt;/li&gt;
+ &lt;li&gt;Added support for modifying entities using PUT and eTag.&lt;/li&gt;
+ &lt;li&gt;Added support for returning XML output on request.&lt;/li&gt;
+ &lt;li&gt;Removed support for English field and class names, limiting ourself
+   to the official names.&lt;/li&gt;
+ &lt;li&gt;...&lt;/li&gt;
+ 
+&lt;/ul&gt;
+
+&lt;p&gt;If this sound interesting to you, please contact us on IRC (#nikita
+on irc.freenode.net) or email
+(&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;nikita-noark
+mailing list).&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Techno TV broadcasting live across Norway and the Internet (#debconf16, #nuug) on @frikanalen</title>
-               <link>http://people.skolelinux.org/pere/blog/Techno_TV_broadcasting_live_across_Norway_and_the_Internet___debconf16___nuug__on__frikanalen.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Techno_TV_broadcasting_live_across_Norway_and_the_Internet___debconf16___nuug__on__frikanalen.html</guid>
-                <pubDate>Mon, 1 Aug 2016 10:30:00 +0200</pubDate>
-               <description>&lt;p&gt;Did you know there is a TV channel broadcasting talks from DebConf
-16 across an entire country?  Or that there is a TV channel
-broadcasting talks by or about
-&lt;a href=&quot;http://beta.frikanalen.no/video/625529/&quot;&gt;Linus Torvalds&lt;/a&gt;,
-&lt;a href=&quot;http://beta.frikanalen.no/video/625599/&quot;&gt;Tor&lt;/a&gt;,
-&lt;a href=&quot;http://beta.frikanalen.no/video/624019/&quot;&gt;OpenID&lt;/A&gt;,
-&lt;a href=&quot;http://beta.frikanalen.no/video/625624/&quot;&gt;Common Lisp&lt;/a&gt;,
-&lt;a href=&quot;http://beta.frikanalen.no/video/625446/&quot;&gt;Civic Tech&lt;/a&gt;,
-&lt;a href=&quot;http://beta.frikanalen.no/video/625090/&quot;&gt;EFF founder John Barlow&lt;/a&gt;,
-&lt;a href=&quot;http://beta.frikanalen.no/video/625432/&quot;&gt;how to make 3D
-printer electronics&lt;/a&gt; and many more fascinating topics?  It works
-using only free software (all of it
-&lt;a href=&quot;http://github.com/Frikanalen&quot;&gt;available from Github&lt;/a&gt;), and
-is administrated using a web browser and a web API.&lt;/p&gt;
-
-&lt;p&gt;The TV channel is the Norwegian open channel
-&lt;a href=&quot;http://www.frikanalen.no/&quot;&gt;Frikanalen&lt;/a&gt;, and I am involved
-via &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG member association&lt;/a&gt; in
-running and developing the software for the channel.  The channel is
-organised as a member organisation where its members can upload and
-broadcast what they want (think of it as Youtube for national
-broadcasting television).  Individuals can broadcast too.  The time
-slots are handled on a first come, first serve basis.  Because the
-channel have almost no viewers and very few active members, we can
-experiment with TV technology without too much flack when we make
-mistakes.  And thanks to the few active members, most of the slots on
-the schedule are free.  I see this as an opportunity to spread
-knowledge about technology and free software, and have a script I run
-regularly to fill up all the open slots the next few days with
-technology related video.  The end result is a channel I like to
-describe as Techno TV - filled with interesting talks and
-presentations.&lt;/p&gt;
-
-&lt;p&gt;It is available on channel 50 on the Norwegian national digital TV
-network (RiksTV).  It is also available as a multicast stream on
-Uninett.  And finally, it is available as
-&lt;a href=&quot;http://beta.frikanalen.no/&quot;&gt;a WebM unicast stream&lt;/a&gt; from
-Frikanalen and NUUG.  Check it out. :)&lt;/p&gt;
+               <title>Idea for storing trusted timestamps in a Noark 5 archive</title>
+               <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html</guid>
+                <pubDate>Wed, 7 Jun 2017 21:40:00 +0200</pubDate>
+               <description>&lt;p&gt;&lt;em&gt;This is a copy of
+&lt;a href=&quot;https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html&quot;&gt;an
+email I posted to the nikita-noark mailing list&lt;/a&gt;.  Please follow up
+there if you would like to discuss this topic.  The background is that
+we are making a free software archive system based on the Norwegian
+&lt;a href=&quot;https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden&quot;&gt;Noark
+5 standard&lt;/a&gt; for government archives.&lt;/em&gt;&lt;/p&gt;
+
+&lt;p&gt;I&#39;ve been wondering a bit lately how trusted timestamps could be
+stored in Noark 5.
+&lt;a href=&quot;https://en.wikipedia.org/wiki/Trusted_timestamping&quot;&gt;Trusted
+timestamps&lt;/a&gt; can be used to verify that some information
+(document/file/checksum/metadata) have not been changed since a
+specific time in the past.  This is useful to verify the integrity of
+the documents in the archive.&lt;/p&gt;
+
+&lt;p&gt;Then it occured to me, perhaps the trusted timestamps could be
+stored as dokument variants (ie dokumentobjekt referered to from
+dokumentbeskrivelse) with the filename set to the hash it is
+stamping?&lt;/p&gt;
+
+&lt;p&gt;Given a &quot;dokumentbeskrivelse&quot; with an associated &quot;dokumentobjekt&quot;,
+a new dokumentobjekt is associated with &quot;dokumentbeskrivelse&quot; with the
+same attributes as the stamped dokumentobjekt except these
+attributes:&lt;/p&gt;
+
+&lt;ul&gt;
+
+&lt;li&gt;format -&gt; &quot;RFC3161&quot;
+&lt;li&gt;mimeType -&gt; &quot;application/timestamp-reply&quot;
+&lt;li&gt;formatDetaljer -&gt; &quot;&amp;lt;source URL for timestamp service&amp;gt;&quot;
+&lt;li&gt;filenavn -&gt; &quot;&amp;lt;sjekksum&amp;gt;.tsr&quot;
+
+&lt;/ul&gt;
+
+&lt;p&gt;This assume a service following
+&lt;a href=&quot;https://tools.ietf.org/html/rfc3161&quot;&gt;IETF RFC 3161&lt;/a&gt; is
+used, which specifiy the given MIME type for replies and the .tsr file
+ending for the content of such trusted timestamp.  As far as I can
+tell from the Noark 5 specifications, it is OK to have several
+variants/renderings of a dokument attached to a given
+dokumentbeskrivelse objekt.  It might be stretching it a bit to make
+some of these variants represent crypto-signatures useful for
+verifying the document integrity instead of representing the dokument
+itself.&lt;/p&gt;
+
+&lt;p&gt;Using the source of the service in formatDetaljer allow several
+timestamping services to be used.  This is useful to spread the risk
+of key compromise over several organisations.  It would only be a
+problem to trust the timestamps if all of the organisations are
+compromised.&lt;/p&gt;
+
+&lt;p&gt;The following oneliner on Linux can be used to generate the tsr
+file.  $input is the path to the file to checksum, and $sha256 is the
+SHA-256 checksum of the file (ie the &quot;&lt;sjekksum&gt;.tsr&quot; value mentioned
+above).&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+openssl ts -query -data &quot;$inputfile&quot; -cert -sha256 -no_nonce \
+  | curl -s -H &quot;Content-Type: application/timestamp-query&quot; \
+      --data-binary &quot;@-&quot; http://zeitstempel.dfn.de &gt; $sha256.tsr
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;To verify the timestamp, you first need to download the public key
+of the trusted timestamp service, for example using this command:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+wget -O ca-cert.txt \
+  https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Note, the public key should be stored alongside the timestamps in
+the archive to make sure it is also available 100 years from now.  It
+is probably a good idea to standardise how and were to store such
+public keys, to make it easier to find for those trying to verify
+documents 100 or 1000 years from now. :)&lt;/p&gt;
+
+&lt;p&gt;The verification itself is a simple openssl command:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
+openssl ts -verify -data $inputfile -in $sha256.tsr \
+  -CAfile ca-cert.txt -text
+&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Is there any reason this approach would not work?  Is it somehow against
+the Noark 5 specification?&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
-               <link>http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
-                <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
-               <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
-to be a slight challenge.  Here is the recipe if I ever need to do it
-again.  It all started by me wanting to try the recipe to set up
-&lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
-hardened Android installation&lt;/a&gt; from the Tor project blog on a
-device I had access to.  It is a old mobile phone with a broken
-microphone The initial idea had been to just
-&lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
-CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
-until a few days ago.&lt;/p&gt;
-
-&lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
-loader (press volume down and power at the same time), (2) select
-&#39;fastboot&#39; before (3) connecting the device via USB to a Linux
-machine, (4) request the device identifier token by running &#39;fastboot
-oem get_identifier_token&#39;, (5) request the device unlocking key using
-the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
-site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
-
-&lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
-or newer, and the device I was working on had 2.00.0027.  This
-apparently can be easily fixed by downloading a Windows program and
-running it on your Windows machine, if you accept the terms Microsoft
-require you to accept to use Windows - which I do not.  So I had to
-come up with a different approach.  I got a lot of help from AndyCap
-on #nuug, and would not have been able to get this working without
-him.&lt;/p&gt;
-
-&lt;p&gt;First I needed to extract the hboot firmware from
-&lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
-windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
-For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
-project named unruu&lt;/a&gt; using libunshield.  The unshield tool did not
-recognise the file format, but unruu worked and extracted rom.zip,
-containing the new hboot firmware and a text file describing which
-devices it would work for.&lt;/p&gt;
-
-&lt;p&gt;Next, I needed to get the new firmware into the device.  For this I
-followed some instructions
-&lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
-from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
-machine with Debian testing:&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
-adb reboot-bootloader
-fastboot oem rebootRUU
-fastboot flash zip rom.zip
-fastboot flash zip rom.zip
-fastboot reboot
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;The flash command apparently need to be done twice to take effect,
-as the first is just preparations and the second one do the flashing.
-The adb command is just to get to the boot loader menu, so turning the
-device on while holding volume down and the power button should work
-too.&lt;/p&gt;
-
-&lt;p&gt;With the new hboot version in place I could start following the
-instructions on the HTC developer web site.  I got the device token
-like this:&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
-fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
-&lt;/pre&gt;
-
-&lt;p&gt;And once I got the unlock code via email, I could use it like
-this:&lt;/p&gt;
-
-&lt;p&gt;&lt;pre&gt;
-fastboot flash unlocktoken Unlock_code.bin
-&lt;/pre&gt;&lt;/p&gt;
-
-&lt;p&gt;And with that final step in place, the phone was unlocked and I
-could start stuffing the software of my own choosing into the device.
-So far I only inserted a replacement recovery image to wipe the phone
-before I start.  We will see what happen next.  Perhaps I should
-install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
+               <title>Når nynorskoversettelsen svikter til eksamen...</title>
+               <link>http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
+                <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
+               <description>&lt;p&gt;&lt;a href=&quot;http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html&quot;&gt;Aftenposten
+melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
+menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
+like.  Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
+på om den fri oversetterløsningen
+&lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
+jobb enn Utdanningsdirektoratet.  Det kan se slik ut.&lt;/p&gt;
+
+&lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
+
+&lt;blockquote&gt;
+&lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
+rolle og muligheter til å håndtere internasjonale utfordringer, som
+for eksempel flykningekrisen.&lt;/p&gt;
+
+&lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
+på temaet:&lt;/p&gt;
+&lt;ol&gt;
+&lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
+&lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
+&lt;/ol&gt;
+
+&lt;/blockquote&gt;
+
+&lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
+
+&lt;blockquote&gt;
+&lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
+andre aktørar og høve til å handtera internasjonale utfordringar, som
+til dømes *flykningekrisen.&lt;/p&gt;
+
+&lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
+temaet:&lt;/p&gt;
+
+&lt;ol&gt;
+&lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
+&lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
+&lt;/ol&gt;
+
+&lt;/blockquote&gt;
+
+&lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
+ekstra språksjekk.  Men ingen ord er forsvunnet, slik det var i
+oppgaven elevene fikk presentert på eksamen.  Jeg mistenker dog at
+&quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
+&quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
+det er kanskje flisespikking.  Det understreker vel bare at det alltid
+trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
-               <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</guid>
-                <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
-               <description>&lt;p&gt;For a while now, I have wanted to test
-&lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
-said to provide end to end encrypted communication and several of my
-friends and family are already using it.  As I by choice do not own a
-mobile phone, this proved to be harder than expected.  And I wanted to
-have the source of the client and know that it was the code used on my
-machine.  But yesterday I managed to get it working.  I used the
-Github source, compared it to the source in
-&lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
-Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
-patches to use the production Signal servers, started the app and
-asked for the hidden &quot;register without a smart phone&quot; form.  Here is
-the recipe how I did it.&lt;/p&gt;
-
-&lt;p&gt;First, I fetched the Signal desktop source from Github, using
-
-&lt;pre&gt;
-git clone https://github.com/WhisperSystems/Signal-Desktop.git
-&lt;/pre&gt;
-
-&lt;p&gt;Next, I patched the source to use the production servers, to be
-able to talk to other Signal users:&lt;/p&gt;
-
-&lt;pre&gt;
-cat &amp;lt;&amp;lt;EOF | patch -p0
-diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
---- ./js/background.js  2016-06-29 13:43:15.630344628 +0200
-+++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js    2016-06-29 14:06:29.530300934 +0200
-@@ -47,8 +47,8 @@
-         });
-     });
- 
--    var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
--    var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
-+    var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
-+    var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
-     var messageReceiver;
-     window.getSocketStatus = function() {
-         if (messageReceiver) {
-diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
---- ./js/expire.js      2016-06-29 13:43:15.630344628 +0200
-+++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
-@@ -1,6 +1,6 @@
- ;(function() {
-     &#39;use strict&#39;;
--    var BUILD_EXPIRATION = 0;
-+    var BUILD_EXPIRATION = 1474492690000;
- 
-     window.extension = window.extension || {};
- 
-EOF
-&lt;/pre&gt;
-
-&lt;p&gt;The first part is changing the servers, and the second is updating
-an expiration timestamp.  This timestamp need to be updated regularly.
-It is set 90 days in the future by the build process (Gruntfile.js).
-The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
-
-&lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
-script to launch Signal in Chromium.&lt;/p&gt;
-
-&lt;pre&gt;
-#!/bin/sh
-cd $(dirname $0)
-mkdir -p userdata
-exec chromium \
-  --proxy-server=&quot;socks://localhost:9050&quot; \
-  --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
-&lt;/pre&gt;
-
-&lt;p&gt; The script start the app and configure Chromium to use the Tor
-SOCKS5 proxy to make sure those controlling the Signal servers (today
-Amazon and Whisper Systems) as well as those listening on the lines
-will have a harder time location my laptop based on the Signal
-connections if they use source IP address.&lt;/p&gt;
-
-&lt;p&gt;When the script starts, one need to follow the instructions under
-&quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
-repository.  I right clicked on the Signal window to get up the
-Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
-&#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
-registration form.  Then I entered by land line phone number and
-pressed &#39;Call&#39;.  5 seconds later the phone rang and a robot voice
-repeated the verification code three times.  After entering the number
-into the verification code field in the form, I could start using
-Signal from my laptop.
-
-&lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
-whom and thus who know who to those controlling the central server,
-but such leakage is hard to avoid with a centrally controlled server
-setup.  It is something to keep in mind when using Signal - the
-content of your chats are harder to intercept, but the meta data
-exposing your contact network is available to people you do not know.
-So better than many options, but not great.  And sadly the usage is
-connected to my land line, thus allowing those controlling the server
-to associate it to my home and person.  I would prefer it if only
-those I knew could tell who I was on Signal.  There are options
-avoiding such information leakage, but most of my friends are not
-using them, so I am stuck with Signal for now.&lt;/p&gt;
+               <title>Epost inn som arkivformat i Riksarkivarens forskrift?</title>
+               <link>http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html</guid>
+                <pubDate>Thu, 27 Apr 2017 11:30:00 +0200</pubDate>
+               <description>&lt;p&gt;I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på
+sin forskrift.  Som en kan se er det ikke mye tid igjen før fristen
+som går ut på søndag.  Denne forskriften er det som lister opp hvilke
+formater det er greit å arkivere i
+&lt;a href=&quot;http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5&quot;&gt;Noark
+5-løsninger&lt;/a&gt; i Norge.&lt;/p&gt;
+
+&lt;p&gt;Jeg fant høringsdokumentene hos
+&lt;a href=&quot;https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing&quot;&gt;Norsk
+Arkivråd&lt;/a&gt; etter å ha blitt tipset på epostlisten til
+&lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;fri
+programvareprosjektet Nikita Noark5-Core&lt;/a&gt;, som lager et Noark 5
+Tjenestegresesnitt.  Jeg er involvert i Nikita-prosjektet og takket
+være min interesse for tjenestegrensesnittsprosjektet har jeg lest en
+god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget
+at standard epost ikke er på listen over godkjente formater som kan
+arkiveres.  Høringen med frist søndag er en glimrende mulighet til å
+forsøke å gjøre noe med det.  Jeg holder på med
+&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex&quot;&gt;egen
+høringsuttalelse&lt;/a&gt;, og lurer på om andre er interessert i å støtte
+forslaget om å tillate arkivering av epost som epost i arkivet.&lt;/p&gt;
+
+&lt;p&gt;Er du igang med å skrive egen høringsuttalelse allerede?  I så fall
+kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror
+ikke det trengs så mye.  Her et kort forslag til tekst:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;
+
+  &lt;p&gt;Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse
+  2016/9840 HELHJO), og tillater oss å sende inn noen innspill om
+  revisjon av Forskrift om utfyllende tekniske og arkivfaglige
+  bestemmelser om behandling av offentlige arkiver (Riksarkivarens
+  forskrift).&lt;/p&gt;
+
+  &lt;p&gt;Svært mye av vår kommuikasjon foregår i dag på e-post.  Vi
+  foreslår derfor at Internett-e-post, slik det er beskrevet i IETF
+  RFC 5322,
+  &lt;a href=&quot;https://tools.ietf.org/html/rfc5322&quot;&gt;https://tools.ietf.org/html/rfc5322&lt;/a&gt;. bør
+  inn som godkjent dokumentformat.  Vi foreslår at forskriftens
+  oversikt over godkjente dokumentformater ved innlevering i § 5-16
+  endres til å ta med Internett-e-post.&lt;/p&gt;
+
+&lt;/blockquote&gt;&lt;/p&gt;
+
+&lt;p&gt;Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan
+epost kan lagres i en Noark 5-struktur, og holder på å skrive et
+forslag om hvordan dette kan gjøres som vil bli sendt over til
+arkivverket så snart det er ferdig.  De som er interesserte kan
+&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md&quot;&gt;følge
+fremdriften på web&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
+  &lt;a href=&quot;https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml&quot;&gt;sendt
+  inn av foreningen NUUG&lt;/a&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>The new &quot;best&quot; multimedia player in Debian?</title>
-               <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
-                <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
-               <description>&lt;p&gt;When I set out a few weeks ago to figure out
-&lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
-multimedia player in Debian claimed to support most file formats /
-MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
-the various players claimed support for.  The range was from 55 to 130
-MIME types.  I suspect most media formats are supported by all
-players, but this is not really reflected in the MimeTypes values in
-their desktop files.  There are probably also some bogus MIME types
-listed, but it is hard to identify which one this is.&lt;/p&gt;
-
-&lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
-the players suggesting to add more MIME types to their desktop files,
-and decided to spend some time myself improving the situation for my
-favorite media player VLC.  The fixes for VLC entered Debian unstable
-yesterday. The complete list of MIME types can be seen on the
-&lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
-player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
-
-&lt;p&gt;The new &quot;best&quot; multimedia player in Debian?  It is VLC, followed by
-totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
-kmplayer.  I am sure some of the other players desktop files support
-several of the formats currently listed as working only with vlc,
-toten and parole.&lt;/p&gt;
-
-&lt;p&gt;A sad observation is that only 14 MIME types are listed as
-supported by all the tested multimedia players in Debian in their
-desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
-audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
-video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
-video/x-ms-asf, video/x-ms-wmv and video/x-msvideo.  Personally I find
-it sad that video/ogg and video/webm is not supported by all the media
-players in Debian.  As far as I can tell, all of them can handle both
-formats.&lt;/p&gt;
+               <title>Offentlig elektronisk postjournal blokkerer tilgang for utvalgte webklienter</title>
+               <link>http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html</guid>
+                <pubDate>Thu, 20 Apr 2017 13:00:00 +0200</pubDate>
+               <description>&lt;p&gt;Jeg oppdaget i dag at &lt;a href=&quot;https://www.oep.no/&quot;&gt;nettstedet som
+publiserer offentlige postjournaler fra statlige etater&lt;/a&gt;, OEP, har
+begynt å blokkerer enkelte typer webklienter fra å få tilgang.  Vet
+ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
+og curl.  For å teste selv, kjør følgende:&lt;/p&gt;
+
+&lt;blockquote&gt;&lt;pre&gt;
+% curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2&gt;&amp;1 |grep &#39;&lt; HTTP&#39;
+&lt; HTTP/1.1 404 Not Found
+% curl -v -s --header &#39;User-Agent:Opera/12.0&#39; https://www.oep.no/pub/report.xhtml?reportId=3 2&gt;&amp;1 |grep &#39;&lt; HTTP&#39;
+&lt; HTTP/1.1 200 OK
+%
+&lt;/pre&gt;&lt;/blockquote&gt;
+
+&lt;p&gt;Her kan en se at tjenesten gir «404 Not Found» for curl i
+standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
+versjon 12.0.  Offentlig elektronisk postjournal startet blokkeringen
+2017-03-02.&lt;/p&gt;
+
+&lt;p&gt;Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
+informasjon fra oep.no.  Kan blokkeringen være gjort for å hindre
+automatisert innsamling av informasjon fra OEP, slik Pressens
+Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
+hindrer innsyn i
+&lt;a href=&quot;http://presse.no/dette-mener-np/undergraver-offentlighetsloven/&quot;&gt;rapporten
+«Slik hindrer departementer innsyn» som ble publiserte i januar
+2017&lt;/a&gt;.  Det virker usannsynlig, da det jo er trivielt å bytte
+User-Agent til noe nytt.&lt;/p&gt;
+
+&lt;p&gt;Finnes det juridisk grunnlag for det offentlige å diskriminere
+webklienter slik det gjøres her?  Der tilgang gis eller ikke alt etter
+hva klienten sier at den heter?  Da OEP eies av DIFI og driftes av
+Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
+aktørene man kan be om innsyn i for å forstå hva som har skjedd.  Men
+&lt;a href=&quot;https://www.oep.no/search/result.html?period=dateRange&amp;fromDate=01.01.2016&amp;toDate=01.04.2017&amp;dateType=documentDate&amp;caseDescription=&amp;descType=both&amp;caseNumber=&amp;documentNumber=&amp;sender=basefarm&amp;senderType=both&amp;documentType=all&amp;legalAuthority=&amp;archiveCode=&amp;list2=196&amp;searchType=advanced&amp;Search=Search+in+records&quot;&gt;postjournalen
+til DIFI viser kun to dokumenter&lt;/a&gt; det siste året mellom DIFI og
+Basefarm.
+&lt;a href=&quot;https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo&quot;&gt;Mimes brønn neste&lt;/a&gt;,
+tenker jeg.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>A program should be able to open its own files on Linux</title>
-               <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
-                <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
-               <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
-decided to test its presentation tool when making the slides for a
-talk I was giving for NUUG on Japhar, a free Java virtual machine.  I
-wrote the first draft of the slides, saved the result and went to bed
-the day before I would give the talk.  The next day I took a plane to
-the location where the meeting should take place, and on the plane I
-started up koffice again to polish the talk a bit, only to discover
-that kpresenter refused to load its own data file.  I cursed a bit and
-started making the slides again from memory, to have something to
-present when I arrived.  I tested that the saved files could be
-loaded, and the day seemed to be rescued.  I continued to polish the
-slides until I suddenly discovered that the saved file could no longer
-be loaded into kpresenter.  In the end I had to rewrite the slides
-three times, condensing the content until the talk became shorter and
-shorter.  After the talk I was able to pinpoint the problem &amp;ndash;
-kpresenter wrote inline images in a way itself could not understand.
-Eventually that bug was fixed and kpresenter ended up being a great
-program to make slides.  The point I&#39;m trying to make is that we
-expect a program to be able to load its own data files, and it is
-embarrassing to its developers if it can&#39;t.&lt;/p&gt;
-
-&lt;p&gt;Did you ever experience a program failing to load its own data
-files from the desktop file browser?  It is not a uncommon problem.  A
-while back I discovered that the screencast recorder
-gtk-recordmydesktop would save an Ogg Theora video file the KDE file
-browser would refuse to open.  No video player claimed to understand
-such file.  I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
-returning the application/ogg MIME type, which no video player I had
-installed listed as a MIME type they would understand.  I asked for
-&lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
-behavour&lt;/a&gt; and use the MIME type video/ogg instead.  I also asked
-several video players to add video/ogg to their desktop files, to give
-the file browser an idea what to do about Ogg Theora files.  After a
-while, the desktop file browsers in Debian started to handle the
-output from gtk-recordmydesktop properly.&lt;/p&gt;
-
-&lt;p&gt;But history repeats itself.  A few days ago I tested the music
-system Rosegarden again, and I discovered that the KDE and xfce file
-browsers did not know what to do with the Rosegarden project files
-(*.rg).  I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
-rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
-included in the next upload.  To increase the chance of me remembering
-how to fix the problem next time some program fail to load its files
-from the file browser, here are some notes on how to fix it.&lt;/p&gt;
-
-&lt;p&gt;The file browsers in Debian in general operates on MIME types.
-There are two sources for the MIME type of a given file.  The output from
-&lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
-shared MIME type registry (under /usr/share/mime/).  The file MIME
-type is mapped to programs supporting the MIME type, and this
-information is collected from
-&lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
-desktop files&lt;/a&gt; available in /usr/share/applications/.  If there is
-one desktop file claiming support for the MIME type of the file, it is
-activated when asking to open a given file.  If there are more, one
-can normally select which one to use by right-clicking on the file and
-selecting the wanted one using &#39;Open with&#39; or similar.  In general
-this work well.  But it depend on each program picking a good MIME
-type (preferably
-&lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
-MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
-registry recognizing the file and the desktop file to list the MIME
-type in its list of supported MIME types.&lt;/p&gt;
-
-&lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
-&lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
-Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
+               <title>Free software archive system Nikita now able to store documents</title>
+               <link>http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html</guid>
+                <pubDate>Sun, 19 Mar 2017 08:00:00 +0100</pubDate>
+               <description>&lt;p&gt;The &lt;a href=&quot;https://github.com/hiOA-ABI/nikita-noark5-core&quot;&gt;Nikita
+Noark 5 core project&lt;/a&gt; is implementing the Norwegian standard for
+keeping an electronic archive of government documents.
+&lt;a href=&quot;http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version&quot;&gt;The
+Noark 5 standard&lt;/a&gt; document the requirement for data systems used by
+the archives in the Norwegian government, and the Noark 5 web interface
+specification document a REST web service for storing, searching and
+retrieving documents and metadata in such archive.  I&#39;ve been involved
+in the project since a few weeks before Christmas, when the Norwegian
+Unix User Group
+&lt;a href=&quot;https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml&quot;&gt;announced
+it supported the project&lt;/a&gt;.  I believe this is an important project,
+and hope it can make it possible for the government archives in the
+future to use free software to keep the archives we citizens depend
+on.  But as I do not hold such archive myself, personally my first use
+case is to store and analyse public mail journal metadata published
+from the government.  I find it useful to have a clear use case in
+mind when developing, to make sure the system scratches one of my
+itches.&lt;/p&gt;
+
+&lt;p&gt;If you would like to help make sure there is a free software
+alternatives for the archives, please join our IRC channel
+(&lt;a href=&quot;irc://irc.freenode.net/%23nikita&quot;&quot;&gt;#nikita on
+irc.freenode.net&lt;/a&gt;) and
+&lt;a href=&quot;https://lists.nuug.no/mailman/listinfo/nikita-noark&quot;&gt;the
+project mailing list&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;When I got involved, the web service could store metadata about
+documents.  But a few weeks ago, a new milestone was reached when it
+became possible to store full text documents too.  Yesterday, I
+completed an implementation of a command line tool
+&lt;tt&gt;archive-pdf&lt;/tt&gt; to upload a PDF file to the archive using this
+API.  The tool is very simple at the moment, and find existing
+&lt;a href=&quot;https://en.wikipedia.org/wiki/Fonds&quot;&gt;fonds&lt;/a&gt;, series and
+files while asking the user to select which one to use if more than
+one exist.  Once a file is identified, the PDF is associated with the
+file and uploaded, using the title extracted from the PDF itself.  The
+process is fairly similar to visiting the archive, opening a cabinet,
+locating a file and storing a piece of paper in the archive.  Here is
+a test run directly after populating the database with test data using
+our API tester:&lt;/p&gt;

 
 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 
 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;

-&amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
-&amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
-  &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
-    &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
-    &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
-    &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
-  &amp;lt;/mime-type&amp;gt;
-&amp;lt;/mime-info&amp;gt;
+~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
+using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
+using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
+
+ 0 - Title of the test case file created 2017-03-18T23:49:32.103446
+ 1 - Title of the test file created 2017-03-18T23:49:32.103446
+Select which mappe you want (or search term): 0
+Uploading mangelmelding/mangler.pdf
+  PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
+  File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
+~/src//noark5-tester$

 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 
 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 

-&lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
-(it is a gzipped XML file).  Note, it is much better to use an
-official MIME type registered with IANA than it is to make up ones own
-unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
-
-&lt;p&gt;The desktop file of the rosegarden program failed to list
-audio/x-rosegarden in its list of supported MIME types, causing the
-file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
+&lt;p&gt;You can see here how the fonds (arkiv) and serie (arkivdel) only had
+one option, while the user need to choose which file (mappe) to use
+among the two created by the API tester.  The &lt;tt&gt;archive-pdf&lt;/tt&gt;
+tool can be found in the git repository for the API tester.&lt;/p&gt;
+
+&lt;p&gt;In the project, I have been mostly working on
+&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester&quot;&gt;the API
+tester&lt;/a&gt; so far, while getting to know the code base.  The API
+tester currently use
+&lt;a href=&quot;https://en.wikipedia.org/wiki/HATEOAS&quot;&gt;the HATEOAS links&lt;/a&gt;
+to traverse the entire exposed service API and verify that the exposed
+operations and objects match the specification, as well as trying to
+create objects holding metadata and uploading a simple XML file to
+store.  The tester has proved very useful for finding flaws in our
+implementation, as well as flaws in the reference site and the
+specification.&lt;/p&gt;
+
+&lt;p&gt;The test document I uploaded is a summary of all the specification
+defects we have collected so far while implementing the web service.
+There are several unclear and conflicting parts of the specification,
+and we have
+&lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding&quot;&gt;started
+writing down&lt;/a&gt; the questions we get from implementing it.  We use a
+format inspired by how &lt;a href=&quot;http://www.opengroup.org/austin/&quot;&gt;The
+Austin Group&lt;/a&gt; collect defect reports for the POSIX standard with
+&lt;a href=&quot;http://www.opengroup.org/austin/mantis.html&quot;&gt;their
+instructions for the MANTIS defect tracker system&lt;/a&gt;, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a &lt;a href=&quot;https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/2017-03-15-mangel-prosess.md&quot;&gt;request for a procedure for submitting defect reports&lt;/a&gt; :).
+
+&lt;p&gt;The Nikita project is implemented using Java and Spring, and is
+fairly easy to get up and running using Docker containers for those
+that want to test the current code base.  The API tester is
+implemented in Python.&lt;/p&gt;
+</description>
+       </item>
+       
+       <item>
+               <title>Detecting NFS hangs on Linux without hanging yourself...</title>
+               <link>http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
+                <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
+               <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
+computers at the time, I often needed a way to detect if the machine
+was experiencing NFS hang.  If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
+file or directory affected by the hang, the process (and possibly the
+shell) will hang too.  So you want to be able to detect this without
+risking the detection process getting stuck too.  It has not been
+obvious how to do this.  When the hang has lasted a while, it is
+possible to find messages like these in dmesg:&lt;/p&gt;
+
+&lt;p&gt;&lt;blockquote&gt;
+nfs: server nfsserver not responding, still trying
+&lt;br&gt;nfs: server nfsserver OK
+&lt;/blockquote&gt;&lt;/p&gt;
+  
+&lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
+be sure looking in dmesg is going to work.  If there are lots of other
+messages in dmesg the lines might have rotated out of site before they
+are noticed.&lt;/p&gt;
+
+&lt;p&gt;While reading through the nfs client implementation in linux kernel
+code, I came across some statistics that seem to give a way to detect
+it.  The om_timeouts sunrpc value in the kernel will increase every
+time the above log entry is inserted into dmesg.  And after digging a
+bit further, I discovered that this value show up in
+/proc/self/mountstats on Linux.&lt;/p&gt;
+
+&lt;p&gt;The mountstats content seem to be shared between files using the
+same file system context, so it is enough to check one of the
+mountstats files to get the state of the mount point for the machine.
+I assume this will not show lazy umounted NFS points, nor NFS mount
+points in a different process context (ie with a different filesystem
+view), but that does not worry me.&lt;/p&gt;
+
+&lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;

 
 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
 
 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;

-% grep Mime /usr/share/applications/rosegarden.desktop
-MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
-X-KDE-NativeMimeType=audio/x-rosegarden-composition
-%
+[...]
+device /dev/mapper/Debian-var mounted on /var with fstype ext3
+device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
+        opts:   rw,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.240.3.145,mountvers=3,mountport=4048,mountproto=udp,local_lock=all
+        age:    7863311
+        caps:   caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
+        sec:    flavor=1,pseudoflavor=1
+        events: 61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0 
+        bytes:  166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809 
+        RPC iostats version: 1.0  p/v: 100003/3 (nfs)
+        xprt:   tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
+        per-op statistics
+                NULL: 0 0 0 0 0 0 0 0
+             GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
+             SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
+              LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
+              ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
+            READLINK: 125 125 0 20472 18620 0 1112 1118
+                READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
+               WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
+              CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
+               MKDIR: 3680 3680 0 773980 993920 26 23990 24245
+             SYMLINK: 903 903 0 233428 245488 6 5865 5917
+               MKNOD: 80 80 0 20148 21760 0 299 304
+              REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
+               RMDIR: 3367 3367 0 645112 484848 22 5782 6002
+              RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
+                LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
+             READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
+         READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
+              FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
+              FSINFO: 2 2 0 232 328 0 1 1
+            PATHCONF: 1 1 0 116 140 0 0 0
+              COMMIT: 0 0 0 0 0 0 0 0
+
+device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
+[...]

 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 
 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
 

-&lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
-MimeType= line.&lt;/p&gt;
-
-&lt;p&gt;If you run into a file which fail to open the correct program when
-selected from the file browser, please check out the output from
-&lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
-MIME type is registered somewhere under /usr/share/mime/ and check
-that some desktop file under /usr/share/applications/ is claiming
-support for this MIME type.  If not, please report a bug to have it
-fixed. :)&lt;/p&gt;
+&lt;p&gt;The key number to look at is the third number in the per-op list.
+It is the number of NFS timeouts experiences per file system
+operation.  Here 22 write timeouts and 5 access timeouts.  If these
+numbers are increasing, I believe the machine is experiencing NFS
+hang.  Unfortunately the timeout value do not start to increase right
+away.  The NFS operations need to time out first, and this can take a
+while.  The exact timeout value depend on the setup.  For example the
+defaults for TCP and UDP mount points are quite different, and the
+timeout value is affected by the soft, hard, timeo and retrans NFS
+mount options.&lt;/p&gt;
+
+&lt;p&gt;The only way I have been able to get working on Debian and RedHat
+Enterprise Linux for getting the timeout count is to peek in /proc/.
+But according to
+&lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
+10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
+command can be used to get these timeout values.  But this do not work
+on Linux, as far as I can tell.  I
+&lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
+but have not seen any replies yet.&lt;/p&gt;
+
+&lt;p&gt;Is there a better way to figure out if a Linux NFS client is
+experiencing NFS hangs?  Is there a way to detect which processes are
+affected?  Is there a way to get the NFS mount going quickly once the
+network problem causing the NFS hang has been cleared?  I would very
+much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
+</description>
+       </item>
+       
+       <item>
+               <title>How does it feel to be wiretapped, when you should be doing the wiretapping...</title>
+               <link>http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_does_it_feel_to_be_wiretapped__when_you_should_be_doing_the_wiretapping___.html</guid>
+                <pubDate>Wed, 8 Mar 2017 11:50:00 +0100</pubDate>
+               <description>&lt;p&gt;So the new president in the United States of America claim to be
+surprised to discover that he was wiretapped during the election
+before he was elected president.  He even claim this must be illegal.
+Well, doh, if it is one thing the confirmations from Snowden
+documented, it is that the entire population in USA is wiretapped, one
+way or another.  Of course the president candidates were wiretapped,
+alongside the senators, judges and the rest of the people in USA.&lt;/p&gt;
+
+&lt;p&gt;Next, the Federal Bureau of Investigation ask the Department of
+Justice to go public rejecting the claims that Donald Trump was
+wiretapped illegally.  I fail to see the relevance, given that I am
+sure the surveillance industry in USA believe they have all the legal
+backing they need to conduct mass surveillance on the entire
+world.&lt;/p&gt;
+
+&lt;p&gt;There is even the director of the FBI stating that he never saw an
+order requesting wiretapping of Donald Trump.  That is not very
+surprising, given how the FISA court work, with all its activity being
+secret.  Perhaps he only heard about it?&lt;/p&gt;
+
+&lt;p&gt;What I find most sad in this story is how Norwegian journalists
+present it.  In a news reports the other day in the radio from the
+Norwegian National broadcasting Company (NRK), I heard the journalist
+claim that &#39;the FBI denies any wiretapping&#39;, while the reality is that
+&#39;the FBI denies any illegal wiretapping&#39;.  There is a fundamental and
+important difference, and it make me sad that the journalists are
+unable to grasp it.&lt;/p&gt;
+
+&lt;p&gt;&lt;strong&gt;Update 2017-03-13:&lt;/strong&gt; Look like
+&lt;a href=&quot;https://theintercept.com/2017/03/13/rand-paul-is-right-nsa-routinely-monitors-americans-communications-without-warrants/&quot;&gt;The
+Intercept report that US Senator Rand Paul confirm what I state above&lt;/a&gt;.&lt;/p&gt;

 </description>
        </item>
        
        <item>
 </description>
        </item>
        
        <item>

-               <title>Tor - from its creators mouth 11 years ago</title>
-               <link>http://people.skolelinux.org/pere/blog/Tor___from_its_creators_mouth_11_years_ago.html</link>
-               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Tor___from_its_creators_mouth_11_years_ago.html</guid>
-                <pubDate>Sat, 28 May 2016 14:20:00 +0200</pubDate>
-               <description>&lt;p&gt;A little more than 11 years ago, one of the creators of Tor, and
-the current President of &lt;a href=&quot;https://www.torproject.org/&quot;&gt;the Tor
-project&lt;/a&gt;, Roger Dingledine, gave a talk for the members of the
-&lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User group&lt;/a&gt; (NUUG).  A
-video of the talk was recorded, and today, thanks to the great help
-from David Noble, I finally was able to publish the video of the talk
-on Frikanalen, the Norwegian open channel TV station where NUUG
-currently publishes its talks.  You can
-&lt;a href=&quot;http://frikanalen.no/se&quot;&gt;watch the live stream using a web
-browser&lt;/a&gt; with WebM support, or check out the recording on the video
-on demand page for the talk
-&quot;&lt;a href=&quot;http://beta.frikanalen.no/video/625599&quot;&gt;Tor: Anonymous
-communication for the US Department of Defence...and you.&lt;/a&gt;&quot;.&lt;/p&gt;
-
-&lt;p&gt;Here is the video included for those of you using browsers with
-HTML video and Ogg Theora support:&lt;/p&gt;
-
-&lt;p&gt;&lt;video width=&quot;70%&quot; poster=&quot;http://simula.gunkies.org/media/625599/large_thumb/20050421-tor-frikanalen.jpg&quot; controls&gt;
-  &lt;source src=&quot;http://simula.gunkies.org/media/625599/theora/20050421-tor-frikanalen.ogv&quot; type=&quot;video/ogg&quot;/&gt;
-&lt;/video&gt;&lt;/p&gt;
-
-&lt;p&gt;I guess the gist of the talk can be summarised quite simply: If you
-want to help the military in USA (and everyone else), use Tor. :)&lt;/p&gt;
+               <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
+               <link>http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
+               <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</guid>
+                <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
+               <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
+Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
+Administrator&#39;s Handbook&lt;/a&gt;.  Now, thanks to the tireless effort of
+Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
+we are working on the proof reading to ensure consistent language and
+use of correct computer science terms.  The plan is to make the book
+available on paper, as well as in electronic form.  For that to
+happen, the proof reading must be completed and all the figures need
+to be translated.  If you want to help out, get in touch.&lt;/p&gt;
+
+&lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
+
+fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
+pages) of the book created every morning is available for
+proofreading.  If you find any errors, please
+&lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
+Weblate and correct the error&lt;/a&gt;.  The
+&lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
+of the translation including figures&lt;/a&gt; is a useful source for those
+provide Norwegian bokmål screen shots and figures.&lt;/p&gt;

 </description>
        </item>
        
 </description>
        </item>