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/Creating__updating_and_checking_debian_copyright_semi_automatically.html">Creating, updating and checking debian/copyright semi-automatically</a></div>
  24       <div class="date">19th February 2016</div>
  25       <div class="body"><p>Making packages for Debian requires quite a lot of attention to
  26 details.  And one of the details is the content of the
  27 debian/copyright file, which should list all relevant licenses used by
  28 the code in the package in question, preferably in
  29 <a href="https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/">machine
  30 readable DEP5 format</a>.</p>
  31
  32 <p>For large packages with lots of contributors it is hard to write
  33 and update this file manually, and if you get some detail wrong, the
  34 package is normally rejected by the ftpmasters.  So getting it right
  35 the first time around get the package into Debian faster, and save
  36 both you and the ftpmasters some work..  Today, while trying to figure
  37 out what was wrong with
  38 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447">the
  39 zfsonlinux copyright file</a>, I decided to spend some time on
  40 figuring out the options for doing this job automatically, or at least
  41 semi-automatically.</p>
  42
  43 <p>Lucikly, there are at least two tools available for generating the
  44 file based on the code in the source package,
  45 <tt><a href="https://tracker.debian.org/pkg/debmake">debmake</a></tt>
  46 and <tt><a href="https://tracker.debian.org/pkg/cme">cme</a></tt>.  I'm
  47 not sure which one of them came first, but both seem to be able to
  48 create a sensible draft file.  As far as I can tell, none of them can
  49 be trusted to get the result just right, so the content need to be
  50 polished a bit before the file is OK to upload.  I found the debmake
  51 option in
  52 <a href="http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html">a
  53 blog posts from 2014</a>.
  54
  55 <p>To generate using debmake, use the -cc option:
  56
  57 <p><pre>
  58 debmake -cc > debian/copyright
  59 </pre></p>
  60
  61 <p>Note there are some problems with python and non-ASCII names, so
  62 this might not be the best option.</p>
  63
  64 <p>The cme option is based on a config parsing library, and I found
  65 this approach in
  66 <a href="https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/">a
  67 blog post from 2015</a>.  To generate using cme, use the 'update
  68 dpkg-copyright' option:
  69
  70 <p><pre>
  71 cme update dpkg-copyright -quiet
  72 </pre></p>
  73
  74 <p>This will create or update debian/copyright.  The cme tool seem to
  75 handle UTF-8 names better than debmake.</p>
  76
  77 <p>When the copyright file is created, I would also like some help to
  78 check if the file is correct.  For this I found two good options,
  79 <tt>debmake -k</tt> and <tt>license-reconcile</tt>.  The former seem
  80 to focus on license types and file matching, and is able to detect
  81 ineffective blocks in the copyright file.  The latter reports missing
  82 copyright holders and years, but was confused by inconsistent license
  83 names (like CDDL vs. CDDL-1.0).  I suspect it is good to use both and
  84 fix all issues reported by them before uploading.  But I do not know
  85 if the tools and the ftpmasters agree on what is important to fix in a
  86 copyright file, so the package might still be rejected.</p>
  87
  88 <p>The devscripts tool <tt>licensecheck</tt> deserve mentioning.  It
  89 will read through the source and try to find all copyright statements.
  90 It is not comparing the result to the content of debian/copyright, but
  91 can be useful when verifying the content of the copyright file.</p>
  92
  93 <p>Are you aware of better tools in Debian to create and update
  94 debian/copyright file.  Please let me know, or blog about it on
  95 planet.debian.org.</p>
  96
  97 <p>As usual, if you use Bitcoin and want to show your support of my
  98 activities, please send Bitcoin donations to my address
  99 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 100
 101 <p><strong>Update 2016-02-20</strong>: I got a tip from Mike Gabriel
 102 on how to use licensecheck and cdbs to create a draft copyright file
 103
 104 <p><pre>
 105 licensecheck --copyright -r `find * -type f` | \
 106   /usr/lib/cdbs/licensecheck2dep5 > debian/copyright.auto
 107 </pre></p>
 108
 109 <p>He mentioned that he normally check the generated file into the
 110 version control system to make it easier to discover license and
 111 copyright changes in the upstream source.  I will try to do the same
 112 with my packages in the future.</p>
 113 </div>
 114       <div class="tags">
 115
 116
 117         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>.
 118
 119
 120       </div>
 121     </div>
 122     <div class="padding"></div>
 123
 124     <div class="entry">
 125       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html">Using appstream in Debian to locate packages with firmware and mime type support</a></div>
 126       <div class="date"> 4th February 2016</div>
 127       <div class="body"><p>The <a href="https://wiki.debian.org/DEP-11">appstream system</a>
 128 is taking shape in Debian, and one provided feature is a very
 129 convenient way to tell you which package to install to make a given
 130 firmware file available when the kernel is looking for it.  This can
 131 be done using apt-file too, but that is for someone else to blog
 132 about. :)</p>
 133
 134 <p>Here is a small recipe to find the package with a given firmware
 135 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
 136 picked from the set of firmware announced using appstream in Debian
 137 unstable.  In general you would be looking for the firmware requested
 138 by the kernel during kernel module loading.  To find the package
 139 providing the example file, do like this:</p>
 140
 141 <blockquote><pre>
 142 % apt install appstream
 143 [...]
 144 % apt update
 145 [...]
 146 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
 147   awk '/Package:/ {print $2}'
 148 firmware-qlogic
 149 %
 150 </pre></blockquote>
 151
 152 <p>See <a href="https://wiki.debian.org/AppStream/Guidelines">the
 153 appstream wiki</a> page to learn how to embed the package metadata in
 154 a way appstream can use.</p>
 155
 156 <p>This same approach can be used to find any package supporting a
 157 given MIME type.  This is very useful when you get a file you do not
 158 know how to handle.  First find the mime type using <tt>file
 159 --mime-type</tt>, and next look up the package providing support for
 160 it.  Lets say you got an SVG file.  Its MIME type is image/svg+xml,
 161 and you can find all packages handling this type like this:</p>
 162
 163 <blockquote><pre>
 164 % apt install appstream
 165 [...]
 166 % apt update
 167 [...]
 168 % appstreamcli what-provides mimetype image/svg+xml | \
 169   awk '/Package:/ {print $2}'
 170 bkchem
 171 phototonic
 172 inkscape
 173 shutter
 174 tetzle
 175 geeqie
 176 xia
 177 pinta
 178 gthumb
 179 karbon
 180 comix
 181 mirage
 182 viewnior
 183 postr
 184 ristretto
 185 kolourpaint4
 186 eog
 187 eom
 188 gimagereader
 189 midori
 190 %
 191 </pre></blockquote>
 192
 193 <p>I believe the MIME types are fetched from the desktop file for
 194 packages providing appstream metadata.</p>
 195 </div>
 196       <div class="tags">
 197
 198
 199         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>.
 200
 201
 202       </div>
 203     </div>
 204     <div class="padding"></div>
 205
 206     <div class="entry">
 207       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html">Creepy, visualise geotagged social media information - nice free software</a></div>
 208       <div class="date">24th January 2016</div>
 209       <div class="body"><p>Most people seem not to realise that every time they walk around
 210 with the computerised radio beacon known as a mobile phone their
 211 position is tracked by the phone company and often stored for a long
 212 time (like every time a SMS is received or sent).  And if their
 213 computerised radio beacon is capable of running programs (often called
 214 mobile apps) downloaded from the Internet, these programs are often
 215 also capable of tracking their location (if the app requested access
 216 during installation).  And when these programs send out information to
 217 central collection points, the location is often included, unless
 218 extra care is taken to not send the location.  The provided
 219 information is used by several entities, for good and bad (what is
 220 good and bad, depend on your point of view).  What is certain, is that
 221 the private sphere and the right to free movement is challenged and
 222 perhaps even eradicated for those announcing their location this way,
 223 when they share their whereabouts with private and public
 224 entities.</p>
 225
 226 <p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png"></p>
 227
 228 <p>The phone company logs provide a register of locations to check out
 229 when one want to figure out what the tracked person was doing.  It is
 230 unavailable for most of us, but provided to selected government
 231 officials, company staff, those illegally buying information from
 232 unfaithful servants and crackers stealing the information.  But the
 233 public information can be collected and analysed, and a free software
 234 tool to do so is called
 235 <a href="http://www.geocreepy.com/">Creepy or Cree.py</a>.  I
 236 discovered it when I read
 237 <a href="http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html">an
 238 article about Creepy</a> in the Norwegian newspaper Aftenposten i
 239 November 2014, and decided to check if it was available in Debian.
 240 The python program was in Debian, but
 241 <a href="https://tracker.debian.org/pkg/creepy">the version in
 242 Debian</a> was completely broken and practically unmaintained.  I
 243 uploaded a new version which did not work quite right, but did not
 244 have time to fix it then.  This Christmas I decided to finally try to
 245 get Creepy operational in Debian.  Now a fixed version is available in
 246 Debian unstable and testing, and almost all Debian specific patches
 247 are now included
 248 <a href="https://github.com/jkakavas/creepy">upstream</a>.</p>
 249
 250 <p>The Creepy program visualises geolocation information fetched from
 251 Twitter, Instagram, Flickr and Google+, and allow one to get a
 252 complete picture of every social media message posted recently in a
 253 given area, or track the movement of a given individual across all
 254 these services.  Earlier it was possible to use the search API of at
 255 least some of these services without identifying oneself, but these
 256 days it is impossible.  This mean that to use Creepy, you need to
 257 configure it to log in as yourself on these services, and provide
 258 information to them about your search interests.  This should be taken
 259 into account when using Creepy, as it will also share information
 260 about yourself with the services.</p>
 261
 262 <p>The picture above show the twitter messages sent from (or at least
 263 geotagged with a position from) the city centre of Oslo, the capital
 264 of Norway.  One useful way to use Creepy is to first look at
 265 information tagged with an area of interest, and next look at all the
 266 information provided by one or more individuals who was in the area.
 267 I tested it by checking out which celebrity provide their location in
 268 twitter messages by checkout out who sent twitter messages near a
 269 Norwegian TV station, and next could track their position over time,
 270 making it possible to locate their home and work place, among other
 271 things.  A similar technique have been
 272 <a href="http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl">used
 273 to locate Russian soldiers in Ukraine</a>, and it is both a powerful
 274 tool to discover lying governments, and a useful tool to help people
 275 understand the value of the private information they provide to the
 276 public.</p>
 277
 278 <p>The package is not trivial to backport to Debian Stable/Jessie, as
 279 it depend on several python modules currently missing in Jessie (at
 280 least python-instagram, python-flickrapi and
 281 python-requests-toolbelt).</p>
 282
 283 <p>(I have uploaded
 284 <a href="https://screenshots.debian.net/package/creepy">the image to
 285 screenshots.debian.net</a> and licensed it under the same terms as the
 286 Creepy program in Debian.)</p>
 287 </div>
 288       <div class="tags">
 289
 290
 291         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/nice free software">nice free software</a>.
 292
 293
 294       </div>
 295     </div>
 296     <div class="padding"></div>
 297
 298     <div class="entry">
 299       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html">Always download Debian packages using Tor - the simple recipe</a></div>
 300       <div class="date">15th January 2016</div>
 301       <div class="body"><p>During his DebConf15 keynote, Jacob Appelbaum
 302 <a href="https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/">observed
 303 that those listening on the Internet lines would have good reason to
 304 believe a computer have a given security hole</a> if it download a
 305 security fix from a Debian mirror.  This is a good reason to always
 306 use encrypted connections to the Debian mirror, to make sure those
 307 listening do not know which IP address to attack.  In August, Richard
 308 Hartmann observed that encryption was not enough, when it was possible
 309 to interfere download size to security patches or the fact that
 310 download took place shortly after a security fix was released, and
 311 <a href="http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/">proposed
 312 to always use Tor to download packages from the Debian mirror</a>.  He
 313 was not the first to propose this, as the
 314 <tt><a href="https://tracker.debian.org/pkg/apt-transport-tor">apt-transport-tor</a></tt>
 315 package by Tim Retout already existed to make it easy to convince apt
 316 to use <a href="https://www.torproject.org/">Tor</a>, but I was not
 317 aware of that package when I read the blog post from Richard.</p>
 318
 319 <p>Richard discussed the idea with Peter Palfrader, one of the Debian
 320 sysadmins, and he set up a Tor hidden service on one of the central
 321 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
 322 it possible to download packages directly between two tor nodes,
 323 making sure the network traffic always were encrypted.</p>
 324
 325 <p>Here is a short recipe for enabling this on your machine, by
 326 installing <tt>apt-transport-tor</tt> and replacing http and https
 327 urls with tor+http and tor+https, and using the hidden service instead
 328 of the official Debian mirror site.  I recommend installing
 329 <tt>etckeeper</tt> before you start to have a history of the changes
 330 done in /etc/.</p>
 331
 332 <blockquote><pre>
 333 apt install apt-transport-tor
 334 sed -i 's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%' /etc/apt/sources.list
 335 sed -i 's% http% tor+http%' /etc/apt/sources.list
 336 </pre></blockquote>
 337
 338 <p>If you have more sources listed in /etc/apt/sources.list.d/, run
 339 the sed commands for these too.  The sed command is assuming your are
 340 using the ftp.debian.org Debian mirror.  Adjust the command (or just
 341 edit the file manually) to match your mirror.</p>
 342
 343 <p>This work in Debian Jessie and later.  Note that tools like
 344 <tt>apt-file</tt> only recently started using the apt transport
 345 system, and do not work with these tor+http URLs.  For
 346 <tt>apt-file</tt> you need the version currently in experimental,
 347 which need a recent apt version currently only in unstable.  So if you
 348 need a working <tt>apt-file</tt>, this is not for you.</p>
 349
 350 <p>Another advantage from this change is that your machine will start
 351 using Tor regularly and at fairly random intervals (every time you
 352 update the package lists or upgrade or install a new package), thus
 353 masking other Tor traffic done from the same machine.  Using Tor will
 354 become normal for the machine in question.</p>
 355
 356 <p>On <a href="https://wiki.debian.org/FreedomBox">Freedombox</a>, APT
 357 is set up by default to use <tt>apt-transport-tor</tt> when Tor is
 358 enabled.  It would be great if it was the default on any Debian
 359 system.</p>
 360 </div>
 361       <div class="tags">
 362
 363
 364         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/sikkerhet">sikkerhet</a>.
 365
 366
 367       </div>
 368     </div>
 369     <div class="padding"></div>
 370
 371     <div class="entry">
 372       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Nedlasting_fra_NRK__som_Matroska_med_undertekster.html">Nedlasting fra NRK, som Matroska med undertekster</a></div>
 373       <div class="date"> 2nd January 2016</div>
 374       <div class="body"><p>Det kommer stadig nye løsninger for å ta lagre unna innslag fra NRK
 375 for å se på det senere.  For en stund tilbake kom jeg over et script
 376 nrkopptak laget av Ingvar Hagelund.  Han fjernet riktignok sitt script
 377 etter forespørsel fra Erik Bolstad i NRK, men noen tok heldigvis og
 378 gjorde det <a href="https://github.com/liangqi/nrkopptak">tilgjengelig
 379 via github</a>.</p>
 380
 381 <p>Scriptet kan lagre som MPEG4 eller Matroska, og bake inn
 382 undertekster i fila på et vis som blant annet VLC forstår.  For å
 383 bruke scriptet, kopier ned git-arkivet og kjør</p>
 384
 385 <p><pre>
 386 nrkopptak/bin/nrk-opptak k <ahref="https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1">https://tv.nrk.no/serie/bmi-turne/MUHH45000115/sesong-1/episode-1</a>
 387 </pre></p>
 388
 389 <p>URL-eksemplet er dagens toppsak på tv.nrk.no.  Argument 'k' ber
 390 scriptet laste ned og lagre som Matroska.  Det finnes en rekke andre
 391 muligheter for valg av kvalitet og format.</p>
 392
 393 <p>Jeg foretrekker dette scriptet fremfor youtube-dl, som
 394 <a href="http://people.skolelinux.org/pere/blog/Hvordan_enkelt_laste_ned_filmer_fra_NRK_med_den__nye__l_sningen.html">
 395 nevnt i 2014 støtter NRK</a> og en rekke andre videokilder, på grunn
 396 av at nrkopptak samler undertekster og video i en enkelt fil, hvilket
 397 gjør håndtering enklere på disk.</p>
 398 </div>
 399       <div class="tags">
 400
 401
 402         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 403
 404
 405       </div>
 406     </div>
 407     <div class="padding"></div>
 408
 409     <div class="entry">
 410       <div class="title"><a href="http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html">OpenALPR, find car license plates in video streams - nice free software</a></div>
 411       <div class="date">23rd December 2015</div>
 412       <div class="body"><p>When I was a kid, we used to collect "car numbers", as we used to
 413 call the car license plate numbers in those days.  I would write the
 414 numbers down in my little book and compare notes with the other kids
 415 to see how many region codes we had seen and if we had seen some
 416 exotic or special region codes and numbers.  It was a fun game to pass
 417 time, as we kids have plenty of it.</p>
 418
 419 <p>A few days I came across
 420 <a href="https://github.com/openalpr/openalpr">the OpenALPR
 421 project</a>, a free software project to automatically discover and
 422 report license plates in images and video streams, and provide the
 423 "car numbers" in a machine readable format.  I've been looking for
 424 such system for a while now, because I believe it is a bad idea that the
 425 <a href="https://en.wikipedia.org/wiki/Automatic_number_plate_recognition">automatic
 426 number plate recognition</a> tool only is available in the hands of
 427 the powerful, and want it to be available also for the powerless to
 428 even the score when it comes to surveillance and sousveillance.  I
 429 discovered the developer
 430 <a href="https://bugs.debian.org/747509">wanted to get the tool into
 431 Debian</a>, and as I too wanted it to be in Debian, I volunteered to
 432 help him get it into shape to get the package uploaded into the Debian
 433 archive.</p>
 434
 435 <p>Today we finally managed to get the package into shape and uploaded
 436 it into Debian, where it currently
 437 <a href="https://ftp-master.debian.org//new/openalpr_2.2.1-1.html">waits
 438 in the NEW queue</a> for review by the Debian ftpmasters.</p>
 439
 440 <p>I guess you are wondering why on earth such tool would be useful
 441 for the common folks, ie those not running a large government
 442 surveillance system?  Well, I plan to put it in a computer on my bike
 443 and in my car, tracking the cars nearby and allowing me to be notified
 444 when number plates on my watch list are discovered.  Another use case
 445 was suggested by a friend of mine, who wanted to set it up at his home
 446 to open the car port automatically when it discovered the plate on his
 447 car.  When I mentioned it perhaps was a bit foolhardy to allow anyone
 448 capable of placing his license plate number of a piece of cardboard to
 449 open his car port, men replied that it was always unlocked anyway.  I
 450 guess for such use case it make sense.  I am sure there are other use
 451 cases too, for those with imagination and a vision.</p>
 452
 453 <p>If you want to build your own version of the Debian package, check
 454 out the upstream git source and symlink ./distros/debian to ./debian/
 455 before running "debuild" to build the source.  Or wait a bit until the
 456 package show up in unstable.</p>
 457 </div>
 458       <div class="tags">
 459
 460
 461         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/nice free software">nice free software</a>.
 462
 463
 464       </div>
 465     </div>
 466     <div class="padding"></div>
 467
 468     <div class="entry">
 469       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html">Using appstream with isenkram to install hardware related packages in Debian</a></div>
 470       <div class="date">20th December 2015</div>
 471       <div class="body"><p>Around three years ago, I created
 472 <a href="http://packages.qa.debian.org/isenkram">the isenkram
 473 system</a> to get a more practical solution in Debian for handing
 474 hardware related packages.  A GUI system in the isenkram package will
 475 present a pop-up dialog when some hardware dongle supported by
 476 relevant packages in Debian is inserted into the machine.  The same
 477 lookup mechanism to detect packages is available as command line
 478 tools in the isenkram-cli package.  In addition to mapping hardware,
 479 it will also map kernel firmware files to packages and make it easy to
 480 install needed firmware packages automatically.  The key for this
 481 system to work is a good way to map hardware to packages, in other
 482 words, allow packages to announce what hardware they will work
 483 with.</p>
 484
 485 <p>I started by providing data files in the isenkram source, and
 486 adding code to download the latest version of these data files at run
 487 time, to ensure every user had the most up to date mapping available.
 488 I also added support for storing the mapping in the Packages file in
 489 the apt repositories, but did not push this approach because while I
 490 was trying to figure out how to best store hardware/package mappings,
 491 <a href="http://www.freedesktop.org/software/appstream/docs/">the
 492 appstream system</a> was announced.  I got in touch and suggested to
 493 add the hardware mapping into that data set to be able to use
 494 appstream as a data source, and this was accepted at least for the
 495 Debian version of appstream.</p>
 496
 497 <p>A few days ago using appstream in Debian for this became possible,
 498 and today I uploaded a new version 0.20 of isenkram adding support for
 499 appstream as a data source for mapping hardware to packages.  The only
 500 package so far using appstream to announce its hardware support is my
 501 pymissile package.  I got help from Matthias Klumpp with figuring out
 502 how do add the required
 503 <a href="https://appstream.debian.org/html/sid/main/metainfo/pymissile.html">metadata
 504 in pymissile</a>.  I added a file debian/pymissile.metainfo.xml with
 505 this content:</p>
 506
 507 <blockquote><pre>
 508 &lt;?xml version="1.0" encoding="UTF-8"?&gt;
 509 &lt;component&gt;
 510   &lt;id&gt;pymissile&lt;/id&gt;
 511   &lt;metadata_license&gt;MIT&lt;/metadata_license&gt;
 512   &lt;name&gt;pymissile&lt;/name&gt;
 513   &lt;summary&gt;Control original Striker USB Missile Launcher&lt;/summary&gt;
 514   &lt;description&gt;
 515     &lt;p&gt;
 516       Pymissile provides a curses interface to control an original
 517       Marks and Spencer / Striker USB Missile Launcher, as well as a
 518       motion control script to allow a webcamera to control the
 519       launcher.
 520     &lt;/p&gt;
 521   &lt;/description&gt;
 522   &lt;provides&gt;
 523     &lt;modalias&gt;usb:v1130p0202d*&lt;/modalias&gt;
 524   &lt;/provides&gt;
 525 &lt;/component&gt;
 526 </pre></blockquote>
 527
 528 <p>The key for isenkram is the component/provides/modalias value,
 529 which is a glob style match rule for hardware specific strings
 530 (modalias strings) provided by the Linux kernel.  In this case, it
 531 will map to all USB devices with vendor code 1130 and product code
 532 0202.</p>
 533
 534 <p>Note, it is important that the license of all the metadata files
 535 are compatible to have permissions to aggregate them into archive wide
 536 appstream files.  Matthias suggested to use MIT or BSD licenses for
 537 these files.  A challenge is figuring out a good id for the data, as
 538 it is supposed to be globally unique and shared across distributions
 539 (in other words, best to coordinate with upstream what to use).  But
 540 it can be changed later or, so we went with the package name as
 541 upstream for this project is dormant.</p>
 542
 543 <p>To get the metadata file installed in the correct location for the
 544 mirror update scripts to pick it up and include its content the
 545 appstream data source, the file must be installed in the binary
 546 package under /usr/share/appdata/.  I did this by adding the following
 547 line to debian/pymissile.install:</p>
 548
 549 <blockquote><pre>
 550 debian/pymissile.metainfo.xml usr/share/appdata
 551 </pre></blockquote>
 552
 553 <p>With that in place, the command line tool isenkram-lookup will list
 554 all packages useful on the current computer automatically, and the GUI
 555 pop-up handler will propose to install the package not already
 556 installed if a hardware dongle is inserted into the machine in
 557 question.</p>
 558
 559 <p>Details of the modalias field in appstream is available from the
 560 <a href="https://wiki.debian.org/DEP-11">DEP-11</a> proposal.</p>
 561
 562 <p>To locate the modalias values of all hardware present in a machine,
 563 try running this command on the command line:</p>
 564
 565 <blockquote><pre>
 566 cat $(find /sys/devices/|grep modalias)
 567 </pre></blockquote>
 568
 569 <p>To learn more about the isenkram system, please check out
 570 <a href="http://people.skolelinux.org/pere/blog/tags/isenkram/">my
 571 blog posts tagged isenkram</a>.</p>
 572 </div>
 573       <div class="tags">
 574
 575
 576         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/isenkram">isenkram</a>.
 577
 578
 579       </div>
 580     </div>
 581     <div class="padding"></div>
 582
 583     <div class="entry">
 584       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Bokhandeldistribusjon_av_boken_Fri_kultur_av_Lawrence_Lessig.html">Bokhandeldistribusjon av boken Fri kultur av Lawrence Lessig</a></div>
 585       <div class="date">14th December 2015</div>
 586       <div class="body"><p><strong>Besøk
 587 <a href="https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">lulu.com</a>
 588 eller
 589 <a href="https://www.amazon.com/Fri-kultur-Norwegian-Lawrence-Lessig/dp/8269018236/">Amazon</a>
 590 for å kjøpe boken på papir, eller last ned ebook som
 591 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.pdf">PDF</a>,
 592 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.epub">ePub</a>
 593 eller
 594 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/raw/master/archive/freeculture.nb.mobi">MOBI</a>
 595 fra
 596 <a href="https://github.com/petterreinholdtsen/free-culture-lessig/">github</a>.</strong></p>
 597
 598 <p>Jeg ble gledelig overrasket i dag da jeg oppdaget at boken jeg har
 599 gitt ut
 600 <a href="https://www.amazon.com/Fri-kultur-Norwegian-Lawrence-Lessig/dp/8269018236/">hadde
 601 dukket opp i Amazon</a>.  Jeg hadde trodd det skulle ta lenger tid, da
 602 jeg fikk beskjed om at det skulle ta seks til åtte uker.
 603 Amazonoppføringen er et resultat av at jeg for noen uker siden
 604 diskuterte prissetting og håndtering av profitt med forfatteren.  Det
 605 måtte avklares da bruksvilkårene til boken har krav om
 606 ikke-kommersiell bruk.  Vi ble enige om at overskuddet fra salg av
 607 boken skal sendes til
 608 <a href="https://creativecommons.org/">Creative Commons-stiftelsen</a>.
 609 Med det på plass kunne jeg be
 610 <a href="https://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html">lulu.com</a>
 611 om å gi boken «utvidet» distribusjon.  Årsaken til at
 612 bokhandeldistribusjon var litt utfordrende er at bokhandlere krever
 613 mulighet for profitt på bøkene de selger (selvfølgelig), og dermed
 614 måtte de få lov til å selge til høyere pris enn lulu.com.  I tillegg
 615 er det krav om samme pris på lulu.com og i bokhandlene, dermed blir
 616 prisen økt også hos lulu.com.  Hva skulle jeg gjøre med den profitten
 617 uten å bryte med klausulen om ikkekommersiell?  Løsningen var å gi
 618 bort profitten til CC-stiftelsen.  Prisen på boken ble nesten
 619 tredoblet, til $19.99 (ca. 160,-) pluss frakt, men synligheten øker
 620 betraktelig når den kan finnes i katalogene til store nettbokhandlere.
 621 Det betyr at hvis du allerede har kjøpt boken har du fått den veldig
 622 billig, og kjøper du den nå, får du den fortsatt billig samt donerer i
 623 tillegg noen tiere til fremme av Creative Commons.</p>
 624
 625 <p>Mens jeg var i gang med å titte etter informasjon om boken
 626 oppdaget jeg  at den også var dukket opp på
 627 <a href="https://books.google.no/books?id=uKUGCwAAQBAJ">Google
 628 Books</a>, der en kan lese den på web.  PDF-utgaven har ennå ikke
 629 dukket opp hos <a href="https://www.nb.no/">Nasjonalbiblioteket</a>,
 630 men det regner jeg med kommer på plass i løpet av noen uker.  Boken er
 631 heller ikke dukket opp hos
 632 <a href="https://www.barnesandnoble.com/">Barnes & Noble</a> ennå, men
 633 jeg antar det bare er et tidsspørsmål før dette er på plass.</p>
 634
 635 <p>Boken er dessverre ikke tilgjengelig fra norske bokhandlere, og
 636 kommer neppe til å bli det med det første.  Årsaken er at for å få det
 637 til måtte jeg personlig håndtere bestilling av bøker, hvilket jeg ikke
 638 er interessert i å bruke tid på.  Jeg kunne betalt ca 2000,- til
 639 <a href="http://www.bokbasen.no/">den norske bokbasen</a>, en felles
 640 database over bøker tilgjengelig for norske bokhandlere, for å få en
 641 oppføring der, men da måtte jeg tatt imot bestillinger på epost og
 642 sendt ut bøker selv.  Det ville krevd at jeg var klar til å
 643 sende ut bøker på kort varsel, dvs. holdt meg med ekstra bøker,
 644 konvolutter og frimerker.  Bokbasen har visst ikke opplegg for å be
 645 bokhandlene bestille direkte via web, så jeg droppet oppføring der.
 646 Jeg har spurt Haugen bok og Tronsmo direkte på epost om de er
 647 interessert i å ta inn boken i sin bestillingskatalog, men ikke fått
 648 svar, så jeg antar de ikke er interessert.  Derimot har jeg fått en
 649 hyggelig henvendelse fra Biblioteksentralen som fortalte at de har
 650 lagt den inn i sin database slik at deres bibliotekskunder enkelt kan
 651 bestille den via dem.</p>
 652
 653 <p>Boken er i følge
 654 <a href="http://bibsys-almaprimo.hosted.exlibrisgroup.com/primo_library/libweb/action/display.do?tabs=detailsTab&ct=display&fn=search&doc=BIBSYS_ILS71518423420002201&indx=1&recIds=BIBSYS_ILS71518423420002201&recIdxs=0&elementId=0&renderMode=poppedOut&displayMode=full&frbrVersion=&dscnt=0&tab=library_catalogue&dstmp=1448543801124&vl(freeText0)=fri%20kultur&vid=UBO&mode=Basic">Bibsys/Oria</a>
 655 og bokdatabasen til
 656 <a href="https://www.deich.folkebibl.no/cgi-bin/websok?tnr=1819617">Deichmanske</a>
 657 tilgjengelig fra flere biblioteker allerede, og alle eksemplarer er
 658 visst allerede utlånt med ventetid.  Det synes jeg er veldig gledelig
 659 å se.  Jeg håper mange kommer til å lese boken.  Jeg tror den er
 660 spesielt egnet for foreldre og bekjente av oss nerder for å forklare
 661 hva slags problemer vi ser med dagens opphavsrettsregime.</p>
 662 </div>
 663       <div class="tags">
 664
 665
 666         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture</a>, <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
 667
 668
 669       </div>
 670     </div>
 671     <div class="padding"></div>
 672
 673     <div class="entry">
 674       <div class="title"><a href="http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html">The GNU General Public License is not magic pixie dust</a></div>
 675       <div class="date">30th November 2015</div>
 676       <div class="body"><p>A blog post from my fellow Debian developer Paul Wise titled
 677 "<a href="http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/">The
 678 GPL is not magic pixie dust</a>" explain the importance of making sure
 679 the <a href="http://www.gnu.org/copyleft/gpl.html">GPL</a> is enforced.
 680 I quote the blog post from Paul in full here with his permission:<p>
 681
 682 <blockquote>
 683
 684 <p><a href="https://sfconservancy.org/supporter/"><img src="https://sfconservancy.org/img/supporter-badge.png" width="194" height="90" alt="Become a Software Freedom Conservancy Supporter!" align="right" border="0" /></a></p>
 685
 686 <blockquote>
 687 The GPL is not magic pixie dust. It does not work by itself.<br/>
 688
 689 The first step is to choose a
 690 <a href="https://copyleft.org/">copyleft</a> license for your
 691 code.<br/>
 692
 693 The next step is, when someone fails to follow that copyleft license,
 694 <b>it must be enforced</b><br/>
 695
 696 and its a simple fact of our modern society that such type of
 697 work<br/>
 698
 699 is incredibly expensive to do and incredibly difficult to do.
 700 </blockquote>
 701
 702 <p><small>-- <a href="http://ebb.org/bkuhn/">Bradley Kuhn</a>, in
 703 <a href="http://faif.us/" title="Free as in Freedom">FaiF</a>
 704 <a href="http://faif.us/cast/2015/nov/24/0x57/">episode
 705 0x57</a></small></p>
 706
 707 <p>As the Debian Website
 708 <a href="https://bugs.debian.org/794116">used</a>
 709 <a href="https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=1.24&amp;r2=1.25">to</a>
 710 imply, public domain and permissively licensed software can lead to
 711 the production of more proprietary software as people discover useful
 712 software, extend it and or incorporate it into their hardware or
 713 software products.  Copyleft licenses such as the GNU GPL were created
 714 to close off this avenue to the production of proprietary software but
 715 such licenses are not enough.  With the ongoing adoption of Free
 716 Software by individuals and groups, inevitably the community's
 717 expectations of license compliance are violated, usually out of
 718 ignorance of the way Free Software works, but not always.  As Karen
 719 and Bradley explained in <a href="http://faif.us/" title="Free as in
 720 Freedom">FaiF</a>
 721 <a href="http://faif.us/cast/2015/nov/24/0x57/">episode 0x57</a>,
 722 copyleft is nothing if no-one is willing and able to stand up in court
 723 to protect it.  The reality of today's world is that legal
 724 representation is expensive, difficult and time consuming.  With
 725 <a href="http://gpl-violations.org/">gpl-violations.org</a> in hiatus
 726 <a href="http://gpl-violations.org/news/20151027-homepage-recovers/">until</a>
 727 some time in 2016, the <a href="https://sfconservancy.org/">Software
 728 Freedom Conservancy</a> (a tax-exempt charity) is the major defender
 729 of the Linux project, Debian and other groups against GPL violations.
 730 In March the SFC supported a
 731 <a href="https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/">lawsuit
 732 by Christoph Hellwig</a> against VMware for refusing to
 733 <a href="https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html">comply
 734 with the GPL</a> in relation to their use of parts of the Linux
 735 kernel.  Since then two of their sponsors pulled corporate funding and
 736 conferences
 737 <a href="https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/">blocked
 738 or cancelled their talks</a>.  As a result they have decided to rely
 739 less on corporate funding and more on the broad community of
 740 individuals who support Free Software and copyleft.  So the SFC has
 741 <a href="https://sfconservancy.org/news/2015/nov/23/2015fundraiser/">launched</a>
 742 a <a href="https://sfconservancy.org/supporter/">campaign</a> to create
 743 a community of folks who stand up for copyleft and the GPL by
 744 supporting their work on promoting and supporting copyleft and Free
 745 Software.</p>
 746
 747 <p>If you support Free Software,
 748 <a href="https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/">like</a>
 749 what the SFC do, agree with their
 750 <a href="https://sfconservancy.org/linux-compliance/principles.html">compliance
 751 principles</a>, are happy about their
 752 <a href="https://sfconservancy.org/supporter/">successes</a> in 2015,
 753 work on a project that is an SFC
 754 <a href="https://sfconservancy.org/members/current/">member</a> and or
 755 just want to stand up for copyleft, please join
 756 <a href="https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA">Christopher
 757 Allan Webber</a>,
 758 <a href="https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/">Carol
 759 Smith</a>,
 760 <a href="http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/">Jono
 761 Bacon</a>, myself and
 762 <a href="https://sfconservancy.org/sponsors/#supporters">others</a> in
 763 becoming a
 764 <a href="https://sfconservancy.org/supporter/">supporter</a>.  For the
 765 next week your donation will be
 766 <a href="https://sfconservancy.org/news/2015/nov/27/black-friday/">matched</a>
 767 by an anonymous donor.  Please also consider asking your employer to
 768 match your donation or become a sponsor of SFC.  Don't forget to
 769 spread the word about your support for SFC via email, your blog and or
 770 social media accounts.</p>
 771
 772 </blockquote>
 773
 774 <p>I agree with Paul on this topic and just signed up as a Supporter
 775 of Software Freedom Conservancy myself.  Perhaps you should be a
 776 supporter too?</p>
 777 </div>
 778       <div class="tags">
 779
 780
 781         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>.
 782
 783
 784       </div>
 785     </div>
 786     <div class="padding"></div>
 787
 788     <div class="entry">
 789       <div class="title"><a href="http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html">PGP key transition statement for key EE4E02F9</a></div>
 790       <div class="date">17th November 2015</div>
 791       <div class="body"><p>I've needed a new OpenPGP key for a while, but have not had time to
 792 set it up properly.  I wanted to generate it offline and have it
 793 available on <a href="http://shop.kernelconcepts.de/#openpgp">a OpenPGP
 794 smart card</a> for daily use, and learning how to do it and finding
 795 time to sit down with an offline machine almost took forever.  But
 796 finally I've been able to complete the process, and have now moved
 797 from my old GPG key to a new GPG key.  See
 798 <a href="http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt">the
 799 full transition statement, signed with both my old and new key</a> for
 800 the details.  This is my new key:</p>
 801
 802 <pre>
 803 pub   3936R/<a href="http://pgp.cs.uu.nl/stats/111D6B29EE4E02F9.html">111D6B29EE4E02F9</a> 2015-11-03 [expires: 2019-11-14]
 804       Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1  D827 111D 6B29 EE4E 02F9
 805 uid                  Petter Reinholdtsen &lt;pere@hungry.com&gt;
 806 uid                  Petter Reinholdtsen &lt;pere@debian.org&gt;
 807 sub   4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
 808 sub   4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
 809 sub   4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
 810 </pre>
 811
 812 <p>The key can be downloaded from the OpenPGP key servers, signed by
 813 my old key.</p>
 814
 815 <p>If you signed my old key
 816 (<a href="http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html">DB4CCC4B2A30D729</a>),
 817 I'd very much appreciate a signature on my new key, details and
 818 instructions in the transition statement. I m happy to reciprocate if
 819 you have a similarly signed transition statement to present.</p>
 820 </div>
 821       <div class="tags">
 822
 823
 824         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/sikkerhet">sikkerhet</a>.
 825
 826
 827       </div>
 828     </div>
 829     <div class="padding"></div>
 830
 831     <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>
 832     <div id="sidebar">
 833
 834
 835
 836 <h2>Archive</h2>
 837 <ul>
 838
 839 <li>2016
 840 <ul>
 841
 842 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
 843
 844 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
 845
 846 </ul></li>
 847
 848 <li>2015
 849 <ul>
 850
 851 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
 852
 853 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
 854
 855 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
 856
 857 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
 858
 859 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
 860
 861 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
 862
 863 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
 864
 865 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
 866
 867 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
 868
 869 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
 870
 871 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
 872
 873 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
 874
 875 </ul></li>
 876
 877 <li>2014
 878 <ul>
 879
 880 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 881
 882 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 883
 884 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
 885
 886 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
 887
 888 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
 889
 890 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
 891
 892 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
 893
 894 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
 895
 896 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
 897
 898 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
 899
 900 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
 901
 902 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
 903
 904 </ul></li>
 905
 906 <li>2013
 907 <ul>
 908
 909 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 910
 911 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 912
 913 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 914
 915 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 916
 917 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 918
 919 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 920
 921 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 922
 923 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 924
 925 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 926
 927 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 928
 929 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 930
 931 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 932
 933 </ul></li>
 934
 935 <li>2012
 936 <ul>
 937
 938 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 939
 940 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 941
 942 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 943
 944 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 945
 946 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 947
 948 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 949
 950 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 951
 952 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 953
 954 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 955
 956 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 957
 958 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 959
 960 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 961
 962 </ul></li>
 963
 964 <li>2011
 965 <ul>
 966
 967 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 968
 969 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 970
 971 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 972
 973 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 974
 975 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 976
 977 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 978
 979 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 980
 981 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 982
 983 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 984
 985 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 986
 987 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 988
 989 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 990
 991 </ul></li>
 992
 993 <li>2010
 994 <ul>
 995
 996 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 997
 998 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 999
1000 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1001
1002 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1003
1004 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1005
1006 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1007
1008 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1009
1010 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1011
1012 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1013
1014 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1015
1016 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1017
1018 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1019
1020 </ul></li>
1021
1022 <li>2009
1023 <ul>
1024
1025 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1026
1027 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1028
1029 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1030
1031 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1032
1033 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1034
1035 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1036
1037 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1038
1039 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1040
1041 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1042
1043 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1044
1045 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1046
1047 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1048
1049 </ul></li>
1050
1051 <li>2008
1052 <ul>
1053
1054 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1055
1056 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1057
1058 </ul></li>
1059
1060 </ul>
1061
1062
1063
1064 <h2>Tags</h2>
1065 <ul>
1066
1067  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1068
1069  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1070
1071  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1072
1073  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1074
1075  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
1076
1077  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (15)</a></li>
1078
1079  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1080
1081  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1082
1083  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (120)</a></li>
1084
1085  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (154)</a></li>
1086
1087  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1088
1089  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
1090
1091  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (20)</a></li>
1092
1093  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1094
1095  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (302)</a></li>
1096
1097  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1098
1099  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1100
1101  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (25)</a></li>
1102
1103  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1104
1105  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (16)</a></li>
1106
1107  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
1108
1109  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
1110
1111  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (11)</a></li>
1112
1113  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (19)</a></li>
1114
1115  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1116
1117  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1118
1119  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1120
1121  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1122
1123  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1124
1125  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (37)</a></li>
1126
1127  <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (7)</a></li>
1128
1129  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (273)</a></li>
1130
1131  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (177)</a></li>
1132
1133  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (22)</a></li>
1134
1135  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1136
1137  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (58)</a></li>
1138
1139  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (92)</a></li>
1140
1141  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1142
1143  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1144
1145  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1146
1147  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1148
1149  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1150
1151  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1152
1153  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1154
1155  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1156
1157  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (45)</a></li>
1158
1159  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1160
1161  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1162
1163  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (48)</a></li>
1164
1165  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1166
1167  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (10)</a></li>
1168
1169  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (36)</a></li>
1170
1171  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
1172
1173  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1174
1175  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1176
1177  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (55)</a></li>
1178
1179  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1180
1181  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (38)</a></li>
1182
1183 </ul>
1184
1185
1186     </div>
1187     <p style="text-align: right">
1188  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1189 </p>
1190
1191   </body>
1192 </html>