]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
77de2358e42810bd4b27f91611e6a366d4e5174b
[homepage.git] / blog / tags / debian / debian.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries tagged debian</title>
5 <description>Entries tagged debian</description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
11 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
13 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
14 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
15 bread shelf on the ICA shop at Storo, the grub menu of Ubuntu with
16 Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck on a
17 screen normally showing the bread types and prizes:&lt;/p&gt;
18
19 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2014-10-04-ubuntu-ica-storo-crop.jpeg&quot;&gt;&lt;/p&gt;
20
21 &lt;p&gt;If it had booted as it was supposed to, I would never had known
22 about this hidden Linux installation. It is interesting what
23 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
24 </description>
25 </item>
26
27 <item>
28 <title>New lsdvd release version 0.17 is ready</title>
29 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
30 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
31 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
32 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
33 got a new set of developers a few weeks ago, after the original
34 developer decided to step down and pass the project to fresh blood.
35 This project is now maintained by Petter Reinholdtsen and Steve
36 Dibb.&lt;/p&gt;
37
38 &lt;p&gt;I just wrapped up
39 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
40 new lsdvd release&lt;/a&gt;, available in git or from
41 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
42 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
43 0.17.&lt;/p&gt;
44
45 &lt;ul&gt;
46
47 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
48 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
49 non-existant, to work around additional copy protection&lt;/li&gt;
50 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
51 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
52 &lt;li&gt;Fix include orders&lt;/li&gt;
53 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
54 &lt;li&gt;Fix the chapter count&lt;/li&gt;
55 &lt;li&gt;Make sure the array size and the array limit used when initialising
56 the palette size is the same.&lt;/li&gt;
57 &lt;li&gt;Fix array printing.&lt;/li&gt;
58 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
59 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
60 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
61 with more GCC compiler warnings.&lt;/li&gt;
62
63 &lt;/ul&gt;
64
65 &lt;p&gt;This change bring together patches for lsdvd in use in various
66 Linux and Unix distributions, as well as patches submitted to the
67 project the last nine years. Please check it out. :)&lt;/p&gt;
68 </description>
69 </item>
70
71 <item>
72 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
73 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
74 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
75 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
76 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
77 project&lt;/a&gt; provide a Linux solution for schools, including a
78 powerful desktop with education software, a central server providing
79 web pages, user database, user home directories, central login and PXE
80 boot of both clients without disk and the installation to install Debian
81 Edu on machines with disk (and a few other services perhaps to small
82 to mention here). We in the Debian Edu team are currently working on
83 the Jessie based version, trying to get everything in shape before the
84 freeze, to avoid having to maintain our own package repository in the
85 future. The
86 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
87 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
88 work left. Some fatal problems block testing, breaking the installer,
89 but it is possible to work around these to get anyway. Here is a
90 recipe on how to get the installation limping along.&lt;/p&gt;
91
92 &lt;p&gt;First, download the test ISO via
93 &lt;a href=&quot;ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;ftp&lt;/a&gt;,
94 &lt;a href=&quot;http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;http&lt;/a&gt;
95 or rsync (use
96 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
97 The ISO build was broken on Tuesday, so we do not get a new ISO every
98 12 hours or so, but thankfully the ISO we already got we are able to
99 install with some tweaking.&lt;/p&gt;
100
101 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
102 (use Alt-Ctrl-F2), run&lt;/p&gt;
103
104 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
105 nano /usr/bin/edu-eatmydata-install
106 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
107
108 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
109 optimization. Return to the installation, select the profile you want
110 and continue. Without this change, exim4-config will fail to install
111 due to a known bug in eatmydata.&lt;/p&gt;
112
113 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
114 this do not work, figure out what your correct value would be. All my
115 test machines need /dev/sda, so I have no advice if it do not fit
116 your need.&lt;/p&gt;
117
118 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
119 root after the initial boot from hard drive, and install the
120 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
121 or mate. If you want several desktop options, install more than one
122 metapackage. Once this is done, reboot and you should have a working
123 graphical login screen. This workaround should no longer be needed
124 once the education-tasks package version 1.801 enter testing in two
125 days.&lt;/p&gt;
126
127 &lt;p&gt;I believe the ISO build will start working on two days when the new
128 tasksel package enter testing and Steve McIntyre get a chance to
129 update the debian-cd git repository. The eatmydata, grub and desktop
130 issues are already fixed in unstable and testing, and should show up
131 on the ISO as soon as the ISO build start working again. Well the
132 eatmydata optimization is really just disabled. The proper fix
133 require an upload by the eatmydata maintainer applying the patch
134 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
135 The rest have proper fixes in unstable.&lt;/p&gt;
136
137 &lt;p&gt;I hope this get you going with the installation testing, as we are
138 quickly running out of time trying to get our Jessie based
139 installation ready before the distribution freeze in a month.&lt;/p&gt;
140 </description>
141 </item>
142
143 <item>
144 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
145 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
146 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
147 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
148 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
149 to handle my fairly large DVD collection. It is a nice command line
150 tool to get details about a DVD, like title, tracks, track length,
151 etc, in XML, Perl or human readable format. But lsdvd have not seen
152 any new development since 2006 and had a few irritating bugs affecting
153 its use with some DVDs. Upstream seemed to be dead, and in January I
154 sent a small probe asking for a version control repository for the
155 project, without any reply. But I use it regularly and would like to
156 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
157 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
158 the project admin, and after getting a reply from him explaining that
159 he was no longer interested in the project, I asked if I could take
160 over. And yesterday, I became project admin.&lt;/p&gt;
161
162 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
163 maintainer interested in joining forces to maintain the upstream
164 project, and I hope we can get a new release out fairly quickly,
165 collecting the patches spread around on the internet into on place.
166 I&#39;ve added the relevant Debian patches to the freshly created git
167 repository, and expect the Gentoo patches to make it too. If you got
168 a DVD collection and care about command line tools, check out
169 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
170 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
171 list&lt;/a&gt;. :)&lt;/p&gt;
172 </description>
173 </item>
174
175 <item>
176 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
177 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
178 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
179 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
180 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
181 a lot quicker. When we install more than 2000 packages in
182 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
183 tasksel in the installer, unpacking the binary packages take forever.
184 A part of the slow I/O issue was discussed in
185 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
186 much file system sync-ing done by dpkg, which is the package
187 responsible for unpacking the binary packages. Other parts (like code
188 executed by postinst scripts) might also sync to disk during
189 installation. All this sync-ing to disk do not really make sense to
190 me. If the machine crash half-way through, I start over, I do not try
191 to salvage the half installed system. So the failure sync-ing is
192 supposed to protect against, hardware or system crash, is not really
193 relevant while the installer is running.&lt;/p&gt;
194
195 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
196 system sync()-ing in a fairly non-intrusive way, without the need to
197 change the code in several packages. The idea is not new, but I have
198 not heard anyone propose the approach using dpkg-divert before. It
199 depend on the small and clever package
200 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
201 uses LD_PRELOAD to replace the system functions for syncing data to
202 disk with functions doing nothing, thus allowing programs to live
203 dangerous while speeding up disk I/O significantly. Instead of
204 modifying the implementation of dpkg, apt and tasksel (which are the
205 packages responsible for selecting, fetching and installing packages),
206 it occurred to me that we could just divert the programs away, replace
207 them with a simple shell wrapper calling
208 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
209 Two days ago I decided to test the idea, and wrapped up a simple
210 implementation for the Debian Edu udeb.&lt;/p&gt;
211
212 &lt;p&gt;The effect was stunning. In my first test it reduced the running
213 time of the pkgsel step (installing tasks) from 64 to less than 44
214 minutes (20 minutes shaved off the installation) on an old Dell
215 Latitude D505 machine. I am not quite sure what the optimised time
216 would have been, as I messed up the testing a bit, causing the debconf
217 priority to get low enough for two questions to pop up during
218 installation. As soon as I saw the questions I moved the installation
219 along, but do not know how long the question were holding up the
220 installation. I did some more measurements using Debian Edu Jessie,
221 and got these results. The time measured is the time stamp in
222 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
223 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
224 yourself. In Debian Edu, the tasksel dialog do not show up, and the
225 timing thus do not depend on how quickly the user handle the tasksel
226 dialog.&lt;/p&gt;
227
228 &lt;p&gt;&lt;table&gt;
229
230 &lt;tr&gt;
231 &lt;th&gt;Machine/setup&lt;/th&gt;
232 &lt;th&gt;Original tasksel&lt;/th&gt;
233 &lt;th&gt;Optimised tasksel&lt;/th&gt;
234 &lt;th&gt;Reduction&lt;/th&gt;
235 &lt;/tr&gt;
236
237 &lt;tr&gt;
238 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
239 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
240 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
241 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
242 &lt;/tr&gt;
243
244 &lt;tr&gt;
245 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
246 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
247 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
248 &lt;td&gt;23 min 40%&lt;/td&gt;
249 &lt;/tr&gt;
250
251 &lt;tr&gt;
252 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
253 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
254 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
255 &lt;td&gt;11 min 50%&lt;/td&gt;
256 &lt;/tr&gt;
257
258 &lt;tr&gt;
259 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
260 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
261 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
262 &lt;td&gt;2 min 33%&lt;/td&gt;
263 &lt;/tr&gt;
264
265 &lt;tr&gt;
266 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
267 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
268 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
269 &lt;td&gt;4 min 21%&lt;/td&gt;
270 &lt;/tr&gt;
271
272 &lt;/table&gt;&lt;/p&gt;
273
274 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
275 time is spent downloading packages. The connection to the Internet
276 was 100Mbit/s during testing, so downloading should not be a
277 significant factor in the measurement. Download typically took a few
278 seconds to a few minutes, depending on the amount of packages being
279 installed.&lt;/p&gt;
280
281 &lt;p&gt;The speedup is implemented by using two hooks in
282 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
283 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
284 finish-install.d hook to remove the divert at the end of the
285 installation. I picked the pre-pkgsel.d hook instead of the
286 post-base-installer.d hook because I test using an ISO without the
287 eatmydata package included, and the post-base-installer.d hook in
288 Debian Edu can only operate on packages included in the ISO. The
289 negative effect of this is that I am unable to activate this
290 optimization for the kernel installation step in d-i. If the code is
291 moved to the post-base-installer.d hook, the speedup would be larger
292 for the entire installation.&lt;/p&gt;
293
294 &lt;p&gt;I&#39;ve implemented this in the
295 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
296 git repository, and plan to provide the optimization as part of the
297 Debian Edu installation. If you want to test this yourself, you can
298 create two files in the installer (or in an udeb). One shell script
299 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
300
301 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
302 #!/bin/sh
303 set -e
304 . /usr/share/debconf/confmodule
305 info() {
306 logger -t my-pkgsel &quot;info: $*&quot;
307 }
308 error() {
309 logger -t my-pkgsel &quot;error: $*&quot;
310 }
311 override_install() {
312 apt-install eatmydata || true
313 if [ -x /target/usr/bin/eatmydata ] ; then
314 for bin in dpkg apt-get aptitude tasksel ; do
315 file=/usr/bin/$bin
316 # Test that the file exist and have not been diverted already.
317 if [ -f /target$file ] ; then
318 info &quot;diverting $file using eatmydata&quot;
319 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
320 &gt; /target$file.edu
321 chmod 755 /target$file.edu
322 in-target dpkg-divert --package debian-edu-config \
323 --rename --quiet --add $file
324 ln -sf ./$bin.edu /target$file
325 else
326 error &quot;unable to divert $file, as it is missing.&quot;
327 fi
328 done
329 else
330 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
331 fi
332 }
333
334 override_install
335 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
336
337 &lt;p&gt;To clean up, another shell script should go into
338 /usr/lib/finish-install.d/ with code like this:
339
340 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
341 #! /bin/sh -e
342 . /usr/share/debconf/confmodule
343 error() {
344 logger -t my-finish-install &quot;error: $@&quot;
345 }
346 remove_install_override() {
347 for bin in dpkg apt-get aptitude tasksel ; do
348 file=/usr/bin/$bin
349 if [ -x /target$file.edu ] ; then
350 rm /target$file
351 in-target dpkg-divert --package debian-edu-config \
352 --rename --quiet --remove $file
353 rm /target$file.edu
354 else
355 error &quot;Missing divert for $file.&quot;
356 fi
357 done
358 sync # Flush file buffers before continuing
359 }
360
361 remove_install_override
362 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
363
364 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
365 edu-eatmydata-install and call it from the pre-pkgsel.d and
366 finish-install.d scripts.&lt;/p&gt;
367
368 &lt;p&gt;By now you might ask if this change should get into the normal
369 Debian installer too? I suspect it should, but am not sure the
370 current debian-installer coordinators find it useful enough. It also
371 depend on the side effects of the change. I&#39;m not aware of any, but I
372 guess we will see if the change is safe after some more testing.
373 Perhaps there is some package in Debian depending on sync() and
374 fsync() having effect? Perhaps it should go into its own udeb, to
375 allow those of us wanting to enable it to do so without affecting
376 everyone.&lt;/p&gt;
377
378 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
379 will break installation of all programs using gnutls because of
380 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711. An updated
381 eatmydata package in Debian will solve it.&lt;/p&gt;
382 </description>
383 </item>
384
385 <item>
386 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
387 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
388 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
389 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
390 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
391 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
392 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
393 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
394 learn that there is a large set of publicly available key servers to
395 use when looking for peoples public key. So far I have used
396 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
397 were misbehaving, but those days are ended. The servers I have used
398 up until yesterday have been slow and some times unavailable. I hope
399 those problems are gone now.&lt;/p&gt;
400
401 &lt;p&gt;Behind the round robin DNS entry of the
402 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
403 there is a pool of more than 100 keyservers which are checked every
404 day to ensure they are well connected and up to date. It must be
405 better than what I have used so far. :)&lt;/p&gt;
406
407 &lt;p&gt;Yesterdays speaker told me that the service is the default
408 keyserver provided by the default configuration in GnuPG, but this do
409 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
410
411 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
412 line:&lt;/p&gt;
413
414 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
415 keyserver pool.sks-keyservers.net
416 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
417
418 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
419 entries in DNS. Just for fun, I did just that at work, so now every
420 user of GnuPG at the University of Oslo should find a OpenGPG
421 keyserver automatically should their need it:&lt;/p&gt;
422
423 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
424 % host -t srv _pgpkey-http._tcp.uio.no
425 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
426 %
427 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
428
429 &lt;p&gt;Now if only
430 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
431 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
432 very happy. It can look up a given key or search for a user ID, but I
433 normally do not want that, but to find a trust path from my key to
434 another key. Given a user ID or key ID, I would like to find (and
435 download) the keys representing a signature path from my key to the
436 key in question, to be able to get a trust path between the two keys.
437 This is as far as I can tell not possible today. Perhaps something
438 for a future version of the protocol?&lt;/p&gt;
439 </description>
440 </item>
441
442 <item>
443 <title>From English wiki to translated PDF and epub via Docbook</title>
444 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
445 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
446 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
447 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
448 project&lt;/a&gt; provide an instruction manual for teachers, system
449 administrators and other users that contain useful tips for setting up
450 and maintaining a Debian Edu installation. This text is about how the
451 text processing of this manual is handled in the project.&lt;/p&gt;
452
453 &lt;p&gt;One goal of the project is to provide information in the native
454 language of its users, and for this we need to handle translations.
455 But we also want to make sure each language contain the same
456 information, so for this we need a good way to keep the translations
457 in sync. And we want it to be easy for our users to improve the
458 documentation, avoiding the need to learn special formats or tools to
459 contribute, and the obvious way to do this is to make it possible to
460 edit the documentation using a web browser. We also want it to be
461 easy for translators to keep the translation up to date, and give them
462 help in figuring out what need to be translated. Here is the list of
463 tools and the process we have found trying to reach all these
464 goals.&lt;/p&gt;
465
466 &lt;p&gt;We maintain the authoritative source of our manual in the
467 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
468 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
469 front page with references to the different chapters, several pages
470 for each chapter, and finally one &quot;collection page&quot; gluing all the
471 chapters together into one large web page (aka
472 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
473 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
474 processing and translations. Thanks to the fact that the
475 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
476 wiki.debian.org support exporting pages in
477 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
478 the list of pages to export using the raw version of the AllInOne
479 page, loop over each of them to generate a Docbook XML version of the
480 manual. This process also download images and transform image
481 references to use the locally downloaded images. The generated
482 Docbook XML files are slightly broken, so some post-processing is done
483 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
484 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
485 a handfull of images. The XML file can now be used to generate PDF, HTML
486 and epub versions of the English manual. This is the basic step of
487 our process, making PDF (using dblatex), HTML (using xsltproc) and
488 epub (using dbtoepub) version from Docbook XML, and the resulting files
489 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
490
491 &lt;p&gt;But English documentation is not enough for us. We want translated
492 documentation too, and we want to make it easy for translators to
493 track the English original. For this we use the
494 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
495 which allow us to transform the English Docbook XML file into a
496 translation file (a .pot file), usable with the normal gettext based
497 translation tools used by those translating free software. The pot
498 file is used to create and maintain translation files (several .po
499 files), which the translations update with the native language
500 translations of all titles, paragraphs and blocks of text in the
501 original. The next step is combining the original English Docbook XML
502 and the translation file (say debian-edu-wheezy-manual.nb.po), to
503 create a translated Docbook XML file (in this case
504 debian-edu-wheezy-manual.nb.xml). This translated (or partly
505 translated, if the translation is not complete) Docbook XML file can
506 then be used like the original to create a PDF, HTML and epub version
507 of the documentation.&lt;/p&gt;
508
509 &lt;p&gt;The translators use different tools to edit the .po files. We
510 recommend using
511 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
512 while some use emacs and vi, others can use web based editors like
513 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
514 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
515 is where the .po file end up, in our git repository. Updated
516 translations can either be committed directly to git, or submitted as
517 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
518 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
519
520 &lt;p&gt;One challenge is images, which both might need to be translated (if
521 they show translated user applications), and are needed in different
522 formats when creating PDF and HTML versions (epub is a HTML version in
523 this regard). For this we transform the original PNG images to the
524 needed density and format during build, and have a way to provide
525 translated images by storing translated versions in
526 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
527 package maintainers know more.&lt;/p&gt;
528
529 &lt;p&gt;If you wonder what the result look like, we provide
530 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
531 of the documentation packages on the web&lt;/a&gt;. See for example the
532 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
533 PDF version&lt;/a&gt; or the
534 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
535 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
536 but perhaps it will be done in the future.&lt;/p&gt;
537
538 &lt;p&gt;To learn more, check out
539 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
540 debian-edu-doc package&lt;/a&gt;,
541 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
542 manual on the wiki&lt;/a&gt; and
543 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
544 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
545 </description>
546 </item>
547
548 <item>
549 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
550 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
551 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
552 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
553 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
554 related packages relevant for the computer installed automatically.
555 So I implemented one, using
556 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
557 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
558 run tasksel as user root. You should be presented with a new option,
559 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
560 select it, tasksel will install the packages isenkram claim is fit for
561 the current hardware, hot pluggable or not.&lt;p&gt;
562
563 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
564 description, and the other is the script used to extract the list of
565 packages to install. The first part is in
566 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
567 this:&lt;/p&gt;
568
569 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
570 Task: isenkram
571 Section: hardware
572 Description: Hardware specific packages (autodetected by isenkram)
573 Based on the detected hardware various hardware specific packages are
574 proposed.
575 Test-new-install: mark show
576 Relevance: 8
577 Packages: for-current-hardware
578 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
579
580 &lt;p&gt;The second part is in
581 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
582 this:&lt;/p&gt;
583
584 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
585 #!/bin/sh
586 #
587 (
588 isenkram-lookup
589 isenkram-autoinstall-firmware -l
590 ) | sort -u
591 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
592
593 &lt;p&gt;All in all, a very short and simple implementation making it
594 trivial to install the hardware dependent package we all may want to
595 have installed on our machines. I&#39;ve not been able to find a way to
596 get tasksel to tell you exactly which packages it plan to install
597 before doing the installation. So if you are curious or careful,
598 check the output from the isenkram-* command line tools first.&lt;/p&gt;
599
600 &lt;p&gt;The information about which packages are handling which hardware is
601 fetched either from the isenkram package itself in
602 /usr/share/isenkram/, from git.debian.org or from the APT package
603 database (using the Modaliases header). The APT package database
604 parsing have caused a nasty resource leak in the isenkram daemon (bugs
605 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
606 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
607 the python-apt code (bug
608 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
609 workaround I was able to get rid of the file descriptor leak and
610 reduce the memory leak from ~30 MiB per hardware detection down to
611 around 2 MiB per hardware detection. It should make the desktop
612 daemon a lot more useful. The fix is in version 0.7 uploaded to
613 unstable today.&lt;/p&gt;
614
615 &lt;p&gt;I believe the current way of mapping hardware to packages in
616 Isenkram is is a good draft, but in the future I expect isenkram to
617 use the AppStream data source for this. A proposal for getting proper
618 AppStream support into Debian is floating around as
619 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
620 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
621 project&lt;/a&gt; will take place this summer to improve the situation. I
622 look forward to seeing the result, and welcome patches for isenkram to
623 start using the information when it is ready.&lt;/p&gt;
624
625 &lt;p&gt;If you want your package to map to some specific hardware, either
626 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
627 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
628 package&lt;/a&gt; or submit a bug report with the details to the isenkram
629 package. See also
630 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
631 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
632 the information will be migrated to AppStream eventually, but for the
633 moment I got no better place to store it.&lt;/p&gt;
634 </description>
635 </item>
636
637 <item>
638 <title>FreedomBox milestone - all packages now in Debian Sid</title>
639 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
640 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
641 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
642 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
643 project&lt;/a&gt; is working on providing the software and hardware to make
644 it easy for non-technical people to host their data and communication
645 at home, and being able to communicate with their friends and family
646 encrypted and away from prying eyes. It is still going strong, and
647 today a major mile stone was reached.&lt;/p&gt;
648
649 &lt;p&gt;Today, the last of the packages currently used by the project to
650 created the system images were accepted into Debian Unstable. It was
651 the freedombox-setup package, which is used to configure the images
652 during build and on the first boot. Now all one need to get going is
653 the build code from the freedom-maker git repository and packages from
654 Debian. And once the freedombox-setup package enter testing, we can
655 build everything directly from Debian. :)&lt;/p&gt;
656
657 &lt;p&gt;Some key packages used by Freedombox are
658 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
659 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
660 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
661 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
662 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
663 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
664 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
665 are plans to integrate more packages into the setup. User
666 documentation is maintained on the Debian wiki. Please
667 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
668 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
669
670 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
671 setup, run this on a Debian machine using a user with sudo rights to
672 become root:&lt;/p&gt;
673
674 &lt;p&gt;&lt;pre&gt;
675 sudo apt-get install git vmdebootstrap mercurial python-docutils \
676 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
677 u-boot-tools
678 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
679 freedom-maker
680 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
681 &lt;/pre&gt;&lt;/p&gt;
682
683 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
684 devices. See the README in the freedom-maker git repo for more
685 details on the build. If you do not want all three images, trim the
686 make line. Note that the virtualbox-image target is not really
687 virtualbox specific. It create a x86 image usable in kvm, qemu,
688 vmware and any other x86 virtual machine environment. You might need
689 the version of vmdebootstrap in Jessie to get the build working, as it
690 include fixes for a race condition with kpartx.&lt;/p&gt;
691
692 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
693 method, boot a Debian Wheezy ISO and use this boot argument to load
694 the preseed values:&lt;/p&gt;
695
696 &lt;p&gt;&lt;pre&gt;
697 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
698 &lt;/pre&gt;&lt;/p&gt;
699
700 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
701 it still work.&lt;/p&gt;
702
703 &lt;p&gt;If you wonder how to help, one task you could look at is using
704 systemd as the boot system. It will become the default for Linux in
705 Jessie, so we need to make sure it is usable on the Freedombox. I did
706 a simple test a few weeks ago, and noticed dnsmasq failed to start
707 during boot when using systemd. I suspect there are other problems
708 too. :) To detect problems, there is a test suite included, which can
709 be run from the plinth web interface.&lt;/p&gt;
710
711 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
712 us get the new release published. :) Please join us on
713 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
714 irc.debian.org)&lt;/a&gt; and
715 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
716 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
717 </description>
718 </item>
719
720 <item>
721 <title>S3QL, a locally mounted cloud file system - nice free software</title>
722 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
723 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
724 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
725 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
726 solution for use at home. My requirements are simple, it must be
727 cheap and locally encrypted (in other words, I keep the encryption
728 keys, the storage provider do not have access to my private files).
729 One idea me and my friends had many years ago, before the cloud
730 storage providers showed up, was to use Google mail as storage,
731 writing a Linux block device storing blocks as emails in the mail
732 service provided by Google, and thus get heaps of free space. On top
733 of this one can add encryption, RAID and volume management to have
734 lots of (fairly slow, I admit that) cheap and encrypted storage. But
735 I never found time to implement such system. But the last few weeks I
736 have looked at a system called
737 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
738 mounted network backed file system with the features I need.&lt;/p&gt;
739
740 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
741 handling several different storage providers, any with Amazon S3,
742 Google Drive or OpenStack API. There are heaps of such storage
743 providers. S3QL can also use a local directory as storage, which
744 combined with sshfs allow for file storage on any ssh server. S3QL
745 include support for encryption, compression, de-duplication, snapshots
746 and immutable file systems, allowing me to mount the remote storage as
747 a local mount point, look at and use the files as if they were local,
748 while the content is stored in the cloud as well. This allow me to
749 have a backup that should survive fire. The file system can not be
750 shared between several machines at the same time, as only one can
751 mount it at the time, but any machine with the encryption key and
752 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
753
754 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
755 package is included already. So to get started, run &lt;tt&gt;apt-get
756 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
757 Greenqloud, after reading their nice recipe on
758 &lt;a href=&quot;https://greenqloud.zendesk.com/entries/44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy&quot;&gt;how
759 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
760 in Iceland more than those in USA when it come to keeping my personal
761 data safe and private, and thus would rather spend money on a company
762 in Iceland. Another nice recipe is available from the article
763 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
764 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
765 Admin magazine. When the provider is picked, figure out how to get
766 the API key needed to connect to the storage API. With Greencloud,
767 the key did not show up until I had added payment details to my
768 account.&lt;/p&gt;
769
770 &lt;p&gt;Armed with the API access details, it is time to create the file
771 system. First, create a new bucket in the cloud. This bucket is the
772 file system storage area. I picked a bucket name reflecting the
773 machine that was going to store data there, but any name will do.
774 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
775 the API login and password, and a locally created password. Store it
776 all in ~root/.s3ql/authinfo2 like this:
777
778 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
779 [s3c]
780 storage-url: s3c://s.greenqloud.com:443/bucket-name
781 backend-login: API-login
782 backend-password: API-password
783 fs-passphrase: local-password
784 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
785
786 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
787 but any sensible way to create a fairly random password should do it.
788 Armed with these details, it is now time to run mkfs, entering the API
789 details and password to create it:&lt;/p&gt;
790
791 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
792 # mkdir -m 700 /var/lib/s3ql-cache
793 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
794 --ssl s3c://s.greenqloud.com:443/bucket-name
795 Enter backend login:
796 Enter backend password:
797 Before using S3QL, make sure to read the user&#39;s guide, especially
798 the &#39;Important Rules to Avoid Loosing Data&#39; section.
799 Enter encryption password:
800 Confirm encryption password:
801 Generating random encryption key...
802 Creating metadata tables...
803 Dumping metadata...
804 ..objects..
805 ..blocks..
806 ..inodes..
807 ..inode_blocks..
808 ..symlink_targets..
809 ..names..
810 ..contents..
811 ..ext_attributes..
812 Compressing and uploading metadata...
813 Wrote 0.00 MB of compressed metadata.
814 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
815
816 &lt;p&gt;The next step is mounting the file system to make the storage available.
817
818 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
819 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
820 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
821 Using 4 upload threads.
822 Downloading and decompressing metadata...
823 Reading metadata...
824 ..objects..
825 ..blocks..
826 ..inodes..
827 ..inode_blocks..
828 ..symlink_targets..
829 ..names..
830 ..contents..
831 ..ext_attributes..
832 Mounting filesystem...
833 # df -h /s3ql
834 Filesystem Size Used Avail Use% Mounted on
835 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
836 #
837 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
838
839 &lt;p&gt;The file system is now ready for use. I use rsync to store my
840 backups in it, and as the metadata used by rsync is downloaded at
841 mount time, no network traffic (and storage cost) is triggered by
842 running rsync. To unmount, one should not use the normal umount
843 command, as this will not flush the cache to the cloud storage, but
844 instead running the umount.s3ql command like this:
845
846 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
847 # umount.s3ql /s3ql
848 #
849 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
850
851 &lt;p&gt;There is a fsck command available to check the file system and
852 correct any problems detected. This can be used if the local server
853 crashes while the file system is mounted, to reset the &quot;already
854 mounted&quot; flag. This is what it look like when processing a working
855 file system:&lt;/p&gt;
856
857 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
858 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
859 Using cached metadata.
860 File system seems clean, checking anyway.
861 Checking DB integrity...
862 Creating temporary extra indices...
863 Checking lost+found...
864 Checking cached objects...
865 Checking names (refcounts)...
866 Checking contents (names)...
867 Checking contents (inodes)...
868 Checking contents (parent inodes)...
869 Checking objects (reference counts)...
870 Checking objects (backend)...
871 ..processed 5000 objects so far..
872 ..processed 10000 objects so far..
873 ..processed 15000 objects so far..
874 Checking objects (sizes)...
875 Checking blocks (referenced objects)...
876 Checking blocks (refcounts)...
877 Checking inode-block mapping (blocks)...
878 Checking inode-block mapping (inodes)...
879 Checking inodes (refcounts)...
880 Checking inodes (sizes)...
881 Checking extended attributes (names)...
882 Checking extended attributes (inodes)...
883 Checking symlinks (inodes)...
884 Checking directory reachability...
885 Checking unix conventions...
886 Checking referential integrity...
887 Dropping temporary indices...
888 Backing up old metadata...
889 Dumping metadata...
890 ..objects..
891 ..blocks..
892 ..inodes..
893 ..inode_blocks..
894 ..symlink_targets..
895 ..names..
896 ..contents..
897 ..ext_attributes..
898 Compressing and uploading metadata...
899 Wrote 0.89 MB of compressed metadata.
900 #
901 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
902
903 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
904 quick, about the same speed as local file access. Uploading large
905 amount of data is to me limited by the bandwidth out of and into my
906 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
907 which is very close to my upload speed, and downloading the same
908 Debian installation ISO gave me 610 kiB/s, close to my download speed.
909 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
910 network, not the file system code. I do not know what a good cache
911 size would be, but suspect that the cache should e larger than your
912 working set.&lt;/p&gt;
913
914 &lt;p&gt;I mentioned that only one machine can mount the file system at the
915 time. If another machine try, it is told that the file system is
916 busy:&lt;/p&gt;
917
918 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
919 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
920 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
921 Using 8 upload threads.
922 Backend reports that fs is still mounted elsewhere, aborting.
923 #
924 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
925
926 &lt;p&gt;The file content is uploaded when the cache is full, while the
927 metadata is uploaded once every 24 hour by default. To ensure the
928 file system content is flushed to the cloud, one can either umount the
929 file system, or ask S3QL to flush the cache and metadata using
930 s3qlctrl:
931
932 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
933 # s3qlctrl upload-meta /s3ql
934 # s3qlctrl flushcache /s3ql
935 #
936 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
937
938 &lt;p&gt;If you are curious about how much space your data uses in the
939 cloud, and how much compression and deduplication cut down on the
940 storage usage, you can use s3qlstat on the mounted file system to get
941 a report:&lt;/p&gt;
942
943 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
944 # s3qlstat /s3ql
945 Directory entries: 9141
946 Inodes: 9143
947 Data blocks: 8851
948 Total data size: 22049.38 MB
949 After de-duplication: 21955.46 MB (99.57% of total)
950 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
951 Database size: 2.39 MB (uncompressed)
952 (some values do not take into account not-yet-uploaded dirty blocks in cache)
953 #
954 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
955
956 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
957 storage. I did not try to locate them all, but am aware of at least
958 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
959 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
960 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
961 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
962 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
963 accept payment in Bitcoin. Pick one that suit your need. Some of
964 them provide several GiB of free storage, but the prize models are
965 quite different and you will have to figure out what suits you
966 best.&lt;/p&gt;
967
968 &lt;p&gt;While researching this blog post, I had a look at research papers
969 and posters discussing the S3QL file system. There are several, which
970 told me that the file system is getting a critical check by the
971 science community and increased my confidence in using it. One nice
972 poster is titled
973 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
974 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
975 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
976 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
977 and Pamela Smith. Please have a look.&lt;/p&gt;
978
979 &lt;p&gt;Given my problems with different file systems earlier, I decided to
980 check out the mounted S3QL file system to see if it would be usable as
981 a home directory (in other word, that it provided POSIX semantics when
982 it come to locking and umask handling etc). Running
983 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html&quot;&gt;my
984 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
985 no error was found. So the file system can be used for home
986 directories, if one chooses to do so.&lt;/p&gt;
987
988 &lt;p&gt;If you do not want a locally file system, and want something that
989 work without the Linux fuse file system, I would like to mention the
990 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
991 provide locally encrypted backup using a command line client. It have
992 a nicer access control system, where one can split out read and write
993 access, allowing some systems to write to the backup and others to
994 only read from it.&lt;/p&gt;
995
996 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
997 activities, please send Bitcoin donations to my address
998 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
999 </description>
1000 </item>
1001
1002 <item>
1003 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
1004 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
1005 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
1006 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
1007 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
1008 project&lt;/a&gt; is working on providing the software and hardware for
1009 making it easy for non-technical people to host their data and
1010 communication at home, and being able to communicate with their
1011 friends and family encrypted and away from prying eyes. It has been
1012 going on for a while, and is slowly progressing towards a new test
1013 release (0.2).&lt;/p&gt;
1014
1015 &lt;p&gt;And what day could be better than the Pi day to announce that the
1016 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
1017 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
1018 system), and can also be installed using a Debian installer preseed
1019 file. The Debian based Freedombox is now based on Debian Jessie,
1020 where most of the needed packages used are already present. Only one,
1021 the freedombox-setup package, is missing. To try to build your own
1022 boot image to test the current status, fetch the freedom-maker scripts
1023 and build using
1024 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
1025 with a user with sudo access to become root:
1026
1027 &lt;pre&gt;
1028 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
1029 freedom-maker
1030 sudo apt-get install git vmdebootstrap mercurial python-docutils \
1031 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
1032 u-boot-tools
1033 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
1034 &lt;/pre&gt;
1035
1036 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
1037 devices. See the README for more details on the build. If you do not
1038 want all three images, trim the make line. But note that thanks to &lt;a
1039 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
1040 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
1041 kpartx call.&lt;/p&gt;
1042
1043 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
1044 method, boot a Debian Wheezy ISO and use this boot argument to load
1045 the preseed values:&lt;/p&gt;
1046
1047 &lt;pre&gt;
1048 url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-jessie.dat&lt;/a&gt;
1049 &lt;/pre&gt;
1050
1051 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
1052 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
1053 currently hang while setting up APT sources. Killing the
1054 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
1055 installation will get the installation going. This affect all
1056 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
1057
1058 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
1059 us get the new release published. :) Please join us on
1060 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
1061 irc.debian.org)&lt;/a&gt; and
1062 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1063 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1064 </description>
1065 </item>
1066
1067 <item>
1068 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1069 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1070 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1071 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1072 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1073 innetgr tools, because I needed them in
1074 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1075 ng-utils, and it has served me well. I placed the project under the
1076 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1077 repository. But many years ago, the CVS repository was dropped (lost,
1078 not migrated to new hardware, not sure), and the project have lacked a
1079 proper home since then.&lt;/p&gt;
1080
1081 &lt;p&gt;Last summer, I had a look at the package and made a new release
1082 fixing a irritating crash bug, but was unable to store the changes in
1083 a proper source control system. I applied for a project on
1084 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1085 to follow up on it. Until today. :)&lt;/p&gt;
1086
1087 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1088 now have a new home, and a git repository with the highlight of the
1089 history of the project. I published all release tarballs and imported
1090 them into the git repository. As the project is really stable and not
1091 expected to gain new features any time soon, I decided to make a new
1092 release and call it 1.0. Visit the new project home on
1093 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1094 if you want to check it out. The new version is also uploaded into
1095 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1096 </description>
1097 </item>
1098
1099 <item>
1100 <title>Testing sysvinit from experimental in Debian Hurd</title>
1101 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1102 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1103 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1104 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1105 their changes into sysvinit, to allow them to use the normal sysvinit
1106 boot system instead of their old one. This follow up on the
1107 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1108 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1109 get Debian on Hurd working more like Debian on Linux. To get started,
1110 I downloaded a prebuilt hard disk image from
1111 &lt;a href=&quot;http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz&quot;&gt;http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz&lt;/a&gt;,
1112 and started it using virt-manager.&lt;/p&gt;
1113
1114 &lt;p&gt;The first think I had to do after logging in (root without any
1115 password) was to get the network operational. I followed
1116 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1117 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1118 commands as root to get the machine to accept a IP address from the
1119 kvm internal DHCP server:&lt;/p&gt;
1120
1121 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1122 settrans -fgap /dev/netdde /hurd/netdde
1123 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1124 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1125 dhclient /dev/eth0
1126 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1127
1128 &lt;p&gt;After this, the machine had internet connectivity, and I could
1129 upgrade it and install the sysvinit packages from experimental and
1130 enable it as the default boot system in Hurd.&lt;/p&gt;
1131
1132 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1133 running on the machine it for ssh login to work a password need to be
1134 set. Also, note that a bug somewhere in openssh on Hurd block
1135 compression from working. Remember to turn that off on the client
1136 side.&lt;/p&gt;
1137
1138 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1139 stuff:&lt;/p&gt;
1140
1141 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1142 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1143 deb http://http.debian.net/debian/ experimental main
1144 EOF
1145 apt-get update
1146 apt-get dist-upgrade
1147 apt-get install -t experimental initscripts sysv-rc sysvinit \
1148 sysvinit-core sysvinit-utils
1149 update-alternatives --config runsystem
1150 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1151
1152 &lt;p&gt;To reboot after switching boot system, you have to use
1153 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1154 yet a sysvinit process able to receive the signals from the normal
1155 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1156 upgrading every package and rebooting, the network come up with DHCP
1157 after boot as it should, and the settrans/pkill hack mentioned at the
1158 start is no longer needed. But for some strange reason, there are no
1159 longer any login prompt in the virtual console, so I logged in using
1160 ssh instead.
1161
1162 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1163 fail some times. No idea what the cause is, but hope the Hurd porters
1164 figure it out. At least Justus said on IRC (#debian-hurd on
1165 irc.debian.org) that they are aware of the problem. A way to reduce
1166 the impact is to upgrade to the Hurd packages built by Justus by
1167 adding this repository to the machine:&lt;/p&gt;
1168
1169 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1170 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1171 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1172 EOF
1173 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1174
1175 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1176 http://ftp.debian-ports.org/debian, because some of the packages in
1177 unstable do not yet include the required patches that are lingering in
1178 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1179
1180 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1181 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1182 i emacs - GNU Emacs editor (metapackage)
1183 i gdb - GNU Debugger
1184 i hurd-recommended - Miscellaneous translators
1185 i isc-dhcp-client - ISC DHCP client
1186 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1187 i libc-bin - Embedded GNU C Library: Binaries
1188 i libc-dev-bin - Embedded GNU C Library: Development binaries
1189 i libc0.3 - Embedded GNU C Library: Shared libraries
1190 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1191 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1192 i multiarch-support - Transitional package to ensure multiarch compatibilit
1193 i A x11-common - X Window System (X.Org) infrastructure
1194 i xorg - X.Org X Window System
1195 i A xserver-xorg - X.Org X server
1196 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1197 #
1198 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1199
1200 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1201 X.org did not work out of the box and I never took the time to follow
1202 the porters instructions to fix it. This time I was interested in the
1203 command line stuff.&lt;p&gt;
1204 </description>
1205 </item>
1206
1207 <item>
1208 <title>New chrpath release 0.16</title>
1209 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1210 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1211 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1212 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1213 find problems in C, C++ and Java code using static source code
1214 analysis. It can detect a lot of different problems, and is very
1215 useful to find memory and locking bugs in the error handling part of
1216 the source. The company behind it provide
1217 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1218 a community service&lt;/a&gt;, and many hundred free software projects are
1219 already checked. A few days ago I decided to have a closer look at
1220 the Coverity system, and discovered that the
1221 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1222 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1223 projects I am involved with was already registered. But these are
1224 fairly big, and I would also like to have a small and easy project to
1225 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1226 checking of the chrpath project&lt;/a&gt;. It was
1227 added to the checker and discovered seven potential defects. Six of
1228 these were real, mostly resource &quot;leak&quot; when the program detected an
1229 error. Nothing serious, as the resources would be released a fraction
1230 of a second later when the program exited because of the error, but it
1231 is nice to do it right in case the source of the program some time in
1232 the future end up in a library. Having fixed all defects and added
1233 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1234 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1235 publish a new release. These are the release notes:&lt;/p&gt;
1236
1237 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1238
1239 &lt;ul&gt;
1240
1241 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1242 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1243 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1244
1245 &lt;/ul&gt;
1246
1247 &lt;p&gt;You can
1248 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1249 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1250 project if something is wrong with the new release. The test suite
1251 did not discover any old errors, so if you find a new one, please also
1252 include a test suite check.&lt;/p&gt;
1253 </description>
1254 </item>
1255
1256 <item>
1257 <title>New chrpath release 0.15</title>
1258 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1259 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1260 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1261 <description>&lt;p&gt;After many years break from the package and a vain hope that
1262 development would be continued by someone else, I finally pulled my
1263 acts together this morning and wrapped up a new release of chrpath,
1264 the command line tool to modify the rpath and runpath of already
1265 compiled ELF programs. The update was triggered by the persistence of
1266 Isha Vishnoi at IBM, which needed a new config.guess file to get
1267 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1268 is working on. I checked the
1269 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1270 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1271 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1272 packages for interesting patches (failed to find the source from
1273 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1274 These are the release notes:&lt;/p&gt;
1275
1276 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1277
1278 &lt;ul&gt;
1279
1280 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1281 with newer architectures. Thanks to isha vishnoi for the heads
1282 up.&lt;/li&gt;
1283
1284 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1285
1286 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1287 Matthias Klose.&lt;/li&gt;
1288
1289 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1290 Petr Machata found in Fedora.&lt;/li&gt;
1291
1292 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1293 .dynamic is a NULL terminated string. Based on patch found in
1294 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1295
1296 &lt;/ul&gt;
1297
1298 &lt;p&gt;You can
1299 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1300 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1301 project if something is wrong with the new release. The test suite
1302 did not discover any old errors, so if you find a new one, please also
1303 include a testsuite check.&lt;/p&gt;
1304 </description>
1305 </item>
1306
1307 <item>
1308 <title>Debian init.d boot script example for rsyslog</title>
1309 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1310 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1311 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1312 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1313 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1314 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1315 init.d scripts at all. Here is an example init.d script, ie a rewrite
1316 of /etc/init.d/rsyslog:&lt;/p&gt;
1317
1318 &lt;p&gt;&lt;pre&gt;
1319 #!/lib/init/init-d-script
1320 ### BEGIN INIT INFO
1321 # Provides: rsyslog
1322 # Required-Start: $remote_fs $time
1323 # Required-Stop: umountnfs $time
1324 # X-Stop-After: sendsigs
1325 # Default-Start: 2 3 4 5
1326 # Default-Stop: 0 1 6
1327 # Short-Description: enhanced syslogd
1328 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1329 # It is quite compatible to stock sysklogd and can be
1330 # used as a drop-in replacement.
1331 ### END INIT INFO
1332 DESC=&quot;enhanced syslogd&quot;
1333 DAEMON=/usr/sbin/rsyslogd
1334 &lt;/pre&gt;&lt;/p&gt;
1335
1336 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1337 script was 137 lines, and the above is just 15 lines, most of it meta
1338 info/comments.&lt;/p&gt;
1339
1340 &lt;p&gt;How to do this, you ask? Well, one create a new script
1341 /lib/init/init-d-script looking something like this:
1342
1343 &lt;p&gt;&lt;pre&gt;
1344 #!/bin/sh
1345
1346 # Define LSB log_* functions.
1347 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1348 # and status_of_proc is working.
1349 . /lib/lsb/init-functions
1350
1351 #
1352 # Function that starts the daemon/service
1353
1354 #
1355 do_start()
1356 {
1357 # Return
1358 # 0 if daemon has been started
1359 # 1 if daemon was already running
1360 # 2 if daemon could not be started
1361 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1362 || return 1
1363 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1364 $DAEMON_ARGS \
1365 || return 2
1366 # Add code here, if necessary, that waits for the process to be ready
1367 # to handle requests from services started subsequently which depend
1368 # on this one. As a last resort, sleep for some time.
1369 }
1370
1371 #
1372 # Function that stops the daemon/service
1373 #
1374 do_stop()
1375 {
1376 # Return
1377 # 0 if daemon has been stopped
1378 # 1 if daemon was already stopped
1379 # 2 if daemon could not be stopped
1380 # other if a failure occurred
1381 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1382 RETVAL=&quot;$?&quot;
1383 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1384 # Wait for children to finish too if this is a daemon that forks
1385 # and if the daemon is only ever run from this initscript.
1386 # If the above conditions are not satisfied then add some other code
1387 # that waits for the process to drop all resources that could be
1388 # needed by services started subsequently. A last resort is to
1389 # sleep for some time.
1390 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1391 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1392 # Many daemons don&#39;t delete their pidfiles when they exit.
1393 rm -f $PIDFILE
1394 return &quot;$RETVAL&quot;
1395 }
1396
1397 #
1398 # Function that sends a SIGHUP to the daemon/service
1399 #
1400 do_reload() {
1401 #
1402 # If the daemon can reload its configuration without
1403 # restarting (for example, when it is sent a SIGHUP),
1404 # then implement that here.
1405 #
1406 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1407 return 0
1408 }
1409
1410 SCRIPTNAME=$1
1411 scriptbasename=&quot;$(basename $1)&quot;
1412 echo &quot;SN: $scriptbasename&quot;
1413 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
1414 script=&quot;$1&quot;
1415 shift
1416 . $script
1417 else
1418 exit 0
1419 fi
1420
1421 NAME=$(basename $DAEMON)
1422 PIDFILE=/var/run/$NAME.pid
1423
1424 # Exit if the package is not installed
1425 #[ -x &quot;$DAEMON&quot; ] || exit 0
1426
1427 # Read configuration variable file if it is present
1428 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
1429
1430 # Load the VERBOSE setting and other rcS variables
1431 . /lib/init/vars.sh
1432
1433 case &quot;$1&quot; in
1434 start)
1435 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
1436 do_start
1437 case &quot;$?&quot; in
1438 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1439 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1440 esac
1441 ;;
1442 stop)
1443 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
1444 do_stop
1445 case &quot;$?&quot; in
1446 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1447 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1448 esac
1449 ;;
1450 status)
1451 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
1452 ;;
1453 #reload|force-reload)
1454 #
1455 # If do_reload() is not implemented then leave this commented out
1456 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
1457 #
1458 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
1459 #do_reload
1460 #log_end_msg $?
1461 #;;
1462 restart|force-reload)
1463 #
1464 # If the &quot;reload&quot; option is implemented then remove the
1465 # &#39;force-reload&#39; alias
1466 #
1467 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
1468 do_stop
1469 case &quot;$?&quot; in
1470 0|1)
1471 do_start
1472 case &quot;$?&quot; in
1473 0) log_end_msg 0 ;;
1474 1) log_end_msg 1 ;; # Old process is still running
1475 *) log_end_msg 1 ;; # Failed to start
1476 esac
1477 ;;
1478 *)
1479 # Failed to stop
1480 log_end_msg 1
1481 ;;
1482 esac
1483 ;;
1484 *)
1485 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
1486 exit 3
1487 ;;
1488 esac
1489
1490 :
1491 &lt;/pre&gt;&lt;/p&gt;
1492
1493 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
1494 lot. I did not really polish the approach, so it might not always
1495 work out of the box, but you get the idea. I did not try very hard to
1496 optimize it nor make it more robust either.&lt;/p&gt;
1497
1498 &lt;p&gt;A better argument for switching init system in Debian than reducing
1499 the size of init scripts (which is a good thing to do anyway), is to
1500 get boot system that is able to handle the kernel events sensibly and
1501 robustly, and do not depend on the boot to run sequentially. The boot
1502 and the kernel have not behaved sequentially in years.&lt;/p&gt;
1503 </description>
1504 </item>
1505
1506 <item>
1507 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
1508 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
1509 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
1510 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
1511 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
1512 remote display access is the preferred solution with oVirt and RedHat
1513 Enterprise Virtualization, and I was sad to discover the other day
1514 that the browser plugin needed to use these systems seamlessly was
1515 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
1516 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
1517 2013-04-01, so I decided to wrap up a package based on the great work
1518 from Cajus Pollmeier and put it in a collab-maint maintained git
1519 repository to get a package I could use. I would very much like
1520 others to help me maintain the package (or just take over, I do not
1521 mind), but as no-one had volunteered so far, I just uploaded it to
1522 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
1523
1524 &lt;p&gt;The source is now available from
1525 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&quot;&gt;http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary&lt;/a&gt;.&lt;/p&gt;
1526 </description>
1527 </item>
1528
1529 <item>
1530 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
1531 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
1532 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
1533 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
1534 <description>&lt;p&gt;The
1535 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
1536 program is a a very nice system to create virtual machine images. It
1537 create a image file, add a partition table, mount it and run
1538 debootstrap in the mounted directory to create a Debian system on a
1539 stick. Yesterday, I decided to try to teach it how to make images for
1540 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
1541 of a plan to simplify the build system for
1542 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
1543 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
1544 the virtualbox images, but its current build system made multistrap
1545 based system for Dreamplug images, and it is lacking support for
1546 Raspberry Pi.&lt;/p&gt;
1547
1548 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
1549 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1550 code and adjusted it to be able to build armel images on my amd64
1551 Debian laptop. I ended up giving vmdebootstrap five new options,
1552 allowing me to replicate the image creation process I use to make
1553 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
1554 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
1555 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
1556 call debootstrap with --foreign and to copy the handler into the
1557 generated chroot before running the second stage. This allow
1558 vmdebootstrap to create armel images on an amd64 host. Next I added
1559 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
1560 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
1561 given file system type, allowing me to create an image with a vfat
1562 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
1563 variant&lt;/tt&gt; option to allow me to create smaller images without the
1564 Debian base system packages installed. Finally, I added an option
1565 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
1566 as a boot loader. It is not needed on the Raspberry Pi and probably
1567 most other non-x86 architectures. The changes were accepted by the
1568 upstream author of vmdebootstrap yesterday and today, and is now
1569 available from
1570 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
1571 upstream project page&lt;/a&gt;.&lt;/p&gt;
1572
1573 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
1574 create a small script (the customize script) to add the non-free
1575 binary blob needed to boot the Raspberry Pi and the APT source
1576 list:&lt;/p&gt;
1577
1578 &lt;p&gt;&lt;pre&gt;
1579 #!/bin/sh
1580 set -e # Exit on first error
1581 rootdir=&quot;$1&quot;
1582 cd &quot;$rootdir&quot;
1583 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
1584 deb http://http.debian.net/debian/ jessie main contrib non-free
1585 EOF
1586 # Install non-free binary blob needed to boot Raspberry Pi. This
1587 # install a kernel somewhere too.
1588 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1589 -O $rootdir/usr/bin/rpi-update
1590 chmod a+x $rootdir/usr/bin/rpi-update
1591 mkdir -p $rootdir/lib/modules
1592 touch $rootdir/boot/start.elf
1593 chroot $rootdir rpi-update
1594 &lt;/pre&gt;&lt;/p&gt;
1595
1596 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
1597 to build the image:&lt;/p&gt;
1598
1599 &lt;pre&gt;
1600 sudo ./vmdebootstrap \
1601 --variant minbase \
1602 --arch armel \
1603 --distribution jessie \
1604 --mirror http://http.debian.net/debian \
1605 --image test.img \
1606 --size 600M \
1607 --bootsize 64M \
1608 --boottype vfat \
1609 --log-level debug \
1610 --verbose \
1611 --no-kernel \
1612 --no-extlinux \
1613 --root-password raspberry \
1614 --hostname raspberrypi \
1615 --foreign /usr/bin/qemu-arm-static \
1616 --customize `pwd`/customize \
1617 --package netbase \
1618 --package git-core \
1619 --package binutils \
1620 --package ca-certificates \
1621 --package wget \
1622 --package kmod
1623 &lt;/pre&gt;&lt;/p&gt;
1624
1625 &lt;p&gt;The list of packages being installed are the ones needed by
1626 rpi-update to make the image bootable on the Raspberry Pi, with the
1627 exception of netbase, which is needed by debootstrap to find
1628 /etc/hosts with the minbase variant. I really wish there was a way to
1629 set up an Raspberry Pi using only packages in the Debian archive, but
1630 that is not possible as far as I know, because it boots from the GPU
1631 using a non-free binary blob.&lt;/p&gt;
1632
1633 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
1634 probably a few others installed. I have not checked the complete
1635 build dependency list.&lt;/p&gt;
1636
1637 &lt;p&gt;The resulting image will not use the hardware floating point unit
1638 on the Raspberry PI, because the armel architecture in Debian is not
1639 optimized for that use. So the images created will be a bit slower
1640 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
1641 </description>
1642 </item>
1643
1644 <item>
1645 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
1646 <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>
1647 <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>
1648 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
1649 <description>&lt;p&gt;The last few days I came across a few good causes that should get
1650 wider attention. I recommend signing and donating to each one of
1651 these. :)&lt;/p&gt;
1652
1653 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
1654 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
1655 Women program which is a Google Summer of Code like initiative to get
1656 more women involved in free software. One debian sponsor has offered
1657 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
1658 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
1659 hope you will to. :)&lt;/p&gt;
1660
1661 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
1662 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
1663 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
1664 take place these days, and their need to fund the work. I&#39;ve already
1665 donated. Are you next?&lt;/p&gt;
1666
1667 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
1668 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1669 statement under the heading
1670 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
1671 Access&lt;/a&gt; for those of us asking for more focus on open access in the
1672 Norwegian government. So far 499 signatures. I hope you will sign it
1673 too.&lt;/p&gt;
1674 </description>
1675 </item>
1676
1677 <item>
1678 <title>Videos about the Freedombox project - for inspiration and learning</title>
1679 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
1680 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
1681 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
1682 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
1683 project&lt;/a&gt; have been going on for a while, and have presented the
1684 vision, ideas and solution several places. Here is a little
1685 collection of videos of talks and presentation of the project.&lt;/p&gt;
1686
1687 &lt;ul&gt;
1688
1689 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
1690 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
1691
1692 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
1693 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1694
1695 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
1696 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1697 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
1698 (Youtube)&lt;/li&gt;
1699
1700 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
1701 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
1702
1703 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
1704 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1705
1706 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
1707 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1708 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
1709
1710 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
1711 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
1712 (Youtube)&lt;/li&gt;
1713
1714 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
1715 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
1716
1717 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
1718 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
1719
1720 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
1721 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1722 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
1723
1724 &lt;/ul&gt;
1725
1726 &lt;p&gt;A larger list is available from
1727 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
1728 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
1729
1730 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
1731 Jessie is coming along quite well, and soon both Owncloud and using
1732 Tor should be available for testers of the Freedombox solution. :) In
1733 a few weeks I hope everything needed to test it is included in Debian.
1734 The withsqlite package is already in Debian, and the plinth package is
1735 pending in NEW. The third and vital part of that puzzle is the
1736 metapackage/setup framework, which is still pending an upload. Join
1737 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
1738 (#freedombox on irc.debian.org)&lt;/a&gt; and
1739 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1740 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1741 </description>
1742 </item>
1743
1744 <item>
1745 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
1746 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
1747 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
1748 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
1749 <description>&lt;p&gt;I was introduced to the
1750 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
1751 in 2010, when Eben Moglen presented his vision about serving the need
1752 of non-technical people to keep their personal information private and
1753 within the legal protection of their own homes. The idea is to give
1754 people back the power over their network and machines, and return
1755 Internet back to its intended peer-to-peer architecture. Instead of
1756 depending on a central service, the Freedombox will give everyone
1757 control over their own basic infrastructure.&lt;/p&gt;
1758
1759 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
1760 taken priority. But this summers nasty news about the misuse of trust
1761 and privilege exercised by the &quot;western&quot; intelligence gathering
1762 communities increased my eagerness to contribute to a point where I
1763 actually started working on the project a while back.&lt;/p&gt;
1764
1765 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
1766 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
1767 create a simple and cheap Debian based appliance that anyone can hook
1768 up in their home and get access to secure and private services and
1769 communication. The initial deployment platform have been the
1770 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
1771 which is a piece of hardware I do not own. So to be able to test what
1772 the current Freedombox setup look like, I had to come up with a way to install
1773 it on some hardware I do have access to. I have rewritten the
1774 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
1775 image build framework to use .deb packages instead of only copying
1776 setup into the boot images, and thanks to this rewrite I am able to
1777 set up any machine supported by Debian Wheezy as a Freedombox, using
1778 the previously mentioned deb (and a few support debs for packages
1779 missing in Debian).&lt;/p&gt;
1780
1781 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
1782 scripts
1783 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
1784 and a administrative web interface
1785 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
1786 withsqlite), as well as a privacy enhancing proxy based on
1787 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
1788 (freedombox-privoxy). There is also a web/javascript based XMPP
1789 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
1790 trying (unsuccessfully so far) to talk to the XMPP server
1791 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
1792 web interface is pluggable, and the goal is to use it to enable OpenID
1793 services, mesh network connectivity, use of TOR, etc, etc. Not much of
1794 this is really working yet, see
1795 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
1796 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
1797 on github at the moment. The HTTP proxy is operational out of the
1798 box, and the admin web interface can be used to add/remove plinth
1799 users. I&#39;ve not been able to do anything else with it so far, but
1800 know there are several branches spread around github and other places
1801 with lots of half baked features.&lt;/p&gt;
1802
1803 &lt;p&gt;Anyway, if you want to have a look at the current state, the
1804 following recipes should work to give you a test machine to poke
1805 at.&lt;/p&gt;
1806
1807 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
1808
1809 &lt;ol&gt;
1810
1811 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
1812 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
1813 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
1814 to the Debian installer:&lt;p&gt;
1815 &lt;pre&gt;url=&lt;a href=&quot;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&quot;&gt;http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat&lt;/a&gt;&lt;/pre&gt;&lt;/li&gt;
1816
1817 &lt;li&gt;Answer the few language/region/password questions and pick disk to
1818 install on.&lt;/li&gt;
1819
1820 &lt;li&gt;When the installation is finished and the machine have rebooted a
1821 few times, your Freedombox is ready for testing.&lt;/li&gt;
1822
1823 &lt;/ol&gt;
1824
1825 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
1826
1827 &lt;ol&gt;
1828
1829 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
1830 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
1831 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
1832 &lt;pre&gt;
1833 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
1834 &lt;/pre&gt;&lt;/li&gt;
1835 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
1836 &lt;pre&gt;
1837 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
1838 apt-key add -
1839 apt-get update
1840 apt-get install freedombox-setup
1841 /usr/lib/freedombox/setup
1842 &lt;/pre&gt;&lt;/li&gt;
1843 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
1844
1845 &lt;/ol&gt;
1846
1847 &lt;p&gt;You can test it on other architectures too, but because the
1848 freedombox-privoxy package is binary, it will only work as intended on
1849 the architectures where I have had time to build the binary and put it
1850 in my APT repository. But do not let this stop you. It is only a
1851 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
1852
1853 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
1854 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
1855 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
1856 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
1857
1858 &lt;p&gt;Please let me know if this works for you, or if you have any
1859 problems. We gather on the IRC channel
1860 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
1861 irc.debian.org and the
1862 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
1863 mailing list&lt;/a&gt;.&lt;/p&gt;
1864
1865 &lt;p&gt;Once you get your freedombox operational, you can visit
1866 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
1867 welcome screen (dead end - do not be surprised if you are unable to
1868 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
1869 to look at the rest of plinth. The default user is &#39;admin&#39; and the
1870 default password is &#39;secret&#39;.&lt;/p&gt;
1871 </description>
1872 </item>
1873
1874 <item>
1875 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
1876 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
1877 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
1878 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
1879 <description>&lt;p&gt;Earlier, I reported about
1880 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html&quot;&gt;my
1881 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
1882 told by IBM that the original disk should be thrown away. And as
1883 there no longer was a problem if I bricked the firmware, I decided
1884 today to try to install Intel firmware to replace the Lenovo firmware
1885 currently on the disk.&lt;/p&gt;
1886
1887 &lt;p&gt;I searched the Intel site for firmware, and found
1888 &lt;a href=&quot;https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&amp;ProdId=3472&amp;DwnldID=18363&amp;ProductFamily=Solid-State+Drives+and+Caching&amp;ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive&amp;ProductProduct=Intel%c2%ae+SSD+520+Series+(180GB%2c+2.5in+SATA+6Gb%2fs%2c+25nm%2c+MLC)&amp;lang=eng&quot;&gt;issdfut_2.0.4.iso&lt;/a&gt;
1889 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
1890 according to the site should contain the latest firmware for SSD
1891 disks. I inserted the broken disk in one of my spare laptops and
1892 booted the ISO from a USB stick. The disk was recognized, but the
1893 program claimed the newest firmware already were installed and refused
1894 to insert any Intel firmware. So no change, and the disk is still
1895 unable to handle write load. :( I guess the only way to get them
1896 working would be if Lenovo releases new firmware. No idea how likely
1897 that is. Anyway, just blogging about this test for completeness. I
1898 got a working Samsung disk, and see no point in spending more time on
1899 the broken disks.&lt;/p&gt;
1900 </description>
1901 </item>
1902
1903 <item>
1904 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
1905 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
1906 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
1907 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
1908 <description>&lt;p&gt;Today I switched to
1909 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
1910 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
1911 my new Thinkpad X230, which was delivered with an
1912 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html&quot;&gt;180
1913 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
1914 sustained writes. My hardware supplier have been very forthcoming in
1915 trying to find a solution, and after first trying with another
1916 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
1917 disk instead to fix it once and for all. The Samsung disk survived
1918 the installation of Debian with encrypted disks (filling the disk with
1919 random data during installation killed the first two), and I thus
1920 decided to trust it with my data. I have installed it as a Debian Edu
1921 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
1922 server at home using Kerberos and LDAP, and will use it as my work
1923 station from now on.&lt;/p&gt;
1924
1925 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
1926 Debian Wheezy default installation need to be tuned a bit to increase
1927 performance and increase life time of the disk. The Linux kernel and
1928 user space applications do not yet adjust automatically to such
1929 environment. To make it easier for my self, I created a draft Debian
1930 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
1931 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
1932 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
1933 is set up to adjust the setup of the machine by just installing the
1934 package. If there is any non-SSD disk in the machine, the package
1935 will refuse to install, as I did not try to write any logic to sort
1936 file systems in SSD and non-SSD file systems.&lt;/p&gt;
1937
1938 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
1939 set up Debian Wheezy with an SSD. It is adjusted to my use case,
1940 where I set up the machine with one large encrypted partition (in
1941 addition to /boot), put LVM on top of this and set up partitions on
1942 top of this again. See the README file in the package source for the
1943 references I used to pick the settings. At the moment these
1944 parameters are tuned:&lt;/p&gt;
1945
1946 &lt;ul&gt;
1947
1948 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
1949 (adding discard to /etc/crypttab)&lt;/li&gt;
1950
1951 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
1952 this case a cryptsetup partition) by changing issue_discards from
1953 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
1954
1955 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
1956 systems.&lt;/li&gt;
1957
1958 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
1959 /etc/fstab.&lt;/li&gt;
1960
1961 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
1962
1963 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
1964 cron.daily).&lt;/li&gt;
1965
1966 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
1967 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
1968
1969 &lt;/ul&gt;
1970
1971 &lt;p&gt;During installation, I cancelled the part where the installer fill
1972 the disk with random data, as this would kill the SSD performance for
1973 little gain. My goal with the encrypted file system is to ensure
1974 those stealing my laptop end up with a brick and not a working
1975 computer. I have no hope in keeping the really resourceful people
1976 from getting the data on the disk (see
1977 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
1978 Thus I concluded that adding the discard option to crypttab is the
1979 right thing to do.&lt;/p&gt;
1980
1981 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
1982 it for SSD, but others recommended deadline and a benchmark I found
1983 indicated that deadline might be better for interactive use.&lt;/p&gt;
1984
1985 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
1986 and ext4, but read that it would give a performance hit ever time a
1987 file is removed, and thought it best to that that slowdown once a day
1988 instead of during my work.&lt;/p&gt;
1989
1990 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
1991 this is already done by Debian Edu.&lt;/p&gt;
1992
1993 &lt;p&gt;I have not yet started on the user space tuning. I expect
1994 iceweasel need some tuning, and perhaps other applications too, but
1995 have not yet had time to investigate those parts.&lt;/p&gt;
1996
1997 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
1998 there.&lt;/p&gt;
1999
2000 &lt;p&gt;As for the answer to the question in the title of this blog post,
2001 as far as I know, the only solution I know about is to replace the
2002 disk. It might be possible to flash it with Intel firmware instead of
2003 the Lenovo firmware. But I have not tried and did not want to do so
2004 without approval from Lenovo as I wanted to keep the warranty on the
2005 disk until a solution was found and they wanted the broken disks
2006 back.&lt;/p&gt;
2007 </description>
2008 </item>
2009
2010 <item>
2011 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
2012 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
2013 <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>
2014 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
2015 <description>&lt;p&gt;A few days ago, I wrote about
2016 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
2017 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
2018 was dying during installation because it is unable to cope with
2019 sustained write. My supplier is in contact with
2020 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
2021 replacement disk to try to fix the problem. They decided to send an
2022 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
2023
2024 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
2025 Debian Edu Wheezy with encrypted disk on it. The new disk have the
2026 same firmware version as the original. This time my hope raised
2027 slightly as the installation progressed, as the original disk used to
2028 die after 4-7% of the disk was written to, while this time it kept
2029 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
2030 died again and I was back on square one. I still do not have a new
2031 laptop with a disk I can trust. I can not live with a disk that might
2032 lock up when I download a new
2033 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
2034 other large files. I look forward to hearing from my supplier with
2035 the next proposal from Lenovo.&lt;/p&gt;
2036
2037 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
2038 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
2039 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2040 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
2041 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2042 P/N 45N8295, P0C38732.&lt;/p&gt;
2043
2044 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
2045 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
2046 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
2047 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
2048 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
2049 P/N 45N8295, P0C38732.&lt;/p&gt;
2050
2051 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
2052 SA, date and WNPP values. Mentioning all the details here in case
2053 someone is able to use the information to find a way to identify the
2054 failing disk among working ones (if any such working disk actually
2055 exist).&lt;/p&gt;
2056 </description>
2057 </item>
2058
2059 <item>
2060 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
2061 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2062 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2063 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2064 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2065 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2066 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2067 member assosiation NUUG&lt;/a&gt; and
2068 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2069 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2070 Bitraf&lt;/a&gt;.&lt;/p&gt;
2071
2072 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2073 welcome, and there is no fee to participate. There is on the other
2074 hand limited space, and only room for 30 people. Please put your name
2075 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2076 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2077 </description>
2078 </item>
2079
2080 <item>
2081 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2082 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2083 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2084 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2085 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2086 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2087 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2088 time to spend on it, and it took a while to find a model I believe
2089 will do the job, but two days ago the replacement finally arrived. I
2090 ended up picking a
2091 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2092 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2093 a roaming workstation, and it seemed to work flawlessly. But my
2094 second installation with encrypted disk was not as successful. More
2095 on that below.&lt;/p&gt;
2096
2097 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2098 important requirements (robust and with a good keyboard) are never
2099 listed in the feature list. But I did get good help from the search
2100 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2101 allowed me to limit the list of interesting laptops based on my other
2102 requirements. A bit surprising that SSD disk are not disks according
2103 to that search interface, so I had to drop specifying the number of
2104 disks from my search parameters. I also asked around among friends to
2105 get their impression on keyboards and robustness.&lt;/p&gt;
2106
2107 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2108 X41. I am not quite convinced about the keyboard, as it is
2109 significantly wider than my old keyboard, and I have to stretch my
2110 hand a lot more to reach the edges. But the key response is fairly
2111 good and the individual key shape is fairly easy to handle, so I hope
2112 I will get used to it. My old X40 was starting to fail, and I really
2113 needed a new laptop now. :)&lt;/p&gt;
2114
2115 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2116 visit to the BIOS during boot it disable it.&lt;/p&gt;
2117
2118 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2119 lock up during load. And this happen when installing Debian Wheezy
2120 with encrypted disk, while the disk is being filled with random data.
2121 I also tested to install Ubuntu Raring, and it happen there too if I
2122 reenable the code to fill the disk with random data (it is disabled by
2123 default in Ubuntu). And the bug with is already known. It was
2124 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2125 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2126 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2127 kernel developers as
2128 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2129 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2130 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2131 Lenovo forums, both for
2132 &lt;a href=&quot;http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-520-180GB-issue/m-p/1070549&quot;&gt;T430
2133 2012-11-10&lt;/a&gt; and for
2134 &lt;a href=&quot;http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/x230-SATA-errors-with-180GB-Intel-520-SSD-under-heavy-write-load/m-p/1068147&quot;&gt;X230
2135 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2136 reports state that the disk lock up during use if many writes are done
2137 on the disk, so it is much no use to work around the installation
2138 problem and end up with a computer that can lock up at any moment.
2139 There is even a
2140 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2141 available&lt;/a&gt; that will lock up the hard drive after running a few
2142 minutes by writing to a file.&lt;/p&gt;
2143
2144 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2145 contacting PCHELP Norway (request 01D1FDP) which handle support
2146 requests for Lenovo, his first suggestion was to upgrade the disk
2147 firmware. Unfortunately there is no newer firmware available from
2148 Lenovo, as my disk already have the most recent one (version LF1i). I
2149 hope to hear more from him today and hope the problem can be
2150 fixed. :)&lt;/p&gt;
2151 </description>
2152 </item>
2153
2154 <item>
2155 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2156 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2157 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2158 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2159 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2160 trusty old Thinkpad X41. Unfortunately I did not have much time to
2161 spend on it, but today the replacement finally arrived. I ended up
2162 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2163 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2164 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2165 this, it is installing what I hope will be a more final installation,
2166 with a encrypted hard drive to ensure any dope head stealing it end up
2167 with an expencive door stop.&lt;/p&gt;
2168
2169 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2170 important requirements (robust and with a good keyboard) are never
2171 listed in the feature list. But I did get good help from the search
2172 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2173 allowed me to limit the list of interesting laptops based on my other
2174 requirements. A bit surprising that SSD disk are not disks, so I had
2175 to drop number of disks from my search parameters.&lt;/p&gt;
2176
2177 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2178 wider than my old keyboard, and I have to stretch my hand a lot more
2179 to reach the edges. But the key response is fairly good and the
2180 individual key shape is fairly easy to handle, so I hope I will get
2181 used to it. My old X40 was starting to fail, and I really needed a
2182 new laptop now. :)&lt;/p&gt;
2183
2184 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2185 </description>
2186 </item>
2187
2188 <item>
2189 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2190 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2191 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2192 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2193 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2194 perfectly capable of, and I have to do it manually to get things
2195 working. One such task is to find out what firmware packages are
2196 needed to get the hardware on my computer working. Most often this
2197 affect the wifi card, but some times it even affect the RAID
2198 controller or the ethernet card. Today I pushed version 0.4 of the
2199 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2200 including a new script isenkram-autoinstall-firmware handling the
2201 process of asking all the loaded kernel modules what firmware files
2202 they want, find debian packages providing these files and install the
2203 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2204
2205 &lt;p&gt;&lt;pre&gt;
2206 # isenkram-autoinstall-firmware
2207 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2208 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2209 info: locating packages with the requested firmware files
2210 info: Updating APT sources after adding non-free APT source
2211 info: trying to install firmware-ipw2x00
2212 firmware-ipw2x00
2213 firmware-ipw2x00
2214 Preconfiguring packages ...
2215 Selecting previously deselected package firmware-ipw2x00.
2216 (Reading database ... 259727 files and directories currently installed.)
2217 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2218 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2219 #
2220 &lt;/pre&gt;&lt;/p&gt;
2221
2222 &lt;p&gt;When all the requested firmware is present, a simple message is
2223 printed instead:&lt;/p&gt;
2224
2225 &lt;p&gt;&lt;pre&gt;
2226 # isenkram-autoinstall-firmware
2227 info: did not find any firmware files requested by loaded kernel modules. exiting
2228 #
2229 &lt;/pre&gt;&lt;/p&gt;
2230
2231 &lt;p&gt;It could use some polish, but it is already working well and saving
2232 me some time when setting up new machines. :)&lt;/p&gt;
2233
2234 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2235 kernel modules, and look up each one of them using modinfo, to find
2236 the firmware files listed in the module meta-information. Next, it
2237 download the Contents file from a nearby APT mirror, and search for
2238 the firmware files in this file to locate the package with the
2239 requested firmware file. If the package is in the non-free section, a
2240 non-free APT source is added and the package is installed using
2241 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2242 machine.&lt;/p&gt;
2243
2244 &lt;p&gt;I hope someone find time to implement a more polished version of
2245 this script as part of the hw-detect debian-installer module, to
2246 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2247 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2248 firmware during a PXE install when the packages already are available
2249 from the nearby Debian mirror.&lt;/p&gt;
2250 </description>
2251 </item>
2252
2253 <item>
2254 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2255 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2256 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2257 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2258 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2259 the screen just turn black when Linux boot, either during installation
2260 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2261 last few years, but only recently understood the cause. I&#39;ve seen it
2262 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2263 The reason seem to be in the wiring of some laptops. The system to
2264 control the screen background light is inverted, so when Linux try to
2265 turn the brightness fully on, it end up turning it off instead. I do
2266 not know which Linux drivers are affected, but this post is about the
2267 i915 driver used by the
2268 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2269 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2270
2271 &lt;p&gt;The problem can be worked around two ways. Either by adding
2272 i915.invert_brightness=1 as a kernel option, or by adding a file in
2273 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2274 option when it load the i915 kernel module. On Debian and Ubuntu, it
2275 can be done by running these commands as root:&lt;/p&gt;
2276
2277 &lt;pre&gt;
2278 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2279 update-initramfs -u -k all
2280 &lt;/pre&gt;
2281
2282 &lt;p&gt;Since March 2012 there is
2283 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2284 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2285 hardware have this problem, and get the driver to invert the
2286 brightness setting automatically. To use it, one need to add a row in
2287 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c&quot;&gt;the
2288 intel_quirks array&lt;/a&gt; in the driver source
2289 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2290 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2291 number (vendor number 8086 is assumed) and subdevice vendor and device
2292 number.&lt;/p&gt;
2293
2294 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2295 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2296
2297 &lt;p&gt;&lt;pre&gt;
2298 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2299 3rd Gen Core processor Graphics Controller [8086:0156] \
2300 (rev 09) (prog-if 00 [VGA controller])
2301 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2302 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2303 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2304 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2305 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2306 Latency: 0
2307 Interrupt: pin A routed to IRQ 42
2308 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2309 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2310 Region 4: I/O ports at 4000 [size=64]
2311 Expansion ROM at &lt;unassigned&gt; [disabled]
2312 Capabilities: &lt;access denied&gt;
2313 Kernel driver in use: i915
2314 &lt;/pre&gt;&lt;/p&gt;
2315
2316 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2317
2318 &lt;p&gt;&lt;pre&gt;
2319 struct intel_quirk intel_quirks[] = {
2320 ...
2321 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2322 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2323 ...
2324 }
2325 &lt;/pre&gt;&lt;/p&gt;
2326
2327 &lt;p&gt;According to the kernel module instructions (as seen using
2328 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2329 invert_brightness flag should be sent to the
2330 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2331 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2332 developers. But my email about the laptop sent 2013-06-03 have not
2333 yet shown up in
2334 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2335 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2336 emails from non-subscribers. Because of this, I sent my patch also to
2337 the Debian bug tracking system instead as
2338 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2339 sure the patch is not lost.&lt;/p&gt;
2340
2341 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2342 with this problem working properly with Linux. If you use Gnome, your
2343 worries should be over at this point. But if you use KDE, there is
2344 something in KDE ignoring the invert_brightness setting and turning on
2345 the screen during login. I&#39;ve reported it to Debian as
2346 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2347 have no idea yet how to figure out exactly what subsystem is doing
2348 this. Perhaps you can help? Perhaps you know what the Gnome
2349 developers did to handle this, and this can give a clue to the KDE
2350 developers? Or you know where in KDE the screen brightness is changed
2351 during login? If so, please update the BTS report (or get in touch if
2352 you do not know how to update BTS).&lt;/p&gt;
2353
2354 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2355 acpi_backlight=vendor, to disable ACPI backlight support completely,
2356 as the ACPI information on the machine is trash and it is better to
2357 leave it to the intel video driver to control the screen
2358 backlight.&lt;/p&gt;
2359 </description>
2360 </item>
2361
2362 <item>
2363 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2364 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2365 <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>
2366 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2367 <description>&lt;p&gt;Two days ago, I asked
2368 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html&quot;&gt;how
2369 I could install Linux on a Packard Bell EasyNote LV computer
2370 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2371 with the obstacles put in the way of Linux users on a laptop with UEFI
2372 and Windows 8.&lt;/p&gt;
2373
2374 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2375 secure booting or fast boot. I suspect fast boot was the problem,
2376 causing the firmware to boot directly from HD without considering any
2377 key presses and alternative devices, but do not know UEFI settings
2378 enough to tell.&lt;/p&gt;
2379
2380 &lt;p&gt;There is no way to install Linux on the machine in question without
2381 opening the box and disconnecting the hard drive! This is as far as I
2382 can tell, the only way to get access to the firmware setup menu
2383 without accepting the Windows 8 license agreement. I am told (and
2384 found description on how to) that it is possible to configure the
2385 firmware setup once booted into Windows 8. But as I believe the terms
2386 of that agreement are completely unacceptable, accepting the license
2387 was never an alternative. I do not enter agreements I do not intend
2388 to follow.&lt;/p&gt;
2389
2390 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2391 waste many hours on this, but luckily there was a way to get it to
2392 work. But I would not recommend it to anyone planning to run Linux on
2393 it, and I have become sceptical to Windows 8 certified laptops. Is
2394 this the way Linux will be forced out of the market place, by making
2395 it close to impossible for &quot;normal&quot; users to install Linux without
2396 accepting the Microsoft Windows license terms? Or at least not
2397 without risking to loose the warranty?&lt;/p&gt;
2398
2399 &lt;p&gt;I&#39;ve updated the
2400 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2401 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2402 do not have to struggle as much as I did to get Linux into the
2403 machine.&lt;/p&gt;
2404
2405 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2406 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2407 </description>
2408 </item>
2409
2410 <item>
2411 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2412 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2413 <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>
2414 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
2415 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
2416 new laptops for my parents and a few others. I bought Packard Bell
2417 Easynote LV to run Kubuntu on and use as their home computer. But I
2418 am completely unable to figure out how to install Linux on it. The
2419 computer is preinstalled with Windows 8, and I suspect it uses UEFI
2420 instead of a BIOS to boot.&lt;/p&gt;
2421
2422 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
2423 to get it to boot the Linux installer from my USB stick. I have yet
2424 to try the DVD install, and still hope it will work. when I turn on
2425 the computer, there is no information on what buttons to press to get
2426 the normal boot menu. I expect to get some boot menu to select PXE or
2427 USB stick booting. When booting, it first ask for the language to
2428 use, then for some regional settings, and finally if I will accept the
2429 Windows 8 terms of use. As these terms are completely unacceptable to
2430 me, I have no other choice but to turn off the computer and try again
2431 to get it to boot the Linux installer.&lt;/p&gt;
2432
2433 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
2434 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2435 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
2436 installed on this machine, please get in touch or update that wiki
2437 page. If I can&#39;t find a way to install Linux, I will have to return
2438 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
2439
2440 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
2441 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
2442 on new Laptops?&lt;/p&gt;
2443 </description>
2444 </item>
2445
2446 <item>
2447 <title>How to transform a Debian based system to a Debian Edu installation</title>
2448 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
2449 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
2450 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
2451 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
2452 an operating system based on Debian intended for use in schools. It
2453 contain a turn-key solution for the computer network provided to
2454 pupils in the primary schools. It provide both the central server,
2455 network boot servers and desktop environments with heaps of
2456 educational software. The project was founded almost 12 years ago,
2457 2001-07-02. If you want to support the project, which is in need for
2458 cash to fund developer gatherings and other project related activity,
2459 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
2460 donate some money&lt;/a&gt;.
2461
2462 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
2463 lists and elsewhere, is the question on how to transform a Debian or
2464 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
2465 hard, and last week I wrote a script to replicate the steps done by
2466 the Debian Edu installer.&lt;/p&gt;
2467
2468 &lt;p&gt;The script,
2469 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/branches/wheezy/debian-edu-config/share/debian-edu-config/tools/debian-edu-bless?view=markup&quot;&gt;debian-edu-bless&lt;a/&gt;
2470 in the debian-edu-config package, will go through these six steps and
2471 transform an existing Debian Wheezy or Ubuntu (untested) installation
2472 into a Debian Edu Workstation:&lt;/p&gt;
2473
2474 &lt;ol&gt;
2475
2476 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
2477 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
2478 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
2479 our configuration.&lt;/li&gt;
2480 &lt;li&gt;Preseed debconf database with profile setup in
2481 /etc/debian-edu/config, and run tasksel to install packages
2482 according to the profile specified in the config above,
2483 overriding some of the Debian automation machinery.&lt;/li&gt;
2484 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
2485 that could not be done using preseeding.&lt;/li&gt;
2486 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
2487
2488 &lt;/ol&gt;
2489
2490 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
2491 replicated like this. Disk partitioning and LVM setup, for example.
2492 So this script just assume there is enough disk space to install all
2493 the needed packages.&lt;/p&gt;
2494
2495 &lt;p&gt;The script was created to help a Debian Edu student working on
2496 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
2497 Debian Edu client, and using it he can take the existing
2498 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
2499 transform it into a fully functioning Debian Edu Workstation (or
2500 Roaming Workstation, or whatever :).&lt;/p&gt;
2501
2502 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
2503 If a LXDE based Roaming workstation is wanted instead, modify the
2504 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
2505
2506 &lt;p&gt;&lt;pre&gt;
2507 PROFILE=&quot;Roaming-Workstation&quot;
2508 DESKTOP=&quot;lxde&quot;
2509 &lt;/pre&gt;&lt;/p&gt;
2510
2511 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
2512 the cloud, by starting with a virtual Debian installation at some
2513 virtual hosting service and setting up all the services on first
2514 boot.&lt;/p&gt;
2515 </description>
2516 </item>
2517
2518 <item>
2519 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
2520 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
2521 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
2522 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
2523 <description>&lt;P&gt;In January,
2524 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
2525 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
2526 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
2527 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
2528 marvellous construction system from Denmark. We also created
2529 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
2530 a place to take notes and write down our plans and hopes. And several
2531 people showed up to help. I was very happy to see the effect of my
2532 call. Since the small start, we have a debtags tag
2533 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
2534 tag for LEGO related packages, and now count 10 packages related to
2535 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
2536
2537 &lt;p&gt;&lt;table&gt;
2538 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/brickos&quot;&gt;brickos&lt;/a&gt;&lt;/td&gt;&lt;td&gt;alternative OS for LEGO Mindstorms RCX. Supports development in C/C++&lt;/td&gt;&lt;/tr&gt;
2539 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/leocad&quot;&gt;leocad&lt;/a&gt;&lt;/td&gt;&lt;td&gt;virtual brick CAD software&lt;/td&gt;&lt;/tr&gt;
2540 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/libnxt&quot;&gt;libnxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;utility library for talking to the LEGO Mindstorms NX&lt;/td&gt;&lt;/tr&gt;
2541 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/lnpd&quot;&gt;lnpd&lt;/a&gt;&lt;/td&gt;&lt;td&gt;daemon for LNP communication with BrickOS&lt;/td&gt;&lt;/tr&gt;
2542 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nbc&quot;&gt;nbc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;compiler for LEGO Mindstorms NXT bricks&lt;/td&gt;&lt;/tr&gt;
2543 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/nqc&quot;&gt;nqc&lt;/a&gt;&lt;/td&gt;&lt;td&gt;Not Quite C compiler for LEGO Mindstorms RCX&lt;/td&gt;&lt;/tr&gt;
2544 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt&quot;&gt;python-nxt&lt;/a&gt;&lt;/td&gt;&lt;td&gt;python driver/interface/wrapper for the Lego Mindstorms NXT robot&lt;/td&gt;&lt;/tr&gt;
2545 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/python-nxt-filer&quot;&gt;python-nxt-filer&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple GUI to manage files on a LEGO Mindstorms NXT&lt;/td&gt;&lt;/tr&gt;
2546 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/scratch&quot;&gt;scratch&lt;/a&gt;&lt;/td&gt;&lt;td&gt;easy to use programming environment for ages 8 and up&lt;/td&gt;&lt;/tr&gt;
2547 &lt;tr&gt;&lt;td&gt;&lt;a href=&quot;http://packages.qa.debian.org/t2n&quot;&gt;t2n&lt;/a&gt;&lt;/td&gt;&lt;td&gt;simple command-line tool for Lego NXT&lt;/td&gt;&lt;/tr&gt;
2548 &lt;/table&gt;&lt;/p&gt;
2549
2550 &lt;p&gt;Some of these are available in Wheezy, and all but one are
2551 currently available in Jessie/testing. leocad is so far only
2552 available in experimental.&lt;/p&gt;
2553
2554 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
2555 adding the rest of the great free software tools available on Linux
2556 for LEGO designers.&lt;/p&gt;
2557 </description>
2558 </item>
2559
2560 <item>
2561 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
2562 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
2563 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
2564 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
2565 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
2566 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
2567 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
2568 Debian release, and I expect to move my machines at home over to it fairly
2569 soon.&lt;/p&gt;
2570
2571 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
2572 in particular make me very happy to see included. The
2573 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
2574 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
2575 included for the first time. Alongside similar programs like
2576 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
2577 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
2578 it allow for visual programming where syntax errors can not happen,
2579 and a friendly programming environment for learning to control the
2580 computer. Scratch will also be included in the next release of Debian
2581 Edu.&lt;/a&gt;
2582
2583 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
2584 Edu/Skolelinux release too. The
2585 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
2586 alpha release&lt;/a&gt; went out last week, and the next should soon
2587 follow.&lt;p&gt;
2588 </description>
2589 </item>
2590
2591 <item>
2592 <title>Isenkram 0.2 finally in the Debian archive</title>
2593 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
2594 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
2595 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
2596 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
2597 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
2598 for many months. I uploaded it to the Debian experimental suite
2599 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
2600
2601 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
2602 install to work with a pluggable hardware device. The suggestion pop
2603 up when the device is plugged in. For example if a Lego Mindstorm NXT
2604 is inserted, it will suggest to install the program needed to program
2605 the NXT controller. Give it a go, and report bugs and suggestions to
2606 BTS. :)&lt;/p&gt;
2607 </description>
2608 </item>
2609
2610 <item>
2611 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
2612 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
2613 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
2614 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
2615 <description>&lt;p&gt;My
2616 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html&quot;&gt;last
2617 bitcoin related blog post&lt;/a&gt; mentioned that the new
2618 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
2619 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2620 2013-01-19, and have been available in unstable since then. It was
2621 automatically copied to Ubuntu, and is available in their Raring
2622 version too.&lt;/p&gt;
2623
2624 &lt;p&gt;But there is a strange problem with the build that block this new
2625 version from being available on the i386 and kfreebsd-i386
2626 architectures. For some strange reason, the autobuilders in Debian
2627 for these architectures fail to run the test suite on these
2628 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
2629 We are so far unable to reproduce it when building it manually, and
2630 no-one have been able to propose a fix. If you got an idea what is
2631 failing, please let us know via the BTS.&lt;/p&gt;
2632
2633 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
2634 I often run low on disk space, is the fact that the client will exit
2635 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
2636 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
2637 it. :)&lt;/p&gt;
2638
2639 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
2640 activities, please send Bitcoin donations to my address
2641 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2642 </description>
2643 </item>
2644
2645 <item>
2646 <title>Welcome to the world, Isenkram!</title>
2647 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
2648 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
2649 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
2650 <description>&lt;p&gt;Yesterday, I
2651 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
2652 for testers&lt;/a&gt; for my prototype for making Debian better at handling
2653 pluggable hardware devices, which I
2654 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
2655 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
2656 up, and caused me to really want to to open up the development to more
2657 people. But before I did this, I want to come up with a sensible name
2658 for this project. Today I finally decided on a new name, and I have
2659 renamed the project from hw-support-handler to this new name. In the
2660 process, I moved the source to git and made it available as a
2661 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
2662 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
2663 To fetch and build the latest version of the source, use&lt;/p&gt;
2664
2665 &lt;pre&gt;
2666 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2667 cd isenkram &amp;&amp; git-buildpackage -us -uc
2668 &lt;/pre&gt;
2669
2670 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
2671 want to hack on the source or improve the package, please go ahead.
2672 But please talk to me first on IRC or via email before you do major
2673 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
2674
2675 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
2676 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2677 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
2678 the German word eisenkram, for those that are familiar with that
2679 word.&lt;/p&gt;
2680
2681 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
2682 instructions, to avoid confusing people with an error from the signing
2683 process.&lt;/p&gt;
2684
2685 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
2686 clone argument to avoid the need for authentication.&lt;/p&gt;
2687 </description>
2688 </item>
2689
2690 <item>
2691 <title>First prototype ready making hardware easier to use in Debian</title>
2692 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
2693 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
2694 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
2695 <description>&lt;p&gt;Early this month I set out to try to
2696 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
2697 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
2698 prototype is working, and it is ready for a larger audience. To test
2699 it, fetch the
2700 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
2701 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
2702 package. You might have to log out and in again activate the
2703 autostart script.&lt;/p&gt;
2704
2705 &lt;p&gt;The design is simple:&lt;/p&gt;
2706
2707 &lt;ul&gt;
2708
2709 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
2710 hw-support-handlerd to start when the user log in.&lt;/li&gt;
2711
2712 &lt;li&gt;This program listen for kernel events about new hardware (directly
2713 from the kernel like udev does), not using HAL dbus events as I
2714 initially did.&lt;/li&gt;
2715
2716 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
2717 the APT database, a database
2718 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
2719 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
2720
2721 &lt;li&gt;If a package is mapped to the hardware in question, the package
2722 isn&#39;t installed yet and this is the first time the hardware was
2723 plugged in, show a desktop notification suggesting to install the
2724 package or packages.&lt;/li&gt;
2725
2726 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
2727 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
2728
2729 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
2730 package while showing progress information in a window.&lt;/li&gt;
2731
2732 &lt;/ul&gt;
2733
2734 &lt;p&gt;I still need to come up with a better name for the system. Here
2735 are some screen shots showing the prototype in action. First the
2736 notification, then the password request, and finally the request to
2737 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
2738
2739 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
2740 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
2741 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
2742 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
2743 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-5-installing-details.png&quot; width=&quot;70%&quot;&gt;&lt;/p&gt;
2744
2745 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
2746 is already useful. The database of hardware to package mappings also
2747 need more work. It is currently compatible with the Ubuntu way of
2748 storing such information in the package control file, but could be
2749 changed to use other formats instead or in addition to the current
2750 method. I&#39;ve dropped the use of discover for this mapping, as the
2751 modalias approach is more flexible and easier to use on Linux as long
2752 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
2753
2754 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
2755 here is the command required to check out and build the source: Use
2756 &#39;&lt;tt&gt;svn checkout
2757 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2758 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
2759 devscripts package.&lt;/p&gt;
2760
2761 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
2762 renamed to Isenkram and the source moved from the Debian Edu
2763 subversion repository to a Debian collab-maint git repository. See
2764 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
2765 instructions&lt;/a&gt; for details.&lt;/p&gt;
2766 </description>
2767 </item>
2768
2769 <item>
2770 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
2771 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
2772 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
2773 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
2774 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
2775 suddenly in bed. With a quiet whimper, it went completely quiet and
2776 black. The power button was no longer able to turn it on. It was a
2777 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2778 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2779 Compaq I had before that. Now I need to find a replacement. To keep
2780 going during Christmas, I moved the one year old SSD disk to my old
2781 X40 where it fitted (only one I had left that could use it), but it is
2782 not a durable solution.
2783
2784 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
2785 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
2786
2787 &lt;ul&gt;
2788
2789 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
2790 than A4).&lt;/li&gt;
2791 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
2792 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
2793 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
2794 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
2795 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
2796 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
2797 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
2798 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
2799 size).&lt;/li&gt;
2800 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
2801 X.org packages.&lt;/li&gt;
2802 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
2803 the time).
2804
2805 &lt;/ul&gt;
2806
2807 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
2808 list. The reason is simply that the specifications on laptops the
2809 last 10-15 years have been sufficient for my needs, and I have to look
2810 at other features to choose my laptop. But are there still made as
2811 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
2812 robust, and Thinkpads seem to be heading in the wrong direction since
2813 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
2814 still be useful.&lt;/p&gt;
2815
2816 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
2817 external keyboard? I&#39;ll have to check the
2818 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
2819 well-supported laptops, or perhaps just buy one preinstalled from one
2820 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
2821 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
2822 </description>
2823 </item>
2824
2825 <item>
2826 <title>How to find a browser plugin supporting a given MIME type</title>
2827 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
2828 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
2829 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
2830 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
2831 install to get support for a given MIME type. Thanks to
2832 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
2833 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
2834 Unfortunately, not very many packages provide the needed meta
2835 information, Anyway, here is a small script to look up all browser
2836 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
2837
2838 &lt;pre&gt;
2839 #!/usr/bin/python
2840 import sys
2841 import apt
2842 def pkgs_handling_mimetype(mimetype):
2843 cache = apt.Cache()
2844 cache.open(None)
2845 thepkgs = []
2846 for pkg in cache:
2847 version = pkg.candidate
2848 if version is None:
2849 version = pkg.installed
2850 if version is None:
2851 continue
2852 record = version.record
2853 if not record.has_key(&#39;Npp-MimeType&#39;):
2854 continue
2855 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
2856 for t in mime_types:
2857 t = t.rstrip().strip()
2858 if t == mimetype:
2859 thepkgs.append(pkg.name)
2860 return thepkgs
2861 mimetype = &quot;audio/ogg&quot;
2862 if 1 &lt; len(sys.argv):
2863 mimetype = sys.argv[1]
2864 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
2865 for pkg in pkgs_handling_mimetype(mimetype):
2866 print &quot; %s&quot; %pkg
2867 &lt;/pre&gt;
2868
2869 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
2870
2871 &lt;pre&gt;
2872 % ./apt-find-browserplug-for-mimetype
2873 Browser plugin packages supporting audio/ogg:
2874 gecko-mediaplayer
2875 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
2876 Browser plugin packages supporting application/x-shockwave-flash:
2877 browser-plugin-gnash
2878 %
2879 &lt;/pre&gt;
2880
2881 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
2882 itself to query for plugins and propose to install the needed
2883 packages. It would be great if Debian supported such feature too. Is
2884 anyone working on adding it?&lt;/p&gt;
2885
2886 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
2887 request for icweasel support for this feature is
2888 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
2889 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
2890 of manpower and wish for a different design is the reason thus feature
2891 is not yet in iceweasel from Debian.&lt;/p&gt;
2892 </description>
2893 </item>
2894
2895 <item>
2896 <title>What is the most supported MIME type in Debian?</title>
2897 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
2898 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
2899 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
2900 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
2901 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
2902 proposal to make it possible for a Desktop application to propose to
2903 the user some package to install to gain support for a given MIME
2904 type, font, library etc. that is currently missing. With such
2905 mechanism in place, it would be possible for the desktop to
2906 automatically propose and install leocad if some LDraw file is
2907 downloaded by the browser.&lt;/p&gt;
2908
2909 &lt;p&gt;To get some idea about the current content of the archive, I decided
2910 to write a simple program to extract all .desktop files from the
2911 Debian archive and look up the claimed MIME support there. The result
2912 can be found on the
2913 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
2914 site&lt;/a&gt;. Using the collected information, it become possible to
2915 answer the question in the title. Here are the 20 most supported MIME
2916 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
2917 The complete list is available from the link above.&lt;/p&gt;
2918
2919 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
2920
2921 &lt;pre&gt;
2922 count MIME type
2923 ----- -----------------------
2924 32 text/plain
2925 30 audio/mpeg
2926 29 image/png
2927 28 image/jpeg
2928 27 application/ogg
2929 26 audio/x-mp3
2930 25 image/tiff
2931 25 image/gif
2932 22 image/bmp
2933 22 audio/x-wav
2934 20 audio/x-flac
2935 19 audio/x-mpegurl
2936 18 video/x-ms-asf
2937 18 audio/x-musepack
2938 18 audio/x-mpeg
2939 18 application/x-ogg
2940 17 video/mpeg
2941 17 audio/x-scpls
2942 17 audio/ogg
2943 16 video/x-ms-wmv
2944 &lt;/pre&gt;
2945
2946 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
2947
2948 &lt;pre&gt;
2949 count MIME type
2950 ----- -----------------------
2951 33 text/plain
2952 32 image/png
2953 32 image/jpeg
2954 29 audio/mpeg
2955 27 image/gif
2956 26 image/tiff
2957 26 application/ogg
2958 25 audio/x-mp3
2959 22 image/bmp
2960 21 audio/x-wav
2961 19 audio/x-mpegurl
2962 19 audio/x-mpeg
2963 18 video/mpeg
2964 18 audio/x-scpls
2965 18 audio/x-flac
2966 18 application/x-ogg
2967 17 video/x-ms-asf
2968 17 text/html
2969 17 audio/x-musepack
2970 16 image/x-xbitmap
2971 &lt;/pre&gt;
2972
2973 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
2974
2975 &lt;pre&gt;
2976 count MIME type
2977 ----- -----------------------
2978 31 text/plain
2979 31 image/png
2980 31 image/jpeg
2981 29 audio/mpeg
2982 28 application/ogg
2983 27 image/gif
2984 26 image/tiff
2985 26 audio/x-mp3
2986 23 audio/x-wav
2987 22 image/bmp
2988 21 audio/x-flac
2989 20 audio/x-mpegurl
2990 19 audio/x-mpeg
2991 18 video/x-ms-asf
2992 18 video/mpeg
2993 18 audio/x-scpls
2994 18 application/x-ogg
2995 17 audio/x-musepack
2996 16 video/x-ms-wmv
2997 16 video/x-msvideo
2998 &lt;/pre&gt;
2999
3000 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
3001 information mentioned in DEP-11. I have not yet had time to look at
3002 it, but hope the PackageKit people in Debian are on top of these
3003 issues.&lt;/p&gt;
3004
3005 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
3006 discovering a typo in my script.&lt;/p&gt;
3007 </description>
3008 </item>
3009
3010 <item>
3011 <title>Using modalias info to find packages handling my hardware</title>
3012 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
3013 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
3014 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
3015 <description>&lt;p&gt;Yesterday, I wrote about the
3016 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
3017 values provided by the Linux kernel&lt;/a&gt; following my hope for
3018 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
3019 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
3020 modalias values attached to package names can be used to map packages
3021 to hardware. This allow the system to look up and suggest relevant
3022 packages when I plug in some new hardware into my machine, and replace
3023 discover and discover-data as the database used to map hardware to
3024 packages.&lt;/p&gt;
3025
3026 &lt;p&gt;I create a modaliases file with entries like the following,
3027 containing package name, kernel module name (if relevant, otherwise
3028 the package name) and globs matching the relevant hardware
3029 modalias.&lt;/p&gt;
3030
3031 &lt;p&gt;&lt;blockquote&gt;
3032 Package: package-name
3033 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
3034 &lt;/blockquote&gt;&lt;/p&gt;
3035
3036 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
3037 for a given modalias value using this file.&lt;/p&gt;
3038
3039 &lt;p&gt;An entry like this would suggest the video and picture application
3040 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
3041
3042 &lt;p&gt;&lt;blockquote&gt;
3043 Package: cheese
3044 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
3045 &lt;/blockquote&gt;&lt;/p&gt;
3046
3047 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
3048 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
3049
3050 &lt;p&gt;&lt;blockquote&gt;
3051 Package: pcmciautils
3052 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
3053 &lt;/blockquote&gt;&lt;/p&gt;
3054
3055 &lt;p&gt;An entry like this would suggest the package colorhug-client when
3056 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
3057
3058 &lt;p&gt;&lt;blockquote&gt;
3059 Package: colorhug-client
3060 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
3061 &lt;/blockquote&gt;&lt;/p&gt;
3062
3063 &lt;p&gt;I believe the format is compatible with the format of the Packages
3064 file in the Debian archive. Ubuntu already uses their Packages file
3065 to store their mappings from packages to hardware.&lt;/p&gt;
3066
3067 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3068 announce the hardware it support in a way my prototype understand.
3069 This allow those publishing packages in an APT source outside the
3070 Debian archive as well as those backporting packages to make sure the
3071 hardware mapping are included in the package meta information. I&#39;ve
3072 tested such header in the pymissile package, and its modalias mapping
3073 is working as it should with my prototype. It even made it to Ubuntu
3074 Raring.&lt;/p&gt;
3075
3076 &lt;p&gt;To test if it was possible to look up supported hardware using only
3077 the shell tools available in the Debian installer, I wrote a shell
3078 implementation of the lookup code. The idea is to create files for
3079 each modalias and let the shell do the matching. Please check out and
3080 try the
3081 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co&quot;&gt;hw-support-lookup&lt;/a&gt;
3082 shell script. It run without any extra dependencies and fetch the
3083 hardware mappings from the Debian archive and the subversion
3084 repository where I currently work on my prototype.&lt;/p&gt;
3085
3086 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3087 install yubikey-personalization:&lt;/p&gt;
3088
3089 &lt;p&gt;&lt;blockquote&gt;
3090 % ./hw-support-lookup
3091 &lt;br&gt;yubikey-personalization
3092 &lt;br&gt;%
3093 &lt;/blockquote&gt;&lt;/p&gt;
3094
3095 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3096 propose to install the pcmciautils package:&lt;/p&gt;
3097
3098 &lt;p&gt;&lt;blockquote&gt;
3099 % ./hw-support-lookup
3100 &lt;br&gt;pcmciautils
3101 &lt;br&gt;%
3102 &lt;/blockquote&gt;&lt;/p&gt;
3103
3104 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3105 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3106 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3107
3108 &lt;p&gt;It could be possible to generate several of the mappings between
3109 packages and hardware. One source would be to look at packages with
3110 kernel modules, ie packages with *.ko files in /lib/modules/, and
3111 extract their modalias information. Another would be to look at
3112 packages with udev rules, ie packages with files in
3113 /lib/udev/rules.d/, and extract their vendor/model information to
3114 generate a modalias matching rule. I have not tested any of these to
3115 see if it work.&lt;/p&gt;
3116
3117 &lt;p&gt;If you want to help implementing a system to let us propose what
3118 packages to install when new hardware is plugged into a Debian
3119 machine, please send me an email or talk to me on
3120 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3121 </description>
3122 </item>
3123
3124 <item>
3125 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3126 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3127 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3128 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3129 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3130 information, to find the packages that support a given piece of
3131 hardware, I refreshed my memory regarding modalias values, and decided
3132 to document the details. Here are my findings so far, also available
3133 in
3134 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3135 Debian Edu subversion repository&lt;/a&gt;:
3136
3137 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3138
3139 &lt;p&gt;This document try to explain what the different types of modalias
3140 values stands for. It is in part based on information from
3141 &amp;lt;URL: &lt;a href=&quot;https://wiki.archlinux.org/index.php/Modalias&quot;&gt;https://wiki.archlinux.org/index.php/Modalias&lt;/a&gt; &amp;gt;,
3142 &amp;lt;URL: &lt;a href=&quot;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&quot;&gt;http://unix.stackexchange.com/questions/26132/how-to-assign-usb-driver-to-device&lt;/a&gt; &amp;gt;,
3143 &amp;lt;URL: &lt;a href=&quot;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&quot;&gt;http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c&lt;/a&gt; &amp;gt; and
3144 &amp;lt;URL: &lt;a href=&quot;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&quot;&gt;http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode&amp;view=markup&lt;/a&gt; &amp;gt;.
3145
3146 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3147 this shell script:&lt;/p&gt;
3148
3149 &lt;pre&gt;
3150 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3151 &lt;/pre&gt;
3152
3153 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3154 using modinfo:&lt;/p&gt;
3155
3156 &lt;pre&gt;
3157 % /sbin/modinfo psmouse | grep alias:
3158 alias: serio:ty05pr*id*ex*
3159 alias: serio:ty01pr*id*ex*
3160 %
3161 &lt;/pre&gt;
3162
3163 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3164
3165 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3166 Bridge memory controller:&lt;/p&gt;
3167
3168 &lt;p&gt;&lt;blockquote&gt;
3169 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3170 &lt;/blockquote&gt;&lt;/p&gt;
3171
3172 &lt;p&gt;This represent these values:&lt;/p&gt;
3173
3174 &lt;pre&gt;
3175 v 00008086 (vendor)
3176 d 00002770 (device)
3177 sv 00001028 (subvendor)
3178 sd 000001AD (subdevice)
3179 bc 06 (bus class)
3180 sc 00 (bus subclass)
3181 i 00 (interface)
3182 &lt;/pre&gt;
3183
3184 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3185 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3186 0600. The 0600 class is a host bridge. Other useful bus values are
3187 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3188
3189 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3190 means.&lt;/p&gt;
3191
3192 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3193
3194 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3195 USB hub in a laptop:&lt;/p&gt;
3196
3197 &lt;p&gt;&lt;blockquote&gt;
3198 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3199 &lt;/blockquote&gt;&lt;/p&gt;
3200
3201 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3202
3203 &lt;pre&gt;
3204 v 1D6B (device vendor)
3205 p 0001 (device product)
3206 d 0206 (bcddevice)
3207 dc 09 (device class)
3208 dsc 00 (device subclass)
3209 dp 00 (device protocol)
3210 ic 09 (interface class)
3211 isc 00 (interface subclass)
3212 ip 00 (interface protocol)
3213 &lt;/pre&gt;
3214
3215 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3216 class is in the interface class section. For a simple USB web camera,
3217 these alias entries show up:&lt;/p&gt;
3218
3219 &lt;p&gt;&lt;blockquote&gt;
3220 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3221 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3222 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3223 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3224 &lt;/blockquote&gt;&lt;/p&gt;
3225
3226 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3227 camera), 0101 is audio control device and 0102 is audio streaming (aka
3228 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3229
3230 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3231
3232 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3233 receiver in a Thinkpad X40:&lt;/p&gt;
3234
3235 &lt;p&gt;&lt;blockquote&gt;
3236 acpi:IBM0071:PNP0511:
3237 &lt;/blockquote&gt;&lt;/p&gt;
3238
3239 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3240
3241 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3242
3243 &lt;p&gt;The DMI table contain lots of information about the computer case
3244 and model. This is an entry for a IBM Thinkpad X40, fetched from
3245 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3246
3247 &lt;p&gt;&lt;blockquote&gt;
3248 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3249 &lt;/blockquote&gt;&lt;/p&gt;
3250
3251 &lt;p&gt;The values present are&lt;/p&gt;
3252
3253 &lt;pre&gt;
3254 bvn IBM (BIOS vendor)
3255 bvr 1UETB6WW(1.66) (BIOS version)
3256 bd 06/15/2005 (BIOS date)
3257 svn IBM (system vendor)
3258 pn 2371H4G (product name)
3259 pvr ThinkPadX40 (product version)
3260 rvn IBM (board vendor)
3261 rn 2371H4G (board name)
3262 rvr NotAvailable (board version)
3263 cvn IBM (chassis vendor)
3264 ct 10 (chassis type)
3265 cvr NotAvailable (chassis version)
3266 &lt;/pre&gt;
3267
3268 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3269 found in the dmidecode source:&lt;/p&gt;
3270
3271 &lt;pre&gt;
3272 3 Desktop
3273 4 Low Profile Desktop
3274 5 Pizza Box
3275 6 Mini Tower
3276 7 Tower
3277 8 Portable
3278 9 Laptop
3279 10 Notebook
3280 11 Hand Held
3281 12 Docking Station
3282 13 All In One
3283 14 Sub Notebook
3284 15 Space-saving
3285 16 Lunch Box
3286 17 Main Server Chassis
3287 18 Expansion Chassis
3288 19 Sub Chassis
3289 20 Bus Expansion Chassis
3290 21 Peripheral Chassis
3291 22 RAID Chassis
3292 23 Rack Mount Chassis
3293 24 Sealed-case PC
3294 25 Multi-system
3295 26 CompactPCI
3296 27 AdvancedTCA
3297 28 Blade
3298 29 Blade Enclosing
3299 &lt;/pre&gt;
3300
3301 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3302 table. For example my home server is a tower, but the DMI modalias
3303 claim it is a desktop.&lt;/p&gt;
3304
3305 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3306
3307 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3308 test machine:&lt;/p&gt;
3309
3310 &lt;p&gt;&lt;blockquote&gt;
3311 serio:ty01pr00id00ex00
3312 &lt;/blockquote&gt;&lt;/p&gt;
3313
3314 &lt;p&gt;The values present are&lt;/p&gt;
3315
3316 &lt;pre&gt;
3317 ty 01 (type)
3318 pr 00 (prototype)
3319 id 00 (id)
3320 ex 00 (extra)
3321 &lt;/pre&gt;
3322
3323 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3324 the valid values are.&lt;/p&gt;
3325
3326 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3327
3328 &lt;p&gt;There are heaps of other modalias subtypes according to
3329 file2alias.c. There is the rest of the list from that source: amba,
3330 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3331 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3332 vmbus, x86cpu and zorro. I did not spend time documenting all of
3333 these, as they do not seem relevant for my intended use with mapping
3334 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3335
3336 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3337
3338 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3339 one can use the following shell script:&lt;/p&gt;
3340
3341 &lt;pre&gt;
3342 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3343 echo &quot;$id&quot; ; \
3344 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3345 done
3346 &lt;/pre&gt;
3347
3348 &lt;p&gt;The output can look like this (only the first few entries as the
3349 list is very long on my test machine):&lt;/p&gt;
3350
3351 &lt;pre&gt;
3352 acpi:ACPI0003:
3353 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3354 acpi:device:
3355 FATAL: Module acpi:device: not found.
3356 acpi:IBM0068:
3357 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3358 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3359 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3360 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3361 acpi:IBM0071:PNP0511:
3362 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3363 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3364 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3365 [...]
3366 &lt;/pre&gt;
3367
3368 &lt;p&gt;If you want to help implementing a system to let us propose what
3369 packages to install when new hardware is plugged into a Debian
3370 machine, please send me an email or talk to me on
3371 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3372
3373 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3374 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3375 in /sys/ with space in them.&lt;/p&gt;
3376 </description>
3377 </item>
3378
3379 <item>
3380 <title>Moved the pymissile Debian packaging to collab-maint</title>
3381 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3382 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3383 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3384 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3385 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3386 Launcher and updated the Debian package
3387 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3388 sure udev will fix the device permissions when it is plugged in. I
3389 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3390 hopefully make the package be proposed by jockey in Ubuntu when a user
3391 plug in his rocket launcher. In the process I moved the source to a
3392 git repository under collab-maint, to make it easier for any DD to
3393 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3394 is not very active, but the software still work for me even after five
3395 years of relative silence. The new git repository is not listed in
3396 the uploaded package yet, because I want to test the other changes a
3397 bit more before I upload the new version. If you want to check out
3398 the new version with a .desktop file included, visit the
3399 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3400 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3401 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3402 </description>
3403 </item>
3404
3405 <item>
3406 <title>Lets make hardware dongles easier to use in Debian</title>
3407 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3408 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3409 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3410 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3411 general, is that there is a great package management system with the
3412 ability to automatically install software packages by downloading them
3413 from the distribution mirrors, but no way to get it to automatically
3414 install the packages I need to use the hardware I plug into my
3415 machine. Even if the package to use it is easily available from the
3416 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3417 suggest to automatically install the python-nxt, nbc and t2n packages
3418 I need to talk to it. When I plug in a Yubikey, it could propose the
3419 yubikey-personalization package. The information required to do this
3420 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
3421
3422 &lt;p&gt;Some years ago, I proposed to
3423 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
3424 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
3425 simple:
3426
3427 &lt;ul&gt;
3428
3429 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
3430 starting when a user log in.&lt;/li&gt;
3431
3432 &lt;li&gt;Set this program up to listen for kernel events emitted when new
3433 hardware is inserted into the computer.&lt;/li&gt;
3434
3435 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
3436 database mapping to packages, and take note of any non-installed
3437 packages.&lt;/li&gt;
3438
3439 &lt;li&gt;Show a message to the user proposing to install the discovered
3440 package, and make it easy to install it.&lt;/li&gt;
3441
3442 &lt;/ul&gt;
3443
3444 &lt;p&gt;I am not sure what the best way to implement this is, but my
3445 initial idea was to use dbus events to discover new hardware, the
3446 discover database to find packages and
3447 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
3448 packages.&lt;/p&gt;
3449
3450 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
3451 draft package is now checked into
3452 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3453 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
3454 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
3455 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3456 the relevant packages in Debian, and uploaded a new version
3457 2.2013.01.09 to unstable. I also discovered that the current
3458 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
3459 package in Debian no longer discovered any USB devices, because
3460 /proc/bus/usb/devices is no longer present. I ported it to use
3461 libusb as a fall back option to get it working. The fixed package
3462 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
3463 because of the freeze).&lt;/p&gt;
3464
3465 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
3466 desktop notification to show up (only once, the first time it is
3467 inserted):&lt;/p&gt;
3468
3469 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-09-hw-autoinstall.png&quot;&gt;&lt;/p&gt;
3470
3471 &lt;p&gt;For this prototype to be really useful, some way to automatically
3472 install the proposed packages by pressing the &quot;Please install
3473 program(s)&quot; button should to be implemented.&lt;/p&gt;
3474
3475 &lt;p&gt;If this idea seem useful to you, and you want to help make it
3476 happen, please help me update the discover-data database with mappings
3477 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
3478 list the package you would like to have installed when a given
3479 hardware device is inserted into your computer, and report bugs using
3480 reportbug if it isn&#39;t. Or, if you know of a better way to provide
3481 such mapping, please let me know.&lt;/p&gt;
3482
3483 &lt;p&gt;This prototype need more work, and there are several questions that
3484 should be considered before it is ready for production use. Is dbus
3485 the correct way to detect new hardware? At the moment I look for HAL
3486 dbus events on the system bus, because that is the events I could see
3487 on my Debian Squeeze KDE desktop. Are there better events to use?
3488 How should the user be notified? Is the desktop notification
3489 mechanism the best option, or should the background daemon raise a
3490 popup instead? How should packages be installed? When should they
3491 not be installed?&lt;/p&gt;
3492
3493 &lt;p&gt;If you want to help getting such feature implemented in Debian,
3494 please send me an email. :)&lt;/p&gt;
3495 </description>
3496 </item>
3497
3498 <item>
3499 <title>New IRC channel for LEGO designers using Debian</title>
3500 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
3501 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
3502 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
3503 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
3504 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
3505 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
3506 discovered I had to build all the tools myself because none were
3507 already in Debian Squeeze. If Debian support for LEGO is something
3508 you care about, please join me on the IRC channel
3509 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
3510 irc.debian.org). There is a lot that could be done to improve the
3511 Debian support for LEGO designers. For example both CAD software
3512 and Mindstorm compilers are missing. :)&lt;/p&gt;
3513
3514 &lt;p&gt;Update 2012-01-03: A
3515 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
3516 including links to Lego related packages is now available.&lt;/p&gt;
3517 </description>
3518 </item>
3519
3520 <item>
3521 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
3522 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
3523 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
3524 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
3525 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
3526 year! I hope next year will prove to be a good year.&lt;/p&gt;
3527
3528 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
3529 decentralised &quot;currency&quot; that allow people to transfer bitcoins
3530 between each other with minimal overhead, is a very interesting
3531 experiment. And as I wrote a few days ago, the bitcoin situation in
3532 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
3533 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
3534 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
3535 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
3536 for one of the ftpmasters to approve the new bitcoin-qt package
3537 name.&lt;/p&gt;
3538
3539 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
3540 team in Debian, you can easily test the package in Debian Squeeze
3541 using the following steps to get a set of working packages:&lt;/p&gt;
3542
3543 &lt;blockquote&gt;&lt;pre&gt;
3544 git clone git://git.debian.org/git/collab-maint/bitcoin
3545 cd bitcoin
3546 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3547 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3548 &lt;/pre&gt;&lt;/blockquote&gt;
3549
3550 &lt;p&gt;You might have to install some build dependencies as well. The
3551 list of commands should give you two packages, bitcoind and
3552 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3553 client will download the complete set of bitcoin &quot;blocks&quot;, which need
3554 around 5.6 GiB of data on my machine at the moment. Make sure your
3555 ~/.bitcoin/ directory have lots of spare room if you want to download
3556 all the blocks. The client will warn if the disk is getting full, so
3557 there is not really a problem if you got too little room, but you will
3558 not be able to get all the features out of the client.&lt;/p&gt;
3559
3560 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3561 activities, please send Bitcoin donations to my address
3562 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3563 </description>
3564 </item>
3565
3566 <item>
3567 <title>A word on bitcoin support in Debian</title>
3568 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
3569 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
3570 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
3571 <description>&lt;p&gt;It has been a while since I wrote about
3572 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
3573 peer-to-peer based crypto-currency, and the reason is simply that I
3574 have been busy elsewhere. But two days ago, I started looking at the
3575 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
3576 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
3577 is now maintained by a
3578 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
3579 people&lt;/a&gt;, and the grunt work had already been done by this team. We
3580 owe a huge thank you to all these team members. :)
3581 But I was sad to discover that the bitcoin client is missing in
3582 Wheezy. It is only available in Sid (and an outdated client from
3583 backports). The client had several RC bugs registered in BTS blocking
3584 it from entering testing. To try to help the team and improve the
3585 situation, I spent some time providing patches and triaging the bug
3586 reports. I also had a look at the bitcoin package available from Matt
3587 Corallo in a
3588 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
3589 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
3590 Debian package.&lt;/p&gt;
3591
3592 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
3593 IRC, I pushed several patches into the collab-maint git repository to
3594 improve the package. It now contains fixes for the RC issues (not from
3595 me, but fixed by Scott Howard), build rules for a Qt GUI client
3596 package, konqueror support for the bitcoin: URI and bash completion
3597 setup. As I work on Debian Squeeze, I also created
3598 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
3599 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
3600 it and try to integrate it into the git repository before uploading a
3601 new version to unstable.
3602
3603 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
3604 centralized control currently exercised in the monetary system. I
3605 find it completely unacceptable that the USA government is collecting
3606 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3607 that the major credit card companies can block legal money
3608 transactions to Wikileaks. But for bitcoin to succeed, more people
3609 need to use bitcoins, and more people need to accept bitcoins when
3610 they sell products and services. Improving the bitcoin support in
3611 Debian is a small step in the right direction, but not enough.
3612 Unfortunately the user experience when browsing the web and wanting to
3613 pay with bitcoin is still not very good. The bitcoin: URI is a step
3614 in the right direction, but need to work in most or every browser in
3615 use. Also the bitcoin-qt client is too heavy to fire up to do a
3616 quick transaction. I believe there are other clients available, but
3617 have not tested them.&lt;/p&gt;
3618
3619 &lt;p&gt;My
3620 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
3621 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
3622 I received 20.15 BTC so far on the address I provided in my blog two
3623 years ago, as can be
3624 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
3625 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
3626 donation. The blockexplorer service demonstrates quite well that
3627 bitcoin is not quite anonymous and untracked. :) I wonder if the
3628 number of users have gone up since then. If you use bitcoin and want
3629 to show your support of my activity, please send Bitcoin donations to
3630 the same address as last time,
3631 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3632 </description>
3633 </item>
3634
3635 <item>
3636 <title>Git repository for song book for Computer Scientists</title>
3637 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
3638 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
3639 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
3640 <description>&lt;p&gt;As I
3641 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
3642 this summer&lt;/a&gt;, I have created a Computer Science song book a few
3643 years ago, and today I finally found time to create a public
3644 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
3645 repository for the project&lt;/a&gt;.&lt;/p&gt;
3646
3647 &lt;p&gt;If you want to help out, please clone the source and submit patches
3648 to the HTML version. To generate the PDF and PostScript version,
3649 please use prince XML, or let me know about a useful free software
3650 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
3651
3652 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
3653 PostScript formats at
3654 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
3655 Science Songbook&lt;/a&gt;.&lt;/p&gt;
3656 </description>
3657 </item>
3658
3659 <item>
3660 <title>Gratulerer med 19-årsdagen, Debian!</title>
3661 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
3662 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
3663 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
3664 <description>&lt;p&gt;I dag fyller
3665 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
3666 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
3667 si gratulerer med dagen, Debian!&lt;/p&gt;
3668 </description>
3669 </item>
3670
3671 <item>
3672 <title>Song book for Computer Scientists</title>
3673 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
3674 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
3675 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
3676 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
3677 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
3678 collecting computer related songs for use at parties. The original
3679 version was written in LaTeX, but a few years ago I got help from
3680 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3681 while keeping the ability to create a nice book in PDF format. I have
3682 not had time to maintain the book for a while now, and guess I should
3683 put it up on some public version control repository where others can
3684 help me extend and update the book. If anyone is volunteering to help
3685 me with this, send me an email. Also let me know if there are songs
3686 missing in my book.&lt;/p&gt;
3687
3688 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
3689 me today that I really should let all my readers share the joys of
3690 singing out load about programming, computers and computer networks.
3691 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
3692 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
3693 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
3694 Computer Science Songbook&lt;/a&gt;.
3695 </description>
3696 </item>
3697
3698 <item>
3699 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
3700 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
3701 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
3702 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
3703 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
3704 around 1000 at the moment. To be able to get help from the vendors
3705 when something go wrong, we want to keep the firmware on the servers
3706 up to date. If the firmware isn&#39;t the latest and greatest, the
3707 vendors typically refuse to start debugging any problems until the
3708 firmware is upgraded. So before every reboot, we want to upgrade the
3709 firmware, and we would really like everyone handling servers at the
3710 university to do this themselves when they plan to reboot a machine.
3711 For that to happen we at the unix server admin group need to provide
3712 the tools to do so.&lt;/p&gt;
3713
3714 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
3715 fetch and install the latest firmware for the servers we got. Most of
3716 our hardware are from Dell and HP, so I have focused on these servers
3717 so far. This blog post is about the Dell part.&lt;/P&gt;
3718
3719 &lt;p&gt;On the Dell FTP site I was lucky enough to find
3720 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
3721 with firmware information for all 11th generation servers, listing
3722 which firmware should be used on a given model and where on the FTP
3723 site I can find it. Using a simple perl XML parser I can then
3724 download the shell scripts Dell provides to do firmware upgrades from
3725 within Linux and reboot when all the firmware is primed and ready to
3726 be activated on the first reboot.&lt;/p&gt;
3727
3728 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
3729 Are there anyone working on similar tools for firmware upgrading all
3730 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
3731
3732 &lt;p&gt;&lt;pre&gt;
3733 #!/usr/bin/perl
3734 use strict;
3735 use warnings;
3736 use File::Temp qw(tempdir);
3737 BEGIN {
3738 # Install needed RHEL packages if missing
3739 my %rhelmodules = (
3740 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
3741 );
3742 for my $module (keys %rhelmodules) {
3743 eval &quot;use $module;&quot;;
3744 if ($@) {
3745 my $pkg = $rhelmodules{$module};
3746 system(&quot;yum install -y $pkg&quot;);
3747 eval &quot;use $module;&quot;;
3748 }
3749 }
3750 }
3751 my $errorsto = &#39;pere@hungry.com&#39;;
3752
3753 upgrade_dell();
3754
3755 exit 0;
3756
3757 sub run_firmware_script {
3758 my ($opts, $script) = @_;
3759 unless ($script) {
3760 print STDERR &quot;fail: missing script name\n&quot;;
3761 exit 1
3762 }
3763 print STDERR &quot;Running $script\n\n&quot;;
3764
3765 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
3766 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
3767 } else {
3768 print STDERR &quot;fail: firmware script returned error\n&quot;;
3769 }
3770 }
3771
3772 sub run_firmware_scripts {
3773 my ($opts, @dirs) = @_;
3774 # Run firmware packages
3775 for my $dir (@dirs) {
3776 print STDERR &quot;info: Running scripts in $dir\n&quot;;
3777 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
3778 while (my $s = readdir $dh) {
3779 next if $s =~ m/^\.\.?/;
3780 run_firmware_script($opts, &quot;$dir/$s&quot;);
3781 }
3782 closedir $dh;
3783 }
3784 }
3785
3786 sub download {
3787 my $url = shift;
3788 print STDERR &quot;info: Downloading $url\n&quot;;
3789 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
3790 }
3791
3792 sub upgrade_dell {
3793 my @dirs;
3794 my $product = `dmidecode -s system-product-name`;
3795 chomp $product;
3796
3797 if ($product =~ m/PowerEdge/) {
3798
3799 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
3800 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
3801
3802 my $tmpdir = tempdir(
3803 CLEANUP =&gt; 1
3804 );
3805 chdir($tmpdir);
3806 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
3807 system(&#39;gunzip Catalog.xml.gz&#39;);
3808 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
3809 # -q is quiet, disabling interactivity and reducing console output
3810 my $fwopts = &quot;-q&quot;;
3811 if (@paths) {
3812 for my $url (@paths) {
3813 fetch_dell_fw($url);
3814 }
3815 run_firmware_scripts($fwopts, $tmpdir);
3816 } else {
3817 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3818 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3819 }
3820 chdir(&#39;/&#39;);
3821 } else {
3822 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3823 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3824 }
3825 }
3826
3827 sub fetch_dell_fw {
3828 my $path = shift;
3829 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
3830 download($url);
3831 }
3832
3833 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
3834 # firmware packages to download from Dell. Only work for Linux
3835 # machines and 11th generation Dell servers.
3836 sub fetch_dell_fw_list {
3837 my $filename = shift;
3838
3839 my $product = `dmidecode -s system-product-name`;
3840 chomp $product;
3841 my ($mybrand, $mymodel) = split(/\s+/, $product);
3842
3843 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
3844
3845 my $xml = XMLin($filename);
3846 my @paths;
3847 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
3848 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
3849 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
3850 my $oscode;
3851 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
3852 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
3853 } else {
3854 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
3855 }
3856 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
3857 {
3858 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
3859 }
3860 }
3861 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
3862 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
3863
3864 # Drop application packages, only firmware and BIOS
3865 next if &#39;APAC&#39; eq $componenttype;
3866
3867 my $cpath = $component-&gt;{path};
3868 for my $path (@paths) {
3869 if ($cpath =~ m%/$path$%) {
3870 push(@paths, $cpath);
3871 }
3872 }
3873 }
3874 return @paths;
3875 }
3876 &lt;/pre&gt;
3877
3878 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
3879 it could work on other platforms with some tweaking. Anyone know a
3880 index like Catalog.xml is available from HP for HP servers? At the
3881 moment I maintain a similar list manually and it is quickly getting
3882 outdated.&lt;/p&gt;
3883 </description>
3884 </item>
3885
3886 <item>
3887 <title>How is booting into runlevel 1 different from single user boots?</title>
3888 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
3889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
3890 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
3891 <description>&lt;p&gt;Wouter Verhelst have some
3892 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
3893 comments and opinions&lt;/a&gt; on my blog post on
3894 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html&quot;&gt;the
3895 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
3896 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html&quot;&gt;the
3897 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
3898 small piece of his comment now, and though it best to address the
3899 misunderstanding he bring forward:&lt;/p&gt;
3900
3901 &lt;p&gt;&lt;blockquote&gt;
3902 Currently, a system admin has four options: [...] boot to a
3903 single-user system (by adding &#39;single&#39; to the kernel command line;
3904 this runs rcS and rc1 scripts)
3905 &lt;/blockquote&gt;&lt;/p&gt;
3906
3907 &lt;p&gt;This make me believe Wouter believe booting into single user mode
3908 and booting into runlevel 1 is the same. I am not surprised he
3909 believe this, because it would make sense and is a quite sensible
3910 thing to believe. But because the boot in Debian is slightly broken,
3911 runlevel 1 do not work properly and it isn&#39;t the same as single user
3912 mode. I&#39;ll try to explain what is actually happing, but it is a bit
3913 hard to explain.&lt;/p&gt;
3914
3915 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
3916 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
3917 executed in single user mode is sulogin. Single user mode is a boot
3918 state &quot;between&quot; the runlevels, and when booting into single user mode,
3919 only the scripts in /etc/rcS.d/ are executed before the init process
3920 enters the single user state. When switching to runlevel 1, the state
3921 is in fact not ending in runlevel 1, but it passes through runlevel 1
3922 and end up in the single user mode (see /etc/rc1.d/S03single, which
3923 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
3924 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
3925 mode enabled by /etc/rcS.d/ (which is more like the initial boot
3926 mode).&lt;/p&gt;
3927
3928 &lt;p&gt;This summary might make it clearer. When booting for the first
3929 time into single user mode, the following commands are executed:
3930 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
3931 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
3932 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
3933 trying to continue after visiting single user mode. Not all services
3934 are started again as they should, causing the machine to end up in an
3935 unpredicatble state. This is why Debian admins recommend rebooting
3936 after visiting single user mode.&lt;/p&gt;
3937
3938 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
3939 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
3940 to runlevel 1, the services started from /etc/rcS.d/ are not properly
3941 stopped when passing through the scripts in /etc/rc1.d/, and not
3942 started again when switching away from runlevel 1 to the runlevels
3943 2-5. I believe the problem is best fixed by moving all the scripts
3944 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
3945 functioning single user mode during boot.&lt;/p&gt;
3946
3947 &lt;p&gt;I have spent several years investigating the Debian boot system,
3948 and discovered this problem a few years ago. I suspect it originates
3949 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
3950 </description>
3951 </item>
3952
3953 <item>
3954 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
3955 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
3956 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
3957 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
3958 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
3959 are started from /etc/rcS.d/. In fact, there is a bite more of them
3960 than make sense, and this causes a few problems. What kind of
3961 problems, you might ask. There are at least two problems. The first
3962 is that it is not possible to recover a machine after switching to
3963 runlevel 1. One need to actually reboot to get the machine back to
3964 the expected state. The other is that single user boot will sometimes
3965 run into problems because some of the subsystems are activated before
3966 the root login is presented, causing problems when trying to recover a
3967 machine from a problem in that subsystem. A minor additional point is
3968 that moving more scripts out of rcS.d/ and into the other rc#.d/
3969 directories will increase the amount of scripts that can run in
3970 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
3971
3972 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
3973 scripts that _have_ to execute before the root login prompt is
3974 presented during a single user boot should go there. Everything else
3975 should go into the numeric runlevels. This means things like
3976 lm-sensors, fuse and x11-common should not run from rcS.d, but from
3977 the numeric runlevels. Today in Debian, there are around 115 init.d
3978 scripts that are started from rcS.d/, and most of them should be moved
3979 out. Do your package have one of them? Please help us make single
3980 user and runlevel 1 better by moving it.&lt;/p&gt;
3981
3982 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
3983 etc. should still be started from rcS.d/, but there is for example no
3984 need to have the network enabled before the single user login prompt
3985 is presented.&lt;/p&gt;
3986
3987 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
3988 Debian systems working while scripts migrate and during upgrades, the
3989 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
3990 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
3991 and the next ones can only be moved when their dependencies have been
3992 moved first. This migration must be done sequentially while we ensure
3993 that the package system upgrade packages in the right order to keep
3994 the system state correct. This will require some coordination when it
3995 comes to network related packages, but most of the packages with
3996 scripts that should migrate do not have anything in rcS.d/ depending
3997 on them. Some packages have already been updated, like the sudo
3998 package, while others are still left to do. I wish I had time to work
3999 on this myself, but real live constrains make it unlikely that I will
4000 find time to push this forward.&lt;/p&gt;
4001 </description>
4002 </item>
4003
4004 <item>
4005 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
4006 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
4007 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
4008 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
4009 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
4010 mentioned the issues I believe should be improved in Debian for its
4011 desktop to be useful for more people. The use case for this is my
4012 parents, which are currently running Kubuntu which solve the
4013 issues.&lt;/p&gt;
4014
4015 &lt;p&gt;I suspect these four missing features are not very hard to
4016 implement. After all, they are present in Ubuntu, so if we wanted to
4017 do this in Debian we would have a source.&lt;/p&gt;
4018
4019 &lt;ol&gt;
4020
4021 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
4022 are new packages available for upgrades, a icon in the KDE status bar
4023 indicate this, and clicking on it will activate the simple upgrade
4024 tool to handle it. I have no problem guiding both of my parents
4025 through the process over the phone. If a kernel reboot is required,
4026 this too is indicated by the status bars and the upgrade tool. Last
4027 time I checked, nothing with the same features was working in KDE in
4028 Debian.&lt;/li&gt;
4029
4030 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
4031 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
4032 currently have a handler for, it will ask the user if the system
4033 should search for a package that would add support for this MIME type,
4034 and if the user say yes, the APT sources will be searched for packages
4035 advertising the MIME type in their control file (visible in the
4036 Packages file in the APT archive). If one or more packages are found,
4037 it is a simple click of the mouse to add support for the missing mime
4038 type. If the package require the user to accept some non-free
4039 license, this is explained to the user. The entire process make it
4040 more clear to the user why something do not work in the browser, and
4041 make the chances higher for the user to blame the web page authors and
4042 not the browser for any missing features.&lt;/li&gt;
4043
4044 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
4045 handlers.&lt;/strong&gt; When the media players encounter a format or codec
4046 it is not supporting, a dialog pop up asking the user if the system
4047 should search for a package that would add support for it. This
4048 happen with things like MP3, Windows Media or H.264. The selection
4049 and installation procedure is very similar to the Firefox browser
4050 plugin handling. This is as far as I know implemented using a
4051 gstreamer hook. The end result is that the user easily get access to
4052 the codecs that are present from the APT archives available, while
4053 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
4054
4055 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
4056 displaying a text/plain file in my Debian browser, it will propose to
4057 start emacs to show it. If I remember correctly, when doing the same
4058 in Kunbutu it show the file as a text file in the browser. At least I
4059 know Opera will show text files within the browser. I much prefer the
4060 latter behaviour.&lt;/li&gt;
4061
4062 &lt;/ol&gt;
4063
4064 &lt;p&gt;There are other nice features as well, like the simplified suite
4065 upgrader, but given that I am the one mostly doing the dist-upgrade,
4066 it do not matter much.&lt;/p&gt;
4067
4068 &lt;p&gt;I really hope we could get these features in place for the next
4069 Debian release. It would require the coordinated effort of several
4070 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4071 </description>
4072 </item>
4073
4074 <item>
4075 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4076 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4077 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4078 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4079 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4080 site is build on Debian/Squeeze, and this platform was chosen because
4081 I am most familiar with Debian (being a Debian Developer for around 10
4082 years) because it is the latest stable Debian release which should get
4083 security support for a few years.&lt;/p&gt;
4084
4085 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4086 that are missing in Debian at the moment. It would be great if these
4087 modules were added to the Debian archive, allowing anyone to set up
4088 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4089 in their own country using only Debian packages. The list of modules
4090 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4091 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4092 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4093 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4094 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4095 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4096 easier in the future.&lt;/p&gt;
4097
4098 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4099 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4100 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4101 with the responsibility of tracking security problems, which I really
4102 do not have time for.&lt;/p&gt;
4103 </description>
4104 </item>
4105
4106 <item>
4107 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4108 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4110 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4111 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4112 posts have been in Norwegian the last few weeks, so here is a short
4113 update in English.&lt;/p&gt;
4114
4115 &lt;p&gt;The kids still keep me too busy to get much free software work
4116 done, but I did manage to organise a project to get a Norwegian port
4117 of the British service
4118 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4119 and it has been running for a month now. The entire project has been
4120 organised by me and two others. Around Christmas we gathered sponsors
4121 to fund the development work. In January I drafted a contract with
4122 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4123 and in February the development took place. Most of it involved
4124 converting the source to use GPS coordinates instead of British
4125 easting/northing, and the resulting code should be a lot easier to get
4126 running in any country by now. The Norwegian
4127 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4128 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4129 source and the source for administrative borders in Norway, and
4130 support for this had to be added/fixed.&lt;/p&gt;
4131
4132 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4133 polishing the system before we announced it March 7th. The system is
4134 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4135 problem reports in a few weeks. Soon we hope to announce the Android
4136 and iPhone versions making it even easier to report problems with the
4137 public infrastructure.&lt;/p&gt;
4138
4139 &lt;p&gt;Perhaps something to consider for those of you in countries without
4140 such service?&lt;/p&gt;
4141 </description>
4142 </item>
4143
4144 <item>
4145 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4146 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4147 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4148 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4149 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4150 issues here at my work with the University of Oslo. My idea is that
4151 it should be possible to use the information about security issues
4152 available on the Internet, and check our locally
4153 maintained/distributed software against this information. It should
4154 allow us to verify that no known security issues are forgotten. The
4155 CVE database listing vulnerabilities seem like a great central point,
4156 and by using the package lists from Debian mapped to CVEs provided by
4157 the testing security team, I believed it should be possible to figure
4158 out which security holes were present in our free software
4159 collection.&lt;/p&gt;
4160
4161 &lt;p&gt;After reading up on the topic, it became obvious that the first
4162 building block is to be able to name software packages in a unique and
4163 consistent way across data sources. I considered several ways to do
4164 this, for example coming up with my own naming scheme like using URLs
4165 to project home pages or URLs to the Freshmeat entries, or using some
4166 existing naming scheme. And it seem like I am not the first one to
4167 come across this problem, as MITRE already proposed and implemented a
4168 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4169 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4170 software, hardware and other platform components. The CPE ids are
4171 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4172 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4173 issues for any CPE name. With this in place, all I need to do is to
4174 locate the CPE id for the software packages we use at the university.
4175 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4176 NVD entry if a CVE for the package exist).&lt;/p&gt;
4177
4178 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4179 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4180 check out, one could look up
4181 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/search?cpe=cpe%3A%2Fa%3Agnu%3Agzip:1.3.3&quot;&gt;cpe:/a:gnu:gzip:1.3.3
4182 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4183 The most recent one is
4184 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4185 and at the bottom of the NVD page for this vulnerability the complete
4186 list of affected versions is provided.&lt;/p&gt;
4187
4188 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4189 for offline processing of issues. Using this dump, I&#39;ve written a
4190 small script taking a list of CPEs as input and list all CVEs
4191 affecting the packages represented by these CPEs. One give it CPEs
4192 with version numbers as specified above and get a list of open
4193 security issues out.&lt;/p&gt;
4194
4195 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4196 information need to be high. For that to happen, I believe as many as
4197 possible need to use and contribute to the NVD database. I notice
4198 RHEL is providing
4199 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4200 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4201 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4202
4203 &lt;p&gt;To get an idea about the quality for free software, I spent some
4204 time making it possible to compare the CVE database from Debian with
4205 the CVE database in NVD. The result look fairly good, but there are
4206 some inconsistencies in NVD (same software package having several
4207 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4208 Debian believe are affected by a CVE). Hope to find time to improve
4209 the quality of NVD, but that require being able to get in touch with
4210 someone maintaining it. So far my three emails with questions and
4211 corrections have not seen any reply, but I hope contact can be
4212 established soon.&lt;/p&gt;
4213
4214 &lt;p&gt;An interesting application for CPEs is cross platform package
4215 mapping. It would be useful to know which packages in for example
4216 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4217 this would be trivial if all linux distributions provided CPE entries
4218 for their packages.&lt;/p&gt;
4219 </description>
4220 </item>
4221
4222 <item>
4223 <title>Which module is loaded for a given PCI and USB device?</title>
4224 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4225 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4226 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4227 <description>&lt;p&gt;In the
4228 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4229 package in Debian, there is a script to report useful information
4230 about the running hardware for use when people report missing
4231 information. One part of this script that I find very useful when
4232 debugging hardware problems, is the part mapping loaded kernel module
4233 to the PCI device it claims. It allow me to quickly see if the kernel
4234 module I expect is driving the hardware I am struggling with. To see
4235 the output, make sure discover-data is installed and run
4236 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4237 one of my machines like this:&lt;/p&gt;
4238
4239 &lt;pre&gt;
4240 loaded modules:
4241 10de:03eb i2c_nforce2
4242 10de:03f1 ohci_hcd
4243 10de:03f2 ehci_hcd
4244 10de:03f0 snd_hda_intel
4245 10de:03ec pata_amd
4246 10de:03f6 sata_nv
4247 1022:1103 k8temp
4248 109e:036e bttv
4249 109e:0878 snd_bt87x
4250 11ab:4364 sky2
4251 &lt;/pre&gt;
4252
4253 &lt;p&gt;The code in question look like this, slightly modified for
4254 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4255
4256 &lt;pre&gt;
4257 if [ -d /sys/bus/pci/devices/ ] ; then
4258 echo loaded pci modules:
4259 (
4260 cd /sys/bus/pci/devices/
4261 for address in * ; do
4262 if [ -d &quot;$address/driver/module&quot; ] ; then
4263 module=`cd $address/driver/module ; pwd -P | xargs basename`
4264 if grep -q &quot;^$module &quot; /proc/modules ; then
4265 address=$(echo $address |sed s/0000://)
4266 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4267 echo &quot;$id $module&quot;
4268 fi
4269 fi
4270 done
4271 )
4272 echo
4273 fi
4274 &lt;/pre&gt;
4275
4276 &lt;p&gt;Similar code could be used to extract USB device module
4277 mappings:&lt;/p&gt;
4278
4279 &lt;pre&gt;
4280 if [ -d /sys/bus/usb/devices/ ] ; then
4281 echo loaded usb modules:
4282 (
4283 cd /sys/bus/usb/devices/
4284 for address in * ; do
4285 if [ -d &quot;$address/driver/module&quot; ] ; then
4286 module=`cd $address/driver/module ; pwd -P | xargs basename`
4287 if grep -q &quot;^$module &quot; /proc/modules ; then
4288 address=$(echo $address |sed s/0000://)
4289 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4290 if [ &quot;$id&quot; ] ; then
4291 echo &quot;$id $module&quot;
4292 fi
4293 fi
4294 fi
4295 done
4296 )
4297 echo
4298 fi
4299 &lt;/pre&gt;
4300
4301 &lt;p&gt;This might perhaps be something to include in other tools as
4302 well.&lt;/p&gt;
4303 </description>
4304 </item>
4305
4306 <item>
4307 <title>How to test if a laptop is working with Linux</title>
4308 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4309 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4310 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4311 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4312 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4313 batch of computers will work with Linux. Every year for the last few
4314 years the university have organised shared bid of a few thousand
4315 computers, and this year HP won the bid. Two different desktops and
4316 five different laptops are on the list this year. We in the UNIX
4317 group want to know which one of these computers work well with RHEL
4318 and Ubuntu, the two Linux distributions we currently handle at the
4319 university.&lt;/p&gt;
4320
4321 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4322 perhaps inspire others to test hardware as well. To test, I PXE
4323 install the OS version of choice, and log in as my normal user and run
4324 a few applications and plug in selected pieces of hardware. When
4325 something fail, I make a note about this in the test matrix and move
4326 on. If I have some spare time I try to report the bug to the OS
4327 vendor, but as I only have the machines for a short time, I rarely
4328 have the time to do this for all the problems I find.&lt;/p&gt;
4329
4330 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4331 I perform on a new model.&lt;/p&gt;
4332
4333 &lt;ul&gt;
4334
4335 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4336 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4337 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4338
4339 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4340 installation, X.org is working.&lt;/li&gt;
4341
4342 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4343 package mesa-utils on Ubuntu) and writing down the frames per second
4344 reported by the program.&lt;/li&gt;
4345
4346 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4347 logging in, and if I can hear this the test is successful. If there
4348 are several audio exits on the machine, I try them all and check if
4349 the Gnome/KDE audio mixer can control where to send the sound. I
4350 normally test this by playing
4351 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4352 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4353
4354 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4355 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4356
4357 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4358 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4359
4360 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4361 picture from the v4l device show up.&lt;/li&gt;
4362
4363 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4364 any bluetooth devices are discovered. In my office, I normally see a
4365 few.&lt;/li&gt;
4366
4367 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4368 memory modules lying around, and stick them in and see if Gnome/KDE
4369 notice this.&lt;/li&gt;
4370
4371 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4372 special button work, and if the laptop continue to work after
4373 resume.&lt;/li&gt;
4374
4375 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4376 adjusting background light, switching on/off external video output,
4377 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4378 laptop to laptop, so I just write down which are working and which are
4379 not.&lt;/li&gt;
4380
4381 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4382 acceleration sensors etc. I rarely test these, as I do not know how
4383 to quickly test if they are working or not, so I only document their
4384 existence.&lt;/li&gt;
4385
4386 &lt;/ul&gt;
4387
4388 &lt;p&gt;By now I suspect you are really curious what the test results are
4389 for the HP machines I am testing. I&#39;m not done yet, so I will report
4390 the test results later. For now I can report that HP 8100 Elite work
4391 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4392 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4393 can see, I have most machines left to test. One interesting
4394 observation is that Ubuntu Lucid has almost twice the frame rate than
4395 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4396 </description>
4397 </item>
4398
4399 <item>
4400 <title>Some thoughts on BitCoins</title>
4401 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4403 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4404 <description>&lt;p&gt;As I continue to explore
4405 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4406 what properties the system have, and how it will be affected by laws
4407 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4408
4409 &lt;p&gt;One interesting thing to note is that since the transactions are
4410 verified using a peer to peer network, all details about a transaction
4411 is known to everyone. This means that if a BitCoin address has been
4412 published like I did with mine in my initial post about BitCoin, it is
4413 possible for everyone to see how many BitCoins have been transfered to
4414 that address. There is even a web service to look at the details for
4415 all transactions. There I can see that my address
4416 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
4417 have received 16.06 Bitcoin, the
4418 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
4419 address of Simon Phipps have received 181.97 BitCoin and the address
4420 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
4421 of EFF have received 2447.38 BitCoins so far. Thank you to each and
4422 every one of you that donated bitcoins to support my activity. The
4423 fact that anyone can see how much money was transfered to a given
4424 address make it more obvious why the BitCoin community recommend to
4425 generate and hand out a new address for each transaction. I&#39;m told
4426 there is no way to track which addresses belong to a given person or
4427 organisation without the person or organisation revealing it
4428 themselves, as Simon, EFF and I have done.&lt;/p&gt;
4429
4430 &lt;p&gt;In Norway, and in most other countries, there are laws and
4431 regulations limiting how much money one can transfer across the border
4432 without declaring it. There are money laundering, tax and accounting
4433 laws and regulations I would expect to apply to the use of BitCoin.
4434 If the Skolelinux foundation
4435 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
4436 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
4437 normal bank transfers like EFF is doing, how should this be accounted?
4438 Given that it is impossible to know if money can cross the border or
4439 not, should everything or nothing be declared? What exchange rate
4440 should be used when calculating taxes? Would receivers have to pay
4441 income tax if the foundation were to pay Skolelinux contributors in
4442 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
4443
4444 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
4445 accepted by a lot of users. It must be possible to get easy access to
4446 the currency (as a wage or using currency exchanges), and it must be
4447 easy to spend it. At the moment BitCoin seem fairly easy to get
4448 access to, but there are very few places to spend it. I am not really
4449 a regular user of any of the vendor types currently accepting BitCoin,
4450 so I wonder when my kind of shop would start accepting BitCoins. I
4451 would like to buy electronics, travels and subway tickets, not herbs
4452 and books. :) The currency is young, and this will improve over time
4453 if it become popular, but I suspect regular banks will start to lobby
4454 to get BitCoin declared illegal if it become popular. I&#39;m sure they
4455 will claim it is helping fund terrorism and money laundering (which
4456 probably would be true, as is any currency in existence), but I
4457 believe the problems should be solved elsewhere and not by blaming
4458 currencies.&lt;/p&gt;
4459
4460 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
4461 CPU intensive process that depend on a bit of luck as well (as one is
4462 competing against all the other miners currently spending CPU cycles
4463 to see which one get the next lump of cash). The &quot;winner&quot; get 50
4464 BitCoin when this happen. Yesterday I came across the obvious way to
4465 join forces to increase ones changes of getting at least some coins,
4466 by coordinating the work on mining BitCoins across several machines
4467 and people, and sharing the result if one is lucky and get the 50
4468 BitCoins. Check out
4469 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
4470 if this sounds interesting. I have not had time to try to set up a
4471 machine to participate there yet, but have seen that running on ones
4472 own for a few days have not yield any BitCoins througth mining
4473 yet.&lt;/p&gt;
4474
4475 &lt;p&gt;Update 2010-12-15: Found an &lt;a
4476 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
4477 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
4478 it was interesting to read. The arguments presented seem to be
4479 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
4480 </description>
4481 </item>
4482
4483 <item>
4484 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
4485 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
4486 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
4487 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
4488 <description>&lt;p&gt;With this weeks lawless
4489 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
4490 attacks&lt;/a&gt; on Wikileak and
4491 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
4492 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
4493 not be trusted to handle money transactions.
4494 A blog post from
4495 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
4496 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
4497 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
4498 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
4499 some help from my friend to get it all running, and he even handed me
4500 some bitcoins to get started. I even donated a few bitcoins to Simon
4501 for helping me remember BitCoin.&lt;/p&gt;
4502
4503 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
4504 crypto-currency, decentralised and handled using peer-to-peer
4505 networks. It allows anonymous transactions and prohibits central
4506 control over the transactions, making it impossible for governments
4507 and companies alike to block donations and other transactions. The
4508 source is free software, and while the key dependency wxWidgets 2.9
4509 for the graphical user interface is missing in Debian, the command
4510 line client builds just fine. Hopefully Jonas
4511 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
4512 Debian&lt;/a&gt; soon.&lt;/p&gt;
4513
4514 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
4515 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
4516 bitcoins&lt;/a&gt; when selling services and goods, and there are even
4517 currency &quot;stock&quot; markets where the exchange rate is decided. There
4518 are not many users so far, but the concept seems promising. If you
4519 want to get started and lack a friend with any bitcoins to spare,
4520 you can even get
4521 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
4522 bitcoin at the time of writing). Use
4523 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
4524 on the current exchange rates.&lt;/p&gt;
4525
4526 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
4527 machines. If you want to support my activity, please send Bitcoin
4528 donations to the address
4529 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
4530 </description>
4531 </item>
4532
4533 <item>
4534 <title>Why isn&#39;t Debian Edu using VLC?</title>
4535 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
4536 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
4537 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
4538 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
4539 presented, and the winner among the multimedia player were VLC.
4540 Personally, I like VLC, and it is my player of choice when I first try
4541 to play a video file or stream. Only if VLC fail will I drag out
4542 gmplayer to see if it can do better. The reason is mostly the failure
4543 model and trust. When VLC fail, it normally pop up a error message
4544 reporting the problem. When mplayer fail, it normally segfault or
4545 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
4546
4547 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
4548 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4549 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
4550 plugin to play web videos seamlessly, and the VLC browser plugin is
4551 not very good. For example, it lack in-line control buttons, so there
4552 is no way for the user to pause the video. Also, when I
4553 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
4554 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
4555 failed on several video pages where mplayer based plugins worked. If
4556 the browser plugin for VLC was as good as the gecko-mediaplayer
4557 package (which uses mplayer), we would switch.&lt;/P&gt;
4558
4559 &lt;p&gt;While VLC is a good player, its user interface is slightly
4560 annoying. The most annoying feature is its inconsistent use of
4561 keyboard shortcuts. When the player is in full screen mode, its
4562 shortcuts are different from when it is playing the video in a window.
4563 For example, space only work as pause when in full screen mode. I
4564 wish it had consisten shortcuts and that space also would work when in
4565 window mode. Another nice shortcut in gmplayer is [enter] to restart
4566 the current video. It is very nice when playing short videos from the
4567 web and want to restart it when new people arrive to have a look at
4568 what is going on.&lt;/p&gt;
4569 </description>
4570 </item>
4571
4572 <item>
4573 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
4574 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
4575 <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>
4576 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
4577 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
4578 upgrade testing of the
4579 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
4580 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
4581 This seem like a very good idea, so I adjusted by test scripts and
4582 can now present the updated result from today:&lt;/p&gt;
4583
4584 &lt;p&gt;This is for Gnome:&lt;/p&gt;
4585
4586 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4587
4588 &lt;blockquote&gt;&lt;p&gt;
4589 apache2.2-bin
4590 aptdaemon
4591 baobab
4592 binfmt-support
4593 browser-plugin-gnash
4594 cheese-common
4595 cli-common
4596 cups-pk-helper
4597 dmz-cursor-theme
4598 empathy
4599 empathy-common
4600 freedesktop-sound-theme
4601 freeglut3
4602 gconf-defaults-service
4603 gdm-themes
4604 gedit-plugins
4605 geoclue
4606 geoclue-hostip
4607 geoclue-localnet
4608 geoclue-manual
4609 geoclue-yahoo
4610 gnash
4611 gnash-common
4612 gnome
4613 gnome-backgrounds
4614 gnome-cards-data
4615 gnome-codec-install
4616 gnome-core
4617 gnome-desktop-environment
4618 gnome-disk-utility
4619 gnome-screenshot
4620 gnome-search-tool
4621 gnome-session-canberra
4622 gnome-system-log
4623 gnome-themes-extras
4624 gnome-themes-more
4625 gnome-user-share
4626 gstreamer0.10-fluendo-mp3
4627 gstreamer0.10-tools
4628 gtk2-engines
4629 gtk2-engines-pixbuf
4630 gtk2-engines-smooth
4631 hamster-applet
4632 libapache2-mod-dnssd
4633 libapr1
4634 libaprutil1
4635 libaprutil1-dbd-sqlite3
4636 libaprutil1-ldap
4637 libart2.0-cil
4638 libboost-date-time1.42.0
4639 libboost-python1.42.0
4640 libboost-thread1.42.0
4641 libchamplain-0.4-0
4642 libchamplain-gtk-0.4-0
4643 libcheese-gtk18
4644 libclutter-gtk-0.10-0
4645 libcryptui0
4646 libdiscid0
4647 libelf1
4648 libepc-1.0-2
4649 libepc-common
4650 libepc-ui-1.0-2
4651 libfreerdp-plugins-standard
4652 libfreerdp0
4653 libgconf2.0-cil
4654 libgdata-common
4655 libgdata7
4656 libgdu-gtk0
4657 libgee2
4658 libgeoclue0
4659 libgexiv2-0
4660 libgif4
4661 libglade2.0-cil
4662 libglib2.0-cil
4663 libgmime2.4-cil
4664 libgnome-vfs2.0-cil
4665 libgnome2.24-cil
4666 libgnomepanel2.24-cil
4667 libgpod-common
4668 libgpod4
4669 libgtk2.0-cil
4670 libgtkglext1
4671 libgtksourceview2.0-common
4672 libmono-addins-gui0.2-cil
4673 libmono-addins0.2-cil
4674 libmono-cairo2.0-cil
4675 libmono-corlib2.0-cil
4676 libmono-i18n-west2.0-cil
4677 libmono-posix2.0-cil
4678 libmono-security2.0-cil
4679 libmono-sharpzip2.84-cil
4680 libmono-system2.0-cil
4681 libmtp8
4682 libmusicbrainz3-6
4683 libndesk-dbus-glib1.0-cil
4684 libndesk-dbus1.0-cil
4685 libopal3.6.8
4686 libpolkit-gtk-1-0
4687 libpt2.6.7
4688 libpython2.6
4689 librpm1
4690 librpmio1
4691 libsdl1.2debian
4692 libsrtp0
4693 libssh-4
4694 libtelepathy-farsight0
4695 libtelepathy-glib0
4696 libtidy-0.99-0
4697 media-player-info
4698 mesa-utils
4699 mono-2.0-gac
4700 mono-gac
4701 mono-runtime
4702 nautilus-sendto
4703 nautilus-sendto-empathy
4704 p7zip-full
4705 pkg-config
4706 python-aptdaemon
4707 python-aptdaemon-gtk
4708 python-axiom
4709 python-beautifulsoup
4710 python-bugbuddy
4711 python-clientform
4712 python-coherence
4713 python-configobj
4714 python-crypto
4715 python-cupshelpers
4716 python-elementtree
4717 python-epsilon
4718 python-evolution
4719 python-feedparser
4720 python-gdata
4721 python-gdbm
4722 python-gst0.10
4723 python-gtkglext1
4724 python-gtksourceview2
4725 python-httplib2
4726 python-louie
4727 python-mako
4728 python-markupsafe
4729 python-mechanize
4730 python-nevow
4731 python-notify
4732 python-opengl
4733 python-openssl
4734 python-pam
4735 python-pkg-resources
4736 python-pyasn1
4737 python-pysqlite2
4738 python-rdflib
4739 python-serial
4740 python-tagpy
4741 python-twisted-bin
4742 python-twisted-conch
4743 python-twisted-core
4744 python-twisted-web
4745 python-utidylib
4746 python-webkit
4747 python-xdg
4748 python-zope.interface
4749 remmina
4750 remmina-plugin-data
4751 remmina-plugin-rdp
4752 remmina-plugin-vnc
4753 rhythmbox-plugin-cdrecorder
4754 rhythmbox-plugins
4755 rpm-common
4756 rpm2cpio
4757 seahorse-plugins
4758 shotwell
4759 software-center
4760 system-config-printer-udev
4761 telepathy-gabble
4762 telepathy-mission-control-5
4763 telepathy-salut
4764 tomboy
4765 totem
4766 totem-coherence
4767 totem-mozilla
4768 totem-plugins
4769 transmission-common
4770 xdg-user-dirs
4771 xdg-user-dirs-gtk
4772 xserver-xephyr
4773 &lt;/p&gt;&lt;/blockquote&gt;
4774
4775 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4776
4777 &lt;blockquote&gt;&lt;p&gt;
4778 cheese
4779 ekiga
4780 eog
4781 epiphany-extensions
4782 evolution-exchange
4783 fast-user-switch-applet
4784 file-roller
4785 gcalctool
4786 gconf-editor
4787 gdm
4788 gedit
4789 gedit-common
4790 gnome-games
4791 gnome-games-data
4792 gnome-nettool
4793 gnome-system-tools
4794 gnome-themes
4795 gnuchess
4796 gucharmap
4797 guile-1.8-libs
4798 libavahi-ui0
4799 libdmx1
4800 libgalago3
4801 libgtk-vnc-1.0-0
4802 libgtksourceview2.0-0
4803 liblircclient0
4804 libsdl1.2debian-alsa
4805 libspeexdsp1
4806 libsvga1
4807 rhythmbox
4808 seahorse
4809 sound-juicer
4810 system-config-printer
4811 totem-common
4812 transmission-gtk
4813 vinagre
4814 vino
4815 &lt;/p&gt;&lt;/blockquote&gt;
4816
4817 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4818
4819 &lt;blockquote&gt;&lt;p&gt;
4820 gstreamer0.10-gnomevfs
4821 &lt;/p&gt;&lt;/blockquote&gt;
4822
4823 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4824
4825 &lt;blockquote&gt;&lt;p&gt;
4826 [nothing]
4827 &lt;/p&gt;&lt;/blockquote&gt;
4828
4829 &lt;p&gt;This is for KDE:&lt;/p&gt;
4830
4831 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4832
4833 &lt;blockquote&gt;&lt;p&gt;
4834 ksmserver
4835 &lt;/p&gt;&lt;/blockquote&gt;
4836
4837 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4838
4839 &lt;blockquote&gt;&lt;p&gt;
4840 kwin
4841 network-manager-kde
4842 &lt;/p&gt;&lt;/blockquote&gt;
4843
4844 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4845
4846 &lt;blockquote&gt;&lt;p&gt;
4847 arts
4848 dolphin
4849 freespacenotifier
4850 google-gadgets-gst
4851 google-gadgets-xul
4852 kappfinder
4853 kcalc
4854 kcharselect
4855 kde-core
4856 kde-plasma-desktop
4857 kde-standard
4858 kde-window-manager
4859 kdeartwork
4860 kdeartwork-emoticons
4861 kdeartwork-style
4862 kdeartwork-theme-icon
4863 kdebase
4864 kdebase-apps
4865 kdebase-workspace
4866 kdebase-workspace-bin
4867 kdebase-workspace-data
4868 kdeeject
4869 kdelibs
4870 kdeplasma-addons
4871 kdeutils
4872 kdewallpapers
4873 kdf
4874 kfloppy
4875 kgpg
4876 khelpcenter4
4877 kinfocenter
4878 konq-plugins-l10n
4879 konqueror-nsplugins
4880 kscreensaver
4881 kscreensaver-xsavers
4882 ktimer
4883 kwrite
4884 libgle3
4885 libkde4-ruby1.8
4886 libkonq5
4887 libkonq5-templates
4888 libnetpbm10
4889 libplasma-ruby
4890 libplasma-ruby1.8
4891 libqt4-ruby1.8
4892 marble-data
4893 marble-plugins
4894 netpbm
4895 nuvola-icon-theme
4896 plasma-dataengines-workspace
4897 plasma-desktop
4898 plasma-desktopthemes-artwork
4899 plasma-runners-addons
4900 plasma-scriptengine-googlegadgets
4901 plasma-scriptengine-python
4902 plasma-scriptengine-qedje
4903 plasma-scriptengine-ruby
4904 plasma-scriptengine-webkit
4905 plasma-scriptengines
4906 plasma-wallpapers-addons
4907 plasma-widget-folderview
4908 plasma-widget-networkmanagement
4909 ruby
4910 sweeper
4911 update-notifier-kde
4912 xscreensaver-data-extra
4913 xscreensaver-gl
4914 xscreensaver-gl-extra
4915 xscreensaver-screensaver-bsod
4916 &lt;/p&gt;&lt;/blockquote&gt;
4917
4918 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4919
4920 &lt;blockquote&gt;&lt;p&gt;
4921 ark
4922 google-gadgets-common
4923 google-gadgets-qt
4924 htdig
4925 kate
4926 kdebase-bin
4927 kdebase-data
4928 kdepasswd
4929 kfind
4930 klipper
4931 konq-plugins
4932 konqueror
4933 ksysguard
4934 ksysguardd
4935 libarchive1
4936 libcln6
4937 libeet1
4938 libeina-svn-06
4939 libggadget-1.0-0b
4940 libggadget-qt-1.0-0b
4941 libgps19
4942 libkdecorations4
4943 libkephal4
4944 libkonq4
4945 libkonqsidebarplugin4a
4946 libkscreensaver5
4947 libksgrd4
4948 libksignalplotter4
4949 libkunitconversion4
4950 libkwineffects1a
4951 libmarblewidget4
4952 libntrack-qt4-1
4953 libntrack0
4954 libplasma-geolocation-interface4
4955 libplasmaclock4a
4956 libplasmagenericshell4
4957 libprocesscore4a
4958 libprocessui4a
4959 libqalculate5
4960 libqedje0a
4961 libqtruby4shared2
4962 libqzion0a
4963 libruby1.8
4964 libscim8c2a
4965 libsmokekdecore4-3
4966 libsmokekdeui4-3
4967 libsmokekfile3
4968 libsmokekhtml3
4969 libsmokekio3
4970 libsmokeknewstuff2-3
4971 libsmokeknewstuff3-3
4972 libsmokekparts3
4973 libsmokektexteditor3
4974 libsmokekutils3
4975 libsmokenepomuk3
4976 libsmokephonon3
4977 libsmokeplasma3
4978 libsmokeqtcore4-3
4979 libsmokeqtdbus4-3
4980 libsmokeqtgui4-3
4981 libsmokeqtnetwork4-3
4982 libsmokeqtopengl4-3
4983 libsmokeqtscript4-3
4984 libsmokeqtsql4-3
4985 libsmokeqtsvg4-3
4986 libsmokeqttest4-3
4987 libsmokeqtuitools4-3
4988 libsmokeqtwebkit4-3
4989 libsmokeqtxml4-3
4990 libsmokesolid3
4991 libsmokesoprano3
4992 libtaskmanager4a
4993 libtidy-0.99-0
4994 libweather-ion4a
4995 libxklavier16
4996 libxxf86misc1
4997 okteta
4998 oxygencursors
4999 plasma-dataengines-addons
5000 plasma-scriptengine-superkaramba
5001 plasma-widget-lancelot
5002 plasma-widgets-addons
5003 plasma-widgets-workspace
5004 polkit-kde-1
5005 ruby1.8
5006 systemsettings
5007 update-notifier-common
5008 &lt;/p&gt;&lt;/blockquote&gt;
5009
5010 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
5011 aptitude a bit more similar, but there are still quite a lott of
5012 differences. I have no idea what packages should be installed after
5013 the upgrade, but hope those that do can have a look.&lt;/p&gt;
5014 </description>
5015 </item>
5016
5017 <item>
5018 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
5019 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
5020 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
5021 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
5022 <description>&lt;p&gt;Most of the computers in use by the
5023 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
5024 are virtual machines. And they have been Xen machines running on a
5025 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
5026 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
5027 bit harder that it could have been, because we set up the Xen virtual
5028 machines to get the virtual partitions from LVM, which as far as I
5029 know is not supported by KVM. So to migrate, we had to convert
5030 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
5031
5032 &lt;p&gt;I found
5033 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
5034 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
5035 migration. It uses qemu-img from the qemu package to make the disk
5036 image, parted to partition it, losetup and kpartx to present the disk
5037 image partions as devices, and dd to copy the data. I NFS mounted the
5038 new servers storage area on the old server to do the migration.&lt;/p&gt;
5039
5040 &lt;pre&gt;
5041 #!/bin/sh
5042
5043 # Based on
5044 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
5045
5046 set -e
5047 set -x
5048
5049 if [ -z &quot;$1&quot; ] ; then
5050 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
5051 exit 1
5052 else
5053 host=&quot;$1&quot;
5054 fi
5055
5056 if [ ! -e /dev/vg_data/$host-disk ] ; then
5057 echo &quot;error: unable to find LVM volume for $host&quot;
5058 exit 1
5059 fi
5060
5061 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5062 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5063 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5064 totalsize=$(( ( $disksize + $swapsize ) ))
5065
5066 img=$host.img
5067 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5068 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5069
5070 parted $img mklabel msdos
5071 parted $img mkpart primary linux-swap 0 $disksize
5072 parted $img mkpart primary ext2 $disksize $totalsize
5073 parted $img set 1 boot on
5074
5075 modprobe dm-mod
5076 losetup /dev/loop0 $img
5077 kpartx -a /dev/loop0
5078
5079 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5080 fsck.ext3 -f /dev/mapper/loop0p1 || true
5081 mkswap /dev/mapper/loop0p2
5082
5083 kpartx -d /dev/loop0
5084 losetup -d /dev/loop0
5085 &lt;/pre&gt;
5086
5087 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5088 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5089
5090 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5091 the new disk image attached, installed grub-pc and linux-image-686 and
5092 set up grub to boot from the disk image. After this, the KVM machines
5093 seem to work just fine.&lt;/p&gt;
5094 </description>
5095 </item>
5096
5097 <item>
5098 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5099 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5100 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5101 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5102 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5103 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5104 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5105 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5106
5107 &lt;p&gt;I still do not know what a correct migration should look like, so I
5108 report any differences between apt and aptitude and hope someone else
5109 can see if anything should be changed.&lt;/p&gt;
5110
5111 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5112
5113 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5114
5115 &lt;blockquote&gt;&lt;p&gt;
5116 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5117 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5118 dmz-cursor-theme empathy empathy-common finger
5119 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5120 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5121 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5122 gnome-cards-data gnome-codec-install gnome-core
5123 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5124 gnome-search-tool gnome-session-canberra gnome-spell
5125 gnome-system-log gnome-themes-extras gnome-themes-more
5126 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5127 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5128 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5129 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5130 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5131 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5132 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5133 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5134 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5135 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5136 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5137 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5138 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5139 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5140 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5141 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5142 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5143 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5144 libmono-security2.0-cil libmono-sharpzip2.84-cil
5145 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5146 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5147 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5148 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5149 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5150 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5151 libxalan2-java libxerces2-java media-player-info mesa-utils
5152 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5153 nautilus-sendto-empathy openoffice.org-writer2latex
5154 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5155 python-aptdaemon python-aptdaemon-gtk python-axiom
5156 python-beautifulsoup python-bugbuddy python-clientform
5157 python-coherence python-configobj python-crypto python-cupshelpers
5158 python-cupsutils python-eggtrayicon python-elementtree
5159 python-epsilon python-evolution python-feedparser python-gdata
5160 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5161 python-gtksourceview2 python-httplib2 python-louie python-mako
5162 python-markupsafe python-mechanize python-nevow python-notify
5163 python-opengl python-openssl python-pam python-pkg-resources
5164 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5165 python-tagpy python-twisted-bin python-twisted-conch
5166 python-twisted-core python-twisted-web python-utidylib python-webkit
5167 python-xdg python-zope.interface remmina remmina-plugin-data
5168 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5169 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5170 software-center svgalibg1 system-config-printer-udev
5171 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5172 totem totem-coherence totem-mozilla totem-plugins
5173 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5174 zip
5175 &lt;/p&gt;&lt;/blockquote&gt;
5176
5177 Installed using apt-get, removed with aptitude
5178
5179 &lt;blockquote&gt;&lt;p&gt;
5180 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5181 epiphany-extensions epiphany-gecko evolution-exchange
5182 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5183 gedit-common gnome-app-install gnome-games gnome-games-data
5184 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5185 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5186 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5187 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5188 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5189 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5190 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5191 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5192 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5193 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5194 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5195 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5196 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5197 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5198 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5199 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5200 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5201 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5202 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5203 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5204 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5205 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5206 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5207 sound-juicer swfdec-gnome system-config-printer totem-common
5208 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5209 &lt;/p&gt;&lt;/blockquote&gt;
5210
5211 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5212
5213 &lt;blockquote&gt;&lt;p&gt;
5214 gstreamer0.10-gnomevfs
5215 &lt;/p&gt;&lt;/blockquote&gt;
5216
5217 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5218
5219 &lt;blockquote&gt;&lt;p&gt;
5220 [nothing]
5221 &lt;/p&gt;&lt;/blockquote&gt;
5222
5223 &lt;p&gt;This is for KDE:&lt;/p&gt;
5224
5225 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5226
5227 &lt;blockquote&gt;&lt;p&gt;
5228 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5229 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5230 ghostscript-x git gnome-audio gnugo granatier gs-common
5231 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5232 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5233 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5234 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5235 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5236 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5237 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5238 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5239 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5240 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5241 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5242 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5243 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5244 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5245 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5246 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5247 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5248 libkrossui4 libmailtools-perl libmime-tools-perl
5249 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5250 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5251 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5252 lirc luatex marble networkstatus noatun-plugins
5253 openoffice.org-writer2latex palapeli palapeli-data parley
5254 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5255 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5256 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5257 ttf-sazanami-gothic
5258 &lt;/p&gt;&lt;/blockquote&gt;
5259
5260 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5261
5262 &lt;blockquote&gt;&lt;p&gt;
5263 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5264 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5265 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5266 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5267 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5268 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5269 kitchensync kiten kjumpingcube klatin klettres klickety klines
5270 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5271 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5272 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5273 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5274 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5275 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5276 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5277 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5278 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5279 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5280 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5281 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5282 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5283 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5284 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5285 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5286 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5287 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5288 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5289 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5290 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5291 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5292 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5293 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5294 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5295 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5296 &lt;/p&gt;&lt;/blockquote&gt;
5297
5298 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5299
5300 &lt;blockquote&gt;&lt;p&gt;
5301 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5302 kdeartwork kdebase kdebase-apps kdebase-workspace
5303 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5304 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5305 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5306 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5307 xscreensaver-screensaver-bsod
5308 &lt;/p&gt;&lt;/blockquote&gt;
5309
5310 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5311
5312 &lt;blockquote&gt;&lt;p&gt;
5313 kdebase-bin konq-plugins konqueror
5314 &lt;/p&gt;&lt;/blockquote&gt;
5315 </description>
5316 </item>
5317
5318 <item>
5319 <title>Gnash buildbot slave and Debian kfreebsd</title>
5320 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5321 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5322 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5323 <description>&lt;p&gt;Answering
5324 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5325 call from the Gnash project&lt;/a&gt; for
5326 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5327 current source, I have set up a virtual KVM machine on the Debian
5328 Edu/Skolelinux virtualization host to test the git source on
5329 Debian/Squeeze. I hope this can help the developers in getting new
5330 releases out more often.&lt;/p&gt;
5331
5332 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5333 I have considered setting up a &lt;a
5334 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5335 machine as well. I have also considered using the kfreebsd
5336 architecture in Debian as a file server in NUUG to get access to the 5
5337 TB zfs volume we currently use to store DV video. Because of this, I
5338 finally got around to do a test installation of Debian/Squeeze with
5339 kfreebsd. Installation went fairly smooth, thought I noticed some
5340 visual glitches in the cdebconf dialogs (black cursor left on the
5341 screen at random locations). Have not gotten very far with the
5342 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5343 fatal problem. Have to spend some more time on it to see if it is
5344 useful as a file server for NUUG. Will try to find time to set up a
5345 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5346 </description>
5347 </item>
5348
5349 <item>
5350 <title>Debian in 3D</title>
5351 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5352 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5353 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5354 <description>&lt;p&gt;&lt;img src=&quot;http://thingiverse-production.s3.amazonaws.com/renders/23/e0/c4/f9/2b/debswagtdose_preview_medium.jpg&quot;&gt;&lt;/p&gt;
5355
5356 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5357 3D linked in from
5358 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5359 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5360 </description>
5361 </item>
5362
5363 <item>
5364 <title>Software updates 2010-10-24</title>
5365 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5366 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5367 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5368 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5369
5370 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5371 raise money for the project is going well. The lower limit of 10
5372 signers was reached in 24 hours, and so far 13 people have signed it.
5373 More signers and more funding is most welcome, and I am really curious
5374 how far we can get before the time limit of December 24 is reached.
5375 :)&lt;/p&gt;
5376
5377 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5378 about what appear to be a great code coverage tool capable of
5379 generating code coverage stats without any changes to the source code.
5380 It is called
5381 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5382 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5383 It is missing in Debian, but the git source built just fine in Squeeze
5384 after I installed libelf-dev, libdwarf-dev, pkg-config and
5385 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5386 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5387
5388 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5389 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5390 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5391 alpha test release of the Squeeze based Debian Edu /
5392 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5393 release. Give it a try if you need a complete linux solution for your
5394 school, including central infrastructure server, workstations, thin
5395 client servers and diskless workstations. A nice touch added
5396 yesterday is RDP support on the thin client servers, for windows
5397 clients to get a Linux desktop on request.&lt;/p&gt;
5398 </description>
5399 </item>
5400
5401 <item>
5402 <title>Some notes on Flash in Debian and Debian Edu</title>
5403 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5404 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5405 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5406 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5407 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5408 second most popular used package that is missing in Debian. The sixth
5409 most popular is flashplayer-mozilla. This is a clear indication that
5410 working flash is important for Debian users. Around 10 percent of the
5411 users submitting data to popcon.debian.org have this package
5412 installed.&lt;/p&gt;
5413
5414 &lt;p&gt;In the report written by Lars Risan in August 2008
5415&lt;a href=&quot;http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile&amp;do=view&amp;target=Skolelinux_i_bruk_rapport_1.0.pdf&quot;&gt;Skolelinux
5416 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5417 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
5418 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5419 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
5420 web sites require Flash to work, and lacking working Flash support in
5421 the web browser and the problems with installing it was perceived as a
5422 good reason to stay with Windows.&lt;/p&gt;
5423
5424 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
5425 said to be the retarded cousin that did not really understand
5426 everything you told him but could work fairly well. This was a
5427 comment regarding the problems Linux have with proprietary formats and
5428 non-standard web pages, and is sad because it exposes a fairly common
5429 understanding of whose fault it is if web pages that only work in for
5430 example Internet Explorer 6 fail to work on Firefox, and funny because
5431 it explain very well how annoying it is for users when Linux
5432 distributions do not work with the documents they receive or the web
5433 pages they want to visit.&lt;/p&gt;
5434
5435 &lt;p&gt;This is part of the reason why I believe it is important for Debian
5436 and Debian Edu to have a well working Flash implementation in the
5437 distribution, to get at least popular sites as Youtube and Google
5438 Video to working out of the box. For Squeeze, Debian have the chance
5439 to include the latest version of Gnash that will make this happen, as
5440 the new release 0.8.8 was published a few weeks ago and is resting in
5441 unstable. The new version work with more sites that version 0.8.7.
5442 The Gnash maintainers have asked for a freeze exception, but the
5443 release team have not had time to reply to it yet. I hope they agree
5444 with me that Flash is important for the Debian desktop users, and thus
5445 accept the new package into Squeeze.&lt;/p&gt;
5446 </description>
5447 </item>
5448
5449 <item>
5450 <title>Circular package dependencies harms apt recovery</title>
5451 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
5452 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
5453 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
5454 <description>&lt;p&gt;I discovered this while doing
5455 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
5456 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
5457 in Debian still got circular dependencies, and it is often claimed
5458 that apt and aptitude should be able to handle this just fine, but
5459 some times these dependency loops causes apt to fail.&lt;/p&gt;
5460
5461 &lt;p&gt;An example is from todays
5462 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
5463 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
5464 causes perl-modules to fail to upgrade. The cause is simple. If a
5465 package fail to unpack, then only part of packages with the circular
5466 dependency might end up being unpacked when unpacking aborts, and the
5467 ones already unpacked will fail to configure in the recovery phase
5468 because its dependencies are unavailable.&lt;/p&gt;
5469
5470 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
5471
5472 &lt;blockquote&gt;&lt;pre&gt;
5473 dpkg: dependency problems prevent configuration of perl-modules:
5474 perl-modules depends on perl (&gt;= 5.10.1-1); however:
5475 Version of perl on system is 5.10.0-19lenny2.
5476 dpkg: error processing perl-modules (--configure):
5477 dependency problems - leaving unconfigured
5478 &lt;/pre&gt;&lt;/blockquote&gt;
5479
5480 &lt;p&gt;The perl/perl-modules circular dependency is already
5481 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
5482 hopefully be solved as soon as possible, but it is not the only one,
5483 and each one of these loops in the dependency tree can cause similar
5484 failures. Of course, they only occur when there are bugs in other
5485 packages causing the unpacking to fail, but it is rather nasty when
5486 the failure of one package causes the problem to become worse because
5487 of dependency loops.&lt;/p&gt;
5488
5489 &lt;p&gt;Thanks to
5490 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
5491 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
5492 dependencies
5493 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
5494 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
5495
5496 &lt;p&gt;Todays testing also exposed a bug in
5497 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
5498 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
5499 apt-get and aptitude, the latter possibly caused by some circular
5500 dependency. Reported both to BTS to try to get someone to look at
5501 it.&lt;/p&gt;
5502 </description>
5503 </item>
5504
5505 <item>
5506 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
5507 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
5508 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
5509 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
5510 <description>&lt;p&gt;This is a
5511 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;followup&lt;/a&gt;
5512 on my
5513 &lt;a href=&quot;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&quot;&gt;previous
5514 work&lt;/a&gt; on
5515 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
5516 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
5517
5518 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
5519 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5520 and dhcp3-server-ldap in Debian use the LDAP server. The two
5521 implementations are quite different in how they use LDAP.&lt;/p&gt;
5522
5523 To get this information, I started slapd with debugging enabled and
5524 dumped the debug output to a file to get the LDAP searches performed
5525 on a Debian Edu main-server. Here is a summary.
5526
5527 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
5528
5529 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
5530 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
5531 the web.
5532
5533 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
5534 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
5535 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
5536 reverse entries are in two different subtrees in LDAP with a structure
5537 based on the DNS names, as in tjener.intern and
5538 2.2.0.10.in-addr.arpa.&lt;/p&gt;
5539
5540 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
5541 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
5542 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
5543 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
5544 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
5545 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
5546 forward entries, it is looking for attributes named dnsttl, arecord,
5547 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5548 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5549 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5550 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5551 spfrecord and modifytimestamp. For reverse entries it is looking for
5552 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5553 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5554 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5555 ldapsearch commands could look like this:&lt;/p&gt;
5556
5557 &lt;blockquote&gt;&lt;pre&gt;
5558 ldapsearch -h ldap \
5559 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5560 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5561 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5562 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5563 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5564 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5565
5566 ldapsearch -h ldap \
5567 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5568 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
5569 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5570 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5571 srvrecord naptrrecord modifytimestamp
5572 &lt;/pre&gt;&lt;/blockquote&gt;
5573
5574 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
5575 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5576 example LDAP objects used there. In addition to these objects, the
5577 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5578 also exist.&lt;/p&gt;
5579
5580 &lt;blockquote&gt;&lt;pre&gt;
5581 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5582 objectclass: top
5583 objectclass: dnsdomain
5584 objectclass: domainrelatedobject
5585 dc: tjener
5586 arecord: 10.0.2.2
5587 associateddomain: tjener.intern
5588
5589 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5590 objectclass: top
5591 objectclass: dnsdomain2
5592 objectclass: domainrelatedobject
5593 dc: 2
5594 ptrrecord: tjener.intern
5595 associateddomain: 2.2.0.10.in-addr.arpa
5596 &lt;/pre&gt;&lt;/blockquote&gt;
5597
5598 &lt;p&gt;In strict mode, the server behaves differently. When looking for
5599 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
5600 same base as in the tree mode for a object with filter
5601 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
5602 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5603 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5604 naptrrecord and modifytimestamp. For reverse entires it also do a
5605 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
5606 and the requested attributes are associateddomain, dnsttl and
5607 modifytimestamp. In short, in strict mode the objects with ptrrecord
5608 go away, and the arecord attribute in the forward object is used
5609 instead.&lt;/p&gt;
5610
5611 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
5612 like this:&lt;/p&gt;
5613
5614 &lt;blockquote&gt;&lt;pre&gt;
5615 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5616 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5617 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5618 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5619 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5620 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5621
5622 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5623 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
5624 &lt;/pre&gt;&lt;/blockquote&gt;
5625
5626 &lt;p&gt;In addition to the forward and reverse searches , there is also a
5627 search for SOA records, which behave similar to the forward and
5628 reverse lookups.&lt;/p&gt;
5629
5630 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
5631 specify any objectclass names, and instead look for the attributes it
5632 need to generate a DNS reply. This make it able to work with any
5633 objectclass that provide the needed attributes.&lt;/p&gt;
5634
5635 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
5636 dnsdomain2 schemas. The latter is used for reverse entries like
5637 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
5638
5639 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
5640 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5641 attributes) and domainrelatedobject (for associatedDomain). The use
5642 of structural object classes make it impossible to combine these
5643 classes with the object classes used by DHCP.&lt;/p&gt;
5644
5645 &lt;p&gt;There are other schemas that could be used too, for example the
5646 dnszone structural object class used by Gosa and bind-sdb for the DNS
5647 attributes combined with the domainrelatedobject object class, but in
5648 this case some unused attributes would have to be included as well
5649 (zonename and relativedomainname).&lt;/p&gt;
5650
5651 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
5652 mode and not use any of the existing objectclasses (dnsdomain,
5653 dnsdomain2 and dnszone) when one want to combine the DNS information
5654 with DHCP information, and instead create a auxiliary object class
5655 defined something like this (using the attributes defined for
5656 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
5657
5658 &lt;blockquote&gt;&lt;pre&gt;
5659 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
5660 SUP top
5661 AUXILIARY
5662 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5663 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5664 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5665 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5666 A6Record $ DNAMERecord
5667 ))
5668 &lt;/pre&gt;&lt;/blockquote&gt;
5669
5670 &lt;p&gt;This will allow any object to become a DNS entry when combined with
5671 the domainrelatedobject object class, and allow any entity to include
5672 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
5673 developers asking for their view on this schema and if they are
5674 interested in providing such schema with PowerDNS, and I hope my
5675 message will be accepted into their mailing list soon.&lt;/p&gt;
5676
5677 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
5678
5679 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
5680 the object attributes, and then uses the attributes it want. This
5681 make it harder to figure out exactly what attributes are used, but
5682 thanks to the working example in Debian Edu I can at least get an idea
5683 what is needed without having to read the source code.&lt;/p&gt;
5684
5685 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
5686 search filter to use to locate the correct dhcpServer entity is
5687 stored. These are the relevant entries from
5688 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
5689
5690 &lt;blockquote&gt;&lt;pre&gt;
5691 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
5692 ldap-dhcp-server-cn &quot;dhcp&quot;;
5693 &lt;/pre&gt;&lt;/blockquote&gt;
5694
5695 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
5696 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
5697 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
5698 search result is this entry:&lt;/p&gt;
5699
5700 &lt;blockquote&gt;&lt;pre&gt;
5701 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5702 cn: dhcp
5703 objectClass: top
5704 objectClass: dhcpServer
5705 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5706 &lt;/pre&gt;&lt;/blockquote&gt;
5707
5708 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
5709 subtree with DHCP configuration. The DHCP configuration subtree base
5710 is located using a base scope search with base &quot;cn=DHCP
5711 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
5712 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
5713 The search result is this entry:&lt;/p&gt;
5714
5715 &lt;blockquote&gt;&lt;pre&gt;
5716 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5717 cn: DHCP Config
5718 objectClass: top
5719 objectClass: dhcpService
5720 objectClass: dhcpOptions
5721 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5722 dhcpStatements: ddns-update-style none
5723 dhcpStatements: authoritative
5724 dhcpOption: smtp-server code 69 = array of ip-address
5725 dhcpOption: www-server code 72 = array of ip-address
5726 dhcpOption: wpad-url code 252 = text
5727 &lt;/pre&gt;&lt;/blockquote&gt;
5728
5729 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
5730 all the DHCP configuration is loaded, it is ready to receive requests.
5731 The subtree in Debian Edu contain objects with object classes
5732 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5733 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5734 and information about netmasks, dynamic range etc. Leaving out the
5735 details here because it is not relevant for the focus of my
5736 investigation, which is to see if it is possible to merge dns and dhcp
5737 related computer objects.&lt;/p&gt;
5738
5739 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
5740 of the client (00:00:00:00:00:00 in this example), using a subtree
5741 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
5742 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5743 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
5744 like:&lt;/p&gt;
5745
5746 &lt;blockquote&gt;&lt;pre&gt;
5747 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5748 cn: hostname
5749 objectClass: top
5750 objectClass: dhcpHost
5751 dhcpHWAddress: ethernet 00:00:00:00:00:00
5752 dhcpStatements: fixed-address hostname
5753 &lt;/pre&gt;&lt;/blockquote&gt;
5754
5755 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
5756 The object classes need to have fixed names, and the configuration
5757 need to be stored in a fairly specific LDAP structure. On the
5758 positive side, the invidiual dhcpHost entires can be anywhere without
5759 the DN pointed to by the dhcpServer entries. The latter should make
5760 it possible to group all host entries in a subtree next to the
5761 configuration entries, and this subtree can also be shared with the
5762 DNS server if the schema proposed above is combined with the dhcpHost
5763 structural object class.
5764
5765 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
5766
5767 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
5768 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
5769 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
5770 allowing DNS objects to be stored anywhere under the base cn specified
5771 in the configuration.&lt;/p&gt;
5772
5773 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
5774 regarding which LDAP schemas to use and which LDAP structure to use.
5775 I guess one could implement ones own schema, as long as the
5776 objectclasses and attributes have the names used, but this do not
5777 really help when the DHCP subtree need to have a fairly fixed
5778 structure.&lt;/p&gt;
5779
5780 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
5781 this might work for Debian Edu:&lt;/p&gt;
5782
5783 &lt;blockquote&gt;&lt;pre&gt;
5784 ou=services
5785 cn=machine-info (dhcpService) - dhcpServiceDN points here
5786 cn=dhcp (dhcpServer)
5787 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5788 cn=10.0.2.0 (dhcpSubnet)
5789 cn=group1 (dhcpGroup/dhcpOptions)
5790 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5791 cn=192.168.0.0 (dhcpSubnet)
5792 cn=group1 (dhcpGroup/dhcpOptions)
5793 ou=machines - PowerDNS base points here
5794 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
5795 &lt;/pre&gt;&lt;/blockquote&gt;
5796
5797 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
5798 entries to be in the dhcpGroup subtrees, the entries can be stored
5799 there instead of a common machines subtree, and the PowerDNS base
5800 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
5801
5802 &lt;p&gt;The combined object under the machines subtree would look something
5803 like this:&lt;/p&gt;
5804
5805 &lt;blockquote&gt;&lt;pre&gt;
5806 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
5807 dc: hostname
5808 objectClass: top
5809 objectClass: dhcpHost
5810 objectclass: domainrelatedobject
5811 objectclass: dnsDomainAux
5812 associateddomain: hostname.intern
5813 arecord: 10.11.12.13
5814 dhcpHWAddress: ethernet 00:00:00:00:00:00
5815 dhcpStatements: fixed-address hostname.intern
5816 &lt;/pre&gt;&lt;/blockquote&gt;
5817
5818 &lt;/p&gt;One could even add the LTSP configuration associated with a given
5819 machine, as long as the required attributes are available in a
5820 auxiliary object class.&lt;/p&gt;
5821 </description>
5822 </item>
5823
5824 <item>
5825 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
5826 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
5827 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
5828 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
5829 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
5830 DHCP services in Debian Edu to use the same LDAP objects for a given
5831 computer, to avoid the possibility of having a inconsistent state for
5832 a computer in LDAP (as in DHCP but no DNS entry or the other way
5833 around) and make it easier to add computers to LDAP.&lt;/p&gt;
5834
5835 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
5836 information finally found a solution that seem to work.&lt;/p&gt;
5837
5838 &lt;p&gt;The old setup required three LDAP objects for a given computer.
5839 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
5840 we switch powerdns to use its strict LDAP method (ldap-method=strict
5841 in pdns-debian-edu.conf), the forward and reverse DNS entries are
5842 merged into one while making it impossible to transfer the reverse map
5843 to a slave DNS server.&lt;/p&gt;
5844
5845 &lt;p&gt;If we also replace the object class used to get the DNS related
5846 attributes to one allowing these attributes to be combined with the
5847 dhcphost object class, we can merge the DNS and DHCP entries into one.
5848 I&#39;ve written such object class in the dnsdomainaux.schema file (need
5849 proper OIDs, but that is a minor issue), and tested the setup. It
5850 seem to work.&lt;/p&gt;
5851
5852 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
5853 for both DNS and DHCP, and even the LTSP configuration I suggested in
5854 an earlier email. The combined LDAP object will look something like
5855 this:&lt;/p&gt;
5856
5857 &lt;blockquote&gt;&lt;pre&gt;
5858 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5859 cn: hostname
5860 objectClass: dhcphost
5861 objectclass: domainrelatedobject
5862 objectclass: dnsdomainaux
5863 associateddomain: hostname.intern
5864 arecord: 10.11.12.13
5865 dhcphwaddress: ethernet 00:00:00:00:00:00
5866 dhcpstatements: fixed-address hostname
5867 ldapconfigsound: Y
5868 &lt;/pre&gt;&lt;/blockquote&gt;
5869
5870 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
5871 the DHCP server uses the dhcphwaddress and dhcpstatements entries
5872 before asking DNS to resolve the fixed-adddress. LTSP will use
5873 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
5874
5875 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
5876 dhcphost in a different location, to allow us to put the objects
5877 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
5878 that. If I can&#39;t figure out a way to do that, we can still get rid of
5879 the hosts subtree and move all its content into the DHCP Config tree
5880 (which probably should be renamed to be more related to the new
5881 content. I suspect cn=dnsdhcp,ou=services or something like that
5882 might be a good place to put it.&lt;/p&gt;
5883
5884 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
5885 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5886 </description>
5887 </item>
5888
5889 <item>
5890 <title>Idea for storing LTSP configuration in LDAP</title>
5891 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
5892 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
5893 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
5894 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
5895 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
5896 clients, and that this can be used to fetch configuration from LDAP if
5897 Debian Edu choose to store configuration there.&lt;/p&gt;
5898
5899 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
5900 to get configuration from LDAP. The idea is to look up the MAC
5901 address of the client in LDAP, and look for attributes on the form
5902 ltspconfigsetting=value, and use this to export SETTING=value to the
5903 LTSP clients.&lt;/p&gt;
5904
5905 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
5906 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
5907 allowing us to store all information about a computer in one place.&lt;/p&gt;
5908
5909 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
5910 this approach. A real LDAP schema for the ltspClientAux objectclass
5911 need to be written. Comments, suggestions, etc?&lt;/p&gt;
5912
5913 &lt;blockquote&gt;&lt;pre&gt;
5914 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
5915 #
5916 # Fetch LTSP client settings from LDAP based on MAC address
5917 #
5918 # Uses ethernet address as stored in the dhcpHost objectclass using
5919 # the dhcpHWAddress attribute or ethernet address stored in the
5920 # ieee802Device objectclass with the macAddress attribute.
5921 #
5922 # This module is written to be schema agnostic, and only depend on the
5923 # existence of attribute names.
5924 #
5925 # The LTSP configuration variables are saved directly using a
5926 # ltspConfig prefix and uppercasing the rest of the attribute name.
5927 # To set the SERVER variable, set the ltspConfigServer attribute.
5928 #
5929 # Some LDAP schema should be created with all the relevant
5930 # configuration settings. Something like this should work:
5931 #
5932 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
5933 # SUP top
5934 # AUXILIARY
5935 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
5936
5937 LDAPSERVER=$(debian-edu-ldapserver)
5938 if [ &quot;$LDAPSERVER&quot; ] ; then
5939 LDAPBASE=$(debian-edu-ldapserver -b)
5940 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
5941 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
5942 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
5943 grep &#39;^ltspConfig&#39; | while read attr value ; do
5944 # Remove prefix and convert to upper case
5945 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
5946 # bass value on to clients
5947 eval &quot;$attr=$value; export $attr&quot;
5948 done
5949 done
5950 fi
5951 &lt;/pre&gt;&lt;/blockquote&gt;
5952
5953 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
5954 the while block might end up in a subshell causing the variables set
5955 there to not show up in ltsp-config, but if that is the case I am sure
5956 the code can be restructured to make sure the variables are passed on.
5957 I expect that can be solved with some testing. :)&lt;/p&gt;
5958
5959 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
5960 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5961
5962 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
5963 configuration in LDAP that was created around year 2000 by
5964 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
5965 Xperience, Inc., 2000&lt;/a&gt;. I found its
5966 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
5967 personal home page over at redhat.com.&lt;/p&gt;
5968 </description>
5969 </item>
5970
5971 <item>
5972 <title>jXplorer, a very nice LDAP GUI</title>
5973 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
5974 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
5975 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
5976 <description>&lt;p&gt;Since
5977 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
5978 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
5979 LDAP GUI that is even better than luma. The java application
5980 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
5981 moving LDAP objects and subtrees using drag-and-drop, and can
5982 authenticate using Kerberos. I have only tested the Kerberos
5983 authentication, but do not have a LDAP setup allowing me to rewrite
5984 LDAP with my test user yet. It is
5985 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
5986 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
5987 have with it is how it handle errors. If something go wrong, its
5988 non-intuitive behaviour require me to go through some query work list
5989 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
5990 </description>
5991 </item>
5992
5993 <item>
5994 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
5995 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
5996 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
5997 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
5998 <description>&lt;p&gt;Here is a short update on my &lt;a
5999 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
6000 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
6001 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
6002 not reporting the status for KDE, because the upgrade crashes when
6003 aptitude try because of missing conflicts
6004 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
6005 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
6006
6007 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
6008 complete list of the installed packages. Based on this I see these
6009 differences when I did a test run today. As usual, I do not really
6010 know what the correct set of packages would be, but thought it best to
6011 publish the difference.&lt;/p&gt;
6012
6013 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6014
6015 &lt;blockquote&gt;&lt;p&gt;
6016 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
6017 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
6018 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
6019 libgtksourceview-common libpt-1.10.10-plugins-alsa
6020 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
6021 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
6022 python-4suite-xml python-eggtrayicon python-gtkhtml2
6023 python-gtkmozembed svgalibg1 xserver-xephyr zip
6024 &lt;/p&gt;&lt;/blockquote&gt;
6025
6026 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6027
6028 &lt;blockquote&gt;&lt;p&gt;
6029 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
6030 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
6031 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
6032 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
6033 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
6034 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
6035 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
6036 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
6037 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
6038 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
6039 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
6040 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
6041 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
6042 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
6043 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
6044 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
6045 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
6046 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
6047 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
6048 mysql-common swfdec-gnome totem-gstreamer wodim
6049 &lt;/p&gt;&lt;/blockquote&gt;
6050
6051 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6052
6053 &lt;blockquote&gt;&lt;p&gt;
6054 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
6055 python-gnomekeyring python-wnck rhythmbox-plugins xorg
6056 xserver-xorg-input-all xserver-xorg-input-evdev
6057 xserver-xorg-input-kbd xserver-xorg-input-mouse
6058 xserver-xorg-input-synaptics xserver-xorg-video-all
6059 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
6060 xserver-xorg-video-chips xserver-xorg-video-cirrus
6061 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6062 xserver-xorg-video-glint xserver-xorg-video-i128
6063 xserver-xorg-video-i740 xserver-xorg-video-mach64
6064 xserver-xorg-video-mga xserver-xorg-video-neomagic
6065 xserver-xorg-video-nouveau xserver-xorg-video-nv
6066 xserver-xorg-video-r128 xserver-xorg-video-radeon
6067 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6068 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6069 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6070 xserver-xorg-video-sis xserver-xorg-video-sisusb
6071 xserver-xorg-video-tdfx xserver-xorg-video-tga
6072 xserver-xorg-video-trident xserver-xorg-video-tseng
6073 xserver-xorg-video-vesa xserver-xorg-video-vmware
6074 xserver-xorg-video-voodoo
6075 &lt;/p&gt;&lt;/blockquote&gt;
6076
6077 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6078
6079 &lt;blockquote&gt;&lt;p&gt;
6080 deskbar-applet xserver-xorg xserver-xorg-core
6081 xserver-xorg-input-wacom xserver-xorg-video-intel
6082 xserver-xorg-video-openchrome
6083 &lt;/p&gt;&lt;/blockquote&gt;
6084
6085 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6086 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6087 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6088 No idea when it hits Squeeze, but when it does I hope it will reduce
6089 the difference somewhat.
6090 </description>
6091 </item>
6092
6093 <item>
6094 <title>LUMA, a very nice LDAP GUI</title>
6095 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6096 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6097 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6098 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6099 directory in Debian Edu, and in the process I started to miss a GUI
6100 tool to browse the LDAP tree. The only one I was able to find in
6101 Debian/Squeeze and Lenny is
6102 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6103 be a great tool to get a overview of the current LDAP directory
6104 populated by default in Skolelinux. Thanks to it, I have been able to
6105 find empty and obsolete subtrees, misplaced objects and duplicate
6106 objects. It will be installed by default in Debian/Squeeze. If you
6107 are working with LDAP, give it a go. :)&lt;/p&gt;
6108
6109 &lt;p&gt;I did notice one problem with it I have not had time to report to
6110 the BTS yet. There is no .desktop file in the package, so the tool do
6111 not show up in the Gnome and KDE menus, but only deep down in in the
6112 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6113 released.&lt;/p&gt;
6114
6115 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6116 like to move objects and remove subtrees directly in the GUI, but have
6117 not found a way to do that with LUMA yet. So in the mean time, I use
6118 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6119
6120 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6121 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6122
6123 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6124 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6125 useful GUI alternative. It seem like a good tool, but is unmaintained
6126 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6127 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6128 </description>
6129 </item>
6130
6131 <item>
6132 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6133 <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>
6134 <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>
6135 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6136 <description>&lt;p&gt;A while back, I
6137 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6138 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6139 for storing DNS and DHCP information in LDAP to combine the two sets
6140 of information into one LDAP object representing a computer.&lt;/p&gt;
6141
6142 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6143 the dhcpHost object class auxiliary, to allow it to be combined with
6144 the dNSDomain object class, and thus forming one object for one
6145 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6146
6147 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6148 without also changing the assigned number for the object class, and I
6149 do not know enough about LDAP schema design to do that properly for
6150 Debian Edu.&lt;/p&gt;
6151
6152 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6153 the
6154 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6155 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6156 available today from IETF.&lt;/p&gt;
6157
6158 &lt;pre&gt;
6159 --- dhcp.schema (revision 65192)
6160 +++ dhcp.schema (working copy)
6161 @@ -376,7 +376,7 @@
6162 objectclass ( 2.16.840.1.113719.1.203.6.6
6163 NAME &#39;dhcpHost&#39;
6164 DESC &#39;This represents information about a particular client&#39;
6165 - SUP top
6166 + SUP top AUXILIARY
6167 MUST cn
6168 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6169 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6170 &lt;/pre&gt;
6171
6172 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6173 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6174 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6175
6176 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6177 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6178 </description>
6179 </item>
6180
6181 <item>
6182 <title>Calling tasksel like the installer, while still getting useful output</title>
6183 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6184 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6185 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6186 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6187 installs packages during the normal debian-installer run. Until now,
6188 I have ended up letting tasksel do the work, with the annoying problem
6189 of not getting any feedback at all when something fails (like a
6190 conffile question from dpkg or a download that fails), using code like
6191 this:
6192
6193 &lt;blockquote&gt;&lt;pre&gt;
6194 export DEBIAN_FRONTEND=noninteractive
6195 tasksel --new-install
6196 &lt;/pre&gt;&lt;/blockquote&gt;
6197
6198 This would invoke tasksel, let its automatic task selection pick the
6199 tasks to install, and continue to install the requested tasks without
6200 any output what so ever.
6201
6202 Recently I revisited this problem while working on the automatic
6203 package upgrade testing, because tasksel would some times hang without
6204 any useful feedback, and I want to see what is going on when it
6205 happen. Then it occured to me, I can parse the output from tasksel
6206 when asked to run in test mode, and use that aptitude command line
6207 printed by tasksel then to simulate the tasksel run. I ended up using
6208 code like this:
6209
6210 &lt;blockquote&gt;&lt;pre&gt;
6211 export DEBIAN_FRONTEND=noninteractive
6212 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6213 $cmd
6214 &lt;/pre&gt;&lt;/blockquote&gt;
6215
6216 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6217 --without-recommends -o APT::Install-Recommends=no -y install
6218 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6219 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6220 laptop task and all packages with priority standard , required and
6221 important, just like tasksel would have done it during
6222 installation.&lt;/p&gt;
6223
6224 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6225 install packages without using debconf-apt-progress, for use cases
6226 like this.&lt;/p&gt;
6227 </description>
6228 </item>
6229
6230 <item>
6231 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6232 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6233 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6234 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6235 <description>&lt;p&gt;My
6236 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6237 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6238 finally made the upgrade logs available from
6239 &lt;a href=&quot;http://people.skolelinux.org/pere/debian-upgrade-testing/&quot;&gt;http://people.skolelinux.org/pere/debian-upgrade-testing/&lt;/a&gt;.
6240 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6241 apt and aptitude, and found their differences interesting. This time
6242 I will only focus on their removal plans.&lt;/p&gt;
6243
6244 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6245 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6246 surprising part is that it want to remove xorg and all
6247 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6248 sure why. When asking aptitude to do the same, it want to remove 129
6249 packages, but most of them are library packages I suspect are no
6250 longer needed. Both of them want to remove bluetooth packages, which
6251 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6252
6253 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6254 which seem like a bad idea and xorg the same way as with Gnome. Asking
6255 aptitude for the same, it wants to remove 192 packages, none which are
6256 too surprising.&lt;/p&gt;
6257
6258 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6259 and avoided, and perhaps others as well. Here are the complete list
6260 of planned removals. The complete logs is available from the URL
6261 above. Note if you want to repeat these tests, that the upgrade test
6262 for kde+apt-get hung in the tasksel setup because of dpkg asking
6263 conffile questions. No idea why. I worked around it by using
6264 &#39;&lt;tt&gt;echo &gt;&gt; /proc/&lt;em&gt;pidofdpkg&lt;/em&gt;/fd/0&lt;/tt&gt;&#39; to tell dpkg to
6265 continue.&lt;/p&gt;
6266
6267 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6268 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6269 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6270 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6271 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6272 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6273 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6274 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6275 xserver-xorg-input-kbd xserver-xorg-input-mouse
6276 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6277 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6278 xserver-xorg-video-ati xserver-xorg-video-chips
6279 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6280 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6281 xserver-xorg-video-glint xserver-xorg-video-i128
6282 xserver-xorg-video-i740 xserver-xorg-video-imstt
6283 xserver-xorg-video-intel xserver-xorg-video-mach64
6284 xserver-xorg-video-mga xserver-xorg-video-neomagic
6285 xserver-xorg-video-nsc xserver-xorg-video-nv
6286 xserver-xorg-video-openchrome xserver-xorg-video-r128
6287 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6288 xserver-xorg-video-rendition xserver-xorg-video-s3
6289 xserver-xorg-video-s3virge xserver-xorg-video-savage
6290 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6291 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6292 xserver-xorg-video-tga xserver-xorg-video-trident
6293 xserver-xorg-video-tseng xserver-xorg-video-v4l
6294 xserver-xorg-video-vesa xserver-xorg-video-vga
6295 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6296 xulrunner-1.9-gnome-support&lt;/p&gt;
6297
6298 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6299
6300 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6301 djvulibre-desktop finger gnome-app-install gnome-mount
6302 gnome-network-admin gnome-spell gnome-vfs-obexftp
6303 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6304 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6305 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6306 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6307 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6308 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6309 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6310 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6311 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6312 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6313 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6314 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6315 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6316 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6317 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6318 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6319 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6320 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6321 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6322 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6323 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6324 openoffice.org-writer2latex openssl-blacklist p7zip
6325 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6326 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6327 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6328 swfdec-mozilla totem-gstreamer update-manager wodim
6329 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6330 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6331 zip&lt;/p&gt;
6332
6333 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6334
6335 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6336 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6337 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6338 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6339 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6340 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6341 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6342 xserver-xorg-input-kbd xserver-xorg-input-mouse
6343 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6344 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6345 xserver-xorg-video-ati xserver-xorg-video-chips
6346 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6347 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6348 xserver-xorg-video-glint xserver-xorg-video-i128
6349 xserver-xorg-video-i740 xserver-xorg-video-imstt
6350 xserver-xorg-video-intel xserver-xorg-video-mach64
6351 xserver-xorg-video-mga xserver-xorg-video-neomagic
6352 xserver-xorg-video-nsc xserver-xorg-video-nv
6353 xserver-xorg-video-openchrome xserver-xorg-video-r128
6354 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6355 xserver-xorg-video-rendition xserver-xorg-video-s3
6356 xserver-xorg-video-s3virge xserver-xorg-video-savage
6357 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6358 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6359 xserver-xorg-video-tga xserver-xorg-video-trident
6360 xserver-xorg-video-tseng xserver-xorg-video-v4l
6361 xserver-xorg-video-vesa xserver-xorg-video-vga
6362 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6363
6364 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6365 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6366 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6367 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6368 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6369 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6370 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6371 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6372 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6373 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6374 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6375 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6376 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6377 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6378 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6379 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6380 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6381 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6382 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6383 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6384 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6385 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6386 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6387 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6388 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6389 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6390 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6391 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6392 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6393 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6394 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6395 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6396 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6397 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6398 texlive-common texlive-doc-base texlive-fonts-recommended
6399 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6400 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6401 xulrunner-1.9&lt;/p&gt;
6402
6403 </description>
6404 </item>
6405
6406 <item>
6407 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6408 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6409 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6410 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6411 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6412 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6413 have been discovered and reported in the process
6414 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
6415 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
6416 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
6417 kdebase-workspace-data), and to get a more regular testing going on, I
6418 am working on a script to automate the test.&lt;/p&gt;
6419
6420 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
6421 Gnome or KDE desktop installation inside the chroot before upgrading
6422 it. To ensure no services are started in the chroot, a policy-rc.d
6423 script is inserted. To make sure tasksel believe it is to install a
6424 desktop on a laptop, the tasksel tests are replaced in the chroot
6425 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
6426
6427 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6428 currently always fail because udev refuses to upgrade with the kernel
6429 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6430 is created. The bug report
6431 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
6432 this problem do not trigger in a chroot, but I touch the file anyway
6433 to make sure the upgrade go well. Testing on virtual and real
6434 hardware have failed me because of udev so far, and creating this file
6435 do the trick in such settings anyway. This is a
6436 &lt;a href=&quot;http://www.linuxquestions.org/questions/debian-26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-804130/&quot;&gt;known
6437 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
6438 maintainer because he lack the resources to rewrite udev to keep
6439 working with old kernels or something like that. I really wish the
6440 udev upstream would keep udev backwards compatible, to avoid such
6441 upgrade problem, but given that they fail to do so, I guess
6442 documenting the way out of this mess is the best option we got for
6443 Debian Squeeze.&lt;/p&gt;
6444
6445 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
6446 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
6447 trick:&lt;/p&gt;
6448
6449 &lt;blockquote&gt;&lt;pre&gt;
6450 #!/bin/sh
6451 set -ex
6452
6453 if [ &quot;$1&quot; ] ; then
6454 desktop=$1
6455 else
6456 desktop=gnome
6457 fi
6458
6459 from=lenny
6460 to=squeeze
6461
6462 exec &amp;lt; /dev/null
6463 unset LANG
6464 mirror=http://ftp.skolelinux.org/debian
6465 tmpdir=chroot-$from-upgrade-$to-$desktop
6466 fuser -mv .
6467 debootstrap $from $tmpdir $mirror
6468 chroot $tmpdir aptitude update
6469 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
6470 #!/bin/sh
6471 exit 101
6472 EOF
6473 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6474 exit_cleanup() {
6475 umount $tmpdir/proc
6476 }
6477 mount -t proc proc $tmpdir/proc
6478 # Make sure proc is unmounted also on failure
6479 trap exit_cleanup EXIT INT
6480
6481 chroot $tmpdir aptitude -y install debconf-utils
6482
6483 # Make sure tasksel autoselection trigger. It need the test scripts
6484 # to return the correct answers.
6485 echo tasksel tasksel/desktop multiselect $desktop | \
6486 chroot $tmpdir debconf-set-selections
6487
6488 # Include the desktop and laptop task
6489 for test in desktop laptop ; do
6490 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
6491 #!/bin/sh
6492 exit 2
6493 EOF
6494 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6495 done
6496
6497 DEBIAN_FRONTEND=noninteractive
6498 DEBIAN_PRIORITY=critical
6499 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6500 chroot $tmpdir tasksel --new-install
6501
6502 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
6503 chroot $tmpdir aptitude update
6504 touch $tmpdir/etc/udev/kernel-upgrade
6505 chroot $tmpdir aptitude -y dist-upgrade
6506 fuser -mv
6507 &lt;/pre&gt;&lt;/blockquote&gt;
6508
6509 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
6510 with aptitude, but I have not had time to look at how they behave
6511 differently so far. I hope to get a cron job running to do the test
6512 regularly and post the result on the web. The Gnome upgrade currently
6513 work, while the KDE upgrade fail because of the bug in
6514 kdebase-workspace-data&lt;/p&gt;
6515
6516 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
6517 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
6518 post, so I will refrain from trying. I can report that for Gnome,
6519 aptitude report 760 packages upgraded, 448 newly installed, 129 to
6520 remove and 1 not upgraded and 1024MB need to be downloaded while for
6521 KDE the same numbers are 702 packages upgraded, 507 newly installed,
6522 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
6523
6524 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
6525 is able to migrate to dependency based boot sequencing and parallel
6526 booting without a hitch. Was unsure if there were still bugs with
6527 packages failing to clean up their obsolete init.d script during
6528 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6529 packages.&lt;/p&gt;
6530 </description>
6531 </item>
6532
6533 <item>
6534 <title>Upstart or sysvinit - as init.d scripts see it</title>
6535 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
6536 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
6537 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
6538 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
6539 scripts to migrate (some of) their operations to upstart job while
6540 keeping the init.d for hurd and kfreebsd. The packages with such
6541 needs will need a way to get their init.d scripts to behave
6542 differently when used with sysvinit and with upstart. Because of
6543 this, I had a look at the environment variables set when a init.d
6544 script is running under upstart, and when it is not.&lt;/p&gt;
6545
6546 &lt;p&gt;With upstart, I notice these environment variables are set when a
6547 script is started from rcS.d/ (ignoring some irrelevant ones like
6548 COLUMNS):&lt;/p&gt;
6549
6550 &lt;blockquote&gt;&lt;pre&gt;
6551 DEFAULT_RUNLEVEL=2
6552 previous=N
6553 PREVLEVEL=
6554 RUNLEVEL=
6555 runlevel=S
6556 UPSTART_EVENTS=startup
6557 UPSTART_INSTANCE=
6558 UPSTART_JOB=rc-sysinit
6559 &lt;/pre&gt;&lt;/blockquote&gt;
6560
6561 &lt;p&gt;With sysvinit, these environment variables are set for the same
6562 script.&lt;/p&gt;
6563
6564 &lt;blockquote&gt;&lt;pre&gt;
6565 INIT_VERSION=sysvinit-2.88
6566 previous=N
6567 PREVLEVEL=N
6568 RUNLEVEL=S
6569 runlevel=S
6570 &lt;/pre&gt;&lt;/blockquote&gt;
6571
6572 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
6573 sysvinit are not set by upstart. Not sure if it is intentional or not
6574 to not be compatible with sysvinit in this regard.&lt;/p&gt;
6575
6576 &lt;p&gt;For scripts needing to behave differently when upstart is used,
6577 looking for the UPSTART_JOB environment variable seem to be a good
6578 choice.&lt;/p&gt;
6579 </description>
6580 </item>
6581
6582 <item>
6583 <title>A manual for standards wars...</title>
6584 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
6585 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
6586 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
6587 <description>&lt;p&gt;Via the
6588 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
6589 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
6590 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
6591 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
6592 following the standards wars of today.&lt;/p&gt;
6593 </description>
6594 </item>
6595
6596 <item>
6597 <title>Sitesummary tip: Listing computer hardware models used at site</title>
6598 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
6599 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
6600 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
6601 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
6602 to get a list of the machine types in use thanks to the DMI
6603 information extracted from each machine. The script to do so is
6604 included in the sitesummary package, and here is example output from
6605 the Skolelinux build servers:&lt;/p&gt;
6606
6607 &lt;blockquote&gt;&lt;pre&gt;
6608 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6609 vendor count
6610 Dell Computer Corporation 1
6611 PowerEdge 1750 1
6612 IBM 1
6613 eserver xSeries 345 -[8670M1X]- 1
6614 Intel 2
6615 [no-dmi-info] 3
6616 maintainer:~#
6617 &lt;/pre&gt;&lt;/blockquote&gt;
6618
6619 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
6620 provided in each machine. Here there are Intel machines without model
6621 information listed with Intel as vendor and no model, and virtual Xen
6622 machines listed as [no-dmi-info]. One can add -l as a command line
6623 option to list the individual machines.&lt;/p&gt;
6624
6625 &lt;p&gt;A larger list is
6626 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
6627 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
6628 provide the basic sitesummary report publicly. In their report there
6629 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
6630 their machines, and as sitesummary is available in both distributions,
6631 it is trivial to get all of them to report to the same central
6632 collector.&lt;/p&gt;
6633 </description>
6634 </item>
6635
6636 <item>
6637 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
6638 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
6639 <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>
6640 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
6641 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
6642 start at boot when an NVidia video card is used is handled. The
6643 problem seem to be that the nvidia X.org driver uses a long time to
6644 initialize, and this duration is longer than kdm is configured to
6645 wait.&lt;/p&gt;
6646
6647 &lt;p&gt;I came across two bugs related to this issue,
6648 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
6649 against initscripts and passed on to nvidia-glx when it became obvious
6650 that the nvidia drivers were involved, and
6651 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
6652 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
6653
6654 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
6655 problem nvidia video card owners experience and make sure the Debian
6656 distribution work out of the box for these users. The nvidia driver
6657 maintainers expect kdm to be set up to wait longer, while kdm expect
6658 the nvidia driver maintainers to fix the driver to start faster, and
6659 while they wait for each other I guess the users end up switching to a
6660 distribution that work for them. I have no idea what the solution is,
6661 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
6662
6663 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
6664 </description>
6665 </item>
6666
6667 <item>
6668 <title>Parallellized boot seem to hold up well in Debian/testing</title>
6669 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
6670 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
6671 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
6672 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
6673 The feature seem to hold up pretty well, but three fairly serious
6674 issues are known and should be solved:
6675
6676 &lt;p&gt;&lt;ul&gt;
6677
6678 &lt;li&gt;The wicd package seen to
6679 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
6680 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
6681 parallel booting is enabled. No idea why, but the wicd maintainer
6682 seem to be on the case.&lt;/li&gt;
6683
6684 &lt;li&gt;The nvidia X driver seem to
6685 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
6686 triggered more easily when parallel booting is in effect. The
6687 maintainer is on the case.&lt;/li&gt;
6688
6689 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
6690 sequencing (the shutdown is broken) when old file-rc users
6691 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
6692 sysv-rc. One way to solve it would be for file-rc to create
6693 /etc/init.d/.legacy-bootordering, and another is to try to make
6694 sysv-rc more robust. Will investigate some more and probably upload a
6695 workaround in sysv-rc to help those trying to move from file-rc to
6696 sysv-rc get a working shutdown.&lt;/li&gt;
6697
6698 &lt;/ul&gt;&lt;/p&gt;
6699
6700 &lt;p&gt;All in all not many surprising issues, and all of them seem
6701 solvable before Squeeze is released. In addition to these there are
6702 some packages with bugs in their dependencies and run level settings,
6703 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
6704
6705 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6706 the BTS, please usertag the report to get it to show up at
6707 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6708 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6709
6710 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
6711 </description>
6712 </item>
6713
6714 <item>
6715 <title>More flexible firmware handling in debian-installer</title>
6716 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
6717 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
6718 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
6719 <description>&lt;p&gt;After a long break from debian-installer development, I finally
6720 found time today to return to the project. Having to spend less time
6721 working dependency based boot in debian, as it is almost complete now,
6722 definitely helped freeing some time.&lt;/p&gt;
6723
6724 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
6725 include some firmware packages on the Debian Edu CDs, those needed to
6726 get disk and network controllers working. Without having these
6727 firmware packages available during installation, it is impossible to
6728 install Debian Edu on the given machine, and because our target group
6729 are non-technical people, asking them to provide firmware packages on
6730 an external medium is a support pain. Initially, I expected it to be
6731 enough to include the firmware packages on the CD to get
6732 debian-installer to find and use them. This proved to be wrong.
6733 Next, I hoped it was enough to symlink the relevant firmware packages
6734 to some useful location on the CD (tried /cdrom/ and
6735 /cdrom/firmware/). This also proved to not work, and at this point I
6736 found time to look at the debian-installer code to figure out what was
6737 going to work.&lt;/p&gt;
6738
6739 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
6740 look revealed that it would only look for firmware packages outside
6741 the installation media, so the CD was never checked for firmware
6742 packages. It would only check USB sticks, floppies and other
6743 &quot;external&quot; media devices. Today I changed it to also look in the
6744 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6745 solve the problem I ran into with Debian edu. I also changed it to
6746 look in /firmware/, to make sure the installer also find firmware
6747 provided in the initrd when booting the installer via PXE, to allow us
6748 to provide the same feature in the PXE setup included in Debian
6749 Edu.&lt;/p&gt;
6750
6751 &lt;p&gt;To make sure firmware deb packages with a license questions are not
6752 activated without asking if the license is accepted, I extended
6753 hw-detect to look for preinst scripts in the firmware packages, and
6754 run these before activating the firmware during installation. The
6755 license question is asked using debconf in the preinst, so this should
6756 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
6757
6758 &lt;p&gt;If you want to discuss the details of these features, please
6759 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
6760 </description>
6761 </item>
6762
6763 <item>
6764 <title>Parallellized boot is now the default in Debian/unstable</title>
6765 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
6766 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
6767 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
6768 <description>&lt;p&gt;Since this evening, parallel booting is the default in
6769 Debian/unstable for machines using dependency based boot sequencing.
6770 Apparently the testing of concurrent booting has been wider than
6771 expected, if I am to believe the
6772 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6773 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
6774 with the feature this weekend, to give us some time to detect any
6775 remaining problems before Squeeze is frozen. If serious problems are
6776 detected, it is simple to change the default back to sequential boot.
6777 The upload of the new sysvinit package also activate a new upstream
6778 version.&lt;/p&gt;
6779
6780 More information about
6781 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6782 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
6783 currently possible to disable parallel booting when one run into
6784 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
6785
6786 &lt;blockquote&gt;&lt;pre&gt;
6787 CONCURRENCY=none
6788 &lt;/pre&gt;&lt;/blockquote&gt;
6789
6790 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6791 the BTS, please usertag the report to get it to show up at
6792 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6793 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6794 </description>
6795 </item>
6796
6797 <item>
6798 <title>Sitesummary tip: Listing MAC address of all clients</title>
6799 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
6800 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
6801 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
6802 <description>&lt;p&gt;In the recent Debian Edu versions, the
6803 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
6804 system&lt;/a&gt; is used to keep track of the machines in the school
6805 network. Each machine will automatically report its status to the
6806 central server after boot and once per night. The network setup is
6807 also reported, and using this information it is possible to get the
6808 MAC address of all network interfaces in the machines. This is useful
6809 to update the DHCP configuration.&lt;/p&gt;
6810
6811 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
6812 ist all MAC addresses of all machines reporting to sitesummary. Run
6813 this on the collector host:&lt;/p&gt;
6814
6815 &lt;blockquote&gt;&lt;pre&gt;
6816 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
6817 &lt;/pre&gt;&lt;/blockquote&gt;
6818
6819 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
6820 line per machine and with space between the MAC addresses.&lt;/p&gt;
6821
6822 &lt;p&gt;To allow system administrators easier job at adding static DHCP
6823 addresses for hosts, it would be possible to extend this to fetch
6824 machine information from sitesummary and update the DHCP and DNS
6825 tables in LDAP using this information. Such tool is unfortunately not
6826 written yet.&lt;/p&gt;
6827 </description>
6828 </item>
6829
6830 <item>
6831 <title>systemd, an interesting alternative to upstart</title>
6832 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
6833 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
6834 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
6835 <description>&lt;p&gt;The last few days a new boot system called
6836 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
6837 has been
6838 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
6839
6840 to the free software world. I have not yet had time to play around
6841 with it, but it seem to be a very interesting alternative to
6842 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
6843 a good alternative for Debian when we are able to switch to an event
6844 based boot system. Tollef is
6845 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
6846 systemd into Debian, and I look forward to seeing how well it work. I
6847 like the fact that systemd handles init.d scripts with dependency
6848 information natively, allowing them to run in parallel where upstart
6849 at the moment do not.&lt;/p&gt;
6850
6851 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
6852 platform support. It only work on recent Linux kernels, and also need
6853 some new kernel features enabled to function properly. This means
6854 kFreeBSD and Hurd ports of Debian will need a port or a different boot
6855 system. Not sure how that will be handled if systemd proves to be the
6856 way forward.&lt;/p&gt;
6857
6858 &lt;p&gt;In the mean time, based on the
6859 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6860 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
6861 decided to enable full parallel booting as the default in Debian as
6862 soon as possible (probably this weekend or early next week), to see if
6863 there are any remaining serious bugs in the init.d dependencies. A
6864 new version of the sysvinit package implementing this change is
6865 already in experimental. If all go well, Squeeze will be released
6866 with parallel booting enabled by default.&lt;/p&gt;
6867 </description>
6868 </item>
6869
6870 <item>
6871 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
6872 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
6873 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
6874 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
6875 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
6876 complete, so complete that it is actually possible to run all the
6877 init.d scripts in parallell based on these dependencies. If you want
6878 to test your Squeeze system, make sure
6879 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6880 based boot sequencing&lt;/a&gt; is enabled, and add this line to
6881 /etc/default/rcS:&lt;/p&gt;
6882
6883 &lt;blockquote&gt;&lt;pre&gt;
6884 CONCURRENCY=makefile
6885 &lt;/pre&gt;&lt;/blockquote&gt;
6886
6887 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
6888 scripts in parallel using the dependency information stored in
6889 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
6890 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
6891 to try to start the kdm and gdm scripts as early as possible, and will
6892 start the facilities required by kdm or gdm as early as possible to
6893 make this happen.&lt;/p&gt;
6894
6895 &lt;p&gt;Give it a try, and see if you like the result. If some services
6896 fail to start properly, it is most likely because they have incomplete
6897 init.d script dependencies in their startup script (or some of their
6898 dependent scripts have incomplete dependencies). Report bugs and get
6899 the package maintainers to fix it. :)&lt;/p&gt;
6900
6901 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
6902 manage to get the init.d script dependencies complete and correct. I
6903 expect we will get there in Squeeze+1, if we get manage to test and
6904 fix the remaining issues.&lt;/p&gt;
6905
6906 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6907 the BTS, please usertag the report to get it to show up at
6908 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6909 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6910 </description>
6911 </item>
6912
6913 <item>
6914 <title>Debian has switched to dependency based boot sequencing</title>
6915 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
6916 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
6917 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
6918 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
6919 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
6920 have been migrated to using dependency based boot sequencing. This
6921 conclude work me and others have been doing for the last three days.
6922 It feels great to see this finally part of the default Debian
6923 installation. Now we just need to weed out the last few problems that
6924 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
6925
6926 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
6927 fixing the more fundamental problem of handing the event based
6928 non-predictable kernel in the early boot.&lt;/p&gt;
6929 </description>
6930 </item>
6931
6932 <item>
6933 <title>Taking over sysvinit development</title>
6934 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
6935 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
6936 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
6937 <description>&lt;p&gt;After several years of frustration with the lack of activity from
6938 the existing sysvinit upstream developer, I decided a few weeks ago to
6939 take over the package and become the new upstream. The number of
6940 patches to track for the Debian package was becoming a burden, and the
6941 lack of synchronization between the distribution made it hard to keep
6942 the package up to date.&lt;/p&gt;
6943
6944 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
6945 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
6946 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
6947 and Fedora), based on the patches currently in use in these
6948 distributions. We Debian maintainers plan to move to this tarball as
6949 the new upstream as soon as we find time to do the merge. Since the
6950 new tarball was created, we agreed with Werner at SuSe to make a new
6951 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
6952 development there. The project is registered and currently waiting
6953 for approval by the Savannah administrators, and as soon as it is
6954 approved, we will import the old versions from svn and continue
6955 working on the future release.&lt;/p&gt;
6956
6957 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
6958 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
6959 </description>
6960 </item>
6961
6962 <item>
6963 <title>Debian boots quicker and quicker</title>
6964 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
6965 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
6966 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
6967 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
6968 people involved in the boot system on Debian and Ubuntu, to see if we
6969 could find more ways to speed up the boot system. This was an Ubuntu
6970 funded
6971 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
6972 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
6973 of boot systems, and ways to handle the increasing number of boot
6974 issues introduced by the Linux kernel becoming more and more
6975 asynchronous and event base. The Ubuntu approach using udev and
6976 upstart might be a good way forward. Time will show.&lt;/p&gt;
6977
6978 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
6979 process in Debian. All of these should be applied to get a quick
6980 boot:&lt;/p&gt;
6981
6982 &lt;ul&gt;
6983
6984 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
6985
6986 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
6987 clock is in UTC.&lt;/li&gt;
6988
6989 &lt;li&gt;Install and activate the insserv package to enable
6990 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6991 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
6992
6993 &lt;/ul&gt;
6994
6995 These points are based on the Google summer of code work done by
6996 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
6997 Villegas&lt;/a&gt;.
6998
6999 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
7000 unstable yesterday. When we tested it, we were able to cut 6 seconds
7001 from the boot sequence. It depend on very correct dependency
7002 declaration in all init.d scripts, so I expect us to find edge cases
7003 where the dependences in some scripts are slightly wrong when we start
7004 using this.&lt;/p&gt;
7005
7006 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
7007 introduced by Raphael Geissert today, one that could affect the
7008 startup speed as well. Instead of starting some scripts concurrently
7009 from rcS.d/ and another set of scripts from rc2.d/, it would be
7010 possible to run a of them in the same process. A quick way to test
7011 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
7012 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
7013 </description>
7014 </item>
7015
7016 <item>
7017 <title>BSAs påstander om piratkopiering møter motstand</title>
7018 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
7019 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
7020 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
7021 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
7022 programvareselskapene som Microsoft og Apple, publisert en rapport der
7023 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
7024 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
7025 dager siden kom
7026 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
7027 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
7028 dagene. Et spesielt interessant kommentar fra Sverige,
7029 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
7030 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
7031
7032 &lt;blockquote&gt;
7033 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
7034 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
7035 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
7036 exakta&quot;, säger BSAs Sverigechef John Hugosson.
7037 &lt;/blockquote&gt;
7038
7039 &lt;p&gt;Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er &lt;a
7040 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
7041 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
7042 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
7043 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
7044
7045 &lt;p&gt;Fant lenkene via &lt;a
7046 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
7047 på Slashdot&lt;/a&gt;.&lt;/p&gt;
7048 </description>
7049 </item>
7050
7051 <item>
7052 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
7053 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
7054 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
7055 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
7056 <description>&lt;p&gt;Kom over
7057 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
7058 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
7059 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
7060 jobber til daglig. En rask opptelling forteller meg at vi har 490
7061 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7062 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7063 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7064 </description>
7065 </item>
7066
7067 <item>
7068 <title>Kryptert harddisk - naturligvis</title>
7069 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7070 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7071 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7072 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7073 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7074 når en tar tap av arbeidstid, fortrolige dokumenter,
7075 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7076 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7077 til at jeg har kryptert harddisken på både kontormaskinen og min
7078 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7079 komme på avveie, den første informasjon relatert til jobben min ved
7080 Universitetet i Oslo, og den andre relatert til blant annet
7081 foreningsarbeide. Kryptering av diskene gjør at det er lite
7082 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7083 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7084 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7085 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7086 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7087 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7088 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7089 det er gjort slik jeg gjør det er minimale, og gevinstene er
7090 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7091 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7092
7093 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7094 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7095 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7096 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7097 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7098 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7099 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7100 betydelige.&lt;/p&gt;
7101 </description>
7102 </item>
7103
7104 <item>
7105 <title>Two projects that have improved the quality of free software a lot</title>
7106 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7107 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7108 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7109 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7110 quality of free software, and I wanted to mention both in case someone
7111 do not yet know them.&lt;/p&gt;
7112
7113 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7114 tool to detect and expose errors in the memory handling of programs.
7115 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7116 and it will report any problems on stdout. It is even better if the
7117 program include debug information. With debug information, it is able
7118 to report the source file name and line number where the problem
7119 occurs. It can report things like &#39;reading past memory block in file
7120 X line N, the memory block was allocated in file Y, line M&#39;, and
7121 &#39;using uninitialised value in control logic&#39;. This tool has made it
7122 trivial to investigate reproducible crash bugs in programs, and have
7123 reduced the number of this kind of bugs in free software a lot.
7124
7125 &lt;p&gt;The second one is
7126 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7127 a source code checker. It is able to process the source of a program
7128 and find problems in the logic without running the program. It
7129 started out as the Stanford Checker and became well known when it was
7130 used to find bugs in the Linux kernel. It is now a commercial tool
7131 and the company behind it is running
7132 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7133 free software community, where a lot of free software projects get
7134 their source checked for free. Several thousand defects have been
7135 found and fixed so far. It can find errors like &#39;lock L taken in file
7136 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7137 Y lines O to P can never be executed&#39;. The projects included in the
7138 community service project have managed to get rid of a lot of
7139 reliability problems thanks to Coverity.&lt;/p&gt;
7140
7141 &lt;p&gt;I believe tools like this, that are able to automatically find
7142 errors in the source, are vital to improve the quality of software and
7143 make sure we can get rid of the crashing and failing software we are
7144 surrounded by today.&lt;/p&gt;
7145 </description>
7146 </item>
7147
7148 <item>
7149 <title>No patch is not better than a useless patch</title>
7150 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7151 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7152 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7153 <description>&lt;p&gt;Julien Blache
7154 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7155 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7156 patch allow one to discuss a concrete and proposed solution, and also
7157 prove that the issue at hand is important enough for someone to spent
7158 time on fixing it. No patch do not provide any of these positive
7159 properties.&lt;/p&gt;
7160 </description>
7161 </item>
7162
7163 <item>
7164 <title>Standardize on protocols and formats, not vendors and applications</title>
7165 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7166 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7167 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7168 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7169 very good one to form a long lived computer infrastructure. It is the
7170 simple one, lost by many in todays computer industry: Standardize on
7171 open network protocols and open exchange/storage formats, not applications.
7172 Applications come and go, while protocols and files tend to stay, and
7173 thus one want to make it easy to change application and vendor, while
7174 avoiding conversion costs and locking users to a specific platform or
7175 application.&lt;/p&gt;
7176
7177 &lt;p&gt;This approach make it possible to replace the client applications
7178 independently of the server applications. One can even allow users to
7179 use several different applications as long as they handle the selected
7180 protocol and format. In the normal case, only one client application
7181 is recommended and users only get help if they choose to use this
7182 application, but those that want to deviate from the easy path are not
7183 blocked from doing so.&lt;/p&gt;
7184
7185 &lt;p&gt;It also allow us to replace the server side without forcing the
7186 users to replace their applications, and thus allow us to select the
7187 best server implementation at any moment, when scale and resouce
7188 requirements change.&lt;/p&gt;
7189
7190 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7191 open formats, but I would never recommend standardizing on a single
7192 application that do not use open network protocol or open formats.&lt;/p&gt;
7193 </description>
7194 </item>
7195
7196 <item>
7197 <title>Returning from Skolelinux developer gathering</title>
7198 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7199 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7200 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7201 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7202 Edu/Skolelinux development gathering. I got a bit done tuning the
7203 desktop, and looked into the dynamic service location protocol
7204 implementation avahi. It look like it could be useful for us. Almost
7205 30 people participated, and I believe it was a great environment to
7206 get to know the Skolelinux system. Walter Bender, involved in the
7207 development of the Sugar educational platform, presented his stuff and
7208 also helped me improve my OLPC installation. He also showed me that
7209 his Turtle Art application can be used in standalone mode, and we
7210 agreed that I would help getting it packaged for Debian. As a
7211 standalone application it would be great for Debian Edu. We also
7212 tried to get the video conferencing working with two OLPCs, but that
7213 proved to be too hard for us. The application seem to need more work
7214 before it is ready for me. I look forward to getting home and relax
7215 now. :)&lt;/p&gt;
7216 </description>
7217 </item>
7218
7219 <item>
7220 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7221 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7222 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7223 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7224 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7225 optimal. There is RFC 2307 documenting one way to store NIS maps in
7226 LDAP, and a modified version of this normally called RFC 2307bis, with
7227 some modifications to be compatible with Active Directory. The RFC
7228 specification handle the content of a lot of system databases, but do
7229 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7230
7231 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7232 we would like to store information about users, SMB clients/hosts,
7233 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7234 and LTSP configuration in LDAP. These objects have a lot in common,
7235 but with the current LDAP schemas it is not possible to have one
7236 object per entity. For example, one need to have at least three LDAP
7237 objects for a given computer, one with the SMB related stuff, one with
7238 DNS information and another with DHCP information. The schemas
7239 provided for DNS and DHCP are impossible to combine into one LDAP
7240 object. In addition, it is impossible to implement quick queries for
7241 netgroup membership, because of the way NIS triples are implemented.
7242 It just do not scale. I believe it is time for a few RFC
7243 specifications to cleam up this mess.&lt;/p&gt;
7244
7245 &lt;p&gt;I would like to have one LDAP object representing each computer in
7246 the network, and this object can then keep the SMB (ie host key), DHCP
7247 (mac address/name) and DNS (name/IP address) settings in one place.
7248 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7249
7250 &lt;p&gt;I would also like to have a quick way to map from a user or
7251 computer and to the net group this user or computer is a member.&lt;/p&gt;
7252
7253 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7254 in this regard, and the unix side need to catch up. Time to start a
7255 new IETF work group?&lt;/p&gt;
7256 </description>
7257 </item>
7258
7259 <item>
7260 <title>Endelig er Debian Lenny gitt ut</title>
7261 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7262 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7263 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7264 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7265 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7266 Et langt steg videre for Debian-prosjektet, og en rekke nye
7267 programpakker blir nå tilgjengelig for de av oss som bruker den
7268 stabile utgaven av Debian. Neste steg er nå å få
7269 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7270 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7271 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7272 slippes løs på skolene. Takk til alle debian-utviklerne som har
7273 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7274 bootsekvens tilgjengelig i stabil utgave, vha pakken
7275 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7276 </description>
7277 </item>
7278
7279 <item>
7280 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7281 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7282 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7283 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7284 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7285 Oslo. Most of Saturday was used for the general assemly for the
7286 member organization, but the rest of the weekend I used to tune the
7287 LTSP installation. LTSP now work out of the box on the 10-network.
7288 Acer Aspire One proved to be a very nice thin client, with both
7289 screen, mouse and keybard in a small box. Was working on getting the
7290 diskless workstation setup configured out of the box, but did not
7291 finish it before the weekend was up.&lt;/p&gt;
7292
7293 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7294 the Brazilian group, so that will have to wait for the next
7295 development gathering. Would love to have the Debian Edu installer
7296 automatically detect and configure a multiseat setup when it find one
7297 of these cards.&lt;/p&gt;
7298 </description>
7299 </item>
7300
7301 <item>
7302 <title>The sorry state of multimedia browser plugins in Debian</title>
7303 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7304 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7305 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7306 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7307 plugins available in Debian Lenny, to see which one we should use by
7308 default in Debian Edu. We need an embedded video playing plugin with
7309 control buttons to pause or stop the video, and capable of streaming
7310 all the multimedia content available on the web. The test results and
7311 notes are available on
7312 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7313 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7314 fill this need. My personal video player favorite, VLC, has a really
7315 bad plugin which fail on a lot of the test pages. A lot of the MIME
7316 types I would expect to work with any free software player (like
7317 video/ogg), just do not work. And simple formats like the
7318 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7319 totem and vlc plugins. I hope the situation will improve soon. No
7320 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7321
7322 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7323 be the only one fitting our needs. :/&lt;/p&gt;
7324 </description>
7325 </item>
7326
7327 </channel>
7328 </rss>