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