blog/tags/nice free software/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: Entries Tagged nice free software</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="nice free software.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     <h3>Entries tagged "nice free software".</h3>
  22
  23     <div class="entry">
  24       <div class="title">
  25         <a href="http://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html">Oolite, a life in space as vagabond and mercenary - nice free software</a>
  26       </div>
  27       <div class="date">
  28         11th December 2016
  29       </div>
  30       <div class="body">
  31         <p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2016-12-11-nice-oolite.png"/></p>
  32
  33 <p>In my early years, I played
  34 <a href="http://wiki.alioth.net/index.php/Classic_Elite">the epic game
  35 Elite</a> on my PC.  I spent many months trading and fighting in
  36 space, and reached the 'elite' fighting status before I moved on.  The
  37 original Elite game was available on Commodore 64 and the IBM PC
  38 edition I played had a 64 KB executable.  I am still impressed today
  39 that the authors managed to squeeze both a 3D engine and details about
  40 more than 2000 planet systems across 7 galaxies into a binary so
  41 small.</p>
  42
  43 <p>I have known about <a href="http://www.oolite.org/">the free
  44 software game Oolite inspired by Elite</a> for a while, but did not
  45 really have time to test it properly until a few days ago.  It was
  46 great to discover that my old knowledge about trading routes were
  47 still valid.  But my fighting and flying abilities were gone, so I had
  48 to retrain to be able to dock on a space station.  And I am still not
  49 able to make much resistance when I am attacked by pirates, so I
  50 bougth and mounted the most powerful laser in the rear to be able to
  51 put up at least some resistance while fleeing for my life. :)</p>
  52
  53 <p>When playing Elite in the late eighties, I had to discover
  54 everything on my own, and I had long lists of prices seen on different
  55 planets to be able to decide where to trade what.  This time I had the
  56 advantages of the
  57 <a href="http://wiki.alioth.net/index.php/Main_Page">Elite wiki</a>,
  58 where information about each planet is easily available with common
  59 price ranges and suggested trading routes.  This improved my ability
  60 to earn money and I have been able to earn enough to buy a lot of
  61 useful equipent in a few days.  I believe I originally played for
  62 months before I could get a docking computer, while now I could get it
  63 after less then a week.</p>
  64
  65 <p>If you like science fiction and dreamed of a life as a vagabond in
  66 space, you should try out Oolite.  It is available for Linux, MacOSX
  67 and Windows, and is included in Debian and derivatives since 2011.</p>
  68
  69 <p>As usual, if you use Bitcoin and want to show your support of my
  70 activities, please send Bitcoin donations to my address
  71 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
  72
  73       </div>
  74       <div class="tags">
  75
  76
  77         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>.
  78
  79
  80       </div>
  81     </div>
  82     <div class="padding"></div>
  83
  84     <div class="entry">
  85       <div class="title">
  86         <a href="http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html">Coz can help you find bottlenecks in multi-threaded software - nice free software</a>
  87       </div>
  88       <div class="date">
  89         11th August 2016
  90       </div>
  91       <div class="body">
  92         <p>This summer, I read a great article
  93 "<a href="https://www.usenix.org/publications/login/summer2016/curtsinger">coz:
  94 This Is the Profiler You're Looking For</a>" in USENIX ;login: about
  95 how to profile multi-threaded programs.  It presented a system for
  96 profiling software by running experiences in the running program,
  97 testing how run time performance is affected by "speeding up" parts of
  98 the code to various degrees compared to a normal run.  It does this by
  99 slowing down parallel threads while the "faster up" code is running
 100 and measure how this affect processing time.  The processing time is
 101 measured using probes inserted into the code, either using progress
 102 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END).  It
 103 can also measure unmodified code by measuring complete the program
 104 runtime and running the program several times instead.</p>
 105
 106 <p>The project and presentation was so inspiring that I would like to
 107 get the system into Debian.  I
 108 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708">created
 109 a WNPP request for it</a> and contacted upstream to try to make the
 110 system ready for Debian by sending patches.  The build process need to
 111 be changed a bit to avoid running 'git clone' to get dependencies, and
 112 to include the JavaScript web page used to visualize the collected
 113 profiling information included in the source package.
 114 But I expect that should work out fairly soon.</p>
 115
 116 <p>The way the system work is fairly simple.  To run an coz experiment
 117 on a binary with debug symbols available, start the program like this:
 118
 119 <p><blockquote><pre>
 120 coz run --- program-to-run
 121 </pre></blockquote></p>
 122
 123 <p>This will create a text file profile.coz with the instrumentation
 124 information.  To show what part of the code affect the performance
 125 most, use a web browser and either point it to
 126 <a href="http://plasma-umass.github.io/coz/">http://plasma-umass.github.io/coz/</a>
 127 or use the copy from git (in the gh-pages branch).  Check out this web
 128 site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like.  To make the
 129 profiling more useful you include &lt;coz.h&gt; and insert the
 130 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
 131 code, rebuild and run the profiler.  This allow coz to do more
 132 targeted experiments.</p>
 133
 134 <p>A video published by ACM
 135 <a href="https://www.youtube.com/watch?v=jE0V-p1odPg">presenting the
 136 Coz profiler</a> is available from Youtube.  There is also a paper
 137 from the 25th Symposium on Operating Systems Principles available
 138 titled
 139 <a href="https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger">Coz:
 140 finding code that counts with causal profiling</a>.</p>
 141
 142 <p><a href="https://github.com/plasma-umass/coz">The source code</a>
 143 for Coz is available from github.  It will only build with clang
 144 because it uses a
 145 <a href="https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606">C++
 146 feature missing in GCC</a>, but I've submitted
 147 <a href="https://github.com/plasma-umass/coz/pull/67">a patch to solve
 148 it</a> and hope it will be included in the upstream source soon.</p>
 149
 150 <p>Please get in touch if you, like me, would like to see this piece
 151 of software in Debian.  I would very much like some help with the
 152 packaging effort, as I lack the in depth knowledge on how to package
 153 C++ libraries.</p>
 154
 155       </div>
 156       <div class="tags">
 157
 158
 159         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>.
 160
 161
 162       </div>
 163     </div>
 164     <div class="padding"></div>
 165
 166     <div class="entry">
 167       <div class="title">
 168         <a href="http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html">Creepy, visualise geotagged social media information - nice free software</a>
 169       </div>
 170       <div class="date">
 171         24th January 2016
 172       </div>
 173       <div class="body">
 174         <p>Most people seem not to realise that every time they walk around
 175 with the computerised radio beacon known as a mobile phone their
 176 position is tracked by the phone company and often stored for a long
 177 time (like every time a SMS is received or sent).  And if their
 178 computerised radio beacon is capable of running programs (often called
 179 mobile apps) downloaded from the Internet, these programs are often
 180 also capable of tracking their location (if the app requested access
 181 during installation).  And when these programs send out information to
 182 central collection points, the location is often included, unless
 183 extra care is taken to not send the location.  The provided
 184 information is used by several entities, for good and bad (what is
 185 good and bad, depend on your point of view).  What is certain, is that
 186 the private sphere and the right to free movement is challenged and
 187 perhaps even eradicated for those announcing their location this way,
 188 when they share their whereabouts with private and public
 189 entities.</p>
 190
 191 <p align="center"><img width="70%" src="http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png"></p>
 192
 193 <p>The phone company logs provide a register of locations to check out
 194 when one want to figure out what the tracked person was doing.  It is
 195 unavailable for most of us, but provided to selected government
 196 officials, company staff, those illegally buying information from
 197 unfaithful servants and crackers stealing the information.  But the
 198 public information can be collected and analysed, and a free software
 199 tool to do so is called
 200 <a href="http://www.geocreepy.com/">Creepy or Cree.py</a>.  I
 201 discovered it when I read
 202 <a href="http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html">an
 203 article about Creepy</a> in the Norwegian newspaper Aftenposten i
 204 November 2014, and decided to check if it was available in Debian.
 205 The python program was in Debian, but
 206 <a href="https://tracker.debian.org/pkg/creepy">the version in
 207 Debian</a> was completely broken and practically unmaintained.  I
 208 uploaded a new version which did not work quite right, but did not
 209 have time to fix it then.  This Christmas I decided to finally try to
 210 get Creepy operational in Debian.  Now a fixed version is available in
 211 Debian unstable and testing, and almost all Debian specific patches
 212 are now included
 213 <a href="https://github.com/jkakavas/creepy">upstream</a>.</p>
 214
 215 <p>The Creepy program visualises geolocation information fetched from
 216 Twitter, Instagram, Flickr and Google+, and allow one to get a
 217 complete picture of every social media message posted recently in a
 218 given area, or track the movement of a given individual across all
 219 these services.  Earlier it was possible to use the search API of at
 220 least some of these services without identifying oneself, but these
 221 days it is impossible.  This mean that to use Creepy, you need to
 222 configure it to log in as yourself on these services, and provide
 223 information to them about your search interests.  This should be taken
 224 into account when using Creepy, as it will also share information
 225 about yourself with the services.</p>
 226
 227 <p>The picture above show the twitter messages sent from (or at least
 228 geotagged with a position from) the city centre of Oslo, the capital
 229 of Norway.  One useful way to use Creepy is to first look at
 230 information tagged with an area of interest, and next look at all the
 231 information provided by one or more individuals who was in the area.
 232 I tested it by checking out which celebrity provide their location in
 233 twitter messages by checkout out who sent twitter messages near a
 234 Norwegian TV station, and next could track their position over time,
 235 making it possible to locate their home and work place, among other
 236 things.  A similar technique have been
 237 <a href="http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl">used
 238 to locate Russian soldiers in Ukraine</a>, and it is both a powerful
 239 tool to discover lying governments, and a useful tool to help people
 240 understand the value of the private information they provide to the
 241 public.</p>
 242
 243 <p>The package is not trivial to backport to Debian Stable/Jessie, as
 244 it depend on several python modules currently missing in Jessie (at
 245 least python-instagram, python-flickrapi and
 246 python-requests-toolbelt).</p>
 247
 248 <p>(I have uploaded
 249 <a href="https://screenshots.debian.net/package/creepy">the image to
 250 screenshots.debian.net</a> and licensed it under the same terms as the
 251 Creepy program in Debian.)</p>
 252
 253       </div>
 254       <div class="tags">
 255
 256
 257         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>.
 258
 259
 260       </div>
 261     </div>
 262     <div class="padding"></div>
 263
 264     <div class="entry">
 265       <div class="title">
 266         <a href="http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html">OpenALPR, find car license plates in video streams - nice free software</a>
 267       </div>
 268       <div class="date">
 269         23rd December 2015
 270       </div>
 271       <div class="body">
 272         <p>When I was a kid, we used to collect "car numbers", as we used to
 273 call the car license plate numbers in those days.  I would write the
 274 numbers down in my little book and compare notes with the other kids
 275 to see how many region codes we had seen and if we had seen some
 276 exotic or special region codes and numbers.  It was a fun game to pass
 277 time, as we kids have plenty of it.</p>
 278
 279 <p>A few days I came across
 280 <a href="https://github.com/openalpr/openalpr">the OpenALPR
 281 project</a>, a free software project to automatically discover and
 282 report license plates in images and video streams, and provide the
 283 "car numbers" in a machine readable format.  I've been looking for
 284 such system for a while now, because I believe it is a bad idea that the
 285 <a href="https://en.wikipedia.org/wiki/Automatic_number_plate_recognition">automatic
 286 number plate recognition</a> tool only is available in the hands of
 287 the powerful, and want it to be available also for the powerless to
 288 even the score when it comes to surveillance and sousveillance.  I
 289 discovered the developer
 290 <a href="https://bugs.debian.org/747509">wanted to get the tool into
 291 Debian</a>, and as I too wanted it to be in Debian, I volunteered to
 292 help him get it into shape to get the package uploaded into the Debian
 293 archive.</p>
 294
 295 <p>Today we finally managed to get the package into shape and uploaded
 296 it into Debian, where it currently
 297 <a href="https://ftp-master.debian.org//new/openalpr_2.2.1-1.html">waits
 298 in the NEW queue</a> for review by the Debian ftpmasters.</p>
 299
 300 <p>I guess you are wondering why on earth such tool would be useful
 301 for the common folks, ie those not running a large government
 302 surveillance system?  Well, I plan to put it in a computer on my bike
 303 and in my car, tracking the cars nearby and allowing me to be notified
 304 when number plates on my watch list are discovered.  Another use case
 305 was suggested by a friend of mine, who wanted to set it up at his home
 306 to open the car port automatically when it discovered the plate on his
 307 car.  When I mentioned it perhaps was a bit foolhardy to allow anyone
 308 capable of placing his license plate number of a piece of cardboard to
 309 open his car port, men replied that it was always unlocked anyway.  I
 310 guess for such use case it make sense.  I am sure there are other use
 311 cases too, for those with imagination and a vision.</p>
 312
 313 <p>If you want to build your own version of the Debian package, check
 314 out the upstream git source and symlink ./distros/debian to ./debian/
 315 before running "debuild" to build the source.  Or wait a bit until the
 316 package show up in unstable.</p>
 317
 318       </div>
 319       <div class="tags">
 320
 321
 322         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>.
 323
 324
 325       </div>
 326     </div>
 327     <div class="padding"></div>
 328
 329     <div class="entry">
 330       <div class="title">
 331         <a href="http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html">listadmin, the quick way to moderate mailman lists - nice free software</a>
 332       </div>
 333       <div class="date">
 334         22nd October 2014
 335       </div>
 336       <div class="body">
 337         <p>If you ever had to moderate a mailman list, like the ones on
 338 alioth.debian.org, you know the web interface is fairly slow to
 339 operate.  First you visit one web page, enter the moderation password
 340 and get a new page shown with a list of all the messages to moderate
 341 and various options for each email address.  This take a while for
 342 every list you moderate, and you need to do it regularly to do a good
 343 job as a list moderator.  But there is a quick alternative,
 344 <a href="http://heim.ifi.uio.no/kjetilho/hacks/#listadmin">the
 345 listadmin program</a>.  It allow you to check lists for new messages
 346 to moderate in a fraction of a second.  Here is a test run on two
 347 lists I recently took over:</p>
 348
 349 <p><blockquote><pre>
 350 % time listadmin xiph
 351 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
 352 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
 353
 354 real    0m1.709s
 355 user    0m0.232s
 356 sys     0m0.012s
 357 %
 358 </pre></blockquote></p>
 359
 360 <p>In 1.7 seconds I had checked two mailing lists and confirmed that
 361 there are no message in the moderation queue.  Every morning I
 362 currently moderate 68 mailman lists, and it normally take around two
 363 minutes.  When I took over the two pkg-xiph lists above a few days
 364 ago, there were 400 emails waiting in the moderator queue.  It took me
 365 less than 15 minutes to process them all using the listadmin
 366 program.</p>
 367
 368 <p>If you install
 369 <a href="https://tracker.debian.org/pkg/listadmin">the listadmin
 370 package</a> from Debian and create a file <tt>~/.listadmin.ini</tt>
 371 with content like this, the moderation task is a breeze:</p>
 372
 373 <p><blockquote><pre>
 374 username username@example.org
 375 spamlevel 23
 376 default discard
 377 discard_if_reason "Posting restricted to members only. Remove us from your mail list."
 378
 379 password secret
 380 adminurl https://{domain}/mailman/admindb/{list}
 381 mailman-list@lists.example.com
 382
 383 password hidden
 384 other-list@otherserver.example.org
 385 </pre></blockquote></p>
 386
 387 <p>There are other options to set as well.  Check the manual page to
 388 learn the details.</p>
 389
 390 <p>If you are forced to moderate lists on a mailman installation where
 391 the SSL certificate is self signed or not properly signed by a
 392 generally accepted signing authority, you can set a environment
 393 variable when calling listadmin to disable SSL verification:</p>
 394
 395 <p><blockquote><pre>
 396 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
 397 </pre></blockquote></p>
 398
 399 <p>If you want to moderate a subset of the lists you take care of, you
 400 can provide an argument to the listadmin script like I do in the
 401 initial screen dump (the xiph argument).  Using an argument, only
 402 lists matching the argument string will be processed.  This make it
 403 quick to accept messages if you notice the moderation request in your
 404 email.</p>
 405
 406 <p>Without the listadmin program, I would never be the moderator of 68
 407 mailing lists, as I simply do not have time to spend on that if the
 408 process was any slower. The listadmin program have saved me hours of
 409 time I could spend elsewhere over the years.  It truly is nice free
 410 software.</p>
 411
 412 <p>As usual, if you use Bitcoin and want to show your support of my
 413 activities, please send Bitcoin donations to my address
 414 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 415
 416 <p>Update 2014-10-27: Added missing 'username' statement in
 417 configuration example.  Also, I've been told that the
 418 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone.  Not
 419 sure why.</p>
 420
 421       </div>
 422       <div class="tags">
 423
 424
 425         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>.
 426
 427
 428       </div>
 429     </div>
 430     <div class="padding"></div>
 431
 432     <div class="entry">
 433       <div class="title">
 434         <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>
 435       </div>
 436       <div class="date">
 437          9th April 2014
 438       </div>
 439       <div class="body">
 440         <p>For a while now, I have been looking for a sensible offsite backup
 441 solution for use at home.  My requirements are simple, it must be
 442 cheap and locally encrypted (in other words, I keep the encryption
 443 keys, the storage provider do not have access to my private files).
 444 One idea me and my friends had many years ago, before the cloud
 445 storage providers showed up, was to use Google mail as storage,
 446 writing a Linux block device storing blocks as emails in the mail
 447 service provided by Google, and thus get heaps of free space.  On top
 448 of this one can add encryption, RAID and volume management to have
 449 lots of (fairly slow, I admit that) cheap and encrypted storage.  But
 450 I never found time to implement such system.  But the last few weeks I
 451 have looked at a system called
 452 <a href="https://bitbucket.org/nikratio/s3ql/">S3QL</a>, a locally
 453 mounted network backed file system with the features I need.</p>
 454
 455 <p>S3QL is a fuse file system with a local cache and cloud storage,
 456 handling several different storage providers, any with Amazon S3,
 457 Google Drive or OpenStack API.  There are heaps of such storage
 458 providers.  S3QL can also use a local directory as storage, which
 459 combined with sshfs allow for file storage on any ssh server.  S3QL
 460 include support for encryption, compression, de-duplication, snapshots
 461 and immutable file systems, allowing me to mount the remote storage as
 462 a local mount point, look at and use the files as if they were local,
 463 while the content is stored in the cloud as well.  This allow me to
 464 have a backup that should survive fire.  The file system can not be
 465 shared between several machines at the same time, as only one can
 466 mount it at the time, but any machine with the encryption key and
 467 access to the storage service can mount it if it is unmounted.</p>
 468
 469 <p>It is simple to use.  I'm using it on Debian Wheezy, where the
 470 package is included already.  So to get started, run <tt>apt-get
 471 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
 472 Greenqloud, after reading their nice recipe on
 473 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
 474 to use S3QL with their Amazon S3 service</a>, because I trust the laws
 475 in Iceland more than those in USA when it come to keeping my personal
 476 data safe and private, and thus would rather spend money on a company
 477 in Iceland.  Another nice recipe is available from the article
 478 <a href="http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage">S3QL
 479 Filesystem for HPC Storage</a> by Jeff Layton in the HPC section of
 480 Admin magazine.  When the provider is picked, figure out how to get
 481 the API key needed to connect to the storage API.  With Greencloud,
 482 the key did not show up until I had added payment details to my
 483 account.</p>
 484
 485 <p>Armed with the API access details, it is time to create the file
 486 system.  First, create a new bucket in the cloud.  This bucket is the
 487 file system storage area.  I picked a bucket name reflecting the
 488 machine that was going to store data there, but any name will do.
 489 I'll refer to it as <tt>bucket-name</tt> below.  In addition, one need
 490 the API login and password, and a locally created password.  Store it
 491 all in ~root/.s3ql/authinfo2 like this:
 492
 493 <p><blockquote><pre>
 494 [s3c]
 495 storage-url: s3c://s.greenqloud.com:443/bucket-name
 496 backend-login: API-login
 497 backend-password: API-password
 498 fs-passphrase: local-password
 499 </pre></blockquote></p>
 500
 501 <p>I create my local passphrase using <tt>pwget 50</tt> or similar,
 502 but any sensible way to create a fairly random password should do it.
 503 Armed with these details, it is now time to run mkfs, entering the API
 504 details and password to create it:</p>
 505
 506 <p><blockquote><pre>
 507 # mkdir -m 700 /var/lib/s3ql-cache
 508 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
 509   --ssl s3c://s.greenqloud.com:443/bucket-name
 510 Enter backend login:
 511 Enter backend password:
 512 Before using S3QL, make sure to read the user's guide, especially
 513 the 'Important Rules to Avoid Loosing Data' section.
 514 Enter encryption password:
 515 Confirm encryption password:
 516 Generating random encryption key...
 517 Creating metadata tables...
 518 Dumping metadata...
 519 ..objects..
 520 ..blocks..
 521 ..inodes..
 522 ..inode_blocks..
 523 ..symlink_targets..
 524 ..names..
 525 ..contents..
 526 ..ext_attributes..
 527 Compressing and uploading metadata...
 528 Wrote 0.00 MB of compressed metadata.
 529 # </pre></blockquote></p>
 530
 531 <p>The next step is mounting the file system to make the storage available.
 532
 533 <p><blockquote><pre>
 534 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
 535   --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
 536 Using 4 upload threads.
 537 Downloading and decompressing metadata...
 538 Reading metadata...
 539 ..objects..
 540 ..blocks..
 541 ..inodes..
 542 ..inode_blocks..
 543 ..symlink_targets..
 544 ..names..
 545 ..contents..
 546 ..ext_attributes..
 547 Mounting filesystem...
 548 # df -h /s3ql
 549 Filesystem                              Size  Used Avail Use% Mounted on
 550 s3c://s.greenqloud.com:443/bucket-name  1.0T     0  1.0T   0% /s3ql
 551 #
 552 </pre></blockquote></p>
 553
 554 <p>The file system is now ready for use.  I use rsync to store my
 555 backups in it, and as the metadata used by rsync is downloaded at
 556 mount time, no network traffic (and storage cost) is triggered by
 557 running rsync.  To unmount, one should not use the normal umount
 558 command, as this will not flush the cache to the cloud storage, but
 559 instead running the umount.s3ql command like this:
 560
 561 <p><blockquote><pre>
 562 # umount.s3ql /s3ql
 563 #
 564 </pre></blockquote></p>
 565
 566 <p>There is a fsck command available to check the file system and
 567 correct any problems detected.  This can be used if the local server
 568 crashes while the file system is mounted, to reset the "already
 569 mounted" flag.  This is what it look like when processing a working
 570 file system:</p>
 571
 572 <p><blockquote><pre>
 573 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
 574 Using cached metadata.
 575 File system seems clean, checking anyway.
 576 Checking DB integrity...
 577 Creating temporary extra indices...
 578 Checking lost+found...
 579 Checking cached objects...
 580 Checking names (refcounts)...
 581 Checking contents (names)...
 582 Checking contents (inodes)...
 583 Checking contents (parent inodes)...
 584 Checking objects (reference counts)...
 585 Checking objects (backend)...
 586 ..processed 5000 objects so far..
 587 ..processed 10000 objects so far..
 588 ..processed 15000 objects so far..
 589 Checking objects (sizes)...
 590 Checking blocks (referenced objects)...
 591 Checking blocks (refcounts)...
 592 Checking inode-block mapping (blocks)...
 593 Checking inode-block mapping (inodes)...
 594 Checking inodes (refcounts)...
 595 Checking inodes (sizes)...
 596 Checking extended attributes (names)...
 597 Checking extended attributes (inodes)...
 598 Checking symlinks (inodes)...
 599 Checking directory reachability...
 600 Checking unix conventions...
 601 Checking referential integrity...
 602 Dropping temporary indices...
 603 Backing up old metadata...
 604 Dumping metadata...
 605 ..objects..
 606 ..blocks..
 607 ..inodes..
 608 ..inode_blocks..
 609 ..symlink_targets..
 610 ..names..
 611 ..contents..
 612 ..ext_attributes..
 613 Compressing and uploading metadata...
 614 Wrote 0.89 MB of compressed metadata.
 615 #
 616 </pre></blockquote></p>
 617
 618 <p>Thanks to the cache, working on files that fit in the cache is very
 619 quick, about the same speed as local file access.  Uploading large
 620 amount of data is to me limited by the bandwidth out of and into my
 621 house.  Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
 622 which is very close to my upload speed, and downloading the same
 623 Debian installation ISO gave me 610 kiB/s, close to my download speed.
 624 Both were measured using <tt>dd</tt>.  So for me, the bottleneck is my
 625 network, not the file system code.  I do not know what a good cache
 626 size would be, but suspect that the cache should e larger than your
 627 working set.</p>
 628
 629 <p>I mentioned that only one machine can mount the file system at the
 630 time.  If another machine try, it is told that the file system is
 631 busy:</p>
 632
 633 <p><blockquote><pre>
 634 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
 635   --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
 636 Using 8 upload threads.
 637 Backend reports that fs is still mounted elsewhere, aborting.
 638 #
 639 </pre></blockquote></p>
 640
 641 <p>The file content is uploaded when the cache is full, while the
 642 metadata is uploaded once every 24 hour by default.  To ensure the
 643 file system content is flushed to the cloud, one can either umount the
 644 file system, or ask S3QL to flush the cache and metadata using
 645 s3qlctrl:
 646
 647 <p><blockquote><pre>
 648 # s3qlctrl upload-meta /s3ql
 649 # s3qlctrl flushcache /s3ql
 650 #
 651 </pre></blockquote></p>
 652
 653 <p>If you are curious about how much space your data uses in the
 654 cloud, and how much compression and deduplication cut down on the
 655 storage usage, you can use s3qlstat on the mounted file system to get
 656 a report:</p>
 657
 658 <p><blockquote><pre>
 659 # s3qlstat /s3ql
 660 Directory entries:    9141
 661 Inodes:               9143
 662 Data blocks:          8851
 663 Total data size:      22049.38 MB
 664 After de-duplication: 21955.46 MB (99.57% of total)
 665 After compression:    21877.28 MB (99.22% of total, 99.64% of de-duplicated)
 666 Database size:        2.39 MB (uncompressed)
 667 (some values do not take into account not-yet-uploaded dirty blocks in cache)
 668 #
 669 </pre></blockquote></p>
 670
 671 <p>I mentioned earlier that there are several possible suppliers of
 672 storage.  I did not try to locate them all, but am aware of at least
 673 <a href="https://www.greenqloud.com/">Greenqloud</a>,
 674 <a href="http://drive.google.com/">Google Drive</a>,
 675 <a href="http://aws.amazon.com/s3/">Amazon S3 web serivces</a>,
 676 <a href="http://www.rackspace.com/">Rackspace</a> and
 677 <a href="http://crowncloud.net/">Crowncloud</A>.  The latter even
 678 accept payment in Bitcoin.  Pick one that suit your need.  Some of
 679 them provide several GiB of free storage, but the prize models are
 680 quite different and you will have to figure out what suits you
 681 best.</p>
 682
 683 <p>While researching this blog post, I had a look at research papers
 684 and posters discussing the S3QL file system.  There are several, which
 685 told me that the file system is getting a critical check by the
 686 science community and increased my confidence in using it.  One nice
 687 poster is titled
 688 "<a href="http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf">An
 689 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
 690 Store and Transformative Parallel I/O Approach</a>" by Hsing-Bung
 691 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
 692 and Pamela Smith.  Please  have a look.</p>
 693
 694 <p>Given my problems with different file systems earlier, I decided to
 695 check out the mounted S3QL file system to see if it would be usable as
 696 a home directory (in other word, that it provided POSIX semantics when
 697 it come to locking and umask handling etc).  Running
 698 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
 699 test code to check file system semantics</a>, I was happy to discover that
 700 no error was found.  So the file system can be used for home
 701 directories, if one chooses to do so.</p>
 702
 703 <p>If you do not want a locally file system, and want something that
 704 work without the Linux fuse file system, I would like to mention the
 705 <a href="http://www.tarsnap.com/">Tarsnap service</a>, which also
 706 provide locally encrypted backup using a command line client.  It have
 707 a nicer access control system, where one can split out read and write
 708 access, allowing some systems to write to the backup and others to
 709 only read from it.</p>
 710
 711 <p>As usual, if you use Bitcoin and want to show your support of my
 712 activities, please send Bitcoin donations to my address
 713 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 714
 715       </div>
 716       <div class="tags">
 717
 718
 719         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>, <a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
 720
 721
 722       </div>
 723     </div>
 724     <div class="padding"></div>
 725
 726     <div class="entry">
 727       <div class="title">
 728         <a href="http://people.skolelinux.org/pere/blog/ReactOS_Windows_clone___nice_free_software.html">ReactOS Windows clone - nice free software</a>
 729       </div>
 730       <div class="date">
 731          1st April 2014
 732       </div>
 733       <div class="body">
 734         <p>Microsoft have announced that Windows XP reaches its end of life
 735 2014-04-08, in 7 days.  But there are heaps of machines still running
 736 Windows XP, and depending on Windows XP to run their applications, and
 737 upgrading will be expensive, both when it comes to money and when it
 738 comes to the amount of effort needed to migrate from Windows XP to a
 739 new operating system.  Some obvious options (buy new a Windows
 740 machine, buy a MacOSX machine, install Linux on the existing machine)
 741 are already well known and covered elsewhere.  Most of them involve
 742 leaving the user applications installed on Windows XP behind and
 743 trying out replacements or updated versions. In this blog post I want
 744 to mention one strange bird that allow people to keep the hardware and
 745 the existing Windows XP applications and run them on a free software
 746 operating system that is Windows XP compatible.</p>
 747
 748 <p><a href="http://www.reactos.org/">ReactOS</a> is a free software
 749 operating system (GNU GPL licensed) working on providing a operating
 750 system that is binary compatible with Windows, able to run windows
 751 programs directly and to use Windows drivers for hardware directly.
 752 The project goal is for Windows user to keep their existing machines,
 753 drivers and software, and gain the advantages from user a operating
 754 system without usage limitations caused by non-free licensing.  It is
 755 a Windows clone running directly on the hardware, so quite different
 756 from the approach taken by <a href="http://www.winehq.org/">the Wine
 757 project</a>, which make it possible to run Windows binaries on
 758 Linux.</p>
 759
 760 <p>The ReactOS project share code with the Wine project, so most
 761 shared libraries available on Windows are already implemented already.
 762 There is also a software manager like the one we are used to on Linux,
 763 allowing the user to install free software applications with a simple
 764 click directly from the Internet.  Check out the
 765 <a href="http://www.reactos.org/screenshots">screen shots on the
 766 project web site</a> for an idea what it look like (it looks just like
 767 Windows before metro).</p>
 768
 769 <p>I do not use ReactOS myself, preferring Linux and Unix like
 770 operating systems.  I've tested it, and it work fine in a virt-manager
 771 virtual machine.  The browser, minesweeper, notepad etc is working
 772 fine as far as I can tell.  Unfortunately, my main test application
 773 is the software included on a CD with the Lego Mindstorms NXT, which
 774 seem to install just fine from CD but fail to leave any binaries on
 775 the disk after the installation.  So no luck with that test software.
 776 No idea why, but hope someone else figure out and fix the problem.
 777 I've tried the ReactOS Live ISO on a physical machine, and it seemed
 778 to work just fine.  If you like Windows and want to keep running your
 779 old Windows binaries, check it out by
 780 <a href="http://www.reactos.org/download">downloading</a> the
 781 installation CD, the live CD or the preinstalled virtual machine
 782 image.</p>
 783
 784       </div>
 785       <div class="tags">
 786
 787
 788         Tags: <a href="http://people.skolelinux.org/pere/blog/tags/english">english</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software</a>, <a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos</a>.
 789
 790
 791       </div>
 792     </div>
 793     <div class="padding"></div>
 794
 795     <div class="entry">
 796       <div class="title">
 797         <a href="http://people.skolelinux.org/pere/blog/Video_DVD_reader_library___python_dvdvideo___nice_free_software.html">Video DVD reader library / python-dvdvideo - nice free software</a>
 798       </div>
 799       <div class="date">
 800         21st March 2014
 801       </div>
 802       <div class="body">
 803         <p>Keeping your DVD collection safe from scratches and curious
 804 children fingers while still having it available when you want to see a
 805 movie is not straight forward.  My preferred method at the moment is
 806 to store a full copy of the ISO on a hard drive, and use VLC, Popcorn
 807 Hour or other useful players to view the resulting file.  This way the
 808 subtitles and bonus material are still available and using the ISO is
 809 just like inserting the original DVD record in the DVD player.</p>
 810
 811 <p>Earlier I used dd for taking security copies, but it do not handle
 812 DVDs giving read errors (which are quite a few of them).  I've also
 813 tried using
 814 <a href="http://people.skolelinux.org/pere/blog/Ripping_problematic_DVDs_using_dvdbackup_and_genisoimage.html">dvdbackup
 815 and genisoimage</a>, but these days I use the marvellous python library
 816 and program
 817 <a href="http://bblank.thinkmo.de/blog/new-software-python-dvdvideo">python-dvdvideo</a>
 818 written by Bastian Blank.  It is
 819 <a href="http://packages.qa.debian.org/p/python-dvdvideo.html">in Debian
 820 already</a> and the binary package name is python3-dvdvideo. Instead
 821 of trying to read every block from the DVD, it parses the file
 822 structure and figure out which block on the DVD is actually in used,
 823 and only read those blocks from the DVD.  This work surprisingly well,
 824 and I have been able to almost backup my entire DVD collection using
 825 this method.</p>
 826
 827 <p>So far, python-dvdvideo have failed on between 10 and
 828 20 DVDs, which is a small fraction of my collection.  The most common
 829 problem is
 830 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720831">DVDs
 831 using UTF-16 instead of UTF-8 characters</a>, which according to
 832 Bastian is against the DVD specification (and seem to cause some
 833 players to fail too).  A rarer problem is what seem to be inconsistent
 834 DVD structures, as the python library
 835 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723079">claim
 836 there is a overlap between objects</a>.  An equally rare problem claim
 837 <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741878">some
 838 value is out of range</a>.  No idea what is going on there.  I wish I
 839 knew enough about the DVD format to fix these, to ensure my movie
 840 collection will stay with me in the future.</p>
 841
 842 <p>So, if you need to keep your DVDs safe, back them up using
 843 python-dvdvideo. :)</p>
 844
 845       </div>
 846       <div class="tags">
 847
 848
 849         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/nice free software">nice free software</a>, <a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett</a>, <a href="http://people.skolelinux.org/pere/blog/tags/video">video</a>.
 850
 851
 852       </div>
 853     </div>
 854     <div class="padding"></div>
 855
 856     <div class="entry">
 857       <div class="title">
 858         <a href="http://people.skolelinux.org/pere/blog/Free_Timetabling_Software___nice_free_software.html">Free Timetabling Software - nice free software</a>
 859       </div>
 860       <div class="date">
 861          7th July 2012
 862       </div>
 863       <div class="body">
 864         <p>Included in <a href="http://www.skolelinux.org/">Debian Edu /
 865 Skolelinux</a> is a large collection of end user and school specific
 866 software.  It is one of the packages not installed by default but
 867 provided in the Debian archive for schools to install if they want to,
 868 is a system to automatically plan the school time table using
 869 information about available teachers, classes and rooms, combined with
 870 the list of required courses and how many hours each topic should
 871 receive.  The software is
 872
 873 <a href="http://lalescu.ro/liviu/fet/">named FET</a>, and it provide a
 874 graphical user interface to input the required information, save the
 875 result in a fairly simple XML format, and generate time tables for
 876 both teachers and students.  It is available both for
 877 <a href="http://lalescu.ro/liviu/fet/download.html">Linux, MacOSX and
 878 Windows</a>.</p>
 879
 880 <p>This is <a href="http://lalescu.ro/liviu/fet/features.html">the
 881 feature list</a>, liftet from the project web site:</p>
 882
 883 <p><ul>
 884
 885   <li>FET is free software, licensed under the GNU GPL v2 or later.
 886     You can freely use, copy, modify and redistribute it </li>
 887
 888   <li>Localized to en_US (US English, default), ar (Arabic), ca
 889     (Catalan), da (Danish), de (German), el (Greek), es (Spanish), fa
 890     (Persian), fr (French), gl (Galician), he (Hebrew), hu
 891     (Hungarian), id (Indonesian), it (Italian), lt (Lithuanian), mk
 892     (Macedonian), ms (Malay), nl (Dutch), pl (Polish), pt_BR
 893     (Brazilian Portuguese), ro (Romanian), ru (Russian), si (Sinhala),
 894     sk (Slovak), sr (Serbian), tr (Turkish), uk (Ukrainian), uz
 895     (Uzbek) and vi (Vietnamese) (incompletely for some languages)
 896     </li>
 897
 898   <li>Fully automatic generation algorithm, allowing also
 899     semi-automatic or manual allocation</li>
 900
 901   <li>Platform independent implementation, allowing running on
 902     GNU/Linux, Windows, Mac and any system that Qt supports </li>
 903
 904   <li>Flexible modular XML format for the input file, allowing editing
 905     with an XML editor or by hand (besides FET interface)</li>
 906
 907   <li>Import/export from CSV format</li>
 908
 909   <li>The resulted timetables are exported into HTML, XML and CSV
 910     formats </li>
 911
 912   <li>Flexible students structure, organized into sets: years, groups
 913     and subgroups. FET allows overlapping years and groups and
 914     non-overlapping subgroups. You can even define individual students
 915     (as separate sets)</li>
 916
 917   <li>Each constraint has a weight percentage, from 0.0% to 100.0%
 918     (but some special constraints are allowed to have only 100% weight
 919     percentage)</li>
 920
 921   <li>Limits for the algorithm (all these limits can be increased on
 922     demand, as a custom version, because this would require a bit more
 923     memory):
 924     <ul>
 925       <li>Maximum total number of hours (periods) per day: 60</li>
 926       <li>Maximum number of working days per week: 35</li>
 927       <li>Maximum total number of teachers: 6000</li>
 928       <li>Maximum total number of sets of students: 30000</li>
 929       <li>Maximum total number of subjects: 6000</li>
 930       <li>Virtually unlimited number of activity tags</li>
 931       <li>Maximum number of activities: 30000</li>
 932       <li>Maximum number of rooms: 6000</li>
 933       <li>Maximum number of buildings: 6000</li>
 934       <li>Possibility of adding multiple teachers and
 935           students sets for each activity.  (it is possible
 936           also to have no teachers or no students sets for an
 937           activity)</li>
 938       <li>Virtually unlimited number of time constraints</li>
 939       <li>Virtually unlimited number of space constraints</li>
 940     </ul></li>
 941
 942   <li>A large and flexible palette of time constraints:
 943     <ul>
 944       <li>Break periods</li>
 945       <li>For teacher(s):
 946         <ul>
 947           <li>Not available periods</li>
 948           <li>Max/min days per week</li>
 949           <li>Max gaps per day/week</li>
 950           <li>Max hours daily/continuously</li>
 951           <li>Min hours daily</li>
 952           <li>Max hours daily/continuously with an activity tag</li>
 953
 954           <li>Respect working in an hourly interval a max number of
 955             days per week</li>
 956         </ul></li>
 957       <li>For students (sets):
 958         <ul>
 959           <li>Not available periods</li>
 960           <li>Begins early (specify max allowed beginnings at second hour)</li>
 961           <li>Max gaps per day/week</li>
 962           <li>Max hours daily/continuously</li>
 963           <li>Min hours daily</li>
 964           <li>Max hours daily/continuously with an activity tag</li>
 965
 966           <li>Respect working in an hourly interval a max number of
 967             days per week</li>
 968         </ul></li>
 969       <li>For an activity or a set of activities/subactivities:
 970         <ul>
 971           <li>A single preferred starting time</li>
 972           <li>A set of preferred starting times</li>
 973           <li>A set of preferred time slots</li>
 974           <li>Min/max days between them</li>
 975           <li>End(s) students day</li>
 976           <li>Same starting time/day/hour</li>
 977           <li>Occupy max time slots from selection (a complex and
 978             flexible constraint, useful in many situations)</li>
 979           <li>Consecutive, ordered, grouped (for 2 or 3 (sub)activities)</li>
 980           <li>Not overlapping</li>
 981           <li>Max simultaneous in selected time slots</li>
 982           <li>Min gaps between a set of (sub)activities</li>
 983         </ul></li>
 984     </ul></li>
 985
 986   <li>A large and flexible palette of space constraints:
 987     <ul>
 988       <li>Room not available periods</li>
 989       <li>For teacher(s):
 990         <ul>
 991           <li>Home room(s)</li>
 992           <li>Max building changes per day/week</li>
 993           <li>Min gaps between building changes</li>
 994         </ul>
 995       </li>
 996
 997       <li>For students (sets):
 998         <ul>
 999           <li>Home room(s)</li>
1000           <li>Max building changes per day/week</li>
1001           <li>Min gaps between building changes</li>
1002         </ul>
1003       </li>
1004       <li>Preferred room(s):
1005         <ul>
1006           <li>For a subject</li>
1007           <li>For an activity tag</li>
1008           <li>For a subject and an activity tag</li>
1009           <li>Individually for a (sub)activity</li>
1010         </ul>
1011       </li>
1012
1013       <li>For a set of activities:
1014         <ul>
1015           <li>Occupy a maximum number of different rooms</li>
1016         </ul>
1017       </li>
1018     </ul>
1019   </li>
1020 </ul></p>
1021
1022 <p>I have not used it myself, as I am not involved in time table
1023 planning at a school, but it seem to work fine when I test it.  If you
1024 need to set up your schools time table, and is tired of doing it
1025 manually, check it out.
1026
1027 A quick summary on how to use it can be found in
1028 <a href="http://marvelsoft.co.in/wp/2012/03/generate-timetable-for-state-cbse-icse-igcse-schools-free/">a
1029 blog post from MarvelSoft</a>.  If you find FET useful, please provide
1030 a recipe for the Debian Edu project in the
1031 <a href="http://wiki.debian.org/DebianEdu#Howtos">Debian Edu HowTo
1032 section</a>.</p>
1033
1034       </div>
1035       <div class="tags">
1036
1037
1038         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/nice free software">nice free software</a>.
1039
1040
1041       </div>
1042     </div>
1043     <div class="padding"></div>
1044
1045     <p style="text-align: right;"><a href="nice free software.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS Feed" width="36" height="14" /></a></p>
1046     <div id="sidebar">
1047
1048
1049
1050 <h2>Archive</h2>
1051 <ul>
1052
1053 <li>2017
1054 <ul>
1055
1056 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/01/">January (4)</a></li>
1057
1058 <li><a href="http://people.skolelinux.org/pere/blog/archive/2017/02/">February (1)</a></li>
1059
1060 </ul></li>
1061
1062 <li>2016
1063 <ul>
1064
1065 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/01/">January (3)</a></li>
1066
1067 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/02/">February (2)</a></li>
1068
1069 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/03/">March (3)</a></li>
1070
1071 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/04/">April (8)</a></li>
1072
1073 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/05/">May (8)</a></li>
1074
1075 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/06/">June (2)</a></li>
1076
1077 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/07/">July (2)</a></li>
1078
1079 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/08/">August (5)</a></li>
1080
1081 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/09/">September (2)</a></li>
1082
1083 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/10/">October (3)</a></li>
1084
1085 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/11/">November (8)</a></li>
1086
1087 <li><a href="http://people.skolelinux.org/pere/blog/archive/2016/12/">December (5)</a></li>
1088
1089 </ul></li>
1090
1091 <li>2015
1092 <ul>
1093
1094 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/01/">January (7)</a></li>
1095
1096 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/02/">February (6)</a></li>
1097
1098 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/03/">March (1)</a></li>
1099
1100 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/04/">April (4)</a></li>
1101
1102 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/05/">May (3)</a></li>
1103
1104 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/06/">June (4)</a></li>
1105
1106 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/07/">July (6)</a></li>
1107
1108 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/08/">August (2)</a></li>
1109
1110 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/09/">September (2)</a></li>
1111
1112 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/10/">October (9)</a></li>
1113
1114 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/11/">November (6)</a></li>
1115
1116 <li><a href="http://people.skolelinux.org/pere/blog/archive/2015/12/">December (3)</a></li>
1117
1118 </ul></li>
1119
1120 <li>2014
1121 <ul>
1122
1123 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
1124
1125 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
1126
1127 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
1128
1129 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
1130
1131 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
1132
1133 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
1134
1135 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
1136
1137 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
1138
1139 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
1140
1141 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
1142
1143 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (3)</a></li>
1144
1145 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/12/">December (5)</a></li>
1146
1147 </ul></li>
1148
1149 <li>2013
1150 <ul>
1151
1152 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
1153
1154 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
1155
1156 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
1157
1158 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
1159
1160 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
1161
1162 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
1163
1164 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
1165
1166 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
1167
1168 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
1169
1170 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
1171
1172 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
1173
1174 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
1175
1176 </ul></li>
1177
1178 <li>2012
1179 <ul>
1180
1181 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
1182
1183 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
1184
1185 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
1186
1187 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
1188
1189 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
1190
1191 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
1192
1193 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
1194
1195 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
1196
1197 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
1198
1199 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
1200
1201 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
1202
1203 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
1204
1205 </ul></li>
1206
1207 <li>2011
1208 <ul>
1209
1210 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
1211
1212 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
1213
1214 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
1215
1216 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
1217
1218 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
1219
1220 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
1221
1222 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
1223
1224 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
1225
1226 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
1227
1228 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
1229
1230 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
1231
1232 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
1233
1234 </ul></li>
1235
1236 <li>2010
1237 <ul>
1238
1239 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
1240
1241 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
1242
1243 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
1244
1245 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
1246
1247 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
1248
1249 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
1250
1251 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
1252
1253 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
1254
1255 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
1256
1257 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
1258
1259 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
1260
1261 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
1262
1263 </ul></li>
1264
1265 <li>2009
1266 <ul>
1267
1268 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
1269
1270 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
1271
1272 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
1273
1274 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
1275
1276 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
1277
1278 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
1279
1280 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
1281
1282 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
1283
1284 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
1285
1286 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
1287
1288 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
1289
1290 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
1291
1292 </ul></li>
1293
1294 <li>2008
1295 <ul>
1296
1297 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
1298
1299 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
1300
1301 </ul></li>
1302
1303 </ul>
1304
1305
1306
1307 <h2>Tags</h2>
1308 <ul>
1309
1310  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
1311
1312  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
1313
1314  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
1315
1316  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
1317
1318  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (9)</a></li>
1319
1320  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (16)</a></li>
1321
1322  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
1323
1324  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
1325
1326  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (145)</a></li>
1327
1328  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (158)</a></li>
1329
1330  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
1331
1332  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (16)</a></li>
1333
1334  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (23)</a></li>
1335
1336  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
1337
1338  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (339)</a></li>
1339
1340  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (23)</a></li>
1341
1342  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
1343
1344  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (29)</a></li>
1345
1346  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
1347
1348  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (18)</a></li>
1349
1350  <li><a href="http://people.skolelinux.org/pere/blog/tags/h264">h264 (20)</a></li>
1351
1352  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (42)</a></li>
1353
1354  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (15)</a></li>
1355
1356  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (20)</a></li>
1357
1358  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
1359
1360  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
1361
1362  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
1363
1364  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
1365
1366  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
1367
1368  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (39)</a></li>
1369
1370  <li><a href="http://people.skolelinux.org/pere/blog/tags/nice free software">nice free software (9)</a></li>
1371
1372  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (287)</a></li>
1373
1374  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (185)</a></li>
1375
1376  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (27)</a></li>
1377
1378  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
1379
1380  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (63)</a></li>
1381
1382  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (99)</a></li>
1383
1384  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
1385
1386  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
1387
1388  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
1389
1390  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
1391
1392  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (10)</a></li>
1393
1394  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
1395
1396  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (5)</a></li>
1397
1398  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
1399
1400  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (52)</a></li>
1401
1402  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
1403
1404  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (5)</a></li>
1405
1406  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (50)</a></li>
1407
1408  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (5)</a></li>
1409
1410  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (11)</a></li>
1411
1412  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (47)</a></li>
1413
1414  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
1415
1416  <li><a href="http://people.skolelinux.org/pere/blog/tags/usenix">usenix (2)</a></li>
1417
1418  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
1419
1420  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (59)</a></li>
1421
1422  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
1423
1424  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (40)</a></li>
1425
1426 </ul>
1427
1428
1429     </div>
1430     <p style="text-align: right">
1431  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
1432 </p>
1433
1434   </body>
1435 </html>