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