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