blog/index.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
   2         "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
   3 <html>
   4  <head>
   5   <title>Petter Reinholdtsen</title>
   6   <link rel="stylesheet" type="text/css" media="screen" href="http://people.skolelinux.org/pere/blog/style.css">
   7   <link rel="alternate" title="RSS Feed" href="http://people.skolelinux.org/pere/blog/index.rss" type="application/rss+xml">
   8
   9  </head>
  10  <body>
  11
  12  <div class="title">
  13   <h1>
  14        <a href="http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen</a>
  15
  16   </h1>
  17
  18  </div>
  19
  20
  21
  22  <div class="entry">
  23   <div class="title"><a href="http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html">A manual for standards wars...</a></div>
  24   <div class="date">2010-06-06 14:15</div>
  25   <div class="body">
  26 <p>Via the
  27 <a href="http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html">blog
  28 of Rob Weir</a> I came across the very interesting essay named
  29 <a href="http://faculty.haas.berkeley.edu/shapiro/wars.pdf">The Art of
  30 Standards Wars</a> (PDF 25 pages).  I recommend it for everyone
  31 following the standards wars of today.</p>
  32 </div>
  33   <div class="tags">
  34
  35
  36
  37    Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <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/standard">standard</a>.
  38
  39   </div>
  40  </div>
  41  <div class="padding"></div>
  42
  43  <div class="entry">
  44   <div class="title"><a href="http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html">Sitesummary tip: Listing computer hardware models used at site</a></div>
  45   <div class="date">2010-06-03 12:05</div>
  46   <div class="body">
  47 <p>When using sitesummary at a site to track machines, it is possible
  48 to get a list of the machine types in use thanks to the DMI
  49 information extracted from each machine.  The script to do so is
  50 included in the sitesummary package, and here is example output from
  51 the Skolelinux build servers:</p>
  52
  53 <blockquote><pre>
  54 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
  55   vendor                    count
  56   Dell Computer Corporation     1
  57     PowerEdge 1750              1
  58   IBM                           1
  59     eserver xSeries 345 -[8670M1X]-     1
  60   Intel                         2
  61   [no-dmi-info]                 3
  62 maintainer:~#
  63 </pre></blockquote>
  64
  65 <p>The quality of the report depend on the quality of the DMI tables
  66 provided in each machine.  Here there are Intel machines without model
  67 information listed with Intel as vendor and mo model, and virtual Xen
  68 machines listed as [no-dmi-info].  One can add -l as a command line
  69 option to list the individual machines.</p>
  70
  71 <p>A larger list is
  72 <a href="http://narvikskolen.no/sitesummary/">available from the the
  73 city of Narvik</a>, which uses Skolelinux on all their shools and also
  74 provide the basic sitesummary report publicly.  In their report there
  75 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
  76 their machines, and as sitesummary is available in both distributions,
  77 it is trivial to get all of them to report to the same central
  78 collector.</p>
  79 </div>
  80   <div class="tags">
  81
  82
  83
  84    Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <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/sitesummary">sitesummary</a>.
  85
  86   </div>
  87  </div>
  88  <div class="padding"></div>
  89
  90  <div class="entry">
  91   <div class="title"><a href="http://people.skolelinux.org/pere/blog/Togsatsing_p___norsk__mot_sykkel.html">Togsatsing på norsk, mot sykkel</a></div>
  92   <div class="date">2010-06-02 23:45</div>
  93   <div class="body">
  94 <p>Det står dårlig til med toget når en finner på å la det
  95 <a href="http://www.aftenposten.no/nyheter/iriks/article3677060.ece">kappkjøre
  96 med sykkel</a>...  Jeg tror det trengs strukturendringer for å få
  97 fikset på togproblemene i Norge.</p>
  98
  99 <p>Mon tro hva toglinje mellom Narvik og Tromsø ville hatt slags
 100 effekt på området der?</p>
 101 </div>
 102   <div class="tags">
 103
 104
 105
 106    Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>.
 107
 108   </div>
 109  </div>
 110  <div class="padding"></div>
 111
 112  <div class="entry">
 113   <div class="title"><a href="http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html">KDM fail at boot with NVidia cards - and no one try to fix it?</a></div>
 114   <div class="date">2010-06-01 17:05</div>
 115   <div class="body">
 116 <p>It is strange to watch how a bug in Debian causing KDM to fail to
 117 start at boot when an NVidia video card is used is handled.  The
 118 problem seem to be that the nvidia X.org driver uses a long time to
 119 initialize, and this duration is longer than kdm is configured to
 120 wait.</p>
 121
 122 <p>I came across two bugs related to this issue,
 123 <a href="http://bugs.debian.org/583312">#583312</a> initially filed
 124 against initscripts and passed on to nvidia-glx when it became obvious
 125 that the nvidia drivers were involved, and
 126 <a href="http://bugs.debian.org/524751">#524751</a> initially filed against
 127 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.</p>
 128
 129 <p>To me, it seem that no-one is interested in actually solving the
 130 problem nvidia video card owners experience and make sure the Debian
 131 distribution work out of the box for these users.  The nvidia driver
 132 maintainers expect kdm to be set up to wait longer, while kdm expect
 133 the nvidia driver maintainers to fix the driver to start faster, and
 134 while they wait for each other I guess the users end up switching to a
 135 distribution that work for them.  I have no idea what the solution is,
 136 but I am pretty sure that waiting for each other is not it.</p>
 137
 138 <p>I wonder why we end up handling bugs this way.</p>
 139 </div>
 140   <div class="tags">
 141
 142
 143
 144    Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <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>.
 145
 146   </div>
 147  </div>
 148  <div class="padding"></div>
 149
 150  <div class="entry">
 151   <div class="title"><a href="http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html">Parallellized boot seem to hold up well in Debian/testing</a></div>
 152   <div class="date">2010-05-27 23:55</div>
 153   <div class="body">
 154 <p>A few days ago, parallel booting was enabled in Debian/testing.
 155 The feature seem to hold up pretty well, but three fairly serious
 156 issues are known and should be solved:
 157
 158 <p><ul>
 159
 160 <li>The wicd package seen to
 161 <a href="http://bugs.debian.org/508289">break NFS mounting</a> and
 162 <a href="http://bugs.debian.org/581586">network setup</a> when
 163 parallel booting is enabled.  No idea why, but the wicd maintainer
 164 seem to be on the case.</li>
 165
 166 <li>The nvidia X driver seem to
 167 <a href="http://bugs.debian.org/583312">have a race condition</a>
 168 triggered more easily when parallel booting is in effect.  The
 169 maintainer is on the case.</li>
 170
 171 <li>The sysv-rc package fail to properly enable dependency based boot
 172 sequencing (the shutdown is broken) when old file-rc users
 173 <a href="http://bugs.debian.org/575080">try to switch back</a> to
 174 sysv-rc.  One way to solve it would be for file-rc to create
 175 /etc/init.d/.legacy-bootordering, and another is to try to make
 176 sysv-rc more robust.  Will investigate some more and probably upload a
 177 workaround in sysv-rc to help those trying to move from file-rc to
 178 sysv-rc get a working shutdown.</li>
 179
 180 </ul></p>
 181
 182 <p>All in all not many surprising issues, and all of them seem
 183 solvable before Squeeze is released.  In addition to these there are
 184 some packages with bugs in their dependencies and run level settings,
 185 which I expect will be fixed in a reasonable time span.</p>
 186
 187 <p>If you report any problems with dependencies in init.d scripts to
 188 the BTS, please usertag the report to get it to show up at
 189 <a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org">the
 190 list of usertagged bugs related to this</a>.</p>
 191
 192 <p>Update: Correct bug number to file-rc issue.</p>
 193 </div>
 194   <div class="tags">
 195
 196
 197
 198    Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <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>.
 199
 200   </div>
 201  </div>
 202  <div class="padding"></div>
 203
 204  <div class="entry">
 205   <div class="title"><a href="http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html">More flexible firmware handling in debian-installer</a></div>
 206   <div class="date">2010-05-22 21:30</div>
 207   <div class="body">
 208 <p>After a long break from debian-installer development, I finally
 209 found time today to return to the project.  Having to spend less time
 210 working dependency based boot in debian, as it is almost complete now,
 211 definitely helped freeing some time.</p>
 212
 213 <p>A while back, I ran into a problem while working on Debian Edu.  We
 214 include some firmware packages on the Debian Edu CDs, those needed to
 215 get disk and network controllers working.  Without having these
 216 firmware packages available during installation, it is impossible to
 217 install Debian Edu on the given machine, and because our target group
 218 are non-technical people, asking them to provide firmware packages on
 219 an external medium is a support pain.  Initially, I expected it to be
 220 enough to include the firmware packages on the CD to get
 221 debian-installer to find and use them.  This proved to be wrong.
 222 Next, I hoped it was enough to symlink the relevant firmware packages
 223 to some useful location on the CD (tried /cdrom/ and
 224 /cdrom/firmware/).  This also proved to not work, and at this point I
 225 found time to look at the debian-installer code to figure out what was
 226 going to work.</p>
 227
 228 <p>The firmware loading code is in the hw-detect package, and a closer
 229 look revealed that it would only look for firmware packages outside
 230 the installation media, so the CD was never checked for firmware
 231 packages.  It would only check USB sticks, floppies and other
 232 "external" media devices.  Today I changed it to also look in the
 233 /cdrom/firmware/ directory on the mounted CD or DVD, which should
 234 solve the problem I ran into with Debian edu.  I also changed it to
 235 look in /firmware/, to make sure the installer also find firmware
 236 provided in the initrd when booting the installer via PXE, to allow us
 237 to provide the same feature in the PXE setup included in Debian
 238 Edu.</p>
 239
 240 <p>To make sure firmware deb packages with a license questions are not
 241 activated without asking if the license is accepted, I extended
 242 hw-detect to look for preinst scripts in the firmware packages, and
 243 run these before activating the firmware during installation.  The
 244 license question is asked using debconf in the preinst, so this should
 245 solve the issue for the firmware packages I have looked at so far.</p>
 246
 247 <p>If you want to discuss the details of these features, please
 248 contact us on debian-boot@lists.debian.org.</p>
 249 </div>
 250   <div class="tags">
 251
 252
 253
 254    Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <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>.
 255
 256   </div>
 257  </div>
 258  <div class="padding"></div>
 259
 260  <div class="entry">
 261   <div class="title"><a href="http://people.skolelinux.org/pere/blog/Magnetstripeinnhold_i_billetter_fra_Flytoget_og_Hurtigruten.html">Magnetstripeinnhold i billetter fra Flytoget og Hurtigruten</a></div>
 262   <div class="date">2010-05-21 16:00</div>
 263   <div class="body">
 264 <p>For en stund tilbake kjøpte jeg en magnetkortleser for å kunne
 265 titte på hva som er skrevet inn på magnetstripene til ulike kort.  Har
 266 ikke hatt tid til å analysere mange kort så langt, men tenkte jeg
 267 skulle dele innholdet på to kort med mine lesere.</p>
 268
 269 <p>For noen dager siden tok jeg flyet til Harstad og Hurtigruten til
 270 Bergen.  Flytoget fra Oslo S til flyplassen ga meg en billett med
 271 magnetstripe.  Påtrykket finner jeg følgende informasjon:</p>
 272
 273 <pre>
 274 Flytoget Airport Express Train
 275
 276 Fra - Til        : Oslo Sentralstasjon
 277 Kategori         : Voksen
 278 Pris             : Nok 170,00
 279 Herav mva. 8,00% : NOK 12,59
 280 Betaling         : Kontant
 281 Til - Fra        : Oslo Lufthavn
 282 Utstedt:         : 08.05.10
 283 Gyldig Fra-Til   : 08.05.10-07.11.10
 284 Billetttype      : Enkeltbillett
 285
 286 102-1015-100508-48382-01-08
 287 </pre>
 288
 289 <p>På selve magnetstripen er innholdet
 290 <tt>;E?+900120011=23250996541068112619257138248441708433322932704083389389062603279671261502492655?</tt>.
 291 Aner ikke hva innholdet representerer, og det er lite overlapp mellom
 292 det jeg ser trykket på billetten og det jeg ser av tegn i
 293 magnetstripen.  Håper det betyr at de bruker kryptografiske metoder
 294 for å gjøre det vanskelig å forfalske billetter.</p>
 295
 296 <p>Den andre billetten er fra Hurtigruten, der jeg mistenker at
 297 strekkoden på fronten er mer brukt enn magnetstripen (det var i hvert
 298 fall den biten vi stakk inn i dørlåsen).</p>
 299
 300 <p>Påtrykket forsiden er følgende:</p>
 301
 302 <pre>
 303 Romnummer 727
 304 Hurtigruten
 305 Midnatsol
 306 Reinholdtsen
 307 Petter
 308 Bookingno: SAX69   0742193
 309 Harstad-Bergen
 310 Dep: 09.05.2010 Arr: 12.05.2010
 311 Lugar fra Risøyhamn
 312 Kost: FRO=4
 313 </pre>
 314
 315 <p>På selve magnetstripen er innholdet
 316 <tt>;1316010007421930=00000000000000000000?+E?</tt>.  Heller ikke her
 317 ser jeg mye korrespondanse mellom påtrykk og magnetstripe.</p>
 318 </div>
 319   <div class="tags">
 320
 321
 322
 323    Tags: <a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk</a>, <a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug</a>, <a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet</a>.
 324
 325   </div>
 326  </div>
 327  <div class="padding"></div>
 328
 329  <div class="entry">
 330   <div class="title"><a href="http://people.skolelinux.org/pere/blog/Pieces_of_the_roaming_laptop_puzzle_in_Debian.html">Pieces of the roaming laptop puzzle in Debian</a></div>
 331   <div class="date">2010-05-19 19:00</div>
 332   <div class="body">
 333 <p>Today, the last piece of the puzzle for roaming laptops in Debian
 334 Edu finally entered the Debian archive.  Today, the new
 335 <a href="http://packages.qa.debian.org/libp/libpam-mklocaluser.html">libpam-mklocaluser</a>
 336 package was accepted.  Two days ago, two other pieces was accepted
 337 into unstable.  The
 338 <a href="http://packages.qa.debian.org/p/pam-python.html">pam-python</a>
 339 package needed by libpam-mklocaluser, and the
 340 <a href="http://packages.qa.debian.org/s/sssd.html">sssd</a> package
 341 passed NEW on Monday.  In addition, the
 342 <a href="http://packages.qa.debian.org/libp/libpam-ccreds.html">libpam-ccreds</a>
 343 package we need is in experimental (version 10-4) since Saturday, and
 344 hopefully will be moved to unstable soon.</p>
 345
 346 <p>This collection of packages allow for two different setups for
 347 roaming laptops.  The traditional setup would be using libpam-ccreds,
 348 nscd and libpam-mklocaluser with LDAP or Kerberos authentication,
 349 which should work out of the box if the configuration changes proposed
 350 for nscd in <a href="http://bugs.debian.org/485282">BTS report
 351 #485282</a> is implemented.  The alternative setup is to use sssd with
 352 libpam-mklocaluser to connect to LDAP or Kerberos and let sssd take
 353 care of the caching of passwords and group information.</p>
 354
 355 <p>I have so far been unable to get sssd to work with the LDAP server
 356 at the University, but suspect the issue is some SSL/GnuTLS related
 357 problem with the server certificate.  I plan to update the Debian
 358 package to version 1.2, which is scheduled for next week, and hope to
 359 find time to make sure the next release will include both the
 360 Debian/Ubuntu specific patches.  Upstream is friendly and responsive,
 361 and I am sure we will find a good solution.</p>
 362
 363 <p>The idea is to set up the roaming laptops to authenticate using
 364 LDAP or Kerberos and create a local user with home directory in /home/
 365 when a usre in LDAP logs in via KDM or GDM for the first time, and
 366 cache the password for offline checking, as well as caching group
 367 memberhips and other relevant LDAP information.  The
 368 libpam-mklocaluser package was created to make sure the local home
 369 directory is in /home/, instead of /site/server/directory/ which would
 370 be the home directory if pam_mkhomedir was used.  To avoid confusion
 371 with support requests and configuration, we do not want local laptops
 372 to have users in a path that is used for the same users home directory
 373 on the home directory servers.</p>
 374
 375 <p>One annoying problem with gdm is that it do not show the PAM
 376 message passed to the user from libpam-mklocaluser when the local user
 377 is created.  Instead gdm simply reject the login with some generic
 378 message.  The message is shown in kdm, ssh and login, so I guess it is
 379 a bug in gdm.  Have not investigated if there is some other message
 380 type that can be used instead to get gdm to also show the message.</p>
 381
 382 <p>If you want to help out with implementing this for Debian Edu,
 383 please contact us on debian-edu@lists.debian.org.</p>
 384 </div>
 385   <div class="tags">
 386
 387
 388
 389    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/nuug">nuug</a>.
 390
 391   </div>
 392  </div>
 393  <div class="padding"></div>
 394
 395  <div class="entry">
 396   <div class="title"><a href="http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html">Parallellized boot is now the default in Debian/unstable</a></div>
 397   <div class="date">2010-05-14 22:40</div>
 398   <div class="body">
 399 <p>Since this evening, parallel booting is the default in
 400 Debian/unstable for machines using dependency based boot sequencing.
 401 Apparently the testing of concurrent booting has been wider than
 402 expected, if I am to believe the
 403 <a href="http://lists.debian.org/debian-devel/2010/05/msg00122.html">input
 404 on debian-devel@</a>, and I concluded a few days ago to move forward
 405 with the feature this weekend, to give us some time to detect any
 406 remaining problems before Squeeze is frozen.  If serious problems are
 407 detected, it is simple to change the default back to sequential boot.
 408 The upload of the new sysvinit package also activate a new upstream
 409 version.</p>
 410
 411 More information about
 412 <a href="http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot">dependency
 413 based boot sequencing</a> is available from the Debian wiki.  It is
 414 currently possible to disable parallel booting when one run into
 415 problems caused by it, by adding this line to /etc/default/rcS:</p>
 416
 417 <blockquote><pre>
 418 CONCURRENCY=none
 419 </pre></blockquote>
 420
 421 <p>If you report any problems with dependencies in init.d scripts to
 422 the BTS, please usertag the report to get it to show up at
 423 <a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org">the
 424 list of usertagged bugs related to this</a>.</p>
 425 </div>
 426   <div class="tags">
 427
 428
 429
 430    Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <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>.
 431
 432   </div>
 433  </div>
 434  <div class="padding"></div>
 435
 436  <div class="entry">
 437   <div class="title"><a href="http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html">Sitesummary tip: Listing MAC address of all clients</a></div>
 438   <div class="date">2010-05-14 21:10</div>
 439   <div class="body">
 440 <p>In the recent Debian Edu versions, the
 441 <a href="http://wiki.debian.org/DebianEdu/HowTo/SiteSummary">sitesummary
 442 system</a> is used to keep track of the machines in the school
 443 network.  Each machine will automatically report its status to the
 444 central server after boot and once per night.  The network setup is
 445 also reported, and using this information it is possible to get the
 446 MAC address of all network interfaces in the machines.  This is useful
 447 to update the DHCP configuration.</p>
 448
 449 <p>To give some idea how to use sitesummary, here is a one-liner to
 450 ist all MAC addresses of all machines reporting to sitesummary.  Run
 451 this on the collector host:</p>
 452
 453 <blockquote><pre>
 454 perl -MSiteSummary -e 'for_all_hosts(sub { print join(" ", get_macaddresses(shift)), "\n"; });'
 455 </pre></blockquote>
 456
 457 <p>This will list all MAC addresses assosiated with all machine, one
 458 line per machine and with space between the MAC addresses.</p>
 459
 460 <p>To allow system administrators easier job at adding static DHCP
 461 addresses for hosts, it would be possible to extend this to fetch
 462 machine information from sitesummary and update the DHCP and DNS
 463 tables in LDAP using this information.  Such tool is unfortunately not
 464 written yet.</p>
 465 </div>
 466   <div class="tags">
 467
 468
 469
 470    Tags: <a href="http://people.skolelinux.org/pere/blog/tags/debian">debian</a>, <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/sitesummary">sitesummary</a>.
 471
 472   </div>
 473  </div>
 474  <div class="padding"></div>
 475
 476  <p style="text-align: right;"><a href="index.rss"><img src="http://people.skolelinux.org/pere/blog/xml.gif" alt="RSS feed" width="36" height="14"></a></p>
 477
 478 <div id="sidebar">
 479
 480
 481
 482
 483
 484 <h2>Archive</h2>
 485 <ul>
 486
 487 <li>2010
 488 <ul>
 489
 490 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/01/">January (2)</a></li>
 491
 492 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/02/">February (1)</a></li>
 493
 494 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/03/">March (3)</a></li>
 495
 496 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/04/">April (3)</a></li>
 497
 498 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/05/">May (9)</a></li>
 499
 500 <li><a href="http://people.skolelinux.org/pere/blog/archive/2010/06/">June (4)</a></li>
 501
 502 </ul></li>
 503
 504 <li>2009
 505 <ul>
 506
 507 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/01/">January (8)</a></li>
 508
 509 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/02/">February (8)</a></li>
 510
 511 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/03/">March (12)</a></li>
 512
 513 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/04/">April (10)</a></li>
 514
 515 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/05/">May (9)</a></li>
 516
 517 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/06/">June (3)</a></li>
 518
 519 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/07/">July (4)</a></li>
 520
 521 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/08/">August (3)</a></li>
 522
 523 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/09/">September (1)</a></li>
 524
 525 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/10/">October (2)</a></li>
 526
 527 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/11/">November (3)</a></li>
 528
 529 <li><a href="http://people.skolelinux.org/pere/blog/archive/2009/12/">December (3)</a></li>
 530
 531 </ul></li>
 532
 533 <li>2008
 534 <ul>
 535
 536 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/11/">November (5)</a></li>
 537
 538 <li><a href="http://people.skolelinux.org/pere/blog/archive/2008/12/">December (7)</a></li>
 539
 540 </ul></li>
 541
 542 </ul>
 543
 544
 545
 546 <h2>Tags</h2>
 547 <ul>
 548
 549  <li><a href="http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (11)</a></li>
 550
 551  <li><a href="http://people.skolelinux.org/pere/blog/tags/amiga">amiga (1)</a></li>
 552
 553  <li><a href="http://people.skolelinux.org/pere/blog/tags/aros">aros (1)</a></li>
 554
 555  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian">debian (23)</a></li>
 556
 557  <li><a href="http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (23)</a></li>
 558
 559  <li><a href="http://people.skolelinux.org/pere/blog/tags/english">english (34)</a></li>
 560
 561  <li><a href="http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (1)</a></li>
 562
 563  <li><a href="http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (6)</a></li>
 564
 565  <li><a href="http://people.skolelinux.org/pere/blog/tags/kart">kart (2)</a></li>
 566
 567  <li><a href="http://people.skolelinux.org/pere/blog/tags/lenker">lenker (1)</a></li>
 568
 569  <li><a href="http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (1)</a></li>
 570
 571  <li><a href="http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (5)</a></li>
 572
 573  <li><a href="http://people.skolelinux.org/pere/blog/tags/norsk">norsk (66)</a></li>
 574
 575  <li><a href="http://people.skolelinux.org/pere/blog/tags/nuug">nuug (74)</a></li>
 576
 577  <li><a href="http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (12)</a></li>
 578
 579  <li><a href="http://people.skolelinux.org/pere/blog/tags/personvern">personvern (11)</a></li>
 580
 581  <li><a href="http://people.skolelinux.org/pere/blog/tags/reprap">reprap (10)</a></li>
 582
 583  <li><a href="http://people.skolelinux.org/pere/blog/tags/rss">rss (1)</a></li>
 584
 585  <li><a href="http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (8)</a></li>
 586
 587  <li><a href="http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (3)</a></li>
 588
 589  <li><a href="http://people.skolelinux.org/pere/blog/tags/standard">standard (12)</a></li>
 590
 591  <li><a href="http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (1)</a></li>
 592
 593  <li><a href="http://people.skolelinux.org/pere/blog/tags/video">video (10)</a></li>
 594
 595  <li><a href="http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (1)</a></li>
 596
 597  <li><a href="http://people.skolelinux.org/pere/blog/tags/web">web (6)</a></li>
 598
 599 </ul>
 600
 601 </div>
 602
 603 <p style="text-align: right">
 604 Created by <a href="http://steve.org.uk/Software/chronicle">Chronicle v3.7</a>
 605 </p>
 606 </body>
 607 </html>