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