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