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