blog/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2           "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" dir="ltr">
   4   <head>
   5     <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
   6     <title>Petter Reinholdtsen</title>
   7     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css" />
   8     <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/vim.css" />
   9     <link rel="alternate" title="RSS Feed" href="http://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml" />
  10   </head>
  11   <body>
  12     <div class="title">
  13  <h1>
  14      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16  </h1>
  17
  18 </div>
  19
  20
  21
  22     <div class="entry">
  23       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html">Norwegian Bokmål edition of Debian Administrator's Handbook is now available</a></div>
  24       <div class="date">25th July 2017</div>
  25       <div class="body"><p align="center"><img align="center" src="http://people.skolelinux.org/pere/blog/images/2017-07-25-debian-handbook-nb-testprint.png"/></p>
  26
  27 <p>I finally received a copy of the Norwegian Bokmål edition of
  28 "<a href="https://debian-handbook.info/">The Debian Administrator's
  29 Handbook</a>".  This test copy arrived in the mail a few days ago, and
  30 I am very happy to hold the result in my hand.   We spent around one and a half year translating it. This paperbook edition
  31 <a href="https://debian-handbook.info/get/#norwegian">is available
  32 from lulu.com</a>.  If you buy it quickly, you save 25% on the list
  33 price.  The book is also available for download in electronic form as
  34 PDF, EPUB and Mobipocket, as can be
  35 <a href="https://debian-handbook.info/browse/nb-NO/stable/">read online
  36 as a web page</a>.</p>
  37
  38 <p>This is the second book I publish (the first was the book
  39 "<a href="http://free-culture.cc/">Free Culture</a>" by Lawrence Lessig
  40 in
  41 <a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">English</a>,
  42 <a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">French</a>
  43 and
  44 <a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Norwegian
  45 Bokmål</a>), and I am very excited to finally wrap up this
  46 project.  I hope
  47 "<a href="http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-23262290.html">Håndbok
  48 for Debian-administratoren</a>" will be well received.</p>
  49 </div>
  50       <div class="tags">
  51
  52
  53         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
  54
  55
  56       </div>
  57     </div>
  58     <div class="padding"></div>
  59
  60     <div class="entry">
  61       <div class="title"><a href="http://people.skolelinux.org/pere/blog/_Rapporten_ser_ikke_p__informasjonssikkerhet_knyttet_til_personlig_integritet_.html">«Rapporten ser ikke på informasjonssikkerhet knyttet til personlig integritet»</a></div>
  62       <div class="date">27th June 2017</div>
  63       <div class="body"><p>Jeg kom over teksten
  64 «<a href="https://freedom-to-tinker.com/2017/06/21/killing-car-privacy-by-federal-mandate/">Killing
  65 car privacy by federal mandate</a>» av Leonid Reyzin på Freedom to
  66 Tinker i dag, og det gleder meg å se en god gjennomgang om hvorfor det
  67 er et urimelig inngrep i privatsfæren å la alle biler kringkaste sin
  68 posisjon og bevegelse via radio.  Det omtalte forslaget basert på
  69 Dedicated Short Range Communication (DSRC) kalles Basic Safety Message
  70 (BSM) i USA og Cooperative Awareness Message (CAM) i Europa, og det
  71 norske Vegvesenet er en av de som ser ut til å kunne tenke seg å
  72 pålegge alle biler å fjerne nok en bit av innbyggernes privatsfære.
  73 Anbefaler alle å lese det som står der.
  74
  75 <p>Mens jeg tittet litt på DSRC på biler i Norge kom jeg over et sitat
  76 jeg synes er illustrativt for hvordan det offentlige Norge håndterer
  77 problemstillinger rundt innbyggernes privatsfære i SINTEF-rapporten
  78 «<a href="https://www.sintef.no/publikasjoner/publikasjon/Download/?pubid=SINTEF+A23933">Informasjonssikkerhet
  79 i AutoPASS-brikker</a>» av Trond Foss:</p>
  80
  81 <p><blockquote>
  82 «Rapporten ser ikke på informasjonssikkerhet knyttet til personlig
  83   integritet.»
  84 </blockquote></p>
  85
  86 <p>Så enkelt kan det tydeligvis gjøres når en vurderer
  87 informasjonssikkerheten.  Det holder vel at folkene på toppen kan si
  88 at «Personvernet er ivaretatt», som jo er den populære intetsigende
  89 frasen som gjør at mange tror enkeltindividers integritet tas vare på.
  90 Sitatet fikk meg til å undres på hvor ofte samme tilnærming, å bare se
  91 bort fra behovet for personlig itegritet, blir valgt når en velger å
  92 legge til rette for nok et inngrep i privatsfæren til personer i
  93 Norge.  Det er jo sjelden det får reaksjoner.  Historien om
  94 reaksjonene på Helse Sør-Østs tjenesteutsetting er jo sørgelig nok et
  95 unntak og toppen av isfjellet, desverre.  Tror jeg fortsatt takker nei
  96 til både AutoPASS og holder meg så langt unna det norske helsevesenet
  97 som jeg kan, inntil de har demonstrert og dokumentert at de verdsetter
  98 individets privatsfære og personlige integritet høyere enn kortsiktig
  99 gevist og samfunnsnytte.</p>
 100 </div>
 101       <div class="tags">
 102
 103
 104         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
 105
 106
 107       </div>
 108     </div>
 109     <div class="padding"></div>
 110
 111     <div class="entry">
 112       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Updated_sales_number_for_my_Free_Culture_paper_editions.html">Updated sales number for my Free Culture paper editions</a></div>
 113       <div class="date">12th June 2017</div>
 114       <div class="body"><p>It is pleasing to see that the work we put down in publishing new
 115 editions of the classic <a href="http://www.free-culture.cc/">Free
 116 Culture book</a> by the founder of the Creative Commons movement,
 117 Lawrence Lessig, is still being appreciated.  I had a look at the
 118 latest sales numbers for the paper edition today.  Not too impressive,
 119 but happy to see some buyers still exist.  All the revenue from the
 120 books is sent to the <a href="https://creativecommons.org/">Creative
 121 Commons Corporation</a>, and they receive the largest cut if you buy
 122 directly from Lulu.  Most books are sold via Amazon, with Ingram
 123 second and only a small fraction directly from Lulu.  The ebook
 124 edition is available for free from
 125 <a href="https://github.com/petterreinholdtsen/free-culture-lessig">Github</a>.</p>
 126
 127 <table border="0">
 128 <tr><th rowspan="2" valign="bottom">Title / language</th><th colspan="3">Quantity</th></tr>
 129 <tr><th>2016 jan-jun</th><th>2016 jul-dec</th><th>2017 jan-may</th></tr>
 130
 131 <tr>
 132   <td><a href="http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html">Culture Libre / French</a></td>
 133   <td align="right">3</td>
 134   <td align="right">6</td>
 135   <td align="right">15</td>
 136 </tr>
 137
 138 <tr>
 139   <td><a href="http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">Fri kultur / Norwegian</a></td>
 140   <td align="right">7</td>
 141   <td align="right">1</td>
 142   <td align="right">0</td>
 143 </tr>
 144
 145 <tr>
 146   <td><a href="http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html">Free Culture / English</a></td>
 147   <td align="right">14</td>
 148   <td align="right">27</td>
 149   <td align="right">16</td>
 150 </tr>
 151
 152 <tr>
 153   <td>Total</td>
 154   <td align="right">24</td>
 155   <td align="right">34</td>
 156   <td align="right">31</td>
 157 </tr>
 158
 159 </table>
 160
 161 <p>A bit sad to see the low sales number on the Norwegian edition, and
 162 a bit surprising the English edition still selling so well.</p>
 163
 164 <p>If you would like to translate and publish the book in your native
 165 language, I would be happy to help make it happen.  Please get in
 166 touch.</p>
 167 </div>
 168       <div class="tags">
 169
 170
 171         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>.
 172
 173
 174       </div>
 175     </div>
 176     <div class="padding"></div>
 177
 178     <div class="entry">
 179       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Release_0_1_1_of_free_software_archive_system_Nikita_announced.html">Release 0.1.1 of free software archive system Nikita announced</a></div>
 180       <div class="date">10th June 2017</div>
 181       <div class="body"><p>I am very happy to report that the
 182 <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita Noark 5
 183 core project</a> tagged its second release today.  The free software
 184 solution is an implementation of the Norwegian archive standard Noark
 185 5 used by government offices in Norway.  These were the changes in
 186 version 0.1.1 since version 0.1.0 (from NEWS.md):
 187
 188 <ul>
 189
 190  <li>Continued work on the angularjs GUI, including document upload.</li>
 191  <li>Implemented correspondencepartPerson, correspondencepartUnit and
 192    correspondencepartInternal</li>
 193  <li>Applied for coverity coverage and started submitting code on
 194    regualr basis.</li>
 195  <li>Started fixing bugs reported by coverity</li>
 196  <li>Corrected and completed HATEOAS links to make sure entire API is
 197    available via URLs in _links.</li>
 198  <li>Corrected all relation URLs to use trailing slash.</li>
 199  <li>Add initial support for storing data in ElasticSearch.</li>
 200  <li>Now able to receive and store uploaded files in the archive.</li>
 201  <li>Changed JSON output for object lists to have relations in _links.</li>
 202  <li>Improve JSON output for empty object lists.</li>
 203  <li>Now uses correct MIME type application/vnd.noark5-v4+json.</li>
 204  <li>Added support for docker container images.</li>
 205  <li>Added simple API browser implemented in JavaScript/Angular.</li>
 206  <li>Started on archive client implemented in JavaScript/Angular.</li>
 207  <li>Started on prototype to show the public mail journal.</li>
 208  <li>Improved performance by disabling Sprint FileWatcher.</li>
 209  <li>Added support for 'arkivskaper', 'saksmappe' and 'journalpost'.</li>
 210  <li>Added support for some metadata codelists.</li>
 211  <li>Added support for Cross-origin resource sharing (CORS).</li>
 212  <li>Changed login method from Basic Auth to JSON Web Token (RFC 7519)
 213    style.</li>
 214  <li>Added support for GET-ing ny-* URLs.</li>
 215  <li>Added support for modifying entities using PUT and eTag.</li>
 216  <li>Added support for returning XML output on request.</li>
 217  <li>Removed support for English field and class names, limiting ourself
 218    to the official names.</li>
 219  <li>...</li>
 220
 221 </ul>
 222
 223 <p>If this sound interesting to you, please contact us on IRC (#nikita
 224 on irc.freenode.net) or email
 225 (<a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">nikita-noark
 226 mailing list).</p>
 227 </div>
 228       <div class="tags">
 229
 230
 231         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 232
 233
 234       </div>
 235     </div>
 236     <div class="padding"></div>
 237
 238     <div class="entry">
 239       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Idea_for_storing_trusted_timestamps_in_a_Noark_5_archive.html">Idea for storing trusted timestamps in a Noark 5 archive</a></div>
 240       <div class="date"> 7th June 2017</div>
 241       <div class="body"><p><em>This is a copy of
 242 <a href="https://lists.nuug.no/pipermail/nikita-noark/2017-June/000297.html">an
 243 email I posted to the nikita-noark mailing list</a>.  Please follow up
 244 there if you would like to discuss this topic.  The background is that
 245 we are making a free software archive system based on the Norwegian
 246 <a href="https://www.arkivverket.no/forvaltning-og-utvikling/regelverk-og-standarder/noark-standarden">Noark
 247 5 standard</a> for government archives.</em></p>
 248
 249 <p>I've been wondering a bit lately how trusted timestamps could be
 250 stored in Noark 5.
 251 <a href="https://en.wikipedia.org/wiki/Trusted_timestamping">Trusted
 252 timestamps</a> can be used to verify that some information
 253 (document/file/checksum/metadata) have not been changed since a
 254 specific time in the past.  This is useful to verify the integrity of
 255 the documents in the archive.</p>
 256
 257 <p>Then it occured to me, perhaps the trusted timestamps could be
 258 stored as dokument variants (ie dokumentobjekt referered to from
 259 dokumentbeskrivelse) with the filename set to the hash it is
 260 stamping?</p>
 261
 262 <p>Given a "dokumentbeskrivelse" with an associated "dokumentobjekt",
 263 a new dokumentobjekt is associated with "dokumentbeskrivelse" with the
 264 same attributes as the stamped dokumentobjekt except these
 265 attributes:</p>
 266
 267 <ul>
 268
 269 <li>format -> "RFC3161"
 270 <li>mimeType -> "application/timestamp-reply"
 271 <li>formatDetaljer -> "&lt;source URL for timestamp service&gt;"
 272 <li>filenavn -> "&lt;sjekksum&gt;.tsr"
 273
 274 </ul>
 275
 276 <p>This assume a service following
 277 <a href="https://tools.ietf.org/html/rfc3161">IETF RFC 3161</a> is
 278 used, which specifiy the given MIME type for replies and the .tsr file
 279 ending for the content of such trusted timestamp.  As far as I can
 280 tell from the Noark 5 specifications, it is OK to have several
 281 variants/renderings of a dokument attached to a given
 282 dokumentbeskrivelse objekt.  It might be stretching it a bit to make
 283 some of these variants represent crypto-signatures useful for
 284 verifying the document integrity instead of representing the dokument
 285 itself.</p>
 286
 287 <p>Using the source of the service in formatDetaljer allow several
 288 timestamping services to be used.  This is useful to spread the risk
 289 of key compromise over several organisations.  It would only be a
 290 problem to trust the timestamps if all of the organisations are
 291 compromised.</p>
 292
 293 <p>The following oneliner on Linux can be used to generate the tsr
 294 file.  $input is the path to the file to checksum, and $sha256 is the
 295 SHA-256 checksum of the file (ie the "<sjekksum>.tsr" value mentioned
 296 above).</p>
 297
 298 <p><blockquote><pre>
 299 openssl ts -query -data "$inputfile" -cert -sha256 -no_nonce \
 300   | curl -s -H "Content-Type: application/timestamp-query" \
 301       --data-binary "@-" http://zeitstempel.dfn.de > $sha256.tsr
 302 </pre></blockquote></p>
 303
 304 <p>To verify the timestamp, you first need to download the public key
 305 of the trusted timestamp service, for example using this command:</p>
 306
 307 <p><blockquote><pre>
 308 wget -O ca-cert.txt \
 309   https://pki.pca.dfn.de/global-services-ca/pub/cacert/chain.txt
 310 </pre></blockquote></p>
 311
 312 <p>Note, the public key should be stored alongside the timestamps in
 313 the archive to make sure it is also available 100 years from now.  It
 314 is probably a good idea to standardise how and were to store such
 315 public keys, to make it easier to find for those trying to verify
 316 documents 100 or 1000 years from now. :)</p>
 317
 318 <p>The verification itself is a simple openssl command:</p>
 319
 320 <p><blockquote><pre>
 321 openssl ts -verify -data $inputfile -in $sha256.tsr \
 322   -CAfile ca-cert.txt -text
 323 </pre></blockquote></p>
 324
 325 <p>Is there any reason this approach would not work?  Is it somehow against
 326 the Noark 5 specification?</p>
 327 </div>
 328       <div class="tags">
 329
 330
 331         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 332
 333
 334       </div>
 335     </div>
 336     <div class="padding"></div>
 337
 338     <div class="entry">
 339       <div class="title"><a href="http://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html">Når nynorskoversettelsen svikter til eksamen...</a></div>
 340       <div class="date"> 3rd June 2017</div>
 341       <div class="body"><p><a href="http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html">Aftenposten
 342 melder i dag</a> om feil i eksamensoppgavene for eksamen i politikk og
 343 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
 344 like.  Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
 345 på om den fri oversetterløsningen
 346 <a href="https://www.apertium.org/">Apertium</a> ville gjort en bedre
 347 jobb enn Utdanningsdirektoratet.  Det kan se slik ut.</p>
 348
 349 <p>Her er bokmålsoppgaven fra eksamenen:</p>
 350
 351 <blockquote>
 352 <p>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
 353 rolle og muligheter til å håndtere internasjonale utfordringer, som
 354 for eksempel flykningekrisen.</p>
 355
 356 <p>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
 357 på temaet:</p>
 358 <ol>
 359 <li>Flykningeregnskapet 2016, UNHCR og IDMC
 360 <li>«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
 361 </ol>
 362
 363 </blockquote>
 364
 365 <p>Dette oversetter Apertium slik:</p>
 366
 367 <blockquote>
 368 <p>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
 369 andre aktørar og høve til å handtera internasjonale utfordringar, som
 370 til dømes *flykningekrisen.</p>
 371
 372 <p>Vedleggja er døme på tekster som kan gje relevante perspektiv på
 373 temaet:</p>
 374
 375 <ol>
 376 <li>*Flykningeregnskapet 2016, *UNHCR og *IDMC</li>
 377 <li>«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015</li>
 378 </ol>
 379
 380 </blockquote>
 381
 382 <p>Ord som ikke ble forstått er markert med stjerne (*), og trenger
 383 ekstra språksjekk.  Men ingen ord er forsvunnet, slik det var i
 384 oppgaven elevene fikk presentert på eksamen.  Jeg mistenker dog at
 385 "andre aktørers rolle og muligheter til ..." burde vært oversatt til
 386 "rolla til andre aktørar og deira høve til ..." eller noe slikt, men
 387 det er kanskje flisespikking.  Det understreker vel bare at det alltid
 388 trengs korrekturlesning etter automatisk oversettelse.</p>
 389 </div>
 390       <div class="tags">
 391
 392
 393         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll</a>.
 394
 395
 396       </div>
 397     </div>
 398     <div class="padding"></div>
 399
 400     <div class="entry">
 401       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Epost_inn_som_arkivformat_i_Riksarkivarens_forskrift_.html">Epost inn som arkivformat i Riksarkivarens forskrift?</a></div>
 402       <div class="date">27th April 2017</div>
 403       <div class="body"><p>I disse dager, med frist 1. mai, har Riksarkivaren ute en høring på
 404 sin forskrift.  Som en kan se er det ikke mye tid igjen før fristen
 405 som går ut på søndag.  Denne forskriften er det som lister opp hvilke
 406 formater det er greit å arkivere i
 407 <a href="http://www.arkivverket.no/arkivverket/Offentleg-forvalting/Noark/Noark-5">Noark
 408 5-løsninger</a> i Norge.</p>
 409
 410 <p>Jeg fant høringsdokumentene hos
 411 <a href="https://www.arkivrad.no/aktuelt/riksarkivarens-forskrift-pa-horing">Norsk
 412 Arkivråd</a> etter å ha blitt tipset på epostlisten til
 413 <a href="https://github.com/hiOA-ABI/nikita-noark5-core">fri
 414 programvareprosjektet Nikita Noark5-Core</a>, som lager et Noark 5
 415 Tjenestegresesnitt.  Jeg er involvert i Nikita-prosjektet og takket
 416 være min interesse for tjenestegrensesnittsprosjektet har jeg lest en
 417 god del Noark 5-relaterte dokumenter, og til min overraskelse oppdaget
 418 at standard epost ikke er på listen over godkjente formater som kan
 419 arkiveres.  Høringen med frist søndag er en glimrende mulighet til å
 420 forsøke å gjøre noe med det.  Jeg holder på med
 421 <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/hoering-arkivforskrift.tex">egen
 422 høringsuttalelse</a>, og lurer på om andre er interessert i å støtte
 423 forslaget om å tillate arkivering av epost som epost i arkivet.</p>
 424
 425 <p>Er du igang med å skrive egen høringsuttalelse allerede?  I så fall
 426 kan du jo vurdere å ta med en formulering om epost-lagring. Jeg tror
 427 ikke det trengs så mye.  Her et kort forslag til tekst:</p>
 428
 429 <p><blockquote>
 430
 431   <p>Viser til høring sendt ut 2017-02-17 (Riksarkivarens referanse
 432   2016/9840 HELHJO), og tillater oss å sende inn noen innspill om
 433   revisjon av Forskrift om utfyllende tekniske og arkivfaglige
 434   bestemmelser om behandling av offentlige arkiver (Riksarkivarens
 435   forskrift).</p>
 436
 437   <p>Svært mye av vår kommuikasjon foregår i dag på e-post.  Vi
 438   foreslår derfor at Internett-e-post, slik det er beskrevet i IETF
 439   RFC 5322,
 440   <a href="https://tools.ietf.org/html/rfc5322">https://tools.ietf.org/html/rfc5322</a>. bør
 441   inn som godkjent dokumentformat.  Vi foreslår at forskriftens
 442   oversikt over godkjente dokumentformater ved innlevering i § 5-16
 443   endres til å ta med Internett-e-post.</p>
 444
 445 </blockquote></p>
 446
 447 <p>Som del av arbeidet med tjenestegrensesnitt har vi testet hvordan
 448 epost kan lagres i en Noark 5-struktur, og holder på å skrive et
 449 forslag om hvordan dette kan gjøres som vil bli sendt over til
 450 arkivverket så snart det er ferdig.  De som er interesserte kan
 451 <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/docs/epostlagring.md">følge
 452 fremdriften på web</a>.</p>
 453
 454 <p>Oppdatering 2017-04-28: I dag ble høringuttalelsen jeg skrev
 455   <a href="https://www.nuug.no/news/NUUGs_h_ringuttalelse_til_Riksarkivarens_forskrift.shtml">sendt
 456   inn av foreningen NUUG</a>.</p>
 457 </div>
 458       <div class="tags">
 459
 460
 461         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 462
 463
 464       </div>
 465     </div>
 466     <div class="padding"></div>
 467
 468     <div class="entry">
 469       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Offentlig_elektronisk_postjournal_blokkerer_tilgang_for_utvalgte_webklienter.html">Offentlig elektronisk postjournal blokkerer tilgang for utvalgte webklienter</a></div>
 470       <div class="date">20th April 2017</div>
 471       <div class="body"><p>Jeg oppdaget i dag at <a href="https://www.oep.no/">nettstedet som
 472 publiserer offentlige postjournaler fra statlige etater</a>, OEP, har
 473 begynt å blokkerer enkelte typer webklienter fra å få tilgang.  Vet
 474 ikke hvor mange det gjelder, men det gjelder i hvert fall libwww-perl
 475 og curl.  For å teste selv, kjør følgende:</p>
 476
 477 <blockquote><pre>
 478 % curl -v -s https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
 479 < HTTP/1.1 404 Not Found
 480 % curl -v -s --header 'User-Agent:Opera/12.0' https://www.oep.no/pub/report.xhtml?reportId=3 2>&1 |grep '< HTTP'
 481 < HTTP/1.1 200 OK
 482 %
 483 </pre></blockquote>
 484
 485 <p>Her kan en se at tjenesten gir «404 Not Found» for curl i
 486 standardoppsettet, mens den gir «200 OK» hvis curl hevder å være Opera
 487 versjon 12.0.  Offentlig elektronisk postjournal startet blokkeringen
 488 2017-03-02.</p>
 489
 490 <p>Blokkeringen vil gjøre det litt vanskeligere å maskinelt hente
 491 informasjon fra oep.no.  Kan blokkeringen være gjort for å hindre
 492 automatisert innsamling av informasjon fra OEP, slik Pressens
 493 Offentlighetsutvalg gjorde for å dokumentere hvordan departementene
 494 hindrer innsyn i
 495 <a href="http://presse.no/dette-mener-np/undergraver-offentlighetsloven/">rapporten
 496 «Slik hindrer departementer innsyn» som ble publiserte i januar
 497 2017</a>.  Det virker usannsynlig, da det jo er trivielt å bytte
 498 User-Agent til noe nytt.</p>
 499
 500 <p>Finnes det juridisk grunnlag for det offentlige å diskriminere
 501 webklienter slik det gjøres her?  Der tilgang gis eller ikke alt etter
 502 hva klienten sier at den heter?  Da OEP eies av DIFI og driftes av
 503 Basefarm, finnes det kanskje noen dokumenter sendt mellom disse to
 504 aktørene man kan be om innsyn i for å forstå hva som har skjedd.  Men
 505 <a href="https://www.oep.no/search/result.html?period=dateRange&fromDate=01.01.2016&toDate=01.04.2017&dateType=documentDate&caseDescription=&descType=both&caseNumber=&documentNumber=&sender=basefarm&senderType=both&documentType=all&legalAuthority=&archiveCode=&list2=196&searchType=advanced&Search=Search+in+records">postjournalen
 506 til DIFI viser kun to dokumenter</a> det siste året mellom DIFI og
 507 Basefarm.
 508 <a href="https://www.mimesbronn.no/request/blokkering_av_tilgang_til_oep_fo">Mimes brønn neste</a>,
 509 tenker jeg.</p>
 510 </div>
 511       <div class="tags">
 512
 513
 514         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>.
 515
 516
 517       </div>
 518     </div>
 519     <div class="padding"></div>
 520
 521     <div class="entry">
 522       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Free_software_archive_system_Nikita_now_able_to_store_documents.html">Free software archive system Nikita now able to store documents</a></div>
 523       <div class="date">19th March 2017</div>
 524       <div class="body"><p>The <a href="https://github.com/hiOA-ABI/nikita-noark5-core">Nikita
 525 Noark 5 core project</a> is implementing the Norwegian standard for
 526 keeping an electronic archive of government documents.
 527 <a href="http://www.arkivverket.no/arkivverket/Offentlig-forvaltning/Noark/Noark-5/English-version">The
 528 Noark 5 standard</a> document the requirement for data systems used by
 529 the archives in the Norwegian government, and the Noark 5 web interface
 530 specification document a REST web service for storing, searching and
 531 retrieving documents and metadata in such archive.  I've been involved
 532 in the project since a few weeks before Christmas, when the Norwegian
 533 Unix User Group
 534 <a href="https://www.nuug.no/news/NOARK5_kjerne_som_fri_programvare_f_r_epostliste_hos_NUUG.shtml">announced
 535 it supported the project</a>.  I believe this is an important project,
 536 and hope it can make it possible for the government archives in the
 537 future to use free software to keep the archives we citizens depend
 538 on.  But as I do not hold such archive myself, personally my first use
 539 case is to store and analyse public mail journal metadata published
 540 from the government.  I find it useful to have a clear use case in
 541 mind when developing, to make sure the system scratches one of my
 542 itches.</p>
 543
 544 <p>If you would like to help make sure there is a free software
 545 alternatives for the archives, please join our IRC channel
 546 (<a href="irc://irc.freenode.net/%23nikita"">#nikita on
 547 irc.freenode.net</a>) and
 548 <a href="https://lists.nuug.no/mailman/listinfo/nikita-noark">the
 549 project mailing list</a>.</p>
 550
 551 <p>When I got involved, the web service could store metadata about
 552 documents.  But a few weeks ago, a new milestone was reached when it
 553 became possible to store full text documents too.  Yesterday, I
 554 completed an implementation of a command line tool
 555 <tt>archive-pdf</tt> to upload a PDF file to the archive using this
 556 API.  The tool is very simple at the moment, and find existing
 557 <a href="https://en.wikipedia.org/wiki/Fonds">fonds</a>, series and
 558 files while asking the user to select which one to use if more than
 559 one exist.  Once a file is identified, the PDF is associated with the
 560 file and uploaded, using the title extracted from the PDF itself.  The
 561 process is fairly similar to visiting the archive, opening a cabinet,
 562 locating a file and storing a piece of paper in the archive.  Here is
 563 a test run directly after populating the database with test data using
 564 our API tester:</p>
 565
 566 <p><blockquote><pre>
 567 ~/src//noark5-tester$ ./archive-pdf mangelmelding/mangler.pdf
 568 using arkiv: Title of the test fonds created 2017-03-18T23:49:32.103446
 569 using arkivdel: Title of the test series created 2017-03-18T23:49:32.103446
 570
 571  0 - Title of the test case file created 2017-03-18T23:49:32.103446
 572  1 - Title of the test file created 2017-03-18T23:49:32.103446
 573 Select which mappe you want (or search term): 0
 574 Uploading mangelmelding/mangler.pdf
 575   PDF title: Mangler i spesifikasjonsdokumentet for NOARK 5 Tjenestegrensesnitt
 576   File 2017/1: Title of the test case file created 2017-03-18T23:49:32.103446
 577 ~/src//noark5-tester$
 578 </pre></blockquote></p>
 579
 580 <p>You can see here how the fonds (arkiv) and serie (arkivdel) only had
 581 one option, while the user need to choose which file (mappe) to use
 582 among the two created by the API tester.  The <tt>archive-pdf</tt>
 583 tool can be found in the git repository for the API tester.</p>
 584
 585 <p>In the project, I have been mostly working on
 586 <a href="https://github.com/petterreinholdtsen/noark5-tester">the API
 587 tester</a> so far, while getting to know the code base.  The API
 588 tester currently use
 589 <a href="https://en.wikipedia.org/wiki/HATEOAS">the HATEOAS links</a>
 590 to traverse the entire exposed service API and verify that the exposed
 591 operations and objects match the specification, as well as trying to
 592 create objects holding metadata and uploading a simple XML file to
 593 store.  The tester has proved very useful for finding flaws in our
 594 implementation, as well as flaws in the reference site and the
 595 specification.</p>
 596
 597 <p>The test document I uploaded is a summary of all the specification
 598 defects we have collected so far while implementing the web service.
 599 There are several unclear and conflicting parts of the specification,
 600 and we have
 601 <a href="https://github.com/petterreinholdtsen/noark5-tester/tree/master/mangelmelding">started
 602 writing down</a> the questions we get from implementing it.  We use a
 603 format inspired by how <a href="http://www.opengroup.org/austin/">The
 604 Austin Group</a> collect defect reports for the POSIX standard with
 605 <a href="http://www.opengroup.org/austin/mantis.html">their
 606 instructions for the MANTIS defect tracker system</a>, in lack of an official way to structure defect reports for Noark 5 (our first submitted defect report was a <a href="https://github.com/petterreinholdtsen/noark5-tester/blob/master/mangelmelding/sendt/2017-03-15-mangel-prosess.md">request for a procedure for submitting defect reports</a> :).
 607
 608 <p>The Nikita project is implemented using Java and Spring, and is
 609 fairly easy to get up and running using Docker containers for those
 610 that want to test the current code base.  The API tester is
 611 implemented in Python.</p>
 612 </div>
 613       <div class="tags">
 614
 615
 616         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 617
 618
 619       </div>
 620     </div>
 621     <div class="padding"></div>
 622
 623     <div class="entry">
 624       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html">Detecting NFS hangs on Linux without hanging yourself...</a></div>
 625       <div class="date"> 9th March 2017</div>
 626       <div class="body"><p>Over the years, administrating thousand of NFS mounting linux
 627 computers at the time, I often needed a way to detect if the machine
 628 was experiencing NFS hang.  If you try to use <tt>df</tt> or look at a
 629 file or directory affected by the hang, the process (and possibly the
 630 shell) will hang too.  So you want to be able to detect this without
 631 risking the detection process getting stuck too.  It has not been
 632 obvious how to do this.  When the hang has lasted a while, it is
 633 possible to find messages like these in dmesg:</p>
 634
 635 <p><blockquote>
 636 nfs: server nfsserver not responding, still trying
 637 <br>nfs: server nfsserver OK
 638 </blockquote></p>
 639
 640 <p>It is hard to know if the hang is still going on, and it is hard to
 641 be sure looking in dmesg is going to work.  If there are lots of other
 642 messages in dmesg the lines might have rotated out of site before they
 643 are noticed.</p>
 644
 645 <p>While reading through the nfs client implementation in linux kernel
 646 code, I came across some statistics that seem to give a way to detect
 647 it.  The om_timeouts sunrpc value in the kernel will increase every
 648 time the above log entry is inserted into dmesg.  And after digging a
 649 bit further, I discovered that this value show up in
 650 /proc/self/mountstats on Linux.</p>
 651
 652 <p>The mountstats content seem to be shared between files using the
 653 same file system context, so it is enough to check one of the
 654 mountstats files to get the state of the mount point for the machine.
 655 I assume this will not show lazy umounted NFS points, nor NFS mount
 656 points in a different process context (ie with a different filesystem
 657 view), but that does not worry me.</p>
 658
 659 <p>The content for a NFS mount point look similar to this:</p>
 660
 661 <p><blockquote><pre>
 662 [...]
 663 device /dev/mapper/Debian-var mounted on /var with fstype ext3
 664 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
 665         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
 666         age:    7863311
 667         caps:   caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
 668         sec:    flavor=1,pseudoflavor=1
 669         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
 670         bytes:  166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
 671         RPC iostats version: 1.0  p/v: 100003/3 (nfs)
 672         xprt:   tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
 673         per-op statistics
 674                 NULL: 0 0 0 0 0 0 0 0
 675              GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
 676              SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
 677               LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
 678               ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
 679             READLINK: 125 125 0 20472 18620 0 1112 1118
 680                 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
 681                WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
 682               CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
 683                MKDIR: 3680 3680 0 773980 993920 26 23990 24245
 684              SYMLINK: 903 903 0 233428 245488 6 5865 5917
 685                MKNOD: 80 80 0 20148 21760 0 299 304
 686               REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
 687                RMDIR: 3367 3367 0 645112 484848 22 5782 6002
 688               RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
 689                 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
 690              READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
 691          READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
 692               FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
 693               FSINFO: 2 2 0 232 328 0 1 1
 694             PATHCONF: 1 1 0 116 140 0 0 0
 695               COMMIT: 0 0 0 0 0 0 0 0
 696
 697 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
 698 [...]
 699 </pre></blockquote></p>
 700
 701 <p>The key number to look at is the third number in the per-op list.
 702 It is the number of NFS timeouts experiences per file system
 703 operation.  Here 22 write timeouts and 5 access timeouts.  If these
 704 numbers are increasing, I believe the machine is experiencing NFS
 705 hang.  Unfortunately the timeout value do not start to increase right
 706 away.  The NFS operations need to time out first, and this can take a
 707 while.  The exact timeout value depend on the setup.  For example the
 708 defaults for TCP and UDP mount points are quite different, and the
 709 timeout value is affected by the soft, hard, timeo and retrans NFS
 710 mount options.</p>
 711
 712 <p>The only way I have been able to get working on Debian and RedHat
 713 Enterprise Linux for getting the timeout count is to peek in /proc/.
 714 But according to
 715 <ahref="http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html">Solaris
 716 10 System Administration Guide: Network Services</a>, the 'nfsstat -c'
 717 command can be used to get these timeout values.  But this do not work
 718 on Linux, as far as I can tell.  I
 719 <ahref="http://bugs.debian.org/857043">asked Debian about this</a>,
 720 but have not seen any replies yet.</p>
 721
 722 <p>Is there a better way to figure out if a Linux NFS client is
 723 experiencing NFS hangs?  Is there a way to detect which processes are
 724 affected?  Is there a way to get the NFS mount going quickly once the
 725 network problem causing the NFS hang has been cleared?  I would very
 726 much welcome some clues, as we regularly run into NFS hangs.</p>
 727 </div>
 728       <div class="tags">
 729
 730
 731         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin</a>.
 732
 733
 734       </div>
 735     </div>
 736     <div class="padding"></div>
 737
 738     <p style="text-align: right;"><a href="index.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14" /></a></p>
 739     <div id="sidebar">
 740
 741
 742
 743 <h2>Archive</h2>
 744 <ul>
 745
 746 <li>2017
 747 <ul>
 748
 749 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
 750
 751 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/02/">February (3)</a></li>
 752
 753 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/03/">March (5)</a></li>
 754
 755 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/04/">April (2)</a></li>
 756
 757 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/06/">June (5)</a></li>
 758
 759 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/07/">July (1)</a></li>
 760
 761 </ul></li>
 762
 763 <li>2016
 764 <ul>
 765
 766 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
 767
 768 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
 769
 770 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
 771
 772 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
 773
 774 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
 775
 776 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
 777
 778 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
 779
 780 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
 781
 782 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
 783
 784 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
 785
 786 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
 787
 788 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
 789
 790 </ul></li>
 791
 792 <li>2015
 793 <ul>
 794
 795 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
 796
 797 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
 798
 799 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
 800
 801 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
 802
 803 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
 804
 805 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
 806
 807 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
 808
 809 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
 810
 811 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
 812
 813 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
 814
 815 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
 816
 817 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
 818
 819 </ul></li>
 820
 821 <li>2014
 822 <ul>
 823
 824 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 825
 826 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 827
 828 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
 829
 830 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
 831
 832 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
 833
 834 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
 835
 836 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
 837
 838 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
 839
 840 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
 841
 842 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
 843
 844 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
 845
 846 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
 847
 848 </ul></li>
 849
 850 <li>2013
 851 <ul>
 852
 853 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 854
 855 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 856
 857 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 858
 859 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 860
 861 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 862
 863 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 864
 865 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 866
 867 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 868
 869 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 870
 871 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 872
 873 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 874
 875 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 876
 877 </ul></li>
 878
 879 <li>2012
 880 <ul>
 881
 882 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 883
 884 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 885
 886 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 887
 888 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 889
 890 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 891
 892 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 893
 894 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 895
 896 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 897
 898 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 899
 900 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 901
 902 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 903
 904 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 905
 906 </ul></li>
 907
 908 <li>2011
 909 <ul>
 910
 911 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 912
 913 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 914
 915 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 916
 917 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 918
 919 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 920
 921 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 922
 923 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 924
 925 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 926
 927 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 928
 929 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 930
 931 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 932
 933 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 934
 935 </ul></li>
 936
 937 <li>2010
 938 <ul>
 939
 940 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 941
 942 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 943
 944 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 945
 946 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 947
 948 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 949
 950 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 951
 952 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 953
 954 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 955
 956 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 957
 958 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 959
 960 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 961
 962 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 963
 964 </ul></li>
 965
 966 <li>2009
 967 <ul>
 968
 969 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 970
 971 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 972
 973 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 974
 975 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 976
 977 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 978
 979 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 980
 981 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 982
 983 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 984
 985 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 986
 987 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 988
 989 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 990
 991 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 992
 993 </ul></li>
 994
 995 <li>2008
 996 <ul>
 997
 998 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 999
1000 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1001
1002 </ul></li>
1003
1004 </ul>
1005
1006
1007
1008 <h2>Tags</h2>
1009 <ul>
1010
1011  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1012
1013  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1014
1015  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1016
1017  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1018
1019  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
1020
1021  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (16)</a></li>
1022
1023  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1024
1025  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1026
1027  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (150)</a></li>
1028
1029  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (158)</a></li>
1030
1031  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian-handbook">debian-handbook (4)</a></li>
1032
1033  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1034
1035  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (16)</a></li>
1036
1037  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (24)</a></li>
1038
1039  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1040
1041  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (350)</a></li>
1042
1043  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1044
1045  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1046
1047  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (30)</a></li>
1048
1049  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1050
1051  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (18)</a></li>
1052
1053  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
1054
1055  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
1056
1057  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (15)</a></li>
1058
1059  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (20)</a></li>
1060
1061  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1062
1063  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1064
1065  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1066
1067  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1068
1069  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1070
1071  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (39)</a></li>
1072
1073  <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (9)</a></li>
1074
1075  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (291)</a></li>
1076
1077  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (189)</a></li>
1078
1079  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (33)</a></li>
1080
1081  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1082
1083  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (64)</a></li>
1084
1085  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (100)</a></li>
1086
1087  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1088
1089  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1090
1091  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1092
1093  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1094
1095  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (10)</a></li>
1096
1097  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1098
1099  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (5)</a></li>
1100
1101  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1102
1103  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (53)</a></li>
1104
1105  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1106
1107  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
1108
1109  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (55)</a></li>
1110
1111  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (6)</a></li>
1112
1113  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (11)</a></li>
1114
1115  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (48)</a></li>
1116
1117  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (3)</a></li>
1118
1119  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1120
1121  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1122
1123  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (59)</a></li>
1124
1125  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1126
1127  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (40)</a></li>
1128
1129 </ul>
1130
1131
1132     </div>
1133     <p style="text-align: right">
1134  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1135 </p>
1136
1137   </body>
1138 </html>