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