]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
29d161bfd97082f733e7b088c11e9cd3f33cee0c
[homepage.git] / blog / tags / debian / debian.rss
1 <?xml version="1.0" encoding="utf-8"?>
2 <rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
3 <channel>
4 <title>Petter Reinholdtsen - Entries tagged debian</title>
5 <description>Entries tagged debian</description>
6 <link>http://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
11 <link>http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</link>
12 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</guid>
13 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
14 <description>&lt;p&gt;For a while now, I have wanted to test
15 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
16 said to provide end to end encrypted communication and several of my
17 friends and family are already using it. As I by choice do not own a
18 mobile phone, this proved to be harder than expected. And I wanted to
19 have the source of the client and know that it was the code used on my
20 machine. But yesterday I managed to get it working. I used the
21 Github source, compared it to the source in
22 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
23 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
24 patches to use the production Signal servers, started the app and
25 asked for the hidden &quot;register without a smart phone&quot; form. Here is
26 the recipe how I did it.&lt;/p&gt;
27
28 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
29
30 &lt;pre&gt;
31 git clone https://github.com/WhisperSystems/Signal-Desktop.git
32 &lt;/pre&gt;
33
34 &lt;p&gt;Next, I patched the source to use the production servers, to be
35 able to talk to other Signal users:&lt;/p&gt;
36
37 &lt;pre&gt;
38 cat &amp;lt;&amp;lt;EOF | patch -p0
39 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
40 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
41 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
42 @@ -47,8 +47,8 @@
43 });
44 });
45
46 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
47 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
48 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
49 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
50 var messageReceiver;
51 window.getSocketStatus = function() {
52 if (messageReceiver) {
53 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
54 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
55 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
56 @@ -1,6 +1,6 @@
57 ;(function() {
58 &#39;use strict&#39;;
59 - var BUILD_EXPIRATION = 0;
60 + var BUILD_EXPIRATION = 1474492690000;
61
62 window.extension = window.extension || {};
63
64 EOF
65 &lt;/pre&gt;
66
67 &lt;p&gt;The first part is changing the servers, and the second is updating
68 an expiration timestamp. This timestamp need to be updated regularly.
69 It is set 90 days in the future by the build process (Gruntfile.js).
70 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
71
72 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
73 script to launch Signal in Chromium.&lt;/p&gt;
74
75 &lt;pre&gt;
76 #!/bin/sh
77 cd $(dirname $0)
78 mkdir -p userdata
79 exec chromium \
80 --proxy-server=&quot;socks://localhost:9050&quot; \
81 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
82 &lt;/pre&gt;
83
84 &lt;p&gt; The script start the app and configure Chromium to use the Tor
85 SOCKS5 proxy to make sure those controlling the Signal servers (today
86 Amazon and Whisper Systems) as well as those listening on the lines
87 will have a harder time location my laptop based on the Signal
88 connections if they use source IP address.&lt;/p&gt;
89
90 &lt;p&gt;When the script starts, one need to follow the instructions under
91 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
92 repository. I right clicked on the Signal window to get up the
93 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
94 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
95 registration form. Then I entered by land line phone number and
96 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
97 repeated the verification code three times. After entering the number
98 into the verification code field in the form, I could start using
99 Signal from my laptop.
100
101 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
102 whom and thus who know who to those controlling the central server,
103 but such leakage is hard to avoid with a centrally controlled server
104 setup. It is something to keep in mind when using Signal - the
105 content of your chats are harder to intercept, but the meta data
106 exposing your contact network is available to people you do not know.
107 So better than many options, but not great. And sadly the usage is
108 connected to my land line, thus allowing those controlling the server
109 to associate it to my home and person. I would prefer it if only
110 those I knew could tell who I was on Signal. There are options
111 avoiding such information leakage, but most of my friends are not
112 using them, so I am stuck with Signal for now.&lt;/p&gt;
113 </description>
114 </item>
115
116 <item>
117 <title>The new &quot;best&quot; multimedia player in Debian?</title>
118 <link>http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
119 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
120 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
121 <description>&lt;p&gt;When I set out a few weeks ago to figure out
122 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
123 multimedia player in Debian claimed to support most file formats /
124 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
125 the various players claimed support for. The range was from 55 to 130
126 MIME types. I suspect most media formats are supported by all
127 players, but this is not really reflected in the MimeTypes values in
128 their desktop files. There are probably also some bogus MIME types
129 listed, but it is hard to identify which one this is.&lt;/p&gt;
130
131 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
132 the players suggesting to add more MIME types to their desktop files,
133 and decided to spend some time myself improving the situation for my
134 favorite media player VLC. The fixes for VLC entered Debian unstable
135 yesterday. The complete list of MIME types can be seen on the
136 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
137 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
138
139 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
140 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
141 kmplayer. I am sure some of the other players desktop files support
142 several of the formats currently listed as working only with vlc,
143 toten and parole.&lt;/p&gt;
144
145 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
146 supported by all the tested multimedia players in Debian in their
147 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
148 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
149 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
150 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
151 it sad that video/ogg and video/webm is not supported by all the media
152 players in Debian. As far as I can tell, all of them can handle both
153 formats.&lt;/p&gt;
154 </description>
155 </item>
156
157 <item>
158 <title>A program should be able to open its own files on Linux</title>
159 <link>http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
160 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
161 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
162 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
163 decided to test its presentation tool when making the slides for a
164 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
165 wrote the first draft of the slides, saved the result and went to bed
166 the day before I would give the talk. The next day I took a plane to
167 the location where the meeting should take place, and on the plane I
168 started up koffice again to polish the talk a bit, only to discover
169 that kpresenter refused to load its own data file. I cursed a bit and
170 started making the slides again from memory, to have something to
171 present when I arrived. I tested that the saved files could be
172 loaded, and the day seemed to be rescued. I continued to polish the
173 slides until I suddenly discovered that the saved file could no longer
174 be loaded into kpresenter. In the end I had to rewrite the slides
175 three times, condensing the content until the talk became shorter and
176 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
177 kpresenter wrote inline images in a way itself could not understand.
178 Eventually that bug was fixed and kpresenter ended up being a great
179 program to make slides. The point I&#39;m trying to make is that we
180 expect a program to be able to load its own data files, and it is
181 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
182
183 &lt;p&gt;Did you ever experience a program failing to load its own data
184 files from the desktop file browser? It is not a uncommon problem. A
185 while back I discovered that the screencast recorder
186 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
187 browser would refuse to open. No video player claimed to understand
188 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
189 returning the application/ogg MIME type, which no video player I had
190 installed listed as a MIME type they would understand. I asked for
191 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
192 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
193 several video players to add video/ogg to their desktop files, to give
194 the file browser an idea what to do about Ogg Theora files. After a
195 while, the desktop file browsers in Debian started to handle the
196 output from gtk-recordmydesktop properly.&lt;/p&gt;
197
198 &lt;p&gt;But history repeats itself. A few days ago I tested the music
199 system Rosegarden again, and I discovered that the KDE and xfce file
200 browsers did not know what to do with the Rosegarden project files
201 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
202 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
203 included in the next upload. To increase the chance of me remembering
204 how to fix the problem next time some program fail to load its files
205 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
206
207 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
208 There are two sources for the MIME type of a given file. The output from
209 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
210 shared MIME type registry (under /usr/share/mime/). The file MIME
211 type is mapped to programs supporting the MIME type, and this
212 information is collected from
213 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
214 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
215 one desktop file claiming support for the MIME type of the file, it is
216 activated when asking to open a given file. If there are more, one
217 can normally select which one to use by right-clicking on the file and
218 selecting the wanted one using &#39;Open with&#39; or similar. In general
219 this work well. But it depend on each program picking a good MIME
220 type (preferably
221 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
222 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
223 registry recognizing the file and the desktop file to list the MIME
224 type in its list of supported MIME types.&lt;/p&gt;
225
226 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
227 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
228 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
229
230 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
231 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
232 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
233 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
234 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
235 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
236 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
237 &amp;lt;/mime-type&amp;gt;
238 &amp;lt;/mime-info&amp;gt;
239 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
240
241 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
242 (it is a gzipped XML file). Note, it is much better to use an
243 official MIME type registered with IANA than it is to make up ones own
244 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
245
246 &lt;p&gt;The desktop file of the rosegarden program failed to list
247 audio/x-rosegarden in its list of supported MIME types, causing the
248 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
249
250 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
251 % grep Mime /usr/share/applications/rosegarden.desktop
252 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
253 X-KDE-NativeMimeType=audio/x-rosegarden-composition
254 %
255 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
256
257 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
258 MimeType= line.&lt;/p&gt;
259
260 &lt;p&gt;If you run into a file which fail to open the correct program when
261 selected from the file browser, please check out the output from
262 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
263 MIME type is registered somewhere under /usr/share/mime/ and check
264 that some desktop file under /usr/share/applications/ is claiming
265 support for this MIME type. If not, please report a bug to have it
266 fixed. :)&lt;/p&gt;
267 </description>
268 </item>
269
270 <item>
271 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
272 <link>http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
273 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
274 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
275 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
276 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
277 related packages. The idea is to have a database of mappings between
278 hardware and packages, and pop up a dialog suggesting for the user to
279 install the packages to use a given hardware dongle. Some use cases
280 are when you insert a Yubikey, it proposes to install the software
281 needed to control it; when you insert a braille reader list it
282 proposes to install the packages needed to send text to the reader;
283 and when you insert a ColorHug screen calibrator it suggests to
284 install the driver for it. The system work well, and even have a few
285 command line tools to install firmware packages and packages for the
286 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
287
288 &lt;p&gt;The system was initially written using aptdaemon, because I found
289 good documentation and example code on how to use it. But aptdaemon
290 is going away and is generally being replaced by
291 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
292 so Isenkram needed a rewrite. And today, thanks to the great patch
293 from my college Sunil Mohan Adapa in the FreedomBox project, the
294 rewrite finally took place. I&#39;ve just uploaded a new version of
295 Isenkram into Debian Unstable with the patch included, and the default
296 for the background daemon is now to use PackageKit. To check it out,
297 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
298 and see if it is recognised.&lt;/p&gt;
299
300 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
301 the machine it is running on, you can check out the isenkram-lookup
302 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
303
304 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
305 % isenkram-lookup
306 bluez
307 cheese
308 fprintd
309 fprintd-demo
310 gkrellm-thinkbat
311 hdapsd
312 libpam-fprintd
313 pidgin-blinklight
314 thinkfan
315 tleds
316 tp-smapi-dkms
317 tp-smapi-source
318 tpb
319 %p
320 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
321
322 &lt;p&gt;The hardware mappings come from several places. The preferred way
323 is for packages to announce their hardware support using
324 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
325 cross distribution appstream system&lt;/a&gt;.
326 See
327 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
328 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
329 </description>
330 </item>
331
332 <item>
333 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
334 <link>http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
335 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
336 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
337 <description>&lt;p&gt;Yesterday I updated the
338 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
339 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
340 enterprising users. There were some nice user and visible changes.
341 First of all, both desktop menu entries now work. A design flaw in
342 one of the script made the history graph fail to show up (its PNG was
343 dumped in ~/.xsession-errors) if no controlling TTY was available.
344 The script worked when called from the command line, but not when
345 called from the desktop menu. I changed this to look for a DISPLAY
346 variable or a TTY before deciding where to draw the graph, and now the
347 graph window pop up as expected.&lt;/p&gt;
348
349 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
350 graphs (the one showing the last few hours). New is also the user of
351 colours showing charging in blue and discharge in red. The percentages
352 of this graph is relative to last full charge, not battery design
353 capacity.&lt;/p&gt;
354
355 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-rate.png&quot;/&gt;&lt;/p&gt;
356
357 &lt;p&gt;The other graph show the entire history of the collected battery
358 statistics, comparing it to the design capacity of the battery to
359 visualise how the battery life time get shorter over time. The red
360 line in this graph is what the previous graph considers 100 percent:
361
362 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-05-23-battery-stats-history.png&quot;/&gt;&lt;/p&gt;
363
364 &lt;p&gt;In this graph you can see that I only charge the battery to 80
365 percent of last full capacity, and how the capacity of the battery is
366 shrinking. :(&lt;/p&gt;
367
368 &lt;p&gt;The last new feature is in the collector, which now will handle
369 more hardware models. On some hardware, Linux power supply
370 information is stored in /sys/class/power_supply/ACAD/, while the
371 collector previously only looked in /sys/class/power_supply/AC/. Now
372 both are checked to figure if there is power connected to the
373 machine.&lt;/p&gt;
374
375 &lt;p&gt;If you are interested in how your laptop battery is doing, please
376 check out the
377 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
378 in Debian unstable, or rebuild it on Jessie to get it working on
379 Debian stable. :) The upstream source is available from &lt;a
380 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
381 Patches are very welcome.&lt;/p&gt;
382
383 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
384 activities, please send Bitcoin donations to my address
385 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
386 </description>
387 </item>
388
389 <item>
390 <title>Debian now with ZFS on Linux included</title>
391 <link>http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
392 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
393 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
394 <description>&lt;p&gt;Today, after many years of hard work from many people,
395 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
396 Debian. The package status can be seen on
397 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
398 for zfs-linux&lt;/a&gt;. and
399 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
400 team status page&lt;/a&gt;. If you want to help out, please join us.
401 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
402 source code&lt;/a&gt; is available via git on Alioth. It would also be
403 great if you could help out with
404 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
405 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
406 </description>
407 </item>
408
409 <item>
410 <title>What is the best multimedia player in Debian?</title>
411 <link>http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
412 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
413 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
414 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
415 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
416
417 &lt;p&gt;A few years ago, I had a look at the media support for Browser
418 plugins in Debian, to get an idea which plugins to include in Debian
419 Edu. I created a script to extract the set of supported MIME types
420 for each plugin, and used this to find out which multimedia browser
421 plugin supported most file formats / media types.
422 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
423 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
424 not been updated for a while. But browser plugins are less relevant
425 these days, so I thought it was time to look at standalone
426 players.&lt;/p&gt;
427
428 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
429 player when I wanted to play videos from the Norwegian National
430 Broadcasting Company, and decided to investigate why. The cause is a
431 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
432 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
433 of MIME types announced in the desktop file and the browser plugin,
434 only to discover that there is quite a large difference between the
435 two for VLC. This discovery made me dig up the script I used to
436 compare browser plugins, and adjust it to compare desktop files
437 instead, to try to figure out which multimedia player in Debian
438 support most file formats.&lt;/p&gt;
439
440 &lt;p&gt;The result can be seen on the Debian Wiki, as
441 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
442 table listing all MIME types supported by one of the packages included
443 in the table&lt;/a&gt;, with the package supporting most MIME types being
444 listed first in the table.&lt;/p&gt;
445
446 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
447 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
448 kmplayer. Time for the other players to update their announced MIME
449 support?&lt;/p&gt;
450 </description>
451 </item>
452
453 <item>
454 <title>The Pyra - handheld computer with Debian preinstalled</title>
455 <link>http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
456 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
457 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
458 <description>A friend of mine made me aware of
459 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
460 handheld computer which will be delivered with Debian preinstalled. I
461 would love to get one of those for my birthday. :)&lt;/p&gt;
462
463 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
464 plugs and many others connectors, and include a full keyboard and a 5&quot;
465 LCD touch screen. The 6000mAh battery is claimed to provide a whole
466 day of battery life time, but I have not seen any independent tests
467 confirming this. The vendor is still collecting preorders, and the
468 last I heard last night was that 22 more orders were needed before
469 production started.&lt;/p&gt;
470
471 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
472 Debian. Please let me know if you know of any others. Is it the
473 first computer being sold with Debian preinstalled?&lt;/p&gt;
474 </description>
475 </item>
476
477 <item>
478 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
479 <link>http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
480 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
481 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
482 <description>&lt;p&gt;During this weekends
483 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
484 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
485 to make sure there are good books about Debian available in Norwegian
486 Bokmål, and got in touch with the people behind the
487 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
488 project&lt;/a&gt; to get started. If you want to help out, please start
489 contributing using
490 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
491 hosted weblate project page&lt;/a&gt;, and get in touch using
492 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
493 translators mailing list&lt;/a&gt;. Please also check out
494 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
495 contributors&lt;/a&gt;.&lt;/p&gt;
496
497 &lt;p&gt;The book is already available on paper in English, French and
498 Japanese, and our goal is to get it available on paper in Norwegian
499 Bokmål too. In addition to the paper edition, there are also EPUB and
500 Mobi versions available. And there are incomplete translations
501 available for many more languages.&lt;/p&gt;
502 </description>
503 </item>
504
505 <item>
506 <title>One in two hundred Debian users using ZFS on Linux?</title>
507 <link>http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
508 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
509 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
510 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
511 packages in Debian, and was quite surprised with what I found. I use
512 ZFS myself at home, but did not really expect many others to do so.
513 But I might be wrong.&lt;/p&gt;
514
515 &lt;p&gt;According to
516 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
517 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
518 0.53% of the population, with the package installed. As far as I know
519 the only use of the spl-linux package is as a support library for ZFS
520 on Linux, so I use it here as proxy for measuring the number of ZFS
521 installation on Linux in Debian. In the kFreeBSD variant of Debian
522 the ZFS feature is already available, and there
523 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
524 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
525 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
526
527 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
528 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
529 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
530 cleared, the package is still not in Debian. The package is again in
531 the NEW queue. Several uploads have been rejected so far because the
532 debian/copyright file was incomplete or wrong, but there is no reason
533 to give up. The current status can be seen on
534 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
535 team status page&lt;/a&gt;, and
536 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
537 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
538
539 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
540 my home server can function in the future using only official Debian
541 packages, and the current blocker is to get the debian/copyright file
542 accepted by the FTP masters in Debian, I decided a while back to try
543 to help out the team. This was the background for my blog post about
544 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
545 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
546 used the techniques I explored there to try to find any errors in the
547 copyright file. It is not very easy to check every one of the around
548 2000 files in the source package, but I hope we this time got it
549 right. If you want to help out, check out the git source and try to
550 find missing entries in the debian/copyright file.&lt;/p&gt;
551 </description>
552 </item>
553
554 <item>
555 <title>Full battery stats collector is now available in Debian</title>
556 <link>http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
557 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
558 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
559 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
560 extended collector that will collect the complete battery history for
561 later processing and graphing. The original collector store the
562 battery level as percentage of last full level, while the new
563 collector also record battery vendor, model, serial number, design
564 full level, last full level and current battery level. This make it
565 possible to predict the lifetime of the battery as well as visualise
566 the energy flow when the battery is charging or discharging.&lt;/p&gt;
567
568 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
569 in the version 0.5.1 package in unstable. Get the new battery level graph
570 and lifetime prediction by running:
571
572 &lt;p&gt;&lt;pre&gt;
573 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
574 &lt;/pre&gt;&lt;/p&gt;
575
576 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
577
578 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
579 entry yet):&lt;/p&gt;
580
581 &lt;p&gt;&lt;pre&gt;
582 /usr/share/battery-stats/battery-stats-graph-flow
583 &lt;/pre&gt;&lt;/p&gt;
584
585 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
586 when there are few data points. The graphs look a bit better with a
587 few years of data.&lt;/p&gt;
588
589 &lt;p&gt;A while back one important feature I use in the battery stats
590 collector broke in Debian. The scripts in
591 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
592 suspect it happened when Jessie started using systemd, but I do not
593 know. The issue is reported as
594 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
595 pm-utils. I managed to work around it by adding an udev rule to call
596 the collector script every time the power connector is connected and
597 disconnected. With this fix in place it was finally time to make a
598 new release of the package, and get it into Debian.&lt;/p&gt;
599
600 &lt;p&gt;If you are interested in how your laptop battery is doing, please
601 check out the
602 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
603 in Debian unstable, or rebuild it on Jessie to get it working on
604 Debian stable. :) The upstream source is available from
605 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
606 As always, patches are very welcome.&lt;/p&gt;
607 </description>
608 </item>
609
610 <item>
611 <title>Making battery measurements a little easier in Debian</title>
612 <link>http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
613 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
614 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
615 <description>&lt;p&gt;Back in September, I blogged about
616 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
617 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
618 how it showed the decay and death of this battery (now replaced). I
619 created a simple deb package to handle the collection and graphing,
620 but did not want to upload it to Debian as there were already
621 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
622 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
623 a point of uploading a competing package when battery-stats could be
624 fixed instead. I reported a few bugs about its non-function, and
625 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
626
627 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
628 hands. The end result is that I am now the new upstream developer of
629 battery stats (&lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;available from github&lt;/a&gt;) and part of the team maintaining
630 battery-stats in Debian, and the package in Debian unstable is finally
631 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
632 information provided by the Linux kernel. If you install the
633 battery-stats package from unstable now, you will be able to get a
634 graph of the current battery fill level, to get some idea about the
635 status of the battery. The source package build and work just fine in
636 Debian testing and stable (and probably oldstable too, but I have not
637 tested). The default graph you get for that system look like this:&lt;/p&gt;
638
639 &lt;p align=&quot;center&quot;&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2016-03-15-battery-stats-graph-example.png&quot; width=&quot;70%&quot; align=&quot;center&quot;&gt;&lt;/p&gt;
640
641 &lt;p&gt;My plans for the future is to merge my old scripts into the
642 battery-stats package, as my old scripts collected a lot more details
643 about the battery. The scripts are merged into the upstream
644 battery-stats git repository already, but I am not convinced they work
645 yet, as I changed a lot of paths along the way. Will have to test a
646 bit more before I make a new release.&lt;/p&gt;
647
648 &lt;p&gt;I will also consider changing the file format slightly, as I
649 suspect the way I combine several values into one field might make it
650 impossible to know the type of the value when using it for processing
651 and graphing.&lt;/p&gt;
652
653 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
654 battery, check out the battery-stats package in
655 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
656 on
657 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
658 I would love some help to improve the system further.&lt;/p&gt;
659 </description>
660 </item>
661
662 <item>
663 <title>Creating, updating and checking debian/copyright semi-automatically</title>
664 <link>http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
665 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
666 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
667 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
668 details. And one of the details is the content of the
669 debian/copyright file, which should list all relevant licenses used by
670 the code in the package in question, preferably in
671 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
672 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
673
674 &lt;p&gt;For large packages with lots of contributors it is hard to write
675 and update this file manually, and if you get some detail wrong, the
676 package is normally rejected by the ftpmasters. So getting it right
677 the first time around get the package into Debian faster, and save
678 both you and the ftpmasters some work.. Today, while trying to figure
679 out what was wrong with
680 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
681 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
682 figuring out the options for doing this job automatically, or at least
683 semi-automatically.&lt;/p&gt;
684
685 &lt;p&gt;Lucikly, there are at least two tools available for generating the
686 file based on the code in the source package,
687 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
688 and &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/cme&quot;&gt;cme&lt;/a&gt;&lt;/tt&gt;. I&#39;m
689 not sure which one of them came first, but both seem to be able to
690 create a sensible draft file. As far as I can tell, none of them can
691 be trusted to get the result just right, so the content need to be
692 polished a bit before the file is OK to upload. I found the debmake
693 option in
694 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
695 blog posts from 2014&lt;/a&gt;.
696
697 &lt;p&gt;To generate using debmake, use the -cc option:
698
699 &lt;p&gt;&lt;pre&gt;
700 debmake -cc &gt; debian/copyright
701 &lt;/pre&gt;&lt;/p&gt;
702
703 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
704 this might not be the best option.&lt;/p&gt;
705
706 &lt;p&gt;The cme option is based on a config parsing library, and I found
707 this approach in
708 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
709 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
710 dpkg-copyright&#39; option:
711
712 &lt;p&gt;&lt;pre&gt;
713 cme update dpkg-copyright
714 &lt;/pre&gt;&lt;/p&gt;
715
716 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
717 handle UTF-8 names better than debmake.&lt;/p&gt;
718
719 &lt;p&gt;When the copyright file is created, I would also like some help to
720 check if the file is correct. For this I found two good options,
721 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
722 to focus on license types and file matching, and is able to detect
723 ineffective blocks in the copyright file. The latter reports missing
724 copyright holders and years, but was confused by inconsistent license
725 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
726 fix all issues reported by them before uploading. But I do not know
727 if the tools and the ftpmasters agree on what is important to fix in a
728 copyright file, so the package might still be rejected.&lt;/p&gt;
729
730 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
731 will read through the source and try to find all copyright statements.
732 It is not comparing the result to the content of debian/copyright, but
733 can be useful when verifying the content of the copyright file.&lt;/p&gt;
734
735 &lt;p&gt;Are you aware of better tools in Debian to create and update
736 debian/copyright file. Please let me know, or blog about it on
737 planet.debian.org.&lt;/p&gt;
738
739 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
740 activities, please send Bitcoin donations to my address
741 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
742
743 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
744 on how to use licensecheck and cdbs to create a draft copyright file
745
746 &lt;p&gt;&lt;pre&gt;
747 licensecheck --copyright -r `find * -type f` | \
748 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
749 &lt;/pre&gt;&lt;/p&gt;
750
751 &lt;p&gt;He mentioned that he normally check the generated file into the
752 version control system to make it easier to discover license and
753 copyright changes in the upstream source. I will try to do the same
754 with my packages in the future.&lt;/p&gt;
755
756 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
757 against using -quiet for new users, so I removed it from the proposed
758 command line.&lt;/p&gt;
759 </description>
760 </item>
761
762 <item>
763 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
764 <link>http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
765 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
766 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
767 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
768 is taking shape in Debian, and one provided feature is a very
769 convenient way to tell you which package to install to make a given
770 firmware file available when the kernel is looking for it. This can
771 be done using apt-file too, but that is for someone else to blog
772 about. :)&lt;/p&gt;
773
774 &lt;p&gt;Here is a small recipe to find the package with a given firmware
775 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
776 picked from the set of firmware announced using appstream in Debian
777 unstable. In general you would be looking for the firmware requested
778 by the kernel during kernel module loading. To find the package
779 providing the example file, do like this:&lt;/p&gt;
780
781 &lt;blockquote&gt;&lt;pre&gt;
782 % apt install appstream
783 [...]
784 % apt update
785 [...]
786 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
787 awk &#39;/Package:/ {print $2}&#39;
788 firmware-qlogic
789 %
790 &lt;/pre&gt;&lt;/blockquote&gt;
791
792 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
793 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
794 a way appstream can use.&lt;/p&gt;
795
796 &lt;p&gt;This same approach can be used to find any package supporting a
797 given MIME type. This is very useful when you get a file you do not
798 know how to handle. First find the mime type using &lt;tt&gt;file
799 --mime-type&lt;/tt&gt;, and next look up the package providing support for
800 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
801 and you can find all packages handling this type like this:&lt;/p&gt;
802
803 &lt;blockquote&gt;&lt;pre&gt;
804 % apt install appstream
805 [...]
806 % apt update
807 [...]
808 % appstreamcli what-provides mimetype image/svg+xml | \
809 awk &#39;/Package:/ {print $2}&#39;
810 bkchem
811 phototonic
812 inkscape
813 shutter
814 tetzle
815 geeqie
816 xia
817 pinta
818 gthumb
819 karbon
820 comix
821 mirage
822 viewnior
823 postr
824 ristretto
825 kolourpaint4
826 eog
827 eom
828 gimagereader
829 midori
830 %
831 &lt;/pre&gt;&lt;/blockquote&gt;
832
833 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
834 packages providing appstream metadata.&lt;/p&gt;
835 </description>
836 </item>
837
838 <item>
839 <title>Creepy, visualise geotagged social media information - nice free software</title>
840 <link>http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
841 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
842 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
843 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
844 with the computerised radio beacon known as a mobile phone their
845 position is tracked by the phone company and often stored for a long
846 time (like every time a SMS is received or sent). And if their
847 computerised radio beacon is capable of running programs (often called
848 mobile apps) downloaded from the Internet, these programs are often
849 also capable of tracking their location (if the app requested access
850 during installation). And when these programs send out information to
851 central collection points, the location is often included, unless
852 extra care is taken to not send the location. The provided
853 information is used by several entities, for good and bad (what is
854 good and bad, depend on your point of view). What is certain, is that
855 the private sphere and the right to free movement is challenged and
856 perhaps even eradicated for those announcing their location this way,
857 when they share their whereabouts with private and public
858 entities.&lt;/p&gt;
859
860 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-01-24-nice-creepy-desktop-window.png&quot;&gt;&lt;/p&gt;
861
862 &lt;p&gt;The phone company logs provide a register of locations to check out
863 when one want to figure out what the tracked person was doing. It is
864 unavailable for most of us, but provided to selected government
865 officials, company staff, those illegally buying information from
866 unfaithful servants and crackers stealing the information. But the
867 public information can be collected and analysed, and a free software
868 tool to do so is called
869 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
870 discovered it when I read
871 &lt;a href=&quot;http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-7787884.html&quot;&gt;an
872 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
873 November 2014, and decided to check if it was available in Debian.
874 The python program was in Debian, but
875 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
876 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
877 uploaded a new version which did not work quite right, but did not
878 have time to fix it then. This Christmas I decided to finally try to
879 get Creepy operational in Debian. Now a fixed version is available in
880 Debian unstable and testing, and almost all Debian specific patches
881 are now included
882 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
883
884 &lt;p&gt;The Creepy program visualises geolocation information fetched from
885 Twitter, Instagram, Flickr and Google+, and allow one to get a
886 complete picture of every social media message posted recently in a
887 given area, or track the movement of a given individual across all
888 these services. Earlier it was possible to use the search API of at
889 least some of these services without identifying oneself, but these
890 days it is impossible. This mean that to use Creepy, you need to
891 configure it to log in as yourself on these services, and provide
892 information to them about your search interests. This should be taken
893 into account when using Creepy, as it will also share information
894 about yourself with the services.&lt;/p&gt;
895
896 &lt;p&gt;The picture above show the twitter messages sent from (or at least
897 geotagged with a position from) the city centre of Oslo, the capital
898 of Norway. One useful way to use Creepy is to first look at
899 information tagged with an area of interest, and next look at all the
900 information provided by one or more individuals who was in the area.
901 I tested it by checking out which celebrity provide their location in
902 twitter messages by checkout out who sent twitter messages near a
903 Norwegian TV station, and next could track their position over time,
904 making it possible to locate their home and work place, among other
905 things. A similar technique have been
906 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
907 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
908 tool to discover lying governments, and a useful tool to help people
909 understand the value of the private information they provide to the
910 public.&lt;/p&gt;
911
912 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
913 it depend on several python modules currently missing in Jessie (at
914 least python-instagram, python-flickrapi and
915 python-requests-toolbelt).&lt;/p&gt;
916
917 &lt;p&gt;(I have uploaded
918 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
919 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
920 Creepy program in Debian.)&lt;/p&gt;
921 </description>
922 </item>
923
924 <item>
925 <title>Always download Debian packages using Tor - the simple recipe</title>
926 <link>http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
927 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
928 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
929 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
930 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
931 that those listening on the Internet lines would have good reason to
932 believe a computer have a given security hole&lt;/a&gt; if it download a
933 security fix from a Debian mirror. This is a good reason to always
934 use encrypted connections to the Debian mirror, to make sure those
935 listening do not know which IP address to attack. In August, Richard
936 Hartmann observed that encryption was not enough, when it was possible
937 to interfere download size to security patches or the fact that
938 download took place shortly after a security fix was released, and
939 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
940 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
941 was not the first to propose this, as the
942 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/apt-transport-tor&quot;&gt;apt-transport-tor&lt;/a&gt;&lt;/tt&gt;
943 package by Tim Retout already existed to make it easy to convince apt
944 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
945 aware of that package when I read the blog post from Richard.&lt;/p&gt;
946
947 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
948 sysadmins, and he set up a Tor hidden service on one of the central
949 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
950 it possible to download packages directly between two tor nodes,
951 making sure the network traffic always were encrypted.&lt;/p&gt;
952
953 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
954 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
955 urls with tor+http and tor+https, and using the hidden service instead
956 of the official Debian mirror site. I recommend installing
957 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
958 done in /etc/.&lt;/p&gt;
959
960 &lt;blockquote&gt;&lt;pre&gt;
961 apt install apt-transport-tor
962 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
963 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
964 &lt;/pre&gt;&lt;/blockquote&gt;
965
966 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
967 the sed commands for these too. The sed command is assuming your are
968 using the ftp.debian.org Debian mirror. Adjust the command (or just
969 edit the file manually) to match your mirror.&lt;/p&gt;
970
971 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
972 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
973 system, and do not work with these tor+http URLs. For
974 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
975 which need a recent apt version currently only in unstable. So if you
976 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
977
978 &lt;p&gt;Another advantage from this change is that your machine will start
979 using Tor regularly and at fairly random intervals (every time you
980 update the package lists or upgrade or install a new package), thus
981 masking other Tor traffic done from the same machine. Using Tor will
982 become normal for the machine in question.&lt;/p&gt;
983
984 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
985 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
986 enabled. It would be great if it was the default on any Debian
987 system.&lt;/p&gt;
988 </description>
989 </item>
990
991 <item>
992 <title>OpenALPR, find car license plates in video streams - nice free software</title>
993 <link>http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
994 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
995 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
996 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
997 call the car license plate numbers in those days. I would write the
998 numbers down in my little book and compare notes with the other kids
999 to see how many region codes we had seen and if we had seen some
1000 exotic or special region codes and numbers. It was a fun game to pass
1001 time, as we kids have plenty of it.&lt;/p&gt;
1002
1003 &lt;p&gt;A few days I came across
1004 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
1005 project&lt;/a&gt;, a free software project to automatically discover and
1006 report license plates in images and video streams, and provide the
1007 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
1008 such system for a while now, because I believe it is a bad idea that the
1009 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
1010 number plate recognition&lt;/a&gt; tool only is available in the hands of
1011 the powerful, and want it to be available also for the powerless to
1012 even the score when it comes to surveillance and sousveillance. I
1013 discovered the developer
1014 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
1015 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
1016 help him get it into shape to get the package uploaded into the Debian
1017 archive.&lt;/p&gt;
1018
1019 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
1020 it into Debian, where it currently
1021 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
1022 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
1023
1024 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
1025 for the common folks, ie those not running a large government
1026 surveillance system? Well, I plan to put it in a computer on my bike
1027 and in my car, tracking the cars nearby and allowing me to be notified
1028 when number plates on my watch list are discovered. Another use case
1029 was suggested by a friend of mine, who wanted to set it up at his home
1030 to open the car port automatically when it discovered the plate on his
1031 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
1032 capable of placing his license plate number of a piece of cardboard to
1033 open his car port, men replied that it was always unlocked anyway. I
1034 guess for such use case it make sense. I am sure there are other use
1035 cases too, for those with imagination and a vision.&lt;/p&gt;
1036
1037 &lt;p&gt;If you want to build your own version of the Debian package, check
1038 out the upstream git source and symlink ./distros/debian to ./debian/
1039 before running &quot;debuild&quot; to build the source. Or wait a bit until the
1040 package show up in unstable.&lt;/p&gt;
1041 </description>
1042 </item>
1043
1044 <item>
1045 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
1046 <link>http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
1047 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
1048 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
1049 <description>&lt;p&gt;Around three years ago, I created
1050 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
1051 system&lt;/a&gt; to get a more practical solution in Debian for handing
1052 hardware related packages. A GUI system in the isenkram package will
1053 present a pop-up dialog when some hardware dongle supported by
1054 relevant packages in Debian is inserted into the machine. The same
1055 lookup mechanism to detect packages is available as command line
1056 tools in the isenkram-cli package. In addition to mapping hardware,
1057 it will also map kernel firmware files to packages and make it easy to
1058 install needed firmware packages automatically. The key for this
1059 system to work is a good way to map hardware to packages, in other
1060 words, allow packages to announce what hardware they will work
1061 with.&lt;/p&gt;
1062
1063 &lt;p&gt;I started by providing data files in the isenkram source, and
1064 adding code to download the latest version of these data files at run
1065 time, to ensure every user had the most up to date mapping available.
1066 I also added support for storing the mapping in the Packages file in
1067 the apt repositories, but did not push this approach because while I
1068 was trying to figure out how to best store hardware/package mappings,
1069 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
1070 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
1071 add the hardware mapping into that data set to be able to use
1072 appstream as a data source, and this was accepted at least for the
1073 Debian version of appstream.&lt;/p&gt;
1074
1075 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
1076 and today I uploaded a new version 0.20 of isenkram adding support for
1077 appstream as a data source for mapping hardware to packages. The only
1078 package so far using appstream to announce its hardware support is my
1079 pymissile package. I got help from Matthias Klumpp with figuring out
1080 how do add the required
1081 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
1082 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
1083 this content:&lt;/p&gt;
1084
1085 &lt;blockquote&gt;&lt;pre&gt;
1086 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
1087 &amp;lt;component&amp;gt;
1088 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
1089 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
1090 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
1091 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
1092 &amp;lt;description&amp;gt;
1093 &amp;lt;p&amp;gt;
1094 Pymissile provides a curses interface to control an original
1095 Marks and Spencer / Striker USB Missile Launcher, as well as a
1096 motion control script to allow a webcamera to control the
1097 launcher.
1098 &amp;lt;/p&amp;gt;
1099 &amp;lt;/description&amp;gt;
1100 &amp;lt;provides&amp;gt;
1101 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
1102 &amp;lt;/provides&amp;gt;
1103 &amp;lt;/component&amp;gt;
1104 &lt;/pre&gt;&lt;/blockquote&gt;
1105
1106 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
1107 which is a glob style match rule for hardware specific strings
1108 (modalias strings) provided by the Linux kernel. In this case, it
1109 will map to all USB devices with vendor code 1130 and product code
1110 0202.&lt;/p&gt;
1111
1112 &lt;p&gt;Note, it is important that the license of all the metadata files
1113 are compatible to have permissions to aggregate them into archive wide
1114 appstream files. Matthias suggested to use MIT or BSD licenses for
1115 these files. A challenge is figuring out a good id for the data, as
1116 it is supposed to be globally unique and shared across distributions
1117 (in other words, best to coordinate with upstream what to use). But
1118 it can be changed later or, so we went with the package name as
1119 upstream for this project is dormant.&lt;/p&gt;
1120
1121 &lt;p&gt;To get the metadata file installed in the correct location for the
1122 mirror update scripts to pick it up and include its content the
1123 appstream data source, the file must be installed in the binary
1124 package under /usr/share/appdata/. I did this by adding the following
1125 line to debian/pymissile.install:&lt;/p&gt;
1126
1127 &lt;blockquote&gt;&lt;pre&gt;
1128 debian/pymissile.metainfo.xml usr/share/appdata
1129 &lt;/pre&gt;&lt;/blockquote&gt;
1130
1131 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
1132 all packages useful on the current computer automatically, and the GUI
1133 pop-up handler will propose to install the package not already
1134 installed if a hardware dongle is inserted into the machine in
1135 question.&lt;/p&gt;
1136
1137 &lt;p&gt;Details of the modalias field in appstream is available from the
1138 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
1139
1140 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
1141 try running this command on the command line:&lt;/p&gt;
1142
1143 &lt;blockquote&gt;&lt;pre&gt;
1144 cat $(find /sys/devices/|grep modalias)
1145 &lt;/pre&gt;&lt;/blockquote&gt;
1146
1147 &lt;p&gt;To learn more about the isenkram system, please check out
1148 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
1149 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
1150 </description>
1151 </item>
1152
1153 <item>
1154 <title>The GNU General Public License is not magic pixie dust</title>
1155 <link>http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
1156 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
1157 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
1158 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
1159 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
1160 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
1161 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
1162 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
1163
1164 &lt;blockquote&gt;
1165
1166 &lt;p&gt;&lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;&lt;img src=&quot;https://sfconservancy.org/img/supporter-badge.png&quot; width=&quot;194&quot; height=&quot;90&quot; alt=&quot;Become a Software Freedom Conservancy Supporter!&quot; align=&quot;right&quot; border=&quot;0&quot; /&gt;&lt;/a&gt;&lt;/p&gt;
1167
1168 &lt;blockquote&gt;
1169 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
1170
1171 The first step is to choose a
1172 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
1173 code.&lt;br/&gt;
1174
1175 The next step is, when someone fails to follow that copyleft license,
1176 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
1177
1178 and its a simple fact of our modern society that such type of
1179 work&lt;br/&gt;
1180
1181 is incredibly expensive to do and incredibly difficult to do.
1182 &lt;/blockquote&gt;
1183
1184 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
1185 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
1186 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
1187 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
1188
1189 &lt;p&gt;As the Debian Website
1190 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
1191 &lt;a href=&quot;https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=1.24&amp;amp;r2=1.25&quot;&gt;to&lt;/a&gt;
1192 imply, public domain and permissively licensed software can lead to
1193 the production of more proprietary software as people discover useful
1194 software, extend it and or incorporate it into their hardware or
1195 software products. Copyleft licenses such as the GNU GPL were created
1196 to close off this avenue to the production of proprietary software but
1197 such licenses are not enough. With the ongoing adoption of Free
1198 Software by individuals and groups, inevitably the community&#39;s
1199 expectations of license compliance are violated, usually out of
1200 ignorance of the way Free Software works, but not always. As Karen
1201 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
1202 Freedom&quot;&gt;FaiF&lt;/a&gt;
1203 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
1204 copyleft is nothing if no-one is willing and able to stand up in court
1205 to protect it. The reality of today&#39;s world is that legal
1206 representation is expensive, difficult and time consuming. With
1207 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
1208 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
1209 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
1210 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
1211 of the Linux project, Debian and other groups against GPL violations.
1212 In March the SFC supported a
1213 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
1214 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
1215 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
1216 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
1217 kernel. Since then two of their sponsors pulled corporate funding and
1218 conferences
1219 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
1220 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
1221 less on corporate funding and more on the broad community of
1222 individuals who support Free Software and copyleft. So the SFC has
1223 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
1224 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
1225 a community of folks who stand up for copyleft and the GPL by
1226 supporting their work on promoting and supporting copyleft and Free
1227 Software.&lt;/p&gt;
1228
1229 &lt;p&gt;If you support Free Software,
1230 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
1231 what the SFC do, agree with their
1232 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
1233 principles&lt;/a&gt;, are happy about their
1234 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
1235 work on a project that is an SFC
1236 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
1237 just want to stand up for copyleft, please join
1238 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
1239 Allan Webber&lt;/a&gt;,
1240 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
1241 Smith&lt;/a&gt;,
1242 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
1243 Bacon&lt;/a&gt;, myself and
1244 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
1245 becoming a
1246 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
1247 next week your donation will be
1248 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
1249 by an anonymous donor. Please also consider asking your employer to
1250 match your donation or become a sponsor of SFC. Don&#39;t forget to
1251 spread the word about your support for SFC via email, your blog and or
1252 social media accounts.&lt;/p&gt;
1253
1254 &lt;/blockquote&gt;
1255
1256 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
1257 of Software Freedom Conservancy myself. Perhaps you should be a
1258 supporter too?&lt;/p&gt;
1259 </description>
1260 </item>
1261
1262 <item>
1263 <title>PGP key transition statement for key EE4E02F9</title>
1264 <link>http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
1265 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
1266 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
1267 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
1268 set it up properly. I wanted to generate it offline and have it
1269 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
1270 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
1271 time to sit down with an offline machine almost took forever. But
1272 finally I&#39;ve been able to complete the process, and have now moved
1273 from my old GPG key to a new GPG key. See
1274 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
1275 full transition statement, signed with both my old and new key&lt;/a&gt; for
1276 the details. This is my new key:&lt;/p&gt;
1277
1278 &lt;pre&gt;
1279 pub 3936R/&lt;a href=&quot;http://pgp.cs.uu.nl/stats/111D6B29EE4E02F9.html&quot;&gt;111D6B29EE4E02F9&lt;/a&gt; 2015-11-03 [expires: 2019-11-14]
1280 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
1281 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
1282 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
1283 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
1284 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
1285 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
1286 &lt;/pre&gt;
1287
1288 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
1289 my old key.&lt;/p&gt;
1290
1291 &lt;p&gt;If you signed my old key
1292 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
1293 I&#39;d very much appreciate a signature on my new key, details and
1294 instructions in the transition statement. I m happy to reciprocate if
1295 you have a similarly signed transition statement to present.&lt;/p&gt;
1296 </description>
1297 </item>
1298
1299 <item>
1300 <title>The life and death of a laptop battery</title>
1301 <link>http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
1302 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
1303 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
1304 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
1305 But this do not last. The last few laptops gave me a feeling that
1306 within a year, the life time is just a fraction of what it used to be,
1307 and it slowly become painful to use the laptop without power connected
1308 all the time. Because of this, when I got a new Thinkpad X230 laptop
1309 about two years ago, I decided to monitor its battery state to have
1310 more hard facts when the battery started to fail.&lt;/p&gt;
1311
1312 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
1313
1314 &lt;p&gt;First I tried to find a sensible Debian package to record the
1315 battery status, assuming that this must be a problem already handled
1316 by someone else. I found
1317 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
1318 which collects statistics from the battery, but it was completely
1319 broken. I sent a few suggestions to the maintainer, but decided to
1320 write my own collector as a shell script while I waited for feedback
1321 from him. Via
1322 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
1323 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
1324 discovered
1325 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
1326 available in Debian.&lt;/p&gt;
1327
1328 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
1329 battery stats ever since. Now my
1330 /var/log/hjemmenett-battery-status.log file contain around 115,000
1331 measurements, from the time the battery was working great until now,
1332 when it is unable to charge above 7% of original capacity. My
1333 collector shell script is quite simple and look like this:&lt;/p&gt;
1334
1335 &lt;pre&gt;
1336 #!/bin/sh
1337 # Inspired by
1338 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
1339 # See also
1340 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
1341 logfile=/var/log/hjemmenett-battery-status.log
1342
1343 files=&quot;manufacturer model_name technology serial_number \
1344 energy_full energy_full_design energy_now cycle_count status&quot;
1345
1346 if [ ! -e &quot;$logfile&quot; ] ; then
1347 (
1348 printf &quot;timestamp,&quot;
1349 for f in $files; do
1350 printf &quot;%s,&quot; $f
1351 done
1352 echo
1353 ) &gt; &quot;$logfile&quot;
1354 fi
1355
1356 log_battery() {
1357 # Print complete message in one echo call, to avoid race condition
1358 # when several log processes run in parallel.
1359 msg=$(printf &quot;%s,&quot; $(date +%s); \
1360 for f in $files; do \
1361 printf &quot;%s,&quot; $(cat $f); \
1362 done)
1363 echo &quot;$msg&quot;
1364 }
1365
1366 cd /sys/class/power_supply
1367
1368 for bat in BAT*; do
1369 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
1370 done
1371 &lt;/pre&gt;
1372
1373 &lt;p&gt;The script is called when the power management system detect a
1374 change in the power status (power plug in or out), and when going into
1375 and out of hibernation and suspend. In addition, it collect a value
1376 every 10 minutes. This make it possible for me know when the battery
1377 is discharging, charging and how the maximum charge change over time.
1378 The code for the Debian package
1379 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
1380 available on github&lt;/a&gt;.&lt;/p&gt;
1381
1382 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
1383
1384 &lt;pre&gt;
1385 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
1386 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
1387 [...]
1388 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
1389 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
1390 &lt;/pre&gt;
1391
1392 &lt;p&gt;I wrote a small script to create a graph of the charge development
1393 over time. This graph depicted above show the slow death of my laptop
1394 battery.&lt;/p&gt;
1395
1396 &lt;p&gt;But why is this happening? Why are my laptop batteries always
1397 dying in a year or two, while the batteries of space probes and
1398 satellites keep working year after year. If we are to believe
1399 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
1400 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
1401 chance, and the fix is to not charge the Lithium-ion batteries to 100%
1402 all the time, but to stay below 90% of full charge most of the time.
1403 I&#39;ve been told that the Tesla electric cars
1404 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
1405 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
1406 100% when preparing for a longer trip (not that I would want a car
1407 like Tesla where rights to privacy is abandoned, but that is another
1408 story), which I guess is the option we should have for laptops on
1409 Linux too.&lt;/p&gt;
1410
1411 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
1412 stop charging at 80%, unless requested to charge to 100% once in
1413 preparation for a longer trip? I found
1414 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
1415 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
1416 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
1417 load).&lt;/p&gt;
1418
1419 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
1420 at the start. I also wonder why the &quot;full capacity&quot; increases some
1421 times, and if it is possible to repeat the process to get the battery
1422 back to design capacity. And I wonder if the discharge and charge
1423 speed change over time, or if this stay the same. I did not yet try
1424 to write a tool to calculate the derivative values of the battery
1425 level, but suspect some interesting insights might be learned from
1426 those.&lt;/p&gt;
1427
1428 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
1429 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
1430 packages instead of the tp-smapi-dkms package I had tried to use
1431 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
1432 and stop. I&#39;ve done so now, but expect my existing battery is toast
1433 and need to be replaced. The proposal is unfortunately Thinkpad
1434 specific.&lt;/p&gt;
1435 </description>
1436 </item>
1437
1438 <item>
1439 <title>New laptop - some more clues and ideas based on feedback</title>
1440 <link>http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
1441 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
1442 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
1443 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
1444 need for a new laptop, and provided very useful feedback. I wish to
1445 thank every one of these. Several pointed me to the possibility of
1446 fixing my X230, and I am already in the process of getting Lenovo to
1447 do so thanks to the on site, next day support contract covering the
1448 machine. But the battery is almost useless (I expect to replace it
1449 with a non-official battery) and I do not expect the machine to live
1450 for many more years, so it is time to plan its replacement. If I did
1451 not have a support contract, it was suggested to find replacement parts
1452 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
1453 might present a language barrier as I do not understand French.&lt;/p&gt;
1454
1455 &lt;p&gt;One tip I got was to use the
1456 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
1457 compare laptop models. It seem to have more models available than
1458 prisjakt.no. Another tip I got from someone I know have similar
1459 keyboard preferences was that the HP EliteBook 840 keyboard is not
1460 very good, and this matches my experience with earlier EliteBook
1461 keyboards I tested. Because of this, I will not consider it any further.
1462
1463 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
1464 newest Thinkpad X model. The keyboard reintroduces mouse buttons
1465 (which is missing from the X240), and is working fairly well with
1466 Debian Sid/Unstable according to
1467 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
1468 got on the keyboard quality are not consistent. Some say the keyboard
1469 is good, others say it is ok, while others say it is not very good.
1470 Those with experience from X41 and and X60 agree that the X250
1471 keyboard is not as good as those trusty old laptops, and suggest I
1472 keep and fix my X230 instead of upgrading, or get a used X230 to
1473 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
1474 activity and battery status, which is very convenient on my X230. I&#39;m
1475 also told that the CPU fan is running very often, making it a bit
1476 noisy. In any case, the X250 do not work out of the box with Debian
1477 Stable/Jessie, one of my requirements.&lt;/p&gt;
1478
1479 &lt;p&gt;I have also gotten a few vendor proposals, one was
1480 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
1481 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
1482 The latter look very attractive to me.&lt;/p&gt;
1483
1484 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
1485 as I keep looking for a replacement.&lt;/p&gt;
1486
1487 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
1488 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
1489 different
1490 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
1491 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
1492 </description>
1493 </item>
1494
1495 <item>
1496 <title>Time to find a new laptop, as the old one is broken after only two years</title>
1497 <link>http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</link>
1498 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</guid>
1499 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
1500 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
1501 replacement soon. The left 5 cm of the screen on my Thinkpad X230
1502 started flickering yesterday, and I suspect the cause is a broken
1503 cable, as changing the angle of the screen some times get rid of the
1504 flickering.&lt;/p&gt;
1505
1506 &lt;p&gt;My requirements have not really changed since I bought it, and is
1507 still as
1508 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
1509 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
1510 good help from
1511 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
1512 where I could select at least a few of the requirements (mouse pin,
1513 wifi, weight) and go through the rest manually. Three button mouse
1514 and a good keyboard is not available as an option, and all the three
1515 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
1516 G2) lack three mouse buttons). It is also unclear to me how good the
1517 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
1518 the keyboard, even if the quality and robustness in the X series have
1519 deteriorated since X41.&lt;/p&gt;
1520
1521 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
1522 seem sensible to me? Are there better services around to search the
1523 set of available laptops for features? Please send me an email if you
1524 have suggestions.&lt;/p&gt;
1525
1526 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
1527 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
1528 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
1529 </description>
1530 </item>
1531
1532 <item>
1533 <title>How to stay with sysvinit in Debian Jessie</title>
1534 <link>http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
1535 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
1536 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
1537 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
1538 sysvinit as its boot system by default. But how can one keep using
1539 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
1540 courtesy of
1541 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
1542 Schubert&lt;/a&gt; and
1543 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
1544 McVittie&lt;/a&gt;.
1545
1546 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
1547 keep sysvinit as your boot system, create a file
1548 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
1549 you upgrade:&lt;/p&gt;
1550
1551 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1552 Package: systemd-sysv
1553 Pin: release o=Debian
1554 Pin-Priority: -1
1555 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1556
1557 &lt;p&gt;This file content will tell apt and aptitude to not consider
1558 installing systemd-sysv as part of any installation and upgrade
1559 solution when resolving dependencies, and thus tell it to avoid
1560 systemd as a default boot system. The end result should be that the
1561 upgraded system keep using sysvinit.&lt;/p&gt;
1562
1563 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
1564 get sysvinit installed by default (debootstrap used by
1565 debian-installer have no option for this), but one can tell the
1566 installer to switch to sysvinit before the first boot. Either by
1567 using a kernel argument to the installer, or by adding a line to the
1568 preseed file used. First, the kernel command line argument:
1569
1570 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1571 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
1572 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1573
1574 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
1575
1576 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1577 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
1578 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
1579
1580 &lt;p&gt;One can of course also do this after the first boot by installing
1581 the sysvinit-core package.&lt;/p&gt;
1582
1583 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
1584 sysvinit boot sequence in Debian have several hardware specific bugs
1585 on Linux caused by the fact that it is unpredictable when hardware
1586 devices show up during boot. But on the other hand, the new default
1587 boot system still have a few rough edges I hope will be fixed before
1588 Jessie is released.&lt;/p&gt;
1589
1590 &lt;p&gt;Update 2014-11-26: Inspired by
1591 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
1592 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
1593 line.&lt;/p&gt;
1594 </description>
1595 </item>
1596
1597 <item>
1598 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
1599 <link>http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
1600 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
1601 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
1602 <description>&lt;p&gt;The right to communicate with your friends and family in private,
1603 without anyone snooping, is a right every citicen have in a liberal
1604 democracy. But this right is under serious attack these days.&lt;/p&gt;
1605
1606 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
1607 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
1608 the whisleblower Snowden) more expensive for Internet email,
1609 is to deliver all email using SMTP via Tor. Such SMTP option would be
1610 a nice addition to the FreedomBox project if we could send email
1611 between FreedomBox machines without leaking metadata about the emails
1612 to the people peeking on the wire. I
1613 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
1614 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
1615 lot of useful feedback and suggestions. It also became obvious to me
1616 that this was not a novel idea, as the same idea was tested and
1617 documented by Johannes Berg as early as 2006, and both
1618 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
1619 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
1620 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
1621
1622 &lt;p&gt;To implement such system one need to set up a Tor hidden service
1623 providing the SMTP protocol on port 25, and use email addresses
1624 looking like username@hidden-service-name.onion. With such addresses
1625 the connections to port 25 on hidden-service-name.onion using Tor will
1626 go to the correct SMTP server. To do this, one need to configure the
1627 Tor daemon to provide the hidden service and the mail server to accept
1628 emails for this .onion domain. To learn more about Exim configuration
1629 in Debian and test the design provided by Johannes Berg in his FAQ, I
1630 set out yesterday to create a Debian package for making it trivial to
1631 set up such SMTP over Tor service based on Debian. Getting it to work
1632 were fairly easy, and
1633 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
1634 source code for the Debian package&lt;/a&gt; is available from github. I
1635 plan to move it into Debian if further testing prove this to be a
1636 useful approach.&lt;/p&gt;
1637
1638 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
1639 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
1640 get rid of exim4). Install tor, clone the git repository mentioned
1641 above, build the deb and install it on the machine. Next, run
1642 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
1643 the instructions to get the service up and running. Restart tor and
1644 exim when it is done, and test mail delivery using swaks like
1645 this:&lt;/p&gt;
1646
1647 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1648 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
1649 --to fbx@dutlqrrmjhtfa3vp.onion
1650 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1651
1652 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
1653 address with your own address to test your server. :)&lt;/p&gt;
1654
1655 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
1656 easier and more automatic. Especially the tor setup need more work.
1657 Also, the package include a tor-smtp tool written in C, but its task
1658 should probably be rewritten in some script language to make the deb
1659 architecture independent. It would probably also make the code easier
1660 to review. The tor-smtp tool currently need to listen on a socket for
1661 exim to talk to it and is started using xinetd. It would be better if
1662 no daemon and no socket is needed. I suspect it is possible to get
1663 exim to run a command line tool for delivery instead of talking to a
1664 socket, and hope to figure out how in a future version of this
1665 system.&lt;/p&gt;
1666
1667 &lt;p&gt;Until I wipe my test machine, I can be reached using the
1668 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
1669 SMTorP. :)&lt;/p&gt;
1670 </description>
1671 </item>
1672
1673 <item>
1674 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
1675 <link>http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
1676 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
1677 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
1678 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
1679 alioth.debian.org, you know the web interface is fairly slow to
1680 operate. First you visit one web page, enter the moderation password
1681 and get a new page shown with a list of all the messages to moderate
1682 and various options for each email address. This take a while for
1683 every list you moderate, and you need to do it regularly to do a good
1684 job as a list moderator. But there is a quick alternative,
1685 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
1686 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
1687 to moderate in a fraction of a second. Here is a test run on two
1688 lists I recently took over:&lt;/p&gt;
1689
1690 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1691 % time listadmin xiph
1692 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
1693 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
1694
1695 real 0m1.709s
1696 user 0m0.232s
1697 sys 0m0.012s
1698 %
1699 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1700
1701 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
1702 there are no message in the moderation queue. Every morning I
1703 currently moderate 68 mailman lists, and it normally take around two
1704 minutes. When I took over the two pkg-xiph lists above a few days
1705 ago, there were 400 emails waiting in the moderator queue. It took me
1706 less than 15 minutes to process them all using the listadmin
1707 program.&lt;/p&gt;
1708
1709 &lt;p&gt;If you install
1710 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
1711 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
1712 with content like this, the moderation task is a breeze:&lt;/p&gt;
1713
1714 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1715 username username@example.org
1716 spamlevel 23
1717 default discard
1718 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
1719
1720 password secret
1721 adminurl https://{domain}/mailman/admindb/{list}
1722 mailman-list@lists.example.com
1723
1724 password hidden
1725 other-list@otherserver.example.org
1726 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1727
1728 &lt;p&gt;There are other options to set as well. Check the manual page to
1729 learn the details.&lt;/p&gt;
1730
1731 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
1732 the SSL certificate is self signed or not properly signed by a
1733 generally accepted signing authority, you can set a environment
1734 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
1735
1736 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1737 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
1738 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1739
1740 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
1741 can provide an argument to the listadmin script like I do in the
1742 initial screen dump (the xiph argument). Using an argument, only
1743 lists matching the argument string will be processed. This make it
1744 quick to accept messages if you notice the moderation request in your
1745 email.&lt;/p&gt;
1746
1747 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
1748 mailing lists, as I simply do not have time to spend on that if the
1749 process was any slower. The listadmin program have saved me hours of
1750 time I could spend elsewhere over the years. It truly is nice free
1751 software.&lt;/p&gt;
1752
1753 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1754 activities, please send Bitcoin donations to my address
1755 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1756
1757 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
1758 configuration example. Also, I&#39;ve been told that the
1759 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
1760 sure why.&lt;/p&gt;
1761 </description>
1762 </item>
1763
1764 <item>
1765 <title>Debian Jessie, PXE and automatic firmware installation</title>
1766 <link>http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
1767 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
1768 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
1769 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
1770 problem that the WiFi card require some firmware to work properly.
1771 And it has been a pain to fix this using preseeding in Debian.
1772 Normally something more is needed. But thanks to
1773 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
1774 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
1775 to do this using simple preseeding.&lt;/p&gt;
1776
1777 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
1778 firmware for the hardware found in the machine (actually, requested by
1779 the kernel modules for the hardware). (It can also install user space
1780 programs supporting the hardware detected, but that is not the focus
1781 of this story.)&lt;/p&gt;
1782
1783 &lt;p&gt;To get this working in the default installation, two preeseding
1784 values are needed. First, the isenkram-cli package must be installed
1785 into the target chroot (aka the hard drive) before tasksel is executed
1786 in the pkgsel step of the debian-installer system. This is done by
1787 preseeding the base-installer/includes debconf value to include the
1788 isenkram-cli package. The package name is next passed to debootstrap
1789 for installation. With the isenkram-cli package in place, tasksel
1790 will automatically use the isenkram tasks to detect hardware specific
1791 packages for the machine being installed and install them, because
1792 isenkram-cli contain tasksel tasks.&lt;/p&gt;
1793
1794 &lt;p&gt;Second, one need to enable the non-free APT repository, because
1795 most firmware unfortunately is non-free. This is done by preseeding
1796 the apt-mirror-setup step. This is unfortunate, but for a lot of
1797 hardware it is the only option in Debian.&lt;/p&gt;
1798
1799 &lt;p&gt;The end result is two lines needed in your preseeding file to get
1800 firmware installed automatically by the installer:&lt;/p&gt;
1801
1802 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1803 base-installer base-installer/includes string isenkram-cli
1804 apt-mirror-setup apt-setup/non-free boolean true
1805 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1806
1807 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
1808 both firmware and user space packages when using this method. It also
1809 do not work well, so use version 0.15 or later. Installing both
1810 firmware and user space packages might give you a bit more than you
1811 want, so I decided to split the tasksel task in two, one for firmware
1812 and one for user space programs. The firmware task is enabled by
1813 default, while the one for user space programs is not. This split is
1814 implemented in the package currently in unstable.&lt;/p&gt;
1815
1816 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
1817 this recipe work for you. :)&lt;/p&gt;
1818
1819 &lt;p&gt;So, I bet you are wondering, how can this work. First and
1820 foremost, it work because tasksel is modular, and driven by whatever
1821 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
1822 isenkram-cli package place two files for tasksel to find. First there
1823 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
1824
1825 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1826 Task: isenkram-packages
1827 Section: hardware
1828 Description: Hardware specific packages (autodetected by isenkram)
1829 Based on the detected hardware various hardware specific packages are
1830 proposed.
1831 Test-new-install: show show
1832 Relevance: 8
1833 Packages: for-current-hardware
1834
1835 Task: isenkram-firmware
1836 Section: hardware
1837 Description: Hardware specific firmware packages (autodetected by isenkram)
1838 Based on the detected hardware various hardware specific firmware
1839 packages are proposed.
1840 Test-new-install: mark show
1841 Relevance: 8
1842 Packages: for-current-hardware-firmware
1843 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1844
1845 &lt;p&gt;The key parts are Test-new-install which indicate how the task
1846 should be handled and the Packages line referencing to a script in
1847 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
1848 list of packages to install. The for-current-hardware-firmware script
1849 look like this to list relevant firmware for the machine:
1850
1851 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1852 #!/bin/sh
1853 #
1854 PATH=/usr/sbin:$PATH
1855 export PATH
1856 isenkram-autoinstall-firmware -l
1857 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1858
1859 &lt;p&gt;With those two pieces in place, the firmware is installed by
1860 tasksel during the normal d-i run. :)&lt;/p&gt;
1861
1862 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
1863 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
1864 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
1865 install.&lt;/p&gt;
1866
1867 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
1868 pilots in testing this feature, as isenkram is used there now to
1869 install firmware, replacing the earlier scripts.&lt;/p&gt;
1870 </description>
1871 </item>
1872
1873 <item>
1874 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
1875 <link>http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
1876 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
1877 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
1878 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
1879 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
1880 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
1881 on a screen normally showing the bread types and prizes:&lt;/p&gt;
1882
1883 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2014-10-04-ubuntu-ica-storo-crop.jpeg&quot;&gt;&lt;/p&gt;
1884
1885 &lt;p&gt;If it had booted as it was supposed to, I would never had known
1886 about this hidden Linux installation. It is interesting what
1887 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
1888 </description>
1889 </item>
1890
1891 <item>
1892 <title>New lsdvd release version 0.17 is ready</title>
1893 <link>http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
1894 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
1895 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
1896 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
1897 got a new set of developers a few weeks ago, after the original
1898 developer decided to step down and pass the project to fresh blood.
1899 This project is now maintained by Petter Reinholdtsen and Steve
1900 Dibb.&lt;/p&gt;
1901
1902 &lt;p&gt;I just wrapped up
1903 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
1904 new lsdvd release&lt;/a&gt;, available in git or from
1905 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
1906 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
1907 0.17.&lt;/p&gt;
1908
1909 &lt;ul&gt;
1910
1911 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
1912 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
1913 non-existant, to work around additional copy protection&lt;/li&gt;
1914 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
1915 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
1916 &lt;li&gt;Fix include orders&lt;/li&gt;
1917 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
1918 &lt;li&gt;Fix the chapter count&lt;/li&gt;
1919 &lt;li&gt;Make sure the array size and the array limit used when initialising
1920 the palette size is the same.&lt;/li&gt;
1921 &lt;li&gt;Fix array printing.&lt;/li&gt;
1922 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
1923 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
1924 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
1925 with more GCC compiler warnings.&lt;/li&gt;
1926
1927 &lt;/ul&gt;
1928
1929 &lt;p&gt;This change bring together patches for lsdvd in use in various
1930 Linux and Unix distributions, as well as patches submitted to the
1931 project the last nine years. Please check it out. :)&lt;/p&gt;
1932 </description>
1933 </item>
1934
1935 <item>
1936 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
1937 <link>http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
1938 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
1939 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
1940 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
1941 project&lt;/a&gt; provide a Linux solution for schools, including a
1942 powerful desktop with education software, a central server providing
1943 web pages, user database, user home directories, central login and PXE
1944 boot of both clients without disk and the installation to install Debian
1945 Edu on machines with disk (and a few other services perhaps to small
1946 to mention here). We in the Debian Edu team are currently working on
1947 the Jessie based version, trying to get everything in shape before the
1948 freeze, to avoid having to maintain our own package repository in the
1949 future. The
1950 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
1951 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
1952 work left. Some fatal problems block testing, breaking the installer,
1953 but it is possible to work around these to get anyway. Here is a
1954 recipe on how to get the installation limping along.&lt;/p&gt;
1955
1956 &lt;p&gt;First, download the test ISO via
1957 &lt;a href=&quot;ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;ftp&lt;/a&gt;,
1958 &lt;a href=&quot;http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso&quot;&gt;http&lt;/a&gt;
1959 or rsync (use
1960 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
1961 The ISO build was broken on Tuesday, so we do not get a new ISO every
1962 12 hours or so, but thankfully the ISO we already got we are able to
1963 install with some tweaking.&lt;/p&gt;
1964
1965 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
1966 (use Alt-Ctrl-F2), run&lt;/p&gt;
1967
1968 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1969 nano /usr/bin/edu-eatmydata-install
1970 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1971
1972 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
1973 optimization. Return to the installation, select the profile you want
1974 and continue. Without this change, exim4-config will fail to install
1975 due to a known bug in eatmydata.&lt;/p&gt;
1976
1977 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
1978 this do not work, figure out what your correct value would be. All my
1979 test machines need /dev/sda, so I have no advice if it do not fit
1980 your need.&lt;/p&gt;
1981
1982 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
1983 root after the initial boot from hard drive, and install the
1984 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
1985 or mate. If you want several desktop options, install more than one
1986 metapackage. Once this is done, reboot and you should have a working
1987 graphical login screen. This workaround should no longer be needed
1988 once the education-tasks package version 1.801 enter testing in two
1989 days.&lt;/p&gt;
1990
1991 &lt;p&gt;I believe the ISO build will start working on two days when the new
1992 tasksel package enter testing and Steve McIntyre get a chance to
1993 update the debian-cd git repository. The eatmydata, grub and desktop
1994 issues are already fixed in unstable and testing, and should show up
1995 on the ISO as soon as the ISO build start working again. Well the
1996 eatmydata optimization is really just disabled. The proper fix
1997 require an upload by the eatmydata maintainer applying the patch
1998 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
1999 The rest have proper fixes in unstable.&lt;/p&gt;
2000
2001 &lt;p&gt;I hope this get you going with the installation testing, as we are
2002 quickly running out of time trying to get our Jessie based
2003 installation ready before the distribution freeze in a month.&lt;/p&gt;
2004 </description>
2005 </item>
2006
2007 <item>
2008 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
2009 <link>http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
2010 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
2011 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
2012 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
2013 to handle my fairly large DVD collection. It is a nice command line
2014 tool to get details about a DVD, like title, tracks, track length,
2015 etc, in XML, Perl or human readable format. But lsdvd have not seen
2016 any new development since 2006 and had a few irritating bugs affecting
2017 its use with some DVDs. Upstream seemed to be dead, and in January I
2018 sent a small probe asking for a version control repository for the
2019 project, without any reply. But I use it regularly and would like to
2020 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
2021 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
2022 the project admin, and after getting a reply from him explaining that
2023 he was no longer interested in the project, I asked if I could take
2024 over. And yesterday, I became project admin.&lt;/p&gt;
2025
2026 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
2027 maintainer interested in joining forces to maintain the upstream
2028 project, and I hope we can get a new release out fairly quickly,
2029 collecting the patches spread around on the internet into on place.
2030 I&#39;ve added the relevant Debian patches to the freshly created git
2031 repository, and expect the Gentoo patches to make it too. If you got
2032 a DVD collection and care about command line tools, check out
2033 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
2034 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
2035 list&lt;/a&gt;. :)&lt;/p&gt;
2036 </description>
2037 </item>
2038
2039 <item>
2040 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
2041 <link>http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
2042 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
2043 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
2044 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
2045 a lot quicker. When we install more than 2000 packages in
2046 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
2047 tasksel in the installer, unpacking the binary packages take forever.
2048 A part of the slow I/O issue was discussed in
2049 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
2050 much file system sync-ing done by dpkg, which is the package
2051 responsible for unpacking the binary packages. Other parts (like code
2052 executed by postinst scripts) might also sync to disk during
2053 installation. All this sync-ing to disk do not really make sense to
2054 me. If the machine crash half-way through, I start over, I do not try
2055 to salvage the half installed system. So the failure sync-ing is
2056 supposed to protect against, hardware or system crash, is not really
2057 relevant while the installer is running.&lt;/p&gt;
2058
2059 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
2060 system sync()-ing in a fairly non-intrusive way, without the need to
2061 change the code in several packages. The idea is not new, but I have
2062 not heard anyone propose the approach using dpkg-divert before. It
2063 depend on the small and clever package
2064 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
2065 uses LD_PRELOAD to replace the system functions for syncing data to
2066 disk with functions doing nothing, thus allowing programs to live
2067 dangerous while speeding up disk I/O significantly. Instead of
2068 modifying the implementation of dpkg, apt and tasksel (which are the
2069 packages responsible for selecting, fetching and installing packages),
2070 it occurred to me that we could just divert the programs away, replace
2071 them with a simple shell wrapper calling
2072 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
2073 Two days ago I decided to test the idea, and wrapped up a simple
2074 implementation for the Debian Edu udeb.&lt;/p&gt;
2075
2076 &lt;p&gt;The effect was stunning. In my first test it reduced the running
2077 time of the pkgsel step (installing tasks) from 64 to less than 44
2078 minutes (20 minutes shaved off the installation) on an old Dell
2079 Latitude D505 machine. I am not quite sure what the optimised time
2080 would have been, as I messed up the testing a bit, causing the debconf
2081 priority to get low enough for two questions to pop up during
2082 installation. As soon as I saw the questions I moved the installation
2083 along, but do not know how long the question were holding up the
2084 installation. I did some more measurements using Debian Edu Jessie,
2085 and got these results. The time measured is the time stamp in
2086 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
2087 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
2088 yourself. In Debian Edu, the tasksel dialog do not show up, and the
2089 timing thus do not depend on how quickly the user handle the tasksel
2090 dialog.&lt;/p&gt;
2091
2092 &lt;p&gt;&lt;table&gt;
2093
2094 &lt;tr&gt;
2095 &lt;th&gt;Machine/setup&lt;/th&gt;
2096 &lt;th&gt;Original tasksel&lt;/th&gt;
2097 &lt;th&gt;Optimised tasksel&lt;/th&gt;
2098 &lt;th&gt;Reduction&lt;/th&gt;
2099 &lt;/tr&gt;
2100
2101 &lt;tr&gt;
2102 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
2103 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
2104 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
2105 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
2106 &lt;/tr&gt;
2107
2108 &lt;tr&gt;
2109 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
2110 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
2111 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
2112 &lt;td&gt;23 min 40%&lt;/td&gt;
2113 &lt;/tr&gt;
2114
2115 &lt;tr&gt;
2116 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
2117 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
2118 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
2119 &lt;td&gt;11 min 50%&lt;/td&gt;
2120 &lt;/tr&gt;
2121
2122 &lt;tr&gt;
2123 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
2124 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
2125 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
2126 &lt;td&gt;2 min 33%&lt;/td&gt;
2127 &lt;/tr&gt;
2128
2129 &lt;tr&gt;
2130 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
2131 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
2132 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
2133 &lt;td&gt;4 min 21%&lt;/td&gt;
2134 &lt;/tr&gt;
2135
2136 &lt;/table&gt;&lt;/p&gt;
2137
2138 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
2139 time is spent downloading packages. The connection to the Internet
2140 was 100Mbit/s during testing, so downloading should not be a
2141 significant factor in the measurement. Download typically took a few
2142 seconds to a few minutes, depending on the amount of packages being
2143 installed.&lt;/p&gt;
2144
2145 &lt;p&gt;The speedup is implemented by using two hooks in
2146 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
2147 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
2148 finish-install.d hook to remove the divert at the end of the
2149 installation. I picked the pre-pkgsel.d hook instead of the
2150 post-base-installer.d hook because I test using an ISO without the
2151 eatmydata package included, and the post-base-installer.d hook in
2152 Debian Edu can only operate on packages included in the ISO. The
2153 negative effect of this is that I am unable to activate this
2154 optimization for the kernel installation step in d-i. If the code is
2155 moved to the post-base-installer.d hook, the speedup would be larger
2156 for the entire installation.&lt;/p&gt;
2157
2158 &lt;p&gt;I&#39;ve implemented this in the
2159 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
2160 git repository, and plan to provide the optimization as part of the
2161 Debian Edu installation. If you want to test this yourself, you can
2162 create two files in the installer (or in an udeb). One shell script
2163 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
2164
2165 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2166 #!/bin/sh
2167 set -e
2168 . /usr/share/debconf/confmodule
2169 info() {
2170 logger -t my-pkgsel &quot;info: $*&quot;
2171 }
2172 error() {
2173 logger -t my-pkgsel &quot;error: $*&quot;
2174 }
2175 override_install() {
2176 apt-install eatmydata || true
2177 if [ -x /target/usr/bin/eatmydata ] ; then
2178 for bin in dpkg apt-get aptitude tasksel ; do
2179 file=/usr/bin/$bin
2180 # Test that the file exist and have not been diverted already.
2181 if [ -f /target$file ] ; then
2182 info &quot;diverting $file using eatmydata&quot;
2183 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
2184 &gt; /target$file.edu
2185 chmod 755 /target$file.edu
2186 in-target dpkg-divert --package debian-edu-config \
2187 --rename --quiet --add $file
2188 ln -sf ./$bin.edu /target$file
2189 else
2190 error &quot;unable to divert $file, as it is missing.&quot;
2191 fi
2192 done
2193 else
2194 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
2195 fi
2196 }
2197
2198 override_install
2199 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2200
2201 &lt;p&gt;To clean up, another shell script should go into
2202 /usr/lib/finish-install.d/ with code like this:
2203
2204 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2205 #! /bin/sh -e
2206 . /usr/share/debconf/confmodule
2207 error() {
2208 logger -t my-finish-install &quot;error: $@&quot;
2209 }
2210 remove_install_override() {
2211 for bin in dpkg apt-get aptitude tasksel ; do
2212 file=/usr/bin/$bin
2213 if [ -x /target$file.edu ] ; then
2214 rm /target$file
2215 in-target dpkg-divert --package debian-edu-config \
2216 --rename --quiet --remove $file
2217 rm /target$file.edu
2218 else
2219 error &quot;Missing divert for $file.&quot;
2220 fi
2221 done
2222 sync # Flush file buffers before continuing
2223 }
2224
2225 remove_install_override
2226 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2227
2228 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
2229 edu-eatmydata-install and call it from the pre-pkgsel.d and
2230 finish-install.d scripts.&lt;/p&gt;
2231
2232 &lt;p&gt;By now you might ask if this change should get into the normal
2233 Debian installer too? I suspect it should, but am not sure the
2234 current debian-installer coordinators find it useful enough. It also
2235 depend on the side effects of the change. I&#39;m not aware of any, but I
2236 guess we will see if the change is safe after some more testing.
2237 Perhaps there is some package in Debian depending on sync() and
2238 fsync() having effect? Perhaps it should go into its own udeb, to
2239 allow those of us wanting to enable it to do so without affecting
2240 everyone.&lt;/p&gt;
2241
2242 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
2243 will break installation of all programs using gnutls because of
2244 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
2245 eatmydata package in Debian will solve it.&lt;/p&gt;
2246
2247 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
2248 the optimization work again. And I have discovered that the
2249 dpkg-divert trick is not really needed and implemented a slightly
2250 simpler approach as part of the debian-edu-install package. See
2251 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
2252
2253 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
2254 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
2255 triggering on i386 made it into testing, and broke this installation
2256 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
2257 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
2258 </description>
2259 </item>
2260
2261 <item>
2262 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
2263 <link>http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
2264 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
2265 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
2266 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
2267 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
2268 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
2269 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
2270 learn that there is a large set of publicly available key servers to
2271 use when looking for peoples public key. So far I have used
2272 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
2273 were misbehaving, but those days are ended. The servers I have used
2274 up until yesterday have been slow and some times unavailable. I hope
2275 those problems are gone now.&lt;/p&gt;
2276
2277 &lt;p&gt;Behind the round robin DNS entry of the
2278 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
2279 there is a pool of more than 100 keyservers which are checked every
2280 day to ensure they are well connected and up to date. It must be
2281 better than what I have used so far. :)&lt;/p&gt;
2282
2283 &lt;p&gt;Yesterdays speaker told me that the service is the default
2284 keyserver provided by the default configuration in GnuPG, but this do
2285 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
2286
2287 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
2288 line:&lt;/p&gt;
2289
2290 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2291 keyserver pool.sks-keyservers.net
2292 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2293
2294 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
2295 entries in DNS. Just for fun, I did just that at work, so now every
2296 user of GnuPG at the University of Oslo should find a OpenGPG
2297 keyserver automatically should their need it:&lt;/p&gt;
2298
2299 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2300 % host -t srv _pgpkey-http._tcp.uio.no
2301 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
2302 %
2303 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2304
2305 &lt;p&gt;Now if only
2306 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
2307 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
2308 very happy. It can look up a given key or search for a user ID, but I
2309 normally do not want that, but to find a trust path from my key to
2310 another key. Given a user ID or key ID, I would like to find (and
2311 download) the keys representing a signature path from my key to the
2312 key in question, to be able to get a trust path between the two keys.
2313 This is as far as I can tell not possible today. Perhaps something
2314 for a future version of the protocol?&lt;/p&gt;
2315 </description>
2316 </item>
2317
2318 <item>
2319 <title>From English wiki to translated PDF and epub via Docbook</title>
2320 <link>http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
2321 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
2322 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
2323 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
2324 project&lt;/a&gt; provide an instruction manual for teachers, system
2325 administrators and other users that contain useful tips for setting up
2326 and maintaining a Debian Edu installation. This text is about how the
2327 text processing of this manual is handled in the project.&lt;/p&gt;
2328
2329 &lt;p&gt;One goal of the project is to provide information in the native
2330 language of its users, and for this we need to handle translations.
2331 But we also want to make sure each language contain the same
2332 information, so for this we need a good way to keep the translations
2333 in sync. And we want it to be easy for our users to improve the
2334 documentation, avoiding the need to learn special formats or tools to
2335 contribute, and the obvious way to do this is to make it possible to
2336 edit the documentation using a web browser. We also want it to be
2337 easy for translators to keep the translation up to date, and give them
2338 help in figuring out what need to be translated. Here is the list of
2339 tools and the process we have found trying to reach all these
2340 goals.&lt;/p&gt;
2341
2342 &lt;p&gt;We maintain the authoritative source of our manual in the
2343 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
2344 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
2345 front page with references to the different chapters, several pages
2346 for each chapter, and finally one &quot;collection page&quot; gluing all the
2347 chapters together into one large web page (aka
2348 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
2349 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
2350 processing and translations. Thanks to the fact that the
2351 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
2352 wiki.debian.org support exporting pages in
2353 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
2354 the list of pages to export using the raw version of the AllInOne
2355 page, loop over each of them to generate a Docbook XML version of the
2356 manual. This process also download images and transform image
2357 references to use the locally downloaded images. The generated
2358 Docbook XML files are slightly broken, so some post-processing is done
2359 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
2360 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
2361 a handfull of images. The XML file can now be used to generate PDF, HTML
2362 and epub versions of the English manual. This is the basic step of
2363 our process, making PDF (using dblatex), HTML (using xsltproc) and
2364 epub (using dbtoepub) version from Docbook XML, and the resulting files
2365 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
2366
2367 &lt;p&gt;But English documentation is not enough for us. We want translated
2368 documentation too, and we want to make it easy for translators to
2369 track the English original. For this we use the
2370 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
2371 which allow us to transform the English Docbook XML file into a
2372 translation file (a .pot file), usable with the normal gettext based
2373 translation tools used by those translating free software. The pot
2374 file is used to create and maintain translation files (several .po
2375 files), which the translations update with the native language
2376 translations of all titles, paragraphs and blocks of text in the
2377 original. The next step is combining the original English Docbook XML
2378 and the translation file (say debian-edu-wheezy-manual.nb.po), to
2379 create a translated Docbook XML file (in this case
2380 debian-edu-wheezy-manual.nb.xml). This translated (or partly
2381 translated, if the translation is not complete) Docbook XML file can
2382 then be used like the original to create a PDF, HTML and epub version
2383 of the documentation.&lt;/p&gt;
2384
2385 &lt;p&gt;The translators use different tools to edit the .po files. We
2386 recommend using
2387 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
2388 while some use emacs and vi, others can use web based editors like
2389 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
2390 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
2391 is where the .po file end up, in our git repository. Updated
2392 translations can either be committed directly to git, or submitted as
2393 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
2394 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
2395
2396 &lt;p&gt;One challenge is images, which both might need to be translated (if
2397 they show translated user applications), and are needed in different
2398 formats when creating PDF and HTML versions (epub is a HTML version in
2399 this regard). For this we transform the original PNG images to the
2400 needed density and format during build, and have a way to provide
2401 translated images by storing translated versions in
2402 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
2403 package maintainers know more.&lt;/p&gt;
2404
2405 &lt;p&gt;If you wonder what the result look like, we provide
2406 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
2407 of the documentation packages on the web&lt;/a&gt;. See for example the
2408 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
2409 PDF version&lt;/a&gt; or the
2410 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
2411 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
2412 but perhaps it will be done in the future.&lt;/p&gt;
2413
2414 &lt;p&gt;To learn more, check out
2415 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
2416 debian-edu-doc package&lt;/a&gt;,
2417 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
2418 manual on the wiki&lt;/a&gt; and
2419 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
2420 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
2421 </description>
2422 </item>
2423
2424 <item>
2425 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
2426 <link>http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
2427 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
2428 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
2429 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
2430 related packages relevant for the computer installed automatically.
2431 So I implemented one, using
2432 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
2433 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
2434 run tasksel as user root. You should be presented with a new option,
2435 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
2436 select it, tasksel will install the packages isenkram claim is fit for
2437 the current hardware, hot pluggable or not.&lt;p&gt;
2438
2439 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
2440 description, and the other is the script used to extract the list of
2441 packages to install. The first part is in
2442 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
2443 this:&lt;/p&gt;
2444
2445 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2446 Task: isenkram
2447 Section: hardware
2448 Description: Hardware specific packages (autodetected by isenkram)
2449 Based on the detected hardware various hardware specific packages are
2450 proposed.
2451 Test-new-install: mark show
2452 Relevance: 8
2453 Packages: for-current-hardware
2454 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2455
2456 &lt;p&gt;The second part is in
2457 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
2458 this:&lt;/p&gt;
2459
2460 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2461 #!/bin/sh
2462 #
2463 (
2464 isenkram-lookup
2465 isenkram-autoinstall-firmware -l
2466 ) | sort -u
2467 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2468
2469 &lt;p&gt;All in all, a very short and simple implementation making it
2470 trivial to install the hardware dependent package we all may want to
2471 have installed on our machines. I&#39;ve not been able to find a way to
2472 get tasksel to tell you exactly which packages it plan to install
2473 before doing the installation. So if you are curious or careful,
2474 check the output from the isenkram-* command line tools first.&lt;/p&gt;
2475
2476 &lt;p&gt;The information about which packages are handling which hardware is
2477 fetched either from the isenkram package itself in
2478 /usr/share/isenkram/, from git.debian.org or from the APT package
2479 database (using the Modaliases header). The APT package database
2480 parsing have caused a nasty resource leak in the isenkram daemon (bugs
2481 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
2482 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
2483 the python-apt code (bug
2484 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
2485 workaround I was able to get rid of the file descriptor leak and
2486 reduce the memory leak from ~30 MiB per hardware detection down to
2487 around 2 MiB per hardware detection. It should make the desktop
2488 daemon a lot more useful. The fix is in version 0.7 uploaded to
2489 unstable today.&lt;/p&gt;
2490
2491 &lt;p&gt;I believe the current way of mapping hardware to packages in
2492 Isenkram is is a good draft, but in the future I expect isenkram to
2493 use the AppStream data source for this. A proposal for getting proper
2494 AppStream support into Debian is floating around as
2495 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
2496 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
2497 project&lt;/a&gt; will take place this summer to improve the situation. I
2498 look forward to seeing the result, and welcome patches for isenkram to
2499 start using the information when it is ready.&lt;/p&gt;
2500
2501 &lt;p&gt;If you want your package to map to some specific hardware, either
2502 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
2503 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
2504 package&lt;/a&gt; or submit a bug report with the details to the isenkram
2505 package. See also
2506 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
2507 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
2508 the information will be migrated to AppStream eventually, but for the
2509 moment I got no better place to store it.&lt;/p&gt;
2510 </description>
2511 </item>
2512
2513 <item>
2514 <title>FreedomBox milestone - all packages now in Debian Sid</title>
2515 <link>http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
2516 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
2517 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
2518 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2519 project&lt;/a&gt; is working on providing the software and hardware to make
2520 it easy for non-technical people to host their data and communication
2521 at home, and being able to communicate with their friends and family
2522 encrypted and away from prying eyes. It is still going strong, and
2523 today a major mile stone was reached.&lt;/p&gt;
2524
2525 &lt;p&gt;Today, the last of the packages currently used by the project to
2526 created the system images were accepted into Debian Unstable. It was
2527 the freedombox-setup package, which is used to configure the images
2528 during build and on the first boot. Now all one need to get going is
2529 the build code from the freedom-maker git repository and packages from
2530 Debian. And once the freedombox-setup package enter testing, we can
2531 build everything directly from Debian. :)&lt;/p&gt;
2532
2533 &lt;p&gt;Some key packages used by Freedombox are
2534 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
2535 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
2536 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
2537 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
2538 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
2539 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
2540 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
2541 are plans to integrate more packages into the setup. User
2542 documentation is maintained on the Debian wiki. Please
2543 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
2544 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
2545
2546 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
2547 setup, run this on a Debian machine using a user with sudo rights to
2548 become root:&lt;/p&gt;
2549
2550 &lt;p&gt;&lt;pre&gt;
2551 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2552 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2553 u-boot-tools
2554 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2555 freedom-maker
2556 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2557 &lt;/pre&gt;&lt;/p&gt;
2558
2559 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2560 devices. See the README in the freedom-maker git repo for more
2561 details on the build. If you do not want all three images, trim the
2562 make line. Note that the virtualbox-image target is not really
2563 virtualbox specific. It create a x86 image usable in kvm, qemu,
2564 vmware and any other x86 virtual machine environment. You might need
2565 the version of vmdebootstrap in Jessie to get the build working, as it
2566 include fixes for a race condition with kpartx.&lt;/p&gt;
2567
2568 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2569 method, boot a Debian Wheezy ISO and use this boot argument to load
2570 the preseed values:&lt;/p&gt;
2571
2572 &lt;p&gt;&lt;pre&gt;
2573 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;
2574 &lt;/pre&gt;&lt;/p&gt;
2575
2576 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
2577 it still work.&lt;/p&gt;
2578
2579 &lt;p&gt;If you wonder how to help, one task you could look at is using
2580 systemd as the boot system. It will become the default for Linux in
2581 Jessie, so we need to make sure it is usable on the Freedombox. I did
2582 a simple test a few weeks ago, and noticed dnsmasq failed to start
2583 during boot when using systemd. I suspect there are other problems
2584 too. :) To detect problems, there is a test suite included, which can
2585 be run from the plinth web interface.&lt;/p&gt;
2586
2587 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2588 us get the new release published. :) Please join us on
2589 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2590 irc.debian.org)&lt;/a&gt; and
2591 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2592 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2593 </description>
2594 </item>
2595
2596 <item>
2597 <title>S3QL, a locally mounted cloud file system - nice free software</title>
2598 <link>http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
2599 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
2600 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
2601 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
2602 solution for use at home. My requirements are simple, it must be
2603 cheap and locally encrypted (in other words, I keep the encryption
2604 keys, the storage provider do not have access to my private files).
2605 One idea me and my friends had many years ago, before the cloud
2606 storage providers showed up, was to use Google mail as storage,
2607 writing a Linux block device storing blocks as emails in the mail
2608 service provided by Google, and thus get heaps of free space. On top
2609 of this one can add encryption, RAID and volume management to have
2610 lots of (fairly slow, I admit that) cheap and encrypted storage. But
2611 I never found time to implement such system. But the last few weeks I
2612 have looked at a system called
2613 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
2614 mounted network backed file system with the features I need.&lt;/p&gt;
2615
2616 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
2617 handling several different storage providers, any with Amazon S3,
2618 Google Drive or OpenStack API. There are heaps of such storage
2619 providers. S3QL can also use a local directory as storage, which
2620 combined with sshfs allow for file storage on any ssh server. S3QL
2621 include support for encryption, compression, de-duplication, snapshots
2622 and immutable file systems, allowing me to mount the remote storage as
2623 a local mount point, look at and use the files as if they were local,
2624 while the content is stored in the cloud as well. This allow me to
2625 have a backup that should survive fire. The file system can not be
2626 shared between several machines at the same time, as only one can
2627 mount it at the time, but any machine with the encryption key and
2628 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
2629
2630 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
2631 package is included already. So to get started, run &lt;tt&gt;apt-get
2632 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
2633 Greenqloud, after reading their nice recipe on
2634 &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
2635 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
2636 in Iceland more than those in USA when it come to keeping my personal
2637 data safe and private, and thus would rather spend money on a company
2638 in Iceland. Another nice recipe is available from the article
2639 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
2640 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
2641 Admin magazine. When the provider is picked, figure out how to get
2642 the API key needed to connect to the storage API. With Greencloud,
2643 the key did not show up until I had added payment details to my
2644 account.&lt;/p&gt;
2645
2646 &lt;p&gt;Armed with the API access details, it is time to create the file
2647 system. First, create a new bucket in the cloud. This bucket is the
2648 file system storage area. I picked a bucket name reflecting the
2649 machine that was going to store data there, but any name will do.
2650 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
2651 the API login and password, and a locally created password. Store it
2652 all in ~root/.s3ql/authinfo2 like this:
2653
2654 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2655 [s3c]
2656 storage-url: s3c://s.greenqloud.com:443/bucket-name
2657 backend-login: API-login
2658 backend-password: API-password
2659 fs-passphrase: local-password
2660 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2661
2662 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
2663 but any sensible way to create a fairly random password should do it.
2664 Armed with these details, it is now time to run mkfs, entering the API
2665 details and password to create it:&lt;/p&gt;
2666
2667 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2668 # mkdir -m 700 /var/lib/s3ql-cache
2669 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2670 --ssl s3c://s.greenqloud.com:443/bucket-name
2671 Enter backend login:
2672 Enter backend password:
2673 Before using S3QL, make sure to read the user&#39;s guide, especially
2674 the &#39;Important Rules to Avoid Loosing Data&#39; section.
2675 Enter encryption password:
2676 Confirm encryption password:
2677 Generating random encryption key...
2678 Creating metadata tables...
2679 Dumping metadata...
2680 ..objects..
2681 ..blocks..
2682 ..inodes..
2683 ..inode_blocks..
2684 ..symlink_targets..
2685 ..names..
2686 ..contents..
2687 ..ext_attributes..
2688 Compressing and uploading metadata...
2689 Wrote 0.00 MB of compressed metadata.
2690 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2691
2692 &lt;p&gt;The next step is mounting the file system to make the storage available.
2693
2694 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2695 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2696 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2697 Using 4 upload threads.
2698 Downloading and decompressing metadata...
2699 Reading metadata...
2700 ..objects..
2701 ..blocks..
2702 ..inodes..
2703 ..inode_blocks..
2704 ..symlink_targets..
2705 ..names..
2706 ..contents..
2707 ..ext_attributes..
2708 Mounting filesystem...
2709 # df -h /s3ql
2710 Filesystem Size Used Avail Use% Mounted on
2711 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
2712 #
2713 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2714
2715 &lt;p&gt;The file system is now ready for use. I use rsync to store my
2716 backups in it, and as the metadata used by rsync is downloaded at
2717 mount time, no network traffic (and storage cost) is triggered by
2718 running rsync. To unmount, one should not use the normal umount
2719 command, as this will not flush the cache to the cloud storage, but
2720 instead running the umount.s3ql command like this:
2721
2722 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2723 # umount.s3ql /s3ql
2724 #
2725 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2726
2727 &lt;p&gt;There is a fsck command available to check the file system and
2728 correct any problems detected. This can be used if the local server
2729 crashes while the file system is mounted, to reset the &quot;already
2730 mounted&quot; flag. This is what it look like when processing a working
2731 file system:&lt;/p&gt;
2732
2733 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2734 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
2735 Using cached metadata.
2736 File system seems clean, checking anyway.
2737 Checking DB integrity...
2738 Creating temporary extra indices...
2739 Checking lost+found...
2740 Checking cached objects...
2741 Checking names (refcounts)...
2742 Checking contents (names)...
2743 Checking contents (inodes)...
2744 Checking contents (parent inodes)...
2745 Checking objects (reference counts)...
2746 Checking objects (backend)...
2747 ..processed 5000 objects so far..
2748 ..processed 10000 objects so far..
2749 ..processed 15000 objects so far..
2750 Checking objects (sizes)...
2751 Checking blocks (referenced objects)...
2752 Checking blocks (refcounts)...
2753 Checking inode-block mapping (blocks)...
2754 Checking inode-block mapping (inodes)...
2755 Checking inodes (refcounts)...
2756 Checking inodes (sizes)...
2757 Checking extended attributes (names)...
2758 Checking extended attributes (inodes)...
2759 Checking symlinks (inodes)...
2760 Checking directory reachability...
2761 Checking unix conventions...
2762 Checking referential integrity...
2763 Dropping temporary indices...
2764 Backing up old metadata...
2765 Dumping metadata...
2766 ..objects..
2767 ..blocks..
2768 ..inodes..
2769 ..inode_blocks..
2770 ..symlink_targets..
2771 ..names..
2772 ..contents..
2773 ..ext_attributes..
2774 Compressing and uploading metadata...
2775 Wrote 0.89 MB of compressed metadata.
2776 #
2777 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2778
2779 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
2780 quick, about the same speed as local file access. Uploading large
2781 amount of data is to me limited by the bandwidth out of and into my
2782 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
2783 which is very close to my upload speed, and downloading the same
2784 Debian installation ISO gave me 610 kiB/s, close to my download speed.
2785 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
2786 network, not the file system code. I do not know what a good cache
2787 size would be, but suspect that the cache should e larger than your
2788 working set.&lt;/p&gt;
2789
2790 &lt;p&gt;I mentioned that only one machine can mount the file system at the
2791 time. If another machine try, it is told that the file system is
2792 busy:&lt;/p&gt;
2793
2794 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2795 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
2796 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
2797 Using 8 upload threads.
2798 Backend reports that fs is still mounted elsewhere, aborting.
2799 #
2800 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2801
2802 &lt;p&gt;The file content is uploaded when the cache is full, while the
2803 metadata is uploaded once every 24 hour by default. To ensure the
2804 file system content is flushed to the cloud, one can either umount the
2805 file system, or ask S3QL to flush the cache and metadata using
2806 s3qlctrl:
2807
2808 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2809 # s3qlctrl upload-meta /s3ql
2810 # s3qlctrl flushcache /s3ql
2811 #
2812 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2813
2814 &lt;p&gt;If you are curious about how much space your data uses in the
2815 cloud, and how much compression and deduplication cut down on the
2816 storage usage, you can use s3qlstat on the mounted file system to get
2817 a report:&lt;/p&gt;
2818
2819 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2820 # s3qlstat /s3ql
2821 Directory entries: 9141
2822 Inodes: 9143
2823 Data blocks: 8851
2824 Total data size: 22049.38 MB
2825 After de-duplication: 21955.46 MB (99.57% of total)
2826 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
2827 Database size: 2.39 MB (uncompressed)
2828 (some values do not take into account not-yet-uploaded dirty blocks in cache)
2829 #
2830 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2831
2832 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
2833 storage. I did not try to locate them all, but am aware of at least
2834 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
2835 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
2836 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
2837 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
2838 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
2839 accept payment in Bitcoin. Pick one that suit your need. Some of
2840 them provide several GiB of free storage, but the prize models are
2841 quite different and you will have to figure out what suits you
2842 best.&lt;/p&gt;
2843
2844 &lt;p&gt;While researching this blog post, I had a look at research papers
2845 and posters discussing the S3QL file system. There are several, which
2846 told me that the file system is getting a critical check by the
2847 science community and increased my confidence in using it. One nice
2848 poster is titled
2849 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
2850 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
2851 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
2852 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
2853 and Pamela Smith. Please have a look.&lt;/p&gt;
2854
2855 &lt;p&gt;Given my problems with different file systems earlier, I decided to
2856 check out the mounted S3QL file system to see if it would be usable as
2857 a home directory (in other word, that it provided POSIX semantics when
2858 it come to locking and umask handling etc). Running
2859 &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
2860 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
2861 no error was found. So the file system can be used for home
2862 directories, if one chooses to do so.&lt;/p&gt;
2863
2864 &lt;p&gt;If you do not want a locally file system, and want something that
2865 work without the Linux fuse file system, I would like to mention the
2866 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
2867 provide locally encrypted backup using a command line client. It have
2868 a nicer access control system, where one can split out read and write
2869 access, allowing some systems to write to the backup and others to
2870 only read from it.&lt;/p&gt;
2871
2872 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2873 activities, please send Bitcoin donations to my address
2874 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2875 </description>
2876 </item>
2877
2878 <item>
2879 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
2880 <link>http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
2881 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
2882 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
2883 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
2884 project&lt;/a&gt; is working on providing the software and hardware for
2885 making it easy for non-technical people to host their data and
2886 communication at home, and being able to communicate with their
2887 friends and family encrypted and away from prying eyes. It has been
2888 going on for a while, and is slowly progressing towards a new test
2889 release (0.2).&lt;/p&gt;
2890
2891 &lt;p&gt;And what day could be better than the Pi day to announce that the
2892 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
2893 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
2894 system), and can also be installed using a Debian installer preseed
2895 file. The Debian based Freedombox is now based on Debian Jessie,
2896 where most of the needed packages used are already present. Only one,
2897 the freedombox-setup package, is missing. To try to build your own
2898 boot image to test the current status, fetch the freedom-maker scripts
2899 and build using
2900 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
2901 with a user with sudo access to become root:
2902
2903 &lt;pre&gt;
2904 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
2905 freedom-maker
2906 sudo apt-get install git vmdebootstrap mercurial python-docutils \
2907 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
2908 u-boot-tools
2909 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
2910 &lt;/pre&gt;
2911
2912 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
2913 devices. See the README for more details on the build. If you do not
2914 want all three images, trim the make line. But note that thanks to &lt;a
2915 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
2916 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
2917 kpartx call.&lt;/p&gt;
2918
2919 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
2920 method, boot a Debian Wheezy ISO and use this boot argument to load
2921 the preseed values:&lt;/p&gt;
2922
2923 &lt;pre&gt;
2924 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;
2925 &lt;/pre&gt;
2926
2927 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
2928 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
2929 currently hang while setting up APT sources. Killing the
2930 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
2931 installation will get the installation going. This affect all
2932 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
2933
2934 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
2935 us get the new release published. :) Please join us on
2936 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
2937 irc.debian.org)&lt;/a&gt; and
2938 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
2939 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
2940 </description>
2941 </item>
2942
2943 <item>
2944 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
2945 <link>http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
2946 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
2947 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
2948 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
2949 innetgr tools, because I needed them in
2950 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
2951 ng-utils, and it has served me well. I placed the project under the
2952 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
2953 repository. But many years ago, the CVS repository was dropped (lost,
2954 not migrated to new hardware, not sure), and the project have lacked a
2955 proper home since then.&lt;/p&gt;
2956
2957 &lt;p&gt;Last summer, I had a look at the package and made a new release
2958 fixing a irritating crash bug, but was unable to store the changes in
2959 a proper source control system. I applied for a project on
2960 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
2961 to follow up on it. Until today. :)&lt;/p&gt;
2962
2963 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
2964 now have a new home, and a git repository with the highlight of the
2965 history of the project. I published all release tarballs and imported
2966 them into the git repository. As the project is really stable and not
2967 expected to gain new features any time soon, I decided to make a new
2968 release and call it 1.0. Visit the new project home on
2969 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
2970 if you want to check it out. The new version is also uploaded into
2971 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
2972 </description>
2973 </item>
2974
2975 <item>
2976 <title>Testing sysvinit from experimental in Debian Hurd</title>
2977 <link>http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
2978 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
2979 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
2980 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
2981 their changes into sysvinit, to allow them to use the normal sysvinit
2982 boot system instead of their old one. This follow up on the
2983 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
2984 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
2985 get Debian on Hurd working more like Debian on Linux. To get started,
2986 I downloaded a prebuilt hard disk image from
2987 &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;,
2988 and started it using virt-manager.&lt;/p&gt;
2989
2990 &lt;p&gt;The first think I had to do after logging in (root without any
2991 password) was to get the network operational. I followed
2992 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
2993 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
2994 commands as root to get the machine to accept a IP address from the
2995 kvm internal DHCP server:&lt;/p&gt;
2996
2997 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2998 settrans -fgap /dev/netdde /hurd/netdde
2999 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
3000 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
3001 dhclient /dev/eth0
3002 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3003
3004 &lt;p&gt;After this, the machine had internet connectivity, and I could
3005 upgrade it and install the sysvinit packages from experimental and
3006 enable it as the default boot system in Hurd.&lt;/p&gt;
3007
3008 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
3009 running on the machine it for ssh login to work a password need to be
3010 set. Also, note that a bug somewhere in openssh on Hurd block
3011 compression from working. Remember to turn that off on the client
3012 side.&lt;/p&gt;
3013
3014 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
3015 stuff:&lt;/p&gt;
3016
3017 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3018 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
3019 deb http://http.debian.net/debian/ experimental main
3020 EOF
3021 apt-get update
3022 apt-get dist-upgrade
3023 apt-get install -t experimental initscripts sysv-rc sysvinit \
3024 sysvinit-core sysvinit-utils
3025 update-alternatives --config runsystem
3026 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3027
3028 &lt;p&gt;To reboot after switching boot system, you have to use
3029 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
3030 yet a sysvinit process able to receive the signals from the normal
3031 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
3032 upgrading every package and rebooting, the network come up with DHCP
3033 after boot as it should, and the settrans/pkill hack mentioned at the
3034 start is no longer needed. But for some strange reason, there are no
3035 longer any login prompt in the virtual console, so I logged in using
3036 ssh instead.
3037
3038 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
3039 fail some times. No idea what the cause is, but hope the Hurd porters
3040 figure it out. At least Justus said on IRC (#debian-hurd on
3041 irc.debian.org) that they are aware of the problem. A way to reduce
3042 the impact is to upgrade to the Hurd packages built by Justus by
3043 adding this repository to the machine:&lt;/p&gt;
3044
3045 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3046 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
3047 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
3048 EOF
3049 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3050
3051 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
3052 http://ftp.debian-ports.org/debian, because some of the packages in
3053 unstable do not yet include the required patches that are lingering in
3054 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
3055
3056 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3057 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
3058 i emacs - GNU Emacs editor (metapackage)
3059 i gdb - GNU Debugger
3060 i hurd-recommended - Miscellaneous translators
3061 i isc-dhcp-client - ISC DHCP client
3062 i isc-dhcp-common - common files used by all the isc-dhcp* packages
3063 i libc-bin - Embedded GNU C Library: Binaries
3064 i libc-dev-bin - Embedded GNU C Library: Development binaries
3065 i libc0.3 - Embedded GNU C Library: Shared libraries
3066 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
3067 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
3068 i multiarch-support - Transitional package to ensure multiarch compatibilit
3069 i A x11-common - X Window System (X.Org) infrastructure
3070 i xorg - X.Org X Window System
3071 i A xserver-xorg - X.Org X server
3072 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
3073 #
3074 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3075
3076 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
3077 X.org did not work out of the box and I never took the time to follow
3078 the porters instructions to fix it. This time I was interested in the
3079 command line stuff.&lt;p&gt;
3080 </description>
3081 </item>
3082
3083 <item>
3084 <title>New chrpath release 0.16</title>
3085 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
3086 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
3087 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
3088 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
3089 find problems in C, C++ and Java code using static source code
3090 analysis. It can detect a lot of different problems, and is very
3091 useful to find memory and locking bugs in the error handling part of
3092 the source. The company behind it provide
3093 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
3094 a community service&lt;/a&gt;, and many hundred free software projects are
3095 already checked. A few days ago I decided to have a closer look at
3096 the Coverity system, and discovered that the
3097 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
3098 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
3099 projects I am involved with was already registered. But these are
3100 fairly big, and I would also like to have a small and easy project to
3101 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
3102 checking of the chrpath project&lt;/a&gt;. It was
3103 added to the checker and discovered seven potential defects. Six of
3104 these were real, mostly resource &quot;leak&quot; when the program detected an
3105 error. Nothing serious, as the resources would be released a fraction
3106 of a second later when the program exited because of the error, but it
3107 is nice to do it right in case the source of the program some time in
3108 the future end up in a library. Having fixed all defects and added
3109 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
3110 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
3111 publish a new release. These are the release notes:&lt;/p&gt;
3112
3113 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
3114
3115 &lt;ul&gt;
3116
3117 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
3118 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
3119 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
3120
3121 &lt;/ul&gt;
3122
3123 &lt;p&gt;You can
3124 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
3125 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
3126 project if something is wrong with the new release. The test suite
3127 did not discover any old errors, so if you find a new one, please also
3128 include a test suite check.&lt;/p&gt;
3129 </description>
3130 </item>
3131
3132 <item>
3133 <title>New chrpath release 0.15</title>
3134 <link>http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
3135 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
3136 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
3137 <description>&lt;p&gt;After many years break from the package and a vain hope that
3138 development would be continued by someone else, I finally pulled my
3139 acts together this morning and wrapped up a new release of chrpath,
3140 the command line tool to modify the rpath and runpath of already
3141 compiled ELF programs. The update was triggered by the persistence of
3142 Isha Vishnoi at IBM, which needed a new config.guess file to get
3143 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
3144 is working on. I checked the
3145 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
3146 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
3147 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
3148 packages for interesting patches (failed to find the source from
3149 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
3150 These are the release notes:&lt;/p&gt;
3151
3152 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
3153
3154 &lt;ul&gt;
3155
3156 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
3157 with newer architectures. Thanks to isha vishnoi for the heads
3158 up.&lt;/li&gt;
3159
3160 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
3161
3162 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
3163 Matthias Klose.&lt;/li&gt;
3164
3165 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
3166 Petr Machata found in Fedora.&lt;/li&gt;
3167
3168 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
3169 .dynamic is a NULL terminated string. Based on patch found in
3170 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
3171
3172 &lt;/ul&gt;
3173
3174 &lt;p&gt;You can
3175 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
3176 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
3177 project if something is wrong with the new release. The test suite
3178 did not discover any old errors, so if you find a new one, please also
3179 include a testsuite check.&lt;/p&gt;
3180 </description>
3181 </item>
3182
3183 <item>
3184 <title>Debian init.d boot script example for rsyslog</title>
3185 <link>http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
3186 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
3187 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
3188 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
3189 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
3190 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
3191 init.d scripts at all. Here is an example init.d script, ie a rewrite
3192 of /etc/init.d/rsyslog:&lt;/p&gt;
3193
3194 &lt;p&gt;&lt;pre&gt;
3195 #!/lib/init/init-d-script
3196 ### BEGIN INIT INFO
3197 # Provides: rsyslog
3198 # Required-Start: $remote_fs $time
3199 # Required-Stop: umountnfs $time
3200 # X-Stop-After: sendsigs
3201 # Default-Start: 2 3 4 5
3202 # Default-Stop: 0 1 6
3203 # Short-Description: enhanced syslogd
3204 # Description: Rsyslog is an enhanced multi-threaded syslogd.
3205 # It is quite compatible to stock sysklogd and can be
3206 # used as a drop-in replacement.
3207 ### END INIT INFO
3208 DESC=&quot;enhanced syslogd&quot;
3209 DAEMON=/usr/sbin/rsyslogd
3210 &lt;/pre&gt;&lt;/p&gt;
3211
3212 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
3213 script was 137 lines, and the above is just 15 lines, most of it meta
3214 info/comments.&lt;/p&gt;
3215
3216 &lt;p&gt;How to do this, you ask? Well, one create a new script
3217 /lib/init/init-d-script looking something like this:
3218
3219 &lt;p&gt;&lt;pre&gt;
3220 #!/bin/sh
3221
3222 # Define LSB log_* functions.
3223 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
3224 # and status_of_proc is working.
3225 . /lib/lsb/init-functions
3226
3227 #
3228 # Function that starts the daemon/service
3229
3230 #
3231 do_start()
3232 {
3233 # Return
3234 # 0 if daemon has been started
3235 # 1 if daemon was already running
3236 # 2 if daemon could not be started
3237 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
3238 || return 1
3239 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
3240 $DAEMON_ARGS \
3241 || return 2
3242 # Add code here, if necessary, that waits for the process to be ready
3243 # to handle requests from services started subsequently which depend
3244 # on this one. As a last resort, sleep for some time.
3245 }
3246
3247 #
3248 # Function that stops the daemon/service
3249 #
3250 do_stop()
3251 {
3252 # Return
3253 # 0 if daemon has been stopped
3254 # 1 if daemon was already stopped
3255 # 2 if daemon could not be stopped
3256 # other if a failure occurred
3257 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
3258 RETVAL=&quot;$?&quot;
3259 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
3260 # Wait for children to finish too if this is a daemon that forks
3261 # and if the daemon is only ever run from this initscript.
3262 # If the above conditions are not satisfied then add some other code
3263 # that waits for the process to drop all resources that could be
3264 # needed by services started subsequently. A last resort is to
3265 # sleep for some time.
3266 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
3267 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
3268 # Many daemons don&#39;t delete their pidfiles when they exit.
3269 rm -f $PIDFILE
3270 return &quot;$RETVAL&quot;
3271 }
3272
3273 #
3274 # Function that sends a SIGHUP to the daemon/service
3275 #
3276 do_reload() {
3277 #
3278 # If the daemon can reload its configuration without
3279 # restarting (for example, when it is sent a SIGHUP),
3280 # then implement that here.
3281 #
3282 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
3283 return 0
3284 }
3285
3286 SCRIPTNAME=$1
3287 scriptbasename=&quot;$(basename $1)&quot;
3288 echo &quot;SN: $scriptbasename&quot;
3289 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
3290 script=&quot;$1&quot;
3291 shift
3292 . $script
3293 else
3294 exit 0
3295 fi
3296
3297 NAME=$(basename $DAEMON)
3298 PIDFILE=/var/run/$NAME.pid
3299
3300 # Exit if the package is not installed
3301 #[ -x &quot;$DAEMON&quot; ] || exit 0
3302
3303 # Read configuration variable file if it is present
3304 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
3305
3306 # Load the VERBOSE setting and other rcS variables
3307 . /lib/init/vars.sh
3308
3309 case &quot;$1&quot; in
3310 start)
3311 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
3312 do_start
3313 case &quot;$?&quot; in
3314 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
3315 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
3316 esac
3317 ;;
3318 stop)
3319 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
3320 do_stop
3321 case &quot;$?&quot; in
3322 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
3323 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
3324 esac
3325 ;;
3326 status)
3327 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
3328 ;;
3329 #reload|force-reload)
3330 #
3331 # If do_reload() is not implemented then leave this commented out
3332 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
3333 #
3334 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
3335 #do_reload
3336 #log_end_msg $?
3337 #;;
3338 restart|force-reload)
3339 #
3340 # If the &quot;reload&quot; option is implemented then remove the
3341 # &#39;force-reload&#39; alias
3342 #
3343 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
3344 do_stop
3345 case &quot;$?&quot; in
3346 0|1)
3347 do_start
3348 case &quot;$?&quot; in
3349 0) log_end_msg 0 ;;
3350 1) log_end_msg 1 ;; # Old process is still running
3351 *) log_end_msg 1 ;; # Failed to start
3352 esac
3353 ;;
3354 *)
3355 # Failed to stop
3356 log_end_msg 1
3357 ;;
3358 esac
3359 ;;
3360 *)
3361 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
3362 exit 3
3363 ;;
3364 esac
3365
3366 :
3367 &lt;/pre&gt;&lt;/p&gt;
3368
3369 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
3370 lot. I did not really polish the approach, so it might not always
3371 work out of the box, but you get the idea. I did not try very hard to
3372 optimize it nor make it more robust either.&lt;/p&gt;
3373
3374 &lt;p&gt;A better argument for switching init system in Debian than reducing
3375 the size of init scripts (which is a good thing to do anyway), is to
3376 get boot system that is able to handle the kernel events sensibly and
3377 robustly, and do not depend on the boot to run sequentially. The boot
3378 and the kernel have not behaved sequentially in years.&lt;/p&gt;
3379 </description>
3380 </item>
3381
3382 <item>
3383 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
3384 <link>http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
3385 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
3386 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
3387 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
3388 remote display access is the preferred solution with oVirt and RedHat
3389 Enterprise Virtualization, and I was sad to discover the other day
3390 that the browser plugin needed to use these systems seamlessly was
3391 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
3392 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
3393 2013-04-01, so I decided to wrap up a package based on the great work
3394 from Cajus Pollmeier and put it in a collab-maint maintained git
3395 repository to get a package I could use. I would very much like
3396 others to help me maintain the package (or just take over, I do not
3397 mind), but as no-one had volunteered so far, I just uploaded it to
3398 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
3399
3400 &lt;p&gt;The source is now available from
3401 &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;
3402 </description>
3403 </item>
3404
3405 <item>
3406 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
3407 <link>http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
3408 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
3409 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
3410 <description>&lt;p&gt;The
3411 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
3412 program is a a very nice system to create virtual machine images. It
3413 create a image file, add a partition table, mount it and run
3414 debootstrap in the mounted directory to create a Debian system on a
3415 stick. Yesterday, I decided to try to teach it how to make images for
3416 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
3417 of a plan to simplify the build system for
3418 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
3419 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
3420 the virtualbox images, but its current build system made multistrap
3421 based system for Dreamplug images, and it is lacking support for
3422 Raspberry Pi.&lt;/p&gt;
3423
3424 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
3425 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
3426 code and adjusted it to be able to build armel images on my amd64
3427 Debian laptop. I ended up giving vmdebootstrap five new options,
3428 allowing me to replicate the image creation process I use to make
3429 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
3430 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
3431 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
3432 call debootstrap with --foreign and to copy the handler into the
3433 generated chroot before running the second stage. This allow
3434 vmdebootstrap to create armel images on an amd64 host. Next I added
3435 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
3436 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
3437 given file system type, allowing me to create an image with a vfat
3438 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
3439 variant&lt;/tt&gt; option to allow me to create smaller images without the
3440 Debian base system packages installed. Finally, I added an option
3441 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
3442 as a boot loader. It is not needed on the Raspberry Pi and probably
3443 most other non-x86 architectures. The changes were accepted by the
3444 upstream author of vmdebootstrap yesterday and today, and is now
3445 available from
3446 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
3447 upstream project page&lt;/a&gt;.&lt;/p&gt;
3448
3449 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
3450 create a small script (the customize script) to add the non-free
3451 binary blob needed to boot the Raspberry Pi and the APT source
3452 list:&lt;/p&gt;
3453
3454 &lt;p&gt;&lt;pre&gt;
3455 #!/bin/sh
3456 set -e # Exit on first error
3457 rootdir=&quot;$1&quot;
3458 cd &quot;$rootdir&quot;
3459 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
3460 deb http://http.debian.net/debian/ jessie main contrib non-free
3461 EOF
3462 # Install non-free binary blob needed to boot Raspberry Pi. This
3463 # install a kernel somewhere too.
3464 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
3465 -O $rootdir/usr/bin/rpi-update
3466 chmod a+x $rootdir/usr/bin/rpi-update
3467 mkdir -p $rootdir/lib/modules
3468 touch $rootdir/boot/start.elf
3469 chroot $rootdir rpi-update
3470 &lt;/pre&gt;&lt;/p&gt;
3471
3472 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
3473 to build the image:&lt;/p&gt;
3474
3475 &lt;pre&gt;
3476 sudo ./vmdebootstrap \
3477 --variant minbase \
3478 --arch armel \
3479 --distribution jessie \
3480 --mirror http://http.debian.net/debian \
3481 --image test.img \
3482 --size 600M \
3483 --bootsize 64M \
3484 --boottype vfat \
3485 --log-level debug \
3486 --verbose \
3487 --no-kernel \
3488 --no-extlinux \
3489 --root-password raspberry \
3490 --hostname raspberrypi \
3491 --foreign /usr/bin/qemu-arm-static \
3492 --customize `pwd`/customize \
3493 --package netbase \
3494 --package git-core \
3495 --package binutils \
3496 --package ca-certificates \
3497 --package wget \
3498 --package kmod
3499 &lt;/pre&gt;&lt;/p&gt;
3500
3501 &lt;p&gt;The list of packages being installed are the ones needed by
3502 rpi-update to make the image bootable on the Raspberry Pi, with the
3503 exception of netbase, which is needed by debootstrap to find
3504 /etc/hosts with the minbase variant. I really wish there was a way to
3505 set up an Raspberry Pi using only packages in the Debian archive, but
3506 that is not possible as far as I know, because it boots from the GPU
3507 using a non-free binary blob.&lt;/p&gt;
3508
3509 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
3510 probably a few others installed. I have not checked the complete
3511 build dependency list.&lt;/p&gt;
3512
3513 &lt;p&gt;The resulting image will not use the hardware floating point unit
3514 on the Raspberry PI, because the armel architecture in Debian is not
3515 optimized for that use. So the images created will be a bit slower
3516 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
3517 </description>
3518 </item>
3519
3520 <item>
3521 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
3522 <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>
3523 <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>
3524 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
3525 <description>&lt;p&gt;The last few days I came across a few good causes that should get
3526 wider attention. I recommend signing and donating to each one of
3527 these. :)&lt;/p&gt;
3528
3529 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
3530 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
3531 Women program which is a Google Summer of Code like initiative to get
3532 more women involved in free software. One debian sponsor has offered
3533 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
3534 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
3535 hope you will to. :)&lt;/p&gt;
3536
3537 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
3538 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
3539 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
3540 take place these days, and their need to fund the work. I&#39;ve already
3541 donated. Are you next?&lt;/p&gt;
3542
3543 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
3544 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
3545 statement under the heading
3546 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
3547 Access&lt;/a&gt; for those of us asking for more focus on open access in the
3548 Norwegian government. So far 499 signatures. I hope you will sign it
3549 too.&lt;/p&gt;
3550 </description>
3551 </item>
3552
3553 <item>
3554 <title>Videos about the Freedombox project - for inspiration and learning</title>
3555 <link>http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
3556 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
3557 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
3558 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
3559 project&lt;/a&gt; have been going on for a while, and have presented the
3560 vision, ideas and solution several places. Here is a little
3561 collection of videos of talks and presentation of the project.&lt;/p&gt;
3562
3563 &lt;ul&gt;
3564
3565 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
3566 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
3567
3568 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
3569 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3570
3571 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
3572 Freedom in the Cloud - Software Freedom, Privacy and and Security for
3573 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
3574 (Youtube)&lt;/li&gt;
3575
3576 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
3577 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
3578
3579 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
3580 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
3581
3582 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
3583 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
3584 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
3585
3586 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
3587 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
3588 (Youtube)&lt;/li&gt;
3589
3590 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
3591 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
3592
3593 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
3594 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
3595
3596 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
3597 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
3598 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
3599
3600 &lt;/ul&gt;
3601
3602 &lt;p&gt;A larger list is available from
3603 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
3604 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
3605
3606 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
3607 Jessie is coming along quite well, and soon both Owncloud and using
3608 Tor should be available for testers of the Freedombox solution. :) In
3609 a few weeks I hope everything needed to test it is included in Debian.
3610 The withsqlite package is already in Debian, and the plinth package is
3611 pending in NEW. The third and vital part of that puzzle is the
3612 metapackage/setup framework, which is still pending an upload. Join
3613 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
3614 (#freedombox on irc.debian.org)&lt;/a&gt; and
3615 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
3616 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
3617 </description>
3618 </item>
3619
3620 <item>
3621 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
3622 <link>http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
3623 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
3624 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
3625 <description>&lt;p&gt;I was introduced to the
3626 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
3627 in 2010, when Eben Moglen presented his vision about serving the need
3628 of non-technical people to keep their personal information private and
3629 within the legal protection of their own homes. The idea is to give
3630 people back the power over their network and machines, and return
3631 Internet back to its intended peer-to-peer architecture. Instead of
3632 depending on a central service, the Freedombox will give everyone
3633 control over their own basic infrastructure.&lt;/p&gt;
3634
3635 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
3636 taken priority. But this summers nasty news about the misuse of trust
3637 and privilege exercised by the &quot;western&quot; intelligence gathering
3638 communities increased my eagerness to contribute to a point where I
3639 actually started working on the project a while back.&lt;/p&gt;
3640
3641 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
3642 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
3643 create a simple and cheap Debian based appliance that anyone can hook
3644 up in their home and get access to secure and private services and
3645 communication. The initial deployment platform have been the
3646 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
3647 which is a piece of hardware I do not own. So to be able to test what
3648 the current Freedombox setup look like, I had to come up with a way to install
3649 it on some hardware I do have access to. I have rewritten the
3650 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
3651 image build framework to use .deb packages instead of only copying
3652 setup into the boot images, and thanks to this rewrite I am able to
3653 set up any machine supported by Debian Wheezy as a Freedombox, using
3654 the previously mentioned deb (and a few support debs for packages
3655 missing in Debian).&lt;/p&gt;
3656
3657 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
3658 scripts
3659 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
3660 and a administrative web interface
3661 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
3662 withsqlite), as well as a privacy enhancing proxy based on
3663 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
3664 (freedombox-privoxy). There is also a web/javascript based XMPP
3665 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
3666 trying (unsuccessfully so far) to talk to the XMPP server
3667 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
3668 web interface is pluggable, and the goal is to use it to enable OpenID
3669 services, mesh network connectivity, use of TOR, etc, etc. Not much of
3670 this is really working yet, see
3671 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
3672 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
3673 on github at the moment. The HTTP proxy is operational out of the
3674 box, and the admin web interface can be used to add/remove plinth
3675 users. I&#39;ve not been able to do anything else with it so far, but
3676 know there are several branches spread around github and other places
3677 with lots of half baked features.&lt;/p&gt;
3678
3679 &lt;p&gt;Anyway, if you want to have a look at the current state, the
3680 following recipes should work to give you a test machine to poke
3681 at.&lt;/p&gt;
3682
3683 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
3684
3685 &lt;ol&gt;
3686
3687 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
3688 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
3689 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
3690 to the Debian installer:&lt;p&gt;
3691 &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;
3692
3693 &lt;li&gt;Answer the few language/region/password questions and pick disk to
3694 install on.&lt;/li&gt;
3695
3696 &lt;li&gt;When the installation is finished and the machine have rebooted a
3697 few times, your Freedombox is ready for testing.&lt;/li&gt;
3698
3699 &lt;/ol&gt;
3700
3701 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
3702
3703 &lt;ol&gt;
3704
3705 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
3706 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
3707 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
3708 &lt;pre&gt;
3709 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
3710 &lt;/pre&gt;&lt;/li&gt;
3711 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
3712 &lt;pre&gt;
3713 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
3714 apt-key add -
3715 apt-get update
3716 apt-get install freedombox-setup
3717 /usr/lib/freedombox/setup
3718 &lt;/pre&gt;&lt;/li&gt;
3719 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
3720
3721 &lt;/ol&gt;
3722
3723 &lt;p&gt;You can test it on other architectures too, but because the
3724 freedombox-privoxy package is binary, it will only work as intended on
3725 the architectures where I have had time to build the binary and put it
3726 in my APT repository. But do not let this stop you. It is only a
3727 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
3728
3729 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
3730 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
3731 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
3732 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
3733
3734 &lt;p&gt;Please let me know if this works for you, or if you have any
3735 problems. We gather on the IRC channel
3736 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
3737 irc.debian.org and the
3738 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
3739 mailing list&lt;/a&gt;.&lt;/p&gt;
3740
3741 &lt;p&gt;Once you get your freedombox operational, you can visit
3742 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
3743 welcome screen (dead end - do not be surprised if you are unable to
3744 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
3745 to look at the rest of plinth. The default user is &#39;admin&#39; and the
3746 default password is &#39;secret&#39;.&lt;/p&gt;
3747 </description>
3748 </item>
3749
3750 <item>
3751 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
3752 <link>http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
3753 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
3754 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
3755 <description>&lt;p&gt;Earlier, I reported about
3756 &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
3757 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
3758 told by IBM that the original disk should be thrown away. And as
3759 there no longer was a problem if I bricked the firmware, I decided
3760 today to try to install Intel firmware to replace the Lenovo firmware
3761 currently on the disk.&lt;/p&gt;
3762
3763 &lt;p&gt;I searched the Intel site for firmware, and found
3764 &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;
3765 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
3766 according to the site should contain the latest firmware for SSD
3767 disks. I inserted the broken disk in one of my spare laptops and
3768 booted the ISO from a USB stick. The disk was recognized, but the
3769 program claimed the newest firmware already were installed and refused
3770 to insert any Intel firmware. So no change, and the disk is still
3771 unable to handle write load. :( I guess the only way to get them
3772 working would be if Lenovo releases new firmware. No idea how likely
3773 that is. Anyway, just blogging about this test for completeness. I
3774 got a working Samsung disk, and see no point in spending more time on
3775 the broken disks.&lt;/p&gt;
3776 </description>
3777 </item>
3778
3779 <item>
3780 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
3781 <link>http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
3782 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
3783 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
3784 <description>&lt;p&gt;Today I switched to
3785 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
3786 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
3787 my new Thinkpad X230, which was delivered with an
3788 &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
3789 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
3790 sustained writes. My hardware supplier have been very forthcoming in
3791 trying to find a solution, and after first trying with another
3792 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
3793 disk instead to fix it once and for all. The Samsung disk survived
3794 the installation of Debian with encrypted disks (filling the disk with
3795 random data during installation killed the first two), and I thus
3796 decided to trust it with my data. I have installed it as a Debian Edu
3797 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
3798 server at home using Kerberos and LDAP, and will use it as my work
3799 station from now on.&lt;/p&gt;
3800
3801 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
3802 Debian Wheezy default installation need to be tuned a bit to increase
3803 performance and increase life time of the disk. The Linux kernel and
3804 user space applications do not yet adjust automatically to such
3805 environment. To make it easier for my self, I created a draft Debian
3806 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
3807 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
3808 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
3809 is set up to adjust the setup of the machine by just installing the
3810 package. If there is any non-SSD disk in the machine, the package
3811 will refuse to install, as I did not try to write any logic to sort
3812 file systems in SSD and non-SSD file systems.&lt;/p&gt;
3813
3814 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
3815 set up Debian Wheezy with an SSD. It is adjusted to my use case,
3816 where I set up the machine with one large encrypted partition (in
3817 addition to /boot), put LVM on top of this and set up partitions on
3818 top of this again. See the README file in the package source for the
3819 references I used to pick the settings. At the moment these
3820 parameters are tuned:&lt;/p&gt;
3821
3822 &lt;ul&gt;
3823
3824 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
3825 (adding discard to /etc/crypttab)&lt;/li&gt;
3826
3827 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
3828 this case a cryptsetup partition) by changing issue_discards from
3829 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
3830
3831 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
3832 systems.&lt;/li&gt;
3833
3834 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
3835 /etc/fstab.&lt;/li&gt;
3836
3837 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
3838
3839 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
3840 cron.daily).&lt;/li&gt;
3841
3842 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
3843 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
3844
3845 &lt;/ul&gt;
3846
3847 &lt;p&gt;During installation, I cancelled the part where the installer fill
3848 the disk with random data, as this would kill the SSD performance for
3849 little gain. My goal with the encrypted file system is to ensure
3850 those stealing my laptop end up with a brick and not a working
3851 computer. I have no hope in keeping the really resourceful people
3852 from getting the data on the disk (see
3853 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
3854 Thus I concluded that adding the discard option to crypttab is the
3855 right thing to do.&lt;/p&gt;
3856
3857 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
3858 it for SSD, but others recommended deadline and a benchmark I found
3859 indicated that deadline might be better for interactive use.&lt;/p&gt;
3860
3861 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
3862 and ext4, but read that it would give a performance hit ever time a
3863 file is removed, and thought it best to that that slowdown once a day
3864 instead of during my work.&lt;/p&gt;
3865
3866 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
3867 this is already done by Debian Edu.&lt;/p&gt;
3868
3869 &lt;p&gt;I have not yet started on the user space tuning. I expect
3870 iceweasel need some tuning, and perhaps other applications too, but
3871 have not yet had time to investigate those parts.&lt;/p&gt;
3872
3873 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
3874 there.&lt;/p&gt;
3875
3876 &lt;p&gt;As for the answer to the question in the title of this blog post,
3877 as far as I know, the only solution I know about is to replace the
3878 disk. It might be possible to flash it with Intel firmware instead of
3879 the Lenovo firmware. But I have not tried and did not want to do so
3880 without approval from Lenovo as I wanted to keep the warranty on the
3881 disk until a solution was found and they wanted the broken disks
3882 back.&lt;/p&gt;
3883 </description>
3884 </item>
3885
3886 <item>
3887 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
3888 <link>http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
3889 <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>
3890 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
3891 <description>&lt;p&gt;A few days ago, I wrote about
3892 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
3893 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
3894 was dying during installation because it is unable to cope with
3895 sustained write. My supplier is in contact with
3896 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
3897 replacement disk to try to fix the problem. They decided to send an
3898 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
3899
3900 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
3901 Debian Edu Wheezy with encrypted disk on it. The new disk have the
3902 same firmware version as the original. This time my hope raised
3903 slightly as the installation progressed, as the original disk used to
3904 die after 4-7% of the disk was written to, while this time it kept
3905 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
3906 died again and I was back on square one. I still do not have a new
3907 laptop with a disk I can trust. I can not live with a disk that might
3908 lock up when I download a new
3909 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
3910 other large files. I look forward to hearing from my supplier with
3911 the next proposal from Lenovo.&lt;/p&gt;
3912
3913 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
3914 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
3915 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3916 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
3917 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3918 P/N 45N8295, P0C38732.&lt;/p&gt;
3919
3920 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
3921 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
3922 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
3923 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
3924 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
3925 P/N 45N8295, P0C38732.&lt;/p&gt;
3926
3927 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
3928 SA, date and WNPP values. Mentioning all the details here in case
3929 someone is able to use the information to find a way to identify the
3930 failing disk among working ones (if any such working disk actually
3931 exist).&lt;/p&gt;
3932 </description>
3933 </item>
3934
3935 <item>
3936 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
3937 <link>http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
3938 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
3939 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
3940 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
3941 Debian Edu developer gathering and Debian and Ubuntu bug squashing
3942 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
3943 member assosiation NUUG&lt;/a&gt; and
3944 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
3945 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
3946 Bitraf&lt;/a&gt;.&lt;/p&gt;
3947
3948 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
3949 welcome, and there is no fee to participate. There is on the other
3950 hand limited space, and only room for 30 people. Please put your name
3951 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
3952 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
3953 </description>
3954 </item>
3955
3956 <item>
3957 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
3958 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
3959 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
3960 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
3961 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
3962 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
3963 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
3964 time to spend on it, and it took a while to find a model I believe
3965 will do the job, but two days ago the replacement finally arrived. I
3966 ended up picking a
3967 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
3968 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
3969 a roaming workstation, and it seemed to work flawlessly. But my
3970 second installation with encrypted disk was not as successful. More
3971 on that below.&lt;/p&gt;
3972
3973 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
3974 important requirements (robust and with a good keyboard) are never
3975 listed in the feature list. But I did get good help from the search
3976 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
3977 allowed me to limit the list of interesting laptops based on my other
3978 requirements. A bit surprising that SSD disk are not disks according
3979 to that search interface, so I had to drop specifying the number of
3980 disks from my search parameters. I also asked around among friends to
3981 get their impression on keyboards and robustness.&lt;/p&gt;
3982
3983 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
3984 X41. I am not quite convinced about the keyboard, as it is
3985 significantly wider than my old keyboard, and I have to stretch my
3986 hand a lot more to reach the edges. But the key response is fairly
3987 good and the individual key shape is fairly easy to handle, so I hope
3988 I will get used to it. My old X40 was starting to fail, and I really
3989 needed a new laptop now. :)&lt;/p&gt;
3990
3991 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
3992 visit to the BIOS during boot it disable it.&lt;/p&gt;
3993
3994 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
3995 lock up during load. And this happen when installing Debian Wheezy
3996 with encrypted disk, while the disk is being filled with random data.
3997 I also tested to install Ubuntu Raring, and it happen there too if I
3998 reenable the code to fill the disk with random data (it is disabled by
3999 default in Ubuntu). And the bug with is already known. It was
4000 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
4001 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
4002 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
4003 kernel developers as
4004 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
4005 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
4006 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
4007 Lenovo forums, both for
4008 &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
4009 2012-11-10&lt;/a&gt; and for
4010 &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
4011 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
4012 reports state that the disk lock up during use if many writes are done
4013 on the disk, so it is much no use to work around the installation
4014 problem and end up with a computer that can lock up at any moment.
4015 There is even a
4016 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
4017 available&lt;/a&gt; that will lock up the hard drive after running a few
4018 minutes by writing to a file.&lt;/p&gt;
4019
4020 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
4021 contacting PCHELP Norway (request 01D1FDP) which handle support
4022 requests for Lenovo, his first suggestion was to upgrade the disk
4023 firmware. Unfortunately there is no newer firmware available from
4024 Lenovo, as my disk already have the most recent one (version LF1i). I
4025 hope to hear more from him today and hope the problem can be
4026 fixed. :)&lt;/p&gt;
4027 </description>
4028 </item>
4029
4030 <item>
4031 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
4032 <link>http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
4033 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
4034 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
4035 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
4036 trusty old Thinkpad X41. Unfortunately I did not have much time to
4037 spend on it, but today the replacement finally arrived. I ended up
4038 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
4039 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
4040 Wheezy as a roaming workstation, and it worked flawlessly. As I write
4041 this, it is installing what I hope will be a more final installation,
4042 with a encrypted hard drive to ensure any dope head stealing it end up
4043 with an expencive door stop.&lt;/p&gt;
4044
4045 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
4046 important requirements (robust and with a good keyboard) are never
4047 listed in the feature list. But I did get good help from the search
4048 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
4049 allowed me to limit the list of interesting laptops based on my other
4050 requirements. A bit surprising that SSD disk are not disks, so I had
4051 to drop number of disks from my search parameters.&lt;/p&gt;
4052
4053 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
4054 wider than my old keyboard, and I have to stretch my hand a lot more
4055 to reach the edges. But the key response is fairly good and the
4056 individual key shape is fairly easy to handle, so I hope I will get
4057 used to it. My old X40 was starting to fail, and I really needed a
4058 new laptop now. :)&lt;/p&gt;
4059
4060 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
4061 </description>
4062 </item>
4063
4064 <item>
4065 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
4066 <link>http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
4067 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
4068 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
4069 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
4070 perfectly capable of, and I have to do it manually to get things
4071 working. One such task is to find out what firmware packages are
4072 needed to get the hardware on my computer working. Most often this
4073 affect the wifi card, but some times it even affect the RAID
4074 controller or the ethernet card. Today I pushed version 0.4 of the
4075 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
4076 including a new script isenkram-autoinstall-firmware handling the
4077 process of asking all the loaded kernel modules what firmware files
4078 they want, find debian packages providing these files and install the
4079 debian packages. Here is a test run on my laptop:&lt;/p&gt;
4080
4081 &lt;p&gt;&lt;pre&gt;
4082 # isenkram-autoinstall-firmware
4083 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
4084 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
4085 info: locating packages with the requested firmware files
4086 info: Updating APT sources after adding non-free APT source
4087 info: trying to install firmware-ipw2x00
4088 firmware-ipw2x00
4089 firmware-ipw2x00
4090 Preconfiguring packages ...
4091 Selecting previously deselected package firmware-ipw2x00.
4092 (Reading database ... 259727 files and directories currently installed.)
4093 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
4094 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
4095 #
4096 &lt;/pre&gt;&lt;/p&gt;
4097
4098 &lt;p&gt;When all the requested firmware is present, a simple message is
4099 printed instead:&lt;/p&gt;
4100
4101 &lt;p&gt;&lt;pre&gt;
4102 # isenkram-autoinstall-firmware
4103 info: did not find any firmware files requested by loaded kernel modules. exiting
4104 #
4105 &lt;/pre&gt;&lt;/p&gt;
4106
4107 &lt;p&gt;It could use some polish, but it is already working well and saving
4108 me some time when setting up new machines. :)&lt;/p&gt;
4109
4110 &lt;p&gt;So, how does it work? It look at the set of currently loaded
4111 kernel modules, and look up each one of them using modinfo, to find
4112 the firmware files listed in the module meta-information. Next, it
4113 download the Contents file from a nearby APT mirror, and search for
4114 the firmware files in this file to locate the package with the
4115 requested firmware file. If the package is in the non-free section, a
4116 non-free APT source is added and the package is installed using
4117 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
4118 machine.&lt;/p&gt;
4119
4120 &lt;p&gt;I hope someone find time to implement a more polished version of
4121 this script as part of the hw-detect debian-installer module, to
4122 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
4123 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
4124 firmware during a PXE install when the packages already are available
4125 from the nearby Debian mirror.&lt;/p&gt;
4126 </description>
4127 </item>
4128
4129 <item>
4130 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
4131 <link>http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
4132 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
4133 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
4134 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
4135 the screen just turn black when Linux boot, either during installation
4136 or on first boot from the hard disk. I&#39;ve seen it once in a while the
4137 last few years, but only recently understood the cause. I&#39;ve seen it
4138 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
4139 The reason seem to be in the wiring of some laptops. The system to
4140 control the screen background light is inverted, so when Linux try to
4141 turn the brightness fully on, it end up turning it off instead. I do
4142 not know which Linux drivers are affected, but this post is about the
4143 i915 driver used by the
4144 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
4145 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
4146
4147 &lt;p&gt;The problem can be worked around two ways. Either by adding
4148 i915.invert_brightness=1 as a kernel option, or by adding a file in
4149 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
4150 option when it load the i915 kernel module. On Debian and Ubuntu, it
4151 can be done by running these commands as root:&lt;/p&gt;
4152
4153 &lt;pre&gt;
4154 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
4155 update-initramfs -u -k all
4156 &lt;/pre&gt;
4157
4158 &lt;p&gt;Since March 2012 there is
4159 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
4160 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
4161 hardware have this problem, and get the driver to invert the
4162 brightness setting automatically. To use it, one need to add a row in
4163 &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
4164 intel_quirks array&lt;/a&gt; in the driver source
4165 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
4166 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
4167 number (vendor number 8086 is assumed) and subdevice vendor and device
4168 number.&lt;/p&gt;
4169
4170 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
4171 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
4172
4173 &lt;p&gt;&lt;pre&gt;
4174 00:02.0 VGA compatible controller [0300]: Intel Corporation \
4175 3rd Gen Core processor Graphics Controller [8086:0156] \
4176 (rev 09) (prog-if 00 [VGA controller])
4177 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
4178 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
4179 ParErr- Stepping- SE RR- FastB2B- DisINTx+
4180 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
4181 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
4182 Latency: 0
4183 Interrupt: pin A routed to IRQ 42
4184 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
4185 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
4186 Region 4: I/O ports at 4000 [size=64]
4187 Expansion ROM at &lt;unassigned&gt; [disabled]
4188 Capabilities: &lt;access denied&gt;
4189 Kernel driver in use: i915
4190 &lt;/pre&gt;&lt;/p&gt;
4191
4192 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
4193
4194 &lt;p&gt;&lt;pre&gt;
4195 struct intel_quirk intel_quirks[] = {
4196 ...
4197 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
4198 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
4199 ...
4200 }
4201 &lt;/pre&gt;&lt;/p&gt;
4202
4203 &lt;p&gt;According to the kernel module instructions (as seen using
4204 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
4205 invert_brightness flag should be sent to the
4206 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
4207 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
4208 developers. But my email about the laptop sent 2013-06-03 have not
4209 yet shown up in
4210 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
4211 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
4212 emails from non-subscribers. Because of this, I sent my patch also to
4213 the Debian bug tracking system instead as
4214 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
4215 sure the patch is not lost.&lt;/p&gt;
4216
4217 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
4218 with this problem working properly with Linux. If you use Gnome, your
4219 worries should be over at this point. But if you use KDE, there is
4220 something in KDE ignoring the invert_brightness setting and turning on
4221 the screen during login. I&#39;ve reported it to Debian as
4222 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
4223 have no idea yet how to figure out exactly what subsystem is doing
4224 this. Perhaps you can help? Perhaps you know what the Gnome
4225 developers did to handle this, and this can give a clue to the KDE
4226 developers? Or you know where in KDE the screen brightness is changed
4227 during login? If so, please update the BTS report (or get in touch if
4228 you do not know how to update BTS).&lt;/p&gt;
4229
4230 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
4231 acpi_backlight=vendor, to disable ACPI backlight support completely,
4232 as the ACPI information on the machine is trash and it is better to
4233 leave it to the intel video driver to control the screen
4234 backlight.&lt;/p&gt;
4235 </description>
4236 </item>
4237
4238 <item>
4239 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
4240 <link>http://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
4241 <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>
4242 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
4243 <description>&lt;p&gt;Two days ago, I asked
4244 &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
4245 I could install Linux on a Packard Bell EasyNote LV computer
4246 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
4247 with the obstacles put in the way of Linux users on a laptop with UEFI
4248 and Windows 8.&lt;/p&gt;
4249
4250 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
4251 secure booting or fast boot. I suspect fast boot was the problem,
4252 causing the firmware to boot directly from HD without considering any
4253 key presses and alternative devices, but do not know UEFI settings
4254 enough to tell.&lt;/p&gt;
4255
4256 &lt;p&gt;There is no way to install Linux on the machine in question without
4257 opening the box and disconnecting the hard drive! This is as far as I
4258 can tell, the only way to get access to the firmware setup menu
4259 without accepting the Windows 8 license agreement. I am told (and
4260 found description on how to) that it is possible to configure the
4261 firmware setup once booted into Windows 8. But as I believe the terms
4262 of that agreement are completely unacceptable, accepting the license
4263 was never an alternative. I do not enter agreements I do not intend
4264 to follow.&lt;/p&gt;
4265
4266 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
4267 waste many hours on this, but luckily there was a way to get it to
4268 work. But I would not recommend it to anyone planning to run Linux on
4269 it, and I have become sceptical to Windows 8 certified laptops. Is
4270 this the way Linux will be forced out of the market place, by making
4271 it close to impossible for &quot;normal&quot; users to install Linux without
4272 accepting the Microsoft Windows license terms? Or at least not
4273 without risking to loose the warranty?&lt;/p&gt;
4274
4275 &lt;p&gt;I&#39;ve updated the
4276 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
4277 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
4278 do not have to struggle as much as I did to get Linux into the
4279 machine.&lt;/p&gt;
4280
4281 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
4282 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
4283 </description>
4284 </item>
4285
4286 <item>
4287 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
4288 <link>http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
4289 <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>
4290 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
4291 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
4292 new laptops for my parents and a few others. I bought Packard Bell
4293 Easynote LV to run Kubuntu on and use as their home computer. But I
4294 am completely unable to figure out how to install Linux on it. The
4295 computer is preinstalled with Windows 8, and I suspect it uses UEFI
4296 instead of a BIOS to boot.&lt;/p&gt;
4297
4298 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
4299 to get it to boot the Linux installer from my USB stick. I have yet
4300 to try the DVD install, and still hope it will work. when I turn on
4301 the computer, there is no information on what buttons to press to get
4302 the normal boot menu. I expect to get some boot menu to select PXE or
4303 USB stick booting. When booting, it first ask for the language to
4304 use, then for some regional settings, and finally if I will accept the
4305 Windows 8 terms of use. As these terms are completely unacceptable to
4306 me, I have no other choice but to turn off the computer and try again
4307 to get it to boot the Linux installer.&lt;/p&gt;
4308
4309 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
4310 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
4311 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
4312 installed on this machine, please get in touch or update that wiki
4313 page. If I can&#39;t find a way to install Linux, I will have to return
4314 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
4315
4316 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
4317 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
4318 on new Laptops?&lt;/p&gt;
4319 </description>
4320 </item>
4321
4322 <item>
4323 <title>How to transform a Debian based system to a Debian Edu installation</title>
4324 <link>http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
4325 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
4326 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
4327 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
4328 an operating system based on Debian intended for use in schools. It
4329 contain a turn-key solution for the computer network provided to
4330 pupils in the primary schools. It provide both the central server,
4331 network boot servers and desktop environments with heaps of
4332 educational software. The project was founded almost 12 years ago,
4333 2001-07-02. If you want to support the project, which is in need for
4334 cash to fund developer gatherings and other project related activity,
4335 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
4336 donate some money&lt;/a&gt;.
4337
4338 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
4339 lists and elsewhere, is the question on how to transform a Debian or
4340 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
4341 hard, and last week I wrote a script to replicate the steps done by
4342 the Debian Edu installer.&lt;/p&gt;
4343
4344 &lt;p&gt;The script,
4345 &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;
4346 in the debian-edu-config package, will go through these six steps and
4347 transform an existing Debian Wheezy or Ubuntu (untested) installation
4348 into a Debian Edu Workstation:&lt;/p&gt;
4349
4350 &lt;ol&gt;
4351
4352 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
4353 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
4354 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
4355 our configuration.&lt;/li&gt;
4356 &lt;li&gt;Preseed debconf database with profile setup in
4357 /etc/debian-edu/config, and run tasksel to install packages
4358 according to the profile specified in the config above,
4359 overriding some of the Debian automation machinery.&lt;/li&gt;
4360 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
4361 that could not be done using preseeding.&lt;/li&gt;
4362 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
4363
4364 &lt;/ol&gt;
4365
4366 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
4367 replicated like this. Disk partitioning and LVM setup, for example.
4368 So this script just assume there is enough disk space to install all
4369 the needed packages.&lt;/p&gt;
4370
4371 &lt;p&gt;The script was created to help a Debian Edu student working on
4372 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
4373 Debian Edu client, and using it he can take the existing
4374 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
4375 transform it into a fully functioning Debian Edu Workstation (or
4376 Roaming Workstation, or whatever :).&lt;/p&gt;
4377
4378 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
4379 If a LXDE based Roaming workstation is wanted instead, modify the
4380 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
4381
4382 &lt;p&gt;&lt;pre&gt;
4383 PROFILE=&quot;Roaming-Workstation&quot;
4384 DESKTOP=&quot;lxde&quot;
4385 &lt;/pre&gt;&lt;/p&gt;
4386
4387 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
4388 the cloud, by starting with a virtual Debian installation at some
4389 virtual hosting service and setting up all the services on first
4390 boot.&lt;/p&gt;
4391 </description>
4392 </item>
4393
4394 <item>
4395 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
4396 <link>http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
4397 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
4398 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
4399 <description>&lt;P&gt;In January,
4400 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
4401 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
4402 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
4403 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
4404 marvellous construction system from Denmark. We also created
4405 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
4406 a place to take notes and write down our plans and hopes. And several
4407 people showed up to help. I was very happy to see the effect of my
4408 call. Since the small start, we have a debtags tag
4409 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
4410 tag for LEGO related packages, and now count 10 packages related to
4411 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
4412
4413 &lt;p&gt;&lt;table&gt;
4414 &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;
4415 &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;
4416 &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;
4417 &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;
4418 &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;
4419 &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;
4420 &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;
4421 &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;
4422 &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;
4423 &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;
4424 &lt;/table&gt;&lt;/p&gt;
4425
4426 &lt;p&gt;Some of these are available in Wheezy, and all but one are
4427 currently available in Jessie/testing. leocad is so far only
4428 available in experimental.&lt;/p&gt;
4429
4430 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
4431 adding the rest of the great free software tools available on Linux
4432 for LEGO designers.&lt;/p&gt;
4433 </description>
4434 </item>
4435
4436 <item>
4437 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
4438 <link>http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
4439 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
4440 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
4441 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
4442 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
4443 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
4444 Debian release, and I expect to move my machines at home over to it fairly
4445 soon.&lt;/p&gt;
4446
4447 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
4448 in particular make me very happy to see included. The
4449 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
4450 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
4451 included for the first time. Alongside similar programs like
4452 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
4453 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
4454 it allow for visual programming where syntax errors can not happen,
4455 and a friendly programming environment for learning to control the
4456 computer. Scratch will also be included in the next release of Debian
4457 Edu.&lt;/a&gt;
4458
4459 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
4460 Edu/Skolelinux release too. The
4461 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
4462 alpha release&lt;/a&gt; went out last week, and the next should soon
4463 follow.&lt;p&gt;
4464 </description>
4465 </item>
4466
4467 <item>
4468 <title>Isenkram 0.2 finally in the Debian archive</title>
4469 <link>http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
4470 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
4471 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
4472 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
4473 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
4474 for many months. I uploaded it to the Debian experimental suite
4475 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
4476
4477 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
4478 install to work with a pluggable hardware device. The suggestion pop
4479 up when the device is plugged in. For example if a Lego Mindstorm NXT
4480 is inserted, it will suggest to install the program needed to program
4481 the NXT controller. Give it a go, and report bugs and suggestions to
4482 BTS. :)&lt;/p&gt;
4483 </description>
4484 </item>
4485
4486 <item>
4487 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
4488 <link>http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
4489 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
4490 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
4491 <description>&lt;p&gt;My
4492 &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
4493 bitcoin related blog post&lt;/a&gt; mentioned that the new
4494 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
4495 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
4496 2013-01-19, and have been available in unstable since then. It was
4497 automatically copied to Ubuntu, and is available in their Raring
4498 version too.&lt;/p&gt;
4499
4500 &lt;p&gt;But there is a strange problem with the build that block this new
4501 version from being available on the i386 and kfreebsd-i386
4502 architectures. For some strange reason, the autobuilders in Debian
4503 for these architectures fail to run the test suite on these
4504 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
4505 We are so far unable to reproduce it when building it manually, and
4506 no-one have been able to propose a fix. If you got an idea what is
4507 failing, please let us know via the BTS.&lt;/p&gt;
4508
4509 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
4510 I often run low on disk space, is the fact that the client will exit
4511 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
4512 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
4513 it. :)&lt;/p&gt;
4514
4515 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
4516 activities, please send Bitcoin donations to my address
4517 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4518 </description>
4519 </item>
4520
4521 <item>
4522 <title>Welcome to the world, Isenkram!</title>
4523 <link>http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
4524 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
4525 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
4526 <description>&lt;p&gt;Yesterday, I
4527 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
4528 for testers&lt;/a&gt; for my prototype for making Debian better at handling
4529 pluggable hardware devices, which I
4530 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
4531 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
4532 up, and caused me to really want to to open up the development to more
4533 people. But before I did this, I want to come up with a sensible name
4534 for this project. Today I finally decided on a new name, and I have
4535 renamed the project from hw-support-handler to this new name. In the
4536 process, I moved the source to git and made it available as a
4537 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
4538 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
4539 To fetch and build the latest version of the source, use&lt;/p&gt;
4540
4541 &lt;pre&gt;
4542 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
4543 cd isenkram &amp;&amp; git-buildpackage -us -uc
4544 &lt;/pre&gt;
4545
4546 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
4547 want to hack on the source or improve the package, please go ahead.
4548 But please talk to me first on IRC or via email before you do major
4549 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
4550
4551 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
4552 stuff, typically meaning tools, nails, screws, etc. Typical hardware
4553 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
4554 the German word eisenkram, for those that are familiar with that
4555 word.&lt;/p&gt;
4556
4557 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
4558 instructions, to avoid confusing people with an error from the signing
4559 process.&lt;/p&gt;
4560
4561 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
4562 clone argument to avoid the need for authentication.&lt;/p&gt;
4563 </description>
4564 </item>
4565
4566 <item>
4567 <title>First prototype ready making hardware easier to use in Debian</title>
4568 <link>http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
4569 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
4570 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
4571 <description>&lt;p&gt;Early this month I set out to try to
4572 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
4573 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
4574 prototype is working, and it is ready for a larger audience. To test
4575 it, fetch the
4576 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
4577 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
4578 package. You might have to log out and in again activate the
4579 autostart script.&lt;/p&gt;
4580
4581 &lt;p&gt;The design is simple:&lt;/p&gt;
4582
4583 &lt;ul&gt;
4584
4585 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
4586 hw-support-handlerd to start when the user log in.&lt;/li&gt;
4587
4588 &lt;li&gt;This program listen for kernel events about new hardware (directly
4589 from the kernel like udev does), not using HAL dbus events as I
4590 initially did.&lt;/li&gt;
4591
4592 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
4593 the APT database, a database
4594 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
4595 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
4596
4597 &lt;li&gt;If a package is mapped to the hardware in question, the package
4598 isn&#39;t installed yet and this is the first time the hardware was
4599 plugged in, show a desktop notification suggesting to install the
4600 package or packages.&lt;/li&gt;
4601
4602 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
4603 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
4604
4605 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
4606 package while showing progress information in a window.&lt;/li&gt;
4607
4608 &lt;/ul&gt;
4609
4610 &lt;p&gt;I still need to come up with a better name for the system. Here
4611 are some screen shots showing the prototype in action. First the
4612 notification, then the password request, and finally the request to
4613 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
4614
4615 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
4616 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
4617 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
4618 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
4619 &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;
4620
4621 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
4622 is already useful. The database of hardware to package mappings also
4623 need more work. It is currently compatible with the Ubuntu way of
4624 storing such information in the package control file, but could be
4625 changed to use other formats instead or in addition to the current
4626 method. I&#39;ve dropped the use of discover for this mapping, as the
4627 modalias approach is more flexible and easier to use on Linux as long
4628 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
4629
4630 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
4631 here is the command required to check out and build the source: Use
4632 &#39;&lt;tt&gt;svn checkout
4633 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
4634 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
4635 devscripts package.&lt;/p&gt;
4636
4637 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
4638 renamed to Isenkram and the source moved from the Debian Edu
4639 subversion repository to a Debian collab-maint git repository. See
4640 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
4641 instructions&lt;/a&gt; for details.&lt;/p&gt;
4642 </description>
4643 </item>
4644
4645 <item>
4646 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
4647 <link>http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
4648 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
4649 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
4650 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
4651 suddenly in bed. With a quiet whimper, it went completely quiet and
4652 black. The power button was no longer able to turn it on. It was a
4653 IBM Thinkpad X41, and the best laptop I ever had. Better than both
4654 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
4655 Compaq I had before that. Now I need to find a replacement. To keep
4656 going during Christmas, I moved the one year old SSD disk to my old
4657 X40 where it fitted (only one I had left that could use it), but it is
4658 not a durable solution.
4659
4660 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
4661 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
4662
4663 &lt;ul&gt;
4664
4665 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
4666 than A4).&lt;/li&gt;
4667 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
4668 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
4669 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
4670 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
4671 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
4672 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
4673 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
4674 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
4675 size).&lt;/li&gt;
4676 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
4677 X.org packages.&lt;/li&gt;
4678 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
4679 the time).
4680
4681 &lt;/ul&gt;
4682
4683 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
4684 list. The reason is simply that the specifications on laptops the
4685 last 10-15 years have been sufficient for my needs, and I have to look
4686 at other features to choose my laptop. But are there still made as
4687 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
4688 robust, and Thinkpads seem to be heading in the wrong direction since
4689 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
4690 still be useful.&lt;/p&gt;
4691
4692 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
4693 external keyboard? I&#39;ll have to check the
4694 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
4695 well-supported laptops, or perhaps just buy one preinstalled from one
4696 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
4697 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
4698 </description>
4699 </item>
4700
4701 <item>
4702 <title>How to find a browser plugin supporting a given MIME type</title>
4703 <link>http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
4704 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
4705 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
4706 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
4707 install to get support for a given MIME type. Thanks to
4708 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
4709 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
4710 Unfortunately, not very many packages provide the needed meta
4711 information, Anyway, here is a small script to look up all browser
4712 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
4713
4714 &lt;pre&gt;
4715 #!/usr/bin/python
4716 import sys
4717 import apt
4718 def pkgs_handling_mimetype(mimetype):
4719 cache = apt.Cache()
4720 cache.open(None)
4721 thepkgs = []
4722 for pkg in cache:
4723 version = pkg.candidate
4724 if version is None:
4725 version = pkg.installed
4726 if version is None:
4727 continue
4728 record = version.record
4729 if not record.has_key(&#39;Npp-MimeType&#39;):
4730 continue
4731 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
4732 for t in mime_types:
4733 t = t.rstrip().strip()
4734 if t == mimetype:
4735 thepkgs.append(pkg.name)
4736 return thepkgs
4737 mimetype = &quot;audio/ogg&quot;
4738 if 1 &lt; len(sys.argv):
4739 mimetype = sys.argv[1]
4740 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
4741 for pkg in pkgs_handling_mimetype(mimetype):
4742 print &quot; %s&quot; %pkg
4743 &lt;/pre&gt;
4744
4745 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
4746
4747 &lt;pre&gt;
4748 % ./apt-find-browserplug-for-mimetype
4749 Browser plugin packages supporting audio/ogg:
4750 gecko-mediaplayer
4751 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
4752 Browser plugin packages supporting application/x-shockwave-flash:
4753 browser-plugin-gnash
4754 %
4755 &lt;/pre&gt;
4756
4757 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
4758 itself to query for plugins and propose to install the needed
4759 packages. It would be great if Debian supported such feature too. Is
4760 anyone working on adding it?&lt;/p&gt;
4761
4762 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
4763 request for icweasel support for this feature is
4764 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
4765 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
4766 of manpower and wish for a different design is the reason thus feature
4767 is not yet in iceweasel from Debian.&lt;/p&gt;
4768 </description>
4769 </item>
4770
4771 <item>
4772 <title>What is the most supported MIME type in Debian?</title>
4773 <link>http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
4774 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
4775 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
4776 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
4777 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
4778 proposal to make it possible for a Desktop application to propose to
4779 the user some package to install to gain support for a given MIME
4780 type, font, library etc. that is currently missing. With such
4781 mechanism in place, it would be possible for the desktop to
4782 automatically propose and install leocad if some LDraw file is
4783 downloaded by the browser.&lt;/p&gt;
4784
4785 &lt;p&gt;To get some idea about the current content of the archive, I decided
4786 to write a simple program to extract all .desktop files from the
4787 Debian archive and look up the claimed MIME support there. The result
4788 can be found on the
4789 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
4790 site&lt;/a&gt;. Using the collected information, it become possible to
4791 answer the question in the title. Here are the 20 most supported MIME
4792 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
4793 The complete list is available from the link above.&lt;/p&gt;
4794
4795 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
4796
4797 &lt;pre&gt;
4798 count MIME type
4799 ----- -----------------------
4800 32 text/plain
4801 30 audio/mpeg
4802 29 image/png
4803 28 image/jpeg
4804 27 application/ogg
4805 26 audio/x-mp3
4806 25 image/tiff
4807 25 image/gif
4808 22 image/bmp
4809 22 audio/x-wav
4810 20 audio/x-flac
4811 19 audio/x-mpegurl
4812 18 video/x-ms-asf
4813 18 audio/x-musepack
4814 18 audio/x-mpeg
4815 18 application/x-ogg
4816 17 video/mpeg
4817 17 audio/x-scpls
4818 17 audio/ogg
4819 16 video/x-ms-wmv
4820 &lt;/pre&gt;
4821
4822 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
4823
4824 &lt;pre&gt;
4825 count MIME type
4826 ----- -----------------------
4827 33 text/plain
4828 32 image/png
4829 32 image/jpeg
4830 29 audio/mpeg
4831 27 image/gif
4832 26 image/tiff
4833 26 application/ogg
4834 25 audio/x-mp3
4835 22 image/bmp
4836 21 audio/x-wav
4837 19 audio/x-mpegurl
4838 19 audio/x-mpeg
4839 18 video/mpeg
4840 18 audio/x-scpls
4841 18 audio/x-flac
4842 18 application/x-ogg
4843 17 video/x-ms-asf
4844 17 text/html
4845 17 audio/x-musepack
4846 16 image/x-xbitmap
4847 &lt;/pre&gt;
4848
4849 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
4850
4851 &lt;pre&gt;
4852 count MIME type
4853 ----- -----------------------
4854 31 text/plain
4855 31 image/png
4856 31 image/jpeg
4857 29 audio/mpeg
4858 28 application/ogg
4859 27 image/gif
4860 26 image/tiff
4861 26 audio/x-mp3
4862 23 audio/x-wav
4863 22 image/bmp
4864 21 audio/x-flac
4865 20 audio/x-mpegurl
4866 19 audio/x-mpeg
4867 18 video/x-ms-asf
4868 18 video/mpeg
4869 18 audio/x-scpls
4870 18 application/x-ogg
4871 17 audio/x-musepack
4872 16 video/x-ms-wmv
4873 16 video/x-msvideo
4874 &lt;/pre&gt;
4875
4876 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
4877 information mentioned in DEP-11. I have not yet had time to look at
4878 it, but hope the PackageKit people in Debian are on top of these
4879 issues.&lt;/p&gt;
4880
4881 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
4882 discovering a typo in my script.&lt;/p&gt;
4883 </description>
4884 </item>
4885
4886 <item>
4887 <title>Using modalias info to find packages handling my hardware</title>
4888 <link>http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
4889 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
4890 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
4891 <description>&lt;p&gt;Yesterday, I wrote about the
4892 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
4893 values provided by the Linux kernel&lt;/a&gt; following my hope for
4894 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
4895 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
4896 modalias values attached to package names can be used to map packages
4897 to hardware. This allow the system to look up and suggest relevant
4898 packages when I plug in some new hardware into my machine, and replace
4899 discover and discover-data as the database used to map hardware to
4900 packages.&lt;/p&gt;
4901
4902 &lt;p&gt;I create a modaliases file with entries like the following,
4903 containing package name, kernel module name (if relevant, otherwise
4904 the package name) and globs matching the relevant hardware
4905 modalias.&lt;/p&gt;
4906
4907 &lt;p&gt;&lt;blockquote&gt;
4908 Package: package-name
4909 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
4910 &lt;/blockquote&gt;&lt;/p&gt;
4911
4912 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
4913 for a given modalias value using this file.&lt;/p&gt;
4914
4915 &lt;p&gt;An entry like this would suggest the video and picture application
4916 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
4917
4918 &lt;p&gt;&lt;blockquote&gt;
4919 Package: cheese
4920 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
4921 &lt;/blockquote&gt;&lt;/p&gt;
4922
4923 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
4924 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
4925
4926 &lt;p&gt;&lt;blockquote&gt;
4927 Package: pcmciautils
4928 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
4929 &lt;/blockquote&gt;&lt;/p&gt;
4930
4931 &lt;p&gt;An entry like this would suggest the package colorhug-client when
4932 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
4933
4934 &lt;p&gt;&lt;blockquote&gt;
4935 Package: colorhug-client
4936 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
4937 &lt;/blockquote&gt;&lt;/p&gt;
4938
4939 &lt;p&gt;I believe the format is compatible with the format of the Packages
4940 file in the Debian archive. Ubuntu already uses their Packages file
4941 to store their mappings from packages to hardware.&lt;/p&gt;
4942
4943 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
4944 announce the hardware it support in a way my prototype understand.
4945 This allow those publishing packages in an APT source outside the
4946 Debian archive as well as those backporting packages to make sure the
4947 hardware mapping are included in the package meta information. I&#39;ve
4948 tested such header in the pymissile package, and its modalias mapping
4949 is working as it should with my prototype. It even made it to Ubuntu
4950 Raring.&lt;/p&gt;
4951
4952 &lt;p&gt;To test if it was possible to look up supported hardware using only
4953 the shell tools available in the Debian installer, I wrote a shell
4954 implementation of the lookup code. The idea is to create files for
4955 each modalias and let the shell do the matching. Please check out and
4956 try the
4957 &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;
4958 shell script. It run without any extra dependencies and fetch the
4959 hardware mappings from the Debian archive and the subversion
4960 repository where I currently work on my prototype.&lt;/p&gt;
4961
4962 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
4963 install yubikey-personalization:&lt;/p&gt;
4964
4965 &lt;p&gt;&lt;blockquote&gt;
4966 % ./hw-support-lookup
4967 &lt;br&gt;yubikey-personalization
4968 &lt;br&gt;%
4969 &lt;/blockquote&gt;&lt;/p&gt;
4970
4971 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
4972 propose to install the pcmciautils package:&lt;/p&gt;
4973
4974 &lt;p&gt;&lt;blockquote&gt;
4975 % ./hw-support-lookup
4976 &lt;br&gt;pcmciautils
4977 &lt;br&gt;%
4978 &lt;/blockquote&gt;&lt;/p&gt;
4979
4980 &lt;p&gt;If you know of any hardware-package mapping that should be added to
4981 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
4982 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
4983
4984 &lt;p&gt;It could be possible to generate several of the mappings between
4985 packages and hardware. One source would be to look at packages with
4986 kernel modules, ie packages with *.ko files in /lib/modules/, and
4987 extract their modalias information. Another would be to look at
4988 packages with udev rules, ie packages with files in
4989 /lib/udev/rules.d/, and extract their vendor/model information to
4990 generate a modalias matching rule. I have not tested any of these to
4991 see if it work.&lt;/p&gt;
4992
4993 &lt;p&gt;If you want to help implementing a system to let us propose what
4994 packages to install when new hardware is plugged into a Debian
4995 machine, please send me an email or talk to me on
4996 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
4997 </description>
4998 </item>
4999
5000 <item>
5001 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
5002 <link>http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
5003 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
5004 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
5005 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
5006 information, to find the packages that support a given piece of
5007 hardware, I refreshed my memory regarding modalias values, and decided
5008 to document the details. Here are my findings so far, also available
5009 in
5010 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
5011 Debian Edu subversion repository&lt;/a&gt;:
5012
5013 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
5014
5015 &lt;p&gt;This document try to explain what the different types of modalias
5016 values stands for. It is in part based on information from
5017 &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;,
5018 &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;,
5019 &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
5020 &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;.
5021
5022 &lt;p&gt;The modalias entries for a given Linux machine can be found using
5023 this shell script:&lt;/p&gt;
5024
5025 &lt;pre&gt;
5026 find /sys -name modalias -print0 | xargs -0 cat | sort -u
5027 &lt;/pre&gt;
5028
5029 &lt;p&gt;The supported modalias globs for a given kernel module can be found
5030 using modinfo:&lt;/p&gt;
5031
5032 &lt;pre&gt;
5033 % /sbin/modinfo psmouse | grep alias:
5034 alias: serio:ty05pr*id*ex*
5035 alias: serio:ty01pr*id*ex*
5036 %
5037 &lt;/pre&gt;
5038
5039 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
5040
5041 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
5042 Bridge memory controller:&lt;/p&gt;
5043
5044 &lt;p&gt;&lt;blockquote&gt;
5045 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
5046 &lt;/blockquote&gt;&lt;/p&gt;
5047
5048 &lt;p&gt;This represent these values:&lt;/p&gt;
5049
5050 &lt;pre&gt;
5051 v 00008086 (vendor)
5052 d 00002770 (device)
5053 sv 00001028 (subvendor)
5054 sd 000001AD (subdevice)
5055 bc 06 (bus class)
5056 sc 00 (bus subclass)
5057 i 00 (interface)
5058 &lt;/pre&gt;
5059
5060 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
5061 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
5062 0600. The 0600 class is a host bridge. Other useful bus values are
5063 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
5064
5065 &lt;p&gt;Not sure how to figure out the interface value, nor what it
5066 means.&lt;/p&gt;
5067
5068 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
5069
5070 &lt;p&gt;Some typical USB entries can look like this. This is an internal
5071 USB hub in a laptop:&lt;/p&gt;
5072
5073 &lt;p&gt;&lt;blockquote&gt;
5074 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
5075 &lt;/blockquote&gt;&lt;/p&gt;
5076
5077 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
5078
5079 &lt;pre&gt;
5080 v 1D6B (device vendor)
5081 p 0001 (device product)
5082 d 0206 (bcddevice)
5083 dc 09 (device class)
5084 dsc 00 (device subclass)
5085 dp 00 (device protocol)
5086 ic 09 (interface class)
5087 isc 00 (interface subclass)
5088 ip 00 (interface protocol)
5089 &lt;/pre&gt;
5090
5091 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
5092 class is in the interface class section. For a simple USB web camera,
5093 these alias entries show up:&lt;/p&gt;
5094
5095 &lt;p&gt;&lt;blockquote&gt;
5096 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
5097 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
5098 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
5099 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
5100 &lt;/blockquote&gt;&lt;/p&gt;
5101
5102 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
5103 camera), 0101 is audio control device and 0102 is audio streaming (aka
5104 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
5105
5106 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
5107
5108 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
5109 receiver in a Thinkpad X40:&lt;/p&gt;
5110
5111 &lt;p&gt;&lt;blockquote&gt;
5112 acpi:IBM0071:PNP0511:
5113 &lt;/blockquote&gt;&lt;/p&gt;
5114
5115 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
5116
5117 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
5118
5119 &lt;p&gt;The DMI table contain lots of information about the computer case
5120 and model. This is an entry for a IBM Thinkpad X40, fetched from
5121 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
5122
5123 &lt;p&gt;&lt;blockquote&gt;
5124 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
5125 &lt;/blockquote&gt;&lt;/p&gt;
5126
5127 &lt;p&gt;The values present are&lt;/p&gt;
5128
5129 &lt;pre&gt;
5130 bvn IBM (BIOS vendor)
5131 bvr 1UETB6WW(1.66) (BIOS version)
5132 bd 06/15/2005 (BIOS date)
5133 svn IBM (system vendor)
5134 pn 2371H4G (product name)
5135 pvr ThinkPadX40 (product version)
5136 rvn IBM (board vendor)
5137 rn 2371H4G (board name)
5138 rvr NotAvailable (board version)
5139 cvn IBM (chassis vendor)
5140 ct 10 (chassis type)
5141 cvr NotAvailable (chassis version)
5142 &lt;/pre&gt;
5143
5144 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
5145 found in the dmidecode source:&lt;/p&gt;
5146
5147 &lt;pre&gt;
5148 3 Desktop
5149 4 Low Profile Desktop
5150 5 Pizza Box
5151 6 Mini Tower
5152 7 Tower
5153 8 Portable
5154 9 Laptop
5155 10 Notebook
5156 11 Hand Held
5157 12 Docking Station
5158 13 All In One
5159 14 Sub Notebook
5160 15 Space-saving
5161 16 Lunch Box
5162 17 Main Server Chassis
5163 18 Expansion Chassis
5164 19 Sub Chassis
5165 20 Bus Expansion Chassis
5166 21 Peripheral Chassis
5167 22 RAID Chassis
5168 23 Rack Mount Chassis
5169 24 Sealed-case PC
5170 25 Multi-system
5171 26 CompactPCI
5172 27 AdvancedTCA
5173 28 Blade
5174 29 Blade Enclosing
5175 &lt;/pre&gt;
5176
5177 &lt;p&gt;The chassis type values are not always accurately set in the DMI
5178 table. For example my home server is a tower, but the DMI modalias
5179 claim it is a desktop.&lt;/p&gt;
5180
5181 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
5182
5183 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
5184 test machine:&lt;/p&gt;
5185
5186 &lt;p&gt;&lt;blockquote&gt;
5187 serio:ty01pr00id00ex00
5188 &lt;/blockquote&gt;&lt;/p&gt;
5189
5190 &lt;p&gt;The values present are&lt;/p&gt;
5191
5192 &lt;pre&gt;
5193 ty 01 (type)
5194 pr 00 (prototype)
5195 id 00 (id)
5196 ex 00 (extra)
5197 &lt;/pre&gt;
5198
5199 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
5200 the valid values are.&lt;/p&gt;
5201
5202 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
5203
5204 &lt;p&gt;There are heaps of other modalias subtypes according to
5205 file2alias.c. There is the rest of the list from that source: amba,
5206 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
5207 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
5208 vmbus, x86cpu and zorro. I did not spend time documenting all of
5209 these, as they do not seem relevant for my intended use with mapping
5210 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
5211
5212 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
5213
5214 &lt;p&gt;To check which kernel modules provide support for a given modalias,
5215 one can use the following shell script:&lt;/p&gt;
5216
5217 &lt;pre&gt;
5218 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
5219 echo &quot;$id&quot; ; \
5220 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
5221 done
5222 &lt;/pre&gt;
5223
5224 &lt;p&gt;The output can look like this (only the first few entries as the
5225 list is very long on my test machine):&lt;/p&gt;
5226
5227 &lt;pre&gt;
5228 acpi:ACPI0003:
5229 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
5230 acpi:device:
5231 FATAL: Module acpi:device: not found.
5232 acpi:IBM0068:
5233 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
5234 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
5235 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
5236 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
5237 acpi:IBM0071:PNP0511:
5238 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
5239 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
5240 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
5241 [...]
5242 &lt;/pre&gt;
5243
5244 &lt;p&gt;If you want to help implementing a system to let us propose what
5245 packages to install when new hardware is plugged into a Debian
5246 machine, please send me an email or talk to me on
5247 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
5248
5249 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
5250 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
5251 in /sys/ with space in them.&lt;/p&gt;
5252 </description>
5253 </item>
5254
5255 <item>
5256 <title>Moved the pymissile Debian packaging to collab-maint</title>
5257 <link>http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
5258 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
5259 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
5260 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
5261 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
5262 Launcher and updated the Debian package
5263 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
5264 sure udev will fix the device permissions when it is plugged in. I
5265 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
5266 hopefully make the package be proposed by jockey in Ubuntu when a user
5267 plug in his rocket launcher. In the process I moved the source to a
5268 git repository under collab-maint, to make it easier for any DD to
5269 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
5270 is not very active, but the software still work for me even after five
5271 years of relative silence. The new git repository is not listed in
5272 the uploaded package yet, because I want to test the other changes a
5273 bit more before I upload the new version. If you want to check out
5274 the new version with a .desktop file included, visit the
5275 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
5276 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
5277 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
5278 </description>
5279 </item>
5280
5281 <item>
5282 <title>Lets make hardware dongles easier to use in Debian</title>
5283 <link>http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
5284 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
5285 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
5286 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
5287 general, is that there is a great package management system with the
5288 ability to automatically install software packages by downloading them
5289 from the distribution mirrors, but no way to get it to automatically
5290 install the packages I need to use the hardware I plug into my
5291 machine. Even if the package to use it is easily available from the
5292 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
5293 suggest to automatically install the python-nxt, nbc and t2n packages
5294 I need to talk to it. When I plug in a Yubikey, it could propose the
5295 yubikey-personalization package. The information required to do this
5296 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
5297
5298 &lt;p&gt;Some years ago, I proposed to
5299 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
5300 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
5301 simple:
5302
5303 &lt;ul&gt;
5304
5305 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
5306 starting when a user log in.&lt;/li&gt;
5307
5308 &lt;li&gt;Set this program up to listen for kernel events emitted when new
5309 hardware is inserted into the computer.&lt;/li&gt;
5310
5311 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
5312 database mapping to packages, and take note of any non-installed
5313 packages.&lt;/li&gt;
5314
5315 &lt;li&gt;Show a message to the user proposing to install the discovered
5316 package, and make it easy to install it.&lt;/li&gt;
5317
5318 &lt;/ul&gt;
5319
5320 &lt;p&gt;I am not sure what the best way to implement this is, but my
5321 initial idea was to use dbus events to discover new hardware, the
5322 discover database to find packages and
5323 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
5324 packages.&lt;/p&gt;
5325
5326 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
5327 draft package is now checked into
5328 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
5329 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
5330 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
5331 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
5332 the relevant packages in Debian, and uploaded a new version
5333 2.2013.01.09 to unstable. I also discovered that the current
5334 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
5335 package in Debian no longer discovered any USB devices, because
5336 /proc/bus/usb/devices is no longer present. I ported it to use
5337 libusb as a fall back option to get it working. The fixed package
5338 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
5339 because of the freeze).&lt;/p&gt;
5340
5341 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
5342 desktop notification to show up (only once, the first time it is
5343 inserted):&lt;/p&gt;
5344
5345 &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;
5346
5347 &lt;p&gt;For this prototype to be really useful, some way to automatically
5348 install the proposed packages by pressing the &quot;Please install
5349 program(s)&quot; button should to be implemented.&lt;/p&gt;
5350
5351 &lt;p&gt;If this idea seem useful to you, and you want to help make it
5352 happen, please help me update the discover-data database with mappings
5353 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
5354 list the package you would like to have installed when a given
5355 hardware device is inserted into your computer, and report bugs using
5356 reportbug if it isn&#39;t. Or, if you know of a better way to provide
5357 such mapping, please let me know.&lt;/p&gt;
5358
5359 &lt;p&gt;This prototype need more work, and there are several questions that
5360 should be considered before it is ready for production use. Is dbus
5361 the correct way to detect new hardware? At the moment I look for HAL
5362 dbus events on the system bus, because that is the events I could see
5363 on my Debian Squeeze KDE desktop. Are there better events to use?
5364 How should the user be notified? Is the desktop notification
5365 mechanism the best option, or should the background daemon raise a
5366 popup instead? How should packages be installed? When should they
5367 not be installed?&lt;/p&gt;
5368
5369 &lt;p&gt;If you want to help getting such feature implemented in Debian,
5370 please send me an email. :)&lt;/p&gt;
5371 </description>
5372 </item>
5373
5374 <item>
5375 <title>New IRC channel for LEGO designers using Debian</title>
5376 <link>http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
5377 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
5378 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
5379 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
5380 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
5381 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
5382 discovered I had to build all the tools myself because none were
5383 already in Debian Squeeze. If Debian support for LEGO is something
5384 you care about, please join me on the IRC channel
5385 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
5386 irc.debian.org). There is a lot that could be done to improve the
5387 Debian support for LEGO designers. For example both CAD software
5388 and Mindstorm compilers are missing. :)&lt;/p&gt;
5389
5390 &lt;p&gt;Update 2012-01-03: A
5391 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
5392 including links to Lego related packages is now available.&lt;/p&gt;
5393 </description>
5394 </item>
5395
5396 <item>
5397 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
5398 <link>http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
5399 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
5400 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
5401 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
5402 year! I hope next year will prove to be a good year.&lt;/p&gt;
5403
5404 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
5405 decentralised &quot;currency&quot; that allow people to transfer bitcoins
5406 between each other with minimal overhead, is a very interesting
5407 experiment. And as I wrote a few days ago, the bitcoin situation in
5408 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
5409 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
5410 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
5411 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
5412 for one of the ftpmasters to approve the new bitcoin-qt package
5413 name.&lt;/p&gt;
5414
5415 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
5416 team in Debian, you can easily test the package in Debian Squeeze
5417 using the following steps to get a set of working packages:&lt;/p&gt;
5418
5419 &lt;blockquote&gt;&lt;pre&gt;
5420 git clone git://git.debian.org/git/collab-maint/bitcoin
5421 cd bitcoin
5422 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
5423 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
5424 &lt;/pre&gt;&lt;/blockquote&gt;
5425
5426 &lt;p&gt;You might have to install some build dependencies as well. The
5427 list of commands should give you two packages, bitcoind and
5428 bitcoin-qt, ready for use in a Squeeze environment. Note that the
5429 client will download the complete set of bitcoin &quot;blocks&quot;, which need
5430 around 5.6 GiB of data on my machine at the moment. Make sure your
5431 ~/.bitcoin/ directory have lots of spare room if you want to download
5432 all the blocks. The client will warn if the disk is getting full, so
5433 there is not really a problem if you got too little room, but you will
5434 not be able to get all the features out of the client.&lt;/p&gt;
5435
5436 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
5437 activities, please send Bitcoin donations to my address
5438 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5439 </description>
5440 </item>
5441
5442 <item>
5443 <title>A word on bitcoin support in Debian</title>
5444 <link>http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
5445 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
5446 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
5447 <description>&lt;p&gt;It has been a while since I wrote about
5448 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
5449 peer-to-peer based crypto-currency, and the reason is simply that I
5450 have been busy elsewhere. But two days ago, I started looking at the
5451 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
5452 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
5453 is now maintained by a
5454 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
5455 people&lt;/a&gt;, and the grunt work had already been done by this team. We
5456 owe a huge thank you to all these team members. :)
5457 But I was sad to discover that the bitcoin client is missing in
5458 Wheezy. It is only available in Sid (and an outdated client from
5459 backports). The client had several RC bugs registered in BTS blocking
5460 it from entering testing. To try to help the team and improve the
5461 situation, I spent some time providing patches and triaging the bug
5462 reports. I also had a look at the bitcoin package available from Matt
5463 Corallo in a
5464 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
5465 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
5466 Debian package.&lt;/p&gt;
5467
5468 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
5469 IRC, I pushed several patches into the collab-maint git repository to
5470 improve the package. It now contains fixes for the RC issues (not from
5471 me, but fixed by Scott Howard), build rules for a Qt GUI client
5472 package, konqueror support for the bitcoin: URI and bash completion
5473 setup. As I work on Debian Squeeze, I also created
5474 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
5475 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
5476 it and try to integrate it into the git repository before uploading a
5477 new version to unstable.
5478
5479 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
5480 centralized control currently exercised in the monetary system. I
5481 find it completely unacceptable that the USA government is collecting
5482 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
5483 that the major credit card companies can block legal money
5484 transactions to Wikileaks. But for bitcoin to succeed, more people
5485 need to use bitcoins, and more people need to accept bitcoins when
5486 they sell products and services. Improving the bitcoin support in
5487 Debian is a small step in the right direction, but not enough.
5488 Unfortunately the user experience when browsing the web and wanting to
5489 pay with bitcoin is still not very good. The bitcoin: URI is a step
5490 in the right direction, but need to work in most or every browser in
5491 use. Also the bitcoin-qt client is too heavy to fire up to do a
5492 quick transaction. I believe there are other clients available, but
5493 have not tested them.&lt;/p&gt;
5494
5495 &lt;p&gt;My
5496 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
5497 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
5498 I received 20.15 BTC so far on the address I provided in my blog two
5499 years ago, as can be
5500 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
5501 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
5502 donation. The blockexplorer service demonstrates quite well that
5503 bitcoin is not quite anonymous and untracked. :) I wonder if the
5504 number of users have gone up since then. If you use bitcoin and want
5505 to show your support of my activity, please send Bitcoin donations to
5506 the same address as last time,
5507 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&amp;label=PetterReinholdtsenBlog&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5508 </description>
5509 </item>
5510
5511 <item>
5512 <title>Git repository for song book for Computer Scientists</title>
5513 <link>http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
5514 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
5515 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
5516 <description>&lt;p&gt;As I
5517 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
5518 this summer&lt;/a&gt;, I have created a Computer Science song book a few
5519 years ago, and today I finally found time to create a public
5520 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
5521 repository for the project&lt;/a&gt;.&lt;/p&gt;
5522
5523 &lt;p&gt;If you want to help out, please clone the source and submit patches
5524 to the HTML version. To generate the PDF and PostScript version,
5525 please use prince XML, or let me know about a useful free software
5526 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
5527
5528 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
5529 PostScript formats at
5530 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
5531 Science Songbook&lt;/a&gt;.&lt;/p&gt;
5532 </description>
5533 </item>
5534
5535 <item>
5536 <title>Gratulerer med 19-årsdagen, Debian!</title>
5537 <link>http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
5538 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
5539 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
5540 <description>&lt;p&gt;I dag fyller
5541 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
5542 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
5543 si gratulerer med dagen, Debian!&lt;/p&gt;
5544 </description>
5545 </item>
5546
5547 <item>
5548 <title>Song book for Computer Scientists</title>
5549 <link>http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
5550 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
5551 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
5552 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
5553 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
5554 collecting computer related songs for use at parties. The original
5555 version was written in LaTeX, but a few years ago I got help from
5556 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
5557 while keeping the ability to create a nice book in PDF format. I have
5558 not had time to maintain the book for a while now, and guess I should
5559 put it up on some public version control repository where others can
5560 help me extend and update the book. If anyone is volunteering to help
5561 me with this, send me an email. Also let me know if there are songs
5562 missing in my book.&lt;/p&gt;
5563
5564 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
5565 me today that I really should let all my readers share the joys of
5566 singing out load about programming, computers and computer networks.
5567 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
5568 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
5569 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
5570 Computer Science Songbook&lt;/a&gt;.
5571 </description>
5572 </item>
5573
5574 <item>
5575 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
5576 <link>http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
5577 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
5578 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
5579 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
5580 around 1000 at the moment. To be able to get help from the vendors
5581 when something go wrong, we want to keep the firmware on the servers
5582 up to date. If the firmware isn&#39;t the latest and greatest, the
5583 vendors typically refuse to start debugging any problems until the
5584 firmware is upgraded. So before every reboot, we want to upgrade the
5585 firmware, and we would really like everyone handling servers at the
5586 university to do this themselves when they plan to reboot a machine.
5587 For that to happen we at the unix server admin group need to provide
5588 the tools to do so.&lt;/p&gt;
5589
5590 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
5591 fetch and install the latest firmware for the servers we got. Most of
5592 our hardware are from Dell and HP, so I have focused on these servers
5593 so far. This blog post is about the Dell part.&lt;/P&gt;
5594
5595 &lt;p&gt;On the Dell FTP site I was lucky enough to find
5596 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
5597 with firmware information for all 11th generation servers, listing
5598 which firmware should be used on a given model and where on the FTP
5599 site I can find it. Using a simple perl XML parser I can then
5600 download the shell scripts Dell provides to do firmware upgrades from
5601 within Linux and reboot when all the firmware is primed and ready to
5602 be activated on the first reboot.&lt;/p&gt;
5603
5604 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
5605 Are there anyone working on similar tools for firmware upgrading all
5606 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
5607
5608 &lt;p&gt;&lt;pre&gt;
5609 #!/usr/bin/perl
5610 use strict;
5611 use warnings;
5612 use File::Temp qw(tempdir);
5613 BEGIN {
5614 # Install needed RHEL packages if missing
5615 my %rhelmodules = (
5616 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
5617 );
5618 for my $module (keys %rhelmodules) {
5619 eval &quot;use $module;&quot;;
5620 if ($@) {
5621 my $pkg = $rhelmodules{$module};
5622 system(&quot;yum install -y $pkg&quot;);
5623 eval &quot;use $module;&quot;;
5624 }
5625 }
5626 }
5627 my $errorsto = &#39;pere@hungry.com&#39;;
5628
5629 upgrade_dell();
5630
5631 exit 0;
5632
5633 sub run_firmware_script {
5634 my ($opts, $script) = @_;
5635 unless ($script) {
5636 print STDERR &quot;fail: missing script name\n&quot;;
5637 exit 1
5638 }
5639 print STDERR &quot;Running $script\n\n&quot;;
5640
5641 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
5642 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
5643 } else {
5644 print STDERR &quot;fail: firmware script returned error\n&quot;;
5645 }
5646 }
5647
5648 sub run_firmware_scripts {
5649 my ($opts, @dirs) = @_;
5650 # Run firmware packages
5651 for my $dir (@dirs) {
5652 print STDERR &quot;info: Running scripts in $dir\n&quot;;
5653 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
5654 while (my $s = readdir $dh) {
5655 next if $s =~ m/^\.\.?/;
5656 run_firmware_script($opts, &quot;$dir/$s&quot;);
5657 }
5658 closedir $dh;
5659 }
5660 }
5661
5662 sub download {
5663 my $url = shift;
5664 print STDERR &quot;info: Downloading $url\n&quot;;
5665 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
5666 }
5667
5668 sub upgrade_dell {
5669 my @dirs;
5670 my $product = `dmidecode -s system-product-name`;
5671 chomp $product;
5672
5673 if ($product =~ m/PowerEdge/) {
5674
5675 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
5676 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
5677
5678 my $tmpdir = tempdir(
5679 CLEANUP =&gt; 1
5680 );
5681 chdir($tmpdir);
5682 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
5683 system(&#39;gunzip Catalog.xml.gz&#39;);
5684 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
5685 # -q is quiet, disabling interactivity and reducing console output
5686 my $fwopts = &quot;-q&quot;;
5687 if (@paths) {
5688 for my $url (@paths) {
5689 fetch_dell_fw($url);
5690 }
5691 run_firmware_scripts($fwopts, $tmpdir);
5692 } else {
5693 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5694 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5695 }
5696 chdir(&#39;/&#39;);
5697 } else {
5698 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
5699 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
5700 }
5701 }
5702
5703 sub fetch_dell_fw {
5704 my $path = shift;
5705 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
5706 download($url);
5707 }
5708
5709 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
5710 # firmware packages to download from Dell. Only work for Linux
5711 # machines and 11th generation Dell servers.
5712 sub fetch_dell_fw_list {
5713 my $filename = shift;
5714
5715 my $product = `dmidecode -s system-product-name`;
5716 chomp $product;
5717 my ($mybrand, $mymodel) = split(/\s+/, $product);
5718
5719 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
5720
5721 my $xml = XMLin($filename);
5722 my @paths;
5723 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
5724 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
5725 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
5726 my $oscode;
5727 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
5728 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
5729 } else {
5730 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
5731 }
5732 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
5733 {
5734 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
5735 }
5736 }
5737 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
5738 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
5739
5740 # Drop application packages, only firmware and BIOS
5741 next if &#39;APAC&#39; eq $componenttype;
5742
5743 my $cpath = $component-&gt;{path};
5744 for my $path (@paths) {
5745 if ($cpath =~ m%/$path$%) {
5746 push(@paths, $cpath);
5747 }
5748 }
5749 }
5750 return @paths;
5751 }
5752 &lt;/pre&gt;
5753
5754 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
5755 it could work on other platforms with some tweaking. Anyone know a
5756 index like Catalog.xml is available from HP for HP servers? At the
5757 moment I maintain a similar list manually and it is quickly getting
5758 outdated.&lt;/p&gt;
5759 </description>
5760 </item>
5761
5762 <item>
5763 <title>How is booting into runlevel 1 different from single user boots?</title>
5764 <link>http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
5765 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
5766 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
5767 <description>&lt;p&gt;Wouter Verhelst have some
5768 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
5769 comments and opinions&lt;/a&gt; on my blog post on
5770 &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
5771 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
5772 &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
5773 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
5774 small piece of his comment now, and though it best to address the
5775 misunderstanding he bring forward:&lt;/p&gt;
5776
5777 &lt;p&gt;&lt;blockquote&gt;
5778 Currently, a system admin has four options: [...] boot to a
5779 single-user system (by adding &#39;single&#39; to the kernel command line;
5780 this runs rcS and rc1 scripts)
5781 &lt;/blockquote&gt;&lt;/p&gt;
5782
5783 &lt;p&gt;This make me believe Wouter believe booting into single user mode
5784 and booting into runlevel 1 is the same. I am not surprised he
5785 believe this, because it would make sense and is a quite sensible
5786 thing to believe. But because the boot in Debian is slightly broken,
5787 runlevel 1 do not work properly and it isn&#39;t the same as single user
5788 mode. I&#39;ll try to explain what is actually happing, but it is a bit
5789 hard to explain.&lt;/p&gt;
5790
5791 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
5792 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
5793 executed in single user mode is sulogin. Single user mode is a boot
5794 state &quot;between&quot; the runlevels, and when booting into single user mode,
5795 only the scripts in /etc/rcS.d/ are executed before the init process
5796 enters the single user state. When switching to runlevel 1, the state
5797 is in fact not ending in runlevel 1, but it passes through runlevel 1
5798 and end up in the single user mode (see /etc/rc1.d/S03single, which
5799 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
5800 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
5801 mode enabled by /etc/rcS.d/ (which is more like the initial boot
5802 mode).&lt;/p&gt;
5803
5804 &lt;p&gt;This summary might make it clearer. When booting for the first
5805 time into single user mode, the following commands are executed:
5806 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
5807 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
5808 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
5809 trying to continue after visiting single user mode. Not all services
5810 are started again as they should, causing the machine to end up in an
5811 unpredicatble state. This is why Debian admins recommend rebooting
5812 after visiting single user mode.&lt;/p&gt;
5813
5814 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
5815 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
5816 to runlevel 1, the services started from /etc/rcS.d/ are not properly
5817 stopped when passing through the scripts in /etc/rc1.d/, and not
5818 started again when switching away from runlevel 1 to the runlevels
5819 2-5. I believe the problem is best fixed by moving all the scripts
5820 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
5821 functioning single user mode during boot.&lt;/p&gt;
5822
5823 &lt;p&gt;I have spent several years investigating the Debian boot system,
5824 and discovered this problem a few years ago. I suspect it originates
5825 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
5826 </description>
5827 </item>
5828
5829 <item>
5830 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
5831 <link>http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
5832 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
5833 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
5834 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
5835 are started from /etc/rcS.d/. In fact, there is a bite more of them
5836 than make sense, and this causes a few problems. What kind of
5837 problems, you might ask. There are at least two problems. The first
5838 is that it is not possible to recover a machine after switching to
5839 runlevel 1. One need to actually reboot to get the machine back to
5840 the expected state. The other is that single user boot will sometimes
5841 run into problems because some of the subsystems are activated before
5842 the root login is presented, causing problems when trying to recover a
5843 machine from a problem in that subsystem. A minor additional point is
5844 that moving more scripts out of rcS.d/ and into the other rc#.d/
5845 directories will increase the amount of scripts that can run in
5846 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
5847
5848 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
5849 scripts that _have_ to execute before the root login prompt is
5850 presented during a single user boot should go there. Everything else
5851 should go into the numeric runlevels. This means things like
5852 lm-sensors, fuse and x11-common should not run from rcS.d, but from
5853 the numeric runlevels. Today in Debian, there are around 115 init.d
5854 scripts that are started from rcS.d/, and most of them should be moved
5855 out. Do your package have one of them? Please help us make single
5856 user and runlevel 1 better by moving it.&lt;/p&gt;
5857
5858 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
5859 etc. should still be started from rcS.d/, but there is for example no
5860 need to have the network enabled before the single user login prompt
5861 is presented.&lt;/p&gt;
5862
5863 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
5864 Debian systems working while scripts migrate and during upgrades, the
5865 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
5866 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
5867 and the next ones can only be moved when their dependencies have been
5868 moved first. This migration must be done sequentially while we ensure
5869 that the package system upgrade packages in the right order to keep
5870 the system state correct. This will require some coordination when it
5871 comes to network related packages, but most of the packages with
5872 scripts that should migrate do not have anything in rcS.d/ depending
5873 on them. Some packages have already been updated, like the sudo
5874 package, while others are still left to do. I wish I had time to work
5875 on this myself, but real live constrains make it unlikely that I will
5876 find time to push this forward.&lt;/p&gt;
5877 </description>
5878 </item>
5879
5880 <item>
5881 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
5882 <link>http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
5883 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
5884 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
5885 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
5886 mentioned the issues I believe should be improved in Debian for its
5887 desktop to be useful for more people. The use case for this is my
5888 parents, which are currently running Kubuntu which solve the
5889 issues.&lt;/p&gt;
5890
5891 &lt;p&gt;I suspect these four missing features are not very hard to
5892 implement. After all, they are present in Ubuntu, so if we wanted to
5893 do this in Debian we would have a source.&lt;/p&gt;
5894
5895 &lt;ol&gt;
5896
5897 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
5898 are new packages available for upgrades, a icon in the KDE status bar
5899 indicate this, and clicking on it will activate the simple upgrade
5900 tool to handle it. I have no problem guiding both of my parents
5901 through the process over the phone. If a kernel reboot is required,
5902 this too is indicated by the status bars and the upgrade tool. Last
5903 time I checked, nothing with the same features was working in KDE in
5904 Debian.&lt;/li&gt;
5905
5906 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
5907 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
5908 currently have a handler for, it will ask the user if the system
5909 should search for a package that would add support for this MIME type,
5910 and if the user say yes, the APT sources will be searched for packages
5911 advertising the MIME type in their control file (visible in the
5912 Packages file in the APT archive). If one or more packages are found,
5913 it is a simple click of the mouse to add support for the missing mime
5914 type. If the package require the user to accept some non-free
5915 license, this is explained to the user. The entire process make it
5916 more clear to the user why something do not work in the browser, and
5917 make the chances higher for the user to blame the web page authors and
5918 not the browser for any missing features.&lt;/li&gt;
5919
5920 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
5921 handlers.&lt;/strong&gt; When the media players encounter a format or codec
5922 it is not supporting, a dialog pop up asking the user if the system
5923 should search for a package that would add support for it. This
5924 happen with things like MP3, Windows Media or H.264. The selection
5925 and installation procedure is very similar to the Firefox browser
5926 plugin handling. This is as far as I know implemented using a
5927 gstreamer hook. The end result is that the user easily get access to
5928 the codecs that are present from the APT archives available, while
5929 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
5930
5931 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
5932 displaying a text/plain file in my Debian browser, it will propose to
5933 start emacs to show it. If I remember correctly, when doing the same
5934 in Kunbutu it show the file as a text file in the browser. At least I
5935 know Opera will show text files within the browser. I much prefer the
5936 latter behaviour.&lt;/li&gt;
5937
5938 &lt;/ol&gt;
5939
5940 &lt;p&gt;There are other nice features as well, like the simplified suite
5941 upgrader, but given that I am the one mostly doing the dist-upgrade,
5942 it do not matter much.&lt;/p&gt;
5943
5944 &lt;p&gt;I really hope we could get these features in place for the next
5945 Debian release. It would require the coordinated effort of several
5946 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
5947 </description>
5948 </item>
5949
5950 <item>
5951 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
5952 <link>http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
5953 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
5954 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
5955 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
5956 site is build on Debian/Squeeze, and this platform was chosen because
5957 I am most familiar with Debian (being a Debian Developer for around 10
5958 years) because it is the latest stable Debian release which should get
5959 security support for a few years.&lt;/p&gt;
5960
5961 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
5962 that are missing in Debian at the moment. It would be great if these
5963 modules were added to the Debian archive, allowing anyone to set up
5964 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
5965 in their own country using only Debian packages. The list of modules
5966 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
5967 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
5968 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
5969 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
5970 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
5971 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
5972 easier in the future.&lt;/p&gt;
5973
5974 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
5975 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
5976 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
5977 with the responsibility of tracking security problems, which I really
5978 do not have time for.&lt;/p&gt;
5979 </description>
5980 </item>
5981
5982 <item>
5983 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
5984 <link>http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
5985 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
5986 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
5987 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
5988 posts have been in Norwegian the last few weeks, so here is a short
5989 update in English.&lt;/p&gt;
5990
5991 &lt;p&gt;The kids still keep me too busy to get much free software work
5992 done, but I did manage to organise a project to get a Norwegian port
5993 of the British service
5994 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
5995 and it has been running for a month now. The entire project has been
5996 organised by me and two others. Around Christmas we gathered sponsors
5997 to fund the development work. In January I drafted a contract with
5998 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
5999 and in February the development took place. Most of it involved
6000 converting the source to use GPS coordinates instead of British
6001 easting/northing, and the resulting code should be a lot easier to get
6002 running in any country by now. The Norwegian
6003 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
6004 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
6005 source and the source for administrative borders in Norway, and
6006 support for this had to be added/fixed.&lt;/p&gt;
6007
6008 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
6009 polishing the system before we announced it March 7th. The system is
6010 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
6011 problem reports in a few weeks. Soon we hope to announce the Android
6012 and iPhone versions making it even easier to report problems with the
6013 public infrastructure.&lt;/p&gt;
6014
6015 &lt;p&gt;Perhaps something to consider for those of you in countries without
6016 such service?&lt;/p&gt;
6017 </description>
6018 </item>
6019
6020 <item>
6021 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
6022 <link>http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
6023 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
6024 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
6025 <description>&lt;p&gt;The last few days I have looked at ways to track open security
6026 issues here at my work with the University of Oslo. My idea is that
6027 it should be possible to use the information about security issues
6028 available on the Internet, and check our locally
6029 maintained/distributed software against this information. It should
6030 allow us to verify that no known security issues are forgotten. The
6031 CVE database listing vulnerabilities seem like a great central point,
6032 and by using the package lists from Debian mapped to CVEs provided by
6033 the testing security team, I believed it should be possible to figure
6034 out which security holes were present in our free software
6035 collection.&lt;/p&gt;
6036
6037 &lt;p&gt;After reading up on the topic, it became obvious that the first
6038 building block is to be able to name software packages in a unique and
6039 consistent way across data sources. I considered several ways to do
6040 this, for example coming up with my own naming scheme like using URLs
6041 to project home pages or URLs to the Freshmeat entries, or using some
6042 existing naming scheme. And it seem like I am not the first one to
6043 come across this problem, as MITRE already proposed and implemented a
6044 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
6045 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
6046 software, hardware and other platform components. The CPE ids are
6047 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
6048 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
6049 issues for any CPE name. With this in place, all I need to do is to
6050 locate the CPE id for the software packages we use at the university.
6051 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
6052 NVD entry if a CVE for the package exist).&lt;/p&gt;
6053
6054 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
6055 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
6056 check out, one could look up
6057 &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
6058 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
6059 The most recent one is
6060 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
6061 and at the bottom of the NVD page for this vulnerability the complete
6062 list of affected versions is provided.&lt;/p&gt;
6063
6064 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
6065 for offline processing of issues. Using this dump, I&#39;ve written a
6066 small script taking a list of CPEs as input and list all CVEs
6067 affecting the packages represented by these CPEs. One give it CPEs
6068 with version numbers as specified above and get a list of open
6069 security issues out.&lt;/p&gt;
6070
6071 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
6072 information need to be high. For that to happen, I believe as many as
6073 possible need to use and contribute to the NVD database. I notice
6074 RHEL is providing
6075 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
6076 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
6077 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
6078
6079 &lt;p&gt;To get an idea about the quality for free software, I spent some
6080 time making it possible to compare the CVE database from Debian with
6081 the CVE database in NVD. The result look fairly good, but there are
6082 some inconsistencies in NVD (same software package having several
6083 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
6084 Debian believe are affected by a CVE). Hope to find time to improve
6085 the quality of NVD, but that require being able to get in touch with
6086 someone maintaining it. So far my three emails with questions and
6087 corrections have not seen any reply, but I hope contact can be
6088 established soon.&lt;/p&gt;
6089
6090 &lt;p&gt;An interesting application for CPEs is cross platform package
6091 mapping. It would be useful to know which packages in for example
6092 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
6093 this would be trivial if all linux distributions provided CPE entries
6094 for their packages.&lt;/p&gt;
6095 </description>
6096 </item>
6097
6098 <item>
6099 <title>Which module is loaded for a given PCI and USB device?</title>
6100 <link>http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
6101 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
6102 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
6103 <description>&lt;p&gt;In the
6104 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
6105 package in Debian, there is a script to report useful information
6106 about the running hardware for use when people report missing
6107 information. One part of this script that I find very useful when
6108 debugging hardware problems, is the part mapping loaded kernel module
6109 to the PCI device it claims. It allow me to quickly see if the kernel
6110 module I expect is driving the hardware I am struggling with. To see
6111 the output, make sure discover-data is installed and run
6112 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
6113 one of my machines like this:&lt;/p&gt;
6114
6115 &lt;pre&gt;
6116 loaded modules:
6117 10de:03eb i2c_nforce2
6118 10de:03f1 ohci_hcd
6119 10de:03f2 ehci_hcd
6120 10de:03f0 snd_hda_intel
6121 10de:03ec pata_amd
6122 10de:03f6 sata_nv
6123 1022:1103 k8temp
6124 109e:036e bttv
6125 109e:0878 snd_bt87x
6126 11ab:4364 sky2
6127 &lt;/pre&gt;
6128
6129 &lt;p&gt;The code in question look like this, slightly modified for
6130 readability and to drop the output to file descriptor 3:&lt;/p&gt;
6131
6132 &lt;pre&gt;
6133 if [ -d /sys/bus/pci/devices/ ] ; then
6134 echo loaded pci modules:
6135 (
6136 cd /sys/bus/pci/devices/
6137 for address in * ; do
6138 if [ -d &quot;$address/driver/module&quot; ] ; then
6139 module=`cd $address/driver/module ; pwd -P | xargs basename`
6140 if grep -q &quot;^$module &quot; /proc/modules ; then
6141 address=$(echo $address |sed s/0000://)
6142 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
6143 echo &quot;$id $module&quot;
6144 fi
6145 fi
6146 done
6147 )
6148 echo
6149 fi
6150 &lt;/pre&gt;
6151
6152 &lt;p&gt;Similar code could be used to extract USB device module
6153 mappings:&lt;/p&gt;
6154
6155 &lt;pre&gt;
6156 if [ -d /sys/bus/usb/devices/ ] ; then
6157 echo loaded usb modules:
6158 (
6159 cd /sys/bus/usb/devices/
6160 for address in * ; do
6161 if [ -d &quot;$address/driver/module&quot; ] ; then
6162 module=`cd $address/driver/module ; pwd -P | xargs basename`
6163 if grep -q &quot;^$module &quot; /proc/modules ; then
6164 address=$(echo $address |sed s/0000://)
6165 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
6166 if [ &quot;$id&quot; ] ; then
6167 echo &quot;$id $module&quot;
6168 fi
6169 fi
6170 fi
6171 done
6172 )
6173 echo
6174 fi
6175 &lt;/pre&gt;
6176
6177 &lt;p&gt;This might perhaps be something to include in other tools as
6178 well.&lt;/p&gt;
6179 </description>
6180 </item>
6181
6182 <item>
6183 <title>How to test if a laptop is working with Linux</title>
6184 <link>http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
6185 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
6186 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
6187 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
6188 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
6189 batch of computers will work with Linux. Every year for the last few
6190 years the university have organised shared bid of a few thousand
6191 computers, and this year HP won the bid. Two different desktops and
6192 five different laptops are on the list this year. We in the UNIX
6193 group want to know which one of these computers work well with RHEL
6194 and Ubuntu, the two Linux distributions we currently handle at the
6195 university.&lt;/p&gt;
6196
6197 &lt;p&gt;My test method is simple, and I share it here to get feedback and
6198 perhaps inspire others to test hardware as well. To test, I PXE
6199 install the OS version of choice, and log in as my normal user and run
6200 a few applications and plug in selected pieces of hardware. When
6201 something fail, I make a note about this in the test matrix and move
6202 on. If I have some spare time I try to report the bug to the OS
6203 vendor, but as I only have the machines for a short time, I rarely
6204 have the time to do this for all the problems I find.&lt;/p&gt;
6205
6206 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
6207 I perform on a new model.&lt;/p&gt;
6208
6209 &lt;ul&gt;
6210
6211 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
6212 and Ubuntu Maverik at the moment. If I feel like it, I also test with
6213 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
6214
6215 &lt;li&gt;Is X.org working? If the graphical login screen show up after
6216 installation, X.org is working.&lt;/li&gt;
6217
6218 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
6219 package mesa-utils on Ubuntu) and writing down the frames per second
6220 reported by the program.&lt;/li&gt;
6221
6222 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
6223 logging in, and if I can hear this the test is successful. If there
6224 are several audio exits on the machine, I try them all and check if
6225 the Gnome/KDE audio mixer can control where to send the sound. I
6226 normally test this by playing
6227 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
6228 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
6229
6230 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
6231 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
6232
6233 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
6234 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
6235
6236 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
6237 picture from the v4l device show up.&lt;/li&gt;
6238
6239 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
6240 any bluetooth devices are discovered. In my office, I normally see a
6241 few.&lt;/li&gt;
6242
6243 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
6244 memory modules lying around, and stick them in and see if Gnome/KDE
6245 notice this.&lt;/li&gt;
6246
6247 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
6248 special button work, and if the laptop continue to work after
6249 resume.&lt;/li&gt;
6250
6251 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
6252 adjusting background light, switching on/off external video output,
6253 switching on/off wifi, bluetooth, etc? The set of buttons differ from
6254 laptop to laptop, so I just write down which are working and which are
6255 not.&lt;/li&gt;
6256
6257 &lt;li&gt;Some laptops have smart card readers, finger print readers,
6258 acceleration sensors etc. I rarely test these, as I do not know how
6259 to quickly test if they are working or not, so I only document their
6260 existence.&lt;/li&gt;
6261
6262 &lt;/ul&gt;
6263
6264 &lt;p&gt;By now I suspect you are really curious what the test results are
6265 for the HP machines I am testing. I&#39;m not done yet, so I will report
6266 the test results later. For now I can report that HP 8100 Elite work
6267 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
6268 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
6269 can see, I have most machines left to test. One interesting
6270 observation is that Ubuntu Lucid has almost twice the frame rate than
6271 RHEL6 with glxgears. No idea why.&lt;/p&gt;
6272 </description>
6273 </item>
6274
6275 <item>
6276 <title>Some thoughts on BitCoins</title>
6277 <link>http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
6278 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
6279 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
6280 <description>&lt;p&gt;As I continue to explore
6281 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
6282 what properties the system have, and how it will be affected by laws
6283 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
6284
6285 &lt;p&gt;One interesting thing to note is that since the transactions are
6286 verified using a peer to peer network, all details about a transaction
6287 is known to everyone. This means that if a BitCoin address has been
6288 published like I did with mine in my initial post about BitCoin, it is
6289 possible for everyone to see how many BitCoins have been transfered to
6290 that address. There is even a web service to look at the details for
6291 all transactions. There I can see that my address
6292 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
6293 have received 16.06 Bitcoin, the
6294 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
6295 address of Simon Phipps have received 181.97 BitCoin and the address
6296 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
6297 of EFF have received 2447.38 BitCoins so far. Thank you to each and
6298 every one of you that donated bitcoins to support my activity. The
6299 fact that anyone can see how much money was transfered to a given
6300 address make it more obvious why the BitCoin community recommend to
6301 generate and hand out a new address for each transaction. I&#39;m told
6302 there is no way to track which addresses belong to a given person or
6303 organisation without the person or organisation revealing it
6304 themselves, as Simon, EFF and I have done.&lt;/p&gt;
6305
6306 &lt;p&gt;In Norway, and in most other countries, there are laws and
6307 regulations limiting how much money one can transfer across the border
6308 without declaring it. There are money laundering, tax and accounting
6309 laws and regulations I would expect to apply to the use of BitCoin.
6310 If the Skolelinux foundation
6311 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
6312 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
6313 normal bank transfers like EFF is doing, how should this be accounted?
6314 Given that it is impossible to know if money can cross the border or
6315 not, should everything or nothing be declared? What exchange rate
6316 should be used when calculating taxes? Would receivers have to pay
6317 income tax if the foundation were to pay Skolelinux contributors in
6318 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
6319
6320 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
6321 accepted by a lot of users. It must be possible to get easy access to
6322 the currency (as a wage or using currency exchanges), and it must be
6323 easy to spend it. At the moment BitCoin seem fairly easy to get
6324 access to, but there are very few places to spend it. I am not really
6325 a regular user of any of the vendor types currently accepting BitCoin,
6326 so I wonder when my kind of shop would start accepting BitCoins. I
6327 would like to buy electronics, travels and subway tickets, not herbs
6328 and books. :) The currency is young, and this will improve over time
6329 if it become popular, but I suspect regular banks will start to lobby
6330 to get BitCoin declared illegal if it become popular. I&#39;m sure they
6331 will claim it is helping fund terrorism and money laundering (which
6332 probably would be true, as is any currency in existence), but I
6333 believe the problems should be solved elsewhere and not by blaming
6334 currencies.&lt;/p&gt;
6335
6336 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
6337 CPU intensive process that depend on a bit of luck as well (as one is
6338 competing against all the other miners currently spending CPU cycles
6339 to see which one get the next lump of cash). The &quot;winner&quot; get 50
6340 BitCoin when this happen. Yesterday I came across the obvious way to
6341 join forces to increase ones changes of getting at least some coins,
6342 by coordinating the work on mining BitCoins across several machines
6343 and people, and sharing the result if one is lucky and get the 50
6344 BitCoins. Check out
6345 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
6346 if this sounds interesting. I have not had time to try to set up a
6347 machine to participate there yet, but have seen that running on ones
6348 own for a few days have not yield any BitCoins througth mining
6349 yet.&lt;/p&gt;
6350
6351 &lt;p&gt;Update 2010-12-15: Found an &lt;a
6352 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
6353 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
6354 it was interesting to read. The arguments presented seem to be
6355 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
6356 </description>
6357 </item>
6358
6359 <item>
6360 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
6361 <link>http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
6362 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
6363 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
6364 <description>&lt;p&gt;With this weeks lawless
6365 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
6366 attacks&lt;/a&gt; on Wikileak and
6367 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
6368 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
6369 not be trusted to handle money transactions.
6370 A blog post from
6371 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
6372 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
6373 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
6374 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
6375 some help from my friend to get it all running, and he even handed me
6376 some bitcoins to get started. I even donated a few bitcoins to Simon
6377 for helping me remember BitCoin.&lt;/p&gt;
6378
6379 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
6380 crypto-currency, decentralised and handled using peer-to-peer
6381 networks. It allows anonymous transactions and prohibits central
6382 control over the transactions, making it impossible for governments
6383 and companies alike to block donations and other transactions. The
6384 source is free software, and while the key dependency wxWidgets 2.9
6385 for the graphical user interface is missing in Debian, the command
6386 line client builds just fine. Hopefully Jonas
6387 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
6388 Debian&lt;/a&gt; soon.&lt;/p&gt;
6389
6390 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
6391 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
6392 bitcoins&lt;/a&gt; when selling services and goods, and there are even
6393 currency &quot;stock&quot; markets where the exchange rate is decided. There
6394 are not many users so far, but the concept seems promising. If you
6395 want to get started and lack a friend with any bitcoins to spare,
6396 you can even get
6397 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
6398 bitcoin at the time of writing). Use
6399 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
6400 on the current exchange rates.&lt;/p&gt;
6401
6402 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
6403 machines. If you want to support my activity, please send Bitcoin
6404 donations to the address
6405 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
6406 </description>
6407 </item>
6408
6409 <item>
6410 <title>Why isn&#39;t Debian Edu using VLC?</title>
6411 <link>http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
6412 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
6413 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
6414 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
6415 presented, and the winner among the multimedia player were VLC.
6416 Personally, I like VLC, and it is my player of choice when I first try
6417 to play a video file or stream. Only if VLC fail will I drag out
6418 gmplayer to see if it can do better. The reason is mostly the failure
6419 model and trust. When VLC fail, it normally pop up a error message
6420 reporting the problem. When mplayer fail, it normally segfault or
6421 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
6422
6423 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
6424 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
6425 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
6426 plugin to play web videos seamlessly, and the VLC browser plugin is
6427 not very good. For example, it lack in-line control buttons, so there
6428 is no way for the user to pause the video. Also, when I
6429 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
6430 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
6431 failed on several video pages where mplayer based plugins worked. If
6432 the browser plugin for VLC was as good as the gecko-mediaplayer
6433 package (which uses mplayer), we would switch.&lt;/P&gt;
6434
6435 &lt;p&gt;While VLC is a good player, its user interface is slightly
6436 annoying. The most annoying feature is its inconsistent use of
6437 keyboard shortcuts. When the player is in full screen mode, its
6438 shortcuts are different from when it is playing the video in a window.
6439 For example, space only work as pause when in full screen mode. I
6440 wish it had consisten shortcuts and that space also would work when in
6441 window mode. Another nice shortcut in gmplayer is [enter] to restart
6442 the current video. It is very nice when playing short videos from the
6443 web and want to restart it when new people arrive to have a look at
6444 what is going on.&lt;/p&gt;
6445 </description>
6446 </item>
6447
6448 <item>
6449 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
6450 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
6451 <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>
6452 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
6453 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
6454 upgrade testing of the
6455 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6456 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
6457 This seem like a very good idea, so I adjusted by test scripts and
6458 can now present the updated result from today:&lt;/p&gt;
6459
6460 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6461
6462 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6463
6464 &lt;blockquote&gt;&lt;p&gt;
6465 apache2.2-bin
6466 aptdaemon
6467 baobab
6468 binfmt-support
6469 browser-plugin-gnash
6470 cheese-common
6471 cli-common
6472 cups-pk-helper
6473 dmz-cursor-theme
6474 empathy
6475 empathy-common
6476 freedesktop-sound-theme
6477 freeglut3
6478 gconf-defaults-service
6479 gdm-themes
6480 gedit-plugins
6481 geoclue
6482 geoclue-hostip
6483 geoclue-localnet
6484 geoclue-manual
6485 geoclue-yahoo
6486 gnash
6487 gnash-common
6488 gnome
6489 gnome-backgrounds
6490 gnome-cards-data
6491 gnome-codec-install
6492 gnome-core
6493 gnome-desktop-environment
6494 gnome-disk-utility
6495 gnome-screenshot
6496 gnome-search-tool
6497 gnome-session-canberra
6498 gnome-system-log
6499 gnome-themes-extras
6500 gnome-themes-more
6501 gnome-user-share
6502 gstreamer0.10-fluendo-mp3
6503 gstreamer0.10-tools
6504 gtk2-engines
6505 gtk2-engines-pixbuf
6506 gtk2-engines-smooth
6507 hamster-applet
6508 libapache2-mod-dnssd
6509 libapr1
6510 libaprutil1
6511 libaprutil1-dbd-sqlite3
6512 libaprutil1-ldap
6513 libart2.0-cil
6514 libboost-date-time1.42.0
6515 libboost-python1.42.0
6516 libboost-thread1.42.0
6517 libchamplain-0.4-0
6518 libchamplain-gtk-0.4-0
6519 libcheese-gtk18
6520 libclutter-gtk-0.10-0
6521 libcryptui0
6522 libdiscid0
6523 libelf1
6524 libepc-1.0-2
6525 libepc-common
6526 libepc-ui-1.0-2
6527 libfreerdp-plugins-standard
6528 libfreerdp0
6529 libgconf2.0-cil
6530 libgdata-common
6531 libgdata7
6532 libgdu-gtk0
6533 libgee2
6534 libgeoclue0
6535 libgexiv2-0
6536 libgif4
6537 libglade2.0-cil
6538 libglib2.0-cil
6539 libgmime2.4-cil
6540 libgnome-vfs2.0-cil
6541 libgnome2.24-cil
6542 libgnomepanel2.24-cil
6543 libgpod-common
6544 libgpod4
6545 libgtk2.0-cil
6546 libgtkglext1
6547 libgtksourceview2.0-common
6548 libmono-addins-gui0.2-cil
6549 libmono-addins0.2-cil
6550 libmono-cairo2.0-cil
6551 libmono-corlib2.0-cil
6552 libmono-i18n-west2.0-cil
6553 libmono-posix2.0-cil
6554 libmono-security2.0-cil
6555 libmono-sharpzip2.84-cil
6556 libmono-system2.0-cil
6557 libmtp8
6558 libmusicbrainz3-6
6559 libndesk-dbus-glib1.0-cil
6560 libndesk-dbus1.0-cil
6561 libopal3.6.8
6562 libpolkit-gtk-1-0
6563 libpt2.6.7
6564 libpython2.6
6565 librpm1
6566 librpmio1
6567 libsdl1.2debian
6568 libsrtp0
6569 libssh-4
6570 libtelepathy-farsight0
6571 libtelepathy-glib0
6572 libtidy-0.99-0
6573 media-player-info
6574 mesa-utils
6575 mono-2.0-gac
6576 mono-gac
6577 mono-runtime
6578 nautilus-sendto
6579 nautilus-sendto-empathy
6580 p7zip-full
6581 pkg-config
6582 python-aptdaemon
6583 python-aptdaemon-gtk
6584 python-axiom
6585 python-beautifulsoup
6586 python-bugbuddy
6587 python-clientform
6588 python-coherence
6589 python-configobj
6590 python-crypto
6591 python-cupshelpers
6592 python-elementtree
6593 python-epsilon
6594 python-evolution
6595 python-feedparser
6596 python-gdata
6597 python-gdbm
6598 python-gst0.10
6599 python-gtkglext1
6600 python-gtksourceview2
6601 python-httplib2
6602 python-louie
6603 python-mako
6604 python-markupsafe
6605 python-mechanize
6606 python-nevow
6607 python-notify
6608 python-opengl
6609 python-openssl
6610 python-pam
6611 python-pkg-resources
6612 python-pyasn1
6613 python-pysqlite2
6614 python-rdflib
6615 python-serial
6616 python-tagpy
6617 python-twisted-bin
6618 python-twisted-conch
6619 python-twisted-core
6620 python-twisted-web
6621 python-utidylib
6622 python-webkit
6623 python-xdg
6624 python-zope.interface
6625 remmina
6626 remmina-plugin-data
6627 remmina-plugin-rdp
6628 remmina-plugin-vnc
6629 rhythmbox-plugin-cdrecorder
6630 rhythmbox-plugins
6631 rpm-common
6632 rpm2cpio
6633 seahorse-plugins
6634 shotwell
6635 software-center
6636 system-config-printer-udev
6637 telepathy-gabble
6638 telepathy-mission-control-5
6639 telepathy-salut
6640 tomboy
6641 totem
6642 totem-coherence
6643 totem-mozilla
6644 totem-plugins
6645 transmission-common
6646 xdg-user-dirs
6647 xdg-user-dirs-gtk
6648 xserver-xephyr
6649 &lt;/p&gt;&lt;/blockquote&gt;
6650
6651 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6652
6653 &lt;blockquote&gt;&lt;p&gt;
6654 cheese
6655 ekiga
6656 eog
6657 epiphany-extensions
6658 evolution-exchange
6659 fast-user-switch-applet
6660 file-roller
6661 gcalctool
6662 gconf-editor
6663 gdm
6664 gedit
6665 gedit-common
6666 gnome-games
6667 gnome-games-data
6668 gnome-nettool
6669 gnome-system-tools
6670 gnome-themes
6671 gnuchess
6672 gucharmap
6673 guile-1.8-libs
6674 libavahi-ui0
6675 libdmx1
6676 libgalago3
6677 libgtk-vnc-1.0-0
6678 libgtksourceview2.0-0
6679 liblircclient0
6680 libsdl1.2debian-alsa
6681 libspeexdsp1
6682 libsvga1
6683 rhythmbox
6684 seahorse
6685 sound-juicer
6686 system-config-printer
6687 totem-common
6688 transmission-gtk
6689 vinagre
6690 vino
6691 &lt;/p&gt;&lt;/blockquote&gt;
6692
6693 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6694
6695 &lt;blockquote&gt;&lt;p&gt;
6696 gstreamer0.10-gnomevfs
6697 &lt;/p&gt;&lt;/blockquote&gt;
6698
6699 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6700
6701 &lt;blockquote&gt;&lt;p&gt;
6702 [nothing]
6703 &lt;/p&gt;&lt;/blockquote&gt;
6704
6705 &lt;p&gt;This is for KDE:&lt;/p&gt;
6706
6707 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6708
6709 &lt;blockquote&gt;&lt;p&gt;
6710 ksmserver
6711 &lt;/p&gt;&lt;/blockquote&gt;
6712
6713 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
6714
6715 &lt;blockquote&gt;&lt;p&gt;
6716 kwin
6717 network-manager-kde
6718 &lt;/p&gt;&lt;/blockquote&gt;
6719
6720 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
6721
6722 &lt;blockquote&gt;&lt;p&gt;
6723 arts
6724 dolphin
6725 freespacenotifier
6726 google-gadgets-gst
6727 google-gadgets-xul
6728 kappfinder
6729 kcalc
6730 kcharselect
6731 kde-core
6732 kde-plasma-desktop
6733 kde-standard
6734 kde-window-manager
6735 kdeartwork
6736 kdeartwork-emoticons
6737 kdeartwork-style
6738 kdeartwork-theme-icon
6739 kdebase
6740 kdebase-apps
6741 kdebase-workspace
6742 kdebase-workspace-bin
6743 kdebase-workspace-data
6744 kdeeject
6745 kdelibs
6746 kdeplasma-addons
6747 kdeutils
6748 kdewallpapers
6749 kdf
6750 kfloppy
6751 kgpg
6752 khelpcenter4
6753 kinfocenter
6754 konq-plugins-l10n
6755 konqueror-nsplugins
6756 kscreensaver
6757 kscreensaver-xsavers
6758 ktimer
6759 kwrite
6760 libgle3
6761 libkde4-ruby1.8
6762 libkonq5
6763 libkonq5-templates
6764 libnetpbm10
6765 libplasma-ruby
6766 libplasma-ruby1.8
6767 libqt4-ruby1.8
6768 marble-data
6769 marble-plugins
6770 netpbm
6771 nuvola-icon-theme
6772 plasma-dataengines-workspace
6773 plasma-desktop
6774 plasma-desktopthemes-artwork
6775 plasma-runners-addons
6776 plasma-scriptengine-googlegadgets
6777 plasma-scriptengine-python
6778 plasma-scriptengine-qedje
6779 plasma-scriptengine-ruby
6780 plasma-scriptengine-webkit
6781 plasma-scriptengines
6782 plasma-wallpapers-addons
6783 plasma-widget-folderview
6784 plasma-widget-networkmanagement
6785 ruby
6786 sweeper
6787 update-notifier-kde
6788 xscreensaver-data-extra
6789 xscreensaver-gl
6790 xscreensaver-gl-extra
6791 xscreensaver-screensaver-bsod
6792 &lt;/p&gt;&lt;/blockquote&gt;
6793
6794 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
6795
6796 &lt;blockquote&gt;&lt;p&gt;
6797 ark
6798 google-gadgets-common
6799 google-gadgets-qt
6800 htdig
6801 kate
6802 kdebase-bin
6803 kdebase-data
6804 kdepasswd
6805 kfind
6806 klipper
6807 konq-plugins
6808 konqueror
6809 ksysguard
6810 ksysguardd
6811 libarchive1
6812 libcln6
6813 libeet1
6814 libeina-svn-06
6815 libggadget-1.0-0b
6816 libggadget-qt-1.0-0b
6817 libgps19
6818 libkdecorations4
6819 libkephal4
6820 libkonq4
6821 libkonqsidebarplugin4a
6822 libkscreensaver5
6823 libksgrd4
6824 libksignalplotter4
6825 libkunitconversion4
6826 libkwineffects1a
6827 libmarblewidget4
6828 libntrack-qt4-1
6829 libntrack0
6830 libplasma-geolocation-interface4
6831 libplasmaclock4a
6832 libplasmagenericshell4
6833 libprocesscore4a
6834 libprocessui4a
6835 libqalculate5
6836 libqedje0a
6837 libqtruby4shared2
6838 libqzion0a
6839 libruby1.8
6840 libscim8c2a
6841 libsmokekdecore4-3
6842 libsmokekdeui4-3
6843 libsmokekfile3
6844 libsmokekhtml3
6845 libsmokekio3
6846 libsmokeknewstuff2-3
6847 libsmokeknewstuff3-3
6848 libsmokekparts3
6849 libsmokektexteditor3
6850 libsmokekutils3
6851 libsmokenepomuk3
6852 libsmokephonon3
6853 libsmokeplasma3
6854 libsmokeqtcore4-3
6855 libsmokeqtdbus4-3
6856 libsmokeqtgui4-3
6857 libsmokeqtnetwork4-3
6858 libsmokeqtopengl4-3
6859 libsmokeqtscript4-3
6860 libsmokeqtsql4-3
6861 libsmokeqtsvg4-3
6862 libsmokeqttest4-3
6863 libsmokeqtuitools4-3
6864 libsmokeqtwebkit4-3
6865 libsmokeqtxml4-3
6866 libsmokesolid3
6867 libsmokesoprano3
6868 libtaskmanager4a
6869 libtidy-0.99-0
6870 libweather-ion4a
6871 libxklavier16
6872 libxxf86misc1
6873 okteta
6874 oxygencursors
6875 plasma-dataengines-addons
6876 plasma-scriptengine-superkaramba
6877 plasma-widget-lancelot
6878 plasma-widgets-addons
6879 plasma-widgets-workspace
6880 polkit-kde-1
6881 ruby1.8
6882 systemsettings
6883 update-notifier-common
6884 &lt;/p&gt;&lt;/blockquote&gt;
6885
6886 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
6887 aptitude a bit more similar, but there are still quite a lott of
6888 differences. I have no idea what packages should be installed after
6889 the upgrade, but hope those that do can have a look.&lt;/p&gt;
6890 </description>
6891 </item>
6892
6893 <item>
6894 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
6895 <link>http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
6896 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
6897 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
6898 <description>&lt;p&gt;Most of the computers in use by the
6899 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
6900 are virtual machines. And they have been Xen machines running on a
6901 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
6902 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
6903 bit harder that it could have been, because we set up the Xen virtual
6904 machines to get the virtual partitions from LVM, which as far as I
6905 know is not supported by KVM. So to migrate, we had to convert
6906 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
6907
6908 &lt;p&gt;I found
6909 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
6910 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
6911 migration. It uses qemu-img from the qemu package to make the disk
6912 image, parted to partition it, losetup and kpartx to present the disk
6913 image partions as devices, and dd to copy the data. I NFS mounted the
6914 new servers storage area on the old server to do the migration.&lt;/p&gt;
6915
6916 &lt;pre&gt;
6917 #!/bin/sh
6918
6919 # Based on
6920 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
6921
6922 set -e
6923 set -x
6924
6925 if [ -z &quot;$1&quot; ] ; then
6926 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
6927 exit 1
6928 else
6929 host=&quot;$1&quot;
6930 fi
6931
6932 if [ ! -e /dev/vg_data/$host-disk ] ; then
6933 echo &quot;error: unable to find LVM volume for $host&quot;
6934 exit 1
6935 fi
6936
6937 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
6938 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6939 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
6940 totalsize=$(( ( $disksize + $swapsize ) ))
6941
6942 img=$host.img
6943 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
6944 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
6945
6946 parted $img mklabel msdos
6947 parted $img mkpart primary linux-swap 0 $disksize
6948 parted $img mkpart primary ext2 $disksize $totalsize
6949 parted $img set 1 boot on
6950
6951 modprobe dm-mod
6952 losetup /dev/loop0 $img
6953 kpartx -a /dev/loop0
6954
6955 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
6956 fsck.ext3 -f /dev/mapper/loop0p1 || true
6957 mkswap /dev/mapper/loop0p2
6958
6959 kpartx -d /dev/loop0
6960 losetup -d /dev/loop0
6961 &lt;/pre&gt;
6962
6963 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
6964 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
6965
6966 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
6967 the new disk image attached, installed grub-pc and linux-image-686 and
6968 set up grub to boot from the disk image. After this, the KVM machines
6969 seem to work just fine.&lt;/p&gt;
6970 </description>
6971 </item>
6972
6973 <item>
6974 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
6975 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
6976 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
6977 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
6978 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
6979 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
6980 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
6981 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
6982
6983 &lt;p&gt;I still do not know what a correct migration should look like, so I
6984 report any differences between apt and aptitude and hope someone else
6985 can see if anything should be changed.&lt;/p&gt;
6986
6987 &lt;p&gt;This is for Gnome:&lt;/p&gt;
6988
6989 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
6990
6991 &lt;blockquote&gt;&lt;p&gt;
6992 apache2.2-bin aptdaemon at-spi baobab binfmt-support
6993 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
6994 dmz-cursor-theme empathy empathy-common finger
6995 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
6996 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
6997 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
6998 gnome-cards-data gnome-codec-install gnome-core
6999 gnome-desktop-environment gnome-disk-utility gnome-screenshot
7000 gnome-search-tool gnome-session-canberra gnome-spell
7001 gnome-system-log gnome-themes-extras gnome-themes-more
7002 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
7003 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
7004 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
7005 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
7006 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
7007 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
7008 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
7009 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
7010 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
7011 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
7012 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
7013 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
7014 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
7015 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
7016 libgtk2.0-cil libgtkglext1 libgtksourceview-common
7017 libgtksourceview2.0-common libmono-addins-gui0.2-cil
7018 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
7019 libmono-i18n-west2.0-cil libmono-posix2.0-cil
7020 libmono-security2.0-cil libmono-sharpzip2.84-cil
7021 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
7022 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
7023 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
7024 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
7025 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
7026 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
7027 libxalan2-java libxerces2-java media-player-info mesa-utils
7028 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
7029 nautilus-sendto-empathy openoffice.org-writer2latex
7030 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
7031 python-aptdaemon python-aptdaemon-gtk python-axiom
7032 python-beautifulsoup python-bugbuddy python-clientform
7033 python-coherence python-configobj python-crypto python-cupshelpers
7034 python-cupsutils python-eggtrayicon python-elementtree
7035 python-epsilon python-evolution python-feedparser python-gdata
7036 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
7037 python-gtksourceview2 python-httplib2 python-louie python-mako
7038 python-markupsafe python-mechanize python-nevow python-notify
7039 python-opengl python-openssl python-pam python-pkg-resources
7040 python-pyasn1 python-pysqlite2 python-rdflib python-serial
7041 python-tagpy python-twisted-bin python-twisted-conch
7042 python-twisted-core python-twisted-web python-utidylib python-webkit
7043 python-xdg python-zope.interface remmina remmina-plugin-data
7044 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
7045 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
7046 software-center svgalibg1 system-config-printer-udev
7047 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
7048 totem totem-coherence totem-mozilla totem-plugins
7049 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
7050 zip
7051 &lt;/p&gt;&lt;/blockquote&gt;
7052
7053 Installed using apt-get, removed with aptitude
7054
7055 &lt;blockquote&gt;&lt;p&gt;
7056 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
7057 epiphany-extensions epiphany-gecko evolution-exchange
7058 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
7059 gedit-common gnome-app-install gnome-games gnome-games-data
7060 gnome-nettool gnome-system-tools gnome-themes gnome-utils
7061 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
7062 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
7063 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
7064 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
7065 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
7066 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
7067 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7068 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7069 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7070 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
7071 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
7072 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
7073 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
7074 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
7075 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
7076 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
7077 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
7078 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
7079 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
7080 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
7081 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
7082 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
7083 sound-juicer swfdec-gnome system-config-printer totem-common
7084 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
7085 &lt;/p&gt;&lt;/blockquote&gt;
7086
7087 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7088
7089 &lt;blockquote&gt;&lt;p&gt;
7090 gstreamer0.10-gnomevfs
7091 &lt;/p&gt;&lt;/blockquote&gt;
7092
7093 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7094
7095 &lt;blockquote&gt;&lt;p&gt;
7096 [nothing]
7097 &lt;/p&gt;&lt;/blockquote&gt;
7098
7099 &lt;p&gt;This is for KDE:&lt;/p&gt;
7100
7101 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7102
7103 &lt;blockquote&gt;&lt;p&gt;
7104 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
7105 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
7106 ghostscript-x git gnome-audio gnugo granatier gs-common
7107 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
7108 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
7109 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
7110 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
7111 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
7112 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
7113 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
7114 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
7115 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
7116 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
7117 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
7118 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
7119 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
7120 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
7121 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
7122 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
7123 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
7124 libkrossui4 libmailtools-perl libmime-tools-perl
7125 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
7126 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
7127 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
7128 lirc luatex marble networkstatus noatun-plugins
7129 openoffice.org-writer2latex palapeli palapeli-data parley
7130 parley-data poster psutils pulseaudio pulseaudio-esound-compat
7131 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
7132 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
7133 ttf-sazanami-gothic
7134 &lt;/p&gt;&lt;/blockquote&gt;
7135
7136 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7137
7138 &lt;blockquote&gt;&lt;p&gt;
7139 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
7140 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
7141 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
7142 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
7143 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
7144 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
7145 kitchensync kiten kjumpingcube klatin klettres klickety klines
7146 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
7147 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
7148 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
7149 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
7150 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
7151 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
7152 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
7153 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
7154 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
7155 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
7156 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
7157 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
7158 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
7159 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
7160 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
7161 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
7162 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
7163 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
7164 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
7165 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
7166 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
7167 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
7168 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
7169 mpeglib network-manager-kde noatun pmount tex-common texlive-base
7170 texlive-common texlive-doc-base texlive-fonts-recommended tidy
7171 ttf-dustin ttf-kochi-gothic ttf-sjfonts
7172 &lt;/p&gt;&lt;/blockquote&gt;
7173
7174 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7175
7176 &lt;blockquote&gt;&lt;p&gt;
7177 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
7178 kdeartwork kdebase kdebase-apps kdebase-workspace
7179 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
7180 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
7181 netpbm plasma-widget-folderview plasma-widget-networkmanagement
7182 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
7183 xscreensaver-screensaver-bsod
7184 &lt;/p&gt;&lt;/blockquote&gt;
7185
7186 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7187
7188 &lt;blockquote&gt;&lt;p&gt;
7189 kdebase-bin konq-plugins konqueror
7190 &lt;/p&gt;&lt;/blockquote&gt;
7191 </description>
7192 </item>
7193
7194 <item>
7195 <title>Gnash buildbot slave and Debian kfreebsd</title>
7196 <link>http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
7197 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
7198 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
7199 <description>&lt;p&gt;Answering
7200 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
7201 call from the Gnash project&lt;/a&gt; for
7202 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
7203 current source, I have set up a virtual KVM machine on the Debian
7204 Edu/Skolelinux virtualization host to test the git source on
7205 Debian/Squeeze. I hope this can help the developers in getting new
7206 releases out more often.&lt;/p&gt;
7207
7208 &lt;p&gt;As the developers want less main-stream build platforms tested to,
7209 I have considered setting up a &lt;a
7210 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
7211 machine as well. I have also considered using the kfreebsd
7212 architecture in Debian as a file server in NUUG to get access to the 5
7213 TB zfs volume we currently use to store DV video. Because of this, I
7214 finally got around to do a test installation of Debian/Squeeze with
7215 kfreebsd. Installation went fairly smooth, thought I noticed some
7216 visual glitches in the cdebconf dialogs (black cursor left on the
7217 screen at random locations). Have not gotten very far with the
7218 testing. Noticed cfdisk did not work, but fdisk did so it was not a
7219 fatal problem. Have to spend some more time on it to see if it is
7220 useful as a file server for NUUG. Will try to find time to set up a
7221 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
7222 </description>
7223 </item>
7224
7225 <item>
7226 <title>Debian in 3D</title>
7227 <link>http://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
7228 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
7229 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
7230 <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;
7231
7232 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
7233 3D linked in from
7234 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
7235 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
7236 </description>
7237 </item>
7238
7239 <item>
7240 <title>Software updates 2010-10-24</title>
7241 <link>http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
7242 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
7243 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
7244 <description>&lt;p&gt;Some updates.&lt;/p&gt;
7245
7246 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
7247 raise money for the project is going well. The lower limit of 10
7248 signers was reached in 24 hours, and so far 13 people have signed it.
7249 More signers and more funding is most welcome, and I am really curious
7250 how far we can get before the time limit of December 24 is reached.
7251 :)&lt;/p&gt;
7252
7253 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
7254 about what appear to be a great code coverage tool capable of
7255 generating code coverage stats without any changes to the source code.
7256 It is called
7257 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
7258 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
7259 It is missing in Debian, but the git source built just fine in Squeeze
7260 after I installed libelf-dev, libdwarf-dev, pkg-config and
7261 libglib2.0-dev. Failed to build in Lenny, but suspect that is
7262 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
7263
7264 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
7265 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
7266 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
7267 alpha test release of the Squeeze based Debian Edu /
7268 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
7269 release. Give it a try if you need a complete linux solution for your
7270 school, including central infrastructure server, workstations, thin
7271 client servers and diskless workstations. A nice touch added
7272 yesterday is RDP support on the thin client servers, for windows
7273 clients to get a Linux desktop on request.&lt;/p&gt;
7274 </description>
7275 </item>
7276
7277 <item>
7278 <title>Some notes on Flash in Debian and Debian Edu</title>
7279 <link>http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
7280 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
7281 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
7282 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
7283 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
7284 second most popular used package that is missing in Debian. The sixth
7285 most popular is flashplayer-mozilla. This is a clear indication that
7286 working flash is important for Debian users. Around 10 percent of the
7287 users submitting data to popcon.debian.org have this package
7288 installed.&lt;/p&gt;
7289
7290 &lt;p&gt;In the report written by Lars Risan in August 2008
7291&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
7292 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
7293 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
7294 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
7295 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
7296 web sites require Flash to work, and lacking working Flash support in
7297 the web browser and the problems with installing it was perceived as a
7298 good reason to stay with Windows.&lt;/p&gt;
7299
7300 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
7301 said to be the retarded cousin that did not really understand
7302 everything you told him but could work fairly well. This was a
7303 comment regarding the problems Linux have with proprietary formats and
7304 non-standard web pages, and is sad because it exposes a fairly common
7305 understanding of whose fault it is if web pages that only work in for
7306 example Internet Explorer 6 fail to work on Firefox, and funny because
7307 it explain very well how annoying it is for users when Linux
7308 distributions do not work with the documents they receive or the web
7309 pages they want to visit.&lt;/p&gt;
7310
7311 &lt;p&gt;This is part of the reason why I believe it is important for Debian
7312 and Debian Edu to have a well working Flash implementation in the
7313 distribution, to get at least popular sites as Youtube and Google
7314 Video to working out of the box. For Squeeze, Debian have the chance
7315 to include the latest version of Gnash that will make this happen, as
7316 the new release 0.8.8 was published a few weeks ago and is resting in
7317 unstable. The new version work with more sites that version 0.8.7.
7318 The Gnash maintainers have asked for a freeze exception, but the
7319 release team have not had time to reply to it yet. I hope they agree
7320 with me that Flash is important for the Debian desktop users, and thus
7321 accept the new package into Squeeze.&lt;/p&gt;
7322 </description>
7323 </item>
7324
7325 <item>
7326 <title>Circular package dependencies harms apt recovery</title>
7327 <link>http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
7328 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
7329 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
7330 <description>&lt;p&gt;I discovered this while doing
7331 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
7332 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
7333 in Debian still got circular dependencies, and it is often claimed
7334 that apt and aptitude should be able to handle this just fine, but
7335 some times these dependency loops causes apt to fail.&lt;/p&gt;
7336
7337 &lt;p&gt;An example is from todays
7338 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
7339 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
7340 causes perl-modules to fail to upgrade. The cause is simple. If a
7341 package fail to unpack, then only part of packages with the circular
7342 dependency might end up being unpacked when unpacking aborts, and the
7343 ones already unpacked will fail to configure in the recovery phase
7344 because its dependencies are unavailable.&lt;/p&gt;
7345
7346 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
7347
7348 &lt;blockquote&gt;&lt;pre&gt;
7349 dpkg: dependency problems prevent configuration of perl-modules:
7350 perl-modules depends on perl (&gt;= 5.10.1-1); however:
7351 Version of perl on system is 5.10.0-19lenny2.
7352 dpkg: error processing perl-modules (--configure):
7353 dependency problems - leaving unconfigured
7354 &lt;/pre&gt;&lt;/blockquote&gt;
7355
7356 &lt;p&gt;The perl/perl-modules circular dependency is already
7357 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
7358 hopefully be solved as soon as possible, but it is not the only one,
7359 and each one of these loops in the dependency tree can cause similar
7360 failures. Of course, they only occur when there are bugs in other
7361 packages causing the unpacking to fail, but it is rather nasty when
7362 the failure of one package causes the problem to become worse because
7363 of dependency loops.&lt;/p&gt;
7364
7365 &lt;p&gt;Thanks to
7366 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
7367 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
7368 dependencies
7369 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
7370 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
7371
7372 &lt;p&gt;Todays testing also exposed a bug in
7373 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
7374 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
7375 apt-get and aptitude, the latter possibly caused by some circular
7376 dependency. Reported both to BTS to try to get someone to look at
7377 it.&lt;/p&gt;
7378 </description>
7379 </item>
7380
7381 <item>
7382 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
7383 <link>http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
7384 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
7385 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
7386 <description>&lt;p&gt;This is a
7387 &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;
7388 on my
7389 &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
7390 work&lt;/a&gt; on
7391 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
7392 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
7393
7394 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
7395 LDAP objects, I have had a look at how the packages pdns-backend-ldap
7396 and dhcp3-server-ldap in Debian use the LDAP server. The two
7397 implementations are quite different in how they use LDAP.&lt;/p&gt;
7398
7399 To get this information, I started slapd with debugging enabled and
7400 dumped the debug output to a file to get the LDAP searches performed
7401 on a Debian Edu main-server. Here is a summary.
7402
7403 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
7404
7405 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
7406 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
7407 the web.
7408
7409 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
7410 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
7411 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
7412 reverse entries are in two different subtrees in LDAP with a structure
7413 based on the DNS names, as in tjener.intern and
7414 2.2.0.10.in-addr.arpa.&lt;/p&gt;
7415
7416 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
7417 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
7418 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
7419 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
7420 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
7421 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
7422 forward entries, it is looking for attributes named dnsttl, arecord,
7423 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
7424 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
7425 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
7426 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
7427 spfrecord and modifytimestamp. For reverse entries it is looking for
7428 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
7429 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
7430 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
7431 ldapsearch commands could look like this:&lt;/p&gt;
7432
7433 &lt;blockquote&gt;&lt;pre&gt;
7434 ldapsearch -h ldap \
7435 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7436 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
7437 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7438 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7439 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7440 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7441
7442 ldapsearch -h ldap \
7443 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
7444 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
7445 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
7446 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
7447 srvrecord naptrrecord modifytimestamp
7448 &lt;/pre&gt;&lt;/blockquote&gt;
7449
7450 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
7451 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
7452 example LDAP objects used there. In addition to these objects, the
7453 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
7454 also exist.&lt;/p&gt;
7455
7456 &lt;blockquote&gt;&lt;pre&gt;
7457 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
7458 objectclass: top
7459 objectclass: dnsdomain
7460 objectclass: domainrelatedobject
7461 dc: tjener
7462 arecord: 10.0.2.2
7463 associateddomain: tjener.intern
7464
7465 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
7466 objectclass: top
7467 objectclass: dnsdomain2
7468 objectclass: domainrelatedobject
7469 dc: 2
7470 ptrrecord: tjener.intern
7471 associateddomain: 2.2.0.10.in-addr.arpa
7472 &lt;/pre&gt;&lt;/blockquote&gt;
7473
7474 &lt;p&gt;In strict mode, the server behaves differently. When looking for
7475 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
7476 same base as in the tree mode for a object with filter
7477 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
7478 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
7479 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
7480 naptrrecord and modifytimestamp. For reverse entires it also do a
7481 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
7482 and the requested attributes are associateddomain, dnsttl and
7483 modifytimestamp. In short, in strict mode the objects with ptrrecord
7484 go away, and the arecord attribute in the forward object is used
7485 instead.&lt;/p&gt;
7486
7487 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
7488 like this:&lt;/p&gt;
7489
7490 &lt;blockquote&gt;&lt;pre&gt;
7491 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7492 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
7493 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
7494 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
7495 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
7496 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
7497
7498 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
7499 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
7500 &lt;/pre&gt;&lt;/blockquote&gt;
7501
7502 &lt;p&gt;In addition to the forward and reverse searches , there is also a
7503 search for SOA records, which behave similar to the forward and
7504 reverse lookups.&lt;/p&gt;
7505
7506 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
7507 specify any objectclass names, and instead look for the attributes it
7508 need to generate a DNS reply. This make it able to work with any
7509 objectclass that provide the needed attributes.&lt;/p&gt;
7510
7511 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
7512 dnsdomain2 schemas. The latter is used for reverse entries like
7513 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
7514
7515 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
7516 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
7517 attributes) and domainrelatedobject (for associatedDomain). The use
7518 of structural object classes make it impossible to combine these
7519 classes with the object classes used by DHCP.&lt;/p&gt;
7520
7521 &lt;p&gt;There are other schemas that could be used too, for example the
7522 dnszone structural object class used by Gosa and bind-sdb for the DNS
7523 attributes combined with the domainrelatedobject object class, but in
7524 this case some unused attributes would have to be included as well
7525 (zonename and relativedomainname).&lt;/p&gt;
7526
7527 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
7528 mode and not use any of the existing objectclasses (dnsdomain,
7529 dnsdomain2 and dnszone) when one want to combine the DNS information
7530 with DHCP information, and instead create a auxiliary object class
7531 defined something like this (using the attributes defined for
7532 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
7533
7534 &lt;blockquote&gt;&lt;pre&gt;
7535 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
7536 SUP top
7537 AUXILIARY
7538 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
7539 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
7540 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
7541 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
7542 A6Record $ DNAMERecord
7543 ))
7544 &lt;/pre&gt;&lt;/blockquote&gt;
7545
7546 &lt;p&gt;This will allow any object to become a DNS entry when combined with
7547 the domainrelatedobject object class, and allow any entity to include
7548 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
7549 developers asking for their view on this schema and if they are
7550 interested in providing such schema with PowerDNS, and I hope my
7551 message will be accepted into their mailing list soon.&lt;/p&gt;
7552
7553 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
7554
7555 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
7556 the object attributes, and then uses the attributes it want. This
7557 make it harder to figure out exactly what attributes are used, but
7558 thanks to the working example in Debian Edu I can at least get an idea
7559 what is needed without having to read the source code.&lt;/p&gt;
7560
7561 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
7562 search filter to use to locate the correct dhcpServer entity is
7563 stored. These are the relevant entries from
7564 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
7565
7566 &lt;blockquote&gt;&lt;pre&gt;
7567 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
7568 ldap-dhcp-server-cn &quot;dhcp&quot;;
7569 &lt;/pre&gt;&lt;/blockquote&gt;
7570
7571 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
7572 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
7573 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
7574 search result is this entry:&lt;/p&gt;
7575
7576 &lt;blockquote&gt;&lt;pre&gt;
7577 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
7578 cn: dhcp
7579 objectClass: top
7580 objectClass: dhcpServer
7581 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7582 &lt;/pre&gt;&lt;/blockquote&gt;
7583
7584 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
7585 subtree with DHCP configuration. The DHCP configuration subtree base
7586 is located using a base scope search with base &quot;cn=DHCP
7587 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
7588 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
7589 The search result is this entry:&lt;/p&gt;
7590
7591 &lt;blockquote&gt;&lt;pre&gt;
7592 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7593 cn: DHCP Config
7594 objectClass: top
7595 objectClass: dhcpService
7596 objectClass: dhcpOptions
7597 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
7598 dhcpStatements: ddns-update-style none
7599 dhcpStatements: authoritative
7600 dhcpOption: smtp-server code 69 = array of ip-address
7601 dhcpOption: www-server code 72 = array of ip-address
7602 dhcpOption: wpad-url code 252 = text
7603 &lt;/pre&gt;&lt;/blockquote&gt;
7604
7605 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
7606 all the DHCP configuration is loaded, it is ready to receive requests.
7607 The subtree in Debian Edu contain objects with object classes
7608 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
7609 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
7610 and information about netmasks, dynamic range etc. Leaving out the
7611 details here because it is not relevant for the focus of my
7612 investigation, which is to see if it is possible to merge dns and dhcp
7613 related computer objects.&lt;/p&gt;
7614
7615 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
7616 of the client (00:00:00:00:00:00 in this example), using a subtree
7617 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
7618 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
7619 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
7620 like:&lt;/p&gt;
7621
7622 &lt;blockquote&gt;&lt;pre&gt;
7623 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7624 cn: hostname
7625 objectClass: top
7626 objectClass: dhcpHost
7627 dhcpHWAddress: ethernet 00:00:00:00:00:00
7628 dhcpStatements: fixed-address hostname
7629 &lt;/pre&gt;&lt;/blockquote&gt;
7630
7631 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
7632 The object classes need to have fixed names, and the configuration
7633 need to be stored in a fairly specific LDAP structure. On the
7634 positive side, the invidiual dhcpHost entires can be anywhere without
7635 the DN pointed to by the dhcpServer entries. The latter should make
7636 it possible to group all host entries in a subtree next to the
7637 configuration entries, and this subtree can also be shared with the
7638 DNS server if the schema proposed above is combined with the dhcpHost
7639 structural object class.
7640
7641 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
7642
7643 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
7644 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
7645 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
7646 allowing DNS objects to be stored anywhere under the base cn specified
7647 in the configuration.&lt;/p&gt;
7648
7649 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
7650 regarding which LDAP schemas to use and which LDAP structure to use.
7651 I guess one could implement ones own schema, as long as the
7652 objectclasses and attributes have the names used, but this do not
7653 really help when the DHCP subtree need to have a fairly fixed
7654 structure.&lt;/p&gt;
7655
7656 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
7657 this might work for Debian Edu:&lt;/p&gt;
7658
7659 &lt;blockquote&gt;&lt;pre&gt;
7660 ou=services
7661 cn=machine-info (dhcpService) - dhcpServiceDN points here
7662 cn=dhcp (dhcpServer)
7663 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
7664 cn=10.0.2.0 (dhcpSubnet)
7665 cn=group1 (dhcpGroup/dhcpOptions)
7666 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
7667 cn=192.168.0.0 (dhcpSubnet)
7668 cn=group1 (dhcpGroup/dhcpOptions)
7669 ou=machines - PowerDNS base points here
7670 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
7671 &lt;/pre&gt;&lt;/blockquote&gt;
7672
7673 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
7674 entries to be in the dhcpGroup subtrees, the entries can be stored
7675 there instead of a common machines subtree, and the PowerDNS base
7676 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
7677
7678 &lt;p&gt;The combined object under the machines subtree would look something
7679 like this:&lt;/p&gt;
7680
7681 &lt;blockquote&gt;&lt;pre&gt;
7682 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
7683 dc: hostname
7684 objectClass: top
7685 objectClass: dhcpHost
7686 objectclass: domainrelatedobject
7687 objectclass: dnsDomainAux
7688 associateddomain: hostname.intern
7689 arecord: 10.11.12.13
7690 dhcpHWAddress: ethernet 00:00:00:00:00:00
7691 dhcpStatements: fixed-address hostname.intern
7692 &lt;/pre&gt;&lt;/blockquote&gt;
7693
7694 &lt;/p&gt;One could even add the LTSP configuration associated with a given
7695 machine, as long as the required attributes are available in a
7696 auxiliary object class.&lt;/p&gt;
7697 </description>
7698 </item>
7699
7700 <item>
7701 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
7702 <link>http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
7703 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
7704 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
7705 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
7706 DHCP services in Debian Edu to use the same LDAP objects for a given
7707 computer, to avoid the possibility of having a inconsistent state for
7708 a computer in LDAP (as in DHCP but no DNS entry or the other way
7709 around) and make it easier to add computers to LDAP.&lt;/p&gt;
7710
7711 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
7712 information finally found a solution that seem to work.&lt;/p&gt;
7713
7714 &lt;p&gt;The old setup required three LDAP objects for a given computer.
7715 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
7716 we switch powerdns to use its strict LDAP method (ldap-method=strict
7717 in pdns-debian-edu.conf), the forward and reverse DNS entries are
7718 merged into one while making it impossible to transfer the reverse map
7719 to a slave DNS server.&lt;/p&gt;
7720
7721 &lt;p&gt;If we also replace the object class used to get the DNS related
7722 attributes to one allowing these attributes to be combined with the
7723 dhcphost object class, we can merge the DNS and DHCP entries into one.
7724 I&#39;ve written such object class in the dnsdomainaux.schema file (need
7725 proper OIDs, but that is a minor issue), and tested the setup. It
7726 seem to work.&lt;/p&gt;
7727
7728 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
7729 for both DNS and DHCP, and even the LTSP configuration I suggested in
7730 an earlier email. The combined LDAP object will look something like
7731 this:&lt;/p&gt;
7732
7733 &lt;blockquote&gt;&lt;pre&gt;
7734 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
7735 cn: hostname
7736 objectClass: dhcphost
7737 objectclass: domainrelatedobject
7738 objectclass: dnsdomainaux
7739 associateddomain: hostname.intern
7740 arecord: 10.11.12.13
7741 dhcphwaddress: ethernet 00:00:00:00:00:00
7742 dhcpstatements: fixed-address hostname
7743 ldapconfigsound: Y
7744 &lt;/pre&gt;&lt;/blockquote&gt;
7745
7746 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
7747 the DHCP server uses the dhcphwaddress and dhcpstatements entries
7748 before asking DNS to resolve the fixed-adddress. LTSP will use
7749 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
7750
7751 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
7752 dhcphost in a different location, to allow us to put the objects
7753 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
7754 that. If I can&#39;t figure out a way to do that, we can still get rid of
7755 the hosts subtree and move all its content into the DHCP Config tree
7756 (which probably should be renamed to be more related to the new
7757 content. I suspect cn=dnsdhcp,ou=services or something like that
7758 might be a good place to put it.&lt;/p&gt;
7759
7760 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7761 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7762 </description>
7763 </item>
7764
7765 <item>
7766 <title>Idea for storing LTSP configuration in LDAP</title>
7767 <link>http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
7768 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
7769 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
7770 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
7771 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
7772 clients, and that this can be used to fetch configuration from LDAP if
7773 Debian Edu choose to store configuration there.&lt;/p&gt;
7774
7775 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
7776 to get configuration from LDAP. The idea is to look up the MAC
7777 address of the client in LDAP, and look for attributes on the form
7778 ltspconfigsetting=value, and use this to export SETTING=value to the
7779 LTSP clients.&lt;/p&gt;
7780
7781 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
7782 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
7783 allowing us to store all information about a computer in one place.&lt;/p&gt;
7784
7785 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
7786 this approach. A real LDAP schema for the ltspClientAux objectclass
7787 need to be written. Comments, suggestions, etc?&lt;/p&gt;
7788
7789 &lt;blockquote&gt;&lt;pre&gt;
7790 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
7791 #
7792 # Fetch LTSP client settings from LDAP based on MAC address
7793 #
7794 # Uses ethernet address as stored in the dhcpHost objectclass using
7795 # the dhcpHWAddress attribute or ethernet address stored in the
7796 # ieee802Device objectclass with the macAddress attribute.
7797 #
7798 # This module is written to be schema agnostic, and only depend on the
7799 # existence of attribute names.
7800 #
7801 # The LTSP configuration variables are saved directly using a
7802 # ltspConfig prefix and uppercasing the rest of the attribute name.
7803 # To set the SERVER variable, set the ltspConfigServer attribute.
7804 #
7805 # Some LDAP schema should be created with all the relevant
7806 # configuration settings. Something like this should work:
7807 #
7808 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
7809 # SUP top
7810 # AUXILIARY
7811 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
7812
7813 LDAPSERVER=$(debian-edu-ldapserver)
7814 if [ &quot;$LDAPSERVER&quot; ] ; then
7815 LDAPBASE=$(debian-edu-ldapserver -b)
7816 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
7817 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
7818 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
7819 grep &#39;^ltspConfig&#39; | while read attr value ; do
7820 # Remove prefix and convert to upper case
7821 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
7822 # bass value on to clients
7823 eval &quot;$attr=$value; export $attr&quot;
7824 done
7825 done
7826 fi
7827 &lt;/pre&gt;&lt;/blockquote&gt;
7828
7829 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
7830 the while block might end up in a subshell causing the variables set
7831 there to not show up in ltsp-config, but if that is the case I am sure
7832 the code can be restructured to make sure the variables are passed on.
7833 I expect that can be solved with some testing. :)&lt;/p&gt;
7834
7835 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
7836 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7837
7838 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
7839 configuration in LDAP that was created around year 2000 by
7840 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
7841 Xperience, Inc., 2000&lt;/a&gt;. I found its
7842 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
7843 personal home page over at redhat.com.&lt;/p&gt;
7844 </description>
7845 </item>
7846
7847 <item>
7848 <title>jXplorer, a very nice LDAP GUI</title>
7849 <link>http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
7850 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
7851 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
7852 <description>&lt;p&gt;Since
7853 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
7854 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
7855 LDAP GUI that is even better than luma. The java application
7856 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
7857 moving LDAP objects and subtrees using drag-and-drop, and can
7858 authenticate using Kerberos. I have only tested the Kerberos
7859 authentication, but do not have a LDAP setup allowing me to rewrite
7860 LDAP with my test user yet. It is
7861 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
7862 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
7863 have with it is how it handle errors. If something go wrong, its
7864 non-intuitive behaviour require me to go through some query work list
7865 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
7866 </description>
7867 </item>
7868
7869 <item>
7870 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
7871 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
7872 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
7873 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
7874 <description>&lt;p&gt;Here is a short update on my &lt;a
7875 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
7876 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
7877 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
7878 not reporting the status for KDE, because the upgrade crashes when
7879 aptitude try because of missing conflicts
7880 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
7881 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
7882
7883 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
7884 complete list of the installed packages. Based on this I see these
7885 differences when I did a test run today. As usual, I do not really
7886 know what the correct set of packages would be, but thought it best to
7887 publish the difference.&lt;/p&gt;
7888
7889 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
7890
7891 &lt;blockquote&gt;&lt;p&gt;
7892 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
7893 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
7894 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
7895 libgtksourceview-common libpt-1.10.10-plugins-alsa
7896 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
7897 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
7898 python-4suite-xml python-eggtrayicon python-gtkhtml2
7899 python-gtkmozembed svgalibg1 xserver-xephyr zip
7900 &lt;/p&gt;&lt;/blockquote&gt;
7901
7902 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
7903
7904 &lt;blockquote&gt;&lt;p&gt;
7905 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
7906 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
7907 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
7908 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
7909 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
7910 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
7911 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
7912 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
7913 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
7914 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
7915 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
7916 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
7917 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
7918 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
7919 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
7920 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
7921 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
7922 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
7923 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
7924 mysql-common swfdec-gnome totem-gstreamer wodim
7925 &lt;/p&gt;&lt;/blockquote&gt;
7926
7927 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
7928
7929 &lt;blockquote&gt;&lt;p&gt;
7930 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
7931 python-gnomekeyring python-wnck rhythmbox-plugins xorg
7932 xserver-xorg-input-all xserver-xorg-input-evdev
7933 xserver-xorg-input-kbd xserver-xorg-input-mouse
7934 xserver-xorg-input-synaptics xserver-xorg-video-all
7935 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
7936 xserver-xorg-video-chips xserver-xorg-video-cirrus
7937 xserver-xorg-video-dummy xserver-xorg-video-fbdev
7938 xserver-xorg-video-glint xserver-xorg-video-i128
7939 xserver-xorg-video-i740 xserver-xorg-video-mach64
7940 xserver-xorg-video-mga xserver-xorg-video-neomagic
7941 xserver-xorg-video-nouveau xserver-xorg-video-nv
7942 xserver-xorg-video-r128 xserver-xorg-video-radeon
7943 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
7944 xserver-xorg-video-s3 xserver-xorg-video-s3virge
7945 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
7946 xserver-xorg-video-sis xserver-xorg-video-sisusb
7947 xserver-xorg-video-tdfx xserver-xorg-video-tga
7948 xserver-xorg-video-trident xserver-xorg-video-tseng
7949 xserver-xorg-video-vesa xserver-xorg-video-vmware
7950 xserver-xorg-video-voodoo
7951 &lt;/p&gt;&lt;/blockquote&gt;
7952
7953 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
7954
7955 &lt;blockquote&gt;&lt;p&gt;
7956 deskbar-applet xserver-xorg xserver-xorg-core
7957 xserver-xorg-input-wacom xserver-xorg-video-intel
7958 xserver-xorg-video-openchrome
7959 &lt;/p&gt;&lt;/blockquote&gt;
7960
7961 &lt;p&gt;I was told on IRC that the xorg-xserver package was
7962 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
7963 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
7964 No idea when it hits Squeeze, but when it does I hope it will reduce
7965 the difference somewhat.
7966 </description>
7967 </item>
7968
7969 <item>
7970 <title>LUMA, a very nice LDAP GUI</title>
7971 <link>http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
7972 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
7973 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
7974 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
7975 directory in Debian Edu, and in the process I started to miss a GUI
7976 tool to browse the LDAP tree. The only one I was able to find in
7977 Debian/Squeeze and Lenny is
7978 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
7979 be a great tool to get a overview of the current LDAP directory
7980 populated by default in Skolelinux. Thanks to it, I have been able to
7981 find empty and obsolete subtrees, misplaced objects and duplicate
7982 objects. It will be installed by default in Debian/Squeeze. If you
7983 are working with LDAP, give it a go. :)&lt;/p&gt;
7984
7985 &lt;p&gt;I did notice one problem with it I have not had time to report to
7986 the BTS yet. There is no .desktop file in the package, so the tool do
7987 not show up in the Gnome and KDE menus, but only deep down in in the
7988 Debian submenu in KDE. I hope that can be fixed before Squeeze is
7989 released.&lt;/p&gt;
7990
7991 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
7992 like to move objects and remove subtrees directly in the GUI, but have
7993 not found a way to do that with LUMA yet. So in the mean time, I use
7994 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
7995
7996 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
7997 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
7998
7999 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
8000 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
8001 useful GUI alternative. It seem like a good tool, but is unmaintained
8002 in Debian and got a RC bug keeping it out of Squeeze. Unless that
8003 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
8004 </description>
8005 </item>
8006
8007 <item>
8008 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
8009 <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>
8010 <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>
8011 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
8012 <description>&lt;p&gt;A while back, I
8013 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
8014 about the fact&lt;/a&gt; that it is not possible with the provided schemas
8015 for storing DNS and DHCP information in LDAP to combine the two sets
8016 of information into one LDAP object representing a computer.&lt;/p&gt;
8017
8018 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
8019 the dhcpHost object class auxiliary, to allow it to be combined with
8020 the dNSDomain object class, and thus forming one object for one
8021 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
8022
8023 &lt;p&gt;If I understand this correctly, it is not safe to do this change
8024 without also changing the assigned number for the object class, and I
8025 do not know enough about LDAP schema design to do that properly for
8026 Debian Edu.&lt;/p&gt;
8027
8028 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
8029 the
8030 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
8031 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
8032 available today from IETF.&lt;/p&gt;
8033
8034 &lt;pre&gt;
8035 --- dhcp.schema (revision 65192)
8036 +++ dhcp.schema (working copy)
8037 @@ -376,7 +376,7 @@
8038 objectclass ( 2.16.840.1.113719.1.203.6.6
8039 NAME &#39;dhcpHost&#39;
8040 DESC &#39;This represents information about a particular client&#39;
8041 - SUP top
8042 + SUP top AUXILIARY
8043 MUST cn
8044 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
8045 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
8046 &lt;/pre&gt;
8047
8048 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
8049 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
8050 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
8051
8052 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
8053 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
8054 </description>
8055 </item>
8056
8057 <item>
8058 <title>Calling tasksel like the installer, while still getting useful output</title>
8059 <link>http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
8060 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
8061 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
8062 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
8063 installs packages during the normal debian-installer run. Until now,
8064 I have ended up letting tasksel do the work, with the annoying problem
8065 of not getting any feedback at all when something fails (like a
8066 conffile question from dpkg or a download that fails), using code like
8067 this:
8068
8069 &lt;blockquote&gt;&lt;pre&gt;
8070 export DEBIAN_FRONTEND=noninteractive
8071 tasksel --new-install
8072 &lt;/pre&gt;&lt;/blockquote&gt;
8073
8074 This would invoke tasksel, let its automatic task selection pick the
8075 tasks to install, and continue to install the requested tasks without
8076 any output what so ever.
8077
8078 Recently I revisited this problem while working on the automatic
8079 package upgrade testing, because tasksel would some times hang without
8080 any useful feedback, and I want to see what is going on when it
8081 happen. Then it occured to me, I can parse the output from tasksel
8082 when asked to run in test mode, and use that aptitude command line
8083 printed by tasksel then to simulate the tasksel run. I ended up using
8084 code like this:
8085
8086 &lt;blockquote&gt;&lt;pre&gt;
8087 export DEBIAN_FRONTEND=noninteractive
8088 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
8089 $cmd
8090 &lt;/pre&gt;&lt;/blockquote&gt;
8091
8092 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
8093 --without-recommends -o APT::Install-Recommends=no -y install
8094 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
8095 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
8096 laptop task and all packages with priority standard , required and
8097 important, just like tasksel would have done it during
8098 installation.&lt;/p&gt;
8099
8100 &lt;p&gt;A better approach is probably to extend tasksel to be able to
8101 install packages without using debconf-apt-progress, for use cases
8102 like this.&lt;/p&gt;
8103 </description>
8104 </item>
8105
8106 <item>
8107 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
8108 <link>http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
8109 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
8110 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
8111 <description>&lt;p&gt;My
8112 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
8113 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
8114 finally made the upgrade logs available from
8115 &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;.
8116 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
8117 apt and aptitude, and found their differences interesting. This time
8118 I will only focus on their removal plans.&lt;/p&gt;
8119
8120 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
8121 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
8122 surprising part is that it want to remove xorg and all
8123 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
8124 sure why. When asking aptitude to do the same, it want to remove 129
8125 packages, but most of them are library packages I suspect are no
8126 longer needed. Both of them want to remove bluetooth packages, which
8127 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
8128
8129 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
8130 which seem like a bad idea and xorg the same way as with Gnome. Asking
8131 aptitude for the same, it wants to remove 192 packages, none which are
8132 too surprising.&lt;/p&gt;
8133
8134 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
8135 and avoided, and perhaps others as well. Here are the complete list
8136 of planned removals. The complete logs is available from the URL
8137 above. Note if you want to repeat these tests, that the upgrade test
8138 for kde+apt-get hung in the tasksel setup because of dpkg asking
8139 conffile questions. No idea why. I worked around it by using
8140 &#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
8141 continue.&lt;/p&gt;
8142
8143 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
8144 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
8145 gnome-desktop-environment gnome-network-admin gtkhtml3.14
8146 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
8147 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
8148 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
8149 serpentine swfdec-mozilla update-manager xorg xserver-xorg
8150 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8151 xserver-xorg-input-kbd xserver-xorg-input-mouse
8152 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8153 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8154 xserver-xorg-video-ati xserver-xorg-video-chips
8155 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8156 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8157 xserver-xorg-video-glint xserver-xorg-video-i128
8158 xserver-xorg-video-i740 xserver-xorg-video-imstt
8159 xserver-xorg-video-intel xserver-xorg-video-mach64
8160 xserver-xorg-video-mga xserver-xorg-video-neomagic
8161 xserver-xorg-video-nsc xserver-xorg-video-nv
8162 xserver-xorg-video-openchrome xserver-xorg-video-r128
8163 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8164 xserver-xorg-video-rendition xserver-xorg-video-s3
8165 xserver-xorg-video-s3virge xserver-xorg-video-savage
8166 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8167 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8168 xserver-xorg-video-tga xserver-xorg-video-trident
8169 xserver-xorg-video-tseng xserver-xorg-video-v4l
8170 xserver-xorg-video-vesa xserver-xorg-video-vga
8171 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
8172 xulrunner-1.9-gnome-support&lt;/p&gt;
8173
8174 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
8175
8176 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
8177 djvulibre-desktop finger gnome-app-install gnome-mount
8178 gnome-network-admin gnome-spell gnome-vfs-obexftp
8179 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
8180 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
8181 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
8182 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
8183 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
8184 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
8185 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
8186 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
8187 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
8188 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
8189 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
8190 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
8191 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
8192 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
8193 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
8194 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
8195 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
8196 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
8197 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
8198 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
8199 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
8200 openoffice.org-writer2latex openssl-blacklist p7zip
8201 python-4suite-xml python-eggtrayicon python-gnome2-desktop
8202 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
8203 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
8204 swfdec-mozilla totem-gstreamer update-manager wodim
8205 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8206 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8207 zip&lt;/p&gt;
8208
8209 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
8210
8211 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
8212 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
8213 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
8214 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
8215 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
8216 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
8217 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
8218 xserver-xorg-input-kbd xserver-xorg-input-mouse
8219 xserver-xorg-input-synaptics xserver-xorg-input-wacom
8220 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
8221 xserver-xorg-video-ati xserver-xorg-video-chips
8222 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
8223 xserver-xorg-video-dummy xserver-xorg-video-fbdev
8224 xserver-xorg-video-glint xserver-xorg-video-i128
8225 xserver-xorg-video-i740 xserver-xorg-video-imstt
8226 xserver-xorg-video-intel xserver-xorg-video-mach64
8227 xserver-xorg-video-mga xserver-xorg-video-neomagic
8228 xserver-xorg-video-nsc xserver-xorg-video-nv
8229 xserver-xorg-video-openchrome xserver-xorg-video-r128
8230 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
8231 xserver-xorg-video-rendition xserver-xorg-video-s3
8232 xserver-xorg-video-s3virge xserver-xorg-video-savage
8233 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
8234 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
8235 xserver-xorg-video-tga xserver-xorg-video-trident
8236 xserver-xorg-video-tseng xserver-xorg-video-v4l
8237 xserver-xorg-video-vesa xserver-xorg-video-vga
8238 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
8239
8240 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
8241 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
8242 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
8243 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
8244 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
8245 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
8246 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
8247 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
8248 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
8249 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
8250 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
8251 kghostview khelpcenter khexedit kiconedit kitchensync klatin
8252 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
8253 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
8254 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
8255 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
8256 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
8257 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
8258 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
8259 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
8260 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
8261 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
8262 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
8263 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
8264 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
8265 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
8266 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
8267 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
8268 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
8269 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
8270 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
8271 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
8272 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
8273 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
8274 texlive-common texlive-doc-base texlive-fonts-recommended
8275 xserver-xorg-video-cyrix xserver-xorg-video-imstt
8276 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
8277 xulrunner-1.9&lt;/p&gt;
8278
8279 </description>
8280 </item>
8281
8282 <item>
8283 <title>Automatic upgrade testing from Lenny to Squeeze</title>
8284 <link>http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
8285 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
8286 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
8287 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
8288 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
8289 have been discovered and reported in the process
8290 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
8291 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
8292 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
8293 kdebase-workspace-data), and to get a more regular testing going on, I
8294 am working on a script to automate the test.&lt;/p&gt;
8295
8296 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
8297 Gnome or KDE desktop installation inside the chroot before upgrading
8298 it. To ensure no services are started in the chroot, a policy-rc.d
8299 script is inserted. To make sure tasksel believe it is to install a
8300 desktop on a laptop, the tasksel tests are replaced in the chroot
8301 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
8302
8303 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
8304 currently always fail because udev refuses to upgrade with the kernel
8305 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
8306 is created. The bug report
8307 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
8308 this problem do not trigger in a chroot, but I touch the file anyway
8309 to make sure the upgrade go well. Testing on virtual and real
8310 hardware have failed me because of udev so far, and creating this file
8311 do the trick in such settings anyway. This is a
8312 &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
8313 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
8314 maintainer because he lack the resources to rewrite udev to keep
8315 working with old kernels or something like that. I really wish the
8316 udev upstream would keep udev backwards compatible, to avoid such
8317 upgrade problem, but given that they fail to do so, I guess
8318 documenting the way out of this mess is the best option we got for
8319 Debian Squeeze.&lt;/p&gt;
8320
8321 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
8322 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
8323 trick:&lt;/p&gt;
8324
8325 &lt;blockquote&gt;&lt;pre&gt;
8326 #!/bin/sh
8327 set -ex
8328
8329 if [ &quot;$1&quot; ] ; then
8330 desktop=$1
8331 else
8332 desktop=gnome
8333 fi
8334
8335 from=lenny
8336 to=squeeze
8337
8338 exec &amp;lt; /dev/null
8339 unset LANG
8340 mirror=http://ftp.skolelinux.org/debian
8341 tmpdir=chroot-$from-upgrade-$to-$desktop
8342 fuser -mv .
8343 debootstrap $from $tmpdir $mirror
8344 chroot $tmpdir aptitude update
8345 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
8346 #!/bin/sh
8347 exit 101
8348 EOF
8349 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
8350 exit_cleanup() {
8351 umount $tmpdir/proc
8352 }
8353 mount -t proc proc $tmpdir/proc
8354 # Make sure proc is unmounted also on failure
8355 trap exit_cleanup EXIT INT
8356
8357 chroot $tmpdir aptitude -y install debconf-utils
8358
8359 # Make sure tasksel autoselection trigger. It need the test scripts
8360 # to return the correct answers.
8361 echo tasksel tasksel/desktop multiselect $desktop | \
8362 chroot $tmpdir debconf-set-selections
8363
8364 # Include the desktop and laptop task
8365 for test in desktop laptop ; do
8366 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
8367 #!/bin/sh
8368 exit 2
8369 EOF
8370 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
8371 done
8372
8373 DEBIAN_FRONTEND=noninteractive
8374 DEBIAN_PRIORITY=critical
8375 export DEBIAN_FRONTEND DEBIAN_PRIORITY
8376 chroot $tmpdir tasksel --new-install
8377
8378 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
8379 chroot $tmpdir aptitude update
8380 touch $tmpdir/etc/udev/kernel-upgrade
8381 chroot $tmpdir aptitude -y dist-upgrade
8382 fuser -mv
8383 &lt;/pre&gt;&lt;/blockquote&gt;
8384
8385 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
8386 with aptitude, but I have not had time to look at how they behave
8387 differently so far. I hope to get a cron job running to do the test
8388 regularly and post the result on the web. The Gnome upgrade currently
8389 work, while the KDE upgrade fail because of the bug in
8390 kdebase-workspace-data&lt;/p&gt;
8391
8392 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
8393 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
8394 post, so I will refrain from trying. I can report that for Gnome,
8395 aptitude report 760 packages upgraded, 448 newly installed, 129 to
8396 remove and 1 not upgraded and 1024MB need to be downloaded while for
8397 KDE the same numbers are 702 packages upgraded, 507 newly installed,
8398 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
8399
8400 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
8401 is able to migrate to dependency based boot sequencing and parallel
8402 booting without a hitch. Was unsure if there were still bugs with
8403 packages failing to clean up their obsolete init.d script during
8404 upgrades, and no such problem seem to affect the Gnome desktop+laptop
8405 packages.&lt;/p&gt;
8406 </description>
8407 </item>
8408
8409 <item>
8410 <title>Upstart or sysvinit - as init.d scripts see it</title>
8411 <link>http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
8412 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
8413 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
8414 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
8415 scripts to migrate (some of) their operations to upstart job while
8416 keeping the init.d for hurd and kfreebsd. The packages with such
8417 needs will need a way to get their init.d scripts to behave
8418 differently when used with sysvinit and with upstart. Because of
8419 this, I had a look at the environment variables set when a init.d
8420 script is running under upstart, and when it is not.&lt;/p&gt;
8421
8422 &lt;p&gt;With upstart, I notice these environment variables are set when a
8423 script is started from rcS.d/ (ignoring some irrelevant ones like
8424 COLUMNS):&lt;/p&gt;
8425
8426 &lt;blockquote&gt;&lt;pre&gt;
8427 DEFAULT_RUNLEVEL=2
8428 previous=N
8429 PREVLEVEL=
8430 RUNLEVEL=
8431 runlevel=S
8432 UPSTART_EVENTS=startup
8433 UPSTART_INSTANCE=
8434 UPSTART_JOB=rc-sysinit
8435 &lt;/pre&gt;&lt;/blockquote&gt;
8436
8437 &lt;p&gt;With sysvinit, these environment variables are set for the same
8438 script.&lt;/p&gt;
8439
8440 &lt;blockquote&gt;&lt;pre&gt;
8441 INIT_VERSION=sysvinit-2.88
8442 previous=N
8443 PREVLEVEL=N
8444 RUNLEVEL=S
8445 runlevel=S
8446 &lt;/pre&gt;&lt;/blockquote&gt;
8447
8448 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
8449 sysvinit are not set by upstart. Not sure if it is intentional or not
8450 to not be compatible with sysvinit in this regard.&lt;/p&gt;
8451
8452 &lt;p&gt;For scripts needing to behave differently when upstart is used,
8453 looking for the UPSTART_JOB environment variable seem to be a good
8454 choice.&lt;/p&gt;
8455 </description>
8456 </item>
8457
8458 <item>
8459 <title>A manual for standards wars...</title>
8460 <link>http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
8461 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
8462 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
8463 <description>&lt;p&gt;Via the
8464 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
8465 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
8466 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
8467 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
8468 following the standards wars of today.&lt;/p&gt;
8469 </description>
8470 </item>
8471
8472 <item>
8473 <title>Sitesummary tip: Listing computer hardware models used at site</title>
8474 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
8475 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
8476 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
8477 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
8478 to get a list of the machine types in use thanks to the DMI
8479 information extracted from each machine. The script to do so is
8480 included in the sitesummary package, and here is example output from
8481 the Skolelinux build servers:&lt;/p&gt;
8482
8483 &lt;blockquote&gt;&lt;pre&gt;
8484 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
8485 vendor count
8486 Dell Computer Corporation 1
8487 PowerEdge 1750 1
8488 IBM 1
8489 eserver xSeries 345 -[8670M1X]- 1
8490 Intel 2
8491 [no-dmi-info] 3
8492 maintainer:~#
8493 &lt;/pre&gt;&lt;/blockquote&gt;
8494
8495 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
8496 provided in each machine. Here there are Intel machines without model
8497 information listed with Intel as vendor and no model, and virtual Xen
8498 machines listed as [no-dmi-info]. One can add -l as a command line
8499 option to list the individual machines.&lt;/p&gt;
8500
8501 &lt;p&gt;A larger list is
8502 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
8503 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
8504 provide the basic sitesummary report publicly. In their report there
8505 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
8506 their machines, and as sitesummary is available in both distributions,
8507 it is trivial to get all of them to report to the same central
8508 collector.&lt;/p&gt;
8509 </description>
8510 </item>
8511
8512 <item>
8513 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
8514 <link>http://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
8515 <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>
8516 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
8517 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
8518 start at boot when an NVidia video card is used is handled. The
8519 problem seem to be that the nvidia X.org driver uses a long time to
8520 initialize, and this duration is longer than kdm is configured to
8521 wait.&lt;/p&gt;
8522
8523 &lt;p&gt;I came across two bugs related to this issue,
8524 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
8525 against initscripts and passed on to nvidia-glx when it became obvious
8526 that the nvidia drivers were involved, and
8527 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
8528 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
8529
8530 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
8531 problem nvidia video card owners experience and make sure the Debian
8532 distribution work out of the box for these users. The nvidia driver
8533 maintainers expect kdm to be set up to wait longer, while kdm expect
8534 the nvidia driver maintainers to fix the driver to start faster, and
8535 while they wait for each other I guess the users end up switching to a
8536 distribution that work for them. I have no idea what the solution is,
8537 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
8538
8539 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
8540 </description>
8541 </item>
8542
8543 <item>
8544 <title>Parallellized boot seem to hold up well in Debian/testing</title>
8545 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
8546 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
8547 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
8548 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
8549 The feature seem to hold up pretty well, but three fairly serious
8550 issues are known and should be solved:
8551
8552 &lt;p&gt;&lt;ul&gt;
8553
8554 &lt;li&gt;The wicd package seen to
8555 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
8556 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
8557 parallel booting is enabled. No idea why, but the wicd maintainer
8558 seem to be on the case.&lt;/li&gt;
8559
8560 &lt;li&gt;The nvidia X driver seem to
8561 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
8562 triggered more easily when parallel booting is in effect. The
8563 maintainer is on the case.&lt;/li&gt;
8564
8565 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
8566 sequencing (the shutdown is broken) when old file-rc users
8567 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
8568 sysv-rc. One way to solve it would be for file-rc to create
8569 /etc/init.d/.legacy-bootordering, and another is to try to make
8570 sysv-rc more robust. Will investigate some more and probably upload a
8571 workaround in sysv-rc to help those trying to move from file-rc to
8572 sysv-rc get a working shutdown.&lt;/li&gt;
8573
8574 &lt;/ul&gt;&lt;/p&gt;
8575
8576 &lt;p&gt;All in all not many surprising issues, and all of them seem
8577 solvable before Squeeze is released. In addition to these there are
8578 some packages with bugs in their dependencies and run level settings,
8579 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
8580
8581 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8582 the BTS, please usertag the report to get it to show up at
8583 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8584 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8585
8586 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
8587 </description>
8588 </item>
8589
8590 <item>
8591 <title>More flexible firmware handling in debian-installer</title>
8592 <link>http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
8593 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
8594 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
8595 <description>&lt;p&gt;After a long break from debian-installer development, I finally
8596 found time today to return to the project. Having to spend less time
8597 working dependency based boot in debian, as it is almost complete now,
8598 definitely helped freeing some time.&lt;/p&gt;
8599
8600 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
8601 include some firmware packages on the Debian Edu CDs, those needed to
8602 get disk and network controllers working. Without having these
8603 firmware packages available during installation, it is impossible to
8604 install Debian Edu on the given machine, and because our target group
8605 are non-technical people, asking them to provide firmware packages on
8606 an external medium is a support pain. Initially, I expected it to be
8607 enough to include the firmware packages on the CD to get
8608 debian-installer to find and use them. This proved to be wrong.
8609 Next, I hoped it was enough to symlink the relevant firmware packages
8610 to some useful location on the CD (tried /cdrom/ and
8611 /cdrom/firmware/). This also proved to not work, and at this point I
8612 found time to look at the debian-installer code to figure out what was
8613 going to work.&lt;/p&gt;
8614
8615 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
8616 look revealed that it would only look for firmware packages outside
8617 the installation media, so the CD was never checked for firmware
8618 packages. It would only check USB sticks, floppies and other
8619 &quot;external&quot; media devices. Today I changed it to also look in the
8620 /cdrom/firmware/ directory on the mounted CD or DVD, which should
8621 solve the problem I ran into with Debian edu. I also changed it to
8622 look in /firmware/, to make sure the installer also find firmware
8623 provided in the initrd when booting the installer via PXE, to allow us
8624 to provide the same feature in the PXE setup included in Debian
8625 Edu.&lt;/p&gt;
8626
8627 &lt;p&gt;To make sure firmware deb packages with a license questions are not
8628 activated without asking if the license is accepted, I extended
8629 hw-detect to look for preinst scripts in the firmware packages, and
8630 run these before activating the firmware during installation. The
8631 license question is asked using debconf in the preinst, so this should
8632 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
8633
8634 &lt;p&gt;If you want to discuss the details of these features, please
8635 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
8636 </description>
8637 </item>
8638
8639 <item>
8640 <title>Parallellized boot is now the default in Debian/unstable</title>
8641 <link>http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
8642 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
8643 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
8644 <description>&lt;p&gt;Since this evening, parallel booting is the default in
8645 Debian/unstable for machines using dependency based boot sequencing.
8646 Apparently the testing of concurrent booting has been wider than
8647 expected, if I am to believe the
8648 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8649 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
8650 with the feature this weekend, to give us some time to detect any
8651 remaining problems before Squeeze is frozen. If serious problems are
8652 detected, it is simple to change the default back to sequential boot.
8653 The upload of the new sysvinit package also activate a new upstream
8654 version.&lt;/p&gt;
8655
8656 More information about
8657 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8658 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
8659 currently possible to disable parallel booting when one run into
8660 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
8661
8662 &lt;blockquote&gt;&lt;pre&gt;
8663 CONCURRENCY=none
8664 &lt;/pre&gt;&lt;/blockquote&gt;
8665
8666 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8667 the BTS, please usertag the report to get it to show up at
8668 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8669 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8670 </description>
8671 </item>
8672
8673 <item>
8674 <title>Sitesummary tip: Listing MAC address of all clients</title>
8675 <link>http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
8676 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
8677 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
8678 <description>&lt;p&gt;In the recent Debian Edu versions, the
8679 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
8680 system&lt;/a&gt; is used to keep track of the machines in the school
8681 network. Each machine will automatically report its status to the
8682 central server after boot and once per night. The network setup is
8683 also reported, and using this information it is possible to get the
8684 MAC address of all network interfaces in the machines. This is useful
8685 to update the DHCP configuration.&lt;/p&gt;
8686
8687 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
8688 ist all MAC addresses of all machines reporting to sitesummary. Run
8689 this on the collector host:&lt;/p&gt;
8690
8691 &lt;blockquote&gt;&lt;pre&gt;
8692 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
8693 &lt;/pre&gt;&lt;/blockquote&gt;
8694
8695 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
8696 line per machine and with space between the MAC addresses.&lt;/p&gt;
8697
8698 &lt;p&gt;To allow system administrators easier job at adding static DHCP
8699 addresses for hosts, it would be possible to extend this to fetch
8700 machine information from sitesummary and update the DHCP and DNS
8701 tables in LDAP using this information. Such tool is unfortunately not
8702 written yet.&lt;/p&gt;
8703 </description>
8704 </item>
8705
8706 <item>
8707 <title>systemd, an interesting alternative to upstart</title>
8708 <link>http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
8709 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
8710 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
8711 <description>&lt;p&gt;The last few days a new boot system called
8712 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
8713 has been
8714 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
8715
8716 to the free software world. I have not yet had time to play around
8717 with it, but it seem to be a very interesting alternative to
8718 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
8719 a good alternative for Debian when we are able to switch to an event
8720 based boot system. Tollef is
8721 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
8722 systemd into Debian, and I look forward to seeing how well it work. I
8723 like the fact that systemd handles init.d scripts with dependency
8724 information natively, allowing them to run in parallel where upstart
8725 at the moment do not.&lt;/p&gt;
8726
8727 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
8728 platform support. It only work on recent Linux kernels, and also need
8729 some new kernel features enabled to function properly. This means
8730 kFreeBSD and Hurd ports of Debian will need a port or a different boot
8731 system. Not sure how that will be handled if systemd proves to be the
8732 way forward.&lt;/p&gt;
8733
8734 &lt;p&gt;In the mean time, based on the
8735 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
8736 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
8737 decided to enable full parallel booting as the default in Debian as
8738 soon as possible (probably this weekend or early next week), to see if
8739 there are any remaining serious bugs in the init.d dependencies. A
8740 new version of the sysvinit package implementing this change is
8741 already in experimental. If all go well, Squeeze will be released
8742 with parallel booting enabled by default.&lt;/p&gt;
8743 </description>
8744 </item>
8745
8746 <item>
8747 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
8748 <link>http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
8749 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
8750 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
8751 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
8752 complete, so complete that it is actually possible to run all the
8753 init.d scripts in parallell based on these dependencies. If you want
8754 to test your Squeeze system, make sure
8755 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8756 based boot sequencing&lt;/a&gt; is enabled, and add this line to
8757 /etc/default/rcS:&lt;/p&gt;
8758
8759 &lt;blockquote&gt;&lt;pre&gt;
8760 CONCURRENCY=makefile
8761 &lt;/pre&gt;&lt;/blockquote&gt;
8762
8763 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
8764 scripts in parallel using the dependency information stored in
8765 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
8766 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
8767 to try to start the kdm and gdm scripts as early as possible, and will
8768 start the facilities required by kdm or gdm as early as possible to
8769 make this happen.&lt;/p&gt;
8770
8771 &lt;p&gt;Give it a try, and see if you like the result. If some services
8772 fail to start properly, it is most likely because they have incomplete
8773 init.d script dependencies in their startup script (or some of their
8774 dependent scripts have incomplete dependencies). Report bugs and get
8775 the package maintainers to fix it. :)&lt;/p&gt;
8776
8777 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
8778 manage to get the init.d script dependencies complete and correct. I
8779 expect we will get there in Squeeze+1, if we get manage to test and
8780 fix the remaining issues.&lt;/p&gt;
8781
8782 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
8783 the BTS, please usertag the report to get it to show up at
8784 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
8785 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
8786 </description>
8787 </item>
8788
8789 <item>
8790 <title>Debian has switched to dependency based boot sequencing</title>
8791 <link>http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
8792 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
8793 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
8794 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
8795 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
8796 have been migrated to using dependency based boot sequencing. This
8797 conclude work me and others have been doing for the last three days.
8798 It feels great to see this finally part of the default Debian
8799 installation. Now we just need to weed out the last few problems that
8800 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
8801
8802 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
8803 fixing the more fundamental problem of handing the event based
8804 non-predictable kernel in the early boot.&lt;/p&gt;
8805 </description>
8806 </item>
8807
8808 <item>
8809 <title>Taking over sysvinit development</title>
8810 <link>http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
8811 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
8812 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
8813 <description>&lt;p&gt;After several years of frustration with the lack of activity from
8814 the existing sysvinit upstream developer, I decided a few weeks ago to
8815 take over the package and become the new upstream. The number of
8816 patches to track for the Debian package was becoming a burden, and the
8817 lack of synchronization between the distribution made it hard to keep
8818 the package up to date.&lt;/p&gt;
8819
8820 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
8821 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
8822 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
8823 and Fedora), based on the patches currently in use in these
8824 distributions. We Debian maintainers plan to move to this tarball as
8825 the new upstream as soon as we find time to do the merge. Since the
8826 new tarball was created, we agreed with Werner at SuSe to make a new
8827 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
8828 development there. The project is registered and currently waiting
8829 for approval by the Savannah administrators, and as soon as it is
8830 approved, we will import the old versions from svn and continue
8831 working on the future release.&lt;/p&gt;
8832
8833 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
8834 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
8835 </description>
8836 </item>
8837
8838 <item>
8839 <title>Debian boots quicker and quicker</title>
8840 <link>http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
8841 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
8842 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
8843 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
8844 people involved in the boot system on Debian and Ubuntu, to see if we
8845 could find more ways to speed up the boot system. This was an Ubuntu
8846 funded
8847 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
8848 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
8849 of boot systems, and ways to handle the increasing number of boot
8850 issues introduced by the Linux kernel becoming more and more
8851 asynchronous and event base. The Ubuntu approach using udev and
8852 upstart might be a good way forward. Time will show.&lt;/p&gt;
8853
8854 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
8855 process in Debian. All of these should be applied to get a quick
8856 boot:&lt;/p&gt;
8857
8858 &lt;ul&gt;
8859
8860 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
8861
8862 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
8863 clock is in UTC.&lt;/li&gt;
8864
8865 &lt;li&gt;Install and activate the insserv package to enable
8866 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
8867 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
8868
8869 &lt;/ul&gt;
8870
8871 These points are based on the Google summer of code work done by
8872 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
8873 Villegas&lt;/a&gt;.
8874
8875 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
8876 unstable yesterday. When we tested it, we were able to cut 6 seconds
8877 from the boot sequence. It depend on very correct dependency
8878 declaration in all init.d scripts, so I expect us to find edge cases
8879 where the dependences in some scripts are slightly wrong when we start
8880 using this.&lt;/p&gt;
8881
8882 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
8883 introduced by Raphael Geissert today, one that could affect the
8884 startup speed as well. Instead of starting some scripts concurrently
8885 from rcS.d/ and another set of scripts from rc2.d/, it would be
8886 possible to run a of them in the same process. A quick way to test
8887 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
8888 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
8889 </description>
8890 </item>
8891
8892 <item>
8893 <title>BSAs påstander om piratkopiering møter motstand</title>
8894 <link>http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
8895 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
8896 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
8897 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
8898 programvareselskapene som Microsoft og Apple, publisert en rapport der
8899 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
8900 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
8901 dager siden kom
8902 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
8903 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
8904 dagene. Et spesielt interessant kommentar fra Sverige,
8905 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
8906 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
8907
8908 &lt;blockquote&gt;
8909 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
8910 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
8911 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
8912 exakta&quot;, säger BSAs Sverigechef John Hugosson.
8913 &lt;/blockquote&gt;
8914
8915 &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
8916 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
8917 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
8918 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
8919 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
8920
8921 &lt;p&gt;Fant lenkene via &lt;a
8922 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
8923 på Slashdot&lt;/a&gt;.&lt;/p&gt;
8924 </description>
8925 </item>
8926
8927 <item>
8928 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
8929 <link>http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
8930 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
8931 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
8932 <description>&lt;p&gt;Kom over
8933 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
8934 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
8935 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
8936 jobber til daglig. En rask opptelling forteller meg at vi har 490
8937 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
8938 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
8939 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
8940 </description>
8941 </item>
8942
8943 <item>
8944 <title>Kryptert harddisk - naturligvis</title>
8945 <link>http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
8946 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
8947 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
8948 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
8949 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
8950 når en tar tap av arbeidstid, fortrolige dokumenter,
8951 personopplysninger og alt annet det innebærer. Det er ingen tvil om
8952 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
8953 til at jeg har kryptert harddisken på både kontormaskinen og min
8954 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
8955 komme på avveie, den første informasjon relatert til jobben min ved
8956 Universitetet i Oslo, og den andre relatert til blant annet
8957 foreningsarbeide. Kryptering av diskene gjør at det er lite
8958 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
8959 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
8960 og en reboot vil gjøre at de ber om passord før de vil starte opp.
8961 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
8962 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
8963 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
8964 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
8965 det er gjort slik jeg gjør det er minimale, og gevinstene er
8966 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
8967 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
8968
8969 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
8970 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
8971 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
8972 er for min del høyere enn gevinsten. Jeg tror oddsene for at
8973 f.eks. etteretningsorganisasjoner har glede av å titte på mine
8974 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
8975 gjøre det vanskeligere for angripere med kompetanse og ressurser er
8976 betydelige.&lt;/p&gt;
8977 </description>
8978 </item>
8979
8980 <item>
8981 <title>Two projects that have improved the quality of free software a lot</title>
8982 <link>http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
8983 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
8984 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
8985 <description>&lt;p&gt;There are two software projects that have had huge influence on the
8986 quality of free software, and I wanted to mention both in case someone
8987 do not yet know them.&lt;/p&gt;
8988
8989 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
8990 tool to detect and expose errors in the memory handling of programs.
8991 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
8992 and it will report any problems on stdout. It is even better if the
8993 program include debug information. With debug information, it is able
8994 to report the source file name and line number where the problem
8995 occurs. It can report things like &#39;reading past memory block in file
8996 X line N, the memory block was allocated in file Y, line M&#39;, and
8997 &#39;using uninitialised value in control logic&#39;. This tool has made it
8998 trivial to investigate reproducible crash bugs in programs, and have
8999 reduced the number of this kind of bugs in free software a lot.
9000
9001 &lt;p&gt;The second one is
9002 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
9003 a source code checker. It is able to process the source of a program
9004 and find problems in the logic without running the program. It
9005 started out as the Stanford Checker and became well known when it was
9006 used to find bugs in the Linux kernel. It is now a commercial tool
9007 and the company behind it is running
9008 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
9009 free software community, where a lot of free software projects get
9010 their source checked for free. Several thousand defects have been
9011 found and fixed so far. It can find errors like &#39;lock L taken in file
9012 X line N is never released if exiting in line M&#39;, or &#39;the code in file
9013 Y lines O to P can never be executed&#39;. The projects included in the
9014 community service project have managed to get rid of a lot of
9015 reliability problems thanks to Coverity.&lt;/p&gt;
9016
9017 &lt;p&gt;I believe tools like this, that are able to automatically find
9018 errors in the source, are vital to improve the quality of software and
9019 make sure we can get rid of the crashing and failing software we are
9020 surrounded by today.&lt;/p&gt;
9021 </description>
9022 </item>
9023
9024 <item>
9025 <title>No patch is not better than a useless patch</title>
9026 <link>http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
9027 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
9028 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
9029 <description>&lt;p&gt;Julien Blache
9030 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
9031 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
9032 patch allow one to discuss a concrete and proposed solution, and also
9033 prove that the issue at hand is important enough for someone to spent
9034 time on fixing it. No patch do not provide any of these positive
9035 properties.&lt;/p&gt;
9036 </description>
9037 </item>
9038
9039 <item>
9040 <title>Standardize on protocols and formats, not vendors and applications</title>
9041 <link>http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
9042 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
9043 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
9044 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
9045 very good one to form a long lived computer infrastructure. It is the
9046 simple one, lost by many in todays computer industry: Standardize on
9047 open network protocols and open exchange/storage formats, not applications.
9048 Applications come and go, while protocols and files tend to stay, and
9049 thus one want to make it easy to change application and vendor, while
9050 avoiding conversion costs and locking users to a specific platform or
9051 application.&lt;/p&gt;
9052
9053 &lt;p&gt;This approach make it possible to replace the client applications
9054 independently of the server applications. One can even allow users to
9055 use several different applications as long as they handle the selected
9056 protocol and format. In the normal case, only one client application
9057 is recommended and users only get help if they choose to use this
9058 application, but those that want to deviate from the easy path are not
9059 blocked from doing so.&lt;/p&gt;
9060
9061 &lt;p&gt;It also allow us to replace the server side without forcing the
9062 users to replace their applications, and thus allow us to select the
9063 best server implementation at any moment, when scale and resouce
9064 requirements change.&lt;/p&gt;
9065
9066 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
9067 open formats, but I would never recommend standardizing on a single
9068 application that do not use open network protocol or open formats.&lt;/p&gt;
9069 </description>
9070 </item>
9071
9072 <item>
9073 <title>Returning from Skolelinux developer gathering</title>
9074 <link>http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
9075 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
9076 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
9077 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
9078 Edu/Skolelinux development gathering. I got a bit done tuning the
9079 desktop, and looked into the dynamic service location protocol
9080 implementation avahi. It look like it could be useful for us. Almost
9081 30 people participated, and I believe it was a great environment to
9082 get to know the Skolelinux system. Walter Bender, involved in the
9083 development of the Sugar educational platform, presented his stuff and
9084 also helped me improve my OLPC installation. He also showed me that
9085 his Turtle Art application can be used in standalone mode, and we
9086 agreed that I would help getting it packaged for Debian. As a
9087 standalone application it would be great for Debian Edu. We also
9088 tried to get the video conferencing working with two OLPCs, but that
9089 proved to be too hard for us. The application seem to need more work
9090 before it is ready for me. I look forward to getting home and relax
9091 now. :)&lt;/p&gt;
9092 </description>
9093 </item>
9094
9095 <item>
9096 <title>Time for new LDAP schemas replacing RFC 2307?</title>
9097 <link>http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
9098 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
9099 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
9100 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
9101 optimal. There is RFC 2307 documenting one way to store NIS maps in
9102 LDAP, and a modified version of this normally called RFC 2307bis, with
9103 some modifications to be compatible with Active Directory. The RFC
9104 specification handle the content of a lot of system databases, but do
9105 not handle DNS zones and DHCP configuration.&lt;/p&gt;
9106
9107 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
9108 we would like to store information about users, SMB clients/hosts,
9109 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
9110 and LTSP configuration in LDAP. These objects have a lot in common,
9111 but with the current LDAP schemas it is not possible to have one
9112 object per entity. For example, one need to have at least three LDAP
9113 objects for a given computer, one with the SMB related stuff, one with
9114 DNS information and another with DHCP information. The schemas
9115 provided for DNS and DHCP are impossible to combine into one LDAP
9116 object. In addition, it is impossible to implement quick queries for
9117 netgroup membership, because of the way NIS triples are implemented.
9118 It just do not scale. I believe it is time for a few RFC
9119 specifications to cleam up this mess.&lt;/p&gt;
9120
9121 &lt;p&gt;I would like to have one LDAP object representing each computer in
9122 the network, and this object can then keep the SMB (ie host key), DHCP
9123 (mac address/name) and DNS (name/IP address) settings in one place.
9124 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
9125
9126 &lt;p&gt;I would also like to have a quick way to map from a user or
9127 computer and to the net group this user or computer is a member.&lt;/p&gt;
9128
9129 &lt;p&gt;Active Directory have done a better job than unix heads like myself
9130 in this regard, and the unix side need to catch up. Time to start a
9131 new IETF work group?&lt;/p&gt;
9132 </description>
9133 </item>
9134
9135 <item>
9136 <title>Endelig er Debian Lenny gitt ut</title>
9137 <link>http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
9138 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
9139 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
9140 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
9141 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
9142 Et langt steg videre for Debian-prosjektet, og en rekke nye
9143 programpakker blir nå tilgjengelig for de av oss som bruker den
9144 stabile utgaven av Debian. Neste steg er nå å få
9145 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
9146 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
9147 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
9148 slippes løs på skolene. Takk til alle debian-utviklerne som har
9149 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
9150 bootsekvens tilgjengelig i stabil utgave, vha pakken
9151 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
9152 </description>
9153 </item>
9154
9155 <item>
9156 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
9157 <link>http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
9158 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
9159 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
9160 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
9161 Oslo. Most of Saturday was used for the general assemly for the
9162 member organization, but the rest of the weekend I used to tune the
9163 LTSP installation. LTSP now work out of the box on the 10-network.
9164 Acer Aspire One proved to be a very nice thin client, with both
9165 screen, mouse and keybard in a small box. Was working on getting the
9166 diskless workstation setup configured out of the box, but did not
9167 finish it before the weekend was up.&lt;/p&gt;
9168
9169 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
9170 the Brazilian group, so that will have to wait for the next
9171 development gathering. Would love to have the Debian Edu installer
9172 automatically detect and configure a multiseat setup when it find one
9173 of these cards.&lt;/p&gt;
9174 </description>
9175 </item>
9176
9177 <item>
9178 <title>The sorry state of multimedia browser plugins in Debian</title>
9179 <link>http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
9180 <guid isPermaLink="true">http://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
9181 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
9182 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
9183 plugins available in Debian Lenny, to see which one we should use by
9184 default in Debian Edu. We need an embedded video playing plugin with
9185 control buttons to pause or stop the video, and capable of streaming
9186 all the multimedia content available on the web. The test results and
9187 notes are available on
9188 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
9189 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
9190 fill this need. My personal video player favorite, VLC, has a really
9191 bad plugin which fail on a lot of the test pages. A lot of the MIME
9192 types I would expect to work with any free software player (like
9193 video/ogg), just do not work. And simple formats like the
9194 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
9195 totem and vlc plugins. I hope the situation will improve soon. No
9196 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
9197
9198 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
9199 be the only one fitting our needs. :/&lt;/p&gt;
9200 </description>
9201 </item>
9202
9203 </channel>
9204 </rss>