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