]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
f02997243042ba07f1cbeab0f8ec4068382fe5ca
[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>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
11 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
13 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
14 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
15 project&lt;/a&gt; provide a Linux solution for schools, including a
16 powerful desktop with education software, a central server providing
17 web pages, user database, user home directories, central login and PXE
18 boot of both clients without disk and the installation to install Debian
19 Edu on machines with disk (and a few other services perhaps to small
20 to mention here). We in the Debian Edu team are currently working on
21 the Jessie based version, trying to get everything in shape before the
22 freeze, to avoid having to maintain our own package repository in the
23 future. The
24 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
25 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
26 work left. Some fatal problems block testing, breaking the installer,
27 but it is possible to work around these to get anyway. Here is a
28 recipe on how to get the installation limping along.&lt;/p&gt;
29
30 &lt;p&gt;First, download the test ISO via
31 &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;,
32 &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;
33 or rsync (use
34 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
35 The ISO build was broken on Tuesday, so we do not get a new ISO every
36 12 hours or so, but thankfully the ISO we already got we are able to
37 install with some tweaking.&lt;/p&gt;
38
39 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
40 (use Alt-Ctrl-F2), run&lt;/p&gt;
41
42 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
43 nano /usr/bin/edu-eatmydata-install
44 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
45
46 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
47 optimization. Return to the installation, select the profile you want
48 and continue. Without this change, exim4-config will fail to install
49 due to a known bug in eatmydata.&lt;/p&gt;
50
51 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
52 this do not work, figure out what your correct value would be. All my
53 test machines need /dev/sda, so I have no advice if it do not fit
54 your need.&lt;/p&gt;
55
56 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
57 root after the initial boot from hard drive, and install the
58 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
59 or mate. If you want several desktop options, install more than one
60 metapackage. Once this is done, reboot and you should have a working
61 graphical login screen. This workaround should no longer be needed
62 once the education-tasks package version 1.801 enter testing in two
63 days.&lt;/p&gt;
64
65 &lt;p&gt;I believe the ISO build will start working on two days when the new
66 tasksel package enter testing and Steve McIntyre get a chance to
67 update the debian-cd git repository. The eatmydata, grub and desktop
68 issues are already fixed in unstable and testing, and should show up
69 on the ISO as soon as the ISO build start working again. Well the
70 eatmydata optimization is really just disabled. The proper fix
71 require an upload by the eatmydata maintainer applying the patch
72 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
73 The rest have proper fixes in unstable.&lt;/p&gt;
74
75 &lt;p&gt;I hope this get you going with the installation testing, as we are
76 quickly running out of time trying to get our Jessie based
77 installation ready before the distribution freeze in a month.&lt;/p&gt;
78 </description>
79 </item>
80
81 <item>
82 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
83 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
84 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
85 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
86 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
87 to handle my fairly large DVD collection. It is a nice command line
88 tool to get details about a DVD, like title, tracks, track length,
89 etc, in XML, Perl or human readable format. But lsdvd have not seen
90 any new development since 2006 and had a few irritating bugs affecting
91 its use with some DVDs. Upstream seemed to be dead, and in January I
92 sent a small probe asking for a version control repository for the
93 project, without any reply. But I use it regularly and would like to
94 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
95 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
96 the project admin, and after getting a reply from him explaining that
97 he was no longer interested in the project, I asked if I could take
98 over. And yesterday, I became project admin.&lt;/p&gt;
99
100 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
101 maintainer interested in joining forces to maintain the upstream
102 project, and I hope we can get a new release out fairly quickly,
103 collecting the patches spread around on the internet into on place.
104 I&#39;ve added the relevant Debian patches to the freshly created git
105 repository, and expect the Gentoo patches to make it too. If you got
106 a DVD collection and care about command line tools, check out
107 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
108 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
109 list&lt;/a&gt;. :)&lt;/p&gt;
110 </description>
111 </item>
112
113 <item>
114 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
115 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
116 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
117 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
118 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
119 a lot quicker. When we install more than 2000 packages in
120 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
121 tasksel in the installer, unpacking the binary packages take forever.
122 A part of the slow I/O issue was discussed in
123 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
124 much file system sync-ing done by dpkg, which is the package
125 responsible for unpacking the binary packages. Other parts (like code
126 executed by postinst scripts) might also sync to disk during
127 installation. All this sync-ing to disk do not really make sense to
128 me. If the machine crash half-way through, I start over, I do not try
129 to salvage the half installed system. So the failure sync-ing is
130 supposed to protect against, hardware or system crash, is not really
131 relevant while the installer is running.&lt;/p&gt;
132
133 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
134 system sync()-ing in a fairly non-intrusive way, without the need to
135 change the code in several packages. The idea is not new, but I have
136 not heard anyone propose the approach using dpkg-divert before. It
137 depend on the small and clever package
138 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
139 uses LD_PRELOAD to replace the system functions for syncing data to
140 disk with functions doing nothing, thus allowing programs to live
141 dangerous while speeding up disk I/O significantly. Instead of
142 modifying the implementation of dpkg, apt and tasksel (which are the
143 packages responsible for selecting, fetching and installing packages),
144 it occurred to me that we could just divert the programs away, replace
145 them with a simple shell wrapper calling
146 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
147 Two days ago I decided to test the idea, and wrapped up a simple
148 implementation for the Debian Edu udeb.&lt;/p&gt;
149
150 &lt;p&gt;The effect was stunning. In my first test it reduced the running
151 time of the pkgsel step (installing tasks) from 64 to less than 44
152 minutes (20 minutes shaved off the installation) on an old Dell
153 Latitude D505 machine. I am not quite sure what the optimised time
154 would have been, as I messed up the testing a bit, causing the debconf
155 priority to get low enough for two questions to pop up during
156 installation. As soon as I saw the questions I moved the installation
157 along, but do not know how long the question were holding up the
158 installation. I did some more measurements using Debian Edu Jessie,
159 and got these results. The time measured is the time stamp in
160 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
161 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
162 yourself. In Debian Edu, the tasksel dialog do not show up, and the
163 timing thus do not depend on how quickly the user handle the tasksel
164 dialog.&lt;/p&gt;
165
166 &lt;p&gt;&lt;table&gt;
167
168 &lt;tr&gt;
169 &lt;th&gt;Machine/setup&lt;/th&gt;
170 &lt;th&gt;Original tasksel&lt;/th&gt;
171 &lt;th&gt;Optimised tasksel&lt;/th&gt;
172 &lt;th&gt;Reduction&lt;/th&gt;
173 &lt;/tr&gt;
174
175 &lt;tr&gt;
176 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
177 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
178 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
179 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
180 &lt;/tr&gt;
181
182 &lt;tr&gt;
183 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
184 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
185 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
186 &lt;td&gt;23 min 40%&lt;/td&gt;
187 &lt;/tr&gt;
188
189 &lt;tr&gt;
190 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
191 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
192 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
193 &lt;td&gt;11 min 50%&lt;/td&gt;
194 &lt;/tr&gt;
195
196 &lt;tr&gt;
197 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
198 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
199 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
200 &lt;td&gt;2 min 33%&lt;/td&gt;
201 &lt;/tr&gt;
202
203 &lt;tr&gt;
204 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
205 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
206 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
207 &lt;td&gt;4 min 21%&lt;/td&gt;
208 &lt;/tr&gt;
209
210 &lt;/table&gt;&lt;/p&gt;
211
212 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
213 time is spent downloading packages. The connection to the Internet
214 was 100Mbit/s during testing, so downloading should not be a
215 significant factor in the measurement. Download typically took a few
216 seconds to a few minutes, depending on the amount of packages being
217 installed.&lt;/p&gt;
218
219 &lt;p&gt;The speedup is implemented by using two hooks in
220 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
221 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
222 finish-install.d hook to remove the divert at the end of the
223 installation. I picked the pre-pkgsel.d hook instead of the
224 post-base-installer.d hook because I test using an ISO without the
225 eatmydata package included, and the post-base-installer.d hook in
226 Debian Edu can only operate on packages included in the ISO. The
227 negative effect of this is that I am unable to activate this
228 optimization for the kernel installation step in d-i. If the code is
229 moved to the post-base-installer.d hook, the speedup would be larger
230 for the entire installation.&lt;/p&gt;
231
232 &lt;p&gt;I&#39;ve implemented this in the
233 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
234 git repository, and plan to provide the optimization as part of the
235 Debian Edu installation. If you want to test this yourself, you can
236 create two files in the installer (or in an udeb). One shell script
237 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
238
239 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
240 #!/bin/sh
241 set -e
242 . /usr/share/debconf/confmodule
243 info() {
244 logger -t my-pkgsel &quot;info: $*&quot;
245 }
246 error() {
247 logger -t my-pkgsel &quot;error: $*&quot;
248 }
249 override_install() {
250 apt-install eatmydata || true
251 if [ -x /target/usr/bin/eatmydata ] ; then
252 for bin in dpkg apt-get aptitude tasksel ; do
253 file=/usr/bin/$bin
254 # Test that the file exist and have not been diverted already.
255 if [ -f /target$file ] ; then
256 info &quot;diverting $file using eatmydata&quot;
257 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
258 &gt; /target$file.edu
259 chmod 755 /target$file.edu
260 in-target dpkg-divert --package debian-edu-config \
261 --rename --quiet --add $file
262 ln -sf ./$bin.edu /target$file
263 else
264 error &quot;unable to divert $file, as it is missing.&quot;
265 fi
266 done
267 else
268 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
269 fi
270 }
271
272 override_install
273 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
274
275 &lt;p&gt;To clean up, another shell script should go into
276 /usr/lib/finish-install.d/ with code like this:
277
278 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
279 #! /bin/sh -e
280 . /usr/share/debconf/confmodule
281 error() {
282 logger -t my-finish-install &quot;error: $@&quot;
283 }
284 remove_install_override() {
285 for bin in dpkg apt-get aptitude tasksel ; do
286 file=/usr/bin/$bin
287 if [ -x /target$file.edu ] ; then
288 rm /target$file
289 in-target dpkg-divert --package debian-edu-config \
290 --rename --quiet --remove $file
291 rm /target$file.edu
292 else
293 error &quot;Missing divert for $file.&quot;
294 fi
295 done
296 sync # Flush file buffers before continuing
297 }
298
299 remove_install_override
300 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
301
302 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
303 edu-eatmydata-install and call it from the pre-pkgsel.d and
304 finish-install.d scripts.&lt;/p&gt;
305
306 &lt;p&gt;By now you might ask if this change should get into the normal
307 Debian installer too? I suspect it should, but am not sure the
308 current debian-installer coordinators find it useful enough. It also
309 depend on the side effects of the change. I&#39;m not aware of any, but I
310 guess we will see if the change is safe after some more testing.
311 Perhaps there is some package in Debian depending on sync() and
312 fsync() having effect? Perhaps it should go into its own udeb, to
313 allow those of us wanting to enable it to do so without affecting
314 everyone.&lt;/p&gt;
315
316 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
317 will break installation of all programs using gnutls because of
318 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711. An updated
319 eatmydata package in Debian will solve it.&lt;/p&gt;
320 </description>
321 </item>
322
323 <item>
324 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
325 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
326 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
327 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
328 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
329 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
330 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
331 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
332 learn that there is a large set of publicly available key servers to
333 use when looking for peoples public key. So far I have used
334 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
335 were misbehaving, but those days are ended. The servers I have used
336 up until yesterday have been slow and some times unavailable. I hope
337 those problems are gone now.&lt;/p&gt;
338
339 &lt;p&gt;Behind the round robin DNS entry of the
340 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
341 there is a pool of more than 100 keyservers which are checked every
342 day to ensure they are well connected and up to date. It must be
343 better than what I have used so far. :)&lt;/p&gt;
344
345 &lt;p&gt;Yesterdays speaker told me that the service is the default
346 keyserver provided by the default configuration in GnuPG, but this do
347 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
348
349 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
350 line:&lt;/p&gt;
351
352 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
353 keyserver pool.sks-keyservers.net
354 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
355
356 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
357 entries in DNS. Just for fun, I did just that at work, so now every
358 user of GnuPG at the University of Oslo should find a OpenGPG
359 keyserver automatically should their need it:&lt;/p&gt;
360
361 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
362 % host -t srv _pgpkey-http._tcp.uio.no
363 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
364 %
365 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
366
367 &lt;p&gt;Now if only
368 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
369 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
370 very happy. It can look up a given key or search for a user ID, but I
371 normally do not want that, but to find a trust path from my key to
372 another key. Given a user ID or key ID, I would like to find (and
373 download) the keys representing a signature path from my key to the
374 key in question, to be able to get a trust path between the two keys.
375 This is as far as I can tell not possible today. Perhaps something
376 for a future version of the protocol?&lt;/p&gt;
377 </description>
378 </item>
379
380 <item>
381 <title>From English wiki to translated PDF and epub via Docbook</title>
382 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
383 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
384 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
385 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
386 project&lt;/a&gt; provide an instruction manual for teachers, system
387 administrators and other users that contain useful tips for setting up
388 and maintaining a Debian Edu installation. This text is about how the
389 text processing of this manual is handled in the project.&lt;/p&gt;
390
391 &lt;p&gt;One goal of the project is to provide information in the native
392 language of its users, and for this we need to handle translations.
393 But we also want to make sure each language contain the same
394 information, so for this we need a good way to keep the translations
395 in sync. And we want it to be easy for our users to improve the
396 documentation, avoiding the need to learn special formats or tools to
397 contribute, and the obvious way to do this is to make it possible to
398 edit the documentation using a web browser. We also want it to be
399 easy for translators to keep the translation up to date, and give them
400 help in figuring out what need to be translated. Here is the list of
401 tools and the process we have found trying to reach all these
402 goals.&lt;/p&gt;
403
404 &lt;p&gt;We maintain the authoritative source of our manual in the
405 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
406 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
407 front page with references to the different chapters, several pages
408 for each chapter, and finally one &quot;collection page&quot; gluing all the
409 chapters together into one large web page (aka
410 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
411 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
412 processing and translations. Thanks to the fact that the
413 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
414 wiki.debian.org support exporting pages in
415 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
416 the list of pages to export using the raw version of the AllInOne
417 page, loop over each of them to generate a Docbook XML version of the
418 manual. This process also download images and transform image
419 references to use the locally downloaded images. The generated
420 Docbook XML files are slightly broken, so some post-processing is done
421 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
422 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
423 a handfull of images. The XML file can now be used to generate PDF, HTML
424 and epub versions of the English manual. This is the basic step of
425 our process, making PDF (using dblatex), HTML (using xsltproc) and
426 epub (using dbtoepub) version from Docbook XML, and the resulting files
427 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
428
429 &lt;p&gt;But English documentation is not enough for us. We want translated
430 documentation too, and we want to make it easy for translators to
431 track the English original. For this we use the
432 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
433 which allow us to transform the English Docbook XML file into a
434 translation file (a .pot file), usable with the normal gettext based
435 translation tools used by those translating free software. The pot
436 file is used to create and maintain translation files (several .po
437 files), which the translations update with the native language
438 translations of all titles, paragraphs and blocks of text in the
439 original. The next step is combining the original English Docbook XML
440 and the translation file (say debian-edu-wheezy-manual.nb.po), to
441 create a translated Docbook XML file (in this case
442 debian-edu-wheezy-manual.nb.xml). This translated (or partly
443 translated, if the translation is not complete) Docbook XML file can
444 then be used like the original to create a PDF, HTML and epub version
445 of the documentation.&lt;/p&gt;
446
447 &lt;p&gt;The translators use different tools to edit the .po files. We
448 recommend using
449 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
450 while some use emacs and vi, others can use web based editors like
451 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
452 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
453 is where the .po file end up, in our git repository. Updated
454 translations can either be committed directly to git, or submitted as
455 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
456 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
457
458 &lt;p&gt;One challenge is images, which both might need to be translated (if
459 they show translated user applications), and are needed in different
460 formats when creating PDF and HTML versions (epub is a HTML version in
461 this regard). For this we transform the original PNG images to the
462 needed density and format during build, and have a way to provide
463 translated images by storing translated versions in
464 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
465 package maintainers know more.&lt;/p&gt;
466
467 &lt;p&gt;If you wonder what the result look like, we provide
468 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
469 of the documentation packages on the web&lt;/a&gt;. See for example the
470 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
471 PDF version&lt;/a&gt; or the
472 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
473 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
474 but perhaps it will be done in the future.&lt;/p&gt;
475
476 &lt;p&gt;To learn more, check out
477 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
478 debian-edu-doc package&lt;/a&gt;,
479 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
480 manual on the wiki&lt;/a&gt; and
481 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
482 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
483 </description>
484 </item>
485
486 <item>
487 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
488 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
489 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
490 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
491 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
492 related packages relevant for the computer installed automatically.
493 So I implemented one, using
494 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
495 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
496 run tasksel as user root. You should be presented with a new option,
497 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
498 select it, tasksel will install the packages isenkram claim is fit for
499 the current hardware, hot pluggable or not.&lt;p&gt;
500
501 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
502 description, and the other is the script used to extract the list of
503 packages to install. The first part is in
504 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
505 this:&lt;/p&gt;
506
507 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
508 Task: isenkram
509 Section: hardware
510 Description: Hardware specific packages (autodetected by isenkram)
511 Based on the detected hardware various hardware specific packages are
512 proposed.
513 Test-new-install: mark show
514 Relevance: 8
515 Packages: for-current-hardware
516 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
517
518 &lt;p&gt;The second part is in
519 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
520 this:&lt;/p&gt;
521
522 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
523 #!/bin/sh
524 #
525 (
526 isenkram-lookup
527 isenkram-autoinstall-firmware -l
528 ) | sort -u
529 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
530
531 &lt;p&gt;All in all, a very short and simple implementation making it
532 trivial to install the hardware dependent package we all may want to
533 have installed on our machines. I&#39;ve not been able to find a way to
534 get tasksel to tell you exactly which packages it plan to install
535 before doing the installation. So if you are curious or careful,
536 check the output from the isenkram-* command line tools first.&lt;/p&gt;
537
538 &lt;p&gt;The information about which packages are handling which hardware is
539 fetched either from the isenkram package itself in
540 /usr/share/isenkram/, from git.debian.org or from the APT package
541 database (using the Modaliases header). The APT package database
542 parsing have caused a nasty resource leak in the isenkram daemon (bugs
543 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
544 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
545 the python-apt code (bug
546 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
547 workaround I was able to get rid of the file descriptor leak and
548 reduce the memory leak from ~30 MiB per hardware detection down to
549 around 2 MiB per hardware detection. It should make the desktop
550 daemon a lot more useful. The fix is in version 0.7 uploaded to
551 unstable today.&lt;/p&gt;
552
553 &lt;p&gt;I believe the current way of mapping hardware to packages in
554 Isenkram is is a good draft, but in the future I expect isenkram to
555 use the AppStream data source for this. A proposal for getting proper
556 AppStream support into Debian is floating around as
557 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
558 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
559 project&lt;/a&gt; will take place this summer to improve the situation. I
560 look forward to seeing the result, and welcome patches for isenkram to
561 start using the information when it is ready.&lt;/p&gt;
562
563 &lt;p&gt;If you want your package to map to some specific hardware, either
564 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
565 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
566 package&lt;/a&gt; or submit a bug report with the details to the isenkram
567 package. See also
568 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
569 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
570 the information will be migrated to AppStream eventually, but for the
571 moment I got no better place to store it.&lt;/p&gt;
572 </description>
573 </item>
574
575 <item>
576 <title>FreedomBox milestone - all packages now in Debian Sid</title>
577 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
578 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
579 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
580 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
581 project&lt;/a&gt; is working on providing the software and hardware to make
582 it easy for non-technical people to host their data and communication
583 at home, and being able to communicate with their friends and family
584 encrypted and away from prying eyes. It is still going strong, and
585 today a major mile stone was reached.&lt;/p&gt;
586
587 &lt;p&gt;Today, the last of the packages currently used by the project to
588 created the system images were accepted into Debian Unstable. It was
589 the freedombox-setup package, which is used to configure the images
590 during build and on the first boot. Now all one need to get going is
591 the build code from the freedom-maker git repository and packages from
592 Debian. And once the freedombox-setup package enter testing, we can
593 build everything directly from Debian. :)&lt;/p&gt;
594
595 &lt;p&gt;Some key packages used by Freedombox are
596 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
597 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
598 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
599 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
600 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
601 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
602 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
603 are plans to integrate more packages into the setup. User
604 documentation is maintained on the Debian wiki. Please
605 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
606 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
607
608 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
609 setup, run this on a Debian machine using a user with sudo rights to
610 become root:&lt;/p&gt;
611
612 &lt;p&gt;&lt;pre&gt;
613 sudo apt-get install git vmdebootstrap mercurial python-docutils \
614 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
615 u-boot-tools
616 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
617 freedom-maker
618 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
619 &lt;/pre&gt;&lt;/p&gt;
620
621 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
622 devices. See the README in the freedom-maker git repo for more
623 details on the build. If you do not want all three images, trim the
624 make line. Note that the virtualbox-image target is not really
625 virtualbox specific. It create a x86 image usable in kvm, qemu,
626 vmware and any other x86 virtual machine environment. You might need
627 the version of vmdebootstrap in Jessie to get the build working, as it
628 include fixes for a race condition with kpartx.&lt;/p&gt;
629
630 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
631 method, boot a Debian Wheezy ISO and use this boot argument to load
632 the preseed values:&lt;/p&gt;
633
634 &lt;p&gt;&lt;pre&gt;
635 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;
636 &lt;/pre&gt;&lt;/p&gt;
637
638 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
639 it still work.&lt;/p&gt;
640
641 &lt;p&gt;If you wonder how to help, one task you could look at is using
642 systemd as the boot system. It will become the default for Linux in
643 Jessie, so we need to make sure it is usable on the Freedombox. I did
644 a simple test a few weeks ago, and noticed dnsmasq failed to start
645 during boot when using systemd. I suspect there are other problems
646 too. :) To detect problems, there is a test suite included, which can
647 be run from the plinth web interface.&lt;/p&gt;
648
649 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
650 us get the new release published. :) Please join us on
651 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
652 irc.debian.org)&lt;/a&gt; and
653 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
654 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
655 </description>
656 </item>
657
658 <item>
659 <title>S3QL, a locally mounted cloud file system - nice free software</title>
660 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
661 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
662 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
663 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
664 solution for use at home. My requirements are simple, it must be
665 cheap and locally encrypted (in other words, I keep the encryption
666 keys, the storage provider do not have access to my private files).
667 One idea me and my friends had many years ago, before the cloud
668 storage providers showed up, was to use Google mail as storage,
669 writing a Linux block device storing blocks as emails in the mail
670 service provided by Google, and thus get heaps of free space. On top
671 of this one can add encryption, RAID and volume management to have
672 lots of (fairly slow, I admit that) cheap and encrypted storage. But
673 I never found time to implement such system. But the last few weeks I
674 have looked at a system called
675 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
676 mounted network backed file system with the features I need.&lt;/p&gt;
677
678 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
679 handling several different storage providers, any with Amazon S3,
680 Google Drive or OpenStack API. There are heaps of such storage
681 providers. S3QL can also use a local directory as storage, which
682 combined with sshfs allow for file storage on any ssh server. S3QL
683 include support for encryption, compression, de-duplication, snapshots
684 and immutable file systems, allowing me to mount the remote storage as
685 a local mount point, look at and use the files as if they were local,
686 while the content is stored in the cloud as well. This allow me to
687 have a backup that should survive fire. The file system can not be
688 shared between several machines at the same time, as only one can
689 mount it at the time, but any machine with the encryption key and
690 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
691
692 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
693 package is included already. So to get started, run &lt;tt&gt;apt-get
694 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
695 Greenqloud, after reading their nice recipe on
696 &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
697 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
698 in Iceland more than those in USA when it come to keeping my personal
699 data safe and private, and thus would rather spend money on a company
700 in Iceland. Another nice recipe is available from the article
701 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
702 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
703 Admin magazine. When the provider is picked, figure out how to get
704 the API key needed to connect to the storage API. With Greencloud,
705 the key did not show up until I had added payment details to my
706 account.&lt;/p&gt;
707
708 &lt;p&gt;Armed with the API access details, it is time to create the file
709 system. First, create a new bucket in the cloud. This bucket is the
710 file system storage area. I picked a bucket name reflecting the
711 machine that was going to store data there, but any name will do.
712 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
713 the API login and password, and a locally created password. Store it
714 all in ~root/.s3ql/authinfo2 like this:
715
716 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
717 [s3c]
718 storage-url: s3c://s.greenqloud.com:443/bucket-name
719 backend-login: API-login
720 backend-password: API-password
721 fs-passphrase: local-password
722 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
723
724 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
725 but any sensible way to create a fairly random password should do it.
726 Armed with these details, it is now time to run mkfs, entering the API
727 details and password to create it:&lt;/p&gt;
728
729 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
730 # mkdir -m 700 /var/lib/s3ql-cache
731 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
732 --ssl s3c://s.greenqloud.com:443/bucket-name
733 Enter backend login:
734 Enter backend password:
735 Before using S3QL, make sure to read the user&#39;s guide, especially
736 the &#39;Important Rules to Avoid Loosing Data&#39; section.
737 Enter encryption password:
738 Confirm encryption password:
739 Generating random encryption key...
740 Creating metadata tables...
741 Dumping metadata...
742 ..objects..
743 ..blocks..
744 ..inodes..
745 ..inode_blocks..
746 ..symlink_targets..
747 ..names..
748 ..contents..
749 ..ext_attributes..
750 Compressing and uploading metadata...
751 Wrote 0.00 MB of compressed metadata.
752 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
753
754 &lt;p&gt;The next step is mounting the file system to make the storage available.
755
756 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
757 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
758 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
759 Using 4 upload threads.
760 Downloading and decompressing metadata...
761 Reading metadata...
762 ..objects..
763 ..blocks..
764 ..inodes..
765 ..inode_blocks..
766 ..symlink_targets..
767 ..names..
768 ..contents..
769 ..ext_attributes..
770 Mounting filesystem...
771 # df -h /s3ql
772 Filesystem Size Used Avail Use% Mounted on
773 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
774 #
775 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
776
777 &lt;p&gt;The file system is now ready for use. I use rsync to store my
778 backups in it, and as the metadata used by rsync is downloaded at
779 mount time, no network traffic (and storage cost) is triggered by
780 running rsync. To unmount, one should not use the normal umount
781 command, as this will not flush the cache to the cloud storage, but
782 instead running the umount.s3ql command like this:
783
784 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
785 # umount.s3ql /s3ql
786 #
787 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
788
789 &lt;p&gt;There is a fsck command available to check the file system and
790 correct any problems detected. This can be used if the local server
791 crashes while the file system is mounted, to reset the &quot;already
792 mounted&quot; flag. This is what it look like when processing a working
793 file system:&lt;/p&gt;
794
795 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
796 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
797 Using cached metadata.
798 File system seems clean, checking anyway.
799 Checking DB integrity...
800 Creating temporary extra indices...
801 Checking lost+found...
802 Checking cached objects...
803 Checking names (refcounts)...
804 Checking contents (names)...
805 Checking contents (inodes)...
806 Checking contents (parent inodes)...
807 Checking objects (reference counts)...
808 Checking objects (backend)...
809 ..processed 5000 objects so far..
810 ..processed 10000 objects so far..
811 ..processed 15000 objects so far..
812 Checking objects (sizes)...
813 Checking blocks (referenced objects)...
814 Checking blocks (refcounts)...
815 Checking inode-block mapping (blocks)...
816 Checking inode-block mapping (inodes)...
817 Checking inodes (refcounts)...
818 Checking inodes (sizes)...
819 Checking extended attributes (names)...
820 Checking extended attributes (inodes)...
821 Checking symlinks (inodes)...
822 Checking directory reachability...
823 Checking unix conventions...
824 Checking referential integrity...
825 Dropping temporary indices...
826 Backing up old metadata...
827 Dumping metadata...
828 ..objects..
829 ..blocks..
830 ..inodes..
831 ..inode_blocks..
832 ..symlink_targets..
833 ..names..
834 ..contents..
835 ..ext_attributes..
836 Compressing and uploading metadata...
837 Wrote 0.89 MB of compressed metadata.
838 #
839 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
840
841 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
842 quick, about the same speed as local file access. Uploading large
843 amount of data is to me limited by the bandwidth out of and into my
844 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
845 which is very close to my upload speed, and downloading the same
846 Debian installation ISO gave me 610 kiB/s, close to my download speed.
847 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
848 network, not the file system code. I do not know what a good cache
849 size would be, but suspect that the cache should e larger than your
850 working set.&lt;/p&gt;
851
852 &lt;p&gt;I mentioned that only one machine can mount the file system at the
853 time. If another machine try, it is told that the file system is
854 busy:&lt;/p&gt;
855
856 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
857 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
858 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
859 Using 8 upload threads.
860 Backend reports that fs is still mounted elsewhere, aborting.
861 #
862 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
863
864 &lt;p&gt;The file content is uploaded when the cache is full, while the
865 metadata is uploaded once every 24 hour by default. To ensure the
866 file system content is flushed to the cloud, one can either umount the
867 file system, or ask S3QL to flush the cache and metadata using
868 s3qlctrl:
869
870 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
871 # s3qlctrl upload-meta /s3ql
872 # s3qlctrl flushcache /s3ql
873 #
874 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
875
876 &lt;p&gt;If you are curious about how much space your data uses in the
877 cloud, and how much compression and deduplication cut down on the
878 storage usage, you can use s3qlstat on the mounted file system to get
879 a report:&lt;/p&gt;
880
881 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
882 # s3qlstat /s3ql
883 Directory entries: 9141
884 Inodes: 9143
885 Data blocks: 8851
886 Total data size: 22049.38 MB
887 After de-duplication: 21955.46 MB (99.57% of total)
888 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
889 Database size: 2.39 MB (uncompressed)
890 (some values do not take into account not-yet-uploaded dirty blocks in cache)
891 #
892 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
893
894 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
895 storage. I did not try to locate them all, but am aware of at least
896 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
897 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
898 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
899 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
900 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
901 accept payment in Bitcoin. Pick one that suit your need. Some of
902 them provide several GiB of free storage, but the prize models are
903 quite different and you will have to figure out what suits you
904 best.&lt;/p&gt;
905
906 &lt;p&gt;While researching this blog post, I had a look at research papers
907 and posters discussing the S3QL file system. There are several, which
908 told me that the file system is getting a critical check by the
909 science community and increased my confidence in using it. One nice
910 poster is titled
911 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
912 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
913 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
914 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
915 and Pamela Smith. Please have a look.&lt;/p&gt;
916
917 &lt;p&gt;Given my problems with different file systems earlier, I decided to
918 check out the mounted S3QL file system to see if it would be usable as
919 a home directory (in other word, that it provided POSIX semantics when
920 it come to locking and umask handling etc). Running
921 &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
922 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
923 no error was found. So the file system can be used for home
924 directories, if one chooses to do so.&lt;/p&gt;
925
926 &lt;p&gt;If you do not want a locally file system, and want something that
927 work without the Linux fuse file system, I would like to mention the
928 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
929 provide locally encrypted backup using a command line client. It have
930 a nicer access control system, where one can split out read and write
931 access, allowing some systems to write to the backup and others to
932 only read from it.&lt;/p&gt;
933
934 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
935 activities, please send Bitcoin donations to my address
936 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
937 </description>
938 </item>
939
940 <item>
941 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
942 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
943 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
944 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
945 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
946 project&lt;/a&gt; is working on providing the software and hardware for
947 making it easy for non-technical people to host their data and
948 communication at home, and being able to communicate with their
949 friends and family encrypted and away from prying eyes. It has been
950 going on for a while, and is slowly progressing towards a new test
951 release (0.2).&lt;/p&gt;
952
953 &lt;p&gt;And what day could be better than the Pi day to announce that the
954 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
955 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
956 system), and can also be installed using a Debian installer preseed
957 file. The Debian based Freedombox is now based on Debian Jessie,
958 where most of the needed packages used are already present. Only one,
959 the freedombox-setup package, is missing. To try to build your own
960 boot image to test the current status, fetch the freedom-maker scripts
961 and build using
962 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
963 with a user with sudo access to become root:
964
965 &lt;pre&gt;
966 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
967 freedom-maker
968 sudo apt-get install git vmdebootstrap mercurial python-docutils \
969 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
970 u-boot-tools
971 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
972 &lt;/pre&gt;
973
974 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
975 devices. See the README for more details on the build. If you do not
976 want all three images, trim the make line. But note that thanks to &lt;a
977 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
978 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
979 kpartx call.&lt;/p&gt;
980
981 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
982 method, boot a Debian Wheezy ISO and use this boot argument to load
983 the preseed values:&lt;/p&gt;
984
985 &lt;pre&gt;
986 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;
987 &lt;/pre&gt;
988
989 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
990 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
991 currently hang while setting up APT sources. Killing the
992 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
993 installation will get the installation going. This affect all
994 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
995
996 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
997 us get the new release published. :) Please join us on
998 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
999 irc.debian.org)&lt;/a&gt; and
1000 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1001 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1002 </description>
1003 </item>
1004
1005 <item>
1006 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
1007 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
1008 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
1009 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
1010 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
1011 innetgr tools, because I needed them in
1012 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
1013 ng-utils, and it has served me well. I placed the project under the
1014 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
1015 repository. But many years ago, the CVS repository was dropped (lost,
1016 not migrated to new hardware, not sure), and the project have lacked a
1017 proper home since then.&lt;/p&gt;
1018
1019 &lt;p&gt;Last summer, I had a look at the package and made a new release
1020 fixing a irritating crash bug, but was unable to store the changes in
1021 a proper source control system. I applied for a project on
1022 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
1023 to follow up on it. Until today. :)&lt;/p&gt;
1024
1025 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
1026 now have a new home, and a git repository with the highlight of the
1027 history of the project. I published all release tarballs and imported
1028 them into the git repository. As the project is really stable and not
1029 expected to gain new features any time soon, I decided to make a new
1030 release and call it 1.0. Visit the new project home on
1031 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
1032 if you want to check it out. The new version is also uploaded into
1033 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
1034 </description>
1035 </item>
1036
1037 <item>
1038 <title>Testing sysvinit from experimental in Debian Hurd</title>
1039 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
1040 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
1041 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
1042 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
1043 their changes into sysvinit, to allow them to use the normal sysvinit
1044 boot system instead of their old one. This follow up on the
1045 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
1046 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
1047 get Debian on Hurd working more like Debian on Linux. To get started,
1048 I downloaded a prebuilt hard disk image from
1049 &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;,
1050 and started it using virt-manager.&lt;/p&gt;
1051
1052 &lt;p&gt;The first think I had to do after logging in (root without any
1053 password) was to get the network operational. I followed
1054 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
1055 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
1056 commands as root to get the machine to accept a IP address from the
1057 kvm internal DHCP server:&lt;/p&gt;
1058
1059 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1060 settrans -fgap /dev/netdde /hurd/netdde
1061 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
1062 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
1063 dhclient /dev/eth0
1064 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1065
1066 &lt;p&gt;After this, the machine had internet connectivity, and I could
1067 upgrade it and install the sysvinit packages from experimental and
1068 enable it as the default boot system in Hurd.&lt;/p&gt;
1069
1070 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
1071 running on the machine it for ssh login to work a password need to be
1072 set. Also, note that a bug somewhere in openssh on Hurd block
1073 compression from working. Remember to turn that off on the client
1074 side.&lt;/p&gt;
1075
1076 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1077 stuff:&lt;/p&gt;
1078
1079 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1080 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1081 deb http://http.debian.net/debian/ experimental main
1082 EOF
1083 apt-get update
1084 apt-get dist-upgrade
1085 apt-get install -t experimental initscripts sysv-rc sysvinit \
1086 sysvinit-core sysvinit-utils
1087 update-alternatives --config runsystem
1088 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1089
1090 &lt;p&gt;To reboot after switching boot system, you have to use
1091 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1092 yet a sysvinit process able to receive the signals from the normal
1093 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1094 upgrading every package and rebooting, the network come up with DHCP
1095 after boot as it should, and the settrans/pkill hack mentioned at the
1096 start is no longer needed. But for some strange reason, there are no
1097 longer any login prompt in the virtual console, so I logged in using
1098 ssh instead.
1099
1100 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1101 fail some times. No idea what the cause is, but hope the Hurd porters
1102 figure it out. At least Justus said on IRC (#debian-hurd on
1103 irc.debian.org) that they are aware of the problem. A way to reduce
1104 the impact is to upgrade to the Hurd packages built by Justus by
1105 adding this repository to the machine:&lt;/p&gt;
1106
1107 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1108 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1109 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1110 EOF
1111 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1112
1113 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1114 http://ftp.debian-ports.org/debian, because some of the packages in
1115 unstable do not yet include the required patches that are lingering in
1116 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1117
1118 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1119 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1120 i emacs - GNU Emacs editor (metapackage)
1121 i gdb - GNU Debugger
1122 i hurd-recommended - Miscellaneous translators
1123 i isc-dhcp-client - ISC DHCP client
1124 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1125 i libc-bin - Embedded GNU C Library: Binaries
1126 i libc-dev-bin - Embedded GNU C Library: Development binaries
1127 i libc0.3 - Embedded GNU C Library: Shared libraries
1128 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1129 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1130 i multiarch-support - Transitional package to ensure multiarch compatibilit
1131 i A x11-common - X Window System (X.Org) infrastructure
1132 i xorg - X.Org X Window System
1133 i A xserver-xorg - X.Org X server
1134 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1135 #
1136 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1137
1138 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1139 X.org did not work out of the box and I never took the time to follow
1140 the porters instructions to fix it. This time I was interested in the
1141 command line stuff.&lt;p&gt;
1142 </description>
1143 </item>
1144
1145 <item>
1146 <title>New chrpath release 0.16</title>
1147 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1148 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1149 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1150 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1151 find problems in C, C++ and Java code using static source code
1152 analysis. It can detect a lot of different problems, and is very
1153 useful to find memory and locking bugs in the error handling part of
1154 the source. The company behind it provide
1155 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1156 a community service&lt;/a&gt;, and many hundred free software projects are
1157 already checked. A few days ago I decided to have a closer look at
1158 the Coverity system, and discovered that the
1159 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1160 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1161 projects I am involved with was already registered. But these are
1162 fairly big, and I would also like to have a small and easy project to
1163 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1164 checking of the chrpath project&lt;/a&gt;. It was
1165 added to the checker and discovered seven potential defects. Six of
1166 these were real, mostly resource &quot;leak&quot; when the program detected an
1167 error. Nothing serious, as the resources would be released a fraction
1168 of a second later when the program exited because of the error, but it
1169 is nice to do it right in case the source of the program some time in
1170 the future end up in a library. Having fixed all defects and added
1171 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1172 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1173 publish a new release. These are the release notes:&lt;/p&gt;
1174
1175 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1176
1177 &lt;ul&gt;
1178
1179 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1180 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1181 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1182
1183 &lt;/ul&gt;
1184
1185 &lt;p&gt;You can
1186 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1187 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1188 project if something is wrong with the new release. The test suite
1189 did not discover any old errors, so if you find a new one, please also
1190 include a test suite check.&lt;/p&gt;
1191 </description>
1192 </item>
1193
1194 <item>
1195 <title>New chrpath release 0.15</title>
1196 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1197 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1198 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1199 <description>&lt;p&gt;After many years break from the package and a vain hope that
1200 development would be continued by someone else, I finally pulled my
1201 acts together this morning and wrapped up a new release of chrpath,
1202 the command line tool to modify the rpath and runpath of already
1203 compiled ELF programs. The update was triggered by the persistence of
1204 Isha Vishnoi at IBM, which needed a new config.guess file to get
1205 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1206 is working on. I checked the
1207 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1208 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1209 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1210 packages for interesting patches (failed to find the source from
1211 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1212 These are the release notes:&lt;/p&gt;
1213
1214 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1215
1216 &lt;ul&gt;
1217
1218 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1219 with newer architectures. Thanks to isha vishnoi for the heads
1220 up.&lt;/li&gt;
1221
1222 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1223
1224 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1225 Matthias Klose.&lt;/li&gt;
1226
1227 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1228 Petr Machata found in Fedora.&lt;/li&gt;
1229
1230 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1231 .dynamic is a NULL terminated string. Based on patch found in
1232 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1233
1234 &lt;/ul&gt;
1235
1236 &lt;p&gt;You can
1237 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1238 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1239 project if something is wrong with the new release. The test suite
1240 did not discover any old errors, so if you find a new one, please also
1241 include a testsuite check.&lt;/p&gt;
1242 </description>
1243 </item>
1244
1245 <item>
1246 <title>Debian init.d boot script example for rsyslog</title>
1247 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1248 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1249 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1250 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1251 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1252 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1253 init.d scripts at all. Here is an example init.d script, ie a rewrite
1254 of /etc/init.d/rsyslog:&lt;/p&gt;
1255
1256 &lt;p&gt;&lt;pre&gt;
1257 #!/lib/init/init-d-script
1258 ### BEGIN INIT INFO
1259 # Provides: rsyslog
1260 # Required-Start: $remote_fs $time
1261 # Required-Stop: umountnfs $time
1262 # X-Stop-After: sendsigs
1263 # Default-Start: 2 3 4 5
1264 # Default-Stop: 0 1 6
1265 # Short-Description: enhanced syslogd
1266 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1267 # It is quite compatible to stock sysklogd and can be
1268 # used as a drop-in replacement.
1269 ### END INIT INFO
1270 DESC=&quot;enhanced syslogd&quot;
1271 DAEMON=/usr/sbin/rsyslogd
1272 &lt;/pre&gt;&lt;/p&gt;
1273
1274 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1275 script was 137 lines, and the above is just 15 lines, most of it meta
1276 info/comments.&lt;/p&gt;
1277
1278 &lt;p&gt;How to do this, you ask? Well, one create a new script
1279 /lib/init/init-d-script looking something like this:
1280
1281 &lt;p&gt;&lt;pre&gt;
1282 #!/bin/sh
1283
1284 # Define LSB log_* functions.
1285 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1286 # and status_of_proc is working.
1287 . /lib/lsb/init-functions
1288
1289 #
1290 # Function that starts the daemon/service
1291
1292 #
1293 do_start()
1294 {
1295 # Return
1296 # 0 if daemon has been started
1297 # 1 if daemon was already running
1298 # 2 if daemon could not be started
1299 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1300 || return 1
1301 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1302 $DAEMON_ARGS \
1303 || return 2
1304 # Add code here, if necessary, that waits for the process to be ready
1305 # to handle requests from services started subsequently which depend
1306 # on this one. As a last resort, sleep for some time.
1307 }
1308
1309 #
1310 # Function that stops the daemon/service
1311 #
1312 do_stop()
1313 {
1314 # Return
1315 # 0 if daemon has been stopped
1316 # 1 if daemon was already stopped
1317 # 2 if daemon could not be stopped
1318 # other if a failure occurred
1319 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1320 RETVAL=&quot;$?&quot;
1321 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1322 # Wait for children to finish too if this is a daemon that forks
1323 # and if the daemon is only ever run from this initscript.
1324 # If the above conditions are not satisfied then add some other code
1325 # that waits for the process to drop all resources that could be
1326 # needed by services started subsequently. A last resort is to
1327 # sleep for some time.
1328 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1329 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1330 # Many daemons don&#39;t delete their pidfiles when they exit.
1331 rm -f $PIDFILE
1332 return &quot;$RETVAL&quot;
1333 }
1334
1335 #
1336 # Function that sends a SIGHUP to the daemon/service
1337 #
1338 do_reload() {
1339 #
1340 # If the daemon can reload its configuration without
1341 # restarting (for example, when it is sent a SIGHUP),
1342 # then implement that here.
1343 #
1344 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1345 return 0
1346 }
1347
1348 SCRIPTNAME=$1
1349 scriptbasename=&quot;$(basename $1)&quot;
1350 echo &quot;SN: $scriptbasename&quot;
1351 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
1352 script=&quot;$1&quot;
1353 shift
1354 . $script
1355 else
1356 exit 0
1357 fi
1358
1359 NAME=$(basename $DAEMON)
1360 PIDFILE=/var/run/$NAME.pid
1361
1362 # Exit if the package is not installed
1363 #[ -x &quot;$DAEMON&quot; ] || exit 0
1364
1365 # Read configuration variable file if it is present
1366 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
1367
1368 # Load the VERBOSE setting and other rcS variables
1369 . /lib/init/vars.sh
1370
1371 case &quot;$1&quot; in
1372 start)
1373 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
1374 do_start
1375 case &quot;$?&quot; in
1376 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1377 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1378 esac
1379 ;;
1380 stop)
1381 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
1382 do_stop
1383 case &quot;$?&quot; in
1384 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1385 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1386 esac
1387 ;;
1388 status)
1389 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
1390 ;;
1391 #reload|force-reload)
1392 #
1393 # If do_reload() is not implemented then leave this commented out
1394 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
1395 #
1396 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
1397 #do_reload
1398 #log_end_msg $?
1399 #;;
1400 restart|force-reload)
1401 #
1402 # If the &quot;reload&quot; option is implemented then remove the
1403 # &#39;force-reload&#39; alias
1404 #
1405 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
1406 do_stop
1407 case &quot;$?&quot; in
1408 0|1)
1409 do_start
1410 case &quot;$?&quot; in
1411 0) log_end_msg 0 ;;
1412 1) log_end_msg 1 ;; # Old process is still running
1413 *) log_end_msg 1 ;; # Failed to start
1414 esac
1415 ;;
1416 *)
1417 # Failed to stop
1418 log_end_msg 1
1419 ;;
1420 esac
1421 ;;
1422 *)
1423 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
1424 exit 3
1425 ;;
1426 esac
1427
1428 :
1429 &lt;/pre&gt;&lt;/p&gt;
1430
1431 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
1432 lot. I did not really polish the approach, so it might not always
1433 work out of the box, but you get the idea. I did not try very hard to
1434 optimize it nor make it more robust either.&lt;/p&gt;
1435
1436 &lt;p&gt;A better argument for switching init system in Debian than reducing
1437 the size of init scripts (which is a good thing to do anyway), is to
1438 get boot system that is able to handle the kernel events sensibly and
1439 robustly, and do not depend on the boot to run sequentially. The boot
1440 and the kernel have not behaved sequentially in years.&lt;/p&gt;
1441 </description>
1442 </item>
1443
1444 <item>
1445 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
1446 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
1447 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
1448 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
1449 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
1450 remote display access is the preferred solution with oVirt and RedHat
1451 Enterprise Virtualization, and I was sad to discover the other day
1452 that the browser plugin needed to use these systems seamlessly was
1453 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
1454 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
1455 2013-04-01, so I decided to wrap up a package based on the great work
1456 from Cajus Pollmeier and put it in a collab-maint maintained git
1457 repository to get a package I could use. I would very much like
1458 others to help me maintain the package (or just take over, I do not
1459 mind), but as no-one had volunteered so far, I just uploaded it to
1460 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
1461
1462 &lt;p&gt;The source is now available from
1463 &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;
1464 </description>
1465 </item>
1466
1467 <item>
1468 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
1469 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
1470 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
1471 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
1472 <description>&lt;p&gt;The
1473 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
1474 program is a a very nice system to create virtual machine images. It
1475 create a image file, add a partition table, mount it and run
1476 debootstrap in the mounted directory to create a Debian system on a
1477 stick. Yesterday, I decided to try to teach it how to make images for
1478 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
1479 of a plan to simplify the build system for
1480 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
1481 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
1482 the virtualbox images, but its current build system made multistrap
1483 based system for Dreamplug images, and it is lacking support for
1484 Raspberry Pi.&lt;/p&gt;
1485
1486 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
1487 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1488 code and adjusted it to be able to build armel images on my amd64
1489 Debian laptop. I ended up giving vmdebootstrap five new options,
1490 allowing me to replicate the image creation process I use to make
1491 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
1492 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
1493 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
1494 call debootstrap with --foreign and to copy the handler into the
1495 generated chroot before running the second stage. This allow
1496 vmdebootstrap to create armel images on an amd64 host. Next I added
1497 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
1498 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
1499 given file system type, allowing me to create an image with a vfat
1500 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
1501 variant&lt;/tt&gt; option to allow me to create smaller images without the
1502 Debian base system packages installed. Finally, I added an option
1503 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
1504 as a boot loader. It is not needed on the Raspberry Pi and probably
1505 most other non-x86 architectures. The changes were accepted by the
1506 upstream author of vmdebootstrap yesterday and today, and is now
1507 available from
1508 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
1509 upstream project page&lt;/a&gt;.&lt;/p&gt;
1510
1511 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
1512 create a small script (the customize script) to add the non-free
1513 binary blob needed to boot the Raspberry Pi and the APT source
1514 list:&lt;/p&gt;
1515
1516 &lt;p&gt;&lt;pre&gt;
1517 #!/bin/sh
1518 set -e # Exit on first error
1519 rootdir=&quot;$1&quot;
1520 cd &quot;$rootdir&quot;
1521 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
1522 deb http://http.debian.net/debian/ jessie main contrib non-free
1523 EOF
1524 # Install non-free binary blob needed to boot Raspberry Pi. This
1525 # install a kernel somewhere too.
1526 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1527 -O $rootdir/usr/bin/rpi-update
1528 chmod a+x $rootdir/usr/bin/rpi-update
1529 mkdir -p $rootdir/lib/modules
1530 touch $rootdir/boot/start.elf
1531 chroot $rootdir rpi-update
1532 &lt;/pre&gt;&lt;/p&gt;
1533
1534 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
1535 to build the image:&lt;/p&gt;
1536
1537 &lt;pre&gt;
1538 sudo ./vmdebootstrap \
1539 --variant minbase \
1540 --arch armel \
1541 --distribution jessie \
1542 --mirror http://http.debian.net/debian \
1543 --image test.img \
1544 --size 600M \
1545 --bootsize 64M \
1546 --boottype vfat \
1547 --log-level debug \
1548 --verbose \
1549 --no-kernel \
1550 --no-extlinux \
1551 --root-password raspberry \
1552 --hostname raspberrypi \
1553 --foreign /usr/bin/qemu-arm-static \
1554 --customize `pwd`/customize \
1555 --package netbase \
1556 --package git-core \
1557 --package binutils \
1558 --package ca-certificates \
1559 --package wget \
1560 --package kmod
1561 &lt;/pre&gt;&lt;/p&gt;
1562
1563 &lt;p&gt;The list of packages being installed are the ones needed by
1564 rpi-update to make the image bootable on the Raspberry Pi, with the
1565 exception of netbase, which is needed by debootstrap to find
1566 /etc/hosts with the minbase variant. I really wish there was a way to
1567 set up an Raspberry Pi using only packages in the Debian archive, but
1568 that is not possible as far as I know, because it boots from the GPU
1569 using a non-free binary blob.&lt;/p&gt;
1570
1571 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
1572 probably a few others installed. I have not checked the complete
1573 build dependency list.&lt;/p&gt;
1574
1575 &lt;p&gt;The resulting image will not use the hardware floating point unit
1576 on the Raspberry PI, because the armel architecture in Debian is not
1577 optimized for that use. So the images created will be a bit slower
1578 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
1579 </description>
1580 </item>
1581
1582 <item>
1583 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
1584 <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>
1585 <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>
1586 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
1587 <description>&lt;p&gt;The last few days I came across a few good causes that should get
1588 wider attention. I recommend signing and donating to each one of
1589 these. :)&lt;/p&gt;
1590
1591 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
1592 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
1593 Women program which is a Google Summer of Code like initiative to get
1594 more women involved in free software. One debian sponsor has offered
1595 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
1596 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
1597 hope you will to. :)&lt;/p&gt;
1598
1599 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
1600 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
1601 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
1602 take place these days, and their need to fund the work. I&#39;ve already
1603 donated. Are you next?&lt;/p&gt;
1604
1605 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
1606 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1607 statement under the heading
1608 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
1609 Access&lt;/a&gt; for those of us asking for more focus on open access in the
1610 Norwegian government. So far 499 signatures. I hope you will sign it
1611 too.&lt;/p&gt;
1612 </description>
1613 </item>
1614
1615 <item>
1616 <title>Videos about the Freedombox project - for inspiration and learning</title>
1617 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
1618 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
1619 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
1620 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
1621 project&lt;/a&gt; have been going on for a while, and have presented the
1622 vision, ideas and solution several places. Here is a little
1623 collection of videos of talks and presentation of the project.&lt;/p&gt;
1624
1625 &lt;ul&gt;
1626
1627 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
1628 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
1629
1630 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
1631 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1632
1633 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
1634 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1635 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
1636 (Youtube)&lt;/li&gt;
1637
1638 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
1639 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
1640
1641 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
1642 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1643
1644 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
1645 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1646 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
1647
1648 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
1649 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
1650 (Youtube)&lt;/li&gt;
1651
1652 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
1653 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
1654
1655 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
1656 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
1657
1658 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
1659 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1660 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
1661
1662 &lt;/ul&gt;
1663
1664 &lt;p&gt;A larger list is available from
1665 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
1666 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
1667
1668 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
1669 Jessie is coming along quite well, and soon both Owncloud and using
1670 Tor should be available for testers of the Freedombox solution. :) In
1671 a few weeks I hope everything needed to test it is included in Debian.
1672 The withsqlite package is already in Debian, and the plinth package is
1673 pending in NEW. The third and vital part of that puzzle is the
1674 metapackage/setup framework, which is still pending an upload. Join
1675 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
1676 (#freedombox on irc.debian.org)&lt;/a&gt; and
1677 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1678 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1679 </description>
1680 </item>
1681
1682 <item>
1683 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
1684 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
1685 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
1686 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
1687 <description>&lt;p&gt;I was introduced to the
1688 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
1689 in 2010, when Eben Moglen presented his vision about serving the need
1690 of non-technical people to keep their personal information private and
1691 within the legal protection of their own homes. The idea is to give
1692 people back the power over their network and machines, and return
1693 Internet back to its intended peer-to-peer architecture. Instead of
1694 depending on a central service, the Freedombox will give everyone
1695 control over their own basic infrastructure.&lt;/p&gt;
1696
1697 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
1698 taken priority. But this summers nasty news about the misuse of trust
1699 and privilege exercised by the &quot;western&quot; intelligence gathering
1700 communities increased my eagerness to contribute to a point where I
1701 actually started working on the project a while back.&lt;/p&gt;
1702
1703 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
1704 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
1705 create a simple and cheap Debian based appliance that anyone can hook
1706 up in their home and get access to secure and private services and
1707 communication. The initial deployment platform have been the
1708 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
1709 which is a piece of hardware I do not own. So to be able to test what
1710 the current Freedombox setup look like, I had to come up with a way to install
1711 it on some hardware I do have access to. I have rewritten the
1712 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
1713 image build framework to use .deb packages instead of only copying
1714 setup into the boot images, and thanks to this rewrite I am able to
1715 set up any machine supported by Debian Wheezy as a Freedombox, using
1716 the previously mentioned deb (and a few support debs for packages
1717 missing in Debian).&lt;/p&gt;
1718
1719 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
1720 scripts
1721 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
1722 and a administrative web interface
1723 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
1724 withsqlite), as well as a privacy enhancing proxy based on
1725 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
1726 (freedombox-privoxy). There is also a web/javascript based XMPP
1727 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
1728 trying (unsuccessfully so far) to talk to the XMPP server
1729 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
1730 web interface is pluggable, and the goal is to use it to enable OpenID
1731 services, mesh network connectivity, use of TOR, etc, etc. Not much of
1732 this is really working yet, see
1733 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
1734 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
1735 on github at the moment. The HTTP proxy is operational out of the
1736 box, and the admin web interface can be used to add/remove plinth
1737 users. I&#39;ve not been able to do anything else with it so far, but
1738 know there are several branches spread around github and other places
1739 with lots of half baked features.&lt;/p&gt;
1740
1741 &lt;p&gt;Anyway, if you want to have a look at the current state, the
1742 following recipes should work to give you a test machine to poke
1743 at.&lt;/p&gt;
1744
1745 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
1746
1747 &lt;ol&gt;
1748
1749 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
1750 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
1751 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
1752 to the Debian installer:&lt;p&gt;
1753 &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;
1754
1755 &lt;li&gt;Answer the few language/region/password questions and pick disk to
1756 install on.&lt;/li&gt;
1757
1758 &lt;li&gt;When the installation is finished and the machine have rebooted a
1759 few times, your Freedombox is ready for testing.&lt;/li&gt;
1760
1761 &lt;/ol&gt;
1762
1763 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
1764
1765 &lt;ol&gt;
1766
1767 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
1768 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
1769 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
1770 &lt;pre&gt;
1771 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
1772 &lt;/pre&gt;&lt;/li&gt;
1773 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
1774 &lt;pre&gt;
1775 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
1776 apt-key add -
1777 apt-get update
1778 apt-get install freedombox-setup
1779 /usr/lib/freedombox/setup
1780 &lt;/pre&gt;&lt;/li&gt;
1781 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
1782
1783 &lt;/ol&gt;
1784
1785 &lt;p&gt;You can test it on other architectures too, but because the
1786 freedombox-privoxy package is binary, it will only work as intended on
1787 the architectures where I have had time to build the binary and put it
1788 in my APT repository. But do not let this stop you. It is only a
1789 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
1790
1791 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
1792 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
1793 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
1794 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
1795
1796 &lt;p&gt;Please let me know if this works for you, or if you have any
1797 problems. We gather on the IRC channel
1798 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
1799 irc.debian.org and the
1800 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
1801 mailing list&lt;/a&gt;.&lt;/p&gt;
1802
1803 &lt;p&gt;Once you get your freedombox operational, you can visit
1804 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
1805 welcome screen (dead end - do not be surprised if you are unable to
1806 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
1807 to look at the rest of plinth. The default user is &#39;admin&#39; and the
1808 default password is &#39;secret&#39;.&lt;/p&gt;
1809 </description>
1810 </item>
1811
1812 <item>
1813 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
1814 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
1815 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
1816 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
1817 <description>&lt;p&gt;Earlier, I reported about
1818 &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
1819 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
1820 told by IBM that the original disk should be thrown away. And as
1821 there no longer was a problem if I bricked the firmware, I decided
1822 today to try to install Intel firmware to replace the Lenovo firmware
1823 currently on the disk.&lt;/p&gt;
1824
1825 &lt;p&gt;I searched the Intel site for firmware, and found
1826 &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;
1827 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
1828 according to the site should contain the latest firmware for SSD
1829 disks. I inserted the broken disk in one of my spare laptops and
1830 booted the ISO from a USB stick. The disk was recognized, but the
1831 program claimed the newest firmware already were installed and refused
1832 to insert any Intel firmware. So no change, and the disk is still
1833 unable to handle write load. :( I guess the only way to get them
1834 working would be if Lenovo releases new firmware. No idea how likely
1835 that is. Anyway, just blogging about this test for completeness. I
1836 got a working Samsung disk, and see no point in spending more time on
1837 the broken disks.&lt;/p&gt;
1838 </description>
1839 </item>
1840
1841 <item>
1842 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
1843 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
1844 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
1845 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
1846 <description>&lt;p&gt;Today I switched to
1847 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
1848 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
1849 my new Thinkpad X230, which was delivered with an
1850 &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
1851 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
1852 sustained writes. My hardware supplier have been very forthcoming in
1853 trying to find a solution, and after first trying with another
1854 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
1855 disk instead to fix it once and for all. The Samsung disk survived
1856 the installation of Debian with encrypted disks (filling the disk with
1857 random data during installation killed the first two), and I thus
1858 decided to trust it with my data. I have installed it as a Debian Edu
1859 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
1860 server at home using Kerberos and LDAP, and will use it as my work
1861 station from now on.&lt;/p&gt;
1862
1863 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
1864 Debian Wheezy default installation need to be tuned a bit to increase
1865 performance and increase life time of the disk. The Linux kernel and
1866 user space applications do not yet adjust automatically to such
1867 environment. To make it easier for my self, I created a draft Debian
1868 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
1869 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
1870 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
1871 is set up to adjust the setup of the machine by just installing the
1872 package. If there is any non-SSD disk in the machine, the package
1873 will refuse to install, as I did not try to write any logic to sort
1874 file systems in SSD and non-SSD file systems.&lt;/p&gt;
1875
1876 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
1877 set up Debian Wheezy with an SSD. It is adjusted to my use case,
1878 where I set up the machine with one large encrypted partition (in
1879 addition to /boot), put LVM on top of this and set up partitions on
1880 top of this again. See the README file in the package source for the
1881 references I used to pick the settings. At the moment these
1882 parameters are tuned:&lt;/p&gt;
1883
1884 &lt;ul&gt;
1885
1886 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
1887 (adding discard to /etc/crypttab)&lt;/li&gt;
1888
1889 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
1890 this case a cryptsetup partition) by changing issue_discards from
1891 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
1892
1893 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
1894 systems.&lt;/li&gt;
1895
1896 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
1897 /etc/fstab.&lt;/li&gt;
1898
1899 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
1900
1901 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
1902 cron.daily).&lt;/li&gt;
1903
1904 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
1905 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
1906
1907 &lt;/ul&gt;
1908
1909 &lt;p&gt;During installation, I cancelled the part where the installer fill
1910 the disk with random data, as this would kill the SSD performance for
1911 little gain. My goal with the encrypted file system is to ensure
1912 those stealing my laptop end up with a brick and not a working
1913 computer. I have no hope in keeping the really resourceful people
1914 from getting the data on the disk (see
1915 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
1916 Thus I concluded that adding the discard option to crypttab is the
1917 right thing to do.&lt;/p&gt;
1918
1919 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
1920 it for SSD, but others recommended deadline and a benchmark I found
1921 indicated that deadline might be better for interactive use.&lt;/p&gt;
1922
1923 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
1924 and ext4, but read that it would give a performance hit ever time a
1925 file is removed, and thought it best to that that slowdown once a day
1926 instead of during my work.&lt;/p&gt;
1927
1928 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
1929 this is already done by Debian Edu.&lt;/p&gt;
1930
1931 &lt;p&gt;I have not yet started on the user space tuning. I expect
1932 iceweasel need some tuning, and perhaps other applications too, but
1933 have not yet had time to investigate those parts.&lt;/p&gt;
1934
1935 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
1936 there.&lt;/p&gt;
1937
1938 &lt;p&gt;As for the answer to the question in the title of this blog post,
1939 as far as I know, the only solution I know about is to replace the
1940 disk. It might be possible to flash it with Intel firmware instead of
1941 the Lenovo firmware. But I have not tried and did not want to do so
1942 without approval from Lenovo as I wanted to keep the warranty on the
1943 disk until a solution was found and they wanted the broken disks
1944 back.&lt;/p&gt;
1945 </description>
1946 </item>
1947
1948 <item>
1949 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
1950 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
1951 <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>
1952 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
1953 <description>&lt;p&gt;A few days ago, I wrote about
1954 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
1955 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
1956 was dying during installation because it is unable to cope with
1957 sustained write. My supplier is in contact with
1958 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
1959 replacement disk to try to fix the problem. They decided to send an
1960 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
1961
1962 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
1963 Debian Edu Wheezy with encrypted disk on it. The new disk have the
1964 same firmware version as the original. This time my hope raised
1965 slightly as the installation progressed, as the original disk used to
1966 die after 4-7% of the disk was written to, while this time it kept
1967 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
1968 died again and I was back on square one. I still do not have a new
1969 laptop with a disk I can trust. I can not live with a disk that might
1970 lock up when I download a new
1971 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
1972 other large files. I look forward to hearing from my supplier with
1973 the next proposal from Lenovo.&lt;/p&gt;
1974
1975 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
1976 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
1977 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
1978 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
1979 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
1980 P/N 45N8295, P0C38732.&lt;/p&gt;
1981
1982 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
1983 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
1984 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
1985 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
1986 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
1987 P/N 45N8295, P0C38732.&lt;/p&gt;
1988
1989 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
1990 SA, date and WNPP values. Mentioning all the details here in case
1991 someone is able to use the information to find a way to identify the
1992 failing disk among working ones (if any such working disk actually
1993 exist).&lt;/p&gt;
1994 </description>
1995 </item>
1996
1997 <item>
1998 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
1999 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
2000 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
2001 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
2002 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
2003 Debian Edu developer gathering and Debian and Ubuntu bug squashing
2004 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
2005 member assosiation NUUG&lt;/a&gt; and
2006 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
2007 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
2008 Bitraf&lt;/a&gt;.&lt;/p&gt;
2009
2010 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
2011 welcome, and there is no fee to participate. There is on the other
2012 hand limited space, and only room for 30 people. Please put your name
2013 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
2014 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
2015 </description>
2016 </item>
2017
2018 <item>
2019 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
2020 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
2021 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
2022 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
2023 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
2024 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
2025 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
2026 time to spend on it, and it took a while to find a model I believe
2027 will do the job, but two days ago the replacement finally arrived. I
2028 ended up picking a
2029 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
2030 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
2031 a roaming workstation, and it seemed to work flawlessly. But my
2032 second installation with encrypted disk was not as successful. More
2033 on that below.&lt;/p&gt;
2034
2035 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2036 important requirements (robust and with a good keyboard) are never
2037 listed in the feature list. But I did get good help from the search
2038 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2039 allowed me to limit the list of interesting laptops based on my other
2040 requirements. A bit surprising that SSD disk are not disks according
2041 to that search interface, so I had to drop specifying the number of
2042 disks from my search parameters. I also asked around among friends to
2043 get their impression on keyboards and robustness.&lt;/p&gt;
2044
2045 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
2046 X41. I am not quite convinced about the keyboard, as it is
2047 significantly wider than my old keyboard, and I have to stretch my
2048 hand a lot more to reach the edges. But the key response is fairly
2049 good and the individual key shape is fairly easy to handle, so I hope
2050 I will get used to it. My old X40 was starting to fail, and I really
2051 needed a new laptop now. :)&lt;/p&gt;
2052
2053 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
2054 visit to the BIOS during boot it disable it.&lt;/p&gt;
2055
2056 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
2057 lock up during load. And this happen when installing Debian Wheezy
2058 with encrypted disk, while the disk is being filled with random data.
2059 I also tested to install Ubuntu Raring, and it happen there too if I
2060 reenable the code to fill the disk with random data (it is disabled by
2061 default in Ubuntu). And the bug with is already known. It was
2062 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
2063 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
2064 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
2065 kernel developers as
2066 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
2067 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
2068 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
2069 Lenovo forums, both for
2070 &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
2071 2012-11-10&lt;/a&gt; and for
2072 &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
2073 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2074 reports state that the disk lock up during use if many writes are done
2075 on the disk, so it is much no use to work around the installation
2076 problem and end up with a computer that can lock up at any moment.
2077 There is even a
2078 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2079 available&lt;/a&gt; that will lock up the hard drive after running a few
2080 minutes by writing to a file.&lt;/p&gt;
2081
2082 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2083 contacting PCHELP Norway (request 01D1FDP) which handle support
2084 requests for Lenovo, his first suggestion was to upgrade the disk
2085 firmware. Unfortunately there is no newer firmware available from
2086 Lenovo, as my disk already have the most recent one (version LF1i). I
2087 hope to hear more from him today and hope the problem can be
2088 fixed. :)&lt;/p&gt;
2089 </description>
2090 </item>
2091
2092 <item>
2093 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2094 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2095 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2096 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2097 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2098 trusty old Thinkpad X41. Unfortunately I did not have much time to
2099 spend on it, but today the replacement finally arrived. I ended up
2100 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2101 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2102 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2103 this, it is installing what I hope will be a more final installation,
2104 with a encrypted hard drive to ensure any dope head stealing it end up
2105 with an expencive door stop.&lt;/p&gt;
2106
2107 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2108 important requirements (robust and with a good keyboard) are never
2109 listed in the feature list. But I did get good help from the search
2110 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2111 allowed me to limit the list of interesting laptops based on my other
2112 requirements. A bit surprising that SSD disk are not disks, so I had
2113 to drop number of disks from my search parameters.&lt;/p&gt;
2114
2115 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2116 wider than my old keyboard, and I have to stretch my hand a lot more
2117 to reach the edges. But the key response is fairly good and the
2118 individual key shape is fairly easy to handle, so I hope I will get
2119 used to it. My old X40 was starting to fail, and I really needed a
2120 new laptop now. :)&lt;/p&gt;
2121
2122 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2123 </description>
2124 </item>
2125
2126 <item>
2127 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2128 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2129 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2130 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2131 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2132 perfectly capable of, and I have to do it manually to get things
2133 working. One such task is to find out what firmware packages are
2134 needed to get the hardware on my computer working. Most often this
2135 affect the wifi card, but some times it even affect the RAID
2136 controller or the ethernet card. Today I pushed version 0.4 of the
2137 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2138 including a new script isenkram-autoinstall-firmware handling the
2139 process of asking all the loaded kernel modules what firmware files
2140 they want, find debian packages providing these files and install the
2141 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2142
2143 &lt;p&gt;&lt;pre&gt;
2144 # isenkram-autoinstall-firmware
2145 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2146 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2147 info: locating packages with the requested firmware files
2148 info: Updating APT sources after adding non-free APT source
2149 info: trying to install firmware-ipw2x00
2150 firmware-ipw2x00
2151 firmware-ipw2x00
2152 Preconfiguring packages ...
2153 Selecting previously deselected package firmware-ipw2x00.
2154 (Reading database ... 259727 files and directories currently installed.)
2155 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2156 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2157 #
2158 &lt;/pre&gt;&lt;/p&gt;
2159
2160 &lt;p&gt;When all the requested firmware is present, a simple message is
2161 printed instead:&lt;/p&gt;
2162
2163 &lt;p&gt;&lt;pre&gt;
2164 # isenkram-autoinstall-firmware
2165 info: did not find any firmware files requested by loaded kernel modules. exiting
2166 #
2167 &lt;/pre&gt;&lt;/p&gt;
2168
2169 &lt;p&gt;It could use some polish, but it is already working well and saving
2170 me some time when setting up new machines. :)&lt;/p&gt;
2171
2172 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2173 kernel modules, and look up each one of them using modinfo, to find
2174 the firmware files listed in the module meta-information. Next, it
2175 download the Contents file from a nearby APT mirror, and search for
2176 the firmware files in this file to locate the package with the
2177 requested firmware file. If the package is in the non-free section, a
2178 non-free APT source is added and the package is installed using
2179 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2180 machine.&lt;/p&gt;
2181
2182 &lt;p&gt;I hope someone find time to implement a more polished version of
2183 this script as part of the hw-detect debian-installer module, to
2184 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2185 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2186 firmware during a PXE install when the packages already are available
2187 from the nearby Debian mirror.&lt;/p&gt;
2188 </description>
2189 </item>
2190
2191 <item>
2192 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2193 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2194 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2195 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2196 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2197 the screen just turn black when Linux boot, either during installation
2198 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2199 last few years, but only recently understood the cause. I&#39;ve seen it
2200 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2201 The reason seem to be in the wiring of some laptops. The system to
2202 control the screen background light is inverted, so when Linux try to
2203 turn the brightness fully on, it end up turning it off instead. I do
2204 not know which Linux drivers are affected, but this post is about the
2205 i915 driver used by the
2206 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2207 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2208
2209 &lt;p&gt;The problem can be worked around two ways. Either by adding
2210 i915.invert_brightness=1 as a kernel option, or by adding a file in
2211 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2212 option when it load the i915 kernel module. On Debian and Ubuntu, it
2213 can be done by running these commands as root:&lt;/p&gt;
2214
2215 &lt;pre&gt;
2216 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2217 update-initramfs -u -k all
2218 &lt;/pre&gt;
2219
2220 &lt;p&gt;Since March 2012 there is
2221 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2222 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2223 hardware have this problem, and get the driver to invert the
2224 brightness setting automatically. To use it, one need to add a row in
2225 &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
2226 intel_quirks array&lt;/a&gt; in the driver source
2227 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2228 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2229 number (vendor number 8086 is assumed) and subdevice vendor and device
2230 number.&lt;/p&gt;
2231
2232 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2233 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2234
2235 &lt;p&gt;&lt;pre&gt;
2236 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2237 3rd Gen Core processor Graphics Controller [8086:0156] \
2238 (rev 09) (prog-if 00 [VGA controller])
2239 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2240 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2241 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2242 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2243 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2244 Latency: 0
2245 Interrupt: pin A routed to IRQ 42
2246 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2247 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2248 Region 4: I/O ports at 4000 [size=64]
2249 Expansion ROM at &lt;unassigned&gt; [disabled]
2250 Capabilities: &lt;access denied&gt;
2251 Kernel driver in use: i915
2252 &lt;/pre&gt;&lt;/p&gt;
2253
2254 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2255
2256 &lt;p&gt;&lt;pre&gt;
2257 struct intel_quirk intel_quirks[] = {
2258 ...
2259 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2260 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2261 ...
2262 }
2263 &lt;/pre&gt;&lt;/p&gt;
2264
2265 &lt;p&gt;According to the kernel module instructions (as seen using
2266 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2267 invert_brightness flag should be sent to the
2268 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2269 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2270 developers. But my email about the laptop sent 2013-06-03 have not
2271 yet shown up in
2272 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2273 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2274 emails from non-subscribers. Because of this, I sent my patch also to
2275 the Debian bug tracking system instead as
2276 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2277 sure the patch is not lost.&lt;/p&gt;
2278
2279 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2280 with this problem working properly with Linux. If you use Gnome, your
2281 worries should be over at this point. But if you use KDE, there is
2282 something in KDE ignoring the invert_brightness setting and turning on
2283 the screen during login. I&#39;ve reported it to Debian as
2284 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2285 have no idea yet how to figure out exactly what subsystem is doing
2286 this. Perhaps you can help? Perhaps you know what the Gnome
2287 developers did to handle this, and this can give a clue to the KDE
2288 developers? Or you know where in KDE the screen brightness is changed
2289 during login? If so, please update the BTS report (or get in touch if
2290 you do not know how to update BTS).&lt;/p&gt;
2291
2292 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2293 acpi_backlight=vendor, to disable ACPI backlight support completely,
2294 as the ACPI information on the machine is trash and it is better to
2295 leave it to the intel video driver to control the screen
2296 backlight.&lt;/p&gt;
2297 </description>
2298 </item>
2299
2300 <item>
2301 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2302 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2303 <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>
2304 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2305 <description>&lt;p&gt;Two days ago, I asked
2306 &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
2307 I could install Linux on a Packard Bell EasyNote LV computer
2308 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2309 with the obstacles put in the way of Linux users on a laptop with UEFI
2310 and Windows 8.&lt;/p&gt;
2311
2312 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2313 secure booting or fast boot. I suspect fast boot was the problem,
2314 causing the firmware to boot directly from HD without considering any
2315 key presses and alternative devices, but do not know UEFI settings
2316 enough to tell.&lt;/p&gt;
2317
2318 &lt;p&gt;There is no way to install Linux on the machine in question without
2319 opening the box and disconnecting the hard drive! This is as far as I
2320 can tell, the only way to get access to the firmware setup menu
2321 without accepting the Windows 8 license agreement. I am told (and
2322 found description on how to) that it is possible to configure the
2323 firmware setup once booted into Windows 8. But as I believe the terms
2324 of that agreement are completely unacceptable, accepting the license
2325 was never an alternative. I do not enter agreements I do not intend
2326 to follow.&lt;/p&gt;
2327
2328 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2329 waste many hours on this, but luckily there was a way to get it to
2330 work. But I would not recommend it to anyone planning to run Linux on
2331 it, and I have become sceptical to Windows 8 certified laptops. Is
2332 this the way Linux will be forced out of the market place, by making
2333 it close to impossible for &quot;normal&quot; users to install Linux without
2334 accepting the Microsoft Windows license terms? Or at least not
2335 without risking to loose the warranty?&lt;/p&gt;
2336
2337 &lt;p&gt;I&#39;ve updated the
2338 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2339 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2340 do not have to struggle as much as I did to get Linux into the
2341 machine.&lt;/p&gt;
2342
2343 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2344 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2345 </description>
2346 </item>
2347
2348 <item>
2349 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2350 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2351 <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>
2352 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
2353 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
2354 new laptops for my parents and a few others. I bought Packard Bell
2355 Easynote LV to run Kubuntu on and use as their home computer. But I
2356 am completely unable to figure out how to install Linux on it. The
2357 computer is preinstalled with Windows 8, and I suspect it uses UEFI
2358 instead of a BIOS to boot.&lt;/p&gt;
2359
2360 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
2361 to get it to boot the Linux installer from my USB stick. I have yet
2362 to try the DVD install, and still hope it will work. when I turn on
2363 the computer, there is no information on what buttons to press to get
2364 the normal boot menu. I expect to get some boot menu to select PXE or
2365 USB stick booting. When booting, it first ask for the language to
2366 use, then for some regional settings, and finally if I will accept the
2367 Windows 8 terms of use. As these terms are completely unacceptable to
2368 me, I have no other choice but to turn off the computer and try again
2369 to get it to boot the Linux installer.&lt;/p&gt;
2370
2371 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
2372 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2373 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
2374 installed on this machine, please get in touch or update that wiki
2375 page. If I can&#39;t find a way to install Linux, I will have to return
2376 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
2377
2378 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
2379 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
2380 on new Laptops?&lt;/p&gt;
2381 </description>
2382 </item>
2383
2384 <item>
2385 <title>How to transform a Debian based system to a Debian Edu installation</title>
2386 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
2387 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
2388 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
2389 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
2390 an operating system based on Debian intended for use in schools. It
2391 contain a turn-key solution for the computer network provided to
2392 pupils in the primary schools. It provide both the central server,
2393 network boot servers and desktop environments with heaps of
2394 educational software. The project was founded almost 12 years ago,
2395 2001-07-02. If you want to support the project, which is in need for
2396 cash to fund developer gatherings and other project related activity,
2397 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
2398 donate some money&lt;/a&gt;.
2399
2400 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
2401 lists and elsewhere, is the question on how to transform a Debian or
2402 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
2403 hard, and last week I wrote a script to replicate the steps done by
2404 the Debian Edu installer.&lt;/p&gt;
2405
2406 &lt;p&gt;The script,
2407 &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;
2408 in the debian-edu-config package, will go through these six steps and
2409 transform an existing Debian Wheezy or Ubuntu (untested) installation
2410 into a Debian Edu Workstation:&lt;/p&gt;
2411
2412 &lt;ol&gt;
2413
2414 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
2415 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
2416 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
2417 our configuration.&lt;/li&gt;
2418 &lt;li&gt;Preseed debconf database with profile setup in
2419 /etc/debian-edu/config, and run tasksel to install packages
2420 according to the profile specified in the config above,
2421 overriding some of the Debian automation machinery.&lt;/li&gt;
2422 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
2423 that could not be done using preseeding.&lt;/li&gt;
2424 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
2425
2426 &lt;/ol&gt;
2427
2428 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
2429 replicated like this. Disk partitioning and LVM setup, for example.
2430 So this script just assume there is enough disk space to install all
2431 the needed packages.&lt;/p&gt;
2432
2433 &lt;p&gt;The script was created to help a Debian Edu student working on
2434 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
2435 Debian Edu client, and using it he can take the existing
2436 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
2437 transform it into a fully functioning Debian Edu Workstation (or
2438 Roaming Workstation, or whatever :).&lt;/p&gt;
2439
2440 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
2441 If a LXDE based Roaming workstation is wanted instead, modify the
2442 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
2443
2444 &lt;p&gt;&lt;pre&gt;
2445 PROFILE=&quot;Roaming-Workstation&quot;
2446 DESKTOP=&quot;lxde&quot;
2447 &lt;/pre&gt;&lt;/p&gt;
2448
2449 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
2450 the cloud, by starting with a virtual Debian installation at some
2451 virtual hosting service and setting up all the services on first
2452 boot.&lt;/p&gt;
2453 </description>
2454 </item>
2455
2456 <item>
2457 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
2458 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
2459 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
2460 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
2461 <description>&lt;P&gt;In January,
2462 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
2463 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
2464 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
2465 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
2466 marvellous construction system from Denmark. We also created
2467 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
2468 a place to take notes and write down our plans and hopes. And several
2469 people showed up to help. I was very happy to see the effect of my
2470 call. Since the small start, we have a debtags tag
2471 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
2472 tag for LEGO related packages, and now count 10 packages related to
2473 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
2474
2475 &lt;p&gt;&lt;table&gt;
2476 &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;
2477 &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;
2478 &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;
2479 &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;
2480 &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;
2481 &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;
2482 &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;
2483 &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;
2484 &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;
2485 &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;
2486 &lt;/table&gt;&lt;/p&gt;
2487
2488 &lt;p&gt;Some of these are available in Wheezy, and all but one are
2489 currently available in Jessie/testing. leocad is so far only
2490 available in experimental.&lt;/p&gt;
2491
2492 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
2493 adding the rest of the great free software tools available on Linux
2494 for LEGO designers.&lt;/p&gt;
2495 </description>
2496 </item>
2497
2498 <item>
2499 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
2500 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
2501 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
2502 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
2503 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
2504 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
2505 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
2506 Debian release, and I expect to move my machines at home over to it fairly
2507 soon.&lt;/p&gt;
2508
2509 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
2510 in particular make me very happy to see included. The
2511 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
2512 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
2513 included for the first time. Alongside similar programs like
2514 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
2515 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
2516 it allow for visual programming where syntax errors can not happen,
2517 and a friendly programming environment for learning to control the
2518 computer. Scratch will also be included in the next release of Debian
2519 Edu.&lt;/a&gt;
2520
2521 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
2522 Edu/Skolelinux release too. The
2523 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
2524 alpha release&lt;/a&gt; went out last week, and the next should soon
2525 follow.&lt;p&gt;
2526 </description>
2527 </item>
2528
2529 <item>
2530 <title>Isenkram 0.2 finally in the Debian archive</title>
2531 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
2532 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
2533 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
2534 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
2535 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
2536 for many months. I uploaded it to the Debian experimental suite
2537 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
2538
2539 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
2540 install to work with a pluggable hardware device. The suggestion pop
2541 up when the device is plugged in. For example if a Lego Mindstorm NXT
2542 is inserted, it will suggest to install the program needed to program
2543 the NXT controller. Give it a go, and report bugs and suggestions to
2544 BTS. :)&lt;/p&gt;
2545 </description>
2546 </item>
2547
2548 <item>
2549 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
2550 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
2551 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
2552 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
2553 <description>&lt;p&gt;My
2554 &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
2555 bitcoin related blog post&lt;/a&gt; mentioned that the new
2556 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
2557 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2558 2013-01-19, and have been available in unstable since then. It was
2559 automatically copied to Ubuntu, and is available in their Raring
2560 version too.&lt;/p&gt;
2561
2562 &lt;p&gt;But there is a strange problem with the build that block this new
2563 version from being available on the i386 and kfreebsd-i386
2564 architectures. For some strange reason, the autobuilders in Debian
2565 for these architectures fail to run the test suite on these
2566 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
2567 We are so far unable to reproduce it when building it manually, and
2568 no-one have been able to propose a fix. If you got an idea what is
2569 failing, please let us know via the BTS.&lt;/p&gt;
2570
2571 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
2572 I often run low on disk space, is the fact that the client will exit
2573 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
2574 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
2575 it. :)&lt;/p&gt;
2576
2577 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
2578 activities, please send Bitcoin donations to my address
2579 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2580 </description>
2581 </item>
2582
2583 <item>
2584 <title>Welcome to the world, Isenkram!</title>
2585 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
2586 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
2587 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
2588 <description>&lt;p&gt;Yesterday, I
2589 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
2590 for testers&lt;/a&gt; for my prototype for making Debian better at handling
2591 pluggable hardware devices, which I
2592 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
2593 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
2594 up, and caused me to really want to to open up the development to more
2595 people. But before I did this, I want to come up with a sensible name
2596 for this project. Today I finally decided on a new name, and I have
2597 renamed the project from hw-support-handler to this new name. In the
2598 process, I moved the source to git and made it available as a
2599 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
2600 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
2601 To fetch and build the latest version of the source, use&lt;/p&gt;
2602
2603 &lt;pre&gt;
2604 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2605 cd isenkram &amp;&amp; git-buildpackage -us -uc
2606 &lt;/pre&gt;
2607
2608 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
2609 want to hack on the source or improve the package, please go ahead.
2610 But please talk to me first on IRC or via email before you do major
2611 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
2612
2613 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
2614 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2615 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
2616 the German word eisenkram, for those that are familiar with that
2617 word.&lt;/p&gt;
2618
2619 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
2620 instructions, to avoid confusing people with an error from the signing
2621 process.&lt;/p&gt;
2622
2623 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
2624 clone argument to avoid the need for authentication.&lt;/p&gt;
2625 </description>
2626 </item>
2627
2628 <item>
2629 <title>First prototype ready making hardware easier to use in Debian</title>
2630 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
2631 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
2632 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
2633 <description>&lt;p&gt;Early this month I set out to try to
2634 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
2635 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
2636 prototype is working, and it is ready for a larger audience. To test
2637 it, fetch the
2638 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
2639 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
2640 package. You might have to log out and in again activate the
2641 autostart script.&lt;/p&gt;
2642
2643 &lt;p&gt;The design is simple:&lt;/p&gt;
2644
2645 &lt;ul&gt;
2646
2647 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
2648 hw-support-handlerd to start when the user log in.&lt;/li&gt;
2649
2650 &lt;li&gt;This program listen for kernel events about new hardware (directly
2651 from the kernel like udev does), not using HAL dbus events as I
2652 initially did.&lt;/li&gt;
2653
2654 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
2655 the APT database, a database
2656 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
2657 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
2658
2659 &lt;li&gt;If a package is mapped to the hardware in question, the package
2660 isn&#39;t installed yet and this is the first time the hardware was
2661 plugged in, show a desktop notification suggesting to install the
2662 package or packages.&lt;/li&gt;
2663
2664 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
2665 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
2666
2667 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
2668 package while showing progress information in a window.&lt;/li&gt;
2669
2670 &lt;/ul&gt;
2671
2672 &lt;p&gt;I still need to come up with a better name for the system. Here
2673 are some screen shots showing the prototype in action. First the
2674 notification, then the password request, and finally the request to
2675 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
2676
2677 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
2678 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
2679 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
2680 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
2681 &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;
2682
2683 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
2684 is already useful. The database of hardware to package mappings also
2685 need more work. It is currently compatible with the Ubuntu way of
2686 storing such information in the package control file, but could be
2687 changed to use other formats instead or in addition to the current
2688 method. I&#39;ve dropped the use of discover for this mapping, as the
2689 modalias approach is more flexible and easier to use on Linux as long
2690 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
2691
2692 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
2693 here is the command required to check out and build the source: Use
2694 &#39;&lt;tt&gt;svn checkout
2695 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2696 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
2697 devscripts package.&lt;/p&gt;
2698
2699 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
2700 renamed to Isenkram and the source moved from the Debian Edu
2701 subversion repository to a Debian collab-maint git repository. See
2702 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
2703 instructions&lt;/a&gt; for details.&lt;/p&gt;
2704 </description>
2705 </item>
2706
2707 <item>
2708 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
2709 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
2710 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
2711 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
2712 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
2713 suddenly in bed. With a quiet whimper, it went completely quiet and
2714 black. The power button was no longer able to turn it on. It was a
2715 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2716 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2717 Compaq I had before that. Now I need to find a replacement. To keep
2718 going during Christmas, I moved the one year old SSD disk to my old
2719 X40 where it fitted (only one I had left that could use it), but it is
2720 not a durable solution.
2721
2722 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
2723 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
2724
2725 &lt;ul&gt;
2726
2727 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
2728 than A4).&lt;/li&gt;
2729 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
2730 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
2731 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
2732 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
2733 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
2734 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
2735 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
2736 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
2737 size).&lt;/li&gt;
2738 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
2739 X.org packages.&lt;/li&gt;
2740 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
2741 the time).
2742
2743 &lt;/ul&gt;
2744
2745 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
2746 list. The reason is simply that the specifications on laptops the
2747 last 10-15 years have been sufficient for my needs, and I have to look
2748 at other features to choose my laptop. But are there still made as
2749 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
2750 robust, and Thinkpads seem to be heading in the wrong direction since
2751 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
2752 still be useful.&lt;/p&gt;
2753
2754 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
2755 external keyboard? I&#39;ll have to check the
2756 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
2757 well-supported laptops, or perhaps just buy one preinstalled from one
2758 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
2759 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
2760 </description>
2761 </item>
2762
2763 <item>
2764 <title>How to find a browser plugin supporting a given MIME type</title>
2765 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
2766 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
2767 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
2768 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
2769 install to get support for a given MIME type. Thanks to
2770 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
2771 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
2772 Unfortunately, not very many packages provide the needed meta
2773 information, Anyway, here is a small script to look up all browser
2774 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
2775
2776 &lt;pre&gt;
2777 #!/usr/bin/python
2778 import sys
2779 import apt
2780 def pkgs_handling_mimetype(mimetype):
2781 cache = apt.Cache()
2782 cache.open(None)
2783 thepkgs = []
2784 for pkg in cache:
2785 version = pkg.candidate
2786 if version is None:
2787 version = pkg.installed
2788 if version is None:
2789 continue
2790 record = version.record
2791 if not record.has_key(&#39;Npp-MimeType&#39;):
2792 continue
2793 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
2794 for t in mime_types:
2795 t = t.rstrip().strip()
2796 if t == mimetype:
2797 thepkgs.append(pkg.name)
2798 return thepkgs
2799 mimetype = &quot;audio/ogg&quot;
2800 if 1 &lt; len(sys.argv):
2801 mimetype = sys.argv[1]
2802 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
2803 for pkg in pkgs_handling_mimetype(mimetype):
2804 print &quot; %s&quot; %pkg
2805 &lt;/pre&gt;
2806
2807 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
2808
2809 &lt;pre&gt;
2810 % ./apt-find-browserplug-for-mimetype
2811 Browser plugin packages supporting audio/ogg:
2812 gecko-mediaplayer
2813 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
2814 Browser plugin packages supporting application/x-shockwave-flash:
2815 browser-plugin-gnash
2816 %
2817 &lt;/pre&gt;
2818
2819 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
2820 itself to query for plugins and propose to install the needed
2821 packages. It would be great if Debian supported such feature too. Is
2822 anyone working on adding it?&lt;/p&gt;
2823
2824 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
2825 request for icweasel support for this feature is
2826 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
2827 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
2828 of manpower and wish for a different design is the reason thus feature
2829 is not yet in iceweasel from Debian.&lt;/p&gt;
2830 </description>
2831 </item>
2832
2833 <item>
2834 <title>What is the most supported MIME type in Debian?</title>
2835 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
2836 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
2837 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
2838 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
2839 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
2840 proposal to make it possible for a Desktop application to propose to
2841 the user some package to install to gain support for a given MIME
2842 type, font, library etc. that is currently missing. With such
2843 mechanism in place, it would be possible for the desktop to
2844 automatically propose and install leocad if some LDraw file is
2845 downloaded by the browser.&lt;/p&gt;
2846
2847 &lt;p&gt;To get some idea about the current content of the archive, I decided
2848 to write a simple program to extract all .desktop files from the
2849 Debian archive and look up the claimed MIME support there. The result
2850 can be found on the
2851 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
2852 site&lt;/a&gt;. Using the collected information, it become possible to
2853 answer the question in the title. Here are the 20 most supported MIME
2854 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
2855 The complete list is available from the link above.&lt;/p&gt;
2856
2857 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
2858
2859 &lt;pre&gt;
2860 count MIME type
2861 ----- -----------------------
2862 32 text/plain
2863 30 audio/mpeg
2864 29 image/png
2865 28 image/jpeg
2866 27 application/ogg
2867 26 audio/x-mp3
2868 25 image/tiff
2869 25 image/gif
2870 22 image/bmp
2871 22 audio/x-wav
2872 20 audio/x-flac
2873 19 audio/x-mpegurl
2874 18 video/x-ms-asf
2875 18 audio/x-musepack
2876 18 audio/x-mpeg
2877 18 application/x-ogg
2878 17 video/mpeg
2879 17 audio/x-scpls
2880 17 audio/ogg
2881 16 video/x-ms-wmv
2882 &lt;/pre&gt;
2883
2884 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
2885
2886 &lt;pre&gt;
2887 count MIME type
2888 ----- -----------------------
2889 33 text/plain
2890 32 image/png
2891 32 image/jpeg
2892 29 audio/mpeg
2893 27 image/gif
2894 26 image/tiff
2895 26 application/ogg
2896 25 audio/x-mp3
2897 22 image/bmp
2898 21 audio/x-wav
2899 19 audio/x-mpegurl
2900 19 audio/x-mpeg
2901 18 video/mpeg
2902 18 audio/x-scpls
2903 18 audio/x-flac
2904 18 application/x-ogg
2905 17 video/x-ms-asf
2906 17 text/html
2907 17 audio/x-musepack
2908 16 image/x-xbitmap
2909 &lt;/pre&gt;
2910
2911 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
2912
2913 &lt;pre&gt;
2914 count MIME type
2915 ----- -----------------------
2916 31 text/plain
2917 31 image/png
2918 31 image/jpeg
2919 29 audio/mpeg
2920 28 application/ogg
2921 27 image/gif
2922 26 image/tiff
2923 26 audio/x-mp3
2924 23 audio/x-wav
2925 22 image/bmp
2926 21 audio/x-flac
2927 20 audio/x-mpegurl
2928 19 audio/x-mpeg
2929 18 video/x-ms-asf
2930 18 video/mpeg
2931 18 audio/x-scpls
2932 18 application/x-ogg
2933 17 audio/x-musepack
2934 16 video/x-ms-wmv
2935 16 video/x-msvideo
2936 &lt;/pre&gt;
2937
2938 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
2939 information mentioned in DEP-11. I have not yet had time to look at
2940 it, but hope the PackageKit people in Debian are on top of these
2941 issues.&lt;/p&gt;
2942
2943 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
2944 discovering a typo in my script.&lt;/p&gt;
2945 </description>
2946 </item>
2947
2948 <item>
2949 <title>Using modalias info to find packages handling my hardware</title>
2950 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
2951 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
2952 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
2953 <description>&lt;p&gt;Yesterday, I wrote about the
2954 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
2955 values provided by the Linux kernel&lt;/a&gt; following my hope for
2956 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
2957 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
2958 modalias values attached to package names can be used to map packages
2959 to hardware. This allow the system to look up and suggest relevant
2960 packages when I plug in some new hardware into my machine, and replace
2961 discover and discover-data as the database used to map hardware to
2962 packages.&lt;/p&gt;
2963
2964 &lt;p&gt;I create a modaliases file with entries like the following,
2965 containing package name, kernel module name (if relevant, otherwise
2966 the package name) and globs matching the relevant hardware
2967 modalias.&lt;/p&gt;
2968
2969 &lt;p&gt;&lt;blockquote&gt;
2970 Package: package-name
2971 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
2972 &lt;/blockquote&gt;&lt;/p&gt;
2973
2974 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
2975 for a given modalias value using this file.&lt;/p&gt;
2976
2977 &lt;p&gt;An entry like this would suggest the video and picture application
2978 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
2979
2980 &lt;p&gt;&lt;blockquote&gt;
2981 Package: cheese
2982 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
2983 &lt;/blockquote&gt;&lt;/p&gt;
2984
2985 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
2986 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
2987
2988 &lt;p&gt;&lt;blockquote&gt;
2989 Package: pcmciautils
2990 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
2991 &lt;/blockquote&gt;&lt;/p&gt;
2992
2993 &lt;p&gt;An entry like this would suggest the package colorhug-client when
2994 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
2995
2996 &lt;p&gt;&lt;blockquote&gt;
2997 Package: colorhug-client
2998 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
2999 &lt;/blockquote&gt;&lt;/p&gt;
3000
3001 &lt;p&gt;I believe the format is compatible with the format of the Packages
3002 file in the Debian archive. Ubuntu already uses their Packages file
3003 to store their mappings from packages to hardware.&lt;/p&gt;
3004
3005 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
3006 announce the hardware it support in a way my prototype understand.
3007 This allow those publishing packages in an APT source outside the
3008 Debian archive as well as those backporting packages to make sure the
3009 hardware mapping are included in the package meta information. I&#39;ve
3010 tested such header in the pymissile package, and its modalias mapping
3011 is working as it should with my prototype. It even made it to Ubuntu
3012 Raring.&lt;/p&gt;
3013
3014 &lt;p&gt;To test if it was possible to look up supported hardware using only
3015 the shell tools available in the Debian installer, I wrote a shell
3016 implementation of the lookup code. The idea is to create files for
3017 each modalias and let the shell do the matching. Please check out and
3018 try the
3019 &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;
3020 shell script. It run without any extra dependencies and fetch the
3021 hardware mappings from the Debian archive and the subversion
3022 repository where I currently work on my prototype.&lt;/p&gt;
3023
3024 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
3025 install yubikey-personalization:&lt;/p&gt;
3026
3027 &lt;p&gt;&lt;blockquote&gt;
3028 % ./hw-support-lookup
3029 &lt;br&gt;yubikey-personalization
3030 &lt;br&gt;%
3031 &lt;/blockquote&gt;&lt;/p&gt;
3032
3033 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
3034 propose to install the pcmciautils package:&lt;/p&gt;
3035
3036 &lt;p&gt;&lt;blockquote&gt;
3037 % ./hw-support-lookup
3038 &lt;br&gt;pcmciautils
3039 &lt;br&gt;%
3040 &lt;/blockquote&gt;&lt;/p&gt;
3041
3042 &lt;p&gt;If you know of any hardware-package mapping that should be added to
3043 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
3044 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
3045
3046 &lt;p&gt;It could be possible to generate several of the mappings between
3047 packages and hardware. One source would be to look at packages with
3048 kernel modules, ie packages with *.ko files in /lib/modules/, and
3049 extract their modalias information. Another would be to look at
3050 packages with udev rules, ie packages with files in
3051 /lib/udev/rules.d/, and extract their vendor/model information to
3052 generate a modalias matching rule. I have not tested any of these to
3053 see if it work.&lt;/p&gt;
3054
3055 &lt;p&gt;If you want to help implementing a system to let us propose what
3056 packages to install when new hardware is plugged into a Debian
3057 machine, please send me an email or talk to me on
3058 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3059 </description>
3060 </item>
3061
3062 <item>
3063 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
3064 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
3065 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
3066 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
3067 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
3068 information, to find the packages that support a given piece of
3069 hardware, I refreshed my memory regarding modalias values, and decided
3070 to document the details. Here are my findings so far, also available
3071 in
3072 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3073 Debian Edu subversion repository&lt;/a&gt;:
3074
3075 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3076
3077 &lt;p&gt;This document try to explain what the different types of modalias
3078 values stands for. It is in part based on information from
3079 &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;,
3080 &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;,
3081 &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
3082 &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;.
3083
3084 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3085 this shell script:&lt;/p&gt;
3086
3087 &lt;pre&gt;
3088 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3089 &lt;/pre&gt;
3090
3091 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3092 using modinfo:&lt;/p&gt;
3093
3094 &lt;pre&gt;
3095 % /sbin/modinfo psmouse | grep alias:
3096 alias: serio:ty05pr*id*ex*
3097 alias: serio:ty01pr*id*ex*
3098 %
3099 &lt;/pre&gt;
3100
3101 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3102
3103 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3104 Bridge memory controller:&lt;/p&gt;
3105
3106 &lt;p&gt;&lt;blockquote&gt;
3107 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3108 &lt;/blockquote&gt;&lt;/p&gt;
3109
3110 &lt;p&gt;This represent these values:&lt;/p&gt;
3111
3112 &lt;pre&gt;
3113 v 00008086 (vendor)
3114 d 00002770 (device)
3115 sv 00001028 (subvendor)
3116 sd 000001AD (subdevice)
3117 bc 06 (bus class)
3118 sc 00 (bus subclass)
3119 i 00 (interface)
3120 &lt;/pre&gt;
3121
3122 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3123 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3124 0600. The 0600 class is a host bridge. Other useful bus values are
3125 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3126
3127 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3128 means.&lt;/p&gt;
3129
3130 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3131
3132 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3133 USB hub in a laptop:&lt;/p&gt;
3134
3135 &lt;p&gt;&lt;blockquote&gt;
3136 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3137 &lt;/blockquote&gt;&lt;/p&gt;
3138
3139 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3140
3141 &lt;pre&gt;
3142 v 1D6B (device vendor)
3143 p 0001 (device product)
3144 d 0206 (bcddevice)
3145 dc 09 (device class)
3146 dsc 00 (device subclass)
3147 dp 00 (device protocol)
3148 ic 09 (interface class)
3149 isc 00 (interface subclass)
3150 ip 00 (interface protocol)
3151 &lt;/pre&gt;
3152
3153 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3154 class is in the interface class section. For a simple USB web camera,
3155 these alias entries show up:&lt;/p&gt;
3156
3157 &lt;p&gt;&lt;blockquote&gt;
3158 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3159 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3160 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3161 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3162 &lt;/blockquote&gt;&lt;/p&gt;
3163
3164 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3165 camera), 0101 is audio control device and 0102 is audio streaming (aka
3166 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3167
3168 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3169
3170 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3171 receiver in a Thinkpad X40:&lt;/p&gt;
3172
3173 &lt;p&gt;&lt;blockquote&gt;
3174 acpi:IBM0071:PNP0511:
3175 &lt;/blockquote&gt;&lt;/p&gt;
3176
3177 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3178
3179 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3180
3181 &lt;p&gt;The DMI table contain lots of information about the computer case
3182 and model. This is an entry for a IBM Thinkpad X40, fetched from
3183 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3184
3185 &lt;p&gt;&lt;blockquote&gt;
3186 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3187 &lt;/blockquote&gt;&lt;/p&gt;
3188
3189 &lt;p&gt;The values present are&lt;/p&gt;
3190
3191 &lt;pre&gt;
3192 bvn IBM (BIOS vendor)
3193 bvr 1UETB6WW(1.66) (BIOS version)
3194 bd 06/15/2005 (BIOS date)
3195 svn IBM (system vendor)
3196 pn 2371H4G (product name)
3197 pvr ThinkPadX40 (product version)
3198 rvn IBM (board vendor)
3199 rn 2371H4G (board name)
3200 rvr NotAvailable (board version)
3201 cvn IBM (chassis vendor)
3202 ct 10 (chassis type)
3203 cvr NotAvailable (chassis version)
3204 &lt;/pre&gt;
3205
3206 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3207 found in the dmidecode source:&lt;/p&gt;
3208
3209 &lt;pre&gt;
3210 3 Desktop
3211 4 Low Profile Desktop
3212 5 Pizza Box
3213 6 Mini Tower
3214 7 Tower
3215 8 Portable
3216 9 Laptop
3217 10 Notebook
3218 11 Hand Held
3219 12 Docking Station
3220 13 All In One
3221 14 Sub Notebook
3222 15 Space-saving
3223 16 Lunch Box
3224 17 Main Server Chassis
3225 18 Expansion Chassis
3226 19 Sub Chassis
3227 20 Bus Expansion Chassis
3228 21 Peripheral Chassis
3229 22 RAID Chassis
3230 23 Rack Mount Chassis
3231 24 Sealed-case PC
3232 25 Multi-system
3233 26 CompactPCI
3234 27 AdvancedTCA
3235 28 Blade
3236 29 Blade Enclosing
3237 &lt;/pre&gt;
3238
3239 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3240 table. For example my home server is a tower, but the DMI modalias
3241 claim it is a desktop.&lt;/p&gt;
3242
3243 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3244
3245 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3246 test machine:&lt;/p&gt;
3247
3248 &lt;p&gt;&lt;blockquote&gt;
3249 serio:ty01pr00id00ex00
3250 &lt;/blockquote&gt;&lt;/p&gt;
3251
3252 &lt;p&gt;The values present are&lt;/p&gt;
3253
3254 &lt;pre&gt;
3255 ty 01 (type)
3256 pr 00 (prototype)
3257 id 00 (id)
3258 ex 00 (extra)
3259 &lt;/pre&gt;
3260
3261 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3262 the valid values are.&lt;/p&gt;
3263
3264 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3265
3266 &lt;p&gt;There are heaps of other modalias subtypes according to
3267 file2alias.c. There is the rest of the list from that source: amba,
3268 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3269 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3270 vmbus, x86cpu and zorro. I did not spend time documenting all of
3271 these, as they do not seem relevant for my intended use with mapping
3272 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3273
3274 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3275
3276 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3277 one can use the following shell script:&lt;/p&gt;
3278
3279 &lt;pre&gt;
3280 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3281 echo &quot;$id&quot; ; \
3282 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3283 done
3284 &lt;/pre&gt;
3285
3286 &lt;p&gt;The output can look like this (only the first few entries as the
3287 list is very long on my test machine):&lt;/p&gt;
3288
3289 &lt;pre&gt;
3290 acpi:ACPI0003:
3291 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3292 acpi:device:
3293 FATAL: Module acpi:device: not found.
3294 acpi:IBM0068:
3295 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3296 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3297 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3298 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3299 acpi:IBM0071:PNP0511:
3300 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3301 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3302 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3303 [...]
3304 &lt;/pre&gt;
3305
3306 &lt;p&gt;If you want to help implementing a system to let us propose what
3307 packages to install when new hardware is plugged into a Debian
3308 machine, please send me an email or talk to me on
3309 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3310
3311 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3312 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3313 in /sys/ with space in them.&lt;/p&gt;
3314 </description>
3315 </item>
3316
3317 <item>
3318 <title>Moved the pymissile Debian packaging to collab-maint</title>
3319 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3320 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3321 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3322 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3323 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3324 Launcher and updated the Debian package
3325 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3326 sure udev will fix the device permissions when it is plugged in. I
3327 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3328 hopefully make the package be proposed by jockey in Ubuntu when a user
3329 plug in his rocket launcher. In the process I moved the source to a
3330 git repository under collab-maint, to make it easier for any DD to
3331 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3332 is not very active, but the software still work for me even after five
3333 years of relative silence. The new git repository is not listed in
3334 the uploaded package yet, because I want to test the other changes a
3335 bit more before I upload the new version. If you want to check out
3336 the new version with a .desktop file included, visit the
3337 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3338 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3339 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3340 </description>
3341 </item>
3342
3343 <item>
3344 <title>Lets make hardware dongles easier to use in Debian</title>
3345 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3346 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3347 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3348 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3349 general, is that there is a great package management system with the
3350 ability to automatically install software packages by downloading them
3351 from the distribution mirrors, but no way to get it to automatically
3352 install the packages I need to use the hardware I plug into my
3353 machine. Even if the package to use it is easily available from the
3354 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3355 suggest to automatically install the python-nxt, nbc and t2n packages
3356 I need to talk to it. When I plug in a Yubikey, it could propose the
3357 yubikey-personalization package. The information required to do this
3358 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
3359
3360 &lt;p&gt;Some years ago, I proposed to
3361 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
3362 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
3363 simple:
3364
3365 &lt;ul&gt;
3366
3367 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
3368 starting when a user log in.&lt;/li&gt;
3369
3370 &lt;li&gt;Set this program up to listen for kernel events emitted when new
3371 hardware is inserted into the computer.&lt;/li&gt;
3372
3373 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
3374 database mapping to packages, and take note of any non-installed
3375 packages.&lt;/li&gt;
3376
3377 &lt;li&gt;Show a message to the user proposing to install the discovered
3378 package, and make it easy to install it.&lt;/li&gt;
3379
3380 &lt;/ul&gt;
3381
3382 &lt;p&gt;I am not sure what the best way to implement this is, but my
3383 initial idea was to use dbus events to discover new hardware, the
3384 discover database to find packages and
3385 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
3386 packages.&lt;/p&gt;
3387
3388 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
3389 draft package is now checked into
3390 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3391 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
3392 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
3393 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3394 the relevant packages in Debian, and uploaded a new version
3395 2.2013.01.09 to unstable. I also discovered that the current
3396 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
3397 package in Debian no longer discovered any USB devices, because
3398 /proc/bus/usb/devices is no longer present. I ported it to use
3399 libusb as a fall back option to get it working. The fixed package
3400 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
3401 because of the freeze).&lt;/p&gt;
3402
3403 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
3404 desktop notification to show up (only once, the first time it is
3405 inserted):&lt;/p&gt;
3406
3407 &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;
3408
3409 &lt;p&gt;For this prototype to be really useful, some way to automatically
3410 install the proposed packages by pressing the &quot;Please install
3411 program(s)&quot; button should to be implemented.&lt;/p&gt;
3412
3413 &lt;p&gt;If this idea seem useful to you, and you want to help make it
3414 happen, please help me update the discover-data database with mappings
3415 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
3416 list the package you would like to have installed when a given
3417 hardware device is inserted into your computer, and report bugs using
3418 reportbug if it isn&#39;t. Or, if you know of a better way to provide
3419 such mapping, please let me know.&lt;/p&gt;
3420
3421 &lt;p&gt;This prototype need more work, and there are several questions that
3422 should be considered before it is ready for production use. Is dbus
3423 the correct way to detect new hardware? At the moment I look for HAL
3424 dbus events on the system bus, because that is the events I could see
3425 on my Debian Squeeze KDE desktop. Are there better events to use?
3426 How should the user be notified? Is the desktop notification
3427 mechanism the best option, or should the background daemon raise a
3428 popup instead? How should packages be installed? When should they
3429 not be installed?&lt;/p&gt;
3430
3431 &lt;p&gt;If you want to help getting such feature implemented in Debian,
3432 please send me an email. :)&lt;/p&gt;
3433 </description>
3434 </item>
3435
3436 <item>
3437 <title>New IRC channel for LEGO designers using Debian</title>
3438 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
3439 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
3440 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
3441 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
3442 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
3443 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
3444 discovered I had to build all the tools myself because none were
3445 already in Debian Squeeze. If Debian support for LEGO is something
3446 you care about, please join me on the IRC channel
3447 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
3448 irc.debian.org). There is a lot that could be done to improve the
3449 Debian support for LEGO designers. For example both CAD software
3450 and Mindstorm compilers are missing. :)&lt;/p&gt;
3451
3452 &lt;p&gt;Update 2012-01-03: A
3453 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
3454 including links to Lego related packages is now available.&lt;/p&gt;
3455 </description>
3456 </item>
3457
3458 <item>
3459 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
3460 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
3461 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
3462 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
3463 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
3464 year! I hope next year will prove to be a good year.&lt;/p&gt;
3465
3466 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
3467 decentralised &quot;currency&quot; that allow people to transfer bitcoins
3468 between each other with minimal overhead, is a very interesting
3469 experiment. And as I wrote a few days ago, the bitcoin situation in
3470 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
3471 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
3472 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
3473 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
3474 for one of the ftpmasters to approve the new bitcoin-qt package
3475 name.&lt;/p&gt;
3476
3477 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
3478 team in Debian, you can easily test the package in Debian Squeeze
3479 using the following steps to get a set of working packages:&lt;/p&gt;
3480
3481 &lt;blockquote&gt;&lt;pre&gt;
3482 git clone git://git.debian.org/git/collab-maint/bitcoin
3483 cd bitcoin
3484 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3485 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3486 &lt;/pre&gt;&lt;/blockquote&gt;
3487
3488 &lt;p&gt;You might have to install some build dependencies as well. The
3489 list of commands should give you two packages, bitcoind and
3490 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3491 client will download the complete set of bitcoin &quot;blocks&quot;, which need
3492 around 5.6 GiB of data on my machine at the moment. Make sure your
3493 ~/.bitcoin/ directory have lots of spare room if you want to download
3494 all the blocks. The client will warn if the disk is getting full, so
3495 there is not really a problem if you got too little room, but you will
3496 not be able to get all the features out of the client.&lt;/p&gt;
3497
3498 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3499 activities, please send Bitcoin donations to my address
3500 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3501 </description>
3502 </item>
3503
3504 <item>
3505 <title>A word on bitcoin support in Debian</title>
3506 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
3507 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
3508 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
3509 <description>&lt;p&gt;It has been a while since I wrote about
3510 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
3511 peer-to-peer based crypto-currency, and the reason is simply that I
3512 have been busy elsewhere. But two days ago, I started looking at the
3513 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
3514 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
3515 is now maintained by a
3516 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
3517 people&lt;/a&gt;, and the grunt work had already been done by this team. We
3518 owe a huge thank you to all these team members. :)
3519 But I was sad to discover that the bitcoin client is missing in
3520 Wheezy. It is only available in Sid (and an outdated client from
3521 backports). The client had several RC bugs registered in BTS blocking
3522 it from entering testing. To try to help the team and improve the
3523 situation, I spent some time providing patches and triaging the bug
3524 reports. I also had a look at the bitcoin package available from Matt
3525 Corallo in a
3526 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
3527 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
3528 Debian package.&lt;/p&gt;
3529
3530 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
3531 IRC, I pushed several patches into the collab-maint git repository to
3532 improve the package. It now contains fixes for the RC issues (not from
3533 me, but fixed by Scott Howard), build rules for a Qt GUI client
3534 package, konqueror support for the bitcoin: URI and bash completion
3535 setup. As I work on Debian Squeeze, I also created
3536 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
3537 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
3538 it and try to integrate it into the git repository before uploading a
3539 new version to unstable.
3540
3541 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
3542 centralized control currently exercised in the monetary system. I
3543 find it completely unacceptable that the USA government is collecting
3544 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3545 that the major credit card companies can block legal money
3546 transactions to Wikileaks. But for bitcoin to succeed, more people
3547 need to use bitcoins, and more people need to accept bitcoins when
3548 they sell products and services. Improving the bitcoin support in
3549 Debian is a small step in the right direction, but not enough.
3550 Unfortunately the user experience when browsing the web and wanting to
3551 pay with bitcoin is still not very good. The bitcoin: URI is a step
3552 in the right direction, but need to work in most or every browser in
3553 use. Also the bitcoin-qt client is too heavy to fire up to do a
3554 quick transaction. I believe there are other clients available, but
3555 have not tested them.&lt;/p&gt;
3556
3557 &lt;p&gt;My
3558 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
3559 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
3560 I received 20.15 BTC so far on the address I provided in my blog two
3561 years ago, as can be
3562 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
3563 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
3564 donation. The blockexplorer service demonstrates quite well that
3565 bitcoin is not quite anonymous and untracked. :) I wonder if the
3566 number of users have gone up since then. If you use bitcoin and want
3567 to show your support of my activity, please send Bitcoin donations to
3568 the same address as last time,
3569 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3570 </description>
3571 </item>
3572
3573 <item>
3574 <title>Git repository for song book for Computer Scientists</title>
3575 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
3576 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
3577 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
3578 <description>&lt;p&gt;As I
3579 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
3580 this summer&lt;/a&gt;, I have created a Computer Science song book a few
3581 years ago, and today I finally found time to create a public
3582 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
3583 repository for the project&lt;/a&gt;.&lt;/p&gt;
3584
3585 &lt;p&gt;If you want to help out, please clone the source and submit patches
3586 to the HTML version. To generate the PDF and PostScript version,
3587 please use prince XML, or let me know about a useful free software
3588 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
3589
3590 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
3591 PostScript formats at
3592 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
3593 Science Songbook&lt;/a&gt;.&lt;/p&gt;
3594 </description>
3595 </item>
3596
3597 <item>
3598 <title>Gratulerer med 19-årsdagen, Debian!</title>
3599 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
3600 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
3601 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
3602 <description>&lt;p&gt;I dag fyller
3603 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
3604 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
3605 si gratulerer med dagen, Debian!&lt;/p&gt;
3606 </description>
3607 </item>
3608
3609 <item>
3610 <title>Song book for Computer Scientists</title>
3611 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
3612 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
3613 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
3614 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
3615 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
3616 collecting computer related songs for use at parties. The original
3617 version was written in LaTeX, but a few years ago I got help from
3618 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3619 while keeping the ability to create a nice book in PDF format. I have
3620 not had time to maintain the book for a while now, and guess I should
3621 put it up on some public version control repository where others can
3622 help me extend and update the book. If anyone is volunteering to help
3623 me with this, send me an email. Also let me know if there are songs
3624 missing in my book.&lt;/p&gt;
3625
3626 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
3627 me today that I really should let all my readers share the joys of
3628 singing out load about programming, computers and computer networks.
3629 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
3630 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
3631 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
3632 Computer Science Songbook&lt;/a&gt;.
3633 </description>
3634 </item>
3635
3636 <item>
3637 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
3638 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
3639 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
3640 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
3641 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
3642 around 1000 at the moment. To be able to get help from the vendors
3643 when something go wrong, we want to keep the firmware on the servers
3644 up to date. If the firmware isn&#39;t the latest and greatest, the
3645 vendors typically refuse to start debugging any problems until the
3646 firmware is upgraded. So before every reboot, we want to upgrade the
3647 firmware, and we would really like everyone handling servers at the
3648 university to do this themselves when they plan to reboot a machine.
3649 For that to happen we at the unix server admin group need to provide
3650 the tools to do so.&lt;/p&gt;
3651
3652 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
3653 fetch and install the latest firmware for the servers we got. Most of
3654 our hardware are from Dell and HP, so I have focused on these servers
3655 so far. This blog post is about the Dell part.&lt;/P&gt;
3656
3657 &lt;p&gt;On the Dell FTP site I was lucky enough to find
3658 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
3659 with firmware information for all 11th generation servers, listing
3660 which firmware should be used on a given model and where on the FTP
3661 site I can find it. Using a simple perl XML parser I can then
3662 download the shell scripts Dell provides to do firmware upgrades from
3663 within Linux and reboot when all the firmware is primed and ready to
3664 be activated on the first reboot.&lt;/p&gt;
3665
3666 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
3667 Are there anyone working on similar tools for firmware upgrading all
3668 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
3669
3670 &lt;p&gt;&lt;pre&gt;
3671 #!/usr/bin/perl
3672 use strict;
3673 use warnings;
3674 use File::Temp qw(tempdir);
3675 BEGIN {
3676 # Install needed RHEL packages if missing
3677 my %rhelmodules = (
3678 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
3679 );
3680 for my $module (keys %rhelmodules) {
3681 eval &quot;use $module;&quot;;
3682 if ($@) {
3683 my $pkg = $rhelmodules{$module};
3684 system(&quot;yum install -y $pkg&quot;);
3685 eval &quot;use $module;&quot;;
3686 }
3687 }
3688 }
3689 my $errorsto = &#39;pere@hungry.com&#39;;
3690
3691 upgrade_dell();
3692
3693 exit 0;
3694
3695 sub run_firmware_script {
3696 my ($opts, $script) = @_;
3697 unless ($script) {
3698 print STDERR &quot;fail: missing script name\n&quot;;
3699 exit 1
3700 }
3701 print STDERR &quot;Running $script\n\n&quot;;
3702
3703 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
3704 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
3705 } else {
3706 print STDERR &quot;fail: firmware script returned error\n&quot;;
3707 }
3708 }
3709
3710 sub run_firmware_scripts {
3711 my ($opts, @dirs) = @_;
3712 # Run firmware packages
3713 for my $dir (@dirs) {
3714 print STDERR &quot;info: Running scripts in $dir\n&quot;;
3715 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
3716 while (my $s = readdir $dh) {
3717 next if $s =~ m/^\.\.?/;
3718 run_firmware_script($opts, &quot;$dir/$s&quot;);
3719 }
3720 closedir $dh;
3721 }
3722 }
3723
3724 sub download {
3725 my $url = shift;
3726 print STDERR &quot;info: Downloading $url\n&quot;;
3727 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
3728 }
3729
3730 sub upgrade_dell {
3731 my @dirs;
3732 my $product = `dmidecode -s system-product-name`;
3733 chomp $product;
3734
3735 if ($product =~ m/PowerEdge/) {
3736
3737 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
3738 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
3739
3740 my $tmpdir = tempdir(
3741 CLEANUP =&gt; 1
3742 );
3743 chdir($tmpdir);
3744 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
3745 system(&#39;gunzip Catalog.xml.gz&#39;);
3746 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
3747 # -q is quiet, disabling interactivity and reducing console output
3748 my $fwopts = &quot;-q&quot;;
3749 if (@paths) {
3750 for my $url (@paths) {
3751 fetch_dell_fw($url);
3752 }
3753 run_firmware_scripts($fwopts, $tmpdir);
3754 } else {
3755 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3756 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3757 }
3758 chdir(&#39;/&#39;);
3759 } else {
3760 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3761 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3762 }
3763 }
3764
3765 sub fetch_dell_fw {
3766 my $path = shift;
3767 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
3768 download($url);
3769 }
3770
3771 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
3772 # firmware packages to download from Dell. Only work for Linux
3773 # machines and 11th generation Dell servers.
3774 sub fetch_dell_fw_list {
3775 my $filename = shift;
3776
3777 my $product = `dmidecode -s system-product-name`;
3778 chomp $product;
3779 my ($mybrand, $mymodel) = split(/\s+/, $product);
3780
3781 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
3782
3783 my $xml = XMLin($filename);
3784 my @paths;
3785 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
3786 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
3787 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
3788 my $oscode;
3789 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
3790 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
3791 } else {
3792 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
3793 }
3794 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
3795 {
3796 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
3797 }
3798 }
3799 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
3800 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
3801
3802 # Drop application packages, only firmware and BIOS
3803 next if &#39;APAC&#39; eq $componenttype;
3804
3805 my $cpath = $component-&gt;{path};
3806 for my $path (@paths) {
3807 if ($cpath =~ m%/$path$%) {
3808 push(@paths, $cpath);
3809 }
3810 }
3811 }
3812 return @paths;
3813 }
3814 &lt;/pre&gt;
3815
3816 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
3817 it could work on other platforms with some tweaking. Anyone know a
3818 index like Catalog.xml is available from HP for HP servers? At the
3819 moment I maintain a similar list manually and it is quickly getting
3820 outdated.&lt;/p&gt;
3821 </description>
3822 </item>
3823
3824 <item>
3825 <title>How is booting into runlevel 1 different from single user boots?</title>
3826 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
3827 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
3828 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
3829 <description>&lt;p&gt;Wouter Verhelst have some
3830 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
3831 comments and opinions&lt;/a&gt; on my blog post on
3832 &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
3833 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
3834 &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
3835 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
3836 small piece of his comment now, and though it best to address the
3837 misunderstanding he bring forward:&lt;/p&gt;
3838
3839 &lt;p&gt;&lt;blockquote&gt;
3840 Currently, a system admin has four options: [...] boot to a
3841 single-user system (by adding &#39;single&#39; to the kernel command line;
3842 this runs rcS and rc1 scripts)
3843 &lt;/blockquote&gt;&lt;/p&gt;
3844
3845 &lt;p&gt;This make me believe Wouter believe booting into single user mode
3846 and booting into runlevel 1 is the same. I am not surprised he
3847 believe this, because it would make sense and is a quite sensible
3848 thing to believe. But because the boot in Debian is slightly broken,
3849 runlevel 1 do not work properly and it isn&#39;t the same as single user
3850 mode. I&#39;ll try to explain what is actually happing, but it is a bit
3851 hard to explain.&lt;/p&gt;
3852
3853 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
3854 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
3855 executed in single user mode is sulogin. Single user mode is a boot
3856 state &quot;between&quot; the runlevels, and when booting into single user mode,
3857 only the scripts in /etc/rcS.d/ are executed before the init process
3858 enters the single user state. When switching to runlevel 1, the state
3859 is in fact not ending in runlevel 1, but it passes through runlevel 1
3860 and end up in the single user mode (see /etc/rc1.d/S03single, which
3861 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
3862 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
3863 mode enabled by /etc/rcS.d/ (which is more like the initial boot
3864 mode).&lt;/p&gt;
3865
3866 &lt;p&gt;This summary might make it clearer. When booting for the first
3867 time into single user mode, the following commands are executed:
3868 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
3869 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
3870 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
3871 trying to continue after visiting single user mode. Not all services
3872 are started again as they should, causing the machine to end up in an
3873 unpredicatble state. This is why Debian admins recommend rebooting
3874 after visiting single user mode.&lt;/p&gt;
3875
3876 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
3877 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
3878 to runlevel 1, the services started from /etc/rcS.d/ are not properly
3879 stopped when passing through the scripts in /etc/rc1.d/, and not
3880 started again when switching away from runlevel 1 to the runlevels
3881 2-5. I believe the problem is best fixed by moving all the scripts
3882 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
3883 functioning single user mode during boot.&lt;/p&gt;
3884
3885 &lt;p&gt;I have spent several years investigating the Debian boot system,
3886 and discovered this problem a few years ago. I suspect it originates
3887 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
3888 </description>
3889 </item>
3890
3891 <item>
3892 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
3893 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
3894 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
3895 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
3896 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
3897 are started from /etc/rcS.d/. In fact, there is a bite more of them
3898 than make sense, and this causes a few problems. What kind of
3899 problems, you might ask. There are at least two problems. The first
3900 is that it is not possible to recover a machine after switching to
3901 runlevel 1. One need to actually reboot to get the machine back to
3902 the expected state. The other is that single user boot will sometimes
3903 run into problems because some of the subsystems are activated before
3904 the root login is presented, causing problems when trying to recover a
3905 machine from a problem in that subsystem. A minor additional point is
3906 that moving more scripts out of rcS.d/ and into the other rc#.d/
3907 directories will increase the amount of scripts that can run in
3908 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
3909
3910 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
3911 scripts that _have_ to execute before the root login prompt is
3912 presented during a single user boot should go there. Everything else
3913 should go into the numeric runlevels. This means things like
3914 lm-sensors, fuse and x11-common should not run from rcS.d, but from
3915 the numeric runlevels. Today in Debian, there are around 115 init.d
3916 scripts that are started from rcS.d/, and most of them should be moved
3917 out. Do your package have one of them? Please help us make single
3918 user and runlevel 1 better by moving it.&lt;/p&gt;
3919
3920 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
3921 etc. should still be started from rcS.d/, but there is for example no
3922 need to have the network enabled before the single user login prompt
3923 is presented.&lt;/p&gt;
3924
3925 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
3926 Debian systems working while scripts migrate and during upgrades, the
3927 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
3928 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
3929 and the next ones can only be moved when their dependencies have been
3930 moved first. This migration must be done sequentially while we ensure
3931 that the package system upgrade packages in the right order to keep
3932 the system state correct. This will require some coordination when it
3933 comes to network related packages, but most of the packages with
3934 scripts that should migrate do not have anything in rcS.d/ depending
3935 on them. Some packages have already been updated, like the sudo
3936 package, while others are still left to do. I wish I had time to work
3937 on this myself, but real live constrains make it unlikely that I will
3938 find time to push this forward.&lt;/p&gt;
3939 </description>
3940 </item>
3941
3942 <item>
3943 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
3944 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
3945 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
3946 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
3947 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
3948 mentioned the issues I believe should be improved in Debian for its
3949 desktop to be useful for more people. The use case for this is my
3950 parents, which are currently running Kubuntu which solve the
3951 issues.&lt;/p&gt;
3952
3953 &lt;p&gt;I suspect these four missing features are not very hard to
3954 implement. After all, they are present in Ubuntu, so if we wanted to
3955 do this in Debian we would have a source.&lt;/p&gt;
3956
3957 &lt;ol&gt;
3958
3959 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
3960 are new packages available for upgrades, a icon in the KDE status bar
3961 indicate this, and clicking on it will activate the simple upgrade
3962 tool to handle it. I have no problem guiding both of my parents
3963 through the process over the phone. If a kernel reboot is required,
3964 this too is indicated by the status bars and the upgrade tool. Last
3965 time I checked, nothing with the same features was working in KDE in
3966 Debian.&lt;/li&gt;
3967
3968 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
3969 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
3970 currently have a handler for, it will ask the user if the system
3971 should search for a package that would add support for this MIME type,
3972 and if the user say yes, the APT sources will be searched for packages
3973 advertising the MIME type in their control file (visible in the
3974 Packages file in the APT archive). If one or more packages are found,
3975 it is a simple click of the mouse to add support for the missing mime
3976 type. If the package require the user to accept some non-free
3977 license, this is explained to the user. The entire process make it
3978 more clear to the user why something do not work in the browser, and
3979 make the chances higher for the user to blame the web page authors and
3980 not the browser for any missing features.&lt;/li&gt;
3981
3982 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
3983 handlers.&lt;/strong&gt; When the media players encounter a format or codec
3984 it is not supporting, a dialog pop up asking the user if the system
3985 should search for a package that would add support for it. This
3986 happen with things like MP3, Windows Media or H.264. The selection
3987 and installation procedure is very similar to the Firefox browser
3988 plugin handling. This is as far as I know implemented using a
3989 gstreamer hook. The end result is that the user easily get access to
3990 the codecs that are present from the APT archives available, while
3991 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
3992
3993 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
3994 displaying a text/plain file in my Debian browser, it will propose to
3995 start emacs to show it. If I remember correctly, when doing the same
3996 in Kunbutu it show the file as a text file in the browser. At least I
3997 know Opera will show text files within the browser. I much prefer the
3998 latter behaviour.&lt;/li&gt;
3999
4000 &lt;/ol&gt;
4001
4002 &lt;p&gt;There are other nice features as well, like the simplified suite
4003 upgrader, but given that I am the one mostly doing the dist-upgrade,
4004 it do not matter much.&lt;/p&gt;
4005
4006 &lt;p&gt;I really hope we could get these features in place for the next
4007 Debian release. It would require the coordinated effort of several
4008 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
4009 </description>
4010 </item>
4011
4012 <item>
4013 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
4014 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
4015 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
4016 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
4017 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
4018 site is build on Debian/Squeeze, and this platform was chosen because
4019 I am most familiar with Debian (being a Debian Developer for around 10
4020 years) because it is the latest stable Debian release which should get
4021 security support for a few years.&lt;/p&gt;
4022
4023 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
4024 that are missing in Debian at the moment. It would be great if these
4025 modules were added to the Debian archive, allowing anyone to set up
4026 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
4027 in their own country using only Debian packages. The list of modules
4028 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
4029 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
4030 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
4031 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
4032 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
4033 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
4034 easier in the future.&lt;/p&gt;
4035
4036 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
4037 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
4038 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
4039 with the responsibility of tracking security problems, which I really
4040 do not have time for.&lt;/p&gt;
4041 </description>
4042 </item>
4043
4044 <item>
4045 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
4046 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
4047 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
4048 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
4049 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
4050 posts have been in Norwegian the last few weeks, so here is a short
4051 update in English.&lt;/p&gt;
4052
4053 &lt;p&gt;The kids still keep me too busy to get much free software work
4054 done, but I did manage to organise a project to get a Norwegian port
4055 of the British service
4056 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
4057 and it has been running for a month now. The entire project has been
4058 organised by me and two others. Around Christmas we gathered sponsors
4059 to fund the development work. In January I drafted a contract with
4060 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
4061 and in February the development took place. Most of it involved
4062 converting the source to use GPS coordinates instead of British
4063 easting/northing, and the resulting code should be a lot easier to get
4064 running in any country by now. The Norwegian
4065 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
4066 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
4067 source and the source for administrative borders in Norway, and
4068 support for this had to be added/fixed.&lt;/p&gt;
4069
4070 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
4071 polishing the system before we announced it March 7th. The system is
4072 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4073 problem reports in a few weeks. Soon we hope to announce the Android
4074 and iPhone versions making it even easier to report problems with the
4075 public infrastructure.&lt;/p&gt;
4076
4077 &lt;p&gt;Perhaps something to consider for those of you in countries without
4078 such service?&lt;/p&gt;
4079 </description>
4080 </item>
4081
4082 <item>
4083 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4084 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4085 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4086 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4087 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4088 issues here at my work with the University of Oslo. My idea is that
4089 it should be possible to use the information about security issues
4090 available on the Internet, and check our locally
4091 maintained/distributed software against this information. It should
4092 allow us to verify that no known security issues are forgotten. The
4093 CVE database listing vulnerabilities seem like a great central point,
4094 and by using the package lists from Debian mapped to CVEs provided by
4095 the testing security team, I believed it should be possible to figure
4096 out which security holes were present in our free software
4097 collection.&lt;/p&gt;
4098
4099 &lt;p&gt;After reading up on the topic, it became obvious that the first
4100 building block is to be able to name software packages in a unique and
4101 consistent way across data sources. I considered several ways to do
4102 this, for example coming up with my own naming scheme like using URLs
4103 to project home pages or URLs to the Freshmeat entries, or using some
4104 existing naming scheme. And it seem like I am not the first one to
4105 come across this problem, as MITRE already proposed and implemented a
4106 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4107 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4108 software, hardware and other platform components. The CPE ids are
4109 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4110 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4111 issues for any CPE name. With this in place, all I need to do is to
4112 locate the CPE id for the software packages we use at the university.
4113 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4114 NVD entry if a CVE for the package exist).&lt;/p&gt;
4115
4116 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4117 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4118 check out, one could look up
4119 &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
4120 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4121 The most recent one is
4122 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4123 and at the bottom of the NVD page for this vulnerability the complete
4124 list of affected versions is provided.&lt;/p&gt;
4125
4126 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4127 for offline processing of issues. Using this dump, I&#39;ve written a
4128 small script taking a list of CPEs as input and list all CVEs
4129 affecting the packages represented by these CPEs. One give it CPEs
4130 with version numbers as specified above and get a list of open
4131 security issues out.&lt;/p&gt;
4132
4133 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4134 information need to be high. For that to happen, I believe as many as
4135 possible need to use and contribute to the NVD database. I notice
4136 RHEL is providing
4137 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4138 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4139 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4140
4141 &lt;p&gt;To get an idea about the quality for free software, I spent some
4142 time making it possible to compare the CVE database from Debian with
4143 the CVE database in NVD. The result look fairly good, but there are
4144 some inconsistencies in NVD (same software package having several
4145 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4146 Debian believe are affected by a CVE). Hope to find time to improve
4147 the quality of NVD, but that require being able to get in touch with
4148 someone maintaining it. So far my three emails with questions and
4149 corrections have not seen any reply, but I hope contact can be
4150 established soon.&lt;/p&gt;
4151
4152 &lt;p&gt;An interesting application for CPEs is cross platform package
4153 mapping. It would be useful to know which packages in for example
4154 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4155 this would be trivial if all linux distributions provided CPE entries
4156 for their packages.&lt;/p&gt;
4157 </description>
4158 </item>
4159
4160 <item>
4161 <title>Which module is loaded for a given PCI and USB device?</title>
4162 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4163 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4164 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4165 <description>&lt;p&gt;In the
4166 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4167 package in Debian, there is a script to report useful information
4168 about the running hardware for use when people report missing
4169 information. One part of this script that I find very useful when
4170 debugging hardware problems, is the part mapping loaded kernel module
4171 to the PCI device it claims. It allow me to quickly see if the kernel
4172 module I expect is driving the hardware I am struggling with. To see
4173 the output, make sure discover-data is installed and run
4174 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4175 one of my machines like this:&lt;/p&gt;
4176
4177 &lt;pre&gt;
4178 loaded modules:
4179 10de:03eb i2c_nforce2
4180 10de:03f1 ohci_hcd
4181 10de:03f2 ehci_hcd
4182 10de:03f0 snd_hda_intel
4183 10de:03ec pata_amd
4184 10de:03f6 sata_nv
4185 1022:1103 k8temp
4186 109e:036e bttv
4187 109e:0878 snd_bt87x
4188 11ab:4364 sky2
4189 &lt;/pre&gt;
4190
4191 &lt;p&gt;The code in question look like this, slightly modified for
4192 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4193
4194 &lt;pre&gt;
4195 if [ -d /sys/bus/pci/devices/ ] ; then
4196 echo loaded pci modules:
4197 (
4198 cd /sys/bus/pci/devices/
4199 for address in * ; do
4200 if [ -d &quot;$address/driver/module&quot; ] ; then
4201 module=`cd $address/driver/module ; pwd -P | xargs basename`
4202 if grep -q &quot;^$module &quot; /proc/modules ; then
4203 address=$(echo $address |sed s/0000://)
4204 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4205 echo &quot;$id $module&quot;
4206 fi
4207 fi
4208 done
4209 )
4210 echo
4211 fi
4212 &lt;/pre&gt;
4213
4214 &lt;p&gt;Similar code could be used to extract USB device module
4215 mappings:&lt;/p&gt;
4216
4217 &lt;pre&gt;
4218 if [ -d /sys/bus/usb/devices/ ] ; then
4219 echo loaded usb modules:
4220 (
4221 cd /sys/bus/usb/devices/
4222 for address in * ; do
4223 if [ -d &quot;$address/driver/module&quot; ] ; then
4224 module=`cd $address/driver/module ; pwd -P | xargs basename`
4225 if grep -q &quot;^$module &quot; /proc/modules ; then
4226 address=$(echo $address |sed s/0000://)
4227 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4228 if [ &quot;$id&quot; ] ; then
4229 echo &quot;$id $module&quot;
4230 fi
4231 fi
4232 fi
4233 done
4234 )
4235 echo
4236 fi
4237 &lt;/pre&gt;
4238
4239 &lt;p&gt;This might perhaps be something to include in other tools as
4240 well.&lt;/p&gt;
4241 </description>
4242 </item>
4243
4244 <item>
4245 <title>How to test if a laptop is working with Linux</title>
4246 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4247 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4248 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4249 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4250 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4251 batch of computers will work with Linux. Every year for the last few
4252 years the university have organised shared bid of a few thousand
4253 computers, and this year HP won the bid. Two different desktops and
4254 five different laptops are on the list this year. We in the UNIX
4255 group want to know which one of these computers work well with RHEL
4256 and Ubuntu, the two Linux distributions we currently handle at the
4257 university.&lt;/p&gt;
4258
4259 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4260 perhaps inspire others to test hardware as well. To test, I PXE
4261 install the OS version of choice, and log in as my normal user and run
4262 a few applications and plug in selected pieces of hardware. When
4263 something fail, I make a note about this in the test matrix and move
4264 on. If I have some spare time I try to report the bug to the OS
4265 vendor, but as I only have the machines for a short time, I rarely
4266 have the time to do this for all the problems I find.&lt;/p&gt;
4267
4268 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4269 I perform on a new model.&lt;/p&gt;
4270
4271 &lt;ul&gt;
4272
4273 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4274 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4275 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4276
4277 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4278 installation, X.org is working.&lt;/li&gt;
4279
4280 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4281 package mesa-utils on Ubuntu) and writing down the frames per second
4282 reported by the program.&lt;/li&gt;
4283
4284 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4285 logging in, and if I can hear this the test is successful. If there
4286 are several audio exits on the machine, I try them all and check if
4287 the Gnome/KDE audio mixer can control where to send the sound. I
4288 normally test this by playing
4289 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4290 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4291
4292 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4293 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4294
4295 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4296 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4297
4298 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4299 picture from the v4l device show up.&lt;/li&gt;
4300
4301 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4302 any bluetooth devices are discovered. In my office, I normally see a
4303 few.&lt;/li&gt;
4304
4305 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4306 memory modules lying around, and stick them in and see if Gnome/KDE
4307 notice this.&lt;/li&gt;
4308
4309 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4310 special button work, and if the laptop continue to work after
4311 resume.&lt;/li&gt;
4312
4313 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4314 adjusting background light, switching on/off external video output,
4315 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4316 laptop to laptop, so I just write down which are working and which are
4317 not.&lt;/li&gt;
4318
4319 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4320 acceleration sensors etc. I rarely test these, as I do not know how
4321 to quickly test if they are working or not, so I only document their
4322 existence.&lt;/li&gt;
4323
4324 &lt;/ul&gt;
4325
4326 &lt;p&gt;By now I suspect you are really curious what the test results are
4327 for the HP machines I am testing. I&#39;m not done yet, so I will report
4328 the test results later. For now I can report that HP 8100 Elite work
4329 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4330 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4331 can see, I have most machines left to test. One interesting
4332 observation is that Ubuntu Lucid has almost twice the frame rate than
4333 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4334 </description>
4335 </item>
4336
4337 <item>
4338 <title>Some thoughts on BitCoins</title>
4339 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4340 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4341 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4342 <description>&lt;p&gt;As I continue to explore
4343 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4344 what properties the system have, and how it will be affected by laws
4345 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4346
4347 &lt;p&gt;One interesting thing to note is that since the transactions are
4348 verified using a peer to peer network, all details about a transaction
4349 is known to everyone. This means that if a BitCoin address has been
4350 published like I did with mine in my initial post about BitCoin, it is
4351 possible for everyone to see how many BitCoins have been transfered to
4352 that address. There is even a web service to look at the details for
4353 all transactions. There I can see that my address
4354 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
4355 have received 16.06 Bitcoin, the
4356 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
4357 address of Simon Phipps have received 181.97 BitCoin and the address
4358 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
4359 of EFF have received 2447.38 BitCoins so far. Thank you to each and
4360 every one of you that donated bitcoins to support my activity. The
4361 fact that anyone can see how much money was transfered to a given
4362 address make it more obvious why the BitCoin community recommend to
4363 generate and hand out a new address for each transaction. I&#39;m told
4364 there is no way to track which addresses belong to a given person or
4365 organisation without the person or organisation revealing it
4366 themselves, as Simon, EFF and I have done.&lt;/p&gt;
4367
4368 &lt;p&gt;In Norway, and in most other countries, there are laws and
4369 regulations limiting how much money one can transfer across the border
4370 without declaring it. There are money laundering, tax and accounting
4371 laws and regulations I would expect to apply to the use of BitCoin.
4372 If the Skolelinux foundation
4373 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
4374 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
4375 normal bank transfers like EFF is doing, how should this be accounted?
4376 Given that it is impossible to know if money can cross the border or
4377 not, should everything or nothing be declared? What exchange rate
4378 should be used when calculating taxes? Would receivers have to pay
4379 income tax if the foundation were to pay Skolelinux contributors in
4380 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
4381
4382 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
4383 accepted by a lot of users. It must be possible to get easy access to
4384 the currency (as a wage or using currency exchanges), and it must be
4385 easy to spend it. At the moment BitCoin seem fairly easy to get
4386 access to, but there are very few places to spend it. I am not really
4387 a regular user of any of the vendor types currently accepting BitCoin,
4388 so I wonder when my kind of shop would start accepting BitCoins. I
4389 would like to buy electronics, travels and subway tickets, not herbs
4390 and books. :) The currency is young, and this will improve over time
4391 if it become popular, but I suspect regular banks will start to lobby
4392 to get BitCoin declared illegal if it become popular. I&#39;m sure they
4393 will claim it is helping fund terrorism and money laundering (which
4394 probably would be true, as is any currency in existence), but I
4395 believe the problems should be solved elsewhere and not by blaming
4396 currencies.&lt;/p&gt;
4397
4398 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
4399 CPU intensive process that depend on a bit of luck as well (as one is
4400 competing against all the other miners currently spending CPU cycles
4401 to see which one get the next lump of cash). The &quot;winner&quot; get 50
4402 BitCoin when this happen. Yesterday I came across the obvious way to
4403 join forces to increase ones changes of getting at least some coins,
4404 by coordinating the work on mining BitCoins across several machines
4405 and people, and sharing the result if one is lucky and get the 50
4406 BitCoins. Check out
4407 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
4408 if this sounds interesting. I have not had time to try to set up a
4409 machine to participate there yet, but have seen that running on ones
4410 own for a few days have not yield any BitCoins througth mining
4411 yet.&lt;/p&gt;
4412
4413 &lt;p&gt;Update 2010-12-15: Found an &lt;a
4414 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
4415 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
4416 it was interesting to read. The arguments presented seem to be
4417 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
4418 </description>
4419 </item>
4420
4421 <item>
4422 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
4423 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
4424 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
4425 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
4426 <description>&lt;p&gt;With this weeks lawless
4427 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
4428 attacks&lt;/a&gt; on Wikileak and
4429 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
4430 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
4431 not be trusted to handle money transactions.
4432 A blog post from
4433 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
4434 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
4435 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
4436 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
4437 some help from my friend to get it all running, and he even handed me
4438 some bitcoins to get started. I even donated a few bitcoins to Simon
4439 for helping me remember BitCoin.&lt;/p&gt;
4440
4441 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
4442 crypto-currency, decentralised and handled using peer-to-peer
4443 networks. It allows anonymous transactions and prohibits central
4444 control over the transactions, making it impossible for governments
4445 and companies alike to block donations and other transactions. The
4446 source is free software, and while the key dependency wxWidgets 2.9
4447 for the graphical user interface is missing in Debian, the command
4448 line client builds just fine. Hopefully Jonas
4449 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
4450 Debian&lt;/a&gt; soon.&lt;/p&gt;
4451
4452 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
4453 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
4454 bitcoins&lt;/a&gt; when selling services and goods, and there are even
4455 currency &quot;stock&quot; markets where the exchange rate is decided. There
4456 are not many users so far, but the concept seems promising. If you
4457 want to get started and lack a friend with any bitcoins to spare,
4458 you can even get
4459 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
4460 bitcoin at the time of writing). Use
4461 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
4462 on the current exchange rates.&lt;/p&gt;
4463
4464 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
4465 machines. If you want to support my activity, please send Bitcoin
4466 donations to the address
4467 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
4468 </description>
4469 </item>
4470
4471 <item>
4472 <title>Why isn&#39;t Debian Edu using VLC?</title>
4473 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
4474 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
4475 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
4476 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
4477 presented, and the winner among the multimedia player were VLC.
4478 Personally, I like VLC, and it is my player of choice when I first try
4479 to play a video file or stream. Only if VLC fail will I drag out
4480 gmplayer to see if it can do better. The reason is mostly the failure
4481 model and trust. When VLC fail, it normally pop up a error message
4482 reporting the problem. When mplayer fail, it normally segfault or
4483 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
4484
4485 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
4486 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4487 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
4488 plugin to play web videos seamlessly, and the VLC browser plugin is
4489 not very good. For example, it lack in-line control buttons, so there
4490 is no way for the user to pause the video. Also, when I
4491 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
4492 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
4493 failed on several video pages where mplayer based plugins worked. If
4494 the browser plugin for VLC was as good as the gecko-mediaplayer
4495 package (which uses mplayer), we would switch.&lt;/P&gt;
4496
4497 &lt;p&gt;While VLC is a good player, its user interface is slightly
4498 annoying. The most annoying feature is its inconsistent use of
4499 keyboard shortcuts. When the player is in full screen mode, its
4500 shortcuts are different from when it is playing the video in a window.
4501 For example, space only work as pause when in full screen mode. I
4502 wish it had consisten shortcuts and that space also would work when in
4503 window mode. Another nice shortcut in gmplayer is [enter] to restart
4504 the current video. It is very nice when playing short videos from the
4505 web and want to restart it when new people arrive to have a look at
4506 what is going on.&lt;/p&gt;
4507 </description>
4508 </item>
4509
4510 <item>
4511 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
4512 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
4513 <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>
4514 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
4515 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
4516 upgrade testing of the
4517 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
4518 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
4519 This seem like a very good idea, so I adjusted by test scripts and
4520 can now present the updated result from today:&lt;/p&gt;
4521
4522 &lt;p&gt;This is for Gnome:&lt;/p&gt;
4523
4524 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4525
4526 &lt;blockquote&gt;&lt;p&gt;
4527 apache2.2-bin
4528 aptdaemon
4529 baobab
4530 binfmt-support
4531 browser-plugin-gnash
4532 cheese-common
4533 cli-common
4534 cups-pk-helper
4535 dmz-cursor-theme
4536 empathy
4537 empathy-common
4538 freedesktop-sound-theme
4539 freeglut3
4540 gconf-defaults-service
4541 gdm-themes
4542 gedit-plugins
4543 geoclue
4544 geoclue-hostip
4545 geoclue-localnet
4546 geoclue-manual
4547 geoclue-yahoo
4548 gnash
4549 gnash-common
4550 gnome
4551 gnome-backgrounds
4552 gnome-cards-data
4553 gnome-codec-install
4554 gnome-core
4555 gnome-desktop-environment
4556 gnome-disk-utility
4557 gnome-screenshot
4558 gnome-search-tool
4559 gnome-session-canberra
4560 gnome-system-log
4561 gnome-themes-extras
4562 gnome-themes-more
4563 gnome-user-share
4564 gstreamer0.10-fluendo-mp3
4565 gstreamer0.10-tools
4566 gtk2-engines
4567 gtk2-engines-pixbuf
4568 gtk2-engines-smooth
4569 hamster-applet
4570 libapache2-mod-dnssd
4571 libapr1
4572 libaprutil1
4573 libaprutil1-dbd-sqlite3
4574 libaprutil1-ldap
4575 libart2.0-cil
4576 libboost-date-time1.42.0
4577 libboost-python1.42.0
4578 libboost-thread1.42.0
4579 libchamplain-0.4-0
4580 libchamplain-gtk-0.4-0
4581 libcheese-gtk18
4582 libclutter-gtk-0.10-0
4583 libcryptui0
4584 libdiscid0
4585 libelf1
4586 libepc-1.0-2
4587 libepc-common
4588 libepc-ui-1.0-2
4589 libfreerdp-plugins-standard
4590 libfreerdp0
4591 libgconf2.0-cil
4592 libgdata-common
4593 libgdata7
4594 libgdu-gtk0
4595 libgee2
4596 libgeoclue0
4597 libgexiv2-0
4598 libgif4
4599 libglade2.0-cil
4600 libglib2.0-cil
4601 libgmime2.4-cil
4602 libgnome-vfs2.0-cil
4603 libgnome2.24-cil
4604 libgnomepanel2.24-cil
4605 libgpod-common
4606 libgpod4
4607 libgtk2.0-cil
4608 libgtkglext1
4609 libgtksourceview2.0-common
4610 libmono-addins-gui0.2-cil
4611 libmono-addins0.2-cil
4612 libmono-cairo2.0-cil
4613 libmono-corlib2.0-cil
4614 libmono-i18n-west2.0-cil
4615 libmono-posix2.0-cil
4616 libmono-security2.0-cil
4617 libmono-sharpzip2.84-cil
4618 libmono-system2.0-cil
4619 libmtp8
4620 libmusicbrainz3-6
4621 libndesk-dbus-glib1.0-cil
4622 libndesk-dbus1.0-cil
4623 libopal3.6.8
4624 libpolkit-gtk-1-0
4625 libpt2.6.7
4626 libpython2.6
4627 librpm1
4628 librpmio1
4629 libsdl1.2debian
4630 libsrtp0
4631 libssh-4
4632 libtelepathy-farsight0
4633 libtelepathy-glib0
4634 libtidy-0.99-0
4635 media-player-info
4636 mesa-utils
4637 mono-2.0-gac
4638 mono-gac
4639 mono-runtime
4640 nautilus-sendto
4641 nautilus-sendto-empathy
4642 p7zip-full
4643 pkg-config
4644 python-aptdaemon
4645 python-aptdaemon-gtk
4646 python-axiom
4647 python-beautifulsoup
4648 python-bugbuddy
4649 python-clientform
4650 python-coherence
4651 python-configobj
4652 python-crypto
4653 python-cupshelpers
4654 python-elementtree
4655 python-epsilon
4656 python-evolution
4657 python-feedparser
4658 python-gdata
4659 python-gdbm
4660 python-gst0.10
4661 python-gtkglext1
4662 python-gtksourceview2
4663 python-httplib2
4664 python-louie
4665 python-mako
4666 python-markupsafe
4667 python-mechanize
4668 python-nevow
4669 python-notify
4670 python-opengl
4671 python-openssl
4672 python-pam
4673 python-pkg-resources
4674 python-pyasn1
4675 python-pysqlite2
4676 python-rdflib
4677 python-serial
4678 python-tagpy
4679 python-twisted-bin
4680 python-twisted-conch
4681 python-twisted-core
4682 python-twisted-web
4683 python-utidylib
4684 python-webkit
4685 python-xdg
4686 python-zope.interface
4687 remmina
4688 remmina-plugin-data
4689 remmina-plugin-rdp
4690 remmina-plugin-vnc
4691 rhythmbox-plugin-cdrecorder
4692 rhythmbox-plugins
4693 rpm-common
4694 rpm2cpio
4695 seahorse-plugins
4696 shotwell
4697 software-center
4698 system-config-printer-udev
4699 telepathy-gabble
4700 telepathy-mission-control-5
4701 telepathy-salut
4702 tomboy
4703 totem
4704 totem-coherence
4705 totem-mozilla
4706 totem-plugins
4707 transmission-common
4708 xdg-user-dirs
4709 xdg-user-dirs-gtk
4710 xserver-xephyr
4711 &lt;/p&gt;&lt;/blockquote&gt;
4712
4713 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4714
4715 &lt;blockquote&gt;&lt;p&gt;
4716 cheese
4717 ekiga
4718 eog
4719 epiphany-extensions
4720 evolution-exchange
4721 fast-user-switch-applet
4722 file-roller
4723 gcalctool
4724 gconf-editor
4725 gdm
4726 gedit
4727 gedit-common
4728 gnome-games
4729 gnome-games-data
4730 gnome-nettool
4731 gnome-system-tools
4732 gnome-themes
4733 gnuchess
4734 gucharmap
4735 guile-1.8-libs
4736 libavahi-ui0
4737 libdmx1
4738 libgalago3
4739 libgtk-vnc-1.0-0
4740 libgtksourceview2.0-0
4741 liblircclient0
4742 libsdl1.2debian-alsa
4743 libspeexdsp1
4744 libsvga1
4745 rhythmbox
4746 seahorse
4747 sound-juicer
4748 system-config-printer
4749 totem-common
4750 transmission-gtk
4751 vinagre
4752 vino
4753 &lt;/p&gt;&lt;/blockquote&gt;
4754
4755 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4756
4757 &lt;blockquote&gt;&lt;p&gt;
4758 gstreamer0.10-gnomevfs
4759 &lt;/p&gt;&lt;/blockquote&gt;
4760
4761 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4762
4763 &lt;blockquote&gt;&lt;p&gt;
4764 [nothing]
4765 &lt;/p&gt;&lt;/blockquote&gt;
4766
4767 &lt;p&gt;This is for KDE:&lt;/p&gt;
4768
4769 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4770
4771 &lt;blockquote&gt;&lt;p&gt;
4772 ksmserver
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 kwin
4779 network-manager-kde
4780 &lt;/p&gt;&lt;/blockquote&gt;
4781
4782 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4783
4784 &lt;blockquote&gt;&lt;p&gt;
4785 arts
4786 dolphin
4787 freespacenotifier
4788 google-gadgets-gst
4789 google-gadgets-xul
4790 kappfinder
4791 kcalc
4792 kcharselect
4793 kde-core
4794 kde-plasma-desktop
4795 kde-standard
4796 kde-window-manager
4797 kdeartwork
4798 kdeartwork-emoticons
4799 kdeartwork-style
4800 kdeartwork-theme-icon
4801 kdebase
4802 kdebase-apps
4803 kdebase-workspace
4804 kdebase-workspace-bin
4805 kdebase-workspace-data
4806 kdeeject
4807 kdelibs
4808 kdeplasma-addons
4809 kdeutils
4810 kdewallpapers
4811 kdf
4812 kfloppy
4813 kgpg
4814 khelpcenter4
4815 kinfocenter
4816 konq-plugins-l10n
4817 konqueror-nsplugins
4818 kscreensaver
4819 kscreensaver-xsavers
4820 ktimer
4821 kwrite
4822 libgle3
4823 libkde4-ruby1.8
4824 libkonq5
4825 libkonq5-templates
4826 libnetpbm10
4827 libplasma-ruby
4828 libplasma-ruby1.8
4829 libqt4-ruby1.8
4830 marble-data
4831 marble-plugins
4832 netpbm
4833 nuvola-icon-theme
4834 plasma-dataengines-workspace
4835 plasma-desktop
4836 plasma-desktopthemes-artwork
4837 plasma-runners-addons
4838 plasma-scriptengine-googlegadgets
4839 plasma-scriptengine-python
4840 plasma-scriptengine-qedje
4841 plasma-scriptengine-ruby
4842 plasma-scriptengine-webkit
4843 plasma-scriptengines
4844 plasma-wallpapers-addons
4845 plasma-widget-folderview
4846 plasma-widget-networkmanagement
4847 ruby
4848 sweeper
4849 update-notifier-kde
4850 xscreensaver-data-extra
4851 xscreensaver-gl
4852 xscreensaver-gl-extra
4853 xscreensaver-screensaver-bsod
4854 &lt;/p&gt;&lt;/blockquote&gt;
4855
4856 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4857
4858 &lt;blockquote&gt;&lt;p&gt;
4859 ark
4860 google-gadgets-common
4861 google-gadgets-qt
4862 htdig
4863 kate
4864 kdebase-bin
4865 kdebase-data
4866 kdepasswd
4867 kfind
4868 klipper
4869 konq-plugins
4870 konqueror
4871 ksysguard
4872 ksysguardd
4873 libarchive1
4874 libcln6
4875 libeet1
4876 libeina-svn-06
4877 libggadget-1.0-0b
4878 libggadget-qt-1.0-0b
4879 libgps19
4880 libkdecorations4
4881 libkephal4
4882 libkonq4
4883 libkonqsidebarplugin4a
4884 libkscreensaver5
4885 libksgrd4
4886 libksignalplotter4
4887 libkunitconversion4
4888 libkwineffects1a
4889 libmarblewidget4
4890 libntrack-qt4-1
4891 libntrack0
4892 libplasma-geolocation-interface4
4893 libplasmaclock4a
4894 libplasmagenericshell4
4895 libprocesscore4a
4896 libprocessui4a
4897 libqalculate5
4898 libqedje0a
4899 libqtruby4shared2
4900 libqzion0a
4901 libruby1.8
4902 libscim8c2a
4903 libsmokekdecore4-3
4904 libsmokekdeui4-3
4905 libsmokekfile3
4906 libsmokekhtml3
4907 libsmokekio3
4908 libsmokeknewstuff2-3
4909 libsmokeknewstuff3-3
4910 libsmokekparts3
4911 libsmokektexteditor3
4912 libsmokekutils3
4913 libsmokenepomuk3
4914 libsmokephonon3
4915 libsmokeplasma3
4916 libsmokeqtcore4-3
4917 libsmokeqtdbus4-3
4918 libsmokeqtgui4-3
4919 libsmokeqtnetwork4-3
4920 libsmokeqtopengl4-3
4921 libsmokeqtscript4-3
4922 libsmokeqtsql4-3
4923 libsmokeqtsvg4-3
4924 libsmokeqttest4-3
4925 libsmokeqtuitools4-3
4926 libsmokeqtwebkit4-3
4927 libsmokeqtxml4-3
4928 libsmokesolid3
4929 libsmokesoprano3
4930 libtaskmanager4a
4931 libtidy-0.99-0
4932 libweather-ion4a
4933 libxklavier16
4934 libxxf86misc1
4935 okteta
4936 oxygencursors
4937 plasma-dataengines-addons
4938 plasma-scriptengine-superkaramba
4939 plasma-widget-lancelot
4940 plasma-widgets-addons
4941 plasma-widgets-workspace
4942 polkit-kde-1
4943 ruby1.8
4944 systemsettings
4945 update-notifier-common
4946 &lt;/p&gt;&lt;/blockquote&gt;
4947
4948 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
4949 aptitude a bit more similar, but there are still quite a lott of
4950 differences. I have no idea what packages should be installed after
4951 the upgrade, but hope those that do can have a look.&lt;/p&gt;
4952 </description>
4953 </item>
4954
4955 <item>
4956 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
4957 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
4958 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
4959 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
4960 <description>&lt;p&gt;Most of the computers in use by the
4961 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
4962 are virtual machines. And they have been Xen machines running on a
4963 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
4964 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
4965 bit harder that it could have been, because we set up the Xen virtual
4966 machines to get the virtual partitions from LVM, which as far as I
4967 know is not supported by KVM. So to migrate, we had to convert
4968 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
4969
4970 &lt;p&gt;I found
4971 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
4972 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
4973 migration. It uses qemu-img from the qemu package to make the disk
4974 image, parted to partition it, losetup and kpartx to present the disk
4975 image partions as devices, and dd to copy the data. I NFS mounted the
4976 new servers storage area on the old server to do the migration.&lt;/p&gt;
4977
4978 &lt;pre&gt;
4979 #!/bin/sh
4980
4981 # Based on
4982 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
4983
4984 set -e
4985 set -x
4986
4987 if [ -z &quot;$1&quot; ] ; then
4988 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
4989 exit 1
4990 else
4991 host=&quot;$1&quot;
4992 fi
4993
4994 if [ ! -e /dev/vg_data/$host-disk ] ; then
4995 echo &quot;error: unable to find LVM volume for $host&quot;
4996 exit 1
4997 fi
4998
4999 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
5000 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5001 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
5002 totalsize=$(( ( $disksize + $swapsize ) ))
5003
5004 img=$host.img
5005 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
5006 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
5007
5008 parted $img mklabel msdos
5009 parted $img mkpart primary linux-swap 0 $disksize
5010 parted $img mkpart primary ext2 $disksize $totalsize
5011 parted $img set 1 boot on
5012
5013 modprobe dm-mod
5014 losetup /dev/loop0 $img
5015 kpartx -a /dev/loop0
5016
5017 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
5018 fsck.ext3 -f /dev/mapper/loop0p1 || true
5019 mkswap /dev/mapper/loop0p2
5020
5021 kpartx -d /dev/loop0
5022 losetup -d /dev/loop0
5023 &lt;/pre&gt;
5024
5025 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
5026 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
5027
5028 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
5029 the new disk image attached, installed grub-pc and linux-image-686 and
5030 set up grub to boot from the disk image. After this, the KVM machines
5031 seem to work just fine.&lt;/p&gt;
5032 </description>
5033 </item>
5034
5035 <item>
5036 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
5037 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
5038 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
5039 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
5040 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
5041 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
5042 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
5043 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
5044
5045 &lt;p&gt;I still do not know what a correct migration should look like, so I
5046 report any differences between apt and aptitude and hope someone else
5047 can see if anything should be changed.&lt;/p&gt;
5048
5049 &lt;p&gt;This is for Gnome:&lt;/p&gt;
5050
5051 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5052
5053 &lt;blockquote&gt;&lt;p&gt;
5054 apache2.2-bin aptdaemon at-spi baobab binfmt-support
5055 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
5056 dmz-cursor-theme empathy empathy-common finger
5057 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
5058 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
5059 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
5060 gnome-cards-data gnome-codec-install gnome-core
5061 gnome-desktop-environment gnome-disk-utility gnome-screenshot
5062 gnome-search-tool gnome-session-canberra gnome-spell
5063 gnome-system-log gnome-themes-extras gnome-themes-more
5064 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
5065 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
5066 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
5067 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
5068 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
5069 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
5070 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
5071 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5072 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5073 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5074 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5075 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5076 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5077 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5078 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5079 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5080 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5081 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5082 libmono-security2.0-cil libmono-sharpzip2.84-cil
5083 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5084 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5085 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5086 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5087 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5088 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5089 libxalan2-java libxerces2-java media-player-info mesa-utils
5090 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5091 nautilus-sendto-empathy openoffice.org-writer2latex
5092 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5093 python-aptdaemon python-aptdaemon-gtk python-axiom
5094 python-beautifulsoup python-bugbuddy python-clientform
5095 python-coherence python-configobj python-crypto python-cupshelpers
5096 python-cupsutils python-eggtrayicon python-elementtree
5097 python-epsilon python-evolution python-feedparser python-gdata
5098 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5099 python-gtksourceview2 python-httplib2 python-louie python-mako
5100 python-markupsafe python-mechanize python-nevow python-notify
5101 python-opengl python-openssl python-pam python-pkg-resources
5102 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5103 python-tagpy python-twisted-bin python-twisted-conch
5104 python-twisted-core python-twisted-web python-utidylib python-webkit
5105 python-xdg python-zope.interface remmina remmina-plugin-data
5106 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5107 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5108 software-center svgalibg1 system-config-printer-udev
5109 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5110 totem totem-coherence totem-mozilla totem-plugins
5111 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5112 zip
5113 &lt;/p&gt;&lt;/blockquote&gt;
5114
5115 Installed using apt-get, removed with aptitude
5116
5117 &lt;blockquote&gt;&lt;p&gt;
5118 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5119 epiphany-extensions epiphany-gecko evolution-exchange
5120 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5121 gedit-common gnome-app-install gnome-games gnome-games-data
5122 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5123 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5124 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5125 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5126 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5127 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5128 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5129 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5130 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5131 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5132 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5133 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5134 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5135 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5136 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5137 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5138 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5139 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5140 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5141 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5142 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5143 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5144 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5145 sound-juicer swfdec-gnome system-config-printer totem-common
5146 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5147 &lt;/p&gt;&lt;/blockquote&gt;
5148
5149 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5150
5151 &lt;blockquote&gt;&lt;p&gt;
5152 gstreamer0.10-gnomevfs
5153 &lt;/p&gt;&lt;/blockquote&gt;
5154
5155 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5156
5157 &lt;blockquote&gt;&lt;p&gt;
5158 [nothing]
5159 &lt;/p&gt;&lt;/blockquote&gt;
5160
5161 &lt;p&gt;This is for KDE:&lt;/p&gt;
5162
5163 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5164
5165 &lt;blockquote&gt;&lt;p&gt;
5166 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5167 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5168 ghostscript-x git gnome-audio gnugo granatier gs-common
5169 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5170 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5171 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5172 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5173 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5174 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5175 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5176 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5177 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5178 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5179 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5180 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5181 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5182 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5183 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5184 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5185 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5186 libkrossui4 libmailtools-perl libmime-tools-perl
5187 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5188 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5189 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5190 lirc luatex marble networkstatus noatun-plugins
5191 openoffice.org-writer2latex palapeli palapeli-data parley
5192 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5193 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5194 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5195 ttf-sazanami-gothic
5196 &lt;/p&gt;&lt;/blockquote&gt;
5197
5198 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5199
5200 &lt;blockquote&gt;&lt;p&gt;
5201 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5202 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5203 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5204 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5205 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5206 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5207 kitchensync kiten kjumpingcube klatin klettres klickety klines
5208 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5209 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5210 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5211 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5212 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5213 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5214 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5215 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5216 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5217 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5218 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5219 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5220 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5221 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5222 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5223 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5224 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5225 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5226 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5227 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5228 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5229 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5230 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5231 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5232 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5233 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5234 &lt;/p&gt;&lt;/blockquote&gt;
5235
5236 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5237
5238 &lt;blockquote&gt;&lt;p&gt;
5239 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5240 kdeartwork kdebase kdebase-apps kdebase-workspace
5241 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5242 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5243 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5244 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5245 xscreensaver-screensaver-bsod
5246 &lt;/p&gt;&lt;/blockquote&gt;
5247
5248 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5249
5250 &lt;blockquote&gt;&lt;p&gt;
5251 kdebase-bin konq-plugins konqueror
5252 &lt;/p&gt;&lt;/blockquote&gt;
5253 </description>
5254 </item>
5255
5256 <item>
5257 <title>Gnash buildbot slave and Debian kfreebsd</title>
5258 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5259 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5260 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5261 <description>&lt;p&gt;Answering
5262 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5263 call from the Gnash project&lt;/a&gt; for
5264 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5265 current source, I have set up a virtual KVM machine on the Debian
5266 Edu/Skolelinux virtualization host to test the git source on
5267 Debian/Squeeze. I hope this can help the developers in getting new
5268 releases out more often.&lt;/p&gt;
5269
5270 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5271 I have considered setting up a &lt;a
5272 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5273 machine as well. I have also considered using the kfreebsd
5274 architecture in Debian as a file server in NUUG to get access to the 5
5275 TB zfs volume we currently use to store DV video. Because of this, I
5276 finally got around to do a test installation of Debian/Squeeze with
5277 kfreebsd. Installation went fairly smooth, thought I noticed some
5278 visual glitches in the cdebconf dialogs (black cursor left on the
5279 screen at random locations). Have not gotten very far with the
5280 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5281 fatal problem. Have to spend some more time on it to see if it is
5282 useful as a file server for NUUG. Will try to find time to set up a
5283 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5284 </description>
5285 </item>
5286
5287 <item>
5288 <title>Debian in 3D</title>
5289 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5290 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5291 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5292 <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;
5293
5294 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5295 3D linked in from
5296 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5297 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5298 </description>
5299 </item>
5300
5301 <item>
5302 <title>Software updates 2010-10-24</title>
5303 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5304 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5305 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5306 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5307
5308 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5309 raise money for the project is going well. The lower limit of 10
5310 signers was reached in 24 hours, and so far 13 people have signed it.
5311 More signers and more funding is most welcome, and I am really curious
5312 how far we can get before the time limit of December 24 is reached.
5313 :)&lt;/p&gt;
5314
5315 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5316 about what appear to be a great code coverage tool capable of
5317 generating code coverage stats without any changes to the source code.
5318 It is called
5319 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5320 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5321 It is missing in Debian, but the git source built just fine in Squeeze
5322 after I installed libelf-dev, libdwarf-dev, pkg-config and
5323 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5324 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5325
5326 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5327 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5328 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5329 alpha test release of the Squeeze based Debian Edu /
5330 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5331 release. Give it a try if you need a complete linux solution for your
5332 school, including central infrastructure server, workstations, thin
5333 client servers and diskless workstations. A nice touch added
5334 yesterday is RDP support on the thin client servers, for windows
5335 clients to get a Linux desktop on request.&lt;/p&gt;
5336 </description>
5337 </item>
5338
5339 <item>
5340 <title>Some notes on Flash in Debian and Debian Edu</title>
5341 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5342 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5343 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5344 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5345 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5346 second most popular used package that is missing in Debian. The sixth
5347 most popular is flashplayer-mozilla. This is a clear indication that
5348 working flash is important for Debian users. Around 10 percent of the
5349 users submitting data to popcon.debian.org have this package
5350 installed.&lt;/p&gt;
5351
5352 &lt;p&gt;In the report written by Lars Risan in August 2008
5353&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
5354 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5355 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
5356 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5357 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
5358 web sites require Flash to work, and lacking working Flash support in
5359 the web browser and the problems with installing it was perceived as a
5360 good reason to stay with Windows.&lt;/p&gt;
5361
5362 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
5363 said to be the retarded cousin that did not really understand
5364 everything you told him but could work fairly well. This was a
5365 comment regarding the problems Linux have with proprietary formats and
5366 non-standard web pages, and is sad because it exposes a fairly common
5367 understanding of whose fault it is if web pages that only work in for
5368 example Internet Explorer 6 fail to work on Firefox, and funny because
5369 it explain very well how annoying it is for users when Linux
5370 distributions do not work with the documents they receive or the web
5371 pages they want to visit.&lt;/p&gt;
5372
5373 &lt;p&gt;This is part of the reason why I believe it is important for Debian
5374 and Debian Edu to have a well working Flash implementation in the
5375 distribution, to get at least popular sites as Youtube and Google
5376 Video to working out of the box. For Squeeze, Debian have the chance
5377 to include the latest version of Gnash that will make this happen, as
5378 the new release 0.8.8 was published a few weeks ago and is resting in
5379 unstable. The new version work with more sites that version 0.8.7.
5380 The Gnash maintainers have asked for a freeze exception, but the
5381 release team have not had time to reply to it yet. I hope they agree
5382 with me that Flash is important for the Debian desktop users, and thus
5383 accept the new package into Squeeze.&lt;/p&gt;
5384 </description>
5385 </item>
5386
5387 <item>
5388 <title>Circular package dependencies harms apt recovery</title>
5389 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
5390 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
5391 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
5392 <description>&lt;p&gt;I discovered this while doing
5393 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
5394 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
5395 in Debian still got circular dependencies, and it is often claimed
5396 that apt and aptitude should be able to handle this just fine, but
5397 some times these dependency loops causes apt to fail.&lt;/p&gt;
5398
5399 &lt;p&gt;An example is from todays
5400 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
5401 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
5402 causes perl-modules to fail to upgrade. The cause is simple. If a
5403 package fail to unpack, then only part of packages with the circular
5404 dependency might end up being unpacked when unpacking aborts, and the
5405 ones already unpacked will fail to configure in the recovery phase
5406 because its dependencies are unavailable.&lt;/p&gt;
5407
5408 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
5409
5410 &lt;blockquote&gt;&lt;pre&gt;
5411 dpkg: dependency problems prevent configuration of perl-modules:
5412 perl-modules depends on perl (&gt;= 5.10.1-1); however:
5413 Version of perl on system is 5.10.0-19lenny2.
5414 dpkg: error processing perl-modules (--configure):
5415 dependency problems - leaving unconfigured
5416 &lt;/pre&gt;&lt;/blockquote&gt;
5417
5418 &lt;p&gt;The perl/perl-modules circular dependency is already
5419 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
5420 hopefully be solved as soon as possible, but it is not the only one,
5421 and each one of these loops in the dependency tree can cause similar
5422 failures. Of course, they only occur when there are bugs in other
5423 packages causing the unpacking to fail, but it is rather nasty when
5424 the failure of one package causes the problem to become worse because
5425 of dependency loops.&lt;/p&gt;
5426
5427 &lt;p&gt;Thanks to
5428 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
5429 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
5430 dependencies
5431 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
5432 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
5433
5434 &lt;p&gt;Todays testing also exposed a bug in
5435 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
5436 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
5437 apt-get and aptitude, the latter possibly caused by some circular
5438 dependency. Reported both to BTS to try to get someone to look at
5439 it.&lt;/p&gt;
5440 </description>
5441 </item>
5442
5443 <item>
5444 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
5445 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
5446 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
5447 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
5448 <description>&lt;p&gt;This is a
5449 &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;
5450 on my
5451 &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
5452 work&lt;/a&gt; on
5453 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
5454 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
5455
5456 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
5457 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5458 and dhcp3-server-ldap in Debian use the LDAP server. The two
5459 implementations are quite different in how they use LDAP.&lt;/p&gt;
5460
5461 To get this information, I started slapd with debugging enabled and
5462 dumped the debug output to a file to get the LDAP searches performed
5463 on a Debian Edu main-server. Here is a summary.
5464
5465 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
5466
5467 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
5468 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
5469 the web.
5470
5471 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
5472 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
5473 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
5474 reverse entries are in two different subtrees in LDAP with a structure
5475 based on the DNS names, as in tjener.intern and
5476 2.2.0.10.in-addr.arpa.&lt;/p&gt;
5477
5478 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
5479 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
5480 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
5481 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
5482 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
5483 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
5484 forward entries, it is looking for attributes named dnsttl, arecord,
5485 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5486 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5487 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5488 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5489 spfrecord and modifytimestamp. For reverse entries it is looking for
5490 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5491 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5492 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5493 ldapsearch commands could look like this:&lt;/p&gt;
5494
5495 &lt;blockquote&gt;&lt;pre&gt;
5496 ldapsearch -h ldap \
5497 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5498 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5499 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5500 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5501 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5502 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5503
5504 ldapsearch -h ldap \
5505 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5506 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
5507 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5508 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5509 srvrecord naptrrecord modifytimestamp
5510 &lt;/pre&gt;&lt;/blockquote&gt;
5511
5512 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
5513 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5514 example LDAP objects used there. In addition to these objects, the
5515 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5516 also exist.&lt;/p&gt;
5517
5518 &lt;blockquote&gt;&lt;pre&gt;
5519 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5520 objectclass: top
5521 objectclass: dnsdomain
5522 objectclass: domainrelatedobject
5523 dc: tjener
5524 arecord: 10.0.2.2
5525 associateddomain: tjener.intern
5526
5527 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5528 objectclass: top
5529 objectclass: dnsdomain2
5530 objectclass: domainrelatedobject
5531 dc: 2
5532 ptrrecord: tjener.intern
5533 associateddomain: 2.2.0.10.in-addr.arpa
5534 &lt;/pre&gt;&lt;/blockquote&gt;
5535
5536 &lt;p&gt;In strict mode, the server behaves differently. When looking for
5537 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
5538 same base as in the tree mode for a object with filter
5539 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
5540 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5541 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5542 naptrrecord and modifytimestamp. For reverse entires it also do a
5543 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
5544 and the requested attributes are associateddomain, dnsttl and
5545 modifytimestamp. In short, in strict mode the objects with ptrrecord
5546 go away, and the arecord attribute in the forward object is used
5547 instead.&lt;/p&gt;
5548
5549 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
5550 like this:&lt;/p&gt;
5551
5552 &lt;blockquote&gt;&lt;pre&gt;
5553 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5554 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5555 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5556 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5557 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5558 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5559
5560 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5561 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
5562 &lt;/pre&gt;&lt;/blockquote&gt;
5563
5564 &lt;p&gt;In addition to the forward and reverse searches , there is also a
5565 search for SOA records, which behave similar to the forward and
5566 reverse lookups.&lt;/p&gt;
5567
5568 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
5569 specify any objectclass names, and instead look for the attributes it
5570 need to generate a DNS reply. This make it able to work with any
5571 objectclass that provide the needed attributes.&lt;/p&gt;
5572
5573 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
5574 dnsdomain2 schemas. The latter is used for reverse entries like
5575 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
5576
5577 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
5578 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5579 attributes) and domainrelatedobject (for associatedDomain). The use
5580 of structural object classes make it impossible to combine these
5581 classes with the object classes used by DHCP.&lt;/p&gt;
5582
5583 &lt;p&gt;There are other schemas that could be used too, for example the
5584 dnszone structural object class used by Gosa and bind-sdb for the DNS
5585 attributes combined with the domainrelatedobject object class, but in
5586 this case some unused attributes would have to be included as well
5587 (zonename and relativedomainname).&lt;/p&gt;
5588
5589 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
5590 mode and not use any of the existing objectclasses (dnsdomain,
5591 dnsdomain2 and dnszone) when one want to combine the DNS information
5592 with DHCP information, and instead create a auxiliary object class
5593 defined something like this (using the attributes defined for
5594 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
5595
5596 &lt;blockquote&gt;&lt;pre&gt;
5597 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
5598 SUP top
5599 AUXILIARY
5600 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5601 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5602 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5603 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5604 A6Record $ DNAMERecord
5605 ))
5606 &lt;/pre&gt;&lt;/blockquote&gt;
5607
5608 &lt;p&gt;This will allow any object to become a DNS entry when combined with
5609 the domainrelatedobject object class, and allow any entity to include
5610 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
5611 developers asking for their view on this schema and if they are
5612 interested in providing such schema with PowerDNS, and I hope my
5613 message will be accepted into their mailing list soon.&lt;/p&gt;
5614
5615 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
5616
5617 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
5618 the object attributes, and then uses the attributes it want. This
5619 make it harder to figure out exactly what attributes are used, but
5620 thanks to the working example in Debian Edu I can at least get an idea
5621 what is needed without having to read the source code.&lt;/p&gt;
5622
5623 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
5624 search filter to use to locate the correct dhcpServer entity is
5625 stored. These are the relevant entries from
5626 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
5627
5628 &lt;blockquote&gt;&lt;pre&gt;
5629 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
5630 ldap-dhcp-server-cn &quot;dhcp&quot;;
5631 &lt;/pre&gt;&lt;/blockquote&gt;
5632
5633 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
5634 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
5635 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
5636 search result is this entry:&lt;/p&gt;
5637
5638 &lt;blockquote&gt;&lt;pre&gt;
5639 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5640 cn: dhcp
5641 objectClass: top
5642 objectClass: dhcpServer
5643 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5644 &lt;/pre&gt;&lt;/blockquote&gt;
5645
5646 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
5647 subtree with DHCP configuration. The DHCP configuration subtree base
5648 is located using a base scope search with base &quot;cn=DHCP
5649 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
5650 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
5651 The search result is this entry:&lt;/p&gt;
5652
5653 &lt;blockquote&gt;&lt;pre&gt;
5654 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5655 cn: DHCP Config
5656 objectClass: top
5657 objectClass: dhcpService
5658 objectClass: dhcpOptions
5659 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5660 dhcpStatements: ddns-update-style none
5661 dhcpStatements: authoritative
5662 dhcpOption: smtp-server code 69 = array of ip-address
5663 dhcpOption: www-server code 72 = array of ip-address
5664 dhcpOption: wpad-url code 252 = text
5665 &lt;/pre&gt;&lt;/blockquote&gt;
5666
5667 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
5668 all the DHCP configuration is loaded, it is ready to receive requests.
5669 The subtree in Debian Edu contain objects with object classes
5670 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5671 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5672 and information about netmasks, dynamic range etc. Leaving out the
5673 details here because it is not relevant for the focus of my
5674 investigation, which is to see if it is possible to merge dns and dhcp
5675 related computer objects.&lt;/p&gt;
5676
5677 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
5678 of the client (00:00:00:00:00:00 in this example), using a subtree
5679 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
5680 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5681 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
5682 like:&lt;/p&gt;
5683
5684 &lt;blockquote&gt;&lt;pre&gt;
5685 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5686 cn: hostname
5687 objectClass: top
5688 objectClass: dhcpHost
5689 dhcpHWAddress: ethernet 00:00:00:00:00:00
5690 dhcpStatements: fixed-address hostname
5691 &lt;/pre&gt;&lt;/blockquote&gt;
5692
5693 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
5694 The object classes need to have fixed names, and the configuration
5695 need to be stored in a fairly specific LDAP structure. On the
5696 positive side, the invidiual dhcpHost entires can be anywhere without
5697 the DN pointed to by the dhcpServer entries. The latter should make
5698 it possible to group all host entries in a subtree next to the
5699 configuration entries, and this subtree can also be shared with the
5700 DNS server if the schema proposed above is combined with the dhcpHost
5701 structural object class.
5702
5703 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
5704
5705 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
5706 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
5707 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
5708 allowing DNS objects to be stored anywhere under the base cn specified
5709 in the configuration.&lt;/p&gt;
5710
5711 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
5712 regarding which LDAP schemas to use and which LDAP structure to use.
5713 I guess one could implement ones own schema, as long as the
5714 objectclasses and attributes have the names used, but this do not
5715 really help when the DHCP subtree need to have a fairly fixed
5716 structure.&lt;/p&gt;
5717
5718 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
5719 this might work for Debian Edu:&lt;/p&gt;
5720
5721 &lt;blockquote&gt;&lt;pre&gt;
5722 ou=services
5723 cn=machine-info (dhcpService) - dhcpServiceDN points here
5724 cn=dhcp (dhcpServer)
5725 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5726 cn=10.0.2.0 (dhcpSubnet)
5727 cn=group1 (dhcpGroup/dhcpOptions)
5728 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5729 cn=192.168.0.0 (dhcpSubnet)
5730 cn=group1 (dhcpGroup/dhcpOptions)
5731 ou=machines - PowerDNS base points here
5732 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
5733 &lt;/pre&gt;&lt;/blockquote&gt;
5734
5735 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
5736 entries to be in the dhcpGroup subtrees, the entries can be stored
5737 there instead of a common machines subtree, and the PowerDNS base
5738 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
5739
5740 &lt;p&gt;The combined object under the machines subtree would look something
5741 like this:&lt;/p&gt;
5742
5743 &lt;blockquote&gt;&lt;pre&gt;
5744 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
5745 dc: hostname
5746 objectClass: top
5747 objectClass: dhcpHost
5748 objectclass: domainrelatedobject
5749 objectclass: dnsDomainAux
5750 associateddomain: hostname.intern
5751 arecord: 10.11.12.13
5752 dhcpHWAddress: ethernet 00:00:00:00:00:00
5753 dhcpStatements: fixed-address hostname.intern
5754 &lt;/pre&gt;&lt;/blockquote&gt;
5755
5756 &lt;/p&gt;One could even add the LTSP configuration associated with a given
5757 machine, as long as the required attributes are available in a
5758 auxiliary object class.&lt;/p&gt;
5759 </description>
5760 </item>
5761
5762 <item>
5763 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
5764 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
5765 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
5766 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
5767 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
5768 DHCP services in Debian Edu to use the same LDAP objects for a given
5769 computer, to avoid the possibility of having a inconsistent state for
5770 a computer in LDAP (as in DHCP but no DNS entry or the other way
5771 around) and make it easier to add computers to LDAP.&lt;/p&gt;
5772
5773 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
5774 information finally found a solution that seem to work.&lt;/p&gt;
5775
5776 &lt;p&gt;The old setup required three LDAP objects for a given computer.
5777 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
5778 we switch powerdns to use its strict LDAP method (ldap-method=strict
5779 in pdns-debian-edu.conf), the forward and reverse DNS entries are
5780 merged into one while making it impossible to transfer the reverse map
5781 to a slave DNS server.&lt;/p&gt;
5782
5783 &lt;p&gt;If we also replace the object class used to get the DNS related
5784 attributes to one allowing these attributes to be combined with the
5785 dhcphost object class, we can merge the DNS and DHCP entries into one.
5786 I&#39;ve written such object class in the dnsdomainaux.schema file (need
5787 proper OIDs, but that is a minor issue), and tested the setup. It
5788 seem to work.&lt;/p&gt;
5789
5790 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
5791 for both DNS and DHCP, and even the LTSP configuration I suggested in
5792 an earlier email. The combined LDAP object will look something like
5793 this:&lt;/p&gt;
5794
5795 &lt;blockquote&gt;&lt;pre&gt;
5796 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5797 cn: hostname
5798 objectClass: dhcphost
5799 objectclass: domainrelatedobject
5800 objectclass: dnsdomainaux
5801 associateddomain: hostname.intern
5802 arecord: 10.11.12.13
5803 dhcphwaddress: ethernet 00:00:00:00:00:00
5804 dhcpstatements: fixed-address hostname
5805 ldapconfigsound: Y
5806 &lt;/pre&gt;&lt;/blockquote&gt;
5807
5808 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
5809 the DHCP server uses the dhcphwaddress and dhcpstatements entries
5810 before asking DNS to resolve the fixed-adddress. LTSP will use
5811 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
5812
5813 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
5814 dhcphost in a different location, to allow us to put the objects
5815 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
5816 that. If I can&#39;t figure out a way to do that, we can still get rid of
5817 the hosts subtree and move all its content into the DHCP Config tree
5818 (which probably should be renamed to be more related to the new
5819 content. I suspect cn=dnsdhcp,ou=services or something like that
5820 might be a good place to put it.&lt;/p&gt;
5821
5822 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
5823 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5824 </description>
5825 </item>
5826
5827 <item>
5828 <title>Idea for storing LTSP configuration in LDAP</title>
5829 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
5830 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
5831 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
5832 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
5833 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
5834 clients, and that this can be used to fetch configuration from LDAP if
5835 Debian Edu choose to store configuration there.&lt;/p&gt;
5836
5837 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
5838 to get configuration from LDAP. The idea is to look up the MAC
5839 address of the client in LDAP, and look for attributes on the form
5840 ltspconfigsetting=value, and use this to export SETTING=value to the
5841 LTSP clients.&lt;/p&gt;
5842
5843 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
5844 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
5845 allowing us to store all information about a computer in one place.&lt;/p&gt;
5846
5847 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
5848 this approach. A real LDAP schema for the ltspClientAux objectclass
5849 need to be written. Comments, suggestions, etc?&lt;/p&gt;
5850
5851 &lt;blockquote&gt;&lt;pre&gt;
5852 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
5853 #
5854 # Fetch LTSP client settings from LDAP based on MAC address
5855 #
5856 # Uses ethernet address as stored in the dhcpHost objectclass using
5857 # the dhcpHWAddress attribute or ethernet address stored in the
5858 # ieee802Device objectclass with the macAddress attribute.
5859 #
5860 # This module is written to be schema agnostic, and only depend on the
5861 # existence of attribute names.
5862 #
5863 # The LTSP configuration variables are saved directly using a
5864 # ltspConfig prefix and uppercasing the rest of the attribute name.
5865 # To set the SERVER variable, set the ltspConfigServer attribute.
5866 #
5867 # Some LDAP schema should be created with all the relevant
5868 # configuration settings. Something like this should work:
5869 #
5870 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
5871 # SUP top
5872 # AUXILIARY
5873 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
5874
5875 LDAPSERVER=$(debian-edu-ldapserver)
5876 if [ &quot;$LDAPSERVER&quot; ] ; then
5877 LDAPBASE=$(debian-edu-ldapserver -b)
5878 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
5879 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
5880 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
5881 grep &#39;^ltspConfig&#39; | while read attr value ; do
5882 # Remove prefix and convert to upper case
5883 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
5884 # bass value on to clients
5885 eval &quot;$attr=$value; export $attr&quot;
5886 done
5887 done
5888 fi
5889 &lt;/pre&gt;&lt;/blockquote&gt;
5890
5891 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
5892 the while block might end up in a subshell causing the variables set
5893 there to not show up in ltsp-config, but if that is the case I am sure
5894 the code can be restructured to make sure the variables are passed on.
5895 I expect that can be solved with some testing. :)&lt;/p&gt;
5896
5897 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
5898 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5899
5900 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
5901 configuration in LDAP that was created around year 2000 by
5902 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
5903 Xperience, Inc., 2000&lt;/a&gt;. I found its
5904 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
5905 personal home page over at redhat.com.&lt;/p&gt;
5906 </description>
5907 </item>
5908
5909 <item>
5910 <title>jXplorer, a very nice LDAP GUI</title>
5911 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
5912 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
5913 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
5914 <description>&lt;p&gt;Since
5915 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
5916 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
5917 LDAP GUI that is even better than luma. The java application
5918 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
5919 moving LDAP objects and subtrees using drag-and-drop, and can
5920 authenticate using Kerberos. I have only tested the Kerberos
5921 authentication, but do not have a LDAP setup allowing me to rewrite
5922 LDAP with my test user yet. It is
5923 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
5924 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
5925 have with it is how it handle errors. If something go wrong, its
5926 non-intuitive behaviour require me to go through some query work list
5927 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
5928 </description>
5929 </item>
5930
5931 <item>
5932 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
5933 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
5934 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
5935 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
5936 <description>&lt;p&gt;Here is a short update on my &lt;a
5937 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
5938 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
5939 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
5940 not reporting the status for KDE, because the upgrade crashes when
5941 aptitude try because of missing conflicts
5942 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
5943 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
5944
5945 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
5946 complete list of the installed packages. Based on this I see these
5947 differences when I did a test run today. As usual, I do not really
5948 know what the correct set of packages would be, but thought it best to
5949 publish the difference.&lt;/p&gt;
5950
5951 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5952
5953 &lt;blockquote&gt;&lt;p&gt;
5954 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
5955 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
5956 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
5957 libgtksourceview-common libpt-1.10.10-plugins-alsa
5958 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
5959 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
5960 python-4suite-xml python-eggtrayicon python-gtkhtml2
5961 python-gtkmozembed svgalibg1 xserver-xephyr zip
5962 &lt;/p&gt;&lt;/blockquote&gt;
5963
5964 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5965
5966 &lt;blockquote&gt;&lt;p&gt;
5967 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
5968 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
5969 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
5970 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
5971 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
5972 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
5973 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5974 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5975 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5976 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
5977 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
5978 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
5979 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
5980 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
5981 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
5982 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
5983 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
5984 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
5985 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
5986 mysql-common swfdec-gnome totem-gstreamer wodim
5987 &lt;/p&gt;&lt;/blockquote&gt;
5988
5989 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5990
5991 &lt;blockquote&gt;&lt;p&gt;
5992 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
5993 python-gnomekeyring python-wnck rhythmbox-plugins xorg
5994 xserver-xorg-input-all xserver-xorg-input-evdev
5995 xserver-xorg-input-kbd xserver-xorg-input-mouse
5996 xserver-xorg-input-synaptics xserver-xorg-video-all
5997 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
5998 xserver-xorg-video-chips xserver-xorg-video-cirrus
5999 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6000 xserver-xorg-video-glint xserver-xorg-video-i128
6001 xserver-xorg-video-i740 xserver-xorg-video-mach64
6002 xserver-xorg-video-mga xserver-xorg-video-neomagic
6003 xserver-xorg-video-nouveau xserver-xorg-video-nv
6004 xserver-xorg-video-r128 xserver-xorg-video-radeon
6005 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
6006 xserver-xorg-video-s3 xserver-xorg-video-s3virge
6007 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
6008 xserver-xorg-video-sis xserver-xorg-video-sisusb
6009 xserver-xorg-video-tdfx xserver-xorg-video-tga
6010 xserver-xorg-video-trident xserver-xorg-video-tseng
6011 xserver-xorg-video-vesa xserver-xorg-video-vmware
6012 xserver-xorg-video-voodoo
6013 &lt;/p&gt;&lt;/blockquote&gt;
6014
6015 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6016
6017 &lt;blockquote&gt;&lt;p&gt;
6018 deskbar-applet xserver-xorg xserver-xorg-core
6019 xserver-xorg-input-wacom xserver-xorg-video-intel
6020 xserver-xorg-video-openchrome
6021 &lt;/p&gt;&lt;/blockquote&gt;
6022
6023 &lt;p&gt;I was told on IRC that the xorg-xserver package was
6024 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
6025 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
6026 No idea when it hits Squeeze, but when it does I hope it will reduce
6027 the difference somewhat.
6028 </description>
6029 </item>
6030
6031 <item>
6032 <title>LUMA, a very nice LDAP GUI</title>
6033 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
6034 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
6035 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
6036 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
6037 directory in Debian Edu, and in the process I started to miss a GUI
6038 tool to browse the LDAP tree. The only one I was able to find in
6039 Debian/Squeeze and Lenny is
6040 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
6041 be a great tool to get a overview of the current LDAP directory
6042 populated by default in Skolelinux. Thanks to it, I have been able to
6043 find empty and obsolete subtrees, misplaced objects and duplicate
6044 objects. It will be installed by default in Debian/Squeeze. If you
6045 are working with LDAP, give it a go. :)&lt;/p&gt;
6046
6047 &lt;p&gt;I did notice one problem with it I have not had time to report to
6048 the BTS yet. There is no .desktop file in the package, so the tool do
6049 not show up in the Gnome and KDE menus, but only deep down in in the
6050 Debian submenu in KDE. I hope that can be fixed before Squeeze is
6051 released.&lt;/p&gt;
6052
6053 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
6054 like to move objects and remove subtrees directly in the GUI, but have
6055 not found a way to do that with LUMA yet. So in the mean time, I use
6056 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
6057
6058 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
6059 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6060
6061 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
6062 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
6063 useful GUI alternative. It seem like a good tool, but is unmaintained
6064 in Debian and got a RC bug keeping it out of Squeeze. Unless that
6065 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
6066 </description>
6067 </item>
6068
6069 <item>
6070 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
6071 <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>
6072 <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>
6073 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6074 <description>&lt;p&gt;A while back, I
6075 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6076 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6077 for storing DNS and DHCP information in LDAP to combine the two sets
6078 of information into one LDAP object representing a computer.&lt;/p&gt;
6079
6080 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6081 the dhcpHost object class auxiliary, to allow it to be combined with
6082 the dNSDomain object class, and thus forming one object for one
6083 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6084
6085 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6086 without also changing the assigned number for the object class, and I
6087 do not know enough about LDAP schema design to do that properly for
6088 Debian Edu.&lt;/p&gt;
6089
6090 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6091 the
6092 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6093 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6094 available today from IETF.&lt;/p&gt;
6095
6096 &lt;pre&gt;
6097 --- dhcp.schema (revision 65192)
6098 +++ dhcp.schema (working copy)
6099 @@ -376,7 +376,7 @@
6100 objectclass ( 2.16.840.1.113719.1.203.6.6
6101 NAME &#39;dhcpHost&#39;
6102 DESC &#39;This represents information about a particular client&#39;
6103 - SUP top
6104 + SUP top AUXILIARY
6105 MUST cn
6106 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6107 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6108 &lt;/pre&gt;
6109
6110 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6111 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6112 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6113
6114 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6115 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6116 </description>
6117 </item>
6118
6119 <item>
6120 <title>Calling tasksel like the installer, while still getting useful output</title>
6121 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6122 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6123 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6124 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6125 installs packages during the normal debian-installer run. Until now,
6126 I have ended up letting tasksel do the work, with the annoying problem
6127 of not getting any feedback at all when something fails (like a
6128 conffile question from dpkg or a download that fails), using code like
6129 this:
6130
6131 &lt;blockquote&gt;&lt;pre&gt;
6132 export DEBIAN_FRONTEND=noninteractive
6133 tasksel --new-install
6134 &lt;/pre&gt;&lt;/blockquote&gt;
6135
6136 This would invoke tasksel, let its automatic task selection pick the
6137 tasks to install, and continue to install the requested tasks without
6138 any output what so ever.
6139
6140 Recently I revisited this problem while working on the automatic
6141 package upgrade testing, because tasksel would some times hang without
6142 any useful feedback, and I want to see what is going on when it
6143 happen. Then it occured to me, I can parse the output from tasksel
6144 when asked to run in test mode, and use that aptitude command line
6145 printed by tasksel then to simulate the tasksel run. I ended up using
6146 code like this:
6147
6148 &lt;blockquote&gt;&lt;pre&gt;
6149 export DEBIAN_FRONTEND=noninteractive
6150 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6151 $cmd
6152 &lt;/pre&gt;&lt;/blockquote&gt;
6153
6154 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6155 --without-recommends -o APT::Install-Recommends=no -y install
6156 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6157 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6158 laptop task and all packages with priority standard , required and
6159 important, just like tasksel would have done it during
6160 installation.&lt;/p&gt;
6161
6162 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6163 install packages without using debconf-apt-progress, for use cases
6164 like this.&lt;/p&gt;
6165 </description>
6166 </item>
6167
6168 <item>
6169 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6170 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6171 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6172 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6173 <description>&lt;p&gt;My
6174 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6175 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6176 finally made the upgrade logs available from
6177 &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;.
6178 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6179 apt and aptitude, and found their differences interesting. This time
6180 I will only focus on their removal plans.&lt;/p&gt;
6181
6182 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6183 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6184 surprising part is that it want to remove xorg and all
6185 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6186 sure why. When asking aptitude to do the same, it want to remove 129
6187 packages, but most of them are library packages I suspect are no
6188 longer needed. Both of them want to remove bluetooth packages, which
6189 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6190
6191 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6192 which seem like a bad idea and xorg the same way as with Gnome. Asking
6193 aptitude for the same, it wants to remove 192 packages, none which are
6194 too surprising.&lt;/p&gt;
6195
6196 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6197 and avoided, and perhaps others as well. Here are the complete list
6198 of planned removals. The complete logs is available from the URL
6199 above. Note if you want to repeat these tests, that the upgrade test
6200 for kde+apt-get hung in the tasksel setup because of dpkg asking
6201 conffile questions. No idea why. I worked around it by using
6202 &#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
6203 continue.&lt;/p&gt;
6204
6205 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6206 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6207 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6208 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6209 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6210 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6211 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6212 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6213 xserver-xorg-input-kbd xserver-xorg-input-mouse
6214 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6215 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6216 xserver-xorg-video-ati xserver-xorg-video-chips
6217 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6218 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6219 xserver-xorg-video-glint xserver-xorg-video-i128
6220 xserver-xorg-video-i740 xserver-xorg-video-imstt
6221 xserver-xorg-video-intel xserver-xorg-video-mach64
6222 xserver-xorg-video-mga xserver-xorg-video-neomagic
6223 xserver-xorg-video-nsc xserver-xorg-video-nv
6224 xserver-xorg-video-openchrome xserver-xorg-video-r128
6225 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6226 xserver-xorg-video-rendition xserver-xorg-video-s3
6227 xserver-xorg-video-s3virge xserver-xorg-video-savage
6228 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6229 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6230 xserver-xorg-video-tga xserver-xorg-video-trident
6231 xserver-xorg-video-tseng xserver-xorg-video-v4l
6232 xserver-xorg-video-vesa xserver-xorg-video-vga
6233 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6234 xulrunner-1.9-gnome-support&lt;/p&gt;
6235
6236 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6237
6238 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6239 djvulibre-desktop finger gnome-app-install gnome-mount
6240 gnome-network-admin gnome-spell gnome-vfs-obexftp
6241 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6242 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6243 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6244 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6245 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6246 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6247 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6248 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6249 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6250 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6251 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6252 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6253 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6254 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6255 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6256 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6257 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6258 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6259 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6260 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6261 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6262 openoffice.org-writer2latex openssl-blacklist p7zip
6263 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6264 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6265 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6266 swfdec-mozilla totem-gstreamer update-manager wodim
6267 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6268 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6269 zip&lt;/p&gt;
6270
6271 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6272
6273 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6274 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6275 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6276 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6277 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6278 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6279 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6280 xserver-xorg-input-kbd xserver-xorg-input-mouse
6281 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6282 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6283 xserver-xorg-video-ati xserver-xorg-video-chips
6284 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6285 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6286 xserver-xorg-video-glint xserver-xorg-video-i128
6287 xserver-xorg-video-i740 xserver-xorg-video-imstt
6288 xserver-xorg-video-intel xserver-xorg-video-mach64
6289 xserver-xorg-video-mga xserver-xorg-video-neomagic
6290 xserver-xorg-video-nsc xserver-xorg-video-nv
6291 xserver-xorg-video-openchrome xserver-xorg-video-r128
6292 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6293 xserver-xorg-video-rendition xserver-xorg-video-s3
6294 xserver-xorg-video-s3virge xserver-xorg-video-savage
6295 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6296 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6297 xserver-xorg-video-tga xserver-xorg-video-trident
6298 xserver-xorg-video-tseng xserver-xorg-video-v4l
6299 xserver-xorg-video-vesa xserver-xorg-video-vga
6300 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6301
6302 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6303 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6304 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6305 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6306 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6307 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6308 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6309 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6310 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6311 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6312 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6313 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6314 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6315 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6316 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6317 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6318 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6319 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6320 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6321 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6322 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6323 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6324 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6325 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6326 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6327 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6328 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6329 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6330 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6331 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6332 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6333 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6334 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6335 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6336 texlive-common texlive-doc-base texlive-fonts-recommended
6337 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6338 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6339 xulrunner-1.9&lt;/p&gt;
6340
6341 </description>
6342 </item>
6343
6344 <item>
6345 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6346 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6347 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6348 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6349 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6350 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6351 have been discovered and reported in the process
6352 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
6353 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
6354 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
6355 kdebase-workspace-data), and to get a more regular testing going on, I
6356 am working on a script to automate the test.&lt;/p&gt;
6357
6358 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
6359 Gnome or KDE desktop installation inside the chroot before upgrading
6360 it. To ensure no services are started in the chroot, a policy-rc.d
6361 script is inserted. To make sure tasksel believe it is to install a
6362 desktop on a laptop, the tasksel tests are replaced in the chroot
6363 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
6364
6365 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6366 currently always fail because udev refuses to upgrade with the kernel
6367 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6368 is created. The bug report
6369 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
6370 this problem do not trigger in a chroot, but I touch the file anyway
6371 to make sure the upgrade go well. Testing on virtual and real
6372 hardware have failed me because of udev so far, and creating this file
6373 do the trick in such settings anyway. This is a
6374 &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
6375 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
6376 maintainer because he lack the resources to rewrite udev to keep
6377 working with old kernels or something like that. I really wish the
6378 udev upstream would keep udev backwards compatible, to avoid such
6379 upgrade problem, but given that they fail to do so, I guess
6380 documenting the way out of this mess is the best option we got for
6381 Debian Squeeze.&lt;/p&gt;
6382
6383 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
6384 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
6385 trick:&lt;/p&gt;
6386
6387 &lt;blockquote&gt;&lt;pre&gt;
6388 #!/bin/sh
6389 set -ex
6390
6391 if [ &quot;$1&quot; ] ; then
6392 desktop=$1
6393 else
6394 desktop=gnome
6395 fi
6396
6397 from=lenny
6398 to=squeeze
6399
6400 exec &amp;lt; /dev/null
6401 unset LANG
6402 mirror=http://ftp.skolelinux.org/debian
6403 tmpdir=chroot-$from-upgrade-$to-$desktop
6404 fuser -mv .
6405 debootstrap $from $tmpdir $mirror
6406 chroot $tmpdir aptitude update
6407 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
6408 #!/bin/sh
6409 exit 101
6410 EOF
6411 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6412 exit_cleanup() {
6413 umount $tmpdir/proc
6414 }
6415 mount -t proc proc $tmpdir/proc
6416 # Make sure proc is unmounted also on failure
6417 trap exit_cleanup EXIT INT
6418
6419 chroot $tmpdir aptitude -y install debconf-utils
6420
6421 # Make sure tasksel autoselection trigger. It need the test scripts
6422 # to return the correct answers.
6423 echo tasksel tasksel/desktop multiselect $desktop | \
6424 chroot $tmpdir debconf-set-selections
6425
6426 # Include the desktop and laptop task
6427 for test in desktop laptop ; do
6428 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
6429 #!/bin/sh
6430 exit 2
6431 EOF
6432 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6433 done
6434
6435 DEBIAN_FRONTEND=noninteractive
6436 DEBIAN_PRIORITY=critical
6437 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6438 chroot $tmpdir tasksel --new-install
6439
6440 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
6441 chroot $tmpdir aptitude update
6442 touch $tmpdir/etc/udev/kernel-upgrade
6443 chroot $tmpdir aptitude -y dist-upgrade
6444 fuser -mv
6445 &lt;/pre&gt;&lt;/blockquote&gt;
6446
6447 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
6448 with aptitude, but I have not had time to look at how they behave
6449 differently so far. I hope to get a cron job running to do the test
6450 regularly and post the result on the web. The Gnome upgrade currently
6451 work, while the KDE upgrade fail because of the bug in
6452 kdebase-workspace-data&lt;/p&gt;
6453
6454 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
6455 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
6456 post, so I will refrain from trying. I can report that for Gnome,
6457 aptitude report 760 packages upgraded, 448 newly installed, 129 to
6458 remove and 1 not upgraded and 1024MB need to be downloaded while for
6459 KDE the same numbers are 702 packages upgraded, 507 newly installed,
6460 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
6461
6462 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
6463 is able to migrate to dependency based boot sequencing and parallel
6464 booting without a hitch. Was unsure if there were still bugs with
6465 packages failing to clean up their obsolete init.d script during
6466 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6467 packages.&lt;/p&gt;
6468 </description>
6469 </item>
6470
6471 <item>
6472 <title>Upstart or sysvinit - as init.d scripts see it</title>
6473 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
6474 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
6475 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
6476 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
6477 scripts to migrate (some of) their operations to upstart job while
6478 keeping the init.d for hurd and kfreebsd. The packages with such
6479 needs will need a way to get their init.d scripts to behave
6480 differently when used with sysvinit and with upstart. Because of
6481 this, I had a look at the environment variables set when a init.d
6482 script is running under upstart, and when it is not.&lt;/p&gt;
6483
6484 &lt;p&gt;With upstart, I notice these environment variables are set when a
6485 script is started from rcS.d/ (ignoring some irrelevant ones like
6486 COLUMNS):&lt;/p&gt;
6487
6488 &lt;blockquote&gt;&lt;pre&gt;
6489 DEFAULT_RUNLEVEL=2
6490 previous=N
6491 PREVLEVEL=
6492 RUNLEVEL=
6493 runlevel=S
6494 UPSTART_EVENTS=startup
6495 UPSTART_INSTANCE=
6496 UPSTART_JOB=rc-sysinit
6497 &lt;/pre&gt;&lt;/blockquote&gt;
6498
6499 &lt;p&gt;With sysvinit, these environment variables are set for the same
6500 script.&lt;/p&gt;
6501
6502 &lt;blockquote&gt;&lt;pre&gt;
6503 INIT_VERSION=sysvinit-2.88
6504 previous=N
6505 PREVLEVEL=N
6506 RUNLEVEL=S
6507 runlevel=S
6508 &lt;/pre&gt;&lt;/blockquote&gt;
6509
6510 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
6511 sysvinit are not set by upstart. Not sure if it is intentional or not
6512 to not be compatible with sysvinit in this regard.&lt;/p&gt;
6513
6514 &lt;p&gt;For scripts needing to behave differently when upstart is used,
6515 looking for the UPSTART_JOB environment variable seem to be a good
6516 choice.&lt;/p&gt;
6517 </description>
6518 </item>
6519
6520 <item>
6521 <title>A manual for standards wars...</title>
6522 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
6523 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
6524 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
6525 <description>&lt;p&gt;Via the
6526 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
6527 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
6528 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
6529 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
6530 following the standards wars of today.&lt;/p&gt;
6531 </description>
6532 </item>
6533
6534 <item>
6535 <title>Sitesummary tip: Listing computer hardware models used at site</title>
6536 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
6537 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
6538 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
6539 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
6540 to get a list of the machine types in use thanks to the DMI
6541 information extracted from each machine. The script to do so is
6542 included in the sitesummary package, and here is example output from
6543 the Skolelinux build servers:&lt;/p&gt;
6544
6545 &lt;blockquote&gt;&lt;pre&gt;
6546 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6547 vendor count
6548 Dell Computer Corporation 1
6549 PowerEdge 1750 1
6550 IBM 1
6551 eserver xSeries 345 -[8670M1X]- 1
6552 Intel 2
6553 [no-dmi-info] 3
6554 maintainer:~#
6555 &lt;/pre&gt;&lt;/blockquote&gt;
6556
6557 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
6558 provided in each machine. Here there are Intel machines without model
6559 information listed with Intel as vendor and no model, and virtual Xen
6560 machines listed as [no-dmi-info]. One can add -l as a command line
6561 option to list the individual machines.&lt;/p&gt;
6562
6563 &lt;p&gt;A larger list is
6564 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
6565 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
6566 provide the basic sitesummary report publicly. In their report there
6567 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
6568 their machines, and as sitesummary is available in both distributions,
6569 it is trivial to get all of them to report to the same central
6570 collector.&lt;/p&gt;
6571 </description>
6572 </item>
6573
6574 <item>
6575 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
6576 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
6577 <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>
6578 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
6579 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
6580 start at boot when an NVidia video card is used is handled. The
6581 problem seem to be that the nvidia X.org driver uses a long time to
6582 initialize, and this duration is longer than kdm is configured to
6583 wait.&lt;/p&gt;
6584
6585 &lt;p&gt;I came across two bugs related to this issue,
6586 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
6587 against initscripts and passed on to nvidia-glx when it became obvious
6588 that the nvidia drivers were involved, and
6589 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
6590 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
6591
6592 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
6593 problem nvidia video card owners experience and make sure the Debian
6594 distribution work out of the box for these users. The nvidia driver
6595 maintainers expect kdm to be set up to wait longer, while kdm expect
6596 the nvidia driver maintainers to fix the driver to start faster, and
6597 while they wait for each other I guess the users end up switching to a
6598 distribution that work for them. I have no idea what the solution is,
6599 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
6600
6601 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
6602 </description>
6603 </item>
6604
6605 <item>
6606 <title>Parallellized boot seem to hold up well in Debian/testing</title>
6607 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
6608 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
6609 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
6610 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
6611 The feature seem to hold up pretty well, but three fairly serious
6612 issues are known and should be solved:
6613
6614 &lt;p&gt;&lt;ul&gt;
6615
6616 &lt;li&gt;The wicd package seen to
6617 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
6618 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
6619 parallel booting is enabled. No idea why, but the wicd maintainer
6620 seem to be on the case.&lt;/li&gt;
6621
6622 &lt;li&gt;The nvidia X driver seem to
6623 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
6624 triggered more easily when parallel booting is in effect. The
6625 maintainer is on the case.&lt;/li&gt;
6626
6627 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
6628 sequencing (the shutdown is broken) when old file-rc users
6629 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
6630 sysv-rc. One way to solve it would be for file-rc to create
6631 /etc/init.d/.legacy-bootordering, and another is to try to make
6632 sysv-rc more robust. Will investigate some more and probably upload a
6633 workaround in sysv-rc to help those trying to move from file-rc to
6634 sysv-rc get a working shutdown.&lt;/li&gt;
6635
6636 &lt;/ul&gt;&lt;/p&gt;
6637
6638 &lt;p&gt;All in all not many surprising issues, and all of them seem
6639 solvable before Squeeze is released. In addition to these there are
6640 some packages with bugs in their dependencies and run level settings,
6641 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
6642
6643 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6644 the BTS, please usertag the report to get it to show up at
6645 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6646 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6647
6648 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
6649 </description>
6650 </item>
6651
6652 <item>
6653 <title>More flexible firmware handling in debian-installer</title>
6654 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
6655 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
6656 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
6657 <description>&lt;p&gt;After a long break from debian-installer development, I finally
6658 found time today to return to the project. Having to spend less time
6659 working dependency based boot in debian, as it is almost complete now,
6660 definitely helped freeing some time.&lt;/p&gt;
6661
6662 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
6663 include some firmware packages on the Debian Edu CDs, those needed to
6664 get disk and network controllers working. Without having these
6665 firmware packages available during installation, it is impossible to
6666 install Debian Edu on the given machine, and because our target group
6667 are non-technical people, asking them to provide firmware packages on
6668 an external medium is a support pain. Initially, I expected it to be
6669 enough to include the firmware packages on the CD to get
6670 debian-installer to find and use them. This proved to be wrong.
6671 Next, I hoped it was enough to symlink the relevant firmware packages
6672 to some useful location on the CD (tried /cdrom/ and
6673 /cdrom/firmware/). This also proved to not work, and at this point I
6674 found time to look at the debian-installer code to figure out what was
6675 going to work.&lt;/p&gt;
6676
6677 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
6678 look revealed that it would only look for firmware packages outside
6679 the installation media, so the CD was never checked for firmware
6680 packages. It would only check USB sticks, floppies and other
6681 &quot;external&quot; media devices. Today I changed it to also look in the
6682 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6683 solve the problem I ran into with Debian edu. I also changed it to
6684 look in /firmware/, to make sure the installer also find firmware
6685 provided in the initrd when booting the installer via PXE, to allow us
6686 to provide the same feature in the PXE setup included in Debian
6687 Edu.&lt;/p&gt;
6688
6689 &lt;p&gt;To make sure firmware deb packages with a license questions are not
6690 activated without asking if the license is accepted, I extended
6691 hw-detect to look for preinst scripts in the firmware packages, and
6692 run these before activating the firmware during installation. The
6693 license question is asked using debconf in the preinst, so this should
6694 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
6695
6696 &lt;p&gt;If you want to discuss the details of these features, please
6697 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
6698 </description>
6699 </item>
6700
6701 <item>
6702 <title>Parallellized boot is now the default in Debian/unstable</title>
6703 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
6704 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
6705 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
6706 <description>&lt;p&gt;Since this evening, parallel booting is the default in
6707 Debian/unstable for machines using dependency based boot sequencing.
6708 Apparently the testing of concurrent booting has been wider than
6709 expected, if I am to believe the
6710 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6711 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
6712 with the feature this weekend, to give us some time to detect any
6713 remaining problems before Squeeze is frozen. If serious problems are
6714 detected, it is simple to change the default back to sequential boot.
6715 The upload of the new sysvinit package also activate a new upstream
6716 version.&lt;/p&gt;
6717
6718 More information about
6719 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6720 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
6721 currently possible to disable parallel booting when one run into
6722 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
6723
6724 &lt;blockquote&gt;&lt;pre&gt;
6725 CONCURRENCY=none
6726 &lt;/pre&gt;&lt;/blockquote&gt;
6727
6728 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6729 the BTS, please usertag the report to get it to show up at
6730 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6731 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6732 </description>
6733 </item>
6734
6735 <item>
6736 <title>Sitesummary tip: Listing MAC address of all clients</title>
6737 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
6738 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
6739 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
6740 <description>&lt;p&gt;In the recent Debian Edu versions, the
6741 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
6742 system&lt;/a&gt; is used to keep track of the machines in the school
6743 network. Each machine will automatically report its status to the
6744 central server after boot and once per night. The network setup is
6745 also reported, and using this information it is possible to get the
6746 MAC address of all network interfaces in the machines. This is useful
6747 to update the DHCP configuration.&lt;/p&gt;
6748
6749 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
6750 ist all MAC addresses of all machines reporting to sitesummary. Run
6751 this on the collector host:&lt;/p&gt;
6752
6753 &lt;blockquote&gt;&lt;pre&gt;
6754 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
6755 &lt;/pre&gt;&lt;/blockquote&gt;
6756
6757 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
6758 line per machine and with space between the MAC addresses.&lt;/p&gt;
6759
6760 &lt;p&gt;To allow system administrators easier job at adding static DHCP
6761 addresses for hosts, it would be possible to extend this to fetch
6762 machine information from sitesummary and update the DHCP and DNS
6763 tables in LDAP using this information. Such tool is unfortunately not
6764 written yet.&lt;/p&gt;
6765 </description>
6766 </item>
6767
6768 <item>
6769 <title>systemd, an interesting alternative to upstart</title>
6770 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
6771 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
6772 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
6773 <description>&lt;p&gt;The last few days a new boot system called
6774 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
6775 has been
6776 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
6777
6778 to the free software world. I have not yet had time to play around
6779 with it, but it seem to be a very interesting alternative to
6780 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
6781 a good alternative for Debian when we are able to switch to an event
6782 based boot system. Tollef is
6783 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
6784 systemd into Debian, and I look forward to seeing how well it work. I
6785 like the fact that systemd handles init.d scripts with dependency
6786 information natively, allowing them to run in parallel where upstart
6787 at the moment do not.&lt;/p&gt;
6788
6789 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
6790 platform support. It only work on recent Linux kernels, and also need
6791 some new kernel features enabled to function properly. This means
6792 kFreeBSD and Hurd ports of Debian will need a port or a different boot
6793 system. Not sure how that will be handled if systemd proves to be the
6794 way forward.&lt;/p&gt;
6795
6796 &lt;p&gt;In the mean time, based on the
6797 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6798 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
6799 decided to enable full parallel booting as the default in Debian as
6800 soon as possible (probably this weekend or early next week), to see if
6801 there are any remaining serious bugs in the init.d dependencies. A
6802 new version of the sysvinit package implementing this change is
6803 already in experimental. If all go well, Squeeze will be released
6804 with parallel booting enabled by default.&lt;/p&gt;
6805 </description>
6806 </item>
6807
6808 <item>
6809 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
6810 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
6811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
6812 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
6813 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
6814 complete, so complete that it is actually possible to run all the
6815 init.d scripts in parallell based on these dependencies. If you want
6816 to test your Squeeze system, make sure
6817 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6818 based boot sequencing&lt;/a&gt; is enabled, and add this line to
6819 /etc/default/rcS:&lt;/p&gt;
6820
6821 &lt;blockquote&gt;&lt;pre&gt;
6822 CONCURRENCY=makefile
6823 &lt;/pre&gt;&lt;/blockquote&gt;
6824
6825 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
6826 scripts in parallel using the dependency information stored in
6827 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
6828 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
6829 to try to start the kdm and gdm scripts as early as possible, and will
6830 start the facilities required by kdm or gdm as early as possible to
6831 make this happen.&lt;/p&gt;
6832
6833 &lt;p&gt;Give it a try, and see if you like the result. If some services
6834 fail to start properly, it is most likely because they have incomplete
6835 init.d script dependencies in their startup script (or some of their
6836 dependent scripts have incomplete dependencies). Report bugs and get
6837 the package maintainers to fix it. :)&lt;/p&gt;
6838
6839 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
6840 manage to get the init.d script dependencies complete and correct. I
6841 expect we will get there in Squeeze+1, if we get manage to test and
6842 fix the remaining issues.&lt;/p&gt;
6843
6844 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6845 the BTS, please usertag the report to get it to show up at
6846 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6847 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6848 </description>
6849 </item>
6850
6851 <item>
6852 <title>Debian has switched to dependency based boot sequencing</title>
6853 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
6854 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
6855 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
6856 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
6857 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
6858 have been migrated to using dependency based boot sequencing. This
6859 conclude work me and others have been doing for the last three days.
6860 It feels great to see this finally part of the default Debian
6861 installation. Now we just need to weed out the last few problems that
6862 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
6863
6864 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
6865 fixing the more fundamental problem of handing the event based
6866 non-predictable kernel in the early boot.&lt;/p&gt;
6867 </description>
6868 </item>
6869
6870 <item>
6871 <title>Taking over sysvinit development</title>
6872 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
6873 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
6874 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
6875 <description>&lt;p&gt;After several years of frustration with the lack of activity from
6876 the existing sysvinit upstream developer, I decided a few weeks ago to
6877 take over the package and become the new upstream. The number of
6878 patches to track for the Debian package was becoming a burden, and the
6879 lack of synchronization between the distribution made it hard to keep
6880 the package up to date.&lt;/p&gt;
6881
6882 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
6883 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
6884 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
6885 and Fedora), based on the patches currently in use in these
6886 distributions. We Debian maintainers plan to move to this tarball as
6887 the new upstream as soon as we find time to do the merge. Since the
6888 new tarball was created, we agreed with Werner at SuSe to make a new
6889 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
6890 development there. The project is registered and currently waiting
6891 for approval by the Savannah administrators, and as soon as it is
6892 approved, we will import the old versions from svn and continue
6893 working on the future release.&lt;/p&gt;
6894
6895 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
6896 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
6897 </description>
6898 </item>
6899
6900 <item>
6901 <title>Debian boots quicker and quicker</title>
6902 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
6903 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
6904 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
6905 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
6906 people involved in the boot system on Debian and Ubuntu, to see if we
6907 could find more ways to speed up the boot system. This was an Ubuntu
6908 funded
6909 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
6910 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
6911 of boot systems, and ways to handle the increasing number of boot
6912 issues introduced by the Linux kernel becoming more and more
6913 asynchronous and event base. The Ubuntu approach using udev and
6914 upstart might be a good way forward. Time will show.&lt;/p&gt;
6915
6916 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
6917 process in Debian. All of these should be applied to get a quick
6918 boot:&lt;/p&gt;
6919
6920 &lt;ul&gt;
6921
6922 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
6923
6924 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
6925 clock is in UTC.&lt;/li&gt;
6926
6927 &lt;li&gt;Install and activate the insserv package to enable
6928 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6929 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
6930
6931 &lt;/ul&gt;
6932
6933 These points are based on the Google summer of code work done by
6934 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
6935 Villegas&lt;/a&gt;.
6936
6937 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
6938 unstable yesterday. When we tested it, we were able to cut 6 seconds
6939 from the boot sequence. It depend on very correct dependency
6940 declaration in all init.d scripts, so I expect us to find edge cases
6941 where the dependences in some scripts are slightly wrong when we start
6942 using this.&lt;/p&gt;
6943
6944 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
6945 introduced by Raphael Geissert today, one that could affect the
6946 startup speed as well. Instead of starting some scripts concurrently
6947 from rcS.d/ and another set of scripts from rc2.d/, it would be
6948 possible to run a of them in the same process. A quick way to test
6949 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
6950 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
6951 </description>
6952 </item>
6953
6954 <item>
6955 <title>BSAs påstander om piratkopiering møter motstand</title>
6956 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
6957 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
6958 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
6959 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
6960 programvareselskapene som Microsoft og Apple, publisert en rapport der
6961 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
6962 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
6963 dager siden kom
6964 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
6965 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
6966 dagene. Et spesielt interessant kommentar fra Sverige,
6967 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
6968 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
6969
6970 &lt;blockquote&gt;
6971 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
6972 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
6973 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
6974 exakta&quot;, säger BSAs Sverigechef John Hugosson.
6975 &lt;/blockquote&gt;
6976
6977 &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
6978 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
6979 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
6980 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
6981 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
6982
6983 &lt;p&gt;Fant lenkene via &lt;a
6984 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
6985 på Slashdot&lt;/a&gt;.&lt;/p&gt;
6986 </description>
6987 </item>
6988
6989 <item>
6990 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
6991 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
6992 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
6993 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
6994 <description>&lt;p&gt;Kom over
6995 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
6996 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
6997 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
6998 jobber til daglig. En rask opptelling forteller meg at vi har 490
6999 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
7000 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
7001 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
7002 </description>
7003 </item>
7004
7005 <item>
7006 <title>Kryptert harddisk - naturligvis</title>
7007 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
7008 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
7009 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
7010 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
7011 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
7012 når en tar tap av arbeidstid, fortrolige dokumenter,
7013 personopplysninger og alt annet det innebærer. Det er ingen tvil om
7014 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
7015 til at jeg har kryptert harddisken på både kontormaskinen og min
7016 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
7017 komme på avveie, den første informasjon relatert til jobben min ved
7018 Universitetet i Oslo, og den andre relatert til blant annet
7019 foreningsarbeide. Kryptering av diskene gjør at det er lite
7020 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
7021 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
7022 og en reboot vil gjøre at de ber om passord før de vil starte opp.
7023 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
7024 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
7025 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
7026 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
7027 det er gjort slik jeg gjør det er minimale, og gevinstene er
7028 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
7029 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
7030
7031 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
7032 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
7033 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
7034 er for min del høyere enn gevinsten. Jeg tror oddsene for at
7035 f.eks. etteretningsorganisasjoner har glede av å titte på mine
7036 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
7037 gjøre det vanskeligere for angripere med kompetanse og ressurser er
7038 betydelige.&lt;/p&gt;
7039 </description>
7040 </item>
7041
7042 <item>
7043 <title>Two projects that have improved the quality of free software a lot</title>
7044 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
7045 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
7046 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
7047 <description>&lt;p&gt;There are two software projects that have had huge influence on the
7048 quality of free software, and I wanted to mention both in case someone
7049 do not yet know them.&lt;/p&gt;
7050
7051 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
7052 tool to detect and expose errors in the memory handling of programs.
7053 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
7054 and it will report any problems on stdout. It is even better if the
7055 program include debug information. With debug information, it is able
7056 to report the source file name and line number where the problem
7057 occurs. It can report things like &#39;reading past memory block in file
7058 X line N, the memory block was allocated in file Y, line M&#39;, and
7059 &#39;using uninitialised value in control logic&#39;. This tool has made it
7060 trivial to investigate reproducible crash bugs in programs, and have
7061 reduced the number of this kind of bugs in free software a lot.
7062
7063 &lt;p&gt;The second one is
7064 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
7065 a source code checker. It is able to process the source of a program
7066 and find problems in the logic without running the program. It
7067 started out as the Stanford Checker and became well known when it was
7068 used to find bugs in the Linux kernel. It is now a commercial tool
7069 and the company behind it is running
7070 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
7071 free software community, where a lot of free software projects get
7072 their source checked for free. Several thousand defects have been
7073 found and fixed so far. It can find errors like &#39;lock L taken in file
7074 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7075 Y lines O to P can never be executed&#39;. The projects included in the
7076 community service project have managed to get rid of a lot of
7077 reliability problems thanks to Coverity.&lt;/p&gt;
7078
7079 &lt;p&gt;I believe tools like this, that are able to automatically find
7080 errors in the source, are vital to improve the quality of software and
7081 make sure we can get rid of the crashing and failing software we are
7082 surrounded by today.&lt;/p&gt;
7083 </description>
7084 </item>
7085
7086 <item>
7087 <title>No patch is not better than a useless patch</title>
7088 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7089 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7090 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7091 <description>&lt;p&gt;Julien Blache
7092 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7093 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7094 patch allow one to discuss a concrete and proposed solution, and also
7095 prove that the issue at hand is important enough for someone to spent
7096 time on fixing it. No patch do not provide any of these positive
7097 properties.&lt;/p&gt;
7098 </description>
7099 </item>
7100
7101 <item>
7102 <title>Standardize on protocols and formats, not vendors and applications</title>
7103 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7104 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7105 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7106 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7107 very good one to form a long lived computer infrastructure. It is the
7108 simple one, lost by many in todays computer industry: Standardize on
7109 open network protocols and open exchange/storage formats, not applications.
7110 Applications come and go, while protocols and files tend to stay, and
7111 thus one want to make it easy to change application and vendor, while
7112 avoiding conversion costs and locking users to a specific platform or
7113 application.&lt;/p&gt;
7114
7115 &lt;p&gt;This approach make it possible to replace the client applications
7116 independently of the server applications. One can even allow users to
7117 use several different applications as long as they handle the selected
7118 protocol and format. In the normal case, only one client application
7119 is recommended and users only get help if they choose to use this
7120 application, but those that want to deviate from the easy path are not
7121 blocked from doing so.&lt;/p&gt;
7122
7123 &lt;p&gt;It also allow us to replace the server side without forcing the
7124 users to replace their applications, and thus allow us to select the
7125 best server implementation at any moment, when scale and resouce
7126 requirements change.&lt;/p&gt;
7127
7128 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7129 open formats, but I would never recommend standardizing on a single
7130 application that do not use open network protocol or open formats.&lt;/p&gt;
7131 </description>
7132 </item>
7133
7134 <item>
7135 <title>Returning from Skolelinux developer gathering</title>
7136 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7137 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7138 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7139 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7140 Edu/Skolelinux development gathering. I got a bit done tuning the
7141 desktop, and looked into the dynamic service location protocol
7142 implementation avahi. It look like it could be useful for us. Almost
7143 30 people participated, and I believe it was a great environment to
7144 get to know the Skolelinux system. Walter Bender, involved in the
7145 development of the Sugar educational platform, presented his stuff and
7146 also helped me improve my OLPC installation. He also showed me that
7147 his Turtle Art application can be used in standalone mode, and we
7148 agreed that I would help getting it packaged for Debian. As a
7149 standalone application it would be great for Debian Edu. We also
7150 tried to get the video conferencing working with two OLPCs, but that
7151 proved to be too hard for us. The application seem to need more work
7152 before it is ready for me. I look forward to getting home and relax
7153 now. :)&lt;/p&gt;
7154 </description>
7155 </item>
7156
7157 <item>
7158 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7159 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7160 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7161 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7162 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7163 optimal. There is RFC 2307 documenting one way to store NIS maps in
7164 LDAP, and a modified version of this normally called RFC 2307bis, with
7165 some modifications to be compatible with Active Directory. The RFC
7166 specification handle the content of a lot of system databases, but do
7167 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7168
7169 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7170 we would like to store information about users, SMB clients/hosts,
7171 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7172 and LTSP configuration in LDAP. These objects have a lot in common,
7173 but with the current LDAP schemas it is not possible to have one
7174 object per entity. For example, one need to have at least three LDAP
7175 objects for a given computer, one with the SMB related stuff, one with
7176 DNS information and another with DHCP information. The schemas
7177 provided for DNS and DHCP are impossible to combine into one LDAP
7178 object. In addition, it is impossible to implement quick queries for
7179 netgroup membership, because of the way NIS triples are implemented.
7180 It just do not scale. I believe it is time for a few RFC
7181 specifications to cleam up this mess.&lt;/p&gt;
7182
7183 &lt;p&gt;I would like to have one LDAP object representing each computer in
7184 the network, and this object can then keep the SMB (ie host key), DHCP
7185 (mac address/name) and DNS (name/IP address) settings in one place.
7186 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7187
7188 &lt;p&gt;I would also like to have a quick way to map from a user or
7189 computer and to the net group this user or computer is a member.&lt;/p&gt;
7190
7191 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7192 in this regard, and the unix side need to catch up. Time to start a
7193 new IETF work group?&lt;/p&gt;
7194 </description>
7195 </item>
7196
7197 <item>
7198 <title>Endelig er Debian Lenny gitt ut</title>
7199 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7200 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7201 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7202 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7203 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7204 Et langt steg videre for Debian-prosjektet, og en rekke nye
7205 programpakker blir nå tilgjengelig for de av oss som bruker den
7206 stabile utgaven av Debian. Neste steg er nå å få
7207 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7208 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7209 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7210 slippes løs på skolene. Takk til alle debian-utviklerne som har
7211 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7212 bootsekvens tilgjengelig i stabil utgave, vha pakken
7213 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7214 </description>
7215 </item>
7216
7217 <item>
7218 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7219 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7220 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7221 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7222 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7223 Oslo. Most of Saturday was used for the general assemly for the
7224 member organization, but the rest of the weekend I used to tune the
7225 LTSP installation. LTSP now work out of the box on the 10-network.
7226 Acer Aspire One proved to be a very nice thin client, with both
7227 screen, mouse and keybard in a small box. Was working on getting the
7228 diskless workstation setup configured out of the box, but did not
7229 finish it before the weekend was up.&lt;/p&gt;
7230
7231 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7232 the Brazilian group, so that will have to wait for the next
7233 development gathering. Would love to have the Debian Edu installer
7234 automatically detect and configure a multiseat setup when it find one
7235 of these cards.&lt;/p&gt;
7236 </description>
7237 </item>
7238
7239 <item>
7240 <title>The sorry state of multimedia browser plugins in Debian</title>
7241 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7242 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7243 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7244 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7245 plugins available in Debian Lenny, to see which one we should use by
7246 default in Debian Edu. We need an embedded video playing plugin with
7247 control buttons to pause or stop the video, and capable of streaming
7248 all the multimedia content available on the web. The test results and
7249 notes are available on
7250 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7251 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7252 fill this need. My personal video player favorite, VLC, has a really
7253 bad plugin which fail on a lot of the test pages. A lot of the MIME
7254 types I would expect to work with any free software player (like
7255 video/ogg), just do not work. And simple formats like the
7256 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7257 totem and vlc plugins. I hope the situation will improve soon. No
7258 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7259
7260 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7261 be the only one fitting our needs. :/&lt;/p&gt;
7262 </description>
7263 </item>
7264
7265 </channel>
7266 </rss>