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/Dugnadsnett_for_alle_stiller_p__Oslo_Maker_Faire_i_januar_2014.html">Dugnadsnett for alle stiller på Oslo Maker Faire i januar 2014</a></div>
  24       <div class="date">10th December 2013</div>
  25       <div class="body"><p>Helga 18. og 19. januar 2014 arrangeres
  26 <a href="http://makerfaireoslo.no/no/program/dugnadsnett">Oslo Maker
  27 Faire</a>, og <a href="http://www.dugnadsnett.no/">Dugnadsnett for
  28 alle</a> har fått plass!  Planen er å ha et bord med en plakat der vi
  29 forteller om hva Dugnadsnett for alle er for noe, og et lite verksted
  30 der vi hjelper folk som er interessert i å få opp sin egen mesh-node.
  31 Jeg gleder meg til å se hvordan prosjektet blir mottatt der.</p>
  32
  33 <p>Målet med dugnadsnett for alle i Oslo er å få på plass et datanett
  34 for kommunikasjon ved hjelp av radio-repeaterstasjoner (kalt
  35 mesh-noder) som gjør at en kan direkte kommunisere med slekt, venner
  36 og bekjente i Oslo via andre som deltar i dugnadsnettet, samt gjøre
  37 det mulig komme ut på internett via dugnadsnettet.  Første delmål er å
  38 kunne sende SMS-meldinger vha. IP-telefoni løsningen
  39 <a href="http://www.servalproject.org/">Serval project</a> mellom
  40 deltagerne i Dugnadsnett for alle i Oslo.  Formålet er å ta tilbake
  41 kontrollen over egen nett-infrastruktur og gjøre det dyrere å bedrive
  42 massiv innsamling av informasjon om borgernes bruk av datanett.</p>
  43
  44 <p>Høres dette interessant ut?  Bli med på prosjektet, fortell oss
  45 hvor du kunne tenke deg å sette opp en radio-repeater (slik at folk i
  46 nærheten kan finne hverandre ved hjelp av
  47 <a href="http://flynor.net/mesh/mesh.php">kartet over planlagte og
  48 eksisterende radio-repeatere</A>), bli med på epostlisten
  49 <a href="http://lists.nuug.no/mailman/listinfo/dugnadsnett">dugnadsnett
  50 (at) nuug.no</a> og stikk innom
  51 <a href="irc://irc.freenode.net/#dugnadsnett.no">IRC-kanalen
  52 #dugnadsnett.no</a>.  Så langt er det planlagt over 40
  53 radio-repeatere, med VPN-forbindelser via Internet for å la de delene
  54 av nettet som ikke når hverandre via radio kunne snakke med hverandre
  55 likevel.</p>
  56 </div>
  57       <div class="tags">
  58
  59
  60         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
  61
  62
  63       </div>
  64     </div>
  65     <div class="padding"></div>
  66
  67     <div class="entry">
  68       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Klaus_Knopper.html">Debian Edu interview: Klaus Knopper</a></div>
  69       <div class="date"> 6th December 2013</div>
  70       <div class="body"><p>It has been a while since I managed to publish the last interview,
  71 but the <a href="http://www.skolelinux.org/">Debian Edu /
  72 Skolelinux</a> community is still going strong, and yesterday we even
  73 had a new school administrator show up on
  74 <a href="irc://irc.debian.org/#debian-edu">#debian-edu</a> to share
  75 his success story with installing Debian Edu at their school.  This
  76 time I have been able to get some helpful comments from the creator of
  77 Knoppix, Klaus Knopper, who was involved in a Skolelinux project in
  78 Germany a few years ago.</p>
  79
  80 <p><strong>Who are you, and how do you spend your days?</strong></p>
  81
  82 <p>I am Klaus Knopper.  I have a master degree in electrical
  83 engineering, and is currently professor in information management at
  84 the university of applied sciences Kaiserslautern / Germany and
  85 freelance Open Source software developer and consultant.</p>
  86
  87 <p>All of this is pretty much of the work I spend my days with. Apart
  88 from teaching, I'm also conducting some more or less experimental
  89 projects like the <a href="http://www.knoppix.org">Knoppix GNU/Linux live
  90 system</a> (Debian-based like Skolelinux),
  91 <a href="http://www.knopper.net/knoppix-adriane/index-en.html">ADRIANE</a>
  92 (a blind-friendly talking desktop system) and
  93 <a href="http://www.knopper.net/linbo/index-en.html">LINBO</a>
  94 (Linux-based network boot console, a fast remote install and repair
  95 system supporting various operating systems).</p>
  96
  97 <p><strong>How did you get in contact with the Skolelinux / Debian Edu
  98 project?</strong></p>
  99
 100 <p>The credit for this have to go to Kurt Gramlich, who is the German
 101 coordinator for Skolelinux.  We were looking for an all-in-one open
 102 source community-supported distribution for schools, and Kurt
 103 introduced us to Skolelinux for this purpose.</p>
 104
 105 <p><strong>What do you see as the advantages of Skolelinux / Debian
 106 Edu?</strong></p>
 107
 108 <ul>
 109   <li>Quick installation,</li>
 110   <li>works (almost) out of the box,</li>
 111   <li>contains many useful software packages for teaching and learning,</li>
 112   <li>is a purely community-based distro and not controlled by a
 113     single company,</li>
 114   <li>has a large number of supporters and teachers who share their
 115     experience and problem solutions.</li>
 116 </ul>
 117
 118 <p><strong>What do you see as the disadvantages of Skolelinux / Debian
 119 Edu?</strong></p>
 120
 121 <ul>
 122   <li>Skolelinux is - as we had to learn - not easily upgradable to
 123   the next version.  Opposed to its genuine Debian base, upgrading to
 124   a new version means a full new installation from scratch to get it
 125   working again reliably.
 126
 127   <li>Skolelinux is based on Debian/stable, and therefore always a
 128   little outdated in terms of program versions compared to Edubuntu or
 129   similar educational Linux distros, which rather use Debian/testing
 130   as their base.
 131
 132   <li>Skolelinux has some very self-opinionated and stubborn default
 133   configuration which in my opinion adds unnecessary complexity and is
 134   not always suitable for a schools needs, the preset network
 135   configuration is actually a core definition feature of Skolelinux
 136   and not easy to change, so schools sometimes have to change their
 137   network configuration to make it "Skolelinux-compatible".
 138
 139   <li>Some proposed extensions, which were made available as
 140   contribution, like secure examination mode and lecture material
 141   distribution and collection, were not accepted into the mainline
 142   Skolelinux development and are now not easy to maintain in the
 143   future because of Skolelinux somewhat undeterministic update
 144   schemes.</li>
 145
 146   <li>Skolelinux has only a very tiny number of base developers
 147   compared to Debian.</li>
 148
 149 </ul>
 150
 151 <p>For these reasons and experience from our project, I would now
 152 rather consider using plain Debian for schools next time, until
 153 Skolelinux is more closely integrated into Debian and becomes
 154 upgradeable without reinstallation.</p>
 155
 156 <p><strong>Which free software do you use daily?</strong></p>
 157
 158 <p>GNU/Linux with LXDE desktop, bash for interactive dialog and
 159 programming, texlive for documentation and correspondence,
 160 occasionally LibreOffice for document format conversion. Various
 161 programming languages for teaching.</p>
 162
 163 <p><strong>Which strategy do you believe is the right one to use to
 164 get schools to use free software?</strong></p>
 165
 166 <p>Strong arguments are</p>
 167
 168 <ul>
 169
 170   <li>Knowledge is free, and so should be methods and tools for
 171     teaching and learning.</li>
 172
 173   <li>Students can learn with and use the same software at school, at
 174     home, and at their working place without running into license or
 175     conversion problems.</li>
 176
 177   <li>Closed source or proprietary software hides knowledge rather
 178     than exposing it, and proprietary software vendors try to bind
 179     customers to certain products.  But teachers need to teach
 180     science, not products.</li>
 181
 182   <li>If you have everything you for daily work as open source, what
 183     would you need proprietary software for?</li>
 184
 185 </ul>
 186 </div>
 187       <div class="tags">
 188
 189
 190         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>.
 191
 192
 193       </div>
 194     </div>
 195     <div class="padding"></div>
 196
 197     <div class="entry">
 198       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Dugnadsnett_for_alle__a_wireless_community_network_in_Oslo__take_shape.html">Dugnadsnett for alle, a wireless community network in Oslo, take shape</a></div>
 199       <div class="date">30th November 2013</div>
 200       <div class="body"><p>If you want the ability to electronically communicate directly with
 201 your neighbors and friends using a network controlled by your peers in
 202 stead of centrally controlled by a few corporations, or would like to
 203 experiment with interesting network technology, the
 204 <a href="http://www.dugnadsnett.no/">Dugnasnett for alle i Oslo</a>
 205 might be project for you.  39 mesh nodes are currently being planned,
 206 in the freshly started initiative from NUUG and Hackeriet to create a
 207 wireless community network.  The work is inspired by
 208 <a href="http://freifunk.net/">Freifunk</a>,
 209 <a href="http://www.awmn.net/">Athens Wireless Metropolitan
 210 Network</a>, <a href="http://en.wikipedia.org/wiki/Roofnet">Roofnet</a>
 211 and other successful mesh networks around the globe.  Two days ago we
 212 held a workshop to try to get people started on setting up their own
 213 mesh node, and there we decided to create a new mailing list
 214 <a href="http://lists.nuug.no/mailman/listinfo/dugnadsnett">dugnadsnett
 215 (at) nuug.no</a> and IRC channel
 216 <a href="irc://irc.freenode.net/#dugnadsnett.no">#dugnadsnett.no</a> to
 217 coordinate the work.  See also the NUUG blog post
 218 <a href="http://www.nuug.no/news/E_postliste_og_IRC_kanal_for_Dugnadsnett_for_alle_i_Oslo.shtml">announcing
 219 the mailing list and IRC channel</a>.</p>
 220 </div>
 221       <div class="tags">
 222
 223
 224         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 225
 226
 227       </div>
 228     </div>
 229     <div class="padding"></div>
 230
 231     <div class="entry">
 232       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Hvor_godt_fungerer_Linux_klienter_mot_MS_Exchange_.html">Hvor godt fungerer Linux-klienter mot MS Exchange?</a></div>
 233       <div class="date">26th November 2013</div>
 234       <div class="body"><p>Jeg
 235 <a href="http://people.skolelinux.org/pere/blog/_pent_m_te_p__onsdag_om_bruken_av_Microsoft_Exchange_ved_Universitetet_i_Oslo.html">skrev
 236 i juni om protestene</a> på planene til min arbeidsplass,
 237 <a href="http://www.uio.no/">Universitetet i Oslo</a>, om å gå bort fra
 238 fri programvare- og åpne standardløsninger for å håndtere epost,
 239 vekk fra IETF-standarden SIEVE for filtrering av epost og over til
 240 godseide spesifikasjoner og epostsystemet Microsoft Exchange.
 241 Protestene har fått litt ny omtale i media de siste dagene, i tillegg
 242 til de oppslagene som kom i mai.</p>
 243
 244 <ul>
 245
 246 <li>2013-11-26 <a href="http://www.version2.dk/artikel/gigantisk-outlook-konvertering-moeder-protester-paa-universitet-55147">Gigantisk Outlook-konvertering møder protester på universitet</a> - versjon2.dk</li>
 247
 248 <li>2013-11-25
 249   <a href="http://www.idg.no/computerworld/article279407.ece">Microsoft-protest
 250   på Universitetet</a> - Computerworld</li>
 251
 252 <li>2013-11-25
 253   <a href="http://www.uniforum.uio.no/nyheter/2013/11/uio-bor-bruke-apen-programvare.html">Kjemper
 254   mot innføring av Microsoft Exchange på UiO</a> - Uniforum</li>
 255
 256 <li>2013-11-25
 257   <a href="http://www.uniforum.uio.no/nyheter/2013/11/uio-utsetter-innforing-av-nytt-e-postsystem.html">Utsetter
 258   innføring av nytt e-postsystem</a> - Uniforum</li>
 259
 260 <li>2013-05-29
 261   <a href="http://universitas.no/nyhet/58462/forsvarer-nytt-it-system">Forsvarer
 262   nytt IT-system</a> - Universitas</li>
 263
 264 <li>2013-05-23
 265   <a href="http://www.uniforum.uio.no/nyheter/2013/05/uio-innforer-nytt-epost-og-kalendersystem.html">UiO
 266   innfører nytt epost- og kalenderverktøy</a> - Uniforum</li>
 267
 268 <li>2013-05-22
 269   <a href="http://universitas.no/nyhet/58424/protestgruppe-vil-stanse-it-system">Protestgruppe
 270   vil stanse IT-system</a> - Universitas</li>
 271
 272 <li>2013-05-15
 273   <a href="http://www.uniforum.uio.no/leserbrev/2013/uio-ma-ha-kontroll-over-sitt-eget-epostsystem.html">UiO
 274   må ha kontroll over sitt eget epostsystem</a> - Uniforum</li>
 275
 276 </ul>
 277
 278 <p>Prosjektledelsen har fortalt at dette skal fungere like godt for
 279 Linux-brukere som for brukere av Microsoft Windows og Apple MacOSX,
 280 men jeg lurer på hva slags erfaringer Linux-brukere i eksisterende
 281 miljøer som bruker MS Exchange har gjort.  Hvis du har slik erfaring
 282 hadet det vært veldig fint om du kan send et leserbrev til
 283 <a href="http://www.uniforum.uio.no/">Uniforum</a> og fortelle om hvor
 284 greit det er å bruke Exchange i kryss-platform-miljøer?  De jeg har
 285 snakket med sier en greit får lest e-posten sin hvis Exchange har
 286 slått på IMAP-funksjonalitet, men at kalender og møtebooking ikke
 287 fungerer godt for Linux-klienter. Jeg har ingen personlig erfaring å
 288 komme med, så jeg er nysgjerrig på hva andre kan dele av erfaringer
 289 med universitetet.</p>
 290
 291 <p>Mitt ankerpunkt mot å bytte ut fri programvare som fungerer godt
 292 med godseid programvare er at en mister kontroll over egen
 293 infrastruktur, låser seg inn i en løsning det vil bli dyrt å komme ut
 294 av, uten at en får funksjonalitet en ikke kunne skaffet seg med fri
 295 programvare, eventuelt videreutviklet med de pengene som brukes på
 296 overgangen til MS Exchange.  Personlig planlegger jeg å fortsette å
 297 laste ned all eposten min til lokal maskin for indeksering og lesing
 298 med <a href=="http://notmuchmail.org">notmuch</a>, så jeg håper jeg
 299 ikke blir veldig skadelidende av overgangen.</p>
 300
 301 <p><a href="http://dinis.linguateca.pt/Diana/ImotMSUiO.html">Underskriftslista
 302 for oss som er mot endringen</a>, som omtales i artiklene, er fortsatt
 303 åpen for de som vil signere på oppropet.  Akkurat nå er det 298
 304 personer som har signert.</p>
 305 </div>
 306       <div class="tags">
 307
 308
 309         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/standard">standard</a>.
 310
 311
 312       </div>
 313     </div>
 314     <div class="padding"></div>
 315
 316     <div class="entry">
 317       <div class="title"><a href="http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html">New chrpath release 0.15</a></div>
 318       <div class="date">24th November 2013</div>
 319       <div class="body"><p>After many years break from the package and a vain hope that
 320 development would be continued by someone else, I finally pulled my
 321 acts together this morning and wrapped up a new release of chrpath,
 322 the command line tool to modify the rpath and runpath of already
 323 compiled ELF programs.  The update was triggered by the persistence of
 324 Isha Vishnoi at IBM, which needed a new config.guess file to get
 325 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
 326 is working on.  I checked the
 327 <a href="http://packages.qa.debian.org/chrpath">Debian</a>,
 328 <a href="https://launchpad.net/ubuntu/+source/chrpath">Ubuntu</a> and
 329 <a href="https://admin.fedoraproject.org/pkgdb/acls/name/chrpath">Fedora</a>
 330 packages for interesting patches (failed to find the source from
 331 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
 332 These are the release notes:</p>
 333
 334 <p>New in 0.15 released 2013-11-24:</p>
 335
 336 <ul>
 337
 338   <li>Updated config.sub and config.guess from the GNU project to work
 339    with newer architectures.  Thanks to isha vishnoi for the heads
 340    up.</li>
 341
 342   <li>Updated README with current URLs.</li>
 343
 344   <li>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
 345    Matthias Klose.</li>
 346
 347   <li>Added missing help for -k|--keepgoing option, using patch by
 348    Petr Machata found in Fedora.</li>
 349
 350   <li>Rewrite removal of RPATH/RUNPATH to make sure the entry in
 351    .dynamic is a NULL terminated string.  Based on patch found in
 352    Fedora credited Axel Thimm and Christian Krause.</li>
 353
 354 </ul>
 355
 356 <p>You can
 357 <a href="https://alioth.debian.org/frs/?group_id=31052">download the
 358 new version 0.15 from alioth</a>.  Please let us know via the Alioth
 359 project if something is wrong with the new release.  The test suite
 360 did not discover any old errors, so if you find a new one, please also
 361 include a testsuite check.</p>
 362 </div>
 363       <div class="tags">
 364
 365
 366         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 367
 368
 369       </div>
 370     </div>
 371     <div class="padding"></div>
 372
 373     <div class="entry">
 374       <div class="title"><a href="http://people.skolelinux.org/pere/blog/RSS_kilde_for_friteksts_k_i_offentlige_anbud_hos_Doffin.html">RSS-kilde for fritekstsøk i offentlige anbud hos Doffin</a></div>
 375       <div class="date">22nd November 2013</div>
 376       <div class="body"><p>I fjor sommer lagde jeg en
 377 <a href="http://people.skolelinux.org/pere/blog/SQL_database_med_anbud_publisert_p__Doffin.html">offentlig
 378 tilgjengelig SQL-database over offentlig anbud</a> basert på skraping
 379 av HTML-data fra Doffin.  Den har stått og gått siden da, og har nå
 380 ca. 28000 oppføringer.  Jeg oppdaget da jeg tittet innom at noen
 381 oppføringer var ikke blitt med, antagelig på grunn av at de fikk
 382 tildelt sekvensnummer i Doffin en godt stund før de ble publisert,
 383 slik at min nettsideskraper som fortsatte skrapingen der den slapp
 384 sist ikke fikk dem med seg.  Jeg har fikset litt slik at skraperen nå
 385 ser litt tilbake i tid for å se om den har gått glipp av noen
 386 oppføringer, og har skrapet på nytt fra midten av september 2013 og
 387 fremover.  Det bør dermed bli en mer komplett database for kommende
 388 måneder.  Hvis jeg får tid skal jeg forsøke å skrape "glemte" data fra
 389 før midten av september 2013, men tør ikke garantere at det blir
 390 prioritert med det første. </p>
 391
 392 <p>Men målet med denne bloggposten er å vise hvordan denne
 393 Doffin-databasen kan brukes og integreres med en RSS-leser, slik at en
 394 kan la datamaskinen holde et øye med Doffin-annonseringer etter
 395 nøkkelord.  En kan lage sitt eget søk ved å besøke
 396 <ahref="https://classic.scraperwiki.com/docs/api?name=norwegian-doffin#sqlite">API-et
 397 hos Scraperwiki</a>, velge format rss2 og så legge inn noe ala dette i
 398 "query in SQL":</p>
 399
 400 <p><pre>
 401 select title, scrapedurl as link, abstract as description,
 402        publishdate as pubDate from 'swdata'
 403    where abstract like '%linux%' or title like '%linux%'
 404    order by seq desc limit 20
 405 </pre></p>
 406
 407 <p>Dette vil søke opp alle anbud med ordet linux i oppsummering eller
 408 tittel.  En kan lage mer avanserte søk hvis en ønsker det.  URL-en som
 409 dukker opp nederst på siden kan en så gi til sin RSS-leser (jeg bruker
 410 akregator selv), og så automatisk få beskjed hvis det dukker opp anbud
 411 med det aktuelle nøkkelordet i teksten.  Merk at kapasiteten og
 412 ytelsen hos Scraperwiki er begrenset, så ikke be RSS-leseren hente ned
 413 oftere enn en gang hver dag.</p>
 414
 415 <p>Du lurer kanskje på hva slags informasjon en kan få ut fra denne
 416 databasen.  Her er to RSS-kilder, med søkeordet
 417 "<a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25linux%25'%20or%20title%20like%20'%25linux%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">linux</a>",
 418 søkeordet
 419 "<a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25fri%20programvare%25'%20or%20title%20like%20'%25fri%20programvare%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">fri
 420 programvare</a>"
 421 og søkeordet
 422 "<a href="https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25odf%25'%20or%20title%20like%20'%25odf%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">odf</a>".
 423 Det er bare å søke på det en er interessert i.  Kopier gjerne
 424 datasettet og sett opp din egen tjeneste hvis du vil gjøre mer
 425 avanserte søk.  SQLite-filen med Doffin-oppføringer kan lastes med fra
 426 Scraperwiki for de som vil grave dypere.</p>
 427 </div>
 428       <div class="tags">
 429
 430
 431         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>.
 432
 433
 434       </div>
 435     </div>
 436     <div class="padding"></div>
 437
 438     <div class="entry">
 439       <div class="title"><a href="http://people.skolelinux.org/pere/blog/All_drones_should_be_radio_marked_with_what_they_do_and_who_they_belong_to.html">All drones should be radio marked with what they do and who they belong to</a></div>
 440       <div class="date">21st November 2013</div>
 441       <div class="body"><p>Drones, flying robots, are getting more and more popular.  The most
 442 know ones are the killer drones used by some government to murder
 443 people they do not like without giving them the chance of a fair
 444 trial, but the technology have many good uses too, from mapping and
 445 forest maintenance to photography and search and rescue.  I am sure it
 446 is just a question of time before "bad drones" are in the hands of
 447 private enterprises and not only state criminals but petty criminals
 448 too.  The drone technology is very useful and very dangerous.  To have
 449 some control over the use of drones, I agree with Daniel Suarez in his
 450 TED talk
 451 "<a href="https://archive.org/details/DanielSuarez_2013G">The kill
 452 decision shouldn't belong to a robot</a>", where he suggested this
 453 little gem to keep the good while limiting the bad use of drones:</p>
 454
 455 <blockquote>
 456
 457 <p>Each robot and drone should have a cryptographically signed
 458 I.D. burned in at the factory that can be used to track its movement
 459 through public spaces. We have license plates on cars, tail numbers on
 460 aircraft. This is no different. And every citizen should be able to
 461 download an app that shows the population of drones and autonomous
 462 vehicles moving through public spaces around them, both right now and
 463 historically. And civic leaders should deploy sensors and civic drones
 464 to detect rogue drones, and instead of sending killer drones of their
 465 own up to shoot them down, they should notify humans to their
 466 presence. And in certain very high-security areas, perhaps civic
 467 drones would snare them and drag them off to a bomb disposal facility.</p>
 468
 469 <p>But notice, this is more an immune system than a weapons system. It
 470 would allow us to avail ourselves of the use of autonomous vehicles
 471 and drones while still preserving our open, civil society.</p>
 472
 473 </blockquote>
 474
 475 <p>The key is that <em>every citizen</em> should be able to read the
 476 radio beacons sent from the drones in the area, to be able to check
 477 both the government and others use of drones.  For such control to be
 478 effective, everyone must be able to do it.  What should such beacon
 479 contain?  At least formal owner, purpose, contact information and GPS
 480 location.  Probably also the origin and target position of the current
 481 flight.  And perhaps some registration number to be able to look up
 482 the drone in a central database tracking their movement.  Robots
 483 should not have privacy.  It is people who need privacy.</p>
 484 </div>
 485       <div class="tags">
 486
 487
 488         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/robot">robot</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 489
 490
 491       </div>
 492     </div>
 493     <div class="padding"></div>
 494
 495     <div class="entry">
 496       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Lets_make_a_wireless_community_network_in_Oslo_.html">Lets make a wireless community network in Oslo!</a></div>
 497       <div class="date">13th November 2013</div>
 498       <div class="body"><p>Today NUUG and Hackeriet announced
 499 <a href="http://www.nuug.no/news/Bli_med___bygge_dugnadsnett_for_alle_i_Oslo.shtml">our
 500 plans to join forces and create a wireless community network in
 501 Oslo</a>.  The workshop to help people get started will take place
 502 Thursday 2013-11-28, but we already are collecting the geolocation of
 503 people joining forces to make this happen.  We have
 504 <a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/oslo-nodes.geojson">9
 505 locations plotted on the map</a>, but we will need more before we have
 506 a connected mesh spread across Oslo.  If this sound interesting to
 507 you, please join us at the workshop.  If you are too impatient to wait
 508 15 days, please join us on the IRC channel
 509 <a href="irc://irc.freenode.net/%23nuug">#nuug on irc.freenode.net</a>
 510 right away. :)</p>
 511 </div>
 512       <div class="tags">
 513
 514
 515         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 516
 517
 518       </div>
 519     </div>
 520     <div class="padding"></div>
 521
 522     <div class="entry">
 523       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Running_TP_Link_MR3040_as_a_batman_adv_mesh_node_using_openwrt.html">Running TP-Link MR3040 as a batman-adv mesh node using openwrt</a></div>
 524       <div class="date">10th November 2013</div>
 525       <div class="body"><p>Continuing my research into mesh networking, I was recommended to
 526 use TP-Link 3040 and 3600 access points as mesh nodes, and the pair I
 527 bought arrived on Friday.  Here are my notes on how to set up the
 528 MR3040 as a mesh node using
 529 <a href="http://www.openwrt.org/">OpenWrt</a>.</p>
 530
 531 <p>I started by following the instructions on the OpenWRT wiki for
 532 <a href="http://wiki.openwrt.org/toh/tp-link/tl-mr3040">TL-MR3040</a>,
 533 and downloaded
 534 <a href="http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin">the
 535 recommended firmware image</a>
 536 (openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin) and
 537 uploaded it into the original web interface.  The flashing went fine,
 538 and the machine was available via telnet on the ethernet port.  After
 539 logging in and setting the root password, ssh was available and I
 540 could start to set it up as a batman-adv mesh node.</p>
 541
 542 <p>I started off by reading the instructions from
 543 <a href="http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine's_Research">Wireless
 544 Africa</a>, which had quite a lot of useful information, but
 545 eventually I followed the recipe from the Open Mesh wiki for
 546 <a href="http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config">using
 547 batman-adv on OpenWrt</a>.  A small snag was the fact that the
 548 <tt>opkg install kmod-batman-adv</tt> command did not work as it
 549 should.  The batman-adv kernel module would fail to load because its
 550 dependency crc16 was not already loaded.  I
 551 <a href="https://dev.openwrt.org/ticket/14452">reported the bug</a> to
 552 the openwrt project and hope it will be fixed soon.  But the problem
 553 only seem to affect initial testing of batman-adv, as configuration
 554 seem to work when booting from scratch.</p>
 555
 556 <p>The setup is done using files in /etc/config/.  I did not bridge
 557 the Ethernet and mesh interfaces this time, to be able to hook up the
 558 box on my local network and log into it for configuration updates.
 559 The following files were changed and look like this after modifying
 560 them:</p>
 561
 562 <p><tt>/etc/config/network</tt></p>
 563
 564 <pre>
 565
 566 config interface 'loopback'
 567         option ifname 'lo'
 568         option proto 'static'
 569         option ipaddr '127.0.0.1'
 570         option netmask '255.0.0.0'
 571
 572 config globals 'globals'
 573         option ula_prefix 'fdbf:4c12:3fed::/48'
 574
 575 config interface 'lan'
 576         option ifname 'eth0'
 577         option type 'bridge'
 578         option proto 'dhcp'
 579         option ipaddr '192.168.1.1'
 580         option netmask '255.255.255.0'
 581         option hostname 'tl-mr3040'
 582         option ip6assign '60'
 583
 584 config interface 'mesh'
 585         option ifname 'adhoc0'
 586         option mtu '1528'
 587         option proto 'batadv'
 588         option mesh 'bat0'
 589 </pre>
 590
 591 <p><tt>/etc/config/wireless</tt></p>
 592 <pre>
 593
 594 config wifi-device 'radio0'
 595         option type 'mac80211'
 596         option channel '11'
 597         option hwmode '11ng'
 598         option path 'platform/ar933x_wmac'
 599         option htmode 'HT20'
 600         list ht_capab 'SHORT-GI-20'
 601         list ht_capab 'SHORT-GI-40'
 602         list ht_capab 'RX-STBC1'
 603         list ht_capab 'DSSS_CCK-40'
 604         option disabled '0'
 605
 606 config wifi-iface 'wmesh'
 607         option device 'radio0'
 608         option ifname 'adhoc0'
 609         option network 'mesh'
 610         option encryption 'none'
 611         option mode 'adhoc'
 612         option bssid '02:BA:00:00:00:01'
 613         option ssid 'meshfx@hackeriet'
 614 </pre>
 615 <p><tt>/etc/config/batman-adv</tt></p>
 616 <pre>
 617
 618 config 'mesh' 'bat0'
 619         option interfaces 'adhoc0'
 620         option 'aggregated_ogms'
 621         option 'ap_isolation'
 622         option 'bonding'
 623         option 'fragmentation'
 624         option 'gw_bandwidth'
 625         option 'gw_mode'
 626         option 'gw_sel_class'
 627         option 'log_level'
 628         option 'orig_interval'
 629         option 'vis_mode'
 630         option 'bridge_loop_avoidance'
 631         option 'distributed_arp_table'
 632         option 'network_coding'
 633         option 'hop_penalty'
 634
 635 # yet another batX instance
 636 # config 'mesh' 'bat5'
 637 #       option 'interfaces' 'second_mesh'
 638 </pre>
 639
 640 <p>The mesh node is now operational.  I have yet to test its range,
 641 but I hope it is good.  I have not yet tested the TP-Link 3600 box
 642 still wrapped up in plastic.</p>
 643 </div>
 644       <div class="tags">
 645
 646
 647         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 648
 649
 650       </div>
 651     </div>
 652     <div class="padding"></div>
 653
 654     <div class="entry">
 655       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html">Debian init.d boot script example for rsyslog</a></div>
 656       <div class="date"> 2nd November 2013</div>
 657       <div class="body"><p>If one of the points of switching to a new init system in Debian is
 658 <a href="http://thomas.goirand.fr/blog/?p=147">to get rid of huge
 659 init.d scripts</a>, I doubt we need to switch away from sysvinit and
 660 init.d scripts at all.  Here is an example init.d script, ie a rewrite
 661 of /etc/init.d/rsyslog:</p>
 662
 663 <p><pre>
 664 #!/lib/init/init-d-script
 665 ### BEGIN INIT INFO
 666 # Provides:          rsyslog
 667 # Required-Start:    $remote_fs $time
 668 # Required-Stop:     umountnfs $time
 669 # X-Stop-After:      sendsigs
 670 # Default-Start:     2 3 4 5
 671 # Default-Stop:      0 1 6
 672 # Short-Description: enhanced syslogd
 673 # Description:       Rsyslog is an enhanced multi-threaded syslogd.
 674 #                    It is quite compatible to stock sysklogd and can be
 675 #                    used as a drop-in replacement.
 676 ### END INIT INFO
 677 DESC="enhanced syslogd"
 678 DAEMON=/usr/sbin/rsyslogd
 679 </pre></p>
 680
 681 <p>Pretty minimalistic to me... For the record, the original sysv-rc
 682 script was 137 lines, and the above is just 15 lines, most of it meta
 683 info/comments.</p>
 684
 685 <p>How to do this, you ask?  Well, one create a new script
 686 /lib/init/init-d-script looking something like this:
 687
 688 <p><pre>
 689 #!/bin/sh
 690
 691 # Define LSB log_* functions.
 692 # Depend on lsb-base (>= 3.2-14) to ensure that this file is present
 693 # and status_of_proc is working.
 694 . /lib/lsb/init-functions
 695
 696 #
 697 # Function that starts the daemon/service
 698
 699 #
 700 do_start()
 701 {
 702         # Return
 703         #   0 if daemon has been started
 704         #   1 if daemon was already running
 705         #   2 if daemon could not be started
 706         start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
 707                 || return 1
 708         start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
 709                 $DAEMON_ARGS \
 710                 || return 2
 711         # Add code here, if necessary, that waits for the process to be ready
 712         # to handle requests from services started subsequently which depend
 713         # on this one.  As a last resort, sleep for some time.
 714 }
 715
 716 #
 717 # Function that stops the daemon/service
 718 #
 719 do_stop()
 720 {
 721         # Return
 722         #   0 if daemon has been stopped
 723         #   1 if daemon was already stopped
 724         #   2 if daemon could not be stopped
 725         #   other if a failure occurred
 726         start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
 727         RETVAL="$?"
 728         [ "$RETVAL" = 2 ] && return 2
 729         # Wait for children to finish too if this is a daemon that forks
 730         # and if the daemon is only ever run from this initscript.
 731         # If the above conditions are not satisfied then add some other code
 732         # that waits for the process to drop all resources that could be
 733         # needed by services started subsequently.  A last resort is to
 734         # sleep for some time.
 735         start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
 736         [ "$?" = 2 ] && return 2
 737         # Many daemons don't delete their pidfiles when they exit.
 738         rm -f $PIDFILE
 739         return "$RETVAL"
 740 }
 741
 742 #
 743 # Function that sends a SIGHUP to the daemon/service
 744 #
 745 do_reload() {
 746         #
 747         # If the daemon can reload its configuration without
 748         # restarting (for example, when it is sent a SIGHUP),
 749         # then implement that here.
 750         #
 751         start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
 752         return 0
 753 }
 754
 755 SCRIPTNAME=$1
 756 scriptbasename="$(basename $1)"
 757 echo "SN: $scriptbasename"
 758 if [ "$scriptbasename" != "init-d-library" ] ; then
 759     script="$1"
 760     shift
 761     . $script
 762 else
 763     exit 0
 764 fi
 765
 766 NAME=$(basename $DAEMON)
 767 PIDFILE=/var/run/$NAME.pid
 768
 769 # Exit if the package is not installed
 770 #[ -x "$DAEMON" ] || exit 0
 771
 772 # Read configuration variable file if it is present
 773 [ -r /etc/default/$NAME ] && . /etc/default/$NAME
 774
 775 # Load the VERBOSE setting and other rcS variables
 776 . /lib/init/vars.sh
 777
 778 case "$1" in
 779   start)
 780         [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
 781         do_start
 782         case "$?" in
 783                 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
 784                 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
 785         esac
 786         ;;
 787   stop)
 788         [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
 789         do_stop
 790         case "$?" in
 791                 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
 792                 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
 793         esac
 794         ;;
 795   status)
 796         status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
 797         ;;
 798   #reload|force-reload)
 799         #
 800         # If do_reload() is not implemented then leave this commented out
 801         # and leave 'force-reload' as an alias for 'restart'.
 802         #
 803         #log_daemon_msg "Reloading $DESC" "$NAME"
 804         #do_reload
 805         #log_end_msg $?
 806         #;;
 807   restart|force-reload)
 808         #
 809         # If the "reload" option is implemented then remove the
 810         # 'force-reload' alias
 811         #
 812         log_daemon_msg "Restarting $DESC" "$NAME"
 813         do_stop
 814         case "$?" in
 815           0|1)
 816                 do_start
 817                 case "$?" in
 818                         0) log_end_msg 0 ;;
 819                         1) log_end_msg 1 ;; # Old process is still running
 820                         *) log_end_msg 1 ;; # Failed to start
 821                 esac
 822                 ;;
 823           *)
 824                 # Failed to stop
 825                 log_end_msg 1
 826                 ;;
 827         esac
 828         ;;
 829   *)
 830         echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
 831         exit 3
 832         ;;
 833 esac
 834
 835 :
 836 </pre></p>
 837
 838 <p>It is based on /etc/init.d/skeleton, and could be improved quite a
 839 lot.  I did not really polish the approach, so it might not always
 840 work out of the box, but you get the idea.  I did not try very hard to
 841 optimize it nor make it more robust either.</p>
 842
 843 <p>A better argument for switching init system in Debian than reducing
 844 the size of init scripts (which is a good thing to do anyway), is to
 845 get boot system that is able to handle the kernel events sensibly and
 846 robustly, and do not depend on the boot to run sequentially.  The boot
 847 and the kernel have not behaved sequentially in years.</p>
 848 </div>
 849       <div class="tags">
 850
 851
 852         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
 853
 854
 855       </div>
 856     </div>
 857     <div class="padding"></div>
 858
 859     <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>
 860     <div id="sidebar">
 861
 862
 863
 864 <h2>Archive</h2>
 865 <ul>
 866
 867 <li>2013
 868 <ul>
 869
 870 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 871
 872 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 873
 874 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 875
 876 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 877
 878 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 879
 880 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 881
 882 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 883
 884 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 885
 886 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 887
 888 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 889
 890 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 891
 892 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (2)</a></li>
 893
 894 </ul></li>
 895
 896 <li>2012
 897 <ul>
 898
 899 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 900
 901 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 902
 903 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 904
 905 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 906
 907 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 908
 909 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 910
 911 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 912
 913 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 914
 915 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 916
 917 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 918
 919 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 920
 921 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 922
 923 </ul></li>
 924
 925 <li>2011
 926 <ul>
 927
 928 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 929
 930 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 931
 932 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 933
 934 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 935
 936 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 937
 938 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 939
 940 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 941
 942 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 943
 944 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 945
 946 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 947
 948 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 949
 950 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 951
 952 </ul></li>
 953
 954 <li>2010
 955 <ul>
 956
 957 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 958
 959 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 960
 961 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 962
 963 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 964
 965 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 966
 967 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 968
 969 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 970
 971 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 972
 973 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 974
 975 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 976
 977 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 978
 979 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 980
 981 </ul></li>
 982
 983 <li>2009
 984 <ul>
 985
 986 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 987
 988 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 989
 990 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 991
 992 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 993
 994 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 995
 996 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 997
 998 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 999
1000 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1001
1002 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1003
1004 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1005
1006 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1007
1008 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1009
1010 </ul></li>
1011
1012 <li>2008
1013 <ul>
1014
1015 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1016
1017 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1018
1019 </ul></li>
1020
1021 </ul>
1022
1023
1024
1025 <h2>Tags</h2>
1026 <ul>
1027
1028  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1029
1030  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1031
1032  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1033
1034  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1035
1036  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (7)</a></li>
1037
1038  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (13)</a></li>
1039
1040  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1041
1042  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (91)</a></li>
1043
1044  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (143)</a></li>
1045
1046  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1047
1048  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
1049
1050  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1051
1052  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (231)</a></li>
1053
1054  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
1055
1056  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1057
1058  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
1059
1060  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (5)</a></li>
1061
1062  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1063
1064  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (38)</a></li>
1065
1066  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
1067
1068  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1069
1070  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
1071
1072  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (6)</a></li>
1073
1074  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1075
1076  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (7)</a></li>
1077
1078  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (25)</a></li>
1079
1080  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (239)</a></li>
1081
1082  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (161)</a></li>
1083
1084  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (9)</a></li>
1085
1086  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1087
1088  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (45)</a></li>
1089
1090  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (67)</a></li>
1091
1092  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1093
1094  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1095
1096  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1097
1098  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1099
1100  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1101
1102  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1103
1104  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1105
1106  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (33)</a></li>
1107
1108  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1109
1110  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1111
1112  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
1113
1114  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1115
1116  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1117
1118  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (21)</a></li>
1119
1120  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1121
1122  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1123
1124  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (39)</a></li>
1125
1126  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1127
1128  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (28)</a></li>
1129
1130 </ul>
1131
1132
1133     </div>
1134     <p style="text-align: right">
1135  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1136 </p>
1137
1138   </body>
1139 </html>