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