]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
67a760e43451b19c80765877f676b80efeed5913
[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>Suddenly I am the new upstream of the lsdvd command line tool</title>
11 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
13 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
14 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
15 to handle my fairly large DVD collection. It is a nice command line
16 tool to get details about a DVD, like title, tracks, track length,
17 etc, in XML, Perl or human readable format. But lsdvd have not seen
18 any new development since 2006 and had a few irritating bugs affecting
19 its use with some DVDs. Upstream seemed to be dead, and in January I
20 sent a small probe asking for a version control repository for the
21 project, without any reply. But I use it regularly and would like to
22 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
23 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
24 the project admin, and after getting a reply from him explaining that
25 he was no longer interested in the project, I asked if I could take
26 over. And yesterday, I became project admin.&lt;/p&gt;
27
28 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
29 maintainer interested in joining forces to maintain the upstream
30 project, and I hope we can get a new release out fairly quickly,
31 collecting the patches spread around on the internet into on place.
32 I&#39;ve added the relevant Debian patches to the freshly created git
33 repository, and expect the Gentoo patches to make it too. If you got
34 a DVD collection and care about command line tools, check out
35 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
36 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
37 list&lt;/a&gt;. :)&lt;/p&gt;
38 </description>
39 </item>
40
41 <item>
42 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
43 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
44 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
45 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
46 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
47 a lot quicker. When we install more than 2000 packages in
48 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
49 tasksel in the installer, unpacking the binary packages take forever.
50 A part of the slow I/O issue was discussed in
51 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
52 much file system sync-ing done by dpkg, which is the package
53 responsible for unpacking the binary packages. Other parts (like code
54 executed by postinst scripts) might also sync to disk during
55 installation. All this sync-ing to disk do not really make sense to
56 me. If the machine crash half-way through, I start over, I do not try
57 to salvage the half installed system. So the failure sync-ing is
58 supposed to protect against, hardware or system crash, is not really
59 relevant while the installer is running.&lt;/p&gt;
60
61 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
62 system sync()-ing in a fairly non-intrusive way, without the need to
63 change the code in several packages. The idea is not new, but I have
64 not heard anyone propose the approach using dpkg-divert before. It
65 depend on the small and clever package
66 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
67 uses LD_PRELOAD to replace the system functions for syncing data to
68 disk with functions doing nothing, thus allowing programs to live
69 dangerous while speeding up disk I/O significantly. Instead of
70 modifying the implementation of dpkg, apt and tasksel (which are the
71 packages responsible for selecting, fetching and installing packages),
72 it occurred to me that we could just divert the programs away, replace
73 them with a simple shell wrapper calling
74 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
75 Two days ago I decided to test the idea, and wrapped up a simple
76 implementation for the Debian Edu udeb.&lt;/p&gt;
77
78 &lt;p&gt;The effect was stunning. In my first test it reduced the running
79 time of the pkgsel step (installing tasks) from 64 to less than 44
80 minutes (20 minutes shaved off the installation) on an old Dell
81 Latitude D505 machine. I am not quite sure what the optimised time
82 would have been, as I messed up the testing a bit, causing the debconf
83 priority to get low enough for two questions to pop up during
84 installation. As soon as I saw the questions I moved the installation
85 along, but do not know how long the question were holding up the
86 installation. I did some more measurements using Debian Edu Jessie,
87 and got these results. The time measured is the time stamp in
88 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
89 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
90 yourself. In Debian Edu, the tasksel dialog do not show up, and the
91 timing thus do not depend on how quickly the user handle the tasksel
92 dialog.&lt;/p&gt;
93
94 &lt;p&gt;&lt;table&gt;
95
96 &lt;tr&gt;
97 &lt;th&gt;Machine/setup&lt;/th&gt;
98 &lt;th&gt;Original tasksel&lt;/th&gt;
99 &lt;th&gt;Optimised tasksel&lt;/th&gt;
100 &lt;th&gt;Reduction&lt;/th&gt;
101 &lt;/tr&gt;
102
103 &lt;tr&gt;
104 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
105 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
106 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
107 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
108 &lt;/tr&gt;
109
110 &lt;tr&gt;
111 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
112 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
113 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
114 &lt;td&gt;23 min 40%&lt;/td&gt;
115 &lt;/tr&gt;
116
117 &lt;tr&gt;
118 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
119 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
120 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
121 &lt;td&gt;11 min 50%&lt;/td&gt;
122 &lt;/tr&gt;
123
124 &lt;tr&gt;
125 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
126 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
127 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
128 &lt;td&gt;2 min 33%&lt;/td&gt;
129 &lt;/tr&gt;
130
131 &lt;tr&gt;
132 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
133 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
134 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
135 &lt;td&gt;4 min 21%&lt;/td&gt;
136 &lt;/tr&gt;
137
138 &lt;/table&gt;&lt;/p&gt;
139
140 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
141 time is spent downloading packages. The connection to the Internet
142 was 100Mbit/s during testing, so downloading should not be a
143 significant factor in the measurement. Download typically took a few
144 seconds to a few minutes, depending on the amount of packages being
145 installed.&lt;/p&gt;
146
147 &lt;p&gt;The speedup is implemented by using two hooks in
148 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
149 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
150 finish-install.d hook to remove the divert at the end of the
151 installation. I picked the pre-pkgsel.d hook instead of the
152 post-base-installer.d hook because I test using an ISO without the
153 eatmydata package included, and the post-base-installer.d hook in
154 Debian Edu can only operate on packages included in the ISO. The
155 negative effect of this is that I am unable to activate this
156 optimization for the kernel installation step in d-i. If the code is
157 moved to the post-base-installer.d hook, the speedup would be larger
158 for the entire installation.&lt;/p&gt;
159
160 &lt;p&gt;I&#39;ve implemented this in the
161 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
162 git repository, and plan to provide the optimization as part of the
163 Debian Edu installation. If you want to test this yourself, you can
164 create two files in the installer (or in an udeb). One shell script
165 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
166
167 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
168 #!/bin/sh
169 set -e
170 . /usr/share/debconf/confmodule
171 info() {
172 logger -t my-pkgsel &quot;info: $*&quot;
173 }
174 error() {
175 logger -t my-pkgsel &quot;error: $*&quot;
176 }
177 override_install() {
178 apt-install eatmydata || true
179 if [ -x /target/usr/bin/eatmydata ] ; then
180 for bin in dpkg apt-get aptitude tasksel ; do
181 file=/usr/bin/$bin
182 # Test that the file exist and have not been diverted already.
183 if [ -f /target$file ] ; then
184 info &quot;diverting $file using eatmydata&quot;
185 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
186 &gt; /target$file.edu
187 chmod 755 /target$file.edu
188 in-target dpkg-divert --package debian-edu-config \
189 --rename --quiet --add $file
190 ln -sf ./$bin.edu /target$file
191 else
192 error &quot;unable to divert $file, as it is missing.&quot;
193 fi
194 done
195 else
196 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
197 fi
198 }
199
200 override_install
201 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
202
203 &lt;p&gt;To clean up, another shell script should go into
204 /usr/lib/finish-install.d/ with code like this:
205
206 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
207 #! /bin/sh -e
208 . /usr/share/debconf/confmodule
209 error() {
210 logger -t my-finish-install &quot;error: $@&quot;
211 }
212 remove_install_override() {
213 for bin in dpkg apt-get aptitude tasksel ; do
214 file=/usr/bin/$bin
215 if [ -x /target$file.edu ] ; then
216 rm /target$file
217 in-target dpkg-divert --package debian-edu-config \
218 --rename --quiet --remove $file
219 rm /target$file.edu
220 else
221 error &quot;Missing divert for $file.&quot;
222 fi
223 done
224 sync # Flush file buffers before continuing
225 }
226
227 remove_install_override
228 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
229
230 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
231 edu-eatmydata-install and call it from the pre-pkgsel.d and
232 finish-install.d scripts.&lt;/p&gt;
233
234 &lt;p&gt;By now you might ask if this change should get into the normal
235 Debian installer too? I suspect it should, but am not sure the
236 current debian-installer coordinators find it useful enough. It also
237 depend on the side effects of the change. I&#39;m not aware of any, but I
238 guess we will see if the change is safe after some more testing.
239 Perhaps there is some package in Debian depending on sync() and
240 fsync() having effect? Perhaps it should go into its own udeb, to
241 allow those of us wanting to enable it to do so without affecting
242 everyone.&lt;/p&gt;
243
244 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
245 will break installation of all programs using gnutls because of
246 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711. An updated
247 eatmydata package in Debian will solve it.&lt;/p&gt;
248 </description>
249 </item>
250
251 <item>
252 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
253 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
254 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
255 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
256 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
257 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
258 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
259 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
260 learn that there is a large set of publicly available key servers to
261 use when looking for peoples public key. So far I have used
262 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
263 were misbehaving, but those days are ended. The servers I have used
264 up until yesterday have been slow and some times unavailable. I hope
265 those problems are gone now.&lt;/p&gt;
266
267 &lt;p&gt;Behind the round robin DNS entry of the
268 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
269 there is a pool of more than 100 keyservers which are checked every
270 day to ensure they are well connected and up to date. It must be
271 better than what I have used so far. :)&lt;/p&gt;
272
273 &lt;p&gt;Yesterdays speaker told me that the service is the default
274 keyserver provided by the default configuration in GnuPG, but this do
275 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
276
277 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
278 line:&lt;/p&gt;
279
280 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
281 keyserver pool.sks-keyservers.net
282 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
283
284 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
285 entries in DNS. Just for fun, I did just that at work, so now every
286 user of GnuPG at the University of Oslo should find a OpenGPG
287 keyserver automatically should their need it:&lt;/p&gt;
288
289 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
290 % host -t srv _pgpkey-http._tcp.uio.no
291 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
292 %
293 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
294
295 &lt;p&gt;Now if only
296 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
297 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
298 very happy. It can look up a given key or search for a user ID, but I
299 normally do not want that, but to find a trust path from my key to
300 another key. Given a user ID or key ID, I would like to find (and
301 download) the keys representing a signature path from my key to the
302 key in question, to be able to get a trust path between the two keys.
303 This is as far as I can tell not possible today. Perhaps something
304 for a future version of the protocol?&lt;/p&gt;
305 </description>
306 </item>
307
308 <item>
309 <title>From English wiki to translated PDF and epub via Docbook</title>
310 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
311 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
312 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
313 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
314 project&lt;/a&gt; provide an instruction manual for teachers, system
315 administrators and other users that contain useful tips for setting up
316 and maintaining a Debian Edu installation. This text is about how the
317 text processing of this manual is handled in the project.&lt;/p&gt;
318
319 &lt;p&gt;One goal of the project is to provide information in the native
320 language of its users, and for this we need to handle translations.
321 But we also want to make sure each language contain the same
322 information, so for this we need a good way to keep the translations
323 in sync. And we want it to be easy for our users to improve the
324 documentation, avoiding the need to learn special formats or tools to
325 contribute, and the obvious way to do this is to make it possible to
326 edit the documentation using a web browser. We also want it to be
327 easy for translators to keep the translation up to date, and give them
328 help in figuring out what need to be translated. Here is the list of
329 tools and the process we have found trying to reach all these
330 goals.&lt;/p&gt;
331
332 &lt;p&gt;We maintain the authoritative source of our manual in the
333 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
334 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
335 front page with references to the different chapters, several pages
336 for each chapter, and finally one &quot;collection page&quot; gluing all the
337 chapters together into one large web page (aka
338 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
339 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
340 processing and translations. Thanks to the fact that the
341 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
342 wiki.debian.org support exporting pages in
343 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
344 the list of pages to export using the raw version of the AllInOne
345 page, loop over each of them to generate a Docbook XML version of the
346 manual. This process also download images and transform image
347 references to use the locally downloaded images. The generated
348 Docbook XML files are slightly broken, so some post-processing is done
349 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
350 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
351 a handfull of images. The XML file can now be used to generate PDF, HTML
352 and epub versions of the English manual. This is the basic step of
353 our process, making PDF (using dblatex), HTML (using xsltproc) and
354 epub (using dbtoepub) version from Docbook XML, and the resulting files
355 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
356
357 &lt;p&gt;But English documentation is not enough for us. We want translated
358 documentation too, and we want to make it easy for translators to
359 track the English original. For this we use the
360 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
361 which allow us to transform the English Docbook XML file into a
362 translation file (a .pot file), usable with the normal gettext based
363 translation tools used by those translating free software. The pot
364 file is used to create and maintain translation files (several .po
365 files), which the translations update with the native language
366 translations of all titles, paragraphs and blocks of text in the
367 original. The next step is combining the original English Docbook XML
368 and the translation file (say debian-edu-wheezy-manual.nb.po), to
369 create a translated Docbook XML file (in this case
370 debian-edu-wheezy-manual.nb.xml). This translated (or partly
371 translated, if the translation is not complete) Docbook XML file can
372 then be used like the original to create a PDF, HTML and epub version
373 of the documentation.&lt;/p&gt;
374
375 &lt;p&gt;The translators use different tools to edit the .po files. We
376 recommend using
377 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
378 while some use emacs and vi, others can use web based editors like
379 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
380 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
381 is where the .po file end up, in our git repository. Updated
382 translations can either be committed directly to git, or submitted as
383 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
384 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
385
386 &lt;p&gt;One challenge is images, which both might need to be translated (if
387 they show translated user applications), and are needed in different
388 formats when creating PDF and HTML versions (epub is a HTML version in
389 this regard). For this we transform the original PNG images to the
390 needed density and format during build, and have a way to provide
391 translated images by storing translated versions in
392 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
393 package maintainers know more.&lt;/p&gt;
394
395 &lt;p&gt;If you wonder what the result look like, we provide
396 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
397 of the documentation packages on the web&lt;/a&gt;. See for example the
398 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
399 PDF version&lt;/a&gt; or the
400 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
401 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
402 but perhaps it will be done in the future.&lt;/p&gt;
403
404 &lt;p&gt;To learn more, check out
405 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
406 debian-edu-doc package&lt;/a&gt;,
407 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
408 manual on the wiki&lt;/a&gt; and
409 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
410 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
411 </description>
412 </item>
413
414 <item>
415 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
416 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
417 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
418 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
419 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
420 related packages relevant for the computer installed automatically.
421 So I implemented one, using
422 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
423 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
424 run tasksel as user root. You should be presented with a new option,
425 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
426 select it, tasksel will install the packages isenkram claim is fit for
427 the current hardware, hot pluggable or not.&lt;p&gt;
428
429 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
430 description, and the other is the script used to extract the list of
431 packages to install. The first part is in
432 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
433 this:&lt;/p&gt;
434
435 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
436 Task: isenkram
437 Section: hardware
438 Description: Hardware specific packages (autodetected by isenkram)
439 Based on the detected hardware various hardware specific packages are
440 proposed.
441 Test-new-install: mark show
442 Relevance: 8
443 Packages: for-current-hardware
444 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
445
446 &lt;p&gt;The second part is in
447 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
448 this:&lt;/p&gt;
449
450 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
451 #!/bin/sh
452 #
453 (
454 isenkram-lookup
455 isenkram-autoinstall-firmware -l
456 ) | sort -u
457 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
458
459 &lt;p&gt;All in all, a very short and simple implementation making it
460 trivial to install the hardware dependent package we all may want to
461 have installed on our machines. I&#39;ve not been able to find a way to
462 get tasksel to tell you exactly which packages it plan to install
463 before doing the installation. So if you are curious or careful,
464 check the output from the isenkram-* command line tools first.&lt;/p&gt;
465
466 &lt;p&gt;The information about which packages are handling which hardware is
467 fetched either from the isenkram package itself in
468 /usr/share/isenkram/, from git.debian.org or from the APT package
469 database (using the Modaliases header). The APT package database
470 parsing have caused a nasty resource leak in the isenkram daemon (bugs
471 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
472 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
473 the python-apt code (bug
474 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
475 workaround I was able to get rid of the file descriptor leak and
476 reduce the memory leak from ~30 MiB per hardware detection down to
477 around 2 MiB per hardware detection. It should make the desktop
478 daemon a lot more useful. The fix is in version 0.7 uploaded to
479 unstable today.&lt;/p&gt;
480
481 &lt;p&gt;I believe the current way of mapping hardware to packages in
482 Isenkram is is a good draft, but in the future I expect isenkram to
483 use the AppStream data source for this. A proposal for getting proper
484 AppStream support into Debian is floating around as
485 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
486 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
487 project&lt;/a&gt; will take place this summer to improve the situation. I
488 look forward to seeing the result, and welcome patches for isenkram to
489 start using the information when it is ready.&lt;/p&gt;
490
491 &lt;p&gt;If you want your package to map to some specific hardware, either
492 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
493 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
494 package&lt;/a&gt; or submit a bug report with the details to the isenkram
495 package. See also
496 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
497 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
498 the information will be migrated to AppStream eventually, but for the
499 moment I got no better place to store it.&lt;/p&gt;
500 </description>
501 </item>
502
503 <item>
504 <title>FreedomBox milestone - all packages now in Debian Sid</title>
505 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
506 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
507 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
508 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
509 project&lt;/a&gt; is working on providing the software and hardware to make
510 it easy for non-technical people to host their data and communication
511 at home, and being able to communicate with their friends and family
512 encrypted and away from prying eyes. It is still going strong, and
513 today a major mile stone was reached.&lt;/p&gt;
514
515 &lt;p&gt;Today, the last of the packages currently used by the project to
516 created the system images were accepted into Debian Unstable. It was
517 the freedombox-setup package, which is used to configure the images
518 during build and on the first boot. Now all one need to get going is
519 the build code from the freedom-maker git repository and packages from
520 Debian. And once the freedombox-setup package enter testing, we can
521 build everything directly from Debian. :)&lt;/p&gt;
522
523 &lt;p&gt;Some key packages used by Freedombox are
524 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
525 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
526 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
527 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
528 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
529 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
530 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
531 are plans to integrate more packages into the setup. User
532 documentation is maintained on the Debian wiki. Please
533 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
534 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
535
536 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
537 setup, run this on a Debian machine using a user with sudo rights to
538 become root:&lt;/p&gt;
539
540 &lt;p&gt;&lt;pre&gt;
541 sudo apt-get install git vmdebootstrap mercurial python-docutils \
542 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
543 u-boot-tools
544 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
545 freedom-maker
546 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
547 &lt;/pre&gt;&lt;/p&gt;
548
549 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
550 devices. See the README in the freedom-maker git repo for more
551 details on the build. If you do not want all three images, trim the
552 make line. Note that the virtualbox-image target is not really
553 virtualbox specific. It create a x86 image usable in kvm, qemu,
554 vmware and any other x86 virtual machine environment. You might need
555 the version of vmdebootstrap in Jessie to get the build working, as it
556 include fixes for a race condition with kpartx.&lt;/p&gt;
557
558 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
559 method, boot a Debian Wheezy ISO and use this boot argument to load
560 the preseed values:&lt;/p&gt;
561
562 &lt;p&gt;&lt;pre&gt;
563 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;
564 &lt;/pre&gt;&lt;/p&gt;
565
566 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
567 it still work.&lt;/p&gt;
568
569 &lt;p&gt;If you wonder how to help, one task you could look at is using
570 systemd as the boot system. It will become the default for Linux in
571 Jessie, so we need to make sure it is usable on the Freedombox. I did
572 a simple test a few weeks ago, and noticed dnsmasq failed to start
573 during boot when using systemd. I suspect there are other problems
574 too. :) To detect problems, there is a test suite included, which can
575 be run from the plinth web interface.&lt;/p&gt;
576
577 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
578 us get the new release published. :) Please join us on
579 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
580 irc.debian.org)&lt;/a&gt; and
581 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
582 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
583 </description>
584 </item>
585
586 <item>
587 <title>S3QL, a locally mounted cloud file system - nice free software</title>
588 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
589 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
590 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
591 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
592 solution for use at home. My requirements are simple, it must be
593 cheap and locally encrypted (in other words, I keep the encryption
594 keys, the storage provider do not have access to my private files).
595 One idea me and my friends had many years ago, before the cloud
596 storage providers showed up, was to use Google mail as storage,
597 writing a Linux block device storing blocks as emails in the mail
598 service provided by Google, and thus get heaps of free space. On top
599 of this one can add encryption, RAID and volume management to have
600 lots of (fairly slow, I admit that) cheap and encrypted storage. But
601 I never found time to implement such system. But the last few weeks I
602 have looked at a system called
603 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
604 mounted network backed file system with the features I need.&lt;/p&gt;
605
606 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
607 handling several different storage providers, any with Amazon S3,
608 Google Drive or OpenStack API. There are heaps of such storage
609 providers. S3QL can also use a local directory as storage, which
610 combined with sshfs allow for file storage on any ssh server. S3QL
611 include support for encryption, compression, de-duplication, snapshots
612 and immutable file systems, allowing me to mount the remote storage as
613 a local mount point, look at and use the files as if they were local,
614 while the content is stored in the cloud as well. This allow me to
615 have a backup that should survive fire. The file system can not be
616 shared between several machines at the same time, as only one can
617 mount it at the time, but any machine with the encryption key and
618 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
619
620 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
621 package is included already. So to get started, run &lt;tt&gt;apt-get
622 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
623 Greenqloud, after reading their nice recipe on
624 &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
625 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
626 in Iceland more than those in USA when it come to keeping my personal
627 data safe and private, and thus would rather spend money on a company
628 in Iceland. Another nice recipe is available from the article
629 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
630 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
631 Admin magazine. When the provider is picked, figure out how to get
632 the API key needed to connect to the storage API. With Greencloud,
633 the key did not show up until I had added payment details to my
634 account.&lt;/p&gt;
635
636 &lt;p&gt;Armed with the API access details, it is time to create the file
637 system. First, create a new bucket in the cloud. This bucket is the
638 file system storage area. I picked a bucket name reflecting the
639 machine that was going to store data there, but any name will do.
640 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
641 the API login and password, and a locally created password. Store it
642 all in ~root/.s3ql/authinfo2 like this:
643
644 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
645 [s3c]
646 storage-url: s3c://s.greenqloud.com:443/bucket-name
647 backend-login: API-login
648 backend-password: API-password
649 fs-passphrase: local-password
650 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
651
652 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
653 but any sensible way to create a fairly random password should do it.
654 Armed with these details, it is now time to run mkfs, entering the API
655 details and password to create it:&lt;/p&gt;
656
657 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
658 # mkdir -m 700 /var/lib/s3ql-cache
659 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
660 --ssl s3c://s.greenqloud.com:443/bucket-name
661 Enter backend login:
662 Enter backend password:
663 Before using S3QL, make sure to read the user&#39;s guide, especially
664 the &#39;Important Rules to Avoid Loosing Data&#39; section.
665 Enter encryption password:
666 Confirm encryption password:
667 Generating random encryption key...
668 Creating metadata tables...
669 Dumping metadata...
670 ..objects..
671 ..blocks..
672 ..inodes..
673 ..inode_blocks..
674 ..symlink_targets..
675 ..names..
676 ..contents..
677 ..ext_attributes..
678 Compressing and uploading metadata...
679 Wrote 0.00 MB of compressed metadata.
680 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
681
682 &lt;p&gt;The next step is mounting the file system to make the storage available.
683
684 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
685 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
686 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
687 Using 4 upload threads.
688 Downloading and decompressing metadata...
689 Reading metadata...
690 ..objects..
691 ..blocks..
692 ..inodes..
693 ..inode_blocks..
694 ..symlink_targets..
695 ..names..
696 ..contents..
697 ..ext_attributes..
698 Mounting filesystem...
699 # df -h /s3ql
700 Filesystem Size Used Avail Use% Mounted on
701 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
702 #
703 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
704
705 &lt;p&gt;The file system is now ready for use. I use rsync to store my
706 backups in it, and as the metadata used by rsync is downloaded at
707 mount time, no network traffic (and storage cost) is triggered by
708 running rsync. To unmount, one should not use the normal umount
709 command, as this will not flush the cache to the cloud storage, but
710 instead running the umount.s3ql command like this:
711
712 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
713 # umount.s3ql /s3ql
714 #
715 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
716
717 &lt;p&gt;There is a fsck command available to check the file system and
718 correct any problems detected. This can be used if the local server
719 crashes while the file system is mounted, to reset the &quot;already
720 mounted&quot; flag. This is what it look like when processing a working
721 file system:&lt;/p&gt;
722
723 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
724 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
725 Using cached metadata.
726 File system seems clean, checking anyway.
727 Checking DB integrity...
728 Creating temporary extra indices...
729 Checking lost+found...
730 Checking cached objects...
731 Checking names (refcounts)...
732 Checking contents (names)...
733 Checking contents (inodes)...
734 Checking contents (parent inodes)...
735 Checking objects (reference counts)...
736 Checking objects (backend)...
737 ..processed 5000 objects so far..
738 ..processed 10000 objects so far..
739 ..processed 15000 objects so far..
740 Checking objects (sizes)...
741 Checking blocks (referenced objects)...
742 Checking blocks (refcounts)...
743 Checking inode-block mapping (blocks)...
744 Checking inode-block mapping (inodes)...
745 Checking inodes (refcounts)...
746 Checking inodes (sizes)...
747 Checking extended attributes (names)...
748 Checking extended attributes (inodes)...
749 Checking symlinks (inodes)...
750 Checking directory reachability...
751 Checking unix conventions...
752 Checking referential integrity...
753 Dropping temporary indices...
754 Backing up old metadata...
755 Dumping metadata...
756 ..objects..
757 ..blocks..
758 ..inodes..
759 ..inode_blocks..
760 ..symlink_targets..
761 ..names..
762 ..contents..
763 ..ext_attributes..
764 Compressing and uploading metadata...
765 Wrote 0.89 MB of compressed metadata.
766 #
767 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
768
769 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
770 quick, about the same speed as local file access. Uploading large
771 amount of data is to me limited by the bandwidth out of and into my
772 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
773 which is very close to my upload speed, and downloading the same
774 Debian installation ISO gave me 610 kiB/s, close to my download speed.
775 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
776 network, not the file system code. I do not know what a good cache
777 size would be, but suspect that the cache should e larger than your
778 working set.&lt;/p&gt;
779
780 &lt;p&gt;I mentioned that only one machine can mount the file system at the
781 time. If another machine try, it is told that the file system is
782 busy:&lt;/p&gt;
783
784 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
785 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
786 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
787 Using 8 upload threads.
788 Backend reports that fs is still mounted elsewhere, aborting.
789 #
790 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
791
792 &lt;p&gt;The file content is uploaded when the cache is full, while the
793 metadata is uploaded once every 24 hour by default. To ensure the
794 file system content is flushed to the cloud, one can either umount the
795 file system, or ask S3QL to flush the cache and metadata using
796 s3qlctrl:
797
798 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
799 # s3qlctrl upload-meta /s3ql
800 # s3qlctrl flushcache /s3ql
801 #
802 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
803
804 &lt;p&gt;If you are curious about how much space your data uses in the
805 cloud, and how much compression and deduplication cut down on the
806 storage usage, you can use s3qlstat on the mounted file system to get
807 a report:&lt;/p&gt;
808
809 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
810 # s3qlstat /s3ql
811 Directory entries: 9141
812 Inodes: 9143
813 Data blocks: 8851
814 Total data size: 22049.38 MB
815 After de-duplication: 21955.46 MB (99.57% of total)
816 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
817 Database size: 2.39 MB (uncompressed)
818 (some values do not take into account not-yet-uploaded dirty blocks in cache)
819 #
820 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
821
822 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
823 storage. I did not try to locate them all, but am aware of at least
824 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
825 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
826 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
827 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
828 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
829 accept payment in Bitcoin. Pick one that suit your need. Some of
830 them provide several GiB of free storage, but the prize models are
831 quite different and you will have to figure out what suits you
832 best.&lt;/p&gt;
833
834 &lt;p&gt;While researching this blog post, I had a look at research papers
835 and posters discussing the S3QL file system. There are several, which
836 told me that the file system is getting a critical check by the
837 science community and increased my confidence in using it. One nice
838 poster is titled
839 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
840 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
841 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
842 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
843 and Pamela Smith. Please have a look.&lt;/p&gt;
844
845 &lt;p&gt;Given my problems with different file systems earlier, I decided to
846 check out the mounted S3QL file system to see if it would be usable as
847 a home directory (in other word, that it provided POSIX semantics when
848 it come to locking and umask handling etc). Running
849 &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
850 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
851 no error was found. So the file system can be used for home
852 directories, if one chooses to do so.&lt;/p&gt;
853
854 &lt;p&gt;If you do not want a locally file system, and want something that
855 work without the Linux fuse file system, I would like to mention the
856 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
857 provide locally encrypted backup using a command line client. It have
858 a nicer access control system, where one can split out read and write
859 access, allowing some systems to write to the backup and others to
860 only read from it.&lt;/p&gt;
861
862 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
863 activities, please send Bitcoin donations to my address
864 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
865 </description>
866 </item>
867
868 <item>
869 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
870 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
871 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
872 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
873 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
874 project&lt;/a&gt; is working on providing the software and hardware for
875 making it easy for non-technical people to host their data and
876 communication at home, and being able to communicate with their
877 friends and family encrypted and away from prying eyes. It has been
878 going on for a while, and is slowly progressing towards a new test
879 release (0.2).&lt;/p&gt;
880
881 &lt;p&gt;And what day could be better than the Pi day to announce that the
882 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
883 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
884 system), and can also be installed using a Debian installer preseed
885 file. The Debian based Freedombox is now based on Debian Jessie,
886 where most of the needed packages used are already present. Only one,
887 the freedombox-setup package, is missing. To try to build your own
888 boot image to test the current status, fetch the freedom-maker scripts
889 and build using
890 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
891 with a user with sudo access to become root:
892
893 &lt;pre&gt;
894 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
895 freedom-maker
896 sudo apt-get install git vmdebootstrap mercurial python-docutils \
897 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
898 u-boot-tools
899 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
900 &lt;/pre&gt;
901
902 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
903 devices. See the README for more details on the build. If you do not
904 want all three images, trim the make line. But note that thanks to &lt;a
905 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
906 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
907 kpartx call.&lt;/p&gt;
908
909 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
910 method, boot a Debian Wheezy ISO and use this boot argument to load
911 the preseed values:&lt;/p&gt;
912
913 &lt;pre&gt;
914 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;
915 &lt;/pre&gt;
916
917 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
918 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
919 currently hang while setting up APT sources. Killing the
920 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
921 installation will get the installation going. This affect all
922 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
923
924 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
925 us get the new release published. :) Please join us on
926 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
927 irc.debian.org)&lt;/a&gt; and
928 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
929 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
930 </description>
931 </item>
932
933 <item>
934 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
935 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
936 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
937 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
938 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
939 innetgr tools, because I needed them in
940 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
941 ng-utils, and it has served me well. I placed the project under the
942 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
943 repository. But many years ago, the CVS repository was dropped (lost,
944 not migrated to new hardware, not sure), and the project have lacked a
945 proper home since then.&lt;/p&gt;
946
947 &lt;p&gt;Last summer, I had a look at the package and made a new release
948 fixing a irritating crash bug, but was unable to store the changes in
949 a proper source control system. I applied for a project on
950 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
951 to follow up on it. Until today. :)&lt;/p&gt;
952
953 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
954 now have a new home, and a git repository with the highlight of the
955 history of the project. I published all release tarballs and imported
956 them into the git repository. As the project is really stable and not
957 expected to gain new features any time soon, I decided to make a new
958 release and call it 1.0. Visit the new project home on
959 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
960 if you want to check it out. The new version is also uploaded into
961 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
962 </description>
963 </item>
964
965 <item>
966 <title>Testing sysvinit from experimental in Debian Hurd</title>
967 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
968 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
969 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
970 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
971 their changes into sysvinit, to allow them to use the normal sysvinit
972 boot system instead of their old one. This follow up on the
973 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
974 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
975 get Debian on Hurd working more like Debian on Linux. To get started,
976 I downloaded a prebuilt hard disk image from
977 &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;,
978 and started it using virt-manager.&lt;/p&gt;
979
980 &lt;p&gt;The first think I had to do after logging in (root without any
981 password) was to get the network operational. I followed
982 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
983 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
984 commands as root to get the machine to accept a IP address from the
985 kvm internal DHCP server:&lt;/p&gt;
986
987 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
988 settrans -fgap /dev/netdde /hurd/netdde
989 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
990 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
991 dhclient /dev/eth0
992 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
993
994 &lt;p&gt;After this, the machine had internet connectivity, and I could
995 upgrade it and install the sysvinit packages from experimental and
996 enable it as the default boot system in Hurd.&lt;/p&gt;
997
998 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
999 running on the machine it for ssh login to work a password need to be
1000 set. Also, note that a bug somewhere in openssh on Hurd block
1001 compression from working. Remember to turn that off on the client
1002 side.&lt;/p&gt;
1003
1004 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
1005 stuff:&lt;/p&gt;
1006
1007 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1008 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
1009 deb http://http.debian.net/debian/ experimental main
1010 EOF
1011 apt-get update
1012 apt-get dist-upgrade
1013 apt-get install -t experimental initscripts sysv-rc sysvinit \
1014 sysvinit-core sysvinit-utils
1015 update-alternatives --config runsystem
1016 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1017
1018 &lt;p&gt;To reboot after switching boot system, you have to use
1019 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
1020 yet a sysvinit process able to receive the signals from the normal
1021 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
1022 upgrading every package and rebooting, the network come up with DHCP
1023 after boot as it should, and the settrans/pkill hack mentioned at the
1024 start is no longer needed. But for some strange reason, there are no
1025 longer any login prompt in the virtual console, so I logged in using
1026 ssh instead.
1027
1028 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
1029 fail some times. No idea what the cause is, but hope the Hurd porters
1030 figure it out. At least Justus said on IRC (#debian-hurd on
1031 irc.debian.org) that they are aware of the problem. A way to reduce
1032 the impact is to upgrade to the Hurd packages built by Justus by
1033 adding this repository to the machine:&lt;/p&gt;
1034
1035 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1036 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
1037 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
1038 EOF
1039 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1040
1041 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
1042 http://ftp.debian-ports.org/debian, because some of the packages in
1043 unstable do not yet include the required patches that are lingering in
1044 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
1045
1046 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1047 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
1048 i emacs - GNU Emacs editor (metapackage)
1049 i gdb - GNU Debugger
1050 i hurd-recommended - Miscellaneous translators
1051 i isc-dhcp-client - ISC DHCP client
1052 i isc-dhcp-common - common files used by all the isc-dhcp* packages
1053 i libc-bin - Embedded GNU C Library: Binaries
1054 i libc-dev-bin - Embedded GNU C Library: Development binaries
1055 i libc0.3 - Embedded GNU C Library: Shared libraries
1056 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
1057 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
1058 i multiarch-support - Transitional package to ensure multiarch compatibilit
1059 i A x11-common - X Window System (X.Org) infrastructure
1060 i xorg - X.Org X Window System
1061 i A xserver-xorg - X.Org X server
1062 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
1063 #
1064 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1065
1066 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
1067 X.org did not work out of the box and I never took the time to follow
1068 the porters instructions to fix it. This time I was interested in the
1069 command line stuff.&lt;p&gt;
1070 </description>
1071 </item>
1072
1073 <item>
1074 <title>New chrpath release 0.16</title>
1075 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
1076 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
1077 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
1078 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
1079 find problems in C, C++ and Java code using static source code
1080 analysis. It can detect a lot of different problems, and is very
1081 useful to find memory and locking bugs in the error handling part of
1082 the source. The company behind it provide
1083 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
1084 a community service&lt;/a&gt;, and many hundred free software projects are
1085 already checked. A few days ago I decided to have a closer look at
1086 the Coverity system, and discovered that the
1087 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
1088 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
1089 projects I am involved with was already registered. But these are
1090 fairly big, and I would also like to have a small and easy project to
1091 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
1092 checking of the chrpath project&lt;/a&gt;. It was
1093 added to the checker and discovered seven potential defects. Six of
1094 these were real, mostly resource &quot;leak&quot; when the program detected an
1095 error. Nothing serious, as the resources would be released a fraction
1096 of a second later when the program exited because of the error, but it
1097 is nice to do it right in case the source of the program some time in
1098 the future end up in a library. Having fixed all defects and added
1099 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
1100 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
1101 publish a new release. These are the release notes:&lt;/p&gt;
1102
1103 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
1104
1105 &lt;ul&gt;
1106
1107 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
1108 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
1109 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
1110
1111 &lt;/ul&gt;
1112
1113 &lt;p&gt;You can
1114 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1115 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
1116 project if something is wrong with the new release. The test suite
1117 did not discover any old errors, so if you find a new one, please also
1118 include a test suite check.&lt;/p&gt;
1119 </description>
1120 </item>
1121
1122 <item>
1123 <title>New chrpath release 0.15</title>
1124 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
1125 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
1126 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
1127 <description>&lt;p&gt;After many years break from the package and a vain hope that
1128 development would be continued by someone else, I finally pulled my
1129 acts together this morning and wrapped up a new release of chrpath,
1130 the command line tool to modify the rpath and runpath of already
1131 compiled ELF programs. The update was triggered by the persistence of
1132 Isha Vishnoi at IBM, which needed a new config.guess file to get
1133 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
1134 is working on. I checked the
1135 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
1136 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
1137 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
1138 packages for interesting patches (failed to find the source from
1139 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
1140 These are the release notes:&lt;/p&gt;
1141
1142 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
1143
1144 &lt;ul&gt;
1145
1146 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
1147 with newer architectures. Thanks to isha vishnoi for the heads
1148 up.&lt;/li&gt;
1149
1150 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
1151
1152 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
1153 Matthias Klose.&lt;/li&gt;
1154
1155 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
1156 Petr Machata found in Fedora.&lt;/li&gt;
1157
1158 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
1159 .dynamic is a NULL terminated string. Based on patch found in
1160 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
1161
1162 &lt;/ul&gt;
1163
1164 &lt;p&gt;You can
1165 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
1166 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
1167 project if something is wrong with the new release. The test suite
1168 did not discover any old errors, so if you find a new one, please also
1169 include a testsuite check.&lt;/p&gt;
1170 </description>
1171 </item>
1172
1173 <item>
1174 <title>Debian init.d boot script example for rsyslog</title>
1175 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
1176 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
1177 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
1178 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
1179 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
1180 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
1181 init.d scripts at all. Here is an example init.d script, ie a rewrite
1182 of /etc/init.d/rsyslog:&lt;/p&gt;
1183
1184 &lt;p&gt;&lt;pre&gt;
1185 #!/lib/init/init-d-script
1186 ### BEGIN INIT INFO
1187 # Provides: rsyslog
1188 # Required-Start: $remote_fs $time
1189 # Required-Stop: umountnfs $time
1190 # X-Stop-After: sendsigs
1191 # Default-Start: 2 3 4 5
1192 # Default-Stop: 0 1 6
1193 # Short-Description: enhanced syslogd
1194 # Description: Rsyslog is an enhanced multi-threaded syslogd.
1195 # It is quite compatible to stock sysklogd and can be
1196 # used as a drop-in replacement.
1197 ### END INIT INFO
1198 DESC=&quot;enhanced syslogd&quot;
1199 DAEMON=/usr/sbin/rsyslogd
1200 &lt;/pre&gt;&lt;/p&gt;
1201
1202 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
1203 script was 137 lines, and the above is just 15 lines, most of it meta
1204 info/comments.&lt;/p&gt;
1205
1206 &lt;p&gt;How to do this, you ask? Well, one create a new script
1207 /lib/init/init-d-script looking something like this:
1208
1209 &lt;p&gt;&lt;pre&gt;
1210 #!/bin/sh
1211
1212 # Define LSB log_* functions.
1213 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
1214 # and status_of_proc is working.
1215 . /lib/lsb/init-functions
1216
1217 #
1218 # Function that starts the daemon/service
1219
1220 #
1221 do_start()
1222 {
1223 # Return
1224 # 0 if daemon has been started
1225 # 1 if daemon was already running
1226 # 2 if daemon could not be started
1227 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
1228 || return 1
1229 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
1230 $DAEMON_ARGS \
1231 || return 2
1232 # Add code here, if necessary, that waits for the process to be ready
1233 # to handle requests from services started subsequently which depend
1234 # on this one. As a last resort, sleep for some time.
1235 }
1236
1237 #
1238 # Function that stops the daemon/service
1239 #
1240 do_stop()
1241 {
1242 # Return
1243 # 0 if daemon has been stopped
1244 # 1 if daemon was already stopped
1245 # 2 if daemon could not be stopped
1246 # other if a failure occurred
1247 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
1248 RETVAL=&quot;$?&quot;
1249 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
1250 # Wait for children to finish too if this is a daemon that forks
1251 # and if the daemon is only ever run from this initscript.
1252 # If the above conditions are not satisfied then add some other code
1253 # that waits for the process to drop all resources that could be
1254 # needed by services started subsequently. A last resort is to
1255 # sleep for some time.
1256 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
1257 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
1258 # Many daemons don&#39;t delete their pidfiles when they exit.
1259 rm -f $PIDFILE
1260 return &quot;$RETVAL&quot;
1261 }
1262
1263 #
1264 # Function that sends a SIGHUP to the daemon/service
1265 #
1266 do_reload() {
1267 #
1268 # If the daemon can reload its configuration without
1269 # restarting (for example, when it is sent a SIGHUP),
1270 # then implement that here.
1271 #
1272 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
1273 return 0
1274 }
1275
1276 SCRIPTNAME=$1
1277 scriptbasename=&quot;$(basename $1)&quot;
1278 echo &quot;SN: $scriptbasename&quot;
1279 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
1280 script=&quot;$1&quot;
1281 shift
1282 . $script
1283 else
1284 exit 0
1285 fi
1286
1287 NAME=$(basename $DAEMON)
1288 PIDFILE=/var/run/$NAME.pid
1289
1290 # Exit if the package is not installed
1291 #[ -x &quot;$DAEMON&quot; ] || exit 0
1292
1293 # Read configuration variable file if it is present
1294 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
1295
1296 # Load the VERBOSE setting and other rcS variables
1297 . /lib/init/vars.sh
1298
1299 case &quot;$1&quot; in
1300 start)
1301 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
1302 do_start
1303 case &quot;$?&quot; in
1304 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1305 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1306 esac
1307 ;;
1308 stop)
1309 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
1310 do_stop
1311 case &quot;$?&quot; in
1312 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
1313 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
1314 esac
1315 ;;
1316 status)
1317 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
1318 ;;
1319 #reload|force-reload)
1320 #
1321 # If do_reload() is not implemented then leave this commented out
1322 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
1323 #
1324 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
1325 #do_reload
1326 #log_end_msg $?
1327 #;;
1328 restart|force-reload)
1329 #
1330 # If the &quot;reload&quot; option is implemented then remove the
1331 # &#39;force-reload&#39; alias
1332 #
1333 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
1334 do_stop
1335 case &quot;$?&quot; in
1336 0|1)
1337 do_start
1338 case &quot;$?&quot; in
1339 0) log_end_msg 0 ;;
1340 1) log_end_msg 1 ;; # Old process is still running
1341 *) log_end_msg 1 ;; # Failed to start
1342 esac
1343 ;;
1344 *)
1345 # Failed to stop
1346 log_end_msg 1
1347 ;;
1348 esac
1349 ;;
1350 *)
1351 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
1352 exit 3
1353 ;;
1354 esac
1355
1356 :
1357 &lt;/pre&gt;&lt;/p&gt;
1358
1359 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
1360 lot. I did not really polish the approach, so it might not always
1361 work out of the box, but you get the idea. I did not try very hard to
1362 optimize it nor make it more robust either.&lt;/p&gt;
1363
1364 &lt;p&gt;A better argument for switching init system in Debian than reducing
1365 the size of init scripts (which is a good thing to do anyway), is to
1366 get boot system that is able to handle the kernel events sensibly and
1367 robustly, and do not depend on the boot to run sequentially. The boot
1368 and the kernel have not behaved sequentially in years.&lt;/p&gt;
1369 </description>
1370 </item>
1371
1372 <item>
1373 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
1374 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
1375 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
1376 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
1377 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
1378 remote display access is the preferred solution with oVirt and RedHat
1379 Enterprise Virtualization, and I was sad to discover the other day
1380 that the browser plugin needed to use these systems seamlessly was
1381 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
1382 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
1383 2013-04-01, so I decided to wrap up a package based on the great work
1384 from Cajus Pollmeier and put it in a collab-maint maintained git
1385 repository to get a package I could use. I would very much like
1386 others to help me maintain the package (or just take over, I do not
1387 mind), but as no-one had volunteered so far, I just uploaded it to
1388 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
1389
1390 &lt;p&gt;The source is now available from
1391 &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;
1392 </description>
1393 </item>
1394
1395 <item>
1396 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
1397 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
1398 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
1399 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
1400 <description>&lt;p&gt;The
1401 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
1402 program is a a very nice system to create virtual machine images. It
1403 create a image file, add a partition table, mount it and run
1404 debootstrap in the mounted directory to create a Debian system on a
1405 stick. Yesterday, I decided to try to teach it how to make images for
1406 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
1407 of a plan to simplify the build system for
1408 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
1409 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
1410 the virtualbox images, but its current build system made multistrap
1411 based system for Dreamplug images, and it is lacking support for
1412 Raspberry Pi.&lt;/p&gt;
1413
1414 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
1415 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
1416 code and adjusted it to be able to build armel images on my amd64
1417 Debian laptop. I ended up giving vmdebootstrap five new options,
1418 allowing me to replicate the image creation process I use to make
1419 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
1420 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
1421 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
1422 call debootstrap with --foreign and to copy the handler into the
1423 generated chroot before running the second stage. This allow
1424 vmdebootstrap to create armel images on an amd64 host. Next I added
1425 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
1426 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
1427 given file system type, allowing me to create an image with a vfat
1428 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
1429 variant&lt;/tt&gt; option to allow me to create smaller images without the
1430 Debian base system packages installed. Finally, I added an option
1431 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
1432 as a boot loader. It is not needed on the Raspberry Pi and probably
1433 most other non-x86 architectures. The changes were accepted by the
1434 upstream author of vmdebootstrap yesterday and today, and is now
1435 available from
1436 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
1437 upstream project page&lt;/a&gt;.&lt;/p&gt;
1438
1439 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
1440 create a small script (the customize script) to add the non-free
1441 binary blob needed to boot the Raspberry Pi and the APT source
1442 list:&lt;/p&gt;
1443
1444 &lt;p&gt;&lt;pre&gt;
1445 #!/bin/sh
1446 set -e # Exit on first error
1447 rootdir=&quot;$1&quot;
1448 cd &quot;$rootdir&quot;
1449 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
1450 deb http://http.debian.net/debian/ jessie main contrib non-free
1451 EOF
1452 # Install non-free binary blob needed to boot Raspberry Pi. This
1453 # install a kernel somewhere too.
1454 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
1455 -O $rootdir/usr/bin/rpi-update
1456 chmod a+x $rootdir/usr/bin/rpi-update
1457 mkdir -p $rootdir/lib/modules
1458 touch $rootdir/boot/start.elf
1459 chroot $rootdir rpi-update
1460 &lt;/pre&gt;&lt;/p&gt;
1461
1462 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
1463 to build the image:&lt;/p&gt;
1464
1465 &lt;pre&gt;
1466 sudo ./vmdebootstrap \
1467 --variant minbase \
1468 --arch armel \
1469 --distribution jessie \
1470 --mirror http://http.debian.net/debian \
1471 --image test.img \
1472 --size 600M \
1473 --bootsize 64M \
1474 --boottype vfat \
1475 --log-level debug \
1476 --verbose \
1477 --no-kernel \
1478 --no-extlinux \
1479 --root-password raspberry \
1480 --hostname raspberrypi \
1481 --foreign /usr/bin/qemu-arm-static \
1482 --customize `pwd`/customize \
1483 --package netbase \
1484 --package git-core \
1485 --package binutils \
1486 --package ca-certificates \
1487 --package wget \
1488 --package kmod
1489 &lt;/pre&gt;&lt;/p&gt;
1490
1491 &lt;p&gt;The list of packages being installed are the ones needed by
1492 rpi-update to make the image bootable on the Raspberry Pi, with the
1493 exception of netbase, which is needed by debootstrap to find
1494 /etc/hosts with the minbase variant. I really wish there was a way to
1495 set up an Raspberry Pi using only packages in the Debian archive, but
1496 that is not possible as far as I know, because it boots from the GPU
1497 using a non-free binary blob.&lt;/p&gt;
1498
1499 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
1500 probably a few others installed. I have not checked the complete
1501 build dependency list.&lt;/p&gt;
1502
1503 &lt;p&gt;The resulting image will not use the hardware floating point unit
1504 on the Raspberry PI, because the armel architecture in Debian is not
1505 optimized for that use. So the images created will be a bit slower
1506 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
1507 </description>
1508 </item>
1509
1510 <item>
1511 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
1512 <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>
1513 <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>
1514 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
1515 <description>&lt;p&gt;The last few days I came across a few good causes that should get
1516 wider attention. I recommend signing and donating to each one of
1517 these. :)&lt;/p&gt;
1518
1519 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
1520 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
1521 Women program which is a Google Summer of Code like initiative to get
1522 more women involved in free software. One debian sponsor has offered
1523 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
1524 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
1525 hope you will to. :)&lt;/p&gt;
1526
1527 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
1528 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
1529 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
1530 take place these days, and their need to fund the work. I&#39;ve already
1531 donated. Are you next?&lt;/p&gt;
1532
1533 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
1534 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
1535 statement under the heading
1536 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
1537 Access&lt;/a&gt; for those of us asking for more focus on open access in the
1538 Norwegian government. So far 499 signatures. I hope you will sign it
1539 too.&lt;/p&gt;
1540 </description>
1541 </item>
1542
1543 <item>
1544 <title>Videos about the Freedombox project - for inspiration and learning</title>
1545 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
1546 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
1547 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
1548 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
1549 project&lt;/a&gt; have been going on for a while, and have presented the
1550 vision, ideas and solution several places. Here is a little
1551 collection of videos of talks and presentation of the project.&lt;/p&gt;
1552
1553 &lt;ul&gt;
1554
1555 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
1556 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
1557
1558 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
1559 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1560
1561 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
1562 Freedom in the Cloud - Software Freedom, Privacy and and Security for
1563 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
1564 (Youtube)&lt;/li&gt;
1565
1566 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
1567 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
1568
1569 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
1570 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
1571
1572 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
1573 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
1574 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
1575
1576 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
1577 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
1578 (Youtube)&lt;/li&gt;
1579
1580 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
1581 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
1582
1583 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
1584 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
1585
1586 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
1587 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
1588 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
1589
1590 &lt;/ul&gt;
1591
1592 &lt;p&gt;A larger list is available from
1593 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
1594 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
1595
1596 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
1597 Jessie is coming along quite well, and soon both Owncloud and using
1598 Tor should be available for testers of the Freedombox solution. :) In
1599 a few weeks I hope everything needed to test it is included in Debian.
1600 The withsqlite package is already in Debian, and the plinth package is
1601 pending in NEW. The third and vital part of that puzzle is the
1602 metapackage/setup framework, which is still pending an upload. Join
1603 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
1604 (#freedombox on irc.debian.org)&lt;/a&gt; and
1605 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
1606 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
1607 </description>
1608 </item>
1609
1610 <item>
1611 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
1612 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
1613 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
1614 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
1615 <description>&lt;p&gt;I was introduced to the
1616 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
1617 in 2010, when Eben Moglen presented his vision about serving the need
1618 of non-technical people to keep their personal information private and
1619 within the legal protection of their own homes. The idea is to give
1620 people back the power over their network and machines, and return
1621 Internet back to its intended peer-to-peer architecture. Instead of
1622 depending on a central service, the Freedombox will give everyone
1623 control over their own basic infrastructure.&lt;/p&gt;
1624
1625 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
1626 taken priority. But this summers nasty news about the misuse of trust
1627 and privilege exercised by the &quot;western&quot; intelligence gathering
1628 communities increased my eagerness to contribute to a point where I
1629 actually started working on the project a while back.&lt;/p&gt;
1630
1631 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
1632 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
1633 create a simple and cheap Debian based appliance that anyone can hook
1634 up in their home and get access to secure and private services and
1635 communication. The initial deployment platform have been the
1636 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
1637 which is a piece of hardware I do not own. So to be able to test what
1638 the current Freedombox setup look like, I had to come up with a way to install
1639 it on some hardware I do have access to. I have rewritten the
1640 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
1641 image build framework to use .deb packages instead of only copying
1642 setup into the boot images, and thanks to this rewrite I am able to
1643 set up any machine supported by Debian Wheezy as a Freedombox, using
1644 the previously mentioned deb (and a few support debs for packages
1645 missing in Debian).&lt;/p&gt;
1646
1647 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
1648 scripts
1649 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
1650 and a administrative web interface
1651 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
1652 withsqlite), as well as a privacy enhancing proxy based on
1653 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
1654 (freedombox-privoxy). There is also a web/javascript based XMPP
1655 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
1656 trying (unsuccessfully so far) to talk to the XMPP server
1657 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
1658 web interface is pluggable, and the goal is to use it to enable OpenID
1659 services, mesh network connectivity, use of TOR, etc, etc. Not much of
1660 this is really working yet, see
1661 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
1662 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
1663 on github at the moment. The HTTP proxy is operational out of the
1664 box, and the admin web interface can be used to add/remove plinth
1665 users. I&#39;ve not been able to do anything else with it so far, but
1666 know there are several branches spread around github and other places
1667 with lots of half baked features.&lt;/p&gt;
1668
1669 &lt;p&gt;Anyway, if you want to have a look at the current state, the
1670 following recipes should work to give you a test machine to poke
1671 at.&lt;/p&gt;
1672
1673 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
1674
1675 &lt;ol&gt;
1676
1677 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
1678 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
1679 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
1680 to the Debian installer:&lt;p&gt;
1681 &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;
1682
1683 &lt;li&gt;Answer the few language/region/password questions and pick disk to
1684 install on.&lt;/li&gt;
1685
1686 &lt;li&gt;When the installation is finished and the machine have rebooted a
1687 few times, your Freedombox is ready for testing.&lt;/li&gt;
1688
1689 &lt;/ol&gt;
1690
1691 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
1692
1693 &lt;ol&gt;
1694
1695 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
1696 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
1697 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
1698 &lt;pre&gt;
1699 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
1700 &lt;/pre&gt;&lt;/li&gt;
1701 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
1702 &lt;pre&gt;
1703 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
1704 apt-key add -
1705 apt-get update
1706 apt-get install freedombox-setup
1707 /usr/lib/freedombox/setup
1708 &lt;/pre&gt;&lt;/li&gt;
1709 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
1710
1711 &lt;/ol&gt;
1712
1713 &lt;p&gt;You can test it on other architectures too, but because the
1714 freedombox-privoxy package is binary, it will only work as intended on
1715 the architectures where I have had time to build the binary and put it
1716 in my APT repository. But do not let this stop you. It is only a
1717 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
1718
1719 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
1720 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
1721 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
1722 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
1723
1724 &lt;p&gt;Please let me know if this works for you, or if you have any
1725 problems. We gather on the IRC channel
1726 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
1727 irc.debian.org and the
1728 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
1729 mailing list&lt;/a&gt;.&lt;/p&gt;
1730
1731 &lt;p&gt;Once you get your freedombox operational, you can visit
1732 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
1733 welcome screen (dead end - do not be surprised if you are unable to
1734 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
1735 to look at the rest of plinth. The default user is &#39;admin&#39; and the
1736 default password is &#39;secret&#39;.&lt;/p&gt;
1737 </description>
1738 </item>
1739
1740 <item>
1741 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
1742 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
1743 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
1744 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
1745 <description>&lt;p&gt;Earlier, I reported about
1746 &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
1747 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
1748 told by IBM that the original disk should be thrown away. And as
1749 there no longer was a problem if I bricked the firmware, I decided
1750 today to try to install Intel firmware to replace the Lenovo firmware
1751 currently on the disk.&lt;/p&gt;
1752
1753 &lt;p&gt;I searched the Intel site for firmware, and found
1754 &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;
1755 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
1756 according to the site should contain the latest firmware for SSD
1757 disks. I inserted the broken disk in one of my spare laptops and
1758 booted the ISO from a USB stick. The disk was recognized, but the
1759 program claimed the newest firmware already were installed and refused
1760 to insert any Intel firmware. So no change, and the disk is still
1761 unable to handle write load. :( I guess the only way to get them
1762 working would be if Lenovo releases new firmware. No idea how likely
1763 that is. Anyway, just blogging about this test for completeness. I
1764 got a working Samsung disk, and see no point in spending more time on
1765 the broken disks.&lt;/p&gt;
1766 </description>
1767 </item>
1768
1769 <item>
1770 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
1771 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
1772 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
1773 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
1774 <description>&lt;p&gt;Today I switched to
1775 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
1776 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
1777 my new Thinkpad X230, which was delivered with an
1778 &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
1779 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
1780 sustained writes. My hardware supplier have been very forthcoming in
1781 trying to find a solution, and after first trying with another
1782 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
1783 disk instead to fix it once and for all. The Samsung disk survived
1784 the installation of Debian with encrypted disks (filling the disk with
1785 random data during installation killed the first two), and I thus
1786 decided to trust it with my data. I have installed it as a Debian Edu
1787 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
1788 server at home using Kerberos and LDAP, and will use it as my work
1789 station from now on.&lt;/p&gt;
1790
1791 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
1792 Debian Wheezy default installation need to be tuned a bit to increase
1793 performance and increase life time of the disk. The Linux kernel and
1794 user space applications do not yet adjust automatically to such
1795 environment. To make it easier for my self, I created a draft Debian
1796 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
1797 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
1798 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
1799 is set up to adjust the setup of the machine by just installing the
1800 package. If there is any non-SSD disk in the machine, the package
1801 will refuse to install, as I did not try to write any logic to sort
1802 file systems in SSD and non-SSD file systems.&lt;/p&gt;
1803
1804 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
1805 set up Debian Wheezy with an SSD. It is adjusted to my use case,
1806 where I set up the machine with one large encrypted partition (in
1807 addition to /boot), put LVM on top of this and set up partitions on
1808 top of this again. See the README file in the package source for the
1809 references I used to pick the settings. At the moment these
1810 parameters are tuned:&lt;/p&gt;
1811
1812 &lt;ul&gt;
1813
1814 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
1815 (adding discard to /etc/crypttab)&lt;/li&gt;
1816
1817 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
1818 this case a cryptsetup partition) by changing issue_discards from
1819 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
1820
1821 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
1822 systems.&lt;/li&gt;
1823
1824 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
1825 /etc/fstab.&lt;/li&gt;
1826
1827 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
1828
1829 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
1830 cron.daily).&lt;/li&gt;
1831
1832 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
1833 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
1834
1835 &lt;/ul&gt;
1836
1837 &lt;p&gt;During installation, I cancelled the part where the installer fill
1838 the disk with random data, as this would kill the SSD performance for
1839 little gain. My goal with the encrypted file system is to ensure
1840 those stealing my laptop end up with a brick and not a working
1841 computer. I have no hope in keeping the really resourceful people
1842 from getting the data on the disk (see
1843 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
1844 Thus I concluded that adding the discard option to crypttab is the
1845 right thing to do.&lt;/p&gt;
1846
1847 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
1848 it for SSD, but others recommended deadline and a benchmark I found
1849 indicated that deadline might be better for interactive use.&lt;/p&gt;
1850
1851 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
1852 and ext4, but read that it would give a performance hit ever time a
1853 file is removed, and thought it best to that that slowdown once a day
1854 instead of during my work.&lt;/p&gt;
1855
1856 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
1857 this is already done by Debian Edu.&lt;/p&gt;
1858
1859 &lt;p&gt;I have not yet started on the user space tuning. I expect
1860 iceweasel need some tuning, and perhaps other applications too, but
1861 have not yet had time to investigate those parts.&lt;/p&gt;
1862
1863 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
1864 there.&lt;/p&gt;
1865
1866 &lt;p&gt;As for the answer to the question in the title of this blog post,
1867 as far as I know, the only solution I know about is to replace the
1868 disk. It might be possible to flash it with Intel firmware instead of
1869 the Lenovo firmware. But I have not tried and did not want to do so
1870 without approval from Lenovo as I wanted to keep the warranty on the
1871 disk until a solution was found and they wanted the broken disks
1872 back.&lt;/p&gt;
1873 </description>
1874 </item>
1875
1876 <item>
1877 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
1878 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
1879 <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>
1880 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
1881 <description>&lt;p&gt;A few days ago, I wrote about
1882 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
1883 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
1884 was dying during installation because it is unable to cope with
1885 sustained write. My supplier is in contact with
1886 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
1887 replacement disk to try to fix the problem. They decided to send an
1888 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
1889
1890 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
1891 Debian Edu Wheezy with encrypted disk on it. The new disk have the
1892 same firmware version as the original. This time my hope raised
1893 slightly as the installation progressed, as the original disk used to
1894 die after 4-7% of the disk was written to, while this time it kept
1895 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
1896 died again and I was back on square one. I still do not have a new
1897 laptop with a disk I can trust. I can not live with a disk that might
1898 lock up when I download a new
1899 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
1900 other large files. I look forward to hearing from my supplier with
1901 the next proposal from Lenovo.&lt;/p&gt;
1902
1903 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
1904 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
1905 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
1906 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
1907 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
1908 P/N 45N8295, P0C38732.&lt;/p&gt;
1909
1910 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
1911 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
1912 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
1913 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
1914 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
1915 P/N 45N8295, P0C38732.&lt;/p&gt;
1916
1917 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
1918 SA, date and WNPP values. Mentioning all the details here in case
1919 someone is able to use the information to find a way to identify the
1920 failing disk among working ones (if any such working disk actually
1921 exist).&lt;/p&gt;
1922 </description>
1923 </item>
1924
1925 <item>
1926 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
1927 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
1928 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
1929 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
1930 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
1931 Debian Edu developer gathering and Debian and Ubuntu bug squashing
1932 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
1933 member assosiation NUUG&lt;/a&gt; and
1934 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
1935 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
1936 Bitraf&lt;/a&gt;.&lt;/p&gt;
1937
1938 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
1939 welcome, and there is no fee to participate. There is on the other
1940 hand limited space, and only room for 30 people. Please put your name
1941 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
1942 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
1943 </description>
1944 </item>
1945
1946 <item>
1947 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
1948 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
1949 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
1950 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
1951 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
1952 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
1953 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
1954 time to spend on it, and it took a while to find a model I believe
1955 will do the job, but two days ago the replacement finally arrived. I
1956 ended up picking a
1957 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
1958 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
1959 a roaming workstation, and it seemed to work flawlessly. But my
1960 second installation with encrypted disk was not as successful. More
1961 on that below.&lt;/p&gt;
1962
1963 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
1964 important requirements (robust and with a good keyboard) are never
1965 listed in the feature list. But I did get good help from the search
1966 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
1967 allowed me to limit the list of interesting laptops based on my other
1968 requirements. A bit surprising that SSD disk are not disks according
1969 to that search interface, so I had to drop specifying the number of
1970 disks from my search parameters. I also asked around among friends to
1971 get their impression on keyboards and robustness.&lt;/p&gt;
1972
1973 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
1974 X41. I am not quite convinced about the keyboard, as it is
1975 significantly wider than my old keyboard, and I have to stretch my
1976 hand a lot more to reach the edges. But the key response is fairly
1977 good and the individual key shape is fairly easy to handle, so I hope
1978 I will get used to it. My old X40 was starting to fail, and I really
1979 needed a new laptop now. :)&lt;/p&gt;
1980
1981 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
1982 visit to the BIOS during boot it disable it.&lt;/p&gt;
1983
1984 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
1985 lock up during load. And this happen when installing Debian Wheezy
1986 with encrypted disk, while the disk is being filled with random data.
1987 I also tested to install Ubuntu Raring, and it happen there too if I
1988 reenable the code to fill the disk with random data (it is disabled by
1989 default in Ubuntu). And the bug with is already known. It was
1990 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
1991 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
1992 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
1993 kernel developers as
1994 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
1995 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
1996 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
1997 Lenovo forums, both for
1998 &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
1999 2012-11-10&lt;/a&gt; and for
2000 &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
2001 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
2002 reports state that the disk lock up during use if many writes are done
2003 on the disk, so it is much no use to work around the installation
2004 problem and end up with a computer that can lock up at any moment.
2005 There is even a
2006 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
2007 available&lt;/a&gt; that will lock up the hard drive after running a few
2008 minutes by writing to a file.&lt;/p&gt;
2009
2010 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
2011 contacting PCHELP Norway (request 01D1FDP) which handle support
2012 requests for Lenovo, his first suggestion was to upgrade the disk
2013 firmware. Unfortunately there is no newer firmware available from
2014 Lenovo, as my disk already have the most recent one (version LF1i). I
2015 hope to hear more from him today and hope the problem can be
2016 fixed. :)&lt;/p&gt;
2017 </description>
2018 </item>
2019
2020 <item>
2021 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
2022 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
2023 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
2024 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
2025 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
2026 trusty old Thinkpad X41. Unfortunately I did not have much time to
2027 spend on it, but today the replacement finally arrived. I ended up
2028 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
2029 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
2030 Wheezy as a roaming workstation, and it worked flawlessly. As I write
2031 this, it is installing what I hope will be a more final installation,
2032 with a encrypted hard drive to ensure any dope head stealing it end up
2033 with an expencive door stop.&lt;/p&gt;
2034
2035 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
2036 important requirements (robust and with a good keyboard) are never
2037 listed in the feature list. But I did get good help from the search
2038 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
2039 allowed me to limit the list of interesting laptops based on my other
2040 requirements. A bit surprising that SSD disk are not disks, so I had
2041 to drop number of disks from my search parameters.&lt;/p&gt;
2042
2043 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
2044 wider than my old keyboard, and I have to stretch my hand a lot more
2045 to reach the edges. But the key response is fairly good and the
2046 individual key shape is fairly easy to handle, so I hope I will get
2047 used to it. My old X40 was starting to fail, and I really needed a
2048 new laptop now. :)&lt;/p&gt;
2049
2050 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
2051 </description>
2052 </item>
2053
2054 <item>
2055 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
2056 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
2057 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
2058 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
2059 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
2060 perfectly capable of, and I have to do it manually to get things
2061 working. One such task is to find out what firmware packages are
2062 needed to get the hardware on my computer working. Most often this
2063 affect the wifi card, but some times it even affect the RAID
2064 controller or the ethernet card. Today I pushed version 0.4 of the
2065 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
2066 including a new script isenkram-autoinstall-firmware handling the
2067 process of asking all the loaded kernel modules what firmware files
2068 they want, find debian packages providing these files and install the
2069 debian packages. Here is a test run on my laptop:&lt;/p&gt;
2070
2071 &lt;p&gt;&lt;pre&gt;
2072 # isenkram-autoinstall-firmware
2073 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
2074 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
2075 info: locating packages with the requested firmware files
2076 info: Updating APT sources after adding non-free APT source
2077 info: trying to install firmware-ipw2x00
2078 firmware-ipw2x00
2079 firmware-ipw2x00
2080 Preconfiguring packages ...
2081 Selecting previously deselected package firmware-ipw2x00.
2082 (Reading database ... 259727 files and directories currently installed.)
2083 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
2084 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
2085 #
2086 &lt;/pre&gt;&lt;/p&gt;
2087
2088 &lt;p&gt;When all the requested firmware is present, a simple message is
2089 printed instead:&lt;/p&gt;
2090
2091 &lt;p&gt;&lt;pre&gt;
2092 # isenkram-autoinstall-firmware
2093 info: did not find any firmware files requested by loaded kernel modules. exiting
2094 #
2095 &lt;/pre&gt;&lt;/p&gt;
2096
2097 &lt;p&gt;It could use some polish, but it is already working well and saving
2098 me some time when setting up new machines. :)&lt;/p&gt;
2099
2100 &lt;p&gt;So, how does it work? It look at the set of currently loaded
2101 kernel modules, and look up each one of them using modinfo, to find
2102 the firmware files listed in the module meta-information. Next, it
2103 download the Contents file from a nearby APT mirror, and search for
2104 the firmware files in this file to locate the package with the
2105 requested firmware file. If the package is in the non-free section, a
2106 non-free APT source is added and the package is installed using
2107 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
2108 machine.&lt;/p&gt;
2109
2110 &lt;p&gt;I hope someone find time to implement a more polished version of
2111 this script as part of the hw-detect debian-installer module, to
2112 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
2113 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
2114 firmware during a PXE install when the packages already are available
2115 from the nearby Debian mirror.&lt;/p&gt;
2116 </description>
2117 </item>
2118
2119 <item>
2120 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
2121 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
2122 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
2123 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
2124 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
2125 the screen just turn black when Linux boot, either during installation
2126 or on first boot from the hard disk. I&#39;ve seen it once in a while the
2127 last few years, but only recently understood the cause. I&#39;ve seen it
2128 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
2129 The reason seem to be in the wiring of some laptops. The system to
2130 control the screen background light is inverted, so when Linux try to
2131 turn the brightness fully on, it end up turning it off instead. I do
2132 not know which Linux drivers are affected, but this post is about the
2133 i915 driver used by the
2134 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2135 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
2136
2137 &lt;p&gt;The problem can be worked around two ways. Either by adding
2138 i915.invert_brightness=1 as a kernel option, or by adding a file in
2139 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
2140 option when it load the i915 kernel module. On Debian and Ubuntu, it
2141 can be done by running these commands as root:&lt;/p&gt;
2142
2143 &lt;pre&gt;
2144 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
2145 update-initramfs -u -k all
2146 &lt;/pre&gt;
2147
2148 &lt;p&gt;Since March 2012 there is
2149 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
2150 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
2151 hardware have this problem, and get the driver to invert the
2152 brightness setting automatically. To use it, one need to add a row in
2153 &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
2154 intel_quirks array&lt;/a&gt; in the driver source
2155 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
2156 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
2157 number (vendor number 8086 is assumed) and subdevice vendor and device
2158 number.&lt;/p&gt;
2159
2160 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
2161 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
2162
2163 &lt;p&gt;&lt;pre&gt;
2164 00:02.0 VGA compatible controller [0300]: Intel Corporation \
2165 3rd Gen Core processor Graphics Controller [8086:0156] \
2166 (rev 09) (prog-if 00 [VGA controller])
2167 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
2168 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
2169 ParErr- Stepping- SE RR- FastB2B- DisINTx+
2170 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
2171 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
2172 Latency: 0
2173 Interrupt: pin A routed to IRQ 42
2174 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
2175 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
2176 Region 4: I/O ports at 4000 [size=64]
2177 Expansion ROM at &lt;unassigned&gt; [disabled]
2178 Capabilities: &lt;access denied&gt;
2179 Kernel driver in use: i915
2180 &lt;/pre&gt;&lt;/p&gt;
2181
2182 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
2183
2184 &lt;p&gt;&lt;pre&gt;
2185 struct intel_quirk intel_quirks[] = {
2186 ...
2187 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
2188 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
2189 ...
2190 }
2191 &lt;/pre&gt;&lt;/p&gt;
2192
2193 &lt;p&gt;According to the kernel module instructions (as seen using
2194 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
2195 invert_brightness flag should be sent to the
2196 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
2197 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
2198 developers. But my email about the laptop sent 2013-06-03 have not
2199 yet shown up in
2200 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
2201 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
2202 emails from non-subscribers. Because of this, I sent my patch also to
2203 the Debian bug tracking system instead as
2204 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
2205 sure the patch is not lost.&lt;/p&gt;
2206
2207 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
2208 with this problem working properly with Linux. If you use Gnome, your
2209 worries should be over at this point. But if you use KDE, there is
2210 something in KDE ignoring the invert_brightness setting and turning on
2211 the screen during login. I&#39;ve reported it to Debian as
2212 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
2213 have no idea yet how to figure out exactly what subsystem is doing
2214 this. Perhaps you can help? Perhaps you know what the Gnome
2215 developers did to handle this, and this can give a clue to the KDE
2216 developers? Or you know where in KDE the screen brightness is changed
2217 during login? If so, please update the BTS report (or get in touch if
2218 you do not know how to update BTS).&lt;/p&gt;
2219
2220 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
2221 acpi_backlight=vendor, to disable ACPI backlight support completely,
2222 as the ACPI information on the machine is trash and it is better to
2223 leave it to the intel video driver to control the screen
2224 backlight.&lt;/p&gt;
2225 </description>
2226 </item>
2227
2228 <item>
2229 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
2230 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
2231 <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>
2232 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
2233 <description>&lt;p&gt;Two days ago, I asked
2234 &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
2235 I could install Linux on a Packard Bell EasyNote LV computer
2236 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
2237 with the obstacles put in the way of Linux users on a laptop with UEFI
2238 and Windows 8.&lt;/p&gt;
2239
2240 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
2241 secure booting or fast boot. I suspect fast boot was the problem,
2242 causing the firmware to boot directly from HD without considering any
2243 key presses and alternative devices, but do not know UEFI settings
2244 enough to tell.&lt;/p&gt;
2245
2246 &lt;p&gt;There is no way to install Linux on the machine in question without
2247 opening the box and disconnecting the hard drive! This is as far as I
2248 can tell, the only way to get access to the firmware setup menu
2249 without accepting the Windows 8 license agreement. I am told (and
2250 found description on how to) that it is possible to configure the
2251 firmware setup once booted into Windows 8. But as I believe the terms
2252 of that agreement are completely unacceptable, accepting the license
2253 was never an alternative. I do not enter agreements I do not intend
2254 to follow.&lt;/p&gt;
2255
2256 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
2257 waste many hours on this, but luckily there was a way to get it to
2258 work. But I would not recommend it to anyone planning to run Linux on
2259 it, and I have become sceptical to Windows 8 certified laptops. Is
2260 this the way Linux will be forced out of the market place, by making
2261 it close to impossible for &quot;normal&quot; users to install Linux without
2262 accepting the Microsoft Windows license terms? Or at least not
2263 without risking to loose the warranty?&lt;/p&gt;
2264
2265 &lt;p&gt;I&#39;ve updated the
2266 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
2267 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
2268 do not have to struggle as much as I did to get Linux into the
2269 machine.&lt;/p&gt;
2270
2271 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
2272 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
2273 </description>
2274 </item>
2275
2276 <item>
2277 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
2278 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
2279 <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>
2280 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
2281 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
2282 new laptops for my parents and a few others. I bought Packard Bell
2283 Easynote LV to run Kubuntu on and use as their home computer. But I
2284 am completely unable to figure out how to install Linux on it. The
2285 computer is preinstalled with Windows 8, and I suspect it uses UEFI
2286 instead of a BIOS to boot.&lt;/p&gt;
2287
2288 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
2289 to get it to boot the Linux installer from my USB stick. I have yet
2290 to try the DVD install, and still hope it will work. when I turn on
2291 the computer, there is no information on what buttons to press to get
2292 the normal boot menu. I expect to get some boot menu to select PXE or
2293 USB stick booting. When booting, it first ask for the language to
2294 use, then for some regional settings, and finally if I will accept the
2295 Windows 8 terms of use. As these terms are completely unacceptable to
2296 me, I have no other choice but to turn off the computer and try again
2297 to get it to boot the Linux installer.&lt;/p&gt;
2298
2299 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
2300 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
2301 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
2302 installed on this machine, please get in touch or update that wiki
2303 page. If I can&#39;t find a way to install Linux, I will have to return
2304 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
2305
2306 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
2307 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
2308 on new Laptops?&lt;/p&gt;
2309 </description>
2310 </item>
2311
2312 <item>
2313 <title>How to transform a Debian based system to a Debian Edu installation</title>
2314 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
2315 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
2316 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
2317 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
2318 an operating system based on Debian intended for use in schools. It
2319 contain a turn-key solution for the computer network provided to
2320 pupils in the primary schools. It provide both the central server,
2321 network boot servers and desktop environments with heaps of
2322 educational software. The project was founded almost 12 years ago,
2323 2001-07-02. If you want to support the project, which is in need for
2324 cash to fund developer gatherings and other project related activity,
2325 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
2326 donate some money&lt;/a&gt;.
2327
2328 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
2329 lists and elsewhere, is the question on how to transform a Debian or
2330 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
2331 hard, and last week I wrote a script to replicate the steps done by
2332 the Debian Edu installer.&lt;/p&gt;
2333
2334 &lt;p&gt;The script,
2335 &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;
2336 in the debian-edu-config package, will go through these six steps and
2337 transform an existing Debian Wheezy or Ubuntu (untested) installation
2338 into a Debian Edu Workstation:&lt;/p&gt;
2339
2340 &lt;ol&gt;
2341
2342 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
2343 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
2344 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
2345 our configuration.&lt;/li&gt;
2346 &lt;li&gt;Preseed debconf database with profile setup in
2347 /etc/debian-edu/config, and run tasksel to install packages
2348 according to the profile specified in the config above,
2349 overriding some of the Debian automation machinery.&lt;/li&gt;
2350 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
2351 that could not be done using preseeding.&lt;/li&gt;
2352 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
2353
2354 &lt;/ol&gt;
2355
2356 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
2357 replicated like this. Disk partitioning and LVM setup, for example.
2358 So this script just assume there is enough disk space to install all
2359 the needed packages.&lt;/p&gt;
2360
2361 &lt;p&gt;The script was created to help a Debian Edu student working on
2362 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
2363 Debian Edu client, and using it he can take the existing
2364 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
2365 transform it into a fully functioning Debian Edu Workstation (or
2366 Roaming Workstation, or whatever :).&lt;/p&gt;
2367
2368 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
2369 If a LXDE based Roaming workstation is wanted instead, modify the
2370 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
2371
2372 &lt;p&gt;&lt;pre&gt;
2373 PROFILE=&quot;Roaming-Workstation&quot;
2374 DESKTOP=&quot;lxde&quot;
2375 &lt;/pre&gt;&lt;/p&gt;
2376
2377 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
2378 the cloud, by starting with a virtual Debian installation at some
2379 virtual hosting service and setting up all the services on first
2380 boot.&lt;/p&gt;
2381 </description>
2382 </item>
2383
2384 <item>
2385 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
2386 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
2387 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
2388 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
2389 <description>&lt;P&gt;In January,
2390 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
2391 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
2392 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
2393 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
2394 marvellous construction system from Denmark. We also created
2395 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
2396 a place to take notes and write down our plans and hopes. And several
2397 people showed up to help. I was very happy to see the effect of my
2398 call. Since the small start, we have a debtags tag
2399 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
2400 tag for LEGO related packages, and now count 10 packages related to
2401 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
2402
2403 &lt;p&gt;&lt;table&gt;
2404 &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;
2405 &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;
2406 &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;
2407 &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;
2408 &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;
2409 &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;
2410 &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;
2411 &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;
2412 &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;
2413 &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;
2414 &lt;/table&gt;&lt;/p&gt;
2415
2416 &lt;p&gt;Some of these are available in Wheezy, and all but one are
2417 currently available in Jessie/testing. leocad is so far only
2418 available in experimental.&lt;/p&gt;
2419
2420 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
2421 adding the rest of the great free software tools available on Linux
2422 for LEGO designers.&lt;/p&gt;
2423 </description>
2424 </item>
2425
2426 <item>
2427 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
2428 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
2429 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
2430 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
2431 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
2432 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
2433 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
2434 Debian release, and I expect to move my machines at home over to it fairly
2435 soon.&lt;/p&gt;
2436
2437 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
2438 in particular make me very happy to see included. The
2439 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
2440 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
2441 included for the first time. Alongside similar programs like
2442 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
2443 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
2444 it allow for visual programming where syntax errors can not happen,
2445 and a friendly programming environment for learning to control the
2446 computer. Scratch will also be included in the next release of Debian
2447 Edu.&lt;/a&gt;
2448
2449 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
2450 Edu/Skolelinux release too. The
2451 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
2452 alpha release&lt;/a&gt; went out last week, and the next should soon
2453 follow.&lt;p&gt;
2454 </description>
2455 </item>
2456
2457 <item>
2458 <title>Isenkram 0.2 finally in the Debian archive</title>
2459 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
2460 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
2461 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
2462 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
2463 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
2464 for many months. I uploaded it to the Debian experimental suite
2465 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
2466
2467 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
2468 install to work with a pluggable hardware device. The suggestion pop
2469 up when the device is plugged in. For example if a Lego Mindstorm NXT
2470 is inserted, it will suggest to install the program needed to program
2471 the NXT controller. Give it a go, and report bugs and suggestions to
2472 BTS. :)&lt;/p&gt;
2473 </description>
2474 </item>
2475
2476 <item>
2477 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
2478 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
2479 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
2480 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
2481 <description>&lt;p&gt;My
2482 &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
2483 bitcoin related blog post&lt;/a&gt; mentioned that the new
2484 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
2485 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
2486 2013-01-19, and have been available in unstable since then. It was
2487 automatically copied to Ubuntu, and is available in their Raring
2488 version too.&lt;/p&gt;
2489
2490 &lt;p&gt;But there is a strange problem with the build that block this new
2491 version from being available on the i386 and kfreebsd-i386
2492 architectures. For some strange reason, the autobuilders in Debian
2493 for these architectures fail to run the test suite on these
2494 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
2495 We are so far unable to reproduce it when building it manually, and
2496 no-one have been able to propose a fix. If you got an idea what is
2497 failing, please let us know via the BTS.&lt;/p&gt;
2498
2499 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
2500 I often run low on disk space, is the fact that the client will exit
2501 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
2502 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
2503 it. :)&lt;/p&gt;
2504
2505 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
2506 activities, please send Bitcoin donations to my address
2507 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2508 </description>
2509 </item>
2510
2511 <item>
2512 <title>Welcome to the world, Isenkram!</title>
2513 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
2514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
2515 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
2516 <description>&lt;p&gt;Yesterday, I
2517 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
2518 for testers&lt;/a&gt; for my prototype for making Debian better at handling
2519 pluggable hardware devices, which I
2520 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
2521 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
2522 up, and caused me to really want to to open up the development to more
2523 people. But before I did this, I want to come up with a sensible name
2524 for this project. Today I finally decided on a new name, and I have
2525 renamed the project from hw-support-handler to this new name. In the
2526 process, I moved the source to git and made it available as a
2527 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
2528 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
2529 To fetch and build the latest version of the source, use&lt;/p&gt;
2530
2531 &lt;pre&gt;
2532 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
2533 cd isenkram &amp;&amp; git-buildpackage -us -uc
2534 &lt;/pre&gt;
2535
2536 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
2537 want to hack on the source or improve the package, please go ahead.
2538 But please talk to me first on IRC or via email before you do major
2539 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
2540
2541 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
2542 stuff, typically meaning tools, nails, screws, etc. Typical hardware
2543 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
2544 the German word eisenkram, for those that are familiar with that
2545 word.&lt;/p&gt;
2546
2547 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
2548 instructions, to avoid confusing people with an error from the signing
2549 process.&lt;/p&gt;
2550
2551 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
2552 clone argument to avoid the need for authentication.&lt;/p&gt;
2553 </description>
2554 </item>
2555
2556 <item>
2557 <title>First prototype ready making hardware easier to use in Debian</title>
2558 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
2559 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
2560 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
2561 <description>&lt;p&gt;Early this month I set out to try to
2562 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
2563 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
2564 prototype is working, and it is ready for a larger audience. To test
2565 it, fetch the
2566 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
2567 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
2568 package. You might have to log out and in again activate the
2569 autostart script.&lt;/p&gt;
2570
2571 &lt;p&gt;The design is simple:&lt;/p&gt;
2572
2573 &lt;ul&gt;
2574
2575 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
2576 hw-support-handlerd to start when the user log in.&lt;/li&gt;
2577
2578 &lt;li&gt;This program listen for kernel events about new hardware (directly
2579 from the kernel like udev does), not using HAL dbus events as I
2580 initially did.&lt;/li&gt;
2581
2582 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
2583 the APT database, a database
2584 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
2585 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
2586
2587 &lt;li&gt;If a package is mapped to the hardware in question, the package
2588 isn&#39;t installed yet and this is the first time the hardware was
2589 plugged in, show a desktop notification suggesting to install the
2590 package or packages.&lt;/li&gt;
2591
2592 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
2593 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
2594
2595 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
2596 package while showing progress information in a window.&lt;/li&gt;
2597
2598 &lt;/ul&gt;
2599
2600 &lt;p&gt;I still need to come up with a better name for the system. Here
2601 are some screen shots showing the prototype in action. First the
2602 notification, then the password request, and finally the request to
2603 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
2604
2605 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
2606 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
2607 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
2608 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
2609 &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;
2610
2611 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
2612 is already useful. The database of hardware to package mappings also
2613 need more work. It is currently compatible with the Ubuntu way of
2614 storing such information in the package control file, but could be
2615 changed to use other formats instead or in addition to the current
2616 method. I&#39;ve dropped the use of discover for this mapping, as the
2617 modalias approach is more flexible and easier to use on Linux as long
2618 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
2619
2620 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
2621 here is the command required to check out and build the source: Use
2622 &#39;&lt;tt&gt;svn checkout
2623 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
2624 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
2625 devscripts package.&lt;/p&gt;
2626
2627 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
2628 renamed to Isenkram and the source moved from the Debian Edu
2629 subversion repository to a Debian collab-maint git repository. See
2630 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
2631 instructions&lt;/a&gt; for details.&lt;/p&gt;
2632 </description>
2633 </item>
2634
2635 <item>
2636 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
2637 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
2638 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
2639 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
2640 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
2641 suddenly in bed. With a quiet whimper, it went completely quiet and
2642 black. The power button was no longer able to turn it on. It was a
2643 IBM Thinkpad X41, and the best laptop I ever had. Better than both
2644 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
2645 Compaq I had before that. Now I need to find a replacement. To keep
2646 going during Christmas, I moved the one year old SSD disk to my old
2647 X40 where it fitted (only one I had left that could use it), but it is
2648 not a durable solution.
2649
2650 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
2651 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
2652
2653 &lt;ul&gt;
2654
2655 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
2656 than A4).&lt;/li&gt;
2657 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
2658 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
2659 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
2660 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
2661 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
2662 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
2663 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
2664 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
2665 size).&lt;/li&gt;
2666 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
2667 X.org packages.&lt;/li&gt;
2668 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
2669 the time).
2670
2671 &lt;/ul&gt;
2672
2673 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
2674 list. The reason is simply that the specifications on laptops the
2675 last 10-15 years have been sufficient for my needs, and I have to look
2676 at other features to choose my laptop. But are there still made as
2677 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
2678 robust, and Thinkpads seem to be heading in the wrong direction since
2679 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
2680 still be useful.&lt;/p&gt;
2681
2682 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
2683 external keyboard? I&#39;ll have to check the
2684 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
2685 well-supported laptops, or perhaps just buy one preinstalled from one
2686 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
2687 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
2688 </description>
2689 </item>
2690
2691 <item>
2692 <title>How to find a browser plugin supporting a given MIME type</title>
2693 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
2694 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
2695 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
2696 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
2697 install to get support for a given MIME type. Thanks to
2698 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
2699 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
2700 Unfortunately, not very many packages provide the needed meta
2701 information, Anyway, here is a small script to look up all browser
2702 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
2703
2704 &lt;pre&gt;
2705 #!/usr/bin/python
2706 import sys
2707 import apt
2708 def pkgs_handling_mimetype(mimetype):
2709 cache = apt.Cache()
2710 cache.open(None)
2711 thepkgs = []
2712 for pkg in cache:
2713 version = pkg.candidate
2714 if version is None:
2715 version = pkg.installed
2716 if version is None:
2717 continue
2718 record = version.record
2719 if not record.has_key(&#39;Npp-MimeType&#39;):
2720 continue
2721 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
2722 for t in mime_types:
2723 t = t.rstrip().strip()
2724 if t == mimetype:
2725 thepkgs.append(pkg.name)
2726 return thepkgs
2727 mimetype = &quot;audio/ogg&quot;
2728 if 1 &lt; len(sys.argv):
2729 mimetype = sys.argv[1]
2730 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
2731 for pkg in pkgs_handling_mimetype(mimetype):
2732 print &quot; %s&quot; %pkg
2733 &lt;/pre&gt;
2734
2735 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
2736
2737 &lt;pre&gt;
2738 % ./apt-find-browserplug-for-mimetype
2739 Browser plugin packages supporting audio/ogg:
2740 gecko-mediaplayer
2741 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
2742 Browser plugin packages supporting application/x-shockwave-flash:
2743 browser-plugin-gnash
2744 %
2745 &lt;/pre&gt;
2746
2747 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
2748 itself to query for plugins and propose to install the needed
2749 packages. It would be great if Debian supported such feature too. Is
2750 anyone working on adding it?&lt;/p&gt;
2751
2752 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
2753 request for icweasel support for this feature is
2754 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
2755 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
2756 of manpower and wish for a different design is the reason thus feature
2757 is not yet in iceweasel from Debian.&lt;/p&gt;
2758 </description>
2759 </item>
2760
2761 <item>
2762 <title>What is the most supported MIME type in Debian?</title>
2763 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
2764 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
2765 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
2766 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
2767 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
2768 proposal to make it possible for a Desktop application to propose to
2769 the user some package to install to gain support for a given MIME
2770 type, font, library etc. that is currently missing. With such
2771 mechanism in place, it would be possible for the desktop to
2772 automatically propose and install leocad if some LDraw file is
2773 downloaded by the browser.&lt;/p&gt;
2774
2775 &lt;p&gt;To get some idea about the current content of the archive, I decided
2776 to write a simple program to extract all .desktop files from the
2777 Debian archive and look up the claimed MIME support there. The result
2778 can be found on the
2779 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
2780 site&lt;/a&gt;. Using the collected information, it become possible to
2781 answer the question in the title. Here are the 20 most supported MIME
2782 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
2783 The complete list is available from the link above.&lt;/p&gt;
2784
2785 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
2786
2787 &lt;pre&gt;
2788 count MIME type
2789 ----- -----------------------
2790 32 text/plain
2791 30 audio/mpeg
2792 29 image/png
2793 28 image/jpeg
2794 27 application/ogg
2795 26 audio/x-mp3
2796 25 image/tiff
2797 25 image/gif
2798 22 image/bmp
2799 22 audio/x-wav
2800 20 audio/x-flac
2801 19 audio/x-mpegurl
2802 18 video/x-ms-asf
2803 18 audio/x-musepack
2804 18 audio/x-mpeg
2805 18 application/x-ogg
2806 17 video/mpeg
2807 17 audio/x-scpls
2808 17 audio/ogg
2809 16 video/x-ms-wmv
2810 &lt;/pre&gt;
2811
2812 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
2813
2814 &lt;pre&gt;
2815 count MIME type
2816 ----- -----------------------
2817 33 text/plain
2818 32 image/png
2819 32 image/jpeg
2820 29 audio/mpeg
2821 27 image/gif
2822 26 image/tiff
2823 26 application/ogg
2824 25 audio/x-mp3
2825 22 image/bmp
2826 21 audio/x-wav
2827 19 audio/x-mpegurl
2828 19 audio/x-mpeg
2829 18 video/mpeg
2830 18 audio/x-scpls
2831 18 audio/x-flac
2832 18 application/x-ogg
2833 17 video/x-ms-asf
2834 17 text/html
2835 17 audio/x-musepack
2836 16 image/x-xbitmap
2837 &lt;/pre&gt;
2838
2839 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
2840
2841 &lt;pre&gt;
2842 count MIME type
2843 ----- -----------------------
2844 31 text/plain
2845 31 image/png
2846 31 image/jpeg
2847 29 audio/mpeg
2848 28 application/ogg
2849 27 image/gif
2850 26 image/tiff
2851 26 audio/x-mp3
2852 23 audio/x-wav
2853 22 image/bmp
2854 21 audio/x-flac
2855 20 audio/x-mpegurl
2856 19 audio/x-mpeg
2857 18 video/x-ms-asf
2858 18 video/mpeg
2859 18 audio/x-scpls
2860 18 application/x-ogg
2861 17 audio/x-musepack
2862 16 video/x-ms-wmv
2863 16 video/x-msvideo
2864 &lt;/pre&gt;
2865
2866 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
2867 information mentioned in DEP-11. I have not yet had time to look at
2868 it, but hope the PackageKit people in Debian are on top of these
2869 issues.&lt;/p&gt;
2870
2871 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
2872 discovering a typo in my script.&lt;/p&gt;
2873 </description>
2874 </item>
2875
2876 <item>
2877 <title>Using modalias info to find packages handling my hardware</title>
2878 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
2879 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
2880 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
2881 <description>&lt;p&gt;Yesterday, I wrote about the
2882 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
2883 values provided by the Linux kernel&lt;/a&gt; following my hope for
2884 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
2885 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
2886 modalias values attached to package names can be used to map packages
2887 to hardware. This allow the system to look up and suggest relevant
2888 packages when I plug in some new hardware into my machine, and replace
2889 discover and discover-data as the database used to map hardware to
2890 packages.&lt;/p&gt;
2891
2892 &lt;p&gt;I create a modaliases file with entries like the following,
2893 containing package name, kernel module name (if relevant, otherwise
2894 the package name) and globs matching the relevant hardware
2895 modalias.&lt;/p&gt;
2896
2897 &lt;p&gt;&lt;blockquote&gt;
2898 Package: package-name
2899 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
2900 &lt;/blockquote&gt;&lt;/p&gt;
2901
2902 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
2903 for a given modalias value using this file.&lt;/p&gt;
2904
2905 &lt;p&gt;An entry like this would suggest the video and picture application
2906 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
2907
2908 &lt;p&gt;&lt;blockquote&gt;
2909 Package: cheese
2910 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
2911 &lt;/blockquote&gt;&lt;/p&gt;
2912
2913 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
2914 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
2915
2916 &lt;p&gt;&lt;blockquote&gt;
2917 Package: pcmciautils
2918 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
2919 &lt;/blockquote&gt;&lt;/p&gt;
2920
2921 &lt;p&gt;An entry like this would suggest the package colorhug-client when
2922 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
2923
2924 &lt;p&gt;&lt;blockquote&gt;
2925 Package: colorhug-client
2926 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
2927 &lt;/blockquote&gt;&lt;/p&gt;
2928
2929 &lt;p&gt;I believe the format is compatible with the format of the Packages
2930 file in the Debian archive. Ubuntu already uses their Packages file
2931 to store their mappings from packages to hardware.&lt;/p&gt;
2932
2933 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
2934 announce the hardware it support in a way my prototype understand.
2935 This allow those publishing packages in an APT source outside the
2936 Debian archive as well as those backporting packages to make sure the
2937 hardware mapping are included in the package meta information. I&#39;ve
2938 tested such header in the pymissile package, and its modalias mapping
2939 is working as it should with my prototype. It even made it to Ubuntu
2940 Raring.&lt;/p&gt;
2941
2942 &lt;p&gt;To test if it was possible to look up supported hardware using only
2943 the shell tools available in the Debian installer, I wrote a shell
2944 implementation of the lookup code. The idea is to create files for
2945 each modalias and let the shell do the matching. Please check out and
2946 try the
2947 &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;
2948 shell script. It run without any extra dependencies and fetch the
2949 hardware mappings from the Debian archive and the subversion
2950 repository where I currently work on my prototype.&lt;/p&gt;
2951
2952 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
2953 install yubikey-personalization:&lt;/p&gt;
2954
2955 &lt;p&gt;&lt;blockquote&gt;
2956 % ./hw-support-lookup
2957 &lt;br&gt;yubikey-personalization
2958 &lt;br&gt;%
2959 &lt;/blockquote&gt;&lt;/p&gt;
2960
2961 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
2962 propose to install the pcmciautils package:&lt;/p&gt;
2963
2964 &lt;p&gt;&lt;blockquote&gt;
2965 % ./hw-support-lookup
2966 &lt;br&gt;pcmciautils
2967 &lt;br&gt;%
2968 &lt;/blockquote&gt;&lt;/p&gt;
2969
2970 &lt;p&gt;If you know of any hardware-package mapping that should be added to
2971 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
2972 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
2973
2974 &lt;p&gt;It could be possible to generate several of the mappings between
2975 packages and hardware. One source would be to look at packages with
2976 kernel modules, ie packages with *.ko files in /lib/modules/, and
2977 extract their modalias information. Another would be to look at
2978 packages with udev rules, ie packages with files in
2979 /lib/udev/rules.d/, and extract their vendor/model information to
2980 generate a modalias matching rule. I have not tested any of these to
2981 see if it work.&lt;/p&gt;
2982
2983 &lt;p&gt;If you want to help implementing a system to let us propose what
2984 packages to install when new hardware is plugged into a Debian
2985 machine, please send me an email or talk to me on
2986 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
2987 </description>
2988 </item>
2989
2990 <item>
2991 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
2992 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
2993 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
2994 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
2995 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
2996 information, to find the packages that support a given piece of
2997 hardware, I refreshed my memory regarding modalias values, and decided
2998 to document the details. Here are my findings so far, also available
2999 in
3000 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3001 Debian Edu subversion repository&lt;/a&gt;:
3002
3003 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
3004
3005 &lt;p&gt;This document try to explain what the different types of modalias
3006 values stands for. It is in part based on information from
3007 &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;,
3008 &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;,
3009 &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
3010 &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;.
3011
3012 &lt;p&gt;The modalias entries for a given Linux machine can be found using
3013 this shell script:&lt;/p&gt;
3014
3015 &lt;pre&gt;
3016 find /sys -name modalias -print0 | xargs -0 cat | sort -u
3017 &lt;/pre&gt;
3018
3019 &lt;p&gt;The supported modalias globs for a given kernel module can be found
3020 using modinfo:&lt;/p&gt;
3021
3022 &lt;pre&gt;
3023 % /sbin/modinfo psmouse | grep alias:
3024 alias: serio:ty05pr*id*ex*
3025 alias: serio:ty01pr*id*ex*
3026 %
3027 &lt;/pre&gt;
3028
3029 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
3030
3031 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
3032 Bridge memory controller:&lt;/p&gt;
3033
3034 &lt;p&gt;&lt;blockquote&gt;
3035 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
3036 &lt;/blockquote&gt;&lt;/p&gt;
3037
3038 &lt;p&gt;This represent these values:&lt;/p&gt;
3039
3040 &lt;pre&gt;
3041 v 00008086 (vendor)
3042 d 00002770 (device)
3043 sv 00001028 (subvendor)
3044 sd 000001AD (subdevice)
3045 bc 06 (bus class)
3046 sc 00 (bus subclass)
3047 i 00 (interface)
3048 &lt;/pre&gt;
3049
3050 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
3051 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
3052 0600. The 0600 class is a host bridge. Other useful bus values are
3053 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
3054
3055 &lt;p&gt;Not sure how to figure out the interface value, nor what it
3056 means.&lt;/p&gt;
3057
3058 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
3059
3060 &lt;p&gt;Some typical USB entries can look like this. This is an internal
3061 USB hub in a laptop:&lt;/p&gt;
3062
3063 &lt;p&gt;&lt;blockquote&gt;
3064 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
3065 &lt;/blockquote&gt;&lt;/p&gt;
3066
3067 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
3068
3069 &lt;pre&gt;
3070 v 1D6B (device vendor)
3071 p 0001 (device product)
3072 d 0206 (bcddevice)
3073 dc 09 (device class)
3074 dsc 00 (device subclass)
3075 dp 00 (device protocol)
3076 ic 09 (interface class)
3077 isc 00 (interface subclass)
3078 ip 00 (interface protocol)
3079 &lt;/pre&gt;
3080
3081 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
3082 class is in the interface class section. For a simple USB web camera,
3083 these alias entries show up:&lt;/p&gt;
3084
3085 &lt;p&gt;&lt;blockquote&gt;
3086 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
3087 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
3088 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
3089 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
3090 &lt;/blockquote&gt;&lt;/p&gt;
3091
3092 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
3093 camera), 0101 is audio control device and 0102 is audio streaming (aka
3094 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
3095
3096 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
3097
3098 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
3099 receiver in a Thinkpad X40:&lt;/p&gt;
3100
3101 &lt;p&gt;&lt;blockquote&gt;
3102 acpi:IBM0071:PNP0511:
3103 &lt;/blockquote&gt;&lt;/p&gt;
3104
3105 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
3106
3107 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
3108
3109 &lt;p&gt;The DMI table contain lots of information about the computer case
3110 and model. This is an entry for a IBM Thinkpad X40, fetched from
3111 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
3112
3113 &lt;p&gt;&lt;blockquote&gt;
3114 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
3115 &lt;/blockquote&gt;&lt;/p&gt;
3116
3117 &lt;p&gt;The values present are&lt;/p&gt;
3118
3119 &lt;pre&gt;
3120 bvn IBM (BIOS vendor)
3121 bvr 1UETB6WW(1.66) (BIOS version)
3122 bd 06/15/2005 (BIOS date)
3123 svn IBM (system vendor)
3124 pn 2371H4G (product name)
3125 pvr ThinkPadX40 (product version)
3126 rvn IBM (board vendor)
3127 rn 2371H4G (board name)
3128 rvr NotAvailable (board version)
3129 cvn IBM (chassis vendor)
3130 ct 10 (chassis type)
3131 cvr NotAvailable (chassis version)
3132 &lt;/pre&gt;
3133
3134 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
3135 found in the dmidecode source:&lt;/p&gt;
3136
3137 &lt;pre&gt;
3138 3 Desktop
3139 4 Low Profile Desktop
3140 5 Pizza Box
3141 6 Mini Tower
3142 7 Tower
3143 8 Portable
3144 9 Laptop
3145 10 Notebook
3146 11 Hand Held
3147 12 Docking Station
3148 13 All In One
3149 14 Sub Notebook
3150 15 Space-saving
3151 16 Lunch Box
3152 17 Main Server Chassis
3153 18 Expansion Chassis
3154 19 Sub Chassis
3155 20 Bus Expansion Chassis
3156 21 Peripheral Chassis
3157 22 RAID Chassis
3158 23 Rack Mount Chassis
3159 24 Sealed-case PC
3160 25 Multi-system
3161 26 CompactPCI
3162 27 AdvancedTCA
3163 28 Blade
3164 29 Blade Enclosing
3165 &lt;/pre&gt;
3166
3167 &lt;p&gt;The chassis type values are not always accurately set in the DMI
3168 table. For example my home server is a tower, but the DMI modalias
3169 claim it is a desktop.&lt;/p&gt;
3170
3171 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
3172
3173 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
3174 test machine:&lt;/p&gt;
3175
3176 &lt;p&gt;&lt;blockquote&gt;
3177 serio:ty01pr00id00ex00
3178 &lt;/blockquote&gt;&lt;/p&gt;
3179
3180 &lt;p&gt;The values present are&lt;/p&gt;
3181
3182 &lt;pre&gt;
3183 ty 01 (type)
3184 pr 00 (prototype)
3185 id 00 (id)
3186 ex 00 (extra)
3187 &lt;/pre&gt;
3188
3189 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
3190 the valid values are.&lt;/p&gt;
3191
3192 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
3193
3194 &lt;p&gt;There are heaps of other modalias subtypes according to
3195 file2alias.c. There is the rest of the list from that source: amba,
3196 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
3197 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
3198 vmbus, x86cpu and zorro. I did not spend time documenting all of
3199 these, as they do not seem relevant for my intended use with mapping
3200 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
3201
3202 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
3203
3204 &lt;p&gt;To check which kernel modules provide support for a given modalias,
3205 one can use the following shell script:&lt;/p&gt;
3206
3207 &lt;pre&gt;
3208 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
3209 echo &quot;$id&quot; ; \
3210 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
3211 done
3212 &lt;/pre&gt;
3213
3214 &lt;p&gt;The output can look like this (only the first few entries as the
3215 list is very long on my test machine):&lt;/p&gt;
3216
3217 &lt;pre&gt;
3218 acpi:ACPI0003:
3219 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
3220 acpi:device:
3221 FATAL: Module acpi:device: not found.
3222 acpi:IBM0068:
3223 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
3224 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
3225 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
3226 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
3227 acpi:IBM0071:PNP0511:
3228 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
3229 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
3230 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
3231 [...]
3232 &lt;/pre&gt;
3233
3234 &lt;p&gt;If you want to help implementing a system to let us propose what
3235 packages to install when new hardware is plugged into a Debian
3236 machine, please send me an email or talk to me on
3237 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
3238
3239 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
3240 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
3241 in /sys/ with space in them.&lt;/p&gt;
3242 </description>
3243 </item>
3244
3245 <item>
3246 <title>Moved the pymissile Debian packaging to collab-maint</title>
3247 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
3248 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
3249 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
3250 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
3251 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
3252 Launcher and updated the Debian package
3253 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
3254 sure udev will fix the device permissions when it is plugged in. I
3255 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
3256 hopefully make the package be proposed by jockey in Ubuntu when a user
3257 plug in his rocket launcher. In the process I moved the source to a
3258 git repository under collab-maint, to make it easier for any DD to
3259 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
3260 is not very active, but the software still work for me even after five
3261 years of relative silence. The new git repository is not listed in
3262 the uploaded package yet, because I want to test the other changes a
3263 bit more before I upload the new version. If you want to check out
3264 the new version with a .desktop file included, visit the
3265 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
3266 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
3267 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
3268 </description>
3269 </item>
3270
3271 <item>
3272 <title>Lets make hardware dongles easier to use in Debian</title>
3273 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
3274 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
3275 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
3276 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
3277 general, is that there is a great package management system with the
3278 ability to automatically install software packages by downloading them
3279 from the distribution mirrors, but no way to get it to automatically
3280 install the packages I need to use the hardware I plug into my
3281 machine. Even if the package to use it is easily available from the
3282 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
3283 suggest to automatically install the python-nxt, nbc and t2n packages
3284 I need to talk to it. When I plug in a Yubikey, it could propose the
3285 yubikey-personalization package. The information required to do this
3286 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
3287
3288 &lt;p&gt;Some years ago, I proposed to
3289 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
3290 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
3291 simple:
3292
3293 &lt;ul&gt;
3294
3295 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
3296 starting when a user log in.&lt;/li&gt;
3297
3298 &lt;li&gt;Set this program up to listen for kernel events emitted when new
3299 hardware is inserted into the computer.&lt;/li&gt;
3300
3301 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
3302 database mapping to packages, and take note of any non-installed
3303 packages.&lt;/li&gt;
3304
3305 &lt;li&gt;Show a message to the user proposing to install the discovered
3306 package, and make it easy to install it.&lt;/li&gt;
3307
3308 &lt;/ul&gt;
3309
3310 &lt;p&gt;I am not sure what the best way to implement this is, but my
3311 initial idea was to use dbus events to discover new hardware, the
3312 discover database to find packages and
3313 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
3314 packages.&lt;/p&gt;
3315
3316 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
3317 draft package is now checked into
3318 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
3319 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
3320 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
3321 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
3322 the relevant packages in Debian, and uploaded a new version
3323 2.2013.01.09 to unstable. I also discovered that the current
3324 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
3325 package in Debian no longer discovered any USB devices, because
3326 /proc/bus/usb/devices is no longer present. I ported it to use
3327 libusb as a fall back option to get it working. The fixed package
3328 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
3329 because of the freeze).&lt;/p&gt;
3330
3331 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
3332 desktop notification to show up (only once, the first time it is
3333 inserted):&lt;/p&gt;
3334
3335 &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;
3336
3337 &lt;p&gt;For this prototype to be really useful, some way to automatically
3338 install the proposed packages by pressing the &quot;Please install
3339 program(s)&quot; button should to be implemented.&lt;/p&gt;
3340
3341 &lt;p&gt;If this idea seem useful to you, and you want to help make it
3342 happen, please help me update the discover-data database with mappings
3343 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
3344 list the package you would like to have installed when a given
3345 hardware device is inserted into your computer, and report bugs using
3346 reportbug if it isn&#39;t. Or, if you know of a better way to provide
3347 such mapping, please let me know.&lt;/p&gt;
3348
3349 &lt;p&gt;This prototype need more work, and there are several questions that
3350 should be considered before it is ready for production use. Is dbus
3351 the correct way to detect new hardware? At the moment I look for HAL
3352 dbus events on the system bus, because that is the events I could see
3353 on my Debian Squeeze KDE desktop. Are there better events to use?
3354 How should the user be notified? Is the desktop notification
3355 mechanism the best option, or should the background daemon raise a
3356 popup instead? How should packages be installed? When should they
3357 not be installed?&lt;/p&gt;
3358
3359 &lt;p&gt;If you want to help getting such feature implemented in Debian,
3360 please send me an email. :)&lt;/p&gt;
3361 </description>
3362 </item>
3363
3364 <item>
3365 <title>New IRC channel for LEGO designers using Debian</title>
3366 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
3367 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
3368 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
3369 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
3370 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
3371 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
3372 discovered I had to build all the tools myself because none were
3373 already in Debian Squeeze. If Debian support for LEGO is something
3374 you care about, please join me on the IRC channel
3375 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
3376 irc.debian.org). There is a lot that could be done to improve the
3377 Debian support for LEGO designers. For example both CAD software
3378 and Mindstorm compilers are missing. :)&lt;/p&gt;
3379
3380 &lt;p&gt;Update 2012-01-03: A
3381 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
3382 including links to Lego related packages is now available.&lt;/p&gt;
3383 </description>
3384 </item>
3385
3386 <item>
3387 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
3388 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
3389 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
3390 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
3391 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
3392 year! I hope next year will prove to be a good year.&lt;/p&gt;
3393
3394 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
3395 decentralised &quot;currency&quot; that allow people to transfer bitcoins
3396 between each other with minimal overhead, is a very interesting
3397 experiment. And as I wrote a few days ago, the bitcoin situation in
3398 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
3399 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
3400 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
3401 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
3402 for one of the ftpmasters to approve the new bitcoin-qt package
3403 name.&lt;/p&gt;
3404
3405 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
3406 team in Debian, you can easily test the package in Debian Squeeze
3407 using the following steps to get a set of working packages:&lt;/p&gt;
3408
3409 &lt;blockquote&gt;&lt;pre&gt;
3410 git clone git://git.debian.org/git/collab-maint/bitcoin
3411 cd bitcoin
3412 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
3413 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
3414 &lt;/pre&gt;&lt;/blockquote&gt;
3415
3416 &lt;p&gt;You might have to install some build dependencies as well. The
3417 list of commands should give you two packages, bitcoind and
3418 bitcoin-qt, ready for use in a Squeeze environment. Note that the
3419 client will download the complete set of bitcoin &quot;blocks&quot;, which need
3420 around 5.6 GiB of data on my machine at the moment. Make sure your
3421 ~/.bitcoin/ directory have lots of spare room if you want to download
3422 all the blocks. The client will warn if the disk is getting full, so
3423 there is not really a problem if you got too little room, but you will
3424 not be able to get all the features out of the client.&lt;/p&gt;
3425
3426 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
3427 activities, please send Bitcoin donations to my address
3428 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3429 </description>
3430 </item>
3431
3432 <item>
3433 <title>A word on bitcoin support in Debian</title>
3434 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
3435 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
3436 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
3437 <description>&lt;p&gt;It has been a while since I wrote about
3438 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
3439 peer-to-peer based crypto-currency, and the reason is simply that I
3440 have been busy elsewhere. But two days ago, I started looking at the
3441 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
3442 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
3443 is now maintained by a
3444 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
3445 people&lt;/a&gt;, and the grunt work had already been done by this team. We
3446 owe a huge thank you to all these team members. :)
3447 But I was sad to discover that the bitcoin client is missing in
3448 Wheezy. It is only available in Sid (and an outdated client from
3449 backports). The client had several RC bugs registered in BTS blocking
3450 it from entering testing. To try to help the team and improve the
3451 situation, I spent some time providing patches and triaging the bug
3452 reports. I also had a look at the bitcoin package available from Matt
3453 Corallo in a
3454 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
3455 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
3456 Debian package.&lt;/p&gt;
3457
3458 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
3459 IRC, I pushed several patches into the collab-maint git repository to
3460 improve the package. It now contains fixes for the RC issues (not from
3461 me, but fixed by Scott Howard), build rules for a Qt GUI client
3462 package, konqueror support for the bitcoin: URI and bash completion
3463 setup. As I work on Debian Squeeze, I also created
3464 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
3465 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
3466 it and try to integrate it into the git repository before uploading a
3467 new version to unstable.
3468
3469 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
3470 centralized control currently exercised in the monetary system. I
3471 find it completely unacceptable that the USA government is collecting
3472 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
3473 that the major credit card companies can block legal money
3474 transactions to Wikileaks. But for bitcoin to succeed, more people
3475 need to use bitcoins, and more people need to accept bitcoins when
3476 they sell products and services. Improving the bitcoin support in
3477 Debian is a small step in the right direction, but not enough.
3478 Unfortunately the user experience when browsing the web and wanting to
3479 pay with bitcoin is still not very good. The bitcoin: URI is a step
3480 in the right direction, but need to work in most or every browser in
3481 use. Also the bitcoin-qt client is too heavy to fire up to do a
3482 quick transaction. I believe there are other clients available, but
3483 have not tested them.&lt;/p&gt;
3484
3485 &lt;p&gt;My
3486 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
3487 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
3488 I received 20.15 BTC so far on the address I provided in my blog two
3489 years ago, as can be
3490 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
3491 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
3492 donation. The blockexplorer service demonstrates quite well that
3493 bitcoin is not quite anonymous and untracked. :) I wonder if the
3494 number of users have gone up since then. If you use bitcoin and want
3495 to show your support of my activity, please send Bitcoin donations to
3496 the same address as last time,
3497 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3498 </description>
3499 </item>
3500
3501 <item>
3502 <title>Git repository for song book for Computer Scientists</title>
3503 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
3504 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
3505 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
3506 <description>&lt;p&gt;As I
3507 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
3508 this summer&lt;/a&gt;, I have created a Computer Science song book a few
3509 years ago, and today I finally found time to create a public
3510 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
3511 repository for the project&lt;/a&gt;.&lt;/p&gt;
3512
3513 &lt;p&gt;If you want to help out, please clone the source and submit patches
3514 to the HTML version. To generate the PDF and PostScript version,
3515 please use prince XML, or let me know about a useful free software
3516 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
3517
3518 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
3519 PostScript formats at
3520 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
3521 Science Songbook&lt;/a&gt;.&lt;/p&gt;
3522 </description>
3523 </item>
3524
3525 <item>
3526 <title>Gratulerer med 19-årsdagen, Debian!</title>
3527 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
3528 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
3529 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
3530 <description>&lt;p&gt;I dag fyller
3531 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
3532 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
3533 si gratulerer med dagen, Debian!&lt;/p&gt;
3534 </description>
3535 </item>
3536
3537 <item>
3538 <title>Song book for Computer Scientists</title>
3539 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
3540 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
3541 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
3542 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
3543 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
3544 collecting computer related songs for use at parties. The original
3545 version was written in LaTeX, but a few years ago I got help from
3546 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
3547 while keeping the ability to create a nice book in PDF format. I have
3548 not had time to maintain the book for a while now, and guess I should
3549 put it up on some public version control repository where others can
3550 help me extend and update the book. If anyone is volunteering to help
3551 me with this, send me an email. Also let me know if there are songs
3552 missing in my book.&lt;/p&gt;
3553
3554 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
3555 me today that I really should let all my readers share the joys of
3556 singing out load about programming, computers and computer networks.
3557 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
3558 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
3559 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
3560 Computer Science Songbook&lt;/a&gt;.
3561 </description>
3562 </item>
3563
3564 <item>
3565 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
3566 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
3567 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
3568 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
3569 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
3570 around 1000 at the moment. To be able to get help from the vendors
3571 when something go wrong, we want to keep the firmware on the servers
3572 up to date. If the firmware isn&#39;t the latest and greatest, the
3573 vendors typically refuse to start debugging any problems until the
3574 firmware is upgraded. So before every reboot, we want to upgrade the
3575 firmware, and we would really like everyone handling servers at the
3576 university to do this themselves when they plan to reboot a machine.
3577 For that to happen we at the unix server admin group need to provide
3578 the tools to do so.&lt;/p&gt;
3579
3580 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
3581 fetch and install the latest firmware for the servers we got. Most of
3582 our hardware are from Dell and HP, so I have focused on these servers
3583 so far. This blog post is about the Dell part.&lt;/P&gt;
3584
3585 &lt;p&gt;On the Dell FTP site I was lucky enough to find
3586 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
3587 with firmware information for all 11th generation servers, listing
3588 which firmware should be used on a given model and where on the FTP
3589 site I can find it. Using a simple perl XML parser I can then
3590 download the shell scripts Dell provides to do firmware upgrades from
3591 within Linux and reboot when all the firmware is primed and ready to
3592 be activated on the first reboot.&lt;/p&gt;
3593
3594 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
3595 Are there anyone working on similar tools for firmware upgrading all
3596 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
3597
3598 &lt;p&gt;&lt;pre&gt;
3599 #!/usr/bin/perl
3600 use strict;
3601 use warnings;
3602 use File::Temp qw(tempdir);
3603 BEGIN {
3604 # Install needed RHEL packages if missing
3605 my %rhelmodules = (
3606 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
3607 );
3608 for my $module (keys %rhelmodules) {
3609 eval &quot;use $module;&quot;;
3610 if ($@) {
3611 my $pkg = $rhelmodules{$module};
3612 system(&quot;yum install -y $pkg&quot;);
3613 eval &quot;use $module;&quot;;
3614 }
3615 }
3616 }
3617 my $errorsto = &#39;pere@hungry.com&#39;;
3618
3619 upgrade_dell();
3620
3621 exit 0;
3622
3623 sub run_firmware_script {
3624 my ($opts, $script) = @_;
3625 unless ($script) {
3626 print STDERR &quot;fail: missing script name\n&quot;;
3627 exit 1
3628 }
3629 print STDERR &quot;Running $script\n\n&quot;;
3630
3631 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
3632 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
3633 } else {
3634 print STDERR &quot;fail: firmware script returned error\n&quot;;
3635 }
3636 }
3637
3638 sub run_firmware_scripts {
3639 my ($opts, @dirs) = @_;
3640 # Run firmware packages
3641 for my $dir (@dirs) {
3642 print STDERR &quot;info: Running scripts in $dir\n&quot;;
3643 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
3644 while (my $s = readdir $dh) {
3645 next if $s =~ m/^\.\.?/;
3646 run_firmware_script($opts, &quot;$dir/$s&quot;);
3647 }
3648 closedir $dh;
3649 }
3650 }
3651
3652 sub download {
3653 my $url = shift;
3654 print STDERR &quot;info: Downloading $url\n&quot;;
3655 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
3656 }
3657
3658 sub upgrade_dell {
3659 my @dirs;
3660 my $product = `dmidecode -s system-product-name`;
3661 chomp $product;
3662
3663 if ($product =~ m/PowerEdge/) {
3664
3665 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
3666 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
3667
3668 my $tmpdir = tempdir(
3669 CLEANUP =&gt; 1
3670 );
3671 chdir($tmpdir);
3672 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
3673 system(&#39;gunzip Catalog.xml.gz&#39;);
3674 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
3675 # -q is quiet, disabling interactivity and reducing console output
3676 my $fwopts = &quot;-q&quot;;
3677 if (@paths) {
3678 for my $url (@paths) {
3679 fetch_dell_fw($url);
3680 }
3681 run_firmware_scripts($fwopts, $tmpdir);
3682 } else {
3683 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3684 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3685 }
3686 chdir(&#39;/&#39;);
3687 } else {
3688 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
3689 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
3690 }
3691 }
3692
3693 sub fetch_dell_fw {
3694 my $path = shift;
3695 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
3696 download($url);
3697 }
3698
3699 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
3700 # firmware packages to download from Dell. Only work for Linux
3701 # machines and 11th generation Dell servers.
3702 sub fetch_dell_fw_list {
3703 my $filename = shift;
3704
3705 my $product = `dmidecode -s system-product-name`;
3706 chomp $product;
3707 my ($mybrand, $mymodel) = split(/\s+/, $product);
3708
3709 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
3710
3711 my $xml = XMLin($filename);
3712 my @paths;
3713 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
3714 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
3715 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
3716 my $oscode;
3717 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
3718 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
3719 } else {
3720 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
3721 }
3722 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
3723 {
3724 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
3725 }
3726 }
3727 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
3728 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
3729
3730 # Drop application packages, only firmware and BIOS
3731 next if &#39;APAC&#39; eq $componenttype;
3732
3733 my $cpath = $component-&gt;{path};
3734 for my $path (@paths) {
3735 if ($cpath =~ m%/$path$%) {
3736 push(@paths, $cpath);
3737 }
3738 }
3739 }
3740 return @paths;
3741 }
3742 &lt;/pre&gt;
3743
3744 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
3745 it could work on other platforms with some tweaking. Anyone know a
3746 index like Catalog.xml is available from HP for HP servers? At the
3747 moment I maintain a similar list manually and it is quickly getting
3748 outdated.&lt;/p&gt;
3749 </description>
3750 </item>
3751
3752 <item>
3753 <title>How is booting into runlevel 1 different from single user boots?</title>
3754 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
3755 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
3756 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
3757 <description>&lt;p&gt;Wouter Verhelst have some
3758 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
3759 comments and opinions&lt;/a&gt; on my blog post on
3760 &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
3761 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
3762 &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
3763 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
3764 small piece of his comment now, and though it best to address the
3765 misunderstanding he bring forward:&lt;/p&gt;
3766
3767 &lt;p&gt;&lt;blockquote&gt;
3768 Currently, a system admin has four options: [...] boot to a
3769 single-user system (by adding &#39;single&#39; to the kernel command line;
3770 this runs rcS and rc1 scripts)
3771 &lt;/blockquote&gt;&lt;/p&gt;
3772
3773 &lt;p&gt;This make me believe Wouter believe booting into single user mode
3774 and booting into runlevel 1 is the same. I am not surprised he
3775 believe this, because it would make sense and is a quite sensible
3776 thing to believe. But because the boot in Debian is slightly broken,
3777 runlevel 1 do not work properly and it isn&#39;t the same as single user
3778 mode. I&#39;ll try to explain what is actually happing, but it is a bit
3779 hard to explain.&lt;/p&gt;
3780
3781 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
3782 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
3783 executed in single user mode is sulogin. Single user mode is a boot
3784 state &quot;between&quot; the runlevels, and when booting into single user mode,
3785 only the scripts in /etc/rcS.d/ are executed before the init process
3786 enters the single user state. When switching to runlevel 1, the state
3787 is in fact not ending in runlevel 1, but it passes through runlevel 1
3788 and end up in the single user mode (see /etc/rc1.d/S03single, which
3789 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
3790 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
3791 mode enabled by /etc/rcS.d/ (which is more like the initial boot
3792 mode).&lt;/p&gt;
3793
3794 &lt;p&gt;This summary might make it clearer. When booting for the first
3795 time into single user mode, the following commands are executed:
3796 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
3797 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
3798 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
3799 trying to continue after visiting single user mode. Not all services
3800 are started again as they should, causing the machine to end up in an
3801 unpredicatble state. This is why Debian admins recommend rebooting
3802 after visiting single user mode.&lt;/p&gt;
3803
3804 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
3805 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
3806 to runlevel 1, the services started from /etc/rcS.d/ are not properly
3807 stopped when passing through the scripts in /etc/rc1.d/, and not
3808 started again when switching away from runlevel 1 to the runlevels
3809 2-5. I believe the problem is best fixed by moving all the scripts
3810 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
3811 functioning single user mode during boot.&lt;/p&gt;
3812
3813 &lt;p&gt;I have spent several years investigating the Debian boot system,
3814 and discovered this problem a few years ago. I suspect it originates
3815 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
3816 </description>
3817 </item>
3818
3819 <item>
3820 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
3821 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
3822 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
3823 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
3824 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
3825 are started from /etc/rcS.d/. In fact, there is a bite more of them
3826 than make sense, and this causes a few problems. What kind of
3827 problems, you might ask. There are at least two problems. The first
3828 is that it is not possible to recover a machine after switching to
3829 runlevel 1. One need to actually reboot to get the machine back to
3830 the expected state. The other is that single user boot will sometimes
3831 run into problems because some of the subsystems are activated before
3832 the root login is presented, causing problems when trying to recover a
3833 machine from a problem in that subsystem. A minor additional point is
3834 that moving more scripts out of rcS.d/ and into the other rc#.d/
3835 directories will increase the amount of scripts that can run in
3836 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
3837
3838 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
3839 scripts that _have_ to execute before the root login prompt is
3840 presented during a single user boot should go there. Everything else
3841 should go into the numeric runlevels. This means things like
3842 lm-sensors, fuse and x11-common should not run from rcS.d, but from
3843 the numeric runlevels. Today in Debian, there are around 115 init.d
3844 scripts that are started from rcS.d/, and most of them should be moved
3845 out. Do your package have one of them? Please help us make single
3846 user and runlevel 1 better by moving it.&lt;/p&gt;
3847
3848 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
3849 etc. should still be started from rcS.d/, but there is for example no
3850 need to have the network enabled before the single user login prompt
3851 is presented.&lt;/p&gt;
3852
3853 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
3854 Debian systems working while scripts migrate and during upgrades, the
3855 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
3856 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
3857 and the next ones can only be moved when their dependencies have been
3858 moved first. This migration must be done sequentially while we ensure
3859 that the package system upgrade packages in the right order to keep
3860 the system state correct. This will require some coordination when it
3861 comes to network related packages, but most of the packages with
3862 scripts that should migrate do not have anything in rcS.d/ depending
3863 on them. Some packages have already been updated, like the sudo
3864 package, while others are still left to do. I wish I had time to work
3865 on this myself, but real live constrains make it unlikely that I will
3866 find time to push this forward.&lt;/p&gt;
3867 </description>
3868 </item>
3869
3870 <item>
3871 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
3872 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
3873 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
3874 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
3875 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
3876 mentioned the issues I believe should be improved in Debian for its
3877 desktop to be useful for more people. The use case for this is my
3878 parents, which are currently running Kubuntu which solve the
3879 issues.&lt;/p&gt;
3880
3881 &lt;p&gt;I suspect these four missing features are not very hard to
3882 implement. After all, they are present in Ubuntu, so if we wanted to
3883 do this in Debian we would have a source.&lt;/p&gt;
3884
3885 &lt;ol&gt;
3886
3887 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
3888 are new packages available for upgrades, a icon in the KDE status bar
3889 indicate this, and clicking on it will activate the simple upgrade
3890 tool to handle it. I have no problem guiding both of my parents
3891 through the process over the phone. If a kernel reboot is required,
3892 this too is indicated by the status bars and the upgrade tool. Last
3893 time I checked, nothing with the same features was working in KDE in
3894 Debian.&lt;/li&gt;
3895
3896 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
3897 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
3898 currently have a handler for, it will ask the user if the system
3899 should search for a package that would add support for this MIME type,
3900 and if the user say yes, the APT sources will be searched for packages
3901 advertising the MIME type in their control file (visible in the
3902 Packages file in the APT archive). If one or more packages are found,
3903 it is a simple click of the mouse to add support for the missing mime
3904 type. If the package require the user to accept some non-free
3905 license, this is explained to the user. The entire process make it
3906 more clear to the user why something do not work in the browser, and
3907 make the chances higher for the user to blame the web page authors and
3908 not the browser for any missing features.&lt;/li&gt;
3909
3910 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
3911 handlers.&lt;/strong&gt; When the media players encounter a format or codec
3912 it is not supporting, a dialog pop up asking the user if the system
3913 should search for a package that would add support for it. This
3914 happen with things like MP3, Windows Media or H.264. The selection
3915 and installation procedure is very similar to the Firefox browser
3916 plugin handling. This is as far as I know implemented using a
3917 gstreamer hook. The end result is that the user easily get access to
3918 the codecs that are present from the APT archives available, while
3919 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
3920
3921 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
3922 displaying a text/plain file in my Debian browser, it will propose to
3923 start emacs to show it. If I remember correctly, when doing the same
3924 in Kunbutu it show the file as a text file in the browser. At least I
3925 know Opera will show text files within the browser. I much prefer the
3926 latter behaviour.&lt;/li&gt;
3927
3928 &lt;/ol&gt;
3929
3930 &lt;p&gt;There are other nice features as well, like the simplified suite
3931 upgrader, but given that I am the one mostly doing the dist-upgrade,
3932 it do not matter much.&lt;/p&gt;
3933
3934 &lt;p&gt;I really hope we could get these features in place for the next
3935 Debian release. It would require the coordinated effort of several
3936 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
3937 </description>
3938 </item>
3939
3940 <item>
3941 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
3942 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
3943 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
3944 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
3945 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
3946 site is build on Debian/Squeeze, and this platform was chosen because
3947 I am most familiar with Debian (being a Debian Developer for around 10
3948 years) because it is the latest stable Debian release which should get
3949 security support for a few years.&lt;/p&gt;
3950
3951 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
3952 that are missing in Debian at the moment. It would be great if these
3953 modules were added to the Debian archive, allowing anyone to set up
3954 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
3955 in their own country using only Debian packages. The list of modules
3956 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
3957 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
3958 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
3959 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
3960 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
3961 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
3962 easier in the future.&lt;/p&gt;
3963
3964 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
3965 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
3966 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
3967 with the responsibility of tracking security problems, which I really
3968 do not have time for.&lt;/p&gt;
3969 </description>
3970 </item>
3971
3972 <item>
3973 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
3974 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
3975 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
3976 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
3977 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
3978 posts have been in Norwegian the last few weeks, so here is a short
3979 update in English.&lt;/p&gt;
3980
3981 &lt;p&gt;The kids still keep me too busy to get much free software work
3982 done, but I did manage to organise a project to get a Norwegian port
3983 of the British service
3984 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
3985 and it has been running for a month now. The entire project has been
3986 organised by me and two others. Around Christmas we gathered sponsors
3987 to fund the development work. In January I drafted a contract with
3988 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
3989 and in February the development took place. Most of it involved
3990 converting the source to use GPS coordinates instead of British
3991 easting/northing, and the resulting code should be a lot easier to get
3992 running in any country by now. The Norwegian
3993 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
3994 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
3995 source and the source for administrative borders in Norway, and
3996 support for this had to be added/fixed.&lt;/p&gt;
3997
3998 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
3999 polishing the system before we announced it March 7th. The system is
4000 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
4001 problem reports in a few weeks. Soon we hope to announce the Android
4002 and iPhone versions making it even easier to report problems with the
4003 public infrastructure.&lt;/p&gt;
4004
4005 &lt;p&gt;Perhaps something to consider for those of you in countries without
4006 such service?&lt;/p&gt;
4007 </description>
4008 </item>
4009
4010 <item>
4011 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
4012 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
4013 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
4014 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
4015 <description>&lt;p&gt;The last few days I have looked at ways to track open security
4016 issues here at my work with the University of Oslo. My idea is that
4017 it should be possible to use the information about security issues
4018 available on the Internet, and check our locally
4019 maintained/distributed software against this information. It should
4020 allow us to verify that no known security issues are forgotten. The
4021 CVE database listing vulnerabilities seem like a great central point,
4022 and by using the package lists from Debian mapped to CVEs provided by
4023 the testing security team, I believed it should be possible to figure
4024 out which security holes were present in our free software
4025 collection.&lt;/p&gt;
4026
4027 &lt;p&gt;After reading up on the topic, it became obvious that the first
4028 building block is to be able to name software packages in a unique and
4029 consistent way across data sources. I considered several ways to do
4030 this, for example coming up with my own naming scheme like using URLs
4031 to project home pages or URLs to the Freshmeat entries, or using some
4032 existing naming scheme. And it seem like I am not the first one to
4033 come across this problem, as MITRE already proposed and implemented a
4034 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
4035 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
4036 software, hardware and other platform components. The CPE ids are
4037 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
4038 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
4039 issues for any CPE name. With this in place, all I need to do is to
4040 locate the CPE id for the software packages we use at the university.
4041 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
4042 NVD entry if a CVE for the package exist).&lt;/p&gt;
4043
4044 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
4045 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
4046 check out, one could look up
4047 &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
4048 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
4049 The most recent one is
4050 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
4051 and at the bottom of the NVD page for this vulnerability the complete
4052 list of affected versions is provided.&lt;/p&gt;
4053
4054 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
4055 for offline processing of issues. Using this dump, I&#39;ve written a
4056 small script taking a list of CPEs as input and list all CVEs
4057 affecting the packages represented by these CPEs. One give it CPEs
4058 with version numbers as specified above and get a list of open
4059 security issues out.&lt;/p&gt;
4060
4061 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
4062 information need to be high. For that to happen, I believe as many as
4063 possible need to use and contribute to the NVD database. I notice
4064 RHEL is providing
4065 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
4066 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
4067 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
4068
4069 &lt;p&gt;To get an idea about the quality for free software, I spent some
4070 time making it possible to compare the CVE database from Debian with
4071 the CVE database in NVD. The result look fairly good, but there are
4072 some inconsistencies in NVD (same software package having several
4073 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
4074 Debian believe are affected by a CVE). Hope to find time to improve
4075 the quality of NVD, but that require being able to get in touch with
4076 someone maintaining it. So far my three emails with questions and
4077 corrections have not seen any reply, but I hope contact can be
4078 established soon.&lt;/p&gt;
4079
4080 &lt;p&gt;An interesting application for CPEs is cross platform package
4081 mapping. It would be useful to know which packages in for example
4082 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
4083 this would be trivial if all linux distributions provided CPE entries
4084 for their packages.&lt;/p&gt;
4085 </description>
4086 </item>
4087
4088 <item>
4089 <title>Which module is loaded for a given PCI and USB device?</title>
4090 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
4091 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
4092 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
4093 <description>&lt;p&gt;In the
4094 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
4095 package in Debian, there is a script to report useful information
4096 about the running hardware for use when people report missing
4097 information. One part of this script that I find very useful when
4098 debugging hardware problems, is the part mapping loaded kernel module
4099 to the PCI device it claims. It allow me to quickly see if the kernel
4100 module I expect is driving the hardware I am struggling with. To see
4101 the output, make sure discover-data is installed and run
4102 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
4103 one of my machines like this:&lt;/p&gt;
4104
4105 &lt;pre&gt;
4106 loaded modules:
4107 10de:03eb i2c_nforce2
4108 10de:03f1 ohci_hcd
4109 10de:03f2 ehci_hcd
4110 10de:03f0 snd_hda_intel
4111 10de:03ec pata_amd
4112 10de:03f6 sata_nv
4113 1022:1103 k8temp
4114 109e:036e bttv
4115 109e:0878 snd_bt87x
4116 11ab:4364 sky2
4117 &lt;/pre&gt;
4118
4119 &lt;p&gt;The code in question look like this, slightly modified for
4120 readability and to drop the output to file descriptor 3:&lt;/p&gt;
4121
4122 &lt;pre&gt;
4123 if [ -d /sys/bus/pci/devices/ ] ; then
4124 echo loaded pci modules:
4125 (
4126 cd /sys/bus/pci/devices/
4127 for address in * ; do
4128 if [ -d &quot;$address/driver/module&quot; ] ; then
4129 module=`cd $address/driver/module ; pwd -P | xargs basename`
4130 if grep -q &quot;^$module &quot; /proc/modules ; then
4131 address=$(echo $address |sed s/0000://)
4132 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
4133 echo &quot;$id $module&quot;
4134 fi
4135 fi
4136 done
4137 )
4138 echo
4139 fi
4140 &lt;/pre&gt;
4141
4142 &lt;p&gt;Similar code could be used to extract USB device module
4143 mappings:&lt;/p&gt;
4144
4145 &lt;pre&gt;
4146 if [ -d /sys/bus/usb/devices/ ] ; then
4147 echo loaded usb modules:
4148 (
4149 cd /sys/bus/usb/devices/
4150 for address in * ; do
4151 if [ -d &quot;$address/driver/module&quot; ] ; then
4152 module=`cd $address/driver/module ; pwd -P | xargs basename`
4153 if grep -q &quot;^$module &quot; /proc/modules ; then
4154 address=$(echo $address |sed s/0000://)
4155 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
4156 if [ &quot;$id&quot; ] ; then
4157 echo &quot;$id $module&quot;
4158 fi
4159 fi
4160 fi
4161 done
4162 )
4163 echo
4164 fi
4165 &lt;/pre&gt;
4166
4167 &lt;p&gt;This might perhaps be something to include in other tools as
4168 well.&lt;/p&gt;
4169 </description>
4170 </item>
4171
4172 <item>
4173 <title>How to test if a laptop is working with Linux</title>
4174 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
4175 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
4176 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
4177 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
4178 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
4179 batch of computers will work with Linux. Every year for the last few
4180 years the university have organised shared bid of a few thousand
4181 computers, and this year HP won the bid. Two different desktops and
4182 five different laptops are on the list this year. We in the UNIX
4183 group want to know which one of these computers work well with RHEL
4184 and Ubuntu, the two Linux distributions we currently handle at the
4185 university.&lt;/p&gt;
4186
4187 &lt;p&gt;My test method is simple, and I share it here to get feedback and
4188 perhaps inspire others to test hardware as well. To test, I PXE
4189 install the OS version of choice, and log in as my normal user and run
4190 a few applications and plug in selected pieces of hardware. When
4191 something fail, I make a note about this in the test matrix and move
4192 on. If I have some spare time I try to report the bug to the OS
4193 vendor, but as I only have the machines for a short time, I rarely
4194 have the time to do this for all the problems I find.&lt;/p&gt;
4195
4196 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
4197 I perform on a new model.&lt;/p&gt;
4198
4199 &lt;ul&gt;
4200
4201 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
4202 and Ubuntu Maverik at the moment. If I feel like it, I also test with
4203 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
4204
4205 &lt;li&gt;Is X.org working? If the graphical login screen show up after
4206 installation, X.org is working.&lt;/li&gt;
4207
4208 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
4209 package mesa-utils on Ubuntu) and writing down the frames per second
4210 reported by the program.&lt;/li&gt;
4211
4212 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
4213 logging in, and if I can hear this the test is successful. If there
4214 are several audio exits on the machine, I try them all and check if
4215 the Gnome/KDE audio mixer can control where to send the sound. I
4216 normally test this by playing
4217 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
4218 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
4219
4220 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
4221 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
4222
4223 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
4224 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
4225
4226 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
4227 picture from the v4l device show up.&lt;/li&gt;
4228
4229 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
4230 any bluetooth devices are discovered. In my office, I normally see a
4231 few.&lt;/li&gt;
4232
4233 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
4234 memory modules lying around, and stick them in and see if Gnome/KDE
4235 notice this.&lt;/li&gt;
4236
4237 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
4238 special button work, and if the laptop continue to work after
4239 resume.&lt;/li&gt;
4240
4241 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
4242 adjusting background light, switching on/off external video output,
4243 switching on/off wifi, bluetooth, etc? The set of buttons differ from
4244 laptop to laptop, so I just write down which are working and which are
4245 not.&lt;/li&gt;
4246
4247 &lt;li&gt;Some laptops have smart card readers, finger print readers,
4248 acceleration sensors etc. I rarely test these, as I do not know how
4249 to quickly test if they are working or not, so I only document their
4250 existence.&lt;/li&gt;
4251
4252 &lt;/ul&gt;
4253
4254 &lt;p&gt;By now I suspect you are really curious what the test results are
4255 for the HP machines I am testing. I&#39;m not done yet, so I will report
4256 the test results later. For now I can report that HP 8100 Elite work
4257 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
4258 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
4259 can see, I have most machines left to test. One interesting
4260 observation is that Ubuntu Lucid has almost twice the frame rate than
4261 RHEL6 with glxgears. No idea why.&lt;/p&gt;
4262 </description>
4263 </item>
4264
4265 <item>
4266 <title>Some thoughts on BitCoins</title>
4267 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
4268 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
4269 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
4270 <description>&lt;p&gt;As I continue to explore
4271 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
4272 what properties the system have, and how it will be affected by laws
4273 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
4274
4275 &lt;p&gt;One interesting thing to note is that since the transactions are
4276 verified using a peer to peer network, all details about a transaction
4277 is known to everyone. This means that if a BitCoin address has been
4278 published like I did with mine in my initial post about BitCoin, it is
4279 possible for everyone to see how many BitCoins have been transfered to
4280 that address. There is even a web service to look at the details for
4281 all transactions. There I can see that my address
4282 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
4283 have received 16.06 Bitcoin, the
4284 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
4285 address of Simon Phipps have received 181.97 BitCoin and the address
4286 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
4287 of EFF have received 2447.38 BitCoins so far. Thank you to each and
4288 every one of you that donated bitcoins to support my activity. The
4289 fact that anyone can see how much money was transfered to a given
4290 address make it more obvious why the BitCoin community recommend to
4291 generate and hand out a new address for each transaction. I&#39;m told
4292 there is no way to track which addresses belong to a given person or
4293 organisation without the person or organisation revealing it
4294 themselves, as Simon, EFF and I have done.&lt;/p&gt;
4295
4296 &lt;p&gt;In Norway, and in most other countries, there are laws and
4297 regulations limiting how much money one can transfer across the border
4298 without declaring it. There are money laundering, tax and accounting
4299 laws and regulations I would expect to apply to the use of BitCoin.
4300 If the Skolelinux foundation
4301 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
4302 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
4303 normal bank transfers like EFF is doing, how should this be accounted?
4304 Given that it is impossible to know if money can cross the border or
4305 not, should everything or nothing be declared? What exchange rate
4306 should be used when calculating taxes? Would receivers have to pay
4307 income tax if the foundation were to pay Skolelinux contributors in
4308 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
4309
4310 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
4311 accepted by a lot of users. It must be possible to get easy access to
4312 the currency (as a wage or using currency exchanges), and it must be
4313 easy to spend it. At the moment BitCoin seem fairly easy to get
4314 access to, but there are very few places to spend it. I am not really
4315 a regular user of any of the vendor types currently accepting BitCoin,
4316 so I wonder when my kind of shop would start accepting BitCoins. I
4317 would like to buy electronics, travels and subway tickets, not herbs
4318 and books. :) The currency is young, and this will improve over time
4319 if it become popular, but I suspect regular banks will start to lobby
4320 to get BitCoin declared illegal if it become popular. I&#39;m sure they
4321 will claim it is helping fund terrorism and money laundering (which
4322 probably would be true, as is any currency in existence), but I
4323 believe the problems should be solved elsewhere and not by blaming
4324 currencies.&lt;/p&gt;
4325
4326 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
4327 CPU intensive process that depend on a bit of luck as well (as one is
4328 competing against all the other miners currently spending CPU cycles
4329 to see which one get the next lump of cash). The &quot;winner&quot; get 50
4330 BitCoin when this happen. Yesterday I came across the obvious way to
4331 join forces to increase ones changes of getting at least some coins,
4332 by coordinating the work on mining BitCoins across several machines
4333 and people, and sharing the result if one is lucky and get the 50
4334 BitCoins. Check out
4335 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
4336 if this sounds interesting. I have not had time to try to set up a
4337 machine to participate there yet, but have seen that running on ones
4338 own for a few days have not yield any BitCoins througth mining
4339 yet.&lt;/p&gt;
4340
4341 &lt;p&gt;Update 2010-12-15: Found an &lt;a
4342 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
4343 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
4344 it was interesting to read. The arguments presented seem to be
4345 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
4346 </description>
4347 </item>
4348
4349 <item>
4350 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
4351 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
4352 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
4353 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
4354 <description>&lt;p&gt;With this weeks lawless
4355 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
4356 attacks&lt;/a&gt; on Wikileak and
4357 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
4358 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
4359 not be trusted to handle money transactions.
4360 A blog post from
4361 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
4362 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
4363 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
4364 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
4365 some help from my friend to get it all running, and he even handed me
4366 some bitcoins to get started. I even donated a few bitcoins to Simon
4367 for helping me remember BitCoin.&lt;/p&gt;
4368
4369 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
4370 crypto-currency, decentralised and handled using peer-to-peer
4371 networks. It allows anonymous transactions and prohibits central
4372 control over the transactions, making it impossible for governments
4373 and companies alike to block donations and other transactions. The
4374 source is free software, and while the key dependency wxWidgets 2.9
4375 for the graphical user interface is missing in Debian, the command
4376 line client builds just fine. Hopefully Jonas
4377 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
4378 Debian&lt;/a&gt; soon.&lt;/p&gt;
4379
4380 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
4381 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
4382 bitcoins&lt;/a&gt; when selling services and goods, and there are even
4383 currency &quot;stock&quot; markets where the exchange rate is decided. There
4384 are not many users so far, but the concept seems promising. If you
4385 want to get started and lack a friend with any bitcoins to spare,
4386 you can even get
4387 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
4388 bitcoin at the time of writing). Use
4389 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
4390 on the current exchange rates.&lt;/p&gt;
4391
4392 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
4393 machines. If you want to support my activity, please send Bitcoin
4394 donations to the address
4395 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
4396 </description>
4397 </item>
4398
4399 <item>
4400 <title>Why isn&#39;t Debian Edu using VLC?</title>
4401 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
4402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
4403 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
4404 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
4405 presented, and the winner among the multimedia player were VLC.
4406 Personally, I like VLC, and it is my player of choice when I first try
4407 to play a video file or stream. Only if VLC fail will I drag out
4408 gmplayer to see if it can do better. The reason is mostly the failure
4409 model and trust. When VLC fail, it normally pop up a error message
4410 reporting the problem. When mplayer fail, it normally segfault or
4411 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
4412
4413 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
4414 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
4415 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
4416 plugin to play web videos seamlessly, and the VLC browser plugin is
4417 not very good. For example, it lack in-line control buttons, so there
4418 is no way for the user to pause the video. Also, when I
4419 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
4420 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
4421 failed on several video pages where mplayer based plugins worked. If
4422 the browser plugin for VLC was as good as the gecko-mediaplayer
4423 package (which uses mplayer), we would switch.&lt;/P&gt;
4424
4425 &lt;p&gt;While VLC is a good player, its user interface is slightly
4426 annoying. The most annoying feature is its inconsistent use of
4427 keyboard shortcuts. When the player is in full screen mode, its
4428 shortcuts are different from when it is playing the video in a window.
4429 For example, space only work as pause when in full screen mode. I
4430 wish it had consisten shortcuts and that space also would work when in
4431 window mode. Another nice shortcut in gmplayer is [enter] to restart
4432 the current video. It is very nice when playing short videos from the
4433 web and want to restart it when new people arrive to have a look at
4434 what is going on.&lt;/p&gt;
4435 </description>
4436 </item>
4437
4438 <item>
4439 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
4440 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
4441 <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>
4442 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
4443 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
4444 upgrade testing of the
4445 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
4446 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
4447 This seem like a very good idea, so I adjusted by test scripts and
4448 can now present the updated result from today:&lt;/p&gt;
4449
4450 &lt;p&gt;This is for Gnome:&lt;/p&gt;
4451
4452 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4453
4454 &lt;blockquote&gt;&lt;p&gt;
4455 apache2.2-bin
4456 aptdaemon
4457 baobab
4458 binfmt-support
4459 browser-plugin-gnash
4460 cheese-common
4461 cli-common
4462 cups-pk-helper
4463 dmz-cursor-theme
4464 empathy
4465 empathy-common
4466 freedesktop-sound-theme
4467 freeglut3
4468 gconf-defaults-service
4469 gdm-themes
4470 gedit-plugins
4471 geoclue
4472 geoclue-hostip
4473 geoclue-localnet
4474 geoclue-manual
4475 geoclue-yahoo
4476 gnash
4477 gnash-common
4478 gnome
4479 gnome-backgrounds
4480 gnome-cards-data
4481 gnome-codec-install
4482 gnome-core
4483 gnome-desktop-environment
4484 gnome-disk-utility
4485 gnome-screenshot
4486 gnome-search-tool
4487 gnome-session-canberra
4488 gnome-system-log
4489 gnome-themes-extras
4490 gnome-themes-more
4491 gnome-user-share
4492 gstreamer0.10-fluendo-mp3
4493 gstreamer0.10-tools
4494 gtk2-engines
4495 gtk2-engines-pixbuf
4496 gtk2-engines-smooth
4497 hamster-applet
4498 libapache2-mod-dnssd
4499 libapr1
4500 libaprutil1
4501 libaprutil1-dbd-sqlite3
4502 libaprutil1-ldap
4503 libart2.0-cil
4504 libboost-date-time1.42.0
4505 libboost-python1.42.0
4506 libboost-thread1.42.0
4507 libchamplain-0.4-0
4508 libchamplain-gtk-0.4-0
4509 libcheese-gtk18
4510 libclutter-gtk-0.10-0
4511 libcryptui0
4512 libdiscid0
4513 libelf1
4514 libepc-1.0-2
4515 libepc-common
4516 libepc-ui-1.0-2
4517 libfreerdp-plugins-standard
4518 libfreerdp0
4519 libgconf2.0-cil
4520 libgdata-common
4521 libgdata7
4522 libgdu-gtk0
4523 libgee2
4524 libgeoclue0
4525 libgexiv2-0
4526 libgif4
4527 libglade2.0-cil
4528 libglib2.0-cil
4529 libgmime2.4-cil
4530 libgnome-vfs2.0-cil
4531 libgnome2.24-cil
4532 libgnomepanel2.24-cil
4533 libgpod-common
4534 libgpod4
4535 libgtk2.0-cil
4536 libgtkglext1
4537 libgtksourceview2.0-common
4538 libmono-addins-gui0.2-cil
4539 libmono-addins0.2-cil
4540 libmono-cairo2.0-cil
4541 libmono-corlib2.0-cil
4542 libmono-i18n-west2.0-cil
4543 libmono-posix2.0-cil
4544 libmono-security2.0-cil
4545 libmono-sharpzip2.84-cil
4546 libmono-system2.0-cil
4547 libmtp8
4548 libmusicbrainz3-6
4549 libndesk-dbus-glib1.0-cil
4550 libndesk-dbus1.0-cil
4551 libopal3.6.8
4552 libpolkit-gtk-1-0
4553 libpt2.6.7
4554 libpython2.6
4555 librpm1
4556 librpmio1
4557 libsdl1.2debian
4558 libsrtp0
4559 libssh-4
4560 libtelepathy-farsight0
4561 libtelepathy-glib0
4562 libtidy-0.99-0
4563 media-player-info
4564 mesa-utils
4565 mono-2.0-gac
4566 mono-gac
4567 mono-runtime
4568 nautilus-sendto
4569 nautilus-sendto-empathy
4570 p7zip-full
4571 pkg-config
4572 python-aptdaemon
4573 python-aptdaemon-gtk
4574 python-axiom
4575 python-beautifulsoup
4576 python-bugbuddy
4577 python-clientform
4578 python-coherence
4579 python-configobj
4580 python-crypto
4581 python-cupshelpers
4582 python-elementtree
4583 python-epsilon
4584 python-evolution
4585 python-feedparser
4586 python-gdata
4587 python-gdbm
4588 python-gst0.10
4589 python-gtkglext1
4590 python-gtksourceview2
4591 python-httplib2
4592 python-louie
4593 python-mako
4594 python-markupsafe
4595 python-mechanize
4596 python-nevow
4597 python-notify
4598 python-opengl
4599 python-openssl
4600 python-pam
4601 python-pkg-resources
4602 python-pyasn1
4603 python-pysqlite2
4604 python-rdflib
4605 python-serial
4606 python-tagpy
4607 python-twisted-bin
4608 python-twisted-conch
4609 python-twisted-core
4610 python-twisted-web
4611 python-utidylib
4612 python-webkit
4613 python-xdg
4614 python-zope.interface
4615 remmina
4616 remmina-plugin-data
4617 remmina-plugin-rdp
4618 remmina-plugin-vnc
4619 rhythmbox-plugin-cdrecorder
4620 rhythmbox-plugins
4621 rpm-common
4622 rpm2cpio
4623 seahorse-plugins
4624 shotwell
4625 software-center
4626 system-config-printer-udev
4627 telepathy-gabble
4628 telepathy-mission-control-5
4629 telepathy-salut
4630 tomboy
4631 totem
4632 totem-coherence
4633 totem-mozilla
4634 totem-plugins
4635 transmission-common
4636 xdg-user-dirs
4637 xdg-user-dirs-gtk
4638 xserver-xephyr
4639 &lt;/p&gt;&lt;/blockquote&gt;
4640
4641 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4642
4643 &lt;blockquote&gt;&lt;p&gt;
4644 cheese
4645 ekiga
4646 eog
4647 epiphany-extensions
4648 evolution-exchange
4649 fast-user-switch-applet
4650 file-roller
4651 gcalctool
4652 gconf-editor
4653 gdm
4654 gedit
4655 gedit-common
4656 gnome-games
4657 gnome-games-data
4658 gnome-nettool
4659 gnome-system-tools
4660 gnome-themes
4661 gnuchess
4662 gucharmap
4663 guile-1.8-libs
4664 libavahi-ui0
4665 libdmx1
4666 libgalago3
4667 libgtk-vnc-1.0-0
4668 libgtksourceview2.0-0
4669 liblircclient0
4670 libsdl1.2debian-alsa
4671 libspeexdsp1
4672 libsvga1
4673 rhythmbox
4674 seahorse
4675 sound-juicer
4676 system-config-printer
4677 totem-common
4678 transmission-gtk
4679 vinagre
4680 vino
4681 &lt;/p&gt;&lt;/blockquote&gt;
4682
4683 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4684
4685 &lt;blockquote&gt;&lt;p&gt;
4686 gstreamer0.10-gnomevfs
4687 &lt;/p&gt;&lt;/blockquote&gt;
4688
4689 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4690
4691 &lt;blockquote&gt;&lt;p&gt;
4692 [nothing]
4693 &lt;/p&gt;&lt;/blockquote&gt;
4694
4695 &lt;p&gt;This is for KDE:&lt;/p&gt;
4696
4697 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4698
4699 &lt;blockquote&gt;&lt;p&gt;
4700 ksmserver
4701 &lt;/p&gt;&lt;/blockquote&gt;
4702
4703 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
4704
4705 &lt;blockquote&gt;&lt;p&gt;
4706 kwin
4707 network-manager-kde
4708 &lt;/p&gt;&lt;/blockquote&gt;
4709
4710 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
4711
4712 &lt;blockquote&gt;&lt;p&gt;
4713 arts
4714 dolphin
4715 freespacenotifier
4716 google-gadgets-gst
4717 google-gadgets-xul
4718 kappfinder
4719 kcalc
4720 kcharselect
4721 kde-core
4722 kde-plasma-desktop
4723 kde-standard
4724 kde-window-manager
4725 kdeartwork
4726 kdeartwork-emoticons
4727 kdeartwork-style
4728 kdeartwork-theme-icon
4729 kdebase
4730 kdebase-apps
4731 kdebase-workspace
4732 kdebase-workspace-bin
4733 kdebase-workspace-data
4734 kdeeject
4735 kdelibs
4736 kdeplasma-addons
4737 kdeutils
4738 kdewallpapers
4739 kdf
4740 kfloppy
4741 kgpg
4742 khelpcenter4
4743 kinfocenter
4744 konq-plugins-l10n
4745 konqueror-nsplugins
4746 kscreensaver
4747 kscreensaver-xsavers
4748 ktimer
4749 kwrite
4750 libgle3
4751 libkde4-ruby1.8
4752 libkonq5
4753 libkonq5-templates
4754 libnetpbm10
4755 libplasma-ruby
4756 libplasma-ruby1.8
4757 libqt4-ruby1.8
4758 marble-data
4759 marble-plugins
4760 netpbm
4761 nuvola-icon-theme
4762 plasma-dataengines-workspace
4763 plasma-desktop
4764 plasma-desktopthemes-artwork
4765 plasma-runners-addons
4766 plasma-scriptengine-googlegadgets
4767 plasma-scriptengine-python
4768 plasma-scriptengine-qedje
4769 plasma-scriptengine-ruby
4770 plasma-scriptengine-webkit
4771 plasma-scriptengines
4772 plasma-wallpapers-addons
4773 plasma-widget-folderview
4774 plasma-widget-networkmanagement
4775 ruby
4776 sweeper
4777 update-notifier-kde
4778 xscreensaver-data-extra
4779 xscreensaver-gl
4780 xscreensaver-gl-extra
4781 xscreensaver-screensaver-bsod
4782 &lt;/p&gt;&lt;/blockquote&gt;
4783
4784 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
4785
4786 &lt;blockquote&gt;&lt;p&gt;
4787 ark
4788 google-gadgets-common
4789 google-gadgets-qt
4790 htdig
4791 kate
4792 kdebase-bin
4793 kdebase-data
4794 kdepasswd
4795 kfind
4796 klipper
4797 konq-plugins
4798 konqueror
4799 ksysguard
4800 ksysguardd
4801 libarchive1
4802 libcln6
4803 libeet1
4804 libeina-svn-06
4805 libggadget-1.0-0b
4806 libggadget-qt-1.0-0b
4807 libgps19
4808 libkdecorations4
4809 libkephal4
4810 libkonq4
4811 libkonqsidebarplugin4a
4812 libkscreensaver5
4813 libksgrd4
4814 libksignalplotter4
4815 libkunitconversion4
4816 libkwineffects1a
4817 libmarblewidget4
4818 libntrack-qt4-1
4819 libntrack0
4820 libplasma-geolocation-interface4
4821 libplasmaclock4a
4822 libplasmagenericshell4
4823 libprocesscore4a
4824 libprocessui4a
4825 libqalculate5
4826 libqedje0a
4827 libqtruby4shared2
4828 libqzion0a
4829 libruby1.8
4830 libscim8c2a
4831 libsmokekdecore4-3
4832 libsmokekdeui4-3
4833 libsmokekfile3
4834 libsmokekhtml3
4835 libsmokekio3
4836 libsmokeknewstuff2-3
4837 libsmokeknewstuff3-3
4838 libsmokekparts3
4839 libsmokektexteditor3
4840 libsmokekutils3
4841 libsmokenepomuk3
4842 libsmokephonon3
4843 libsmokeplasma3
4844 libsmokeqtcore4-3
4845 libsmokeqtdbus4-3
4846 libsmokeqtgui4-3
4847 libsmokeqtnetwork4-3
4848 libsmokeqtopengl4-3
4849 libsmokeqtscript4-3
4850 libsmokeqtsql4-3
4851 libsmokeqtsvg4-3
4852 libsmokeqttest4-3
4853 libsmokeqtuitools4-3
4854 libsmokeqtwebkit4-3
4855 libsmokeqtxml4-3
4856 libsmokesolid3
4857 libsmokesoprano3
4858 libtaskmanager4a
4859 libtidy-0.99-0
4860 libweather-ion4a
4861 libxklavier16
4862 libxxf86misc1
4863 okteta
4864 oxygencursors
4865 plasma-dataengines-addons
4866 plasma-scriptengine-superkaramba
4867 plasma-widget-lancelot
4868 plasma-widgets-addons
4869 plasma-widgets-workspace
4870 polkit-kde-1
4871 ruby1.8
4872 systemsettings
4873 update-notifier-common
4874 &lt;/p&gt;&lt;/blockquote&gt;
4875
4876 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
4877 aptitude a bit more similar, but there are still quite a lott of
4878 differences. I have no idea what packages should be installed after
4879 the upgrade, but hope those that do can have a look.&lt;/p&gt;
4880 </description>
4881 </item>
4882
4883 <item>
4884 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
4885 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
4886 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
4887 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
4888 <description>&lt;p&gt;Most of the computers in use by the
4889 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
4890 are virtual machines. And they have been Xen machines running on a
4891 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
4892 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
4893 bit harder that it could have been, because we set up the Xen virtual
4894 machines to get the virtual partitions from LVM, which as far as I
4895 know is not supported by KVM. So to migrate, we had to convert
4896 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
4897
4898 &lt;p&gt;I found
4899 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
4900 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
4901 migration. It uses qemu-img from the qemu package to make the disk
4902 image, parted to partition it, losetup and kpartx to present the disk
4903 image partions as devices, and dd to copy the data. I NFS mounted the
4904 new servers storage area on the old server to do the migration.&lt;/p&gt;
4905
4906 &lt;pre&gt;
4907 #!/bin/sh
4908
4909 # Based on
4910 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
4911
4912 set -e
4913 set -x
4914
4915 if [ -z &quot;$1&quot; ] ; then
4916 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
4917 exit 1
4918 else
4919 host=&quot;$1&quot;
4920 fi
4921
4922 if [ ! -e /dev/vg_data/$host-disk ] ; then
4923 echo &quot;error: unable to find LVM volume for $host&quot;
4924 exit 1
4925 fi
4926
4927 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
4928 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
4929 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
4930 totalsize=$(( ( $disksize + $swapsize ) ))
4931
4932 img=$host.img
4933 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
4934 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
4935
4936 parted $img mklabel msdos
4937 parted $img mkpart primary linux-swap 0 $disksize
4938 parted $img mkpart primary ext2 $disksize $totalsize
4939 parted $img set 1 boot on
4940
4941 modprobe dm-mod
4942 losetup /dev/loop0 $img
4943 kpartx -a /dev/loop0
4944
4945 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
4946 fsck.ext3 -f /dev/mapper/loop0p1 || true
4947 mkswap /dev/mapper/loop0p2
4948
4949 kpartx -d /dev/loop0
4950 losetup -d /dev/loop0
4951 &lt;/pre&gt;
4952
4953 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
4954 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
4955
4956 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
4957 the new disk image attached, installed grub-pc and linux-image-686 and
4958 set up grub to boot from the disk image. After this, the KVM machines
4959 seem to work just fine.&lt;/p&gt;
4960 </description>
4961 </item>
4962
4963 <item>
4964 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
4965 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
4966 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
4967 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
4968 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
4969 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
4970 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
4971 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
4972
4973 &lt;p&gt;I still do not know what a correct migration should look like, so I
4974 report any differences between apt and aptitude and hope someone else
4975 can see if anything should be changed.&lt;/p&gt;
4976
4977 &lt;p&gt;This is for Gnome:&lt;/p&gt;
4978
4979 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
4980
4981 &lt;blockquote&gt;&lt;p&gt;
4982 apache2.2-bin aptdaemon at-spi baobab binfmt-support
4983 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
4984 dmz-cursor-theme empathy empathy-common finger
4985 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
4986 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
4987 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
4988 gnome-cards-data gnome-codec-install gnome-core
4989 gnome-desktop-environment gnome-disk-utility gnome-screenshot
4990 gnome-search-tool gnome-session-canberra gnome-spell
4991 gnome-system-log gnome-themes-extras gnome-themes-more
4992 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
4993 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
4994 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
4995 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
4996 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
4997 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
4998 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
4999 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
5000 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
5001 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
5002 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
5003 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
5004 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
5005 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
5006 libgtk2.0-cil libgtkglext1 libgtksourceview-common
5007 libgtksourceview2.0-common libmono-addins-gui0.2-cil
5008 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
5009 libmono-i18n-west2.0-cil libmono-posix2.0-cil
5010 libmono-security2.0-cil libmono-sharpzip2.84-cil
5011 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
5012 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
5013 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
5014 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
5015 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
5016 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
5017 libxalan2-java libxerces2-java media-player-info mesa-utils
5018 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
5019 nautilus-sendto-empathy openoffice.org-writer2latex
5020 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
5021 python-aptdaemon python-aptdaemon-gtk python-axiom
5022 python-beautifulsoup python-bugbuddy python-clientform
5023 python-coherence python-configobj python-crypto python-cupshelpers
5024 python-cupsutils python-eggtrayicon python-elementtree
5025 python-epsilon python-evolution python-feedparser python-gdata
5026 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
5027 python-gtksourceview2 python-httplib2 python-louie python-mako
5028 python-markupsafe python-mechanize python-nevow python-notify
5029 python-opengl python-openssl python-pam python-pkg-resources
5030 python-pyasn1 python-pysqlite2 python-rdflib python-serial
5031 python-tagpy python-twisted-bin python-twisted-conch
5032 python-twisted-core python-twisted-web python-utidylib python-webkit
5033 python-xdg python-zope.interface remmina remmina-plugin-data
5034 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
5035 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
5036 software-center svgalibg1 system-config-printer-udev
5037 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
5038 totem totem-coherence totem-mozilla totem-plugins
5039 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
5040 zip
5041 &lt;/p&gt;&lt;/blockquote&gt;
5042
5043 Installed using apt-get, removed with aptitude
5044
5045 &lt;blockquote&gt;&lt;p&gt;
5046 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
5047 epiphany-extensions epiphany-gecko evolution-exchange
5048 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
5049 gedit-common gnome-app-install gnome-games gnome-games-data
5050 gnome-nettool gnome-system-tools gnome-themes gnome-utils
5051 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
5052 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
5053 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
5054 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
5055 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
5056 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
5057 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5058 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5059 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5060 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
5061 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
5062 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
5063 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
5064 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
5065 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
5066 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
5067 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
5068 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
5069 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
5070 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
5071 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
5072 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
5073 sound-juicer swfdec-gnome system-config-printer totem-common
5074 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
5075 &lt;/p&gt;&lt;/blockquote&gt;
5076
5077 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5078
5079 &lt;blockquote&gt;&lt;p&gt;
5080 gstreamer0.10-gnomevfs
5081 &lt;/p&gt;&lt;/blockquote&gt;
5082
5083 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5084
5085 &lt;blockquote&gt;&lt;p&gt;
5086 [nothing]
5087 &lt;/p&gt;&lt;/blockquote&gt;
5088
5089 &lt;p&gt;This is for KDE:&lt;/p&gt;
5090
5091 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5092
5093 &lt;blockquote&gt;&lt;p&gt;
5094 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
5095 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
5096 ghostscript-x git gnome-audio gnugo granatier gs-common
5097 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
5098 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
5099 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
5100 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
5101 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
5102 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
5103 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
5104 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
5105 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
5106 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
5107 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
5108 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
5109 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
5110 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
5111 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
5112 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
5113 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
5114 libkrossui4 libmailtools-perl libmime-tools-perl
5115 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
5116 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
5117 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
5118 lirc luatex marble networkstatus noatun-plugins
5119 openoffice.org-writer2latex palapeli palapeli-data parley
5120 parley-data poster psutils pulseaudio pulseaudio-esound-compat
5121 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
5122 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
5123 ttf-sazanami-gothic
5124 &lt;/p&gt;&lt;/blockquote&gt;
5125
5126 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5127
5128 &lt;blockquote&gt;&lt;p&gt;
5129 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
5130 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
5131 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
5132 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
5133 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
5134 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
5135 kitchensync kiten kjumpingcube klatin klettres klickety klines
5136 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
5137 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
5138 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
5139 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
5140 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
5141 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
5142 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
5143 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
5144 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
5145 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
5146 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
5147 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
5148 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
5149 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
5150 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
5151 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
5152 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
5153 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
5154 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
5155 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
5156 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
5157 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
5158 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
5159 mpeglib network-manager-kde noatun pmount tex-common texlive-base
5160 texlive-common texlive-doc-base texlive-fonts-recommended tidy
5161 ttf-dustin ttf-kochi-gothic ttf-sjfonts
5162 &lt;/p&gt;&lt;/blockquote&gt;
5163
5164 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5165
5166 &lt;blockquote&gt;&lt;p&gt;
5167 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
5168 kdeartwork kdebase kdebase-apps kdebase-workspace
5169 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
5170 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
5171 netpbm plasma-widget-folderview plasma-widget-networkmanagement
5172 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
5173 xscreensaver-screensaver-bsod
5174 &lt;/p&gt;&lt;/blockquote&gt;
5175
5176 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5177
5178 &lt;blockquote&gt;&lt;p&gt;
5179 kdebase-bin konq-plugins konqueror
5180 &lt;/p&gt;&lt;/blockquote&gt;
5181 </description>
5182 </item>
5183
5184 <item>
5185 <title>Gnash buildbot slave and Debian kfreebsd</title>
5186 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
5187 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
5188 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
5189 <description>&lt;p&gt;Answering
5190 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
5191 call from the Gnash project&lt;/a&gt; for
5192 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
5193 current source, I have set up a virtual KVM machine on the Debian
5194 Edu/Skolelinux virtualization host to test the git source on
5195 Debian/Squeeze. I hope this can help the developers in getting new
5196 releases out more often.&lt;/p&gt;
5197
5198 &lt;p&gt;As the developers want less main-stream build platforms tested to,
5199 I have considered setting up a &lt;a
5200 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
5201 machine as well. I have also considered using the kfreebsd
5202 architecture in Debian as a file server in NUUG to get access to the 5
5203 TB zfs volume we currently use to store DV video. Because of this, I
5204 finally got around to do a test installation of Debian/Squeeze with
5205 kfreebsd. Installation went fairly smooth, thought I noticed some
5206 visual glitches in the cdebconf dialogs (black cursor left on the
5207 screen at random locations). Have not gotten very far with the
5208 testing. Noticed cfdisk did not work, but fdisk did so it was not a
5209 fatal problem. Have to spend some more time on it to see if it is
5210 useful as a file server for NUUG. Will try to find time to set up a
5211 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
5212 </description>
5213 </item>
5214
5215 <item>
5216 <title>Debian in 3D</title>
5217 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
5218 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
5219 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
5220 <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;
5221
5222 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
5223 3D linked in from
5224 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
5225 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
5226 </description>
5227 </item>
5228
5229 <item>
5230 <title>Software updates 2010-10-24</title>
5231 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
5232 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
5233 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
5234 <description>&lt;p&gt;Some updates.&lt;/p&gt;
5235
5236 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
5237 raise money for the project is going well. The lower limit of 10
5238 signers was reached in 24 hours, and so far 13 people have signed it.
5239 More signers and more funding is most welcome, and I am really curious
5240 how far we can get before the time limit of December 24 is reached.
5241 :)&lt;/p&gt;
5242
5243 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
5244 about what appear to be a great code coverage tool capable of
5245 generating code coverage stats without any changes to the source code.
5246 It is called
5247 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
5248 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
5249 It is missing in Debian, but the git source built just fine in Squeeze
5250 after I installed libelf-dev, libdwarf-dev, pkg-config and
5251 libglib2.0-dev. Failed to build in Lenny, but suspect that is
5252 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
5253
5254 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
5255 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
5256 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
5257 alpha test release of the Squeeze based Debian Edu /
5258 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
5259 release. Give it a try if you need a complete linux solution for your
5260 school, including central infrastructure server, workstations, thin
5261 client servers and diskless workstations. A nice touch added
5262 yesterday is RDP support on the thin client servers, for windows
5263 clients to get a Linux desktop on request.&lt;/p&gt;
5264 </description>
5265 </item>
5266
5267 <item>
5268 <title>Some notes on Flash in Debian and Debian Edu</title>
5269 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
5270 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
5271 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
5272 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
5273 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
5274 second most popular used package that is missing in Debian. The sixth
5275 most popular is flashplayer-mozilla. This is a clear indication that
5276 working flash is important for Debian users. Around 10 percent of the
5277 users submitting data to popcon.debian.org have this package
5278 installed.&lt;/p&gt;
5279
5280 &lt;p&gt;In the report written by Lars Risan in August 2008
5281&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
5282 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
5283 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
5284 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
5285 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
5286 web sites require Flash to work, and lacking working Flash support in
5287 the web browser and the problems with installing it was perceived as a
5288 good reason to stay with Windows.&lt;/p&gt;
5289
5290 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
5291 said to be the retarded cousin that did not really understand
5292 everything you told him but could work fairly well. This was a
5293 comment regarding the problems Linux have with proprietary formats and
5294 non-standard web pages, and is sad because it exposes a fairly common
5295 understanding of whose fault it is if web pages that only work in for
5296 example Internet Explorer 6 fail to work on Firefox, and funny because
5297 it explain very well how annoying it is for users when Linux
5298 distributions do not work with the documents they receive or the web
5299 pages they want to visit.&lt;/p&gt;
5300
5301 &lt;p&gt;This is part of the reason why I believe it is important for Debian
5302 and Debian Edu to have a well working Flash implementation in the
5303 distribution, to get at least popular sites as Youtube and Google
5304 Video to working out of the box. For Squeeze, Debian have the chance
5305 to include the latest version of Gnash that will make this happen, as
5306 the new release 0.8.8 was published a few weeks ago and is resting in
5307 unstable. The new version work with more sites that version 0.8.7.
5308 The Gnash maintainers have asked for a freeze exception, but the
5309 release team have not had time to reply to it yet. I hope they agree
5310 with me that Flash is important for the Debian desktop users, and thus
5311 accept the new package into Squeeze.&lt;/p&gt;
5312 </description>
5313 </item>
5314
5315 <item>
5316 <title>Circular package dependencies harms apt recovery</title>
5317 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
5318 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
5319 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
5320 <description>&lt;p&gt;I discovered this while doing
5321 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
5322 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
5323 in Debian still got circular dependencies, and it is often claimed
5324 that apt and aptitude should be able to handle this just fine, but
5325 some times these dependency loops causes apt to fail.&lt;/p&gt;
5326
5327 &lt;p&gt;An example is from todays
5328 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
5329 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
5330 causes perl-modules to fail to upgrade. The cause is simple. If a
5331 package fail to unpack, then only part of packages with the circular
5332 dependency might end up being unpacked when unpacking aborts, and the
5333 ones already unpacked will fail to configure in the recovery phase
5334 because its dependencies are unavailable.&lt;/p&gt;
5335
5336 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
5337
5338 &lt;blockquote&gt;&lt;pre&gt;
5339 dpkg: dependency problems prevent configuration of perl-modules:
5340 perl-modules depends on perl (&gt;= 5.10.1-1); however:
5341 Version of perl on system is 5.10.0-19lenny2.
5342 dpkg: error processing perl-modules (--configure):
5343 dependency problems - leaving unconfigured
5344 &lt;/pre&gt;&lt;/blockquote&gt;
5345
5346 &lt;p&gt;The perl/perl-modules circular dependency is already
5347 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
5348 hopefully be solved as soon as possible, but it is not the only one,
5349 and each one of these loops in the dependency tree can cause similar
5350 failures. Of course, they only occur when there are bugs in other
5351 packages causing the unpacking to fail, but it is rather nasty when
5352 the failure of one package causes the problem to become worse because
5353 of dependency loops.&lt;/p&gt;
5354
5355 &lt;p&gt;Thanks to
5356 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
5357 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
5358 dependencies
5359 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
5360 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
5361
5362 &lt;p&gt;Todays testing also exposed a bug in
5363 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
5364 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
5365 apt-get and aptitude, the latter possibly caused by some circular
5366 dependency. Reported both to BTS to try to get someone to look at
5367 it.&lt;/p&gt;
5368 </description>
5369 </item>
5370
5371 <item>
5372 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
5373 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
5374 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
5375 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
5376 <description>&lt;p&gt;This is a
5377 &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;
5378 on my
5379 &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
5380 work&lt;/a&gt; on
5381 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
5382 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
5383
5384 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
5385 LDAP objects, I have had a look at how the packages pdns-backend-ldap
5386 and dhcp3-server-ldap in Debian use the LDAP server. The two
5387 implementations are quite different in how they use LDAP.&lt;/p&gt;
5388
5389 To get this information, I started slapd with debugging enabled and
5390 dumped the debug output to a file to get the LDAP searches performed
5391 on a Debian Edu main-server. Here is a summary.
5392
5393 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
5394
5395 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
5396 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
5397 the web.
5398
5399 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
5400 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
5401 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
5402 reverse entries are in two different subtrees in LDAP with a structure
5403 based on the DNS names, as in tjener.intern and
5404 2.2.0.10.in-addr.arpa.&lt;/p&gt;
5405
5406 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
5407 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
5408 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
5409 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
5410 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
5411 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
5412 forward entries, it is looking for attributes named dnsttl, arecord,
5413 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
5414 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
5415 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
5416 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
5417 spfrecord and modifytimestamp. For reverse entries it is looking for
5418 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
5419 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
5420 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
5421 ldapsearch commands could look like this:&lt;/p&gt;
5422
5423 &lt;blockquote&gt;&lt;pre&gt;
5424 ldapsearch -h ldap \
5425 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5426 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5427 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5428 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5429 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5430 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5431
5432 ldapsearch -h ldap \
5433 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
5434 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
5435 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
5436 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
5437 srvrecord naptrrecord modifytimestamp
5438 &lt;/pre&gt;&lt;/blockquote&gt;
5439
5440 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
5441 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
5442 example LDAP objects used there. In addition to these objects, the
5443 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
5444 also exist.&lt;/p&gt;
5445
5446 &lt;blockquote&gt;&lt;pre&gt;
5447 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
5448 objectclass: top
5449 objectclass: dnsdomain
5450 objectclass: domainrelatedobject
5451 dc: tjener
5452 arecord: 10.0.2.2
5453 associateddomain: tjener.intern
5454
5455 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
5456 objectclass: top
5457 objectclass: dnsdomain2
5458 objectclass: domainrelatedobject
5459 dc: 2
5460 ptrrecord: tjener.intern
5461 associateddomain: 2.2.0.10.in-addr.arpa
5462 &lt;/pre&gt;&lt;/blockquote&gt;
5463
5464 &lt;p&gt;In strict mode, the server behaves differently. When looking for
5465 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
5466 same base as in the tree mode for a object with filter
5467 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
5468 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
5469 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
5470 naptrrecord and modifytimestamp. For reverse entires it also do a
5471 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
5472 and the requested attributes are associateddomain, dnsttl and
5473 modifytimestamp. In short, in strict mode the objects with ptrrecord
5474 go away, and the arecord attribute in the forward object is used
5475 instead.&lt;/p&gt;
5476
5477 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
5478 like this:&lt;/p&gt;
5479
5480 &lt;blockquote&gt;&lt;pre&gt;
5481 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5482 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
5483 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
5484 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
5485 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
5486 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
5487
5488 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
5489 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
5490 &lt;/pre&gt;&lt;/blockquote&gt;
5491
5492 &lt;p&gt;In addition to the forward and reverse searches , there is also a
5493 search for SOA records, which behave similar to the forward and
5494 reverse lookups.&lt;/p&gt;
5495
5496 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
5497 specify any objectclass names, and instead look for the attributes it
5498 need to generate a DNS reply. This make it able to work with any
5499 objectclass that provide the needed attributes.&lt;/p&gt;
5500
5501 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
5502 dnsdomain2 schemas. The latter is used for reverse entries like
5503 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
5504
5505 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
5506 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
5507 attributes) and domainrelatedobject (for associatedDomain). The use
5508 of structural object classes make it impossible to combine these
5509 classes with the object classes used by DHCP.&lt;/p&gt;
5510
5511 &lt;p&gt;There are other schemas that could be used too, for example the
5512 dnszone structural object class used by Gosa and bind-sdb for the DNS
5513 attributes combined with the domainrelatedobject object class, but in
5514 this case some unused attributes would have to be included as well
5515 (zonename and relativedomainname).&lt;/p&gt;
5516
5517 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
5518 mode and not use any of the existing objectclasses (dnsdomain,
5519 dnsdomain2 and dnszone) when one want to combine the DNS information
5520 with DHCP information, and instead create a auxiliary object class
5521 defined something like this (using the attributes defined for
5522 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
5523
5524 &lt;blockquote&gt;&lt;pre&gt;
5525 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
5526 SUP top
5527 AUXILIARY
5528 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
5529 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
5530 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
5531 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
5532 A6Record $ DNAMERecord
5533 ))
5534 &lt;/pre&gt;&lt;/blockquote&gt;
5535
5536 &lt;p&gt;This will allow any object to become a DNS entry when combined with
5537 the domainrelatedobject object class, and allow any entity to include
5538 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
5539 developers asking for their view on this schema and if they are
5540 interested in providing such schema with PowerDNS, and I hope my
5541 message will be accepted into their mailing list soon.&lt;/p&gt;
5542
5543 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
5544
5545 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
5546 the object attributes, and then uses the attributes it want. This
5547 make it harder to figure out exactly what attributes are used, but
5548 thanks to the working example in Debian Edu I can at least get an idea
5549 what is needed without having to read the source code.&lt;/p&gt;
5550
5551 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
5552 search filter to use to locate the correct dhcpServer entity is
5553 stored. These are the relevant entries from
5554 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
5555
5556 &lt;blockquote&gt;&lt;pre&gt;
5557 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
5558 ldap-dhcp-server-cn &quot;dhcp&quot;;
5559 &lt;/pre&gt;&lt;/blockquote&gt;
5560
5561 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
5562 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
5563 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
5564 search result is this entry:&lt;/p&gt;
5565
5566 &lt;blockquote&gt;&lt;pre&gt;
5567 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
5568 cn: dhcp
5569 objectClass: top
5570 objectClass: dhcpServer
5571 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5572 &lt;/pre&gt;&lt;/blockquote&gt;
5573
5574 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
5575 subtree with DHCP configuration. The DHCP configuration subtree base
5576 is located using a base scope search with base &quot;cn=DHCP
5577 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
5578 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
5579 The search result is this entry:&lt;/p&gt;
5580
5581 &lt;blockquote&gt;&lt;pre&gt;
5582 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5583 cn: DHCP Config
5584 objectClass: top
5585 objectClass: dhcpService
5586 objectClass: dhcpOptions
5587 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
5588 dhcpStatements: ddns-update-style none
5589 dhcpStatements: authoritative
5590 dhcpOption: smtp-server code 69 = array of ip-address
5591 dhcpOption: www-server code 72 = array of ip-address
5592 dhcpOption: wpad-url code 252 = text
5593 &lt;/pre&gt;&lt;/blockquote&gt;
5594
5595 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
5596 all the DHCP configuration is loaded, it is ready to receive requests.
5597 The subtree in Debian Edu contain objects with object classes
5598 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
5599 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
5600 and information about netmasks, dynamic range etc. Leaving out the
5601 details here because it is not relevant for the focus of my
5602 investigation, which is to see if it is possible to merge dns and dhcp
5603 related computer objects.&lt;/p&gt;
5604
5605 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
5606 of the client (00:00:00:00:00:00 in this example), using a subtree
5607 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
5608 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
5609 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
5610 like:&lt;/p&gt;
5611
5612 &lt;blockquote&gt;&lt;pre&gt;
5613 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5614 cn: hostname
5615 objectClass: top
5616 objectClass: dhcpHost
5617 dhcpHWAddress: ethernet 00:00:00:00:00:00
5618 dhcpStatements: fixed-address hostname
5619 &lt;/pre&gt;&lt;/blockquote&gt;
5620
5621 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
5622 The object classes need to have fixed names, and the configuration
5623 need to be stored in a fairly specific LDAP structure. On the
5624 positive side, the invidiual dhcpHost entires can be anywhere without
5625 the DN pointed to by the dhcpServer entries. The latter should make
5626 it possible to group all host entries in a subtree next to the
5627 configuration entries, and this subtree can also be shared with the
5628 DNS server if the schema proposed above is combined with the dhcpHost
5629 structural object class.
5630
5631 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
5632
5633 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
5634 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
5635 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
5636 allowing DNS objects to be stored anywhere under the base cn specified
5637 in the configuration.&lt;/p&gt;
5638
5639 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
5640 regarding which LDAP schemas to use and which LDAP structure to use.
5641 I guess one could implement ones own schema, as long as the
5642 objectclasses and attributes have the names used, but this do not
5643 really help when the DHCP subtree need to have a fairly fixed
5644 structure.&lt;/p&gt;
5645
5646 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
5647 this might work for Debian Edu:&lt;/p&gt;
5648
5649 &lt;blockquote&gt;&lt;pre&gt;
5650 ou=services
5651 cn=machine-info (dhcpService) - dhcpServiceDN points here
5652 cn=dhcp (dhcpServer)
5653 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
5654 cn=10.0.2.0 (dhcpSubnet)
5655 cn=group1 (dhcpGroup/dhcpOptions)
5656 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
5657 cn=192.168.0.0 (dhcpSubnet)
5658 cn=group1 (dhcpGroup/dhcpOptions)
5659 ou=machines - PowerDNS base points here
5660 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
5661 &lt;/pre&gt;&lt;/blockquote&gt;
5662
5663 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
5664 entries to be in the dhcpGroup subtrees, the entries can be stored
5665 there instead of a common machines subtree, and the PowerDNS base
5666 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
5667
5668 &lt;p&gt;The combined object under the machines subtree would look something
5669 like this:&lt;/p&gt;
5670
5671 &lt;blockquote&gt;&lt;pre&gt;
5672 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
5673 dc: hostname
5674 objectClass: top
5675 objectClass: dhcpHost
5676 objectclass: domainrelatedobject
5677 objectclass: dnsDomainAux
5678 associateddomain: hostname.intern
5679 arecord: 10.11.12.13
5680 dhcpHWAddress: ethernet 00:00:00:00:00:00
5681 dhcpStatements: fixed-address hostname.intern
5682 &lt;/pre&gt;&lt;/blockquote&gt;
5683
5684 &lt;/p&gt;One could even add the LTSP configuration associated with a given
5685 machine, as long as the required attributes are available in a
5686 auxiliary object class.&lt;/p&gt;
5687 </description>
5688 </item>
5689
5690 <item>
5691 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
5692 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
5693 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
5694 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
5695 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
5696 DHCP services in Debian Edu to use the same LDAP objects for a given
5697 computer, to avoid the possibility of having a inconsistent state for
5698 a computer in LDAP (as in DHCP but no DNS entry or the other way
5699 around) and make it easier to add computers to LDAP.&lt;/p&gt;
5700
5701 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
5702 information finally found a solution that seem to work.&lt;/p&gt;
5703
5704 &lt;p&gt;The old setup required three LDAP objects for a given computer.
5705 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
5706 we switch powerdns to use its strict LDAP method (ldap-method=strict
5707 in pdns-debian-edu.conf), the forward and reverse DNS entries are
5708 merged into one while making it impossible to transfer the reverse map
5709 to a slave DNS server.&lt;/p&gt;
5710
5711 &lt;p&gt;If we also replace the object class used to get the DNS related
5712 attributes to one allowing these attributes to be combined with the
5713 dhcphost object class, we can merge the DNS and DHCP entries into one.
5714 I&#39;ve written such object class in the dnsdomainaux.schema file (need
5715 proper OIDs, but that is a minor issue), and tested the setup. It
5716 seem to work.&lt;/p&gt;
5717
5718 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
5719 for both DNS and DHCP, and even the LTSP configuration I suggested in
5720 an earlier email. The combined LDAP object will look something like
5721 this:&lt;/p&gt;
5722
5723 &lt;blockquote&gt;&lt;pre&gt;
5724 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
5725 cn: hostname
5726 objectClass: dhcphost
5727 objectclass: domainrelatedobject
5728 objectclass: dnsdomainaux
5729 associateddomain: hostname.intern
5730 arecord: 10.11.12.13
5731 dhcphwaddress: ethernet 00:00:00:00:00:00
5732 dhcpstatements: fixed-address hostname
5733 ldapconfigsound: Y
5734 &lt;/pre&gt;&lt;/blockquote&gt;
5735
5736 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
5737 the DHCP server uses the dhcphwaddress and dhcpstatements entries
5738 before asking DNS to resolve the fixed-adddress. LTSP will use
5739 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
5740
5741 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
5742 dhcphost in a different location, to allow us to put the objects
5743 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
5744 that. If I can&#39;t figure out a way to do that, we can still get rid of
5745 the hosts subtree and move all its content into the DHCP Config tree
5746 (which probably should be renamed to be more related to the new
5747 content. I suspect cn=dnsdhcp,ou=services or something like that
5748 might be a good place to put it.&lt;/p&gt;
5749
5750 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
5751 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5752 </description>
5753 </item>
5754
5755 <item>
5756 <title>Idea for storing LTSP configuration in LDAP</title>
5757 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
5758 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
5759 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
5760 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
5761 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
5762 clients, and that this can be used to fetch configuration from LDAP if
5763 Debian Edu choose to store configuration there.&lt;/p&gt;
5764
5765 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
5766 to get configuration from LDAP. The idea is to look up the MAC
5767 address of the client in LDAP, and look for attributes on the form
5768 ltspconfigsetting=value, and use this to export SETTING=value to the
5769 LTSP clients.&lt;/p&gt;
5770
5771 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
5772 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
5773 allowing us to store all information about a computer in one place.&lt;/p&gt;
5774
5775 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
5776 this approach. A real LDAP schema for the ltspClientAux objectclass
5777 need to be written. Comments, suggestions, etc?&lt;/p&gt;
5778
5779 &lt;blockquote&gt;&lt;pre&gt;
5780 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
5781 #
5782 # Fetch LTSP client settings from LDAP based on MAC address
5783 #
5784 # Uses ethernet address as stored in the dhcpHost objectclass using
5785 # the dhcpHWAddress attribute or ethernet address stored in the
5786 # ieee802Device objectclass with the macAddress attribute.
5787 #
5788 # This module is written to be schema agnostic, and only depend on the
5789 # existence of attribute names.
5790 #
5791 # The LTSP configuration variables are saved directly using a
5792 # ltspConfig prefix and uppercasing the rest of the attribute name.
5793 # To set the SERVER variable, set the ltspConfigServer attribute.
5794 #
5795 # Some LDAP schema should be created with all the relevant
5796 # configuration settings. Something like this should work:
5797 #
5798 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
5799 # SUP top
5800 # AUXILIARY
5801 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
5802
5803 LDAPSERVER=$(debian-edu-ldapserver)
5804 if [ &quot;$LDAPSERVER&quot; ] ; then
5805 LDAPBASE=$(debian-edu-ldapserver -b)
5806 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
5807 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
5808 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
5809 grep &#39;^ltspConfig&#39; | while read attr value ; do
5810 # Remove prefix and convert to upper case
5811 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
5812 # bass value on to clients
5813 eval &quot;$attr=$value; export $attr&quot;
5814 done
5815 done
5816 fi
5817 &lt;/pre&gt;&lt;/blockquote&gt;
5818
5819 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
5820 the while block might end up in a subshell causing the variables set
5821 there to not show up in ltsp-config, but if that is the case I am sure
5822 the code can be restructured to make sure the variables are passed on.
5823 I expect that can be solved with some testing. :)&lt;/p&gt;
5824
5825 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
5826 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5827
5828 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
5829 configuration in LDAP that was created around year 2000 by
5830 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
5831 Xperience, Inc., 2000&lt;/a&gt;. I found its
5832 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
5833 personal home page over at redhat.com.&lt;/p&gt;
5834 </description>
5835 </item>
5836
5837 <item>
5838 <title>jXplorer, a very nice LDAP GUI</title>
5839 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
5840 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
5841 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
5842 <description>&lt;p&gt;Since
5843 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
5844 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
5845 LDAP GUI that is even better than luma. The java application
5846 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
5847 moving LDAP objects and subtrees using drag-and-drop, and can
5848 authenticate using Kerberos. I have only tested the Kerberos
5849 authentication, but do not have a LDAP setup allowing me to rewrite
5850 LDAP with my test user yet. It is
5851 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
5852 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
5853 have with it is how it handle errors. If something go wrong, its
5854 non-intuitive behaviour require me to go through some query work list
5855 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
5856 </description>
5857 </item>
5858
5859 <item>
5860 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
5861 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
5862 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
5863 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
5864 <description>&lt;p&gt;Here is a short update on my &lt;a
5865 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
5866 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
5867 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
5868 not reporting the status for KDE, because the upgrade crashes when
5869 aptitude try because of missing conflicts
5870 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
5871 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
5872
5873 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
5874 complete list of the installed packages. Based on this I see these
5875 differences when I did a test run today. As usual, I do not really
5876 know what the correct set of packages would be, but thought it best to
5877 publish the difference.&lt;/p&gt;
5878
5879 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
5880
5881 &lt;blockquote&gt;&lt;p&gt;
5882 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
5883 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
5884 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
5885 libgtksourceview-common libpt-1.10.10-plugins-alsa
5886 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
5887 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
5888 python-4suite-xml python-eggtrayicon python-gtkhtml2
5889 python-gtkmozembed svgalibg1 xserver-xephyr zip
5890 &lt;/p&gt;&lt;/blockquote&gt;
5891
5892 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
5893
5894 &lt;blockquote&gt;&lt;p&gt;
5895 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
5896 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
5897 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
5898 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
5899 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
5900 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
5901 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
5902 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
5903 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
5904 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
5905 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
5906 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
5907 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
5908 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
5909 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
5910 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
5911 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
5912 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
5913 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
5914 mysql-common swfdec-gnome totem-gstreamer wodim
5915 &lt;/p&gt;&lt;/blockquote&gt;
5916
5917 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
5918
5919 &lt;blockquote&gt;&lt;p&gt;
5920 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
5921 python-gnomekeyring python-wnck rhythmbox-plugins xorg
5922 xserver-xorg-input-all xserver-xorg-input-evdev
5923 xserver-xorg-input-kbd xserver-xorg-input-mouse
5924 xserver-xorg-input-synaptics xserver-xorg-video-all
5925 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
5926 xserver-xorg-video-chips xserver-xorg-video-cirrus
5927 xserver-xorg-video-dummy xserver-xorg-video-fbdev
5928 xserver-xorg-video-glint xserver-xorg-video-i128
5929 xserver-xorg-video-i740 xserver-xorg-video-mach64
5930 xserver-xorg-video-mga xserver-xorg-video-neomagic
5931 xserver-xorg-video-nouveau xserver-xorg-video-nv
5932 xserver-xorg-video-r128 xserver-xorg-video-radeon
5933 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
5934 xserver-xorg-video-s3 xserver-xorg-video-s3virge
5935 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
5936 xserver-xorg-video-sis xserver-xorg-video-sisusb
5937 xserver-xorg-video-tdfx xserver-xorg-video-tga
5938 xserver-xorg-video-trident xserver-xorg-video-tseng
5939 xserver-xorg-video-vesa xserver-xorg-video-vmware
5940 xserver-xorg-video-voodoo
5941 &lt;/p&gt;&lt;/blockquote&gt;
5942
5943 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
5944
5945 &lt;blockquote&gt;&lt;p&gt;
5946 deskbar-applet xserver-xorg xserver-xorg-core
5947 xserver-xorg-input-wacom xserver-xorg-video-intel
5948 xserver-xorg-video-openchrome
5949 &lt;/p&gt;&lt;/blockquote&gt;
5950
5951 &lt;p&gt;I was told on IRC that the xorg-xserver package was
5952 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
5953 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
5954 No idea when it hits Squeeze, but when it does I hope it will reduce
5955 the difference somewhat.
5956 </description>
5957 </item>
5958
5959 <item>
5960 <title>LUMA, a very nice LDAP GUI</title>
5961 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
5962 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
5963 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
5964 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
5965 directory in Debian Edu, and in the process I started to miss a GUI
5966 tool to browse the LDAP tree. The only one I was able to find in
5967 Debian/Squeeze and Lenny is
5968 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
5969 be a great tool to get a overview of the current LDAP directory
5970 populated by default in Skolelinux. Thanks to it, I have been able to
5971 find empty and obsolete subtrees, misplaced objects and duplicate
5972 objects. It will be installed by default in Debian/Squeeze. If you
5973 are working with LDAP, give it a go. :)&lt;/p&gt;
5974
5975 &lt;p&gt;I did notice one problem with it I have not had time to report to
5976 the BTS yet. There is no .desktop file in the package, so the tool do
5977 not show up in the Gnome and KDE menus, but only deep down in in the
5978 Debian submenu in KDE. I hope that can be fixed before Squeeze is
5979 released.&lt;/p&gt;
5980
5981 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
5982 like to move objects and remove subtrees directly in the GUI, but have
5983 not found a way to do that with LUMA yet. So in the mean time, I use
5984 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
5985
5986 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
5987 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
5988
5989 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
5990 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
5991 useful GUI alternative. It seem like a good tool, but is unmaintained
5992 in Debian and got a RC bug keeping it out of Squeeze. Unless that
5993 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
5994 </description>
5995 </item>
5996
5997 <item>
5998 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
5999 <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>
6000 <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>
6001 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
6002 <description>&lt;p&gt;A while back, I
6003 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
6004 about the fact&lt;/a&gt; that it is not possible with the provided schemas
6005 for storing DNS and DHCP information in LDAP to combine the two sets
6006 of information into one LDAP object representing a computer.&lt;/p&gt;
6007
6008 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
6009 the dhcpHost object class auxiliary, to allow it to be combined with
6010 the dNSDomain object class, and thus forming one object for one
6011 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
6012
6013 &lt;p&gt;If I understand this correctly, it is not safe to do this change
6014 without also changing the assigned number for the object class, and I
6015 do not know enough about LDAP schema design to do that properly for
6016 Debian Edu.&lt;/p&gt;
6017
6018 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
6019 the
6020 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
6021 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
6022 available today from IETF.&lt;/p&gt;
6023
6024 &lt;pre&gt;
6025 --- dhcp.schema (revision 65192)
6026 +++ dhcp.schema (working copy)
6027 @@ -376,7 +376,7 @@
6028 objectclass ( 2.16.840.1.113719.1.203.6.6
6029 NAME &#39;dhcpHost&#39;
6030 DESC &#39;This represents information about a particular client&#39;
6031 - SUP top
6032 + SUP top AUXILIARY
6033 MUST cn
6034 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
6035 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
6036 &lt;/pre&gt;
6037
6038 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
6039 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
6040 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
6041
6042 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
6043 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
6044 </description>
6045 </item>
6046
6047 <item>
6048 <title>Calling tasksel like the installer, while still getting useful output</title>
6049 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
6050 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
6051 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
6052 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
6053 installs packages during the normal debian-installer run. Until now,
6054 I have ended up letting tasksel do the work, with the annoying problem
6055 of not getting any feedback at all when something fails (like a
6056 conffile question from dpkg or a download that fails), using code like
6057 this:
6058
6059 &lt;blockquote&gt;&lt;pre&gt;
6060 export DEBIAN_FRONTEND=noninteractive
6061 tasksel --new-install
6062 &lt;/pre&gt;&lt;/blockquote&gt;
6063
6064 This would invoke tasksel, let its automatic task selection pick the
6065 tasks to install, and continue to install the requested tasks without
6066 any output what so ever.
6067
6068 Recently I revisited this problem while working on the automatic
6069 package upgrade testing, because tasksel would some times hang without
6070 any useful feedback, and I want to see what is going on when it
6071 happen. Then it occured to me, I can parse the output from tasksel
6072 when asked to run in test mode, and use that aptitude command line
6073 printed by tasksel then to simulate the tasksel run. I ended up using
6074 code like this:
6075
6076 &lt;blockquote&gt;&lt;pre&gt;
6077 export DEBIAN_FRONTEND=noninteractive
6078 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
6079 $cmd
6080 &lt;/pre&gt;&lt;/blockquote&gt;
6081
6082 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
6083 --without-recommends -o APT::Install-Recommends=no -y install
6084 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
6085 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
6086 laptop task and all packages with priority standard , required and
6087 important, just like tasksel would have done it during
6088 installation.&lt;/p&gt;
6089
6090 &lt;p&gt;A better approach is probably to extend tasksel to be able to
6091 install packages without using debconf-apt-progress, for use cases
6092 like this.&lt;/p&gt;
6093 </description>
6094 </item>
6095
6096 <item>
6097 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
6098 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
6099 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
6100 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
6101 <description>&lt;p&gt;My
6102 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
6103 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
6104 finally made the upgrade logs available from
6105 &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;.
6106 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
6107 apt and aptitude, and found their differences interesting. This time
6108 I will only focus on their removal plans.&lt;/p&gt;
6109
6110 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
6111 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
6112 surprising part is that it want to remove xorg and all
6113 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
6114 sure why. When asking aptitude to do the same, it want to remove 129
6115 packages, but most of them are library packages I suspect are no
6116 longer needed. Both of them want to remove bluetooth packages, which
6117 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
6118
6119 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
6120 which seem like a bad idea and xorg the same way as with Gnome. Asking
6121 aptitude for the same, it wants to remove 192 packages, none which are
6122 too surprising.&lt;/p&gt;
6123
6124 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
6125 and avoided, and perhaps others as well. Here are the complete list
6126 of planned removals. The complete logs is available from the URL
6127 above. Note if you want to repeat these tests, that the upgrade test
6128 for kde+apt-get hung in the tasksel setup because of dpkg asking
6129 conffile questions. No idea why. I worked around it by using
6130 &#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
6131 continue.&lt;/p&gt;
6132
6133 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
6134 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
6135 gnome-desktop-environment gnome-network-admin gtkhtml3.14
6136 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
6137 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
6138 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
6139 serpentine swfdec-mozilla update-manager xorg xserver-xorg
6140 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6141 xserver-xorg-input-kbd xserver-xorg-input-mouse
6142 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6143 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6144 xserver-xorg-video-ati xserver-xorg-video-chips
6145 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6146 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6147 xserver-xorg-video-glint xserver-xorg-video-i128
6148 xserver-xorg-video-i740 xserver-xorg-video-imstt
6149 xserver-xorg-video-intel xserver-xorg-video-mach64
6150 xserver-xorg-video-mga xserver-xorg-video-neomagic
6151 xserver-xorg-video-nsc xserver-xorg-video-nv
6152 xserver-xorg-video-openchrome xserver-xorg-video-r128
6153 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6154 xserver-xorg-video-rendition xserver-xorg-video-s3
6155 xserver-xorg-video-s3virge xserver-xorg-video-savage
6156 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6157 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6158 xserver-xorg-video-tga xserver-xorg-video-trident
6159 xserver-xorg-video-tseng xserver-xorg-video-v4l
6160 xserver-xorg-video-vesa xserver-xorg-video-vga
6161 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
6162 xulrunner-1.9-gnome-support&lt;/p&gt;
6163
6164 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
6165
6166 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
6167 djvulibre-desktop finger gnome-app-install gnome-mount
6168 gnome-network-admin gnome-spell gnome-vfs-obexftp
6169 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
6170 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
6171 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
6172 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
6173 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
6174 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
6175 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
6176 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
6177 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
6178 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
6179 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
6180 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
6181 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
6182 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
6183 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
6184 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
6185 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
6186 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
6187 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
6188 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
6189 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
6190 openoffice.org-writer2latex openssl-blacklist p7zip
6191 python-4suite-xml python-eggtrayicon python-gnome2-desktop
6192 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
6193 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
6194 swfdec-mozilla totem-gstreamer update-manager wodim
6195 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6196 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6197 zip&lt;/p&gt;
6198
6199 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
6200
6201 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
6202 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
6203 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
6204 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
6205 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
6206 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
6207 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
6208 xserver-xorg-input-kbd xserver-xorg-input-mouse
6209 xserver-xorg-input-synaptics xserver-xorg-input-wacom
6210 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
6211 xserver-xorg-video-ati xserver-xorg-video-chips
6212 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
6213 xserver-xorg-video-dummy xserver-xorg-video-fbdev
6214 xserver-xorg-video-glint xserver-xorg-video-i128
6215 xserver-xorg-video-i740 xserver-xorg-video-imstt
6216 xserver-xorg-video-intel xserver-xorg-video-mach64
6217 xserver-xorg-video-mga xserver-xorg-video-neomagic
6218 xserver-xorg-video-nsc xserver-xorg-video-nv
6219 xserver-xorg-video-openchrome xserver-xorg-video-r128
6220 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
6221 xserver-xorg-video-rendition xserver-xorg-video-s3
6222 xserver-xorg-video-s3virge xserver-xorg-video-savage
6223 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
6224 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
6225 xserver-xorg-video-tga xserver-xorg-video-trident
6226 xserver-xorg-video-tseng xserver-xorg-video-v4l
6227 xserver-xorg-video-vesa xserver-xorg-video-vga
6228 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
6229
6230 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
6231 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
6232 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
6233 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
6234 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
6235 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
6236 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
6237 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
6238 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
6239 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
6240 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
6241 kghostview khelpcenter khexedit kiconedit kitchensync klatin
6242 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
6243 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
6244 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
6245 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
6246 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
6247 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
6248 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
6249 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
6250 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
6251 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
6252 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
6253 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
6254 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
6255 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
6256 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
6257 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
6258 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
6259 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
6260 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
6261 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
6262 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
6263 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
6264 texlive-common texlive-doc-base texlive-fonts-recommended
6265 xserver-xorg-video-cyrix xserver-xorg-video-imstt
6266 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
6267 xulrunner-1.9&lt;/p&gt;
6268
6269 </description>
6270 </item>
6271
6272 <item>
6273 <title>Automatic upgrade testing from Lenny to Squeeze</title>
6274 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
6275 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
6276 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
6277 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
6278 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
6279 have been discovered and reported in the process
6280 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
6281 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
6282 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
6283 kdebase-workspace-data), and to get a more regular testing going on, I
6284 am working on a script to automate the test.&lt;/p&gt;
6285
6286 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
6287 Gnome or KDE desktop installation inside the chroot before upgrading
6288 it. To ensure no services are started in the chroot, a policy-rc.d
6289 script is inserted. To make sure tasksel believe it is to install a
6290 desktop on a laptop, the tasksel tests are replaced in the chroot
6291 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
6292
6293 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
6294 currently always fail because udev refuses to upgrade with the kernel
6295 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
6296 is created. The bug report
6297 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
6298 this problem do not trigger in a chroot, but I touch the file anyway
6299 to make sure the upgrade go well. Testing on virtual and real
6300 hardware have failed me because of udev so far, and creating this file
6301 do the trick in such settings anyway. This is a
6302 &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
6303 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
6304 maintainer because he lack the resources to rewrite udev to keep
6305 working with old kernels or something like that. I really wish the
6306 udev upstream would keep udev backwards compatible, to avoid such
6307 upgrade problem, but given that they fail to do so, I guess
6308 documenting the way out of this mess is the best option we got for
6309 Debian Squeeze.&lt;/p&gt;
6310
6311 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
6312 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
6313 trick:&lt;/p&gt;
6314
6315 &lt;blockquote&gt;&lt;pre&gt;
6316 #!/bin/sh
6317 set -ex
6318
6319 if [ &quot;$1&quot; ] ; then
6320 desktop=$1
6321 else
6322 desktop=gnome
6323 fi
6324
6325 from=lenny
6326 to=squeeze
6327
6328 exec &amp;lt; /dev/null
6329 unset LANG
6330 mirror=http://ftp.skolelinux.org/debian
6331 tmpdir=chroot-$from-upgrade-$to-$desktop
6332 fuser -mv .
6333 debootstrap $from $tmpdir $mirror
6334 chroot $tmpdir aptitude update
6335 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
6336 #!/bin/sh
6337 exit 101
6338 EOF
6339 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
6340 exit_cleanup() {
6341 umount $tmpdir/proc
6342 }
6343 mount -t proc proc $tmpdir/proc
6344 # Make sure proc is unmounted also on failure
6345 trap exit_cleanup EXIT INT
6346
6347 chroot $tmpdir aptitude -y install debconf-utils
6348
6349 # Make sure tasksel autoselection trigger. It need the test scripts
6350 # to return the correct answers.
6351 echo tasksel tasksel/desktop multiselect $desktop | \
6352 chroot $tmpdir debconf-set-selections
6353
6354 # Include the desktop and laptop task
6355 for test in desktop laptop ; do
6356 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
6357 #!/bin/sh
6358 exit 2
6359 EOF
6360 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
6361 done
6362
6363 DEBIAN_FRONTEND=noninteractive
6364 DEBIAN_PRIORITY=critical
6365 export DEBIAN_FRONTEND DEBIAN_PRIORITY
6366 chroot $tmpdir tasksel --new-install
6367
6368 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
6369 chroot $tmpdir aptitude update
6370 touch $tmpdir/etc/udev/kernel-upgrade
6371 chroot $tmpdir aptitude -y dist-upgrade
6372 fuser -mv
6373 &lt;/pre&gt;&lt;/blockquote&gt;
6374
6375 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
6376 with aptitude, but I have not had time to look at how they behave
6377 differently so far. I hope to get a cron job running to do the test
6378 regularly and post the result on the web. The Gnome upgrade currently
6379 work, while the KDE upgrade fail because of the bug in
6380 kdebase-workspace-data&lt;/p&gt;
6381
6382 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
6383 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
6384 post, so I will refrain from trying. I can report that for Gnome,
6385 aptitude report 760 packages upgraded, 448 newly installed, 129 to
6386 remove and 1 not upgraded and 1024MB need to be downloaded while for
6387 KDE the same numbers are 702 packages upgraded, 507 newly installed,
6388 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
6389
6390 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
6391 is able to migrate to dependency based boot sequencing and parallel
6392 booting without a hitch. Was unsure if there were still bugs with
6393 packages failing to clean up their obsolete init.d script during
6394 upgrades, and no such problem seem to affect the Gnome desktop+laptop
6395 packages.&lt;/p&gt;
6396 </description>
6397 </item>
6398
6399 <item>
6400 <title>Upstart or sysvinit - as init.d scripts see it</title>
6401 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
6402 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
6403 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
6404 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
6405 scripts to migrate (some of) their operations to upstart job while
6406 keeping the init.d for hurd and kfreebsd. The packages with such
6407 needs will need a way to get their init.d scripts to behave
6408 differently when used with sysvinit and with upstart. Because of
6409 this, I had a look at the environment variables set when a init.d
6410 script is running under upstart, and when it is not.&lt;/p&gt;
6411
6412 &lt;p&gt;With upstart, I notice these environment variables are set when a
6413 script is started from rcS.d/ (ignoring some irrelevant ones like
6414 COLUMNS):&lt;/p&gt;
6415
6416 &lt;blockquote&gt;&lt;pre&gt;
6417 DEFAULT_RUNLEVEL=2
6418 previous=N
6419 PREVLEVEL=
6420 RUNLEVEL=
6421 runlevel=S
6422 UPSTART_EVENTS=startup
6423 UPSTART_INSTANCE=
6424 UPSTART_JOB=rc-sysinit
6425 &lt;/pre&gt;&lt;/blockquote&gt;
6426
6427 &lt;p&gt;With sysvinit, these environment variables are set for the same
6428 script.&lt;/p&gt;
6429
6430 &lt;blockquote&gt;&lt;pre&gt;
6431 INIT_VERSION=sysvinit-2.88
6432 previous=N
6433 PREVLEVEL=N
6434 RUNLEVEL=S
6435 runlevel=S
6436 &lt;/pre&gt;&lt;/blockquote&gt;
6437
6438 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
6439 sysvinit are not set by upstart. Not sure if it is intentional or not
6440 to not be compatible with sysvinit in this regard.&lt;/p&gt;
6441
6442 &lt;p&gt;For scripts needing to behave differently when upstart is used,
6443 looking for the UPSTART_JOB environment variable seem to be a good
6444 choice.&lt;/p&gt;
6445 </description>
6446 </item>
6447
6448 <item>
6449 <title>A manual for standards wars...</title>
6450 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
6451 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
6452 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
6453 <description>&lt;p&gt;Via the
6454 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
6455 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
6456 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
6457 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
6458 following the standards wars of today.&lt;/p&gt;
6459 </description>
6460 </item>
6461
6462 <item>
6463 <title>Sitesummary tip: Listing computer hardware models used at site</title>
6464 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
6465 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
6466 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
6467 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
6468 to get a list of the machine types in use thanks to the DMI
6469 information extracted from each machine. The script to do so is
6470 included in the sitesummary package, and here is example output from
6471 the Skolelinux build servers:&lt;/p&gt;
6472
6473 &lt;blockquote&gt;&lt;pre&gt;
6474 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
6475 vendor count
6476 Dell Computer Corporation 1
6477 PowerEdge 1750 1
6478 IBM 1
6479 eserver xSeries 345 -[8670M1X]- 1
6480 Intel 2
6481 [no-dmi-info] 3
6482 maintainer:~#
6483 &lt;/pre&gt;&lt;/blockquote&gt;
6484
6485 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
6486 provided in each machine. Here there are Intel machines without model
6487 information listed with Intel as vendor and no model, and virtual Xen
6488 machines listed as [no-dmi-info]. One can add -l as a command line
6489 option to list the individual machines.&lt;/p&gt;
6490
6491 &lt;p&gt;A larger list is
6492 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
6493 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
6494 provide the basic sitesummary report publicly. In their report there
6495 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
6496 their machines, and as sitesummary is available in both distributions,
6497 it is trivial to get all of them to report to the same central
6498 collector.&lt;/p&gt;
6499 </description>
6500 </item>
6501
6502 <item>
6503 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
6504 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
6505 <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>
6506 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
6507 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
6508 start at boot when an NVidia video card is used is handled. The
6509 problem seem to be that the nvidia X.org driver uses a long time to
6510 initialize, and this duration is longer than kdm is configured to
6511 wait.&lt;/p&gt;
6512
6513 &lt;p&gt;I came across two bugs related to this issue,
6514 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
6515 against initscripts and passed on to nvidia-glx when it became obvious
6516 that the nvidia drivers were involved, and
6517 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
6518 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
6519
6520 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
6521 problem nvidia video card owners experience and make sure the Debian
6522 distribution work out of the box for these users. The nvidia driver
6523 maintainers expect kdm to be set up to wait longer, while kdm expect
6524 the nvidia driver maintainers to fix the driver to start faster, and
6525 while they wait for each other I guess the users end up switching to a
6526 distribution that work for them. I have no idea what the solution is,
6527 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
6528
6529 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
6530 </description>
6531 </item>
6532
6533 <item>
6534 <title>Parallellized boot seem to hold up well in Debian/testing</title>
6535 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
6536 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
6537 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
6538 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
6539 The feature seem to hold up pretty well, but three fairly serious
6540 issues are known and should be solved:
6541
6542 &lt;p&gt;&lt;ul&gt;
6543
6544 &lt;li&gt;The wicd package seen to
6545 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
6546 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
6547 parallel booting is enabled. No idea why, but the wicd maintainer
6548 seem to be on the case.&lt;/li&gt;
6549
6550 &lt;li&gt;The nvidia X driver seem to
6551 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
6552 triggered more easily when parallel booting is in effect. The
6553 maintainer is on the case.&lt;/li&gt;
6554
6555 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
6556 sequencing (the shutdown is broken) when old file-rc users
6557 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
6558 sysv-rc. One way to solve it would be for file-rc to create
6559 /etc/init.d/.legacy-bootordering, and another is to try to make
6560 sysv-rc more robust. Will investigate some more and probably upload a
6561 workaround in sysv-rc to help those trying to move from file-rc to
6562 sysv-rc get a working shutdown.&lt;/li&gt;
6563
6564 &lt;/ul&gt;&lt;/p&gt;
6565
6566 &lt;p&gt;All in all not many surprising issues, and all of them seem
6567 solvable before Squeeze is released. In addition to these there are
6568 some packages with bugs in their dependencies and run level settings,
6569 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
6570
6571 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6572 the BTS, please usertag the report to get it to show up at
6573 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6574 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6575
6576 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
6577 </description>
6578 </item>
6579
6580 <item>
6581 <title>More flexible firmware handling in debian-installer</title>
6582 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
6583 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
6584 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
6585 <description>&lt;p&gt;After a long break from debian-installer development, I finally
6586 found time today to return to the project. Having to spend less time
6587 working dependency based boot in debian, as it is almost complete now,
6588 definitely helped freeing some time.&lt;/p&gt;
6589
6590 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
6591 include some firmware packages on the Debian Edu CDs, those needed to
6592 get disk and network controllers working. Without having these
6593 firmware packages available during installation, it is impossible to
6594 install Debian Edu on the given machine, and because our target group
6595 are non-technical people, asking them to provide firmware packages on
6596 an external medium is a support pain. Initially, I expected it to be
6597 enough to include the firmware packages on the CD to get
6598 debian-installer to find and use them. This proved to be wrong.
6599 Next, I hoped it was enough to symlink the relevant firmware packages
6600 to some useful location on the CD (tried /cdrom/ and
6601 /cdrom/firmware/). This also proved to not work, and at this point I
6602 found time to look at the debian-installer code to figure out what was
6603 going to work.&lt;/p&gt;
6604
6605 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
6606 look revealed that it would only look for firmware packages outside
6607 the installation media, so the CD was never checked for firmware
6608 packages. It would only check USB sticks, floppies and other
6609 &quot;external&quot; media devices. Today I changed it to also look in the
6610 /cdrom/firmware/ directory on the mounted CD or DVD, which should
6611 solve the problem I ran into with Debian edu. I also changed it to
6612 look in /firmware/, to make sure the installer also find firmware
6613 provided in the initrd when booting the installer via PXE, to allow us
6614 to provide the same feature in the PXE setup included in Debian
6615 Edu.&lt;/p&gt;
6616
6617 &lt;p&gt;To make sure firmware deb packages with a license questions are not
6618 activated without asking if the license is accepted, I extended
6619 hw-detect to look for preinst scripts in the firmware packages, and
6620 run these before activating the firmware during installation. The
6621 license question is asked using debconf in the preinst, so this should
6622 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
6623
6624 &lt;p&gt;If you want to discuss the details of these features, please
6625 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
6626 </description>
6627 </item>
6628
6629 <item>
6630 <title>Parallellized boot is now the default in Debian/unstable</title>
6631 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
6632 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
6633 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
6634 <description>&lt;p&gt;Since this evening, parallel booting is the default in
6635 Debian/unstable for machines using dependency based boot sequencing.
6636 Apparently the testing of concurrent booting has been wider than
6637 expected, if I am to believe the
6638 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6639 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
6640 with the feature this weekend, to give us some time to detect any
6641 remaining problems before Squeeze is frozen. If serious problems are
6642 detected, it is simple to change the default back to sequential boot.
6643 The upload of the new sysvinit package also activate a new upstream
6644 version.&lt;/p&gt;
6645
6646 More information about
6647 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6648 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
6649 currently possible to disable parallel booting when one run into
6650 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
6651
6652 &lt;blockquote&gt;&lt;pre&gt;
6653 CONCURRENCY=none
6654 &lt;/pre&gt;&lt;/blockquote&gt;
6655
6656 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6657 the BTS, please usertag the report to get it to show up at
6658 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6659 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6660 </description>
6661 </item>
6662
6663 <item>
6664 <title>Sitesummary tip: Listing MAC address of all clients</title>
6665 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
6666 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
6667 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
6668 <description>&lt;p&gt;In the recent Debian Edu versions, the
6669 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
6670 system&lt;/a&gt; is used to keep track of the machines in the school
6671 network. Each machine will automatically report its status to the
6672 central server after boot and once per night. The network setup is
6673 also reported, and using this information it is possible to get the
6674 MAC address of all network interfaces in the machines. This is useful
6675 to update the DHCP configuration.&lt;/p&gt;
6676
6677 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
6678 ist all MAC addresses of all machines reporting to sitesummary. Run
6679 this on the collector host:&lt;/p&gt;
6680
6681 &lt;blockquote&gt;&lt;pre&gt;
6682 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
6683 &lt;/pre&gt;&lt;/blockquote&gt;
6684
6685 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
6686 line per machine and with space between the MAC addresses.&lt;/p&gt;
6687
6688 &lt;p&gt;To allow system administrators easier job at adding static DHCP
6689 addresses for hosts, it would be possible to extend this to fetch
6690 machine information from sitesummary and update the DHCP and DNS
6691 tables in LDAP using this information. Such tool is unfortunately not
6692 written yet.&lt;/p&gt;
6693 </description>
6694 </item>
6695
6696 <item>
6697 <title>systemd, an interesting alternative to upstart</title>
6698 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
6699 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
6700 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
6701 <description>&lt;p&gt;The last few days a new boot system called
6702 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
6703 has been
6704 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
6705
6706 to the free software world. I have not yet had time to play around
6707 with it, but it seem to be a very interesting alternative to
6708 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
6709 a good alternative for Debian when we are able to switch to an event
6710 based boot system. Tollef is
6711 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
6712 systemd into Debian, and I look forward to seeing how well it work. I
6713 like the fact that systemd handles init.d scripts with dependency
6714 information natively, allowing them to run in parallel where upstart
6715 at the moment do not.&lt;/p&gt;
6716
6717 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
6718 platform support. It only work on recent Linux kernels, and also need
6719 some new kernel features enabled to function properly. This means
6720 kFreeBSD and Hurd ports of Debian will need a port or a different boot
6721 system. Not sure how that will be handled if systemd proves to be the
6722 way forward.&lt;/p&gt;
6723
6724 &lt;p&gt;In the mean time, based on the
6725 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
6726 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
6727 decided to enable full parallel booting as the default in Debian as
6728 soon as possible (probably this weekend or early next week), to see if
6729 there are any remaining serious bugs in the init.d dependencies. A
6730 new version of the sysvinit package implementing this change is
6731 already in experimental. If all go well, Squeeze will be released
6732 with parallel booting enabled by default.&lt;/p&gt;
6733 </description>
6734 </item>
6735
6736 <item>
6737 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
6738 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
6739 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
6740 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
6741 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
6742 complete, so complete that it is actually possible to run all the
6743 init.d scripts in parallell based on these dependencies. If you want
6744 to test your Squeeze system, make sure
6745 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6746 based boot sequencing&lt;/a&gt; is enabled, and add this line to
6747 /etc/default/rcS:&lt;/p&gt;
6748
6749 &lt;blockquote&gt;&lt;pre&gt;
6750 CONCURRENCY=makefile
6751 &lt;/pre&gt;&lt;/blockquote&gt;
6752
6753 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
6754 scripts in parallel using the dependency information stored in
6755 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
6756 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
6757 to try to start the kdm and gdm scripts as early as possible, and will
6758 start the facilities required by kdm or gdm as early as possible to
6759 make this happen.&lt;/p&gt;
6760
6761 &lt;p&gt;Give it a try, and see if you like the result. If some services
6762 fail to start properly, it is most likely because they have incomplete
6763 init.d script dependencies in their startup script (or some of their
6764 dependent scripts have incomplete dependencies). Report bugs and get
6765 the package maintainers to fix it. :)&lt;/p&gt;
6766
6767 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
6768 manage to get the init.d script dependencies complete and correct. I
6769 expect we will get there in Squeeze+1, if we get manage to test and
6770 fix the remaining issues.&lt;/p&gt;
6771
6772 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
6773 the BTS, please usertag the report to get it to show up at
6774 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
6775 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
6776 </description>
6777 </item>
6778
6779 <item>
6780 <title>Debian has switched to dependency based boot sequencing</title>
6781 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
6782 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
6783 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
6784 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
6785 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
6786 have been migrated to using dependency based boot sequencing. This
6787 conclude work me and others have been doing for the last three days.
6788 It feels great to see this finally part of the default Debian
6789 installation. Now we just need to weed out the last few problems that
6790 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
6791
6792 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
6793 fixing the more fundamental problem of handing the event based
6794 non-predictable kernel in the early boot.&lt;/p&gt;
6795 </description>
6796 </item>
6797
6798 <item>
6799 <title>Taking over sysvinit development</title>
6800 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
6801 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
6802 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
6803 <description>&lt;p&gt;After several years of frustration with the lack of activity from
6804 the existing sysvinit upstream developer, I decided a few weeks ago to
6805 take over the package and become the new upstream. The number of
6806 patches to track for the Debian package was becoming a burden, and the
6807 lack of synchronization between the distribution made it hard to keep
6808 the package up to date.&lt;/p&gt;
6809
6810 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
6811 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
6812 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
6813 and Fedora), based on the patches currently in use in these
6814 distributions. We Debian maintainers plan to move to this tarball as
6815 the new upstream as soon as we find time to do the merge. Since the
6816 new tarball was created, we agreed with Werner at SuSe to make a new
6817 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
6818 development there. The project is registered and currently waiting
6819 for approval by the Savannah administrators, and as soon as it is
6820 approved, we will import the old versions from svn and continue
6821 working on the future release.&lt;/p&gt;
6822
6823 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
6824 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
6825 </description>
6826 </item>
6827
6828 <item>
6829 <title>Debian boots quicker and quicker</title>
6830 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
6831 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
6832 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
6833 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
6834 people involved in the boot system on Debian and Ubuntu, to see if we
6835 could find more ways to speed up the boot system. This was an Ubuntu
6836 funded
6837 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
6838 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
6839 of boot systems, and ways to handle the increasing number of boot
6840 issues introduced by the Linux kernel becoming more and more
6841 asynchronous and event base. The Ubuntu approach using udev and
6842 upstart might be a good way forward. Time will show.&lt;/p&gt;
6843
6844 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
6845 process in Debian. All of these should be applied to get a quick
6846 boot:&lt;/p&gt;
6847
6848 &lt;ul&gt;
6849
6850 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
6851
6852 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
6853 clock is in UTC.&lt;/li&gt;
6854
6855 &lt;li&gt;Install and activate the insserv package to enable
6856 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
6857 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
6858
6859 &lt;/ul&gt;
6860
6861 These points are based on the Google summer of code work done by
6862 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
6863 Villegas&lt;/a&gt;.
6864
6865 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
6866 unstable yesterday. When we tested it, we were able to cut 6 seconds
6867 from the boot sequence. It depend on very correct dependency
6868 declaration in all init.d scripts, so I expect us to find edge cases
6869 where the dependences in some scripts are slightly wrong when we start
6870 using this.&lt;/p&gt;
6871
6872 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
6873 introduced by Raphael Geissert today, one that could affect the
6874 startup speed as well. Instead of starting some scripts concurrently
6875 from rcS.d/ and another set of scripts from rc2.d/, it would be
6876 possible to run a of them in the same process. A quick way to test
6877 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
6878 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
6879 </description>
6880 </item>
6881
6882 <item>
6883 <title>BSAs påstander om piratkopiering møter motstand</title>
6884 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
6885 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
6886 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
6887 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
6888 programvareselskapene som Microsoft og Apple, publisert en rapport der
6889 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
6890 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
6891 dager siden kom
6892 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
6893 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
6894 dagene. Et spesielt interessant kommentar fra Sverige,
6895 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
6896 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
6897
6898 &lt;blockquote&gt;
6899 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
6900 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
6901 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
6902 exakta&quot;, säger BSAs Sverigechef John Hugosson.
6903 &lt;/blockquote&gt;
6904
6905 &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
6906 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
6907 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
6908 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
6909 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
6910
6911 &lt;p&gt;Fant lenkene via &lt;a
6912 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
6913 på Slashdot&lt;/a&gt;.&lt;/p&gt;
6914 </description>
6915 </item>
6916
6917 <item>
6918 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
6919 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
6920 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
6921 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
6922 <description>&lt;p&gt;Kom over
6923 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
6924 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
6925 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
6926 jobber til daglig. En rask opptelling forteller meg at vi har 490
6927 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
6928 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
6929 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
6930 </description>
6931 </item>
6932
6933 <item>
6934 <title>Kryptert harddisk - naturligvis</title>
6935 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
6936 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
6937 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
6938 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
6939 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
6940 når en tar tap av arbeidstid, fortrolige dokumenter,
6941 personopplysninger og alt annet det innebærer. Det er ingen tvil om
6942 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
6943 til at jeg har kryptert harddisken på både kontormaskinen og min
6944 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
6945 komme på avveie, den første informasjon relatert til jobben min ved
6946 Universitetet i Oslo, og den andre relatert til blant annet
6947 foreningsarbeide. Kryptering av diskene gjør at det er lite
6948 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
6949 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
6950 og en reboot vil gjøre at de ber om passord før de vil starte opp.
6951 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
6952 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
6953 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
6954 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
6955 det er gjort slik jeg gjør det er minimale, og gevinstene er
6956 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
6957 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
6958
6959 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
6960 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
6961 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
6962 er for min del høyere enn gevinsten. Jeg tror oddsene for at
6963 f.eks. etteretningsorganisasjoner har glede av å titte på mine
6964 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
6965 gjøre det vanskeligere for angripere med kompetanse og ressurser er
6966 betydelige.&lt;/p&gt;
6967 </description>
6968 </item>
6969
6970 <item>
6971 <title>Two projects that have improved the quality of free software a lot</title>
6972 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
6973 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
6974 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
6975 <description>&lt;p&gt;There are two software projects that have had huge influence on the
6976 quality of free software, and I wanted to mention both in case someone
6977 do not yet know them.&lt;/p&gt;
6978
6979 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
6980 tool to detect and expose errors in the memory handling of programs.
6981 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
6982 and it will report any problems on stdout. It is even better if the
6983 program include debug information. With debug information, it is able
6984 to report the source file name and line number where the problem
6985 occurs. It can report things like &#39;reading past memory block in file
6986 X line N, the memory block was allocated in file Y, line M&#39;, and
6987 &#39;using uninitialised value in control logic&#39;. This tool has made it
6988 trivial to investigate reproducible crash bugs in programs, and have
6989 reduced the number of this kind of bugs in free software a lot.
6990
6991 &lt;p&gt;The second one is
6992 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
6993 a source code checker. It is able to process the source of a program
6994 and find problems in the logic without running the program. It
6995 started out as the Stanford Checker and became well known when it was
6996 used to find bugs in the Linux kernel. It is now a commercial tool
6997 and the company behind it is running
6998 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
6999 free software community, where a lot of free software projects get
7000 their source checked for free. Several thousand defects have been
7001 found and fixed so far. It can find errors like &#39;lock L taken in file
7002 X line N is never released if exiting in line M&#39;, or &#39;the code in file
7003 Y lines O to P can never be executed&#39;. The projects included in the
7004 community service project have managed to get rid of a lot of
7005 reliability problems thanks to Coverity.&lt;/p&gt;
7006
7007 &lt;p&gt;I believe tools like this, that are able to automatically find
7008 errors in the source, are vital to improve the quality of software and
7009 make sure we can get rid of the crashing and failing software we are
7010 surrounded by today.&lt;/p&gt;
7011 </description>
7012 </item>
7013
7014 <item>
7015 <title>No patch is not better than a useless patch</title>
7016 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
7017 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
7018 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
7019 <description>&lt;p&gt;Julien Blache
7020 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
7021 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
7022 patch allow one to discuss a concrete and proposed solution, and also
7023 prove that the issue at hand is important enough for someone to spent
7024 time on fixing it. No patch do not provide any of these positive
7025 properties.&lt;/p&gt;
7026 </description>
7027 </item>
7028
7029 <item>
7030 <title>Standardize on protocols and formats, not vendors and applications</title>
7031 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
7032 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
7033 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
7034 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
7035 very good one to form a long lived computer infrastructure. It is the
7036 simple one, lost by many in todays computer industry: Standardize on
7037 open network protocols and open exchange/storage formats, not applications.
7038 Applications come and go, while protocols and files tend to stay, and
7039 thus one want to make it easy to change application and vendor, while
7040 avoiding conversion costs and locking users to a specific platform or
7041 application.&lt;/p&gt;
7042
7043 &lt;p&gt;This approach make it possible to replace the client applications
7044 independently of the server applications. One can even allow users to
7045 use several different applications as long as they handle the selected
7046 protocol and format. In the normal case, only one client application
7047 is recommended and users only get help if they choose to use this
7048 application, but those that want to deviate from the easy path are not
7049 blocked from doing so.&lt;/p&gt;
7050
7051 &lt;p&gt;It also allow us to replace the server side without forcing the
7052 users to replace their applications, and thus allow us to select the
7053 best server implementation at any moment, when scale and resouce
7054 requirements change.&lt;/p&gt;
7055
7056 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
7057 open formats, but I would never recommend standardizing on a single
7058 application that do not use open network protocol or open formats.&lt;/p&gt;
7059 </description>
7060 </item>
7061
7062 <item>
7063 <title>Returning from Skolelinux developer gathering</title>
7064 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
7065 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
7066 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
7067 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
7068 Edu/Skolelinux development gathering. I got a bit done tuning the
7069 desktop, and looked into the dynamic service location protocol
7070 implementation avahi. It look like it could be useful for us. Almost
7071 30 people participated, and I believe it was a great environment to
7072 get to know the Skolelinux system. Walter Bender, involved in the
7073 development of the Sugar educational platform, presented his stuff and
7074 also helped me improve my OLPC installation. He also showed me that
7075 his Turtle Art application can be used in standalone mode, and we
7076 agreed that I would help getting it packaged for Debian. As a
7077 standalone application it would be great for Debian Edu. We also
7078 tried to get the video conferencing working with two OLPCs, but that
7079 proved to be too hard for us. The application seem to need more work
7080 before it is ready for me. I look forward to getting home and relax
7081 now. :)&lt;/p&gt;
7082 </description>
7083 </item>
7084
7085 <item>
7086 <title>Time for new LDAP schemas replacing RFC 2307?</title>
7087 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
7088 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
7089 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
7090 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
7091 optimal. There is RFC 2307 documenting one way to store NIS maps in
7092 LDAP, and a modified version of this normally called RFC 2307bis, with
7093 some modifications to be compatible with Active Directory. The RFC
7094 specification handle the content of a lot of system databases, but do
7095 not handle DNS zones and DHCP configuration.&lt;/p&gt;
7096
7097 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
7098 we would like to store information about users, SMB clients/hosts,
7099 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
7100 and LTSP configuration in LDAP. These objects have a lot in common,
7101 but with the current LDAP schemas it is not possible to have one
7102 object per entity. For example, one need to have at least three LDAP
7103 objects for a given computer, one with the SMB related stuff, one with
7104 DNS information and another with DHCP information. The schemas
7105 provided for DNS and DHCP are impossible to combine into one LDAP
7106 object. In addition, it is impossible to implement quick queries for
7107 netgroup membership, because of the way NIS triples are implemented.
7108 It just do not scale. I believe it is time for a few RFC
7109 specifications to cleam up this mess.&lt;/p&gt;
7110
7111 &lt;p&gt;I would like to have one LDAP object representing each computer in
7112 the network, and this object can then keep the SMB (ie host key), DHCP
7113 (mac address/name) and DNS (name/IP address) settings in one place.
7114 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
7115
7116 &lt;p&gt;I would also like to have a quick way to map from a user or
7117 computer and to the net group this user or computer is a member.&lt;/p&gt;
7118
7119 &lt;p&gt;Active Directory have done a better job than unix heads like myself
7120 in this regard, and the unix side need to catch up. Time to start a
7121 new IETF work group?&lt;/p&gt;
7122 </description>
7123 </item>
7124
7125 <item>
7126 <title>Endelig er Debian Lenny gitt ut</title>
7127 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
7128 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
7129 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
7130 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
7131 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
7132 Et langt steg videre for Debian-prosjektet, og en rekke nye
7133 programpakker blir nå tilgjengelig for de av oss som bruker den
7134 stabile utgaven av Debian. Neste steg er nå å få
7135 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
7136 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
7137 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
7138 slippes løs på skolene. Takk til alle debian-utviklerne som har
7139 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
7140 bootsekvens tilgjengelig i stabil utgave, vha pakken
7141 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
7142 </description>
7143 </item>
7144
7145 <item>
7146 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
7147 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
7148 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
7149 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
7150 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
7151 Oslo. Most of Saturday was used for the general assemly for the
7152 member organization, but the rest of the weekend I used to tune the
7153 LTSP installation. LTSP now work out of the box on the 10-network.
7154 Acer Aspire One proved to be a very nice thin client, with both
7155 screen, mouse and keybard in a small box. Was working on getting the
7156 diskless workstation setup configured out of the box, but did not
7157 finish it before the weekend was up.&lt;/p&gt;
7158
7159 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
7160 the Brazilian group, so that will have to wait for the next
7161 development gathering. Would love to have the Debian Edu installer
7162 automatically detect and configure a multiseat setup when it find one
7163 of these cards.&lt;/p&gt;
7164 </description>
7165 </item>
7166
7167 <item>
7168 <title>The sorry state of multimedia browser plugins in Debian</title>
7169 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
7170 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
7171 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
7172 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
7173 plugins available in Debian Lenny, to see which one we should use by
7174 default in Debian Edu. We need an embedded video playing plugin with
7175 control buttons to pause or stop the video, and capable of streaming
7176 all the multimedia content available on the web. The test results and
7177 notes are available on
7178 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
7179 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
7180 fill this need. My personal video player favorite, VLC, has a really
7181 bad plugin which fail on a lot of the test pages. A lot of the MIME
7182 types I would expect to work with any free software player (like
7183 video/ogg), just do not work. And simple formats like the
7184 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
7185 totem and vlc plugins. I hope the situation will improve soon. No
7186 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
7187
7188 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
7189 be the only one fitting our needs. :/&lt;/p&gt;
7190 </description>
7191 </item>
7192
7193 </channel>
7194 </rss>