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">
5 <meta http-equiv=
"Content-Type" content=
"text/html;charset=utf-8" />
6 <title>Petter Reinholdtsen: entries from March
2014</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=
"03.rss" type=
"application/rss+xml" />
15 <a href=
"http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen
</a>
22 <h3>Entries from March
2014.
</h3>
26 <a href=
"http://people.skolelinux.org/pere/blog/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html">Video DVD reader library / python-dvdvideo - nice free software
</a>
32 <p>Keeping your DVD collection safe from scratches and curious
33 children fingers while still having it available when you want to see a
34 movie is not straight forward. My preferred method at the moment is
35 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
36 Hour or other useful players to view the resulting file. This way the
37 subtitles and bonus material are still available and using the ISO is
38 just like inserting the original DVD record in the DVD player.
</p>
40 <p>Earlier I used dd for taking security copies, but it do not handle
41 DVDs giving read errors (which are quite a few of them). I've also
43 <a href=
"http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html">dvdbackup
44 and genisoimage
</a>, but these days I use the marvellous python library
46 <a href=
"http://bblank.thinkmo.de/blog/new-software-python-dvdvideo">python-dvdvideo
</a>
47 written by Bastian Blank. It is
48 <a href
"http://packages.qa.debian.org/p/python-dvdvideo.html">in Debian
49 already
</a> and the binary package name is python3-dvdvideo. Instead
50 of trying to read every block from the DVD, it parses the file
51 structure and figure out which block on the DVD is actually in used,
52 and only read those blocks from the DVD. This work surprisingly well,
53 and I have been able to almost backup my entire DVD collection using
54 this method.
</p> So far, python-dvdvideo have failed on between
10 and
55 20 DVDs, which is a small fraction of my collection. The most common
57 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720831">DVDs
58 using UTF-
16 instead of UTF-
8 characters
</a>, which according to
59 Bastian is against the DVD specification (and seem to cause some
60 players to fail too). A rarer problem is what seem to be inconsistent
61 DVD structures, as the python library
62 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723079">claim
63 there is a overlap between objects
</a>. An equally rare problem claim
64 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741878">some
65 value is out of range
</a>. No idea what is going on there. I wish I
66 knew enough about the DVD format to fix these, to ensure my movie
67 collection will stay with me in the future.
</p>
69 <p>So, if you need to keep your DVDs safe, back them up using
70 python-dvdvideo. :)
</p>
76 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/video">video
</a>.
81 <div class=
"padding"></div>
85 <a href=
"http://people.skolelinux.org/pere/blog/Norsk_utgave_av_Alaveteli___WhatDoTheyKnow_p__trappene.html">Norsk utgave av Alaveteli / WhatDoTheyKnow på trappene
</a>
91 <p>Det offentlige Norge har mye kunnskap og informasjon. Men hvordan
92 kan en få tilgang til den på en enkel måte? Takket være et lite
93 knippe lover og tilhørende forskrifter, blant annet
94 <a href=
"http://lovdata.no/dokument/NL/lov/2006-05-19-16">offentlighetsloven
</a>,
95 <a href=
"http://lovdata.no/dokument/NL/lov/2003-05-09-31">miljøinformasjonsloven
</a>
97 <a href=
"http://lovdata.no/dokument/NL/lov/1967-02-10/">forvaltningsloven
</a>
98 har en rett til å spørre det offentlige og få svar. Men det finnes
99 intet offentlig arkiv over hva andre har spurt om, og dermed risikerer en
100 å måtte forstyrre myndighetene gang på gang for å få tak i samme
101 informasjonen på nytt.
<a href=
"http://www.mysociety.org/">Britiske
102 mySociety
</a> har laget tjenesten
103 <a href=
"http://www.whatdotheyknow.com/">WhatDoTheyKnow
</a> som gjør
104 noe med dette. I Storbritannia blir WhatdoTheyKnow brukt i
105 <a href=
"http://www.mysociety.org/2011/07/01/whatdotheyknows-share-of-central-government-foi-requests-q2-2011/">ca
106 15% av alle innsynsforespørsler mot sentraladministrasjonen
</a>.
107 Prosjektet heter
<a href=
"http://www.alaveteli.org/">Alaveteli
</A>, og
108 er takk i bruk en rekke steder etter at løsningen ble generalisert og
109 gjort mulig å oversette. Den hjelper borgerne med å be om innsyn,
110 rådgir ved purringer og klager og lar alle se hvilke henvendelser som
111 er sendt til det offentlige og hvilke svar som er kommet inn, i et
112 søkpart arkiv. Her i Norge holder vi i foreningen NUUG på å få opp en
113 norsk utgave av Alaveteli, og her trenger vi din hjelp med
116 <p>Så langt er
76 % av Alaveteli oversatt til norsk bokmål, men vi
117 skulle gjerne vært oppe i
100 % før lansering. Oversettelsen gjøres
118 på
<a href=
"https://www.transifex.com/projects/p/alaveteli/">Transifex,
119 der enhver som registrerer seg
</a> og ber om tilgang til
120 bokmålsoversettelsen får bidra. Vi har satt opp en test av tjenesten
121 (som ikke sender epost til det offentlige, kun til oss som holder på å
122 sette opp tjenesten) på maskinen
123 <a href=
"http://alaveteli-dev.nuug.no/">alaveteli-dev.nuug.no
</a>, der
124 en kan se hvordan de oversatte meldingen blir seende ut på nettsiden.
125 Når tjenesten lanseres vil den hete
126 <a href=
"https://www.mimesbrønn.no/">Mimes brønn
</a>, etter
127 visdomskilden som Odin måtte gi øyet sitt for å få drikke i. Den
128 nettsiden er er ennå ikke klar til bruk.
</p>
130 <p>Hvis noen vil oversette til nynorsk også, så skal vi finne ut
131 hvordan vi lager en flerspråklig tjeneste. Men i første omgang er
132 fokus på bokmålsoversettelsen, der vi selv har nok peiling til å ha
133 fått oversatt
76%, men trenger hjelp for å komme helt i mål. :)
</p>
139 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</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>.
144 <div class=
"padding"></div>
148 <a href=
"http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html">Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</a>
154 <p>The
<a href=
"https://wiki.debian.org/FreedomBox">Freedombox
155 project
</a> is working on providing the software and hardware for
156 making it easy for non-technical people to host their data and
157 communication at home, and being able to communicate with their
158 friends and family encrypted and away from prying eyes. It has been
159 going on for a while, and is slowly progressing towards a new test
162 <p>And what day could be better than the Pi day to announce that the
163 new version will provide "hard drive" / SD card / USB stick images for
164 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
165 system), and can also be installed using a Debian installer preseed
166 file. The Debian based Freedombox is now based on Debian Jessie,
167 where most of the needed packages used are already present. Only one,
168 the freedombox-setup package, is missing. To try to build your own
169 boot image to test the current status, fetch the freedom-maker scripts
171 <a href=
"http://packages.qa.debian.org/vmdebootstrap">vmdebootstrap
</a>
172 with a user with sudo access to become root:
175 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
177 sudo apt-get install git vmdebootstrap mercurial python-docutils \
178 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
180 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
183 <p>Root access is needed to run debootstrap and mount loopback
184 devices. See the README for more details on the build. If you do not
185 want all three images, trim the make line. But note that thanks to
<a
186 href=
"https://bugs.debian.org/741407">a race condition in
187 vmdebootstrap
</a>, the build might fail without the patch to the
190 <p>If you instead want to install using a Debian CD and the preseed
191 method, boot a Debian Wheezy ISO and use this boot argument to load
192 the preseed values:
</p>
195 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a>
198 <p>But note that due to
<a href=
"https://bugs.debian.org/740673">a
199 recently introduced bug in apt in Jessie
</a>, the installer will
200 currently hang while setting up APT sources. Killing the
201 '
<tt>apt-cdrom ident
</tt>' process when it hang a few times during the
202 installation will get the installation going. This affect all
203 installations in Jessie, and I expect it will be fixed soon.
</p>
205 Give it a go and let us know how it goes on the mailing list, and help
206 us get the new release published. :) Please join us on
207 <a href=
"irc://irc.debian.org:6667/%23freedombox">IRC (#freedombox on
208 irc.debian.org)
</a> and
209 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss">the
210 mailing list
</a> if you want to help make this vision come true.
</p>
216 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/freedombox">freedombox
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/web">web
</a>.
221 <div class=
"padding"></div>
225 <a href=
"http://people.skolelinux.org/pere/blog/How_to_add_extra_storage_servers_in_Debian_Edu___Skolelinux.html">How to add extra storage servers in Debian Edu / Skolelinux
</a>
231 <p>On larger sites, it is useful to use a dedicated storage server for
232 storing user home directories and data. The design for handling this
233 in
<a href=
"http://www.skolelinux.org/">Debian Edu / Skolelinux
</a>, is
234 to update the automount rules in LDAP and let the automount daemon on
235 the clients take care of the rest. I was reminded about the need to
236 document this better when one of the customers of
237 <a href=
"http://www.slxdrift.no/">Skolelinux Drift AS
</a>, where I am
238 on the board of directors, asked about how to do this. The steps to
239 get this working are the following:
</p>
243 <li>Add new storage server in DNS. I use nas-server.intern as the
244 example host here.
</li>
246 <li>Add automoun LDAP information about this server in LDAP, to allow
247 all clients to automatically mount it on reqeust.
</li>
249 <li>Add the relevant entries in tjener.intern:/etc/fstab, because
250 tjener.intern do not use automount to avoid mounting loops.
</li>
254 <p>DNS entries are added in GOsa², and not described here. Follow the
255 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/GettingStarted">instructions
256 in the manual
</a> (Machine Management with GOsa² in section Getting
259 <p>Ensure that the NFS export points on the server are exported to the
260 relevant subnets or machines:
</p>
263 root@tjener:~# showmount -e nas-server
264 Export list for nas-server:
267 </pre></blockquote></p>
269 <p>Here everything on the backbone network is granted access to the
270 /storage export. With NFSv3 it is slightly better to limit it to
271 netgroup membership or single IP addresses to have some limits on the
274 <p>The next step is to update LDAP. This can not be done using GOsa²,
275 because it lack a module for automount. Instead, use ldapvi and add
276 the required LDAP objects using an editor.
</p>
279 ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no
280 </pre></blockquote></p>
282 <p>When the editor show up, add the following LDAP objects at the
283 bottom of the document. The "/&" part in the last LDAP object is a
284 wild card matching everything the nas-server exports, removing the
285 need to list individual mount points in LDAP.
</p>
288 add cn=nas-server,ou=auto.skole,ou=automount,dc=skole,dc=skolelinux,dc=no
289 objectClass: automount
291 automountInformation: -fstype=autofs --timeout=
60 ldap:ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
293 add ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
295 objectClass: automountMap
298 add cn=/,ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
299 objectClass: automount
301 automountInformation: -fstype=nfs,tcp,rsize=
32768,wsize=
32768,rw,intr,hard,nodev,nosuid,noatime nas-server.intern:/&
302 </pre></blockquote></p>
304 <p>The last step to remember is to mount the relevant mount points in
305 tjener.intern by adding them to /etc/fstab, creating the mount
306 directories using mkdir and running "mount -a" to mount them.
</p>
308 <p>When this is done, your users should be able to access the files on
309 the storage server directly by just visiting the
310 /tjener/nas-server/storage/ directory using any application on any
311 workstation, LTSP client or LTSP server.
</p>
317 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/ldap">ldap
</a>.
322 <div class=
"padding"></div>
326 <a href=
"http://people.skolelinux.org/pere/blog/Hvordan_b_r_RFC_822_formattert_epost_lagres_i_en_NOARK5_database_.html">Hvordan bør RFC
822-formattert epost lagres i en NOARK5-database?
</a>
332 <p>For noen uker siden ble NXCs fri programvarelisenserte
334 <a href=
"http://www.nuug.no/aktiviteter/20140211-noark/">presentert hos
336 <a href=
"https://www.youtube.com/watch?v=JCb_dNS3MHQ">på youtube
337 foreløbig
</a>), og det fikk meg til å titte litt mer på NOARK5,
338 standarden for arkivhåndtering i det offentlige Norge. Jeg lurer på
339 om denne kjernen kan være nyttig i et par av mine prosjekter, og for ett
340 av dem er det mest aktuelt å lagre epost. Jeg klarte ikke finne noen
341 anbefaling om hvordan RFC
822-formattert epost (aka Internett-epost)
342 burde lagres i NOARK5, selv om jeg vet at noen arkiver tar
343 PDF-utskrift av eposten med sitt epostprogram og så arkiverer PDF-en
344 (eller enda værre, tar papirutskrift og lagrer bildet av eposten som
347 <p>Det er ikke så mange formater som er akseptert av riksarkivet til
348 langtidsoppbevaring av offentlige arkiver, og PDF og XML er de mest
349 aktuelle i så måte. Det slo meg at det måtte da finnes en eller annen
350 egnet XML-representasjon og at det kanskje var enighet om hvilken som
351 burde brukes, så jeg tok mot til meg og spurte
352 <a href=
"http://samdok.com/">SAMDOK
</a>, en gruppe tilknyttet
353 arkivverket som ser ut til å jobbe med NOARK-samhandling, om de hadde
359 <p>Usikker på om dette er riktig forum å ta opp mitt spørsmål, men jeg
360 lurer på om det er definert en anbefaling om hvordan RFC
361 822-formatterte epost (aka vanlig Internet-epost) bør lages håndteres
362 i NOARK5, slik at en bevarer all informasjon i eposten
363 (f.eks. Received-linjer). Finnes det en anbefalt XML-mapping ala den
365 <URL:
<a href=
"https://www.informit.com/articles/article.aspx?p=32074">https://www.informit.com/articles/article.aspx?p=
32074</a> >? Mitt
366 mål er at det skal være mulig å lagre eposten i en NOARK5-kjerne og
367 kunne få ut en identisk formattert kopi av opprinnelig epost ved
371 <p>Postmottaker hos SAMDOK mente spørsmålet heller burde stilles
372 direkte til riksarkivet, og jeg fikk i dag svar derfra formulert av
373 seniorrådgiver Geir Ivar Tungesvik:
</p>
376 <p>Riksarkivet har ingen anbefalinger når det gjelder konvertering fra
377 e-post til XML. Det står arkivskaper fritt å eventuelt definere/bruke
378 eget format. Inklusive da - som det spørres om - et format der det er
379 mulig å re-etablere e-post format ut fra XML-en. XML (e-post)
380 dokumenter må være referert i arkivstrukturen, og det må vedlegges et
381 gyldig XML skjema (.xsd) for XML-filene. Arkivskaper står altså fritt
382 til å gjøre hva de vil, bare det dokumenteres og det kan dannes et
383 utrekk ved avlevering til depot.
</p>
385 <p>De obligatoriske kravene i Noark
5 standarden må altså oppfylles -
386 etter dialog med Riksarkivet i forbindelse med godkjenning. For
387 offentlige arkiv er det særlig viktig med filene loependeJournal.xml
388 og offentligJournal.xml. Private arkiv som vil forholde seg til Noark
389 5 standarden er selvsagt frie til å bruke det som er relevant for dem
390 av obligatoriske krav.
</p>
393 <p>Det ser dermed ut for meg som om det er et lite behov for å
394 standardisere XML-lagring av RFC-
822-formatterte meldinger. Noen som
395 vet om god spesifikasjon i så måte? I tillegg til den omtalt over,
396 har jeg kommet over flere aktuelle beskrivelser (søk på "rfc
822
397 xml", så finner du aktuelle alternativer).
</p>
401 <li><a href=
"http://www.openhealth.org/xmtp/">XML MIME Transformation
402 protocol (XMTP)
</a> fra OpenHealth, sist oppdatert
2001.
</li>
404 <li><a href=
"https://tools.ietf.org/html/draft-klyne-message-rfc822-xml-03">An
405 XML format for mail and other messages
</a> utkast fra IETF datert
408 <li><a href=
"http://www.informit.com/articles/article.aspx?p=32074">xMail:
409 E-mail as XML
</a> en artikkel fra
2003 som beskriver python-modulen
410 rfc822 som gir ut XML-representasjon av en RFC
822-formattert epost.
</li>
414 <p>Finnes det andre og bedre spesifikasjoner for slik lagring? Send
415 meg en epost hvis du har innspill.
</p>
421 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn
</a>.
426 <div class=
"padding"></div>
428 <p style=
"text-align: right;"><a href=
"03.rss"><img src=
"http://people.skolelinux.org/pere/blog/xml.gif" alt=
"RSS Feed" width=
"36" height=
"14" /></a></p>
439 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/01/">January (
2)
</a></li>
441 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/02/">February (
3)
</a></li>
443 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2014/03/">March (
5)
</a></li>
450 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/01/">January (
11)
</a></li>
452 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/02/">February (
9)
</a></li>
454 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/03/">March (
9)
</a></li>
456 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/04/">April (
6)
</a></li>
458 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/05/">May (
9)
</a></li>
460 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/06/">June (
10)
</a></li>
462 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/07/">July (
7)
</a></li>
464 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/08/">August (
3)
</a></li>
466 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/09/">September (
5)
</a></li>
468 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/10/">October (
7)
</a></li>
470 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/11/">November (
9)
</a></li>
472 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/12/">December (
3)
</a></li>
479 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/01/">January (
7)
</a></li>
481 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/02/">February (
10)
</a></li>
483 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/03/">March (
17)
</a></li>
485 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/04/">April (
12)
</a></li>
487 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/05/">May (
12)
</a></li>
489 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/06/">June (
20)
</a></li>
491 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/07/">July (
17)
</a></li>
493 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/08/">August (
6)
</a></li>
495 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/09/">September (
9)
</a></li>
497 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/10/">October (
17)
</a></li>
499 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/11/">November (
10)
</a></li>
501 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/12/">December (
7)
</a></li>
508 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/01/">January (
16)
</a></li>
510 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/02/">February (
6)
</a></li>
512 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/03/">March (
6)
</a></li>
514 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/04/">April (
7)
</a></li>
516 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/05/">May (
3)
</a></li>
518 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/06/">June (
2)
</a></li>
520 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/07/">July (
7)
</a></li>
522 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/08/">August (
6)
</a></li>
524 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/09/">September (
4)
</a></li>
526 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/10/">October (
2)
</a></li>
528 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/11/">November (
3)
</a></li>
530 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/12/">December (
1)
</a></li>
537 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/01/">January (
2)
</a></li>
539 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/02/">February (
1)
</a></li>
541 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/03/">March (
3)
</a></li>
543 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/04/">April (
3)
</a></li>
545 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/05/">May (
9)
</a></li>
547 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/06/">June (
14)
</a></li>
549 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/07/">July (
12)
</a></li>
551 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/08/">August (
13)
</a></li>
553 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/09/">September (
7)
</a></li>
555 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/10/">October (
9)
</a></li>
557 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/11/">November (
13)
</a></li>
559 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/12/">December (
12)
</a></li>
566 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/01/">January (
8)
</a></li>
568 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/02/">February (
8)
</a></li>
570 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/03/">March (
12)
</a></li>
572 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/04/">April (
10)
</a></li>
574 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/05/">May (
9)
</a></li>
576 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/06/">June (
3)
</a></li>
578 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/07/">July (
4)
</a></li>
580 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/08/">August (
3)
</a></li>
582 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/09/">September (
1)
</a></li>
584 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/10/">October (
2)
</a></li>
586 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/11/">November (
3)
</a></li>
588 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/12/">December (
3)
</a></li>
595 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/11/">November (
5)
</a></li>
597 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/12/">December (
7)
</a></li>
608 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (
13)
</a></li>
610 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/amiga">amiga (
1)
</a></li>
612 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/aros">aros (
1)
</a></li>
614 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bankid">bankid (
4)
</a></li>
616 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (
8)
</a></li>
618 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (
14)
</a></li>
620 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bsa">bsa (
2)
</a></li>
622 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (
2)
</a></li>
624 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian (
95)
</a></li>
626 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (
145)
</a></li>
628 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/digistan">digistan (
10)
</a></li>
630 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/docbook">docbook (
10)
</a></li>
632 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (
4)
</a></li>
634 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/english">english (
239)
</a></li>
636 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (
21)
</a></li>
638 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (
12)
</a></li>
640 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (
12)
</a></li>
642 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (
6)
</a></li>
644 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (
11)
</a></li>
646 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/intervju">intervju (
39)
</a></li>
648 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (
7)
</a></li>
650 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/kart">kart (
18)
</a></li>
652 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ldap">ldap (
9)
</a></li>
654 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/lenker">lenker (
7)
</a></li>
656 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (
1)
</a></li>
658 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (
7)
</a></li>
660 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (
26)
</a></li>
662 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk (
242)
</a></li>
664 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug (
162)
</a></li>
666 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (
11)
</a></li>
668 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/open311">open311 (
2)
</a></li>
670 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (
46)
</a></li>
672 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/personvern">personvern (
69)
</a></li>
674 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/raid">raid (
1)
</a></li>
676 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/reprap">reprap (
11)
</a></li>
678 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rfid">rfid (
2)
</a></li>
680 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/robot">robot (
9)
</a></li>
682 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rss">rss (
1)
</a></li>
684 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ruter">ruter (
4)
</a></li>
686 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (
2)
</a></li>
688 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (
35)
</a></li>
690 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (
4)
</a></li>
692 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (
4)
</a></li>
694 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard (
44)
</a></li>
696 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (
3)
</a></li>
698 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (
9)
</a></li>
700 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (
22)
</a></li>
702 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (
1)
</a></li>
704 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/valg">valg (
8)
</a></li>
706 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/video">video (
40)
</a></li>
708 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (
4)
</a></li>
710 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/web">web (
29)
</a></li>
716 <p style=
"text-align: right">
717 Created by
<a href=
"http://steve.org.uk/Software/chronicle">Chronicle v4.6
</a>