1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged debian
</title>
5 <description>Entries tagged debian
</description>
6 <link>http://people.skolelinux.org/pere/blog/
</link>
10 <title>Debian Jessie, PXE and automatic firmware installation
</title>
11 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
12 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
13 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
14 <description><p
>When PXE installing laptops with Debian, I often run into the
15 problem that the WiFi card require some firmware to work properly.
16 And it has been a pain to fix this using preseeding in Debian.
17 Normally something more is needed. But thanks to
18 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
19 package
</a
> and its recent tasksel extension, it has now become easy
20 to do this using simple preseeding.
</p
>
22 <p
>The isenkram-cli package provide tasksel tasks which will install
23 firmware for the hardware found in the machine (actually, requested by
24 the kernel modules for the hardware). (It can also install user space
25 programs supporting the hardware detected, but that is not the focus
26 of this story.)
</p
>
28 <p
>To get this working in the default installation, two preeseding
29 values are needed. First, the isenkram-cli package must be installed
30 into the target chroot (aka the hard drive) before tasksel is executed
31 in the pkgsel step of the debian-installer system. This is done by
32 preseeding the base-installer/includes debconf value to include the
33 isenkram-cli package. The package name is next passed to debootstrap
34 for installation. With the isenkram-cli package in place, tasksel
35 will automatically use the isenkram tasks to detect hardware specific
36 packages for the machine being installed and install them, because
37 isenkram-cli contain tasksel tasks.
</p
>
39 <p
>Second, one need to enable the non-free APT repository, because
40 most firmware unfortunately is non-free. This is done by preseeding
41 the apt-mirror-setup step. This is unfortunate, but for a lot of
42 hardware it is the only option in Debian.
</p
>
44 <p
>The end result is two lines needed in your preseeding file to get
45 firmware installed automatically by the installer:
</p
>
47 <p
><blockquote
><pre
>
48 base-installer base-installer/includes string isenkram-cli
49 apt-mirror-setup apt-setup/non-free boolean true
50 </pre
></blockquote
></p
>
52 <p
>The current version of isenkram-cli in testing/jessie will install
53 both firmware and user space packages when using this method. It also
54 do not work well, so use version
0.15 or later. Installing both
55 firmware and user space packages might give you a bit more than you
56 want, so I decided to split the tasksel task in two, one for firmware
57 and one for user space programs. The firmware task is enabled by
58 default, while the one for user space programs is not. This split is
59 implemented in the package currently in unstable.
</p
>
61 <p
>If you decide to give this a go, please let me know (via email) how
62 this recipe work for you if you decide to give it a go. :)
</p
>
64 <p
>So, I bet you are wondering, how can this work. First and
65 foremost, it work because tasksel is modular, and driven by whatever
66 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
67 isenkram-cli package place two files for tasksel to find. First there
68 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
70 <p
><blockquote
><pre
>
71 Task: isenkram-packages
73 Description: Hardware specific packages (autodetected by isenkram)
74 Based on the detected hardware various hardware specific packages are
76 Test-new-install: show show
78 Packages: for-current-hardware
80 Task: isenkram-firmware
82 Description: Hardware specific firmware packages (autodetected by isenkram)
83 Based on the detected hardware various hardware specific firmware
84 packages are proposed.
85 Test-new-install: mark show
87 Packages: for-current-hardware-firmware
88 </pre
></blockquote
></p
>
90 <p
>The key parts are Test-new-install which indicate how the task
91 should be handled and the Packages line referencing to a script in
92 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
93 list of packages to install. The for-current-hardware-firmware script
94 look like this to list relevant firmware for the machine:
96 <p
><blockquote
><pre
>
101 isenkram-autoinstall-firmware -l
102 </pre
></blockquote
></p
>
104 <p
>With those two pieces in place, the firmware is installed by
105 tasksel during the normal d-i run. :)
</p
>
107 <p
>If you want to test what tasksel will install when isenkram-cli is
108 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
109 --new-install
</tt
> to get the list of packages that tasksel would
112 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
113 pilots in testing this feature, as isenkram is used there now to
114 install firmware, replacing the earlier scripts.
</p
>
119 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
120 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
121 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
122 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
123 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
124 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
125 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
126 on a screen normally showing the bread types and prizes:
</p
>
128 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
130 <p
>If it had booted as it was supposed to, I would never had known
131 about this hidden Linux installation. It is interesting what
132 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
137 <title>New lsdvd release version
0.17 is ready
</title>
138 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
139 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
140 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
141 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
142 got a new set of developers a few weeks ago, after the original
143 developer decided to step down and pass the project to fresh blood.
144 This project is now maintained by Petter Reinholdtsen and Steve
147 <p
>I just wrapped up
148 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
149 new lsdvd release
</a
>, available in git or from
150 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
151 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
156 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
157 <li
>Check for garbage in the program chains, which indicate that a track is
158 non-existant, to work around additional copy protection
</li
>
159 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
160 <li
>Fix pallete display of first entry
</li
>
161 <li
>Fix include orders
</li
>
162 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
163 <li
>Fix the chapter count
</li
>
164 <li
>Make sure the array size and the array limit used when initialising
165 the palette size is the same.
</li
>
166 <li
>Fix array printing.
</li
>
167 <li
>Correct subsecond calculations.
</li
>
168 <li
>Add sector information to the output format.
</li
>
169 <li
>Clean up code to be closer to ANSI C and compile without warnings
170 with more GCC compiler warnings.
</li
>
174 <p
>This change bring together patches for lsdvd in use in various
175 Linux and Unix distributions, as well as patches submitted to the
176 project the last nine years. Please check it out. :)
</p
>
181 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
182 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
183 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
184 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
185 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
186 project
</a
> provide a Linux solution for schools, including a
187 powerful desktop with education software, a central server providing
188 web pages, user database, user home directories, central login and PXE
189 boot of both clients without disk and the installation to install Debian
190 Edu on machines with disk (and a few other services perhaps to small
191 to mention here). We in the Debian Edu team are currently working on
192 the Jessie based version, trying to get everything in shape before the
193 freeze, to avoid having to maintain our own package repository in the
195 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
196 status
</a
> can be seen on the Debian wiki, and there is still heaps of
197 work left. Some fatal problems block testing, breaking the installer,
198 but it is possible to work around these to get anyway. Here is a
199 recipe on how to get the installation limping along.
</p
>
201 <p
>First, download the test ISO via
202 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
203 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
205 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
206 The ISO build was broken on Tuesday, so we do not get a new ISO every
207 12 hours or so, but thankfully the ISO we already got we are able to
208 install with some tweaking.
</p
>
210 <p
>When you get to the Debian Edu profile question, go to tty2
211 (use Alt-Ctrl-F2), run
</p
>
213 <p
><blockquote
><pre
>
214 nano /usr/bin/edu-eatmydata-install
215 </pre
></blockquote
></p
>
217 <p
>and add
'exit
0' as the second line, disabling the eatmydata
218 optimization. Return to the installation, select the profile you want
219 and continue. Without this change, exim4-config will fail to install
220 due to a known bug in eatmydata.
</p
>
222 <p
>When you get the grub question at the end, answer /dev/sda (or if
223 this do not work, figure out what your correct value would be. All my
224 test machines need /dev/sda, so I have no advice if it do not fit
227 <p
>If you installed a profile including a graphical desktop, log in as
228 root after the initial boot from hard drive, and install the
229 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
230 or mate. If you want several desktop options, install more than one
231 metapackage. Once this is done, reboot and you should have a working
232 graphical login screen. This workaround should no longer be needed
233 once the education-tasks package version
1.801 enter testing in two
236 <p
>I believe the ISO build will start working on two days when the new
237 tasksel package enter testing and Steve McIntyre get a chance to
238 update the debian-cd git repository. The eatmydata, grub and desktop
239 issues are already fixed in unstable and testing, and should show up
240 on the ISO as soon as the ISO build start working again. Well the
241 eatmydata optimization is really just disabled. The proper fix
242 require an upload by the eatmydata maintainer applying the patch
243 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
244 The rest have proper fixes in unstable.
</p
>
246 <p
>I hope this get you going with the installation testing, as we are
247 quickly running out of time trying to get our Jessie based
248 installation ready before the distribution freeze in a month.
</p
>
253 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
254 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
255 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
256 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
257 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
258 to handle my fairly large DVD collection. It is a nice command line
259 tool to get details about a DVD, like title, tracks, track length,
260 etc, in XML, Perl or human readable format. But lsdvd have not seen
261 any new development since
2006 and had a few irritating bugs affecting
262 its use with some DVDs. Upstream seemed to be dead, and in January I
263 sent a small probe asking for a version control repository for the
264 project, without any reply. But I use it regularly and would like to
265 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
266 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
267 the project admin, and after getting a reply from him explaining that
268 he was no longer interested in the project, I asked if I could take
269 over. And yesterday, I became project admin.
</p
>
271 <p
>I
've been in touch with a Gentoo developer and the Debian
272 maintainer interested in joining forces to maintain the upstream
273 project, and I hope we can get a new release out fairly quickly,
274 collecting the patches spread around on the internet into on place.
275 I
've added the relevant Debian patches to the freshly created git
276 repository, and expect the Gentoo patches to make it too. If you got
277 a DVD collection and care about command line tools, check out
278 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
279 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
280 list
</a
>. :)
</p
>
285 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
286 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
287 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
288 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
289 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
290 a lot quicker. When we install more than
2000 packages in
291 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
292 tasksel in the installer, unpacking the binary packages take forever.
293 A part of the slow I/O issue was discussed in
294 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
295 much file system sync-ing done by dpkg, which is the package
296 responsible for unpacking the binary packages. Other parts (like code
297 executed by postinst scripts) might also sync to disk during
298 installation. All this sync-ing to disk do not really make sense to
299 me. If the machine crash half-way through, I start over, I do not try
300 to salvage the half installed system. So the failure sync-ing is
301 supposed to protect against, hardware or system crash, is not really
302 relevant while the installer is running.
</p
>
304 <p
>A few days ago, I thought of a way to get rid of all the file
305 system sync()-ing in a fairly non-intrusive way, without the need to
306 change the code in several packages. The idea is not new, but I have
307 not heard anyone propose the approach using dpkg-divert before. It
308 depend on the small and clever package
309 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
310 uses LD_PRELOAD to replace the system functions for syncing data to
311 disk with functions doing nothing, thus allowing programs to live
312 dangerous while speeding up disk I/O significantly. Instead of
313 modifying the implementation of dpkg, apt and tasksel (which are the
314 packages responsible for selecting, fetching and installing packages),
315 it occurred to me that we could just divert the programs away, replace
316 them with a simple shell wrapper calling
317 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
318 Two days ago I decided to test the idea, and wrapped up a simple
319 implementation for the Debian Edu udeb.
</p
>
321 <p
>The effect was stunning. In my first test it reduced the running
322 time of the pkgsel step (installing tasks) from
64 to less than
44
323 minutes (
20 minutes shaved off the installation) on an old Dell
324 Latitude D505 machine. I am not quite sure what the optimised time
325 would have been, as I messed up the testing a bit, causing the debconf
326 priority to get low enough for two questions to pop up during
327 installation. As soon as I saw the questions I moved the installation
328 along, but do not know how long the question were holding up the
329 installation. I did some more measurements using Debian Edu Jessie,
330 and got these results. The time measured is the time stamp in
331 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
332 "pkgsel: finishing up
" lines, if you want to do the same measurement
333 yourself. In Debian Edu, the tasksel dialog do not show up, and the
334 timing thus do not depend on how quickly the user handle the tasksel
337 <p
><table
>
340 <th
>Machine/setup
</th
>
341 <th
>Original tasksel
</th
>
342 <th
>Optimised tasksel
</th
>
343 <th
>Reduction
</th
>
347 <td
>Latitude D505 Main+LTSP LXDE
</td
>
348 <td
>64 min (
07:
46-
08:
50)
</td
>
349 <td
><44 min (
11:
27-
12:
11)
</td
>
350 <td
>>20 min
18%
</td
>
354 <td
>Latitude D505 Roaming LXDE
</td
>
355 <td
>57 min (
08:
48-
09:
45)
</td
>
356 <td
>34 min (
07:
43-
08:
17)
</td
>
357 <td
>23 min
40%
</td
>
361 <td
>Latitude D505 Minimal
</td
>
362 <td
>22 min (
10:
37-
10:
59)
</td
>
363 <td
>11 min (
11:
16-
11:
27)
</td
>
364 <td
>11 min
50%
</td
>
368 <td
>Thinkpad X200 Minimal
</td
>
369 <td
>6 min (
08:
19-
08:
25)
</td
>
370 <td
>4 min (
08:
04-
08:
08)
</td
>
371 <td
>2 min
33%
</td
>
375 <td
>Thinkpad X200 Roaming KDE
</td
>
376 <td
>19 min (
09:
21-
09:
40)
</td
>
377 <td
>15 min (
10:
25-
10:
40)
</td
>
378 <td
>4 min
21%
</td
>
381 </table
></p
>
383 <p
>The test is done using a netinst ISO on a USB stick, so some of the
384 time is spent downloading packages. The connection to the Internet
385 was
100Mbit/s during testing, so downloading should not be a
386 significant factor in the measurement. Download typically took a few
387 seconds to a few minutes, depending on the amount of packages being
390 <p
>The speedup is implemented by using two hooks in
391 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
392 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
393 finish-install.d hook to remove the divert at the end of the
394 installation. I picked the pre-pkgsel.d hook instead of the
395 post-base-installer.d hook because I test using an ISO without the
396 eatmydata package included, and the post-base-installer.d hook in
397 Debian Edu can only operate on packages included in the ISO. The
398 negative effect of this is that I am unable to activate this
399 optimization for the kernel installation step in d-i. If the code is
400 moved to the post-base-installer.d hook, the speedup would be larger
401 for the entire installation.
</p
>
403 <p
>I
've implemented this in the
404 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
405 git repository, and plan to provide the optimization as part of the
406 Debian Edu installation. If you want to test this yourself, you can
407 create two files in the installer (or in an udeb). One shell script
408 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
410 <p
><blockquote
><pre
>
413 . /usr/share/debconf/confmodule
415 logger -t my-pkgsel
"info: $*
"
418 logger -t my-pkgsel
"error: $*
"
421 apt-install eatmydata || true
422 if [ -x /target/usr/bin/eatmydata ] ; then
423 for bin in dpkg apt-get aptitude tasksel ; do
425 # Test that the file exist and have not been diverted already.
426 if [ -f /target$file ] ; then
427 info
"diverting $file using eatmydata
"
428 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
429 > /target$file.edu
430 chmod
755 /target$file.edu
431 in-target dpkg-divert --package debian-edu-config \
432 --rename --quiet --add $file
433 ln -sf ./$bin.edu /target$file
435 error
"unable to divert $file, as it is missing.
"
439 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
444 </pre
></blockquote
></p
>
446 <p
>To clean up, another shell script should go into
447 /usr/lib/finish-install.d/ with code like this:
449 <p
><blockquote
><pre
>
451 . /usr/share/debconf/confmodule
453 logger -t my-finish-install
"error: $@
"
455 remove_install_override() {
456 for bin in dpkg apt-get aptitude tasksel ; do
458 if [ -x /target$file.edu ] ; then
460 in-target dpkg-divert --package debian-edu-config \
461 --rename --quiet --remove $file
464 error
"Missing divert for $file.
"
467 sync # Flush file buffers before continuing
470 remove_install_override
471 </pre
></blockquote
></p
>
473 <p
>In Debian Edu, I placed both code fragments in a separate script
474 edu-eatmydata-install and call it from the pre-pkgsel.d and
475 finish-install.d scripts.
</p
>
477 <p
>By now you might ask if this change should get into the normal
478 Debian installer too? I suspect it should, but am not sure the
479 current debian-installer coordinators find it useful enough. It also
480 depend on the side effects of the change. I
'm not aware of any, but I
481 guess we will see if the change is safe after some more testing.
482 Perhaps there is some package in Debian depending on sync() and
483 fsync() having effect? Perhaps it should go into its own udeb, to
484 allow those of us wanting to enable it to do so without affecting
487 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
488 will break installation of all programs using gnutls because of
489 <a href=
"https://bugs.debian.org/
702711">bug #
702711. An updated
490 eatmydata package in Debian will solve it.
</p
>
495 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
496 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
497 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
498 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
499 <description><p
>Yesterday, I had the pleasure of attending a talk with the
500 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
501 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
502 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
503 learn that there is a large set of publicly available key servers to
504 use when looking for peoples public key. So far I have used
505 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
506 were misbehaving, but those days are ended. The servers I have used
507 up until yesterday have been slow and some times unavailable. I hope
508 those problems are gone now.
</p
>
510 <p
>Behind the round robin DNS entry of the
511 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
512 there is a pool of more than
100 keyservers which are checked every
513 day to ensure they are well connected and up to date. It must be
514 better than what I have used so far. :)
</p
>
516 <p
>Yesterdays speaker told me that the service is the default
517 keyserver provided by the default configuration in GnuPG, but this do
518 not seem to be used in Debian. Perhaps it should?
</p
>
520 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
523 <p
><blockquote
><pre
>
524 keyserver pool.sks-keyservers.net
525 </pre
></blockquote
></p
>
527 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
528 entries in DNS. Just for fun, I did just that at work, so now every
529 user of GnuPG at the University of Oslo should find a OpenGPG
530 keyserver automatically should their need it:
</p
>
532 <p
><blockquote
><pre
>
533 % host -t srv _pgpkey-http._tcp.uio.no
534 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
536 </pre
></blockquote
></p
>
539 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
540 HKP lookup protocol
</a
> supported finding signature paths, I would be
541 very happy. It can look up a given key or search for a user ID, but I
542 normally do not want that, but to find a trust path from my key to
543 another key. Given a user ID or key ID, I would like to find (and
544 download) the keys representing a signature path from my key to the
545 key in question, to be able to get a trust path between the two keys.
546 This is as far as I can tell not possible today. Perhaps something
547 for a future version of the protocol?
</p
>
552 <title>From English wiki to translated PDF and epub via Docbook
</title>
553 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
554 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
555 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
556 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
557 project
</a
> provide an instruction manual for teachers, system
558 administrators and other users that contain useful tips for setting up
559 and maintaining a Debian Edu installation. This text is about how the
560 text processing of this manual is handled in the project.
</p
>
562 <p
>One goal of the project is to provide information in the native
563 language of its users, and for this we need to handle translations.
564 But we also want to make sure each language contain the same
565 information, so for this we need a good way to keep the translations
566 in sync. And we want it to be easy for our users to improve the
567 documentation, avoiding the need to learn special formats or tools to
568 contribute, and the obvious way to do this is to make it possible to
569 edit the documentation using a web browser. We also want it to be
570 easy for translators to keep the translation up to date, and give them
571 help in figuring out what need to be translated. Here is the list of
572 tools and the process we have found trying to reach all these
575 <p
>We maintain the authoritative source of our manual in the
576 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
577 wiki
</a
>, as several wiki pages written in English. It consist of one
578 front page with references to the different chapters, several pages
579 for each chapter, and finally one
"collection page
" gluing all the
580 chapters together into one large web page (aka
581 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
582 AllInOne page
</a
>). The AllInOne page is the one used for further
583 processing and translations. Thanks to the fact that the
584 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
585 wiki.debian.org support exporting pages in
586 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
587 the list of pages to export using the raw version of the AllInOne
588 page, loop over each of them to generate a Docbook XML version of the
589 manual. This process also download images and transform image
590 references to use the locally downloaded images. The generated
591 Docbook XML files are slightly broken, so some post-processing is done
592 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
593 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
594 a handfull of images. The XML file can now be used to generate PDF, HTML
595 and epub versions of the English manual. This is the basic step of
596 our process, making PDF (using dblatex), HTML (using xsltproc) and
597 epub (using dbtoepub) version from Docbook XML, and the resulting files
598 are placed in the debian-edu-doc-en binary package.
</p
>
600 <p
>But English documentation is not enough for us. We want translated
601 documentation too, and we want to make it easy for translators to
602 track the English original. For this we use the
603 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
604 which allow us to transform the English Docbook XML file into a
605 translation file (a .pot file), usable with the normal gettext based
606 translation tools used by those translating free software. The pot
607 file is used to create and maintain translation files (several .po
608 files), which the translations update with the native language
609 translations of all titles, paragraphs and blocks of text in the
610 original. The next step is combining the original English Docbook XML
611 and the translation file (say debian-edu-wheezy-manual.nb.po), to
612 create a translated Docbook XML file (in this case
613 debian-edu-wheezy-manual.nb.xml). This translated (or partly
614 translated, if the translation is not complete) Docbook XML file can
615 then be used like the original to create a PDF, HTML and epub version
616 of the documentation.
</p
>
618 <p
>The translators use different tools to edit the .po files. We
620 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
621 while some use emacs and vi, others can use web based editors like
622 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
623 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
624 is where the .po file end up, in our git repository. Updated
625 translations can either be committed directly to git, or submitted as
626 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
627 against the debian-edu-doc package
</a
>.
</p
>
629 <p
>One challenge is images, which both might need to be translated (if
630 they show translated user applications), and are needed in different
631 formats when creating PDF and HTML versions (epub is a HTML version in
632 this regard). For this we transform the original PNG images to the
633 needed density and format during build, and have a way to provide
634 translated images by storing translated versions in
635 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
636 package maintainers know more.
</p
>
638 <p
>If you wonder what the result look like, we provide
639 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
640 of the documentation packages on the web
</a
>. See for example the
641 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
642 PDF version
</a
> or the
643 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
644 HTML version
</a
>. We do not yet build the epub version by default,
645 but perhaps it will be done in the future.
</p
>
647 <p
>To learn more, check out
648 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
649 debian-edu-doc package
</a
>,
650 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
651 manual on the wiki
</a
> and
652 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
653 translation instructions
</a
> in the manual.
</p
>
658 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
659 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
660 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
661 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
662 <description><p
>It would be nice if it was easier in Debian to get all the hardware
663 related packages relevant for the computer installed automatically.
664 So I implemented one, using
665 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
666 package
</a
>. To use it, install the tasksel and isenkram packages and
667 run tasksel as user root. You should be presented with a new option,
668 "Hardware specific packages (autodetected by isenkram)
". When you
669 select it, tasksel will install the packages isenkram claim is fit for
670 the current hardware, hot pluggable or not.
<p
>
672 <p
>The implementation is in two files, one is the tasksel menu entry
673 description, and the other is the script used to extract the list of
674 packages to install. The first part is in
675 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
678 <p
><blockquote
><pre
>
681 Description: Hardware specific packages (autodetected by isenkram)
682 Based on the detected hardware various hardware specific packages are
684 Test-new-install: mark show
686 Packages: for-current-hardware
687 </pre
></blockquote
></p
>
689 <p
>The second part is in
690 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
693 <p
><blockquote
><pre
>
698 isenkram-autoinstall-firmware -l
700 </pre
></blockquote
></p
>
702 <p
>All in all, a very short and simple implementation making it
703 trivial to install the hardware dependent package we all may want to
704 have installed on our machines. I
've not been able to find a way to
705 get tasksel to tell you exactly which packages it plan to install
706 before doing the installation. So if you are curious or careful,
707 check the output from the isenkram-* command line tools first.
</p
>
709 <p
>The information about which packages are handling which hardware is
710 fetched either from the isenkram package itself in
711 /usr/share/isenkram/, from git.debian.org or from the APT package
712 database (using the Modaliases header). The APT package database
713 parsing have caused a nasty resource leak in the isenkram daemon (bugs
714 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
715 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
716 the python-apt code (bug
717 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
718 workaround I was able to get rid of the file descriptor leak and
719 reduce the memory leak from ~
30 MiB per hardware detection down to
720 around
2 MiB per hardware detection. It should make the desktop
721 daemon a lot more useful. The fix is in version
0.7 uploaded to
722 unstable today.
</p
>
724 <p
>I believe the current way of mapping hardware to packages in
725 Isenkram is is a good draft, but in the future I expect isenkram to
726 use the AppStream data source for this. A proposal for getting proper
727 AppStream support into Debian is floating around as
728 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
729 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
730 project
</a
> will take place this summer to improve the situation. I
731 look forward to seeing the result, and welcome patches for isenkram to
732 start using the information when it is ready.
</p
>
734 <p
>If you want your package to map to some specific hardware, either
735 add a
"Xb-Modaliases
" header to your control file like I did in
736 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
737 package
</a
> or submit a bug report with the details to the isenkram
739 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
740 blog posts tagged isenkram
</a
> for details on the notation. I expect
741 the information will be migrated to AppStream eventually, but for the
742 moment I got no better place to store it.
</p
>
747 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
748 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
749 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
750 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
751 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
752 project
</a
> is working on providing the software and hardware to make
753 it easy for non-technical people to host their data and communication
754 at home, and being able to communicate with their friends and family
755 encrypted and away from prying eyes. It is still going strong, and
756 today a major mile stone was reached.
</p
>
758 <p
>Today, the last of the packages currently used by the project to
759 created the system images were accepted into Debian Unstable. It was
760 the freedombox-setup package, which is used to configure the images
761 during build and on the first boot. Now all one need to get going is
762 the build code from the freedom-maker git repository and packages from
763 Debian. And once the freedombox-setup package enter testing, we can
764 build everything directly from Debian. :)
</p
>
766 <p
>Some key packages used by Freedombox are
767 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
768 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
769 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
770 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
771 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
772 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
773 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
774 are plans to integrate more packages into the setup. User
775 documentation is maintained on the Debian wiki. Please
776 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
777 the manual
</a
> and help us improve it.
</p
>
779 <p
>To test for yourself and create boot images with the FreedomBox
780 setup, run this on a Debian machine using a user with sudo rights to
781 become root:
</p
>
784 sudo apt-get install git vmdebootstrap mercurial python-docutils \
785 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
787 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
789 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
790 </pre
></p
>
792 <p
>Root access is needed to run debootstrap and mount loopback
793 devices. See the README in the freedom-maker git repo for more
794 details on the build. If you do not want all three images, trim the
795 make line. Note that the virtualbox-image target is not really
796 virtualbox specific. It create a x86 image usable in kvm, qemu,
797 vmware and any other x86 virtual machine environment. You might need
798 the version of vmdebootstrap in Jessie to get the build working, as it
799 include fixes for a race condition with kpartx.
</p
>
801 <p
>If you instead want to install using a Debian CD and the preseed
802 method, boot a Debian Wheezy ISO and use this boot argument to load
803 the preseed values:
</p
>
806 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
807 </pre
></p
>
809 <p
>I have not tested it myself the last few weeks, so I do not know if
810 it still work.
</p
>
812 <p
>If you wonder how to help, one task you could look at is using
813 systemd as the boot system. It will become the default for Linux in
814 Jessie, so we need to make sure it is usable on the Freedombox. I did
815 a simple test a few weeks ago, and noticed dnsmasq failed to start
816 during boot when using systemd. I suspect there are other problems
817 too. :) To detect problems, there is a test suite included, which can
818 be run from the plinth web interface.
</p
>
820 <p
>Give it a go and let us know how it goes on the mailing list, and help
821 us get the new release published. :) Please join us on
822 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
823 irc.debian.org)
</a
> and
824 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
825 mailing list
</a
> if you want to help make this vision come true.
</p
>
830 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
831 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
832 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
833 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
834 <description><p
>For a while now, I have been looking for a sensible offsite backup
835 solution for use at home. My requirements are simple, it must be
836 cheap and locally encrypted (in other words, I keep the encryption
837 keys, the storage provider do not have access to my private files).
838 One idea me and my friends had many years ago, before the cloud
839 storage providers showed up, was to use Google mail as storage,
840 writing a Linux block device storing blocks as emails in the mail
841 service provided by Google, and thus get heaps of free space. On top
842 of this one can add encryption, RAID and volume management to have
843 lots of (fairly slow, I admit that) cheap and encrypted storage. But
844 I never found time to implement such system. But the last few weeks I
845 have looked at a system called
846 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
847 mounted network backed file system with the features I need.
</p
>
849 <p
>S3QL is a fuse file system with a local cache and cloud storage,
850 handling several different storage providers, any with Amazon S3,
851 Google Drive or OpenStack API. There are heaps of such storage
852 providers. S3QL can also use a local directory as storage, which
853 combined with sshfs allow for file storage on any ssh server. S3QL
854 include support for encryption, compression, de-duplication, snapshots
855 and immutable file systems, allowing me to mount the remote storage as
856 a local mount point, look at and use the files as if they were local,
857 while the content is stored in the cloud as well. This allow me to
858 have a backup that should survive fire. The file system can not be
859 shared between several machines at the same time, as only one can
860 mount it at the time, but any machine with the encryption key and
861 access to the storage service can mount it if it is unmounted.
</p
>
863 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
864 package is included already. So to get started, run
<tt
>apt-get
865 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
866 Greenqloud, after reading their nice recipe on
867 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
868 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
869 in Iceland more than those in USA when it come to keeping my personal
870 data safe and private, and thus would rather spend money on a company
871 in Iceland. Another nice recipe is available from the article
872 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
873 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
874 Admin magazine. When the provider is picked, figure out how to get
875 the API key needed to connect to the storage API. With Greencloud,
876 the key did not show up until I had added payment details to my
879 <p
>Armed with the API access details, it is time to create the file
880 system. First, create a new bucket in the cloud. This bucket is the
881 file system storage area. I picked a bucket name reflecting the
882 machine that was going to store data there, but any name will do.
883 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
884 the API login and password, and a locally created password. Store it
885 all in ~root/.s3ql/authinfo2 like this:
887 <p
><blockquote
><pre
>
889 storage-url: s3c://s.greenqloud.com:
443/bucket-name
890 backend-login: API-login
891 backend-password: API-password
892 fs-passphrase: local-password
893 </pre
></blockquote
></p
>
895 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
896 but any sensible way to create a fairly random password should do it.
897 Armed with these details, it is now time to run mkfs, entering the API
898 details and password to create it:
</p
>
900 <p
><blockquote
><pre
>
901 # mkdir -m
700 /var/lib/s3ql-cache
902 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
903 --ssl s3c://s.greenqloud.com:
443/bucket-name
905 Enter backend password:
906 Before using S3QL, make sure to read the user
's guide, especially
907 the
'Important Rules to Avoid Loosing Data
' section.
908 Enter encryption password:
909 Confirm encryption password:
910 Generating random encryption key...
911 Creating metadata tables...
921 Compressing and uploading metadata...
922 Wrote
0.00 MB of compressed metadata.
923 #
</pre
></blockquote
></p
>
925 <p
>The next step is mounting the file system to make the storage available.
927 <p
><blockquote
><pre
>
928 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
929 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
930 Using
4 upload threads.
931 Downloading and decompressing metadata...
941 Mounting filesystem...
943 Filesystem Size Used Avail Use% Mounted on
944 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
946 </pre
></blockquote
></p
>
948 <p
>The file system is now ready for use. I use rsync to store my
949 backups in it, and as the metadata used by rsync is downloaded at
950 mount time, no network traffic (and storage cost) is triggered by
951 running rsync. To unmount, one should not use the normal umount
952 command, as this will not flush the cache to the cloud storage, but
953 instead running the umount.s3ql command like this:
955 <p
><blockquote
><pre
>
958 </pre
></blockquote
></p
>
960 <p
>There is a fsck command available to check the file system and
961 correct any problems detected. This can be used if the local server
962 crashes while the file system is mounted, to reset the
"already
963 mounted
" flag. This is what it look like when processing a working
964 file system:
</p
>
966 <p
><blockquote
><pre
>
967 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
968 Using cached metadata.
969 File system seems clean, checking anyway.
970 Checking DB integrity...
971 Creating temporary extra indices...
972 Checking lost+found...
973 Checking cached objects...
974 Checking names (refcounts)...
975 Checking contents (names)...
976 Checking contents (inodes)...
977 Checking contents (parent inodes)...
978 Checking objects (reference counts)...
979 Checking objects (backend)...
980 ..processed
5000 objects so far..
981 ..processed
10000 objects so far..
982 ..processed
15000 objects so far..
983 Checking objects (sizes)...
984 Checking blocks (referenced objects)...
985 Checking blocks (refcounts)...
986 Checking inode-block mapping (blocks)...
987 Checking inode-block mapping (inodes)...
988 Checking inodes (refcounts)...
989 Checking inodes (sizes)...
990 Checking extended attributes (names)...
991 Checking extended attributes (inodes)...
992 Checking symlinks (inodes)...
993 Checking directory reachability...
994 Checking unix conventions...
995 Checking referential integrity...
996 Dropping temporary indices...
997 Backing up old metadata...
1007 Compressing and uploading metadata...
1008 Wrote
0.89 MB of compressed metadata.
1010 </pre
></blockquote
></p
>
1012 <p
>Thanks to the cache, working on files that fit in the cache is very
1013 quick, about the same speed as local file access. Uploading large
1014 amount of data is to me limited by the bandwidth out of and into my
1015 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
1016 which is very close to my upload speed, and downloading the same
1017 Debian installation ISO gave me
610 kiB/s, close to my download speed.
1018 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
1019 network, not the file system code. I do not know what a good cache
1020 size would be, but suspect that the cache should e larger than your
1021 working set.
</p
>
1023 <p
>I mentioned that only one machine can mount the file system at the
1024 time. If another machine try, it is told that the file system is
1027 <p
><blockquote
><pre
>
1028 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
1029 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
1030 Using
8 upload threads.
1031 Backend reports that fs is still mounted elsewhere, aborting.
1033 </pre
></blockquote
></p
>
1035 <p
>The file content is uploaded when the cache is full, while the
1036 metadata is uploaded once every
24 hour by default. To ensure the
1037 file system content is flushed to the cloud, one can either umount the
1038 file system, or ask S3QL to flush the cache and metadata using
1041 <p
><blockquote
><pre
>
1042 # s3qlctrl upload-meta /s3ql
1043 # s3qlctrl flushcache /s3ql
1045 </pre
></blockquote
></p
>
1047 <p
>If you are curious about how much space your data uses in the
1048 cloud, and how much compression and deduplication cut down on the
1049 storage usage, you can use s3qlstat on the mounted file system to get
1052 <p
><blockquote
><pre
>
1054 Directory entries:
9141
1057 Total data size:
22049.38 MB
1058 After de-duplication:
21955.46 MB (
99.57% of total)
1059 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
1060 Database size:
2.39 MB (uncompressed)
1061 (some values do not take into account not-yet-uploaded dirty blocks in cache)
1063 </pre
></blockquote
></p
>
1065 <p
>I mentioned earlier that there are several possible suppliers of
1066 storage. I did not try to locate them all, but am aware of at least
1067 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
1068 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
1069 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
1070 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
1071 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
1072 accept payment in Bitcoin. Pick one that suit your need. Some of
1073 them provide several GiB of free storage, but the prize models are
1074 quite different and you will have to figure out what suits you
1077 <p
>While researching this blog post, I had a look at research papers
1078 and posters discussing the S3QL file system. There are several, which
1079 told me that the file system is getting a critical check by the
1080 science community and increased my confidence in using it. One nice
1082 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
1083 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
1084 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
1085 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
1086 and Pamela Smith. Please have a look.
</p
>
1088 <p
>Given my problems with different file systems earlier, I decided to
1089 check out the mounted S3QL file system to see if it would be usable as
1090 a home directory (in other word, that it provided POSIX semantics when
1091 it come to locking and umask handling etc). Running
1092 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
1093 test code to check file system semantics
</a
>, I was happy to discover that
1094 no error was found. So the file system can be used for home
1095 directories, if one chooses to do so.
</p
>
1097 <p
>If you do not want a locally file system, and want something that
1098 work without the Linux fuse file system, I would like to mention the
1099 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
1100 provide locally encrypted backup using a command line client. It have
1101 a nicer access control system, where one can split out read and write
1102 access, allowing some systems to write to the backup and others to
1103 only read from it.
</p
>
1105 <p
>As usual, if you use Bitcoin and want to show your support of my
1106 activities, please send Bitcoin donations to my address
1107 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1112 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
1113 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
1114 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
1115 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
1116 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
1117 project
</a
> is working on providing the software and hardware for
1118 making it easy for non-technical people to host their data and
1119 communication at home, and being able to communicate with their
1120 friends and family encrypted and away from prying eyes. It has been
1121 going on for a while, and is slowly progressing towards a new test
1122 release (
0.2).
</p
>
1124 <p
>And what day could be better than the Pi day to announce that the
1125 new version will provide
"hard drive
" / SD card / USB stick images for
1126 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1127 system), and can also be installed using a Debian installer preseed
1128 file. The Debian based Freedombox is now based on Debian Jessie,
1129 where most of the needed packages used are already present. Only one,
1130 the freedombox-setup package, is missing. To try to build your own
1131 boot image to test the current status, fetch the freedom-maker scripts
1133 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
1134 with a user with sudo access to become root:
1137 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1139 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1140 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1142 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1145 <p
>Root access is needed to run debootstrap and mount loopback
1146 devices. See the README for more details on the build. If you do not
1147 want all three images, trim the make line. But note that thanks to
<a
1148 href=
"https://bugs.debian.org/
741407">a race condition in
1149 vmdebootstrap
</a
>, the build might fail without the patch to the
1150 kpartx call.
</p
>
1152 <p
>If you instead want to install using a Debian CD and the preseed
1153 method, boot a Debian Wheezy ISO and use this boot argument to load
1154 the preseed values:
</p
>
1157 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
1160 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
1161 recently introduced bug in apt in Jessie
</a
>, the installer will
1162 currently hang while setting up APT sources. Killing the
1163 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
1164 installation will get the installation going. This affect all
1165 installations in Jessie, and I expect it will be fixed soon.
</p
>
1167 <p
>Give it a go and let us know how it goes on the mailing list, and help
1168 us get the new release published. :) Please join us on
1169 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
1170 irc.debian.org)
</a
> and
1171 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1172 mailing list
</a
> if you want to help make this vision come true.
</p
>
1177 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
1178 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
1179 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
1180 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
1181 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
1182 innetgr tools, because I needed them in
1183 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
1184 ng-utils, and it has served me well. I placed the project under the
1185 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
1186 repository. But many years ago, the CVS repository was dropped (lost,
1187 not migrated to new hardware, not sure), and the project have lacked a
1188 proper home since then.
</p
>
1190 <p
>Last summer, I had a look at the package and made a new release
1191 fixing a irritating crash bug, but was unable to store the changes in
1192 a proper source control system. I applied for a project on
1193 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
1194 to follow up on it. Until today. :)
</p
>
1196 <p
>After many hours of cleaning and migration, the ng-utils project
1197 now have a new home, and a git repository with the highlight of the
1198 history of the project. I published all release tarballs and imported
1199 them into the git repository. As the project is really stable and not
1200 expected to gain new features any time soon, I decided to make a new
1201 release and call it
1.0. Visit the new project home on
1202 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
1203 if you want to check it out. The new version is also uploaded into
1204 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
1209 <title>Testing sysvinit from experimental in Debian Hurd
</title>
1210 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
1211 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
1212 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
1213 <description><p
>A few days ago I decided to try to help the Hurd people to get
1214 their changes into sysvinit, to allow them to use the normal sysvinit
1215 boot system instead of their old one. This follow up on the
1216 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
1217 Google Summer of Code work
</a
> done last summer by Justus Winter to
1218 get Debian on Hurd working more like Debian on Linux. To get started,
1219 I downloaded a prebuilt hard disk image from
1220 <a href=
"http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz
">http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz
</a
>,
1221 and started it using virt-manager.
</p
>
1223 <p
>The first think I had to do after logging in (root without any
1224 password) was to get the network operational. I followed
1225 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
1226 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
1227 commands as root to get the machine to accept a IP address from the
1228 kvm internal DHCP server:
</p
>
1230 <p
><blockquote
><pre
>
1231 settrans -fgap /dev/netdde /hurd/netdde
1232 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
1233 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
1235 </pre
></blockquote
></p
>
1237 <p
>After this, the machine had internet connectivity, and I could
1238 upgrade it and install the sysvinit packages from experimental and
1239 enable it as the default boot system in Hurd.
</p
>
1241 <p
>But before I did that, I set a password on the root user, as ssh is
1242 running on the machine it for ssh login to work a password need to be
1243 set. Also, note that a bug somewhere in openssh on Hurd block
1244 compression from working. Remember to turn that off on the client
1247 <p
>Run these commands as root to upgrade and test the new sysvinit
1250 <p
><blockquote
><pre
>
1251 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
1252 deb http://http.debian.net/debian/ experimental main
1255 apt-get dist-upgrade
1256 apt-get install -t experimental initscripts sysv-rc sysvinit \
1257 sysvinit-core sysvinit-utils
1258 update-alternatives --config runsystem
1259 </pre
></blockquote
></p
>
1261 <p
>To reboot after switching boot system, you have to use
1262 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
1263 yet a sysvinit process able to receive the signals from the normal
1264 'reboot
' command. After switching to sysvinit as the boot system,
1265 upgrading every package and rebooting, the network come up with DHCP
1266 after boot as it should, and the settrans/pkill hack mentioned at the
1267 start is no longer needed. But for some strange reason, there are no
1268 longer any login prompt in the virtual console, so I logged in using
1271 <p
>Note that there are some race conditions in Hurd making the boot
1272 fail some times. No idea what the cause is, but hope the Hurd porters
1273 figure it out. At least Justus said on IRC (#debian-hurd on
1274 irc.debian.org) that they are aware of the problem. A way to reduce
1275 the impact is to upgrade to the Hurd packages built by Justus by
1276 adding this repository to the machine:
</p
>
1278 <p
><blockquote
><pre
>
1279 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
1280 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1282 </pre
></blockquote
></p
>
1284 <p
>At the moment the prebuilt virtual machine get some packages from
1285 http://ftp.debian-ports.org/debian, because some of the packages in
1286 unstable do not yet include the required patches that are lingering in
1287 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
1289 <p
><blockquote
><pre
>
1290 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
1291 i emacs - GNU Emacs editor (metapackage)
1292 i gdb - GNU Debugger
1293 i hurd-recommended - Miscellaneous translators
1294 i isc-dhcp-client - ISC DHCP client
1295 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1296 i libc-bin - Embedded GNU C Library: Binaries
1297 i libc-dev-bin - Embedded GNU C Library: Development binaries
1298 i libc0.3 - Embedded GNU C Library: Shared libraries
1299 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1300 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1301 i multiarch-support - Transitional package to ensure multiarch compatibilit
1302 i A x11-common - X Window System (X.Org) infrastructure
1303 i xorg - X.Org X Window System
1304 i A xserver-xorg - X.Org X server
1305 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1307 </pre
></blockquote
></p
>
1309 <p
>All in all, testing hurd has been an interesting experience. :)
1310 X.org did not work out of the box and I never took the time to follow
1311 the porters instructions to fix it. This time I was interested in the
1312 command line stuff.
<p
>
1317 <title>New chrpath release
0.16</title>
1318 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
1319 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
1320 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
1321 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
1322 find problems in C, C++ and Java code using static source code
1323 analysis. It can detect a lot of different problems, and is very
1324 useful to find memory and locking bugs in the error handling part of
1325 the source. The company behind it provide
1326 <a href=
"https://scan.coverity.com/
">check of free software projects as
1327 a community service
</a
>, and many hundred free software projects are
1328 already checked. A few days ago I decided to have a closer look at
1329 the Coverity system, and discovered that the
1330 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
1331 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
1332 projects I am involved with was already registered. But these are
1333 fairly big, and I would also like to have a small and easy project to
1334 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
1335 checking of the chrpath project
</a
>. It was
1336 added to the checker and discovered seven potential defects. Six of
1337 these were real, mostly resource
"leak
" when the program detected an
1338 error. Nothing serious, as the resources would be released a fraction
1339 of a second later when the program exited because of the error, but it
1340 is nice to do it right in case the source of the program some time in
1341 the future end up in a library. Having fixed all defects and added
1342 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
1343 mailing list for the chrpath developers
</a
>, I decided it was time to
1344 publish a new release. These are the release notes:
</p
>
1346 <p
>New in
0.16 released
2014-
01-
14:
</p
>
1350 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
1351 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
1352 <li
>Mention new project mailing list in the documentation.
</li
>
1357 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1358 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
1359 project if something is wrong with the new release. The test suite
1360 did not discover any old errors, so if you find a new one, please also
1361 include a test suite check.
</p
>
1366 <title>New chrpath release
0.15</title>
1367 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
1368 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
1369 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
1370 <description><p
>After many years break from the package and a vain hope that
1371 development would be continued by someone else, I finally pulled my
1372 acts together this morning and wrapped up a new release of chrpath,
1373 the command line tool to modify the rpath and runpath of already
1374 compiled ELF programs. The update was triggered by the persistence of
1375 Isha Vishnoi at IBM, which needed a new config.guess file to get
1376 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
1377 is working on. I checked the
1378 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
1379 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
1380 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
1381 packages for interesting patches (failed to find the source from
1382 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1383 These are the release notes:
</p
>
1385 <p
>New in
0.15 released
2013-
11-
24:
</p
>
1389 <li
>Updated config.sub and config.guess from the GNU project to work
1390 with newer architectures. Thanks to isha vishnoi for the heads
1393 <li
>Updated README with current URLs.
</li
>
1395 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1396 Matthias Klose.
</li
>
1398 <li
>Added missing help for -k|--keepgoing option, using patch by
1399 Petr Machata found in Fedora.
</li
>
1401 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
1402 .dynamic is a NULL terminated string. Based on patch found in
1403 Fedora credited Axel Thimm and Christian Krause.
</li
>
1408 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
1409 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
1410 project if something is wrong with the new release. The test suite
1411 did not discover any old errors, so if you find a new one, please also
1412 include a testsuite check.
</p
>
1417 <title>Debian init.d boot script example for rsyslog
</title>
1418 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
1419 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
1420 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
1421 <description><p
>If one of the points of switching to a new init system in Debian is
1422 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
1423 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
1424 init.d scripts at all. Here is an example init.d script, ie a rewrite
1425 of /etc/init.d/rsyslog:
</p
>
1427 <p
><pre
>
1428 #!/lib/init/init-d-script
1431 # Required-Start: $remote_fs $time
1432 # Required-Stop: umountnfs $time
1433 # X-Stop-After: sendsigs
1434 # Default-Start:
2 3 4 5
1435 # Default-Stop:
0 1 6
1436 # Short-Description: enhanced syslogd
1437 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1438 # It is quite compatible to stock sysklogd and can be
1439 # used as a drop-in replacement.
1441 DESC=
"enhanced syslogd
"
1442 DAEMON=/usr/sbin/rsyslogd
1443 </pre
></p
>
1445 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
1446 script was
137 lines, and the above is just
15 lines, most of it meta
1447 info/comments.
</p
>
1449 <p
>How to do this, you ask? Well, one create a new script
1450 /lib/init/init-d-script looking something like this:
1452 <p
><pre
>
1455 # Define LSB log_* functions.
1456 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
1457 # and status_of_proc is working.
1458 . /lib/lsb/init-functions
1461 # Function that starts the daemon/service
1467 #
0 if daemon has been started
1468 #
1 if daemon was already running
1469 #
2 if daemon could not be started
1470 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
1472 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1475 # Add code here, if necessary, that waits for the process to be ready
1476 # to handle requests from services started subsequently which depend
1477 # on this one. As a last resort, sleep for some time.
1481 # Function that stops the daemon/service
1486 #
0 if daemon has been stopped
1487 #
1 if daemon was already stopped
1488 #
2 if daemon could not be stopped
1489 # other if a failure occurred
1490 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
1491 RETVAL=
"$?
"
1492 [
"$RETVAL
" =
2 ]
&& return
2
1493 # Wait for children to finish too if this is a daemon that forks
1494 # and if the daemon is only ever run from this initscript.
1495 # If the above conditions are not satisfied then add some other code
1496 # that waits for the process to drop all resources that could be
1497 # needed by services started subsequently. A last resort is to
1498 # sleep for some time.
1499 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
1500 [
"$?
" =
2 ]
&& return
2
1501 # Many daemons don
't delete their pidfiles when they exit.
1503 return
"$RETVAL
"
1507 # Function that sends a SIGHUP to the daemon/service
1511 # If the daemon can reload its configuration without
1512 # restarting (for example, when it is sent a SIGHUP),
1513 # then implement that here.
1515 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
1520 scriptbasename=
"$(basename $
1)
"
1521 echo
"SN: $scriptbasename
"
1522 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
1523 script=
"$
1"
1530 NAME=$(basename $DAEMON)
1531 PIDFILE=/var/run/$NAME.pid
1533 # Exit if the package is not installed
1534 #[ -x
"$DAEMON
" ] || exit
0
1536 # Read configuration variable file if it is present
1537 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
1539 # Load the VERBOSE setting and other rcS variables
1542 case
"$
1" in
1544 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
1546 case
"$?
" in
1547 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1548 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1552 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
1554 case
"$?
" in
1555 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
1556 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
1560 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
1562 #reload|force-reload)
1564 # If do_reload() is not implemented then leave this commented out
1565 # and leave
'force-reload
' as an alias for
'restart
'.
1567 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
1571 restart|force-reload)
1573 # If the
"reload
" option is implemented then remove the
1574 #
'force-reload
' alias
1576 log_daemon_msg
"Restarting $DESC
" "$NAME
"
1578 case
"$?
" in
1581 case
"$?
" in
1583 1) log_end_msg
1 ;; # Old process is still running
1584 *) log_end_msg
1 ;; # Failed to start
1594 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
1600 </pre
></p
>
1602 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
1603 lot. I did not really polish the approach, so it might not always
1604 work out of the box, but you get the idea. I did not try very hard to
1605 optimize it nor make it more robust either.
</p
>
1607 <p
>A better argument for switching init system in Debian than reducing
1608 the size of init scripts (which is a good thing to do anyway), is to
1609 get boot system that is able to handle the kernel events sensibly and
1610 robustly, and do not depend on the boot to run sequentially. The boot
1611 and the kernel have not behaved sequentially in years.
</p
>
1616 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
1617 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
1618 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
1619 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
1620 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
1621 remote display access is the preferred solution with oVirt and RedHat
1622 Enterprise Virtualization, and I was sad to discover the other day
1623 that the browser plugin needed to use these systems seamlessly was
1624 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
1625 for a package
</a
> was from
2012-
04-
10 with no progress since
1626 2013-
04-
01, so I decided to wrap up a package based on the great work
1627 from Cajus Pollmeier and put it in a collab-maint maintained git
1628 repository to get a package I could use. I would very much like
1629 others to help me maintain the package (or just take over, I do not
1630 mind), but as no-one had volunteered so far, I just uploaded it to
1631 NEW. I hope it will be available in Debian in a few days.
</p
>
1633 <p
>The source is now available from
1634 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
">http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
</a
>.
</p
>
1639 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
1640 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
1641 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
1642 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
1643 <description><p
>The
1644 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
1645 program is a a very nice system to create virtual machine images. It
1646 create a image file, add a partition table, mount it and run
1647 debootstrap in the mounted directory to create a Debian system on a
1648 stick. Yesterday, I decided to try to teach it how to make images for
1649 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
1650 of a plan to simplify the build system for
1651 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
1652 project
</a
>. The FreedomBox project already uses vmdebootstrap for
1653 the virtualbox images, but its current build system made multistrap
1654 based system for Dreamplug images, and it is lacking support for
1655 Raspberry Pi.
</p
>
1657 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
1658 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1659 code and adjusted it to be able to build armel images on my amd64
1660 Debian laptop. I ended up giving vmdebootstrap five new options,
1661 allowing me to replicate the image creation process I use to make
1662 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
1663 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
1664 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
1665 call debootstrap with --foreign and to copy the handler into the
1666 generated chroot before running the second stage. This allow
1667 vmdebootstrap to create armel images on an amd64 host. Next I added
1668 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
1669 fstype
</tt
> to teach it to create a separate /boot/ partition with the
1670 given file system type, allowing me to create an image with a vfat
1671 partition for the /boot/ stuff. I also added a
<tt
>--variant
1672 variant
</tt
> option to allow me to create smaller images without the
1673 Debian base system packages installed. Finally, I added an option
1674 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
1675 as a boot loader. It is not needed on the Raspberry Pi and probably
1676 most other non-x86 architectures. The changes were accepted by the
1677 upstream author of vmdebootstrap yesterday and today, and is now
1679 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
1680 upstream project page
</a
>.
</p
>
1682 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
1683 create a small script (the customize script) to add the non-free
1684 binary blob needed to boot the Raspberry Pi and the APT source
1687 <p
><pre
>
1689 set -e # Exit on first error
1690 rootdir=
"$
1"
1691 cd
"$rootdir
"
1692 cat
&lt;
&lt;EOF
> etc/apt/sources.list
1693 deb http://http.debian.net/debian/ jessie main contrib non-free
1695 # Install non-free binary blob needed to boot Raspberry Pi. This
1696 # install a kernel somewhere too.
1697 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1698 -O $rootdir/usr/bin/rpi-update
1699 chmod a+x $rootdir/usr/bin/rpi-update
1700 mkdir -p $rootdir/lib/modules
1701 touch $rootdir/boot/start.elf
1702 chroot $rootdir rpi-update
1703 </pre
></p
>
1705 <p
>Next, fetch the latest vmdebootstrap script and call it like this
1706 to build the image:
</p
>
1709 sudo ./vmdebootstrap \
1712 --distribution jessie \
1713 --mirror http://http.debian.net/debian \
1722 --root-password raspberry \
1723 --hostname raspberrypi \
1724 --foreign /usr/bin/qemu-arm-static \
1725 --customize `pwd`/customize \
1727 --package git-core \
1728 --package binutils \
1729 --package ca-certificates \
1732 </pre
></p
>
1734 <p
>The list of packages being installed are the ones needed by
1735 rpi-update to make the image bootable on the Raspberry Pi, with the
1736 exception of netbase, which is needed by debootstrap to find
1737 /etc/hosts with the minbase variant. I really wish there was a way to
1738 set up an Raspberry Pi using only packages in the Debian archive, but
1739 that is not possible as far as I know, because it boots from the GPU
1740 using a non-free binary blob.
</p
>
1742 <p
>The build host need debootstrap, kpartx and qemu-user-static and
1743 probably a few others installed. I have not checked the complete
1744 build dependency list.
</p
>
1746 <p
>The resulting image will not use the hardware floating point unit
1747 on the Raspberry PI, because the armel architecture in Debian is not
1748 optimized for that use. So the images created will be a bit slower
1749 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
1754 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
1755 <link>http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</link>
1756 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html
</guid>
1757 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
1758 <description><p
>The last few days I came across a few good causes that should get
1759 wider attention. I recommend signing and donating to each one of
1762 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
1763 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
1764 Women program which is a Google Summer of Code like initiative to get
1765 more women involved in free software. One debian sponsor has offered
1766 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
1767 earmarked
</a
> for this initiative. I donated a few minutes ago, and
1768 hope you will to. :)
</p
>
1770 <p
>And the Electronic Frontier Foundation just announced plans to
1771 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
1772 documentaries about the excessive spying
</a
> on every Internet user that
1773 take place these days, and their need to fund the work. I
've already
1774 donated. Are you next?
</p
>
1776 <p
>For my Norwegian audience, the organisation Studentenes og
1777 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1778 statement under the heading
1779 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
1780 Access
</a
> for those of us asking for more focus on open access in the
1781 Norwegian government. So far
499 signatures. I hope you will sign it
1787 <title>Videos about the Freedombox project - for inspiration and learning
</title>
1788 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
1789 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
1790 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
1791 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
1792 project
</a
> have been going on for a while, and have presented the
1793 vision, ideas and solution several places. Here is a little
1794 collection of videos of talks and presentation of the project.
</p
>
1798 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
1799 2,
5 minute marketing film
</a
> (Youtube)
</li
>
1801 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
1802 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
1804 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
1805 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1806 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
1807 (Youtube)
</li
>
1809 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
1810 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
1812 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
1813 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
1815 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
1816 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1817 York City in
2012</a
> (Youtube)
</li
>
1819 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
1820 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
1821 (Youtube)
</li
>
1823 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
1824 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
1826 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
1827 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
1829 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
1830 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1831 2013</a
> (Youtube)
</li
>
1835 <p
>A larger list is available from
1836 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
1837 Freedombox Wiki
</a
>.
</p
>
1839 <p
>On other news, I am happy to report that Freedombox based on Debian
1840 Jessie is coming along quite well, and soon both Owncloud and using
1841 Tor should be available for testers of the Freedombox solution. :) In
1842 a few weeks I hope everything needed to test it is included in Debian.
1843 The withsqlite package is already in Debian, and the plinth package is
1844 pending in NEW. The third and vital part of that puzzle is the
1845 metapackage/setup framework, which is still pending an upload. Join
1846 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
1847 (#freedombox on irc.debian.org)
</a
> and
1848 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
1849 mailing list
</a
> if you want to help make this vision come true.
</p
>
1854 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
1855 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
1856 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
1857 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
1858 <description><p
>I was introduced to the
1859 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
1860 in
2010, when Eben Moglen presented his vision about serving the need
1861 of non-technical people to keep their personal information private and
1862 within the legal protection of their own homes. The idea is to give
1863 people back the power over their network and machines, and return
1864 Internet back to its intended peer-to-peer architecture. Instead of
1865 depending on a central service, the Freedombox will give everyone
1866 control over their own basic infrastructure.
</p
>
1868 <p
>I
've intended to join the effort since then, but other tasks have
1869 taken priority. But this summers nasty news about the misuse of trust
1870 and privilege exercised by the
"western
" intelligence gathering
1871 communities increased my eagerness to contribute to a point where I
1872 actually started working on the project a while back.
</p
>
1874 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
1875 Debian initiative
</a
> based on the vision from Eben Moglen, is to
1876 create a simple and cheap Debian based appliance that anyone can hook
1877 up in their home and get access to secure and private services and
1878 communication. The initial deployment platform have been the
1879 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
1880 which is a piece of hardware I do not own. So to be able to test what
1881 the current Freedombox setup look like, I had to come up with a way to install
1882 it on some hardware I do have access to. I have rewritten the
1883 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
1884 image build framework to use .deb packages instead of only copying
1885 setup into the boot images, and thanks to this rewrite I am able to
1886 set up any machine supported by Debian Wheezy as a Freedombox, using
1887 the previously mentioned deb (and a few support debs for packages
1888 missing in Debian).
</p
>
1890 <p
>The current Freedombox setup consist of a set of bootstrapping
1892 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
1893 and a administrative web interface
1894 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
1895 withsqlite), as well as a privacy enhancing proxy based on
1896 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
1897 (freedombox-privoxy). There is also a web/javascript based XMPP
1898 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
1899 trying (unsuccessfully so far) to talk to the XMPP server
1900 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
1901 web interface is pluggable, and the goal is to use it to enable OpenID
1902 services, mesh network connectivity, use of TOR, etc, etc. Not much of
1903 this is really working yet, see
1904 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
1905 project TODO
</a
> for links to GIT repositories. Most of the code is
1906 on github at the moment. The HTTP proxy is operational out of the
1907 box, and the admin web interface can be used to add/remove plinth
1908 users. I
've not been able to do anything else with it so far, but
1909 know there are several branches spread around github and other places
1910 with lots of half baked features.
</p
>
1912 <p
>Anyway, if you want to have a look at the current state, the
1913 following recipes should work to give you a test machine to poke
1916 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
1920 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
1921 <li
>Boot from it, either as CD or USB stick.
</li
>
1922 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
1923 to the Debian installer:
<p
>
1924 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
1926 <li
>Answer the few language/region/password questions and pick disk to
1927 install on.
</li
>
1929 <li
>When the installation is finished and the machine have rebooted a
1930 few times, your Freedombox is ready for testing.
</li
>
1934 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
1938 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
1939 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
1940 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
1942 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
1943 </pre
></li
>
1944 <li
><p
>Run this as root:
</p
>
1946 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
1949 apt-get install freedombox-setup
1950 /usr/lib/freedombox/setup
1951 </pre
></li
>
1952 <li
>Reboot into your freshly created Freedombox.
</li
>
1956 <p
>You can test it on other architectures too, but because the
1957 freedombox-privoxy package is binary, it will only work as intended on
1958 the architectures where I have had time to build the binary and put it
1959 in my APT repository. But do not let this stop you. It is only a
1960 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
1962 <p
>Note that by default Freedombox is a DHCP server on the
1963 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
1964 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
1965 disable
</tt
>" as root.
</p
>
1967 <p
>Please let me know if this works for you, or if you have any
1968 problems. We gather on the IRC channel
1969 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
1970 irc.debian.org and the
1971 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
1972 mailing list
</a
>.
</p
>
1974 <p
>Once you get your freedombox operational, you can visit
1975 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
1976 welcome screen (dead end - do not be surprised if you are unable to
1977 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
1978 to look at the rest of plinth. The default user is
'admin
' and the
1979 default password is
'secret
'.
</p
>
1984 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
1985 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
1986 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
1987 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
1988 <description><p
>Earlier, I reported about
1989 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
1990 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
1991 told by IBM that the original disk should be thrown away. And as
1992 there no longer was a problem if I bricked the firmware, I decided
1993 today to try to install Intel firmware to replace the Lenovo firmware
1994 currently on the disk.
</p
>
1996 <p
>I searched the Intel site for firmware, and found
1997 <a href=
"https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y
&ProdId=
3472&DwnldID=
18363&ProductFamily=Solid-State+Drives+and+Caching
&ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive
&ProductProduct=Intel%c2%ae+SSD+
520+Series+(
180GB%
2c+
2.5in+SATA+
6Gb%
2fs%
2c+
25nm%
2c+MLC)
&lang=eng
">issdfut_2.0
.4.iso
</a
>
1998 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
1999 according to the site should contain the latest firmware for SSD
2000 disks. I inserted the broken disk in one of my spare laptops and
2001 booted the ISO from a USB stick. The disk was recognized, but the
2002 program claimed the newest firmware already were installed and refused
2003 to insert any Intel firmware. So no change, and the disk is still
2004 unable to handle write load. :( I guess the only way to get them
2005 working would be if Lenovo releases new firmware. No idea how likely
2006 that is. Anyway, just blogging about this test for completeness. I
2007 got a working Samsung disk, and see no point in spending more time on
2008 the broken disks.
</p
>
2013 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
2014 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
2015 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
2016 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
2017 <description><p
>Today I switched to
2018 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
2019 new laptop
</a
>. I
've previously written about the problems I had with
2020 my new Thinkpad X230, which was delivered with an
2021 <a href=
"http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
">180
2022 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
2023 sustained writes. My hardware supplier have been very forthcoming in
2024 trying to find a solution, and after first trying with another
2025 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
2026 disk instead to fix it once and for all. The Samsung disk survived
2027 the installation of Debian with encrypted disks (filling the disk with
2028 random data during installation killed the first two), and I thus
2029 decided to trust it with my data. I have installed it as a Debian Edu
2030 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
2031 server at home using Kerberos and LDAP, and will use it as my work
2032 station from now on.
</p
>
2034 <p
>As this is a solid state disk with no moving parts, I believe the
2035 Debian Wheezy default installation need to be tuned a bit to increase
2036 performance and increase life time of the disk. The Linux kernel and
2037 user space applications do not yet adjust automatically to such
2038 environment. To make it easier for my self, I created a draft Debian
2039 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
2040 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
2041 for the ssd-setup package
</a
> is available from collab-maint, and it
2042 is set up to adjust the setup of the machine by just installing the
2043 package. If there is any non-SSD disk in the machine, the package
2044 will refuse to install, as I did not try to write any logic to sort
2045 file systems in SSD and non-SSD file systems.
</p
>
2047 <p
>I consider the package a draft, as I am a bit unsure how to best
2048 set up Debian Wheezy with an SSD. It is adjusted to my use case,
2049 where I set up the machine with one large encrypted partition (in
2050 addition to /boot), put LVM on top of this and set up partitions on
2051 top of this again. See the README file in the package source for the
2052 references I used to pick the settings. At the moment these
2053 parameters are tuned:
</p
>
2057 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
2058 (adding discard to /etc/crypttab)
</li
>
2060 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
2061 this case a cryptsetup partition) by changing issue_discards from
2062 0 to
1 in /etc/lvm/lvm.conf.
</li
>
2064 <li
>Set relatime as a file system option for ext3 and ext4 file
2067 <li
>Tell swap to use TRIM commands by adding
'discard
' to
2068 /etc/fstab.
</li
>
2070 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
2072 <li
>Run fstrim on every ext3 and ext4 file system every night (from
2073 cron.daily).
</li
>
2075 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
2076 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
2080 <p
>During installation, I cancelled the part where the installer fill
2081 the disk with random data, as this would kill the SSD performance for
2082 little gain. My goal with the encrypted file system is to ensure
2083 those stealing my laptop end up with a brick and not a working
2084 computer. I have no hope in keeping the really resourceful people
2085 from getting the data on the disk (see
2086 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
2087 Thus I concluded that adding the discard option to crypttab is the
2088 right thing to do.
</p
>
2090 <p
>I considered using the noop I/O scheduler, as several recommended
2091 it for SSD, but others recommended deadline and a benchmark I found
2092 indicated that deadline might be better for interactive use.
</p
>
2094 <p
>I also considered using the
'discard
' file system option for ext3
2095 and ext4, but read that it would give a performance hit ever time a
2096 file is removed, and thought it best to that that slowdown once a day
2097 instead of during my work.
</p
>
2099 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
2100 this is already done by Debian Edu.
</p
>
2102 <p
>I have not yet started on the user space tuning. I expect
2103 iceweasel need some tuning, and perhaps other applications too, but
2104 have not yet had time to investigate those parts.
</p
>
2106 <p
>The package should work on Ubuntu too, but I have not yet tested it
2109 <p
>As for the answer to the question in the title of this blog post,
2110 as far as I know, the only solution I know about is to replace the
2111 disk. It might be possible to flash it with Intel firmware instead of
2112 the Lenovo firmware. But I have not tried and did not want to do so
2113 without approval from Lenovo as I wanted to keep the warranty on the
2114 disk until a solution was found and they wanted the broken disks
2120 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
2121 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
2122 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</guid>
2123 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
2124 <description><p
>A few days ago, I wrote about
2125 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
2126 problems I experienced with my new X230 and its SSD disk
</a
>, which
2127 was dying during installation because it is unable to cope with
2128 sustained write. My supplier is in contact with
2129 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
2130 replacement disk to try to fix the problem. They decided to send an
2131 identical model, so my hopes for a permanent fix was slim.
</p
>
2133 <p
>Anyway, today I got the replacement disk and tried to install
2134 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2135 same firmware version as the original. This time my hope raised
2136 slightly as the installation progressed, as the original disk used to
2137 die after
4-
7% of the disk was written to, while this time it kept
2138 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
2139 died again and I was back on square one. I still do not have a new
2140 laptop with a disk I can trust. I can not live with a disk that might
2141 lock up when I download a new
2142 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
2143 other large files. I look forward to hearing from my supplier with
2144 the next proposal from Lenovo.
</p
>
2146 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
2147 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2148 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2149 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
2150 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2151 P/N
45N8295, P0C38732.
</p
>
2153 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
2154 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
2155 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
2156 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
2157 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
2158 P/N
45N8295, P0C38732.
</p
>
2160 <p
>The only difference is in the first number (serial number?), ISN,
2161 SA, date and WNPP values. Mentioning all the details here in case
2162 someone is able to use the information to find a way to identify the
2163 failing disk among working ones (if any such working disk actually
2169 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
2170 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
2171 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
2172 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
2173 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
2174 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2175 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
2176 member assosiation NUUG
</a
> and
2177 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
2178 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
2179 Bitraf
</a
>.
</p
>
2181 <p
>It starts
10:
00 and continue until late evening. Everyone is
2182 welcome, and there is no fee to participate. There is on the other
2183 hand limited space, and only room for
30 people. Please put your name
2184 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
2185 wiki page
</a
> if you plan to join us.
</p
>
2190 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
2191 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
2192 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
2193 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
2194 <description><p
>Half a year ago, I reported that I had to find a
2195 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
2196 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
2197 time to spend on it, and it took a while to find a model I believe
2198 will do the job, but two days ago the replacement finally arrived. I
2200 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
2201 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2202 a roaming workstation, and it seemed to work flawlessly. But my
2203 second installation with encrypted disk was not as successful. More
2204 on that below.
</p
>
2206 <p
>I had a hard time trying to track down a good laptop, as my most
2207 important requirements (robust and with a good keyboard) are never
2208 listed in the feature list. But I did get good help from the search
2209 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2210 allowed me to limit the list of interesting laptops based on my other
2211 requirements. A bit surprising that SSD disk are not disks according
2212 to that search interface, so I had to drop specifying the number of
2213 disks from my search parameters. I also asked around among friends to
2214 get their impression on keyboards and robustness.
</p
>
2216 <p
>So the new laptop arrived, and it is quite a lot wider than the
2217 X41. I am not quite convinced about the keyboard, as it is
2218 significantly wider than my old keyboard, and I have to stretch my
2219 hand a lot more to reach the edges. But the key response is fairly
2220 good and the individual key shape is fairly easy to handle, so I hope
2221 I will get used to it. My old X40 was starting to fail, and I really
2222 needed a new laptop now. :)
</p
>
2224 <p
>Turning off the touch pad was simple. All it took was a quick
2225 visit to the BIOS during boot it disable it.
</p
>
2227 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
2228 lock up during load. And this happen when installing Debian Wheezy
2229 with encrypted disk, while the disk is being filled with random data.
2230 I also tested to install Ubuntu Raring, and it happen there too if I
2231 reenable the code to fill the disk with random data (it is disabled by
2232 default in Ubuntu). And the bug with is already known. It was
2233 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
2234 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
2235 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2236 kernel developers as
2237 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
2238 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
2239 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2240 Lenovo forums, both for
2241 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
2242 2012-
11-
10</a
> and for
2243 <a href=
"http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/x230-SATA-errors-with-
180GB-Intel-
520-SSD-under-heavy-write-load/m-p/
1068147">X230
2244 03-
20-
2013</a
>. The problem do not only affect installation. The
2245 reports state that the disk lock up during use if many writes are done
2246 on the disk, so it is much no use to work around the installation
2247 problem and end up with a computer that can lock up at any moment.
2249 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
2250 available
</a
> that will lock up the hard drive after running a few
2251 minutes by writing to a file.
</p
>
2253 <p
>I
've contacted my supplier and asked how to handle this, and after
2254 contacting PCHELP Norway (request
01D1FDP) which handle support
2255 requests for Lenovo, his first suggestion was to upgrade the disk
2256 firmware. Unfortunately there is no newer firmware available from
2257 Lenovo, as my disk already have the most recent one (version LF1i). I
2258 hope to hear more from him today and hope the problem can be
2264 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
2265 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
2266 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
2267 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
2268 <description><p
>Half a year ago, I reported that I had to find a replacement for my
2269 trusty old Thinkpad X41. Unfortunately I did not have much time to
2270 spend on it, but today the replacement finally arrived. I ended up
2271 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
2272 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
2273 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2274 this, it is installing what I hope will be a more final installation,
2275 with a encrypted hard drive to ensure any dope head stealing it end up
2276 with an expencive door stop.
</p
>
2278 <p
>I had a hard time trying to track down a good laptop, as my most
2279 important requirements (robust and with a good keyboard) are never
2280 listed in the feature list. But I did get good help from the search
2281 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
2282 allowed me to limit the list of interesting laptops based on my other
2283 requirements. A bit surprising that SSD disk are not disks, so I had
2284 to drop number of disks from my search parameters.
</p
>
2286 <p
>I am not quite convinced about the keyboard, as it is significantly
2287 wider than my old keyboard, and I have to stretch my hand a lot more
2288 to reach the edges. But the key response is fairly good and the
2289 individual key shape is fairly easy to handle, so I hope I will get
2290 used to it. My old X40 was starting to fail, and I really needed a
2291 new laptop now. :)
</p
>
2293 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
2298 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
2299 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
2300 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
2301 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
2302 <description><p
>It annoys me when the computer fail to do automatically what it is
2303 perfectly capable of, and I have to do it manually to get things
2304 working. One such task is to find out what firmware packages are
2305 needed to get the hardware on my computer working. Most often this
2306 affect the wifi card, but some times it even affect the RAID
2307 controller or the ethernet card. Today I pushed version
0.4 of the
2308 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
2309 including a new script isenkram-autoinstall-firmware handling the
2310 process of asking all the loaded kernel modules what firmware files
2311 they want, find debian packages providing these files and install the
2312 debian packages. Here is a test run on my laptop:
</p
>
2314 <p
><pre
>
2315 # isenkram-autoinstall-firmware
2316 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2317 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2318 info: locating packages with the requested firmware files
2319 info: Updating APT sources after adding non-free APT source
2320 info: trying to install firmware-ipw2x00
2323 Preconfiguring packages ...
2324 Selecting previously deselected package firmware-ipw2x00.
2325 (Reading database ...
259727 files and directories currently installed.)
2326 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2327 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
2329 </pre
></p
>
2331 <p
>When all the requested firmware is present, a simple message is
2332 printed instead:
</p
>
2334 <p
><pre
>
2335 # isenkram-autoinstall-firmware
2336 info: did not find any firmware files requested by loaded kernel modules. exiting
2338 </pre
></p
>
2340 <p
>It could use some polish, but it is already working well and saving
2341 me some time when setting up new machines. :)
</p
>
2343 <p
>So, how does it work? It look at the set of currently loaded
2344 kernel modules, and look up each one of them using modinfo, to find
2345 the firmware files listed in the module meta-information. Next, it
2346 download the Contents file from a nearby APT mirror, and search for
2347 the firmware files in this file to locate the package with the
2348 requested firmware file. If the package is in the non-free section, a
2349 non-free APT source is added and the package is installed using
2350 <tt
>apt-get install
</tt
>. The end result is a slightly better working
2353 <p
>I hope someone find time to implement a more polished version of
2354 this script as part of the hw-detect debian-installer module, to
2355 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
2356 #
655507</a
>. There really is no need to insert USB sticks with
2357 firmware during a PXE install when the packages already are available
2358 from the nearby Debian mirror.
</p
>
2363 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
2364 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
2365 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
2366 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
2367 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2368 the screen just turn black when Linux boot, either during installation
2369 or on first boot from the hard disk. I
've seen it once in a while the
2370 last few years, but only recently understood the cause. I
've seen it
2371 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2372 The reason seem to be in the wiring of some laptops. The system to
2373 control the screen background light is inverted, so when Linux try to
2374 turn the brightness fully on, it end up turning it off instead. I do
2375 not know which Linux drivers are affected, but this post is about the
2376 i915 driver used by the
2377 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2378 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
2380 <p
>The problem can be worked around two ways. Either by adding
2381 i915.invert_brightness=
1 as a kernel option, or by adding a file in
2382 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
2383 option when it load the i915 kernel module. On Debian and Ubuntu, it
2384 can be done by running these commands as root:
</p
>
2387 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
2388 update-initramfs -u -k all
2391 <p
>Since March
2012 there is
2392 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
2393 mechanism in the Linux kernel
</a
> to tell the i915 driver which
2394 hardware have this problem, and get the driver to invert the
2395 brightness setting automatically. To use it, one need to add a row in
2396 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
2397 intel_quirks array
</a
> in the driver source
2398 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
2399 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
2400 number (vendor number
8086 is assumed) and subdevice vendor and device
2403 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
2404 -vvnn
</tt
> for the video card in question:
</p
>
2406 <p
><pre
>
2407 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
2408 3rd Gen Core processor Graphics Controller [
8086:
0156] \
2409 (rev
09) (prog-if
00 [VGA controller])
2410 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
2411 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2412 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2413 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
2414 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
2416 Interrupt: pin A routed to IRQ
42
2417 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
2418 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
2419 Region
4: I/O ports at
4000 [size=
64]
2420 Expansion ROM at
<unassigned
> [disabled]
2421 Capabilities:
<access denied
>
2422 Kernel driver in use: i915
2423 </pre
></p
>
2425 <p
>The resulting intel_quirks entry would then look like this:
</p
>
2427 <p
><pre
>
2428 struct intel_quirk intel_quirks[] = {
2430 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2431 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
2434 </pre
></p
>
2436 <p
>According to the kernel module instructions (as seen using
2437 <tt
>modinfo i915
</tt
>), information about hardware needing the
2438 invert_brightness flag should be sent to the
2439 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
2440 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
2441 developers. But my email about the laptop sent
2013-
06-
03 have not
2443 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
2444 web archive for the mailing list
</a
>, so I suspect they do not accept
2445 emails from non-subscribers. Because of this, I sent my patch also to
2446 the Debian bug tracking system instead as
2447 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
2448 sure the patch is not lost.
</p
>
2450 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
2451 with this problem working properly with Linux. If you use Gnome, your
2452 worries should be over at this point. But if you use KDE, there is
2453 something in KDE ignoring the invert_brightness setting and turning on
2454 the screen during login. I
've reported it to Debian as
2455 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
2456 have no idea yet how to figure out exactly what subsystem is doing
2457 this. Perhaps you can help? Perhaps you know what the Gnome
2458 developers did to handle this, and this can give a clue to the KDE
2459 developers? Or you know where in KDE the screen brightness is changed
2460 during login? If so, please update the BTS report (or get in touch if
2461 you do not know how to update BTS).
</p
>
2463 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
2464 acpi_backlight=vendor, to disable ACPI backlight support completely,
2465 as the ACPI information on the machine is trash and it is better to
2466 leave it to the intel video driver to control the screen
2467 backlight.
</p
>
2472 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
2473 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
2474 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</guid>
2475 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
2476 <description><p
>Two days ago, I asked
2477 <a href=
"http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
">how
2478 I could install Linux on a Packard Bell EasyNote LV computer
2479 preinstalled with Windows
8</a
>. I found a solution, but am horrified
2480 with the obstacles put in the way of Linux users on a laptop with UEFI
2481 and Windows
8.
</p
>
2483 <p
>I never found out if the cause of my problems were the use of UEFI
2484 secure booting or fast boot. I suspect fast boot was the problem,
2485 causing the firmware to boot directly from HD without considering any
2486 key presses and alternative devices, but do not know UEFI settings
2487 enough to tell.
</p
>
2489 <p
>There is no way to install Linux on the machine in question without
2490 opening the box and disconnecting the hard drive! This is as far as I
2491 can tell, the only way to get access to the firmware setup menu
2492 without accepting the Windows
8 license agreement. I am told (and
2493 found description on how to) that it is possible to configure the
2494 firmware setup once booted into Windows
8. But as I believe the terms
2495 of that agreement are completely unacceptable, accepting the license
2496 was never an alternative. I do not enter agreements I do not intend
2497 to follow.
</p
>
2499 <p
>I feared I had to return the laptops and ask for a refund, and
2500 waste many hours on this, but luckily there was a way to get it to
2501 work. But I would not recommend it to anyone planning to run Linux on
2502 it, and I have become sceptical to Windows
8 certified laptops. Is
2503 this the way Linux will be forced out of the market place, by making
2504 it close to impossible for
"normal
" users to install Linux without
2505 accepting the Microsoft Windows license terms? Or at least not
2506 without risking to loose the warranty?
</p
>
2508 <p
>I
've updated the
2509 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
2510 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
2511 do not have to struggle as much as I did to get Linux into the
2514 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2515 Michael Tokarev and others for feedback and ideas.
</p
>
2520 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
2521 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
2522 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</guid>
2523 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
2524 <description><p
>I
've run into quite a problem the last few days. I bought three
2525 new laptops for my parents and a few others. I bought Packard Bell
2526 Easynote LV to run Kubuntu on and use as their home computer. But I
2527 am completely unable to figure out how to install Linux on it. The
2528 computer is preinstalled with Windows
8, and I suspect it uses UEFI
2529 instead of a BIOS to boot.
</p
>
2531 <p
>The problem is that I am unable to get it to PXE boot, and unable
2532 to get it to boot the Linux installer from my USB stick. I have yet
2533 to try the DVD install, and still hope it will work. when I turn on
2534 the computer, there is no information on what buttons to press to get
2535 the normal boot menu. I expect to get some boot menu to select PXE or
2536 USB stick booting. When booting, it first ask for the language to
2537 use, then for some regional settings, and finally if I will accept the
2538 Windows
8 terms of use. As these terms are completely unacceptable to
2539 me, I have no other choice but to turn off the computer and try again
2540 to get it to boot the Linux installer.
</p
>
2542 <p
>I have gathered my findings so far on a Linlap page about the
2543 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
2544 EasyNote LV
</a
> model. If you have any idea how to get Linux
2545 installed on this machine, please get in touch or update that wiki
2546 page. If I can
't find a way to install Linux, I will have to return
2547 the laptop to the seller and find another machine for my parents.
</p
>
2549 <p
>I wonder, is this the way Linux will be forced out of the market
2550 using UEFI and
"secure boot
" by making it impossible to install Linux
2551 on new Laptops?
</p
>
2556 <title>How to transform a Debian based system to a Debian Edu installation
</title>
2557 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
2558 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
2559 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
2560 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
2561 an operating system based on Debian intended for use in schools. It
2562 contain a turn-key solution for the computer network provided to
2563 pupils in the primary schools. It provide both the central server,
2564 network boot servers and desktop environments with heaps of
2565 educational software. The project was founded almost
12 years ago,
2566 2001-
07-
02. If you want to support the project, which is in need for
2567 cash to fund developer gatherings and other project related activity,
2568 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
2569 donate some money
</a
>.
2571 <p
>A topic that come up again and again on the Debian Edu mailing
2572 lists and elsewhere, is the question on how to transform a Debian or
2573 Ubuntu installation into a Debian Edu installation. It isn
't very
2574 hard, and last week I wrote a script to replicate the steps done by
2575 the Debian Edu installer.
</p
>
2577 <p
>The script,
2578 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/branches/wheezy/debian-edu-config/share/debian-edu-config/tools/debian-edu-bless?view=markup
">debian-edu-bless
<a/
>
2579 in the debian-edu-config package, will go through these six steps and
2580 transform an existing Debian Wheezy or Ubuntu (untested) installation
2581 into a Debian Edu Workstation:
</p
>
2585 <li
>Add skolelinux related APT sources.
</li
>
2586 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
2587 <li
>Install debian-edu-install to load preseeding values and pull in
2588 our configuration.
</li
>
2589 <li
>Preseed debconf database with profile setup in
2590 /etc/debian-edu/config, and run tasksel to install packages
2591 according to the profile specified in the config above,
2592 overriding some of the Debian automation machinery.
</li
>
2593 <li
>Run debian-edu-cfengine-D installation to configure everything
2594 that could not be done using preseeding.
</li
>
2595 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
2599 <p
>There are some steps in the Debian Edu installation that can not be
2600 replicated like this. Disk partitioning and LVM setup, for example.
2601 So this script just assume there is enough disk space to install all
2602 the needed packages.
</p
>
2604 <p
>The script was created to help a Debian Edu student working on
2605 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
2606 Debian Edu client, and using it he can take the existing
2607 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
2608 transform it into a fully functioning Debian Edu Workstation (or
2609 Roaming Workstation, or whatever :).
</p
>
2611 <p
>The default setting in the script is to create a KDE Workstation.
2612 If a LXDE based Roaming workstation is wanted instead, modify the
2613 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
2615 <p
><pre
>
2616 PROFILE=
"Roaming-Workstation
"
2617 DESKTOP=
"lxde
"
2618 </pre
></p
>
2620 <p
>The script could even become useful to set up Debian Edu servers in
2621 the cloud, by starting with a virtual Debian installation at some
2622 virtual hosting service and setting up all the services on first
2628 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
2629 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
2630 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
2631 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
2632 <description><P
>In January,
2633 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
2634 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
2635 channel #debian-lego
</a
>, for those of us in the Debian and Linux
2636 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
2637 marvellous construction system from Denmark. We also created
2638 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
2639 a place to take notes and write down our plans and hopes. And several
2640 people showed up to help. I was very happy to see the effect of my
2641 call. Since the small start, we have a debtags tag
2642 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
2643 tag for LEGO related packages, and now count
10 packages related to
2644 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
2646 <p
><table
>
2647 <tr
><td
><a href=
"http://packages.qa.debian.org/brickos
">brickos
</a
></td
><td
>alternative OS for LEGO Mindstorms RCX. Supports development in C/C++
</td
></tr
>
2648 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
2649 <tr
><td
><a href=
"http://packages.qa.debian.org/libnxt
">libnxt
</a
></td
><td
>utility library for talking to the LEGO Mindstorms NX
</td
></tr
>
2650 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
2651 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
2652 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
2653 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt
">python-nxt
</a
></td
><td
>python driver/interface/wrapper for the Lego Mindstorms NXT robot
</td
></tr
>
2654 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt-filer
">python-nxt-filer
</a
></td
><td
>simple GUI to manage files on a LEGO Mindstorms NXT
</td
></tr
>
2655 <tr
><td
><a href=
"http://packages.qa.debian.org/scratch
">scratch
</a
></td
><td
>easy to use programming environment for ages
8 and up
</td
></tr
>
2656 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
2657 </table
></p
>
2659 <p
>Some of these are available in Wheezy, and all but one are
2660 currently available in Jessie/testing. leocad is so far only
2661 available in experimental.
</p
>
2663 <p
>If you care about LEGO in Debian, please join us on IRC and help
2664 adding the rest of the great free software tools available on Linux
2665 for LEGO designers.
</p
>
2670 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
2671 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
2672 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
2673 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
2674 <description><p
>When I woke up this morning, I was very happy to see that the
2675 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
2676 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
2677 Debian release, and I expect to move my machines at home over to it fairly
2680 <p
>The new debian release contain heaps of new stuff, and one program
2681 in particular make me very happy to see included. The
2682 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
2683 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
2684 included for the first time. Alongside similar programs like
2685 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
2686 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
2687 it allow for visual programming where syntax errors can not happen,
2688 and a friendly programming environment for learning to control the
2689 computer. Scratch will also be included in the next release of Debian
2692 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
2693 Edu/Skolelinux release too. The
2694 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
2695 alpha release
</a
> went out last week, and the next should soon
2701 <title>Isenkram
0.2 finally in the Debian archive
</title>
2702 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
2703 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
2704 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
2705 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
2706 package
</a
> finally made it into the archive, after lingering in NEW
2707 for many months. I uploaded it to the Debian experimental suite
2708 2013-
01-
27, and today it was accepted into the archive.
</p
>
2710 <p
>Isenkram is a system for suggesting to users what packages to
2711 install to work with a pluggable hardware device. The suggestion pop
2712 up when the device is plugged in. For example if a Lego Mindstorm NXT
2713 is inserted, it will suggest to install the program needed to program
2714 the NXT controller. Give it a go, and report bugs and suggestions to
2720 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
2721 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
2722 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
2723 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
2724 <description><p
>My
2725 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
2726 bitcoin related blog post
</a
> mentioned that the new
2727 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
2728 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2729 2013-
01-
19, and have been available in unstable since then. It was
2730 automatically copied to Ubuntu, and is available in their Raring
2731 version too.
</p
>
2733 <p
>But there is a strange problem with the build that block this new
2734 version from being available on the i386 and kfreebsd-i386
2735 architectures. For some strange reason, the autobuilders in Debian
2736 for these architectures fail to run the test suite on these
2737 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
2738 We are so far unable to reproduce it when building it manually, and
2739 no-one have been able to propose a fix. If you got an idea what is
2740 failing, please let us know via the BTS.
</p
>
2742 <p
>One feature that is annoying me with of the bitcoin client, because
2743 I often run low on disk space, is the fact that the client will exit
2744 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
2745 #
696715</a
>). So make sure you have enough disk space when you run
2748 <p
>As usual, if you use bitcoin and want to show your support of my
2749 activities, please send Bitcoin donations to my address
2750 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2755 <title>Welcome to the world, Isenkram!
</title>
2756 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
2757 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
2758 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
2759 <description><p
>Yesterday, I
2760 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
2761 for testers
</a
> for my prototype for making Debian better at handling
2762 pluggable hardware devices, which I
2763 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
2764 out to create
</a
> earlier this month. Several valuable testers showed
2765 up, and caused me to really want to to open up the development to more
2766 people. But before I did this, I want to come up with a sensible name
2767 for this project. Today I finally decided on a new name, and I have
2768 renamed the project from hw-support-handler to this new name. In the
2769 process, I moved the source to git and made it available as a
2770 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
2771 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
2772 To fetch and build the latest version of the source, use
</p
>
2775 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2776 cd isenkram
&& git-buildpackage -us -uc
2779 <p
>I have not yet adjusted all files to use the new name yet. If you
2780 want to hack on the source or improve the package, please go ahead.
2781 But please talk to me first on IRC or via email before you do major
2782 changes, to make sure we do not step on each others toes. :)
</p
>
2784 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
2785 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2786 stuff, in other words. I
've been told it is the Norwegian variant of
2787 the German word eisenkram, for those that are familiar with that
2790 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
2791 instructions, to avoid confusing people with an error from the signing
2794 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
2795 clone argument to avoid the need for authentication.
</p
>
2800 <title>First prototype ready making hardware easier to use in Debian
</title>
2801 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
2802 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
2803 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
2804 <description><p
>Early this month I set out to try to
2805 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
2806 the Debian support for pluggable hardware devices
</a
>. Now my
2807 prototype is working, and it is ready for a larger audience. To test
2809 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
2810 from the Debian Edu subversion repository
</a
>, build and install the
2811 package. You might have to log out and in again activate the
2812 autostart script.
</p
>
2814 <p
>The design is simple:
</p
>
2818 <li
>Add desktop entry in /usr/share/autostart/ causing a program
2819 hw-support-handlerd to start when the user log in.
</li
>
2821 <li
>This program listen for kernel events about new hardware (directly
2822 from the kernel like udev does), not using HAL dbus events as I
2823 initially did.
</li
>
2825 <li
>When new hardware is inserted, look up the hardware modalias in
2826 the APT database, a database
2827 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
2828 via HTTP
</a
> and a database available as part of the package.
</li
>
2830 <li
>If a package is mapped to the hardware in question, the package
2831 isn
't installed yet and this is the first time the hardware was
2832 plugged in, show a desktop notification suggesting to install the
2833 package or packages.
</li
>
2835 <li
>If the user click on the
'install package now
' button, ask
2836 aptdaemon via the PackageKit API to install the requrired package.
</li
>
2838 <li
>aptdaemon ask for root password or sudo password, and install the
2839 package while showing progress information in a window.
</li
>
2843 <p
>I still need to come up with a better name for the system. Here
2844 are some screen shots showing the prototype in action. First the
2845 notification, then the password request, and finally the request to
2846 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
2848 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
2849 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
2850 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
2851 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
2852 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
2854 <p
>The prototype still need to be improved with longer timeouts, but
2855 is already useful. The database of hardware to package mappings also
2856 need more work. It is currently compatible with the Ubuntu way of
2857 storing such information in the package control file, but could be
2858 changed to use other formats instead or in addition to the current
2859 method. I
've dropped the use of discover for this mapping, as the
2860 modalias approach is more flexible and easier to use on Linux as long
2861 as the Linux kernel expose its modalias strings directly.
</p
>
2863 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
2864 here is the command required to check out and build the source: Use
2865 '<tt
>svn checkout
2866 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2867 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
2868 devscripts package.
</p
>
2870 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
2871 renamed to Isenkram and the source moved from the Debian Edu
2872 subversion repository to a Debian collab-maint git repository. See
2873 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
2874 instructions
</a
> for details.
</p
>
2879 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
2880 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
2881 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
2882 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
2883 <description><p
>This Christmas my trusty old laptop died. It died quietly and
2884 suddenly in bed. With a quiet whimper, it went completely quiet and
2885 black. The power button was no longer able to turn it on. It was a
2886 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2887 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2888 Compaq I had before that. Now I need to find a replacement. To keep
2889 going during Christmas, I moved the one year old SSD disk to my old
2890 X40 where it fitted (only one I had left that could use it), but it is
2891 not a durable solution.
2893 <p
>My laptop needs are fairly modest. This is my wishlist from when I
2894 got a new one more than
10 years ago. It still holds true.:)
</p
>
2898 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
2899 than A4).
</li
>
2900 <li
>Robust, it will be in my backpack every day.
</li
>
2901 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
2902 <li
>Long battery life time. Preferable a week.
</li
>
2903 <li
>Internal WIFI network card.
</li
>
2904 <li
>Internal Twisted Pair network card.
</li
>
2905 <li
>Some USB slots (
2-
3 is plenty)
</li
>
2906 <li
>Good keyboard - similar to the Thinkpad.
</li
>
2907 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
2909 <li
>Hardware supported by Debian Stable, ie the default kernel and
2910 X.org packages.
</li
>
2911 <li
>Quiet, preferably fan free (or at least not using the fan most of
2916 <p
>You will notice that there are no RAM and CPU requirements in the
2917 list. The reason is simply that the specifications on laptops the
2918 last
10-
15 years have been sufficient for my needs, and I have to look
2919 at other features to choose my laptop. But are there still made as
2920 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
2921 robust, and Thinkpads seem to be heading in the wrong direction since
2922 Lenovo took over. But I
've been told that X220 and X1 Carbon might
2923 still be useful.
</p
>
2925 <p
>Perhaps I should rethink my needs, and look for a pad with an
2926 external keyboard? I
'll have to check the
2927 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
2928 well-supported laptops, or perhaps just buy one preinstalled from one
2929 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
2930 Pre-loaded site
</a
>.
</p
>
2935 <title>How to find a browser plugin supporting a given MIME type
</title>
2936 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
2937 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
2938 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
2939 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
2940 install to get support for a given MIME type. Thanks to
2941 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
2942 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
2943 Unfortunately, not very many packages provide the needed meta
2944 information, Anyway, here is a small script to look up all browser
2945 plugin packages announcing ther MIME support using this specification:
</p
>
2951 def pkgs_handling_mimetype(mimetype):
2956 version = pkg.candidate
2958 version = pkg.installed
2961 record = version.record
2962 if not record.has_key(
'Npp-MimeType
'):
2964 mime_types = record[
'Npp-MimeType
'].split(
',
')
2965 for t in mime_types:
2966 t = t.rstrip().strip()
2968 thepkgs.append(pkg.name)
2970 mimetype =
"audio/ogg
"
2971 if
1 < len(sys.argv):
2972 mimetype = sys.argv[
1]
2973 print
"Browser plugin packages supporting %s:
" % mimetype
2974 for pkg in pkgs_handling_mimetype(mimetype):
2975 print
" %s
" %pkg
2978 <p
>It can be used like this to look up a given MIME type:
</p
>
2981 % ./apt-find-browserplug-for-mimetype
2982 Browser plugin packages supporting audio/ogg:
2984 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
2985 Browser plugin packages supporting application/x-shockwave-flash:
2986 browser-plugin-gnash
2990 <p
>In Ubuntu this mechanism is combined with support in the browser
2991 itself to query for plugins and propose to install the needed
2992 packages. It would be great if Debian supported such feature too. Is
2993 anyone working on adding it?
</p
>
2995 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
2996 request for icweasel support for this feature is
2997 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
2998 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
2999 of manpower and wish for a different design is the reason thus feature
3000 is not yet in iceweasel from Debian.
</p
>
3005 <title>What is the most supported MIME type in Debian?
</title>
3006 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
3007 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
3008 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
3009 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
3010 proposal to add AppStream information to the Debian archive
</a
>, is a
3011 proposal to make it possible for a Desktop application to propose to
3012 the user some package to install to gain support for a given MIME
3013 type, font, library etc. that is currently missing. With such
3014 mechanism in place, it would be possible for the desktop to
3015 automatically propose and install leocad if some LDraw file is
3016 downloaded by the browser.
</p
>
3018 <p
>To get some idea about the current content of the archive, I decided
3019 to write a simple program to extract all .desktop files from the
3020 Debian archive and look up the claimed MIME support there. The result
3022 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
3023 site
</a
>. Using the collected information, it become possible to
3024 answer the question in the title. Here are the
20 most supported MIME
3025 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
3026 The complete list is available from the link above.
</p
>
3028 <p
><strong
>Debian Stable:
</strong
></p
>
3032 ----- -----------------------
3048 18 application/x-ogg
3055 <p
><strong
>Debian Testing:
</strong
></p
>
3059 ----- -----------------------
3075 18 application/x-ogg
3082 <p
><strong
>Debian Unstable:
</strong
></p
>
3086 ----- -----------------------
3103 18 application/x-ogg
3109 <p
>I am told that PackageKit can provide an API to access the kind of
3110 information mentioned in DEP-
11. I have not yet had time to look at
3111 it, but hope the PackageKit people in Debian are on top of these
3114 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
3115 discovering a typo in my script.
</p
>
3120 <title>Using modalias info to find packages handling my hardware
</title>
3121 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
3122 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
3123 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
3124 <description><p
>Yesterday, I wrote about the
3125 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
3126 values provided by the Linux kernel
</a
> following my hope for
3127 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
3128 dongle support in Debian
</a
>. Using this knowledge, I have tested how
3129 modalias values attached to package names can be used to map packages
3130 to hardware. This allow the system to look up and suggest relevant
3131 packages when I plug in some new hardware into my machine, and replace
3132 discover and discover-data as the database used to map hardware to
3135 <p
>I create a modaliases file with entries like the following,
3136 containing package name, kernel module name (if relevant, otherwise
3137 the package name) and globs matching the relevant hardware
3140 <p
><blockquote
>
3141 Package: package-name
3142 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
3143 </blockquote
></p
>
3145 <p
>It is fairly trivial to write code to find the relevant packages
3146 for a given modalias value using this file.
</p
>
3148 <p
>An entry like this would suggest the video and picture application
3149 cheese for many USB web cameras (interface bus class
0E01):
</p
>
3151 <p
><blockquote
>
3153 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
3154 </blockquote
></p
>
3156 <p
>An entry like this would suggest the pcmciautils package when a
3157 CardBus bridge (bus class
0607) PCI device is present:
</p
>
3159 <p
><blockquote
>
3160 Package: pcmciautils
3161 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3162 </blockquote
></p
>
3164 <p
>An entry like this would suggest the package colorhug-client when
3165 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
3167 <p
><blockquote
>
3168 Package: colorhug-client
3169 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
3170 </blockquote
></p
>
3172 <p
>I believe the format is compatible with the format of the Packages
3173 file in the Debian archive. Ubuntu already uses their Packages file
3174 to store their mappings from packages to hardware.
</p
>
3176 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
3177 announce the hardware it support in a way my prototype understand.
3178 This allow those publishing packages in an APT source outside the
3179 Debian archive as well as those backporting packages to make sure the
3180 hardware mapping are included in the package meta information. I
've
3181 tested such header in the pymissile package, and its modalias mapping
3182 is working as it should with my prototype. It even made it to Ubuntu
3185 <p
>To test if it was possible to look up supported hardware using only
3186 the shell tools available in the Debian installer, I wrote a shell
3187 implementation of the lookup code. The idea is to create files for
3188 each modalias and let the shell do the matching. Please check out and
3190 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
3191 shell script. It run without any extra dependencies and fetch the
3192 hardware mappings from the Debian archive and the subversion
3193 repository where I currently work on my prototype.
</p
>
3195 <p
>When I use it on a machine with a yubikey inserted, it suggest to
3196 install yubikey-personalization:
</p
>
3198 <p
><blockquote
>
3199 % ./hw-support-lookup
3200 <br
>yubikey-personalization
3202 </blockquote
></p
>
3204 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3205 propose to install the pcmciautils package:
</p
>
3207 <p
><blockquote
>
3208 % ./hw-support-lookup
3209 <br
>pcmciautils
3211 </blockquote
></p
>
3213 <p
>If you know of any hardware-package mapping that should be added to
3214 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
3215 database
</a
>, please tell me about it.
</p
>
3217 <p
>It could be possible to generate several of the mappings between
3218 packages and hardware. One source would be to look at packages with
3219 kernel modules, ie packages with *.ko files in /lib/modules/, and
3220 extract their modalias information. Another would be to look at
3221 packages with udev rules, ie packages with files in
3222 /lib/udev/rules.d/, and extract their vendor/model information to
3223 generate a modalias matching rule. I have not tested any of these to
3224 see if it work.
</p
>
3226 <p
>If you want to help implementing a system to let us propose what
3227 packages to install when new hardware is plugged into a Debian
3228 machine, please send me an email or talk to me on
3229 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3234 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
3235 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
3236 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
3237 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
3238 <description><p
>While looking into how to look up Debian packages based on hardware
3239 information, to find the packages that support a given piece of
3240 hardware, I refreshed my memory regarding modalias values, and decided
3241 to document the details. Here are my findings so far, also available
3243 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3244 Debian Edu subversion repository
</a
>:
3246 <p
><strong
>Modalias decoded
</strong
></p
>
3248 <p
>This document try to explain what the different types of modalias
3249 values stands for. It is in part based on information from
3250 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
3251 &lt;URL:
<a href=
"http://unix.stackexchange.com/questions/
26132/how-to-assign-usb-driver-to-device
">http://unix.stackexchange.com/questions/
26132/how-to-assign-usb-driver-to-device
</a
> &gt;,
3252 &lt;URL:
<a href=
"http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c
">http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c
</a
> &gt; and
3253 &lt;URL:
<a href=
"http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode
&view=markup
">http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode
&view=markup
</a
> &gt;.
3255 <p
>The modalias entries for a given Linux machine can be found using
3256 this shell script:
</p
>
3259 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
3262 <p
>The supported modalias globs for a given kernel module can be found
3263 using modinfo:
</p
>
3266 % /sbin/modinfo psmouse | grep alias:
3267 alias: serio:ty05pr*id*ex*
3268 alias: serio:ty01pr*id*ex*
3272 <p
><strong
>PCI subtype
</strong
></p
>
3274 <p
>A typical PCI entry can look like this. This is an Intel Host
3275 Bridge memory controller:
</p
>
3277 <p
><blockquote
>
3278 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3279 </blockquote
></p
>
3281 <p
>This represent these values:
</p
>
3286 sv
00001028 (subvendor)
3287 sd
000001AD (subdevice)
3289 sc
00 (bus subclass)
3293 <p
>The vendor/device values are the same values outputted from
'lspci
3294 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
3295 0600. The
0600 class is a host bridge. Other useful bus values are
3296 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
3298 <p
>Not sure how to figure out the interface value, nor what it
3301 <p
><strong
>USB subtype
</strong
></p
>
3303 <p
>Some typical USB entries can look like this. This is an internal
3304 USB hub in a laptop:
</p
>
3306 <p
><blockquote
>
3307 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3308 </blockquote
></p
>
3310 <p
>Here is the values included in this alias:
</p
>
3313 v
1D6B (device vendor)
3314 p
0001 (device product)
3316 dc
09 (device class)
3317 dsc
00 (device subclass)
3318 dp
00 (device protocol)
3319 ic
09 (interface class)
3320 isc
00 (interface subclass)
3321 ip
00 (interface protocol)
3324 <p
>The
0900 device class/subclass means hub. Some times the relevant
3325 class is in the interface class section. For a simple USB web camera,
3326 these alias entries show up:
</p
>
3328 <p
><blockquote
>
3329 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3330 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3331 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3332 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3333 </blockquote
></p
>
3335 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
3336 camera),
0101 is audio control device and
0102 is audio streaming (aka
3337 microphone). Thus this is a camera with microphone included.
</p
>
3339 <p
><strong
>ACPI subtype
</strong
></p
>
3341 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
3342 receiver in a Thinkpad X40:
</p
>
3344 <p
><blockquote
>
3345 acpi:IBM0071:PNP0511:
3346 </blockquote
></p
>
3348 <p
>The values between the colons are IDs.
</p
>
3350 <p
><strong
>DMI subtype
</strong
></p
>
3352 <p
>The DMI table contain lots of information about the computer case
3353 and model. This is an entry for a IBM Thinkpad X40, fetched from
3354 /sys/devices/virtual/dmi/id/modalias:
</p
>
3356 <p
><blockquote
>
3357 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3358 </blockquote
></p
>
3360 <p
>The values present are
</p
>
3363 bvn IBM (BIOS vendor)
3364 bvr
1UETB
6WW(
1.66) (BIOS version)
3365 bd
06/
15/
2005 (BIOS date)
3366 svn IBM (system vendor)
3367 pn
2371H4G (product name)
3368 pvr ThinkPadX40 (product version)
3369 rvn IBM (board vendor)
3370 rn
2371H4G (board name)
3371 rvr NotAvailable (board version)
3372 cvn IBM (chassis vendor)
3373 ct
10 (chassis type)
3374 cvr NotAvailable (chassis version)
3377 <p
>The chassis type
10 is Notebook. Other interesting values can be
3378 found in the dmidecode source:
</p
>
3382 4 Low Profile Desktop
3395 17 Main Server Chassis
3396 18 Expansion Chassis
3398 20 Bus Expansion Chassis
3399 21 Peripheral Chassis
3401 23 Rack Mount Chassis
3410 <p
>The chassis type values are not always accurately set in the DMI
3411 table. For example my home server is a tower, but the DMI modalias
3412 claim it is a desktop.
</p
>
3414 <p
><strong
>SerIO subtype
</strong
></p
>
3416 <p
>This type is used for PS/
2 mouse plugs. One example is from my
3417 test machine:
</p
>
3419 <p
><blockquote
>
3420 serio:ty01pr00id00ex00
3421 </blockquote
></p
>
3423 <p
>The values present are
</p
>
3432 <p
>This type is supported by the psmouse driver. I am not sure what
3433 the valid values are.
</p
>
3435 <p
><strong
>Other subtypes
</strong
></p
>
3437 <p
>There are heaps of other modalias subtypes according to
3438 file2alias.c. There is the rest of the list from that source: amba,
3439 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3440 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3441 vmbus, x86cpu and zorro. I did not spend time documenting all of
3442 these, as they do not seem relevant for my intended use with mapping
3443 hardware to packages when new stuff is inserted during run time.
</p
>
3445 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
3447 <p
>To check which kernel modules provide support for a given modalias,
3448 one can use the following shell script:
</p
>
3451 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
3452 echo
"$id
" ; \
3453 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
3457 <p
>The output can look like this (only the first few entries as the
3458 list is very long on my test machine):
</p
>
3462 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
3464 FATAL: Module acpi:device: not found.
3466 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
3467 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
3468 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
3469 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3470 acpi:IBM0071:PNP0511:
3471 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
3472 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
3473 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
3477 <p
>If you want to help implementing a system to let us propose what
3478 packages to install when new hardware is plugged into a Debian
3479 machine, please send me an email or talk to me on
3480 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
3482 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
3483 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
3484 in /sys/ with space in them.
</p
>
3489 <title>Moved the pymissile Debian packaging to collab-maint
</title>
3490 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
3491 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
3492 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
3493 <description><p
>As part of my investigation on how to improve the support in Debian
3494 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3495 Launcher and updated the Debian package
3496 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
3497 sure udev will fix the device permissions when it is plugged in. I
3498 also added a
"Modaliases
" header to test it in the Debian archive and
3499 hopefully make the package be proposed by jockey in Ubuntu when a user
3500 plug in his rocket launcher. In the process I moved the source to a
3501 git repository under collab-maint, to make it easier for any DD to
3502 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
3503 is not very active, but the software still work for me even after five
3504 years of relative silence. The new git repository is not listed in
3505 the uploaded package yet, because I want to test the other changes a
3506 bit more before I upload the new version. If you want to check out
3507 the new version with a .desktop file included, visit the
3508 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
3509 view
</a
> or use
"<tt
>git clone
3510 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
3515 <title>Lets make hardware dongles easier to use in Debian
</title>
3516 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
3517 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
3518 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
3519 <description><p
>One thing that annoys me with Debian and Linux distributions in
3520 general, is that there is a great package management system with the
3521 ability to automatically install software packages by downloading them
3522 from the distribution mirrors, but no way to get it to automatically
3523 install the packages I need to use the hardware I plug into my
3524 machine. Even if the package to use it is easily available from the
3525 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3526 suggest to automatically install the python-nxt, nbc and t2n packages
3527 I need to talk to it. When I plug in a Yubikey, it could propose the
3528 yubikey-personalization package. The information required to do this
3529 is available, but no-one have pulled all the pieces together.
</p
>
3531 <p
>Some years ago, I proposed to
3532 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
3533 the discover subsystem to implement this
</a
>. The idea is fairly
3538 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
3539 starting when a user log in.
</li
>
3541 <li
>Set this program up to listen for kernel events emitted when new
3542 hardware is inserted into the computer.
</li
>
3544 <li
>When new hardware is inserted, look up the hardware ID in a
3545 database mapping to packages, and take note of any non-installed
3546 packages.
</li
>
3548 <li
>Show a message to the user proposing to install the discovered
3549 package, and make it easy to install it.
</li
>
3553 <p
>I am not sure what the best way to implement this is, but my
3554 initial idea was to use dbus events to discover new hardware, the
3555 discover database to find packages and
3556 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
3559 <p
>Yesterday, I found time to try to implement this idea, and the
3560 draft package is now checked into
3561 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
3562 Debian Edu subversion repository
</a
>. In the process, I updated the
3563 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
3564 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3565 the relevant packages in Debian, and uploaded a new version
3566 2.2013.01.09 to unstable. I also discovered that the current
3567 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
3568 package in Debian no longer discovered any USB devices, because
3569 /proc/bus/usb/devices is no longer present. I ported it to use
3570 libusb as a fall back option to get it working. The fixed package
3571 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
3572 because of the freeze).
</p
>
3574 <p
>With this prototype in place, I can insert my Yubikey, and get this
3575 desktop notification to show up (only once, the first time it is
3576 inserted):
</p
>
3578 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
3580 <p
>For this prototype to be really useful, some way to automatically
3581 install the proposed packages by pressing the
"Please install
3582 program(s)
" button should to be implemented.
</p
>
3584 <p
>If this idea seem useful to you, and you want to help make it
3585 happen, please help me update the discover-data database with mappings
3586 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
3587 list the package you would like to have installed when a given
3588 hardware device is inserted into your computer, and report bugs using
3589 reportbug if it isn
't. Or, if you know of a better way to provide
3590 such mapping, please let me know.
</p
>
3592 <p
>This prototype need more work, and there are several questions that
3593 should be considered before it is ready for production use. Is dbus
3594 the correct way to detect new hardware? At the moment I look for HAL
3595 dbus events on the system bus, because that is the events I could see
3596 on my Debian Squeeze KDE desktop. Are there better events to use?
3597 How should the user be notified? Is the desktop notification
3598 mechanism the best option, or should the background daemon raise a
3599 popup instead? How should packages be installed? When should they
3600 not be installed?
</p
>
3602 <p
>If you want to help getting such feature implemented in Debian,
3603 please send me an email. :)
</p
>
3608 <title>New IRC channel for LEGO designers using Debian
</title>
3609 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
3610 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
3611 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
3612 <description><p
>During Christmas, I have worked a bit on the Debian support for
3613 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
3614 NXT
</a
>. My son and I have played a bit with my NXT set, and I
3615 discovered I had to build all the tools myself because none were
3616 already in Debian Squeeze. If Debian support for LEGO is something
3617 you care about, please join me on the IRC channel
3618 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
3619 irc.debian.org). There is a lot that could be done to improve the
3620 Debian support for LEGO designers. For example both CAD software
3621 and Mindstorm compilers are missing. :)
</p
>
3623 <p
>Update
2012-
01-
03: A
3624 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
3625 including links to Lego related packages is now available.
</p
>
3630 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
3631 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
3632 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
3633 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
3634 <description><p
>Let me start by wishing you all marry Christmas and a happy new
3635 year! I hope next year will prove to be a good year.
</p
>
3637 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
3638 decentralised
"currency
" that allow people to transfer bitcoins
3639 between each other with minimal overhead, is a very interesting
3640 experiment. And as I wrote a few days ago, the bitcoin situation in
3641 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
3642 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
3643 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
3644 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
3645 for one of the ftpmasters to approve the new bitcoin-qt package
3648 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
3649 team in Debian, you can easily test the package in Debian Squeeze
3650 using the following steps to get a set of working packages:
</p
>
3652 <blockquote
><pre
>
3653 git clone git://git.debian.org/git/collab-maint/bitcoin
3655 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3656 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3657 </pre
></blockquote
>
3659 <p
>You might have to install some build dependencies as well. The
3660 list of commands should give you two packages, bitcoind and
3661 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3662 client will download the complete set of bitcoin
"blocks
", which need
3663 around
5.6 GiB of data on my machine at the moment. Make sure your
3664 ~/.bitcoin/ directory have lots of spare room if you want to download
3665 all the blocks. The client will warn if the disk is getting full, so
3666 there is not really a problem if you got too little room, but you will
3667 not be able to get all the features out of the client.
</p
>
3669 <p
>As usual, if you use bitcoin and want to show your support of my
3670 activities, please send Bitcoin donations to my address
3671 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3676 <title>A word on bitcoin support in Debian
</title>
3677 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
3678 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
3679 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
3680 <description><p
>It has been a while since I wrote about
3681 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
3682 peer-to-peer based crypto-currency, and the reason is simply that I
3683 have been busy elsewhere. But two days ago, I started looking at the
3684 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
3685 Debian
</a
> again to try to recover my old bitcoin wallet. The package
3686 is now maintained by a
3687 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
3688 people
</a
>, and the grunt work had already been done by this team. We
3689 owe a huge thank you to all these team members. :)
3690 But I was sad to discover that the bitcoin client is missing in
3691 Wheezy. It is only available in Sid (and an outdated client from
3692 backports). The client had several RC bugs registered in BTS blocking
3693 it from entering testing. To try to help the team and improve the
3694 situation, I spent some time providing patches and triaging the bug
3695 reports. I also had a look at the bitcoin package available from Matt
3697 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
3698 Ubuntu
</a
>, and moved the useful pieces from that version into the
3699 Debian package.
</p
>
3701 <p
>After checking with the main package maintainer Jonas Smedegaard on
3702 IRC, I pushed several patches into the collab-maint git repository to
3703 improve the package. It now contains fixes for the RC issues (not from
3704 me, but fixed by Scott Howard), build rules for a Qt GUI client
3705 package, konqueror support for the bitcoin: URI and bash completion
3706 setup. As I work on Debian Squeeze, I also created
3707 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
3708 patch to backport
</a
> the latest version. Jonas is going to look at
3709 it and try to integrate it into the git repository before uploading a
3710 new version to unstable.
3712 <p
>I would very much like bitcoin to succeed, to get rid of the
3713 centralized control currently exercised in the monetary system. I
3714 find it completely unacceptable that the USA government is collecting
3715 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3716 that the major credit card companies can block legal money
3717 transactions to Wikileaks. But for bitcoin to succeed, more people
3718 need to use bitcoins, and more people need to accept bitcoins when
3719 they sell products and services. Improving the bitcoin support in
3720 Debian is a small step in the right direction, but not enough.
3721 Unfortunately the user experience when browsing the web and wanting to
3722 pay with bitcoin is still not very good. The bitcoin: URI is a step
3723 in the right direction, but need to work in most or every browser in
3724 use. Also the bitcoin-qt client is too heavy to fire up to do a
3725 quick transaction. I believe there are other clients available, but
3726 have not tested them.
</p
>
3729 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
3730 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
3731 I received
20.15 BTC so far on the address I provided in my blog two
3732 years ago, as can be
3733 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
3734 on the blockexplorer service
</a
>. Thank you everyone for your
3735 donation. The blockexplorer service demonstrates quite well that
3736 bitcoin is not quite anonymous and untracked. :) I wonder if the
3737 number of users have gone up since then. If you use bitcoin and want
3738 to show your support of my activity, please send Bitcoin donations to
3739 the same address as last time,
3740 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
&label=PetterReinholdtsenBlog
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3745 <title>Git repository for song book for Computer Scientists
</title>
3746 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
3747 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
3748 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
3749 <description><p
>As I
3750 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
3751 this summer
</a
>, I have created a Computer Science song book a few
3752 years ago, and today I finally found time to create a public
3753 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
3754 repository for the project
</a
>.
</p
>
3756 <p
>If you want to help out, please clone the source and submit patches
3757 to the HTML version. To generate the PDF and PostScript version,
3758 please use prince XML, or let me know about a useful free software
3759 processor capable of creating a good looking PDF from the HTML.
</p
>
3761 <p
>Want to sing? You can still find the song book in HTML, PDF and
3762 PostScript formats at
3763 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
3764 Science Songbook
</a
>.
</p
>
3769 <title>Gratulerer med
19-årsdagen, Debian!
</title>
3770 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
3771 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
3772 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
3773 <description><p
>I dag fyller
3774 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
3775 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
3776 si gratulerer med dagen, Debian!
</p
>
3781 <title>Song book for Computer Scientists
</title>
3782 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
3783 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
3784 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
3785 <description><p
>Many years ago, while studying Computer Science at the
3786 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
3787 collecting computer related songs for use at parties. The original
3788 version was written in LaTeX, but a few years ago I got help from
3789 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3790 while keeping the ability to create a nice book in PDF format. I have
3791 not had time to maintain the book for a while now, and guess I should
3792 put it up on some public version control repository where others can
3793 help me extend and update the book. If anyone is volunteering to help
3794 me with this, send me an email. Also let me know if there are songs
3795 missing in my book.
</p
>
3797 <p
>I have not mentioned the book on my blog so far, and it occured to
3798 me today that I really should let all my readers share the joys of
3799 singing out load about programming, computers and computer networks.
3800 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
3801 12</a
> is about to start (and I am not going). Want to sing? Check
3802 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
3803 Computer Science Songbook
</a
>.
3808 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
3809 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
3810 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
3811 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
3812 <description><p
>At work we have heaps of servers. I believe the total count is
3813 around
1000 at the moment. To be able to get help from the vendors
3814 when something go wrong, we want to keep the firmware on the servers
3815 up to date. If the firmware isn
't the latest and greatest, the
3816 vendors typically refuse to start debugging any problems until the
3817 firmware is upgraded. So before every reboot, we want to upgrade the
3818 firmware, and we would really like everyone handling servers at the
3819 university to do this themselves when they plan to reboot a machine.
3820 For that to happen we at the unix server admin group need to provide
3821 the tools to do so.
</p
>
3823 <p
>To make firmware upgrading easier, I am working on a script to
3824 fetch and install the latest firmware for the servers we got. Most of
3825 our hardware are from Dell and HP, so I have focused on these servers
3826 so far. This blog post is about the Dell part.
</P
>
3828 <p
>On the Dell FTP site I was lucky enough to find
3829 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
3830 with firmware information for all
11th generation servers, listing
3831 which firmware should be used on a given model and where on the FTP
3832 site I can find it. Using a simple perl XML parser I can then
3833 download the shell scripts Dell provides to do firmware upgrades from
3834 within Linux and reboot when all the firmware is primed and ready to
3835 be activated on the first reboot.
</p
>
3837 <p
>This is the Dell related fragment of the perl code I am working on.
3838 Are there anyone working on similar tools for firmware upgrading all
3839 servers at a site? Please get in touch and lets share resources.
</p
>
3841 <p
><pre
>
3845 use File::Temp qw(tempdir);
3847 # Install needed RHEL packages if missing
3849 'XML::Simple
' =
> 'perl-XML-Simple
',
3851 for my $module (keys %rhelmodules) {
3852 eval
"use $module;
";
3854 my $pkg = $rhelmodules{$module};
3855 system(
"yum install -y $pkg
");
3856 eval
"use $module;
";
3860 my $errorsto =
'pere@hungry.com
';
3866 sub run_firmware_script {
3867 my ($opts, $script) = @_;
3869 print STDERR
"fail: missing script name\n
";
3872 print STDERR
"Running $script\n\n
";
3874 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
3875 print STDERR
"success: firmware script ran succcessfully\n
";
3877 print STDERR
"fail: firmware script returned error\n
";
3881 sub run_firmware_scripts {
3882 my ($opts, @dirs) = @_;
3883 # Run firmware packages
3884 for my $dir (@dirs) {
3885 print STDERR
"info: Running scripts in $dir\n
";
3886 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
3887 while (my $s = readdir $dh) {
3888 next if $s =~ m/^\.\.?/;
3889 run_firmware_script($opts,
"$dir/$s
");
3897 print STDERR
"info: Downloading $url\n
";
3898 system(
"wget --quiet \
"$url\
"");
3903 my $product = `dmidecode -s system-product-name`;
3906 if ($product =~ m/PowerEdge/) {
3908 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
3909 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
3911 my $tmpdir = tempdir(
3915 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
3916 system(
'gunzip Catalog.xml.gz
');
3917 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
3918 # -q is quiet, disabling interactivity and reducing console output
3919 my $fwopts =
"-q
";
3921 for my $url (@paths) {
3922 fetch_dell_fw($url);
3924 run_firmware_scripts($fwopts, $tmpdir);
3926 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
3927 print STDERR
"error: Please report to $errorsto.\n
";
3931 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
3932 print STDERR
"error: Please report to $errorsto.\n
";
3938 my $url =
"ftp://ftp.us.dell.com/$path
";
3942 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
3943 # firmware packages to download from Dell. Only work for Linux
3944 # machines and
11th generation Dell servers.
3945 sub fetch_dell_fw_list {
3946 my $filename = shift;
3948 my $product = `dmidecode -s system-product-name`;
3950 my ($mybrand, $mymodel) = split(/\s+/, $product);
3952 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
3954 my $xml = XMLin($filename);
3956 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
3957 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
3958 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
3960 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
3961 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
3963 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
3965 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
3967 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
3970 for my $component (@{$xml-
>{SoftwareComponent}}) {
3971 my $componenttype = $component-
>{ComponentType}-
>{value};
3973 # Drop application packages, only firmware and BIOS
3974 next if
'APAC
' eq $componenttype;
3976 my $cpath = $component-
>{path};
3977 for my $path (@paths) {
3978 if ($cpath =~ m%/$path$%) {
3979 push(@paths, $cpath);
3987 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
3988 it could work on other platforms with some tweaking. Anyone know a
3989 index like Catalog.xml is available from HP for HP servers? At the
3990 moment I maintain a similar list manually and it is quickly getting
3996 <title>How is booting into runlevel
1 different from single user boots?
</title>
3997 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
3998 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
3999 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
4000 <description><p
>Wouter Verhelst have some
4001 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
4002 comments and opinions
</a
> on my blog post on
4003 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
4004 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
4005 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
4006 default KDE desktop in Debian
</a
>. I only have time to address one
4007 small piece of his comment now, and though it best to address the
4008 misunderstanding he bring forward:
</p
>
4010 <p
><blockquote
>
4011 Currently, a system admin has four options: [...] boot to a
4012 single-user system (by adding
'single
' to the kernel command line;
4013 this runs rcS and rc1 scripts)
4014 </blockquote
></p
>
4016 <p
>This make me believe Wouter believe booting into single user mode
4017 and booting into runlevel
1 is the same. I am not surprised he
4018 believe this, because it would make sense and is a quite sensible
4019 thing to believe. But because the boot in Debian is slightly broken,
4020 runlevel
1 do not work properly and it isn
't the same as single user
4021 mode. I
'll try to explain what is actually happing, but it is a bit
4022 hard to explain.
</p
>
4024 <p
>Single user mode is defined like this in /etc/inittab:
4025 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
4026 executed in single user mode is sulogin. Single user mode is a boot
4027 state
"between
" the runlevels, and when booting into single user mode,
4028 only the scripts in /etc/rcS.d/ are executed before the init process
4029 enters the single user state. When switching to runlevel
1, the state
4030 is in fact not ending in runlevel
1, but it passes through runlevel
1
4031 and end up in the single user mode (see /etc/rc1.d/S03single, which
4032 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
4033 1. It is confusing that the
'S
' (single user) init mode is not the
4034 mode enabled by /etc/rcS.d/ (which is more like the initial boot
4037 <p
>This summary might make it clearer. When booting for the first
4038 time into single user mode, the following commands are executed:
4039 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
4040 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
4041 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
4042 trying to continue after visiting single user mode. Not all services
4043 are started again as they should, causing the machine to end up in an
4044 unpredicatble state. This is why Debian admins recommend rebooting
4045 after visiting single user mode.
</p
>
4047 <p
>A similar problem with runlevel
1 is caused by the amount of
4048 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
4049 to runlevel
1, the services started from /etc/rcS.d/ are not properly
4050 stopped when passing through the scripts in /etc/rc1.d/, and not
4051 started again when switching away from runlevel
1 to the runlevels
4052 2-
5. I believe the problem is best fixed by moving all the scripts
4053 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
4054 functioning single user mode during boot.
</p
>
4056 <p
>I have spent several years investigating the Debian boot system,
4057 and discovered this problem a few years ago. I suspect it originates
4058 from when sysvinit was introduced into Debian, a long time ago.
</p
>
4063 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
4064 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
4065 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
4066 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
4067 <description><p
>In the Debian boot system, several packages include scripts that
4068 are started from /etc/rcS.d/. In fact, there is a bite more of them
4069 than make sense, and this causes a few problems. What kind of
4070 problems, you might ask. There are at least two problems. The first
4071 is that it is not possible to recover a machine after switching to
4072 runlevel
1. One need to actually reboot to get the machine back to
4073 the expected state. The other is that single user boot will sometimes
4074 run into problems because some of the subsystems are activated before
4075 the root login is presented, causing problems when trying to recover a
4076 machine from a problem in that subsystem. A minor additional point is
4077 that moving more scripts out of rcS.d/ and into the other rc#.d/
4078 directories will increase the amount of scripts that can run in
4079 parallel during boot, and thus decrease the boot time.
</p
>
4081 <p
>So, which scripts should start from rcS.d/. In short, only the
4082 scripts that _have_ to execute before the root login prompt is
4083 presented during a single user boot should go there. Everything else
4084 should go into the numeric runlevels. This means things like
4085 lm-sensors, fuse and x11-common should not run from rcS.d, but from
4086 the numeric runlevels. Today in Debian, there are around
115 init.d
4087 scripts that are started from rcS.d/, and most of them should be moved
4088 out. Do your package have one of them? Please help us make single
4089 user and runlevel
1 better by moving it.
</p
>
4091 <p
>Scripts setting up the screen, keyboard, system partitions
4092 etc. should still be started from rcS.d/, but there is for example no
4093 need to have the network enabled before the single user login prompt
4094 is presented.
</p
>
4096 <p
>As always, things are not so easy to fix as they sound. To keep
4097 Debian systems working while scripts migrate and during upgrades, the
4098 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
4099 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
4100 and the next ones can only be moved when their dependencies have been
4101 moved first. This migration must be done sequentially while we ensure
4102 that the package system upgrade packages in the right order to keep
4103 the system state correct. This will require some coordination when it
4104 comes to network related packages, but most of the packages with
4105 scripts that should migrate do not have anything in rcS.d/ depending
4106 on them. Some packages have already been updated, like the sudo
4107 package, while others are still left to do. I wish I had time to work
4108 on this myself, but real live constrains make it unlikely that I will
4109 find time to push this forward.
</p
>
4114 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
4115 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
4116 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
4117 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
4118 <description><p
>While at Debconf11, I have several times during discussions
4119 mentioned the issues I believe should be improved in Debian for its
4120 desktop to be useful for more people. The use case for this is my
4121 parents, which are currently running Kubuntu which solve the
4124 <p
>I suspect these four missing features are not very hard to
4125 implement. After all, they are present in Ubuntu, so if we wanted to
4126 do this in Debian we would have a source.
</p
>
4130 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
4131 are new packages available for upgrades, a icon in the KDE status bar
4132 indicate this, and clicking on it will activate the simple upgrade
4133 tool to handle it. I have no problem guiding both of my parents
4134 through the process over the phone. If a kernel reboot is required,
4135 this too is indicated by the status bars and the upgrade tool. Last
4136 time I checked, nothing with the same features was working in KDE in
4139 <li
><strong
>Simple handling of missing Firefox browser
4140 plugins.
</strong
> When the browser encounter a MIME type it do not
4141 currently have a handler for, it will ask the user if the system
4142 should search for a package that would add support for this MIME type,
4143 and if the user say yes, the APT sources will be searched for packages
4144 advertising the MIME type in their control file (visible in the
4145 Packages file in the APT archive). If one or more packages are found,
4146 it is a simple click of the mouse to add support for the missing mime
4147 type. If the package require the user to accept some non-free
4148 license, this is explained to the user. The entire process make it
4149 more clear to the user why something do not work in the browser, and
4150 make the chances higher for the user to blame the web page authors and
4151 not the browser for any missing features.
</li
>
4153 <li
><strong
>Simple handling of missing multimedia codec/format
4154 handlers.
</strong
> When the media players encounter a format or codec
4155 it is not supporting, a dialog pop up asking the user if the system
4156 should search for a package that would add support for it. This
4157 happen with things like MP3, Windows Media or H
.264. The selection
4158 and installation procedure is very similar to the Firefox browser
4159 plugin handling. This is as far as I know implemented using a
4160 gstreamer hook. The end result is that the user easily get access to
4161 the codecs that are present from the APT archives available, while
4162 explaining more on why a given format is unsupported by Ubuntu.
</li
>
4164 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
4165 displaying a text/plain file in my Debian browser, it will propose to
4166 start emacs to show it. If I remember correctly, when doing the same
4167 in Kunbutu it show the file as a text file in the browser. At least I
4168 know Opera will show text files within the browser. I much prefer the
4169 latter behaviour.
</li
>
4173 <p
>There are other nice features as well, like the simplified suite
4174 upgrader, but given that I am the one mostly doing the dist-upgrade,
4175 it do not matter much.
</p
>
4177 <p
>I really hope we could get these features in place for the next
4178 Debian release. It would require the coordinated effort of several
4179 maintainers, but would make the end user experience a lot better.
</p
>
4184 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
4185 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
4186 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
4187 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
4188 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
4189 site is build on Debian/Squeeze, and this platform was chosen because
4190 I am most familiar with Debian (being a Debian Developer for around
10
4191 years) because it is the latest stable Debian release which should get
4192 security support for a few years.
</p
>
4194 <p
>The web service is written in Perl, and depend on some perl modules
4195 that are missing in Debian at the moment. It would be great if these
4196 modules were added to the Debian archive, allowing anyone to set up
4197 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
4198 in their own country using only Debian packages. The list of modules
4199 missing in Debian/Squeeze isn
't very long, and I hope the perl group
4200 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
4201 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4202 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4203 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4204 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4205 easier in the future.
</p
>
4207 <p
>Thanks to the great tools in Debian, getting the missing modules
4208 installed on my server was a simple call to
'cpan2deb Module::Name
'
4209 and
'dpkg -i
' to install the resulting package. But this leave me
4210 with the responsibility of tracking security problems, which I really
4211 do not have time for.
</p
>
4216 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
4217 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
4218 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
4219 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
4220 <description><p
>Here is a small update for my English readers. Most of my blog
4221 posts have been in Norwegian the last few weeks, so here is a short
4222 update in English.
</p
>
4224 <p
>The kids still keep me too busy to get much free software work
4225 done, but I did manage to organise a project to get a Norwegian port
4226 of the British service
4227 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
4228 and it has been running for a month now. The entire project has been
4229 organised by me and two others. Around Christmas we gathered sponsors
4230 to fund the development work. In January I drafted a contract with
4231 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
4232 and in February the development took place. Most of it involved
4233 converting the source to use GPS coordinates instead of British
4234 easting/northing, and the resulting code should be a lot easier to get
4235 running in any country by now. The Norwegian
4236 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
4237 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
4238 source and the source for administrative borders in Norway, and
4239 support for this had to be added/fixed.
</p
>
4241 <p
>The Norwegian version went live March
3th, and we spent the weekend
4242 polishing the system before we announced it March
7th. The system is
4243 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
4244 problem reports in a few weeks. Soon we hope to announce the Android
4245 and iPhone versions making it even easier to report problems with the
4246 public infrastructure.
</p
>
4248 <p
>Perhaps something to consider for those of you in countries without
4249 such service?
</p
>
4254 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
4255 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
4256 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
4257 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
4258 <description><p
>The last few days I have looked at ways to track open security
4259 issues here at my work with the University of Oslo. My idea is that
4260 it should be possible to use the information about security issues
4261 available on the Internet, and check our locally
4262 maintained/distributed software against this information. It should
4263 allow us to verify that no known security issues are forgotten. The
4264 CVE database listing vulnerabilities seem like a great central point,
4265 and by using the package lists from Debian mapped to CVEs provided by
4266 the testing security team, I believed it should be possible to figure
4267 out which security holes were present in our free software
4268 collection.
</p
>
4270 <p
>After reading up on the topic, it became obvious that the first
4271 building block is to be able to name software packages in a unique and
4272 consistent way across data sources. I considered several ways to do
4273 this, for example coming up with my own naming scheme like using URLs
4274 to project home pages or URLs to the Freshmeat entries, or using some
4275 existing naming scheme. And it seem like I am not the first one to
4276 come across this problem, as MITRE already proposed and implemented a
4277 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
4278 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
4279 software, hardware and other platform components. The CPE ids are
4280 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
4281 Vulnerability Database
</a
>, allowing me to look up know security
4282 issues for any CPE name. With this in place, all I need to do is to
4283 locate the CPE id for the software packages we use at the university.
4284 This is fairly trivial (I google for
'cve cpe $package
' and check the
4285 NVD entry if a CVE for the package exist).
</p
>
4287 <p
>To give you an example. The GNU gzip source package have the CPE
4288 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
4289 check out, one could look up
4290 <a href=
"http://web.nvd.nist.gov/view/vuln/search?cpe=cpe%
3A%
2Fa%
3Agnu%
3Agzip:
1.3.3">cpe:/a:gnu:gzip:
1.3.3
4291 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
4292 The most recent one is
4293 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
4294 and at the bottom of the NVD page for this vulnerability the complete
4295 list of affected versions is provided.
</p
>
4297 <p
>The NVD database of CVEs is also available as a XML dump, allowing
4298 for offline processing of issues. Using this dump, I
've written a
4299 small script taking a list of CPEs as input and list all CVEs
4300 affecting the packages represented by these CPEs. One give it CPEs
4301 with version numbers as specified above and get a list of open
4302 security issues out.
</p
>
4304 <p
>Of course for this approach to be useful, the quality of the NVD
4305 information need to be high. For that to happen, I believe as many as
4306 possible need to use and contribute to the NVD database. I notice
4308 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
4309 map from CVE to CPE
</a
>, indicating that they are using the CPE
4310 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
4312 <p
>To get an idea about the quality for free software, I spent some
4313 time making it possible to compare the CVE database from Debian with
4314 the CVE database in NVD. The result look fairly good, but there are
4315 some inconsistencies in NVD (same software package having several
4316 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4317 Debian believe are affected by a CVE). Hope to find time to improve
4318 the quality of NVD, but that require being able to get in touch with
4319 someone maintaining it. So far my three emails with questions and
4320 corrections have not seen any reply, but I hope contact can be
4321 established soon.
</p
>
4323 <p
>An interesting application for CPEs is cross platform package
4324 mapping. It would be useful to know which packages in for example
4325 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4326 this would be trivial if all linux distributions provided CPE entries
4327 for their packages.
</p
>
4332 <title>Which module is loaded for a given PCI and USB device?
</title>
4333 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
4334 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
4335 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
4336 <description><p
>In the
4337 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
4338 package in Debian, there is a script to report useful information
4339 about the running hardware for use when people report missing
4340 information. One part of this script that I find very useful when
4341 debugging hardware problems, is the part mapping loaded kernel module
4342 to the PCI device it claims. It allow me to quickly see if the kernel
4343 module I expect is driving the hardware I am struggling with. To see
4344 the output, make sure discover-data is installed and run
4345 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
4346 one of my machines like this:
</p
>
4350 10de:
03eb i2c_nforce2
4353 10de:
03f0 snd_hda_intel
4362 <p
>The code in question look like this, slightly modified for
4363 readability and to drop the output to file descriptor
3:
</p
>
4366 if [ -d /sys/bus/pci/devices/ ] ; then
4367 echo loaded pci modules:
4369 cd /sys/bus/pci/devices/
4370 for address in * ; do
4371 if [ -d
"$address/driver/module
" ] ; then
4372 module=`cd $address/driver/module ; pwd -P | xargs basename`
4373 if grep -q
"^$module
" /proc/modules ; then
4374 address=$(echo $address |sed s/
0000://)
4375 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
4376 echo
"$id $module
"
4385 <p
>Similar code could be used to extract USB device module
4389 if [ -d /sys/bus/usb/devices/ ] ; then
4390 echo loaded usb modules:
4392 cd /sys/bus/usb/devices/
4393 for address in * ; do
4394 if [ -d
"$address/driver/module
" ] ; then
4395 module=`cd $address/driver/module ; pwd -P | xargs basename`
4396 if grep -q
"^$module
" /proc/modules ; then
4397 address=$(echo $address |sed s/
0000://)
4398 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
4399 if [
"$id
" ] ; then
4400 echo
"$id $module
"
4410 <p
>This might perhaps be something to include in other tools as
4416 <title>How to test if a laptop is working with Linux
</title>
4417 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
4418 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
4419 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
4420 <description><p
>The last few days I have spent at work here at the
<a
4421 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
4422 batch of computers will work with Linux. Every year for the last few
4423 years the university have organised shared bid of a few thousand
4424 computers, and this year HP won the bid. Two different desktops and
4425 five different laptops are on the list this year. We in the UNIX
4426 group want to know which one of these computers work well with RHEL
4427 and Ubuntu, the two Linux distributions we currently handle at the
4428 university.
</p
>
4430 <p
>My test method is simple, and I share it here to get feedback and
4431 perhaps inspire others to test hardware as well. To test, I PXE
4432 install the OS version of choice, and log in as my normal user and run
4433 a few applications and plug in selected pieces of hardware. When
4434 something fail, I make a note about this in the test matrix and move
4435 on. If I have some spare time I try to report the bug to the OS
4436 vendor, but as I only have the machines for a short time, I rarely
4437 have the time to do this for all the problems I find.
</p
>
4439 <p
>Anyway, to get to the point of this post. Here is the simple tests
4440 I perform on a new model.
</p
>
4444 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
4445 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4446 RHEL5 and Debian Edu/Squeeze.
</li
>
4448 <li
>Is X.org working? If the graphical login screen show up after
4449 installation, X.org is working.
</li
>
4451 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
4452 package mesa-utils on Ubuntu) and writing down the frames per second
4453 reported by the program.
</li
>
4455 <li
>Is sound working? With Gnome and KDE, a sound is played when
4456 logging in, and if I can hear this the test is successful. If there
4457 are several audio exits on the machine, I try them all and check if
4458 the Gnome/KDE audio mixer can control where to send the sound. I
4459 normally test this by playing
4460 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
4461 video
</a
> in Firefox/Iceweasel.
</li
>
4463 <li
>Is the USB subsystem working? I test this by plugging in a USB
4464 memory stick and see if Gnome/KDE notices this.
</li
>
4466 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
4467 I have lying around, and see if Gnome/KDE notices this.
</li
>
4469 <li
>Is any built in camera working? Test using cheese, and see if a
4470 picture from the v4l device show up.
</li
>
4472 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4473 any bluetooth devices are discovered. In my office, I normally see a
4476 <li
>For laptops, is the SD or Compaq Flash reader working. I have
4477 memory modules lying around, and stick them in and see if Gnome/KDE
4478 notice this.
</li
>
4480 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
4481 special button work, and if the laptop continue to work after
4484 <li
>For laptops, is the extra buttons working, like audio level,
4485 adjusting background light, switching on/off external video output,
4486 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4487 laptop to laptop, so I just write down which are working and which are
4490 <li
>Some laptops have smart card readers, finger print readers,
4491 acceleration sensors etc. I rarely test these, as I do not know how
4492 to quickly test if they are working or not, so I only document their
4493 existence.
</li
>
4497 <p
>By now I suspect you are really curious what the test results are
4498 for the HP machines I am testing. I
'm not done yet, so I will report
4499 the test results later. For now I can report that HP
8100 Elite work
4500 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
4501 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
4502 can see, I have most machines left to test. One interesting
4503 observation is that Ubuntu Lucid has almost twice the frame rate than
4504 RHEL6 with glxgears. No idea why.
</p
>
4509 <title>Some thoughts on BitCoins
</title>
4510 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
4511 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
4512 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
4513 <description><p
>As I continue to explore
4514 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
4515 what properties the system have, and how it will be affected by laws
4516 and regulations here in Norway. Here are some random notes.
</p
>
4518 <p
>One interesting thing to note is that since the transactions are
4519 verified using a peer to peer network, all details about a transaction
4520 is known to everyone. This means that if a BitCoin address has been
4521 published like I did with mine in my initial post about BitCoin, it is
4522 possible for everyone to see how many BitCoins have been transfered to
4523 that address. There is even a web service to look at the details for
4524 all transactions. There I can see that my address
4525 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
4526 have received
16.06 Bitcoin, the
4527 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
4528 address of Simon Phipps have received
181.97 BitCoin and the address
4529 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
4530 of EFF have received
2447.38 BitCoins so far. Thank you to each and
4531 every one of you that donated bitcoins to support my activity. The
4532 fact that anyone can see how much money was transfered to a given
4533 address make it more obvious why the BitCoin community recommend to
4534 generate and hand out a new address for each transaction. I
'm told
4535 there is no way to track which addresses belong to a given person or
4536 organisation without the person or organisation revealing it
4537 themselves, as Simon, EFF and I have done.
</p
>
4539 <p
>In Norway, and in most other countries, there are laws and
4540 regulations limiting how much money one can transfer across the border
4541 without declaring it. There are money laundering, tax and accounting
4542 laws and regulations I would expect to apply to the use of BitCoin.
4543 If the Skolelinux foundation
4544 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
4545 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
4546 normal bank transfers like EFF is doing, how should this be accounted?
4547 Given that it is impossible to know if money can cross the border or
4548 not, should everything or nothing be declared? What exchange rate
4549 should be used when calculating taxes? Would receivers have to pay
4550 income tax if the foundation were to pay Skolelinux contributors in
4551 BitCoin? I have no idea, but it would be interesting to know.
</p
>
4553 <p
>For a currency to be useful and successful, it must be trusted and
4554 accepted by a lot of users. It must be possible to get easy access to
4555 the currency (as a wage or using currency exchanges), and it must be
4556 easy to spend it. At the moment BitCoin seem fairly easy to get
4557 access to, but there are very few places to spend it. I am not really
4558 a regular user of any of the vendor types currently accepting BitCoin,
4559 so I wonder when my kind of shop would start accepting BitCoins. I
4560 would like to buy electronics, travels and subway tickets, not herbs
4561 and books. :) The currency is young, and this will improve over time
4562 if it become popular, but I suspect regular banks will start to lobby
4563 to get BitCoin declared illegal if it become popular. I
'm sure they
4564 will claim it is helping fund terrorism and money laundering (which
4565 probably would be true, as is any currency in existence), but I
4566 believe the problems should be solved elsewhere and not by blaming
4567 currencies.
</p
>
4569 <p
>The process of creating new BitCoins is called mining, and it is
4570 CPU intensive process that depend on a bit of luck as well (as one is
4571 competing against all the other miners currently spending CPU cycles
4572 to see which one get the next lump of cash). The
"winner
" get
50
4573 BitCoin when this happen. Yesterday I came across the obvious way to
4574 join forces to increase ones changes of getting at least some coins,
4575 by coordinating the work on mining BitCoins across several machines
4576 and people, and sharing the result if one is lucky and get the
50
4578 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
4579 if this sounds interesting. I have not had time to try to set up a
4580 machine to participate there yet, but have seen that running on ones
4581 own for a few days have not yield any BitCoins througth mining
4584 <p
>Update
2010-
12-
15: Found an
<a
4585 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
4586 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
4587 it was interesting to read. The arguments presented seem to be
4588 equally valid for gold, which was used as a currency for many years.
</p
>
4593 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
4594 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
4595 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
4596 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
4597 <description><p
>With this weeks lawless
4598 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
4599 attacks
</a
> on Wikileak and
4600 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
4601 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
4602 not be trusted to handle money transactions.
4604 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
4605 Phipps on bitcoin
</a
> reminded me about a project that a friend of
4606 mine mentioned earlier. I decided to follow Simon
's example, and get
4607 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
4608 some help from my friend to get it all running, and he even handed me
4609 some bitcoins to get started. I even donated a few bitcoins to Simon
4610 for helping me remember BitCoin.
</p
>
4612 <p
>So, what is bitcoins, you probably wonder? It is a digital
4613 crypto-currency, decentralised and handled using peer-to-peer
4614 networks. It allows anonymous transactions and prohibits central
4615 control over the transactions, making it impossible for governments
4616 and companies alike to block donations and other transactions. The
4617 source is free software, and while the key dependency wxWidgets
2.9
4618 for the graphical user interface is missing in Debian, the command
4619 line client builds just fine. Hopefully Jonas
4620 <a href=
"http://bugs.debian.org/
578157">will get the package into
4621 Debian
</a
> soon.
</p
>
4623 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
4624 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
4625 bitcoins
</a
> when selling services and goods, and there are even
4626 currency
"stock
" markets where the exchange rate is decided. There
4627 are not many users so far, but the concept seems promising. If you
4628 want to get started and lack a friend with any bitcoins to spare,
4630 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
4631 bitcoin at the time of writing). Use
4632 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
4633 on the current exchange rates.
</p
>
4635 <p
>As an experiment, I have decided to set up bitcoind on one of my
4636 machines. If you want to support my activity, please send Bitcoin
4637 donations to the address
4638 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
4643 <title>Why isn
't Debian Edu using VLC?
</title>
4644 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
4645 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
4646 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
4647 <description><p
>In the latest issue of Linux Journal, the readers choices were
4648 presented, and the winner among the multimedia player were VLC.
4649 Personally, I like VLC, and it is my player of choice when I first try
4650 to play a video file or stream. Only if VLC fail will I drag out
4651 gmplayer to see if it can do better. The reason is mostly the failure
4652 model and trust. When VLC fail, it normally pop up a error message
4653 reporting the problem. When mplayer fail, it normally segfault or
4654 just hangs. The latter failure mode drain my trust in the program.
<p
>
4656 <p
>But even if VLC is my player of choice, we have choosen to use
4657 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
4658 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
4659 plugin to play web videos seamlessly, and the VLC browser plugin is
4660 not very good. For example, it lack in-line control buttons, so there
4661 is no way for the user to pause the video. Also, when I
4662 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
4663 tested the browser plugins
</a
> available in Debian, the VLC plugin
4664 failed on several video pages where mplayer based plugins worked. If
4665 the browser plugin for VLC was as good as the gecko-mediaplayer
4666 package (which uses mplayer), we would switch.
</P
>
4668 <p
>While VLC is a good player, its user interface is slightly
4669 annoying. The most annoying feature is its inconsistent use of
4670 keyboard shortcuts. When the player is in full screen mode, its
4671 shortcuts are different from when it is playing the video in a window.
4672 For example, space only work as pause when in full screen mode. I
4673 wish it had consisten shortcuts and that space also would work when in
4674 window mode. Another nice shortcut in gmplayer is [enter] to restart
4675 the current video. It is very nice when playing short videos from the
4676 web and want to restart it when new people arrive to have a look at
4677 what is going on.
</p
>
4682 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
4683 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
4684 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</guid>
4685 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
4686 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
4687 upgrade testing of the
4688 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
4689 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
4690 This seem like a very good idea, so I adjusted by test scripts and
4691 can now present the updated result from today:
</p
>
4693 <p
>This is for Gnome:
</p
>
4695 <p
>Installed using apt-get, missing with aptitude
</p
>
4697 <blockquote
><p
>
4702 browser-plugin-gnash
4709 freedesktop-sound-theme
4711 gconf-defaults-service
4726 gnome-desktop-environment
4730 gnome-session-canberra
4735 gstreamer0.10-fluendo-mp3
4741 libapache2-mod-dnssd
4744 libaprutil1-dbd-sqlite3
4747 libboost-date-time1.42
.0
4748 libboost-python1.42
.0
4749 libboost-thread1.42
.0
4751 libchamplain-gtk-
0.4-
0
4753 libclutter-gtk-
0.10-
0
4760 libfreerdp-plugins-standard
4775 libgnomepanel2.24-cil
4780 libgtksourceview2.0-common
4781 libmono-addins-gui0.2-cil
4782 libmono-addins0.2-cil
4783 libmono-cairo2.0-cil
4784 libmono-corlib2.0-cil
4785 libmono-i18n-west2.0-cil
4786 libmono-posix2.0-cil
4787 libmono-security2.0-cil
4788 libmono-sharpzip2.84-cil
4789 libmono-system2.0-cil
4792 libndesk-dbus-glib1.0-cil
4793 libndesk-dbus1.0-cil
4803 libtelepathy-farsight0
4812 nautilus-sendto-empathy
4816 python-aptdaemon-gtk
4818 python-beautifulsoup
4833 python-gtksourceview2
4844 python-pkg-resources
4851 python-twisted-conch
4857 python-zope.interface
4862 rhythmbox-plugin-cdrecorder
4869 system-config-printer-udev
4871 telepathy-mission-control-
5
4882 </p
></blockquote
>
4884 <p
>Installed using apt-get, removed with aptitude
</p
>
4886 <blockquote
><p
>
4892 fast-user-switch-applet
4911 libgtksourceview2.0-
0
4913 libsdl1.2debian-alsa
4919 system-config-printer
4924 </p
></blockquote
>
4926 <p
>Installed using aptitude, missing with apt-get
</p
>
4928 <blockquote
><p
>
4929 gstreamer0.10-gnomevfs
4930 </p
></blockquote
>
4932 <p
>Installed using aptitude, removed with apt-get
</p
>
4934 <blockquote
><p
>
4936 </p
></blockquote
>
4938 <p
>This is for KDE:
</p
>
4940 <p
>Installed using apt-get, missing with aptitude
</p
>
4942 <blockquote
><p
>
4944 </p
></blockquote
>
4946 <p
>Installed using apt-get, removed with aptitude
</p
>
4948 <blockquote
><p
>
4951 </p
></blockquote
>
4953 <p
>Installed using aptitude, missing with apt-get
</p
>
4955 <blockquote
><p
>
4969 kdeartwork-emoticons
4971 kdeartwork-theme-icon
4975 kdebase-workspace-bin
4976 kdebase-workspace-data
4990 kscreensaver-xsavers
5005 plasma-dataengines-workspace
5007 plasma-desktopthemes-artwork
5008 plasma-runners-addons
5009 plasma-scriptengine-googlegadgets
5010 plasma-scriptengine-python
5011 plasma-scriptengine-qedje
5012 plasma-scriptengine-ruby
5013 plasma-scriptengine-webkit
5014 plasma-scriptengines
5015 plasma-wallpapers-addons
5016 plasma-widget-folderview
5017 plasma-widget-networkmanagement
5021 xscreensaver-data-extra
5023 xscreensaver-gl-extra
5024 xscreensaver-screensaver-bsod
5025 </p
></blockquote
>
5027 <p
>Installed using aptitude, removed with apt-get
</p
>
5029 <blockquote
><p
>
5031 google-gadgets-common
5049 libggadget-qt-
1.0-
0b
5054 libkonqsidebarplugin4a
5063 libplasma-geolocation-interface4
5065 libplasmagenericshell4
5079 libsmokeknewstuff2-
3
5080 libsmokeknewstuff3-
3
5082 libsmokektexteditor3
5090 libsmokeqtnetwork4-
3
5096 libsmokeqtuitools4-
3
5108 plasma-dataengines-addons
5109 plasma-scriptengine-superkaramba
5110 plasma-widget-lancelot
5111 plasma-widgets-addons
5112 plasma-widgets-workspace
5116 update-notifier-common
5117 </p
></blockquote
>
5119 <p
>Running apt-get autoremove made the results using apt-get and
5120 aptitude a bit more similar, but there are still quite a lott of
5121 differences. I have no idea what packages should be installed after
5122 the upgrade, but hope those that do can have a look.
</p
>
5127 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
5128 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
5129 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
5130 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
5131 <description><p
>Most of the computers in use by the
5132 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
5133 are virtual machines. And they have been Xen machines running on a
5134 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
5135 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
5136 bit harder that it could have been, because we set up the Xen virtual
5137 machines to get the virtual partitions from LVM, which as far as I
5138 know is not supported by KVM. So to migrate, we had to convert
5139 several LVM logical volumes to partitions on a virtual disk file.
</p
>
5142 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
5143 nice recipe
</a
> to do this, and wrote the following script to do the
5144 migration. It uses qemu-img from the qemu package to make the disk
5145 image, parted to partition it, losetup and kpartx to present the disk
5146 image partions as devices, and dd to copy the data. I NFS mounted the
5147 new servers storage area on the old server to do the migration.
</p
>
5153 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5158 if [ -z
"$
1" ] ; then
5159 echo
"Usage: $
0 &lt;hostname
&gt;
"
5165 if [ ! -e /dev/vg_data/$host-disk ] ; then
5166 echo
"error: unable to find LVM volume for $host
"
5170 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5171 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5172 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
5173 totalsize=$(( ( $disksize + $swapsize ) ))
5176 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
5177 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5179 parted $img mklabel msdos
5180 parted $img mkpart primary linux-swap
0 $disksize
5181 parted $img mkpart primary ext2 $disksize $totalsize
5182 parted $img set
1 boot on
5185 losetup /dev/loop0 $img
5186 kpartx -a /dev/loop0
5188 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
5189 fsck.ext3 -f /dev/mapper/loop0p1 || true
5190 mkswap /dev/mapper/loop0p2
5192 kpartx -d /dev/loop0
5193 losetup -d /dev/loop0
5196 <p
>The script is perhaps so simple that it is not copyrightable, but
5197 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
5199 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
5200 the new disk image attached, installed grub-pc and linux-image-
686 and
5201 set up grub to boot from the disk image. After this, the KVM machines
5202 seem to work just fine.
</p
>
5207 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
5208 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
5209 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
5210 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
5211 <description><p
>I
'm still running upgrade testing of the
5212 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
5213 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
5214 status. Here is a short update based on a test I ran
20101118.
</p
>
5216 <p
>I still do not know what a correct migration should look like, so I
5217 report any differences between apt and aptitude and hope someone else
5218 can see if anything should be changed.
</p
>
5220 <p
>This is for Gnome:
</p
>
5222 <p
>Installed using apt-get, missing with aptitude
</p
>
5224 <blockquote
><p
>
5225 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5226 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
5227 dmz-cursor-theme empathy empathy-common finger
5228 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5229 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5230 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5231 gnome-cards-data gnome-codec-install gnome-core
5232 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5233 gnome-search-tool gnome-session-canberra gnome-spell
5234 gnome-system-log gnome-themes-extras gnome-themes-more
5235 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5236 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5237 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5238 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5239 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
5240 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
5241 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
5242 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
5243 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
5244 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5245 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
5246 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5247 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5248 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5249 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5250 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5251 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5252 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5253 libmono-security2.0-cil libmono-sharpzip2.84-cil
5254 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
5255 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
5256 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
5257 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
5258 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
5259 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
5260 libxalan2-java libxerces2-java media-player-info mesa-utils
5261 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
5262 nautilus-sendto-empathy openoffice.org-writer2latex
5263 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
5264 python-aptdaemon python-aptdaemon-gtk python-axiom
5265 python-beautifulsoup python-bugbuddy python-clientform
5266 python-coherence python-configobj python-crypto python-cupshelpers
5267 python-cupsutils python-eggtrayicon python-elementtree
5268 python-epsilon python-evolution python-feedparser python-gdata
5269 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5270 python-gtksourceview2 python-httplib2 python-louie python-mako
5271 python-markupsafe python-mechanize python-nevow python-notify
5272 python-opengl python-openssl python-pam python-pkg-resources
5273 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5274 python-tagpy python-twisted-bin python-twisted-conch
5275 python-twisted-core python-twisted-web python-utidylib python-webkit
5276 python-xdg python-zope.interface remmina remmina-plugin-data
5277 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5278 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5279 software-center svgalibg1 system-config-printer-udev
5280 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
5281 totem totem-coherence totem-mozilla totem-plugins
5282 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5284 </p
></blockquote
>
5286 Installed using apt-get, removed with aptitude
5288 <blockquote
><p
>
5289 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5290 epiphany-extensions epiphany-gecko evolution-exchange
5291 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5292 gedit-common gnome-app-install gnome-games gnome-games-data
5293 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5294 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5295 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5296 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
5297 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
5298 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
5299 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
5300 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
5301 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
5302 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
5303 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
5304 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
5305 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5306 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5307 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5308 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5309 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
5310 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
5311 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
5312 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
5313 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
5314 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5315 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5316 sound-juicer swfdec-gnome system-config-printer totem-common
5317 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5318 </p
></blockquote
>
5320 <p
>Installed using aptitude, missing with apt-get
</p
>
5322 <blockquote
><p
>
5323 gstreamer0.10-gnomevfs
5324 </p
></blockquote
>
5326 <p
>Installed using aptitude, removed with apt-get
</p
>
5328 <blockquote
><p
>
5330 </p
></blockquote
>
5332 <p
>This is for KDE:
</p
>
5334 <p
>Installed using apt-get, missing with aptitude
</p
>
5336 <blockquote
><p
>
5337 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
5338 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5339 ghostscript-x git gnome-audio gnugo granatier gs-common
5340 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5341 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5342 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5343 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5344 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5345 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5346 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5347 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5348 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5349 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5350 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5351 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
5352 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5353 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5354 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5355 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5356 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5357 libkrossui4 libmailtools-perl libmime-tools-perl
5358 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5359 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5360 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5361 lirc luatex marble networkstatus noatun-plugins
5362 openoffice.org-writer2latex palapeli palapeli-data parley
5363 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5364 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5365 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5367 </p
></blockquote
>
5369 <p
>Installed using apt-get, removed with aptitude
</p
>
5371 <blockquote
><p
>
5372 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5373 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5374 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5375 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5376 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5377 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5378 kitchensync kiten kjumpingcube klatin klettres klickety klines
5379 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5380 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5381 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5382 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5383 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5384 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5385 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5386 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5387 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5388 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
5389 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
5390 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5391 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
5392 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
5393 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5394 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5395 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5396 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5397 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5398 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5399 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
5400 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
5401 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5402 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5403 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5404 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5405 </p
></blockquote
>
5407 <p
>Installed using aptitude, missing with apt-get
</p
>
5409 <blockquote
><p
>
5410 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5411 kdeartwork kdebase kdebase-apps kdebase-workspace
5412 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5413 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5414 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5415 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5416 xscreensaver-screensaver-bsod
5417 </p
></blockquote
>
5419 <p
>Installed using aptitude, removed with apt-get
</p
>
5421 <blockquote
><p
>
5422 kdebase-bin konq-plugins konqueror
5423 </p
></blockquote
>
5428 <title>Gnash buildbot slave and Debian kfreebsd
</title>
5429 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
5430 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
5431 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
5432 <description><p
>Answering
5433 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
5434 call from the Gnash project
</a
> for
5435 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
5436 current source, I have set up a virtual KVM machine on the Debian
5437 Edu/Skolelinux virtualization host to test the git source on
5438 Debian/Squeeze. I hope this can help the developers in getting new
5439 releases out more often.
</p
>
5441 <p
>As the developers want less main-stream build platforms tested to,
5442 I have considered setting up a
<a
5443 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
5444 machine as well. I have also considered using the kfreebsd
5445 architecture in Debian as a file server in NUUG to get access to the
5
5446 TB zfs volume we currently use to store DV video. Because of this, I
5447 finally got around to do a test installation of Debian/Squeeze with
5448 kfreebsd. Installation went fairly smooth, thought I noticed some
5449 visual glitches in the cdebconf dialogs (black cursor left on the
5450 screen at random locations). Have not gotten very far with the
5451 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5452 fatal problem. Have to spend some more time on it to see if it is
5453 useful as a file server for NUUG. Will try to find time to set up a
5454 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
5459 <title>Debian in
3D
</title>
5460 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
5461 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
5462 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
5463 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
5465 <p
>3D printing is just great. I just came across this Debian logo in
5467 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
5468 thingiverse blog
</a
>.
</p
>
5473 <title>Software updates
2010-
10-
24</title>
5474 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
5475 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
5476 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
5477 <description><p
>Some updates.
</p
>
5479 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
5480 raise money for the project is going well. The lower limit of
10
5481 signers was reached in
24 hours, and so far
13 people have signed it.
5482 More signers and more funding is most welcome, and I am really curious
5483 how far we can get before the time limit of December
24 is reached.
5486 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
5487 about what appear to be a great code coverage tool capable of
5488 generating code coverage stats without any changes to the source code.
5490 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
5491 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
5492 It is missing in Debian, but the git source built just fine in Squeeze
5493 after I installed libelf-dev, libdwarf-dev, pkg-config and
5494 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5495 solvable. I hope kcov make it into Debian soon.
</p
>
5497 <p
>Finally found time to wrap up the release notes for
<a
5498 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
5499 new alpha release of Debian Edu
</a
>, and just published the second
5500 alpha test release of the Squeeze based Debian Edu /
5501 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
5502 release. Give it a try if you need a complete linux solution for your
5503 school, including central infrastructure server, workstations, thin
5504 client servers and diskless workstations. A nice touch added
5505 yesterday is RDP support on the thin client servers, for windows
5506 clients to get a Linux desktop on request.
</p
>
5511 <title>Some notes on Flash in Debian and Debian Edu
</title>
5512 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
5513 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
5514 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
5515 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
5516 popularity-contest numbers
</a
>, the adobe-flashplugin package the
5517 second most popular used package that is missing in Debian. The sixth
5518 most popular is flashplayer-mozilla. This is a clear indication that
5519 working flash is important for Debian users. Around
10 percent of the
5520 users submitting data to popcon.debian.org have this package
5521 installed.
</p
>
5523 <p
>In the report written by Lars Risan in August
2008
5524 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
5525 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5526 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
5527 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
5528 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
5529 web sites require Flash to work, and lacking working Flash support in
5530 the web browser and the problems with installing it was perceived as a
5531 good reason to stay with Windows.
</p
>
5533 <p
>I once saw a funny and sad comment in a web forum, where Linux was
5534 said to be the retarded cousin that did not really understand
5535 everything you told him but could work fairly well. This was a
5536 comment regarding the problems Linux have with proprietary formats and
5537 non-standard web pages, and is sad because it exposes a fairly common
5538 understanding of whose fault it is if web pages that only work in for
5539 example Internet Explorer
6 fail to work on Firefox, and funny because
5540 it explain very well how annoying it is for users when Linux
5541 distributions do not work with the documents they receive or the web
5542 pages they want to visit.
</p
>
5544 <p
>This is part of the reason why I believe it is important for Debian
5545 and Debian Edu to have a well working Flash implementation in the
5546 distribution, to get at least popular sites as Youtube and Google
5547 Video to working out of the box. For Squeeze, Debian have the chance
5548 to include the latest version of Gnash that will make this happen, as
5549 the new release
0.8.8 was published a few weeks ago and is resting in
5550 unstable. The new version work with more sites that version
0.8.7.
5551 The Gnash maintainers have asked for a freeze exception, but the
5552 release team have not had time to reply to it yet. I hope they agree
5553 with me that Flash is important for the Debian desktop users, and thus
5554 accept the new package into Squeeze.
</p
>
5559 <title>Circular package dependencies harms apt recovery
</title>
5560 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
5561 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
5562 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
5563 <description><p
>I discovered this while doing
5564 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
5565 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
5566 in Debian still got circular dependencies, and it is often claimed
5567 that apt and aptitude should be able to handle this just fine, but
5568 some times these dependency loops causes apt to fail.
</p
>
5570 <p
>An example is from todays
5571 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
5572 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
5573 causes perl-modules to fail to upgrade. The cause is simple. If a
5574 package fail to unpack, then only part of packages with the circular
5575 dependency might end up being unpacked when unpacking aborts, and the
5576 ones already unpacked will fail to configure in the recovery phase
5577 because its dependencies are unavailable.
</p
>
5579 <p
>In this log, the problem manifest itself with this error:
</p
>
5581 <blockquote
><pre
>
5582 dpkg: dependency problems prevent configuration of perl-modules:
5583 perl-modules depends on perl (
>=
5.10.1-
1); however:
5584 Version of perl on system is
5.10.0-
19lenny
2.
5585 dpkg: error processing perl-modules (--configure):
5586 dependency problems - leaving unconfigured
5587 </pre
></blockquote
>
5589 <p
>The perl/perl-modules circular dependency is already
5590 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
5591 hopefully be solved as soon as possible, but it is not the only one,
5592 and each one of these loops in the dependency tree can cause similar
5593 failures. Of course, they only occur when there are bugs in other
5594 packages causing the unpacking to fail, but it is rather nasty when
5595 the failure of one package causes the problem to become worse because
5596 of dependency loops.
</p
>
5599 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
5600 tireless effort by Bill Allombert
</a
>, the number of circular
5602 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
5603 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
5605 <p
>Todays testing also exposed a bug in
5606 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
5607 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
5608 apt-get and aptitude, the latter possibly caused by some circular
5609 dependency. Reported both to BTS to try to get someone to look at
5615 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
5616 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
5617 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
5618 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
5619 <description><p
>This is a
5620 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
5622 <a href=
"http://people.skolelinux.org/pere/blog/Idea_for_a_change_to_LDAP_schemas_allowing_DNS_and_DHCP_info_to_be_combined_into_one_object.html
">previous
5624 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
5625 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
5627 <p
>As a step to try to see if it possible to merge the DNS and DHCP
5628 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5629 and dhcp3-server-ldap in Debian use the LDAP server. The two
5630 implementations are quite different in how they use LDAP.
</p
>
5632 To get this information, I started slapd with debugging enabled and
5633 dumped the debug output to a file to get the LDAP searches performed
5634 on a Debian Edu main-server. Here is a summary.
5636 <p
><strong
>powerdns
</strong
></p
>
5638 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
5639 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
5642 <p
>PowerDNS have two modes of operation using LDAP as its backend.
5643 One
"strict
" mode where the forward and reverse DNS lookups are done
5644 using the same LDAP objects, and a
"tree
" mode where the forward and
5645 reverse entries are in two different subtrees in LDAP with a structure
5646 based on the DNS names, as in tjener.intern and
5647 2.2.0.10.in-addr.arpa.
</p
>
5649 <p
>In tree mode, the server is set up to use a LDAP subtree as its
5650 base, and uses a
"base
" scoped search for the DNS name by adding
5651 "dc=tjener,dc=intern,
" to the base with a filter for
5652 "(associateddomain=tjener.intern)
" for the forward entry and
5653 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
5654 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
5655 forward entries, it is looking for attributes named dnsttl, arecord,
5656 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5657 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5658 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5659 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5660 spfrecord and modifytimestamp. For reverse entries it is looking for
5661 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5662 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5663 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5664 ldapsearch commands could look like this:
</p
>
5666 <blockquote
><pre
>
5667 ldapsearch -h ldap \
5668 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5669 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
5670 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5671 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5672 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5673 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5675 ldapsearch -h ldap \
5676 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5677 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
5678 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5679 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5680 srvrecord naptrrecord modifytimestamp
5681 </pre
></blockquote
>
5683 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
5684 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5685 example LDAP objects used there. In addition to these objects, the
5686 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5687 also exist.
</p
>
5689 <blockquote
><pre
>
5690 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5692 objectclass: dnsdomain
5693 objectclass: domainrelatedobject
5696 associateddomain: tjener.intern
5698 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5700 objectclass: dnsdomain2
5701 objectclass: domainrelatedobject
5703 ptrrecord: tjener.intern
5704 associateddomain:
2.2.0.10.in-addr.arpa
5705 </pre
></blockquote
>
5707 <p
>In strict mode, the server behaves differently. When looking for
5708 forward DNS entries, it is doing a
"subtree
" scoped search with the
5709 same base as in the tree mode for a object with filter
5710 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
5711 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5712 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5713 naptrrecord and modifytimestamp. For reverse entires it also do a
5714 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
5715 and the requested attributes are associateddomain, dnsttl and
5716 modifytimestamp. In short, in strict mode the objects with ptrrecord
5717 go away, and the arecord attribute in the forward object is used
5720 <p
>The forward and reverse searches can be simulated using ldapsearch
5721 like this:
</p
>
5723 <blockquote
><pre
>
5724 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5725 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
5726 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5727 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5728 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5729 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5731 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5732 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
5733 </pre
></blockquote
>
5735 <p
>In addition to the forward and reverse searches , there is also a
5736 search for SOA records, which behave similar to the forward and
5737 reverse lookups.
</p
>
5739 <p
>A thing to note with the PowerDNS behaviour is that it do not
5740 specify any objectclass names, and instead look for the attributes it
5741 need to generate a DNS reply. This make it able to work with any
5742 objectclass that provide the needed attributes.
</p
>
5744 <p
>The attributes are normally provided in the cosine (RFC
1274) and
5745 dnsdomain2 schemas. The latter is used for reverse entries like
5746 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
5748 <p
>In Debian Edu, we have created DNS objects using the object classes
5749 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5750 attributes) and domainrelatedobject (for associatedDomain). The use
5751 of structural object classes make it impossible to combine these
5752 classes with the object classes used by DHCP.
</p
>
5754 <p
>There are other schemas that could be used too, for example the
5755 dnszone structural object class used by Gosa and bind-sdb for the DNS
5756 attributes combined with the domainrelatedobject object class, but in
5757 this case some unused attributes would have to be included as well
5758 (zonename and relativedomainname).
</p
>
5760 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
5761 mode and not use any of the existing objectclasses (dnsdomain,
5762 dnsdomain2 and dnszone) when one want to combine the DNS information
5763 with DHCP information, and instead create a auxiliary object class
5764 defined something like this (using the attributes defined for
5765 dnsdomain and dnsdomain2 or dnszone):
</p
>
5767 <blockquote
><pre
>
5768 objectclass ( some-oid NAME
'dnsDomainAux
'
5771 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5772 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5773 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5774 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5775 A6Record $ DNAMERecord
5777 </pre
></blockquote
>
5779 <p
>This will allow any object to become a DNS entry when combined with
5780 the domainrelatedobject object class, and allow any entity to include
5781 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
5782 developers asking for their view on this schema and if they are
5783 interested in providing such schema with PowerDNS, and I hope my
5784 message will be accepted into their mailing list soon.
</p
>
5786 <p
><strong
>ISC dhcp
</strong
></p
>
5788 <p
>The DHCP server searches for specific objectclass and requests all
5789 the object attributes, and then uses the attributes it want. This
5790 make it harder to figure out exactly what attributes are used, but
5791 thanks to the working example in Debian Edu I can at least get an idea
5792 what is needed without having to read the source code.
</p
>
5794 <p
>In the DHCP server configuration, the LDAP base to use and the
5795 search filter to use to locate the correct dhcpServer entity is
5796 stored. These are the relevant entries from
5797 /etc/dhcp3/dhcpd.conf:
</p
>
5799 <blockquote
><pre
>
5800 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
5801 ldap-dhcp-server-cn
"dhcp
";
5802 </pre
></blockquote
>
5804 <p
>The DHCP server uses this information to nest all the DHCP
5805 configuration it need. The cn
"dhcp
" is located using the given LDAP
5806 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
5807 search result is this entry:
</p
>
5809 <blockquote
><pre
>
5810 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5813 objectClass: dhcpServer
5814 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5815 </pre
></blockquote
>
5817 <p
>The content of the dhcpServiceDN attribute is next used to locate the
5818 subtree with DHCP configuration. The DHCP configuration subtree base
5819 is located using a base scope search with base
"cn=DHCP
5820 Config,dc=skole,dc=skolelinux,dc=no
" and filter
5821 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
5822 The search result is this entry:
</p
>
5824 <blockquote
><pre
>
5825 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5828 objectClass: dhcpService
5829 objectClass: dhcpOptions
5830 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5831 dhcpStatements: ddns-update-style none
5832 dhcpStatements: authoritative
5833 dhcpOption: smtp-server code
69 = array of ip-address
5834 dhcpOption: www-server code
72 = array of ip-address
5835 dhcpOption: wpad-url code
252 = text
5836 </pre
></blockquote
>
5838 <p
>Next, the entire subtree is processed, one level at the time. When
5839 all the DHCP configuration is loaded, it is ready to receive requests.
5840 The subtree in Debian Edu contain objects with object classes
5841 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5842 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5843 and information about netmasks, dynamic range etc. Leaving out the
5844 details here because it is not relevant for the focus of my
5845 investigation, which is to see if it is possible to merge dns and dhcp
5846 related computer objects.
</p
>
5848 <p
>When a DHCP request come in, LDAP is searched for the MAC address
5849 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
5850 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
5851 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5852 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
5855 <blockquote
><pre
>
5856 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5859 objectClass: dhcpHost
5860 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
5861 dhcpStatements: fixed-address hostname
5862 </pre
></blockquote
>
5864 <p
>There is less flexiblity in the way LDAP searches are done here.
5865 The object classes need to have fixed names, and the configuration
5866 need to be stored in a fairly specific LDAP structure. On the
5867 positive side, the invidiual dhcpHost entires can be anywhere without
5868 the DN pointed to by the dhcpServer entries. The latter should make
5869 it possible to group all host entries in a subtree next to the
5870 configuration entries, and this subtree can also be shared with the
5871 DNS server if the schema proposed above is combined with the dhcpHost
5872 structural object class.
5874 <p
><strong
>Conclusion
</strong
></p
>
5876 <p
>The PowerDNS implementation seem to be very flexible when it come
5877 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
5878 come to the the LDAP structure, the
"strict
" mode is very flexible,
5879 allowing DNS objects to be stored anywhere under the base cn specified
5880 in the configuration.
</p
>
5882 <p
>The DHCP implementation on the other hand is very inflexible, both
5883 regarding which LDAP schemas to use and which LDAP structure to use.
5884 I guess one could implement ones own schema, as long as the
5885 objectclasses and attributes have the names used, but this do not
5886 really help when the DHCP subtree need to have a fairly fixed
5887 structure.
</p
>
5889 <p
>Based on the observed behaviour, I suspect a LDAP structure like
5890 this might work for Debian Edu:
</p
>
5892 <blockquote
><pre
>
5894 cn=machine-info (dhcpService) - dhcpServiceDN points here
5895 cn=dhcp (dhcpServer)
5896 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5897 cn=
10.0.2.0 (dhcpSubnet)
5898 cn=group1 (dhcpGroup/dhcpOptions)
5899 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5900 cn=
192.168.0.0 (dhcpSubnet)
5901 cn=group1 (dhcpGroup/dhcpOptions)
5902 ou=machines - PowerDNS base points here
5903 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
5904 </pre
></blockquote
>
5906 <P
>This is not tested yet. If the DHCP server require the dhcpHost
5907 entries to be in the dhcpGroup subtrees, the entries can be stored
5908 there instead of a common machines subtree, and the PowerDNS base
5909 would have to be moved one level up to the machine-info subtree.
</p
>
5911 <p
>The combined object under the machines subtree would look something
5912 like this:
</p
>
5914 <blockquote
><pre
>
5915 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
5918 objectClass: dhcpHost
5919 objectclass: domainrelatedobject
5920 objectclass: dnsDomainAux
5921 associateddomain: hostname.intern
5922 arecord:
10.11.12.13
5923 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
5924 dhcpStatements: fixed-address hostname.intern
5925 </pre
></blockquote
>
5927 </p
>One could even add the LTSP configuration associated with a given
5928 machine, as long as the required attributes are available in a
5929 auxiliary object class.
</p
>
5934 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
5935 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
5936 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
5937 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
5938 <description><p
>For a while now, I have wanted to find a way to change the DNS and
5939 DHCP services in Debian Edu to use the same LDAP objects for a given
5940 computer, to avoid the possibility of having a inconsistent state for
5941 a computer in LDAP (as in DHCP but no DNS entry or the other way
5942 around) and make it easier to add computers to LDAP.
</p
>
5944 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
5945 information finally found a solution that seem to work.
</p
>
5947 <p
>The old setup required three LDAP objects for a given computer.
5948 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
5949 we switch powerdns to use its strict LDAP method (ldap-method=strict
5950 in pdns-debian-edu.conf), the forward and reverse DNS entries are
5951 merged into one while making it impossible to transfer the reverse map
5952 to a slave DNS server.
</p
>
5954 <p
>If we also replace the object class used to get the DNS related
5955 attributes to one allowing these attributes to be combined with the
5956 dhcphost object class, we can merge the DNS and DHCP entries into one.
5957 I
've written such object class in the dnsdomainaux.schema file (need
5958 proper OIDs, but that is a minor issue), and tested the setup. It
5959 seem to work.
</p
>
5961 <p
>With this test setup in place, we can get away with one LDAP object
5962 for both DNS and DHCP, and even the LTSP configuration I suggested in
5963 an earlier email. The combined LDAP object will look something like
5966 <blockquote
><pre
>
5967 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5969 objectClass: dhcphost
5970 objectclass: domainrelatedobject
5971 objectclass: dnsdomainaux
5972 associateddomain: hostname.intern
5973 arecord:
10.11.12.13
5974 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
5975 dhcpstatements: fixed-address hostname
5977 </pre
></blockquote
>
5979 <p
>The DNS server uses the associateddomain and arecord entries, while
5980 the DHCP server uses the dhcphwaddress and dhcpstatements entries
5981 before asking DNS to resolve the fixed-adddress. LTSP will use
5982 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
5984 <p
>I am not yet sure if I can get the DHCP server to look for its
5985 dhcphost in a different location, to allow us to put the objects
5986 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
5987 that. If I can
't figure out a way to do that, we can still get rid of
5988 the hosts subtree and move all its content into the DHCP Config tree
5989 (which probably should be renamed to be more related to the new
5990 content. I suspect cn=dnsdhcp,ou=services or something like that
5991 might be a good place to put it.
</p
>
5993 <p
>If you want to help out with implementing this for Debian Edu,
5994 please contact us on debian-edu@lists.debian.org.
</p
>
5999 <title>Idea for storing LTSP configuration in LDAP
</title>
6000 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
6001 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
6002 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
6003 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
6004 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
6005 clients, and that this can be used to fetch configuration from LDAP if
6006 Debian Edu choose to store configuration there.
</p
>
6008 <p
>Armed with this information, I got inspired and wrote a test module
6009 to get configuration from LDAP. The idea is to look up the MAC
6010 address of the client in LDAP, and look for attributes on the form
6011 ltspconfigsetting=value, and use this to export SETTING=value to the
6012 LTSP clients.
</p
>
6014 <p
>The goal is to be able to store the LTSP configuration attributes
6015 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
6016 allowing us to store all information about a computer in one place.
</p
>
6018 <p
>This is a untested draft implementation, and I welcome feedback on
6019 this approach. A real LDAP schema for the ltspClientAux objectclass
6020 need to be written. Comments, suggestions, etc?
</p
>
6022 <blockquote
><pre
>
6023 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
6025 # Fetch LTSP client settings from LDAP based on MAC address
6027 # Uses ethernet address as stored in the dhcpHost objectclass using
6028 # the dhcpHWAddress attribute or ethernet address stored in the
6029 # ieee802Device objectclass with the macAddress attribute.
6031 # This module is written to be schema agnostic, and only depend on the
6032 # existence of attribute names.
6034 # The LTSP configuration variables are saved directly using a
6035 # ltspConfig prefix and uppercasing the rest of the attribute name.
6036 # To set the SERVER variable, set the ltspConfigServer attribute.
6038 # Some LDAP schema should be created with all the relevant
6039 # configuration settings. Something like this should work:
6041 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
6044 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
6046 LDAPSERVER=$(debian-edu-ldapserver)
6047 if [
"$LDAPSERVER
" ] ; then
6048 LDAPBASE=$(debian-edu-ldapserver -b)
6049 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
6050 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
6051 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
6052 grep
'^ltspConfig
' | while read attr value ; do
6053 # Remove prefix and convert to upper case
6054 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
6055 # bass value on to clients
6056 eval
"$attr=$value; export $attr
"
6060 </pre
></blockquote
>
6062 <p
>I
'm not sure this shell construction will work, because I suspect
6063 the while block might end up in a subshell causing the variables set
6064 there to not show up in ltsp-config, but if that is the case I am sure
6065 the code can be restructured to make sure the variables are passed on.
6066 I expect that can be solved with some testing. :)
</p
>
6068 <p
>If you want to help out with implementing this for Debian Edu,
6069 please contact us on debian-edu@lists.debian.org.
</p
>
6071 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
6072 configuration in LDAP that was created around year
2000 by
6073 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
6074 Xperience, Inc.,
2000</a
>. I found its
6075 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
6076 personal home page over at redhat.com.
</p
>
6081 <title>jXplorer, a very nice LDAP GUI
</title>
6082 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
6083 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
6084 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
6085 <description><p
>Since
6086 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
6087 last post
</a
> about available LDAP tools in Debian, I was told about a
6088 LDAP GUI that is even better than luma. The java application
6089 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
6090 moving LDAP objects and subtrees using drag-and-drop, and can
6091 authenticate using Kerberos. I have only tested the Kerberos
6092 authentication, but do not have a LDAP setup allowing me to rewrite
6093 LDAP with my test user yet. It is
6094 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
6095 Debian
</a
> testing and unstable at the moment. The only problem I
6096 have with it is how it handle errors. If something go wrong, its
6097 non-intuitive behaviour require me to go through some query work list
6098 and remove the failing query. Nothing big, but very annoying.
</p
>
6103 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
6104 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
6105 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
6106 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
6107 <description><p
>Here is a short update on my
<a
6108 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
6109 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
6110 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
6111 not reporting the status for KDE, because the upgrade crashes when
6112 aptitude try because of missing conflicts
6113 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
6114 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
6116 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
6117 complete list of the installed packages. Based on this I see these
6118 differences when I did a test run today. As usual, I do not really
6119 know what the correct set of packages would be, but thought it best to
6120 publish the difference.
</p
>
6122 <p
>Installed using apt-get, missing with aptitude
</p
>
6124 <blockquote
><p
>
6125 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
6126 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
6127 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6128 libgtksourceview-common libpt-
1.10.10-plugins-alsa
6129 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6130 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6131 python-
4suite-xml python-eggtrayicon python-gtkhtml2
6132 python-gtkmozembed svgalibg1 xserver-xephyr zip
6133 </p
></blockquote
>
6135 <p
>Installed using apt-get, removed with aptitude
</p
>
6137 <blockquote
><p
>
6138 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6139 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6140 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
6141 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
6142 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
6143 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
6144 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
6145 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
6146 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
6147 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
6148 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
6149 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
6150 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6151 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
6152 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6153 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
6154 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
6155 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6156 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6157 mysql-common swfdec-gnome totem-gstreamer wodim
6158 </p
></blockquote
>
6160 <p
>Installed using aptitude, missing with apt-get
</p
>
6162 <blockquote
><p
>
6163 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6164 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6165 xserver-xorg-input-all xserver-xorg-input-evdev
6166 xserver-xorg-input-kbd xserver-xorg-input-mouse
6167 xserver-xorg-input-synaptics xserver-xorg-video-all
6168 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6169 xserver-xorg-video-chips xserver-xorg-video-cirrus
6170 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6171 xserver-xorg-video-glint xserver-xorg-video-i128
6172 xserver-xorg-video-i740 xserver-xorg-video-mach64
6173 xserver-xorg-video-mga xserver-xorg-video-neomagic
6174 xserver-xorg-video-nouveau xserver-xorg-video-nv
6175 xserver-xorg-video-r128 xserver-xorg-video-radeon
6176 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6177 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6178 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6179 xserver-xorg-video-sis xserver-xorg-video-sisusb
6180 xserver-xorg-video-tdfx xserver-xorg-video-tga
6181 xserver-xorg-video-trident xserver-xorg-video-tseng
6182 xserver-xorg-video-vesa xserver-xorg-video-vmware
6183 xserver-xorg-video-voodoo
6184 </p
></blockquote
>
6186 <p
>Installed using aptitude, removed with apt-get
</p
>
6188 <blockquote
><p
>
6189 deskbar-applet xserver-xorg xserver-xorg-core
6190 xserver-xorg-input-wacom xserver-xorg-video-intel
6191 xserver-xorg-video-openchrome
6192 </p
></blockquote
>
6194 <p
>I was told on IRC that the xorg-xserver package was
6195 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
6196 in git
</a
> today to try to get apt-get to not remove xorg completely.
6197 No idea when it hits Squeeze, but when it does I hope it will reduce
6198 the difference somewhat.
6203 <title>LUMA, a very nice LDAP GUI
</title>
6204 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
6205 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
6206 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
6207 <description><p
>The last few days I have been looking into the status of the LDAP
6208 directory in Debian Edu, and in the process I started to miss a GUI
6209 tool to browse the LDAP tree. The only one I was able to find in
6210 Debian/Squeeze and Lenny is
6211 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
6212 be a great tool to get a overview of the current LDAP directory
6213 populated by default in Skolelinux. Thanks to it, I have been able to
6214 find empty and obsolete subtrees, misplaced objects and duplicate
6215 objects. It will be installed by default in Debian/Squeeze. If you
6216 are working with LDAP, give it a go. :)
</p
>
6218 <p
>I did notice one problem with it I have not had time to report to
6219 the BTS yet. There is no .desktop file in the package, so the tool do
6220 not show up in the Gnome and KDE menus, but only deep down in in the
6221 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6224 <p
>I have not yet been able to get it to modify the tree yet. I would
6225 like to move objects and remove subtrees directly in the GUI, but have
6226 not found a way to do that with LUMA yet. So in the mean time, I use
6227 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
6229 <p
>If you have tips on other GUI tools for LDAP that might be useful
6230 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
6232 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
6233 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
6234 useful GUI alternative. It seem like a good tool, but is unmaintained
6235 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6236 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
6241 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
6242 <link>http://people.skolelinux.org/pere/blog/Idea_for_a_change_to_LDAP_schemas_allowing_DNS_and_DHCP_info_to_be_combined_into_one_object.html
</link>
6243 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Idea_for_a_change_to_LDAP_schemas_allowing_DNS_and_DHCP_info_to_be_combined_into_one_object.html
</guid>
6244 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
6245 <description><p
>A while back, I
6246 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
6247 about the fact
</a
> that it is not possible with the provided schemas
6248 for storing DNS and DHCP information in LDAP to combine the two sets
6249 of information into one LDAP object representing a computer.
</p
>
6251 <p
>In the mean time, I discovered that a simple fix would be to make
6252 the dhcpHost object class auxiliary, to allow it to be combined with
6253 the dNSDomain object class, and thus forming one object for one
6254 computer when storing both DHCP and DNS information in LDAP.
</p
>
6256 <p
>If I understand this correctly, it is not safe to do this change
6257 without also changing the assigned number for the object class, and I
6258 do not know enough about LDAP schema design to do that properly for
6259 Debian Edu.
</p
>
6261 <p
>Anyway, for future reference, this is how I believe we could change
6263 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
6264 schema
</a
> to solve at least part of the problem with the LDAP schemas
6265 available today from IETF.
</p
>
6268 --- dhcp.schema (revision
65192)
6269 +++ dhcp.schema (working copy)
6271 objectclass (
2.16.840.1.113719.1.203.6.6
6272 NAME
'dhcpHost
'
6273 DESC
'This represents information about a particular client
'
6277 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6278 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
6281 <p
>I very much welcome clues on how to do this properly for Debian
6282 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6283 package, and should thus be free to rewrite it as we see fit.
</p
>
6285 <p
>If you want to help out with implementing this for Debian Edu,
6286 please contact us on debian-edu@lists.debian.org.
</p
>
6291 <title>Calling tasksel like the installer, while still getting useful output
</title>
6292 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
6293 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
6294 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
6295 <description><p
>A few times I have had the need to simulate the way tasksel
6296 installs packages during the normal debian-installer run. Until now,
6297 I have ended up letting tasksel do the work, with the annoying problem
6298 of not getting any feedback at all when something fails (like a
6299 conffile question from dpkg or a download that fails), using code like
6302 <blockquote
><pre
>
6303 export DEBIAN_FRONTEND=noninteractive
6304 tasksel --new-install
6305 </pre
></blockquote
>
6307 This would invoke tasksel, let its automatic task selection pick the
6308 tasks to install, and continue to install the requested tasks without
6309 any output what so ever.
6311 Recently I revisited this problem while working on the automatic
6312 package upgrade testing, because tasksel would some times hang without
6313 any useful feedback, and I want to see what is going on when it
6314 happen. Then it occured to me, I can parse the output from tasksel
6315 when asked to run in test mode, and use that aptitude command line
6316 printed by tasksel then to simulate the tasksel run. I ended up using
6319 <blockquote
><pre
>
6320 export DEBIAN_FRONTEND=noninteractive
6321 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
6323 </pre
></blockquote
>
6325 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
6326 --without-recommends -o APT::Install-Recommends=no -y install
6327 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6328 ~pimportant
</tt
>", which will install the gnome desktop task, the
6329 laptop task and all packages with priority standard , required and
6330 important, just like tasksel would have done it during
6331 installation.
</p
>
6333 <p
>A better approach is probably to extend tasksel to be able to
6334 install packages without using debconf-apt-progress, for use cases
6335 like this.
</p
>
6340 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
6341 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
6342 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
6343 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
6344 <description><p
>My
6345 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
6346 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
6347 finally made the upgrade logs available from
6348 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
6349 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6350 apt and aptitude, and found their differences interesting. This time
6351 I will only focus on their removal plans.
</p
>
6353 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
6354 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
6355 surprising part is that it want to remove xorg and all
6356 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6357 sure why. When asking aptitude to do the same, it want to remove
129
6358 packages, but most of them are library packages I suspect are no
6359 longer needed. Both of them want to remove bluetooth packages, which
6360 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
6362 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
6363 which seem like a bad idea and xorg the same way as with Gnome. Asking
6364 aptitude for the same, it wants to remove
192 packages, none which are
6365 too surprising.
</p
>
6367 <p
>I guess the removal of xorg during upgrades should be investigated
6368 and avoided, and perhaps others as well. Here are the complete list
6369 of planned removals. The complete logs is available from the URL
6370 above. Note if you want to repeat these tests, that the upgrade test
6371 for kde+apt-get hung in the tasksel setup because of dpkg asking
6372 conffile questions. No idea why. I worked around it by using
6373 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
6376 <p
><b
>apt-get gnome
72</b
>
6377 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
6378 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6379 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
6380 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6381 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6382 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6383 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6384 xserver-xorg-input-kbd xserver-xorg-input-mouse
6385 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6386 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6387 xserver-xorg-video-ati xserver-xorg-video-chips
6388 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6389 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6390 xserver-xorg-video-glint xserver-xorg-video-i128
6391 xserver-xorg-video-i740 xserver-xorg-video-imstt
6392 xserver-xorg-video-intel xserver-xorg-video-mach64
6393 xserver-xorg-video-mga xserver-xorg-video-neomagic
6394 xserver-xorg-video-nsc xserver-xorg-video-nv
6395 xserver-xorg-video-openchrome xserver-xorg-video-r128
6396 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6397 xserver-xorg-video-rendition xserver-xorg-video-s3
6398 xserver-xorg-video-s3virge xserver-xorg-video-savage
6399 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6400 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6401 xserver-xorg-video-tga xserver-xorg-video-trident
6402 xserver-xorg-video-tseng xserver-xorg-video-v4l
6403 xserver-xorg-video-vesa xserver-xorg-video-vga
6404 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
6405 xulrunner-
1.9-gnome-support
</p
>
6407 <p
><b
>aptitude gnome
129</b
>
6409 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
6410 djvulibre-desktop finger gnome-app-install gnome-mount
6411 gnome-network-admin gnome-spell gnome-vfs-obexftp
6412 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6413 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6414 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6415 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
6416 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
6417 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
6418 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
6419 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
6420 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
6421 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
6422 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
6423 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
6424 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6425 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
6426 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
6427 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
6428 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
6429 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
6430 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6431 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6432 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6433 openoffice.org-writer2latex openssl-blacklist p7zip
6434 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
6435 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6436 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6437 swfdec-mozilla totem-gstreamer update-manager wodim
6438 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6439 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6442 <p
><b
>apt-get kde
82</b
>
6444 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6445 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6446 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6447 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6448 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6449 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6450 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6451 xserver-xorg-input-kbd xserver-xorg-input-mouse
6452 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6453 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6454 xserver-xorg-video-ati xserver-xorg-video-chips
6455 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6456 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6457 xserver-xorg-video-glint xserver-xorg-video-i128
6458 xserver-xorg-video-i740 xserver-xorg-video-imstt
6459 xserver-xorg-video-intel xserver-xorg-video-mach64
6460 xserver-xorg-video-mga xserver-xorg-video-neomagic
6461 xserver-xorg-video-nsc xserver-xorg-video-nv
6462 xserver-xorg-video-openchrome xserver-xorg-video-r128
6463 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6464 xserver-xorg-video-rendition xserver-xorg-video-s3
6465 xserver-xorg-video-s3virge xserver-xorg-video-savage
6466 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6467 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6468 xserver-xorg-video-tga xserver-xorg-video-trident
6469 xserver-xorg-video-tseng xserver-xorg-video-v4l
6470 xserver-xorg-video-vesa xserver-xorg-video-vga
6471 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
6473 <p
><b
>aptitude kde
192</b
>
6474 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
6475 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6476 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6477 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6478 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6479 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6480 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6481 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6482 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6483 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6484 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6485 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6486 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6487 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6488 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6489 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6490 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6491 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6492 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
6493 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6494 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6495 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
6496 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6497 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6498 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6499 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6500 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6501 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
6502 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
6503 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6504 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6505 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6506 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6507 texlive-common texlive-doc-base texlive-fonts-recommended
6508 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6509 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6510 xulrunner-
1.9</p
>
6516 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
6517 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
6518 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
6519 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
6520 <description><p
>The last few days I have done some upgrade testing in Debian, to
6521 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6522 have been discovered and reported in the process
6523 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
6524 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
6525 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
6526 kdebase-workspace-data), and to get a more regular testing going on, I
6527 am working on a script to automate the test.
</p
>
6529 <p
>The idea is to create a Lenny chroot and use tasksel to install a
6530 Gnome or KDE desktop installation inside the chroot before upgrading
6531 it. To ensure no services are started in the chroot, a policy-rc.d
6532 script is inserted. To make sure tasksel believe it is to install a
6533 desktop on a laptop, the tasksel tests are replaced in the chroot
6534 (only acceptable because this is a throw-away chroot).
</p
>
6536 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6537 currently always fail because udev refuses to upgrade with the kernel
6538 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6539 is created. The bug report
6540 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
6541 this problem do not trigger in a chroot, but I touch the file anyway
6542 to make sure the upgrade go well. Testing on virtual and real
6543 hardware have failed me because of udev so far, and creating this file
6544 do the trick in such settings anyway. This is a
6545 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
6546 issue
</a
> and the current udev behaviour is intended by the udev
6547 maintainer because he lack the resources to rewrite udev to keep
6548 working with old kernels or something like that. I really wish the
6549 udev upstream would keep udev backwards compatible, to avoid such
6550 upgrade problem, but given that they fail to do so, I guess
6551 documenting the way out of this mess is the best option we got for
6552 Debian Squeeze.
</p
>
6554 <p
>Anyway, back to the task at hand, testing upgrades. This test
6555 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
6558 <blockquote
><pre
>
6562 if [
"$
1" ] ; then
6571 exec
&lt; /dev/null
6573 mirror=http://ftp.skolelinux.org/debian
6574 tmpdir=chroot-$from-upgrade-$to-$desktop
6576 debootstrap $from $tmpdir $mirror
6577 chroot $tmpdir aptitude update
6578 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
6582 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6586 mount -t proc proc $tmpdir/proc
6587 # Make sure proc is unmounted also on failure
6588 trap exit_cleanup EXIT INT
6590 chroot $tmpdir aptitude -y install debconf-utils
6592 # Make sure tasksel autoselection trigger. It need the test scripts
6593 # to return the correct answers.
6594 echo tasksel tasksel/desktop multiselect $desktop | \
6595 chroot $tmpdir debconf-set-selections
6597 # Include the desktop and laptop task
6598 for test in desktop laptop ; do
6599 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
6603 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6606 DEBIAN_FRONTEND=noninteractive
6607 DEBIAN_PRIORITY=critical
6608 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6609 chroot $tmpdir tasksel --new-install
6611 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
6612 chroot $tmpdir aptitude update
6613 touch $tmpdir/etc/udev/kernel-upgrade
6614 chroot $tmpdir aptitude -y dist-upgrade
6616 </pre
></blockquote
>
6618 <p
>I suspect it would be useful to test upgrades with both apt-get and
6619 with aptitude, but I have not had time to look at how they behave
6620 differently so far. I hope to get a cron job running to do the test
6621 regularly and post the result on the web. The Gnome upgrade currently
6622 work, while the KDE upgrade fail because of the bug in
6623 kdebase-workspace-data
</p
>
6625 <p
>I am not quite sure what kind of extract from the huge upgrade logs
6626 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
6627 post, so I will refrain from trying. I can report that for Gnome,
6628 aptitude report
760 packages upgraded,
448 newly installed,
129 to
6629 remove and
1 not upgraded and
1024MB need to be downloaded while for
6630 KDE the same numbers are
702 packages upgraded,
507 newly installed,
6631 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
6633 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
6634 is able to migrate to dependency based boot sequencing and parallel
6635 booting without a hitch. Was unsure if there were still bugs with
6636 packages failing to clean up their obsolete init.d script during
6637 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6643 <title>Upstart or sysvinit - as init.d scripts see it
</title>
6644 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
6645 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
6646 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
6647 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
6648 scripts to migrate (some of) their operations to upstart job while
6649 keeping the init.d for hurd and kfreebsd. The packages with such
6650 needs will need a way to get their init.d scripts to behave
6651 differently when used with sysvinit and with upstart. Because of
6652 this, I had a look at the environment variables set when a init.d
6653 script is running under upstart, and when it is not.
</p
>
6655 <p
>With upstart, I notice these environment variables are set when a
6656 script is started from rcS.d/ (ignoring some irrelevant ones like
6659 <blockquote
><pre
>
6665 UPSTART_EVENTS=startup
6667 UPSTART_JOB=rc-sysinit
6668 </pre
></blockquote
>
6670 <p
>With sysvinit, these environment variables are set for the same
6673 <blockquote
><pre
>
6674 INIT_VERSION=sysvinit-
2.88
6679 </pre
></blockquote
>
6681 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
6682 sysvinit are not set by upstart. Not sure if it is intentional or not
6683 to not be compatible with sysvinit in this regard.
</p
>
6685 <p
>For scripts needing to behave differently when upstart is used,
6686 looking for the UPSTART_JOB environment variable seem to be a good
6692 <title>A manual for standards wars...
</title>
6693 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
6694 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
6695 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
6696 <description><p
>Via the
6697 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
6698 of Rob Weir
</a
> I came across the very interesting essay named
6699 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
6700 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
6701 following the standards wars of today.
</p
>
6706 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
6707 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
6708 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
6709 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
6710 <description><p
>When using sitesummary at a site to track machines, it is possible
6711 to get a list of the machine types in use thanks to the DMI
6712 information extracted from each machine. The script to do so is
6713 included in the sitesummary package, and here is example output from
6714 the Skolelinux build servers:
</p
>
6716 <blockquote
><pre
>
6717 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6719 Dell Computer Corporation
1
6722 eserver xSeries
345 -[
8670M1X]-
1
6726 </pre
></blockquote
>
6728 <p
>The quality of the report depend on the quality of the DMI tables
6729 provided in each machine. Here there are Intel machines without model
6730 information listed with Intel as vendor and no model, and virtual Xen
6731 machines listed as [no-dmi-info]. One can add -l as a command line
6732 option to list the individual machines.
</p
>
6734 <p
>A larger list is
6735 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
6736 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
6737 provide the basic sitesummary report publicly. In their report there
6738 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
6739 their machines, and as sitesummary is available in both distributions,
6740 it is trivial to get all of them to report to the same central
6741 collector.
</p
>
6746 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
6747 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
6748 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</guid>
6749 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
6750 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
6751 start at boot when an NVidia video card is used is handled. The
6752 problem seem to be that the nvidia X.org driver uses a long time to
6753 initialize, and this duration is longer than kdm is configured to
6756 <p
>I came across two bugs related to this issue,
6757 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
6758 against initscripts and passed on to nvidia-glx when it became obvious
6759 that the nvidia drivers were involved, and
6760 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
6761 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
6763 <p
>To me, it seem that no-one is interested in actually solving the
6764 problem nvidia video card owners experience and make sure the Debian
6765 distribution work out of the box for these users. The nvidia driver
6766 maintainers expect kdm to be set up to wait longer, while kdm expect
6767 the nvidia driver maintainers to fix the driver to start faster, and
6768 while they wait for each other I guess the users end up switching to a
6769 distribution that work for them. I have no idea what the solution is,
6770 but I am pretty sure that waiting for each other is not it.
</p
>
6772 <p
>I wonder why we end up handling bugs this way.
</p
>
6777 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
6778 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
6779 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
6780 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
6781 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
6782 The feature seem to hold up pretty well, but three fairly serious
6783 issues are known and should be solved:
6787 <li
>The wicd package seen to
6788 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
6789 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
6790 parallel booting is enabled. No idea why, but the wicd maintainer
6791 seem to be on the case.
</li
>
6793 <li
>The nvidia X driver seem to
6794 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
6795 triggered more easily when parallel booting is in effect. The
6796 maintainer is on the case.
</li
>
6798 <li
>The sysv-rc package fail to properly enable dependency based boot
6799 sequencing (the shutdown is broken) when old file-rc users
6800 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
6801 sysv-rc. One way to solve it would be for file-rc to create
6802 /etc/init.d/.legacy-bootordering, and another is to try to make
6803 sysv-rc more robust. Will investigate some more and probably upload a
6804 workaround in sysv-rc to help those trying to move from file-rc to
6805 sysv-rc get a working shutdown.
</li
>
6807 </ul
></p
>
6809 <p
>All in all not many surprising issues, and all of them seem
6810 solvable before Squeeze is released. In addition to these there are
6811 some packages with bugs in their dependencies and run level settings,
6812 which I expect will be fixed in a reasonable time span.
</p
>
6814 <p
>If you report any problems with dependencies in init.d scripts to
6815 the BTS, please usertag the report to get it to show up at
6816 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6817 list of usertagged bugs related to this
</a
>.
</p
>
6819 <p
>Update: Correct bug number to file-rc issue.
</p
>
6824 <title>More flexible firmware handling in debian-installer
</title>
6825 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
6826 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
6827 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
6828 <description><p
>After a long break from debian-installer development, I finally
6829 found time today to return to the project. Having to spend less time
6830 working dependency based boot in debian, as it is almost complete now,
6831 definitely helped freeing some time.
</p
>
6833 <p
>A while back, I ran into a problem while working on Debian Edu. We
6834 include some firmware packages on the Debian Edu CDs, those needed to
6835 get disk and network controllers working. Without having these
6836 firmware packages available during installation, it is impossible to
6837 install Debian Edu on the given machine, and because our target group
6838 are non-technical people, asking them to provide firmware packages on
6839 an external medium is a support pain. Initially, I expected it to be
6840 enough to include the firmware packages on the CD to get
6841 debian-installer to find and use them. This proved to be wrong.
6842 Next, I hoped it was enough to symlink the relevant firmware packages
6843 to some useful location on the CD (tried /cdrom/ and
6844 /cdrom/firmware/). This also proved to not work, and at this point I
6845 found time to look at the debian-installer code to figure out what was
6846 going to work.
</p
>
6848 <p
>The firmware loading code is in the hw-detect package, and a closer
6849 look revealed that it would only look for firmware packages outside
6850 the installation media, so the CD was never checked for firmware
6851 packages. It would only check USB sticks, floppies and other
6852 "external
" media devices. Today I changed it to also look in the
6853 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6854 solve the problem I ran into with Debian edu. I also changed it to
6855 look in /firmware/, to make sure the installer also find firmware
6856 provided in the initrd when booting the installer via PXE, to allow us
6857 to provide the same feature in the PXE setup included in Debian
6860 <p
>To make sure firmware deb packages with a license questions are not
6861 activated without asking if the license is accepted, I extended
6862 hw-detect to look for preinst scripts in the firmware packages, and
6863 run these before activating the firmware during installation. The
6864 license question is asked using debconf in the preinst, so this should
6865 solve the issue for the firmware packages I have looked at so far.
</p
>
6867 <p
>If you want to discuss the details of these features, please
6868 contact us on debian-boot@lists.debian.org.
</p
>
6873 <title>Parallellized boot is now the default in Debian/unstable
</title>
6874 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
6875 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
6876 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
6877 <description><p
>Since this evening, parallel booting is the default in
6878 Debian/unstable for machines using dependency based boot sequencing.
6879 Apparently the testing of concurrent booting has been wider than
6880 expected, if I am to believe the
6881 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
6882 on debian-devel@
</a
>, and I concluded a few days ago to move forward
6883 with the feature this weekend, to give us some time to detect any
6884 remaining problems before Squeeze is frozen. If serious problems are
6885 detected, it is simple to change the default back to sequential boot.
6886 The upload of the new sysvinit package also activate a new upstream
6889 More information about
6890 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
6891 based boot sequencing
</a
> is available from the Debian wiki. It is
6892 currently possible to disable parallel booting when one run into
6893 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
6895 <blockquote
><pre
>
6897 </pre
></blockquote
>
6899 <p
>If you report any problems with dependencies in init.d scripts to
6900 the BTS, please usertag the report to get it to show up at
6901 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
6902 list of usertagged bugs related to this
</a
>.
</p
>
6907 <title>Sitesummary tip: Listing MAC address of all clients
</title>
6908 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
6909 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
6910 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
6911 <description><p
>In the recent Debian Edu versions, the
6912 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
6913 system
</a
> is used to keep track of the machines in the school
6914 network. Each machine will automatically report its status to the
6915 central server after boot and once per night. The network setup is
6916 also reported, and using this information it is possible to get the
6917 MAC address of all network interfaces in the machines. This is useful
6918 to update the DHCP configuration.
</p
>
6920 <p
>To give some idea how to use sitesummary, here is a one-liner to
6921 ist all MAC addresses of all machines reporting to sitesummary. Run
6922 this on the collector host:
</p
>
6924 <blockquote
><pre
>
6925 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
6926 </pre
></blockquote
>
6928 <p
>This will list all MAC addresses assosiated with all machine, one
6929 line per machine and with space between the MAC addresses.
</p
>
6931 <p
>To allow system administrators easier job at adding static DHCP
6932 addresses for hosts, it would be possible to extend this to fetch
6933 machine information from sitesummary and update the DHCP and DNS
6934 tables in LDAP using this information. Such tool is unfortunately not
6935 written yet.
</p
>
6940 <title>systemd, an interesting alternative to upstart
</title>
6941 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
6942 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
6943 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
6944 <description><p
>The last few days a new boot system called
6945 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
6947 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
6949 to the free software world. I have not yet had time to play around
6950 with it, but it seem to be a very interesting alternative to
6951 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
6952 a good alternative for Debian when we are able to switch to an event
6953 based boot system. Tollef is
6954 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
6955 systemd into Debian, and I look forward to seeing how well it work. I
6956 like the fact that systemd handles init.d scripts with dependency
6957 information natively, allowing them to run in parallel where upstart
6958 at the moment do not.
</p
>
6960 <p
>Unfortunately do systemd have the same problem as upstart regarding
6961 platform support. It only work on recent Linux kernels, and also need
6962 some new kernel features enabled to function properly. This means
6963 kFreeBSD and Hurd ports of Debian will need a port or a different boot
6964 system. Not sure how that will be handled if systemd proves to be the
6965 way forward.
</p
>
6967 <p
>In the mean time, based on the
6968 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
6969 on debian-devel@
</a
> regarding parallel booting in Debian, I have
6970 decided to enable full parallel booting as the default in Debian as
6971 soon as possible (probably this weekend or early next week), to see if
6972 there are any remaining serious bugs in the init.d dependencies. A
6973 new version of the sysvinit package implementing this change is
6974 already in experimental. If all go well, Squeeze will be released
6975 with parallel booting enabled by default.
</p
>
6980 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
6981 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
6982 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
6983 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
6984 <description><p
>These days, the init.d script dependencies in Squeeze are quite
6985 complete, so complete that it is actually possible to run all the
6986 init.d scripts in parallell based on these dependencies. If you want
6987 to test your Squeeze system, make sure
6988 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
6989 based boot sequencing
</a
> is enabled, and add this line to
6990 /etc/default/rcS:
</p
>
6992 <blockquote
><pre
>
6993 CONCURRENCY=makefile
6994 </pre
></blockquote
>
6996 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
6997 scripts in parallel using the dependency information stored in
6998 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
6999 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
7000 to try to start the kdm and gdm scripts as early as possible, and will
7001 start the facilities required by kdm or gdm as early as possible to
7002 make this happen.
</p
>
7004 <p
>Give it a try, and see if you like the result. If some services
7005 fail to start properly, it is most likely because they have incomplete
7006 init.d script dependencies in their startup script (or some of their
7007 dependent scripts have incomplete dependencies). Report bugs and get
7008 the package maintainers to fix it. :)
</p
>
7010 <p
>Running scripts in parallel could be the default in Debian when we
7011 manage to get the init.d script dependencies complete and correct. I
7012 expect we will get there in Squeeze+
1, if we get manage to test and
7013 fix the remaining issues.
</p
>
7015 <p
>If you report any problems with dependencies in init.d scripts to
7016 the BTS, please usertag the report to get it to show up at
7017 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
7018 list of usertagged bugs related to this
</a
>.
</p
>
7023 <title>Debian has switched to dependency based boot sequencing
</title>
7024 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
7025 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
7026 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
7027 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
7028 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
7029 have been migrated to using dependency based boot sequencing. This
7030 conclude work me and others have been doing for the last three days.
7031 It feels great to see this finally part of the default Debian
7032 installation. Now we just need to weed out the last few problems that
7033 are bound to show up, to get everything ready for Squeeze.
</p
>
7035 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
7036 fixing the more fundamental problem of handing the event based
7037 non-predictable kernel in the early boot.
</p
>
7042 <title>Taking over sysvinit development
</title>
7043 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
7044 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
7045 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
7046 <description><p
>After several years of frustration with the lack of activity from
7047 the existing sysvinit upstream developer, I decided a few weeks ago to
7048 take over the package and become the new upstream. The number of
7049 patches to track for the Debian package was becoming a burden, and the
7050 lack of synchronization between the distribution made it hard to keep
7051 the package up to date.
</p
>
7053 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
7054 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
7055 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
7056 and Fedora), based on the patches currently in use in these
7057 distributions. We Debian maintainers plan to move to this tarball as
7058 the new upstream as soon as we find time to do the merge. Since the
7059 new tarball was created, we agreed with Werner at SuSe to make a new
7060 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
7061 development there. The project is registered and currently waiting
7062 for approval by the Savannah administrators, and as soon as it is
7063 approved, we will import the old versions from svn and continue
7064 working on the future release.
</p
>
7066 <p
>It is a bit ironic that this is done now, when some of the involved
7067 distributions are moving to upstart as a syvinit replacement.
</p
>
7072 <title>Debian boots quicker and quicker
</title>
7073 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
7074 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
7075 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
7076 <description><p
>I spent Monday and tuesday this week in London with a lot of the
7077 people involved in the boot system on Debian and Ubuntu, to see if we
7078 could find more ways to speed up the boot system. This was an Ubuntu
7080 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
7081 gathering
</a
>. It was quite productive. We also discussed the future
7082 of boot systems, and ways to handle the increasing number of boot
7083 issues introduced by the Linux kernel becoming more and more
7084 asynchronous and event base. The Ubuntu approach using udev and
7085 upstart might be a good way forward. Time will show.
</p
>
7087 <p
>Anyway, there are a few ways at the moment to speed up the boot
7088 process in Debian. All of these should be applied to get a quick
7093 <li
>Use dash as /bin/sh.
</li
>
7095 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
7096 clock is in UTC.
</li
>
7098 <li
>Install and activate the insserv package to enable
7099 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
7100 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
7104 These points are based on the Google summer of code work done by
7105 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
7108 <p
>Support for makefile-style concurrency during boot was uploaded to
7109 unstable yesterday. When we tested it, we were able to cut
6 seconds
7110 from the boot sequence. It depend on very correct dependency
7111 declaration in all init.d scripts, so I expect us to find edge cases
7112 where the dependences in some scripts are slightly wrong when we start
7113 using this.
</p
>
7115 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7116 introduced by Raphael Geissert today, one that could affect the
7117 startup speed as well. Instead of starting some scripts concurrently
7118 from rcS.d/ and another set of scripts from rc2.d/, it would be
7119 possible to run a of them in the same process. A quick way to test
7120 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
7121 insserv
'. Will need to test if that work. :)
</p
>
7126 <title>BSAs påstander om piratkopiering møter motstand
</title>
7127 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
7128 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
7129 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
7130 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
7131 programvareselskapene som Microsoft og Apple, publisert en rapport der
7132 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7133 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7135 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
7136 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
7137 dagene. Et spesielt interessant kommentar fra Sverige,
7138 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
7139 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
7142 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
7143 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7144 företag.
"Man bör nog kanske inte se de här siffrorna som helt
7145 exakta
", säger BSAs Sverigechef John Hugosson.
7148 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
7149 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
7150 piracy figures need a shot of reality
</a
> og
<a
7151 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
7152 Copyright Treaty Work?
</a
></p
>
7154 <p
>Fant lenkene via
<a
7155 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
7156 på Slashdot
</a
>.
</p
>
7161 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
7162 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
7163 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
7164 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
7165 <description><p
>Kom over
7166 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
7167 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7168 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7169 jobber til daglig. En rask opptelling forteller meg at vi har
490
7170 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
7171 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
7172 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
7177 <title>Kryptert harddisk - naturligvis
</title>
7178 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
7179 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
7180 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
7181 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
7182 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
7183 når en tar tap av arbeidstid, fortrolige dokumenter,
7184 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7185 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7186 til at jeg har kryptert harddisken på både kontormaskinen og min
7187 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7188 komme på avveie, den første informasjon relatert til jobben min ved
7189 Universitetet i Oslo, og den andre relatert til blant annet
7190 foreningsarbeide. Kryptering av diskene gjør at det er lite
7191 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7192 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7193 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7194 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7195 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7196 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7197 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7198 det er gjort slik jeg gjør det er minimale, og gevinstene er
7199 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7200 maskinen reinstalleres og alt er tapt.
</p
>
7202 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7203 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7204 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7205 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7206 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7207 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7208 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7209 betydelige.
</p
>
7214 <title>Two projects that have improved the quality of free software a lot
</title>
7215 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
7216 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
7217 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
7218 <description><p
>There are two software projects that have had huge influence on the
7219 quality of free software, and I wanted to mention both in case someone
7220 do not yet know them.
</p
>
7222 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
7223 tool to detect and expose errors in the memory handling of programs.
7224 It is easy to use, all one need to do is to run
'valgrind program
',
7225 and it will report any problems on stdout. It is even better if the
7226 program include debug information. With debug information, it is able
7227 to report the source file name and line number where the problem
7228 occurs. It can report things like
'reading past memory block in file
7229 X line N, the memory block was allocated in file Y, line M
', and
7230 'using uninitialised value in control logic
'. This tool has made it
7231 trivial to investigate reproducible crash bugs in programs, and have
7232 reduced the number of this kind of bugs in free software a lot.
7234 <p
>The second one is
7235 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
7236 a source code checker. It is able to process the source of a program
7237 and find problems in the logic without running the program. It
7238 started out as the Stanford Checker and became well known when it was
7239 used to find bugs in the Linux kernel. It is now a commercial tool
7240 and the company behind it is running
7241 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
7242 free software community, where a lot of free software projects get
7243 their source checked for free. Several thousand defects have been
7244 found and fixed so far. It can find errors like
'lock L taken in file
7245 X line N is never released if exiting in line M
', or
'the code in file
7246 Y lines O to P can never be executed
'. The projects included in the
7247 community service project have managed to get rid of a lot of
7248 reliability problems thanks to Coverity.
</p
>
7250 <p
>I believe tools like this, that are able to automatically find
7251 errors in the source, are vital to improve the quality of software and
7252 make sure we can get rid of the crashing and failing software we are
7253 surrounded by today.
</p
>
7258 <title>No patch is not better than a useless patch
</title>
7259 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
7260 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
7261 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
7262 <description><p
>Julien Blache
7263 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
7264 patch is better than a useless patch
</a
>. I completely disagree, as a
7265 patch allow one to discuss a concrete and proposed solution, and also
7266 prove that the issue at hand is important enough for someone to spent
7267 time on fixing it. No patch do not provide any of these positive
7268 properties.
</p
>
7273 <title>Standardize on protocols and formats, not vendors and applications
</title>
7274 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
7275 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
7276 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
7277 <description><p
>Where I work at the University of Oslo, one decision stand out as a
7278 very good one to form a long lived computer infrastructure. It is the
7279 simple one, lost by many in todays computer industry: Standardize on
7280 open network protocols and open exchange/storage formats, not applications.
7281 Applications come and go, while protocols and files tend to stay, and
7282 thus one want to make it easy to change application and vendor, while
7283 avoiding conversion costs and locking users to a specific platform or
7284 application.
</p
>
7286 <p
>This approach make it possible to replace the client applications
7287 independently of the server applications. One can even allow users to
7288 use several different applications as long as they handle the selected
7289 protocol and format. In the normal case, only one client application
7290 is recommended and users only get help if they choose to use this
7291 application, but those that want to deviate from the easy path are not
7292 blocked from doing so.
</p
>
7294 <p
>It also allow us to replace the server side without forcing the
7295 users to replace their applications, and thus allow us to select the
7296 best server implementation at any moment, when scale and resouce
7297 requirements change.
</p
>
7299 <p
>I strongly recommend standardizing - on open network protocols and
7300 open formats, but I would never recommend standardizing on a single
7301 application that do not use open network protocol or open formats.
</p
>
7306 <title>Returning from Skolelinux developer gathering
</title>
7307 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
7308 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
7309 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
7310 <description><p
>I
'm sitting on the train going home from this weekends Debian
7311 Edu/Skolelinux development gathering. I got a bit done tuning the
7312 desktop, and looked into the dynamic service location protocol
7313 implementation avahi. It look like it could be useful for us. Almost
7314 30 people participated, and I believe it was a great environment to
7315 get to know the Skolelinux system. Walter Bender, involved in the
7316 development of the Sugar educational platform, presented his stuff and
7317 also helped me improve my OLPC installation. He also showed me that
7318 his Turtle Art application can be used in standalone mode, and we
7319 agreed that I would help getting it packaged for Debian. As a
7320 standalone application it would be great for Debian Edu. We also
7321 tried to get the video conferencing working with two OLPCs, but that
7322 proved to be too hard for us. The application seem to need more work
7323 before it is ready for me. I look forward to getting home and relax
7329 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
7330 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
7331 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
7332 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
7333 <description><p
>The state of standardized LDAP schemas on Linux is far from
7334 optimal. There is RFC
2307 documenting one way to store NIS maps in
7335 LDAP, and a modified version of this normally called RFC
2307bis, with
7336 some modifications to be compatible with Active Directory. The RFC
7337 specification handle the content of a lot of system databases, but do
7338 not handle DNS zones and DHCP configuration.
</p
>
7340 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
7341 we would like to store information about users, SMB clients/hosts,
7342 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7343 and LTSP configuration in LDAP. These objects have a lot in common,
7344 but with the current LDAP schemas it is not possible to have one
7345 object per entity. For example, one need to have at least three LDAP
7346 objects for a given computer, one with the SMB related stuff, one with
7347 DNS information and another with DHCP information. The schemas
7348 provided for DNS and DHCP are impossible to combine into one LDAP
7349 object. In addition, it is impossible to implement quick queries for
7350 netgroup membership, because of the way NIS triples are implemented.
7351 It just do not scale. I believe it is time for a few RFC
7352 specifications to cleam up this mess.
</p
>
7354 <p
>I would like to have one LDAP object representing each computer in
7355 the network, and this object can then keep the SMB (ie host key), DHCP
7356 (mac address/name) and DNS (name/IP address) settings in one place.
7357 It need to be efficently stored to make sure it scale well.
</p
>
7359 <p
>I would also like to have a quick way to map from a user or
7360 computer and to the net group this user or computer is a member.
</p
>
7362 <p
>Active Directory have done a better job than unix heads like myself
7363 in this regard, and the unix side need to catch up. Time to start a
7364 new IETF work group?
</p
>
7369 <title>Endelig er Debian Lenny gitt ut
</title>
7370 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
7371 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
7372 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
7373 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
7374 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
7375 Et langt steg videre for Debian-prosjektet, og en rekke nye
7376 programpakker blir nå tilgjengelig for de av oss som bruker den
7377 stabile utgaven av Debian. Neste steg er nå å få
7378 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
7379 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
7380 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7381 slippes løs på skolene. Takk til alle debian-utviklerne som har
7382 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7383 bootsekvens tilgjengelig i stabil utgave, vha pakken
7384 <tt
>insserv
</tt
>.
</p
>
7389 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
7390 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
7391 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
7392 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
7393 <description><p
>This weekend we had a small developer gathering for Debian Edu in
7394 Oslo. Most of Saturday was used for the general assemly for the
7395 member organization, but the rest of the weekend I used to tune the
7396 LTSP installation. LTSP now work out of the box on the
10-network.
7397 Acer Aspire One proved to be a very nice thin client, with both
7398 screen, mouse and keybard in a small box. Was working on getting the
7399 diskless workstation setup configured out of the box, but did not
7400 finish it before the weekend was up.
</p
>
7402 <p
>Did not find time to look at the
4 VGA cards in one box we got from
7403 the Brazilian group, so that will have to wait for the next
7404 development gathering. Would love to have the Debian Edu installer
7405 automatically detect and configure a multiseat setup when it find one
7406 of these cards.
</p
>
7411 <title>The sorry state of multimedia browser plugins in Debian
</title>
7412 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
7413 <guid isPermaLink=
"true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
7414 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
7415 <description><p
>Recently I have spent some time evaluating the multimedia browser
7416 plugins available in Debian Lenny, to see which one we should use by
7417 default in Debian Edu. We need an embedded video playing plugin with
7418 control buttons to pause or stop the video, and capable of streaming
7419 all the multimedia content available on the web. The test results and
7420 notes are available on
7421 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
7422 Debian wiki
</a
>. I was surprised how few of the plugins are able to
7423 fill this need. My personal video player favorite, VLC, has a really
7424 bad plugin which fail on a lot of the test pages. A lot of the MIME
7425 types I would expect to work with any free software player (like
7426 video/ogg), just do not work. And simple formats like the
7427 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
7428 totem and vlc plugins. I hope the situation will improve soon. No
7429 wonder sites use the proprietary Adobe flash to play video.
</p
>
7431 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
7432 be the only one fitting our needs. :/
</p
>