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