blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.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: S3QL, a locally mounted cloud file system - 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
  10
  11   </head>
  12   <body>
  13     <div class="title">
  14  <h1>
  15      <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  16
  17  </h1>
  18
  19 </div>
  20
  21
  22     <div class="entry">
  23       <div class="title">S3QL, a locally mounted cloud file system - nice free software</div>
  24       <div class="date"> 9th April 2014</div>
  25       <div class="body"><p>For a while now, I have been looking for a sensible offsite backup
  26 solution for use at home.  My requirements are simple, it must be
  27 cheap and locally encrypted (in other words, I keep the encryption
  28 keys, the storage provider do not have access to my private files).
  29 One idea me and my friends had many years ago, before the cloud
  30 storage providers showed up, was to use Google mail as storage,
  31 writing a Linux block device storing blocks as emails in the mail
  32 service provided by Google, and thus get heaps of free space.  On top
  33 of this one can add encryption, RAID and volume management to have
  34 lots of (fairly slow, I admit that) cheap and encrypted storage.  But
  35 I never found time to implement such system.  But the last few weeks I
  36 have looked at a system called
  37 <a href="https://bitbucket.org/nikratio/s3ql/">S3QL</a>, a locally
  38 mounted network backed file system with the features I need.</p>
  39
  40 <p>S3QL is a fuse file system with a local cache and cloud storage,
  41 handling several different storage providers, any with Amazon S3,
  42 Google Drive or OpenStack API.  There are heaps of such storage
  43 providers.  S3QL can also use a local directory as storage, which
  44 combined with sshfs allow for file storage on any ssh server.  S3QL
  45 include support for encryption, compression, de-duplication, snapshots
  46 and immutable file systems, allowing me to mount the remote storage as
  47 a local mount point, look at and use the files as if they were local,
  48 while the content is stored in the cloud as well.  This allow me to
  49 have a backup that should survive fire.  The file system can not be
  50 shared between several machines at the same time, as only one can
  51 mount it at the time, but any machine with the encryption key and
  52 access to the storage service can mount it if it is unmounted.</p>
  53
  54 <p>It is simple to use.  I'm using it on Debian Wheezy, where the
  55 package is included already.  So to get started, run <tt>apt-get
  56 install s3ql</tt>.  Next, pick a storage provider.  I ended up picking
  57 Greenqloud, after reading their nice recipe on
  58 <a href="https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy">how
  59 to use S3QL with their Amazon S3 service</a>, because I trust the laws
  60 in Iceland more than those in USA when it come to keeping my personal
  61 data safe and private, and thus would rather spend money on a company
  62 in Iceland.  Another nice recipe is available from the article
  63 <a href="http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage">S3QL
  64 Filesystem for HPC Storage</a> by Jeff Layton in the HPC section of
  65 Admin magazine.  When the provider is picked, figure out how to get
  66 the API key needed to connect to the storage API.  With Greencloud,
  67 the key did not show up until I had added payment details to my
  68 account.</p>
  69
  70 <p>Armed with the API access details, it is time to create the file
  71 system.  First, create a new bucket in the cloud.  This bucket is the
  72 file system storage area.  I picked a bucket name reflecting the
  73 machine that was going to store data there, but any name will do.
  74 I'll refer to it as <tt>bucket-name</tt> below.  In addition, one need
  75 the API login and password, and a locally created password.  Store it
  76 all in ~root/.s3ql/authinfo2 like this:
  77
  78 <p><blockquote><pre>
  79 [s3c]
  80 storage-url: s3c://s.greenqloud.com:443/bucket-name
  81 backend-login: API-login
  82 backend-password: API-password
  83 fs-passphrase: local-password
  84 </pre></blockquote></p>
  85
  86 <p>I create my local passphrase using <tt>pwget 50</tt> or similar,
  87 but any sensible way to create a fairly random password should do it.
  88 Armed with these details, it is now time to run mkfs, entering the API
  89 details and password to create it:</p>
  90
  91 <p><blockquote><pre>
  92 # mkdir -m 700 /var/lib/s3ql-cache
  93 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
  94   --ssl s3c://s.greenqloud.com:443/bucket-name
  95 Enter backend login:
  96 Enter backend password:
  97 Before using S3QL, make sure to read the user's guide, especially
  98 the 'Important Rules to Avoid Loosing Data' section.
  99 Enter encryption password:
 100 Confirm encryption password:
 101 Generating random encryption key...
 102 Creating metadata tables...
 103 Dumping metadata...
 104 ..objects..
 105 ..blocks..
 106 ..inodes..
 107 ..inode_blocks..
 108 ..symlink_targets..
 109 ..names..
 110 ..contents..
 111 ..ext_attributes..
 112 Compressing and uploading metadata...
 113 Wrote 0.00 MB of compressed metadata.
 114 # </pre></blockquote></p>
 115
 116 <p>The next step is mounting the file system to make the storage available.
 117
 118 <p><blockquote><pre>
 119 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
 120   --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
 121 Using 4 upload threads.
 122 Downloading and decompressing metadata...
 123 Reading metadata...
 124 ..objects..
 125 ..blocks..
 126 ..inodes..
 127 ..inode_blocks..
 128 ..symlink_targets..
 129 ..names..
 130 ..contents..
 131 ..ext_attributes..
 132 Mounting filesystem...
 133 # df -h /s3ql
 134 Filesystem                              Size  Used Avail Use% Mounted on
 135 s3c://s.greenqloud.com:443/bucket-name  1.0T     0  1.0T   0% /s3ql
 136 #
 137 </pre></blockquote></p>
 138
 139 <p>The file system is now ready for use.  I use rsync to store my
 140 backups in it, and as the metadata used by rsync is downloaded at
 141 mount time, no network traffic (and storage cost) is triggered by
 142 running rsync.  To unmount, one should not use the normal umount
 143 command, as this will not flush the cache to the cloud storage, but
 144 instead running the umount.s3ql command like this:
 145
 146 <p><blockquote><pre>
 147 # umount.s3ql /s3ql
 148 #
 149 </pre></blockquote></p>
 150
 151 <p>There is a fsck command available to check the file system and
 152 correct any problems detected.  This can be used if the local server
 153 crashes while the file system is mounted, to reset the "already
 154 mounted" flag.  This is what it look like when processing a working
 155 file system:</p>
 156
 157 <p><blockquote><pre>
 158 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
 159 Using cached metadata.
 160 File system seems clean, checking anyway.
 161 Checking DB integrity...
 162 Creating temporary extra indices...
 163 Checking lost+found...
 164 Checking cached objects...
 165 Checking names (refcounts)...
 166 Checking contents (names)...
 167 Checking contents (inodes)...
 168 Checking contents (parent inodes)...
 169 Checking objects (reference counts)...
 170 Checking objects (backend)...
 171 ..processed 5000 objects so far..
 172 ..processed 10000 objects so far..
 173 ..processed 15000 objects so far..
 174 Checking objects (sizes)...
 175 Checking blocks (referenced objects)...
 176 Checking blocks (refcounts)...
 177 Checking inode-block mapping (blocks)...
 178 Checking inode-block mapping (inodes)...
 179 Checking inodes (refcounts)...
 180 Checking inodes (sizes)...
 181 Checking extended attributes (names)...
 182 Checking extended attributes (inodes)...
 183 Checking symlinks (inodes)...
 184 Checking directory reachability...
 185 Checking unix conventions...
 186 Checking referential integrity...
 187 Dropping temporary indices...
 188 Backing up old metadata...
 189 Dumping metadata...
 190 ..objects..
 191 ..blocks..
 192 ..inodes..
 193 ..inode_blocks..
 194 ..symlink_targets..
 195 ..names..
 196 ..contents..
 197 ..ext_attributes..
 198 Compressing and uploading metadata...
 199 Wrote 0.89 MB of compressed metadata.
 200 #
 201 </pre></blockquote></p>
 202
 203 <p>Thanks to the cache, working on files that fit in the cache is very
 204 quick, about the same speed as local file access.  Uploading large
 205 amount of data is to me limited by the bandwidth out of and into my
 206 house.  Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
 207 which is very close to my upload speed, and downloading the same
 208 Debian installation ISO gave me 610 kiB/s, close to my download speed.
 209 Both were measured using <tt>dd</tt>.  So for me, the bottleneck is my
 210 network, not the file system code.  I do not know what a good cache
 211 size would be, but suspect that the cache should e larger than your
 212 working set.</p>
 213
 214 <p>I mentioned that only one machine can mount the file system at the
 215 time.  If another machine try, it is told that the file system is
 216 busy:</p>
 217
 218 <p><blockquote><pre>
 219 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
 220   --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
 221 Using 8 upload threads.
 222 Backend reports that fs is still mounted elsewhere, aborting.
 223 #
 224 </pre></blockquote></p>
 225
 226 <p>The file content is uploaded when the cache is full, while the
 227 metadata is uploaded once every 24 hour by default.  To ensure the
 228 file system content is flushed to the cloud, one can either umount the
 229 file system, or ask S3QL to flush the cache and metadata using
 230 s3qlctrl:
 231
 232 <p><blockquote><pre>
 233 # s3qlctrl upload-meta /s3ql
 234 # s3qlctrl flushcache /s3ql
 235 #
 236 </pre></blockquote></p>
 237
 238 <p>If you are curious about how much space your data uses in the
 239 cloud, and how much compression and deduplication cut down on the
 240 storage usage, you can use s3qlstat on the mounted file system to get
 241 a report:</p>
 242
 243 <p><blockquote><pre>
 244 # s3qlstat /s3ql
 245 Directory entries:    9141
 246 Inodes:               9143
 247 Data blocks:          8851
 248 Total data size:      22049.38 MB
 249 After de-duplication: 21955.46 MB (99.57% of total)
 250 After compression:    21877.28 MB (99.22% of total, 99.64% of de-duplicated)
 251 Database size:        2.39 MB (uncompressed)
 252 (some values do not take into account not-yet-uploaded dirty blocks in cache)
 253 #
 254 </pre></blockquote></p>
 255
 256 <p>I mentioned earlier that there are several possible suppliers of
 257 storage.  I did not try to locate them all, but am aware of at least
 258 <a href="https://www.greenqloud.com/">Greenqloud</a>,
 259 <a href="http://drive.google.com/">Google Drive</a>,
 260 <a href="http://aws.amazon.com/s3/">Amazon S3 web serivces</a>,
 261 <a href="http://www.rackspace.com/">Rackspace</a> and
 262 <a href="http://crowncloud.net/">Crowncloud</A>.  The latter even
 263 accept payment in Bitcoin.  Pick one that suit your need.  Some of
 264 them provide several GiB of free storage, but the prize models are
 265 quite different and you will have to figure out what suits you
 266 best.</p>
 267
 268 <p>While researching this blog post, I had a look at research papers
 269 and posters discussing the S3QL file system.  There are several, which
 270 told me that the file system is getting a critical check by the
 271 science community and increased my confidence in using it.  One nice
 272 poster is titled
 273 "<a href="http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf">An
 274 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
 275 Store and Transformative Parallel I/O Approach</a>" by Hsing-Bung
 276 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
 277 and Pamela Smith.  Please  have a look.</p>
 278
 279 <p>Given my problems with different file systems earlier, I decided to
 280 check out the mounted S3QL file system to see if it would be usable as
 281 a home directory (in other word, that it provided POSIX semantics when
 282 it come to locking and umask handling etc).  Running
 283 <a href="http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html">my
 284 test code to check file system semantics</a>, I was happy to discover that
 285 no error was found.  So the file system can be used for home
 286 directories, if one chooses to do so.</p>
 287
 288 <p>If you do not want a locally file system, and want something that
 289 work without the Linux fuse file system, I would like to mention the
 290 <a href="http://www.tarsnap.com/">Tarsnap service</a>, which also
 291 provide locally encrypted backup using a command line client.  It have
 292 a nicer access control system, where one can split out read and write
 293 access, allowing some systems to write to the backup and others to
 294 only read from it.</p>
 295
 296 <p>As usual, if you use Bitcoin and want to show your support of my
 297 activities, please send Bitcoin donations to my address
 298 <b><a href="bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&label=PetterReinholdtsenBlog">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b</a></b>.</p>
 299 </div>
 300
 301       <div class="tags">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>.</div>
 302
 303
 304     </div>
 305
 306
 307
 308
 309     <div id="sidebar">
 310
 311
 312
 313 <h2>Archive</h2>
 314 <ul>
 315
 316 <li>2014
 317 <ul>
 318
 319 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/01/">January (2)</a></li>
 320
 321 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/02/">February (3)</a></li>
 322
 323 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/03/">March (8)</a></li>
 324
 325 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/04/">April (7)</a></li>
 326
 327 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/05/">May (1)</a></li>
 328
 329 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/06/">June (2)</a></li>
 330
 331 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/07/">July (2)</a></li>
 332
 333 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/08/">August (2)</a></li>
 334
 335 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/09/">September (5)</a></li>
 336
 337 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/10/">October (6)</a></li>
 338
 339 <li><a href="http://people.skolelinux.org/pere/blog/archive/2014/11/">November (1)</a></li>
 340
 341 </ul></li>
 342
 343 <li>2013
 344 <ul>
 345
 346 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/01/">January (11)</a></li>
 347
 348 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/02/">February (9)</a></li>
 349
 350 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/03/">March (9)</a></li>
 351
 352 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/04/">April (6)</a></li>
 353
 354 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/05/">May (9)</a></li>
 355
 356 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/06/">June (10)</a></li>
 357
 358 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/07/">July (7)</a></li>
 359
 360 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/08/">August (3)</a></li>
 361
 362 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/09/">September (5)</a></li>
 363
 364 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/10/">October (7)</a></li>
 365
 366 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/11/">November (9)</a></li>
 367
 368 <li><a href="http://people.skolelinux.org/pere/blog/archive/2013/12/">December (3)</a></li>
 369
 370 </ul></li>
 371
 372 <li>2012
 373 <ul>
 374
 375 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/01/">January (7)</a></li>
 376
 377 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/02/">February (10)</a></li>
 378
 379 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/03/">March (17)</a></li>
 380
 381 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/04/">April (12)</a></li>
 382
 383 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/05/">May (12)</a></li>
 384
 385 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/06/">June (20)</a></li>
 386
 387 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/07/">July (17)</a></li>
 388
 389 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/08/">August (6)</a></li>
 390
 391 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/09/">September (9)</a></li>
 392
 393 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/10/">October (17)</a></li>
 394
 395 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/11/">November (10)</a></li>
 396
 397 <li><a href="http://people.skolelinux.org/pere/blog/archive/2012/12/">December (7)</a></li>
 398
 399 </ul></li>
 400
 401 <li>2011
 402 <ul>
 403
 404 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/01/">January (16)</a></li>
 405
 406 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/02/">February (6)</a></li>
 407
 408 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/03/">March (6)</a></li>
 409
 410 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/04/">April (7)</a></li>
 411
 412 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/05/">May (3)</a></li>
 413
 414 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/06/">June (2)</a></li>
 415
 416 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/07/">July (7)</a></li>
 417
 418 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/08/">August (6)</a></li>
 419
 420 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/09/">September (4)</a></li>
 421
 422 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/10/">October (2)</a></li>
 423
 424 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/11/">November (3)</a></li>
 425
 426 <li><a href="http://people.skolelinux.org/pere/blog/archive/2011/12/">December (1)</a></li>
 427
 428 </ul></li>
 429
 430 <li>2010
 431 <ul>
 432
 433 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 434
 435 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 436
 437 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 438
 439 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 440
 441 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 442
 443 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (14)</a></li>
 444
 445 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/07/">July (12)</a></li>
 446
 447 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/08/">August (13)</a></li>
 448
 449 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/09/">September (7)</a></li>
 450
 451 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/10/">October (9)</a></li>
 452
 453 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/11/">November (13)</a></li>
 454
 455 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/12/">December (12)</a></li>
 456
 457 </ul></li>
 458
 459 <li>2009
 460 <ul>
 461
 462 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 463
 464 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 465
 466 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 467
 468 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 469
 470 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 471
 472 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 473
 474 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 475
 476 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 477
 478 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 479
 480 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 481
 482 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 483
 484 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 485
 486 </ul></li>
 487
 488 <li>2008
 489 <ul>
 490
 491 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 492
 493 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 494
 495 </ul></li>
 496
 497 </ul>
 498
 499
 500
 501 <h2>Tags</h2>
 502 <ul>
 503
 504  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (13)</a></li>
 505
 506  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 507
 508  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 509
 510  <li><a href="http://people.skolelinux.org/pere/blog/tags/bankid">bankid (4)</a></li>
 511
 512  <li><a href="http://people.skolelinux.org/pere/blog/tags/bitcoin">bitcoin (8)</a></li>
 513
 514  <li><a href="http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (14)</a></li>
 515
 516  <li><a href="http://people.skolelinux.org/pere/blog/tags/bsa">bsa (2)</a></li>
 517
 518  <li><a href="http://people.skolelinux.org/pere/blog/tags/chrpath">chrpath (2)</a></li>
 519
 520  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (108)</a></li>
 521
 522  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (151)</a></li>
 523
 524  <li><a href="http://people.skolelinux.org/pere/blog/tags/digistan">digistan (10)</a></li>
 525
 526  <li><a href="http://people.skolelinux.org/pere/blog/tags/dld">dld (15)</a></li>
 527
 528  <li><a href="http://people.skolelinux.org/pere/blog/tags/docbook">docbook (12)</a></li>
 529
 530  <li><a href="http://people.skolelinux.org/pere/blog/tags/drivstoffpriser">drivstoffpriser (4)</a></li>
 531
 532  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (262)</a></li>
 533
 534  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (21)</a></li>
 535
 536  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (12)</a></li>
 537
 538  <li><a href="http://people.skolelinux.org/pere/blog/tags/freeculture">freeculture (13)</a></li>
 539
 540  <li><a href="http://people.skolelinux.org/pere/blog/tags/freedombox">freedombox (9)</a></li>
 541
 542  <li><a href="http://people.skolelinux.org/pere/blog/tags/frikanalen">frikanalen (11)</a></li>
 543
 544  <li><a href="http://people.skolelinux.org/pere/blog/tags/intervju">intervju (41)</a></li>
 545
 546  <li><a href="http://people.skolelinux.org/pere/blog/tags/isenkram">isenkram (10)</a></li>
 547
 548  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (19)</a></li>
 549
 550  <li><a href="http://people.skolelinux.org/pere/blog/tags/ldap">ldap (9)</a></li>
 551
 552  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (8)</a></li>
 553
 554  <li><a href="http://people.skolelinux.org/pere/blog/tags/lsdvd">lsdvd (2)</a></li>
 555
 556  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
 557
 558  <li><a href="http://people.skolelinux.org/pere/blog/tags/mesh network">mesh network (8)</a></li>
 559
 560  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (31)</a></li>
 561
 562  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (248)</a></li>
 563
 564  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (163)</a></li>
 565
 566  <li><a href="http://people.skolelinux.org/pere/blog/tags/offentlig innsyn">offentlig innsyn (11)</a></li>
 567
 568  <li><a href="http://people.skolelinux.org/pere/blog/tags/open311">open311 (2)</a></li>
 569
 570  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (48)</a></li>
 571
 572  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (76)</a></li>
 573
 574  <li><a href="http://people.skolelinux.org/pere/blog/tags/raid">raid (1)</a></li>
 575
 576  <li><a href="http://people.skolelinux.org/pere/blog/tags/reactos">reactos (1)</a></li>
 577
 578  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (11)</a></li>
 579
 580  <li><a href="http://people.skolelinux.org/pere/blog/tags/rfid">rfid (3)</a></li>
 581
 582  <li><a href="http://people.skolelinux.org/pere/blog/tags/robot">robot (9)</a></li>
 583
 584  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
 585
 586  <li><a href="http://people.skolelinux.org/pere/blog/tags/ruter">ruter (4)</a></li>
 587
 588  <li><a href="http://people.skolelinux.org/pere/blog/tags/scraperwiki">scraperwiki (2)</a></li>
 589
 590  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (41)</a></li>
 591
 592  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (4)</a></li>
 593
 594  <li><a href="http://people.skolelinux.org/pere/blog/tags/skepsis">skepsis (4)</a></li>
 595
 596  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (45)</a></li>
 597
 598  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (3)</a></li>
 599
 600  <li><a href="http://people.skolelinux.org/pere/blog/tags/stortinget">stortinget (9)</a></li>
 601
 602  <li><a href="http://people.skolelinux.org/pere/blog/tags/surveillance">surveillance (27)</a></li>
 603
 604  <li><a href="http://people.skolelinux.org/pere/blog/tags/sysadmin">sysadmin (2)</a></li>
 605
 606  <li><a href="http://people.skolelinux.org/pere/blog/tags/valg">valg (8)</a></li>
 607
 608  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (44)</a></li>
 609
 610  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (4)</a></li>
 611
 612  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (33)</a></li>
 613
 614 </ul>
 615
 616
 617     </div>
 618     <p style="text-align: right">
 619  Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v4.6</a>
 620 </p>
 621
 622   </body>
 623 </html>