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/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>
  24       <div class="date">21st November 2013</div>
  25       <div class="body">Drones, flying robots, are getting more and more popular.  The most
  26 know ones are the killer drones used by some government to murder
  27 people they do not like without giving them the chance of a fair
  28 trial, but the technology have many good uses too, from mapping and
  29 forest maintenance to photography and search and rescue.  I am sure it
  30 is just a question of time before "bad drones" are in the hands of
  31 private enterprises and not only state criminals but petty criminals
  32 too.  The drone technology is very useful and very dangerous.  To have
  33 some control over the use of drones, I agree with Daniel Suarez in his
  34 TED talk
  35 "<a href="https://archive.org/details/DanielSuarez_2013G">The kill
  36 decision shouldn't belong to a robot</a>", where he suggested this
  37 little gem to keep the good while limiting the bad use of drones:</p>
  38
  39 <blockquote>
  40
  41 <p>Each robot and drone should have a cryptographically signed
  42 I.D. burned in at the factory that can be used to track its movement
  43 through public spaces. We have license plates on cars, tail numbers on
  44 aircraft. This is no different. And every citizen should be able to
  45 download an app that shows the population of drones and autonomous
  46 vehicles moving through public spaces around them, both right now and
  47 historically. And civic leaders should deploy sensors and civic drones
  48 to detect rogue drones, and instead of sending killer drones of their
  49 own up to shoot them down, they should notify humans to their
  50 presence. And in certain very high-security areas, perhaps civic
  51 drones would snare them and drag them off to a bomb disposal facility.</p>
  52
  53 <p>But notice, this is more an immune system than a weapons system. It
  54 would allow us to avail ourselves of the use of autonomous vehicles
  55 and drones while still preserving our open, civil society.</p>
  56
  57 </blockquote>
  58
  59 <p>The key is that <em>every citizen</em> should be able to read the
  60 radio beacons sent from the drones in the area, to be able to check
  61 both the government and others use of drones.  For such control to be
  62 effective, everyone must be able to do it.  What should such beacon
  63 contain?  At least formal owner, purpose, contact information and GPS
  64 location.  Probably also the origin and target position of the current
  65 flight.  And perhaps some registration number to be able to look up
  66 the drone in a central database tracking their movement.  Robots
  67 should not have privacy.  It is people who need privacy.</p>
  68 </div>
  69       <div class="tags">
  70
  71
  72         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>.
  73
  74
  75       </div>
  76     </div>
  77     <div class="padding"></div>
  78
  79     <div class="entry">
  80       <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>
  81       <div class="date">13th November 2013</div>
  82       <div class="body"><p>Today NUUG and Hackeriet announced
  83 <a href="http://www.nuug.no/news/Bli_med___bygge_dugnadsnett_for_alle_i_Oslo.shtml">our
  84 plans to join forces and create a wireless community network in
  85 Oslo</a>.  The workshop to help people get started will take place
  86 Thursday 2013-11-28, but we already are collecting the geolocation of
  87 people joining forces to make this happen.  We have
  88 <a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/oslo-nodes.geojson">9
  89 locations plotted on the map</a>, but we will need more before we have
  90 a connected mesh spread across Oslo.  If this sound interesting to
  91 you, please join us at the workshop.  If you are too impatient to wait
  92 15 days, please join us on the IRC channel
  93 <a href="irc://irc.freenode.net/%23nuug">#nuug on irc.freenode.net</a>
  94 right away. :)</p>
  95 </div>
  96       <div class="tags">
  97
  98
  99         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>.
 100
 101
 102       </div>
 103     </div>
 104     <div class="padding"></div>
 105
 106     <div class="entry">
 107       <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>
 108       <div class="date">10th November 2013</div>
 109       <div class="body"><p>Continuing my research into mesh networking, I was recommended to
 110 use TP-Link 3040 and 3600 access points as mesh nodes, and the pair I
 111 bought arrived on Friday.  Here are my notes on how to set up the
 112 MR3040 as a mesh node using
 113 <a href="http://www.openwrt.org/">OpenWrt</a>.</p>
 114
 115 <p>I started by following the instructions on the OpenWRT wiki for
 116 <a href="http://wiki.openwrt.org/toh/tp-link/tl-mr3040">TL-MR3040</a>,
 117 and downloaded
 118 <a href="http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin">the
 119 recommended firmware image</a>
 120 (openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin) and
 121 uploaded it into the original web interface.  The flashing went fine,
 122 and the machine was available via telnet on the ethernet port.  After
 123 logging in and setting the root password, ssh was available and I
 124 could start to set it up as a batman-adv mesh node.</p>
 125
 126 <p>I started off by reading the instructions from
 127 <a href="http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine's_Research">Wireless
 128 Africa</a>, which had quite a lot of useful information, but
 129 eventually I followed the recipe from the Open Mesh wiki for
 130 <a href="http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config">using
 131 batman-adv on OpenWrt</a>.  A small snag was the fact that the
 132 <tt>opkg install kmod-batman-adv</tt> command did not work as it
 133 should.  The batman-adv kernel module would fail to load because its
 134 dependency crc16 was not already loaded.  I
 135 <a href="https://dev.openwrt.org/ticket/14452">reported the bug</a> to
 136 the openwrt project and hope it will be fixed soon.  But the problem
 137 only seem to affect initial testing of batman-adv, as configuration
 138 seem to work when booting from scratch.</p>
 139
 140 <p>The setup is done using files in /etc/config/.  I did not bridge
 141 the Ethernet and mesh interfaces this time, to be able to hook up the
 142 box on my local network and log into it for configuration updates.
 143 The following files were changed and look like this after modifying
 144 them:</p>
 145
 146 <p><tt>/etc/config/network</tt></p>
 147
 148 <pre>
 149
 150 config interface 'loopback'
 151         option ifname 'lo'
 152         option proto 'static'
 153         option ipaddr '127.0.0.1'
 154         option netmask '255.0.0.0'
 155
 156 config globals 'globals'
 157         option ula_prefix 'fdbf:4c12:3fed::/48'
 158
 159 config interface 'lan'
 160         option ifname 'eth0'
 161         option type 'bridge'
 162         option proto 'dhcp'
 163         option ipaddr '192.168.1.1'
 164         option netmask '255.255.255.0'
 165         option hostname 'tl-mr3040'
 166         option ip6assign '60'
 167
 168 config interface 'mesh'
 169         option ifname 'adhoc0'
 170         option mtu '1528'
 171         option proto 'batadv'
 172         option mesh 'bat0'
 173 </pre>
 174
 175 <p><tt>/etc/config/wireless</tt></p>
 176 <pre>
 177
 178 config wifi-device 'radio0'
 179         option type 'mac80211'
 180         option channel '11'
 181         option hwmode '11ng'
 182         option path 'platform/ar933x_wmac'
 183         option htmode 'HT20'
 184         list ht_capab 'SHORT-GI-20'
 185         list ht_capab 'SHORT-GI-40'
 186         list ht_capab 'RX-STBC1'
 187         list ht_capab 'DSSS_CCK-40'
 188         option disabled '0'
 189
 190 config wifi-iface 'wmesh'
 191         option device 'radio0'
 192         option ifname 'adhoc0'
 193         option network 'mesh'
 194         option encryption 'none'
 195         option mode 'adhoc'
 196         option bssid '02:BA:00:00:00:01'
 197         option ssid 'meshfx@hackeriet'
 198 </pre>
 199 <p><tt>/etc/config/batman-adv</tt></p>
 200 <pre>
 201
 202 config 'mesh' 'bat0'
 203         option interfaces 'adhoc0'
 204         option 'aggregated_ogms'
 205         option 'ap_isolation'
 206         option 'bonding'
 207         option 'fragmentation'
 208         option 'gw_bandwidth'
 209         option 'gw_mode'
 210         option 'gw_sel_class'
 211         option 'log_level'
 212         option 'orig_interval'
 213         option 'vis_mode'
 214         option 'bridge_loop_avoidance'
 215         option 'distributed_arp_table'
 216         option 'network_coding'
 217         option 'hop_penalty'
 218
 219 # yet another batX instance
 220 # config 'mesh' 'bat5'
 221 #       option 'interfaces' 'second_mesh'
 222 </pre>
 223
 224 <p>The mesh node is now operational.  I have yet to test its range,
 225 but I hope it is good.  I have not yet tested the TP-Link 3600 box
 226 still wrapped up in plastic.</p>
 227 </div>
 228       <div class="tags">
 229
 230
 231         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>.
 232
 233
 234       </div>
 235     </div>
 236     <div class="padding"></div>
 237
 238     <div class="entry">
 239       <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>
 240       <div class="date"> 2nd November 2013</div>
 241       <div class="body"><p>If one of the points of switching to a new init system in Debian is
 242 <a href="http://thomas.goirand.fr/blog/?p=147">to get rid of huge
 243 init.d scripts</a>, I doubt we need to switch away from sysvinit and
 244 init.d scripts at all.  Here is an example init.d script, ie a rewrite
 245 of /etc/init.d/rsyslog:</p>
 246
 247 <p><pre>
 248 #!/lib/init/init-d-script
 249 ### BEGIN INIT INFO
 250 # Provides:          rsyslog
 251 # Required-Start:    $remote_fs $time
 252 # Required-Stop:     umountnfs $time
 253 # X-Stop-After:      sendsigs
 254 # Default-Start:     2 3 4 5
 255 # Default-Stop:      0 1 6
 256 # Short-Description: enhanced syslogd
 257 # Description:       Rsyslog is an enhanced multi-threaded syslogd.
 258 #                    It is quite compatible to stock sysklogd and can be
 259 #                    used as a drop-in replacement.
 260 ### END INIT INFO
 261 DESC="enhanced syslogd"
 262 DAEMON=/usr/sbin/rsyslogd
 263 </pre></p>
 264
 265 <p>Pretty minimalistic to me... For the record, the original sysv-rc
 266 script was 137 lines, and the above is just 15 lines, most of it meta
 267 info/comments.</p>
 268
 269 <p>How to do this, you ask?  Well, one create a new script
 270 /lib/init/init-d-script looking something like this:
 271
 272 <p><pre>
 273 #!/bin/sh
 274
 275 # Define LSB log_* functions.
 276 # Depend on lsb-base (>= 3.2-14) to ensure that this file is present
 277 # and status_of_proc is working.
 278 . /lib/lsb/init-functions
 279
 280 #
 281 # Function that starts the daemon/service
 282
 283 #
 284 do_start()
 285 {
 286         # Return
 287         #   0 if daemon has been started
 288         #   1 if daemon was already running
 289         #   2 if daemon could not be started
 290         start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \
 291                 || return 1
 292         start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
 293                 $DAEMON_ARGS \
 294                 || return 2
 295         # Add code here, if necessary, that waits for the process to be ready
 296         # to handle requests from services started subsequently which depend
 297         # on this one.  As a last resort, sleep for some time.
 298 }
 299
 300 #
 301 # Function that stops the daemon/service
 302 #
 303 do_stop()
 304 {
 305         # Return
 306         #   0 if daemon has been stopped
 307         #   1 if daemon was already stopped
 308         #   2 if daemon could not be stopped
 309         #   other if a failure occurred
 310         start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
 311         RETVAL="$?"
 312         [ "$RETVAL" = 2 ] && return 2
 313         # Wait for children to finish too if this is a daemon that forks
 314         # and if the daemon is only ever run from this initscript.
 315         # If the above conditions are not satisfied then add some other code
 316         # that waits for the process to drop all resources that could be
 317         # needed by services started subsequently.  A last resort is to
 318         # sleep for some time.
 319         start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
 320         [ "$?" = 2 ] && return 2
 321         # Many daemons don't delete their pidfiles when they exit.
 322         rm -f $PIDFILE
 323         return "$RETVAL"
 324 }
 325
 326 #
 327 # Function that sends a SIGHUP to the daemon/service
 328 #
 329 do_reload() {
 330         #
 331         # If the daemon can reload its configuration without
 332         # restarting (for example, when it is sent a SIGHUP),
 333         # then implement that here.
 334         #
 335         start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
 336         return 0
 337 }
 338
 339 SCRIPTNAME=$1
 340 scriptbasename="$(basename $1)"
 341 echo "SN: $scriptbasename"
 342 if [ "$scriptbasename" != "init-d-library" ] ; then
 343     script="$1"
 344     shift
 345     . $script
 346 else
 347     exit 0
 348 fi
 349
 350 NAME=$(basename $DAEMON)
 351 PIDFILE=/var/run/$NAME.pid
 352
 353 # Exit if the package is not installed
 354 #[ -x "$DAEMON" ] || exit 0
 355
 356 # Read configuration variable file if it is present
 357 [ -r /etc/default/$NAME ] && . /etc/default/$NAME
 358
 359 # Load the VERBOSE setting and other rcS variables
 360 . /lib/init/vars.sh
 361
 362 case "$1" in
 363   start)
 364         [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
 365         do_start
 366         case "$?" in
 367                 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
 368                 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
 369         esac
 370         ;;
 371   stop)
 372         [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
 373         do_stop
 374         case "$?" in
 375                 0|1) [ "$VERBOSE" != no ] && log_end_msg 0 ;;
 376                 2) [ "$VERBOSE" != no ] && log_end_msg 1 ;;
 377         esac
 378         ;;
 379   status)
 380         status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
 381         ;;
 382   #reload|force-reload)
 383         #
 384         # If do_reload() is not implemented then leave this commented out
 385         # and leave 'force-reload' as an alias for 'restart'.
 386         #
 387         #log_daemon_msg "Reloading $DESC" "$NAME"
 388         #do_reload
 389         #log_end_msg $?
 390         #;;
 391   restart|force-reload)
 392         #
 393         # If the "reload" option is implemented then remove the
 394         # 'force-reload' alias
 395         #
 396         log_daemon_msg "Restarting $DESC" "$NAME"
 397         do_stop
 398         case "$?" in
 399           0|1)
 400                 do_start
 401                 case "$?" in
 402                         0) log_end_msg 0 ;;
 403                         1) log_end_msg 1 ;; # Old process is still running
 404                         *) log_end_msg 1 ;; # Failed to start
 405                 esac
 406                 ;;
 407           *)
 408                 # Failed to stop
 409                 log_end_msg 1
 410                 ;;
 411         esac
 412         ;;
 413   *)
 414         echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}" >&2
 415         exit 3
 416         ;;
 417 esac
 418
 419 :
 420 </pre></p>
 421
 422 <p>It is based on /etc/init.d/skeleton, and could be improved quite a
 423 lot.  I did not really polish the approach, so it might not always
 424 work out of the box, but you get the idea.  I did not try very hard to
 425 optimize it nor make it more robust either.</p>
 426
 427 <p>A better argument for switching init system in Debian than reducing
 428 the size of init scripts (which is a good thing to do anyway), is to
 429 get boot system that is able to handle the kernel events sensibly and
 430 robustly, and do not depend on the boot to run sequentially.  The boot
 431 and the kernel have not behaved sequentially in years.</p>
 432 </div>
 433       <div class="tags">
 434
 435
 436         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>.
 437
 438
 439       </div>
 440     </div>
 441     <div class="padding"></div>
 442
 443     <div class="entry">
 444       <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>
 445       <div class="date"> 1st November 2013</div>
 446       <div class="body"><p><a href="http://www.spice-space.org/">The SPICE protocol</a> for
 447 remote display access is the preferred solution with oVirt and RedHat
 448 Enterprise Virtualization, and I was sad to discover the other day
 449 that the browser plugin needed to use these systems seamlessly was
 450 missing in Debian.  The <a href="http://bugs.debian.org/668284">request
 451 for a package</a> was from 2012-04-10 with no progress since
 452 2013-04-01, so I decided to wrap up a package based on the great work
 453 from Cajus Pollmeier and put it in a collab-maint maintained git
 454 repository to get a package I could use.  I would very much like
 455 others to help me maintain the package (or just take over, I do not
 456 mind), but as no-one had volunteered so far, I just uploaded it to
 457 NEW.  I hope it will be available in Debian in a few days.</p>
 458
 459 <p>The source is now available from
 460 <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>
 461 </div>
 462       <div class="tags">
 463
 464
 465         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>.
 466
 467
 468       </div>
 469     </div>
 470     <div class="padding"></div>
 471
 472     <div class="entry">
 473       <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>
 474       <div class="date">27th October 2013</div>
 475       <div class="body"><p>The
 476 <a href="http://packages.qa.debian.org/v/vmdebootstrap.html">vmdebootstrap</a>
 477 program is a a very nice system to create virtual machine images.  It
 478 create a image file, add a partition table, mount it and run
 479 debootstrap in the mounted directory to create a Debian system on a
 480 stick.  Yesterday, I decided to try to teach it how to make images for
 481 <a href="https://wiki.debian.org/RaspberryPi">Raspberry Pi</a>, as part
 482 of a plan to simplify the build system for
 483 <a href="https://wiki.debian.org/FreedomBox">the FreedomBox
 484 project</a>.  The FreedomBox project already uses vmdebootstrap for
 485 the virtualbox images, but its current build system made multistrap
 486 based system for Dreamplug images, and it is lacking support for
 487 Raspberry Pi.</p>
 488
 489 <p>Armed with the knowledge on how to build "foreign" (aka non-native
 490 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
 491 code and adjusted it to be able to build armel images on my amd64
 492 Debian laptop.  I ended up giving vmdebootstrap five new options,
 493 allowing me to replicate the image creation process I use to make
 494 <a href="http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian
 495 Jessie based mesh node images for the Raspberry Pi</a>.  First, the
 496 <tt>--foreign /path/to/binfm_handler</tt> option tell vmdebootstrap to
 497 call debootstrap with --foreign and to copy the handler into the
 498 generated chroot before running the second stage.  This allow
 499 vmdebootstrap to create armel images on an amd64 host.  Next I added
 500 two new options <tt>--bootsize size</tt> and <tt>--boottype
 501 fstype</tt> to teach it to create a separate /boot/ partition with the
 502 given file system type, allowing me to create an image with a vfat
 503 partition for the /boot/ stuff.  I also added a <tt>--variant
 504 variant</tt> option to allow me to create smaller images without the
 505 Debian base system packages installed.  Finally, I added an option
 506 <tt>--no-extlinux</tt> to tell vmdebootstrap to not install extlinux
 507 as a boot loader.  It is not needed on the Raspberry Pi and probably
 508 most other non-x86 architectures.  The changes were accepted by the
 509 upstream author of vmdebootstrap yesterday and today, and is now
 510 available from
 511 <a href="http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/">the
 512 upstream project page</a>.</p>
 513
 514 <p>To use it to build a Raspberry Pi image using Debian Jessie, first
 515 create a small script (the customize script) to add the non-free
 516 binary blob needed to boot the Raspberry Pi and the APT source
 517 list:</p>
 518
 519 <p><pre>
 520 #!/bin/sh
 521 set -e # Exit on first error
 522 rootdir="$1"
 523 cd "$rootdir"
 524 cat &lt;&lt;EOF > etc/apt/sources.list
 525 deb http://http.debian.net/debian/ jessie main contrib non-free
 526 EOF
 527 # Install non-free binary blob needed to boot Raspberry Pi.  This
 528 # install a kernel somewhere too.
 529 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
 530     -O $rootdir/usr/bin/rpi-update
 531 chmod a+x $rootdir/usr/bin/rpi-update
 532 mkdir -p $rootdir/lib/modules
 533 touch $rootdir/boot/start.elf
 534 chroot $rootdir rpi-update
 535 </pre></p>
 536
 537 <p>Next, fetch the latest vmdebootstrap script and call it like this
 538 to build the image:</p>
 539
 540 <pre>
 541 sudo ./vmdebootstrap \
 542     --variant minbase \
 543     --arch armel \
 544     --distribution jessie \
 545     --mirror http://http.debian.net/debian \
 546     --image test.img \
 547     --size 600M \
 548     --bootsize 64M \
 549     --boottype vfat \
 550     --log-level debug \
 551     --verbose \
 552     --no-kernel \
 553     --no-extlinux \
 554     --root-password raspberry \
 555     --hostname raspberrypi \
 556     --foreign /usr/bin/qemu-arm-static \
 557     --customize `pwd`/customize \
 558     --package netbase \
 559     --package git-core \
 560     --package binutils \
 561     --package ca-certificates \
 562     --package wget \
 563     --package kmod
 564 </pre></p>
 565
 566 <p>The list of packages being installed are the ones needed by
 567 rpi-update to make the image bootable on the Raspberry Pi, with the
 568 exception of netbase, which is needed by debootstrap to find
 569 /etc/hosts with the minbase variant.  I really wish there was a way to
 570 set up an Raspberry Pi using only packages in the Debian archive, but
 571 that is not possible as far as I know, because it boots from the GPU
 572 using a non-free binary blob.</p>
 573
 574 <p>The build host need debootstrap, kpartx and qemu-user-static and
 575 probably a few others installed.  I have not checked the complete
 576 build dependency list.</p>
 577
 578 <p>The resulting image will not use the hardware floating point unit
 579 on the Raspberry PI, because the armel architecture in Debian is not
 580 optimized for that use.  So the images created will be a bit slower
 581 than <a href="http://www.raspbian.org/">Raspbian</a> based images.</p>
 582 </div>
 583       <div class="tags">
 584
 585
 586         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>.
 587
 588
 589       </div>
 590     </div>
 591     <div class="padding"></div>
 592
 593     <div class="entry">
 594       <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>
 595       <div class="date">26th October 2013</div>
 596       <div class="body"><p>De siste måneders eksponering av
 597 <a href="http://www.aftenposten.no/nyheter/uriks/Her-er-Edvard-Snowdens-mest-omtalte-avsloringer-7351734.html">den
 598 totale overvåkningen som foregår i den vestlige verden dokumenterer
 599 hvor sårbare vi er</a>.  Men det slår meg at de som er mest sårbare
 600 for dette, myndighetspersoner på alle nivåer, neppe har innsett at de
 601 selv er de mest interessante personene å lage profiler på, for å kunne
 602 påvirke dem.</p>
 603
 604 <p>For å ta et lite eksempel: Stortingets nettsted,
 605 <a href="http://www.stortinget.no/">www.stortinget.no</a> (og
 606 forsåvidt også
 607 <a href="http://data.stortinget.no/">data.stortinget.no</a>),
 608 inneholder informasjon om det som foregår på Stortinget, og jeg antar
 609 de største brukerne av informasjonen der er representanter og
 610 rådgivere på Stortinget.  Intet overraskende med det.  Det som derimot
 611 er mer skjult er at Stortingets nettsted bruker
 612 <a href="http://en.wikipedia.org/wiki/Google_Analytics">Google
 613 Analytics</a>, hvilket gjør at enhver som besøker nettsidene der også
 614 rapporterer om besøket via Internett-linjer som passerer Sverige,
 615 England og videre til USA.  Det betyr at informasjon om ethvert besøk
 616 på stortingets nettsider kan snappes opp av svensk, britisk og USAs
 617 etterretningsvesen.  De kan dermed holde et øye med hvilke
 618 Stortingssaker stortingsrepresentantene synes er interessante å sjekke
 619 ut, og hvilke sider rådgivere og andre på stortinget synes er
 620 interessant å besøke, når de gjør det og hvilke andre representanter
 621 som sjekker de samme sidene omtrent samtidig.  Stortingets bruk av
 622 Google Analytics gjør det dermed enkelt for utenlands etteretning å
 623 spore representantenes aktivitet og interesse.  Hvis noen av
 624 representantene bruker Google Mail eller noen andre tjenestene som
 625 krever innlogging, så vil det være enda enklere å finne ut nøyaktig
 626 hvilke personer som bruker hvilke nettlesere og dermed knytte
 627 informasjonen opp til enkeltpersoner på Stortinget.</p>
 628
 629 <p>Og jo flere nettsteder som bruker Google Analytics, jo bedre
 630 oversikt over stortingsrepresentantenes lesevaner og interesse blir
 631 tilgjengelig for svensk, britisk og USAs etterretning.  Hva de kan
 632 bruke den informasjonen til overlater jeg til leseren å undres
 633 over.</p>
 634 </div>
 635       <div class="tags">
 636
 637
 638         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>.
 639
 640
 641       </div>
 642     </div>
 643     <div class="padding"></div>
 644
 645     <div class="entry">
 646       <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>
 647       <div class="date">21st October 2013</div>
 648       <div class="body"><p>The last few days I have been experimenting with
 649 <a href="http://www.open-mesh.org/projects/batman-adv/wiki">the
 650 batman-adv mesh technology</a>.  I want to gain some experience to see
 651 if it will fit <a href="https://wiki.debian.org/FreedomBox">the
 652 Freedombox project</a>, and together with my neighbors try to build a
 653 mesh network around the park where I live.  Batman-adv is a layer 2
 654 mesh system ("ethernet" in other words), where the mesh network appear
 655 as if all the mesh clients are connected to the same switch.</p>
 656
 657 <p>My hardware of choice was the Linksys WRT54GL routers I had lying
 658 around, but I've been unable to get them working with batman-adv.  So
 659 instead, I started playing with a
 660 <a href="http://www.raspberrypi.org/">Raspberry Pi</a>, and tried to
 661 get it working as a mesh node.  My idea is to use it to create a mesh
 662 node which function as a switch port, where everything connected to
 663 the Raspberry Pi ethernet plug is connected (bridged) to the mesh
 664 network.  This allow me to hook a wifi base station like the Linksys
 665 WRT54GL to the mesh by plugging it into a Raspberry Pi, and allow
 666 non-mesh clients to hook up to the mesh.  This in turn is useful for
 667 Android phones using <a href="http://servalproject.org/">the Serval
 668 Project</a> voip client, allowing every one around the playground to
 669 phone and message each other for free.  The reason is that Android
 670 phones do not see ad-hoc wifi networks (they are filtered away from
 671 the GUI view), and can not join the mesh without being rooted.  But if
 672 they are connected using a normal wifi base station, they can talk to
 673 every client on the local network.</p>
 674
 675 <p>To get this working, I've created a debian package
 676 <a href="https://github.com/petterreinholdtsen/meshfx-node">meshfx-node</a>
 677 and a script
 678 <a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/build-rpi-mesh-node">build-rpi-mesh-node</a>
 679 to create the Raspberry Pi boot image.  I'm using Debian Jessie (and
 680 not Raspbian), to get more control over the packages available.
 681 Unfortunately a huge binary blob need to be inserted into the boot
 682 image to get it booting, but I'll ignore that for now.  Also, as
 683 Debian lack support for the CPU features available in the Raspberry
 684 Pi, the system do not use the hardware floating point unit.  I hope
 685 the routing performance isn't affected by the lack of hardware FPU
 686 support.</p>
 687
 688 <p>To create an image, run the following with a sudo enabled user
 689 after inserting the target SD card into the build machine:</p>
 690
 691 <p><pre>
 692 % wget -O build-rpi-mesh-node \
 693     https://raw.github.com/petterreinholdtsen/meshfx-node/master/build-rpi-mesh-node
 694 % sudo bash -x ./build-rpi-mesh-node > build.log 2>&1
 695 % dd if=/root/rpi/rpi_basic_jessie_$(date +%Y%m%d).img of=/dev/mmcblk0 bs=1M
 696 %
 697 </pre></p>
 698
 699 <p>Booting with the resulting SD card on a Raspberry PI with a USB
 700 wifi card inserted should give you a mesh node.  At least it does for
 701 me with a the wifi card I am using. The default mesh settings are the
 702 ones used by the Oslo mesh project at Hackeriet, as I mentioned in
 703 <a href="http://people.skolelinux.org/pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html">an
 704 earlier blog post about this mesh testing</a>.</p>
 705
 706 <p>The mesh node was not horribly expensive either.  I bought
 707 everything over the counter in shops nearby.  If I had ordered online
 708 from the lowest bidder, the price should be significantly lower:</p>
 709
 710 <p><table>
 711
 712 <tr><th>Supplier</th><th>Model</th><th>NOK</th></tr>
 713 <tr><td>Teknikkmagasinet</td><td>Raspberry Pi model B</td><td>349.90</td></tr>
 714 <tr><td>Teknikkmagasinet</td><td>Raspberry Pi type B case</td><td>99.90</td></tr>
 715 <tr><td>Lefdal</td><td>Jensen Air:Link 25150</td><td>295.-</td></tr>
 716 <tr><td>Clas Ohlson</td><td>Kingston 16 GB SD card</td><td>199.-</td></tr>
 717 <tr><td>Total cost</td><td></td><td>943.80</td></tr>
 718
 719 </table></p>
 720
 721 <p>Now my mesh network at home consist of one laptop in the basement
 722 connected to my production network, one Raspberry Pi node on the 1th
 723 floor that can be seen by my neighbor across the park, and one
 724 play-node I use to develop the image building script.  And some times
 725 I hook up my work horse laptop to the mesh to test it.  I look forward
 726 to figuring out what kind of latency the batman-adv setup will give,
 727 and how much packet loss we will experience around the park. :)</p>
 728 </div>
 729       <div class="tags">
 730
 731
 732         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>.
 733
 734
 735       </div>
 736     </div>
 737     <div class="padding"></div>
 738
 739     <div class="entry">
 740       <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>
 741       <div class="date">19th October 2013</div>
 742       <div class="body"><p>Back in 2010, I created a Perl library to talk to
 743 <a href="http://en.wikipedia.org/wiki/Spykee">the Spykee robot</a>
 744 (with two belts, wifi, USB and Linux) and made it available from my
 745 web page.  Today I concluded that it should move to a site that is
 746 easier to use to cooperate with others, and moved it to github.  If
 747 you got a Spykee robot, you might want to check out
 748 <a href="https://github.com/petterreinholdtsen/libspykee-perl">the
 749 libspykee-perl github repository</a>.</p>
 750 </div>
 751       <div class="tags">
 752
 753
 754         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/robot">robot</a>.
 755
 756
 757       </div>
 758     </div>
 759     <div class="padding"></div>
 760
 761     <div class="entry">
 762       <div class="title"><a href="http://people.skolelinux.org/pere/blog/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>
 763       <div class="date">15th October 2013</div>
 764       <div class="body"><p>The last few days I came across a few good causes that should get
 765 wider attention.  I recommend signing and donating to each one of
 766 these. :)</p>
 767
 768 <p>Via <a href="http://www.debian.org/News/weekly/2013/18/">Debian
 769 Project News for 2013-10-14</a> I came across the Outreach Program for
 770 Women program which is a Google Summer of Code like initiative to get
 771 more women involved in free software.  One debian sponsor has offered
 772 to match <a href="http://debian.ch/opw2013">any donation done to Debian
 773 earmarked</a> for this initiative.  I donated a few minutes ago, and
 774 hope you will to. :)</p>
 775
 776 <p>And the Electronic Frontier Foundation just announced plans to
 777 create <a href="https://supporters.eff.org/donate/nsa-videos">video
 778 documentaries about the excessive spying</a> on every Internet user that
 779 take place these days, and their need to fund the work.  I've already
 780 donated.  Are you next?</p>
 781
 782 <p>For my Norwegian audience, the organisation Studentenes og
 783 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
 784 statement under the heading
 785 <a href="http://saih.no/Bloggers_United/">Bloggers United for Open
 786 Access</a> for those of us asking for more focus on open access in the
 787 Norwegian government.  So far 499 signatures.  I hope you will sign it
 788 too.</p>
 789 </div>
 790       <div class="tags">
 791
 792
 793         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>.
 794
 795
 796       </div>
 797     </div>
 798     <div class="padding"></div>
 799
 800     <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>
 801     <div id="sidebar">
 802
 803
 804
 805 <h2>Archive</h2>
 806 <ul>
 807
 808 <li>2013
 809 <ul>
 810
 811 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 812
 813 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 814
 815 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 816
 817 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 818
 819 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 820
 821 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 822
 823 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 824
 825 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 826
 827 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 828
 829 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 830
 831 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (5)</a></li>
 832
 833 </ul></li>
 834
 835 <li>2012
 836 <ul>
 837
 838 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 839
 840 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 841
 842 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 843
 844 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 845
 846 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 847
 848 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 849
 850 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 851
 852 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 853
 854 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 855
 856 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 857
 858 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 859
 860 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 861
 862 </ul></li>
 863
 864 <li>2011
 865 <ul>
 866
 867 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 868
 869 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 870
 871 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 872
 873 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 874
 875 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 876
 877 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 878
 879 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 880
 881 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 882
 883 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 884
 885 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 886
 887 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 888
 889 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 890
 891 </ul></li>
 892
 893 <li>2010
 894 <ul>
 895
 896 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 897
 898 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 899
 900 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 901
 902 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 903
 904 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 905
 906 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 907
 908 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 909
 910 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 911
 912 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 913
 914 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 915
 916 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 917
 918 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 919
 920 </ul></li>
 921
 922 <li>2009
 923 <ul>
 924
 925 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 926
 927 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 928
 929 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 930
 931 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 932
 933 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 934
 935 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 936
 937 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 938
 939 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 940
 941 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 942
 943 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 944
 945 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 946
 947 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 948
 949 </ul></li>
 950
 951 <li>2008
 952 <ul>
 953
 954 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 955
 956 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 957
 958 </ul></li>
 959
 960 </ul>
 961
 962
 963
 964 <h2>Tags</h2>
 965 <ul>
 966
 967  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
 968
 969  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 970
 971  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 972
 973  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
 974
 975  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (7)</a></li>
 976
 977  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (13)</a></li>
 978
 979  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 980
 981  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (90)</a></li>
 982
 983  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (142)</a></li>
 984
 985  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
 986
 987  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
 988
 989  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 990
 991  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (228)</a></li>
 992
 993  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
 994
 995  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
 996
 997  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
 998
 999  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (5)</a></li>
1000
1001  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1002
1003  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (37)</a></li>
1004
1005  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (7)</a></li>
1006
1007  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1008
1009  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (8)</a></li>
1010
1011  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (6)</a></li>
1012
1013  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1014
1015  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (5)</a></li>
1016
1017  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (25)</a></li>
1018
1019  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (236)</a></li>
1020
1021  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (158)</a></li>
1022
1023  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (8)</a></li>
1024
1025  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1026
1027  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (45)</a></li>
1028
1029  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (67)</a></li>
1030
1031  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1032
1033  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1034
1035  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1036
1037  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1038
1039  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1040
1041  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1042
1043  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1044
1045  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (33)</a></li>
1046
1047  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1048
1049  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1050
1051  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (43)</a></li>
1052
1053  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1054
1055  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1056
1057  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (21)</a></li>
1058
1059  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1060
1061  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1062
1063  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (39)</a></li>
1064
1065  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1066
1067  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (28)</a></li>
1068
1069 </ul>
1070
1071
1072     </div>
1073     <p style="text-align: right">
1074  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1075 </p>
1076
1077   </body>
1078 </html>