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/Debian_init_d_boot_script_example_for_rsyslog.html">Debian init.d boot script example for rsyslog</a></div>
  24       <div class="date"> 2nd November 2013</div>
  25       <div class="body"><p>If one of the points of switching to a new init system in Debian is
  26 <a href="http://thomas.goirand.fr/blog/?p=147">to get rid of huge
  27 init.d scripts</a>, I doubt we need to switch away from sysvinit and
  28 init.d scripts at all.  Here is an example init.d script, ie a rewrite
  29 of /etc/init.d/rsyslog:</p>
  30
  31 <p><pre>
  32 #!/lib/init/init-d-script
  33 ### BEGIN INIT INFO
  34 # Provides:          rsyslog
  35 # Required-Start:    $remote_fs $time
  36 # Required-Stop:     umountnfs $time
  37 # X-Stop-After:      sendsigs
  38 # Default-Start:     2 3 4 5
  39 # Default-Stop:      0 1 6
  40 # Short-Description: enhanced syslogd
  41 # Description:       Rsyslog is an enhanced multi-threaded syslogd.
  42 #                    It is quite compatible to stock sysklogd and can be
  43 #                    used as a drop-in replacement.
  44 ### END INIT INFO
  45 DESC="enhanced syslogd"
  46 DAEMON=/usr/sbin/rsyslogd
  47 </pre></p>
  48
  49 <p>Pretty minimalistic to me... For the record, the original sysv-rc
  50 script was 137 lines, and the above is just 15 lines, most of it meta
  51 info/comments.</p>
  52
  53 <p>How to do this, you ask?  Well, one create a new script
  54 /lib/init/init-d-script looking something like this:
  55
  56 <p><pre>
  57 #!/bin/sh
  58
  59 # Define LSB log_* functions.
  60 # Depend on lsb-base (>= 3.2-14) to ensure that this file is present
  61 # and status_of_proc is working.
  62 . /lib/lsb/init-functions
  63
  64 #
  65 # Function that starts the daemon/service
  66
  67 #
  68 do_start()
  69 {
  70         # Return
  71         #   0 if daemon has been started
  72         #   1 if daemon was already running
  73         #   2 if daemon could not be started
  74         start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
  75                 || return 1
  76         start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
  77                 $DAEMON_ARGS \
  78                 || return 2
  79         # Add code here, if necessary, that waits for the process to be ready
  80         # to handle requests from services started subsequently which depend
  81         # on this one.  As a last resort, sleep for some time.
  82 }
  83
  84 #
  85 # Function that stops the daemon/service
  86 #
  87 do_stop()
  88 {
  89         # Return
  90         #   0 if daemon has been stopped
  91         #   1 if daemon was already stopped
  92         #   2 if daemon could not be stopped
  93         #   other if a failure occurred
  94         start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
  95         RETVAL="$?"
  96         [ "$RETVAL" = 2 ] && return 2
  97         # Wait for children to finish too if this is a daemon that forks
  98         # and if the daemon is only ever run from this initscript.
  99         # If the above conditions are not satisfied then add some other code
 100         # that waits for the process to drop all resources that could be
 101         # needed by services started subsequently.  A last resort is to
 102         # sleep for some time.
 103         start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
 104         [ "$?" = 2 ] && return 2
 105         # Many daemons don't delete their pidfiles when they exit.
 106         rm -f $PIDFILE
 107         return "$RETVAL"
 108 }
 109
 110 #
 111 # Function that sends a SIGHUP to the daemon/service
 112 #
 113 do_reload() {
 114         #
 115         # If the daemon can reload its configuration without
 116         # restarting (for example, when it is sent a SIGHUP),
 117         # then implement that here.
 118         #
 119         start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
 120         return 0
 121 }
 122
 123 SCRIPTNAME=$1
 124 scriptbasename="$(basename $1)"
 125 echo "SN: $scriptbasename"
 126 if [ "$scriptbasename" != "init-d-library" ] ; then
 127     script="$1"
 128     shift
 129     . $script
 130 else
 131     exit 0
 132 fi
 133
 134 NAME=$(basename $DAEMON)
 135 PIDFILE=/var/run/$NAME.pid
 136
 137 # Exit if the package is not installed
 138 #[ -x "$DAEMON" ] || exit 0
 139
 140 # Read configuration variable file if it is present
 141 [ -r /etc/default/$NAME ] && . /etc/default/$NAME
 142
 143 # Load the VERBOSE setting and other rcS variables
 144 . /lib/init/vars.sh
 145
 146 case "$1" in
 147   start)
 148         [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
 149         do_start
 150         case "$?" in
 151                 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
 152                 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
 153         esac
 154         ;;
 155   stop)
 156         [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
 157         do_stop
 158         case "$?" in
 159                 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
 160                 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
 161         esac
 162         ;;
 163   status)
 164         status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
 165         ;;
 166   #reload|force-reload)
 167         #
 168         # If do_reload() is not implemented then leave this commented out
 169         # and leave 'force-reload' as an alias for 'restart'.
 170         #
 171         #log_daemon_msg "Reloading $DESC" "$NAME"
 172         #do_reload
 173         #log_end_msg $?
 174         #;;
 175   restart|force-reload)
 176         #
 177         # If the "reload" option is implemented then remove the
 178         # 'force-reload' alias
 179         #
 180         log_daemon_msg "Restarting $DESC" "$NAME"
 181         do_stop
 182         case "$?" in
 183           0|1)
 184                 do_start
 185                 case "$?" in
 186                         0) log_end_msg 0 ;;
 187                         1) log_end_msg 1 ;; # Old process is still running
 188                         *) log_end_msg 1 ;; # Failed to start
 189                 esac
 190                 ;;
 191           *)
 192                 # Failed to stop
 193                 log_end_msg 1
 194                 ;;
 195         esac
 196         ;;
 197   *)
 198         echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
 199         exit 3
 200         ;;
 201 esac
 202
 203 :
 204 </pre></p>
 205
 206 <p>It is based on /etc/init.d/skeleton, and could be improved quite a
 207 lot.  I did not really polish the approach, so it might not always
 208 work out of the box, but you get the idea.  I did not try very hard to
 209 optimize it nor make it more robust either.</p>
 210
 211 <p>A better argument for switching init system in Debian than reducing
 212 the size of init scripts (which is a good thing to do anyway), is to
 213 get boot system that is able to handle the kernel events sensibly and
 214 robustly, and do not depend on the boot to run sequentially.  The boot
 215 and the kernel have not behaved sequentially in year.</p>
 216 </div>
 217       <div class="tags">
 218
 219
 220         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>.
 221
 222
 223       </div>
 224     </div>
 225     <div class="padding"></div>
 226
 227     <div class="entry">
 228       <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>
 229       <div class="date"> 1st November 2013</div>
 230       <div class="body"><p><a href="http://www.spice-space.org/">The SPICE protocol</a> for
 231 remote display access is the preferred solution with oVirt and RedHat
 232 Enterprise Virtualization, and I was sad to discover the other day
 233 that the browser plugin needed to use these systems seamlessly was
 234 missing in Debian.  The <a href="http://bugs.debian.org/668284">request
 235 for a package</a> was from 2012-04-10 with no progress since
 236 2013-04-01, so I decided to wrap up a package based on the great work
 237 from Cajus Pollmeier and put it in a collab-maint maintained git
 238 repository to get a package I could use.  I would very much like
 239 others to help me maintain the package (or just take over, I do not
 240 mind), but as no-one had volunteered so far, I just uploaded it to
 241 NEW.  I hope it will be available in Debian in a few days.</p>
 242
 243 <p>The source is now available from
 244 <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>
 245 </div>
 246       <div class="tags">
 247
 248
 249         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>.
 250
 251
 252       </div>
 253     </div>
 254     <div class="padding"></div>
 255
 256     <div class="entry">
 257       <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>
 258       <div class="date">27th October 2013</div>
 259       <div class="body"><p>The
 260 <a href="http://packages.qa.debian.org/v/vmdebootstrap.html">vmdebootstrap</a>
 261 program is a a very nice system to create virtual machine images.  It
 262 create a image file, add a partition table, mount it and run
 263 debootstrap in the mounted directory to create a Debian system on a
 264 stick.  Yesterday, I decided to try to teach it how to make images for
 265 <a href="https://wiki.debian.org/RaspberryPi">Raspberry Pi</a>, as part
 266 of a plan to simplify the build system for
 267 <a href="https://wiki.debian.org/FreedomBox">the FreedomBox
 268 project</a>.  The FreedomBox project already uses vmdebootstrap for
 269 the virtualbox images, but its current build system made multistrap
 270 based system for Dreamplug images, and it is lacking support for
 271 Raspberry Pi.</p>
 272
 273 <p>Armed with the knowledge on how to build "foreign" (aka non-native
 274 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
 275 code and adjusted it to be able to build armel images on my amd64
 276 Debian laptop.  I ended up giving vmdebootstrap five new options,
 277 allowing me to replicate the image creation process I use to make
 278 <a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian
 279 Jessie based mesh node images for the Raspberry Pi</a>.  First, the
 280 <tt>--foreign /path/to/binfm_handler</tt> option tell vmdebootstrap to
 281 call debootstrap with --foreign and to copy the handler into the
 282 generated chroot before running the second stage.  This allow
 283 vmdebootstrap to create armel images on an amd64 host.  Next I added
 284 two new options <tt>--bootsize size</tt> and <tt>--boottype
 285 fstype</tt> to teach it to create a separate /boot/ partition with the
 286 given file system type, allowing me to create an image with a vfat
 287 partition for the /boot/ stuff.  I also added a <tt>--variant
 288 variant</tt> option to allow me to create smaller images without the
 289 Debian base system packages installed.  Finally, I added an option
 290 <tt>--no-extlinux</tt> to tell vmdebootstrap to not install extlinux
 291 as a boot loader.  It is not needed on the Raspberry Pi and probably
 292 most other non-x86 architectures.  The changes were accepted by the
 293 upstream author of vmdebootstrap yesterday and today, and is now
 294 available from
 295 <a href="http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/">the
 296 upstream project page</a>.</p>
 297
 298 <p>To use it to build a Raspberry Pi image using Debian Jessie, first
 299 create a small script (the customize script) to add the non-free
 300 binary blob needed to boot the Raspberry Pi and the APT source
 301 list:</p>
 302
 303 <p><pre>
 304 #!/bin/sh
 305 set -e # Exit on first error
 306 rootdir="$1"
 307 cd "$rootdir"
 308 cat &lt;&lt;EOF > etc/apt/sources.list
 309 deb http://http.debian.net/debian/ jessie main contrib non-free
 310 EOF
 311 # Install non-free binary blob needed to boot Raspberry Pi.  This
 312 # install a kernel somewhere too.
 313 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
 314     -O $rootdir/usr/bin/rpi-update
 315 chmod a+x $rootdir/usr/bin/rpi-update
 316 mkdir -p $rootdir/lib/modules
 317 touch $rootdir/boot/start.elf
 318 chroot $rootdir rpi-update
 319 </pre></p>
 320
 321 <p>Next, fetch the latest vmdebootstrap script and call it like this
 322 to build the image:</p>
 323
 324 <pre>
 325 sudo ./vmdebootstrap \
 326     --variant minbase \
 327     --arch armel \
 328     --distribution jessie \
 329     --mirror http://http.debian.net/debian \
 330     --image test.img \
 331     --size 600M \
 332     --bootsize 64M \
 333     --boottype vfat \
 334     --log-level debug \
 335     --verbose \
 336     --no-kernel \
 337     --no-extlinux \
 338     --root-password raspberry \
 339     --hostname raspberrypi \
 340     --foreign /usr/bin/qemu-arm-static \
 341     --customize `pwd`/customize \
 342     --package netbase \
 343     --package git-core \
 344     --package binutils \
 345     --package ca-certificates \
 346     --package wget \
 347     --package kmod
 348 </pre></p>
 349
 350 <p>The list of packages being installed are the ones needed by
 351 rpi-update to make the image bootable on the Raspberry Pi, with the
 352 exception of netbase, which is needed by debootstrap to find
 353 /etc/hosts with the minbase variant.  I really wish there was a way to
 354 set up an Raspberry Pi using only packages in the Debian archive, but
 355 that is not possible as far as I know, because it boots from the GPU
 356 using a non-free binary blob.</p>
 357
 358 <p>The build host need debootstrap, kpartx and qemu-user-static and
 359 probably a few others installed.  I have not checked the complete
 360 build dependency list.</p>
 361
 362 <p>The resulting image will not use the hardware floating point unit
 363 on the Raspberry PI, because the armel architecture in Debian is not
 364 optimized for that use.  So the images created will be a bit slower
 365 than <a href="http://www.raspbian.org/">Raspbian</a> based images.</p>
 366 </div>
 367       <div class="tags">
 368
 369
 370         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>.
 371
 372
 373       </div>
 374     </div>
 375     <div class="padding"></div>
 376
 377     <div class="entry">
 378       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Det_er_jo_makta_som_er_mest_s_rbar_ved_massiv_overv_kning_av_Internett.html">Det er jo makta som er mest sårbar ved massiv overvåkning av Internett</a></div>
 379       <div class="date">26th October 2013</div>
 380       <div class="body"><p>De siste måneders eksponering av
 381 <a href="http://www.aftenposten.no/nyheter/uriks/Her-er-Edvard-Snowdens-mest-omtalte-avsloringer-7351734.html">den
 382 totale overvåkningen som foregår i den vestlige verden dokumenterer
 383 hvor sårbare vi er</a>.  Men det slår meg at de som er mest sårbare
 384 for dette, myndighetspersoner på alle nivåer, neppe har innsett at de
 385 selv er de mest interessante personene å lage profiler på, for å kunne
 386 påvirke dem.</p>
 387
 388 <p>For å ta et lite eksempel: Stortingets nettsted,
 389 <a href="http://www.stortinget.no/">www.stortinget.no</a> (og
 390 forsåvidt også
 391 <a href="http://data.stortinget.no/">data.stortinget.no</a>),
 392 inneholder informasjon om det som foregår på Stortinget, og jeg antar
 393 de største brukerne av informasjonen der er representanter og
 394 rådgivere på Stortinget.  Intet overraskende med det.  Det som derimot
 395 er mer skjult er at Stortingets nettsted bruker
 396 <a href="http://en.wikipedia.org/wiki/Google_Analytics">Google
 397 Analytics</a>, hvilket gjør at enhver som besøker nettsidene der også
 398 rapporterer om besøket via Internett-linjer som passerer Sverige,
 399 England og videre til USA.  Det betyr at informasjon om ethvert besøk
 400 på stortingets nettsider kan snappes opp av svensk, britisk og USAs
 401 etterretningsvesen.  De kan dermed holde et øye med hvilke
 402 Stortingssaker stortingsrepresentantene synes er interessante å sjekke
 403 ut, og hvilke sider rådgivere og andre på stortinget synes er
 404 interessant å besøke, når de gjør det og hvilke andre representanter
 405 som sjekker de samme sidene omtrent samtidig.  Stortingets bruk av
 406 Google Analytics gjør det dermed enkelt for utenlands etteretning å
 407 spore representantenes aktivitet og interesse.  Hvis noen av
 408 representantene bruker Google Mail eller noen andre tjenestene som
 409 krever innlogging, så vil det være enda enklere å finne ut nøyaktig
 410 hvilke personer som bruker hvilke nettlesere og dermed knytte
 411 informasjonen opp til enkeltpersoner på Stortinget.</p>
 412
 413 <p>Og jo flere nettsteder som bruker Google Analytics, jo bedre
 414 oversikt over stortingsrepresentantenes lesevaner og interesse blir
 415 tilgjengelig for svensk, britisk og USAs etterretning.  Hva de kan
 416 bruke den informasjonen til overlater jeg til leseren å undres
 417 over.</p>
 418 </div>
 419       <div class="tags">
 420
 421
 422         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 423
 424
 425       </div>
 426     </div>
 427     <div class="padding"></div>
 428
 429     <div class="entry">
 430       <div class="title"><a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">A Raspberry Pi based batman-adv Mesh network node</a></div>
 431       <div class="date">21st October 2013</div>
 432       <div class="body"><p>The last few days I have been experimenting with
 433 <a href="http://www.open-mesh.org/projects/batman-adv/wiki">the
 434 batman-adv mesh technology</a>.  I want to gain some experience to see
 435 if it will fit <a href="https://wiki.debian.org/FreedomBox">the
 436 Freedombox project</a>, and together with my neighbors try to build a
 437 mesh network around the park where I live.  Batman-adv is a layer 2
 438 mesh system ("ethernet" in other words), where the mesh network appear
 439 as if all the mesh clients are connected to the same switch.</p>
 440
 441 <p>My hardware of choice was the Linksys WRT54GL routers I had lying
 442 around, but I've been unable to get them working with batman-adv.  So
 443 instead, I started playing with a
 444 <a href="http://www.raspberrypi.org/">Raspberry Pi</a>, and tried to
 445 get it working as a mesh node.  My idea is to use it to create a mesh
 446 node which function as a switch port, where everything connected to
 447 the Raspberry Pi ethernet plug is connected (bridged) to the mesh
 448 network.  This allow me to hook a wifi base station like the Linksys
 449 WRT54GL to the mesh by plugging it into a Raspberry Pi, and allow
 450 non-mesh clients to hook up to the mesh.  This in turn is useful for
 451 Android phones using <a href="http://servalproject.org/">the Serval
 452 Project</a> voip client, allowing every one around the playground to
 453 phone and message each other for free.  The reason is that Android
 454 phones do not see ad-hoc wifi networks (they are filtered away from
 455 the GUI view), and can not join the mesh without being rooted.  But if
 456 they are connected using a normal wifi base station, they can talk to
 457 every client on the local network.</p>
 458
 459 <p>To get this working, I've created a debian package
 460 <a href="https://github.com/petterreinholdtsen/meshfx-node">meshfx-node</a>
 461 and a script
 462 <a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/build-rpi-mesh-node">build-rpi-mesh-node</a>
 463 to create the Raspberry Pi boot image.  I'm using Debian Jessie (and
 464 not Raspbian), to get more control over the packages available.
 465 Unfortunately a huge binary blob need to be inserted into the boot
 466 image to get it booting, but I'll ignore that for now.  Also, as
 467 Debian lack support for the CPU features available in the Raspberry
 468 Pi, the system do not use the hardware floating point unit.  I hope
 469 the routing performance isn't affected by the lack of hardware FPU
 470 support.</p>
 471
 472 <p>To create an image, run the following with a sudo enabled user
 473 after inserting the target SD card into the build machine:</p>
 474
 475 <p><pre>
 476 % wget -O build-rpi-mesh-node \
 477     https://raw.github.com/petterreinholdtsen/meshfx-node/master/build-rpi-mesh-node
 478 % sudo bash -x ./build-rpi-mesh-node > build.log 2>&1
 479 % dd if=/root/rpi/rpi_basic_jessie_$(date +%Y%m%d).img of=/dev/mmcblk0 bs=1M
 480 %
 481 </pre></p>
 482
 483 <p>Booting with the resulting SD card on a Raspberry PI with a USB
 484 wifi card inserted should give you a mesh node.  At least it does for
 485 me with a the wifi card I am using. The default mesh settings are the
 486 ones used by the Oslo mesh project at Hackeriet, as I mentioned in
 487 <a href="http://people.skolelinux.org/pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html">an
 488 earlier blog post about this mesh testing</a>.</p>
 489
 490 <p>The mesh node was not horribly expensive either.  I bought
 491 everything over the counter in shops nearby.  If I had ordered online
 492 from the lowest bidder, the price should be significantly lower:</p>
 493
 494 <p><table>
 495
 496 <tr><th>Supplier</th><th>Model</th><th>NOK</th></tr>
 497 <tr><td>Teknikkmagasinet</td><td>Raspberry Pi model B</td><td>349.90</td></tr>
 498 <tr><td>Teknikkmagasinet</td><td>Raspberry Pi type B case</td><td>99.90</td></tr>
 499 <tr><td>Lefdal</td><td>Jensen Air:Link 25150</td><td>295.-</td></tr>
 500 <tr><td>Clas Ohlson</td><td>Kingston 16 GB SD card</td><td>199.-</td></tr>
 501 <tr><td>Total cost</td><td></td><td>943.80</td></tr>
 502
 503 </table></p>
 504
 505 <p>Now my mesh network at home consist of one laptop in the basement
 506 connected to my production network, one Raspberry Pi node on the 1th
 507 floor that can be seen by my neighbor across the park, and one
 508 play-node I use to develop the image building script.  And some times
 509 I hook up my work horse laptop to the mesh to test it.  I look forward
 510 to figuring out what kind of latency the batman-adv setup will give,
 511 and how much packet loss we will experience around the park. :)</p>
 512 </div>
 513       <div class="tags">
 514
 515
 516         Tags: <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>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 517
 518
 519       </div>
 520     </div>
 521     <div class="padding"></div>
 522
 523     <div class="entry">
 524       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Perl_library_to_control_the_Spykee_robot_moved_to_github.html">Perl library to control the Spykee robot moved to github</a></div>
 525       <div class="date">19th October 2013</div>
 526       <div class="body"><p>Back in 2010, I created a Perl library to talk to
 527 <a href="http://en.wikipedia.org/wiki/Spykee">the Spykee robot</a>
 528 (with two belts, wifi, USB and Linux) and made it available from my
 529 web page.  Today I concluded that it should move to a site that is
 530 easier to use to cooperate with others, and moved it to github.  If
 531 you got a Spykee robot, you might want to check out
 532 <a href="https://github.com/petterreinholdtsen/libspykee-perl">the
 533 libspykee-perl github repository</a>.</p>
 534 </div>
 535       <div class="tags">
 536
 537
 538         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/robot">robot</a>.
 539
 540
 541       </div>
 542     </div>
 543     <div class="padding"></div>
 544
 545     <div class="entry">
 546       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html">Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</a></div>
 547       <div class="date">15th October 2013</div>
 548       <div class="body"><p>The last few days I came across a few good causes that should get
 549 wider attention.  I recommend signing and donating to each one of
 550 these. :)</p>
 551
 552 <p>Via <a href="http://www.debian.org/News/weekly/2013/18/">Debian
 553 Project News for 2013-10-14</a> I came across the Outreach Program for
 554 Women program which is a Google Summer of Code like initiative to get
 555 more women involved in free software.  One debian sponsor has offered
 556 to match <a href="http://debian.ch/opw2013">any donation done to Debian
 557 earmarked</a> for this initiative.  I donated a few minutes ago, and
 558 hope you will to. :)</p>
 559
 560 <p>And the Electronic Frontier Foundation just announced plans to
 561 create <a href="https://supporters.eff.org/donate/nsa-videos">video
 562 documentaries about the excessive spying</a> on every Internet user that
 563 take place these days, and their need to fund the work.  I've already
 564 donated.  Are you next?</p>
 565
 566 <p>For my Norwegian audience, the organisation Studentenes og
 567 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
 568 statement under the heading
 569 <a href="http://saih.no/Bloggers_United/">Bloggers United for Open
 570 Access</a> for those of us asking for more focus on open access in the
 571 Norwegian government.  So far 499 signatures.  I hope you will sign it
 572 too.</p>
 573 </div>
 574       <div class="tags">
 575
 576
 577         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/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>.
 578
 579
 580       </div>
 581     </div>
 582     <div class="padding"></div>
 583
 584     <div class="entry">
 585       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html">Oslo community mesh network - with NUUG and Hackeriet at Hausmania</a></div>
 586       <div class="date">11th October 2013</div>
 587       <div class="body"><p>Wireless mesh networks are self organising and self healing
 588 networks that can be used to connect computers across small and large
 589 areas, depending on the radio technology used.  Normal wifi equipment
 590 can be used to create home made radio networks, and there are several
 591 successful examples like
 592 <a href="http://www.freifunk.net/">Freifunk</a> and
 593 <a href="http://www.awmn.net/">Athens Wireless Metropolitan Network</a>
 594 (see
 595 <a href="http://en.wikipedia.org/wiki/List_of_wireless_community_networks_by_region#Greece">wikipedia
 596 for a large list</a>) around the globe.  To give you an idea how it
 597 work, check out the nice overview of the Kiel Freifunk community which
 598 can be seen from their
 599 <a href="http://freifunk.in-kiel.de/ffmap/nodes.html">dynamically
 600 updated node graph and map</a>, where one can see how the mesh nodes
 601 automatically handle routing and recover from nodes disappearing.
 602 There is also a small community mesh network group in Oslo, Norway,
 603 and that is the main topic of this blog post.</p>
 604
 605 <p>I've wanted to check out mesh networks for a while now, and hoped
 606 to do it as part of my involvement with the <a
 607 href="http://www.nuug.no/">NUUG member organisation</a> community, and
 608 my recent involvement in
 609 <a href="https://wiki.debian.org/FreedomBox">the Freedombox project</a>
 610 finally lead me to give mesh networks some priority, as I suspect a
 611 Freedombox should use mesh networks to connect neighbours and family
 612 when possible, given that most communication between people are
 613 between those nearby (as shown for example by research on Facebook
 614 communication patterns).  It also allow people to communicate without
 615 any central hub to tap into for those that want to listen in on the
 616 private communication of citizens, which have become more and more
 617 important over the years.</p>
 618
 619 <p>So far I have only been able to find one group of people in Oslo
 620 working on community mesh networks, over at the hack space
 621 <a href="http://hackeriet.no/">Hackeriet</a> at Husmania.  They seem to
 622 have started with some Freifunk based effort using OLSR, called
 623 <a href="http://oslo.freifunk.net/index.php?title=Main_Page">the Oslo
 624 Freifunk project</a>, but that effort is now dead and the people
 625 behind it have moved on to a batman-adv based system called
 626 <a href="http://meshfx.org/trac">meshfx</a>.  Unfortunately the wiki
 627 site for the Oslo Freifunk project is no longer possible to update to
 628 reflect this fact, so the old project page can't be updated to point to
 629 the new project.  A while back, the people at Hackeriet invited people
 630 from the Freifunk community to Oslo to talk about mesh networks.  I
 631 came across this video where Hans Jørgen Lysglimt interview the
 632 speakers about this talk (from
 633 <a href="https://www.youtube.com/watch?v=N2Kd7CLkhSY">youtube</a>):</p>
 634
 635 <p><iframe width="420" height="315" src="https://www.youtube.com/embed/N2Kd7CLkhSY" frameborder="0" allowfullscreen></iframe></p>
 636
 637 <p>I mentioned OLSR and batman-adv, which are mesh routing protocols.
 638 There are heaps of different protocols, and I am still struggling to
 639 figure out which one would be "best" for some definitions of best, but
 640 given that the community mesh group in Oslo is so small, I believe it
 641 is best to hook up with the existing one instead of trying to create a
 642 completely different setup, and thus I have decided to focus on
 643 batman-adv for now.  It sure help me to  know that the very cool
 644 <a href="http://www.servalproject.org/">Serval project in Australia</a>
 645 is using batman-adv as their meshing technology when it create a self
 646 organizing and self healing telephony system for disaster areas and
 647 less industrialized communities.  Check out this cool video presenting
 648 that project (from
 649 <a href="https://www.youtube.com/watch?v=30qNfzJCQOA">youtube</a>):</p>
 650
 651 <p><iframe width="560" height="315" src="https://www.youtube.com/embed/30qNfzJCQOA" frameborder="0" allowfullscreen></iframe></p>
 652
 653 <p>According to the wikipedia page on
 654 <a href="http://en.wikipedia.org/wiki/Wireless_mesh_network">Wireless
 655 mesh network</a> there are around 70 competing schemes for routing
 656 packets across mesh networks, and OLSR, B.A.T.M.A.N. and
 657 B.A.T.M.A.N. advanced are protocols used by several free software
 658 based community mesh networks.</p>
 659
 660 <p>The batman-adv protocol is a bit special, as it provide layer 2
 661 (as in ethernet ) routing, allowing ipv4 and ipv6 to work on the same
 662 network.  One way to think about it is that it provide a mesh based
 663 vlan you can bridge to or handle like any other vlan connected to your
 664 computer.  The required drivers are already in the Linux kernel at
 665 least since Debian Wheezy, and it is fairly easy to set up.  A
 666 <a href="http://www.open-mesh.org/projects/batman-adv/wiki/Quick-start-guide">good
 667 introduction</a> is available from the Open Mesh project.  These are
 668 the key settings needed to join the Oslo meshfx network:</p>
 669
 670 <p><table>
 671 <tr><th>Setting</th><th>Value</th></tr>
 672 <tr><td>Protocol / kernel module</td><td>batman-adv</td></tr>
 673 <tr><td>ESSID</td><td>meshfx@hackeriet</td></tr>
 674 <td>Channel / Frequency</td><td>11 / 2462</td></tr>
 675 <td>Cell ID</td><td>02:BA:00:00:00:01</td>
 676 </table></p>
 677
 678 <p>The reason for setting ad-hoc wifi Cell ID is to work around bugs
 679 in firmware used in wifi card and wifi drivers.  (See a nice post from
 680 VillageTelco about
 681 "<a href="http://tiebing.blogspot.no/2009/12/ad-hoc-cell-splitting-re-post-original.html">Information
 682 about cell-id splitting, stuck beacons, and failed IBSS merges!</a>
 683 for details.)  When these settings are activated and you have some
 684 other mesh node nearby, your computer will be connected to the mesh
 685 network and can communicate with any mesh node that is connected to
 686 any of the nodes in your network of nodes. :)</p>
 687
 688 <p>My initial plan was to reuse my old Linksys WRT54GL as a mesh node,
 689 but that seem to be very hard, as I have not been able to locate a
 690 firmware supporting batman-adv.  If anyone know how to use that old
 691 wifi access point with batman-adv these days, please let me know.</p>
 692
 693 <p>If you find this project interesting and want to join, please join
 694 us on IRC, either channel
 695 <a href="irc://irc.freenode.net/#oslohackerspace">#oslohackerspace</a>
 696 or <a href="irc://irc.freenode.net/#nuug">#nuug</a> on
 697 irc.freenode.net.</p>
 698
 699 <p>While investigating mesh networks in Oslo, I came across an old
 700 research paper from the university of Stavanger and Telenor Research
 701 and Innovation called
 702 <a href="http://folk.uio.no/paalee/publications/netrel-egeland-iswcs-2008.pdf">The
 703 reliability of wireless backhaul mesh networks</a> and elsewhere
 704 learned that Telenor have been experimenting with mesh networks at
 705 Grünerløkka in Oslo.  So mesh networks are also interesting for
 706 commercial companies, even though Telenor discovered that it was hard
 707 to figure out a good business plan for mesh networking and as far as I
 708 know have closed down the experiment.  Perhaps Telenor or others would
 709 be interested in a cooperation?</p>
 710
 711 <p><strong>Update 2013-10-12</strong>: I was just
 712 <a href="http://lists.alioth.debian.org/pipermail/freedombox-discuss/2013-October/005900.html">told
 713 by the Serval project developers</a> that they no longer use
 714 batman-adv (but are compatible with it), but their own crypto based
 715 mesh system.</p>
 716 </div>
 717       <div class="tags">
 718
 719
 720         Tags: <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>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>.
 721
 722
 723       </div>
 724     </div>
 725     <div class="padding"></div>
 726
 727     <div class="entry">
 728       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Skolelinux___Debian_Edu_7_1_install_and_overview_video_from_Marcelo_Salvador.html">Skolelinux / Debian Edu 7.1 install and overview video from Marcelo Salvador</a></div>
 729       <div class="date"> 8th October 2013</div>
 730       <div class="body"><p>The other day I was pleased and surprised to discover that Marcelo
 731 Salvador had published a
 732 <a href="https://www.youtube.com/watch?v=w-GgpdqgLFc">video on
 733 Youtube</a> showing how to install the standalone Debian Edu /
 734 Skolelinux profile.  This is the profile intended for use at home or
 735 on laptops that should not be integrated into the provided network
 736 services (no central home directory, no Kerberos / LDAP directory etc,
 737 in other word a single user machine).  The result is 11 minutes long,
 738 and show some user applications (seem to be rather randomly picked).
 739 Missed a few of my favorites like celestia, planets and chromium
 740 showing the <a href="http://www.zygotebody.com/">Zygote Body 3D model
 741 of the human body</a>, but I guess he did not know about those or find
 742 other programs more interesting. :) And the video do not show the
 743 advantages I believe is one of the most valuable featuers in Debian
 744 Edu, its central school server making it possible to run hundreds of
 745 computers without hard drives by installing one central
 746 <a href="http://www.ltsp.org/">LTSP server</a>.</p>
 747
 748 <p>Anyway, check out the video, embedded below and linked to above:</p>
 749
 750 <iframe width="420" height="315" src="http://www.youtube.com/embed/w-GgpdqgLFc" frameborder="0" allowfullscreen></iframe>
 751
 752 <p>Are there other nice videos demonstrating Skolelinux?  Please let
 753 me know. :)</p>
 754 </div>
 755       <div class="tags">
 756
 757
 758         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/video">video</a>.
 759
 760
 761       </div>
 762     </div>
 763     <div class="padding"></div>
 764
 765     <div class="entry">
 766       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Finally__Debian_Edu_Wheezy_is_released_today_.html">Finally, Debian Edu Wheezy is released today!</a></div>
 767       <div class="date">29th September 2013</div>
 768       <div class="body"><p>A few hours ago, the announcement for the first stable release of
 769 Debian Edu Wheezy went out from the Debian publicity team.  The
 770 complete announcement text can be found at
 771 <a href="http://www.debian.org/News/2013/20130928">the Debian News
 772 section</a>, translated to several languages.  Please check it out.</p>
 773
 774 <p>There is one minor known problem that we will fix very soon.  One
 775 can not install a amd64 Thin Client Server using PXE, as the /var/
 776 partition is too small.  A workaround is to extend the partition (use
 777 lvresize + resize2fs in tty 2 while installing).</p>
 778 </div>
 779       <div class="tags">
 780
 781
 782         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>.
 783
 784
 785       </div>
 786     </div>
 787     <div class="padding"></div>
 788
 789     <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>
 790     <div id="sidebar">
 791
 792
 793
 794 <h2>Archive</h2>
 795 <ul>
 796
 797 <li>2013
 798 <ul>
 799
 800 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 801
 802 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 803
 804 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 805
 806 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 807
 808 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 809
 810 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 811
 812 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 813
 814 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 815
 816 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 817
 818 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 819
 820 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (2)</a></li>
 821
 822 </ul></li>
 823
 824 <li>2012
 825 <ul>
 826
 827 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 828
 829 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 830
 831 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 832
 833 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 834
 835 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 836
 837 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 838
 839 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 840
 841 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 842
 843 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 844
 845 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 846
 847 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 848
 849 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 850
 851 </ul></li>
 852
 853 <li>2011
 854 <ul>
 855
 856 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 857
 858 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 859
 860 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 861
 862 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 863
 864 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 865
 866 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 867
 868 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 869
 870 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 871
 872 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 873
 874 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 875
 876 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 877
 878 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 879
 880 </ul></li>
 881
 882 <li>2010
 883 <ul>
 884
 885 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 886
 887 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 888
 889 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 890
 891 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 892
 893 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 894
 895 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 896
 897 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 898
 899 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 900
 901 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 902
 903 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 904
 905 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 906
 907 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 908
 909 </ul></li>
 910
 911 <li>2009
 912 <ul>
 913
 914 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 915
 916 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 917
 918 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 919
 920 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 921
 922 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 923
 924 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 925
 926 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 927
 928 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 929
 930 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 931
 932 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 933
 934 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 935
 936 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 937
 938 </ul></li>
 939
 940 <li>2008
 941 <ul>
 942
 943 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 944
 945 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 946
 947 </ul></li>
 948
 949 </ul>
 950
 951
 952
 953 <h2>Tags</h2>
 954 <ul>
 955
 956  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
 957
 958  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 959
 960  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 961
 962  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
 963
 964  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (7)</a></li>
 965
 966  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (13)</a></li>
 967
 968  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 969
 970  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (90)</a></li>
 971
 972  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (142)</a></li>
 973
 974  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
 975
 976  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
 977
 978  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 979
 980  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (225)</a></li>
 981
 982  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
 983
 984  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
 985
 986  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
 987
 988  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (5)</a></li>
 989
 990  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
 991
 992  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (37)</a></li>
 993
 994  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
 995
 996  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
 997
 998  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
 999
1000  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (6)</a></li>
1001
1002  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1003
1004  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (3)</a></li>
1005
1006  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (25)</a></li>
1007
1008  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (236)</a></li>
1009
1010  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (156)</a></li>
1011
1012  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (8)</a></li>
1013
1014  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1015
1016  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (45)</a></li>
1017
1018  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (67)</a></li>
1019
1020  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1021
1022  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1023
1024  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1025
1026  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (8)</a></li>
1027
1028  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1029
1030  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1031
1032  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1033
1034  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (32)</a></li>
1035
1036  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1037
1038  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1039
1040  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (43)</a></li>
1041
1042  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1043
1044  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1045
1046  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (20)</a></li>
1047
1048  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1049
1050  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1051
1052  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (39)</a></li>
1053
1054  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1055
1056  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (28)</a></li>
1057
1058 </ul>
1059
1060
1061     </div>
1062     <p style="text-align: right">
1063  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1064 </p>
1065
1066   </body>
1067 </html>