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/Debian_Edu___some_ideas_for_the_future_versions.html">Debian Edu - some ideas for the future versions</a></div>
  24       <div class="date">11th June 2012</div>
  25       <div class="body"><p>During my work on Debian Edu based on Squeeze, I came across some
  26 issues that should be addressed in the Wheezy release.  I finally
  27 found time to wrap up my notes and provide quick summary of what I
  28 found, with a bit explanation.</p>
  29
  30 <p><ul>
  31
  32 <li>We need to rewrite our package installation framework, as tasksel
  33 changed from using tasksel tasks to using meta packages (aka packages
  34 with dependencies like our education-* packages), and our installation
  35 system depend on tasksel tasks in
  36 /usr/share/tasksel/debian-edu-tasks.desc for package
  37 installation.</li>
  38
  39 <li>Enable Kerberos login for more services.  Now with the Kerberos
  40 foundation in place, we should use it to get single sign on with more
  41 services, and avoiding unneeded password / login questions.  We should
  42 at least try to enable it for these services:
  43 <ul>
  44
  45   <li>CUPS for admins to add/configure printers and users when using
  46     quotas.</li>
  47   <li>Nagios for admins checking the system status.</li>
  48   <li>GOsa for admins updating LDAP and users changing their passwords.</li>
  49   <li>LDAP for admins updating LDAP.</li>
  50   <li>Squid for users when exam mode / filtering is active.</li>
  51   <li>ssh for admins and users to save a password prompt.</li>
  52
  53 </ul></li>
  54
  55 <li>When we move GOsa to use Kerberos instead of LDAP bind to
  56 authenticate users, we should try to block or at least limit access to
  57 use LDAP bind for authentication, to ensure Kerberos is used when it
  58 is intended, and nothing fall back to using the less safe LDAP bind</li>
  59
  60 <li>Merge debian-edu-config and debian-edu-install.  The split made
  61 sense when d-e-install did a lot more, but these days it is just an
  62 inconvenience when we update the debconf preseeding values.</li>
  63
  64 <li>Fix partman-auto to allow us to abort the installation before
  65 touching the disk if the disk is too small.  This is
  66 <a href="http://bugs.debian.org/653305">BTS report #653305</a> and the
  67 d-i developers are fine with the patch and someone just need to apply
  68 it and upload.</li>
  69
  70 <li>Adjust to new LTSP framework (boot time config instead of install
  71 time config).  LTSP changed its design, and our hooks to install
  72 packages and update the configuration is most likely not going to work
  73 in Wheezy.
  74
  75 <li>Consider switching to NBD instead of NFS for LTSP root, to allow
  76 the Kernel to cache files in its normal file cache, possibly speeding
  77 up KDE login on slow networks.</li>
  78
  79 <li>Make it possible to create expired user passwords that need to
  80 change on first login.  This is useful when handing out password on
  81 paper, to make sure only the user know the password.  This require
  82 fixes to the PAM handling of kdm and gdm.</li>
  83
  84 <li>Make GUI for adding new machines automatically from sitesummary.
  85 The current command line script is not very friendly to people most
  86 familiar with GUIs.  This should probably be integrated into GOsa to
  87 have it available where the admin will be looking for it..</li>
  88
  89 <li>We should find way for Nagios to check that the DHCP service
  90 actually is working (as in handling out IP addresses).  None of the
  91 Nagios checks I have found so far have been working for me.</li>
  92
  93 <li>We should switch from libpam-nss-ldapd to sssd for all profiles
  94 using LDAP, and not only on for roaming workstations, to have less
  95 packages to configure and consistent setup across all profiles.</li>
  96
  97 <li>We should configure Kerberos to update LDAP and Samba password
  98 when changing password using the Kerberos protocol.  The hook was
  99 requested in <a href="http://bugs.debian.org/588968">BTS report
 100 #588968</a> and is now available in Wheezy.  We might need to write a
 101 MIT Kerberos plugin in C to get this.</li>
 102
 103 <li>We should clean up the set of applications installed by default.
 104 <ul>
 105
 106 <li>reduce the number of chemistry visualisers</li>
 107 <li>consider dropping xpaint</li>
 108 <li>and probably more?</li>
 109 </ul></li>
 110
 111 <li>Some hardware need external firmware to work properly.  This is
 112 mostly the case for WiFi network cards, but there are some other
 113 examples too.  For popular laptops to work out of the box, such
 114 firmware need to be installed from non-free, and we should provide
 115 some GUI to do this.  Ubuntu already have this implemented, and we
 116 could consider using their packages.  At the moment we have some
 117 command line script to do this (one for the running system, another
 118 for the LTSP chroot).</li>
 119
 120
 121 <li>In Squeeze, we provide KDE, Gnome and LXDE as desktop options.  We
 122 should extend the list to Xfce and Sugar, and preferably find a way to
 123 install several and allow the admin or the user to select which one to
 124 use.</li>
 125
 126 <li>The golearn tool from the goplay package make it easy to check out
 127 interesting educational packages.  We should work on the package
 128 tagging in Debian to ensure it represent all the useful educational
 129 packages, and extend the tool to allow it to use packagekit to install
 130 new applications with a simple mouse click.</li>
 131
 132 <li>The Squeeze version got half a exam solution already in place,
 133 with the introduction of iptable based network blocking, but for it to
 134 be a complete exam solution the Squid proxy need to enable
 135 filtering/blocking as well when the exam mode is enabled.  We should
 136 implement a way to easily enable this for the schools that want it,
 137 instead of the "it is documented" method of today.</li>
 138
 139 <li>A feature used in several schools is the ability for a teacher to
 140 "take over" the desktop of individual or all computers in the room.
 141 There are at least three implementations,
 142 <a href="italc.sourceforge.net/">italc</a>,
 143 <a href="http://www.itais.net/help/en/">controlaula</a> og
 144 <a href="http://www.epoptes.org/">epoptes</a> and we should pick one of
 145 them and make it trivial to set it up in a school.  The challenges is
 146 how to distribute crypto keys and how to group computers in one room
 147 and how to set up which machine/user can control the machines in a
 148 given room.</li>
 149
 150 <li>Tablets and surf boards are getting more and more popular, and we
 151 should look into providing a good solution for integrating these into
 152 the Debian Edu network.  Not quite sure how.  Perhaps we should
 153 provide a installation profile with better touch screen support for
 154 them, or add some sync services to allow them to exchange
 155 configuration and data with the central server.  This should be
 156 investigated.</li>
 157
 158 </ul></p>
 159
 160 <p>I guess we will discover more as we continue to work on the Wheezy
 161 version.</p>
 162 </div>
 163       <div class="tags">
 164
 165
 166         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>.
 167
 168
 169       </div>
 170     </div>
 171     <div class="padding"></div>
 172
 173     <div class="entry">
 174       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Litt_statistikk_fra_Offentlig_Elektronisk_postjournal.html">Litt statistikk fra Offentlig Elektronisk postjournal</a></div>
 175       <div class="date">10th June 2012</div>
 176       <div class="body"><p>De siste månedene har jeg sammen med andre i NUUG jobbet med å
 177 gjøre det enklere å få innsyn i offentlige dokumenter, og dette
 178 inkluderer å gjøre postjournaler enklere tilgjengelig for maskinell
 179 analyse og søk.  I den forbindelse tok jeg i dag å tittet litt på
 180 <a href="http://www.oep.no/">Offentlig Elektronisk Postjournal
 181 (OEP)</a>, FAD/DIFIs fellesløsning for departementer og statlige
 182 etater.</p>
 183
 184 <p>Her er antall oppføringer pr. måned det siste året,
 185 <a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=htmltable&name=postliste-oep&query=select%20strftime(%22%25Y-%25m%22%2C%20%60recordpublishdate%60)%20as%20oeppubmonth%2C%20count(*)%20from%20%60swdata%60%20group%20by%20oeppubmonth%20order%20by%20oeppubmonth">summert
 186 opp</a> ved hjelp av
 187 <a href="https://scraperwiki.com/scrapers/postliste-oep/">en
 188 Scraperwiki-database</a>.  Merk at denne Scraperwikien har
 189 ytelsesproblemer pga. mengden data. </p>
 190
 191 <p><table border="1">
 192 <tr><th>Måned</th><th>Antall</th></tr>
 193 <tr><td>2011-07</td><td>164355</td></tr>
 194 <tr><td>2011-08</td><td>153662</td></tr>
 195 <tr><td>2011-09</td><td>173134</td></tr>
 196 <tr><td>2011-10</td><td>170665</td></tr>
 197 <tr><td>2011-11</td><td>198409</td></tr>
 198 <tr><td>2011-12</td><td>175908</td></tr>
 199 <tr><td>2012-01</td><td>206875</td></tr>
 200 <tr><td>2012-02</td><td>202862</td></tr>
 201 <tr><td>2012-03</td><td>204225</td></tr>
 202 <tr><td>2012-04</td><td>207931</td></tr>
 203 <tr><td>2012-05</td><td>223754</td></tr>
 204 </table></p>
 205
 206 <p>Det er også interessant å se hvor ofte ulike etater sender inn sine
 207 journaloppføringer til OEP.  OEP inneholder en liste med sist
 208 innrapporteringsdato for alle som sender til OEP, og ved å se når og
 209 hvor ofte det blir sendt inn fra etatene kan
 210 <a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=htmltable&name=postliste-oep-deliverydates&query=select%20agency%2C%0A(julianday(datetime('now'))%20-%20%0A%20julianday(min(%60deliverydate%60)))%2Fcount(*)%20as%20dayfreq%2C%0A%20count(*)%0Afrom%20%60swdata%60%20group%20by%20agency%20order%20by%20dayfreq%20desc">frekvensen
 211 beregnes</a>.  Her er bunnlista, dvs. de som leverer mer enn hver 10
 212 dag beregnet fra
 213 <a href="https://scraperwiki.com/scrapers/postliste-oep-deliverydates/">en
 214 Scraperwiki-database</a>:</p>
 215
 216 <p><table border="1">
 217
 218 <tr> <th>Etat</th> <th>Frekvens</th> <th>Leveringer</th> </tr>
 219 <tr> <td>Norges geologiske undersøkelse</td> <td>83.7527546296</td> <td>1</td> </tr>
 220 <tr> <td>Medietilsynet</td> <td>33.7527546296</td> <td>1</td> </tr>
 221 <tr> <td>Departementenes servicesenter</td> <td>23.8763773148</td> <td>2</td> </tr>
 222 <tr> <td>Kunnskapsdepartementet</td> <td>15.8763773148</td> <td>2</td> </tr>
 223 <tr> <td>Kompetansesenter for distriktsutvikling</td> <td>15.3763773148</td> <td>2</td> </tr>
 224 <tr> <td>Toll- og avgiftsdirektoratet</td> <td>15.3763773148</td> <td>2</td> </tr>
 225 <tr> <td>Fredskorpset</td> <td>12.5842515432</td> <td>3</td> </tr>
 226 <tr> <td>Statens legemiddelverk</td> <td>12.1881886574</td> <td>4</td> </tr>
 227 <tr> <td>Utlendingsnemnda</td> <td>11.5842515432</td> <td>3</td> </tr>
 228 <tr> <td>Politidirektoratet</td> <td>10.9175848765</td> <td>3</td> </tr>
 229 <tr> <td>Skattedirektoratet</td> <td>10.9175848765</td> <td>3</td> </tr>
 230 <tr> <td>Statens innkrevingssentral</td> <td>10.5842515432</td> <td>3</td> </tr>
 231 <tr> <td>Barne-, ungdoms- og familiedirektoratet</td> <td>10.2509182099</td> <td>3</td> </tr>
 232 <tr> <td>Kunst i offentlige rom</td> <td>10.2509182099</td> <td>3</td> </tr>
 233
 234 </table></p>
 235
 236 <p>En kan beregne lignende frekvenser ved å sammenligne
 237 journalføringsdato med publiseringsdato for hver enkelt oppføring i
 238 OEP, men den lenken legger jeg ikke ved her for å unngå at
 239 søkemotorroboter begynner å overbelaste Scraperwiki-databasen.</p>
 240
 241 <p>Jeg har spurt Norges geologiske undersøkelse om hvorfor de leverer
 242 så sjelden, og det kommer av at de har problemer etter oppgradering av
 243 arkivsystemet sitt og jobber med å fikse det slik at de kan gå tilbake
 244 til å levere hver uke.  Har ikke undersøkt noen av de andre.</p>
 245 </div>
 246       <div class="tags">
 247
 248
 249         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>.
 250
 251
 252       </div>
 253     </div>
 254     <div class="padding"></div>
 255
 256     <div class="entry">
 257       <div class="title"><a href="http://people.skolelinux.org/pere/blog/TV_with_face_recognition__for_improved_viewer_experience.html">TV with face recognition, for improved viewer experience</a></div>
 258       <div class="date"> 9th June 2012</div>
 259       <div class="body"><p>Slashdot got a story about Intel planning a
 260 <a href="http://entertainment.slashdot.org/story/12/06/09/0012247/intel-to-launch-tv-service-with-facial-recognition-by-end-of-the-year">TV
 261 with face recognition</a> to recognise the viewer, and it occurred to
 262 me that it would be more interesting to turn it around, and do face
 263 recognition on the TV image itself.  It could let the viewer know who
 264 is present on the screen, and perhaps look up their credibility,
 265 company affiliation, previous appearances etc for the viewer to better
 266 evaluate what is being said and done.  That would be a feature I would
 267 be willing to pay for.</p>
 268
 269 <p>I would not be willing to pay for a TV that point a camera on my
 270 household, like the big brother feature apparently proposed by Intel.
 271 It is the telescreen idea fetched straight out of the book
 272 <a href="http://gutenberg.net.au/ebooks01/0100021.txt">1984 by George
 273 Orwell</a>.</p>
 274 </div>
 275       <div class="tags">
 276
 277
 278         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>.
 279
 280
 281       </div>
 282     </div>
 283     <div class="padding"></div>
 284
 285     <div class="entry">
 286       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Web_service_to_look_up_HP_and_Dell_computer_hardware_support_status.html">Web service to look up HP and Dell computer hardware support status</a></div>
 287       <div class="date"> 6th June 2012</div>
 288       <div class="body"><p>A few days ago
 289 <a href="http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html">I
 290 reported how to get</a> the support status out of Dell using an
 291 unofficial and undocumented SOAP API, which I since have found out was
 292 <a href="http://lists.us.dell.com/pipermail/linux-poweredge/2012-February/045959.html">discovered
 293 by Daniel De Marco in february</a>.  Combined with my web scraping
 294 code for HP, Dell and IBM
 295 <a href="http://people.skolelinux.org/pere/blog/Checking_server_hardware_support_status_for_Dell__HP_and_IBM_servers.html">from
 296 2009</a>, I got inspired and wrote
 297 <a href="https://views.scraperwiki.com/run/computer-hardware-support-status/">a
 298 web service</a> based on Scraperwiki to make it easy to look up the
 299 support status and get a machine readable result back.</p>
 300
 301 <p>This is what it look like at the moment when asking for the JSON
 302 output:
 303
 304 <blockquote><pre>
 305 % GET <a href="https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&vendor=Dell&servicetag=2v1xwn1">https://views.scraperwiki.com/run/computer-hardware-support-status/?format=json&vendor=Dell&servicetag=2v1xwn1</a>
 306 supportstatus({"servicetag": "2v1xwn1", "warrantyend": "2013-11-24", "shipped": "2010-11-24", "scrapestamputc": "2012-06-06T20:26:56.965847", "scrapedurl": "http://143.166.84.118/services/assetservice.asmx?WSDL", "vendor": "Dell", "productid": ""})
 307 %
 308 </pre></blockquote>
 309
 310 <p>It currently support Dell and HP, and I am hoping for help to add
 311 support for other vendors.  The python source is available on
 312 Scraperwiki and I welcome help with adding more features.</p>
 313 </div>
 314       <div class="tags">
 315
 316
 317         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>.
 318
 319
 320       </div>
 321     </div>
 322     <div class="padding"></div>
 323
 324     <div class="entry">
 325       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Kommentar_til_artikkel_i_Adresseavisa_som_omtaler_FiksGataMi.html">Kommentar til artikkel i Adresseavisa som omtaler FiksGataMi</a></div>
 326       <div class="date"> 2nd June 2012</div>
 327       <div class="body"><p>Jeg oppdaget nylig en
 328 <a href="http://www.adressa.no/nyheter/trondheim/article1831198.ece">artikkel
 329 i Adresseavisa</a> i Trondheim som nevner FiksGataMi, og der Trondheim
 330 kommune ser ut til å fortelle at de ikke følger forvaltningslovens
 331 krav ved mottak av meldinger sendt inn via FiksGataMi.  La derfor
 332 nettopp inn denne kommentaren til artikkelen:<p>
 333
 334 <p><blockquote>
 335
 336 <p>Her er en liten faktaoppdatering om FiksGataMi-tjenesten, da noen
 337 ser ut til å ha misforstått hvordan den fungerer.</p>
 338
 339 <p>FiksGataMi er et privat initiativ opprettet og drevet av
 340 medlemsforeningen NUUG.  FiksGataMi tar imot meldinger om feil i
 341 offentlig infrastruktur, og sender meldingen skriftlig videre på vegne
 342 av innmelder til aktuell aktør i det offentlige, det være seg kommune,
 343 fylke eller vegvesenregion.  Offentlig etat blir valgt ut fra
 344 geografisk plassering og kategori valgt av innsender.  Offentlige
 345 etater er i følge forvaltningsloven pliktig å følge opp og besvare
 346 skriftlige henvendelser, og hvis noen av mottakerne ikke gjør dette
 347 kan en klage på lovbrudd i det offentlige.  FiksGataMi fungerer dermed
 348 som en slags epostklient for innbyggerne der kopi av innsendte
 349 meldinger gjøres tilgjengelig og knyttes til kartplassering for enkel
 350 gjenfinning.  Å sende inn nye problemrapporter via FiksGataMi er
 351 dermed ikke avhengig av at kommunen aktivt må følge med på meldinger
 352 hos FiksGataMi, da de får dem tilsendt på sine offisielle
 353 epostmottakspunkter.  Hvorvidt noe blir fikset og om innbyggerne er
 354 opp til mottaker av meldingene.  For Trondheim kommune er
 355 mottaksadressen bydrift.vegdrift@trondheim.kommune.no, en adresse jeg
 356 inntil jeg leste denne artikkelen trodde ble håndtert i henhold til
 357 forvaltningslovens krav.</p>
 358
 359 <p>Kan ellers fortelle at 57 kommuner lenker til FiksGataMi fra sine
 360 nettsider, og at 37 % (4182 av 11266 ) av problemrapportene sendt inn
 361 via FiksGataMi er markert som løst i løsningen.  Trondheim kommune har
 362 fått tilbud om å få rapportene levert på datamaskinlesbart format i
 363 stedet for epost, men har ikke takket ja så langt.</p>
 364
 365 <p>Vennlig hilsen Petter Reinholdtsen, en av NUUG-folkene bak FiksGataMi.no</p>
 366
 367 </blockquote></p>
 368
 369 <p>Det høres for meg ut som om innbyggerne i Trondheim burde klage på
 370 kommunens potensielle lovbrudd.</p>
 371 </div>
 372       <div class="tags">
 373
 374
 375         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
 376
 377
 378       </div>
 379     </div>
 380     <div class="padding"></div>
 381
 382     <div class="entry">
 383       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Mike_Gabriel.html">Debian Edu interview: Mike Gabriel</a></div>
 384       <div class="date"> 2nd June 2012</div>
 385       <div class="body"><p>Back in 2010, Mike Gabriel showed up on the
 386 <a href="http://www.skolelinux.org/">Debian Edu and Skolelinux</a>
 387 mailing list.  He quickly proved to be a valuable developer, and
 388 thanks to his tireless effort we now have Kerberos integrated into the
 389 <a href="http://www.debian.org/News/2012/20120311.html">Debian Edu
 390 Squeeze</a> version.</p>
 391
 392 <p><strong>Who are you, and how do you spend your days?</strong></p>
 393
 394 <p>My name is Mike Gabriel, I am 38 years old and live near Kiel,
 395 Schleswig-Holstein, Germany. I live together with a wonderful partner
 396 (Angela Fuß) and two own children and two bonus children (contributed
 397 by Angela).</p>
 398
 399 <p>During the day I am part-time employed as a system administrator
 400 and part-time working as an IT consultant. The consultancy work
 401 touches free software topics wherever and whenever possible. During
 402 the nights I am a free software developer. In the gaps I also train in
 403 becoming an osteopath.</p>
 404
 405 <p>Starting in 2010 we (Andreas Buchholz, Angela Fuß, Mike Gabriel)
 406 have set up a free software project in the area of Kiel that aims at
 407 introducing free software into schools. The project's name is
 408 "IT-Zukunft Schule" (IT future for schools). The project links IT
 409 skills with communication skills.</p>
 410
 411 <p><strong>How did you get in contact with the Skolelinux/Debian Edu
 412 project?</strong></p>
 413
 414 <p>While preparing our own customised Linux distribution for
 415 "IT-Zukunft Schule" we were repeatedly asked if we really wanted to
 416 reinvent the wheel. What schools really need is already available,
 417 people said.  From this impulse we started evaluating other Linux
 418 distributions that target being used for school networks.</p>
 419
 420 <p>At the end we short-listed two approaches and compared them: a
 421 commercial Linux distribution developed by a company in Bremen,
 422 Germany, and Skolelinux / Debian Edu. Between 12/2010 and 03/2011 we
 423 went to several events and met people being responsible for marketing
 424 and development of either of the distributions. Skolelinux / Debian
 425 Edu was by far much more convincing compared to the other product that
 426 got short-listed beforehand--across the full spectrum. What was most
 427 attractive for me personally: the perspective of collaboration within
 428 the developmental branch of the Debian Edu project itself.</p>
 429
 430 <p>In parallel with this, we talked to many local and not-so-local
 431 people.  People teaching at schools, headmasters, politicians, data
 432 protection experts, other IT professionals.</p>
 433
 434 <p>We came to two conclusions:</p>
 435
 436 <p>First, a technical conclusion: What schools need is available in
 437 bits and pieces here and there, and none of the solutions really fit
 438 by 100%. Any school we have seen has a very individual IT setup
 439 whereas most of each school's requirements could mapped by a standard
 440 IT solution.  The requirement to this IT solution is flexibility and
 441 customisability, so that individual adaptations here and there are
 442 possible.  In terms of re-distributing and rolling out such a
 443 standardised IT system for schools (a system that is still to some
 444 degree customisable) there is still a lot of work to do here
 445 locally. Debian Edu / Skolelinux has been our choice as the starting
 446 point.</p>
 447
 448 <p>Second, a holistic conclusion: What schools need does not exist at
 449 all (or we missed it so far). There are several technical solutions
 450 for handling IT at schools that tend to make a good impression. What
 451 has been missing completely here in Germany, though, is the enrolment
 452 of people into using IT and teaching with IT. "IT-Zukunft Schule"
 453 tries to provide an approach for this.</p>
 454
 455 <p>Only some schools have some sort of a media concept which explains,
 456 defines and gives guidance on how to use IT in class. Most schools in
 457 Northern Germany do not have an IT service provider, the school's IT
 458 equipment is managed by one or (if the school is lucky) two (admin)
 459 teachers, most of the workload these admin teachers get done in there
 460 spare time.</p>
 461
 462 <p>We were surprised that only a very few admin teachers were
 463 networked with colleagues from other schools. Basically, every school
 464 here around has its individual approach of providing IT equipment to
 465 teachers and students and the exchange of ideas has been quasi
 466 non-existent until 2010/2011.</p>
 467
 468 <p>Quite some (non-admin) teachers try to avoid using IT technology in
 469 class as a learning medium completely. Several reasons for this
 470 avoidance do exist.</p>
 471
 472 <p>We discovered that no-one has ever taken a closer look at this
 473 social part of IT management in schools, so far. On our quest journey
 474 for a technical IT solution for schools, we discussed this issue with
 475 several teachers, headmasters, politicians, other IT professionals and
 476 they all confirmed: a holistic approach of considering IT management
 477 at schools, an approach that includes the people in place, will be new
 478 and probably a gain for all.</p>
 479
 480 <p><strong>What do you see as the advantages of Skolelinux/Debian
 481 Edu?</strong></p>
 482
 483 <p>There is a list of advantages: international context, openness to
 484 any kind of contributions, do-ocracy policy, the closeness to Debian,
 485 the different installation scenarios possible (from stand-alone
 486 workstation to complex multi-server sites), the transparency within
 487 project communication, honest communication within the group of
 488 developers, etc.</p>
 489
 490 <p><strong>What do you see as the disadvantages of Skolelinux/Debian
 491 Edu?</strong></p>
 492
 493 <p>Every coin has two sides:</p>
 494
 495 <p>Technically: <a href="http://bugs.debian.org/311188">BTS issue
 496 #311188</a>, tricky upgradability of a Debian Edu main server, network
 497 client installations on top of a plain vanilla Debian installation
 498 should become possible sometime in the near future, one could think
 499 about splitting the very complex package debian-edu-config into
 500 several portions (to make it easier for new developers to
 501 contribute).</p>
 502
 503 <p>Another issue I see is that we (as Debian Edu developers) should
 504 find out more about the network of people who do the marketing for
 505 Debian Edu / Skolelinux. There is a very active group in Germany
 506 promoting Skolelinux on the bigger Linux Days within Germany. Are
 507 there other groups like that in other countries? How can we bring
 508 these marketing people together (marketing group A with group B and
 509 all of them with the group of Debian Edu developers)? During the last
 510 meeting of the German Skolelinux group, I got the impression of people
 511 there being rather disconnected from the development department of
 512 Debian Edu / Skolelinux.</p>
 513
 514 <p><strong>Which free software do you use daily?</strong></p>
 515
 516 <p>For my daily business, I do not use commercial software at all.</p>
 517
 518 <p>For normal stuff I use Iceweasel/Firefox, Libreoffice.org. For
 519 serious text writing I prefer LaTeX. I use gimp, inkscape, scribus for
 520 more artistic tasks. I run virtual machines in KVM and Virtualbox.</p>
 521
 522 <p>I am one of the upstream developers of X2Go. In 2010 I started the
 523 development of a Python based X2Go Client, called PyHoca-GUI.
 524 PyHoca-GUI has brought forth a Python X2Go Client API that currently
 525 is being integrated in Ubuntu's software center.</p>
 526
 527 <p>For communications I have my own Kolab server running using Horde
 528 as web-based groupware client. For IRC I love to use irssi, for Jabber
 529 I have several clients that I use, mostly pidgin, though. I am also
 530 the Debian maintainer of Coccinella, a Jabber-based interactive
 531 whiteboard.</p>
 532
 533 <p>My favourite terminal emulator is KDE's Yakuake.</p>
 534
 535 <p><strong>Which strategy do you believe is the right one to use to
 536 get schools to use free software?</strong></p>
 537
 538 <p>Communicate, communicate, communicate. Enrol people, enrol people,
 539 enrol people.</p>
 540 </div>
 541       <div class="tags">
 542
 543
 544         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>.
 545
 546
 547       </div>
 548     </div>
 549     <div class="padding"></div>
 550
 551     <div class="entry">
 552       <div class="title"><a href="http://people.skolelinux.org/pere/blog/SOAP_based_webservice_from_Dell_to_check_server_support_status.html">SOAP based webservice from Dell to check server support status</a></div>
 553       <div class="date"> 1st June 2012</div>
 554       <div class="body"><p>A few years ago I wrote
 555 <a href="http://people.skolelinux.org/pere/blog/Checking_server_hardware_support_status_for_Dell__HP_and_IBM_servers.html">how
 556 to extract support status</a> for your Dell and HP servers.  Recently
 557 I have learned from colleges here at the
 558 <a href="http://www.uio.no/">University of Oslo</a> that Dell have
 559 made this even easier, by providing a SOAP based web service.  Given
 560 the service tag, one can now query the Dell servers and get machine
 561 readable information about the support status.  This perl code
 562 demonstrate how to do it:</p>
 563
 564 <p><pre>
 565 use strict;
 566 use warnings;
 567 use SOAP::Lite;
 568 use Data::Dumper;
 569 my $GUID = '11111111-1111-1111-1111-111111111111';
 570 my $App = 'test';
 571 my $servicetag = $ARGV[0] or die "Please supply a servicetag. $!\n";
 572 my ($deal, $latest, @dates);
 573 my $s = SOAP::Lite
 574     -> uri('http://support.dell.com/WebServices/')
 575     -> on_action( sub { join '', @_ } )
 576     -> proxy('http://xserv.dell.com/services/assetservice.asmx')
 577     ;
 578 my $a = $s->GetAssetInformation(
 579     SOAP::Data->name('guid')->value($GUID)->type(''),
 580     SOAP::Data->name('applicationName')->value($App)->type(''),
 581     SOAP::Data->name('serviceTags')->value($servicetag)->type(''),
 582 );
 583 print Dumper($a -> result) ;
 584 </pre></p>
 585
 586 <p>The output can look like this:</p>
 587
 588 <p><pre>
 589 $VAR1 = {
 590           'Asset' => {
 591                      'Entitlements' => {
 592                                        'EntitlementData' => [
 593                                                             {
 594                                                               'EntitlementType' => 'Expired',
 595                                                               'EndDate' => '2009-07-29T00:00:00',
 596                                                               'Provider' => '',
 597                                                               'StartDate' => '2006-07-29T00:00:00',
 598                                                               'DaysLeft' => '0'
 599                                                             },
 600                                                             {
 601                                                               'EntitlementType' => 'Expired',
 602                                                               'EndDate' => '2009-07-29T00:00:00',
 603                                                               'Provider' => '',
 604                                                               'StartDate' => '2006-07-29T00:00:00',
 605                                                               'DaysLeft' => '0'
 606                                                             },
 607                                                             {
 608                                                               'EntitlementType' => 'Expired',
 609                                                               'EndDate' => '2007-07-29T00:00:00',
 610                                                               'Provider' => '',
 611                                                               'StartDate' => '2006-07-29T00:00:00',
 612                                                               'DaysLeft' => '0'
 613                                                             }
 614                                                           ]
 615                                      },
 616                      'AssetHeaderData' => {
 617                                           'SystemModel' => 'GX620',
 618                                           'ServiceTag' => '8DSGD2J',
 619                                           'SystemShipDate' => '2006-07-29T19:00:00-05:00',
 620                                           'Buid' => '2323',
 621                                           'Region' => 'Europe',
 622                                           'SystemID' => 'PLX_GX620',
 623                                           'SystemType' => 'OptiPlex'
 624                                         }
 625                    }
 626         };
 627 </pre></p>
 628
 629 <p>I have not been able to find any documentation from Dell about this
 630 service outside the
 631 <a href="http://xserv.dell.com/services/assetservice.asmx?op=GetAssetInformation">inline
 632 documentation</a>, and according to
 633 <a href="http://iboyd.net/index.php/2012/02/14/updated-dell-warranty-information-script/">one
 634 comment</a> it can have stability issues, but it is a lot better than
 635 scraping HTML pages. :)</p>
 636
 637 <p>Wonder if HP and other server vendors have a similar service.  If
 638 you know of one, drop me an email. :)</p>
 639 </div>
 640       <div class="tags">
 641
 642
 643         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>.
 644
 645
 646       </div>
 647     </div>
 648     <div class="padding"></div>
 649
 650     <div class="entry">
 651       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Veileder_fra_DIFI_om_publisering_av_offentlige_data.html">Veileder fra DIFI om publisering av offentlige data</a></div>
 652       <div class="date"> 1st June 2012</div>
 653       <div class="body"><p>På onsdag rakk jeg såvidt innom
 654 <a href="http://www.meetup.com/osloopendata/">Oslo Open Data Forums</a>
 655 møte, og fikk lagt hendene mine på DIFIs helt nye veileder
 656 "<a href="http://veileder.data.norge.no/">Åpne data.  Del og skap
 657 verdier.  Veileder i tilgjengeliggjøring av offentlig data</a>" (også
 658 <a href="http://www.difi.no/filearchive/veileder-i-tilgjengeliggjoring-av-offentlig-data-web.pdf">tilgjengelig
 659 som PDF</a> fra DIFI).</p>
 660
 661 <p>Veilederen er veldig bra, og nevner viktige problemstillinger og
 662 skisserer f.eks. både verdiskapningspotensialet og formatmulighetene
 663 som en bør ha i bakhodet når en publiserer offentlig informasjon på
 664 maskinlesbart format.  Kildekoden til veilederen er
 665 <a href="https://github.com/difi/veileder-opnedata">tilgjengelig via
 666 github</a>, og en kan rapportere tilbakemeldinger og forslag til
 667 forbedringer der (eller via epost og twitter for de som ønsker
 668 det).</p>
 669
 670 <p>Det eneste jeg virkelig savnet i veilederen var omtale av
 671 <a href="http://www.w3.org/DesignIssues/LinkedData.html">w3cs
 672 stjerneklassifisering</a> av åpne datakilder, som jeg tror ville være
 673 nyttige mentale knagger for de som vurderer å publisere sin
 674 informasjon på som åpne data.  Jeg har
 675 <a href="https://github.com/difi/veileder-opnedata/issues/1">rapportert
 676 en github-bug</a> om dette, så får vi se hvordan den blir behandlet.</p>
 677
 678 <p>Det slo meg at det var veldig lite konkret i veilederen om valg av
 679 bruksvilkår ved publisering (aka lisens), men jeg er ikke sikker på om
 680 det hører hjemme der, da det er et vanskelig tema som kanskje heller
 681 hører hjemme i sin egen veileder.  Uansett, anbefaler alle å ta en
 682 titt på veilederen og sikre at alle offentlige etater en har kontakt
 683 med får en kopi.</p>
 684 </div>
 685       <div class="tags">
 686
 687
 688         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</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/First_monitor_calibration_using_ColorHug.html">First monitor calibration using ColorHug</a></div>
 697       <div class="date">31st May 2012</div>
 698       <div class="body"><p>A few days ago my color calibration gadget
 699 <a href="http://www.hughski.com/index.html">ColorHug</a> arrived in the
 700 mail, and I've had a few days to test it.  As all my machines are
 701 running Debian Squeeze, where
 702 <a href="http://packages.qa.debian.org/c/colorhug-client.html">the
 703 calibration software</a> is missing (it is present in Wheezy and Sid),
 704 I ran the calibration using the Fedora based live CD.  This worked
 705 just fine.  So far I have only done the quick calibration.  It was
 706 slow enough for me, so I will leave the more extensive calibration for
 707 another day.</p>
 708
 709 <p>After calibration, I get a
 710 <a href="http://en.wikipedia.org/wiki/ICC_profile">ICC color
 711 profile</a> file that can be passed to programs understanding such
 712 tools.  KDE do not seem to understand it out of the box, so I searched
 713 for command line tools to use to load the color profile into X.
 714 xcalib was the first one I found, and it seem to work fine for single
 715 monitor setups.  But for my video player, a laptop with a flat screen
 716 attached, it was unable to load the color profile for the correct
 717 monitor.  After searching a bit, I
 718 <a href="http://ubuntuforums.org/showthread.php?t=1347896">discovered</a>
 719 that the dispwin tool from the argyll package would do what I wanted,
 720 and a simple</p>
 721
 722 <p><pre>
 723 dispwin -d 1 profile.icc
 724 </pre></p>
 725
 726 <p>later I had the color profile loaded for the correct monitor.  The
 727 result was a bit more pink than I expected.  I guess I picked the
 728 wrong monitor type for the "led" monitor I got, but the result is good
 729 enough for now.</p>
 730 </div>
 731       <div class="tags">
 732
 733
 734         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 735
 736
 737       </div>
 738     </div>
 739     <div class="padding"></div>
 740
 741     <div class="entry">
 742       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Hvor_samles_det_inn_bensinpriser_for_Norge_.html">Hvor samles det inn bensinpriser for Norge?</a></div>
 743       <div class="date">31st May 2012</div>
 744       <div class="body"><p>Det finnes i følge de som har talt ca. 1600 bensinstasjoner i
 745 Norge.  Daglig innsamling av informasjon fra alle disse vil antagelig
 746 kreve noen tusen frivillige.  Dugnadsbasert innsamling av bensinpriser
 747 for å gjøre det enklere å sammenligne priser og dermed bedre
 748 konkurransen i bensinmarkedet er en idé som mange har gjennomført de
 749 siste årene.  Her er et forsøk på en oversikt over de som finnes i
 750 dag.</p>
 751
 752 <dl>
 753
 754 <dt>Dinside.no nettside</dt>
 755
 756 <dd>Nettavisen dinside startet for noen år siden en dugnad for å
 757 <a href="http://www.dinside.no/1931/her-faar-du-billigst-bensin-diesel">samle
 758 inn drivstoffpriser</a>.  Tjenesten samler inn med et nettsideskjema
 759 der en må registrere seg for å delta.  En SMS-tjeneste har visst
 760 eksistert tidligere, men er ute av drift 2012-05-31.  Listen over
 761 bensinstasjoner er kun tilgjengelig for registrerte brukere, og
 762 mangler geografiske koordinater for fremvisning på kart.  Listen over
 763 innsamlede bensinpriser er tilgjengelig som nettside i litt over 24
 764 timer etter registrering.  Antall innsamlede priser pr. dag ligger i
 765 området 10-35, og jeg har startet på
 766 <a href="https://scraperwiki.com/scrapers/dinside-bensinpriser/">en
 767 database over de publiserte prisene</a> hos Scraperwiki.</dd>
 768
 769 <dt>Bitfactorys mobilapp</dt>
 770
 771 <dd>I fjor lanserte
 772 <a href="http://www.bitfactory.no/bensinpris.html">selskapet Bitfactory
 773 sin landsdekkende mobilapp</a> (først for iphone, siden også for
 774 Android) for å samle inn drivstoffpriser og gjøre det enkelt å finne
 775 billigste stasjon i nærområdet ved hjelp av smarttelefon.  Den
 776 innsamlede informasjonen er ikke publisert på web, men dagens priser
 777 kan hentes ut ved hjelp av et
 778 <a href="http://people.skolelinux.org/pere/blog/Litt_informasjon_om_Bitfactorys_Bensinpris_API.html">web-API
 779 som jeg har dokumentert med reversutvikling</a>.  Stasjonslisten
 780 inneholder geografiske koordinater for fremvisning på kart.  Antall
 781 innsamlede priser pr. dag ser ut til å ligge rundt 200.</dd>
 782
 783
 784
 785 <dt>NAF Bergens nettside og iphone-app</dt>
 786
 787 <dd>I år lanserte NAF Bergen <a href="http://www.drivstoffpriser.no/">en
 788 landsdekkende iphone-app</a> koblet til NAF Bergens tjeneste for å
 789 samle inn og varsle brukerne om bensinpriser.  Nettstedet har
 790 publisert listen over bensinstasjoner, men ikke en komplett oversikt
 791 over innsamlede priser.  De har interessant statistikk over
 792 prisutviklingen som går tilbake til 2009.
 793
 794 <dt>bensinpris.net</dt>
 795
 796 <dd>Nettside med prisinformasjon for Trondheimsområdet.  Informasjonen
 797 registreres via web og SMS, og krever ikke registrering.  Nettsiden
 798 viser de tre siste prisene registret for bensin og disel.  Har liste
 799 over kjente stasjoner tilgjengelig.  Svært lite oppdatert for
 800 tiden.</dd>
 801
 802 </dl>
 803
 804 <p>I tillegg er jeg kjent med drivstoffguiden.no som ser ut til å være
 805 nedlagt, og at SSB som del av beregningen av konsumprisindeksen samler
 806 inn driftstoffpriser hver måned og
 807 <a href="http://www.ssb.no/petroleumsalg/">legger dem ut i
 808 PDF-format</a>.</p>
 809
 810 <p>Det jeg ikke forstår er hvorfor det stadig opprettes nye nett- og
 811 mobiltjenester for å samle inn bensinpriser, i stedet for å samarbeide
 812 med de eksisterende løsninger for å gjøre de gode nok til nye
 813 bruksområder.  Jobben med å samle inn priser er formidabel, og hvis
 814 målet er bedre konkurranse på bensinmarkedet ville jeg tro det beste
 815 var om kundene samlet seg om _ett_ nettsted og samlet alle prisene
 816 der, i stedet for å spre innsatsen på mange nettsteder.  Jeg mistenker
 817 årsaken ligger i at de aktørene som har satt opp tjenester så langt
 818 ikke har lagt opp til deling og samarbeid på like vilkår med andre
 819 aktører, og dermed gjort det vanskelig å legge til funksjonalitet som
 820 presentasjon på kart, statistisk analyse eller kvalitetssikring av
 821 bensinstasjonslisten og prisinformasjonen.</p>
 822
 823 <table>
 824
 825 <tr>
 826 <th>Tjeneste</th>
 827 <th>Offentlig stasjons-liste</th>
 828 <th>Publisert stasjons-geopunkt</th>
 829 <th>Publisert API for inn-legging</th>
 830 <th>Publisert API for ut-henting</th>
 831 <th>Publisert alle priser</th>
 832 <th>Publisert database</th>
 833 <th>Lands-dekkende</th>
 834 </tr>
 835
 836 <tr>
 837 <td>Dinside</td>
 838 <td>(ja)</td>
 839 <td>nei</td>
 840 <td>nei</td>
 841 <td>nei</td>
 842 <td>ja</td>
 843 <td>(ja)</td>
 844 <td>ja</td>
 845 </tr>
 846
 847 <tr>
 848 <td>Bitfactorys mobilapp</td>
 849 <td>nei</td>
 850 <td>ja</td>
 851 <td>(ja)</td>
 852 <td>(ja)</td>
 853 <td>nei</td>
 854 <td>nei</td>
 855 <td>ja</td>
 856 </tr>
 857
 858 <tr>
 859 <td>drivstoffpriser.no</td>
 860 <td>ja</td>
 861 <td>ja</td>
 862 <td>nei</td>
 863 <td>nei</td>
 864 <td>nei</td>
 865 <td>nei</td>
 866 <td>ja</td>
 867 </tr>
 868
 869 <tr>
 870 <td>bensinpris.net</td>
 871 <td>ja</td>
 872 <td>nei</td>
 873 <td>nei</td>
 874 <td>nei</td>
 875 <td>nei</td>
 876 <td>nei</td>
 877 <td>nei</td>
 878 </tr>
 879
 880 </table>
 881
 882 <p>Dinside mangler dugnadsbasert kvalitetssikring av stasjonslista,
 883 georeferert informasjon og API for innlegging og uthenting av
 884 informasjon.  Bitfactory mangler publisering av all innsamlet
 885 informasjon, dugnadsbasert kvalitetssikring av stasjonslista og
 886 dokumentert API for innlegging og uthenting av informasjon.  NAFs
 887 løsning mangler publisering av all innsamlet informasjon og API for
 888 innlegging og uthenting av informasjon.</p>
 889
 890 <p>Jeg har nylig spurt folkene bak dinside.nos oversikt og
 891 drivstoffpriser.no om de er villige til å gi ut sine innsamlede data
 892 uten bruksbegresninger og tilby et dokumentert og publisert API for å
 893 legge inn og hente ut informasjon.  Så får vi se hva de sier.</p>
 894 </div>
 895       <div class="tags">
 896
 897
 898         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
 899
 900
 901       </div>
 902     </div>
 903     <div class="padding"></div>
 904
 905     <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>
 906     <div id="sidebar">
 907
 908
 909
 910 <h2>Archive</h2>
 911 <ul>
 912
 913 <li>2012
 914 <ul>
 915
 916 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 917
 918 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 919
 920 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 921
 922 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 923
 924 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 925
 926 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (8)</a></li>
 927
 928 </ul></li>
 929
 930 <li>2011
 931 <ul>
 932
 933 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 934
 935 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 936
 937 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 938
 939 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 940
 941 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 942
 943 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 944
 945 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 946
 947 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 948
 949 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 950
 951 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 952
 953 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 954
 955 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 956
 957 </ul></li>
 958
 959 <li>2010
 960 <ul>
 961
 962 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 963
 964 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 965
 966 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 967
 968 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 969
 970 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 971
 972 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 973
 974 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 975
 976 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 977
 978 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 979
 980 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 981
 982 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 983
 984 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 985
 986 </ul></li>
 987
 988 <li>2009
 989 <ul>
 990
 991 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 992
 993 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 994
 995 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 996
 997 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 998
 999 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1000
1001 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1002
1003 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1004
1005 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1006
1007 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1008
1009 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1010
1011 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1012
1013 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1014
1015 </ul></li>
1016
1017 <li>2008
1018 <ul>
1019
1020 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1021
1022 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1023
1024 </ul></li>
1025
1026 </ul>
1027
1028
1029
1030 <h2>Tags</h2>
1031 <ul>
1032
1033  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1034
1035  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1036
1037  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1038
1039  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (2)</a></li>
1040
1041  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (12)</a></li>
1042
1043  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1044
1045  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (54)</a></li>
1046
1047  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (104)</a></li>
1048
1049  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (8)</a></li>
1050
1051  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (3)</a></li>
1052
1053  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (135)</a></li>
1054
1055  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (16)</a></li>
1056
1057  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1058
1059  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (27)</a></li>
1060
1061  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (16)</a></li>
1062
1063  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
1064
1065  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (4)</a></li>
1066
1067  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1068
1069  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (16)</a></li>
1070
1071  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (170)</a></li>
1072
1073  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (130)</a></li>
1074
1075  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (1)</a></li>
1076
1077  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1078
1079  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (25)</a></li>
1080
1081  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (47)</a></li>
1082
1083  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1084
1085  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1086
1087  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1088
1089  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (4)</a></li>
1090
1091  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1092
1093  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1094
1095  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (1)</a></li>
1096
1097  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (23)</a></li>
1098
1099  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1100
1101  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (29)</a></li>
1102
1103  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
1104
1105  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (4)</a></li>
1106
1107  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (10)</a></li>
1108
1109  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (6)</a></li>
1110
1111  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (25)</a></li>
1112
1113  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
1114
1115  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (20)</a></li>
1116
1117 </ul>
1118
1119
1120     </div>
1121     <p style="text-align: right">
1122  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.4</a>
1123 </p>
1124
1125   </body>
1126 </html>