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