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