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">
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" />
14 <a href=
"http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen
</a>
23 <div class=
"title"><a href=
"http://people.skolelinux.org/pere/blog/RSS_kilde_for_friteksts_k_i_offentlige_anbud_hos_Doffin.html">RSS-kilde for fritekstsøk i offentlige anbud hos Doffin
</a></div>
24 <div class=
"date">22nd November
2013</div>
25 <div class=
"body"><p>I fjor sommer lagde jeg en
26 <a href=
"http://people.skolelinux.org/pere/blog/SQL_database_med_anbud_publisert_p__Doffin.html">offentlig
27 tilgjengelig SQL-database over offentlig anbud
</a> basert på skraping
28 av HTML-data fra Doffin. Den har stått og gått siden da, og har nå
29 ca.
28000 oppføringer. Jeg oppdaget da jeg tittet innom at noen
30 oppføringer var ikke blitt med, antagelig på grunn av at de fikk
31 tildelt sekvensnummer i Doffin en godt stund før de ble publisert,
32 slik at min nettsideskraper som fortsatte skrapingen der den slapp
33 sist ikke fikk dem med seg. Jeg har fikset litt slik at skraperen nå
34 ser litt tilbake i tid for å se om den har gått glipp av noen
35 oppføringer, og har skrapet på nytt fra midten av september
2013 og
36 fremover. Det bør dermed bli en mer komplett database for kommende
37 måneder. Hvis jeg får tid skal jeg forsøke å skrape "glemte" data fra
38 før midten av september
2013, men tør ikke garantere at det blir
39 prioritert med det første.
</p>
41 <p>Men målet med denne bloggposten er å vise hvordan denne
42 Doffin-databasen kan brukes og integreres med en RSS-leser, slik at en
43 kan la datamaskinen holde et øye med Doffin-annonseringer etter
44 nøkkelord. En kan lage sitt eget søk ved å besøke
45 <ahref=
"https://classic.scraperwiki.com/docs/api?name=norwegian-doffin#sqlite">API-et
46 hos Scraperwiki
</a>, velge format rss2 og så legge inn noe ala dette i
50 select title, scrapedurl as link, abstract as description,
51 publishdate as pubDate from 'swdata'
52 where abstract like '%linux%' or title like '%linux%'
53 order by seq desc limit
20
56 <p>Dette vil søke opp alle anbud med ordet linux i oppsummering eller
57 tittel. En kan lage mer avanserte søk hvis en ønsker det. URL-en som
58 dukker opp nederst på siden kan en så gi til sin RSS-leser (jeg bruker
59 akregator selv), og så automatisk få beskjed hvis det dukker opp anbud
60 med det aktuelle nøkkelordet i teksten. Merk at kapasiteten hos
61 Scraperwiki er begrenset, så be RSS-leseren kun hente ned en gang hver
62 dag eller noe slikt.
</p>
64 <p>Du lurer kanskje på hva slags informasjon en kan få ut fra denne
65 databasen. Her er to RSS-kilder, med søkeordet
66 "
<a href=
"https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25linux%25'%20or%20title%20like%20'%25linux%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">linux
</a>",
68 "<a href=
"https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25fri%20programvare%25'%20or%20title%20like%20'%25fri%20programvare%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">fri
71 "<a href=
"https://api.scraperwiki.com/api/1.0/datastore/sqlite?format=rss2&name=norwegian-doffin&query=select%20title%2C%20scrapedurl%20as%20link%2C%20abstract%20as%20description%2C%0A%20%20%20%20%20%20%20publishdate%20as%20pubDate%20from%20'swdata'%0A%20%20%20where%20abstract%20like%20'%25odf%25'%20or%20title%20like%20'%25odf%25'%0A%20%20%20order%20by%20seq%20desc%20limit%2020">odf
</a>".
72 Det er bare å søke på det en er interessert i. Kopier gjerne
73 datasettet og sett opp din egen tjeneste hvis du vil gjøre mer
74 avanserte søk. SQLite-filen med Doffin-oppføringer kan lastes med fra
75 Scraperwiki for de som vil grave dypere.</p>
76 <!-- nov 625, okt 1080, sep 1120 -->
81 Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk
">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug
">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn
">offentlig innsyn</a>.
86 <div class="padding
"></div>
89 <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>
90 <div class="date
">21st November 2013</div>
91 <div class="body
">Drones, flying robots, are getting more and more popular. The most
92 know ones are the killer drones used by some government to murder
93 people they do not like without giving them the chance of a fair
94 trial, but the technology have many good uses too, from mapping and
95 forest maintenance to photography and search and rescue. I am sure it
96 is just a question of time before "bad drones" are in the hands of
97 private enterprises and not only state criminals but petty criminals
98 too. The drone technology is very useful and very dangerous. To have
99 some control over the use of drones, I agree with Daniel Suarez in his
101 "
<a href=
"https://archive.org/details/DanielSuarez_2013G">The kill
102 decision shouldn't belong to a robot
</a>", where he suggested this
103 little gem to keep the good while limiting the bad use of drones:</p>
107 <p>Each robot and drone should have a cryptographically signed
108 I.D. burned in at the factory that can be used to track its movement
109 through public spaces. We have license plates on cars, tail numbers on
110 aircraft. This is no different. And every citizen should be able to
111 download an app that shows the population of drones and autonomous
112 vehicles moving through public spaces around them, both right now and
113 historically. And civic leaders should deploy sensors and civic drones
114 to detect rogue drones, and instead of sending killer drones of their
115 own up to shoot them down, they should notify humans to their
116 presence. And in certain very high-security areas, perhaps civic
117 drones would snare them and drag them off to a bomb disposal facility.</p>
119 <p>But notice, this is more an immune system than a weapons system. It
120 would allow us to avail ourselves of the use of autonomous vehicles
121 and drones while still preserving our open, civil society.</p>
125 <p>The key is that <em>every citizen</em> should be able to read the
126 radio beacons sent from the drones in the area, to be able to check
127 both the government and others use of drones. For such control to be
128 effective, everyone must be able to do it. What should such beacon
129 contain? At least formal owner, purpose, contact information and GPS
130 location. Probably also the origin and target position of the current
131 flight. And perhaps some registration number to be able to look up
132 the drone in a central database tracking their movement. Robots
133 should not have privacy. It is people who need privacy.</p>
138 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>.
143 <div class="padding
"></div>
146 <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>
147 <div class="date
">13th November 2013</div>
148 <div class="body
"><p>Today NUUG and Hackeriet announced
149 <a href="http://www.nuug.no/news/Bli_med___bygge_dugnadsnett_for_alle_i_Oslo.shtml
">our
150 plans to join forces and create a wireless community network in
151 Oslo</a>. The workshop to help people get started will take place
152 Thursday 2013-11-28, but we already are collecting the geolocation of
153 people joining forces to make this happen. We have
154 <a href="https://github.com/petterreinholdtsen/meshfx-node/blob/master/oslo-nodes.geojson
">9
155 locations plotted on the map</a>, but we will need more before we have
156 a connected mesh spread across Oslo. If this sound interesting to
157 you, please join us at the workshop. If you are too impatient to wait
158 15 days, please join us on the IRC channel
159 <a href="irc://irc.freenode.net/%
23nuug
">#nuug on irc.freenode.net</a>
165 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>.
170 <div class="padding
"></div>
173 <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>
174 <div class="date
">10th November 2013</div>
175 <div class="body
"><p>Continuing my research into mesh networking, I was recommended to
176 use TP-Link 3040 and 3600 access points as mesh nodes, and the pair I
177 bought arrived on Friday. Here are my notes on how to set up the
178 MR3040 as a mesh node using
179 <a href="http://www.openwrt.org/
">OpenWrt</a>.</p>
181 <p>I started by following the instructions on the OpenWRT wiki for
182 <a href="http://wiki.openwrt.org/toh/tp-link/tl-mr3040
">TL-MR3040</a>,
184 <a href="http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin
">the
185 recommended firmware image</a>
186 (openwrt-ar71xx-generic-tl-mr3040-v2-squashfs-factory.bin) and
187 uploaded it into the original web interface. The flashing went fine,
188 and the machine was available via telnet on the ethernet port. After
189 logging in and setting the root password, ssh was available and I
190 could start to set it up as a batman-adv mesh node.</p>
192 <p>I started off by reading the instructions from
193 <a href="http://wirelessafrica.meraka.org.za/wiki/index.php?title=Antoine's_Research
">Wireless
194 Africa</a>, which had quite a lot of useful information, but
195 eventually I followed the recipe from the Open Mesh wiki for
196 <a href="http://www.open-mesh.org/projects/batman-adv/wiki/Batman-adv-openwrt-config
">using
197 batman-adv on OpenWrt</a>. A small snag was the fact that the
198 <tt>opkg install kmod-batman-adv</tt> command did not work as it
199 should. The batman-adv kernel module would fail to load because its
200 dependency crc16 was not already loaded. I
201 <a href="https://dev.openwrt.org/ticket/
14452">reported the bug</a> to
202 the openwrt project and hope it will be fixed soon. But the problem
203 only seem to affect initial testing of batman-adv, as configuration
204 seem to work when booting from scratch.</p>
206 <p>The setup is done using files in /etc/config/. I did not bridge
207 the Ethernet and mesh interfaces this time, to be able to hook up the
208 box on my local network and log into it for configuration updates.
209 The following files were changed and look like this after modifying
212 <p><tt>/etc/config/network</tt></p>
216 config interface 'loopback'
218 option proto 'static'
219 option ipaddr '127.0.0.1'
220 option netmask '255.0.0.0'
222 config globals 'globals'
223 option ula_prefix 'fdbf:4c12:3fed::/48'
225 config interface 'lan'
229 option ipaddr '192.168.1.1'
230 option netmask '255.255.255.0'
231 option hostname 'tl-mr3040'
232 option ip6assign '60'
234 config interface 'mesh'
235 option ifname 'adhoc0'
237 option proto 'batadv'
241 <p><tt>/etc/config/wireless</tt></p>
244 config wifi-device 'radio0'
245 option type 'mac80211'
248 option path 'platform/ar933x_wmac'
250 list ht_capab 'SHORT-GI-20'
251 list ht_capab 'SHORT-GI-40'
252 list ht_capab 'RX-STBC1'
253 list ht_capab 'DSSS_CCK-40'
256 config wifi-iface 'wmesh'
257 option device 'radio0'
258 option ifname 'adhoc0'
259 option network 'mesh'
260 option encryption 'none'
262 option bssid '02:BA:00:00:00:01'
263 option ssid 'meshfx@hackeriet'
265 <p><tt>/etc/config/batman-adv</tt></p>
269 option interfaces 'adhoc0'
270 option 'aggregated_ogms'
271 option 'ap_isolation'
273 option 'fragmentation'
274 option 'gw_bandwidth'
276 option 'gw_sel_class'
278 option 'orig_interval'
280 option 'bridge_loop_avoidance'
281 option 'distributed_arp_table'
282 option 'network_coding'
285 # yet another batX instance
286 # config 'mesh' 'bat5'
287 # option 'interfaces' 'second_mesh'
290 <p>The mesh node is now operational. I have yet to test its range,
291 but I hope it is good. I have not yet tested the TP-Link 3600 box
292 still wrapped up in plastic.</p>
297 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>.
302 <div class="padding
"></div>
305 <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>
306 <div class="date
"> 2nd November 2013</div>
307 <div class="body
"><p>If one of the points of switching to a new init system in Debian is
308 <a href="http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
309 init.d scripts</a>, I doubt we need to switch away from sysvinit and
310 init.d scripts at all. Here is an example init.d script, ie a rewrite
311 of /etc/init.d/rsyslog:</p>
314 #!/lib/init/init-d-script
317 # Required-Start: $remote_fs $time
318 # Required-Stop: umountnfs $time
319 # X-Stop-After: sendsigs
320 # Default-Start: 2 3 4 5
321 # Default-Stop: 0 1 6
322 # Short-Description: enhanced syslogd
323 # Description: Rsyslog is an enhanced multi-threaded syslogd.
324 # It is quite compatible to stock sysklogd and can be
325 # used as a drop-in replacement.
327 DESC="enhanced syslogd"
328 DAEMON=/usr/sbin/rsyslogd
331 <p>Pretty minimalistic to me... For the record, the original sysv-rc
332 script was
137 lines, and the above is just
15 lines, most of it meta
335 <p>How to do this, you ask? Well, one create a new script
336 /lib/init/init-d-script looking something like this:
341 # Define LSB log_* functions.
342 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
343 # and status_of_proc is working.
344 . /lib/lsb/init-functions
347 # Function that starts the daemon/service
353 #
0 if daemon has been started
354 #
1 if daemon was already running
355 #
2 if daemon could not be started
356 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
358 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
361 # Add code here, if necessary, that waits for the process to be ready
362 # to handle requests from services started subsequently which depend
363 # on this one. As a last resort, sleep for some time.
367 # Function that stops the daemon/service
372 #
0 if daemon has been stopped
373 #
1 if daemon was already stopped
374 #
2 if daemon could not be stopped
375 # other if a failure occurred
376 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
378 [ "$RETVAL" =
2 ] && return
2
379 # Wait for children to finish too if this is a daemon that forks
380 # and if the daemon is only ever run from this initscript.
381 # If the above conditions are not satisfied then add some other code
382 # that waits for the process to drop all resources that could be
383 # needed by services started subsequently. A last resort is to
384 # sleep for some time.
385 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
386 [ "$?" =
2 ] && return
2
387 # Many daemons don't delete their pidfiles when they exit.
393 # Function that sends a SIGHUP to the daemon/service
397 # If the daemon can reload its configuration without
398 # restarting (for example, when it is sent a SIGHUP),
399 # then implement that here.
401 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
406 scriptbasename="$(basename $
1)"
407 echo "SN: $scriptbasename"
408 if [ "$scriptbasename" != "init-d-library" ] ; then
416 NAME=$(basename $DAEMON)
417 PIDFILE=/var/run/$NAME.pid
419 # Exit if the package is not installed
420 #[ -x "$DAEMON" ] || exit
0
422 # Read configuration variable file if it is present
423 [ -r /etc/default/$NAME ] && . /etc/default/$NAME
425 # Load the VERBOSE setting and other rcS variables
430 [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
433 0|
1) [ "$VERBOSE" != no ] && log_end_msg
0 ;;
434 2) [ "$VERBOSE" != no ] && log_end_msg
1 ;;
438 [ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
441 0|
1) [ "$VERBOSE" != no ] && log_end_msg
0 ;;
442 2) [ "$VERBOSE" != no ] && log_end_msg
1 ;;
446 status_of_proc "$DAEMON" "$NAME" && exit
0 || exit $?
448 #reload|force-reload)
450 # If do_reload() is not implemented then leave this commented out
451 # and leave 'force-reload' as an alias for 'restart'.
453 #log_daemon_msg "Reloading $DESC" "$NAME"
457 restart|force-reload)
459 # If the "reload" option is implemented then remove the
460 # 'force-reload' alias
462 log_daemon_msg "Restarting $DESC" "$NAME"
469 1) log_end_msg
1 ;; # Old process is still running
470 *) log_end_msg
1 ;; # Failed to start
480 echo "Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}"
>&
2
488 <p>It is based on /etc/init.d/skeleton, and could be improved quite a
489 lot. I did not really polish the approach, so it might not always
490 work out of the box, but you get the idea. I did not try very hard to
491 optimize it nor make it more robust either.
</p>
493 <p>A better argument for switching init system in Debian than reducing
494 the size of init scripts (which is a good thing to do anyway), is to
495 get boot system that is able to handle the kernel events sensibly and
496 robustly, and do not depend on the boot to run sequentially. The boot
497 and the kernel have not behaved sequentially in years.
</p>
502 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>.
507 <div class=
"padding"></div>
510 <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>
511 <div class=
"date"> 1st November
2013</div>
512 <div class=
"body"><p><a href=
"http://www.spice-space.org/">The SPICE protocol
</a> for
513 remote display access is the preferred solution with oVirt and RedHat
514 Enterprise Virtualization, and I was sad to discover the other day
515 that the browser plugin needed to use these systems seamlessly was
516 missing in Debian. The
<a href=
"http://bugs.debian.org/668284">request
517 for a package
</a> was from
2012-
04-
10 with no progress since
518 2013-
04-
01, so I decided to wrap up a package based on the great work
519 from Cajus Pollmeier and put it in a collab-maint maintained git
520 repository to get a package I could use. I would very much like
521 others to help me maintain the package (or just take over, I do not
522 mind), but as no-one had volunteered so far, I just uploaded it to
523 NEW. I hope it will be available in Debian in a few days.
</p>
525 <p>The source is now available from
526 <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>
531 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>.
536 <div class=
"padding"></div>
539 <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>
540 <div class=
"date">27th October
2013</div>
541 <div class=
"body"><p>The
542 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html">vmdebootstrap
</a>
543 program is a a very nice system to create virtual machine images. It
544 create a image file, add a partition table, mount it and run
545 debootstrap in the mounted directory to create a Debian system on a
546 stick. Yesterday, I decided to try to teach it how to make images for
547 <a href=
"https://wiki.debian.org/RaspberryPi">Raspberry Pi
</a>, as part
548 of a plan to simplify the build system for
549 <a href=
"https://wiki.debian.org/FreedomBox">the FreedomBox
550 project
</a>. The FreedomBox project already uses vmdebootstrap for
551 the virtualbox images, but its current build system made multistrap
552 based system for Dreamplug images, and it is lacking support for
555 <p>Armed with the knowledge on how to build "foreign" (aka non-native
556 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
557 code and adjusted it to be able to build armel images on my amd64
558 Debian laptop. I ended up giving vmdebootstrap five new options,
559 allowing me to replicate the image creation process I use to make
560 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html">Debian
561 Jessie based mesh node images for the Raspberry Pi
</a>. First, the
562 <tt>--foreign /path/to/binfm_handler
</tt> option tell vmdebootstrap to
563 call debootstrap with --foreign and to copy the handler into the
564 generated chroot before running the second stage. This allow
565 vmdebootstrap to create armel images on an amd64 host. Next I added
566 two new options
<tt>--bootsize size
</tt> and
<tt>--boottype
567 fstype
</tt> to teach it to create a separate /boot/ partition with the
568 given file system type, allowing me to create an image with a vfat
569 partition for the /boot/ stuff. I also added a
<tt>--variant
570 variant
</tt> option to allow me to create smaller images without the
571 Debian base system packages installed. Finally, I added an option
572 <tt>--no-extlinux
</tt> to tell vmdebootstrap to not install extlinux
573 as a boot loader. It is not needed on the Raspberry Pi and probably
574 most other non-x86 architectures. The changes were accepted by the
575 upstream author of vmdebootstrap yesterday and today, and is now
577 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/">the
578 upstream project page
</a>.
</p>
580 <p>To use it to build a Raspberry Pi image using Debian Jessie, first
581 create a small script (the customize script) to add the non-free
582 binary blob needed to boot the Raspberry Pi and the APT source
587 set -e # Exit on first error
590 cat
<<EOF
> etc/apt/sources.list
591 deb http://http.debian.net/debian/ jessie main contrib non-free
593 # Install non-free binary blob needed to boot Raspberry Pi. This
594 # install a kernel somewhere too.
595 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
596 -O $rootdir/usr/bin/rpi-update
597 chmod a+x $rootdir/usr/bin/rpi-update
598 mkdir -p $rootdir/lib/modules
599 touch $rootdir/boot/start.elf
600 chroot $rootdir rpi-update
603 <p>Next, fetch the latest vmdebootstrap script and call it like this
604 to build the image:
</p>
607 sudo ./vmdebootstrap \
610 --distribution jessie \
611 --mirror http://http.debian.net/debian \
620 --root-password raspberry \
621 --hostname raspberrypi \
622 --foreign /usr/bin/qemu-arm-static \
623 --customize `pwd`/customize \
627 --package ca-certificates \
632 <p>The list of packages being installed are the ones needed by
633 rpi-update to make the image bootable on the Raspberry Pi, with the
634 exception of netbase, which is needed by debootstrap to find
635 /etc/hosts with the minbase variant. I really wish there was a way to
636 set up an Raspberry Pi using only packages in the Debian archive, but
637 that is not possible as far as I know, because it boots from the GPU
638 using a non-free binary blob.
</p>
640 <p>The build host need debootstrap, kpartx and qemu-user-static and
641 probably a few others installed. I have not checked the complete
642 build dependency list.
</p>
644 <p>The resulting image will not use the hardware floating point unit
645 on the Raspberry PI, because the armel architecture in Debian is not
646 optimized for that use. So the images created will be a bit slower
647 than
<a href=
"http://www.raspbian.org/">Raspbian
</a> based images.
</p>
652 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>.
657 <div class=
"padding"></div>
660 <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>
661 <div class=
"date">26th October
2013</div>
662 <div class=
"body"><p>De siste måneders eksponering av
663 <a href=
"http://www.aftenposten.no/nyheter/uriks/Her-er-Edvard-Snowdens-mest-omtalte-avsloringer-7351734.html">den
664 totale overvåkningen som foregår i den vestlige verden dokumenterer
665 hvor sårbare vi er
</a>. Men det slår meg at de som er mest sårbare
666 for dette, myndighetspersoner på alle nivåer, neppe har innsett at de
667 selv er de mest interessante personene å lage profiler på, for å kunne
670 <p>For å ta et lite eksempel: Stortingets nettsted,
671 <a href=
"http://www.stortinget.no/">www.stortinget.no
</a> (og
673 <a href=
"http://data.stortinget.no/">data.stortinget.no
</a>),
674 inneholder informasjon om det som foregår på Stortinget, og jeg antar
675 de største brukerne av informasjonen der er representanter og
676 rådgivere på Stortinget. Intet overraskende med det. Det som derimot
677 er mer skjult er at Stortingets nettsted bruker
678 <a href=
"http://en.wikipedia.org/wiki/Google_Analytics">Google
679 Analytics
</a>, hvilket gjør at enhver som besøker nettsidene der også
680 rapporterer om besøket via Internett-linjer som passerer Sverige,
681 England og videre til USA. Det betyr at informasjon om ethvert besøk
682 på stortingets nettsider kan snappes opp av svensk, britisk og USAs
683 etterretningsvesen. De kan dermed holde et øye med hvilke
684 Stortingssaker stortingsrepresentantene synes er interessante å sjekke
685 ut, og hvilke sider rådgivere og andre på stortinget synes er
686 interessant å besøke, når de gjør det og hvilke andre representanter
687 som sjekker de samme sidene omtrent samtidig. Stortingets bruk av
688 Google Analytics gjør det dermed enkelt for utenlands etteretning å
689 spore representantenes aktivitet og interesse. Hvis noen av
690 representantene bruker Google Mail eller noen andre tjenestene som
691 krever innlogging, så vil det være enda enklere å finne ut nøyaktig
692 hvilke personer som bruker hvilke nettlesere og dermed knytte
693 informasjonen opp til enkeltpersoner på Stortinget.
</p>
695 <p>Og jo flere nettsteder som bruker Google Analytics, jo bedre
696 oversikt over stortingsrepresentantenes lesevaner og interesse blir
697 tilgjengelig for svensk, britisk og USAs etterretning. Hva de kan
698 bruke den informasjonen til overlater jeg til leseren å undres
704 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>.
709 <div class=
"padding"></div>
712 <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>
713 <div class=
"date">21st October
2013</div>
714 <div class=
"body"><p>The last few days I have been experimenting with
715 <a href=
"http://www.open-mesh.org/projects/batman-adv/wiki">the
716 batman-adv mesh technology
</a>. I want to gain some experience to see
717 if it will fit
<a href=
"https://wiki.debian.org/FreedomBox">the
718 Freedombox project
</a>, and together with my neighbors try to build a
719 mesh network around the park where I live. Batman-adv is a layer
2
720 mesh system ("ethernet" in other words), where the mesh network appear
721 as if all the mesh clients are connected to the same switch.
</p>
723 <p>My hardware of choice was the Linksys WRT54GL routers I had lying
724 around, but I've been unable to get them working with batman-adv. So
725 instead, I started playing with a
726 <a href=
"http://www.raspberrypi.org/">Raspberry Pi
</a>, and tried to
727 get it working as a mesh node. My idea is to use it to create a mesh
728 node which function as a switch port, where everything connected to
729 the Raspberry Pi ethernet plug is connected (bridged) to the mesh
730 network. This allow me to hook a wifi base station like the Linksys
731 WRT54GL to the mesh by plugging it into a Raspberry Pi, and allow
732 non-mesh clients to hook up to the mesh. This in turn is useful for
733 Android phones using
<a href=
"http://servalproject.org/">the Serval
734 Project
</a> voip client, allowing every one around the playground to
735 phone and message each other for free. The reason is that Android
736 phones do not see ad-hoc wifi networks (they are filtered away from
737 the GUI view), and can not join the mesh without being rooted. But if
738 they are connected using a normal wifi base station, they can talk to
739 every client on the local network.
</p>
741 <p>To get this working, I've created a debian package
742 <a href=
"https://github.com/petterreinholdtsen/meshfx-node">meshfx-node
</a>
744 <a href=
"https://github.com/petterreinholdtsen/meshfx-node/blob/master/build-rpi-mesh-node">build-rpi-mesh-node
</a>
745 to create the Raspberry Pi boot image. I'm using Debian Jessie (and
746 not Raspbian), to get more control over the packages available.
747 Unfortunately a huge binary blob need to be inserted into the boot
748 image to get it booting, but I'll ignore that for now. Also, as
749 Debian lack support for the CPU features available in the Raspberry
750 Pi, the system do not use the hardware floating point unit. I hope
751 the routing performance isn't affected by the lack of hardware FPU
754 <p>To create an image, run the following with a sudo enabled user
755 after inserting the target SD card into the build machine:
</p>
758 % wget -O build-rpi-mesh-node \
759 https://raw.github.com/petterreinholdtsen/meshfx-node/master/build-rpi-mesh-node
760 % sudo bash -x ./build-rpi-mesh-node
> build.log
2>&
1
761 % dd if=/root/rpi/rpi_basic_jessie_$(date +%Y%m%d).img of=/dev/mmcblk0 bs=
1M
765 <p>Booting with the resulting SD card on a Raspberry PI with a USB
766 wifi card inserted should give you a mesh node. At least it does for
767 me with a the wifi card I am using. The default mesh settings are the
768 ones used by the Oslo mesh project at Hackeriet, as I mentioned in
769 <a href=
"http://people.skolelinux.org/pere/blog/Oslo_community_mesh_network___with_NUUG_and_Hackeriet_at_Hausmania.html">an
770 earlier blog post about this mesh testing
</a>.
</p>
772 <p>The mesh node was not horribly expensive either. I bought
773 everything over the counter in shops nearby. If I had ordered online
774 from the lowest bidder, the price should be significantly lower:
</p>
778 <tr><th>Supplier
</th><th>Model
</th><th>NOK
</th></tr>
779 <tr><td>Teknikkmagasinet
</td><td>Raspberry Pi model B
</td><td>349.90</td></tr>
780 <tr><td>Teknikkmagasinet
</td><td>Raspberry Pi type B case
</td><td>99.90</td></tr>
781 <tr><td>Lefdal
</td><td>Jensen Air:Link
25150</td><td>295.-
</td></tr>
782 <tr><td>Clas Ohlson
</td><td>Kingston
16 GB SD card
</td><td>199.-
</td></tr>
783 <tr><td>Total cost
</td><td></td><td>943.80</td></tr>
787 <p>Now my mesh network at home consist of one laptop in the basement
788 connected to my production network, one Raspberry Pi node on the
1th
789 floor that can be seen by my neighbor across the park, and one
790 play-node I use to develop the image building script. And some times
791 I hook up my work horse laptop to the mesh to test it. I look forward
792 to figuring out what kind of latency the batman-adv setup will give,
793 and how much packet loss we will experience around the park. :)
</p>
798 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>.
803 <div class=
"padding"></div>
806 <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>
807 <div class=
"date">19th October
2013</div>
808 <div class=
"body"><p>Back in
2010, I created a Perl library to talk to
809 <a href=
"http://en.wikipedia.org/wiki/Spykee">the Spykee robot
</a>
810 (with two belts, wifi, USB and Linux) and made it available from my
811 web page. Today I concluded that it should move to a site that is
812 easier to use to cooperate with others, and moved it to github. If
813 you got a Spykee robot, you might want to check out
814 <a href=
"https://github.com/petterreinholdtsen/libspykee-perl">the
815 libspykee-perl github repository
</a>.
</p>
820 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>.
825 <div class=
"padding"></div>
827 <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>
838 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/01/">January (
11)
</a></li>
840 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/02/">February (
9)
</a></li>
842 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/03/">March (
9)
</a></li>
844 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/04/">April (
6)
</a></li>
846 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/05/">May (
9)
</a></li>
848 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/06/">June (
10)
</a></li>
850 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/07/">July (
7)
</a></li>
852 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/08/">August (
3)
</a></li>
854 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/09/">September (
5)
</a></li>
856 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/10/">October (
7)
</a></li>
858 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2013/11/">November (
6)
</a></li>
865 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/01/">January (
7)
</a></li>
867 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/02/">February (
10)
</a></li>
869 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/03/">March (
17)
</a></li>
871 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/04/">April (
12)
</a></li>
873 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/05/">May (
12)
</a></li>
875 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/06/">June (
20)
</a></li>
877 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/07/">July (
17)
</a></li>
879 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/08/">August (
6)
</a></li>
881 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/09/">September (
9)
</a></li>
883 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/10/">October (
17)
</a></li>
885 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/11/">November (
10)
</a></li>
887 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2012/12/">December (
7)
</a></li>
894 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/01/">January (
16)
</a></li>
896 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/02/">February (
6)
</a></li>
898 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/03/">March (
6)
</a></li>
900 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/04/">April (
7)
</a></li>
902 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/05/">May (
3)
</a></li>
904 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/06/">June (
2)
</a></li>
906 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/07/">July (
7)
</a></li>
908 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/08/">August (
6)
</a></li>
910 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/09/">September (
4)
</a></li>
912 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/10/">October (
2)
</a></li>
914 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/11/">November (
3)
</a></li>
916 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2011/12/">December (
1)
</a></li>
923 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/01/">January (
2)
</a></li>
925 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/02/">February (
1)
</a></li>
927 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/03/">March (
3)
</a></li>
929 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/04/">April (
3)
</a></li>
931 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/05/">May (
9)
</a></li>
933 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/06/">June (
14)
</a></li>
935 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/07/">July (
12)
</a></li>
937 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/08/">August (
13)
</a></li>
939 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/09/">September (
7)
</a></li>
941 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/10/">October (
9)
</a></li>
943 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/11/">November (
13)
</a></li>
945 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/12/">December (
12)
</a></li>
952 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/01/">January (
8)
</a></li>
954 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/02/">February (
8)
</a></li>
956 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/03/">March (
12)
</a></li>
958 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/04/">April (
10)
</a></li>
960 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/05/">May (
9)
</a></li>
962 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/06/">June (
3)
</a></li>
964 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/07/">July (
4)
</a></li>
966 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/08/">August (
3)
</a></li>
968 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/09/">September (
1)
</a></li>
970 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/10/">October (
2)
</a></li>
972 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/11/">November (
3)
</a></li>
974 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/12/">December (
3)
</a></li>
981 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/11/">November (
5)
</a></li>
983 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/12/">December (
7)
</a></li>
994 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (
13)
</a></li>
996 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/amiga">amiga (
1)
</a></li>
998 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/aros">aros (
1)
</a></li>
1000 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bankid">bankid (
4)
</a></li>
1002 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (
7)
</a></li>
1004 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (
13)
</a></li>
1006 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bsa">bsa (
2)
</a></li>
1008 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian (
90)
</a></li>
1010 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (
142)
</a></li>
1012 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/digistan">digistan (
10)
</a></li>
1014 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/docbook">docbook (
10)
</a></li>
1016 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (
4)
</a></li>
1018 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/english">english (
228)
</a></li>
1020 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (
21)
</a></li>
1022 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (
12)
</a></li>
1024 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (
12)
</a></li>
1026 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (
5)
</a></li>
1028 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (
11)
</a></li>
1030 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/intervju">intervju (
37)
</a></li>
1032 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (
7)
</a></li>
1034 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/kart">kart (
18)
</a></li>
1036 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ldap">ldap (
8)
</a></li>
1038 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/lenker">lenker (
6)
</a></li>
1040 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (
1)
</a></li>
1042 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (
5)
</a></li>
1044 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (
25)
</a></li>
1046 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk (
237)
</a></li>
1048 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug (
159)
</a></li>
1050 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (
9)
</a></li>
1052 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/open311">open311 (
2)
</a></li>
1054 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (
45)
</a></li>
1056 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/personvern">personvern (
67)
</a></li>
1058 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/raid">raid (
1)
</a></li>
1060 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/reprap">reprap (
11)
</a></li>
1062 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rfid">rfid (
2)
</a></li>
1064 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/robot">robot (
9)
</a></li>
1066 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rss">rss (
1)
</a></li>
1068 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ruter">ruter (
4)
</a></li>
1070 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (
2)
</a></li>
1072 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (
33)
</a></li>
1074 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (
4)
</a></li>
1076 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (
4)
</a></li>
1078 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard (
43)
</a></li>
1080 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (
3)
</a></li>
1082 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (
9)
</a></li>
1084 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (
21)
</a></li>
1086 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (
1)
</a></li>
1088 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/valg">valg (
8)
</a></li>
1090 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/video">video (
39)
</a></li>
1092 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (
4)
</a></li>
1094 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/web">web (
28)
</a></li>
1100 <p style=
"text-align: right">
1101 Created by
<a href=
"http://steve.org.uk/Software/chronicle">Chronicle v4.6
</a>