1 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Strict//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
5 <title>Petter Reinholdtsen: Entries Tagged bootsystem
</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=
"bootsystem.rss" type=
"application/rss+xml">
13 <a href=
"http://people.skolelinux.org/pere/blog/">Petter Reinholdtsen
</a>
19 <p>Entries tagged "bootsystem".
</p>
26 <a href=
"http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html">Debian boots quicker and quicker
</a>
34 <p>I spent Monday and tuesday this week in London with a lot of the
35 people involved in the boot system on Debian and Ubuntu, to see if we
36 could find more ways to speed up the boot system. This was an Ubuntu
38 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint">developer
39 gathering
</a>. It was quite productive. We also discussed the future
40 of boot systems, and ways to handle the increasing number of boot
41 issues introduced by the Linux kernel becoming more and more
42 asynchronous and event base. The Ubuntu approach using udev and
43 upstart might be a good way forward. Time will show.
</p>
45 <p>Anyway, there are a few ways at the moment to speed up the boot
46 process in Debian. All of these should be applied to get a quick
51 <li>Use dash as /bin/sh.
</li>
53 <li>Disable the init.d/hwclock*.sh scripts and make sure the hardware
56 <li>Install and activate the insserv package to enable
57 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot">dependency
58 based boot sequencing
</a>, and enable concurrent booting.
</li>
62 These points are based on the Google summer of code work done by
63 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/">Carlos
66 <p>Support for makefile-style concurrency during boot was uploaded to
67 unstable yesterday. When we tested it, we were able to cut
6 seconds
68 from the boot sequence. It depend on very correct dependency
69 declaration in all init.d scripts, so I expect us to find edge cases
70 where the dependences in some scripts are slightly wrong when we start
73 <p>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
74 introduced by Raphael Geissert today, one that could affect the
75 startup speed as well. Instead of starting some scripts concurrently
76 from rcS.d/ and another set of scripts from rc2.d/, it would be
77 possible to run a of them in the same process. A quick way to test
78 this would be to enable insserv and run 'mv /etc/rc2.d/S* /etc/rcS.d/;
79 insserv'. Will need to test if that work. :)
</p>
86 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
90 <div class=
"padding"></div>
94 <a href=
"http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html">Taking over sysvinit development
</a>
102 <p>After several years of frustration with the lack of activity from
103 the existing sysvinit upstream developer, I decided a few weeks ago to
104 take over the package and become the new upstream. The number of
105 patches to track for the Debian package was becoming a burden, and the
106 lack of synchronization between the distribution made it hard to keep
107 the package up to date.
</p>
109 <p>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
110 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
111 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
112 and Fedora), based on the patches currently in use in these
113 distributions. We Debian maintainers plan to move to this tarball as
114 the new upstream as soon as we find time to do the merge. Since the
115 new tarball was created, we agreed with Werner at SuSe to make a new
116 upstream project at
<a href=
"http://savannah.nongnu.org/">Savannah
</a>, and continue
117 development there. The project is registered and currently waiting
118 for approval by the Savannah administrators, and as soon as it is
119 approved, we will import the old versions from svn and continue
120 working on the future release.
</p>
122 <p>It is a bit ironic that this is done now, when some of the involved
123 distributions are moving to upstart as a syvinit replacement.
</p>
130 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<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>.
134 <div class=
"padding"></div>
138 <a href=
"http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html">Debian has switched to dependency based boot sequencing
</a>
146 <p>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
147 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
148 have been migrated to using dependency based boot sequencing. This
149 conclude work me and others have been doing for the last three days.
150 It feels great to see this finally part of the default Debian
151 installation. Now we just need to weed out the last few problems that
152 are bound to show up, to get everything ready for Squeeze.
</p>
154 <p>The next step is migrating /sbin/init from sysvinit to upstart, and
155 fixing the more fundamental problem of handing the event based
156 non-predictable kernel in the early boot.
</p>
163 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<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>.
167 <div class=
"padding"></div>
171 <a href=
"http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html">Parallellizing the boot in Debian Squeeze - ready for wider testing
</a>
179 <p>These days, the init.d script dependencies in Squeeze are quite
180 complete, so complete that it is actually possible to run all the
181 init.d scripts in parallell based on these dependencies. If you want
182 to test your Squeeze system, make sure
183 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot">dependency
184 based boot sequencing
</a> is enabled, and add this line to
185 /etc/default/rcS:
</p>
191 <p>That is it. It will cause sysv-rc to use the startpar tool to run
192 scripts in parallel using the dependency information stored in
193 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
194 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
195 to try to start the kdm and gdm scripts as early as possible, and will
196 start the facilities required by kdm or gdm as early as possible to
197 make this happen.
</p>
199 <p>Give it a try, and see if you like the result. If some services
200 fail to start properly, it is most likely because they have incomplete
201 init.d script dependencies in their startup script (or some of their
202 dependent scripts have incomplete dependencies). Report bugs and get
203 the package maintainers to fix it. :)
</p>
205 <p>Running scripts in parallel could be the default in Debian when we
206 manage to get the init.d script dependencies complete and correct. I
207 expect we will get there in Squeeze+
1, if we get manage to test and
208 fix the remaining issues.
</p>
210 <p>If you report any problems with dependencies in init.d scripts to
211 the BTS, please usertag the report to get it to show up at
212 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org">the
213 list of usertagged bugs related to this
</a>.
</p>
220 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
224 <div class=
"padding"></div>
228 <a href=
"http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html">systemd, an interesting alternative to upstart
</a>
236 <p>The last few days a new boot system called
237 <a href=
"http://www.freedesktop.org/wiki/Software/systemd">systemd
</a>
239 <a href=
"http://0pointer.de/blog/projects/systemd.html">introduced
</a>
241 to the free software world. I have not yet had time to play around
242 with it, but it seem to be a very interesting alternative to
243 <a href=
"http://upstart.ubuntu.com/">upstart
</a>, and might prove to be
244 a good alternative for Debian when we are able to switch to an event
245 based boot system. Tollef is
246 <a href=
"http://bugs.debian.org/580814">in the process
</a> of getting
247 systemd into Debian, and I look forward to seeing how well it work. I
248 like the fact that systemd handles init.d scripts with dependency
249 information natively, allowing them to run in parallel where upstart
250 at the moment do not.
</p>
252 <p>Unfortunately do systemd have the same problem as upstart regarding
253 platform support. It only work on recent Linux kernels, and also need
254 some new kernel features enabled to function properly. This means
255 kFreeBSD and Hurd ports of Debian will need a port or a different boot
256 system. Not sure how that will be handled if systemd proves to be the
259 <p>In the mean time, based on the
260 <a href=
"http://lists.debian.org/debian-devel/2010/05/msg00122.html">input
261 on debian-devel@
</a> regarding parallel booting in Debian, I have
262 decided to enable full parallel booting as the default in Debian as
263 soon as possible (probably this weekend or early next week), to see if
264 there are any remaining serious bugs in the init.d dependencies. A
265 new version of the sysvinit package implementing this change is
266 already in experimental. If all go well, Squeeze will be released
267 with parallel booting enabled by default.
</p>
274 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<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>.
278 <div class=
"padding"></div>
282 <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>
290 <p>Since this evening, parallel booting is the default in
291 Debian/unstable for machines using dependency based boot sequencing.
292 Apparently the testing of concurrent booting has been wider than
293 expected, if I am to believe the
294 <a href=
"http://lists.debian.org/debian-devel/2010/05/msg00122.html">input
295 on debian-devel@
</a>, and I concluded a few days ago to move forward
296 with the feature this weekend, to give us some time to detect any
297 remaining problems before Squeeze is frozen. If serious problems are
298 detected, it is simple to change the default back to sequential boot.
299 The upload of the new sysvinit package also activate a new upstream
302 More information about
303 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot">dependency
304 based boot sequencing
</a> is available from the Debian wiki. It is
305 currently possible to disable parallel booting when one run into
306 problems caused by it, by adding this line to /etc/default/rcS:
</p>
312 <p>If you report any problems with dependencies in init.d scripts to
313 the BTS, please usertag the report to get it to show up at
314 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org">the
315 list of usertagged bugs related to this
</a>.
</p>
322 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<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>.
326 <div class=
"padding"></div>
330 <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>
338 <p>A few days ago, parallel booting was enabled in Debian/testing.
339 The feature seem to hold up pretty well, but three fairly serious
340 issues are known and should be solved:
344 <li>The wicd package seen to
345 <a href=
"http://bugs.debian.org/508289">break NFS mounting
</a> and
346 <a href=
"http://bugs.debian.org/581586">network setup
</a> when
347 parallel booting is enabled. No idea why, but the wicd maintainer
348 seem to be on the case.
</li>
350 <li>The nvidia X driver seem to
351 <a href=
"http://bugs.debian.org/583312">have a race condition
</a>
352 triggered more easily when parallel booting is in effect. The
353 maintainer is on the case.
</li>
355 <li>The sysv-rc package fail to properly enable dependency based boot
356 sequencing (the shutdown is broken) when old file-rc users
357 <a href=
"http://bugs.debian.org/575080">try to switch back
</a> to
358 sysv-rc. One way to solve it would be for file-rc to create
359 /etc/init.d/.legacy-bootordering, and another is to try to make
360 sysv-rc more robust. Will investigate some more and probably upload a
361 workaround in sysv-rc to help those trying to move from file-rc to
362 sysv-rc get a working shutdown.
</li>
366 <p>All in all not many surprising issues, and all of them seem
367 solvable before Squeeze is released. In addition to these there are
368 some packages with bugs in their dependencies and run level settings,
369 which I expect will be fixed in a reasonable time span.
</p>
371 <p>If you report any problems with dependencies in init.d scripts to
372 the BTS, please usertag the report to get it to show up at
373 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org">the
374 list of usertagged bugs related to this
</a>.
</p>
376 <p>Update: Correct bug number to file-rc issue.
</p>
383 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<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>.
387 <div class=
"padding"></div>
391 <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>
399 <p>It is strange to watch how a bug in Debian causing KDM to fail to
400 start at boot when an NVidia video card is used is handled. The
401 problem seem to be that the nvidia X.org driver uses a long time to
402 initialize, and this duration is longer than kdm is configured to
405 <p>I came across two bugs related to this issue,
406 <a href=
"http://bugs.debian.org/583312">#
583312</a> initially filed
407 against initscripts and passed on to nvidia-glx when it became obvious
408 that the nvidia drivers were involved, and
409 <a href=
"http://bugs.debian.org/524751">#
524751</a> initially filed against
410 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p>
412 <p>To me, it seem that no-one is interested in actually solving the
413 problem nvidia video card owners experience and make sure the Debian
414 distribution work out of the box for these users. The nvidia driver
415 maintainers expect kdm to be set up to wait longer, while kdm expect
416 the nvidia driver maintainers to fix the driver to start faster, and
417 while they wait for each other I guess the users end up switching to a
418 distribution that work for them. I have no idea what the solution is,
419 but I am pretty sure that waiting for each other is not it.
</p>
421 <p>I wonder why we end up handling bugs this way.
</p>
428 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<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>.
432 <div class=
"padding"></div>
436 <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>
444 <p>If Debian is to migrate to upstart on Linux, I expect some init.d
445 scripts to migrate (some of) their operations to upstart job while
446 keeping the init.d for hurd and kfreebsd. The packages with such
447 needs will need a way to get their init.d scripts to behave
448 differently when used with sysvinit and with upstart. Because of
449 this, I had a look at the environment variables set when a init.d
450 script is running under upstart, and when it is not.
</p>
452 <p>With upstart, I notice these environment variables are set when a
453 script is started from rcS.d/ (ignoring some irrelevant ones like
462 UPSTART_EVENTS=startup
464 UPSTART_JOB=rc-sysinit
467 <p>With sysvinit, these environment variables are set for the same
471 INIT_VERSION=sysvinit-
2.88
478 <p>The RUNLEVEL and PREVLEVEL environment variables passed on from
479 sysvinit are not set by upstart. Not sure if it is intentional or not
480 to not be compatible with sysvinit in this regard.
</p>
482 <p>For scripts needing to behave differently when upstart is used,
483 looking for the UPSTART_JOB environment variable seem to be a good
491 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian
</a>,
<a href=
"http://people.skolelinux.org/pere/blog/tags/english">english
</a>.
495 <div class=
"padding"></div>
499 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html">Automatic upgrade testing from Lenny to Squeeze
</a>
507 <p>The last few days I have done some upgrade testing in Debian, to
508 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
509 have been discovered and reported in the process
510 (
<a href=
"http://bugs.debian.org/585410">#
585410</a> in nagios3-cgi,
511 <a href=
"http://bugs.debian.org/584879">#
584879</a> already fixed in
512 enscript and
<a href=
"http://bugs.debian.org/584861">#
584861</a> in
513 kdebase-workspace-data), and to get a more regular testing going on, I
514 am working on a script to automate the test.
</p>
516 <p>The idea is to create a Lenny chroot and use tasksel to install a
517 Gnome or KDE desktop installation inside the chroot before upgrading
518 it. To ensure no services are started in the chroot, a policy-rc.d
519 script is inserted. To make sure tasksel believe it is to install a
520 desktop on a laptop, the tasksel tests are replaced in the chroot
521 (only acceptable because this is a throw-away chroot).
</p>
523 <p>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
524 currently always fail because udev refuses to upgrade with the kernel
525 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
526 is created. The bug report
527 <a href=
"http://bugs.debian.org/566000">#
566000</a> make me suspect
528 this problem do not trigger in a chroot, but I touch the file anyway
529 to make sure the upgrade go well. Testing on virtual and real
530 hardware have failed me because of udev so far, and creating this file
531 do the trick in such settings anyway. This is a
532 <a href=
"http://www.linuxquestions.org/questions/debian-26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-804130/">known
533 issue
</a> and the current udev behaviour is intended by the udev
534 maintainer because he lack the resources to rewrite udev to keep
535 working with old kernels or something like that. I really wish the
536 udev upstream would keep udev backwards compatible, to avoid such
537 upgrade problem, but given that they fail to do so, I guess
538 documenting the way out of this mess is the best option we got for
541 <p>Anyway, back to the task at hand, testing upgrades. This test
542 script, which I call
<tt>upgrade-test
</tt> for now, is doing the
560 mirror=http://ftp.skolelinux.org/debian
561 tmpdir=chroot-$from-upgrade-$to-$desktop
563 debootstrap $from $tmpdir $mirror
564 chroot $tmpdir aptitude update
565 cat
> $tmpdir/usr/sbin/policy-rc.d
<<EOF
569 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
573 mount -t proc proc $tmpdir/proc
574 # Make sure proc is unmounted also on failure
575 trap exit_cleanup EXIT INT
577 chroot $tmpdir aptitude -y install debconf-utils
579 # Make sure tasksel autoselection trigger. It need the test scripts
580 # to return the correct answers.
581 echo tasksel tasksel/desktop multiselect $desktop | \
582 chroot $tmpdir debconf-set-selections
584 # Include the desktop and laptop task
585 for test in desktop laptop ; do
586 echo
> $tmpdir/usr/lib/tasksel/tests/$test
<<EOF
590 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
593 DEBIAN_FRONTEND=noninteractive
594 DEBIAN_PRIORITY=critical
595 export DEBIAN_FRONTEND DEBIAN_PRIORITY
596 chroot $tmpdir tasksel --new-install
598 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
599 chroot $tmpdir aptitude update
600 touch $tmpdir/etc/udev/kernel-upgrade
601 chroot $tmpdir aptitude -y dist-upgrade
605 <p>I suspect it would be useful to test upgrades with both apt-get and
606 with aptitude, but I have not had time to look at how they behave
607 differently so far. I hope to get a cron job running to do the test
608 regularly and post the result on the web. The Gnome upgrade currently
609 work, while the KDE upgrade fail because of the bug in
610 kdebase-workspace-data
</p>
612 <p>I am not quite sure what kind of extract from the huge upgrade logs
613 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
614 post, so I will refrain from trying. I can report that for Gnome,
615 aptitude report
760 packages upgraded,
448 newly installed,
129 to
616 remove and
1 not upgraded and
1024MB need to be downloaded while for
617 KDE the same numbers are
702 packages upgraded,
507 newly installed,
618 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p>
620 <p>I am very happy to notice that the Gnome desktop + laptop upgrade
621 is able to migrate to dependency based boot sequencing and parallel
622 booting without a hitch. Was unsure if there were still bugs with
623 packages failing to clean up their obsolete init.d script during
624 upgrades, and no such problem seem to affect the Gnome desktop+laptop
632 Tags:
<a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem
</a>,
<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>.
636 <div class=
"padding"></div>
638 <p style=
"text-align: right;"><a href=
"bootsystem.rss"><img src=
"http://people.skolelinux.org/pere/blog/xml.gif" alt=
"RSS Feed" width=
"36" height=
"14"></a></p>
651 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/01/">January (
2)
</a></li>
653 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/02/">February (
1)
</a></li>
655 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/03/">March (
3)
</a></li>
657 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/04/">April (
3)
</a></li>
659 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/05/">May (
9)
</a></li>
661 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/06/">June (
14)
</a></li>
663 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/07/">July (
12)
</a></li>
665 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2010/08/">August (
5)
</a></li>
672 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/01/">January (
8)
</a></li>
674 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/02/">February (
8)
</a></li>
676 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/03/">March (
12)
</a></li>
678 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/04/">April (
10)
</a></li>
680 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/05/">May (
9)
</a></li>
682 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/06/">June (
3)
</a></li>
684 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/07/">July (
4)
</a></li>
686 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/08/">August (
3)
</a></li>
688 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/09/">September (
1)
</a></li>
690 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/10/">October (
2)
</a></li>
692 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/11/">November (
3)
</a></li>
694 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2009/12/">December (
3)
</a></li>
701 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/11/">November (
5)
</a></li>
703 <li><a href=
"http://people.skolelinux.org/pere/blog/archive/2008/12/">December (
7)
</a></li>
714 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/3d-printer">3d-printer (
11)
</a></li>
716 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/amiga">amiga (
1)
</a></li>
718 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/aros">aros (
1)
</a></li>
720 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/bootsystem">bootsystem (
10)
</a></li>
722 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian">debian (
35)
</a></li>
724 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/debian edu">debian edu (
40)
</a></li>
726 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/english">english (
56)
</a></li>
728 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fiksgatami">fiksgatami (
1)
</a></li>
730 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/fildeling">fildeling (
8)
</a></li>
732 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/kart">kart (
3)
</a></li>
734 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ldap">ldap (
8)
</a></li>
736 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/lenker">lenker (
2)
</a></li>
738 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/ltsp">ltsp (
1)
</a></li>
740 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/multimedia">multimedia (
5)
</a></li>
742 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/norsk">norsk (
71)
</a></li>
744 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/nuug">nuug (
93)
</a></li>
746 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/opphavsrett">opphavsrett (
14)
</a></li>
748 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/personvern">personvern (
15)
</a></li>
750 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/reprap">reprap (
10)
</a></li>
752 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/rss">rss (
1)
</a></li>
754 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sikkerhet">sikkerhet (
11)
</a></li>
756 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/sitesummary">sitesummary (
3)
</a></li>
758 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/standard">standard (
13)
</a></li>
760 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/stavekontroll">stavekontroll (
1)
</a></li>
762 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/video">video (
10)
</a></li>
764 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/vitenskap">vitenskap (
1)
</a></li>
766 <li><a href=
"http://people.skolelinux.org/pere/blog/tags/web">web (
7)
</a></li>