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