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