]> pere.pagekite.me Git - homepage.git/blob - blog/index.html
Generated.
[homepage.git] / 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/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html">Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</a></div>
24 <div class="date">14th March 2014</div>
25 <div class="body"><p>The <a href="https://wiki.debian.org/FreedomBox">Freedombox
26 project</a> is working on providing the software and hardware for
27 making it easy for non-technical people to host their data and
28 communication at home, and being able to communicate with their
29 friends and family encrypted and away from prying eyes. It has been
30 going on for a while, and is slowly progressing towards a new test
31 release (0.2).</p>
32
33 <p>And what day could be better than the Pi day to announce that the
34 new version will provide "hard drive" / SD card / USB stick images for
35 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
36 system), and can also be installed using a Debian installer preseed
37 file. The Debian based Freedombox is now based on Debian Jessie,
38 where most of the needed packages used are already present. Only one,
39 the freedombox-setup package, is missing. To try to build your own
40 boot image to test the current status, fetch the freedom-maker scripts
41 and build using
42 <a href="http://packages.qa.debian.org/vmdebootstrap">vmdebootstrap</a>
43 with a user with sudo access to become root:
44
45 <pre>
46 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
47 freedom-maker
48 sudo apt-get install git vmdebootstrap mercurial python-docutils \
49 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
50 u-boot-tools
51 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
52 </pre>
53
54 <p>Root access is needed to run debootstrap and mount loopback
55 devices. See the README for more details on the build. If you do not
56 want all three images, trim the make line. But note that thanks to <a
57 href="https://bugs.debian.org/741407">a race condition in
58 vmdebootstrap</a>, the build might fail without the patch to the
59 kpartx call.</p>
60
61 <p>If you instead want to install using a Debian CD and the preseed
62 method, boot a Debian Wheezy ISO and use this boot argument to load
63 the preseed values:</p>
64
65 <pre>
66 url=<a href="http://www.reinholdtsen.name/freedombox/preseed-jessie.dat">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat</a>
67 </pre>
68
69 <p>But note that due to <a href="https://bugs.debian.org/740673">a
70 recently introduced bug in apt in Jessie</a>, the installer will
71 currently hang while setting up APT sources. Killing the
72 '<tt>apt-cdrom ident</tt>' process when it hang a few times during the
73 installation will get the installation going. This affect all
74 installations in Jessie, and I expect it will be fixed soon.</p>
75
76 Give it a go and let us know how it goes on the mailing list, and help
77 us get the new release published. :) Please join us on
78 <a href="irc://irc.debian.org:6667/%23freedombox">IRC (#freedombox on
79 irc.debian.org)</a> and
80 <a href="http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss">the
81 mailing list</a> if you want to help make this vision come true.</p>
82 </div>
83 <div class="tags">
84
85
86 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>.
87
88
89 </div>
90 </div>
91 <div class="padding"></div>
92
93 <div class="entry">
94 <div class="title"><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></div>
95 <div class="date">12th March 2014</div>
96 <div class="body"><p>On larger sites, it is useful to use a dedicated storage server for
97 storing user home directories and data. The design for handling this
98 in <a href="http://www.skolelinux.org/">Debian Edu / Skolelinux</a>, is
99 to update the automount rules in LDAP and let the automount daemon on
100 the clients take care of the rest. I was reminded about the need to
101 document this better when one of the customers of
102 <a href="http://www.slxdrift.no/">Skolelinux Drift AS</a>, where I am
103 on the board of directors, asked about how to do this. The steps to
104 get this working are the following:</p>
105
106 <p><ol>
107
108 <li>Add new storage server in DNS. I use nas-server.intern as the
109 example host here.</li>
110
111 <li>Add automoun LDAP information about this server in LDAP, to allow
112 all clients to automatically mount it on reqeust.</li>
113
114 <li>Add the relevant entries in tjener.intern:/etc/fstab, because
115 tjener.intern do not use automount to avoid mounting loops.</li>
116
117 </ol></p>
118
119 <p>DNS entries are added in GOsa², and not described here. Follow the
120 <a href="https://wiki.debian.org/DebianEdu/Documentation/Wheezy/GettingStarted">instructions
121 in the manual</a> (Machine Management with GOsa² in section Getting
122 started).</p>
123
124 <p>Ensure that the NFS export points on the server are exported to the
125 relevant subnets or machines:</p>
126
127 <p><blockquote><pre>
128 root@tjener:~# showmount -e nas-server
129 Export list for nas-server:
130 /storage 10.0.0.0/8
131 root@tjener:~#
132 </pre></blockquote></p>
133
134 <p>Here everything on the backbone network is granted access to the
135 /storage export. With NFSv3 it is slightly better to limit it to
136 netgroup membership or single IP addresses to have some limits on the
137 NFS access.</p>
138
139 <p>The next step is to update LDAP. This can not be done using GOsa²,
140 because it lack a module for automount. Instead, use ldapvi and add
141 the required LDAP objects using an editor.</p>
142
143 <p><blockquote><pre>
144 ldapvi --ldap-conf -ZD '(cn=admin)' -b ou=automount,dc=skole,dc=skolelinux,dc=no
145 </pre></blockquote></p>
146
147 <p>When the editor show up, add the following LDAP objects at the
148 bottom of the document. The "/&" part in the last LDAP object is a
149 wild card matching everything the nas-server exports, removing the
150 need to list individual mount points in LDAP.</p>
151
152 <p><blockquote><pre>
153 add cn=nas-server,ou=auto.skole,ou=automount,dc=skole,dc=skolelinux,dc=no
154 objectClass: automount
155 cn: nas-server
156 automountInformation: -fstype=autofs --timeout=60 ldap:ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
157
158 add ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
159 objectClass: top
160 objectClass: automountMap
161 ou: auto.nas-server
162
163 add cn=/,ou=auto.nas-server,ou=automount,dc=skole,dc=skolelinux,dc=no
164 objectClass: automount
165 cn: /
166 automountInformation: -fstype=nfs,tcp,rsize=32768,wsize=32768,rw,intr,hard,nodev,nosuid,noatime nas-server.intern:/&
167 </pre></blockquote></p>
168
169 <p>The last step to remember is to mount the relevant mount points in
170 tjener.intern by adding them to /etc/fstab, creating the mount
171 directories using mkdir and running "mount -a" to mount them.</p>
172
173 <p>When this is done, your users should be able to access the files on
174 the storage server directly by just visiting the
175 /tjener/nas-server/storage/ directory using any application on any
176 workstation, LTSP client or LTSP server.</p>
177 </div>
178 <div class="tags">
179
180
181 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>.
182
183
184 </div>
185 </div>
186 <div class="padding"></div>
187
188 <div class="entry">
189 <div class="title"><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></div>
190 <div class="date"> 7th March 2014</div>
191 <div class="body"><p>For noen uker siden ble NXCs fri programvarelisenserte
192 NOARK5-løsning
193 <a href="http://www.nuug.no/aktiviteter/20140211-noark/">presentert hos
194 NUUG</a> (video
195 <a href="https://www.youtube.com/watch?v=JCb_dNS3MHQ">på youtube
196 foreløbig</a>), og det fikk meg til å titte litt mer på NOARK5,
197 standarden for arkivhåndtering i det offentlige Norge. Jeg lurer på
198 om denne kjernen kan være nyttig i et par av mine prosjekter, og for ett
199 av dem er det mest aktuelt å lagre epost. Jeg klarte ikke finne noen
200 anbefaling om hvordan RFC 822-formattert epost (aka Internett-epost)
201 burde lagres i NOARK5, selv om jeg vet at noen arkiver tar
202 PDF-utskrift av eposten med sitt epostprogram og så arkiverer PDF-en
203 (eller enda værre, tar papirutskrift og lagrer bildet av eposten som
204 PDF i arkivet).</p>
205
206 <p>Det er ikke så mange formater som er akseptert av riksarkivet til
207 langtidsoppbevaring av offentlige arkiver, og PDF og XML er de mest
208 aktuelle i så måte. Det slo meg at det måtte da finnes en eller annen
209 egnet XML-representasjon og at det kanskje var enighet om hvilken som
210 burde brukes, så jeg tok mot til meg og spurte
211 <a href="http://samdok.com/">SAMDOK</a>, en gruppe tilknyttet
212 arkivverket som ser ut til å jobbe med NOARK-samhandling, om de hadde
213 noen anbefalinger:
214
215 <p><blockquote>
216 <p>Hei.</p>
217
218 <p>Usikker på om dette er riktig forum å ta opp mitt spørsmål, men jeg
219 lurer på om det er definert en anbefaling om hvordan RFC
220 822-formatterte epost (aka vanlig Internet-epost) bør lages håndteres
221 i NOARK5, slik at en bevarer all informasjon i eposten
222 (f.eks. Received-linjer). Finnes det en anbefalt XML-mapping ala den
223 som beskrives på
224 &lt;URL: <a href="https://www.informit.com/articles/article.aspx?p=32074">https://www.informit.com/articles/article.aspx?p=32074</a> &gt;? Mitt
225 mål er at det skal være mulig å lagre eposten i en NOARK5-kjerne og
226 kunne få ut en identisk formattert kopi av opprinnelig epost ved
227 behov.</p>
228 </blockquote></p>
229
230 <p>Postmottaker hos SAMDOK mente spørsmålet heller burde stilles
231 direkte til riksarkivet, og jeg fikk i dag svar derfra formulert av
232 seniorrådgiver Geir Ivar Tungesvik:</p>
233
234 <p><blockquote>
235 <p>Riksarkivet har ingen anbefalinger når det gjelder konvertering fra
236 e-post til XML. Det står arkivskaper fritt å eventuelt definere/bruke
237 eget format. Inklusive da - som det spørres om - et format der det er
238 mulig å re-etablere e-post format ut fra XML-en. XML (e-post)
239 dokumenter må være referert i arkivstrukturen, og det må vedlegges et
240 gyldig XML skjema (.xsd) for XML-filene. Arkivskaper står altså fritt
241 til å gjøre hva de vil, bare det dokumenteres og det kan dannes et
242 utrekk ved avlevering til depot.</p>
243
244 <p>De obligatoriske kravene i Noark 5 standarden må altså oppfylles -
245 etter dialog med Riksarkivet i forbindelse med godkjenning. For
246 offentlige arkiv er det særlig viktig med filene loependeJournal.xml
247 og offentligJournal.xml. Private arkiv som vil forholde seg til Noark
248 5 standarden er selvsagt frie til å bruke det som er relevant for dem
249 av obligatoriske krav.</p>
250 </blockquote></p>
251
252 <p>Det ser dermed ut for meg som om det er et lite behov for å
253 standardisere XML-lagring av RFC-822-formatterte meldinger. Noen som
254 vet om god spesifikasjon i så måte? I tillegg til den omtalt over,
255 har jeg kommet over flere aktuelle beskrivelser (søk på "rfc 822
256 xml", så finner du aktuelle alternativer).</p>
257
258 <ul>
259
260 <li><a href="http://www.openhealth.org/xmtp/">XML MIME Transformation
261 protocol (XMTP)</a> fra OpenHealth, sist oppdatert 2001.</li>
262
263 <li><a href="https://tools.ietf.org/html/draft-klyne-message-rfc822-xml-03">An
264 XML format for mail and other messages</a> utkast fra IETF datert
265 2001.</li>
266
267 <li><a href="http://www.informit.com/articles/article.aspx?p=32074">xMail:
268 E-mail as XML</a> en artikkel fra 2003 som beskriver python-modulen
269 rfc822 som gir ut XML-representasjon av en RFC 822-formattert epost.</li>
270
271 </ul>
272
273 <p>Finnes det andre og bedre spesifikasjoner for slik lagring? Send
274 meg en epost hvis du har innspill.</p>
275 </div>
276 <div class="tags">
277
278
279 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>.
280
281
282 </div>
283 </div>
284 <div class="padding"></div>
285
286 <div class="entry">
287 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Lenker_for_2014_02_28.html">Lenker for 2014-02-28</a></div>
288 <div class="date">28th February 2014</div>
289 <div class="body"><p>Her er noen lenker til tekster jeg har satt pris på å lese de siste
290 månedene. Det er mye om varsleren Edward Snowden, som burde få all
291 hjelp, støtte og beskyttelse Norge kan stille opp med for å ha satt
292 totalitær overvåkning på sakskartet, men også endel annet
293 tankevekkende og interessant.</p>
294
295 <ul>
296
297 <li>2013-12-21
298 <a href="http://www.dagbladet.no/2013/12/21/nyheter/thomas_drake/nsa/overvakning/snowden/30925886/">-
299 NSA tenker som Stasi</a> - Dagbladet.no</li>
300
301 <li>2013-12-19 <a href="http://www.dagensit.no/article2732734.ece">-
302 Staten har ikke rett til å vite alt om deg</a> - DN.no</li>
303
304 <li>2013-12-21
305 <a href="http://www.dagbladet.no/2013/12/21/nyheter/krig_og_konflikter/politikk/utenriks/30961126/">Nye
306 mål for NSAs spionasje avslørt</a> - Dagbladet.no</li>
307
308 <li>2013-12-19
309 <a href="http://www.dagbladet.no/2013/12/19/nyheter/nsa/usa/politikk/barack_obama/30918684/">«NSA
310 bør fjernes fra sin makt til å samle inn metadata fra amerikanske
311 telefonsamtaler»</a> - Dagbladet.no</li>
312
313 <li>2013-12-18
314 <a href="http://www.dagbladet.no/2013/12/18/kultur/meninger/hovedkronikk/debatt/snowden/30901089/">Etterretning,
315 overvåking, frihet og sikkerhet</a> - Dagbladet.no</li>
316
317 <li>2013-12-17
318 <a href="http://www.nrk.no/verden/snowden-vil-ha-asyl-i-brasil-1.11423444">Snowden
319 angriper USA i åpent brev</a> - nrk.no</li>
320
321 <li>2013-12-17
322 <a href="http://www.digi.no/925820/rettslig-nederlag-for-etterretning">Rettslig
323 nederlag for etterretning</a> - digi.no</li>
324
325 <li>2013-12-21
326 <a href="http://www.dagbladet.no/2013/12/21/kultur/meninger/hovedkommentar/kommentar/etterretning/30963284/">Truende
327 nedkjøling</a> - dagbladet.no</li>
328
329 <li>2013-12-20
330 <a href="http://www.aftenposten.no/viten/Matematikk-og-forstaelse-7411849.html">Matematikk
331 og forståelse</a> - aftenposten.no</li>
332
333 <li>2013-10-20
334 <a href="http://www.nrk.no/viten/ny-studie_sovn-reinser-hjernen-var-1.11306106">Vi
335 søv for å reinse hjernen vår, ifølgje ny studie</a> - nrk.no</li>
336
337 <li>2013-12-11
338 <a href="http://www.nrk.no/buskerud/julebaksten-i-vasken-1.11410033">Rotterace
339 i kloakken</a> - nrk.no</li>
340
341 <li>2013-12-30
342 <a href="http://www.aftenposten.no/viten/Apne-brev-og-frie-tanker-7413734.html">Åpne
343 brev og frie tanker</a> - aftenposten.no</li>
344
345 <li>2014-01-12
346 <a href="http://www.aftenposten.no/viten/Stopp-kunnskapsapartheidet-7428229.html">Stopp dagens kunnskapsapartheid!</a> - aftenposten.no</li>
347
348 <li>2014-01-09
349 <a href="http://www.aftenposten.no/nyheter/uriks/EU-rapport-Britisk-og-amerikansk-overvaking-ser-ut-til-a-vare-ulovlig-7428933.html">EU-rapport:
350 Britisk og amerikansk overvåking ser ut til å være ulovlig</a> -
351 aftenposten.no</li>
352
353 <li>2013-10-23 Professor Jan Arild Audestad
354 <a href="http://www.digi.no/924008/advarer-mot-konspirasjonsteori">Advarer
355 mot konspirasjonsteori</a> i digi.no og sier han ikke tror NSA kan
356 avlytte mobiltelefoner, mens han noen måneder senere forteller:</li>
357
358 <li>2014-01-09
359 <a href="http://www.aftenposten.no/nyheter/iriks/--Vi-ble-presset-til-a-svekke-mobilsikkerheten-pa-80-tallet-7410467.html">-
360 Vi ble presset til å svekke mobilsikkerheten på 80-tallet</a> -
361 aftenposten.no</li>
362
363 <li>2014-02-12
364 <a href="http://tv.nrk.no/program/koid20005814/et-moete-med-edward-snowden">Et
365 møte med Edward Snowden</a> - intervju sendt av nrk, tilgjengelig til
366 2015-01-31</li>
367
368 <li>2014-02-17
369 <a href="http://politiken.dk/debat/profiler/jessteinpedersen/ECE2210356/litteraturredaktoeren-helle-thornings-tavshed-om-snowden-er-en-skandale/">Litteraturredaktøren:
370 Helle Thornings tavshed om Snowden er en skandale</a> -
371 politiken.dk</li>
372
373 <li>2014-02-21
374 <a href="http://www.aftenposten.no/meninger/kronikker/Bra-a-ha-en-Storebror-7476734.html">Bra å ha en «Storebror»</a> - aftenposten.no</li>
375
376 <li>2014-02-28
377 <a href="http://johnchristianelden.blogg.no/1393536806_narkotikasiktet_stort.html">"Narkotikasiktet
378 Stortingsmann" - Spillet bak kulissene</a> - John Christian Eldens
379 blogg</li>
380
381 <li>2014-02-28
382 <a href="http://www.aftenposten.no/meninger/Heksejakt-pa-hasjbrukere-7486283.html">Heksejakt
383 på hasjbrukere</a> - aftenposten.no</li>
384
385 </ul>
386 </div>
387 <div class="tags">
388
389
390 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>.
391
392
393 </div>
394 </div>
395 <div class="padding"></div>
396
397 <div class="entry">
398 <div class="title"><a href="http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html">New home and release 1.0 for netgroup and innetgr (aka ng-utils)</a></div>
399 <div class="date">22nd February 2014</div>
400 <div class="body"><p>Many years ago, I wrote a GPL licensed version of the netgroup and
401 innetgr tools, because I needed them in
402 <a href="http://www.skolelinux.org/">Skolelinux</a>. I called the project
403 ng-utils, and it has served me well. I placed the project under the
404 <a href="http://www.hungry.com/">Hungry Programmer</a> umbrella, and it was maintained in our CVS
405 repository. But many years ago, the CVS repository was dropped (lost,
406 not migrated to new hardware, not sure), and the project have lacked a
407 proper home since then.</p>
408
409 <p>Last summer, I had a look at the package and made a new release
410 fixing a irritating crash bug, but was unable to store the changes in
411 a proper source control system. I applied for a project on
412 <a href="https://alioth.debian.org/">Alioth</a>, but did not have time
413 to follow up on it. Until today. :)</p>
414
415 <p>After many hours of cleaning and migration, the ng-utils project
416 now have a new home, and a git repository with the highlight of the
417 history of the project. I published all release tarballs and imported
418 them into the git repository. As the project is really stable and not
419 expected to gain new features any time soon, I decided to make a new
420 release and call it 1.0. Visit the new project home on
421 <a href="https://alioth.debian.org/projects/ng-utils/">https://alioth.debian.org/projects/ng-utils/</a>
422 if you want to check it out. The new version is also uploaded into
423 <a href="http://packages.qa.debian.org/n/ng-utils.html">Debian Unstable</a>.</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/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/Testing_sysvinit_from_experimental_in_Debian_Hurd.html">Testing sysvinit from experimental in Debian Hurd</a></div>
437 <div class="date"> 3rd February 2014</div>
438 <div class="body"><p>A few days ago I decided to try to help the Hurd people to get
439 their changes into sysvinit, to allow them to use the normal sysvinit
440 boot system instead of their old one. This follow up on the
441 <a href="https://teythoon.cryptobitch.de//categories/gsoc.html">great
442 Google Summer of Code work</a> done last summer by Justus Winter to
443 get Debian on Hurd working more like Debian on Linux. To get started,
444 I downloaded a prebuilt hard disk image from
445 <a href="http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz">http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz</a>,
446 and started it using virt-manager.</p>
447
448 <p>The first think I had to do after logging in (root without any
449 password) was to get the network operational. I followed
450 <a href="https://www.debian.org/ports/hurd/hurd-install">the
451 instructions on the Debian GNU/Hurd ports page</a> and ran these
452 commands as root to get the machine to accept a IP address from the
453 kvm internal DHCP server:</p>
454
455 <p><blockquote><pre>
456 settrans -fgap /dev/netdde /hurd/netdde
457 kill $(ps -ef|awk '/[p]finet/ { print $2}')
458 kill $(ps -ef|awk '/[d]evnode/ { print $2}')
459 dhclient /dev/eth0
460 </pre></blockquote></p>
461
462 <p>After this, the machine had internet connectivity, and I could
463 upgrade it and install the sysvinit packages from experimental and
464 enable it as the default boot system in Hurd.</p>
465
466 <p>But before I did that, I set a password on the root user, as ssh is
467 running on the machine it for ssh login to work a password need to be
468 set. Also, note that a bug somewhere in openssh on Hurd block
469 compression from working. Remember to turn that off on the client
470 side.</p>
471
472 <p>Run these commands as root to upgrade and test the new sysvinit
473 stuff:</p>
474
475 <p><blockquote><pre>
476 cat > /etc/apt/sources.list.d/experimental.list &lt;&lt;EOF
477 deb http://http.debian.net/debian/ experimental main
478 EOF
479 apt-get update
480 apt-get dist-upgrade
481 apt-get install -t experimental initscripts sysv-rc sysvinit \
482 sysvinit-core sysvinit-utils
483 update-alternatives --config runsystem
484 </pre></blockquote></p>
485
486 <p>To reboot after switching boot system, you have to use
487 <tt>reboot-hurd</tt> instead of just <tt>reboot</tt>, as there is not
488 yet a sysvinit process able to receive the signals from the normal
489 'reboot' command. After switching to sysvinit as the boot system,
490 upgrading every package and rebooting, the network come up with DHCP
491 after boot as it should, and the settrans/pkill hack mentioned at the
492 start is no longer needed. But for some strange reason, there are no
493 longer any login prompt in the virtual console, so I logged in using
494 ssh instead.
495
496 <p>Note that there are some race conditions in Hurd making the boot
497 fail some times. No idea what the cause is, but hope the Hurd porters
498 figure it out. At least Justus said on IRC (#debian-hurd on
499 irc.debian.org) that they are aware of the problem. A way to reduce
500 the impact is to upgrade to the Hurd packages built by Justus by
501 adding this repository to the machine:</p>
502
503 <p><blockquote><pre>
504 cat > /etc/apt/sources.list.d/hurd-ci.list &lt;&lt;EOF
505 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
506 EOF
507 </pre></blockquote></p>
508
509 <p>At the moment the prebuilt virtual machine get some packages from
510 http://ftp.debian-ports.org/debian, because some of the packages in
511 unstable do not yet include the required patches that are lingering in
512 BTS. This is the completely list of "unofficial" packages installed:</p>
513
514 <p><blockquote><pre>
515 # aptitude search '?narrow(?version(CURRENT),?origin(Debian Ports))'
516 i emacs - GNU Emacs editor (metapackage)
517 i gdb - GNU Debugger
518 i hurd-recommended - Miscellaneous translators
519 i isc-dhcp-client - ISC DHCP client
520 i isc-dhcp-common - common files used by all the isc-dhcp* packages
521 i libc-bin - Embedded GNU C Library: Binaries
522 i libc-dev-bin - Embedded GNU C Library: Development binaries
523 i libc0.3 - Embedded GNU C Library: Shared libraries
524 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
525 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
526 i multiarch-support - Transitional package to ensure multiarch compatibilit
527 i A x11-common - X Window System (X.Org) infrastructure
528 i xorg - X.Org X Window System
529 i A xserver-xorg - X.Org X server
530 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
531 #
532 </pre></blockquote></p>
533
534 <p>All in all, testing hurd has been an interesting experience. :)
535 X.org did not work out of the box and I never took the time to follow
536 the porters instructions to fix it. This time I was interested in the
537 command line stuff.<p>
538 </div>
539 <div class="tags">
540
541
542 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
543
544
545 </div>
546 </div>
547 <div class="padding"></div>
548
549 <div class="entry">
550 <div class="title"><a href="http://people.skolelinux.org/pere/blog/A_fist_full_of_non_anonymous_Bitcoins.html">A fist full of non-anonymous Bitcoins</a></div>
551 <div class="date">29th January 2014</div>
552 <div class="body"><p>Bitcoin is a incredible use of peer to peer communication and
553 encryption, allowing direct and immediate money transfer without any
554 central control. It is sometimes claimed to be ideal for illegal
555 activity, which I believe is quite a long way from the truth. At least
556 I would not conduct illegal money transfers using a system where the
557 details of every transaction are kept forever. This point is
558 investigated in
559 <a href="https://www.usenix.org/publications/login">USENIX ;login:</a>
560 from December 2013, in the article
561 "<a href="https://www.usenix.org/system/files/login/articles/03_meiklejohn-online.pdf">A
562 Fistful of Bitcoins - Characterizing Payments Among Men with No
563 Names</a>" by Sarah Meiklejohn, Marjori Pomarole,Grant Jordan, Kirill
564 Levchenko, Damon McCoy, Geoffrey M. Voelker, and Stefan Savage. They
565 analyse the transaction log in the Bitcoin system, using it to find
566 addresses belong to individuals and organisations and follow the flow
567 of money from both Bitcoin theft and trades on Silk Road to where the
568 money end up. This is how they wrap up their article:</p>
569
570 <p><blockquote>
571 <p>"To demonstrate the usefulness of this type of analysis, we turned
572 our attention to criminal activity. In the Bitcoin economy, criminal
573 activity can appear in a number of forms, such as dealing drugs on
574 Silk Road or simply stealing someone else’s bitcoins. We followed the
575 flow of bitcoins out of Silk Road (in particular, from one notorious
576 address) and from a number of highly publicized thefts to see whether
577 we could track the bitcoins to known services. Although some of the
578 thieves attempted to use sophisticated mixing techniques (or possibly
579 mix services) to obscure the flow of bitcoins, for the most part
580 tracking the bitcoins was quite straightforward, and we ultimately saw
581 large quantities of bitcoins flow to a variety of exchanges directly
582 from the point of theft (or the withdrawal from Silk Road).</p>
583
584 <p>As acknowledged above, following stolen bitcoins to the point at
585 which they are deposited into an exchange does not in itself identify
586 the thief; however, it does enable further de-anonymization in the
587 case in which certain agencies can determine (through, for example,
588 subpoena power) the real-world owner of the account into which the
589 stolen bitcoins were deposited. Because such exchanges seem to serve
590 as chokepoints into and out of the Bitcoin economy (i.e., there are
591 few alternative ways to cash out), we conclude that using Bitcoin for
592 money laundering or other illicit purposes does not (at least at
593 present) seem to be particularly attractive."</p>
594 </blockquote><p>
595
596 <p>These researches are not the first to analyse the Bitcoin
597 transaction log. The 2011 paper
598 "<a href="http://arxiv.org/abs/1107.4524">An Analysis of Anonymity in
599 the Bitcoin System</A>" by Fergal Reid and Martin Harrigan is
600 summarized like this:</p>
601
602 <p><blockquote>
603 "Anonymity in Bitcoin, a peer-to-peer electronic currency system, is a
604 complicated issue. Within the system, users are identified by
605 public-keys only. An attacker wishing to de-anonymize its users will
606 attempt to construct the one-to-many mapping between users and
607 public-keys and associate information external to the system with the
608 users. Bitcoin tries to prevent this attack by storing the mapping of
609 a user to his or her public-keys on that user's node only and by
610 allowing each user to generate as many public-keys as required. In
611 this chapter we consider the topological structure of two networks
612 derived from Bitcoin's public transaction history. We show that the
613 two networks have a non-trivial topological structure, provide
614 complementary views of the Bitcoin system and have implications for
615 anonymity. We combine these structures with external information and
616 techniques such as context discovery and flow analysis to investigate
617 an alleged theft of Bitcoins, which, at the time of the theft, had a
618 market value of approximately half a million U.S. dollars."
619 </blockquote></p>
620
621 <p>I hope these references can help kill the urban myth that Bitcoin
622 is anonymous. It isn't really a good fit for illegal activites. Use
623 cash if you need to stay anonymous, at least until regular DNA
624 sampling of notes and coins become the norm. :)</p>
625
626 <p>As usual, if you use Bitcoin and want to show your support of my
627 activities, please send Bitcoin donations to my address
628 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
629 </div>
630 <div class="tags">
631
632
633 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
634
635
636 </div>
637 </div>
638 <div class="padding"></div>
639
640 <div class="entry">
641 <div class="title"><a href="http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html">New chrpath release 0.16</a></div>
642 <div class="date">14th January 2014</div>
643 <div class="body"><p><a href="http://www.coverity.com/">Coverity</a> is a nice tool to
644 find problems in C, C++ and Java code using static source code
645 analysis. It can detect a lot of different problems, and is very
646 useful to find memory and locking bugs in the error handling part of
647 the source. The company behind it provide
648 <a href="https://scan.coverity.com/">check of free software projects as
649 a community service</a>, and many hundred free software projects are
650 already checked. A few days ago I decided to have a closer look at
651 the Coverity system, and discovered that the
652 <a href="http://www.gnu.org/software/gnash/">gnash</a> and
653 <a href="http://sourceforge.net/projects/ipmitool/">ipmitool</a>
654 projects I am involved with was already registered. But these are
655 fairly big, and I would also like to have a small and easy project to
656 check, and decided to <a href="http://scan.coverity.com/projects/1179">request
657 checking of the chrpath project</a>. It was
658 added to the checker and discovered seven potential defects. Six of
659 these were real, mostly resource "leak" when the program detected an
660 error. Nothing serious, as the resources would be released a fraction
661 of a second later when the program exited because of the error, but it
662 is nice to do it right in case the source of the program some time in
663 the future end up in a library. Having fixed all defects and added
664 <a href="https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel">a
665 mailing list for the chrpath developers</a>, I decided it was time to
666 publish a new release. These are the release notes:</p>
667
668 <p>New in 0.16 released 2014-01-14:</p>
669
670 <ul>
671
672 <li>Fixed all minor bugs discovered by Coverity.</li>
673 <li>Updated config.sub and config.guess from the GNU project.</li>
674 <li>Mention new project mailing list in the documentation.</li>
675
676 </ul>
677
678 <p>You can
679 <a href="https://alioth.debian.org/frs/?group_id=31052">download the
680 new version 0.16 from alioth</a>. Please let us know via the Alioth
681 project if something is wrong with the new release. The test suite
682 did not discover any old errors, so if you find a new one, please also
683 include a test suite check.</p>
684 </div>
685 <div class="tags">
686
687
688 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
689
690
691 </div>
692 </div>
693 <div class="padding"></div>
694
695 <div class="entry">
696 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Dominik_George.html">Debian Edu interview: Dominik George</a></div>
697 <div class="date">25th December 2013</div>
698 <div class="body"><p>The <a href="http://www.skolelinux.org/">Debian Edu / Skolelinux
699 project</a> consist of both newcomers and old timers, and this time I
700 was able to get an interview with a newcomer in the project who showed
701 up on the IRC channel a few weeks ago to let us know about his
702 successful installation of Debian Edu Wheezy in his School. Say hello
703 to <a href="https://www.ohloh.net/accounts/Natureshadow">Dominik
704 George</a>.</p>
705
706 <!-- http://www.dominik-george.de/images/foto.jpg -->
707
708 <p><strong>Who are you, and how do you spend your days?</strong></p>
709
710 <p>I am a 23 year-old student from Germany who has spent half of his
711 life with open source. In "real life", I am, as already mentioned, a
712 student in the fields of Computer Science, Electrical Engineering,
713 Information Technologies and Anglistics. Due to my (only partially
714 voluntary) huge engagement in the open source world, these things are
715 a bit vacant right now however.</p>
716
717 <p>I also have been working as a project teacher at a Gymasnium
718 (public school) for various years now. I took up that work some time
719 around 2005 when still attending that school myself and have continued
720 it until today. I also had been running the (kind of very advanced)
721 network of that school together with a team of very interested and
722 talented students in the age of 11 to 15 years, who took the chance to
723 learn a lot about open source and networking before I left the school
724 to help building another school's informational education concept from
725 scratch.</p>
726
727 <p>That said, one might see me as a kind of "glue" between school kids
728 and the elderly of teachers as well as between the open source
729 ecosystem and the (even more complex) educational ecosystem.</p>
730
731 <p>When I am not busy with open source or education, I like Geocaching
732 and cycling.</p>
733
734 <p><strong>How did you get in contact with the Skolelinux / Debian Edu
735 project?</strong></p>
736
737 <p>I think that happened some time around 2009 when I first attended
738 <a href="http://www.froscon.org">FrOSCon</a> and visited the project
739 booth. I think I wasn't too interested back then because I used to
740 have an attitude of disliking software that does too much stuff on its
741 own. Maybe I was too inexperienced to realise the upsides of an
742 "out-of-the-box" solution ;).</p>
743
744 <p>The first time I actively talked to Skolelinux people was at
745 <a href="http://www.openrheinruhr.de">OpenRheinRuhr</a> 2011 when the
746 BiscuIT project, a home-grewn software used by my school for various
747 really cool things from timetables and class contact lists to lunch
748 ordering, student ID card printing and project elections first got to
749 a stage where it could have been published. I asked the Skolelinux
750 guys running the booth if the project were interested in it and gave a
751 small demonstration, but there wasn't any real feedback and the guys
752 seemed rather uninterested.</p>
753
754 <p>After I left the school where I developed the software, it got
755 mostly lost, but I am now reimplementing it for my new school. I have
756 reusability and compatibility in mind, and I hop there will be a new
757 basis for contributing it to the Skolelinux project ;)!</p>
758
759 <p><strong>What do you see as the advantages of Skolelinux / Debian
760 Edu?</strong></p>
761
762 <p>The most important advantage seems to be that it "just
763 works". After overcoming some minor (but still very annoying) glitches
764 in the installer, I got a fully functional, working school network,
765 without the month-long hassle I experienced when setting all that up
766 from scratch in earlier years. And above that, it rocked - I didn't
767 have any real hardware at hand, because the school was just founded
768 and has no money whatsoever, so I installed a combined server (main
769 server, terminal services and workstation) in a VM on my personal
770 notebook, bridging the LTSP network interface to the ethernet port,
771 and then PXE-booted the Windows notebooks that were lying around from
772 it. I could use 8 clients without any performance issues, by using a
773 tiny little VM on a tiny little notebook. I think that's enough to say
774 that it rocks!</p>
775
776 <p>Secondly, there are marketing reasons. Life's bad, and so no
777 politician will ever permit a setup described as "Debian, an universal
778 operating system, with some really cool educational tools" while they
779 will be jsut fine with "Skolelinux, a single-purpose solution for your
780 school network", even if both turn out to be the very same thing (yes,
781 this is unfair towards the Skolelinux project, and must not be taken
782 too seriously - you get the idea, anyway).</p>
783
784 <p><strong>What do you see as the disadvantages of Skolelinux / Debian
785 Edu?</strong></p>
786
787 <p>I have not been involved with Skolelinux long enough to really
788 answer this question in a fair way. Thus, please allow me to put it in
789 other words: "What do you expect from Skolelinux to keep liking it?" I
790 can list a few points about that:</p>
791
792 <ul>
793
794 <li>always strive to get all things integrated into Debian upstream
795 <li>be open to discussion about changes and the like, even with newcomers
796 <li>be helpful at being helpful ;)
797
798 </ul>
799
800 <p>I'm really sorry I cannot say much more about that :(!</p>
801
802 <p><strong>Which free software do you use daily?</strong></p>
803
804 <p>First of all, all software I use is free and open. I have abandoned
805 all non-free software (except for firmware on my darned phone) this
806 year.</p>
807
808 <p>I run Debian GNU/Linux on all PC systems I use. On that, I mostly
809 run text tools. I use
810 <a href="https://www.mirbsd.org/mksh.htm">mksh</a> as shell,
811 <a href="https://www.mirbsd.org/jupp.htm">jupp</a> as very advanced
812 text editor (I even got the developer to help me write a script/macro
813 based full-featured student management software with the two),
814 <a href="http://mcabber.com/">mcabber</a> for XMPP and
815 <a href="http://www.irssi.org/">irssi</a> for IRC. For that overly
816 coloured world called the WWW, I use
817 <a href="https://www.mozilla.org/en-US/firefox/new/">Iceweasel
818 (Firefox)</a>. Oh, and <a href="http://www.mutt.org/">mutt</a> for
819 e-mail.</p>
820
821 <p>However, while I am personally aware of the fact that text tools
822 are more efficient and powerful than anything else, I also use (or at
823 least operate) some tools that are suitable to bring open source to
824 kids. One of these things is <a href="http://jappix.org/">Jappix</a>,
825 which I already introduced to some kids even before they got aware of
826 Facebook, making them see for themselves that they do not need
827 Facebook now ;).</p>
828
829 <p><strong>Which strategy do you believe is the right one to use to
830 get schools to use free software?</strong></p>
831
832 <p>Well, that's a two-sided thing. One side is what I believe, and one
833 side is what I have experienced.</p>
834
835 <p>I believe that the right strategy is showing them the benefits. But
836 that won't work out as long as the acceptance of free alternatives
837 grows globally. What I mean is that if all the kids are almost forced
838 to use Windows, Facebook, Skype, you name it at home, they will not
839 see why they would want to use alternatives at school. I have seen
840 students take seat in front of a fully-functional, modern Debian
841 desktop that could do anything their Windows at home could do, and
842 they jsut refused to use it because "Linux sucks". It is something
843 that makes the council of our city spend around 600000 € to buy
844 software - not including hardware, mind you - for operating school
845 networks, and for installing a system that, as has been proved, does
846 not work. For those of you readers who are good at maths, have you
847 already found out how many lives could have been saved with that money
848 if we had instead used it to bring education to parts of the world
849 that need it? I have, and found it to be nothing less dramatic than
850 plain criminal.</p>
851
852 <p>That said, the only feasible way appears to be the bottom up
853 method. We have to bring free software to kids and parents. I have
854 founded an association named
855 <a href="https://www.teckids.org">Teckids</a> here in Germany that does
856 just that. We organise several events for kids and adolescents in the
857 area of free and open source software, for example the
858 <a href="http://kids.froscon.org">FrogLabs</a>, which share staff with
859 Teckids and are the youth programme of
860 <a href="http://www.froscon.org">the Free and Open Source Software
861 Conference (FrOSCon)</a>. We do a lot more than most other conferences
862 - this year, we first offered the FrogLabs as a holiday camp for kids
863 aged 10 to 16. It was a huge success, with approx. 30 kids taking part
864 and learning with and about free software through a whole weekend. All
865 of us had a lot of fun, and the results were really exciting.</p>
866
867 <p>Apart from that, we are preparing a campaign that is supposed to bring
868 the message of free alternatives to stuff kids use every day to them and
869 their parents, e.g. the use of Jabber / Jappix instead of Facebook and
870 Skype. To make that possible, we are planning to get together a team of
871 clever kids who understand very well what their peers need and can bring
872 it across to them. So we will have a peer-driven network of adolescents
873 who teach each other and collect feedback from the community of minors.
874 We then take that feedback and our own experience to work closely with
875 open source projects, such as Skolelinux or Jappix, at improving their
876 software in a way that makes it more and more attractive for the target
877 group. At least I hope that we will have good cooperation with
878 Skolelinux in the future ;)!</p>
879
880 <p>So in conclusion, what I believe is that, if it weren't for the world
881 being so bad, it should be very clear to the political decision makers
882 that the only way to go nowadays is free software for various reasons,
883 but I have learnt that the only way that seems to work is bottom up.</p>
884
885 <!--
886
887 > * Who should be interviewed with this questions in the future?
888
889 That's probably the hardest question of them all, as I do not know the
890 community. However, I would be willing to do the following:
891
892 <li>Run an interview with a German headteacher who is very open to
893 free software, and also prefers it, but cannot really use it because
894 of the decision makers above;
895 <li>Run interviews with some kids, both with and without previous
896 knowledge about free software
897
898 If that is wanted, just let me know ;).
899
900 -->
901 </div>
902 <div class="tags">
903
904
905 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/intervju">intervju</a>.
906
907
908 </div>
909 </div>
910 <div class="padding"></div>
911
912 <div class="entry">
913 <div class="title"><a href="http://people.skolelinux.org/pere/blog/Dugnadsnett_for_alle_stiller_p__Oslo_Maker_Faire_i_januar_2014.html">Dugnadsnett for alle stiller på Oslo Maker Faire i januar 2014</a></div>
914 <div class="date">10th December 2013</div>
915 <div class="body"><p>Helga 18. og 19. januar 2014 arrangeres
916 <a href="http://makerfaireoslo.no/no/program/dugnadsnett">Oslo Maker
917 Faire</a>, og <a href="http://www.dugnadsnett.no/">Dugnadsnett for
918 alle</a> har fått plass! Planen er å ha et bord med en plakat der vi
919 forteller om hva Dugnadsnett for alle er for noe, og et lite verksted
920 der vi hjelper folk som er interessert i å få opp sin egen mesh-node.
921 Jeg gleder meg til å se hvordan prosjektet blir mottatt der.</p>
922
923 <p>Målet med dugnadsnett for alle i Oslo er å få på plass et datanett
924 for kommunikasjon ved hjelp av radio-repeaterstasjoner (kalt
925 mesh-noder) som gjør at en kan direkte kommunisere med slekt, venner
926 og bekjente i Oslo via andre som deltar i dugnadsnettet, samt gjøre
927 det mulig komme ut på internett via dugnadsnettet. Første delmål er å
928 kunne sende SMS-meldinger vha. IP-telefoni løsningen
929 <a href="http://www.servalproject.org/">Serval project</a> mellom
930 deltagerne i Dugnadsnett for alle i Oslo. Formålet er å ta tilbake
931 kontrollen over egen nett-infrastruktur og gjøre det dyrere å bedrive
932 massiv innsamling av informasjon om borgernes bruk av datanett.</p>
933
934 <p>Høres dette interessant ut? Bli med på prosjektet, fortell oss
935 hvor du kunne tenke deg å sette opp en radio-repeater (slik at folk i
936 nærheten kan finne hverandre ved hjelp av
937 <a href="http://flynor.net/mesh/mesh.php">kartet over planlagte og
938 eksisterende radio-repeatere</A>), bli med på epostlisten
939 <a href="http://lists.nuug.no/mailman/listinfo/dugnadsnett">dugnadsnett
940 (at) nuug.no</a> og stikk innom
941 <a href="irc://irc.freenode.net/#dugnadsnett.no">IRC-kanalen
942 #dugnadsnett.no</a>. Så langt er det planlagt over 40
943 radio-repeatere, med VPN-forbindelser via Internet for å la de delene
944 av nettet som ikke når hverandre via radio kunne snakke med hverandre
945 likevel.</p>
946 </div>
947 <div class="tags">
948
949
950 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
951
952
953 </div>
954 </div>
955 <div class="padding"></div>
956
957 <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>
958 <div id="sidebar">
959
960
961
962 <h2>Archive</h2>
963 <ul>
964
965 <li>2014
966 <ul>
967
968 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
969
970 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
971
972 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (3)</a></li>
973
974 </ul></li>
975
976 <li>2013
977 <ul>
978
979 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
980
981 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
982
983 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
984
985 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
986
987 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
988
989 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
990
991 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
992
993 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
994
995 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
996
997 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
998
999 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1000
1001 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1002
1003 </ul></li>
1004
1005 <li>2012
1006 <ul>
1007
1008 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1009
1010 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1011
1012 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1013
1014 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1015
1016 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1017
1018 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1019
1020 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1021
1022 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1023
1024 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1025
1026 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1027
1028 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1029
1030 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1031
1032 </ul></li>
1033
1034 <li>2011
1035 <ul>
1036
1037 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1038
1039 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1040
1041 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1042
1043 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1044
1045 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1046
1047 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1048
1049 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1050
1051 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1052
1053 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1054
1055 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1056
1057 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1058
1059 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1060
1061 </ul></li>
1062
1063 <li>2010
1064 <ul>
1065
1066 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1067
1068 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1069
1070 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1071
1072 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1073
1074 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1075
1076 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1077
1078 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1079
1080 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1081
1082 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1083
1084 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1085
1086 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1087
1088 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1089
1090 </ul></li>
1091
1092 <li>2009
1093 <ul>
1094
1095 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1096
1097 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1098
1099 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1100
1101 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1102
1103 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1104
1105 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1106
1107 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1108
1109 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1110
1111 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1112
1113 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1114
1115 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1116
1117 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1118
1119 </ul></li>
1120
1121 <li>2008
1122 <ul>
1123
1124 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1125
1126 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1127
1128 </ul></li>
1129
1130 </ul>
1131
1132
1133
1134 <h2>Tags</h2>
1135 <ul>
1136
1137 <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1138
1139 <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1140
1141 <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1142
1143 <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1144
1145 <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
1146
1147 <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (14)</a></li>
1148
1149 <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1150
1151 <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1152
1153 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (95)</a></li>
1154
1155 <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (145)</a></li>
1156
1157 <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1158
1159 <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
1160
1161 <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1162
1163 <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (238)</a></li>
1164
1165 <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
1166
1167 <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1168
1169 <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
1170
1171 <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (6)</a></li>
1172
1173 <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1174
1175 <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (39)</a></li>
1176
1177 <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
1178
1179 <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1180
1181 <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1182
1183 <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (7)</a></li>
1184
1185 <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1186
1187 <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (7)</a></li>
1188
1189 <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (25)</a></li>
1190
1191 <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (241)</a></li>
1192
1193 <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (161)</a></li>
1194
1195 <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (10)</a></li>
1196
1197 <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1198
1199 <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (45)</a></li>
1200
1201 <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (69)</a></li>
1202
1203 <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1204
1205 <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1206
1207 <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1208
1209 <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1210
1211 <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1212
1213 <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1214
1215 <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1216
1217 <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (35)</a></li>
1218
1219 <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1220
1221 <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1222
1223 <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
1224
1225 <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1226
1227 <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1228
1229 <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (22)</a></li>
1230
1231 <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1232
1233 <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1234
1235 <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (39)</a></li>
1236
1237 <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1238
1239 <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (29)</a></li>
1240
1241 </ul>
1242
1243
1244 </div>
1245 <p style="text-align: right">
1246 Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1247 </p>
1248
1249 </body>
1250 </html>