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/Free_software_car_computer_solution_.html">Free software car computer solution?</a></div>
  24       <div class="date">29th May 2014</div>
  25       <div class="body"><p>Dear lazyweb.  I'm planning to set up a small Raspberry Pi computer
  26 in my car, connected to
  27 <a href="http://www.dx.com/p/400a-4-0-tft-lcd-digital-monitor-for-vehicle-parking-reverse-camera-1440x272-12v-dc-57776">a
  28 small screen</a> next to the rear mirror.  I plan to hook it up with a
  29 GPL and a USB wifi card too.  The idea is to get my own
  30 "<a href="http://en.wikipedia.org/wiki/Carputer">Carputer</a>".  But I
  31 wonder if someone already created a good free software solution for
  32 such car computer.</p>
  33
  34 <p>This is my current wish list for such system:</p>
  35
  36 <ul>
  37
  38  <li>Work on Raspberry Pi.</li>
  39
  40  <li>Show current speed limit based on location, and warn if going too
  41    fast (for example using color codes yellow and red on the screen,
  42    or make a sound).  This could be done either using either data from
  43    <a href="http://www.openstreetmap.org/">Openstreetmap</a> or OCR
  44    info gathered from a dashboard camera.</li>
  45
  46  <li>Track automatic toll road passes and their cost, show total spent
  47    and make it possible to calculate toll costs for planned
  48    route.</li>
  49
  50  <li>Collect GPX tracks for use with OpenStreetMap.</li>
  51
  52  <li>Automatically detect and use any wireless connection to connect
  53    to home server.  Try IP over DNS
  54    (<a href="http://dev.kryo.se/iodine/">iodine</a>) or ICMP
  55    (<a href="http://code.gerade.org/hans/">Hans</a>) if direct
  56    connection do not work.</li>
  57
  58  <li>Set up mesh network to talk to other cars with the same system,
  59    or some stanard car mesh protocol.</li>
  60
  61  <li>Warn when approaching speed cameras and speed camera ranges
  62    (speed calculated between two cameras).</li>
  63
  64  <li>Suport dashboard/front facing camera to discover speed limits and
  65    run OCR to track registration number of passing cars.</li>
  66
  67 </ul>
  68
  69 <p>If you know of any free software car computer system supporting
  70 some or all of these features, please let me know.</p>
  71 </div>
  72       <div class="tags">
  73
  74
  75         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>.
  76
  77
  78       </div>
  79     </div>
  80     <div class="padding"></div>
  81
  82     <div class="entry">
  83       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Half_the_Coverity_issues_in_Gnash_fixed_in_the_next_release.html">Half the Coverity issues in Gnash fixed in the next release</a></div>
  84       <div class="date">29th April 2014</div>
  85       <div class="body"><p>I've been following <a href="http://www.getgnash.org/">the Gnash
  86 project</a> for quite a while now.  It is a free software
  87 implementation of Adobe Flash, both a standalone player and a browser
  88 plugin.  Gnash implement support for the AVM1 format (and not the
  89 newer AVM2 format - see
  90 <a href="http://lightspark.github.io/">Lightspark</a> for that one),
  91 allowing several flash based sites to work.  Thanks to the friendly
  92 developers at Youtube, it also work with Youtube videos, because the
  93 Javascript code at Youtube detect Gnash and serve a AVM1 player to
  94 those users. :) Would be great if someone found time to implement AVM2
  95 support, but it has not happened yet.  If you install both Lightspark
  96 and Gnash, Lightspark will invoke Gnash if it find a AVM1 flash file,
  97 so you can get both handled as free software.  Unfortunately,
  98 Lightspark so far only implement a small subset of AVM2, and many
  99 sites do not work yet.</p>
 100
 101 <p>A few months ago, I started looking at
 102 <a href="http://scan.coverity.com/">Coverity</a>, the static source
 103 checker used to find heaps and heaps of bugs in free software (thanks
 104 to the donation of a scanning service to free software projects by the
 105 company developing this non-free code checker), and Gnash was one of
 106 the projects I decided to check out.  Coverity is able to find lock
 107 errors, memory errors, dead code and more.  A few days ago they even
 108 extended it to also be able to find the heartbleed bug in OpenSSL.
 109 There are heaps of checks being done on the instrumented code, and the
 110 amount of bogus warnings is quite low compared to the other static
 111 code checkers I have tested over the years.</p>
 112
 113 <p>Since a few weeks ago, I've been working with the other Gnash
 114 developers squashing bugs discovered by Coverity.  I was quite happy
 115 today when I checked the current status and saw that of the 777 issues
 116 detected so far, 374 are marked as fixed.  This make me confident that
 117 the next Gnash release will be more stable and more dependable than
 118 the previous one.  Most of the reported issues were and are in the
 119 test suite, but it also found a few in the rest of the code.</p>
 120
 121 <p>If you want to help out, you find us on
 122 <a href="https://lists.gnu.org/mailman/listinfo/gnash-dev">the
 123 gnash-dev mailing list</a> and on
 124 <a href="irc://irc.freenode.net/#gnash">the #gnash channel on
 125 irc.freenode.net IRC server</a>.</p>
 126 </div>
 127       <div class="tags">
 128
 129
 130         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia</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>.
 131
 132
 133       </div>
 134     </div>
 135     <div class="padding"></div>
 136
 137     <div class="entry">
 138       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html">Install hardware dependent packages using tasksel (Isenkram 0.7)</a></div>
 139       <div class="date">23rd April 2014</div>
 140       <div class="body"><p>It would be nice if it was easier in Debian to get all the hardware
 141 related packages relevant for the computer installed automatically.
 142 So I implemented one, using
 143 <a href="http://packages.qa.debian.org/isenkram">my Isenkram
 144 package</a>.  To use it, install the tasksel and isenkram packages and
 145 run tasksel as user root.  You should be presented with a new option,
 146 "Hardware specific packages (autodetected by isenkram)".  When you
 147 select it, tasksel will install the packages isenkram claim is fit for
 148 the current hardware, hot pluggable or not.<p>
 149
 150 <p>The implementation is in two files, one is the tasksel menu entry
 151 description, and the other is the script used to extract the list of
 152 packages to install.  The first part is in
 153 <tt>/usr/share/tasksel/descs/isenkram.desc</tt> and look like
 154 this:</p>
 155
 156 <p><blockquote><pre>
 157 Task: isenkram
 158 Section: hardware
 159 Description: Hardware specific packages (autodetected by isenkram)
 160  Based on the detected hardware various hardware specific packages are
 161  proposed.
 162 Test-new-install: mark show
 163 Relevance: 8
 164 Packages: for-current-hardware
 165 </pre></blockquote></p>
 166
 167 <p>The second part is in
 168 <tt>/usr/lib/tasksel/packages/for-current-hardware</tt> and look like
 169 this:</p>
 170
 171 <p><blockquote><pre>
 172 #!/bin/sh
 173 #
 174 (
 175     isenkram-lookup
 176     isenkram-autoinstall-firmware -l
 177 ) | sort -u
 178 </pre></blockquote></p>
 179
 180 <p>All in all, a very short and simple implementation making it
 181 trivial to install the hardware dependent package we all may want to
 182 have installed on our machines.  I've not been able to find a way to
 183 get tasksel to tell you exactly which packages it plan to install
 184 before doing the installation.  So if you are curious or careful,
 185 check the output from the isenkram-* command line tools first.</p>
 186
 187 <p>The information about which packages are handling which hardware is
 188 fetched either from the isenkram package itself in
 189 /usr/share/isenkram/, from git.debian.org or from the APT package
 190 database (using the Modaliases header).  The APT package database
 191 parsing have caused a nasty resource leak in the isenkram daemon (bugs
 192 <a href="http://bugs.debian.org/719837">#719837</a> and
 193 <a href="http://bugs.debian.org/730704">#730704</a>).  The cause is in
 194 the python-apt code (bug
 195 <a href="http://bugs.debian.org/745487">#745487</a>), but using a
 196 workaround I was able to get rid of the file descriptor leak and
 197 reduce the memory leak from ~30 MiB per hardware detection down to
 198 around 2 MiB per hardware detection.  It should make the desktop
 199 daemon a lot more useful.  The fix is in version 0.7 uploaded to
 200 unstable today.</p>
 201
 202 <p>I believe the current way of mapping hardware to packages in
 203 Isenkram is is a good draft, but in the future I expect isenkram to
 204 use the AppStream data source for this.  A proposal for getting proper
 205 AppStream support into Debian is floating around as
 206 <a href="https://wiki.debian.org/DEP-11">DEP-11</a>, and
 207 <a href="https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive">GSoC
 208 project</a> will take place this summer to improve the situation.  I
 209 look forward to seeing the result, and welcome patches for isenkram to
 210 start using the information when it is ready.</p>
 211
 212 <p>If you want your package to map to some specific hardware, either
 213 add a "Xb-Modaliases" header to your control file like I did in
 214 <a href="http://packages.qa.debian.org/pymissile">the pymissile
 215 package</a> or submit a bug report with the details to the isenkram
 216 package.  See also
 217 <a href="http://people.skolelinux.org/pere/blog/tags/isenkram/">all my
 218 blog posts tagged isenkram</a> for details on the notation.  I expect
 219 the information will be migrated to AppStream eventually, but for the
 220 moment I got no better place to store it.</p>
 221 </div>
 222       <div class="tags">
 223
 224
 225         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>.
 226
 227
 228       </div>
 229     </div>
 230     <div class="padding"></div>
 231
 232     <div class="entry">
 233       <div class="title"><a href="http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html">FreedomBox milestone - all packages now in Debian Sid</a></div>
 234       <div class="date">15th April 2014</div>
 235       <div class="body"><p>The <a href="https://wiki.debian.org/FreedomBox">Freedombox
 236 project</a> is working on providing the software and hardware to make
 237 it easy for non-technical people to host their data and communication
 238 at home, and being able to communicate with their friends and family
 239 encrypted and away from prying eyes.  It is still going strong, and
 240 today a major mile stone was reached.</p>
 241
 242 <p>Today, the last of the packages currently used by the project to
 243 created the system images were accepted into Debian Unstable.  It was
 244 the freedombox-setup package, which is used to configure the images
 245 during build and on the first boot.  Now all one need to get going is
 246 the build code from the freedom-maker git repository and packages from
 247 Debian.  And once the freedombox-setup package enter testing, we can
 248 build everything directly from Debian. :)</p>
 249
 250 <p>Some key packages used by Freedombox are
 251 <a href="http://packages.qa.debian.org/freedombox-setup">freedombox-setup</a>,
 252 <a href="http://packages.qa.debian.org/plinth">plinth</a>,
 253 <a href="http://packages.qa.debian.org/pagekite">pagekite</a>,
 254 <a href="http://packages.qa.debian.org/tor">tor</a>,
 255 <a href="http://packages.qa.debian.org/privoxy">privoxy</a>,
 256 <a href="http://packages.qa.debian.org/owncloud">owncloud</a> and
 257 <a href="http://packages.qa.debian.org/dnsmasq">dnsmasq</a>.  There
 258 are plans to integrate more packages into the setup.  User
 259 documentation is maintained on the Debian wiki.  Please
 260 <a href="https://wiki.debian.org/FreedomBox/Manual/Jessie">check out
 261 the manual</a> and help us improve it.</p>
 262
 263 <p>To test for yourself and create boot images with the FreedomBox
 264 setup, run this on a Debian machine using a user with sudo rights to
 265 become root:</p>
 266
 267 <p><pre>
 268 sudo apt-get install git vmdebootstrap mercurial python-docutils \
 269   mktorrent extlinux virtualbox qemu-user-static binfmt-support \
 270   u-boot-tools
 271 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
 272   freedom-maker
 273 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
 274 </pre></p>
 275
 276 <p>Root access is needed to run debootstrap and mount loopback
 277 devices.  See the README in the freedom-maker git repo for more
 278 details on the build.  If you do not want all three images, trim the
 279 make line.  Note that the virtualbox-image target is not really
 280 virtualbox specific.  It create a x86 image usable in kvm, qemu,
 281 vmware and any other x86 virtual machine environment.  You might need
 282 the version of vmdebootstrap in Jessie to get the build working, as it
 283 include fixes for a race condition with kpartx.</p>
 284
 285 <p>If you instead want to install using a Debian CD and the preseed
 286 method, boot a Debian Wheezy ISO and use this boot argument to load
 287 the preseed values:</p>
 288
 289 <p><pre>
 290 url=<a href="http://www.reinholdtsen.name/freedombox/preseed-jessie.dat">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat</a>
 291 </pre></p>
 292
 293 <p>I have not tested it myself the last few weeks, so I do not know if
 294 it still work.</p>
 295
 296 <p>If you wonder how to help, one task you could look at is using
 297 systemd as the boot system.  It will become the default for Linux in
 298 Jessie, so we need to make sure it is usable on the Freedombox.  I did
 299 a simple test a few weeks ago, and noticed dnsmasq failed to start
 300 during boot when using systemd.  I suspect there are other problems
 301 too. :) To detect problems, there is a test suite included, which can
 302 be run from the plinth web interface.</p>
 303
 304 <p>Give it a go and let us know how it goes on the mailing list, and help
 305 us get the new release published. :) Please join us on
 306 <a href="irc://irc.debian.org:6667/%23freedombox">IRC (#freedombox on
 307 irc.debian.org)</a> and
 308 <a href="http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss">the
 309 mailing list</a> if you want to help make this vision come true.</p>
 310 </div>
 311       <div class="tags">
 312
 313
 314         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/sikkerhet">sikkerhet</a>, <a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance</a>, <a href="http://people.skolelinux.org/pere/blog/tags/web">web</a>.
 315
 316
 317       </div>
 318     </div>
 319     <div class="padding"></div>
 320
 321     <div class="entry">
 322       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Spr_kkoder_for_POSIX_locale_i_Norge.html">Språkkoder for POSIX locale i Norge</a></div>
 323       <div class="date">11th April 2014</div>
 324       <div class="body"><p>For 12 år siden, skrev jeg et lite notat om
 325 <a href="http://i18n.skolelinux.no/localekoder.txt">bruk av språkkoder
 326 i Norge</a>.  Jeg ble nettopp minnet på dette da jeg fikk spørsmål om
 327 notatet fortsatt var aktuelt, og tenkte det var greit å repetere hva
 328 som fortsatt gjelder.  Det jeg skrev da er fortsatt like aktuelt.</p>
 329
 330 <p>Når en velger språk i programmer på unix, så velger en blant mange
 331 språkkoder.  For språk i Norge anbefales følgende språkkoder (anbefalt
 332 locale i parantes):</p>
 333
 334 <p><dl>
 335 <dt>nb (nb_NO)</dt><dd>Bokmål i Norge</dd>
 336 <dt>nn (nn_NO)</dt><dd>Nynorsk i Norge</dd>
 337 <dt>se (se_NO)</dt><dd>Nordsamisk i Norge</dd>
 338 </dl></p>
 339
 340 <p>Alle programmer som bruker andre koder bør endres.</p>
 341
 342 <p>Språkkoden bør brukes når .po-filer navngis og installeres.  Dette
 343 er ikke det samme som locale-koden.  For Norsk Bokmål, så bør filene
 344 være navngitt nb.po, mens locale (LANG) bør være nb_NO.</p>
 345
 346 <p>Hvis vi ikke får standardisert de kodene i alle programmene med
 347 norske oversettelser, så er det umulig å gi LANG-variablen ett innhold
 348 som fungerer for alle programmer.</p>
 349
 350 <p>Språkkodene er de offisielle kodene fra ISO 639, og bruken av dem i
 351 forbindelse med POSIX localer er standardisert i RFC 3066 og ISO
 352 15897.  Denne anbefalingen er i tråd med de angitte standardene.</p>
 353
 354 <p>Følgende koder er eller har vært i bruk som locale-verdier for
 355 "norske" språk.  Disse bør unngås, og erstattes når de oppdages:</p>
 356
 357 <p><table>
 358 <tr><td>norwegian</td><td>-> nb_NO</td></tr>
 359 <tr><td>bokmål   </td><td>-> nb_NO</td></tr>
 360 <tr><td>bokmal   </td><td>-> nb_NO</td></tr>
 361 <tr><td>nynorsk  </td><td>-> nn_NO</td></tr>
 362 <tr><td>no       </td><td>-> nb_NO</td></tr>
 363 <tr><td>no_NO    </td><td>-> nb_NO</td></tr>
 364 <tr><td>no_NY    </td><td>-> nn_NO</td></tr>
 365 <tr><td>sme_NO   </td><td>-> se_NO</td></tr>
 366 </table></p>
 367
 368 <p>Merk at når det gjelder de samiske språkene, at se_NO i praksis
 369 henviser til nordsamisk i Norge, mens f.eks.  smj_NO henviser til
 370 lulesamisk.  Dette notatet er dog ikke ment å gi råd rundt samiske
 371 språkkoder, der gjør
 372 <a href="http://www.divvun.no/">Divvun-prosjektet</a> en bedre
 373 jobb.</p>
 374
 375 <p><strong>Referanser:</strong></p>
 376
 377 <ul>
 378
 379   <li><a href="http://www.rfc-base.org/rfc-3066.html">RFC 3066 - Tags
 380     for the Identification of Languages</a> (Erstatter RFC 1766)</li>
 381
 382   <li><a href="http://www.loc.gov/standards/iso639-2/langcodes.html">ISO
 383     639</a> - Codes for the Representation of Names of Languages</li>
 384
 385   <li><a href="http://std.dkuug.dk/jtc1/sc22/wg20/docs/n897-14652w25.pdf">ISO
 386     DTR 14652</a> - locale-standard Specification method for cultural
 387     conventions</li>
 388
 389   <li><a href="http://std.dkuug.dk/jtc1/sc22/wg20/docs/n610.pdf">ISO
 390     15897: Registration procedures for cultural elements (cultural
 391     registry)</a>,
 392     <a href="http://std.dkuug.dk/jtc1/sc22/wg20/docs/n849-15897wd6.pdf">(nytt
 393     draft)</a></li>
 394
 395   <li><a href="http://std.dkuug.dk/jtc1/sc22/wg20/">ISO/IEC
 396     JTC1/SC22/WG20</a> - Gruppen for i18n-standardisering i ISO</li>
 397
 398 <ul>
 399 </div>
 400       <div class="tags">
 401
 402
 403         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
 404
 405
 406       </div>
 407     </div>
 408     <div class="padding"></div>
 409
 410     <div class="entry">
 411       <div class="title"><a href="http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html">S3QL, a locally mounted cloud file system - nice free software</a></div>
 412       <div class="date"> 9th April 2014</div>
 413       <div class="body"><p>For a while now, I have been looking for a sensible offsite backup
 414 solution for use at home.  My requirements are simple, it must be
 415 cheap and locally encrypted (in other words, I keep the encryption
 416 keys, the storage provider do not have access to my private files).
 417 One idea me and my friends had many years ago, before the cloud
 418 storage providers showed up, was to use Google mail as storage,
 419 writing a Linux block device storing blocks as emails in the mail
 420 service provided by Google, and thus get heaps of free space.  On top
 421 of this one can add encryption, RAID and volume management to have
 422 lots of (fairly slow, I admit that) cheap and encrypted storage.  But
 423 I never found time to implement such system.  But the last few weeks I
 424 have looked at a system called
 425 <a href="https://bitbucket.org/nikratio/s3ql/">S3QL</a>, a locally
 426 mounted network backed file system with the features I need.</p>
 427
 428 <p>S3QL is a fuse file system with a local cache and cloud storage,
 429 handling several different storage providers, any with Amazon S3,
 430 Google Drive or OpenStack API.  There are heaps of such storage
 431 providers.  S3QL can also use a local directory as storage, which
 432 combined with sshfs allow for file storage on any ssh server.  S3QL
 433 include support for encryption, compression, de-duplication, snapshots
 434 and immutable file systems, allowing me to mount the remote storage as
 435 a local mount point, look at and use the files as if they were local,
 436 while the content is stored in the cloud as well.  This allow me to
 437 have a backup that should survive fire.  The file system can not be
 438 shared between several machines at the same time, as only one can
 439 mount it at the time, but any machine with the encryption key and
 440 access to the storage service can mount it if it is unmounted.</p>
 441
 442 <p>It is simple to use.  I'm using it on Debian Wheezy, where the
 443 package is included already.  So to get started, run <tt>apt-get
 444 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
 445 Greenqloud, after reading their nice recipe on
 446 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
 447 to use S3QL with their Amazon S3 service</a>, because I trust the laws
 448 in Iceland more than those in USA when it come to keeping my personal
 449 data safe and private, and thus would rather spend money on a company
 450 in Iceland.  Another nice recipe is available from the article
 451 <a href="http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage">S3QL
 452 Filesystem for HPC Storage</a> by Jeff Layton in the HPC section of
 453 Admin magazine.  When the provider is picked, figure out how to get
 454 the API key needed to connect to the storage API.  With Greencloud,
 455 the key did not show up until I had added payment details to my
 456 account.</p>
 457
 458 <p>Armed with the API access details, it is time to create the file
 459 system.  First, create a new bucket in the cloud.  This bucket is the
 460 file system storage area.  I picked a bucket name reflecting the
 461 machine that was going to store data there, but any name will do.
 462 I'll refer to it as <tt>bucket-name</tt> below.  In addition, one need
 463 the API login and password, and a locally created password.  Store it
 464 all in ~root/.s3ql/authinfo2 like this:
 465
 466 <p><blockquote><pre>
 467 [s3c]
 468 storage-url: s3c://s.greenqloud.com:443/bucket-name
 469 backend-login: API-login
 470 backend-password: API-password
 471 fs-passphrase: local-password
 472 </pre></blockquote></p>
 473
 474 <p>I create my local passphrase using <tt>pwget 50</tt> or similar,
 475 but any sensible way to create a fairly random password should do it.
 476 Armed with these details, it is now time to run mkfs, entering the API
 477 details and password to create it:</p>
 478
 479 <p><blockquote><pre>
 480 # mkdir -m 700 /var/lib/s3ql-cache
 481 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
 482   --ssl s3c://s.greenqloud.com:443/bucket-name
 483 Enter backend login:
 484 Enter backend password:
 485 Before using S3QL, make sure to read the user's guide, especially
 486 the 'Important Rules to Avoid Loosing Data' section.
 487 Enter encryption password:
 488 Confirm encryption password:
 489 Generating random encryption key...
 490 Creating metadata tables...
 491 Dumping metadata...
 492 ..objects..
 493 ..blocks..
 494 ..inodes..
 495 ..inode_blocks..
 496 ..symlink_targets..
 497 ..names..
 498 ..contents..
 499 ..ext_attributes..
 500 Compressing and uploading metadata...
 501 Wrote 0.00 MB of compressed metadata.
 502 # </pre></blockquote></p>
 503
 504 <p>The next step is mounting the file system to make the storage available.
 505
 506 <p><blockquote><pre>
 507 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
 508   --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
 509 Using 4 upload threads.
 510 Downloading and decompressing metadata...
 511 Reading metadata...
 512 ..objects..
 513 ..blocks..
 514 ..inodes..
 515 ..inode_blocks..
 516 ..symlink_targets..
 517 ..names..
 518 ..contents..
 519 ..ext_attributes..
 520 Mounting filesystem...
 521 # df -h /s3ql
 522 Filesystem                              Size  Used Avail Use% Mounted on
 523 s3c://s.greenqloud.com:443/bucket-name  1.0T     0  1.0T   0% /s3ql
 524 #
 525 </pre></blockquote></p>
 526
 527 <p>The file system is now ready for use.  I use rsync to store my
 528 backups in it, and as the metadata used by rsync is downloaded at
 529 mount time, no network traffic (and storage cost) is triggered by
 530 running rsync.  To unmount, one should not use the normal umount
 531 command, as this will not flush the cache to the cloud storage, but
 532 instead running the umount.s3ql command like this:
 533
 534 <p><blockquote><pre>
 535 # umount.s3ql /s3ql
 536 #
 537 </pre></blockquote></p>
 538
 539 <p>There is a fsck command available to check the file system and
 540 correct any problems detected.  This can be used if the local server
 541 crashes while the file system is mounted, to reset the "already
 542 mounted" flag.  This is what it look like when processing a working
 543 file system:</p>
 544
 545 <p><blockquote><pre>
 546 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
 547 Using cached metadata.
 548 File system seems clean, checking anyway.
 549 Checking DB integrity...
 550 Creating temporary extra indices...
 551 Checking lost+found...
 552 Checking cached objects...
 553 Checking names (refcounts)...
 554 Checking contents (names)...
 555 Checking contents (inodes)...
 556 Checking contents (parent inodes)...
 557 Checking objects (reference counts)...
 558 Checking objects (backend)...
 559 ..processed 5000 objects so far..
 560 ..processed 10000 objects so far..
 561 ..processed 15000 objects so far..
 562 Checking objects (sizes)...
 563 Checking blocks (referenced objects)...
 564 Checking blocks (refcounts)...
 565 Checking inode-block mapping (blocks)...
 566 Checking inode-block mapping (inodes)...
 567 Checking inodes (refcounts)...
 568 Checking inodes (sizes)...
 569 Checking extended attributes (names)...
 570 Checking extended attributes (inodes)...
 571 Checking symlinks (inodes)...
 572 Checking directory reachability...
 573 Checking unix conventions...
 574 Checking referential integrity...
 575 Dropping temporary indices...
 576 Backing up old metadata...
 577 Dumping metadata...
 578 ..objects..
 579 ..blocks..
 580 ..inodes..
 581 ..inode_blocks..
 582 ..symlink_targets..
 583 ..names..
 584 ..contents..
 585 ..ext_attributes..
 586 Compressing and uploading metadata...
 587 Wrote 0.89 MB of compressed metadata.
 588 #
 589 </pre></blockquote></p>
 590
 591 <p>Thanks to the cache, working on files that fit in the cache is very
 592 quick, about the same speed as local file access.  Uploading large
 593 amount of data is to me limited by the bandwidth out of and into my
 594 house.  Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
 595 which is very close to my upload speed, and downloading the same
 596 Debian installation ISO gave me 610 kiB/s, close to my download speed.
 597 Both were measured using <tt>dd</tt>.  So for me, the bottleneck is my
 598 network, not the file system code.  I do not know what a good cache
 599 size would be, but suspect that the cache should e larger than your
 600 working set.</p>
 601
 602 <p>I mentioned that only one machine can mount the file system at the
 603 time.  If another machine try, it is told that the file system is
 604 busy:</p>
 605
 606 <p><blockquote><pre>
 607 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
 608   --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
 609 Using 8 upload threads.
 610 Backend reports that fs is still mounted elsewhere, aborting.
 611 #
 612 </pre></blockquote></p>
 613
 614 <p>The file content is uploaded when the cache is full, while the
 615 metadata is uploaded once every 24 hour by default.  To ensure the
 616 file system content is flushed to the cloud, one can either umount the
 617 file system, or ask S3QL to flush the cache and metadata using
 618 s3qlctrl:
 619
 620 <p><blockquote><pre>
 621 # s3qlctrl upload-meta /s3ql
 622 # s3qlctrl flushcache /s3ql
 623 #
 624 </pre></blockquote></p>
 625
 626 <p>If you are curious about how much space your data uses in the
 627 cloud, and how much compression and deduplication cut down on the
 628 storage usage, you can use s3qlstat on the mounted file system to get
 629 a report:</p>
 630
 631 <p><blockquote><pre>
 632 # s3qlstat /s3ql
 633 Directory entries:    9141
 634 Inodes:               9143
 635 Data blocks:          8851
 636 Total data size:      22049.38 MB
 637 After de-duplication: 21955.46 MB (99.57% of total)
 638 After compression:    21877.28 MB (99.22% of total, 99.64% of de-duplicated)
 639 Database size:        2.39 MB (uncompressed)
 640 (some values do not take into account not-yet-uploaded dirty blocks in cache)
 641 #
 642 </pre></blockquote></p>
 643
 644 <p>I mentioned earlier that there are several possible suppliers of
 645 storage.  I did not try to locate them all, but am aware of at least
 646 <a href="https://www.greenqloud.com/">Greenqloud</a>,
 647 <a href="http://drive.google.com/">Google Drive</a>,
 648 <a href="http://aws.amazon.com/s3/">Amazon S3 web serivces</a>,
 649 <a href="http://www.rackspace.com/">Rackspace</a> and
 650 <a href="http://crowncloud.net/">Crowncloud</A>.  The latter even
 651 accept payment in Bitcoin.  Pick one that suit your need.  Some of
 652 them provide several GiB of free storage, but the prize models are
 653 quite different and you will have to figure out what suits you
 654 best.</p>
 655
 656 <p>While researching this blog post, I had a look at research papers
 657 and posters discussing the S3QL file system.  There are several, which
 658 told me that the file system is getting a critical check by the
 659 science community and increased my confidence in using it.  One nice
 660 poster is titled
 661 "<a href="http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf">An
 662 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
 663 Store and Transformative Parallel I/O Approach</a>" by Hsing-Bung
 664 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
 665 and Pamela Smith.  Please  have a look.</p>
 666
 667 <p>Given my problems with different file systems earlier, I decided to
 668 check out the mounted S3QL file system to see if it would be usable as
 669 a home directory (in other word, that it provided POSIX semantics when
 670 it come to locking and umask handling etc).  Running
 671 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
 672 test code to check file system semantics</a>, I was happy to discover that
 673 no error was found.  So the file system can be used for home
 674 directories, if one chooses to do so.</p>
 675
 676 <p>If you do not want a locally file system, and want something that
 677 work without the Linux fuse file system, I would like to mention the
 678 <a href="http://www.tarsnap.com/">Tarsnap service</a>, which also
 679 provide locally encrypted backup using a command line client.  It have
 680 a nicer access control system, where one can split out read and write
 681 access, allowing some systems to write to the backup and others to
 682 only read from it.</p>
 683
 684 <p>As usual, if you use Bitcoin and want to show your support of my
 685 activities, please send Bitcoin donations to my address
 686 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 687 </div>
 688       <div class="tags">
 689
 690
 691         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/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
 692
 693
 694       </div>
 695     </div>
 696     <div class="padding"></div>
 697
 698     <div class="entry">
 699       <div class="title"><a href="http://people.skolelinux.org/pere/blog/EU_domstolen_bekreftet_i_dag_at_datalagringsdirektivet_er_ulovlig.html">EU-domstolen bekreftet i dag at datalagringsdirektivet er ulovlig</a></div>
 700       <div class="date"> 8th April 2014</div>
 701       <div class="body"><p>I dag kom endelig avgjørelsen fra EU-domstolen om
 702 datalagringsdirektivet, som ikke overraskende ble dømt ulovlig og i
 703 strid med borgernes grunnleggende rettigheter.  Hvis du lurer på hva
 704 datalagringsdirektivet er for noe, så er det
 705 <a href="http://tv.nrk.no/program/koid75005313/tema-dine-digitale-spor-datalagringsdirektivet">en
 706 flott dokumentar tilgjengelig hos NRK</a> som jeg tidligere
 707 <a href="http://people.skolelinux.org/pere/blog/Dokumentaren_om_Datalagringsdirektivet_sendes_endelig_p__NRK.html">har
 708 anbefalt</a> alle å se.</p>
 709
 710 <p>Her er et liten knippe nyhetsoppslag om saken, og jeg regner med at
 711 det kommer flere ut over dagen.  Flere kan finnes
 712 <a href="http://www.mylder.no/?drill=datalagringsdirektivet&intern=1">via
 713 mylder</a>.</p>
 714
 715 <p><ul>
 716
 717 <li><a href="http://e24.no/digital/eu-domstolen-datalagringsdirektivet-er-ugyldig/22879592">EU-domstolen:
 718 Datalagringsdirektivet er ugyldig</a> - e24.no 2014-04-08
 719
 720 <li><a href="http://www.aftenposten.no/nyheter/iriks/EU-domstolen-Datalagringsdirektivet-er-ulovlig-7529032.html">EU-domstolen:
 721 Datalagringsdirektivet er ulovlig</a> - aftenposten.no 2014-04-08
 722
 723 <li><a href="http://www.aftenposten.no/nyheter/iriks/politikk/Krever-DLD-stopp-i-Norge-7530086.html">Krever
 724 DLD-stopp i Norge</a> - aftenposten.no 2014-04-08
 725
 726 <li><a href="http://www.p4.no/story.aspx?id=566431">Apenes: - En
 727 gledens dag</a> - p4.no 2014-04-08
 728
 729 <li><a href="http://www.nrk.no/norge/_-datalagringsdirektivet-er-ugyldig-1.11655929">EU-domstolen:
 730 – Datalagringsdirektivet er ugyldig</a> - nrk.no 2014-04-08</li>
 731
 732 <li><a href="http://www.vg.no/nyheter/utenriks/data-og-nett/eu-domstolen-datalagringsdirektivet-er-ugyldig/a/10130280/">EU-domstolen:
 733 Datalagringsdirektivet er ugyldig</a> - vg.no 2014-04-08</li>
 734
 735 <li><a href="http://www.dagbladet.no/2014/04/08/nyheter/innenriks/datalagringsdirektivet/personvern/32711646/">-
 736 Vi bør skrote hele datalagringsdirektivet</a> - dagbladet.no
 737 2014-04-08</li>
 738
 739 <li><a href="http://www.digi.no/928137/eu-domstolen-dld-er-ugyldig">EU-domstolen:
 740 DLD er ugyldig</a> - digi.no 2014-04-08</li>
 741
 742 <li><a href="http://www.irishtimes.com/business/sectors/technology/european-court-declares-data-retention-directive-invalid-1.1754150">European
 743 court declares data retention directive invalid</a> - irishtimes.com
 744 2014-04-08</li>
 745
 746 <li><a href="http://www.reuters.com/article/2014/04/08/us-eu-data-ruling-idUSBREA370F020140408?feedType=RSS">EU
 747 court rules against requirement to keep data of telecom users</a> -
 748 reuters.com 2014-04-08</li>
 749
 750 </ul>
 751 </p>
 752
 753 <p>Jeg synes det er veldig fint at nok en stemme slår fast at
 754 totalitær overvåkning av befolkningen er uakseptabelt, men det er
 755 fortsatt like viktig å beskytte privatsfæren som før, da de
 756 teknologiske mulighetene fortsatt finnes og utnyttes, og jeg tror
 757 innsats i prosjekter som
 758 <a href="https://wiki.debian.org/FreedomBox">Freedombox</a> og
 759 <a href="http://www.dugnadsnett.no/">Dugnadsnett</a> er viktigere enn
 760 noen gang.</p>
 761
 762 <p><strong>Update 2014-04-08 12:10</strong>: Kronerullingen for å
 763 stoppe datalagringsdirektivet i Norge gjøres hos foreningen
 764 <a href="http://www.digitaltpersonvern.no/">Digitalt Personvern</a>,
 765 som har samlet inn 843 215,- så langt men trenger nok mye mer hvis
 766
 767 ikke Høyre og Arbeiderpartiet bytter mening i saken.  Det var
 768 <a href="http://www.holderdeord.no/parliament-issues/48650">kun
 769 partinene Høyre og Arbeiderpartiet</a> som stemte for
 770 Datalagringsdirektivet, og en av dem må bytte mening for at det skal
 771 bli flertall mot i Stortinget.  Se mer om saken
 772 <a href="http://www.holderdeord.no/issues/69-innfore-datalagringsdirektivet">Holder
 773 de ord</a>.</p>
 774 </div>
 775       <div class="tags">
 776
 777
 778         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/dld">dld</a>, <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/surveillance">surveillance</a>.
 779
 780
 781       </div>
 782     </div>
 783     <div class="padding"></div>
 784
 785     <div class="entry">
 786       <div class="title"><a href="http://people.skolelinux.org/pere/blog/ReactOS_Windows_clone___nice_free_software.html">ReactOS Windows clone - nice free software</a></div>
 787       <div class="date"> 1st April 2014</div>
 788       <div class="body"><p>Microsoft have announced that Windows XP reaches its end of life
 789 2014-04-08, in 7 days.  But there are heaps of machines still running
 790 Windows XP, and depending on Windows XP to run their applications, and
 791 upgrading will be expensive, both when it comes to money and when it
 792 comes to the amount of effort needed to migrate from Windows XP to a
 793 new operating system.  Some obvious options (buy new a Windows
 794 machine, buy a MacOSX machine, install Linux on the existing machine)
 795 are already well known and covered elsewhere.  Most of them involve
 796 leaving the user applications installed on Windows XP behind and
 797 trying out replacements or updated versions. In this blog post I want
 798 to mention one strange bird that allow people to keep the hardware and
 799 the existing Windows XP applications and run them on a free software
 800 operating system that is Windows XP compatible.</p>
 801
 802 <p><a href="http://www.reactos.org/">ReactOS</a> is a free software
 803 operating system (GNU GPL licensed) working on providing a operating
 804 system that is binary compatible with Windows, able to run windows
 805 programs directly and to use Windows drivers for hardware directly.
 806 The project goal is for Windows user to keep their existing machines,
 807 drivers and software, and gain the advantages from user a operating
 808 system without usage limitations caused by non-free licensing.  It is
 809 a Windows clone running directly on the hardware, so quite different
 810 from the approach taken by <a href="http://www.winehq.org/">the Wine
 811 project</a>, which make it possible to run Windows binaries on
 812 Linux.</p>
 813
 814 <p>The ReactOS project share code with the Wine project, so most
 815 shared libraries available on Windows are already implemented already.
 816 There is also a software manager like the one we are used to on Linux,
 817 allowing the user to install free software applications with a simple
 818 click directly from the Internet.  Check out the
 819 <a href="http://www.reactos.org/screenshots">screen shots on the
 820 project web site</a> for an idea what it look like (it looks just like
 821 Windows before metro).</p>
 822
 823 <p>I do not use ReactOS myself, preferring Linux and Unix like
 824 operating systems.  I've tested it, and it work fine in a virt-manager
 825 virtual machine.  The browser, minesweeper, notepad etc is working
 826 fine as far as I can tell.  Unfortunately, my main test application
 827 is the software included on a CD with the Lego Mindstorms NXT, which
 828 seem to install just fine from CD but fail to leave any binaries on
 829 the disk after the installation.  So no luck with that test software.
 830 No idea why, but hope someone else figure out and fix the problem.
 831 I've tried the ReactOS Live ISO on a physical machine, and it seemed
 832 to work just fine.  If you like Windows and want to keep running your
 833 old Windows binaries, check it out by
 834 <a href="http://www.reactos.org/download">downloading</a> the
 835 installation CD, the live CD or the preinstalled virtual machine
 836 image.</p>
 837 </div>
 838       <div class="tags">
 839
 840
 841         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos</a>.
 842
 843
 844       </div>
 845     </div>
 846     <div class="padding"></div>
 847
 848     <div class="entry">
 849       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Debian_Edu_interview__Roger_Marsal.html">Debian Edu interview: Roger Marsal</a></div>
 850       <div class="date">30th March 2014</div>
 851       <div class="body"><p><a href="http://www.skolelinux.org/">Debian Edu / Skolelinux</a>
 852 keep gaining new users.  Some weeks ago, a person showed up on IRC,
 853 <a href="irc://irc.debian.org/#debian-edu">#debian-edu</a>, with a
 854 wish to contribute, and I managed to get a interview with this great
 855 contributor Roger Marsal to learn more about his background.</p>
 856
 857 <p><strong>Who are you, and how do you spend your days?</strong></p>
 858
 859 <p>My name is Roger Marsal, I'm 27 years old (1986 generation) and I
 860 live in Barcelona, Spain. I've got a strong business background and I
 861 work as a patrimony manager and as a real estate agent.  Additionally,
 862 I've co-founded a British based tech company that is nowadays on the
 863 last development phase of a new social networking concept.</p>
 864
 865 <p>I'm a Linux enthusiast that started its journey with Ubuntu four years
 866 ago and have recently switched to Debian seeking rock solid stability
 867 and as a necessary step to gain expertise.</p>
 868
 869 <p>In a nutshell, I spend my days working and learning as much as I
 870 can to face both my job, entrepreneur project and feed my Linux
 871 hunger.</p>
 872
 873 <p><strong>How did you get in contact with the Skolelinux / Debian Edu
 874 project?</strong></p>
 875
 876 <p>I discovered the <a href="http://www.ltsp.org/">LTSP</a> advantages
 877 with "Ubuntu 12.04 alternate install" and after a year of use I
 878 started looking for an alternative.  Even though I highly value and
 879 respect the Ubuntu project, I thought it was necessary for me to
 880 change to a more robust and stable alternative.  As far as I was using
 881 Debian on my personal laptop I thought it would be fine to install
 882 Debian and configure an LTSP server myself.  Surprised, I discovered
 883 that the Debian project also supported a kind of Edubuntu equivalent,
 884 and after having some pain I obtained a Debian Edu network up and
 885 running.  I just loved it.</p>
 886
 887 <p><strong>What do you see as the advantages of Skolelinux / Debian
 888 Edu?</strong></p>
 889
 890 <p>I found a main advantage in that, once you know "the tips and
 891 tricks", a new installation just works out of the box. It's the most
 892 complete alternative I've found to create an LTSP network. All the
 893 other distributions seems to be made of plastic, Debian Edu seems to
 894 be made of steel.</p>
 895
 896 <p><strong>What do you see as the disadvantages of Skolelinux / Debian
 897 Edu?</strong></p>
 898
 899 <p>I found two main disadvantages.</p>
 900
 901 <p>I'm not an expert but I've got notions and I had to spent a considerable
 902 amount of time trying to bring up a standard network topology. I'm quite
 903 stubborn and I just worked until I did but I'm sure many people with few
 904 resources (not big schools, but academies for example) would have switched
 905 or dropped.</p>
 906
 907 <p>It's amazing how such a complex system like Debian Edu has achieved
 908 this out-of-the-box state. Even though tweaking without breaking gets
 909 more difficult, as more factors have to be considered. This can
 910 discourage many people too.</p>
 911
 912 <p><strong>Which free software do you use daily?</strong></p>
 913
 914 <p>I use Debian, Firefox, Okular, Inkscape, LibreOffice and
 915 Virtualbox.</p>
 916
 917
 918 <p><strong>Which strategy do you believe is the right one to use to
 919 get schools to use free software?</strong></p>
 920
 921 <p>I don't think there is a need for a particular strategy. The free
 922 attribute in both "freedom" and "no price" meanings is what will
 923 really bring free software to schools. In my experience I can think of
 924 the <a href="http://www.r-project.org/">"R" statistical language</a>; a
 925 few years a ago was an extremely nerd tool for university people.
 926 Today it's being increasingly used to teach statistics at many
 927 different level of studies.  I believe free and open software will
 928 increasingly gain popularity, but I'm sure schools will be one of the
 929 first scenarios where this will happen.</p>
 930 </div>
 931       <div class="tags">
 932
 933
 934         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju</a>.
 935
 936
 937       </div>
 938     </div>
 939     <div class="padding"></div>
 940
 941     <div class="entry">
 942       <div class="title"><a href="http://people.skolelinux.org/pere/blog/Dokumentaren_om_Datalagringsdirektivet_sendes_endelig_p__NRK.html">Dokumentaren om Datalagringsdirektivet sendes endelig på NRK</a></div>
 943       <div class="date">26th March 2014</div>
 944       <div class="body"><p><a href="http://www.nuug.no/">Foreningen NUUG</a> melder i natt at
 945 NRK nå har bestemt seg for
 946 <a href="http://www.nuug.no/news/NRK_viser_filmen_om_Datalagringsdirektivet_f_rste_gang_2014_03_31.shtml">når
 947 den norske dokumentarfilmen om datalagringsdirektivet skal
 948 sendes</a> (se <a href="http://www.imdb.com/title/tt2832844/">IMDB</a>
 949 for detaljer om filmen) . Første visning blir på NRK2 mandag
 950 2014-03-31 kl. 19:50, og deretter visninger onsdag 2014-04-02
 951 kl. 12:30, fredag 2014-04-04 kl. 19:40 og søndag 2014-04-06 kl. 15:10.
 952 Jeg har sett dokumentaren, og jeg anbefaler enhver å se den selv.  Som
 953 oppvarming mens vi venter anbefaler jeg Bjørn Stærks kronikk i
 954 Aftenposten fra i går,
 955 <a href="http://www.aftenposten.no/meninger/kronikker/Autoritar-gjokunge-7514915.html">Autoritær
 956 gjøkunge</a>, der han gir en grei skisse av hvor ille det står til med
 957 retten til privatliv og beskyttelsen av demokrati i Norge og resten
 958 verden, og helt riktig slår fast at det er vi i databransjen som
 959 sitter med nøkkelen til å gjøre noe med dette.  Jeg har involvert meg
 960 i prosjektene <a href="http://www.dugnadsnett.no/">dugnadsnett.no</a>
 961 og <a href="https://wiki.debian.org/FreedomBox">FreedomBox</a> for å
 962 forsøke å gjøre litt selv for å bedre situasjonen, men det er mye
 963 hardt arbeid fra mange flere enn meg som gjenstår før vi kan sies å ha
 964 gjenopprettet balansen.</p>
 965
 966 <p>Jeg regner med at nettutgaven dukker opp på
 967 <a href="http://tv.nrk.no/program/koid75005313/tema-dine-digitale-spor-datalagringsdirektivet">NRKs
 968 side om filmen om datalagringsdirektivet</a> om fem dager.  Hold et
 969 øye med siden, og tips venner og slekt om at de også bør se den.</p>
 970 </div>
 971       <div class="tags">
 972
 973
 974         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/dld">dld</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/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/surveillance">surveillance</a>.
 975
 976
 977       </div>
 978     </div>
 979     <div class="padding"></div>
 980
 981     <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>
 982     <div id="sidebar">
 983
 984
 985
 986 <h2>Archive</h2>
 987 <ul>
 988
 989 <li>2014
 990 <ul>
 991
 992 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 993
 994 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 995
 996 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
 997
 998 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
 999
1000 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1001
1002 </ul></li>
1003
1004 <li>2013
1005 <ul>
1006
1007 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1008
1009 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1010
1011 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1012
1013 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1014
1015 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1016
1017 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1018
1019 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1020
1021 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1022
1023 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1024
1025 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1026
1027 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1028
1029 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1030
1031 </ul></li>
1032
1033 <li>2012
1034 <ul>
1035
1036 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1037
1038 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1039
1040 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1041
1042 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1043
1044 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1045
1046 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1047
1048 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1049
1050 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1051
1052 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1053
1054 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1055
1056 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1057
1058 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1059
1060 </ul></li>
1061
1062 <li>2011
1063 <ul>
1064
1065 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1066
1067 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1068
1069 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1070
1071 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1072
1073 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1074
1075 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1076
1077 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1078
1079 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1080
1081 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1082
1083 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1084
1085 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1086
1087 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1088
1089 </ul></li>
1090
1091 <li>2010
1092 <ul>
1093
1094 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1095
1096 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1097
1098 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1099
1100 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1101
1102 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1103
1104 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1105
1106 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1107
1108 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1109
1110 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1111
1112 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1113
1114 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1115
1116 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1117
1118 </ul></li>
1119
1120 <li>2009
1121 <ul>
1122
1123 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1124
1125 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1126
1127 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1128
1129 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1130
1131 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1132
1133 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1134
1135 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1136
1137 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1138
1139 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1140
1141 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1142
1143 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1144
1145 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1146
1147 </ul></li>
1148
1149 <li>2008
1150 <ul>
1151
1152 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1153
1154 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1155
1156 </ul></li>
1157
1158 </ul>
1159
1160
1161
1162 <h2>Tags</h2>
1163 <ul>
1164
1165  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1166
1167  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1168
1169  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1170
1171  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1172
1173  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
1174
1175  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (14)</a></li>
1176
1177  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1178
1179  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1180
1181  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (98)</a></li>
1182
1183  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (146)</a></li>
1184
1185  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1186
1187  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
1188
1189  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (10)</a></li>
1190
1191  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1192
1193  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (247)</a></li>
1194
1195  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
1196
1197  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1198
1199  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (12)</a></li>
1200
1201  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (8)</a></li>
1202
1203  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
1204
1205  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (40)</a></li>
1206
1207  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (9)</a></li>
1208
1209  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (18)</a></li>
1210
1211  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1212
1213  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (7)</a></li>
1214
1215  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1216
1217  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1218
1219  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (27)</a></li>
1220
1221  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (245)</a></li>
1222
1223  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (162)</a></li>
1224
1225  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (11)</a></li>
1226
1227  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1228
1229  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (46)</a></li>
1230
1231  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (72)</a></li>
1232
1233  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1234
1235  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1236
1237  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1238
1239  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (2)</a></li>
1240
1241  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
1242
1243  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1244
1245  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
1246
1247  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1248
1249  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (40)</a></li>
1250
1251  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1252
1253  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
1254
1255  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (44)</a></li>
1256
1257  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
1258
1259  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
1260
1261  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (25)</a></li>
1262
1263  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (1)</a></li>
1264
1265  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1266
1267  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (41)</a></li>
1268
1269  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1270
1271  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (31)</a></li>
1272
1273 </ul>
1274
1275
1276     </div>
1277     <p style="text-align: right">
1278  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1279 </p>
1280
1281   </body>
1282 </html>