]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
fb91d30d1bc512c167b992e8a477ec40870936d8
[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>https://people.skolelinux.org/pere/blog/</link>
7
8
9 <item>
10 <title>Managing and using ONVIF IP cameras with Linux</title>
11 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</link>
12 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html</guid>
13 <pubDate>Wed, 19 Oct 2022 12:30:00 +0200</pubDate>
14 <description>&lt;p&gt;Recently I have been looking at how to control and collect data
15 from a handful IP cameras using Linux. I both wanted to change their
16 settings and to make their imagery available via a free software
17 service under my control. Here is a summary of the tools I found.&lt;/p&gt;
18
19 &lt;p&gt;First I had to identify the cameras and their protocols. As far as
20 I could tell, they were using some SOAP looking protocol and their
21 internal web server seem to only work with Microsoft Internet Explorer
22 with some proprietary binary plugin, which in these days of course is
23 a security disaster and also made it impossible for me to use the
24 camera web interface. Luckily I discovered that the SOAP looking
25 protocol is actually following &lt;a href=&quot;https://www.onvif.org/&quot;&gt;the
26 ONVIF specification&lt;/a&gt;, which seem to be supported by a lot of IP
27 cameras these days.&lt;/p&gt;
28
29 &lt;p&gt;Once the protocol was identified, I was able to find what appear to
30 be the most popular way to configure ONVIF cameras, the free software
31 Windows tool named
32 &lt;a href=&quot;https://sourceforge.net/projects/onvifdm/&quot;&gt;ONVIF Device
33 Manager&lt;/a&gt;. Lacking any other options at the time, I tried
34 unsuccessfully to get it running using Wine, but was missing a dotnet
35 40 library and I found no way around it to run it on Linux.&lt;/p&gt;
36
37 &lt;p&gt;The next tool I found to configure the cameras were a non-free Linux Qt
38 client &lt;a href=&quot;https://www.lingodigit.com/onvif_nvcdemo.html&quot;&gt;ONVIF
39 Device Tool&lt;/a&gt;. I did not like its terms of use, so did not spend
40 much time on it.&lt;/p&gt;
41
42 &lt;p&gt;To collect the video and make it available in a web interface, I
43 found the Zoneminder tool in Debian. A recent version was able to
44 automatically detect and configure ONVIF devices, so I could use it to
45 set up motion detection in and collection of the camera output. I had
46 initial problems getting the ONVIF autodetection to work, as both
47 Firefox and Chromium &lt;a href=&quot;https://bugs.debian.org/1001188&quot;&gt;refused
48 the inter-tab communication&lt;/a&gt; being used by the Zoneminder web
49 pages, but managed to get konqueror to work. Apparently the &quot;Enhanced
50 Tracking Protection&quot; in Firefox cause the problem. I ended up
51 upgrading to the Bookworm edition of Zoneminder in the process to try
52 to fix the issue, and believe the problem might be solved now.&lt;/p&gt;
53
54 &lt;p&gt;In the process I came across the nice Linux GUI tool
55 &lt;a href=&quot;https://gitlab.com/caspermeijn/onvifviewer/&quot;&gt;ONVIF Viewer&lt;/a&gt;
56 allowing me to preview the camera output and validate the login
57 passwords required. Sadly its author has grown tired of maintaining
58 the software, so it might not see any future updates. Which is sad,
59 as the viewer is sightly unstable and the picture tend to lock up.
60 Note, this lockup might be due to limitations in the cameras and not
61 the viewer implementation. I suspect the camera is only able to
62 provide pictures to one client at the time, and the Zoneminder feed
63 might interfere with the GUI viewer. I have
64 &lt;a href=&quot;https://bugs.debian.org/1000820&quot;&gt;asked for the tool to be
65 included in Debian&lt;/a&gt;.&lt;/p&gt;
66
67 &lt;p&gt;Finally, I found what appear to be very nice Linux free software
68 replacement for the Windows tool, named
69 &lt;a href=&quot;https://github.com/sr99622/libonvif/&quot;&gt;libonvif&lt;/a&gt;. It
70 provide a C library to talk to ONVIF devices as well as a command line
71 and GUI tool using the library. Using the GUI tool I was able to change
72 the admin passwords and update other settings of the cameras. I have
73 &lt;a href=&quot;https://bugs.debian.org/1021980&quot;&gt;asked for the package to be
74 included in Debian&lt;/a&gt;.&lt;/p&gt;
75
76 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
77 activities, please send Bitcoin donations to my address
78 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
79
80
81 </description>
82 </item>
83
84 <item>
85 <title>Time to translate the Bullseye edition of the Debian Administrator&#39;s Handbook</title>
86 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</link>
87 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</guid>
88 <pubDate>Mon, 12 Sep 2022 15:45:00 +0200</pubDate>
89 <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2020-10-20-debian-handbook-nb-testprint.jpeg&quot; width=&quot;60%&quot;/&gt;&lt;/p&gt;
90
91 &lt;p&gt;(The picture is of the previous edition.)&lt;/p&gt;
92
93 &lt;p&gt;Almost two years after the previous Norwegian Bokmål translation of
94 the &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
95 Handbook&lt;/a&gt;&quot; was published, a new edition is finally being prepared. The
96 english text is updated, and it is time to start working on the
97 translations. Around 37 percent of the strings have been updated, one
98 way or another, and the translations starting from a complete Debian Buster
99 edition now need to bring their translation up from 63% to 100%. The
100 complete book is licensed using a Creative Commons license, and has
101 been published in several languages over the years. The translations
102 are done by volunteers to bring Linux in their native tongue. The
103 last time I checked, it complete text was available in English,
104 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
105 In addition, work has been started for Arabic (Morocco), Catalan,
106 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
107 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
108 Romanian, Russian, Swedish, Turkish and Vietnamese.&lt;/p&gt;
109
110 &lt;p&gt;The translation is conducted on
111 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
112 hosted weblate project page&lt;/a&gt;. Prospective translators are
113 recommeded to subscribe to
114 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
115 translators mailing list&lt;/a&gt; and should also check out
116 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
117 contributors&lt;/a&gt;.&lt;/p&gt;
118
119 &lt;p&gt;I am one of the Norwegian Bokmål translators of this book, and we
120 have just started. Your contribution is most welcome.&lt;/p&gt;
121
122 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
123 activities, please send Bitcoin donations to my address
124 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
125 </description>
126 </item>
127
128 <item>
129 <title>Automatic LinuxCNC servo PID tuning?</title>
130 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</link>
131 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</guid>
132 <pubDate>Sat, 16 Jul 2022 22:30:00 +0200</pubDate>
133 <description>&lt;p&gt;While working on a CNC with servo motors controlled by the
134 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;
135 &lt;a href=&quot;https://en.wikipedia.org/wiki/PID_controller&quot;&gt;PID
136 controller&lt;/a&gt;, I recently had to learn how to tune the collection of values
137 that control such mathematical machinery that a PID controller is. It
138 proved to be a lot harder than I hoped, and I still have not succeeded
139 in getting the Z PID controller to successfully defy gravity, nor X
140 and Y to move accurately and reliably. But while climbing up this
141 rather steep learning curve, I discovered that some motor control
142 systems are able to tune their PID controllers. I got the impression
143 from the documentation that LinuxCNC were not. This proved to be not
144 true&lt;/p&gt;
145
146 &lt;p&gt;The LinuxCNC
147 &lt;a href=&quot;http://linuxcnc.org/docs/html/man/man9/pid.9.html&quot;&gt;pid
148 component&lt;/a&gt; is the recommended PID controller to use. It uses eight
149 constants &lt;tt&gt;Pgain&lt;/tt&gt;, &lt;tt&gt;Igain&lt;/tt&gt;, &lt;tt&gt;Dgain&lt;/tt&gt;,
150 &lt;tt&gt;bias&lt;/tt&gt;, &lt;tt&gt;FF0&lt;/tt&gt;, &lt;tt&gt;FF1&lt;/tt&gt;, &lt;tt&gt;FF2&lt;/tt&gt; and
151 &lt;tt&gt;FF3&lt;/tt&gt; to calculate the output value based on current and wanted
152 state, and all of these need to have a sensible value for the
153 controller to behave properly. Note, there are even more values
154 involved, theser are just the most important ones. In my case I need
155 the X, Y and Z axes to follow the requested path with little error.
156 This has proved quite a challenge for someone who have never tuned a
157 PID controller before, but there is at least some help to be found.
158
159 &lt;p&gt;I discovered that included in LinuxCNC was this old PID component
160 at_pid claiming to have auto tuning capabilities. Sadly it had been
161 neglected since 2011, and could not be used as a plug in replacement
162 for the default pid component. One would have to rewriting the
163 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
164 to quickly test auto tuning to see if it did a better job than me at
165 figuring out good P, I and D values to use.&lt;/p&gt;
166
167 &lt;p&gt;I decided to have a look if the situation could be improved. This
168 involved trying to understand the code and history of the pid and
169 at_pid components. Apparently they had a common ancestor, as code
170 structure, comments and variable names were quite close to each other.
171 Sadly this was not reflected in the git history, making it hard to
172 figure out what really happened. My guess is that the author of
173 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c&quot;&gt;at_pid.c&lt;/a&gt;
174 took a version of
175 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c&quot;&gt;pid.c&lt;/a&gt;,
176 rewrote it to follow the structure he wished pid.c to have, then added
177 support for auto tuning and finally got it included into the LinuxCNC
178 repository. The restructuring and lack of early history made it
179 harder to figure out which part of the code were relevant to the auto
180 tuning, and which part of the code needed to be updated to work the
181 same way as the current pid.c implementation. I started by trying to
182 isolate relevant changes in pid.c, and applying them to at_pid.c. My
183 aim was to make sure the at_pid component could replace the pid
184 component with a simple change in the HAL setup loadrt line, without
185 having to &quot;rewire&quot; the rest of the HAL configuration. After a few
186 hours following this approach, I had learned quite a lot about the
187 code structure of both components, while concluding I was heading down
188 the wrong rabbit hole, and should get back to the surface and find a
189 different path.&lt;/p&gt;
190
191 &lt;p&gt;For the second attempt, I decided to throw away all the PID control
192 related part of the original at_pid.c, and instead isolate and lift
193 the auto tuning part of the code and inject it into a copy of pid.c.
194 This ensured compatibility with the current pid component, while
195 adding auto tuning as a run time option. To make it easier to identify
196 the relevant parts in the future, I wrapped all the auto tuning code
197 with &#39;#ifdef AUTO_TUNER&#39;. The end result behave just like the current
198 pid component by default, as that part of the code is identical. The
199 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/1820&quot;&gt;end result
200 entered the LinuxCNC master branch&lt;/a&gt; a few days ago.&lt;/p&gt;
201
202 &lt;p&gt;To enable auto tuning, one need to set a few HAL pins in the PID
203 component. The most important ones are &lt;tt&gt;tune-effort&lt;/tt&gt;,
204 &lt;tt&gt;tune-mode&lt;/tt&gt; and &lt;tt&gt;tune-start&lt;/tt&gt;. But lets take a step
205 back, and see what the auto tuning code will do. I do not know the
206 mathematical foundation of the at_pid algorithm, but from observation
207 I can tell that the algorithm will, when enabled, produce a square
208 wave pattern centered around the &lt;tt&gt;bias&lt;/tt&gt; value on the output pin
209 of the PID controller. This can be seen using the HAL Scope provided
210 by LinuxCNC. In my case, this is translated into voltage (+-10V) sent
211 to the motor controller, which in turn is translated into motor speed.
212 So at_pid will ask the motor to move the axis back and forth. The
213 number of cycles in the pattern is controlled by the
214 &lt;tt&gt;tune-cycles&lt;/tt&gt; pin, and the extremes of the wave pattern is
215 controlled by the &lt;tt&gt;tune-effort&lt;/tt&gt; pin. Of course, trying to
216 change the direction of a physical object instantly (as in going
217 directly from a positive voltage to the equivalent negative voltage)
218 do not change velocity instantly, and it take some time for the object
219 to slow down and move in the opposite direction. This result in a
220 more smooth movement wave form, as the axis in question were vibrating
221 back and forth. When the axis reached the target speed in the
222 opposing direction, the auto tuner change direction again. After
223 several of these changes, the average time delay between the &#39;peaks&#39;
224 and &#39;valleys&#39; of this movement graph is then used to calculate
225 proposed values for Pgain, Igain and Dgain, and insert them into the
226 HAL model to use by the pid controller. The auto tuned settings are
227 not great, but htye work a lot better than the values I had been able
228 to cook up on my own, at least for the horizontal X and Y axis. But I
229 had to use very small &lt;tt&gt;tune-effort&lt;tt&gt; values, as my motor
230 controllers error out if the voltage change too quickly. I&#39;ve been
231 less lucky with the Z axis, which is moving a heavy object up and
232 down, and seem to confuse the algorithm. The Z axis movement became a
233 lot better when I introduced a &lt;tt&gt;bias&lt;/tt&gt; value to counter the
234 gravitational drag, but I will have to work a lot more on the Z axis
235 PID values.&lt;/p&gt;
236
237 &lt;p&gt;Armed with this knowledge, it is time to look at how to do the
238 tuning. Lets say the HAL configuration in question load the PID
239 component for X, Y and Z like this:&lt;/p&gt;
240
241 &lt;blockquote&gt;&lt;pre&gt;
242 loadrt pid names=pid.x,pid.y,pid.z
243 &lt;/pre&gt;&lt;/blockquote&gt;
244
245 &lt;p&gt;Armed with the new and improved at_pid component, the new line will
246 look like this:&lt;/p&gt;
247
248 &lt;blockquote&gt;&lt;pre&gt;
249 loadrt at_pid names=pid.x,pid.y,pid.z
250 &lt;/pre&gt;&lt;/blockquote&gt;
251
252 &lt;p&gt;The rest of the HAL setup can stay the same. This work because the
253 components are referenced by name. If the component had used count=3
254 instead, all use of pid.# had to be changed to at_pid.#.&lt;/p&gt;
255
256 &lt;p&gt;To start tuning the X axis, move the axis to the middle of its
257 range, to make sure it do not hit anything when it start moving back
258 and forth. Next, set the &lt;tt&gt;tune-effort&lt;/tt&gt; to a low number in the
259 output range. I used 0.1 as my initial value. Next, assign 1 to the
260 &lt;tt&gt;tune-mode&lt;/tt&gt; value. Note, this will disable the pid controlling
261 part and feed 0 to the output pin, which in my case initially caused a
262 lot of drift. In my case it proved to be a good idea with X and Y to
263 tune the motor driver to make sure 0 voltage stopped the motor
264 rotation. On the other hand, for the Z axis this proved to be a bad
265 idea, so it will depend on your setup. It might help to set the
266 &lt;tt&gt;bias&lt;/tt&gt; value to a output value that reduce or eliminate the
267 axis drift. Finally, after setting &lt;tt&gt;tune-mode&lt;/tt&gt;, set
268 &lt;tt&gt;tune-start&lt;/tt&gt; to 1 to activate the auto tuning. If all go well,
269 your axis will vibrate for a few seconds and when it is done, new
270 values for Pgain, Igain and Dgain will be active. To test them,
271 change &lt;tt&gt;tune-mode&lt;/tt&gt; back to 0. Note that this might cause the
272 machine to suddenly jerk as it bring the axis back to its commanded
273 position, which it might have drifted away from during tuning. To
274 summarize with some halcmd lines:&lt;/p&gt;
275
276 &lt;blockquote&gt;&lt;pre&gt;
277 setp pid.x.tune-effort 0.1
278 setp pid.x.tune-mode 1
279 setp pid.x.tune-start 1
280 # wait for the tuning to complete
281 setp pid.x.tune-mode 0
282 &lt;/pre&gt;&lt;/blockquote&gt;
283
284 &lt;p&gt;After doing this task quite a few times while trying to figure out
285 how to properly tune the PID controllers on the machine in, I decided
286 to figure out if this process could be automated, and wrote a script
287 to do the entire tuning process from power on. The end result will
288 ensure the machine is powered on and ready to run, home all axis if it
289 is not already done, check that the extra tuning pins are available,
290 move the axis to its mid point, run the auto tuning and re-enable the
291 pid controller when it is done. It can be run several times. Check
292 out the
293 &lt;a href=&quot;https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner&quot;&gt;run-auto-pid-tuner&lt;/a&gt;
294 script on github if you want to learn how it is done.&lt;/p&gt;
295
296 &lt;p&gt;My hope is that this little adventure can inspire someone who know
297 more about motor PID controller tuning can implement even better
298 algorithms for automatic PID tuning in LinuxCNC, making life easier
299 for both me and all the others that want to use LinuxCNC but lack the
300 in depth knowledge needed to tune PID controllers well.&lt;/p&gt;
301
302 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
303 activities, please send Bitcoin donations to my address
304 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
305 </description>
306 </item>
307
308 <item>
309 <title>LinuxCNC translators life just got a bit easier</title>
310 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</link>
311 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</guid>
312 <pubDate>Fri, 3 Jun 2022 21:10:00 +0200</pubDate>
313 <description>&lt;p&gt;Back in oktober last year, when I started looking at the
314 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt; system, I
315 proposed to change the documentation build system make life easier for
316 translators. The original system consisted of independently written
317 documentation files for each language, with no automated way to track
318 changes done in other translations and no help for the translators to
319 know how much was left to translated. By using
320 &lt;a href=&quot;https://po4a.org/&quot;&gt;the po4a system&lt;/a&gt; to generate POT and PO
321 files from the English documentation, this can be improved. A small
322 team of LinuxCNC contributors got together and today our labour
323 finally payed off. Since a few hours ago, it is now possible to
324 translate &lt;a href=&quot;https://hosted.weblate.org/projects/linuxcnc/&quot;&gt;the
325 LinuxCNC documentation on Weblate&lt;/a&gt;, alongside the program itself.&lt;/p&gt;
326
327 &lt;p&gt;The effort to migrate the documentation to use po4a has been both
328 slow and frustrating. I am very happy we finally made it.&lt;/p&gt;
329
330 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
331 activities, please send Bitcoin donations to my address
332 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
333 </description>
334 </item>
335
336 <item>
337 <title>geteltorito make CD firmware upgrades a breeze</title>
338 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</link>
339 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</guid>
340 <pubDate>Wed, 20 Apr 2022 11:50:00 +0200</pubDate>
341 <description>&lt;p&gt;Recently I wanted to upgrade the firmware of my thinkpad, and
342 located the firmware download page from Lenovo (which annoyingly do
343 not allow access via Tor, forcing me to hand them more personal
344 information that I would like). The
345 &lt;a href=&quot;https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso&amp;SearchType=Customer search&amp;searchLocation=Masthead&quot;&gt;download
346 from Lenovo&lt;/a&gt; is a bootable ISO image, which is a bit of a problem
347 when all I got available is a USB memory stick. I tried booting the
348 ISO as a USB stick, but this did not work. But genisoimage came to
349 the rescue.&lt;/p&gt;
350
351 &lt;P&gt;The geteltorito program in
352 &lt;a href=&quot;http://tracker.debian.org/cdrkit&quot;&gt;the genisoimage binary
353 package&lt;/a&gt; is able to convert the bootable ISO image to a bootable
354 USB stick using a simple command line recipe, which I then can write
355 to the most recently inserted USB stick:&lt;/p&gt;
356
357 &lt;blockquote&gt;&lt;pre&gt;
358 geteltorito -o usbstick.img lenovo-firmware.iso
359 sudo dd bs=10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -1)
360 &lt;/pre&gt;&lt;/blockquote&gt;
361
362 &lt;p&gt;This USB stick booted the firmware upgrader just fine, and in a few
363 minutes my machine had the latest and greatest BIOS firmware in place.&lt;/p&gt;
364 </description>
365 </item>
366
367 <item>
368 <title>Run your industrial metal working machine using Debian?</title>
369 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</link>
370 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</guid>
371 <pubDate>Wed, 2 Mar 2022 18:40:00 +0100</pubDate>
372 <description>&lt;p&gt;After many months of hard work by the good people involved in
373 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;, the
374 system was accepted Sunday
375 &lt;a href=&quot;https://tracker.debian.org/pkg/linuxcnc&quot;&gt;into Debian&lt;/a&gt;.
376 Once it was available from Debian, I was surprised to discover from
377 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=linuxcnc&quot;&gt;its
378 popularity-contest numbers&lt;/a&gt; that people have been reporting its use
379 since 2012. &lt;a href=&quot;http://linuxcnc.org/&quot;&gt;Its project site&lt;/a&gt; might
380 be a good place to check out, but sadly is not working when visiting
381 via Tor.&lt;/p&gt;
382
383 &lt;p&gt;But what is LinuxCNC, you are probably wondering? Perhaps a
384 Wikipedia quote is in place?&lt;/p&gt;
385
386 &lt;blockquote&gt;
387 &quot;LinuxCNC is a software system for numerical control of
388 machines such as milling machines, lathes, plasma cutters, routers,
389 cutting machines, robots and hexapods. It can control up to 9 axes or
390 joints of a CNC machine using G-code (RS-274NGC) as input. It has
391 several GUIs suited to specific kinds of usage (touch screen,
392 interactive development).&quot;
393 &lt;/blockquote&gt;
394
395 &lt;p&gt;It can even control 3D printers. And even though the Wikipedia
396 page indicate that it can only work with hard real time kernel
397 features, it can also work with the user space soft real time features
398 provided by the Debian kernel.
399 &lt;a href=&quot;https://github.com/linuxcnc/linuxcnc&quot;&gt;The source code&lt;/a&gt; is
400 available from Github. The last few months I&#39;ve been involved in the
401 translation setup for the program and documentation. Translators are
402 most welcome to
403 &lt;a href=&quot;https://hosted.weblate.org/engage/linuxcnc/&quot;&gt;join the
404 effort&lt;/a&gt; using Weblate.&lt;/p&gt;
405
406 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
407 activities, please send Bitcoin donations to my address
408 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
409 </description>
410 </item>
411
412 <item>
413 <title>Debian still an excellent choice for Lego builders</title>
414 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</link>
415 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</guid>
416 <pubDate>Sun, 24 Oct 2021 07:10:00 +0200</pubDate>
417 <description>&lt;p&gt;The Debian Lego team saw a lot of activity the last few weeks. All
418 the packages under the team umbrella has been updated to fix
419 packaging, lintian issues and BTS reports. In addition, a new and
420 inspiring team member appeared on both the
421 &lt;a href=&quot;https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team&quot;&gt;debian-lego-team
422 Team mailing list&lt;/a&gt; and
423 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC channel
424 #debian-lego&lt;/a&gt;. If you are interested in Lego CAD design and LEGO
425 Mindstorms programming, check out the
426 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;team wiki page&lt;/a&gt; to
427 see what Debian can offer the Lego enthusiast.&lt;/p&gt;
428
429 &lt;p&gt;Patches has been sent upstream, causing new upstream releases, one
430 even the first one in more than ten years, and old upstreams was
431 released with new ones. There are still a lot of work left, and the
432 team welcome more members to help us make sure Debian is the Linux
433 distribution of choice for Lego builders. If you want to contribute,
434 join us in the IRC channel and become part of
435 &lt;a href=&quot;https://salsa.debian.org/debian-lego-team/&quot;&gt;the team on
436 Salsa&lt;/a&gt;.&lt;/p&gt;
437
438 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
439 activities, please send Bitcoin donations to my address
440 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
441 </description>
442 </item>
443
444 <item>
445 <title>Six complete translations of The Debian Administrator&#39;s Handbook for Buster</title>
446 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</link>
447 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</guid>
448 <pubDate>Mon, 5 Jul 2021 19:20:00 +0200</pubDate>
449 <description>&lt;p&gt;I am happy observe that the &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The
450 Debian Administrator&#39;s Handbook&lt;/a&gt; is available in six languages now.
451 I am not sure which one of these are completely proof read, but the
452 complete book is available in these languages:
453
454 &lt;ul&gt;
455
456 &lt;li&gt;English&lt;/li&gt;
457 &lt;li&gt;Norwegian Bokmål&lt;/li&gt;
458 &lt;li&gt;German&lt;/li&gt;
459 &lt;li&gt;Indonesian&lt;/li&gt;
460 &lt;li&gt;Brazil Portuguese&lt;/li&gt;
461 &lt;li&gt;Spanish&lt;/li&gt;
462
463 &lt;/ul&gt;
464
465 &lt;p&gt;This is the list of languages more than 70% complete, in other
466 words with not too much left to do:&lt;/p&gt;
467
468 &lt;ul&gt;
469
470 &lt;li&gt;Chinese (Simplified) - 90%&lt;/li&gt;
471 &lt;li&gt;French - 79%&lt;/li&gt;
472 &lt;li&gt;Italian - 79%&lt;/li&gt;
473 &lt;li&gt;Japanese - 77%&lt;/li&gt;
474 &lt;li&gt;Arabic (Morocco) - 75%&lt;/li&gt;
475 &lt;li&gt;Persian - 71%&lt;/li&gt;
476
477 &lt;/ul&gt;
478
479 &lt;p&gt;I wonder how long it will take to bring these to 100%.&lt;/p&gt;
480
481 &lt;p&gt;Then there is the list of languages about halfway done:&lt;/p&gt;
482
483 &lt;ul&gt;
484
485 &lt;li&gt;Russian - 63%&lt;/li&gt;
486 &lt;li&gt;Swedish - 53%&lt;/li&gt;
487 &lt;li&gt;Chinese (Traditional) - 46%&lt;/li&gt;
488 &lt;li&gt;Catalan - 45%&lt;/li&gt;
489
490 &lt;/ul&gt;
491
492 &lt;p&gt;Several are on to a good start:&lt;/p&gt;
493
494 &lt;ul&gt;
495
496 &lt;li&gt;Dutch - 26%&lt;/li&gt;
497 &lt;li&gt;Vietnamese - 25%&lt;/li&gt;
498 &lt;li&gt;Polish - 23%&lt;/li&gt;
499 &lt;li&gt;Czech - 22%&lt;/li&gt;
500 &lt;li&gt;Turkish - 18%&lt;/li&gt;
501
502 &lt;/ul&gt;
503
504 &lt;p&gt;Finally, there are the ones just getting started:&lt;/p&gt;
505
506 &lt;ul&gt;
507
508 &lt;li&gt;Korean - 4%&lt;/li&gt;
509 &lt;li&gt;Croatian - 2%&lt;/li&gt;
510 &lt;li&gt;Greek - 2%&lt;/li&gt;
511 &lt;li&gt;Danish - 1%&lt;/li&gt;
512 &lt;li&gt;Romanian - 1%&lt;/li&gt;
513
514 &lt;/ul&gt;
515
516 &lt;p&gt;If you want to help provide a Debian instruction book in your own
517 language, visit
518 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/#languages&quot;&gt;Weblate&lt;/a&gt;
519 to contribute to the translations.&lt;/p&gt;
520
521 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
522 activities, please send Bitcoin donations to my address
523 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
524 </description>
525 </item>
526
527 <item>
528 <title>Latest Jami back in Debian Testing, and scriptable using dbus</title>
529 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</link>
530 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</guid>
531 <pubDate>Tue, 12 Jan 2021 17:00:00 +0100</pubDate>
532 <description>&lt;p&gt;After a lot of hard work by its maintainer Alexandre Viau and
533 others, the decentralized communication platform
534 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;
535 (earlier known as Ring), managed to get
536 &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;its latest version&lt;/a&gt;
537 into Debian Testing. Several of its dependencies has caused build and
538 propagation problems, which all seem to be solved now.&lt;/p&gt;
539
540 &lt;p&gt;In addition to the fact that Jami is decentralized, similar to how
541 bittorrent is decentralized, I first of all like how it is not
542 connected to external IDs like phone numbers. This allow me to set up
543 computers to send me notifications using Jami without having to find
544 get a phone number for each computer. Automatic notification via Jami
545 is also made trivial thanks to the provided client side API (as a DBus
546 service). Here is my bourne shell script demonstrating how to let any
547 system send a message to any Jami address. It will create a new
548 identity before sending the message, if no Jami identity exist
549 already:&lt;/p&gt;
550
551 &lt;p&gt;&lt;pre&gt;
552 #!/bin/sh
553 #
554 # Usage: $0 &lt;jami-address&gt; &lt;message&gt;
555 #
556 # Send &lt;message&gt; to &lt;jami-address&gt;, create local jami account if
557 # missing.
558 #
559 # License: GPL v2 or later at your choice
560 # Author: Petter Reinholdtsen
561
562
563 if [ -z &quot;$HOME&quot; ] ; then
564 echo &quot;error: missing \$HOME, required for dbus to work&quot;
565 exit 1
566 fi
567
568 # First, get dbus running if not already running
569 DBUSLAUNCH=/usr/bin/dbus-launch
570 PIDFILE=/run/asterisk/dbus-session.pid
571 if [ -e $PIDFILE ] ; then
572 . $PIDFILE
573 if ! kill -0 $DBUS_SESSION_BUS_PID 2&gt;/dev/null ; then
574 unset DBUS_SESSION_BUS_ADDRESS
575 fi
576 fi
577 if [ -z &quot;$DBUS_SESSION_BUS_ADDRESS&quot; ] &amp;&amp; [ -x &quot;$DBUSLAUNCH&quot; ]; then
578 DBUS_SESSION_BUS_ADDRESS=&quot;unix:path=$HOME/.dbus&quot;
579 dbus-daemon --session --address=&quot;$DBUS_SESSION_BUS_ADDRESS&quot; --nofork --nopidfile --syslog-only &lt; /dev/null &gt; /dev/null 2&gt;&amp;1 3&gt;&amp;1 &amp;
580 DBUS_SESSION_BUS_PID=$!
581 (
582 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
583 echo DBUS_SESSION_BUS_ADDRESS=\&quot;&quot;$DBUS_SESSION_BUS_ADDRESS&quot;\&quot;
584 echo export DBUS_SESSION_BUS_ADDRESS
585 ) &gt; $PIDFILE
586 . $PIDFILE
587 fi &amp;
588
589 dringop() {
590 part=&quot;$1&quot;; shift
591 op=&quot;$1&quot;; shift
592 dbus-send --session \
593 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
594 }
595
596 dringopreply() {
597 part=&quot;$1&quot;; shift
598 op=&quot;$1&quot;; shift
599 dbus-send --session --print-reply \
600 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
601 }
602
603 firstaccount() {
604 dringopreply ConfigurationManager getAccountList | \
605 grep string | awk -F&#39;&quot;&#39; &#39;{print $2}&#39; | head -n 1
606 }
607
608 account=$(firstaccount)
609
610 if [ -z &quot;$account&quot; ] ; then
611 echo &quot;Missing local account, trying to create it&quot;
612 dringop ConfigurationManager addAccount \
613 dict:string:string:&quot;Account.type&quot;,&quot;RING&quot;,&quot;Account.videoEnabled&quot;,&quot;false&quot;
614 account=$(firstaccount)
615 if [ -z &quot;$account&quot; ] ; then
616 echo &quot;unable to create local account&quot;
617 exit 1
618 fi
619 fi
620
621 # Not using dringopreply to ensure $2 can contain spaces
622 dbus-send --print-reply --session \
623 --dest=cx.ring.Ring \
624 /cx/ring/Ring/ConfigurationManager \
625 cx.ring.Ring.ConfigurationManager.sendTextMessage \
626 string:&quot;$account&quot; string:&quot;$1&quot; \
627 dict:string:string:&quot;text/plain&quot;,&quot;$2&quot;
628 &lt;/pre&gt;&lt;/p&gt;
629
630 &lt;p&gt;If you want to check it out yourself, visit the
631 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system project page&lt;/a&gt; to learn
632 more, and install the latest Jami client from Debian Unstable or
633 Testing.&lt;/p&gt;
634
635 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
636 activities, please send Bitcoin donations to my address
637 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
638 </description>
639 </item>
640
641 <item>
642 <title>Buster based Bokmål edition of Debian Administrator&#39;s Handbook</title>
643 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
644 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
645 <pubDate>Tue, 20 Oct 2020 18:35:00 +0200</pubDate>
646 <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2020-10-20-debian-handbook-nb-testprint.jpeg&quot; width=&quot;60%&quot;/&gt;&lt;/p&gt;
647
648 &lt;p&gt;I am happy to report that we finally made it! Norwegian Bokmål
649 became the first translation published on paper of the new Buster
650 based edition of &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
651 Administrator&#39;s Handbook&lt;/a&gt;&quot;. The print proof reading copy arrived
652 some days ago, and it looked good, so now the book is approved for
653 general distribution. This updated paperback edition &lt;a
654 href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available from
655 lulu.com&lt;/a&gt;. The book is also available for download in electronic
656 form as PDF, EPUB and Mobipocket, and can also be
657 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online&lt;/a&gt;.&lt;/p&gt;
658
659 &lt;p&gt;I am very happy to wrap up this Creative Common licensed project,
660 which concludes several months of work by several volunteers. The
661 number of Linux related books published in Norwegian are few, and I
662 really hope this one will gain many readers, as it is packed with deep
663 knowledge on Linux and the Debian ecosystem. The book will be
664 available for various Internet book stores like Amazon and Barnes &amp;
665 Noble soon, but I recommend buying
666 &quot;&lt;a href=&quot;https://www.lulu.com/en/us/shop/roland-mas-and-rapha%C3%ABl-hertzog/h%C3%A5ndbok-for-debian-administratoren/paperback/product-9j7qwq.html&quot;&gt;Håndbok
667 for Debian-administratoren&lt;/a&gt;&quot; directly from the source at Lulu.
668
669 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
670 activities, please send Bitcoin donations to my address
671 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
672 </description>
673 </item>
674
675 <item>
676 <title>Buster update of Norwegian Bokmål edition of Debian Administrator&#39;s Handbook almost done</title>
677 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</link>
678 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</guid>
679 <pubDate>Fri, 11 Sep 2020 09:45:00 +0200</pubDate>
680 <description>&lt;p&gt;Thanks to the good work of several volunteers, the updated edition
681 of the Norwegian translation for
682 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
683 Handbook&lt;/a&gt;&quot; is now almost completed. After many months of proof
684 reading, I consider the proof reading complete enough for us to move
685 to the next step, and have asked for the print version to be prepared
686 and sent of to the print on demand service lulu.com. While it is
687 still not to late if you find any incorrect translations on
688 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
689 hosted Weblate service&lt;/a&gt;, but it will be soon. :) You can check out
690 &lt;a href=&quot; https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;the Buster
691 edition on the web&lt;/a&gt; until the print edition is ready.&lt;/p&gt;
692
693 &lt;p&gt;The book will be for sale on lulu.com and various web book stores,
694 with links available from the web site for the book linked to above.
695 I hope a lot of readers find it useful.&lt;/p&gt;
696
697 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
698 activities, please send Bitcoin donations to my address
699 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
700 </description>
701 </item>
702
703 <item>
704 <title>Working on updated Norwegian Bokmål edition of Debian Administrator&#39;s Handbook</title>
705 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
706 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
707 <pubDate>Sat, 4 Jul 2020 23:55:00 +0200</pubDate>
708 <description>&lt;p&gt;Three years ago, the first Norwegian Bokmål edition of
709 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
710 Handbook&lt;/a&gt;&quot; was published. This was based on Debian Jessie. Now a
711 new and updated version based on Buster is getting ready. Work on the
712 updated Norwegian Bokmål edition has been going on for a few months
713 now, and yesterday, we reached the first mile stone, with 100% of the
714 texts being translated. A lot of proof reading remains, of course,
715 but a major step towards a new edition has been taken.&lt;/p&gt;
716
717 &lt;p&gt;The book is translated by volunteers, and we would love to get some
718 help with the proof reading. The translation uses
719 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
720 hosted Weblate service&lt;/a&gt;, and we welcome everyone to have a look and
721 submit improvements and suggestions. There is also a proof readers
722 PDF available on request, get in touch if you want to help out that
723 way.&lt;/p&gt;
724
725 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
726 activities, please send Bitcoin donations to my address
727 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
728 </description>
729 </item>
730
731 <item>
732 <title>Secure Socket API - a simple and powerful approach for TLS support in software</title>
733 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</link>
734 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</guid>
735 <pubDate>Sat, 6 Jun 2020 12:40:00 +0200</pubDate>
736 <description>&lt;p&gt;As a member of the &lt;a href=&quot;https://www.nuug.no/&quot;&gt;Norwegian Unix
737 User Group&lt;/a&gt;, I have the pleasure of receiving the
738 &lt;a href=&quot;https://www.usenix.org/&quot;&gt;USENIX&lt;/a&gt; magazine
739 &lt;a href=&quot;https://www.usenix.org/publications/login/&quot;&gt;;login:&lt;/a&gt;
740 several times a year. I rarely have time to read all the articles,
741 but try to at least skim through them all as there is a lot of nice
742 knowledge passed on there. I even carry the latest issue with me most
743 of the time to try to get through all the articles when I have a few
744 spare minutes.&lt;/p&gt;
745
746 &lt;p&gt;The other day I came across a nice article titled
747 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/winter2018/oneill&quot;&gt;The
748 Secure Socket API: TLS as an Operating System Service&lt;/a&gt;&quot; with a
749 marvellous idea I hope can make it all the way into the POSIX standard.
750 The idea is as simple as it is powerful. By introducing a new
751 socket() option IPPROTO_TLS to use TLS, and a system wide service to
752 handle setting up TLS connections, one both make it trivial to add TLS
753 support to any program currently using the POSIX socket API, and gain
754 system wide control over certificates, TLS versions and encryption
755 systems used. Instead of doing this:&lt;/p&gt;
756
757 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
758 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
759 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
760
761 &lt;p&gt;the program code would be doing this:&lt;p&gt;
762
763 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
764 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
765 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
766
767 &lt;p&gt;According to the ;login: article, converting a C program to use TLS
768 would normally modify only 5-10 lines in the code, which is amazing
769 when compared to using for example the OpenSSL API.&lt;/p&gt;
770
771 &lt;p&gt;The project has set up the
772 &lt;a href=&quot;https://securesocketapi.org/&quot;&gt;https://securesocketapi.org/&lt;/a&gt;
773 web site to spread the idea, and the code for a kernel module and the
774 associated system daemon is available from two github repositories:
775 &lt;a href=&quot;https://github.com/markoneill/ssa&quot;&gt;ssa&lt;/a&gt; and
776 &lt;a href=&quot;https://github.com/markoneill/ssa-daemon&quot;&gt;ssa-daemon&lt;/a&gt;.
777 Unfortunately there is no explicit license information with the code,
778 so its copyright status is unclear. A
779 &lt;a href=&quot;https://github.com/markoneill/ssa/issues/2&quot;&gt;request to solve
780 this&lt;/a&gt; about it has been unsolved since 2018-08-17.&lt;/p&gt;
781
782 &lt;p&gt;I love the idea of extending socket() to gain TLS support, and
783 understand why it is an advantage to implement this as a kernel module
784 and system wide service daemon, but can not help to think that it
785 would be a lot easier to get projects to move to this way of setting
786 up TLS if it was done with a user space approach where programs
787 wanting to use this API approach could just link with a wrapper
788 library.&lt;/p&gt;
789
790 &lt;p&gt;I recommend you check out this simple and powerful approach to more
791 secure network connections. :)&lt;/p&gt;
792
793 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
794 activities, please send Bitcoin donations to my address
795 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
796 </description>
797 </item>
798
799 <item>
800 <title>Jami as a Zoom client, a trick for password protected rooms...</title>
801 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</link>
802 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</guid>
803 <pubDate>Fri, 8 May 2020 13:30:00 +0200</pubDate>
804 <description>&lt;p&gt;Half a year ago,
805 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html&quot;&gt;I
806 wrote&lt;/a&gt; about &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami communication
807 client&lt;/a&gt;, capable of peer-to-peer encrypted communication. It
808 handle both messages, audio and video. It uses distributed hash
809 tables instead of central infrastructure to connect its users to each
810 other, which in my book is a plus. I mentioned briefly that it could
811 also work as a SIP client, which came in handy when the higher
812 educational sector in Norway started to promote Zoom as its video
813 conferencing solution. I am reluctant to use the official Zoom client
814 software, due to their &lt;a href=&quot;https://zoom.us/terms&quot;&gt;copyright
815 license clauses&lt;/a&gt; prohibiting users to reverse engineer (for example
816 to check the security) and benchmark it, and thus prefer to connect to
817 Zoom meetings with free software clients.&lt;/p&gt;
818
819 &lt;p&gt;Jami worked OK as a SIP client to Zoom as long as there was no
820 password set on the room. The Jami daemon leak memory like crazy
821 (approximately 1 GiB a minute) when I am connected to the video
822 conference, so I had to restart the client every 7-10 minutes, which
823 is not great. I tried to get other SIP Linux clients to work
824 without success, so I decided I would have to live with this wart
825 until someone managed to fix the leak in the dring code base. But
826 another problem showed up once the rooms were password protected. I
827 could not get my dial tone signaling through from Jami to Zoom, and
828 dial tone signaling is used to enter the password when connecting to
829 Zoom. I tried a lot of different permutations with my Jami and
830 Asterisk setup to try to figure out why the signaling did not get
831 through, only to finally discover that the fundamental problem seem to
832 be that Zoom is simply not able to receive dial tone signaling when
833 connecting via SIP. There seem to be nothing wrong with the Jami and
834 Asterisk end, it is simply broken in the Zoom end. I got help from a
835 very skilled VoIP engineer figuring out this last part. And being a
836 very skilled engineer, he was also able to locate a solution for me.
837 Or to be exact, a workaround that solve my initial problem of
838 connecting to password protected Zoom rooms using Jami.&lt;/p&gt;
839
840 &lt;p&gt;So, how do you do this, I am sure you are wondering by now. The
841 trick is already
842 &lt;a href=&quot;https://support.zoom.us/hc/en-us/articles/202405539-H-323-SIP-Room-Connector-Dial-Strings#sip&quot;&gt;documented
843 from Zoom&lt;/a&gt;, and it is to modify the SIP address to include the room
844 password. What is most surprising about this is that the
845 automatically generated email from Zoom with instructions on how to
846 connect via SIP do not mention this. The SIP address to use normally
847 consist of the room ID (a number), an @ character and the IP address
848 of the Zoom SIP gateway. But Zoom understand a lot more than just the
849 room ID in front of the at sign. The format is &quot;&lt;tt&gt;[Meeting
850 ID].[Password].[Layout].[Host Key]&lt;/tt&gt;&quot;, and you can here see how you
851 can both enter password, control the layout (full screen, active
852 presence and gallery) and specify the host key to start the meeting.
853 The full SIP address entered into Jami to provide the password will
854 then look like this (all using made up numbers):&lt;/p&gt;
855
856 &lt;p&gt;&lt;blockquote&gt;
857 &lt;tt&gt;sip:657837644.522827@192.168.169.170&lt;/tt&gt;
858 &lt;/blockquote&gt;&lt;/p&gt;
859
860 &lt;p&gt;Now if only jami would reduce its memory usage, I could even
861 recommend this setup to others. :)&lt;/p&gt;
862
863 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
864 activities, please send Bitcoin donations to my address
865 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
866 </description>
867 </item>
868
869 <item>
870 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software</title>
871 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</link>
872 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</guid>
873 <pubDate>Wed, 29 Apr 2020 13:10:00 +0200</pubDate>
874 <description>&lt;p&gt;The curiosity got the better of me when
875 &lt;a href=&quot;https://developers.slashdot.org/story/20/04/06/1424246/new-jersey-desperately-needs-cobol-programmers&quot;&gt;Slashdot
876 reported&lt;/a&gt; that New Jersey was desperately looking for
877 &lt;a href=&quot;https://en.wikipedia.org/wiki/COBOL&quot;&gt;COBOL&lt;/a&gt; programmers,
878 and a few days later it was reported that
879 &lt;a href=&quot;https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce&quot;&gt;IBM
880 tried to locate COBOL programmers&lt;/a&gt;.&lt;/p&gt;
881
882 &lt;p&gt;I thus decided to have a look at free software alternatives to
883 learn COBOL, and had the pleasure to find
884 &lt;a href=&quot;https://sourceforge.net/projects/open-cobol/&quot;&gt;GnuCOBOL&lt;/a&gt; was
885 already &lt;a href=&quot;https://tracker.debian.org/pkg/gnucobol&quot;&gt;in
886 Debian&lt;/a&gt;. It used to be called Open Cobol, and is a &quot;compiler&quot;
887 transforming COBOL code to C or C++ before giving it to GCC or Visual
888 Studio to build binaries.&lt;/p&gt;
889
890 &lt;p&gt;I managed to get in touch with upstream, and was impressed with the
891 quick response, and also was happy to see a new Debian maintainer
892 taking over when the original one recently asked to be replaced. A
893 new Debian upload was done as recently as yesterday.&lt;/p&gt;
894
895 &lt;p&gt;Using the Debian package, I was able to follow a simple COBOL
896 introduction and make and run simple COBOL programs. It was fun to
897 learn a new programming language. If you want to test for yourself,
898 &lt;a href=&quot;https://en.wikipedia.org/wiki/GnuCOBOL&quot;&gt;the GnuCOBOL Wikipedia
899 page&lt;/a&gt; have a few simple examples to get you startet.&lt;/p&gt;
900
901 &lt;p&gt;As I do not have much experience with COBOL, I do not know how
902 standard compliant it is, but it claim to pass most tests from COBOL
903 test suite, which sound good to me. It is nice to know it is possible
904 to learn COBOL using software without any usage restrictions, and I am
905 very happy such nice free software project as this is available. If
906 you as me is curious about COBOL, check it out.&lt;/p&gt;
907
908 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
909 activities, please send Bitcoin donations to my address
910 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
911 </description>
912 </item>
913
914 <item>
915 <title>Jami/Ring, finally functioning peer to peer communication client</title>
916 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
917 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
918 <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
919 <description>&lt;p&gt;Some years ago, in 2016, I
920 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html&quot;&gt;wrote
921 for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
922 It would provide messaging without any central server coordinating the
923 system and without requiring all users to register a phone number or
924 own a mobile phone. Back then, I could not get it to work, and put it
925 aside until it had seen more development. A few days ago I decided to
926 give it another try, and am happy to report that this time I am able
927 to not only send and receive messages, but also place audio and video
928 calls. But only if UDP is not blocked into your network.&lt;/p&gt;
929
930 &lt;p&gt;The Ring system changed name earlier this year to
931 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;. I
932 tried doing web search for &#39;ring&#39; when I discovered it for the first
933 time, and can only applaud this change as it is impossible to find
934 something called Ring among the noise of other uses of that word. Now
935 you can search for &#39;jami&#39; and this client and
936 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
937 least on duckduckgo.&lt;/p&gt;
938
939 &lt;p&gt;Jami will by default encrypt messages as well as audio and video
940 calls, and try to send them directly between the communicating parties
941 if possible. If this proves impossible (for example if both ends are
942 behind NAT), it will use a central SIP TURN server maintained by the
943 Jami project. Jami can also be a normal SIP client. If the SIP
944 server is unencrypted, the audio and video calls will also be
945 unencrypted. This is as far as I know the only case where Jami will
946 do anything without encryption.&lt;/p&gt;
947
948 &lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
949 Android, iOS, and Android TV. It is included in Debian already. Jami
950 also work for those using F-Droid without any Google connections,
951 while Signal do not.
952 &lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
953 protocol&lt;/a&gt; is described in the Ring project wiki. The system uses a
954 distributed hash table (DHT) system (similar to BitTorrent) running
955 over UDP. On one of the networks I use, I discovered Jami failed to
956 work. I tracked this down to the fact that incoming UDP packages
957 going to ports 1-49999 were blocked, and the DHT would pick a random
958 port and end up in the low range most of the time. After talking to
959 the developers, I solved this by enabling the dhtproxy in the
960 settings, thus using TCP to talk to a central DHT proxy instead of
961
962 peering directly with others. I&#39;ve been told the developers are
963 working on allowing DHT to use TCP to avoid this problem. I also ran
964 into a problem when trying to talk to the version of Ring included in
965 Debian Stable (Stretch). Apparently the protocol changed between
966 beta2 and the current version, making these clients incompatible.
967 Hopefully the protocol will not be made incompatible in the
968 future.&lt;/p&gt;
969
970 &lt;p&gt;It is worth noting that while looking at Jami and its features, I
971 came across another communication platform I have not tested yet. The
972 &lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
973 and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;. It might
974 become the topic of a future blog post.&lt;/p&gt;
975
976 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
977 activities, please send Bitcoin donations to my address
978 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
979 </description>
980 </item>
981
982 <item>
983 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål</title>
984 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</link>
985 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</guid>
986 <pubDate>Wed, 23 Jan 2019 07:50:00 +0100</pubDate>
987 <description>&lt;p&gt;I høst ble jeg inspirert til å bidra til oversettelsen av
988 &lt;a href=&quot;http://unknown-horizons.org/&quot;&gt;strategispillet Unknown
989 Horizons&lt;/a&gt;, og oversatte de nesten 200 strengene i prosjektet til
990 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
991 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
992 nye versjonen kom på nyåret, og ble
993 &lt;a href=&quot;https://tracker.debian.org/pkg/unknown-horizons&quot;&gt;lastet opp i
994 Debian&lt;/a&gt; for noen få dager siden. I går kveld fikk jeg testet det ut, og
995 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
996 måtte justeres, men ikke noe alvorlig. Har oppdatert
997 &lt;a href=&quot;https://hosted.weblate.org/projects/uh/&quot;&gt;oversettelsen på
998 Weblate&lt;/a&gt;, slik at neste utgave vil være enda bedre. :)&lt;/p&gt;
999
1000 &lt;p&gt;Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1001 å spille for oss som liker slikt. :)&lt;/p&gt;
1002
1003 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1004 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1005 til min adresse
1006 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
1007 Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
1008 </description>
1009 </item>
1010
1011 <item>
1012 <title>Debian now got everything you need to program Micro:bit</title>
1013 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</link>
1014 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</guid>
1015 <pubDate>Tue, 22 Jan 2019 17:20:00 +0100</pubDate>
1016 <description>&lt;p&gt;I am amazed and very pleased to discover that since a few days ago,
1017 everything you need to program the &lt;a href=&quot;https://microbit.org/&quot;&gt;BBC
1018 micro:bit&lt;/a&gt; is available from the Debian archive. All this is
1019 thanks to the hard work of Nick Morrott and the Debian python
1020 packaging team. The micro:bit project recommend the mu-editor to
1021 program the microcomputer, as this editor will take care of all the
1022 machinery required to injekt/flash micropython alongside the program
1023 into the micro:bit, as long as the pieces are available.&lt;/p&gt;
1024
1025 &lt;p&gt;There are three main pieces involved. The first to enter Debian
1026 was
1027 &lt;a href=&quot;https://tracker.debian.org/pkg/python-uflash&quot;&gt;python-uflash&lt;/a&gt;,
1028 which was accepted into the archive 2019-01-12. The next one was
1029 &lt;a href=&quot;https://tracker.debian.org/pkg/mu-editor&quot;&gt;mu-editor&lt;/a&gt;, which
1030 showed up 2019-01-13. The final and hardest part to to into the
1031 archive was
1032 &lt;a href=&quot;https://tracker.debian.org/pkg/firmware-microbit-micropython&quot;&gt;firmware-microbit-micropython&lt;/a&gt;,
1033 which needed to get its build system and dependencies into Debian
1034 before it was accepted 2019-01-20. The last one is already in Debian
1035 Unstable and should enter Debian Testing / Buster in three days. This
1036 all allow any user of the micro:bit to get going by simply running
1037 &#39;apt install mu-editor&#39; when using Testing or Unstable, and once
1038 Buster is released as stable, all the users of Debian stable will be
1039 catered for.&lt;/p&gt;
1040
1041 &lt;p&gt;As a minor final touch, I added rules to
1042 &lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the isenkram
1043 package&lt;/a&gt; for recognizing micro:bit and recommend the mu-editor
1044 package. This make sure any user of the isenkram desktop daemon will
1045 get a popup suggesting to install mu-editor then the USB cable from
1046 the micro:bit is inserted for the first time.&lt;/p&gt;
1047
1048 &lt;p&gt;This should make it easier to have fun.&lt;/p&gt;
1049
1050 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1051 activities, please send Bitcoin donations to my address
1052 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1053 </description>
1054 </item>
1055
1056 <item>
1057 <title>Learn to program with Minetest on Debian</title>
1058 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
1059 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
1060 <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
1061 <description>&lt;p&gt;A fun way to learn how to program
1062 &lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
1063 instructions in the book
1064 &quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
1065 with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
1066 who like to play with Minecraft. The book uses a Python library to
1067 talk to a TCP/IP socket with an API accepting build instructions and
1068 providing information about the current players in a Minecraft world.
1069 The TCP/IP API was first created for the Minecraft implementation for
1070 Raspberry Pi, and has since been ported to some server versions of
1071 Minecraft. The book contain recipes for those using Windows, MacOSX
1072 and Raspian. But a little known fact is that you can follow the same
1073 recipes using the free software construction game
1074 &lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;
1075
1076 &lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
1077 Minetest module implementing the same API&lt;/a&gt;, making it possible to
1078 use the Python programs coded to talk to Minecraft with Minetest too.
1079 I
1080 &lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
1081 this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
1082 FTP masters NEW queue, learning to program Python with Minetest on
1083 Debian will be a simple &#39;apt install&#39; away. The Debian package is
1084 maintained as part of the Debian Games team, and
1085 &lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
1086 packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
1087 Salsa.&lt;/p&gt;
1088
1089 &lt;p&gt;You will most likely need to install several of the Minetest
1090 modules in Debian for the examples included with the library to work
1091 well, as there are several blocks used by the example scripts that are
1092 provided via modules in Minetest. Without the required blocks, a
1093 simple stone block is used instead. My initial testing with a analog
1094 clock did not get gold arms as instructed in the python library, but
1095 instead used stone arms.&lt;/p&gt;
1096
1097 &lt;p&gt;I tried to find a way to add the API to the desktop version of
1098 Minecraft, but were unable to find any working recipes. The
1099 &lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
1100 I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
1101 working with a standalone Minecraft server setup. Are there any
1102 options to use with the normal desktop version?&lt;/p&gt;
1103
1104 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1105 activities, please send Bitcoin donations to my address
1106 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1107 </description>
1108 </item>
1109
1110 <item>
1111 <title>Time for an official MIME type for patches?</title>
1112 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
1113 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
1114 <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
1115 <description>&lt;p&gt;As part of my involvement in
1116 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
1117 archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
1118 emails into a test instance of the archive to see how well this would
1119 go. I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
1120 notmuch email database&lt;/a&gt;, all public emails sent to me via
1121 @lists.debian.org, giving me a set of around 216 000 emails to import.
1122 In the process, I had a look at the various attachments included in
1123 these emails, to figure out what to do with attachments, and noticed
1124 that one of the most common attachment formats do not have
1125 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
1126 official MIME type&lt;/a&gt; registered with IANA/IETF. The output from
1127 diff, ie the input for patch, is on the top 10 list of formats
1128 included in these emails. At the moment people seem to use either
1129 text/x-patch or text/x-diff, but neither is officially registered. It
1130 would be better if one official MIME type were registered and used
1131 everywhere.&lt;/p&gt;
1132
1133 &lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
1134 up the topic on
1135 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
1136 media-types mailing list&lt;/a&gt;. If you are interested in discussion
1137 which MIME type to use as the official for patch files, or involved in
1138 making software using a MIME type for patches, perhaps you would like
1139 to join the discussion?&lt;/p&gt;
1140
1141 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1142 activities, please send Bitcoin donations to my address
1143 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1144 </description>
1145 </item>
1146
1147 <item>
1148 <title>Automatic Google Drive sync using grive in Debian</title>
1149 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
1150 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
1151 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
1152 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
1153 rescue the remains, I helped set up automatic sync with Google Drive.
1154 I did not find any sensible Debian package handling this
1155 automatically, so I rebuild the grive2 source from
1156 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
1157 task and added a autostart desktop entry and a small shell script to
1158 run in the background while the user is logged in to do the sync.
1159 Here is a sketch of the setup for future reference.&lt;/p&gt;
1160
1161 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
1162 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
1163 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
1164 to start the sync when the user log in:&lt;/p&gt;
1165
1166 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1167 [Desktop Entry]
1168 Name=Google drive autosync
1169 Type=Application
1170 Exec=/home/user/bin/grive-sync
1171 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1172
1173 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
1174 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
1175
1176 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1177 #!/bin/sh
1178 set -e
1179 cd ~/
1180 cleanup() {
1181 if [ &quot;$syncpid&quot; ] ; then
1182 kill $syncpid
1183 fi
1184 }
1185 trap cleanup EXIT INT QUIT
1186 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
1187 syncpdi=$!
1188 while true; do
1189 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
1190 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
1191 exit 1
1192 fi
1193 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
1194 /usr/lib/grive/grive-sync.sh sync googledrive
1195 fi
1196 sleep 300
1197 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
1198 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1199
1200 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
1201 GNU GPL v2 licensed (or any later version, at your leisure), but I
1202 doubt this code is possible to claim copyright on.&lt;/p&gt;
1203
1204 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1205 activities, please send Bitcoin donations to my address
1206 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1207 </description>
1208 </item>
1209
1210 <item>
1211 <title>Using the Kodi API to play Youtube videos</title>
1212 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
1213 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
1214 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
1215 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
1216 tell it to play a youtube URL I received in a chat, without having to
1217 insert search terms using the on-screen keyboard. After searching the
1218 web for API access to the Youtube plugin and testing a bit, I managed
1219 to find a recipe that worked. If you got a kodi instance with its API
1220 available from http://kodihost/jsonrpc, you can try the following to
1221 have check out a nice cover band.&lt;/p&gt;
1222
1223 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
1224 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
1225 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
1226 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
1227 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1228
1229 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
1230 first argument. It can now handle direct video links, youtube links
1231 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
1232 Chromecast. :)&lt;/p&gt;
1233
1234 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1235 activities, please send Bitcoin donations to my address
1236 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1237 </description>
1238 </item>
1239
1240 <item>
1241 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
1242 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
1243 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
1244 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
1245 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
1246 with my family using a self hosted solution, as it is unacceptable to
1247 place images from my personal life under the control of strangers
1248 working for data hoarders like Google or Dropbox. The last few days I
1249 have drafted an approach that might work out, and I would like to
1250 share it with you. I would like to publish images on a server under
1251 my control, and point some Internet connected display units using some
1252 free and open standard to the images I published. As my primary
1253 language is not limited to ASCII, I need to store metadata using
1254 UTF-8. Many years ago, I hoped to find a digital photo frame capable
1255 of reading a RSS feed with image references (aka using the
1256 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
1257 of such frames. In the end I gave up that approach.&lt;/p&gt;
1258
1259 &lt;p&gt;Some months ago, I discovered that
1260 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
1261 read images from a RSS feed, and used it to set up a screen saver on
1262 my home info screen, showing images from the Daily images feed from
1263 NASA. This proved to work well. More recently I discovered that
1264 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
1265 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
1266 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
1267 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
1268 screen saver capable of reading a RSS feed with images and news. For
1269 fun, I used it this summer to test Kodi on my parents TV by hooking up
1270 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
1271 screen saver showing selected pictures from my selection.&lt;/p&gt;
1272
1273 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
1274 a RSS feed for the Kodi instance. I adjusted my &lt;a
1275 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
1276 /var/www/html/privatepictures/, wrote a small Perl script to extract
1277 title and description metadata from the photo files and generate the
1278 RSS file. I ended up using Perl instead of python, as the
1279 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
1280 tags I ended up using, while python3-exif did not. The relevant EXIF
1281 tags only support ASCII, so I had to find better alternatives. XMP
1282 seem to have the support I need.&lt;/p&gt;
1283
1284 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
1285 use tags that can be easily added/updated using normal free software
1286 photo managing software. I ended up using the tags set using this
1287 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
1288
1289 &lt;blockquote&gt;&lt;pre&gt;
1290 exiftool -headline=&#39;The RSS image title&#39; \
1291 -description=&#39;The RSS image description.&#39; \
1292 -subject+=for-family photo.jpeg
1293 &lt;/pre&gt;&lt;/blockquote&gt;
1294
1295 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
1296 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
1297 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
1298 shared with my family. Images with this keyword set are located and
1299 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
1300
1301 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
1302 suggestions.&lt;/p&gt;
1303
1304 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1305 activities, please send Bitcoin donations to my address
1306 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1307 </description>
1308 </item>
1309
1310 <item>
1311 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
1312 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
1313 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
1314 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
1315 <description>&lt;p&gt;Last night, I wrote
1316 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
1317 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
1318 During the day I received valuable feedback, and thanks to the
1319 suggestions I have been able to rewrite the recipe into a much simpler
1320 approach requiring no setup at all. It is a single script that take
1321 care of it all.&lt;/p&gt;
1322
1323 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
1324 desktop and stream it to Kodi. This fixed the video quality issue I
1325 saw initially. It further removes the need to add a m3u file on the
1326 Kodi machine, as it instead connects to
1327 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
1328 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
1329 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
1330 the script below, run it with the DNS name or IP address of the kodi
1331 server to stream to as the only argument, and watch your screen show
1332 up on the Kodi screen. Note, it depend on multicast on the local
1333 network, so if you need to stream outside the local network, the
1334 script must be modified. Also note, I have no idea if audio work, as
1335 I only care about the picture part.&lt;/p&gt;
1336
1337 &lt;blockquote&gt;&lt;pre&gt;
1338 #!/bin/sh
1339 #
1340 # Stream the Linux desktop view to Kodi. See
1341 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
1342 # for backgorund information.
1343
1344 # Make sure the stream is stopped in Kodi and the gstreamer process is
1345 # killed if something go wrong (for example if curl is unable to find the
1346 # kodi server). Do the same when interrupting this script.
1347 kodicmd() {
1348 host=&quot;$1&quot;
1349 cmd=&quot;$2&quot;
1350 params=&quot;$3&quot;
1351 curl --silent --header &#39;Content-Type: application/json&#39; \
1352 --data-binary &quot;{ \&quot;id\&quot;: 1, \&quot;jsonrpc\&quot;: \&quot;2.0\&quot;, \&quot;method\&quot;: \&quot;$cmd\&quot;, \&quot;params\&quot;: $params }&quot; \
1353 &quot;http://$host/jsonrpc&quot;
1354 }
1355 cleanup() {
1356 if [ -n &quot;$kodihost&quot; ] ; then
1357 # Stop the playing when we end
1358 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
1359 jq .result[].playerid)
1360 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
1361 fi
1362 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
1363 kill &quot;$gstpid&quot;
1364 fi
1365 }
1366 trap cleanup EXIT INT
1367
1368 if [ -n &quot;$1&quot; ]; then
1369 kodihost=$1
1370 shift
1371 else
1372 kodihost=kodi.local
1373 fi
1374
1375 mcast=239.255.0.1
1376 mcastport=1234
1377 mcastttl=1
1378
1379 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
1380 cut -d&quot; &quot; -f2|head -1)
1381 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
1382 videoconvert ! queue2 ! \
1383 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
1384 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
1385 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
1386 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
1387 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
1388 &gt; /dev/null 2&gt;&amp;1 &amp;
1389 gstpid=$!
1390
1391 # Give stream a second to get going
1392 sleep 1
1393
1394 # Ask kodi to start streaming using its JSON-RPC API
1395 kodicmd &quot;$kodihost&quot; Player.Open \
1396 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
1397
1398 # wait for gst to end
1399 wait &quot;$gstpid&quot;
1400 &lt;/pre&gt;&lt;/blockquote&gt;
1401
1402 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
1403
1404 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1405 activities, please send Bitcoin donations to my address
1406 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1407 </description>
1408 </item>
1409
1410 <item>
1411 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
1412 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
1413 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
1414 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
1415 <description>&lt;p&gt;PS: See
1416 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
1417 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
1418
1419 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
1420 my projector connected to Kodi. I sadly had to admit that I had no
1421 idea, as it was a task I never had tried. Since then, I have been
1422 looking for a way to do so, preferable without much extra software to
1423 install on either side. Today I found a way that seem to kind of
1424 work. Not great, but it is a start.&lt;/p&gt;
1425
1426 &lt;p&gt;I had a look at several approaches, for example
1427 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
1428 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
1429 local storage enough to store the stream locally. This is not going
1430 to work well for me, lacking enough free space, and it would
1431 impossible for my friend to get working.&lt;/p&gt;
1432
1433 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
1434 video stream that Kodi could play. Preferably using
1435 broadcast/multicast, to avoid having to change any setup on the Kodi
1436 side when starting such stream. Unfortunately, the only recipe I
1437 could find using multicast used the rtp protocol, and this protocol
1438 seem to not be supported by Kodi.&lt;/p&gt;
1439
1440 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
1441 have to specify the IP address of the streaming machine in both the
1442 sending command and the file on the Kodi server. But it is showing my
1443 desktop, and thus allow us to have a shared look on the big screen at
1444 the programs I work on.&lt;/p&gt;
1445
1446 &lt;p&gt;I did not spend much time investigating codeces. I combined the
1447 rtp and rtsp recipes from
1448 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
1449 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
1450 this working on the desktop/streaming end.&lt;/p&gt;
1451
1452 &lt;blockquote&gt;&lt;pre&gt;
1453 vlc screen:// --sout \
1454 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{dst=projector.local,port=1234,sdp=rtsp://192.168.11.4:8080/test.sdp}&#39;
1455 &lt;/pre&gt;&lt;/blockquote&gt;
1456
1457 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
1458 same IP address:&lt;/p&gt;
1459
1460 &lt;blockquote&gt;&lt;pre&gt;
1461 echo rtsp://192.168.11.4:8080/test.sdp \
1462 &gt; /storage/videos/screenstream.m3u
1463 &lt;/pre&gt;&lt;/blockquote&gt;
1464
1465 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
1466 as I can tell the IP must be hardcoded for this to work. In other
1467 words, if someone elses machine is going to do the steaming, you have
1468 to update screenstream.m3u on the Kodi machine and adjust the vlc
1469 recipe. To get started, locate the file in Kodi and select the m3u
1470 file while the VLC stream is running. The desktop then show up in my
1471 big screen. :)&lt;/p&gt;
1472
1473 &lt;p&gt;When using the same technique to stream a video file with audio,
1474 the audio quality is really bad. No idea if the problem is package
1475 loss or bad parameters for the transcode. I do not know VLC nor Kodi
1476 enough to tell.&lt;/p&gt;
1477
1478 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
1479 succestions and reminded me about an important step. The &quot;screen:&quot;
1480 input source is only available once the vlc-plugin-access-extra
1481 package is installed on Debian. Without it, you will see this error
1482 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
1483 for details.&quot; He further found that it is possible to drop some parts
1484 of the VLC command line to reduce the amount of hardcoded information.
1485 It is also useful to consider using cvlc to avoid having the VLC
1486 window in the desktop view. In sum, this give us this command line on
1487 the source end
1488
1489 &lt;blockquote&gt;&lt;pre&gt;
1490 cvlc screen:// --sout \
1491 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
1492 &lt;/pre&gt;&lt;/blockquote&gt;
1493
1494 &lt;p&gt;and this on the Kodi end&lt;p&gt;
1495
1496 &lt;blockquote&gt;&lt;pre&gt;
1497 echo rtsp://192.168.11.4:8080/ \
1498 &gt; /storage/videos/screenstream.m3u
1499 &lt;/pre&gt;&lt;/blockquote&gt;
1500
1501 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
1502 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
1503 audio quality, so I guess the issue is in the input or transcoding
1504 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
1505 parameters to use more bandwidth, but it did not make a
1506 difference.&lt;/p&gt;
1507
1508 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
1509 gstreamer instead of VLC, and this proved to work great! He also
1510 provided me with the trick to get Kodi to use a multicast stream as
1511 its source. By using this monstrous oneliner, I can stream my desktop
1512 with good video quality in reasonable framerate to the 239.255.0.1
1513 multicast address on port 1234:
1514
1515 &lt;blockquote&gt;&lt;pre&gt;
1516 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
1517 videoconvert ! queue2 ! \
1518 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
1519 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
1520 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
1521 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
1522 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
1523 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
1524 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
1525 &lt;/pre&gt;&lt;/blockquote&gt;
1526
1527 &lt;p&gt;and this on the Kodi end&lt;p&gt;
1528
1529 &lt;blockquote&gt;&lt;pre&gt;
1530 echo udp://@239.255.0.1:1234 \
1531 &gt; /storage/videos/screenstream.m3u
1532 &lt;/pre&gt;&lt;/blockquote&gt;
1533
1534 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
1535 pick the one you need. This approach will of course lead to trouble
1536 if more than one source uses the same multicast port and address.
1537 Note the ttl-mc=1 setting, which limit the multicast packages to the
1538 local network. If the value is increased, your screen will be
1539 broadcasted further, one network &quot;hop&quot; for each increase (read up on
1540 multicast to learn more. :)!&lt;/p&gt;
1541
1542 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
1543 could use this VLC command to stream to the same multicast address.
1544 The image quality is way better than the rtsp approach, but gstreamer
1545 seem to be doing a better job.&lt;/p&gt;
1546
1547 &lt;blockquote&gt;&lt;pre&gt;
1548 cvlc screen:// --sout &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{mux=ts,dst=239.255.0.1,port=1234,sdp=sap}&#39;
1549 &lt;/pre&gt;&lt;/blockquote&gt;
1550
1551 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1552 activities, please send Bitcoin donations to my address
1553 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1554 </description>
1555 </item>
1556
1557 <item>
1558 <title>What is the most supported MIME type in Debian in 2018?</title>
1559 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
1560 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
1561 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
1562 <description>&lt;p&gt;Five years ago,
1563 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
1564 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
1565 analysing the desktop files in all packages in the archive. Since
1566 then, the DEP-11 AppStream system has been put into production, making
1567 the task a lot easier. This made me want to repeat the measurement,
1568 to see how much things changed. Here are the new numbers, for
1569 unstable only this time:
1570
1571 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
1572
1573 &lt;pre&gt;
1574 count MIME type
1575 ----- -----------------------
1576 56 image/jpeg
1577 55 image/png
1578 49 image/tiff
1579 48 image/gif
1580 39 image/bmp
1581 38 text/plain
1582 37 audio/mpeg
1583 34 application/ogg
1584 33 audio/x-flac
1585 32 audio/x-mp3
1586 30 audio/x-wav
1587 30 audio/x-vorbis+ogg
1588 29 image/x-portable-pixmap
1589 27 inode/directory
1590 27 image/x-portable-bitmap
1591 27 audio/x-mpeg
1592 26 application/x-ogg
1593 25 audio/x-mpegurl
1594 25 audio/ogg
1595 24 text/html
1596 &lt;/pre&gt;
1597
1598 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
1599 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
1600 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
1601
1602 &lt;p&gt;It is interesting to see how image formats have passed text/plain
1603 as the most announced supported MIME type. These days, thanks to the
1604 AppStream system, if you run into a file format you do not know, and
1605 want to figure out which packages support the format, you can find the
1606 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
1607 look up all packages announcing support for this format in their
1608 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
1609 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
1610 me, want to know which packages support inode/directory, you can get a
1611 list like this:&lt;/p&gt;
1612
1613 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1614 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
1615 Package: anjuta
1616 Package: audacious
1617 Package: baobab
1618 Package: cervisia
1619 Package: chirp
1620 Package: dolphin
1621 Package: doublecmd-common
1622 Package: easytag
1623 Package: enlightenment
1624 Package: ephoto
1625 Package: filelight
1626 Package: gwenview
1627 Package: k4dirstat
1628 Package: kaffeine
1629 Package: kdesvn
1630 Package: kid3
1631 Package: kid3-qt
1632 Package: nautilus
1633 Package: nemo
1634 Package: pcmanfm
1635 Package: pcmanfm-qt
1636 Package: qweborf
1637 Package: ranger
1638 Package: sirikali
1639 Package: spacefm
1640 Package: spacefm
1641 Package: vifm
1642 %
1643 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1644
1645 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
1646 format is not yet supported by any package in Debian:&lt;/p&gt;
1647
1648 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1649 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
1650 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
1651 %
1652 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1653
1654 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
1655 format:&lt;/p&gt;
1656
1657 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1658 % appstreamcli what-provides mimetype application/sla|grep Package
1659 Package: cura
1660 Package: meshlab
1661 Package: printrun
1662 %
1663 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1664
1665 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
1666
1667 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1668 activities, please send Bitcoin donations to my address
1669 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1670 </description>
1671 </item>
1672
1673 <item>
1674 <title>Debian APT upgrade without enough free space on the disk...</title>
1675 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
1676 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
1677 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
1678 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
1679 for a while, and when I need to update it there is not enough free
1680 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
1681 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
1682 upgrade only some of the packages in one batch, until the amount of
1683 packages to download fall below the amount of free space available.
1684 Today, I had about 500 packages to upgrade, and after a while I got
1685 tired of trying to install chunks of packages manually. I concluded
1686 that I did not have the spare hours required to complete the task, and
1687 decided to see if I could automate it. I came up with this small
1688 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
1689
1690 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1691 #!/bin/sh
1692 #
1693 # Upgrade packages when the disk is too full to upgrade every
1694 # upgradable package in one lump. Fetching packages to upgrade using
1695 # apt, and then installing using dpkg, to avoid changing the package
1696 # flag for manual/automatic.
1697
1698 set -e
1699
1700 ignore() {
1701 if [ &quot;$1&quot; ]; then
1702 grep -v &quot;$1&quot;
1703 else
1704 cat
1705 fi
1706 }
1707
1708 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
1709 echo &quot;Upgrading $p&quot;
1710 apt clean
1711 apt install --download-only -y $p
1712 for f in /var/cache/apt/archives/*.deb; do
1713 if [ -e &quot;$f&quot; ]; then
1714 dpkg -i /var/cache/apt/archives/*.deb
1715 break
1716 fi
1717 done
1718 done
1719 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1720
1721 &lt;p&gt;The script will extract the list of packages to upgrade, try to
1722 download the packages needed to upgrade one package, install the
1723 downloaded packages using dpkg. The idea is to upgrade packages
1724 without changing the APT mark for the package (ie the one recording of
1725 the package was manually requested or pulled in as a dependency). To
1726 use it, simply run it as root from the command line. If it fail, try
1727 &#39;apt install -f&#39; to clean up the mess and run the script again. This
1728 might happen if the new packages conflict with one of the old
1729 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
1730
1731 &lt;p&gt;It take one option, a package to ignore in the list of packages to
1732 upgrade. The option to ignore a package is there to be able to skip
1733 the packages that are simply too large to unpack. Today this was
1734 &#39;ghc&#39;, but I have run into other large packages causing similar
1735 problems earlier (like TeX).&lt;/p&gt;
1736
1737 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
1738 alternative ways to handle this. The &quot;unattended-upgrades
1739 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
1740 each package to upgrade, and then upgrade them in order, smallest set
1741 first. It might be a better option than my above mentioned script.
1742 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
1743 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
1744
1745 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1746 activities, please send Bitcoin donations to my address
1747 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1748 </description>
1749 </item>
1750
1751 <item>
1752 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
1753 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
1754 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
1755 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
1756 <description>&lt;p&gt;A new version of the
1757 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
1758 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
1759 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
1760 useful. It was uploaded the last few days, and the last update will
1761 enter testing tomorrow. See the
1762 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
1763 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
1764 was announced 6 days ago. We will try to get it into Debian as
1765 well.&lt;/p&gt;
1766
1767 &lt;p&gt;More information related to 3D printing is available on the
1768 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
1769 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
1770 in Debian.&lt;/p&gt;
1771
1772 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1773 activities, please send Bitcoin donations to my address
1774 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1775 </description>
1776 </item>
1777
1778 <item>
1779 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
1780 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
1781 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
1782 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
1783 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
1784 that the nice and user friendly 3D printer slicer software Cura just
1785 entered Debian Unstable. It consist of five packages,
1786 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
1787 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
1788 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
1789 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
1790 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
1791 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
1792 two, uranium and cura, entered Unstable yesterday. This should make
1793 it easier for Debian users to print on at least the Ultimaker class of
1794 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
1795 make life easier for at least me. :)&lt;/p&gt;
1796
1797 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
1798 happy to assist him in sponsoring the packages. With the introduction
1799 of Cura, Debian is up to three 3D printer slicers at your service,
1800 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
1801 printer, give it a go. :)&lt;/p&gt;
1802
1803 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
1804 team, flocking together on the
1805 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
1806 mailing list and the
1807 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
1808 IRC channel.&lt;/p&gt;
1809
1810 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
1811 version 3.0.3 and then update the entire set of packages to version
1812 3.1.0 which showed up the last few days.&lt;/p&gt;
1813 </description>
1814 </item>
1815
1816 <item>
1817 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
1818 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
1819 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
1820 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
1821 <description>&lt;p&gt;At my nearby maker space,
1822 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
1823 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
1824 on Windows and MacOS X than Linux, because the software involved had
1825 to be manually compiled and set up on Linux while premade packages
1826 worked out of the box on Windows and MacOS X. I found this annoying,
1827 as the software involved,
1828 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
1829 and should be trivial to get up and running on Linux if someone took
1830 the time to package it for the relevant distributions. I even found
1831 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
1832 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
1833 never resulted in the software showing up in Debian. So a few days
1834 ago I offered my help to try to improve the situation.&lt;/p&gt;
1835
1836 &lt;p&gt;Now I am very happy to see that all the packages required by a
1837 working Cura in Debian are uploaded into Debian and waiting in the NEW
1838 queue for the ftpmasters to have a look. You can track the progress
1839 on
1840 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
1841 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
1842
1843 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
1844 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
1845 queue&lt;/a&gt; while we work up updating the packages to the latest
1846 upstream version.&lt;/p&gt;
1847
1848 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
1849 to use and was unable to configure correctly for Ultimaker 2+ in the
1850 short time I spent on it, are already in Debian. If you are looking
1851 for 3D printer &quot;slicers&quot; and want something already available in
1852 Debian, check out
1853 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
1854 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
1855 The latter is a fork of the former.&lt;/p&gt;
1856
1857 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1858 activities, please send Bitcoin donations to my address
1859 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1860 </description>
1861 </item>
1862
1863 <item>
1864 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
1865 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
1866 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
1867 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
1868 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
1869 mobile cell towers. And this radio chatter is available for anyone
1870 with a radio receiver capable of receiving them. Details about the
1871 mobile phones with very good accuracy is of course collected by the
1872 phone companies, but this is not the topic of this blog post. The
1873 mobile phone radio chatter make it possible to figure out when a cell
1874 phone is nearby, as it include the SIM card ID (IMSI). By paying
1875 attention over time, one can see when a phone arrive and when it leave
1876 an area. I believe it would be nice to make this information more
1877 available to the general public, to make more people aware of how
1878 their phones are announcing their whereabouts to anyone that care to
1879 listen.&lt;/p&gt;
1880
1881 &lt;p&gt;I am very happy to report that we managed to get something
1882 visualizing this information up and running for
1883 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
1884 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
1885 library. The solution is based on the
1886 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
1887 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
1888 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
1889 Sone from the Computer Science department of the University of
1890 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
1891 IMSIs) as dots in a web browser graph, with lines to the dot
1892 representing mobile base station it is talking to. It was working in
1893 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
1894
1895 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
1896 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
1897 connected and visualize the visible cell phone towers using an
1898 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
1899 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
1900 grgsm_livemon_headless processes from
1901 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
1902 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
1903
1904 &lt;p&gt;The frequencies to listen to, are identified using a slightly
1905 patched scan-and-livemon (to set the --args values for each receiver),
1906 and the Hopglass data is generated using the
1907 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
1908 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
1909 more than four SDRs working. There is also a geographical map trying
1910 to show the location of the base stations, but I believe their
1911 coordinates are hardcoded to some random location in Germany, I
1912 believe. The code should be replaced with code to look up location in
1913 a text file, a sqlite database or one of the online databases
1914 mentioned in
1915 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
1916 issue for the topic&lt;/a&gt;.
1917
1918 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
1919 </description>
1920 </item>
1921
1922 <item>
1923 <title>Easier recipe to observe the cell phones around you</title>
1924 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
1925 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
1926 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
1927 <description>&lt;p&gt;A little more than a month ago I wrote
1928 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html&quot;&gt;how
1929 to observe the SIM card ID (aka IMSI number) of mobile phones talking
1930 to nearby mobile phone base stations using Debian GNU/Linux and a
1931 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
1932 the location of people and equipment (like cars and trains) with an
1933 accuracy of a few kilometer. Since then we have worked to make the
1934 procedure even simpler, and it is now possible to do this without any
1935 manual frequency tuning and without building your own packages.&lt;/p&gt;
1936
1937 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
1938 package is now included in Debian testing and unstable, and the
1939 IMSI-catcher code no longer require root access to fetch and decode
1940 the GSM data collected using gr-gsm.&lt;/p&gt;
1941
1942 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
1943 clone of two python scripts:&lt;/p&gt;
1944
1945 &lt;ol&gt;
1946
1947 &lt;li&gt;Start with a Debian machine running the Buster version (aka
1948 testing).&lt;/li&gt;
1949
1950 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
1951 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
1952
1953 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
1954 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
1955
1956 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
1957
1958 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
1959 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
1960 stations and start listening for GSM packages on one of them.&lt;/li&gt;
1961
1962 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
1963 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
1964
1965 &lt;/ol&gt;
1966
1967 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
1968 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
1969 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
1970 work with RTL 8232 and other similar USB radio receivers you can get
1971 very cheaply
1972 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
1973 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
1974 and only use HackRF for fetching GSM data.&lt;/p&gt;
1975
1976 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
1977 frequencies at the time, so if you are going to track and count every
1978 cell phone around you, you need to listen to all the frequencies used.
1979 To listen to several frequencies, use the --numrecv argument to
1980 scan-and-livemon to use several receivers. Further, I am not sure if
1981 phones using 3G or 4G will show as talking GSM to base stations, so
1982 this approach might not see all phones around you. I typically see
1983 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
1984
1985 &lt;p&gt;I&#39;ve tried to run the scanner on a
1986 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
1987 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
1988 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
1989 stdout, I am told there it is caused by a buffer overflow between the
1990 radio and GNU Radio, caused by the program being unable to read the
1991 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
1992 where you started scan-and-livemon, you need a give the process more
1993 CPU power. Perhaps someone are able to optimize the code to a point
1994 where it become possible to set up RPi3 based GSM sniffers? I tried
1995 using Raspbian instead of Debian, but there seem to be something wrong
1996 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
1997 </description>
1998 </item>
1999
2000 <item>
2001 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
2002 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
2003 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
2004 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
2005 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
2006 web based ICT news magazine digi.no on
2007 &lt;a href=&quot;https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-60-kroner-na-kan-mobiler-kartlegges-av-alle/398588&quot;&gt;how
2008 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
2009 DVB-T software defined radios. The article refered to instructions
2010 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
2011 Keld Norman on Youtube on how to make a simple $7 IMSI Catcher&lt;/a&gt;, and I decided to test them out.&lt;/p&gt;
2012
2013 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
2014 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2015 and the ask pybombs to fetch and build everything you need from
2016 scratch. I wanted to see if I could do the same on the most recent
2017 Debian packages, but this did not work because pybombs tried to build
2018 stuff that no longer build with the most recent openssl library or
2019 some other version skew problem. While trying to get this recipe
2020 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
2021 and the only piece of software dependency missing in Debian was the
2022 gr-gsm package. I also found out that the lead upstream developer of
2023 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2024 Debian packages provided in an Ubuntu PPA repository. All I needed to
2025 do was to dget the Debian source package and built it.&lt;/p&gt;
2026
2027 &lt;p&gt;The IMSI collector is a python script listening for packages on the
2028 loopback network device and printing to the terminal some specific GSM
2029 packages with IMSI numbers in them. The code is fairly short and easy
2030 to understand. The reason this work is because gr-gsm include a tool
2031 to read GSM data from a software defined radio like a DVB-T USB stick
2032 and other software defined radios, decode them and inject them into a
2033 network device on your Linux machine (using the loopback device by
2034 default). This proved to work just fine, and I&#39;ve been testing the
2035 collector for a few days now.&lt;/p&gt;
2036
2037 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
2038
2039 &lt;ol&gt;
2040
2041 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
2042
2043 &lt;li&gt;build and install the gr-gsm package available from
2044 &lt;a href=&quot;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&quot;&gt;http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/&lt;/a&gt;,&lt;/li&gt;
2045
2046 &lt;li&gt;clone the git repostory from &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher&quot;&gt;https://github.com/Oros42/IMSI-catcher&lt;/a&gt;,&lt;/li&gt;
2047
2048 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
2049 where it was started is filled with a stream of text (meaning you
2050 found a GSM station).&lt;/li&gt;
2051
2052 &lt;li&gt;go into the IMSI-catcher directory and run &#39;sudo python simple_IMSI-catcher.py&#39; to extract the IMSI numbers.&lt;/li&gt;
2053
2054 &lt;/ol&gt;
2055
2056 &lt;p&gt;To make it even easier in the future to get this sniffer up and
2057 running, I decided to package
2058 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
2059 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
2060 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
2061 Luckily the gnuradio maintainer has promised to help me, as I do not
2062 know much about gnuradio stuff yet.&lt;/p&gt;
2063
2064 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
2065 commercial tools like
2066 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
2067 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
2068 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
2069 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
2070 more people realise how their whereabouts when carrying a cell phone
2071 is easily tracked. Seeing the data flow on the screen, realizing that
2072 I live close to a police station and knowing that the police is also
2073 wearing cell phones, I wonder how hard it would be for criminals to
2074 track the position of the police officers to discover when there are
2075 police near by, or for foreign military forces to track the location
2076 of the Norwegian military forces, or for anyone to track the location
2077 of government officials...&lt;/p&gt;
2078
2079 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
2080 script mentioned above is only a fraction of the data broadcasted on
2081 the GSM network. It will only collect one frequency at the time,
2082 while a typical phone will be using several frequencies, and not all
2083 phones will be using the frequencies tracked by the grgsm_livemod
2084 program. Also, there is a lot of radio chatter being ignored by the
2085 simple_IMSI-catcher script, which would be collected by extending the
2086 parser code. I wonder if gr-gsm can be set up to listen to more than
2087 one frequency?&lt;/p&gt;
2088 </description>
2089 </item>
2090
2091 <item>
2092 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
2093 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
2094 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
2095 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
2096 <description>&lt;p align=&quot;center&quot;&gt;&lt;img align=&quot;center&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2017-07-25-debian-handbook-nb-testprint.png&quot;/&gt;&lt;/p&gt;
2097
2098 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
2099 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
2100 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
2101 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2102 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
2103 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
2104 price. The book is also available for download in electronic form as
2105 PDF, EPUB and Mobipocket, as can be
2106 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
2107 as a web page&lt;/a&gt;.&lt;/p&gt;
2108
2109 &lt;p&gt;This is the second book I publish (the first was the book
2110 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
2111 in
2112 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
2113 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
2114 and
2115 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
2116 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
2117 project. I hope
2118 &quot;&lt;a href=&quot;http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-23262290.html&quot;&gt;Håndbok
2119 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
2120 </description>
2121 </item>
2122
2123 <item>
2124 <title>Når nynorskoversettelsen svikter til eksamen...</title>
2125 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
2126 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
2127 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
2128 <description>&lt;p&gt;&lt;a href=&quot;http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-622459b.html&quot;&gt;Aftenposten
2129 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
2130 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2131 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2132 på om den fri oversetterløsningen
2133 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
2134 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
2135
2136 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
2137
2138 &lt;blockquote&gt;
2139 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2140 rolle og muligheter til å håndtere internasjonale utfordringer, som
2141 for eksempel flykningekrisen.&lt;/p&gt;
2142
2143 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2144 på temaet:&lt;/p&gt;
2145 &lt;ol&gt;
2146 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
2147 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
2148 &lt;/ol&gt;
2149
2150 &lt;/blockquote&gt;
2151
2152 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
2153
2154 &lt;blockquote&gt;
2155 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2156 andre aktørar og høve til å handtera internasjonale utfordringar, som
2157 til dømes *flykningekrisen.&lt;/p&gt;
2158
2159 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
2160 temaet:&lt;/p&gt;
2161
2162 &lt;ol&gt;
2163 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
2164 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
2165 &lt;/ol&gt;
2166
2167 &lt;/blockquote&gt;
2168
2169 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
2170 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2171 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2172 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
2173 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
2174 det er kanskje flisespikking. Det understreker vel bare at det alltid
2175 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
2176 </description>
2177 </item>
2178
2179 <item>
2180 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
2181 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
2182 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
2183 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
2184 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
2185 computers at the time, I often needed a way to detect if the machine
2186 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
2187 file or directory affected by the hang, the process (and possibly the
2188 shell) will hang too. So you want to be able to detect this without
2189 risking the detection process getting stuck too. It has not been
2190 obvious how to do this. When the hang has lasted a while, it is
2191 possible to find messages like these in dmesg:&lt;/p&gt;
2192
2193 &lt;p&gt;&lt;blockquote&gt;
2194 nfs: server nfsserver not responding, still trying
2195 &lt;br&gt;nfs: server nfsserver OK
2196 &lt;/blockquote&gt;&lt;/p&gt;
2197
2198 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
2199 be sure looking in dmesg is going to work. If there are lots of other
2200 messages in dmesg the lines might have rotated out of site before they
2201 are noticed.&lt;/p&gt;
2202
2203 &lt;p&gt;While reading through the nfs client implementation in linux kernel
2204 code, I came across some statistics that seem to give a way to detect
2205 it. The om_timeouts sunrpc value in the kernel will increase every
2206 time the above log entry is inserted into dmesg. And after digging a
2207 bit further, I discovered that this value show up in
2208 /proc/self/mountstats on Linux.&lt;/p&gt;
2209
2210 &lt;p&gt;The mountstats content seem to be shared between files using the
2211 same file system context, so it is enough to check one of the
2212 mountstats files to get the state of the mount point for the machine.
2213 I assume this will not show lazy umounted NFS points, nor NFS mount
2214 points in a different process context (ie with a different filesystem
2215 view), but that does not worry me.&lt;/p&gt;
2216
2217 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
2218
2219 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2220 [...]
2221 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2222 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
2223 opts: rw,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=3,acregmax=60,acdirmin=30,acdirmax=60,soft,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=129.240.3.145,mountvers=3,mountport=4048,mountproto=udp,local_lock=all
2224 age: 7863311
2225 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
2226 sec: flavor=1,pseudoflavor=1
2227 events: 61063112 732346265 1028140 35486205 16220064 8162542 761447191 71714012 37189 3891185 45561809 110486139 4850138 420353 15449177 296502 52736725 13523379 0 52182 9016896 1231 0 0 0 0 0
2228 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2229 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
2230 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
2231 per-op statistics
2232 NULL: 0 0 0 0 0 0 0 0
2233 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
2234 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
2235 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
2236 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
2237 READLINK: 125 125 0 20472 18620 0 1112 1118
2238 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
2239 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
2240 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
2241 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
2242 SYMLINK: 903 903 0 233428 245488 6 5865 5917
2243 MKNOD: 80 80 0 20148 21760 0 299 304
2244 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
2245 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
2246 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
2247 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
2248 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
2249 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
2250 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
2251 FSINFO: 2 2 0 232 328 0 1 1
2252 PATHCONF: 1 1 0 116 140 0 0 0
2253 COMMIT: 0 0 0 0 0 0 0 0
2254
2255 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
2256 [...]
2257 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2258
2259 &lt;p&gt;The key number to look at is the third number in the per-op list.
2260 It is the number of NFS timeouts experiences per file system
2261 operation. Here 22 write timeouts and 5 access timeouts. If these
2262 numbers are increasing, I believe the machine is experiencing NFS
2263 hang. Unfortunately the timeout value do not start to increase right
2264 away. The NFS operations need to time out first, and this can take a
2265 while. The exact timeout value depend on the setup. For example the
2266 defaults for TCP and UDP mount points are quite different, and the
2267 timeout value is affected by the soft, hard, timeo and retrans NFS
2268 mount options.&lt;/p&gt;
2269
2270 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
2271 Enterprise Linux for getting the timeout count is to peek in /proc/.
2272 But according to
2273 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
2274 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
2275 command can be used to get these timeout values. But this do not work
2276 on Linux, as far as I can tell. I
2277 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
2278 but have not seen any replies yet.&lt;/p&gt;
2279
2280 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
2281 experiencing NFS hangs? Is there a way to detect which processes are
2282 affected? Is there a way to get the NFS mount going quickly once the
2283 network problem causing the NFS hang has been cleared? I would very
2284 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
2285 </description>
2286 </item>
2287
2288 <item>
2289 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
2290 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
2291 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</guid>
2292 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
2293 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
2294 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
2295 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
2296 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
2297 we are working on the proof reading to ensure consistent language and
2298 use of correct computer science terms. The plan is to make the book
2299 available on paper, as well as in electronic form. For that to
2300 happen, the proof reading must be completed and all the figures need
2301 to be translated. If you want to help out, get in touch.&lt;/p&gt;
2302
2303 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
2304
2305 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
2306 pages) of the book created every morning is available for
2307 proofreading. If you find any errors, please
2308 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
2309 Weblate and correct the error&lt;/a&gt;. The
2310 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
2311 of the translation including figures&lt;/a&gt; is a useful source for those
2312 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
2313 </description>
2314 </item>
2315
2316 <item>
2317 <title>Unlimited randomness with the ChaosKey?</title>
2318 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
2319 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
2320 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
2321 <description>&lt;p&gt;A few days ago I ordered a small batch of
2322 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
2323 USB dongle for generating entropy created by Bdale Garbee and Keith
2324 Packard. Yesterday it arrived, and I am very happy to report that it
2325 work great! According to its designers, to get it to work out of the
2326 box, you need the Linux kernel version 4.1 or later. I tested on a
2327 Debian Stretch machine (kernel version 4.9), and there it worked just
2328 fine, increasing the available entropy very quickly. I wrote a small
2329 test oneliner to test. It first print the current entropy level,
2330 drain /dev/random, and then print the entropy level for five seconds.
2331 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
2332
2333 &lt;blockquote&gt;&lt;pre&gt;
2334 % cat /proc/sys/kernel/random/entropy_avail; \
2335 dd bs=1M if=/dev/random of=/dev/null count=1; \
2336 for n in $(seq 1 5); do \
2337 cat /proc/sys/kernel/random/entropy_avail; \
2338 sleep 1; \
2339 done
2340 300
2341 0+1 oppføringer inn
2342 0+1 oppføringer ut
2343 28 byte kopiert, 0,000264565 s, 106 kB/s
2344 4
2345 8
2346 12
2347 17
2348 21
2349 %
2350 &lt;/pre&gt;&lt;/blockquote&gt;
2351
2352 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
2353 application requiring random bits (like a HTTPS enabled web server)
2354 will halt and wait for more entrpy. And here is the situation with
2355 the ChaosKey inserted:&lt;/p&gt;
2356
2357 &lt;blockquote&gt;&lt;pre&gt;
2358 % cat /proc/sys/kernel/random/entropy_avail; \
2359 dd bs=1M if=/dev/random of=/dev/null count=1; \
2360 for n in $(seq 1 5); do \
2361 cat /proc/sys/kernel/random/entropy_avail; \
2362 sleep 1; \
2363 done
2364 1079
2365 0+1 oppføringer inn
2366 0+1 oppføringer ut
2367 104 byte kopiert, 0,000487647 s, 213 kB/s
2368 433
2369 1028
2370 1031
2371 1035
2372 1038
2373 %
2374 &lt;/pre&gt;&lt;/blockquote&gt;
2375
2376 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
2377 someone want to buy one here in Norway. :)&lt;/p&gt;
2378
2379 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
2380 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
2381 recording illuminating&lt;/a&gt;. It explains exactly what the source of
2382 randomness is, if you are unable to spot it from the schema drawing
2383 available from the ChaosKey web site linked at the start of this blog
2384 post.&lt;/p&gt;
2385 </description>
2386 </item>
2387
2388 <item>
2389 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
2390 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
2391 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
2392 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
2393 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
2394 web servers, and who own the network equipment it is flowing through?
2395 It is possible to get a glimpse of this from using traceroute, but it
2396 is hard to find all the details. Many years ago, I wrote a system to
2397 map the Norwegian Internet (trying to figure out if our plans for a
2398 network game service would get low enough latency, and who we needed
2399 to talk to about setting up game servers close to the users. Back
2400 then I used traceroute output from many locations (I asked my friends
2401 to run a script and send me their traceroute output) to create the
2402 graph and the map. The output from traceroute typically look like
2403 this:
2404
2405 &lt;p&gt;&lt;pre&gt;
2406 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
2407 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
2408 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
2409 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
2410 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
2411 5 he16-1-1.cr1.san110.as2116.net (195.0.244.234) 2.627 ms he16-1-1.cr2.oslosda310.as2116.net (195.0.244.48) 3.172 ms he16-1-1.cr1.san110.as2116.net (195.0.244.234) 2.857 ms
2412 6 ae1.ar8.oslosda310.as2116.net (195.0.242.39) 0.662 ms 0.637 ms ae0.ar8.oslosda310.as2116.net (195.0.242.23) 0.622 ms
2413 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
2414 8 * * *
2415 9 * * *
2416 [...]
2417 &lt;/pre&gt;&lt;/p&gt;
2418
2419 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
2420 network equipment involved in getting the data traffic from me to the
2421 www.stortinget.no server, and how long it took in milliseconds for a
2422 package to reach the equipment and return to me. Three packages are
2423 sent, and some times the packages do not follow the same path. This
2424 is shown for hop 5, where three different IP addresses replied to the
2425 traceroute request.&lt;/p&gt;
2426
2427 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
2428 implementations I use are traceroute (using ICMP packages) mtr (can do
2429 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
2430 traceroute and a lot of other capabilities). All of them are easily
2431 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
2432
2433 &lt;p&gt;This time around, I wanted to know the geographic location of
2434 different route points, to visualize how visiting a web page spread
2435 information about the visit to a lot of servers around the globe. The
2436 background is that a web site today often will ask the browser to get
2437 from many servers the parts (for example HTML, JSON, fonts,
2438 JavaScript, CSS, video) required to display the content. This will
2439 leak information about the visit to those controlling these servers
2440 and anyone able to peek at the data traffic passing by (like your ISP,
2441 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
2442
2443 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
2444 www.stortinget.no. It is read daily by all members of parliament and
2445 their staff, as well as political journalists, activits and many other
2446 citizens of Norway. A visit to the www.stortinget.no web site will
2447 ask your browser to contact 8 other servers: ajax.googleapis.com,
2448 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
2449 stats.g.doubleclick.net, www.google-analytics.com,
2450 www.googletagmanager.com and www.netigate.se. I extracted this by
2451 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
2452 Stortinget web page and tell me all the URLs PhantomJS downloaded to
2453 render the page (in HAR format using
2454 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
2455 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
2456 to do this). My goal is to visualize network traces to all IP
2457 addresses behind these DNS names, do show where visitors personal
2458 information is spread when visiting the page.&lt;/p&gt;
2459
2460 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
2461 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geoip-small.png&quot; alt=&quot;map of combined traces for URLs used by www.stortinget.no using GeoIP&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
2462
2463 &lt;p&gt;When I had a look around for options, I could not find any good
2464 free software tools to do this, and decided I needed my own traceroute
2465 wrapper outputting KML based on locations looked up using GeoIP. KML
2466 is easy to work with and easy to generate, and understood by several
2467 of the GIS tools I have available. I got good help from by NUUG
2468 colleague Anders Einar with this, and the result can be seen in
2469 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
2470 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
2471 free GeoIP databases I could find (and the for-pay databases my
2472 friends had access to) is not up to the task. The IP addresses of
2473 central Internet infrastructure would typically be placed near the
2474 controlling companies main office, and not where the router is really
2475 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
2476 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
2477
2478 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;&lt;img
2479 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy-small.png&quot; alt=&quot;scapy traceroute graph for URLs used by www.stortinget.no&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
2480
2481 &lt;p&gt;I also had a look at the visual traceroute graph created by
2482 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
2483 showing IP network ownership (aka AS owner) for the IP address in
2484 question.
2485 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
2486 graph display a lot of useful information about the traceroute in SVG
2487 format&lt;/a&gt;, and give a good indication on who control the network
2488 equipment involved, but it do not include geolocation. This graph
2489 make it possible to see the information is made available at least for
2490 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
2491 3 Communications and NetDNA.&lt;/p&gt;
2492
2493 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;https://geotraceroute.com/index.php?node=4&amp;host=www.stortinget.no&quot;&gt;&lt;img
2494 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-small.png&quot; alt=&quot;example geotraceroute view for www.stortinget.no&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
2495
2496 &lt;p&gt;In the process, I came across the
2497 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
2498 Salim Gasmi. Its methology of combining guesses based on DNS names,
2499 various location databases and finally use latecy times to rule out
2500 candidate locations seemed to do a very good job of guessing correct
2501 geolocation. But it could only do one trace at the time, did not have
2502 a sensor in Norway and did not make the geolocations easily available
2503 for postprocessing. So I contacted the developer and asked if he
2504 would be willing to share the code (he refused until he had time to
2505 clean it up), but he was interested in providing the geolocations in a
2506 machine readable format, and willing to set up a sensor in Norway. So
2507 since yesterday, it is possible to run traces from Norway in this
2508 service thanks to a sensor node set up by
2509 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
2510 trace in KML format for further processing.&lt;/p&gt;
2511
2512 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.kml&quot;&gt;&lt;img
2513 src=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-geotraceroute-kml-join.png&quot; alt=&quot;map of combined traces for URLs used by www.stortinget.no using geotraceroute&quot;/&gt;&lt;/a&gt;&lt;/p&gt;
2514
2515 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
2516 Denmark, Germany, Holland and Ireland. Plenty of places where the
2517 Snowden confirmations verified the traffic is read by various actors
2518 without your best interest as their top priority.&lt;/p&gt;
2519
2520 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
2521 over all the hosts behind the urls imported by www.stortinget.no and
2522 ask for the KML file from GeoTraceroute, and create a combined KML
2523 file with all the traces (unfortunately only one of the IP addresses
2524 behind the DNS name is traced this time. To get them all, one would
2525 have to request traces using IP number instead of DNS names from
2526 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
2527
2528 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
2529 the IP traffic moves and who control the boxes involved in moving it.
2530 And every time the link crosses for example the Swedish border, we can
2531 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
2532 Britain and NSA in USA and cables around the globe. (Hm, what should
2533 we tell them? :) Keep that in mind if you ever send anything
2534 unencrypted over the Internet.&lt;/p&gt;
2535
2536 &lt;p&gt;PS: KML files are drawn using
2537 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
2538 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
2539 Marble. There are heaps of other options too.&lt;/p&gt;
2540
2541 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2542 activities, please send Bitcoin donations to my address
2543 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2544 </description>
2545 </item>
2546
2547 <item>
2548 <title>Appstream just learned how to map hardware to packages too!</title>
2549 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
2550 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
2551 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
2552 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
2553 readers probably know, I have been working on the
2554 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
2555 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
2556 it easier for users to figure out what to install to get a given piece
2557 of hardware to work in Debian, and a key part of this system is a way
2558 to map hardware to packages. Isenkram have its own mapping database,
2559 and also uses data provided by each package using the AppStream
2560 metadata format. And today,
2561 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
2562 Debian learned to look up hardware the same way Isenkram is doing it,
2563 ie using fnmatch():&lt;/p&gt;
2564
2565 &lt;p&gt;&lt;pre&gt;
2566 % appstreamcli what-provides modalias \
2567 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2568 Identifier: pymissile [generic]
2569 Name: pymissile
2570 Summary: Control original Striker USB Missile Launcher
2571 Package: pymissile
2572 % appstreamcli what-provides modalias usb:v0694p0002d0000
2573 Identifier: libnxt [generic]
2574 Name: libnxt
2575 Summary: utility library for talking to the LEGO Mindstorms NXT brick
2576 Package: libnxt
2577 ---
2578 Identifier: t2n [generic]
2579 Name: t2n
2580 Summary: Simple command-line tool for Lego NXT
2581 Package: t2n
2582 ---
2583 Identifier: python-nxt [generic]
2584 Name: python-nxt
2585 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
2586 Package: python-nxt
2587 ---
2588 Identifier: nbc [generic]
2589 Name: nbc
2590 Summary: C compiler for LEGO Mindstorms NXT bricks
2591 Package: nbc
2592 %
2593 &lt;/pre&gt;&lt;/p&gt;
2594
2595 &lt;p&gt;A similar query can be done using the combined AppStream and
2596 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
2597
2598 &lt;p&gt;&lt;pre&gt;
2599 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2600 pymissile
2601 % isenkram-lookup usb:v0694p0002d0000
2602 libnxt
2603 nbc
2604 python-nxt
2605 t2n
2606 %
2607 &lt;/pre&gt;&lt;/p&gt;
2608
2609 &lt;p&gt;You can find modalias values relevant for your machine using
2610 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
2611
2612 &lt;p&gt;If you want to make this system a success and help Debian users
2613 make the most of the hardware they have, please
2614 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
2615 AppStream metadata for your package following the guidelines&lt;/a&gt;
2616 documented in the wiki. So far only 11 packages provide such
2617 information, among the several hundred hardware specific packages in
2618 Debian. The Isenkram database on the other hand contain 101 packages,
2619 mostly related to USB dongles. Most of the packages with hardware
2620 mapping in AppStream are LEGO Mindstorms related, because I have, as
2621 part of my involvement in
2622 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
2623 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
2624 complete set of packages in Debian for that particular hardware. The
2625 team also got a nice Christmas present today. The
2626 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
2627 package&lt;/a&gt; made it into Debian. With this package in place, it is
2628 now possible to use the LEGO Mindstorms NXT unit with only free
2629 software, as the nxt-firmware package contain the source and firmware
2630 binaries for the NXT brick.&lt;/p&gt;
2631
2632 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2633 activities, please send Bitcoin donations to my address
2634 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2635 </description>
2636 </item>
2637
2638 <item>
2639 <title>Isenkram updated with a lot more hardware-package mappings</title>
2640 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
2641 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
2642 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
2643 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
2644 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
2645 and install packages to get your hardware dongles to work, is still
2646 going strong. It is a system to look up the hardware present on or
2647 connected to the current system, and map the hardware to Debian
2648 packages. It can either be done using the tools in isenkram-cli or
2649 using the user space daemon in the isenkram package. The latter will
2650 notify you, when inserting new hardware, about what packages to
2651 install to get the dongle working. It will even provide a button to
2652 click on to ask packagekit to install the packages.&lt;/p&gt;
2653
2654 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
2655
2656 &lt;p&gt;&lt;pre&gt;
2657 % isenkram-lookup
2658 bluez
2659 cheese
2660 ethtool
2661 fprintd
2662 fprintd-demo
2663 gkrellm-thinkbat
2664 hdapsd
2665 libpam-fprintd
2666 pidgin-blinklight
2667 thinkfan
2668 tlp
2669 tp-smapi-dkms
2670 tp-smapi-source
2671 tpb
2672 %
2673 &lt;/pre&gt;&lt;/p&gt;
2674
2675 &lt;p&gt;It can also list the firware package providing firmware requested
2676 by the load kernel modules, which in my case is an empty list because
2677 I have all the firmware my machine need:
2678
2679 &lt;p&gt;&lt;pre&gt;
2680 % /usr/sbin/isenkram-autoinstall-firmware -l
2681 info: did not find any firmware files requested by loaded kernel modules. exiting
2682 %
2683 &lt;/pre&gt;&lt;/p&gt;
2684
2685 &lt;p&gt;The last few days I had a look at several of the around 250
2686 packages in Debian with udev rules. These seem like good candidates
2687 to install when a given hardware dongle is inserted, and I found
2688 several that should be proposed by isenkram. I have not had time to
2689 check all of them, but am happy to report that now there are 97
2690 packages packages mapped to hardware by Isenkram. 11 of these
2691 packages provide hardware mapping using AppStream, while the rest are
2692 listed in the modaliases file provided in isenkram.&lt;/p&gt;
2693
2694 &lt;p&gt;These are the packages with hardware mappings at the moment. The
2695 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
2696 support using AppStream, for everyone to use:&lt;/p&gt;
2697
2698 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
2699 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
2700 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
2701 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
2702 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
2703 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
2704 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
2705 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
2706 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
2707 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
2708 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
2709 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
2710 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
2711 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
2712 pcscd, pidgin-blinklight, printer-driver-splix,
2713 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
2714 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
2715 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
2716 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
2717 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
2718 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
2719 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
2720 xserver-xorg-video-vmware, yubikey-personalization and
2721 zd1211-firmware&lt;/p&gt;
2722
2723 &lt;p&gt;If you know of other packages, please let me know with a wishlist
2724 bug report against the isenkram-cli package, and ask the package
2725 maintainer to
2726 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
2727 metadata according to the guidelines&lt;/a&gt; to provide the information
2728 for everyone. In time, I hope to get rid of the isenkram specific
2729 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
2730
2731 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
2732 much hardware, and suggest that the package with with any ethernet
2733 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
2734 the details. I hope the maintainer find time to address it soon. In
2735 the mean time I provide an override in isenkram.&lt;/p&gt;
2736 </description>
2737 </item>
2738
2739 <item>
2740 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
2741 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
2742 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
2743 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
2744 <description>&lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-12-11-nice-oolite.png&quot;/&gt;&lt;/p&gt;
2745
2746 &lt;p&gt;In my early years, I played
2747 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
2748 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
2749 space, and reached the &#39;elite&#39; fighting status before I moved on. The
2750 original Elite game was available on Commodore 64 and the IBM PC
2751 edition I played had a 64 KB executable. I am still impressed today
2752 that the authors managed to squeeze both a 3D engine and details about
2753 more than 2000 planet systems across 7 galaxies into a binary so
2754 small.&lt;/p&gt;
2755
2756 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
2757 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
2758 really have time to test it properly until a few days ago. It was
2759 great to discover that my old knowledge about trading routes were
2760 still valid. But my fighting and flying abilities were gone, so I had
2761 to retrain to be able to dock on a space station. And I am still not
2762 able to make much resistance when I am attacked by pirates, so I
2763 bougth and mounted the most powerful laser in the rear to be able to
2764 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
2765
2766 &lt;p&gt;When playing Elite in the late eighties, I had to discover
2767 everything on my own, and I had long lists of prices seen on different
2768 planets to be able to decide where to trade what. This time I had the
2769 advantages of the
2770 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
2771 where information about each planet is easily available with common
2772 price ranges and suggested trading routes. This improved my ability
2773 to earn money and I have been able to earn enough to buy a lot of
2774 useful equipent in a few days. I believe I originally played for
2775 months before I could get a docking computer, while now I could get it
2776 after less then a week.&lt;/p&gt;
2777
2778 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
2779 space, you should try out Oolite. It is available for Linux, MacOSX
2780 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
2781
2782 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2783 activities, please send Bitcoin donations to my address
2784 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2785 </description>
2786 </item>
2787
2788 <item>
2789 <title>Quicker Debian installations using eatmydata</title>
2790 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
2791 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
2792 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
2793 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
2794 installation system, observing how using
2795 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
2796 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
2797 speedup around 20-40 percent for Debian Edu, where we install around
2798 1000 packages from within the installer. The eatmydata package
2799 provide a way to disable/delay file system flushing. This is a bit
2800 risky in the general case, as files that should be stored on disk will
2801 stay only in memory a bit longer than expected, causing problems if a
2802 machine crashes at an inconvenient time. But for an installation, if
2803 the machine crashes during installation the process is normally
2804 restarted, and avoiding disk operations as much as possible to speed
2805 up the process make perfect sense.
2806
2807 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
2808 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
2809 but did not have time to push it any further. But a few months ago I
2810 picked it up again and worked with the libeatmydata package maintainer
2811 Mattia Rizzolo to make it easier for everyone to get this installation
2812 speedup in Debian. Thanks to our cooperation There is now an
2813 eatmydata-udeb package in Debian testing and unstable, and simply
2814 enabling/installing it in debian-installer (d-i) is enough to get the
2815 quicker installations. It can be enabled using preseeding. The
2816 following untested kernel argument should do the trick:&lt;/p&gt;
2817
2818 &lt;blockquote&gt;&lt;pre&gt;
2819 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
2820 &lt;/pre&gt;&lt;/blockquote&gt;
2821
2822 &lt;p&gt;This should ask d-i to install the package inside the d-i
2823 environment early in the installation sequence. Having it installed
2824 in d-i in turn will make sure the relevant scripts are called just
2825 after debootstrap filled /target/ with the freshly installed Debian
2826 system to configure apt to run dpkg with eatmydata. This is enough to
2827 speed up the installation process. There is a proposal to
2828 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
2829 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
2830 tested its impact.&lt;/p&gt;
2831
2832 </description>
2833 </item>
2834
2835 <item>
2836 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
2837 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
2838 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
2839 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
2840 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
2841 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
2842 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
2843 elever over det ganske land skal levere inn hvert år. Det mange ikke
2844 vet er at selv om de kommersielle alternativene
2845 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
2846 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
2847 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
2848 utmerket fri programvarealternativ som kan. Oversetterverktøyet
2849 Apertium har støtte for en rekke språkkombinasjoner, og takket være
2850 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
2851 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
2852 nynorsk, og få den automatoversatt til det andre skriftspråket.
2853 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
2854 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
2855 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
2856 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
2857 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
2858 teksten din i webskjemaet der.
2859
2860 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
2861 teknologien kan du enten installere pakken
2862 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
2863 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
2864 api.apertium.org. Se
2865 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
2866 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
2867 denne teksten som ble skrevet på bokmål over maskinoversatt til
2868 nynorsk.&lt;/p&gt;
2869
2870 &lt;hr/&gt;
2871
2872 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
2873 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
2874 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
2875 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
2876 veit er at sjølv om dei kommersielle alternativa
2877 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
2878 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
2879 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
2880 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
2881 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
2882 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
2883 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
2884 nynorsk, og få den *automatoversatt til det andre skriftspråket.
2885 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
2886 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
2887 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
2888 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
2889 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
2890 teksta di i *webskjemaet der.
2891
2892 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
2893 teknologien kan du anten installera pakken
2894 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
2895 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
2896 *api.*apertium.org. Sjå
2897 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
2898 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
2899 for denne teksta som vart skreva på bokmål over *maskinoversatt til
2900 nynorsk.&lt;/p&gt;
2901 </description>
2902 </item>
2903
2904 <item>
2905 <title>Coz profiler for multi-threaded software is now in Debian</title>
2906 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
2907 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
2908 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
2909 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
2910 profiler able to run benchmarking experiments on the instrumented
2911 multi-threaded program, finally
2912 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
2913 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
2914 months since
2915 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html&quot;&gt;I
2916 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
2917 it suitable for Debian. There are still issues with clang
2918 compatibility, inline assembly only working x86 and minimized
2919 JavaScript libraries.&lt;/p&gt;
2920
2921 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
2922
2923 &lt;p&gt;&lt;blockquote&gt;
2924 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
2925 &lt;/blockquote&gt;&lt;/p&gt;
2926
2927 &lt;p&gt;This will produce a profile.coz file in the current working
2928 directory with the profiling information. This is then given to a
2929 JavaScript application provided in the package and available from
2930 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
2931 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
2932
2933 &lt;p&gt;&lt;blockquote&gt;
2934 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
2935 &lt;/blockquote&gt;&lt;/p&gt;
2936
2937 &lt;p&gt;See the project home page and the
2938 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
2939 ;login: article on Coz&lt;/a&gt; for more information on how it is
2940 working.&lt;/p&gt;
2941 </description>
2942 </item>
2943
2944 <item>
2945 <title>My own self balancing Lego Segway</title>
2946 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
2947 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
2948 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
2949 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
2950 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
2951 present. It had been on my wishlist for a while, because I wanted to
2952 build a Segway like balancing lego robot. I had already built
2953 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
2954 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
2955 NXT kit as the balance sensor, but it was not working very well. It
2956 could balance for a while, but was very sensitive to the light
2957 condition in the room and the reflective properties of the surface and
2958 would fall over after a short while. I wanted something more robust,
2959 and had
2960 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
2961 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
2962 wishlist for some years before it suddenly showed up as a gift from my
2963 loved ones. :)&lt;/p&gt;
2964
2965 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
2966 since then. But that changed some days ago, when I was searching for
2967 lego segway information and came across a recipe from HiTechnic for
2968 building
2969 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
2970 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
2971 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
2972 code&lt;/a&gt; was included, so it was just a question of putting it all
2973 together. And thanks to the great work of many Debian developers, the
2974 compiler needed to build the source for the NXT is already included in
2975 Debian, so I was read to go in less than an hour. The resulting robot
2976 do not look very impressive in its simplicity:&lt;/p&gt;
2977
2978 &lt;p align=&quot;center&quot;&gt;&lt;img width=&quot;70%&quot; src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-robot.jpeg&quot;&gt;&lt;/p&gt;
2979
2980 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
2981 design from HiTechnic, I had to comment out the last task
2982 (taskControl). I simply placed /* and */ around it get the program
2983 working without that sensor present. Now it balances just fine until
2984 the battery status run low:&lt;/p&gt;
2985
2986 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
2987 &lt;source src=&quot;http://people.skolelinux.org/pere/blog/images/2016-11-04-lego-htway-balancing.ogv&quot; type=&quot;video/ogg&quot;&gt;
2988 &lt;/video&gt;&lt;/p&gt;
2989
2990 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
2991 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
2992
2993 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
2994 they need to work with LEGO in Debian and all our derivative
2995 distributions like Ubuntu, check out
2996 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
2997 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
2998 RCX and NXT controller (no EV3), and would like to make sure the
2999 Debian tools needed to program the systems I own work as they
3000 should.&lt;/p&gt;
3001 </description>
3002 </item>
3003
3004 <item>
3005 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
3006 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
3007 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
3008 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
3009 <description>&lt;p&gt;In July
3010 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html&quot;&gt;I
3011 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
3012 the ability to receive SMS messages (aka without a cell phone). It is
3013 time to share some experiences and provide an updated setup.&lt;/p&gt;
3014
3015 &lt;p&gt;The Signal app have worked fine for several months now, and I use
3016 it regularly to chat with my loved ones. I had a major snag at the
3017 end of my summer vacation, when the the app completely forgot my
3018 setup, identity and keys. The reason behind this major mess was
3019 running out of disk space. To avoid that ever happening again I have
3020 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
3021 roll back to an earlier version if the files are wiped by mistake. I
3022 had to use it once after introducing the git backup. When rolling
3023 back to an earlier version, one need to use the &#39;reset session&#39; option
3024 in Signal to get going, and notify the people you talk with about the
3025 problem. I assume there is some sequence number tracking in the
3026 protocol to detect rollback attacks. The git repository is rather big
3027 (674 MiB so far), but I have not tried to figure out if some of the
3028 content can be added to a .gitignore file due to lack of spare
3029 time.&lt;/p&gt;
3030
3031 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
3032 make it impossible to send messages using Signal. I could still
3033 receive them, but had to patch the code with a new timestamp to send.
3034 I believe the timeout is added by the developers to force people to
3035 upgrade to the latest version of the app, even when there is no
3036 protocol changes, to reduce the version skew among the user base and
3037 thus try to keep the number of support requests down.&lt;/p&gt;
3038
3039 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
3040 making the old patch fail to apply cleanly. Below is an updated
3041 patch, including the shell wrapper I use to start Signal. The
3042 original version required a new user to locate the JavaScript console
3043 and call a function from there. I got help from a friend with more
3044 JavaScript knowledge than me to modify the code to provide a GUI
3045 button instead. This mean that to get started you just need to run
3046 the wrapper and click the &#39;Register without mobile phone&#39; to get going
3047 now. I&#39;ve also modified the timeout code to always set it to 90 days
3048 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
3049
3050 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
3051
3052 &lt;ol&gt;
3053
3054 &lt;li&gt;First, install required packages to get the source code and the
3055 browser you need. Signal only work with Chrome/Chromium, as far as I
3056 know, so you need to install it.
3057
3058 &lt;pre&gt;
3059 apt install git tor chromium
3060 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3061 &lt;/pre&gt;&lt;/li&gt;
3062
3063 &lt;li&gt;Modify the source code using command listed in the the patch
3064 block below.&lt;/li&gt;
3065
3066 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
3067 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
3068
3069 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
3070 number you can receive calls to the next minute, receive the
3071 verification code and enter it into the form field and press
3072 &#39;Register&#39;. Note, the phone number you use will be user Signal
3073 username, ie the way others can find you on Signal.&lt;/li&gt;
3074
3075 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
3076 not show up in the contact list until you restart Signal, and there is
3077 no way to assign names to Contacts. There is also no way to create or
3078 update chat groups. I suspect this is because the web app do not have
3079 a associated contact database.&lt;/li&gt;
3080
3081 &lt;/ol&gt;
3082
3083 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
3084 main author moxie0 reject federation and accept dependencies to major
3085 corporations like Google (part of the code is fetched from Google) and
3086 Amazon (the central coordination point is owned by Amazon). See for
3087 example
3088 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
3089 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
3090 view on these issues. But the network effect is strong in this case,
3091 and several of the people I want to communicate with already use
3092 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
3093 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
3094 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
3095 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
3096 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
3097 working on Debian Stable.&lt;/p&gt;
3098
3099 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
3100 working. It switch to the production servers, disable to timeout,
3101 make registration easier and add the shell wrapper:&lt;/p&gt;
3102
3103 &lt;pre&gt;
3104 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
3105 diff --git a/js/background.js b/js/background.js
3106 index 24b4c1d..579345f 100644
3107 --- a/js/background.js
3108 +++ b/js/background.js
3109 @@ -33,9 +33,9 @@
3110 });
3111 });
3112
3113 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
3114 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
3115 var SERVER_PORTS = [80, 4433, 8443];
3116 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
3117 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
3118 var messageReceiver;
3119 window.getSocketStatus = function() {
3120 if (messageReceiver) {
3121 diff --git a/js/expire.js b/js/expire.js
3122 index 639aeae..beb91c3 100644
3123 --- a/js/expire.js
3124 +++ b/js/expire.js
3125 @@ -1,6 +1,6 @@
3126 ;(function() {
3127 &#39;use strict&#39;;
3128 - var BUILD_EXPIRATION = 0;
3129 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
3130
3131 window.extension = window.extension || {};
3132
3133 diff --git a/js/views/install_view.js b/js/views/install_view.js
3134 index 7816f4f..1d6233b 100644
3135 --- a/js/views/install_view.js
3136 +++ b/js/views/install_view.js
3137 @@ -38,7 +38,8 @@
3138 return {
3139 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
3140 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
3141 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
3142 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
3143 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
3144 };
3145 },
3146 clearQR: function() {
3147 diff --git a/options.html b/options.html
3148 index dc0f28e..8d709f6 100644
3149 --- a/options.html
3150 +++ b/options.html
3151 @@ -14,7 +14,10 @@
3152 &amp;lt;div class=&#39;nav&#39;&gt;
3153 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
3154 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
3155 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
3156 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
3157 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
3158 +
3159 + &amp;lt;/div&gt;
3160 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
3161 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
3162 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
3163 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
3164 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
3165 @@ -0,0 +1,12 @@
3166 +#!/bin/sh
3167 +set -e
3168 +cd $(dirname $0)
3169 +mkdir -p userdata
3170 +userdata=&quot;`pwd`/userdata&quot;
3171 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
3172 + (cd $userdata &amp;&amp; git init)
3173 +fi
3174 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
3175 +exec chromium \
3176 + --proxy-server=&quot;socks://localhost:9050&quot; \
3177 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3178 EOF
3179 chmod a+rx run-signal-app
3180 &lt;/pre&gt;
3181
3182 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3183 activities, please send Bitcoin donations to my address
3184 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3185 </description>
3186 </item>
3187
3188 <item>
3189 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
3190 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
3191 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
3192 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
3193 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3194 system&lt;/a&gt; provide a practical and easy way to figure out which
3195 packages support the hardware in a given machine. The command line
3196 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
3197 convenient way to list and install packages relevant for the current
3198 hardware during system installation, both user space packages and
3199 firmware packages. The GUI background daemon on the other hand provide
3200 a pop-up proposing to install packages when a new dongle is inserted
3201 while using the computer. For example, if you plug in a smart card
3202 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
3203 that package isn&#39;t already installed, and if you plug in a USB video
3204 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
3205 cheese is currently missing. This already work just fine.&lt;/p&gt;
3206
3207 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
3208 package names. When I started no such database existed in Debian, so
3209 I made my own data set and included it with the isenkram package and
3210 made isenkram fetch the latest version of this database from git using
3211 http. This way the isenkram users would get updated package proposals
3212 as soon as I learned more about hardware related packages.&lt;/p&gt;
3213
3214 &lt;p&gt;The hardware is identified using modalias strings. The modalias
3215 design is from the Linux kernel where most hardware descriptors are
3216 made available as a strings that can be matched using filename style
3217 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3218 identifiers.&lt;/p&gt;
3219
3220 &lt;p&gt;The downside to the Isenkram specific database is that there is no
3221 information about relevant distribution / Debian version, making
3222 isenkram propose obsolete packages too. But along came AppStream, a
3223 cross distribution mechanism to store and collect metadata about
3224 software packages. When I heard about the proposal, I contacted the
3225 people involved and suggested to add a hardware matching rule using
3226 modalias strings in the specification, to be able to use AppStream for
3227 mapping hardware to packages. This idea was accepted and AppStream is
3228 now a great way for a package to announce the hardware it support in a
3229 distribution neutral way. I wrote
3230 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html&quot;&gt;a
3231 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
3232 December. If you have a hardware related package in Debian, please
3233 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
3234
3235 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
3236 RCX or NXT unit, announce this support using AppStream. The effect is
3237 that when you insert such LEGO robot controller into your Debian
3238 machine, Isenkram will propose to install the packages needed to get
3239 it working. The intention is that this should allow the local user to
3240 start programming his robot controller right away without having to
3241 guess what packages to use or which permissions to fix.&lt;/p&gt;
3242
3243 &lt;p&gt;But when I sat down with my son the other day to program our NXT
3244 unit using his Debian Stretch computer, I discovered something
3245 annoying. The local console user (ie my son) did not get access to
3246 the USB device for programming the unit. This used to work, but no
3247 longer in Jessie and Stretch. After some investigation and asking
3248 around on #debian-devel, I discovered that this was because udev had
3249 changed the mechanism used to grant access to local devices. The
3250 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
3251 no longer applied, because LDAP users no longer was added to the
3252 plugdev group during login. Michael Biebl told me that this method
3253 was obsolete and the new method used ACLs instead. This was good
3254 news, as the plugdev mechanism is a mess when using a remote user
3255 directory like LDAP. Using ACLs would make sure a user lost device
3256 access when she logged out, even if the user left behind a background
3257 process which would retain the plugdev membership with the ConsoleKit
3258 setup. Armed with this knowledge I moved on to fix the access problem
3259 for the LEGO Mindstorms related packages.&lt;/p&gt;
3260
3261 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
3262 applied directly for a device, or is applied in
3263 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
3264 LEGO Mindstorms udev rules did not have a class, I decided to add the
3265 tag directly in the udev rules files included in the packages. Here
3266 is one example. For the nqc C compiler for the RCX, the
3267 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
3268
3269 &lt;p&gt;&lt;pre&gt;
3270 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
3271 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
3272 &lt;/pre&gt;&lt;/p&gt;
3273
3274 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
3275 packages using plugdev in their /lib/udev/rules.d/ files should be
3276 changed to use this tag (either directly or indirectly via
3277 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
3278 to detect this?&lt;/p&gt;
3279
3280 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
3281 It is unclear to me if the uaccess tag is an internal implementation
3282 detail like the udev-acl tag used by
3283 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
3284 indirect method is the preferred way. Michael
3285 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
3286 documentation from the systemd project&lt;/a&gt; and I hope it will make
3287 this clearer. For now I use the generic classes when they exist and
3288 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
3289 directly if no such class exist.&lt;/p&gt;
3290
3291 &lt;p&gt;To learn more about the isenkram system, please check out
3292 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3293 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3294
3295 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
3296 please join us on our IRC channel
3297 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
3298 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
3299 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
3300 list is not yet created, but we are working on it. :)&lt;/p&gt;
3301
3302 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3303 activities, please send Bitcoin donations to my address
3304 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3305 </description>
3306 </item>
3307
3308 <item>
3309 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
3310 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
3311 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</guid>
3312 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
3313 <description>&lt;p&gt;In April we
3314 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html&quot;&gt;started
3315 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
3316 how to set up and administrate a Debian system. Today I am happy to
3317 report that the first draft is now publicly available. You can find
3318 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
3319 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
3320 eight chapters have a first draft translation, and we are working on
3321 proofreading the content. If you want to help out, please start
3322 contributing using
3323 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3324 hosted weblate project page&lt;/a&gt;, and get in touch using
3325 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3326 translators mailing list&lt;/a&gt;. Please also check out
3327 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3328 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
3329 and update weblate if you find errors.&lt;/p&gt;
3330
3331 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
3332 electronic form.&lt;/p&gt;
3333 </description>
3334 </item>
3335
3336 <item>
3337 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
3338 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
3339 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
3340 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
3341 <description>&lt;p&gt;This summer, I read a great article
3342 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
3343 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
3344 how to profile multi-threaded programs. It presented a system for
3345 profiling software by running experiences in the running program,
3346 testing how run time performance is affected by &quot;speeding up&quot; parts of
3347 the code to various degrees compared to a normal run. It does this by
3348 slowing down parallel threads while the &quot;faster up&quot; code is running
3349 and measure how this affect processing time. The processing time is
3350 measured using probes inserted into the code, either using progress
3351 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
3352 can also measure unmodified code by measuring complete the program
3353 runtime and running the program several times instead.&lt;/p&gt;
3354
3355 &lt;p&gt;The project and presentation was so inspiring that I would like to
3356 get the system into Debian. I
3357 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
3358 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
3359 system ready for Debian by sending patches. The build process need to
3360 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
3361 to include the JavaScript web page used to visualize the collected
3362 profiling information included in the source package.
3363 But I expect that should work out fairly soon.&lt;/p&gt;
3364
3365 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
3366 on a binary with debug symbols available, start the program like this:
3367
3368 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3369 coz run --- program-to-run
3370 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3371
3372 &lt;p&gt;This will create a text file profile.coz with the instrumentation
3373 information. To show what part of the code affect the performance
3374 most, use a web browser and either point it to
3375 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
3376 or use the copy from git (in the gh-pages branch). Check out this web
3377 site to have a look at several example profiling runs and get an idea what the end result from the profile runs look like. To make the
3378 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
3379 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
3380 code, rebuild and run the profiler. This allow coz to do more
3381 targeted experiments.&lt;/p&gt;
3382
3383 &lt;p&gt;A video published by ACM
3384 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
3385 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
3386 from the 25th Symposium on Operating Systems Principles available
3387 titled
3388 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
3389 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
3390
3391 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
3392 for Coz is available from github. It will only build with clang
3393 because it uses a
3394 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
3395 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
3396 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
3397 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
3398
3399 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
3400 of software in Debian. I would very much like some help with the
3401 packaging effort, as I lack the in depth knowledge on how to package
3402 C++ libraries.&lt;/p&gt;
3403 </description>
3404 </item>
3405
3406 <item>
3407 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
3408 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
3409 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
3410 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
3411 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
3412 to be a slight challenge. Here is the recipe if I ever need to do it
3413 again. It all started by me wanting to try the recipe to set up
3414 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
3415 hardened Android installation&lt;/a&gt; from the Tor project blog on a
3416 device I had access to. It is a old mobile phone with a broken
3417 microphone The initial idea had been to just
3418 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
3419 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
3420 until a few days ago.&lt;/p&gt;
3421
3422 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
3423 loader (press volume down and power at the same time), (2) select
3424 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
3425 machine, (4) request the device identifier token by running &#39;fastboot
3426 oem get_identifier_token&#39;, (5) request the device unlocking key using
3427 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
3428 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
3429
3430 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
3431 or newer, and the device I was working on had 2.00.0027. This
3432 apparently can be easily fixed by downloading a Windows program and
3433 running it on your Windows machine, if you accept the terms Microsoft
3434 require you to accept to use Windows - which I do not. So I had to
3435 come up with a different approach. I got a lot of help from AndyCap
3436 on #nuug, and would not have been able to get this working without
3437 him.&lt;/p&gt;
3438
3439 &lt;p&gt;First I needed to extract the hboot firmware from
3440 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
3441 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
3442 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
3443 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
3444 recognise the file format, but unruu worked and extracted rom.zip,
3445 containing the new hboot firmware and a text file describing which
3446 devices it would work for.&lt;/p&gt;
3447
3448 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
3449 followed some instructions
3450 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
3451 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
3452 machine with Debian testing:&lt;/p&gt;
3453
3454 &lt;p&gt;&lt;pre&gt;
3455 adb reboot-bootloader
3456 fastboot oem rebootRUU
3457 fastboot flash zip rom.zip
3458 fastboot flash zip rom.zip
3459 fastboot reboot
3460 &lt;/pre&gt;&lt;/p&gt;
3461
3462 &lt;p&gt;The flash command apparently need to be done twice to take effect,
3463 as the first is just preparations and the second one do the flashing.
3464 The adb command is just to get to the boot loader menu, so turning the
3465 device on while holding volume down and the power button should work
3466 too.&lt;/p&gt;
3467
3468 &lt;p&gt;With the new hboot version in place I could start following the
3469 instructions on the HTC developer web site. I got the device token
3470 like this:&lt;/p&gt;
3471
3472 &lt;p&gt;&lt;pre&gt;
3473 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
3474 &lt;/pre&gt;
3475
3476 &lt;p&gt;And once I got the unlock code via email, I could use it like
3477 this:&lt;/p&gt;
3478
3479 &lt;p&gt;&lt;pre&gt;
3480 fastboot flash unlocktoken Unlock_code.bin
3481 &lt;/pre&gt;&lt;/p&gt;
3482
3483 &lt;p&gt;And with that final step in place, the phone was unlocked and I
3484 could start stuffing the software of my own choosing into the device.
3485 So far I only inserted a replacement recovery image to wipe the phone
3486 before I start. We will see what happen next. Perhaps I should
3487 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
3488 </description>
3489 </item>
3490
3491 <item>
3492 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
3493 <link>https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</link>
3494 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html</guid>
3495 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
3496 <description>&lt;p&gt;For a while now, I have wanted to test
3497 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
3498 said to provide end to end encrypted communication and several of my
3499 friends and family are already using it. As I by choice do not own a
3500 mobile phone, this proved to be harder than expected. And I wanted to
3501 have the source of the client and know that it was the code used on my
3502 machine. But yesterday I managed to get it working. I used the
3503 Github source, compared it to the source in
3504 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
3505 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
3506 patches to use the production Signal servers, started the app and
3507 asked for the hidden &quot;register without a smart phone&quot; form. Here is
3508 the recipe how I did it.&lt;/p&gt;
3509
3510 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
3511
3512 &lt;pre&gt;
3513 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3514 &lt;/pre&gt;
3515
3516 &lt;p&gt;Next, I patched the source to use the production servers, to be
3517 able to talk to other Signal users:&lt;/p&gt;
3518
3519 &lt;pre&gt;
3520 cat &amp;lt;&amp;lt;EOF | patch -p0
3521 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
3522 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
3523 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
3524 @@ -47,8 +47,8 @@
3525 });
3526 });
3527
3528 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
3529 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
3530 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
3531 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
3532 var messageReceiver;
3533 window.getSocketStatus = function() {
3534 if (messageReceiver) {
3535 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
3536 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
3537 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
3538 @@ -1,6 +1,6 @@
3539 ;(function() {
3540 &#39;use strict&#39;;
3541 - var BUILD_EXPIRATION = 0;
3542 + var BUILD_EXPIRATION = 1474492690000;
3543
3544 window.extension = window.extension || {};
3545
3546 EOF
3547 &lt;/pre&gt;
3548
3549 &lt;p&gt;The first part is changing the servers, and the second is updating
3550 an expiration timestamp. This timestamp need to be updated regularly.
3551 It is set 90 days in the future by the build process (Gruntfile.js).
3552 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
3553
3554 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
3555 script to launch Signal in Chromium.&lt;/p&gt;
3556
3557 &lt;pre&gt;
3558 #!/bin/sh
3559 cd $(dirname $0)
3560 mkdir -p userdata
3561 exec chromium \
3562 --proxy-server=&quot;socks://localhost:9050&quot; \
3563 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
3564 &lt;/pre&gt;
3565
3566 &lt;p&gt; The script start the app and configure Chromium to use the Tor
3567 SOCKS5 proxy to make sure those controlling the Signal servers (today
3568 Amazon and Whisper Systems) as well as those listening on the lines
3569 will have a harder time location my laptop based on the Signal
3570 connections if they use source IP address.&lt;/p&gt;
3571
3572 &lt;p&gt;When the script starts, one need to follow the instructions under
3573 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
3574 repository. I right clicked on the Signal window to get up the
3575 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
3576 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
3577 registration form. Then I entered by land line phone number and
3578 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
3579 repeated the verification code three times. After entering the number
3580 into the verification code field in the form, I could start using
3581 Signal from my laptop.
3582
3583 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
3584 whom and thus who know who to those controlling the central server,
3585 but such leakage is hard to avoid with a centrally controlled server
3586 setup. It is something to keep in mind when using Signal - the
3587 content of your chats are harder to intercept, but the meta data
3588 exposing your contact network is available to people you do not know.
3589 So better than many options, but not great. And sadly the usage is
3590 connected to my land line, thus allowing those controlling the server
3591 to associate it to my home and person. I would prefer it if only
3592 those I knew could tell who I was on Signal. There are options
3593 avoiding such information leakage, but most of my friends are not
3594 using them, so I am stuck with Signal for now.&lt;/p&gt;
3595
3596 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
3597 on this topic in
3598 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html&quot;&gt;Experience
3599 and updated recipe for using the Signal app without a mobile
3600 phone&lt;/a&gt;.&lt;/p&gt;
3601 </description>
3602 </item>
3603
3604 <item>
3605 <title>The new &quot;best&quot; multimedia player in Debian?</title>
3606 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
3607 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
3608 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
3609 <description>&lt;p&gt;When I set out a few weeks ago to figure out
3610 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
3611 multimedia player in Debian claimed to support most file formats /
3612 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
3613 the various players claimed support for. The range was from 55 to 130
3614 MIME types. I suspect most media formats are supported by all
3615 players, but this is not really reflected in the MimeTypes values in
3616 their desktop files. There are probably also some bogus MIME types
3617 listed, but it is hard to identify which one this is.&lt;/p&gt;
3618
3619 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
3620 the players suggesting to add more MIME types to their desktop files,
3621 and decided to spend some time myself improving the situation for my
3622 favorite media player VLC. The fixes for VLC entered Debian unstable
3623 yesterday. The complete list of MIME types can be seen on the
3624 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
3625 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
3626
3627 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
3628 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
3629 kmplayer. I am sure some of the other players desktop files support
3630 several of the formats currently listed as working only with vlc,
3631 toten and parole.&lt;/p&gt;
3632
3633 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
3634 supported by all the tested multimedia players in Debian in their
3635 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
3636 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
3637 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
3638 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
3639 it sad that video/ogg and video/webm is not supported by all the media
3640 players in Debian. As far as I can tell, all of them can handle both
3641 formats.&lt;/p&gt;
3642 </description>
3643 </item>
3644
3645 <item>
3646 <title>A program should be able to open its own files on Linux</title>
3647 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
3648 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
3649 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
3650 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
3651 decided to test its presentation tool when making the slides for a
3652 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
3653 wrote the first draft of the slides, saved the result and went to bed
3654 the day before I would give the talk. The next day I took a plane to
3655 the location where the meeting should take place, and on the plane I
3656 started up koffice again to polish the talk a bit, only to discover
3657 that kpresenter refused to load its own data file. I cursed a bit and
3658 started making the slides again from memory, to have something to
3659 present when I arrived. I tested that the saved files could be
3660 loaded, and the day seemed to be rescued. I continued to polish the
3661 slides until I suddenly discovered that the saved file could no longer
3662 be loaded into kpresenter. In the end I had to rewrite the slides
3663 three times, condensing the content until the talk became shorter and
3664 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
3665 kpresenter wrote inline images in a way itself could not understand.
3666 Eventually that bug was fixed and kpresenter ended up being a great
3667 program to make slides. The point I&#39;m trying to make is that we
3668 expect a program to be able to load its own data files, and it is
3669 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
3670
3671 &lt;p&gt;Did you ever experience a program failing to load its own data
3672 files from the desktop file browser? It is not a uncommon problem. A
3673 while back I discovered that the screencast recorder
3674 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
3675 browser would refuse to open. No video player claimed to understand
3676 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
3677 returning the application/ogg MIME type, which no video player I had
3678 installed listed as a MIME type they would understand. I asked for
3679 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
3680 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
3681 several video players to add video/ogg to their desktop files, to give
3682 the file browser an idea what to do about Ogg Theora files. After a
3683 while, the desktop file browsers in Debian started to handle the
3684 output from gtk-recordmydesktop properly.&lt;/p&gt;
3685
3686 &lt;p&gt;But history repeats itself. A few days ago I tested the music
3687 system Rosegarden again, and I discovered that the KDE and xfce file
3688 browsers did not know what to do with the Rosegarden project files
3689 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
3690 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
3691 included in the next upload. To increase the chance of me remembering
3692 how to fix the problem next time some program fail to load its files
3693 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
3694
3695 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
3696 There are two sources for the MIME type of a given file. The output from
3697 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
3698 shared MIME type registry (under /usr/share/mime/). The file MIME
3699 type is mapped to programs supporting the MIME type, and this
3700 information is collected from
3701 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
3702 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
3703 one desktop file claiming support for the MIME type of the file, it is
3704 activated when asking to open a given file. If there are more, one
3705 can normally select which one to use by right-clicking on the file and
3706 selecting the wanted one using &#39;Open with&#39; or similar. In general
3707 this work well. But it depend on each program picking a good MIME
3708 type (preferably
3709 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
3710 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
3711 registry recognizing the file and the desktop file to list the MIME
3712 type in its list of supported MIME types.&lt;/p&gt;
3713
3714 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
3715 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
3716 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
3717
3718 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3719 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
3720 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
3721 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
3722 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
3723 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
3724 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
3725 &amp;lt;/mime-type&amp;gt;
3726 &amp;lt;/mime-info&amp;gt;
3727 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3728
3729 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
3730 (it is a gzipped XML file). Note, it is much better to use an
3731 official MIME type registered with IANA than it is to make up ones own
3732 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
3733
3734 &lt;p&gt;The desktop file of the rosegarden program failed to list
3735 audio/x-rosegarden in its list of supported MIME types, causing the
3736 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
3737
3738 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3739 % grep Mime /usr/share/applications/rosegarden.desktop
3740 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
3741 X-KDE-NativeMimeType=audio/x-rosegarden-composition
3742 %
3743 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3744
3745 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
3746 MimeType= line.&lt;/p&gt;
3747
3748 &lt;p&gt;If you run into a file which fail to open the correct program when
3749 selected from the file browser, please check out the output from
3750 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
3751 MIME type is registered somewhere under /usr/share/mime/ and check
3752 that some desktop file under /usr/share/applications/ is claiming
3753 support for this MIME type. If not, please report a bug to have it
3754 fixed. :)&lt;/p&gt;
3755 </description>
3756 </item>
3757
3758 <item>
3759 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
3760 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
3761 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
3762 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
3763 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
3764 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
3765 related packages. The idea is to have a database of mappings between
3766 hardware and packages, and pop up a dialog suggesting for the user to
3767 install the packages to use a given hardware dongle. Some use cases
3768 are when you insert a Yubikey, it proposes to install the software
3769 needed to control it; when you insert a braille reader list it
3770 proposes to install the packages needed to send text to the reader;
3771 and when you insert a ColorHug screen calibrator it suggests to
3772 install the driver for it. The system work well, and even have a few
3773 command line tools to install firmware packages and packages for the
3774 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
3775
3776 &lt;p&gt;The system was initially written using aptdaemon, because I found
3777 good documentation and example code on how to use it. But aptdaemon
3778 is going away and is generally being replaced by
3779 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
3780 so Isenkram needed a rewrite. And today, thanks to the great patch
3781 from my college Sunil Mohan Adapa in the FreedomBox project, the
3782 rewrite finally took place. I&#39;ve just uploaded a new version of
3783 Isenkram into Debian Unstable with the patch included, and the default
3784 for the background daemon is now to use PackageKit. To check it out,
3785 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
3786 and see if it is recognised.&lt;/p&gt;
3787
3788 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
3789 the machine it is running on, you can check out the isenkram-lookup
3790 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
3791
3792 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3793 % isenkram-lookup
3794 bluez
3795 cheese
3796 fprintd
3797 fprintd-demo
3798 gkrellm-thinkbat
3799 hdapsd
3800 libpam-fprintd
3801 pidgin-blinklight
3802 thinkfan
3803 tleds
3804 tp-smapi-dkms
3805 tp-smapi-source
3806 tpb
3807 %p
3808 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3809
3810 &lt;p&gt;The hardware mappings come from several places. The preferred way
3811 is for packages to announce their hardware support using
3812 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
3813 cross distribution appstream system&lt;/a&gt;.
3814 See
3815 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
3816 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
3817 </description>
3818 </item>
3819
3820 <item>
3821 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
3822 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
3823 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
3824 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
3825 <description>&lt;p&gt;Yesterday I updated the
3826 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
3827 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
3828 enterprising users. There were some nice user and visible changes.
3829 First of all, both desktop menu entries now work. A design flaw in
3830 one of the script made the history graph fail to show up (its PNG was
3831 dumped in ~/.xsession-errors) if no controlling TTY was available.
3832 The script worked when called from the command line, but not when
3833 called from the desktop menu. I changed this to look for a DISPLAY
3834 variable or a TTY before deciding where to draw the graph, and now the
3835 graph window pop up as expected.&lt;/p&gt;
3836
3837 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
3838 graphs (the one showing the last few hours). New is also the user of
3839 colours showing charging in blue and discharge in red. The percentages
3840 of this graph is relative to last full charge, not battery design
3841 capacity.&lt;/p&gt;
3842
3843 &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;
3844
3845 &lt;p&gt;The other graph show the entire history of the collected battery
3846 statistics, comparing it to the design capacity of the battery to
3847 visualise how the battery life time get shorter over time. The red
3848 line in this graph is what the previous graph considers 100 percent:
3849
3850 &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;
3851
3852 &lt;p&gt;In this graph you can see that I only charge the battery to 80
3853 percent of last full capacity, and how the capacity of the battery is
3854 shrinking. :(&lt;/p&gt;
3855
3856 &lt;p&gt;The last new feature is in the collector, which now will handle
3857 more hardware models. On some hardware, Linux power supply
3858 information is stored in /sys/class/power_supply/ACAD/, while the
3859 collector previously only looked in /sys/class/power_supply/AC/. Now
3860 both are checked to figure if there is power connected to the
3861 machine.&lt;/p&gt;
3862
3863 &lt;p&gt;If you are interested in how your laptop battery is doing, please
3864 check out the
3865 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
3866 in Debian unstable, or rebuild it on Jessie to get it working on
3867 Debian stable. :) The upstream source is available from &lt;a
3868 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3869 Patches are very welcome.&lt;/p&gt;
3870
3871 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3872 activities, please send Bitcoin donations to my address
3873 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3874 </description>
3875 </item>
3876
3877 <item>
3878 <title>Debian now with ZFS on Linux included</title>
3879 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
3880 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
3881 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
3882 <description>&lt;p&gt;Today, after many years of hard work from many people,
3883 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
3884 Debian. The package status can be seen on
3885 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
3886 for zfs-linux&lt;/a&gt;. and
3887 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
3888 team status page&lt;/a&gt;. If you want to help out, please join us.
3889 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
3890 source code&lt;/a&gt; is available via git on Alioth. It would also be
3891 great if you could help out with
3892 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
3893 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
3894 </description>
3895 </item>
3896
3897 <item>
3898 <title>What is the best multimedia player in Debian?</title>
3899 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
3900 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
3901 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
3902 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
3903 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
3904
3905 &lt;p&gt;A few years ago, I had a look at the media support for Browser
3906 plugins in Debian, to get an idea which plugins to include in Debian
3907 Edu. I created a script to extract the set of supported MIME types
3908 for each plugin, and used this to find out which multimedia browser
3909 plugin supported most file formats / media types.
3910 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
3911 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
3912 not been updated for a while. But browser plugins are less relevant
3913 these days, so I thought it was time to look at standalone
3914 players.&lt;/p&gt;
3915
3916 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
3917 player when I wanted to play videos from the Norwegian National
3918 Broadcasting Company, and decided to investigate why. The cause is a
3919 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
3920 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
3921 of MIME types announced in the desktop file and the browser plugin,
3922 only to discover that there is quite a large difference between the
3923 two for VLC. This discovery made me dig up the script I used to
3924 compare browser plugins, and adjust it to compare desktop files
3925 instead, to try to figure out which multimedia player in Debian
3926 support most file formats.&lt;/p&gt;
3927
3928 &lt;p&gt;The result can be seen on the Debian Wiki, as
3929 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
3930 table listing all MIME types supported by one of the packages included
3931 in the table&lt;/a&gt;, with the package supporting most MIME types being
3932 listed first in the table.&lt;/p&gt;
3933
3934 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
3935 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
3936 kmplayer. Time for the other players to update their announced MIME
3937 support?&lt;/p&gt;
3938 </description>
3939 </item>
3940
3941 <item>
3942 <title>The Pyra - handheld computer with Debian preinstalled</title>
3943 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
3944 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
3945 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
3946 <description>A friend of mine made me aware of
3947 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
3948 handheld computer which will be delivered with Debian preinstalled. I
3949 would love to get one of those for my birthday. :)&lt;/p&gt;
3950
3951 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
3952 plugs and many others connectors, and include a full keyboard and a 5&quot;
3953 LCD touch screen. The 6000mAh battery is claimed to provide a whole
3954 day of battery life time, but I have not seen any independent tests
3955 confirming this. The vendor is still collecting preorders, and the
3956 last I heard last night was that 22 more orders were needed before
3957 production started.&lt;/p&gt;
3958
3959 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
3960 Debian. Please let me know if you know of any others. Is it the
3961 first computer being sold with Debian preinstalled?&lt;/p&gt;
3962 </description>
3963 </item>
3964
3965 <item>
3966 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
3967 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
3968 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
3969 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
3970 <description>&lt;p&gt;During this weekends
3971 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
3972 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
3973 to make sure there are good books about Debian available in Norwegian
3974 Bokmål, and got in touch with the people behind the
3975 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
3976 project&lt;/a&gt; to get started. If you want to help out, please start
3977 contributing using
3978 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3979 hosted weblate project page&lt;/a&gt;, and get in touch using
3980 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3981 translators mailing list&lt;/a&gt;. Please also check out
3982 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3983 contributors&lt;/a&gt;.&lt;/p&gt;
3984
3985 &lt;p&gt;The book is already available on paper in English, French and
3986 Japanese, and our goal is to get it available on paper in Norwegian
3987 Bokmål too. In addition to the paper edition, there are also EPUB and
3988 Mobi versions available. And there are incomplete translations
3989 available for many more languages.&lt;/p&gt;
3990 </description>
3991 </item>
3992
3993 <item>
3994 <title>One in two hundred Debian users using ZFS on Linux?</title>
3995 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
3996 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
3997 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
3998 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
3999 packages in Debian, and was quite surprised with what I found. I use
4000 ZFS myself at home, but did not really expect many others to do so.
4001 But I might be wrong.&lt;/p&gt;
4002
4003 &lt;p&gt;According to
4004 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
4005 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
4006 0.53% of the population, with the package installed. As far as I know
4007 the only use of the spl-linux package is as a support library for ZFS
4008 on Linux, so I use it here as proxy for measuring the number of ZFS
4009 installation on Linux in Debian. In the kFreeBSD variant of Debian
4010 the ZFS feature is already available, and there
4011 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
4012 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
4013 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
4014
4015 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
4016 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
4017 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
4018 cleared, the package is still not in Debian. The package is again in
4019 the NEW queue. Several uploads have been rejected so far because the
4020 debian/copyright file was incomplete or wrong, but there is no reason
4021 to give up. The current status can be seen on
4022 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
4023 team status page&lt;/a&gt;, and
4024 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
4025 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
4026
4027 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
4028 my home server can function in the future using only official Debian
4029 packages, and the current blocker is to get the debian/copyright file
4030 accepted by the FTP masters in Debian, I decided a while back to try
4031 to help out the team. This was the background for my blog post about
4032 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
4033 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
4034 used the techniques I explored there to try to find any errors in the
4035 copyright file. It is not very easy to check every one of the around
4036 2000 files in the source package, but I hope we this time got it
4037 right. If you want to help out, check out the git source and try to
4038 find missing entries in the debian/copyright file.&lt;/p&gt;
4039 </description>
4040 </item>
4041
4042 <item>
4043 <title>Full battery stats collector is now available in Debian</title>
4044 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
4045 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
4046 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
4047 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
4048 extended collector that will collect the complete battery history for
4049 later processing and graphing. The original collector store the
4050 battery level as percentage of last full level, while the new
4051 collector also record battery vendor, model, serial number, design
4052 full level, last full level and current battery level. This make it
4053 possible to predict the lifetime of the battery as well as visualise
4054 the energy flow when the battery is charging or discharging.&lt;/p&gt;
4055
4056 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
4057 in the version 0.5.1 package in unstable. Get the new battery level graph
4058 and lifetime prediction by running:
4059
4060 &lt;p&gt;&lt;pre&gt;
4061 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4062 &lt;/pre&gt;&lt;/p&gt;
4063
4064 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
4065
4066 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
4067 entry yet):&lt;/p&gt;
4068
4069 &lt;p&gt;&lt;pre&gt;
4070 /usr/share/battery-stats/battery-stats-graph-flow
4071 &lt;/pre&gt;&lt;/p&gt;
4072
4073 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
4074 when there are few data points. The graphs look a bit better with a
4075 few years of data.&lt;/p&gt;
4076
4077 &lt;p&gt;A while back one important feature I use in the battery stats
4078 collector broke in Debian. The scripts in
4079 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
4080 suspect it happened when Jessie started using systemd, but I do not
4081 know. The issue is reported as
4082 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
4083 pm-utils. I managed to work around it by adding an udev rule to call
4084 the collector script every time the power connector is connected and
4085 disconnected. With this fix in place it was finally time to make a
4086 new release of the package, and get it into Debian.&lt;/p&gt;
4087
4088 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4089 check out the
4090 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4091 in Debian unstable, or rebuild it on Jessie to get it working on
4092 Debian stable. :) The upstream source is available from
4093 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4094 As always, patches are very welcome.&lt;/p&gt;
4095 </description>
4096 </item>
4097
4098 <item>
4099 <title>Making battery measurements a little easier in Debian</title>
4100 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
4101 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
4102 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
4103 <description>&lt;p&gt;Back in September, I blogged about
4104 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
4105 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
4106 how it showed the decay and death of this battery (now replaced). I
4107 created a simple deb package to handle the collection and graphing,
4108 but did not want to upload it to Debian as there were already
4109 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
4110 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
4111 a point of uploading a competing package when battery-stats could be
4112 fixed instead. I reported a few bugs about its non-function, and
4113 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
4114
4115 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
4116 hands. The end result is that I am now the new upstream developer of
4117 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
4118 battery-stats in Debian, and the package in Debian unstable is finally
4119 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
4120 information provided by the Linux kernel. If you install the
4121 battery-stats package from unstable now, you will be able to get a
4122 graph of the current battery fill level, to get some idea about the
4123 status of the battery. The source package build and work just fine in
4124 Debian testing and stable (and probably oldstable too, but I have not
4125 tested). The default graph you get for that system look like this:&lt;/p&gt;
4126
4127 &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;
4128
4129 &lt;p&gt;My plans for the future is to merge my old scripts into the
4130 battery-stats package, as my old scripts collected a lot more details
4131 about the battery. The scripts are merged into the upstream
4132 battery-stats git repository already, but I am not convinced they work
4133 yet, as I changed a lot of paths along the way. Will have to test a
4134 bit more before I make a new release.&lt;/p&gt;
4135
4136 &lt;p&gt;I will also consider changing the file format slightly, as I
4137 suspect the way I combine several values into one field might make it
4138 impossible to know the type of the value when using it for processing
4139 and graphing.&lt;/p&gt;
4140
4141 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
4142 battery, check out the battery-stats package in
4143 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
4144 on
4145 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4146 I would love some help to improve the system further.&lt;/p&gt;
4147 </description>
4148 </item>
4149
4150 <item>
4151 <title>Creating, updating and checking debian/copyright semi-automatically</title>
4152 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
4153 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
4154 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
4155 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
4156 details. And one of the details is the content of the
4157 debian/copyright file, which should list all relevant licenses used by
4158 the code in the package in question, preferably in
4159 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
4160 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
4161
4162 &lt;p&gt;For large packages with lots of contributors it is hard to write
4163 and update this file manually, and if you get some detail wrong, the
4164 package is normally rejected by the ftpmasters. So getting it right
4165 the first time around get the package into Debian faster, and save
4166 both you and the ftpmasters some work.. Today, while trying to figure
4167 out what was wrong with
4168 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
4169 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
4170 figuring out the options for doing this job automatically, or at least
4171 semi-automatically.&lt;/p&gt;
4172
4173 &lt;p&gt;Lucikly, there are at least two tools available for generating the
4174 file based on the code in the source package,
4175 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
4176 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
4177 not sure which one of them came first, but both seem to be able to
4178 create a sensible draft file. As far as I can tell, none of them can
4179 be trusted to get the result just right, so the content need to be
4180 polished a bit before the file is OK to upload. I found the debmake
4181 option in
4182 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
4183 blog posts from 2014&lt;/a&gt;.
4184
4185 &lt;p&gt;To generate using debmake, use the -cc option:
4186
4187 &lt;p&gt;&lt;pre&gt;
4188 debmake -cc &gt; debian/copyright
4189 &lt;/pre&gt;&lt;/p&gt;
4190
4191 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
4192 this might not be the best option.&lt;/p&gt;
4193
4194 &lt;p&gt;The cme option is based on a config parsing library, and I found
4195 this approach in
4196 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
4197 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
4198 dpkg-copyright&#39; option:
4199
4200 &lt;p&gt;&lt;pre&gt;
4201 cme update dpkg-copyright
4202 &lt;/pre&gt;&lt;/p&gt;
4203
4204 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
4205 handle UTF-8 names better than debmake.&lt;/p&gt;
4206
4207 &lt;p&gt;When the copyright file is created, I would also like some help to
4208 check if the file is correct. For this I found two good options,
4209 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
4210 to focus on license types and file matching, and is able to detect
4211 ineffective blocks in the copyright file. The latter reports missing
4212 copyright holders and years, but was confused by inconsistent license
4213 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
4214 fix all issues reported by them before uploading. But I do not know
4215 if the tools and the ftpmasters agree on what is important to fix in a
4216 copyright file, so the package might still be rejected.&lt;/p&gt;
4217
4218 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
4219 will read through the source and try to find all copyright statements.
4220 It is not comparing the result to the content of debian/copyright, but
4221 can be useful when verifying the content of the copyright file.&lt;/p&gt;
4222
4223 &lt;p&gt;Are you aware of better tools in Debian to create and update
4224 debian/copyright file. Please let me know, or blog about it on
4225 planet.debian.org.&lt;/p&gt;
4226
4227 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4228 activities, please send Bitcoin donations to my address
4229 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4230
4231 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
4232 on how to use licensecheck and cdbs to create a draft copyright file
4233
4234 &lt;p&gt;&lt;pre&gt;
4235 licensecheck --copyright -r `find * -type f` | \
4236 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
4237 &lt;/pre&gt;&lt;/p&gt;
4238
4239 &lt;p&gt;He mentioned that he normally check the generated file into the
4240 version control system to make it easier to discover license and
4241 copyright changes in the upstream source. I will try to do the same
4242 with my packages in the future.&lt;/p&gt;
4243
4244 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
4245 against using -quiet for new users, so I removed it from the proposed
4246 command line.&lt;/p&gt;
4247 </description>
4248 </item>
4249
4250 <item>
4251 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
4252 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
4253 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
4254 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
4255 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
4256 is taking shape in Debian, and one provided feature is a very
4257 convenient way to tell you which package to install to make a given
4258 firmware file available when the kernel is looking for it. This can
4259 be done using apt-file too, but that is for someone else to blog
4260 about. :)&lt;/p&gt;
4261
4262 &lt;p&gt;Here is a small recipe to find the package with a given firmware
4263 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
4264 picked from the set of firmware announced using appstream in Debian
4265 unstable. In general you would be looking for the firmware requested
4266 by the kernel during kernel module loading. To find the package
4267 providing the example file, do like this:&lt;/p&gt;
4268
4269 &lt;blockquote&gt;&lt;pre&gt;
4270 % apt install appstream
4271 [...]
4272 % apt update
4273 [...]
4274 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
4275 awk &#39;/Package:/ {print $2}&#39;
4276 firmware-qlogic
4277 %
4278 &lt;/pre&gt;&lt;/blockquote&gt;
4279
4280 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
4281 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
4282 a way appstream can use.&lt;/p&gt;
4283
4284 &lt;p&gt;This same approach can be used to find any package supporting a
4285 given MIME type. This is very useful when you get a file you do not
4286 know how to handle. First find the mime type using &lt;tt&gt;file
4287 --mime-type&lt;/tt&gt;, and next look up the package providing support for
4288 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
4289 and you can find all packages handling this type like this:&lt;/p&gt;
4290
4291 &lt;blockquote&gt;&lt;pre&gt;
4292 % apt install appstream
4293 [...]
4294 % apt update
4295 [...]
4296 % appstreamcli what-provides mimetype image/svg+xml | \
4297 awk &#39;/Package:/ {print $2}&#39;
4298 bkchem
4299 phototonic
4300 inkscape
4301 shutter
4302 tetzle
4303 geeqie
4304 xia
4305 pinta
4306 gthumb
4307 karbon
4308 comix
4309 mirage
4310 viewnior
4311 postr
4312 ristretto
4313 kolourpaint4
4314 eog
4315 eom
4316 gimagereader
4317 midori
4318 %
4319 &lt;/pre&gt;&lt;/blockquote&gt;
4320
4321 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
4322 packages providing appstream metadata.&lt;/p&gt;
4323 </description>
4324 </item>
4325
4326 <item>
4327 <title>Creepy, visualise geotagged social media information - nice free software</title>
4328 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
4329 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
4330 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
4331 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
4332 with the computerised radio beacon known as a mobile phone their
4333 position is tracked by the phone company and often stored for a long
4334 time (like every time a SMS is received or sent). And if their
4335 computerised radio beacon is capable of running programs (often called
4336 mobile apps) downloaded from the Internet, these programs are often
4337 also capable of tracking their location (if the app requested access
4338 during installation). And when these programs send out information to
4339 central collection points, the location is often included, unless
4340 extra care is taken to not send the location. The provided
4341 information is used by several entities, for good and bad (what is
4342 good and bad, depend on your point of view). What is certain, is that
4343 the private sphere and the right to free movement is challenged and
4344 perhaps even eradicated for those announcing their location this way,
4345 when they share their whereabouts with private and public
4346 entities.&lt;/p&gt;
4347
4348 &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;
4349
4350 &lt;p&gt;The phone company logs provide a register of locations to check out
4351 when one want to figure out what the tracked person was doing. It is
4352 unavailable for most of us, but provided to selected government
4353 officials, company staff, those illegally buying information from
4354 unfaithful servants and crackers stealing the information. But the
4355 public information can be collected and analysed, and a free software
4356 tool to do so is called
4357 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
4358 discovered it when I read
4359 &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
4360 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
4361 November 2014, and decided to check if it was available in Debian.
4362 The python program was in Debian, but
4363 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
4364 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
4365 uploaded a new version which did not work quite right, but did not
4366 have time to fix it then. This Christmas I decided to finally try to
4367 get Creepy operational in Debian. Now a fixed version is available in
4368 Debian unstable and testing, and almost all Debian specific patches
4369 are now included
4370 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
4371
4372 &lt;p&gt;The Creepy program visualises geolocation information fetched from
4373 Twitter, Instagram, Flickr and Google+, and allow one to get a
4374 complete picture of every social media message posted recently in a
4375 given area, or track the movement of a given individual across all
4376 these services. Earlier it was possible to use the search API of at
4377 least some of these services without identifying oneself, but these
4378 days it is impossible. This mean that to use Creepy, you need to
4379 configure it to log in as yourself on these services, and provide
4380 information to them about your search interests. This should be taken
4381 into account when using Creepy, as it will also share information
4382 about yourself with the services.&lt;/p&gt;
4383
4384 &lt;p&gt;The picture above show the twitter messages sent from (or at least
4385 geotagged with a position from) the city centre of Oslo, the capital
4386 of Norway. One useful way to use Creepy is to first look at
4387 information tagged with an area of interest, and next look at all the
4388 information provided by one or more individuals who was in the area.
4389 I tested it by checking out which celebrity provide their location in
4390 twitter messages by checkout out who sent twitter messages near a
4391 Norwegian TV station, and next could track their position over time,
4392 making it possible to locate their home and work place, among other
4393 things. A similar technique have been
4394 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
4395 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
4396 tool to discover lying governments, and a useful tool to help people
4397 understand the value of the private information they provide to the
4398 public.&lt;/p&gt;
4399
4400 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
4401 it depend on several python modules currently missing in Jessie (at
4402 least python-instagram, python-flickrapi and
4403 python-requests-toolbelt).&lt;/p&gt;
4404
4405 &lt;p&gt;(I have uploaded
4406 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
4407 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
4408 Creepy program in Debian.)&lt;/p&gt;
4409 </description>
4410 </item>
4411
4412 <item>
4413 <title>Always download Debian packages using Tor - the simple recipe</title>
4414 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
4415 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
4416 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
4417 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
4418 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
4419 that those listening on the Internet lines would have good reason to
4420 believe a computer have a given security hole&lt;/a&gt; if it download a
4421 security fix from a Debian mirror. This is a good reason to always
4422 use encrypted connections to the Debian mirror, to make sure those
4423 listening do not know which IP address to attack. In August, Richard
4424 Hartmann observed that encryption was not enough, when it was possible
4425 to interfere download size to security patches or the fact that
4426 download took place shortly after a security fix was released, and
4427 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
4428 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
4429 was not the first to propose this, as the
4430 &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;
4431 package by Tim Retout already existed to make it easy to convince apt
4432 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
4433 aware of that package when I read the blog post from Richard.&lt;/p&gt;
4434
4435 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
4436 sysadmins, and he set up a Tor hidden service on one of the central
4437 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
4438 it possible to download packages directly between two tor nodes,
4439 making sure the network traffic always were encrypted.&lt;/p&gt;
4440
4441 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
4442 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
4443 urls with tor+http and tor+https, and using the hidden service instead
4444 of the official Debian mirror site. I recommend installing
4445 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
4446 done in /etc/.&lt;/p&gt;
4447
4448 &lt;blockquote&gt;&lt;pre&gt;
4449 apt install apt-transport-tor
4450 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
4451 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
4452 &lt;/pre&gt;&lt;/blockquote&gt;
4453
4454 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
4455 the sed commands for these too. The sed command is assuming your are
4456 using the ftp.debian.org Debian mirror. Adjust the command (or just
4457 edit the file manually) to match your mirror.&lt;/p&gt;
4458
4459 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
4460 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
4461 system, and do not work with these tor+http URLs. For
4462 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
4463 which need a recent apt version currently only in unstable. So if you
4464 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
4465
4466 &lt;p&gt;Another advantage from this change is that your machine will start
4467 using Tor regularly and at fairly random intervals (every time you
4468 update the package lists or upgrade or install a new package), thus
4469 masking other Tor traffic done from the same machine. Using Tor will
4470 become normal for the machine in question.&lt;/p&gt;
4471
4472 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
4473 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
4474 enabled. It would be great if it was the default on any Debian
4475 system.&lt;/p&gt;
4476 </description>
4477 </item>
4478
4479 <item>
4480 <title>OpenALPR, find car license plates in video streams - nice free software</title>
4481 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
4482 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
4483 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
4484 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
4485 call the car license plate numbers in those days. I would write the
4486 numbers down in my little book and compare notes with the other kids
4487 to see how many region codes we had seen and if we had seen some
4488 exotic or special region codes and numbers. It was a fun game to pass
4489 time, as we kids have plenty of it.&lt;/p&gt;
4490
4491 &lt;p&gt;A few days I came across
4492 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
4493 project&lt;/a&gt;, a free software project to automatically discover and
4494 report license plates in images and video streams, and provide the
4495 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
4496 such system for a while now, because I believe it is a bad idea that the
4497 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
4498 number plate recognition&lt;/a&gt; tool only is available in the hands of
4499 the powerful, and want it to be available also for the powerless to
4500 even the score when it comes to surveillance and sousveillance. I
4501 discovered the developer
4502 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
4503 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
4504 help him get it into shape to get the package uploaded into the Debian
4505 archive.&lt;/p&gt;
4506
4507 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
4508 it into Debian, where it currently
4509 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
4510 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
4511
4512 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
4513 for the common folks, ie those not running a large government
4514 surveillance system? Well, I plan to put it in a computer on my bike
4515 and in my car, tracking the cars nearby and allowing me to be notified
4516 when number plates on my watch list are discovered. Another use case
4517 was suggested by a friend of mine, who wanted to set it up at his home
4518 to open the car port automatically when it discovered the plate on his
4519 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
4520 capable of placing his license plate number of a piece of cardboard to
4521 open his car port, men replied that it was always unlocked anyway. I
4522 guess for such use case it make sense. I am sure there are other use
4523 cases too, for those with imagination and a vision.&lt;/p&gt;
4524
4525 &lt;p&gt;If you want to build your own version of the Debian package, check
4526 out the upstream git source and symlink ./distros/debian to ./debian/
4527 before running &quot;debuild&quot; to build the source. Or wait a bit until the
4528 package show up in unstable.&lt;/p&gt;
4529 </description>
4530 </item>
4531
4532 <item>
4533 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
4534 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
4535 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
4536 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
4537 <description>&lt;p&gt;Around three years ago, I created
4538 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
4539 system&lt;/a&gt; to get a more practical solution in Debian for handing
4540 hardware related packages. A GUI system in the isenkram package will
4541 present a pop-up dialog when some hardware dongle supported by
4542 relevant packages in Debian is inserted into the machine. The same
4543 lookup mechanism to detect packages is available as command line
4544 tools in the isenkram-cli package. In addition to mapping hardware,
4545 it will also map kernel firmware files to packages and make it easy to
4546 install needed firmware packages automatically. The key for this
4547 system to work is a good way to map hardware to packages, in other
4548 words, allow packages to announce what hardware they will work
4549 with.&lt;/p&gt;
4550
4551 &lt;p&gt;I started by providing data files in the isenkram source, and
4552 adding code to download the latest version of these data files at run
4553 time, to ensure every user had the most up to date mapping available.
4554 I also added support for storing the mapping in the Packages file in
4555 the apt repositories, but did not push this approach because while I
4556 was trying to figure out how to best store hardware/package mappings,
4557 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
4558 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
4559 add the hardware mapping into that data set to be able to use
4560 appstream as a data source, and this was accepted at least for the
4561 Debian version of appstream.&lt;/p&gt;
4562
4563 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
4564 and today I uploaded a new version 0.20 of isenkram adding support for
4565 appstream as a data source for mapping hardware to packages. The only
4566 package so far using appstream to announce its hardware support is my
4567 pymissile package. I got help from Matthias Klumpp with figuring out
4568 how do add the required
4569 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
4570 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
4571 this content:&lt;/p&gt;
4572
4573 &lt;blockquote&gt;&lt;pre&gt;
4574 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
4575 &amp;lt;component&amp;gt;
4576 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
4577 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
4578 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
4579 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
4580 &amp;lt;description&amp;gt;
4581 &amp;lt;p&amp;gt;
4582 Pymissile provides a curses interface to control an original
4583 Marks and Spencer / Striker USB Missile Launcher, as well as a
4584 motion control script to allow a webcamera to control the
4585 launcher.
4586 &amp;lt;/p&amp;gt;
4587 &amp;lt;/description&amp;gt;
4588 &amp;lt;provides&amp;gt;
4589 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
4590 &amp;lt;/provides&amp;gt;
4591 &amp;lt;/component&amp;gt;
4592 &lt;/pre&gt;&lt;/blockquote&gt;
4593
4594 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
4595 which is a glob style match rule for hardware specific strings
4596 (modalias strings) provided by the Linux kernel. In this case, it
4597 will map to all USB devices with vendor code 1130 and product code
4598 0202.&lt;/p&gt;
4599
4600 &lt;p&gt;Note, it is important that the license of all the metadata files
4601 are compatible to have permissions to aggregate them into archive wide
4602 appstream files. Matthias suggested to use MIT or BSD licenses for
4603 these files. A challenge is figuring out a good id for the data, as
4604 it is supposed to be globally unique and shared across distributions
4605 (in other words, best to coordinate with upstream what to use). But
4606 it can be changed later or, so we went with the package name as
4607 upstream for this project is dormant.&lt;/p&gt;
4608
4609 &lt;p&gt;To get the metadata file installed in the correct location for the
4610 mirror update scripts to pick it up and include its content the
4611 appstream data source, the file must be installed in the binary
4612 package under /usr/share/appdata/. I did this by adding the following
4613 line to debian/pymissile.install:&lt;/p&gt;
4614
4615 &lt;blockquote&gt;&lt;pre&gt;
4616 debian/pymissile.metainfo.xml usr/share/appdata
4617 &lt;/pre&gt;&lt;/blockquote&gt;
4618
4619 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
4620 all packages useful on the current computer automatically, and the GUI
4621 pop-up handler will propose to install the package not already
4622 installed if a hardware dongle is inserted into the machine in
4623 question.&lt;/p&gt;
4624
4625 &lt;p&gt;Details of the modalias field in appstream is available from the
4626 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
4627
4628 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
4629 try running this command on the command line:&lt;/p&gt;
4630
4631 &lt;blockquote&gt;&lt;pre&gt;
4632 cat $(find /sys/devices/|grep modalias)
4633 &lt;/pre&gt;&lt;/blockquote&gt;
4634
4635 &lt;p&gt;To learn more about the isenkram system, please check out
4636 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
4637 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
4638 </description>
4639 </item>
4640
4641 <item>
4642 <title>The GNU General Public License is not magic pixie dust</title>
4643 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
4644 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
4645 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
4646 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
4647 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
4648 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
4649 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
4650 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
4651
4652 &lt;blockquote&gt;
4653
4654 &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;
4655
4656 &lt;blockquote&gt;
4657 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
4658
4659 The first step is to choose a
4660 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
4661 code.&lt;br/&gt;
4662
4663 The next step is, when someone fails to follow that copyleft license,
4664 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
4665
4666 and its a simple fact of our modern society that such type of
4667 work&lt;br/&gt;
4668
4669 is incredibly expensive to do and incredibly difficult to do.
4670 &lt;/blockquote&gt;
4671
4672 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
4673 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
4674 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
4675 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
4676
4677 &lt;p&gt;As the Debian Website
4678 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
4679 &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;
4680 imply, public domain and permissively licensed software can lead to
4681 the production of more proprietary software as people discover useful
4682 software, extend it and or incorporate it into their hardware or
4683 software products. Copyleft licenses such as the GNU GPL were created
4684 to close off this avenue to the production of proprietary software but
4685 such licenses are not enough. With the ongoing adoption of Free
4686 Software by individuals and groups, inevitably the community&#39;s
4687 expectations of license compliance are violated, usually out of
4688 ignorance of the way Free Software works, but not always. As Karen
4689 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
4690 Freedom&quot;&gt;FaiF&lt;/a&gt;
4691 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
4692 copyleft is nothing if no-one is willing and able to stand up in court
4693 to protect it. The reality of today&#39;s world is that legal
4694 representation is expensive, difficult and time consuming. With
4695 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
4696 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
4697 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
4698 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
4699 of the Linux project, Debian and other groups against GPL violations.
4700 In March the SFC supported a
4701 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
4702 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
4703 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
4704 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
4705 kernel. Since then two of their sponsors pulled corporate funding and
4706 conferences
4707 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
4708 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
4709 less on corporate funding and more on the broad community of
4710 individuals who support Free Software and copyleft. So the SFC has
4711 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
4712 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
4713 a community of folks who stand up for copyleft and the GPL by
4714 supporting their work on promoting and supporting copyleft and Free
4715 Software.&lt;/p&gt;
4716
4717 &lt;p&gt;If you support Free Software,
4718 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
4719 what the SFC do, agree with their
4720 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
4721 principles&lt;/a&gt;, are happy about their
4722 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
4723 work on a project that is an SFC
4724 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
4725 just want to stand up for copyleft, please join
4726 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
4727 Allan Webber&lt;/a&gt;,
4728 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
4729 Smith&lt;/a&gt;,
4730 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
4731 Bacon&lt;/a&gt;, myself and
4732 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
4733 becoming a
4734 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
4735 next week your donation will be
4736 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
4737 by an anonymous donor. Please also consider asking your employer to
4738 match your donation or become a sponsor of SFC. Don&#39;t forget to
4739 spread the word about your support for SFC via email, your blog and or
4740 social media accounts.&lt;/p&gt;
4741
4742 &lt;/blockquote&gt;
4743
4744 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
4745 of Software Freedom Conservancy myself. Perhaps you should be a
4746 supporter too?&lt;/p&gt;
4747 </description>
4748 </item>
4749
4750 <item>
4751 <title>PGP key transition statement for key EE4E02F9</title>
4752 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
4753 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
4754 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
4755 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
4756 set it up properly. I wanted to generate it offline and have it
4757 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
4758 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
4759 time to sit down with an offline machine almost took forever. But
4760 finally I&#39;ve been able to complete the process, and have now moved
4761 from my old GPG key to a new GPG key. See
4762 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
4763 full transition statement, signed with both my old and new key&lt;/a&gt; for
4764 the details. This is my new key:&lt;/p&gt;
4765
4766 &lt;pre&gt;
4767 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]
4768 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
4769 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
4770 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
4771 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
4772 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
4773 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
4774 &lt;/pre&gt;
4775
4776 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
4777 my old key.&lt;/p&gt;
4778
4779 &lt;p&gt;If you signed my old key
4780 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
4781 I&#39;d very much appreciate a signature on my new key, details and
4782 instructions in the transition statement. I m happy to reciprocate if
4783 you have a similarly signed transition statement to present.&lt;/p&gt;
4784 </description>
4785 </item>
4786
4787 <item>
4788 <title>The life and death of a laptop battery</title>
4789 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
4790 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
4791 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
4792 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
4793 But this do not last. The last few laptops gave me a feeling that
4794 within a year, the life time is just a fraction of what it used to be,
4795 and it slowly become painful to use the laptop without power connected
4796 all the time. Because of this, when I got a new Thinkpad X230 laptop
4797 about two years ago, I decided to monitor its battery state to have
4798 more hard facts when the battery started to fail.&lt;/p&gt;
4799
4800 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
4801
4802 &lt;p&gt;First I tried to find a sensible Debian package to record the
4803 battery status, assuming that this must be a problem already handled
4804 by someone else. I found
4805 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
4806 which collects statistics from the battery, but it was completely
4807 broken. I sent a few suggestions to the maintainer, but decided to
4808 write my own collector as a shell script while I waited for feedback
4809 from him. Via
4810 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
4811 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
4812 discovered
4813 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
4814 available in Debian.&lt;/p&gt;
4815
4816 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
4817 battery stats ever since. Now my
4818 /var/log/hjemmenett-battery-status.log file contain around 115,000
4819 measurements, from the time the battery was working great until now,
4820 when it is unable to charge above 7% of original capacity. My
4821 collector shell script is quite simple and look like this:&lt;/p&gt;
4822
4823 &lt;pre&gt;
4824 #!/bin/sh
4825 # Inspired by
4826 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
4827 # See also
4828 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
4829 logfile=/var/log/hjemmenett-battery-status.log
4830
4831 files=&quot;manufacturer model_name technology serial_number \
4832 energy_full energy_full_design energy_now cycle_count status&quot;
4833
4834 if [ ! -e &quot;$logfile&quot; ] ; then
4835 (
4836 printf &quot;timestamp,&quot;
4837 for f in $files; do
4838 printf &quot;%s,&quot; $f
4839 done
4840 echo
4841 ) &gt; &quot;$logfile&quot;
4842 fi
4843
4844 log_battery() {
4845 # Print complete message in one echo call, to avoid race condition
4846 # when several log processes run in parallel.
4847 msg=$(printf &quot;%s,&quot; $(date +%s); \
4848 for f in $files; do \
4849 printf &quot;%s,&quot; $(cat $f); \
4850 done)
4851 echo &quot;$msg&quot;
4852 }
4853
4854 cd /sys/class/power_supply
4855
4856 for bat in BAT*; do
4857 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
4858 done
4859 &lt;/pre&gt;
4860
4861 &lt;p&gt;The script is called when the power management system detect a
4862 change in the power status (power plug in or out), and when going into
4863 and out of hibernation and suspend. In addition, it collect a value
4864 every 10 minutes. This make it possible for me know when the battery
4865 is discharging, charging and how the maximum charge change over time.
4866 The code for the Debian package
4867 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
4868 available on github&lt;/a&gt;.&lt;/p&gt;
4869
4870 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
4871
4872 &lt;pre&gt;
4873 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
4874 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
4875 [...]
4876 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
4877 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
4878 &lt;/pre&gt;
4879
4880 &lt;p&gt;I wrote a small script to create a graph of the charge development
4881 over time. This graph depicted above show the slow death of my laptop
4882 battery.&lt;/p&gt;
4883
4884 &lt;p&gt;But why is this happening? Why are my laptop batteries always
4885 dying in a year or two, while the batteries of space probes and
4886 satellites keep working year after year. If we are to believe
4887 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
4888 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
4889 chance, and the fix is to not charge the Lithium-ion batteries to 100%
4890 all the time, but to stay below 90% of full charge most of the time.
4891 I&#39;ve been told that the Tesla electric cars
4892 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
4893 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
4894 100% when preparing for a longer trip (not that I would want a car
4895 like Tesla where rights to privacy is abandoned, but that is another
4896 story), which I guess is the option we should have for laptops on
4897 Linux too.&lt;/p&gt;
4898
4899 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
4900 stop charging at 80%, unless requested to charge to 100% once in
4901 preparation for a longer trip? I found
4902 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
4903 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
4904 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
4905 load).&lt;/p&gt;
4906
4907 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
4908 at the start. I also wonder why the &quot;full capacity&quot; increases some
4909 times, and if it is possible to repeat the process to get the battery
4910 back to design capacity. And I wonder if the discharge and charge
4911 speed change over time, or if this stay the same. I did not yet try
4912 to write a tool to calculate the derivative values of the battery
4913 level, but suspect some interesting insights might be learned from
4914 those.&lt;/p&gt;
4915
4916 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
4917 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
4918 packages instead of the tp-smapi-dkms package I had tried to use
4919 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
4920 and stop. I&#39;ve done so now, but expect my existing battery is toast
4921 and need to be replaced. The proposal is unfortunately Thinkpad
4922 specific.&lt;/p&gt;
4923 </description>
4924 </item>
4925
4926 <item>
4927 <title>New laptop - some more clues and ideas based on feedback</title>
4928 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
4929 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
4930 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
4931 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
4932 need for a new laptop, and provided very useful feedback. I wish to
4933 thank every one of these. Several pointed me to the possibility of
4934 fixing my X230, and I am already in the process of getting Lenovo to
4935 do so thanks to the on site, next day support contract covering the
4936 machine. But the battery is almost useless (I expect to replace it
4937 with a non-official battery) and I do not expect the machine to live
4938 for many more years, so it is time to plan its replacement. If I did
4939 not have a support contract, it was suggested to find replacement parts
4940 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
4941 might present a language barrier as I do not understand French.&lt;/p&gt;
4942
4943 &lt;p&gt;One tip I got was to use the
4944 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
4945 compare laptop models. It seem to have more models available than
4946 prisjakt.no. Another tip I got from someone I know have similar
4947 keyboard preferences was that the HP EliteBook 840 keyboard is not
4948 very good, and this matches my experience with earlier EliteBook
4949 keyboards I tested. Because of this, I will not consider it any further.
4950
4951 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
4952 newest Thinkpad X model. The keyboard reintroduces mouse buttons
4953 (which is missing from the X240), and is working fairly well with
4954 Debian Sid/Unstable according to
4955 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
4956 got on the keyboard quality are not consistent. Some say the keyboard
4957 is good, others say it is ok, while others say it is not very good.
4958 Those with experience from X41 and and X60 agree that the X250
4959 keyboard is not as good as those trusty old laptops, and suggest I
4960 keep and fix my X230 instead of upgrading, or get a used X230 to
4961 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
4962 activity and battery status, which is very convenient on my X230. I&#39;m
4963 also told that the CPU fan is running very often, making it a bit
4964 noisy. In any case, the X250 do not work out of the box with Debian
4965 Stable/Jessie, one of my requirements.&lt;/p&gt;
4966
4967 &lt;p&gt;I have also gotten a few vendor proposals, one was
4968 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
4969 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
4970 The latter look very attractive to me.&lt;/p&gt;
4971
4972 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
4973 as I keep looking for a replacement.&lt;/p&gt;
4974
4975 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
4976 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
4977 different
4978 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
4979 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
4980 </description>
4981 </item>
4982
4983 <item>
4984 <title>Time to find a new laptop, as the old one is broken after only two years</title>
4985 <link>https://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</link>
4986 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_find_a_new_laptop__as_the_old_one_is_broken_after_only_two_years.html</guid>
4987 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
4988 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
4989 replacement soon. The left 5 cm of the screen on my Thinkpad X230
4990 started flickering yesterday, and I suspect the cause is a broken
4991 cable, as changing the angle of the screen some times get rid of the
4992 flickering.&lt;/p&gt;
4993
4994 &lt;p&gt;My requirements have not really changed since I bought it, and is
4995 still as
4996 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
4997 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
4998 good help from
4999 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
5000 where I could select at least a few of the requirements (mouse pin,
5001 wifi, weight) and go through the rest manually. Three button mouse
5002 and a good keyboard is not available as an option, and all the three
5003 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
5004 G2) lack three mouse buttons). It is also unclear to me how good the
5005 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5006 the keyboard, even if the quality and robustness in the X series have
5007 deteriorated since X41.&lt;/p&gt;
5008
5009 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
5010 seem sensible to me? Are there better services around to search the
5011 set of available laptops for features? Please send me an email if you
5012 have suggestions.&lt;/p&gt;
5013
5014 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
5015 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
5016 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
5017 </description>
5018 </item>
5019
5020 <item>
5021 <title>How to stay with sysvinit in Debian Jessie</title>
5022 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
5023 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
5024 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
5025 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
5026 sysvinit as its boot system by default. But how can one keep using
5027 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5028 courtesy of
5029 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
5030 Schubert&lt;/a&gt; and
5031 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
5032 McVittie&lt;/a&gt;.
5033
5034 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
5035 keep sysvinit as your boot system, create a file
5036 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
5037 you upgrade:&lt;/p&gt;
5038
5039 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5040 Package: systemd-sysv
5041 Pin: release o=Debian
5042 Pin-Priority: -1
5043 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5044
5045 &lt;p&gt;This file content will tell apt and aptitude to not consider
5046 installing systemd-sysv as part of any installation and upgrade
5047 solution when resolving dependencies, and thus tell it to avoid
5048 systemd as a default boot system. The end result should be that the
5049 upgraded system keep using sysvinit.&lt;/p&gt;
5050
5051 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
5052 get sysvinit installed by default (debootstrap used by
5053 debian-installer have no option for this), but one can tell the
5054 installer to switch to sysvinit before the first boot. Either by
5055 using a kernel argument to the installer, or by adding a line to the
5056 preseed file used. First, the kernel command line argument:
5057
5058 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5059 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
5060 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5061
5062 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
5063
5064 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5065 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5066 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
5067
5068 &lt;p&gt;One can of course also do this after the first boot by installing
5069 the sysvinit-core package.&lt;/p&gt;
5070
5071 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
5072 sysvinit boot sequence in Debian have several hardware specific bugs
5073 on Linux caused by the fact that it is unpredictable when hardware
5074 devices show up during boot. But on the other hand, the new default
5075 boot system still have a few rough edges I hope will be fixed before
5076 Jessie is released.&lt;/p&gt;
5077
5078 &lt;p&gt;Update 2014-11-26: Inspired by
5079 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
5080 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
5081 line.&lt;/p&gt;
5082 </description>
5083 </item>
5084
5085 <item>
5086 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
5087 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
5088 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
5089 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
5090 <description>&lt;p&gt;The right to communicate with your friends and family in private,
5091 without anyone snooping, is a right every citicen have in a liberal
5092 democracy. But this right is under serious attack these days.&lt;/p&gt;
5093
5094 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
5095 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5096 the whisleblower Snowden) more expensive for Internet email,
5097 is to deliver all email using SMTP via Tor. Such SMTP option would be
5098 a nice addition to the FreedomBox project if we could send email
5099 between FreedomBox machines without leaking metadata about the emails
5100 to the people peeking on the wire. I
5101 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
5102 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
5103 lot of useful feedback and suggestions. It also became obvious to me
5104 that this was not a novel idea, as the same idea was tested and
5105 documented by Johannes Berg as early as 2006, and both
5106 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
5107 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
5108 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
5109
5110 &lt;p&gt;To implement such system one need to set up a Tor hidden service
5111 providing the SMTP protocol on port 25, and use email addresses
5112 looking like username@hidden-service-name.onion. With such addresses
5113 the connections to port 25 on hidden-service-name.onion using Tor will
5114 go to the correct SMTP server. To do this, one need to configure the
5115 Tor daemon to provide the hidden service and the mail server to accept
5116 emails for this .onion domain. To learn more about Exim configuration
5117 in Debian and test the design provided by Johannes Berg in his FAQ, I
5118 set out yesterday to create a Debian package for making it trivial to
5119 set up such SMTP over Tor service based on Debian. Getting it to work
5120 were fairly easy, and
5121 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
5122 source code for the Debian package&lt;/a&gt; is available from github. I
5123 plan to move it into Debian if further testing prove this to be a
5124 useful approach.&lt;/p&gt;
5125
5126 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
5127 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
5128 get rid of exim4). Install tor, clone the git repository mentioned
5129 above, build the deb and install it on the machine. Next, run
5130 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
5131 the instructions to get the service up and running. Restart tor and
5132 exim when it is done, and test mail delivery using swaks like
5133 this:&lt;/p&gt;
5134
5135 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5136 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5137 --to fbx@dutlqrrmjhtfa3vp.onion
5138 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5139
5140 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
5141 address with your own address to test your server. :)&lt;/p&gt;
5142
5143 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
5144 easier and more automatic. Especially the tor setup need more work.
5145 Also, the package include a tor-smtp tool written in C, but its task
5146 should probably be rewritten in some script language to make the deb
5147 architecture independent. It would probably also make the code easier
5148 to review. The tor-smtp tool currently need to listen on a socket for
5149 exim to talk to it and is started using xinetd. It would be better if
5150 no daemon and no socket is needed. I suspect it is possible to get
5151 exim to run a command line tool for delivery instead of talking to a
5152 socket, and hope to figure out how in a future version of this
5153 system.&lt;/p&gt;
5154
5155 &lt;p&gt;Until I wipe my test machine, I can be reached using the
5156 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
5157 SMTorP. :)&lt;/p&gt;
5158 </description>
5159 </item>
5160
5161 <item>
5162 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
5163 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
5164 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
5165 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
5166 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
5167 alioth.debian.org, you know the web interface is fairly slow to
5168 operate. First you visit one web page, enter the moderation password
5169 and get a new page shown with a list of all the messages to moderate
5170 and various options for each email address. This take a while for
5171 every list you moderate, and you need to do it regularly to do a good
5172 job as a list moderator. But there is a quick alternative,
5173 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
5174 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
5175 to moderate in a fraction of a second. Here is a test run on two
5176 lists I recently took over:&lt;/p&gt;
5177
5178 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5179 % time listadmin xiph
5180 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5181 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5182
5183 real 0m1.709s
5184 user 0m0.232s
5185 sys 0m0.012s
5186 %
5187 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5188
5189 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
5190 there are no message in the moderation queue. Every morning I
5191 currently moderate 68 mailman lists, and it normally take around two
5192 minutes. When I took over the two pkg-xiph lists above a few days
5193 ago, there were 400 emails waiting in the moderator queue. It took me
5194 less than 15 minutes to process them all using the listadmin
5195 program.&lt;/p&gt;
5196
5197 &lt;p&gt;If you install
5198 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
5199 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
5200 with content like this, the moderation task is a breeze:&lt;/p&gt;
5201
5202 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5203 username username@example.org
5204 spamlevel 23
5205 default discard
5206 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
5207
5208 password secret
5209 adminurl https://{domain}/mailman/admindb/{list}
5210 mailman-list@lists.example.com
5211
5212 password hidden
5213 other-list@otherserver.example.org
5214 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5215
5216 &lt;p&gt;There are other options to set as well. Check the manual page to
5217 learn the details.&lt;/p&gt;
5218
5219 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
5220 the SSL certificate is self signed or not properly signed by a
5221 generally accepted signing authority, you can set a environment
5222 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
5223
5224 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5225 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
5226 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5227
5228 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
5229 can provide an argument to the listadmin script like I do in the
5230 initial screen dump (the xiph argument). Using an argument, only
5231 lists matching the argument string will be processed. This make it
5232 quick to accept messages if you notice the moderation request in your
5233 email.&lt;/p&gt;
5234
5235 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
5236 mailing lists, as I simply do not have time to spend on that if the
5237 process was any slower. The listadmin program have saved me hours of
5238 time I could spend elsewhere over the years. It truly is nice free
5239 software.&lt;/p&gt;
5240
5241 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5242 activities, please send Bitcoin donations to my address
5243 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5244
5245 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
5246 configuration example. Also, I&#39;ve been told that the
5247 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
5248 sure why.&lt;/p&gt;
5249 </description>
5250 </item>
5251
5252 <item>
5253 <title>Debian Jessie, PXE and automatic firmware installation</title>
5254 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
5255 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
5256 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
5257 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
5258 problem that the WiFi card require some firmware to work properly.
5259 And it has been a pain to fix this using preseeding in Debian.
5260 Normally something more is needed. But thanks to
5261 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
5262 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
5263 to do this using simple preseeding.&lt;/p&gt;
5264
5265 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
5266 firmware for the hardware found in the machine (actually, requested by
5267 the kernel modules for the hardware). (It can also install user space
5268 programs supporting the hardware detected, but that is not the focus
5269 of this story.)&lt;/p&gt;
5270
5271 &lt;p&gt;To get this working in the default installation, two preeseding
5272 values are needed. First, the isenkram-cli package must be installed
5273 into the target chroot (aka the hard drive) before tasksel is executed
5274 in the pkgsel step of the debian-installer system. This is done by
5275 preseeding the base-installer/includes debconf value to include the
5276 isenkram-cli package. The package name is next passed to debootstrap
5277 for installation. With the isenkram-cli package in place, tasksel
5278 will automatically use the isenkram tasks to detect hardware specific
5279 packages for the machine being installed and install them, because
5280 isenkram-cli contain tasksel tasks.&lt;/p&gt;
5281
5282 &lt;p&gt;Second, one need to enable the non-free APT repository, because
5283 most firmware unfortunately is non-free. This is done by preseeding
5284 the apt-mirror-setup step. This is unfortunate, but for a lot of
5285 hardware it is the only option in Debian.&lt;/p&gt;
5286
5287 &lt;p&gt;The end result is two lines needed in your preseeding file to get
5288 firmware installed automatically by the installer:&lt;/p&gt;
5289
5290 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5291 base-installer base-installer/includes string isenkram-cli
5292 apt-mirror-setup apt-setup/non-free boolean true
5293 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5294
5295 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
5296 both firmware and user space packages when using this method. It also
5297 do not work well, so use version 0.15 or later. Installing both
5298 firmware and user space packages might give you a bit more than you
5299 want, so I decided to split the tasksel task in two, one for firmware
5300 and one for user space programs. The firmware task is enabled by
5301 default, while the one for user space programs is not. This split is
5302 implemented in the package currently in unstable.&lt;/p&gt;
5303
5304 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
5305 this recipe work for you. :)&lt;/p&gt;
5306
5307 &lt;p&gt;So, I bet you are wondering, how can this work. First and
5308 foremost, it work because tasksel is modular, and driven by whatever
5309 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
5310 isenkram-cli package place two files for tasksel to find. First there
5311 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
5312
5313 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5314 Task: isenkram-packages
5315 Section: hardware
5316 Description: Hardware specific packages (autodetected by isenkram)
5317 Based on the detected hardware various hardware specific packages are
5318 proposed.
5319 Test-new-install: show show
5320 Relevance: 8
5321 Packages: for-current-hardware
5322
5323 Task: isenkram-firmware
5324 Section: hardware
5325 Description: Hardware specific firmware packages (autodetected by isenkram)
5326 Based on the detected hardware various hardware specific firmware
5327 packages are proposed.
5328 Test-new-install: mark show
5329 Relevance: 8
5330 Packages: for-current-hardware-firmware
5331 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5332
5333 &lt;p&gt;The key parts are Test-new-install which indicate how the task
5334 should be handled and the Packages line referencing to a script in
5335 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
5336 list of packages to install. The for-current-hardware-firmware script
5337 look like this to list relevant firmware for the machine:
5338
5339 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5340 #!/bin/sh
5341 #
5342 PATH=/usr/sbin:$PATH
5343 export PATH
5344 isenkram-autoinstall-firmware -l
5345 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5346
5347 &lt;p&gt;With those two pieces in place, the firmware is installed by
5348 tasksel during the normal d-i run. :)&lt;/p&gt;
5349
5350 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
5351 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
5352 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
5353 install.&lt;/p&gt;
5354
5355 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
5356 pilots in testing this feature, as isenkram is used there now to
5357 install firmware, replacing the earlier scripts.&lt;/p&gt;
5358 </description>
5359 </item>
5360
5361 <item>
5362 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
5363 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
5364 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
5365 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
5366 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
5367 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
5368 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
5369 on a screen normally showing the bread types and prizes:&lt;/p&gt;
5370
5371 &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;
5372
5373 &lt;p&gt;If it had booted as it was supposed to, I would never had known
5374 about this hidden Linux installation. It is interesting what
5375 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
5376 </description>
5377 </item>
5378
5379 <item>
5380 <title>New lsdvd release version 0.17 is ready</title>
5381 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
5382 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
5383 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
5384 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
5385 got a new set of developers a few weeks ago, after the original
5386 developer decided to step down and pass the project to fresh blood.
5387 This project is now maintained by Petter Reinholdtsen and Steve
5388 Dibb.&lt;/p&gt;
5389
5390 &lt;p&gt;I just wrapped up
5391 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
5392 new lsdvd release&lt;/a&gt;, available in git or from
5393 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
5394 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
5395 0.17.&lt;/p&gt;
5396
5397 &lt;ul&gt;
5398
5399 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
5400 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
5401 non-existant, to work around additional copy protection&lt;/li&gt;
5402 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
5403 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
5404 &lt;li&gt;Fix include orders&lt;/li&gt;
5405 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
5406 &lt;li&gt;Fix the chapter count&lt;/li&gt;
5407 &lt;li&gt;Make sure the array size and the array limit used when initialising
5408 the palette size is the same.&lt;/li&gt;
5409 &lt;li&gt;Fix array printing.&lt;/li&gt;
5410 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
5411 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
5412 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
5413 with more GCC compiler warnings.&lt;/li&gt;
5414
5415 &lt;/ul&gt;
5416
5417 &lt;p&gt;This change bring together patches for lsdvd in use in various
5418 Linux and Unix distributions, as well as patches submitted to the
5419 project the last nine years. Please check it out. :)&lt;/p&gt;
5420 </description>
5421 </item>
5422
5423 <item>
5424 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
5425 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
5426 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
5427 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
5428 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
5429 project&lt;/a&gt; provide a Linux solution for schools, including a
5430 powerful desktop with education software, a central server providing
5431 web pages, user database, user home directories, central login and PXE
5432 boot of both clients without disk and the installation to install Debian
5433 Edu on machines with disk (and a few other services perhaps to small
5434 to mention here). We in the Debian Edu team are currently working on
5435 the Jessie based version, trying to get everything in shape before the
5436 freeze, to avoid having to maintain our own package repository in the
5437 future. The
5438 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
5439 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
5440 work left. Some fatal problems block testing, breaking the installer,
5441 but it is possible to work around these to get anyway. Here is a
5442 recipe on how to get the installation limping along.&lt;/p&gt;
5443
5444 &lt;p&gt;First, download the test ISO via
5445 &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;,
5446 &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;
5447 or rsync (use
5448 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
5449 The ISO build was broken on Tuesday, so we do not get a new ISO every
5450 12 hours or so, but thankfully the ISO we already got we are able to
5451 install with some tweaking.&lt;/p&gt;
5452
5453 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
5454 (use Alt-Ctrl-F2), run&lt;/p&gt;
5455
5456 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5457 nano /usr/bin/edu-eatmydata-install
5458 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5459
5460 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
5461 optimization. Return to the installation, select the profile you want
5462 and continue. Without this change, exim4-config will fail to install
5463 due to a known bug in eatmydata.&lt;/p&gt;
5464
5465 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
5466 this do not work, figure out what your correct value would be. All my
5467 test machines need /dev/sda, so I have no advice if it do not fit
5468 your need.&lt;/p&gt;
5469
5470 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
5471 root after the initial boot from hard drive, and install the
5472 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
5473 or mate. If you want several desktop options, install more than one
5474 metapackage. Once this is done, reboot and you should have a working
5475 graphical login screen. This workaround should no longer be needed
5476 once the education-tasks package version 1.801 enter testing in two
5477 days.&lt;/p&gt;
5478
5479 &lt;p&gt;I believe the ISO build will start working on two days when the new
5480 tasksel package enter testing and Steve McIntyre get a chance to
5481 update the debian-cd git repository. The eatmydata, grub and desktop
5482 issues are already fixed in unstable and testing, and should show up
5483 on the ISO as soon as the ISO build start working again. Well the
5484 eatmydata optimization is really just disabled. The proper fix
5485 require an upload by the eatmydata maintainer applying the patch
5486 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
5487 The rest have proper fixes in unstable.&lt;/p&gt;
5488
5489 &lt;p&gt;I hope this get you going with the installation testing, as we are
5490 quickly running out of time trying to get our Jessie based
5491 installation ready before the distribution freeze in a month.&lt;/p&gt;
5492 </description>
5493 </item>
5494
5495 <item>
5496 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
5497 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
5498 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
5499 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
5500 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
5501 to handle my fairly large DVD collection. It is a nice command line
5502 tool to get details about a DVD, like title, tracks, track length,
5503 etc, in XML, Perl or human readable format. But lsdvd have not seen
5504 any new development since 2006 and had a few irritating bugs affecting
5505 its use with some DVDs. Upstream seemed to be dead, and in January I
5506 sent a small probe asking for a version control repository for the
5507 project, without any reply. But I use it regularly and would like to
5508 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
5509 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
5510 the project admin, and after getting a reply from him explaining that
5511 he was no longer interested in the project, I asked if I could take
5512 over. And yesterday, I became project admin.&lt;/p&gt;
5513
5514 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
5515 maintainer interested in joining forces to maintain the upstream
5516 project, and I hope we can get a new release out fairly quickly,
5517 collecting the patches spread around on the internet into on place.
5518 I&#39;ve added the relevant Debian patches to the freshly created git
5519 repository, and expect the Gentoo patches to make it too. If you got
5520 a DVD collection and care about command line tools, check out
5521 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
5522 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
5523 list&lt;/a&gt;. :)&lt;/p&gt;
5524 </description>
5525 </item>
5526
5527 <item>
5528 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
5529 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
5530 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
5531 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
5532 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
5533 a lot quicker. When we install more than 2000 packages in
5534 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
5535 tasksel in the installer, unpacking the binary packages take forever.
5536 A part of the slow I/O issue was discussed in
5537 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
5538 much file system sync-ing done by dpkg, which is the package
5539 responsible for unpacking the binary packages. Other parts (like code
5540 executed by postinst scripts) might also sync to disk during
5541 installation. All this sync-ing to disk do not really make sense to
5542 me. If the machine crash half-way through, I start over, I do not try
5543 to salvage the half installed system. So the failure sync-ing is
5544 supposed to protect against, hardware or system crash, is not really
5545 relevant while the installer is running.&lt;/p&gt;
5546
5547 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
5548 system sync()-ing in a fairly non-intrusive way, without the need to
5549 change the code in several packages. The idea is not new, but I have
5550 not heard anyone propose the approach using dpkg-divert before. It
5551 depend on the small and clever package
5552 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
5553 uses LD_PRELOAD to replace the system functions for syncing data to
5554 disk with functions doing nothing, thus allowing programs to live
5555 dangerous while speeding up disk I/O significantly. Instead of
5556 modifying the implementation of dpkg, apt and tasksel (which are the
5557 packages responsible for selecting, fetching and installing packages),
5558 it occurred to me that we could just divert the programs away, replace
5559 them with a simple shell wrapper calling
5560 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
5561 Two days ago I decided to test the idea, and wrapped up a simple
5562 implementation for the Debian Edu udeb.&lt;/p&gt;
5563
5564 &lt;p&gt;The effect was stunning. In my first test it reduced the running
5565 time of the pkgsel step (installing tasks) from 64 to less than 44
5566 minutes (20 minutes shaved off the installation) on an old Dell
5567 Latitude D505 machine. I am not quite sure what the optimised time
5568 would have been, as I messed up the testing a bit, causing the debconf
5569 priority to get low enough for two questions to pop up during
5570 installation. As soon as I saw the questions I moved the installation
5571 along, but do not know how long the question were holding up the
5572 installation. I did some more measurements using Debian Edu Jessie,
5573 and got these results. The time measured is the time stamp in
5574 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
5575 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
5576 yourself. In Debian Edu, the tasksel dialog do not show up, and the
5577 timing thus do not depend on how quickly the user handle the tasksel
5578 dialog.&lt;/p&gt;
5579
5580 &lt;p&gt;&lt;table&gt;
5581
5582 &lt;tr&gt;
5583 &lt;th&gt;Machine/setup&lt;/th&gt;
5584 &lt;th&gt;Original tasksel&lt;/th&gt;
5585 &lt;th&gt;Optimised tasksel&lt;/th&gt;
5586 &lt;th&gt;Reduction&lt;/th&gt;
5587 &lt;/tr&gt;
5588
5589 &lt;tr&gt;
5590 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
5591 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
5592 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
5593 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
5594 &lt;/tr&gt;
5595
5596 &lt;tr&gt;
5597 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
5598 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
5599 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
5600 &lt;td&gt;23 min 40%&lt;/td&gt;
5601 &lt;/tr&gt;
5602
5603 &lt;tr&gt;
5604 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
5605 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
5606 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
5607 &lt;td&gt;11 min 50%&lt;/td&gt;
5608 &lt;/tr&gt;
5609
5610 &lt;tr&gt;
5611 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
5612 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
5613 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
5614 &lt;td&gt;2 min 33%&lt;/td&gt;
5615 &lt;/tr&gt;
5616
5617 &lt;tr&gt;
5618 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
5619 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
5620 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
5621 &lt;td&gt;4 min 21%&lt;/td&gt;
5622 &lt;/tr&gt;
5623
5624 &lt;/table&gt;&lt;/p&gt;
5625
5626 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
5627 time is spent downloading packages. The connection to the Internet
5628 was 100Mbit/s during testing, so downloading should not be a
5629 significant factor in the measurement. Download typically took a few
5630 seconds to a few minutes, depending on the amount of packages being
5631 installed.&lt;/p&gt;
5632
5633 &lt;p&gt;The speedup is implemented by using two hooks in
5634 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
5635 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
5636 finish-install.d hook to remove the divert at the end of the
5637 installation. I picked the pre-pkgsel.d hook instead of the
5638 post-base-installer.d hook because I test using an ISO without the
5639 eatmydata package included, and the post-base-installer.d hook in
5640 Debian Edu can only operate on packages included in the ISO. The
5641 negative effect of this is that I am unable to activate this
5642 optimization for the kernel installation step in d-i. If the code is
5643 moved to the post-base-installer.d hook, the speedup would be larger
5644 for the entire installation.&lt;/p&gt;
5645
5646 &lt;p&gt;I&#39;ve implemented this in the
5647 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
5648 git repository, and plan to provide the optimization as part of the
5649 Debian Edu installation. If you want to test this yourself, you can
5650 create two files in the installer (or in an udeb). One shell script
5651 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
5652
5653 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5654 #!/bin/sh
5655 set -e
5656 . /usr/share/debconf/confmodule
5657 info() {
5658 logger -t my-pkgsel &quot;info: $*&quot;
5659 }
5660 error() {
5661 logger -t my-pkgsel &quot;error: $*&quot;
5662 }
5663 override_install() {
5664 apt-install eatmydata || true
5665 if [ -x /target/usr/bin/eatmydata ] ; then
5666 for bin in dpkg apt-get aptitude tasksel ; do
5667 file=/usr/bin/$bin
5668 # Test that the file exist and have not been diverted already.
5669 if [ -f /target$file ] ; then
5670 info &quot;diverting $file using eatmydata&quot;
5671 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
5672 &gt; /target$file.edu
5673 chmod 755 /target$file.edu
5674 in-target dpkg-divert --package debian-edu-config \
5675 --rename --quiet --add $file
5676 ln -sf ./$bin.edu /target$file
5677 else
5678 error &quot;unable to divert $file, as it is missing.&quot;
5679 fi
5680 done
5681 else
5682 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
5683 fi
5684 }
5685
5686 override_install
5687 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5688
5689 &lt;p&gt;To clean up, another shell script should go into
5690 /usr/lib/finish-install.d/ with code like this:
5691
5692 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5693 #! /bin/sh -e
5694 . /usr/share/debconf/confmodule
5695 error() {
5696 logger -t my-finish-install &quot;error: $@&quot;
5697 }
5698 remove_install_override() {
5699 for bin in dpkg apt-get aptitude tasksel ; do
5700 file=/usr/bin/$bin
5701 if [ -x /target$file.edu ] ; then
5702 rm /target$file
5703 in-target dpkg-divert --package debian-edu-config \
5704 --rename --quiet --remove $file
5705 rm /target$file.edu
5706 else
5707 error &quot;Missing divert for $file.&quot;
5708 fi
5709 done
5710 sync # Flush file buffers before continuing
5711 }
5712
5713 remove_install_override
5714 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5715
5716 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
5717 edu-eatmydata-install and call it from the pre-pkgsel.d and
5718 finish-install.d scripts.&lt;/p&gt;
5719
5720 &lt;p&gt;By now you might ask if this change should get into the normal
5721 Debian installer too? I suspect it should, but am not sure the
5722 current debian-installer coordinators find it useful enough. It also
5723 depend on the side effects of the change. I&#39;m not aware of any, but I
5724 guess we will see if the change is safe after some more testing.
5725 Perhaps there is some package in Debian depending on sync() and
5726 fsync() having effect? Perhaps it should go into its own udeb, to
5727 allow those of us wanting to enable it to do so without affecting
5728 everyone.&lt;/p&gt;
5729
5730 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
5731 will break installation of all programs using gnutls because of
5732 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
5733 eatmydata package in Debian will solve it.&lt;/p&gt;
5734
5735 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
5736 the optimization work again. And I have discovered that the
5737 dpkg-divert trick is not really needed and implemented a slightly
5738 simpler approach as part of the debian-edu-install package. See
5739 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
5740
5741 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
5742 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
5743 triggering on i386 made it into testing, and broke this installation
5744 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
5745 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
5746 </description>
5747 </item>
5748
5749 <item>
5750 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
5751 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
5752 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
5753 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
5754 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
5755 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
5756 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
5757 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
5758 learn that there is a large set of publicly available key servers to
5759 use when looking for peoples public key. So far I have used
5760 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
5761 were misbehaving, but those days are ended. The servers I have used
5762 up until yesterday have been slow and some times unavailable. I hope
5763 those problems are gone now.&lt;/p&gt;
5764
5765 &lt;p&gt;Behind the round robin DNS entry of the
5766 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
5767 there is a pool of more than 100 keyservers which are checked every
5768 day to ensure they are well connected and up to date. It must be
5769 better than what I have used so far. :)&lt;/p&gt;
5770
5771 &lt;p&gt;Yesterdays speaker told me that the service is the default
5772 keyserver provided by the default configuration in GnuPG, but this do
5773 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
5774
5775 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
5776 line:&lt;/p&gt;
5777
5778 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5779 keyserver pool.sks-keyservers.net
5780 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5781
5782 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
5783 entries in DNS. Just for fun, I did just that at work, so now every
5784 user of GnuPG at the University of Oslo should find a OpenGPG
5785 keyserver automatically should their need it:&lt;/p&gt;
5786
5787 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5788 % host -t srv _pgpkey-http._tcp.uio.no
5789 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
5790 %
5791 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5792
5793 &lt;p&gt;Now if only
5794 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
5795 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
5796 very happy. It can look up a given key or search for a user ID, but I
5797 normally do not want that, but to find a trust path from my key to
5798 another key. Given a user ID or key ID, I would like to find (and
5799 download) the keys representing a signature path from my key to the
5800 key in question, to be able to get a trust path between the two keys.
5801 This is as far as I can tell not possible today. Perhaps something
5802 for a future version of the protocol?&lt;/p&gt;
5803 </description>
5804 </item>
5805
5806 <item>
5807 <title>From English wiki to translated PDF and epub via Docbook</title>
5808 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
5809 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
5810 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
5811 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
5812 project&lt;/a&gt; provide an instruction manual for teachers, system
5813 administrators and other users that contain useful tips for setting up
5814 and maintaining a Debian Edu installation. This text is about how the
5815 text processing of this manual is handled in the project.&lt;/p&gt;
5816
5817 &lt;p&gt;One goal of the project is to provide information in the native
5818 language of its users, and for this we need to handle translations.
5819 But we also want to make sure each language contain the same
5820 information, so for this we need a good way to keep the translations
5821 in sync. And we want it to be easy for our users to improve the
5822 documentation, avoiding the need to learn special formats or tools to
5823 contribute, and the obvious way to do this is to make it possible to
5824 edit the documentation using a web browser. We also want it to be
5825 easy for translators to keep the translation up to date, and give them
5826 help in figuring out what need to be translated. Here is the list of
5827 tools and the process we have found trying to reach all these
5828 goals.&lt;/p&gt;
5829
5830 &lt;p&gt;We maintain the authoritative source of our manual in the
5831 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
5832 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
5833 front page with references to the different chapters, several pages
5834 for each chapter, and finally one &quot;collection page&quot; gluing all the
5835 chapters together into one large web page (aka
5836 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
5837 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
5838 processing and translations. Thanks to the fact that the
5839 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
5840 wiki.debian.org support exporting pages in
5841 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
5842 the list of pages to export using the raw version of the AllInOne
5843 page, loop over each of them to generate a Docbook XML version of the
5844 manual. This process also download images and transform image
5845 references to use the locally downloaded images. The generated
5846 Docbook XML files are slightly broken, so some post-processing is done
5847 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
5848 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
5849 a handfull of images. The XML file can now be used to generate PDF, HTML
5850 and epub versions of the English manual. This is the basic step of
5851 our process, making PDF (using dblatex), HTML (using xsltproc) and
5852 epub (using dbtoepub) version from Docbook XML, and the resulting files
5853 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
5854
5855 &lt;p&gt;But English documentation is not enough for us. We want translated
5856 documentation too, and we want to make it easy for translators to
5857 track the English original. For this we use the
5858 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
5859 which allow us to transform the English Docbook XML file into a
5860 translation file (a .pot file), usable with the normal gettext based
5861 translation tools used by those translating free software. The pot
5862 file is used to create and maintain translation files (several .po
5863 files), which the translations update with the native language
5864 translations of all titles, paragraphs and blocks of text in the
5865 original. The next step is combining the original English Docbook XML
5866 and the translation file (say debian-edu-wheezy-manual.nb.po), to
5867 create a translated Docbook XML file (in this case
5868 debian-edu-wheezy-manual.nb.xml). This translated (or partly
5869 translated, if the translation is not complete) Docbook XML file can
5870 then be used like the original to create a PDF, HTML and epub version
5871 of the documentation.&lt;/p&gt;
5872
5873 &lt;p&gt;The translators use different tools to edit the .po files. We
5874 recommend using
5875 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
5876 while some use emacs and vi, others can use web based editors like
5877 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
5878 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
5879 is where the .po file end up, in our git repository. Updated
5880 translations can either be committed directly to git, or submitted as
5881 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
5882 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
5883
5884 &lt;p&gt;One challenge is images, which both might need to be translated (if
5885 they show translated user applications), and are needed in different
5886 formats when creating PDF and HTML versions (epub is a HTML version in
5887 this regard). For this we transform the original PNG images to the
5888 needed density and format during build, and have a way to provide
5889 translated images by storing translated versions in
5890 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
5891 package maintainers know more.&lt;/p&gt;
5892
5893 &lt;p&gt;If you wonder what the result look like, we provide
5894 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
5895 of the documentation packages on the web&lt;/a&gt;. See for example the
5896 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
5897 PDF version&lt;/a&gt; or the
5898 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
5899 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
5900 but perhaps it will be done in the future.&lt;/p&gt;
5901
5902 &lt;p&gt;To learn more, check out
5903 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
5904 debian-edu-doc package&lt;/a&gt;,
5905 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
5906 manual on the wiki&lt;/a&gt; and
5907 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
5908 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
5909 </description>
5910 </item>
5911
5912 <item>
5913 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
5914 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
5915 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
5916 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
5917 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
5918 related packages relevant for the computer installed automatically.
5919 So I implemented one, using
5920 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
5921 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
5922 run tasksel as user root. You should be presented with a new option,
5923 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
5924 select it, tasksel will install the packages isenkram claim is fit for
5925 the current hardware, hot pluggable or not.&lt;p&gt;
5926
5927 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
5928 description, and the other is the script used to extract the list of
5929 packages to install. The first part is in
5930 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
5931 this:&lt;/p&gt;
5932
5933 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5934 Task: isenkram
5935 Section: hardware
5936 Description: Hardware specific packages (autodetected by isenkram)
5937 Based on the detected hardware various hardware specific packages are
5938 proposed.
5939 Test-new-install: mark show
5940 Relevance: 8
5941 Packages: for-current-hardware
5942 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5943
5944 &lt;p&gt;The second part is in
5945 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
5946 this:&lt;/p&gt;
5947
5948 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5949 #!/bin/sh
5950 #
5951 (
5952 isenkram-lookup
5953 isenkram-autoinstall-firmware -l
5954 ) | sort -u
5955 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5956
5957 &lt;p&gt;All in all, a very short and simple implementation making it
5958 trivial to install the hardware dependent package we all may want to
5959 have installed on our machines. I&#39;ve not been able to find a way to
5960 get tasksel to tell you exactly which packages it plan to install
5961 before doing the installation. So if you are curious or careful,
5962 check the output from the isenkram-* command line tools first.&lt;/p&gt;
5963
5964 &lt;p&gt;The information about which packages are handling which hardware is
5965 fetched either from the isenkram package itself in
5966 /usr/share/isenkram/, from git.debian.org or from the APT package
5967 database (using the Modaliases header). The APT package database
5968 parsing have caused a nasty resource leak in the isenkram daemon (bugs
5969 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
5970 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
5971 the python-apt code (bug
5972 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
5973 workaround I was able to get rid of the file descriptor leak and
5974 reduce the memory leak from ~30 MiB per hardware detection down to
5975 around 2 MiB per hardware detection. It should make the desktop
5976 daemon a lot more useful. The fix is in version 0.7 uploaded to
5977 unstable today.&lt;/p&gt;
5978
5979 &lt;p&gt;I believe the current way of mapping hardware to packages in
5980 Isenkram is is a good draft, but in the future I expect isenkram to
5981 use the AppStream data source for this. A proposal for getting proper
5982 AppStream support into Debian is floating around as
5983 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
5984 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
5985 project&lt;/a&gt; will take place this summer to improve the situation. I
5986 look forward to seeing the result, and welcome patches for isenkram to
5987 start using the information when it is ready.&lt;/p&gt;
5988
5989 &lt;p&gt;If you want your package to map to some specific hardware, either
5990 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
5991 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
5992 package&lt;/a&gt; or submit a bug report with the details to the isenkram
5993 package. See also
5994 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
5995 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
5996 the information will be migrated to AppStream eventually, but for the
5997 moment I got no better place to store it.&lt;/p&gt;
5998 </description>
5999 </item>
6000
6001 <item>
6002 <title>FreedomBox milestone - all packages now in Debian Sid</title>
6003 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
6004 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
6005 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
6006 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6007 project&lt;/a&gt; is working on providing the software and hardware to make
6008 it easy for non-technical people to host their data and communication
6009 at home, and being able to communicate with their friends and family
6010 encrypted and away from prying eyes. It is still going strong, and
6011 today a major mile stone was reached.&lt;/p&gt;
6012
6013 &lt;p&gt;Today, the last of the packages currently used by the project to
6014 created the system images were accepted into Debian Unstable. It was
6015 the freedombox-setup package, which is used to configure the images
6016 during build and on the first boot. Now all one need to get going is
6017 the build code from the freedom-maker git repository and packages from
6018 Debian. And once the freedombox-setup package enter testing, we can
6019 build everything directly from Debian. :)&lt;/p&gt;
6020
6021 &lt;p&gt;Some key packages used by Freedombox are
6022 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
6023 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
6024 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
6025 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
6026 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
6027 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
6028 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
6029 are plans to integrate more packages into the setup. User
6030 documentation is maintained on the Debian wiki. Please
6031 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
6032 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
6033
6034 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
6035 setup, run this on a Debian machine using a user with sudo rights to
6036 become root:&lt;/p&gt;
6037
6038 &lt;p&gt;&lt;pre&gt;
6039 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6040 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6041 u-boot-tools
6042 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6043 freedom-maker
6044 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6045 &lt;/pre&gt;&lt;/p&gt;
6046
6047 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
6048 devices. See the README in the freedom-maker git repo for more
6049 details on the build. If you do not want all three images, trim the
6050 make line. Note that the virtualbox-image target is not really
6051 virtualbox specific. It create a x86 image usable in kvm, qemu,
6052 vmware and any other x86 virtual machine environment. You might need
6053 the version of vmdebootstrap in Jessie to get the build working, as it
6054 include fixes for a race condition with kpartx.&lt;/p&gt;
6055
6056 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
6057 method, boot a Debian Wheezy ISO and use this boot argument to load
6058 the preseed values:&lt;/p&gt;
6059
6060 &lt;p&gt;&lt;pre&gt;
6061 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;
6062 &lt;/pre&gt;&lt;/p&gt;
6063
6064 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
6065 it still work.&lt;/p&gt;
6066
6067 &lt;p&gt;If you wonder how to help, one task you could look at is using
6068 systemd as the boot system. It will become the default for Linux in
6069 Jessie, so we need to make sure it is usable on the Freedombox. I did
6070 a simple test a few weeks ago, and noticed dnsmasq failed to start
6071 during boot when using systemd. I suspect there are other problems
6072 too. :) To detect problems, there is a test suite included, which can
6073 be run from the plinth web interface.&lt;/p&gt;
6074
6075 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6076 us get the new release published. :) Please join us on
6077 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6078 irc.debian.org)&lt;/a&gt; and
6079 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6080 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6081 </description>
6082 </item>
6083
6084 <item>
6085 <title>S3QL, a locally mounted cloud file system - nice free software</title>
6086 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
6087 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
6088 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
6089 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
6090 solution for use at home. My requirements are simple, it must be
6091 cheap and locally encrypted (in other words, I keep the encryption
6092 keys, the storage provider do not have access to my private files).
6093 One idea me and my friends had many years ago, before the cloud
6094 storage providers showed up, was to use Google mail as storage,
6095 writing a Linux block device storing blocks as emails in the mail
6096 service provided by Google, and thus get heaps of free space. On top
6097 of this one can add encryption, RAID and volume management to have
6098 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6099 I never found time to implement such system. But the last few weeks I
6100 have looked at a system called
6101 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
6102 mounted network backed file system with the features I need.&lt;/p&gt;
6103
6104 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
6105 handling several different storage providers, any with Amazon S3,
6106 Google Drive or OpenStack API. There are heaps of such storage
6107 providers. S3QL can also use a local directory as storage, which
6108 combined with sshfs allow for file storage on any ssh server. S3QL
6109 include support for encryption, compression, de-duplication, snapshots
6110 and immutable file systems, allowing me to mount the remote storage as
6111 a local mount point, look at and use the files as if they were local,
6112 while the content is stored in the cloud as well. This allow me to
6113 have a backup that should survive fire. The file system can not be
6114 shared between several machines at the same time, as only one can
6115 mount it at the time, but any machine with the encryption key and
6116 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
6117
6118 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
6119 package is included already. So to get started, run &lt;tt&gt;apt-get
6120 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
6121 Greenqloud, after reading their nice recipe on
6122 &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
6123 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
6124 in Iceland more than those in USA when it come to keeping my personal
6125 data safe and private, and thus would rather spend money on a company
6126 in Iceland. Another nice recipe is available from the article
6127 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
6128 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
6129 Admin magazine. When the provider is picked, figure out how to get
6130 the API key needed to connect to the storage API. With Greencloud,
6131 the key did not show up until I had added payment details to my
6132 account.&lt;/p&gt;
6133
6134 &lt;p&gt;Armed with the API access details, it is time to create the file
6135 system. First, create a new bucket in the cloud. This bucket is the
6136 file system storage area. I picked a bucket name reflecting the
6137 machine that was going to store data there, but any name will do.
6138 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
6139 the API login and password, and a locally created password. Store it
6140 all in ~root/.s3ql/authinfo2 like this:
6141
6142 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6143 [s3c]
6144 storage-url: s3c://s.greenqloud.com:443/bucket-name
6145 backend-login: API-login
6146 backend-password: API-password
6147 fs-passphrase: local-password
6148 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6149
6150 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
6151 but any sensible way to create a fairly random password should do it.
6152 Armed with these details, it is now time to run mkfs, entering the API
6153 details and password to create it:&lt;/p&gt;
6154
6155 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6156 # mkdir -m 700 /var/lib/s3ql-cache
6157 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6158 --ssl s3c://s.greenqloud.com:443/bucket-name
6159 Enter backend login:
6160 Enter backend password:
6161 Before using S3QL, make sure to read the user&#39;s guide, especially
6162 the &#39;Important Rules to Avoid Loosing Data&#39; section.
6163 Enter encryption password:
6164 Confirm encryption password:
6165 Generating random encryption key...
6166 Creating metadata tables...
6167 Dumping metadata...
6168 ..objects..
6169 ..blocks..
6170 ..inodes..
6171 ..inode_blocks..
6172 ..symlink_targets..
6173 ..names..
6174 ..contents..
6175 ..ext_attributes..
6176 Compressing and uploading metadata...
6177 Wrote 0.00 MB of compressed metadata.
6178 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6179
6180 &lt;p&gt;The next step is mounting the file system to make the storage available.
6181
6182 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6183 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6184 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6185 Using 4 upload threads.
6186 Downloading and decompressing metadata...
6187 Reading metadata...
6188 ..objects..
6189 ..blocks..
6190 ..inodes..
6191 ..inode_blocks..
6192 ..symlink_targets..
6193 ..names..
6194 ..contents..
6195 ..ext_attributes..
6196 Mounting filesystem...
6197 # df -h /s3ql
6198 Filesystem Size Used Avail Use% Mounted on
6199 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
6200 #
6201 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6202
6203 &lt;p&gt;The file system is now ready for use. I use rsync to store my
6204 backups in it, and as the metadata used by rsync is downloaded at
6205 mount time, no network traffic (and storage cost) is triggered by
6206 running rsync. To unmount, one should not use the normal umount
6207 command, as this will not flush the cache to the cloud storage, but
6208 instead running the umount.s3ql command like this:
6209
6210 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6211 # umount.s3ql /s3ql
6212 #
6213 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6214
6215 &lt;p&gt;There is a fsck command available to check the file system and
6216 correct any problems detected. This can be used if the local server
6217 crashes while the file system is mounted, to reset the &quot;already
6218 mounted&quot; flag. This is what it look like when processing a working
6219 file system:&lt;/p&gt;
6220
6221 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6222 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
6223 Using cached metadata.
6224 File system seems clean, checking anyway.
6225 Checking DB integrity...
6226 Creating temporary extra indices...
6227 Checking lost+found...
6228 Checking cached objects...
6229 Checking names (refcounts)...
6230 Checking contents (names)...
6231 Checking contents (inodes)...
6232 Checking contents (parent inodes)...
6233 Checking objects (reference counts)...
6234 Checking objects (backend)...
6235 ..processed 5000 objects so far..
6236 ..processed 10000 objects so far..
6237 ..processed 15000 objects so far..
6238 Checking objects (sizes)...
6239 Checking blocks (referenced objects)...
6240 Checking blocks (refcounts)...
6241 Checking inode-block mapping (blocks)...
6242 Checking inode-block mapping (inodes)...
6243 Checking inodes (refcounts)...
6244 Checking inodes (sizes)...
6245 Checking extended attributes (names)...
6246 Checking extended attributes (inodes)...
6247 Checking symlinks (inodes)...
6248 Checking directory reachability...
6249 Checking unix conventions...
6250 Checking referential integrity...
6251 Dropping temporary indices...
6252 Backing up old metadata...
6253 Dumping metadata...
6254 ..objects..
6255 ..blocks..
6256 ..inodes..
6257 ..inode_blocks..
6258 ..symlink_targets..
6259 ..names..
6260 ..contents..
6261 ..ext_attributes..
6262 Compressing and uploading metadata...
6263 Wrote 0.89 MB of compressed metadata.
6264 #
6265 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6266
6267 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
6268 quick, about the same speed as local file access. Uploading large
6269 amount of data is to me limited by the bandwidth out of and into my
6270 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
6271 which is very close to my upload speed, and downloading the same
6272 Debian installation ISO gave me 610 kiB/s, close to my download speed.
6273 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
6274 network, not the file system code. I do not know what a good cache
6275 size would be, but suspect that the cache should e larger than your
6276 working set.&lt;/p&gt;
6277
6278 &lt;p&gt;I mentioned that only one machine can mount the file system at the
6279 time. If another machine try, it is told that the file system is
6280 busy:&lt;/p&gt;
6281
6282 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6283 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6284 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6285 Using 8 upload threads.
6286 Backend reports that fs is still mounted elsewhere, aborting.
6287 #
6288 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6289
6290 &lt;p&gt;The file content is uploaded when the cache is full, while the
6291 metadata is uploaded once every 24 hour by default. To ensure the
6292 file system content is flushed to the cloud, one can either umount the
6293 file system, or ask S3QL to flush the cache and metadata using
6294 s3qlctrl:
6295
6296 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6297 # s3qlctrl upload-meta /s3ql
6298 # s3qlctrl flushcache /s3ql
6299 #
6300 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6301
6302 &lt;p&gt;If you are curious about how much space your data uses in the
6303 cloud, and how much compression and deduplication cut down on the
6304 storage usage, you can use s3qlstat on the mounted file system to get
6305 a report:&lt;/p&gt;
6306
6307 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6308 # s3qlstat /s3ql
6309 Directory entries: 9141
6310 Inodes: 9143
6311 Data blocks: 8851
6312 Total data size: 22049.38 MB
6313 After de-duplication: 21955.46 MB (99.57% of total)
6314 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
6315 Database size: 2.39 MB (uncompressed)
6316 (some values do not take into account not-yet-uploaded dirty blocks in cache)
6317 #
6318 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6319
6320 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
6321 storage. I did not try to locate them all, but am aware of at least
6322 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
6323 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
6324 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
6325 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
6326 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
6327 accept payment in Bitcoin. Pick one that suit your need. Some of
6328 them provide several GiB of free storage, but the prize models are
6329 quite different and you will have to figure out what suits you
6330 best.&lt;/p&gt;
6331
6332 &lt;p&gt;While researching this blog post, I had a look at research papers
6333 and posters discussing the S3QL file system. There are several, which
6334 told me that the file system is getting a critical check by the
6335 science community and increased my confidence in using it. One nice
6336 poster is titled
6337 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
6338 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
6339 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
6340 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
6341 and Pamela Smith. Please have a look.&lt;/p&gt;
6342
6343 &lt;p&gt;Given my problems with different file systems earlier, I decided to
6344 check out the mounted S3QL file system to see if it would be usable as
6345 a home directory (in other word, that it provided POSIX semantics when
6346 it come to locking and umask handling etc). Running
6347 &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
6348 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
6349 no error was found. So the file system can be used for home
6350 directories, if one chooses to do so.&lt;/p&gt;
6351
6352 &lt;p&gt;If you do not want a locally file system, and want something that
6353 work without the Linux fuse file system, I would like to mention the
6354 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
6355 provide locally encrypted backup using a command line client. It have
6356 a nicer access control system, where one can split out read and write
6357 access, allowing some systems to write to the backup and others to
6358 only read from it.&lt;/p&gt;
6359
6360 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
6361 activities, please send Bitcoin donations to my address
6362 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6363 </description>
6364 </item>
6365
6366 <item>
6367 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
6368 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
6369 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
6370 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
6371 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6372 project&lt;/a&gt; is working on providing the software and hardware for
6373 making it easy for non-technical people to host their data and
6374 communication at home, and being able to communicate with their
6375 friends and family encrypted and away from prying eyes. It has been
6376 going on for a while, and is slowly progressing towards a new test
6377 release (0.2).&lt;/p&gt;
6378
6379 &lt;p&gt;And what day could be better than the Pi day to announce that the
6380 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
6381 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
6382 system), and can also be installed using a Debian installer preseed
6383 file. The Debian based Freedombox is now based on Debian Jessie,
6384 where most of the needed packages used are already present. Only one,
6385 the freedombox-setup package, is missing. To try to build your own
6386 boot image to test the current status, fetch the freedom-maker scripts
6387 and build using
6388 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
6389 with a user with sudo access to become root:
6390
6391 &lt;pre&gt;
6392 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6393 freedom-maker
6394 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6395 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6396 u-boot-tools
6397 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6398 &lt;/pre&gt;
6399
6400 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
6401 devices. See the README for more details on the build. If you do not
6402 want all three images, trim the make line. But note that thanks to &lt;a
6403 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
6404 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
6405 kpartx call.&lt;/p&gt;
6406
6407 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
6408 method, boot a Debian Wheezy ISO and use this boot argument to load
6409 the preseed values:&lt;/p&gt;
6410
6411 &lt;pre&gt;
6412 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;
6413 &lt;/pre&gt;
6414
6415 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
6416 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
6417 currently hang while setting up APT sources. Killing the
6418 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
6419 installation will get the installation going. This affect all
6420 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
6421
6422 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6423 us get the new release published. :) Please join us on
6424 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6425 irc.debian.org)&lt;/a&gt; and
6426 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6427 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6428 </description>
6429 </item>
6430
6431 <item>
6432 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
6433 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
6434 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
6435 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
6436 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
6437 innetgr tools, because I needed them in
6438 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
6439 ng-utils, and it has served me well. I placed the project under the
6440 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
6441 repository. But many years ago, the CVS repository was dropped (lost,
6442 not migrated to new hardware, not sure), and the project have lacked a
6443 proper home since then.&lt;/p&gt;
6444
6445 &lt;p&gt;Last summer, I had a look at the package and made a new release
6446 fixing a irritating crash bug, but was unable to store the changes in
6447 a proper source control system. I applied for a project on
6448 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
6449 to follow up on it. Until today. :)&lt;/p&gt;
6450
6451 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
6452 now have a new home, and a git repository with the highlight of the
6453 history of the project. I published all release tarballs and imported
6454 them into the git repository. As the project is really stable and not
6455 expected to gain new features any time soon, I decided to make a new
6456 release and call it 1.0. Visit the new project home on
6457 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
6458 if you want to check it out. The new version is also uploaded into
6459 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
6460 </description>
6461 </item>
6462
6463 <item>
6464 <title>Testing sysvinit from experimental in Debian Hurd</title>
6465 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
6466 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
6467 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
6468 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
6469 their changes into sysvinit, to allow them to use the normal sysvinit
6470 boot system instead of their old one. This follow up on the
6471 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
6472 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
6473 get Debian on Hurd working more like Debian on Linux. To get started,
6474 I downloaded a prebuilt hard disk image from
6475 &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;,
6476 and started it using virt-manager.&lt;/p&gt;
6477
6478 &lt;p&gt;The first think I had to do after logging in (root without any
6479 password) was to get the network operational. I followed
6480 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
6481 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
6482 commands as root to get the machine to accept a IP address from the
6483 kvm internal DHCP server:&lt;/p&gt;
6484
6485 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6486 settrans -fgap /dev/netdde /hurd/netdde
6487 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
6488 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
6489 dhclient /dev/eth0
6490 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6491
6492 &lt;p&gt;After this, the machine had internet connectivity, and I could
6493 upgrade it and install the sysvinit packages from experimental and
6494 enable it as the default boot system in Hurd.&lt;/p&gt;
6495
6496 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
6497 running on the machine it for ssh login to work a password need to be
6498 set. Also, note that a bug somewhere in openssh on Hurd block
6499 compression from working. Remember to turn that off on the client
6500 side.&lt;/p&gt;
6501
6502 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
6503 stuff:&lt;/p&gt;
6504
6505 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6506 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
6507 deb http://http.debian.net/debian/ experimental main
6508 EOF
6509 apt-get update
6510 apt-get dist-upgrade
6511 apt-get install -t experimental initscripts sysv-rc sysvinit \
6512 sysvinit-core sysvinit-utils
6513 update-alternatives --config runsystem
6514 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6515
6516 &lt;p&gt;To reboot after switching boot system, you have to use
6517 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
6518 yet a sysvinit process able to receive the signals from the normal
6519 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
6520 upgrading every package and rebooting, the network come up with DHCP
6521 after boot as it should, and the settrans/pkill hack mentioned at the
6522 start is no longer needed. But for some strange reason, there are no
6523 longer any login prompt in the virtual console, so I logged in using
6524 ssh instead.
6525
6526 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
6527 fail some times. No idea what the cause is, but hope the Hurd porters
6528 figure it out. At least Justus said on IRC (#debian-hurd on
6529 irc.debian.org) that they are aware of the problem. A way to reduce
6530 the impact is to upgrade to the Hurd packages built by Justus by
6531 adding this repository to the machine:&lt;/p&gt;
6532
6533 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6534 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
6535 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
6536 EOF
6537 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6538
6539 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
6540 http://ftp.debian-ports.org/debian, because some of the packages in
6541 unstable do not yet include the required patches that are lingering in
6542 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
6543
6544 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6545 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
6546 i emacs - GNU Emacs editor (metapackage)
6547 i gdb - GNU Debugger
6548 i hurd-recommended - Miscellaneous translators
6549 i isc-dhcp-client - ISC DHCP client
6550 i isc-dhcp-common - common files used by all the isc-dhcp* packages
6551 i libc-bin - Embedded GNU C Library: Binaries
6552 i libc-dev-bin - Embedded GNU C Library: Development binaries
6553 i libc0.3 - Embedded GNU C Library: Shared libraries
6554 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
6555 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
6556 i multiarch-support - Transitional package to ensure multiarch compatibilit
6557 i A x11-common - X Window System (X.Org) infrastructure
6558 i xorg - X.Org X Window System
6559 i A xserver-xorg - X.Org X server
6560 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
6561 #
6562 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6563
6564 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
6565 X.org did not work out of the box and I never took the time to follow
6566 the porters instructions to fix it. This time I was interested in the
6567 command line stuff.&lt;p&gt;
6568 </description>
6569 </item>
6570
6571 <item>
6572 <title>New chrpath release 0.16</title>
6573 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
6574 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
6575 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
6576 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
6577 find problems in C, C++ and Java code using static source code
6578 analysis. It can detect a lot of different problems, and is very
6579 useful to find memory and locking bugs in the error handling part of
6580 the source. The company behind it provide
6581 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
6582 a community service&lt;/a&gt;, and many hundred free software projects are
6583 already checked. A few days ago I decided to have a closer look at
6584 the Coverity system, and discovered that the
6585 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
6586 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
6587 projects I am involved with was already registered. But these are
6588 fairly big, and I would also like to have a small and easy project to
6589 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
6590 checking of the chrpath project&lt;/a&gt;. It was
6591 added to the checker and discovered seven potential defects. Six of
6592 these were real, mostly resource &quot;leak&quot; when the program detected an
6593 error. Nothing serious, as the resources would be released a fraction
6594 of a second later when the program exited because of the error, but it
6595 is nice to do it right in case the source of the program some time in
6596 the future end up in a library. Having fixed all defects and added
6597 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
6598 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
6599 publish a new release. These are the release notes:&lt;/p&gt;
6600
6601 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
6602
6603 &lt;ul&gt;
6604
6605 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
6606 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
6607 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
6608
6609 &lt;/ul&gt;
6610
6611 &lt;p&gt;You can
6612 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
6613 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
6614 project if something is wrong with the new release. The test suite
6615 did not discover any old errors, so if you find a new one, please also
6616 include a test suite check.&lt;/p&gt;
6617 </description>
6618 </item>
6619
6620 <item>
6621 <title>New chrpath release 0.15</title>
6622 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
6623 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
6624 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
6625 <description>&lt;p&gt;After many years break from the package and a vain hope that
6626 development would be continued by someone else, I finally pulled my
6627 acts together this morning and wrapped up a new release of chrpath,
6628 the command line tool to modify the rpath and runpath of already
6629 compiled ELF programs. The update was triggered by the persistence of
6630 Isha Vishnoi at IBM, which needed a new config.guess file to get
6631 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
6632 is working on. I checked the
6633 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
6634 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
6635 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
6636 packages for interesting patches (failed to find the source from
6637 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
6638 These are the release notes:&lt;/p&gt;
6639
6640 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
6641
6642 &lt;ul&gt;
6643
6644 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
6645 with newer architectures. Thanks to isha vishnoi for the heads
6646 up.&lt;/li&gt;
6647
6648 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
6649
6650 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
6651 Matthias Klose.&lt;/li&gt;
6652
6653 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
6654 Petr Machata found in Fedora.&lt;/li&gt;
6655
6656 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
6657 .dynamic is a NULL terminated string. Based on patch found in
6658 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
6659
6660 &lt;/ul&gt;
6661
6662 &lt;p&gt;You can
6663 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
6664 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
6665 project if something is wrong with the new release. The test suite
6666 did not discover any old errors, so if you find a new one, please also
6667 include a testsuite check.&lt;/p&gt;
6668 </description>
6669 </item>
6670
6671 <item>
6672 <title>Debian init.d boot script example for rsyslog</title>
6673 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
6674 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
6675 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
6676 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
6677 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
6678 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
6679 init.d scripts at all. Here is an example init.d script, ie a rewrite
6680 of /etc/init.d/rsyslog:&lt;/p&gt;
6681
6682 &lt;p&gt;&lt;pre&gt;
6683 #!/lib/init/init-d-script
6684 ### BEGIN INIT INFO
6685 # Provides: rsyslog
6686 # Required-Start: $remote_fs $time
6687 # Required-Stop: umountnfs $time
6688 # X-Stop-After: sendsigs
6689 # Default-Start: 2 3 4 5
6690 # Default-Stop: 0 1 6
6691 # Short-Description: enhanced syslogd
6692 # Description: Rsyslog is an enhanced multi-threaded syslogd.
6693 # It is quite compatible to stock sysklogd and can be
6694 # used as a drop-in replacement.
6695 ### END INIT INFO
6696 DESC=&quot;enhanced syslogd&quot;
6697 DAEMON=/usr/sbin/rsyslogd
6698 &lt;/pre&gt;&lt;/p&gt;
6699
6700 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
6701 script was 137 lines, and the above is just 15 lines, most of it meta
6702 info/comments.&lt;/p&gt;
6703
6704 &lt;p&gt;How to do this, you ask? Well, one create a new script
6705 /lib/init/init-d-script looking something like this:
6706
6707 &lt;p&gt;&lt;pre&gt;
6708 #!/bin/sh
6709
6710 # Define LSB log_* functions.
6711 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
6712 # and status_of_proc is working.
6713 . /lib/lsb/init-functions
6714
6715 #
6716 # Function that starts the daemon/service
6717
6718 #
6719 do_start()
6720 {
6721 # Return
6722 # 0 if daemon has been started
6723 # 1 if daemon was already running
6724 # 2 if daemon could not be started
6725 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
6726 || return 1
6727 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
6728 $DAEMON_ARGS \
6729 || return 2
6730 # Add code here, if necessary, that waits for the process to be ready
6731 # to handle requests from services started subsequently which depend
6732 # on this one. As a last resort, sleep for some time.
6733 }
6734
6735 #
6736 # Function that stops the daemon/service
6737 #
6738 do_stop()
6739 {
6740 # Return
6741 # 0 if daemon has been stopped
6742 # 1 if daemon was already stopped
6743 # 2 if daemon could not be stopped
6744 # other if a failure occurred
6745 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
6746 RETVAL=&quot;$?&quot;
6747 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
6748 # Wait for children to finish too if this is a daemon that forks
6749 # and if the daemon is only ever run from this initscript.
6750 # If the above conditions are not satisfied then add some other code
6751 # that waits for the process to drop all resources that could be
6752 # needed by services started subsequently. A last resort is to
6753 # sleep for some time.
6754 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
6755 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
6756 # Many daemons don&#39;t delete their pidfiles when they exit.
6757 rm -f $PIDFILE
6758 return &quot;$RETVAL&quot;
6759 }
6760
6761 #
6762 # Function that sends a SIGHUP to the daemon/service
6763 #
6764 do_reload() {
6765 #
6766 # If the daemon can reload its configuration without
6767 # restarting (for example, when it is sent a SIGHUP),
6768 # then implement that here.
6769 #
6770 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
6771 return 0
6772 }
6773
6774 SCRIPTNAME=$1
6775 scriptbasename=&quot;$(basename $1)&quot;
6776 echo &quot;SN: $scriptbasename&quot;
6777 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
6778 script=&quot;$1&quot;
6779 shift
6780 . $script
6781 else
6782 exit 0
6783 fi
6784
6785 NAME=$(basename $DAEMON)
6786 PIDFILE=/var/run/$NAME.pid
6787
6788 # Exit if the package is not installed
6789 #[ -x &quot;$DAEMON&quot; ] || exit 0
6790
6791 # Read configuration variable file if it is present
6792 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
6793
6794 # Load the VERBOSE setting and other rcS variables
6795 . /lib/init/vars.sh
6796
6797 case &quot;$1&quot; in
6798 start)
6799 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
6800 do_start
6801 case &quot;$?&quot; in
6802 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
6803 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
6804 esac
6805 ;;
6806 stop)
6807 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
6808 do_stop
6809 case &quot;$?&quot; in
6810 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
6811 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
6812 esac
6813 ;;
6814 status)
6815 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
6816 ;;
6817 #reload|force-reload)
6818 #
6819 # If do_reload() is not implemented then leave this commented out
6820 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
6821 #
6822 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
6823 #do_reload
6824 #log_end_msg $?
6825 #;;
6826 restart|force-reload)
6827 #
6828 # If the &quot;reload&quot; option is implemented then remove the
6829 # &#39;force-reload&#39; alias
6830 #
6831 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
6832 do_stop
6833 case &quot;$?&quot; in
6834 0|1)
6835 do_start
6836 case &quot;$?&quot; in
6837 0) log_end_msg 0 ;;
6838 1) log_end_msg 1 ;; # Old process is still running
6839 *) log_end_msg 1 ;; # Failed to start
6840 esac
6841 ;;
6842 *)
6843 # Failed to stop
6844 log_end_msg 1
6845 ;;
6846 esac
6847 ;;
6848 *)
6849 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
6850 exit 3
6851 ;;
6852 esac
6853
6854 :
6855 &lt;/pre&gt;&lt;/p&gt;
6856
6857 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
6858 lot. I did not really polish the approach, so it might not always
6859 work out of the box, but you get the idea. I did not try very hard to
6860 optimize it nor make it more robust either.&lt;/p&gt;
6861
6862 &lt;p&gt;A better argument for switching init system in Debian than reducing
6863 the size of init scripts (which is a good thing to do anyway), is to
6864 get boot system that is able to handle the kernel events sensibly and
6865 robustly, and do not depend on the boot to run sequentially. The boot
6866 and the kernel have not behaved sequentially in years.&lt;/p&gt;
6867 </description>
6868 </item>
6869
6870 <item>
6871 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
6872 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
6873 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
6874 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
6875 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
6876 remote display access is the preferred solution with oVirt and RedHat
6877 Enterprise Virtualization, and I was sad to discover the other day
6878 that the browser plugin needed to use these systems seamlessly was
6879 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
6880 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
6881 2013-04-01, so I decided to wrap up a package based on the great work
6882 from Cajus Pollmeier and put it in a collab-maint maintained git
6883 repository to get a package I could use. I would very much like
6884 others to help me maintain the package (or just take over, I do not
6885 mind), but as no-one had volunteered so far, I just uploaded it to
6886 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
6887
6888 &lt;p&gt;The source is now available from
6889 &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;
6890 </description>
6891 </item>
6892
6893 <item>
6894 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
6895 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
6896 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
6897 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
6898 <description>&lt;p&gt;The
6899 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
6900 program is a a very nice system to create virtual machine images. It
6901 create a image file, add a partition table, mount it and run
6902 debootstrap in the mounted directory to create a Debian system on a
6903 stick. Yesterday, I decided to try to teach it how to make images for
6904 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
6905 of a plan to simplify the build system for
6906 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
6907 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
6908 the virtualbox images, but its current build system made multistrap
6909 based system for Dreamplug images, and it is lacking support for
6910 Raspberry Pi.&lt;/p&gt;
6911
6912 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
6913 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
6914 code and adjusted it to be able to build armel images on my amd64
6915 Debian laptop. I ended up giving vmdebootstrap five new options,
6916 allowing me to replicate the image creation process I use to make
6917 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
6918 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
6919 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
6920 call debootstrap with --foreign and to copy the handler into the
6921 generated chroot before running the second stage. This allow
6922 vmdebootstrap to create armel images on an amd64 host. Next I added
6923 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
6924 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
6925 given file system type, allowing me to create an image with a vfat
6926 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
6927 variant&lt;/tt&gt; option to allow me to create smaller images without the
6928 Debian base system packages installed. Finally, I added an option
6929 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
6930 as a boot loader. It is not needed on the Raspberry Pi and probably
6931 most other non-x86 architectures. The changes were accepted by the
6932 upstream author of vmdebootstrap yesterday and today, and is now
6933 available from
6934 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
6935 upstream project page&lt;/a&gt;.&lt;/p&gt;
6936
6937 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
6938 create a small script (the customize script) to add the non-free
6939 binary blob needed to boot the Raspberry Pi and the APT source
6940 list:&lt;/p&gt;
6941
6942 &lt;p&gt;&lt;pre&gt;
6943 #!/bin/sh
6944 set -e # Exit on first error
6945 rootdir=&quot;$1&quot;
6946 cd &quot;$rootdir&quot;
6947 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
6948 deb http://http.debian.net/debian/ jessie main contrib non-free
6949 EOF
6950 # Install non-free binary blob needed to boot Raspberry Pi. This
6951 # install a kernel somewhere too.
6952 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
6953 -O $rootdir/usr/bin/rpi-update
6954 chmod a+x $rootdir/usr/bin/rpi-update
6955 mkdir -p $rootdir/lib/modules
6956 touch $rootdir/boot/start.elf
6957 chroot $rootdir rpi-update
6958 &lt;/pre&gt;&lt;/p&gt;
6959
6960 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
6961 to build the image:&lt;/p&gt;
6962
6963 &lt;pre&gt;
6964 sudo ./vmdebootstrap \
6965 --variant minbase \
6966 --arch armel \
6967 --distribution jessie \
6968 --mirror http://http.debian.net/debian \
6969 --image test.img \
6970 --size 600M \
6971 --bootsize 64M \
6972 --boottype vfat \
6973 --log-level debug \
6974 --verbose \
6975 --no-kernel \
6976 --no-extlinux \
6977 --root-password raspberry \
6978 --hostname raspberrypi \
6979 --foreign /usr/bin/qemu-arm-static \
6980 --customize `pwd`/customize \
6981 --package netbase \
6982 --package git-core \
6983 --package binutils \
6984 --package ca-certificates \
6985 --package wget \
6986 --package kmod
6987 &lt;/pre&gt;&lt;/p&gt;
6988
6989 &lt;p&gt;The list of packages being installed are the ones needed by
6990 rpi-update to make the image bootable on the Raspberry Pi, with the
6991 exception of netbase, which is needed by debootstrap to find
6992 /etc/hosts with the minbase variant. I really wish there was a way to
6993 set up an Raspberry Pi using only packages in the Debian archive, but
6994 that is not possible as far as I know, because it boots from the GPU
6995 using a non-free binary blob.&lt;/p&gt;
6996
6997 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
6998 probably a few others installed. I have not checked the complete
6999 build dependency list.&lt;/p&gt;
7000
7001 &lt;p&gt;The resulting image will not use the hardware floating point unit
7002 on the Raspberry PI, because the armel architecture in Debian is not
7003 optimized for that use. So the images created will be a bit slower
7004 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
7005 </description>
7006 </item>
7007
7008 <item>
7009 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
7010 <link>https://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html</link>
7011 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Good_causes__Debian_Outreach_Program_for_Women__EFF_documenting_the_spying_and_Open_access_in_Norway.html</guid>
7012 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
7013 <description>&lt;p&gt;The last few days I came across a few good causes that should get
7014 wider attention. I recommend signing and donating to each one of
7015 these. :)&lt;/p&gt;
7016
7017 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
7018 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
7019 Women program which is a Google Summer of Code like initiative to get
7020 more women involved in free software. One debian sponsor has offered
7021 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
7022 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
7023 hope you will to. :)&lt;/p&gt;
7024
7025 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
7026 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
7027 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
7028 take place these days, and their need to fund the work. I&#39;ve already
7029 donated. Are you next?&lt;/p&gt;
7030
7031 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
7032 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7033 statement under the heading
7034 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
7035 Access&lt;/a&gt; for those of us asking for more focus on open access in the
7036 Norwegian government. So far 499 signatures. I hope you will sign it
7037 too.&lt;/p&gt;
7038 </description>
7039 </item>
7040
7041 <item>
7042 <title>Videos about the Freedombox project - for inspiration and learning</title>
7043 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
7044 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
7045 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
7046 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
7047 project&lt;/a&gt; have been going on for a while, and have presented the
7048 vision, ideas and solution several places. Here is a little
7049 collection of videos of talks and presentation of the project.&lt;/p&gt;
7050
7051 &lt;ul&gt;
7052
7053 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
7054 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
7055
7056 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
7057 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7058
7059 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
7060 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7061 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
7062 (Youtube)&lt;/li&gt;
7063
7064 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
7065 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
7066
7067 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
7068 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
7069
7070 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
7071 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7072 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
7073
7074 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
7075 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
7076 (Youtube)&lt;/li&gt;
7077
7078 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
7079 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
7080
7081 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
7082 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
7083
7084 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
7085 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7086 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
7087
7088 &lt;/ul&gt;
7089
7090 &lt;p&gt;A larger list is available from
7091 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
7092 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
7093
7094 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
7095 Jessie is coming along quite well, and soon both Owncloud and using
7096 Tor should be available for testers of the Freedombox solution. :) In
7097 a few weeks I hope everything needed to test it is included in Debian.
7098 The withsqlite package is already in Debian, and the plinth package is
7099 pending in NEW. The third and vital part of that puzzle is the
7100 metapackage/setup framework, which is still pending an upload. Join
7101 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
7102 (#freedombox on irc.debian.org)&lt;/a&gt; and
7103 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
7104 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
7105 </description>
7106 </item>
7107
7108 <item>
7109 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
7110 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
7111 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
7112 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
7113 <description>&lt;p&gt;I was introduced to the
7114 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
7115 in 2010, when Eben Moglen presented his vision about serving the need
7116 of non-technical people to keep their personal information private and
7117 within the legal protection of their own homes. The idea is to give
7118 people back the power over their network and machines, and return
7119 Internet back to its intended peer-to-peer architecture. Instead of
7120 depending on a central service, the Freedombox will give everyone
7121 control over their own basic infrastructure.&lt;/p&gt;
7122
7123 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
7124 taken priority. But this summers nasty news about the misuse of trust
7125 and privilege exercised by the &quot;western&quot; intelligence gathering
7126 communities increased my eagerness to contribute to a point where I
7127 actually started working on the project a while back.&lt;/p&gt;
7128
7129 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
7130 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
7131 create a simple and cheap Debian based appliance that anyone can hook
7132 up in their home and get access to secure and private services and
7133 communication. The initial deployment platform have been the
7134 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
7135 which is a piece of hardware I do not own. So to be able to test what
7136 the current Freedombox setup look like, I had to come up with a way to install
7137 it on some hardware I do have access to. I have rewritten the
7138 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
7139 image build framework to use .deb packages instead of only copying
7140 setup into the boot images, and thanks to this rewrite I am able to
7141 set up any machine supported by Debian Wheezy as a Freedombox, using
7142 the previously mentioned deb (and a few support debs for packages
7143 missing in Debian).&lt;/p&gt;
7144
7145 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
7146 scripts
7147 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
7148 and a administrative web interface
7149 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
7150 withsqlite), as well as a privacy enhancing proxy based on
7151 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
7152 (freedombox-privoxy). There is also a web/javascript based XMPP
7153 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
7154 trying (unsuccessfully so far) to talk to the XMPP server
7155 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
7156 web interface is pluggable, and the goal is to use it to enable OpenID
7157 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7158 this is really working yet, see
7159 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
7160 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
7161 on github at the moment. The HTTP proxy is operational out of the
7162 box, and the admin web interface can be used to add/remove plinth
7163 users. I&#39;ve not been able to do anything else with it so far, but
7164 know there are several branches spread around github and other places
7165 with lots of half baked features.&lt;/p&gt;
7166
7167 &lt;p&gt;Anyway, if you want to have a look at the current state, the
7168 following recipes should work to give you a test machine to poke
7169 at.&lt;/p&gt;
7170
7171 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
7172
7173 &lt;ol&gt;
7174
7175 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
7176 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
7177 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
7178 to the Debian installer:&lt;p&gt;
7179 &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;
7180
7181 &lt;li&gt;Answer the few language/region/password questions and pick disk to
7182 install on.&lt;/li&gt;
7183
7184 &lt;li&gt;When the installation is finished and the machine have rebooted a
7185 few times, your Freedombox is ready for testing.&lt;/li&gt;
7186
7187 &lt;/ol&gt;
7188
7189 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
7190
7191 &lt;ol&gt;
7192
7193 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
7194 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
7195 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
7196 &lt;pre&gt;
7197 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
7198 &lt;/pre&gt;&lt;/li&gt;
7199 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
7200 &lt;pre&gt;
7201 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7202 apt-key add -
7203 apt-get update
7204 apt-get install freedombox-setup
7205 /usr/lib/freedombox/setup
7206 &lt;/pre&gt;&lt;/li&gt;
7207 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
7208
7209 &lt;/ol&gt;
7210
7211 &lt;p&gt;You can test it on other architectures too, but because the
7212 freedombox-privoxy package is binary, it will only work as intended on
7213 the architectures where I have had time to build the binary and put it
7214 in my APT repository. But do not let this stop you. It is only a
7215 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
7216
7217 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
7218 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
7219 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
7220 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
7221
7222 &lt;p&gt;Please let me know if this works for you, or if you have any
7223 problems. We gather on the IRC channel
7224 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
7225 irc.debian.org and the
7226 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
7227 mailing list&lt;/a&gt;.&lt;/p&gt;
7228
7229 &lt;p&gt;Once you get your freedombox operational, you can visit
7230 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
7231 welcome screen (dead end - do not be surprised if you are unable to
7232 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
7233 to look at the rest of plinth. The default user is &#39;admin&#39; and the
7234 default password is &#39;secret&#39;.&lt;/p&gt;
7235 </description>
7236 </item>
7237
7238 <item>
7239 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
7240 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
7241 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
7242 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
7243 <description>&lt;p&gt;Earlier, I reported about
7244 &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
7245 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
7246 told by IBM that the original disk should be thrown away. And as
7247 there no longer was a problem if I bricked the firmware, I decided
7248 today to try to install Intel firmware to replace the Lenovo firmware
7249 currently on the disk.&lt;/p&gt;
7250
7251 &lt;p&gt;I searched the Intel site for firmware, and found
7252 &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;
7253 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
7254 according to the site should contain the latest firmware for SSD
7255 disks. I inserted the broken disk in one of my spare laptops and
7256 booted the ISO from a USB stick. The disk was recognized, but the
7257 program claimed the newest firmware already were installed and refused
7258 to insert any Intel firmware. So no change, and the disk is still
7259 unable to handle write load. :( I guess the only way to get them
7260 working would be if Lenovo releases new firmware. No idea how likely
7261 that is. Anyway, just blogging about this test for completeness. I
7262 got a working Samsung disk, and see no point in spending more time on
7263 the broken disks.&lt;/p&gt;
7264 </description>
7265 </item>
7266
7267 <item>
7268 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
7269 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
7270 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
7271 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
7272 <description>&lt;p&gt;Today I switched to
7273 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
7274 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
7275 my new Thinkpad X230, which was delivered with an
7276 &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
7277 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
7278 sustained writes. My hardware supplier have been very forthcoming in
7279 trying to find a solution, and after first trying with another
7280 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
7281 disk instead to fix it once and for all. The Samsung disk survived
7282 the installation of Debian with encrypted disks (filling the disk with
7283 random data during installation killed the first two), and I thus
7284 decided to trust it with my data. I have installed it as a Debian Edu
7285 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
7286 server at home using Kerberos and LDAP, and will use it as my work
7287 station from now on.&lt;/p&gt;
7288
7289 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
7290 Debian Wheezy default installation need to be tuned a bit to increase
7291 performance and increase life time of the disk. The Linux kernel and
7292 user space applications do not yet adjust automatically to such
7293 environment. To make it easier for my self, I created a draft Debian
7294 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
7295 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
7296 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
7297 is set up to adjust the setup of the machine by just installing the
7298 package. If there is any non-SSD disk in the machine, the package
7299 will refuse to install, as I did not try to write any logic to sort
7300 file systems in SSD and non-SSD file systems.&lt;/p&gt;
7301
7302 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
7303 set up Debian Wheezy with an SSD. It is adjusted to my use case,
7304 where I set up the machine with one large encrypted partition (in
7305 addition to /boot), put LVM on top of this and set up partitions on
7306 top of this again. See the README file in the package source for the
7307 references I used to pick the settings. At the moment these
7308 parameters are tuned:&lt;/p&gt;
7309
7310 &lt;ul&gt;
7311
7312 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
7313 (adding discard to /etc/crypttab)&lt;/li&gt;
7314
7315 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
7316 this case a cryptsetup partition) by changing issue_discards from
7317 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
7318
7319 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
7320 systems.&lt;/li&gt;
7321
7322 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
7323 /etc/fstab.&lt;/li&gt;
7324
7325 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
7326
7327 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
7328 cron.daily).&lt;/li&gt;
7329
7330 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
7331 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
7332
7333 &lt;/ul&gt;
7334
7335 &lt;p&gt;During installation, I cancelled the part where the installer fill
7336 the disk with random data, as this would kill the SSD performance for
7337 little gain. My goal with the encrypted file system is to ensure
7338 those stealing my laptop end up with a brick and not a working
7339 computer. I have no hope in keeping the really resourceful people
7340 from getting the data on the disk (see
7341 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
7342 Thus I concluded that adding the discard option to crypttab is the
7343 right thing to do.&lt;/p&gt;
7344
7345 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
7346 it for SSD, but others recommended deadline and a benchmark I found
7347 indicated that deadline might be better for interactive use.&lt;/p&gt;
7348
7349 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
7350 and ext4, but read that it would give a performance hit ever time a
7351 file is removed, and thought it best to that that slowdown once a day
7352 instead of during my work.&lt;/p&gt;
7353
7354 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
7355 this is already done by Debian Edu.&lt;/p&gt;
7356
7357 &lt;p&gt;I have not yet started on the user space tuning. I expect
7358 iceweasel need some tuning, and perhaps other applications too, but
7359 have not yet had time to investigate those parts.&lt;/p&gt;
7360
7361 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
7362 there.&lt;/p&gt;
7363
7364 &lt;p&gt;As for the answer to the question in the title of this blog post,
7365 as far as I know, the only solution I know about is to replace the
7366 disk. It might be possible to flash it with Intel firmware instead of
7367 the Lenovo firmware. But I have not tried and did not want to do so
7368 without approval from Lenovo as I wanted to keep the warranty on the
7369 disk until a solution was found and they wanted the broken disks
7370 back.&lt;/p&gt;
7371 </description>
7372 </item>
7373
7374 <item>
7375 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
7376 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
7377 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</guid>
7378 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
7379 <description>&lt;p&gt;A few days ago, I wrote about
7380 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
7381 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
7382 was dying during installation because it is unable to cope with
7383 sustained write. My supplier is in contact with
7384 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
7385 replacement disk to try to fix the problem. They decided to send an
7386 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
7387
7388 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
7389 Debian Edu Wheezy with encrypted disk on it. The new disk have the
7390 same firmware version as the original. This time my hope raised
7391 slightly as the installation progressed, as the original disk used to
7392 die after 4-7% of the disk was written to, while this time it kept
7393 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
7394 died again and I was back on square one. I still do not have a new
7395 laptop with a disk I can trust. I can not live with a disk that might
7396 lock up when I download a new
7397 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
7398 other large files. I look forward to hearing from my supplier with
7399 the next proposal from Lenovo.&lt;/p&gt;
7400
7401 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
7402 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
7403 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
7404 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
7405 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
7406 P/N 45N8295, P0C38732.&lt;/p&gt;
7407
7408 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
7409 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
7410 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
7411 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
7412 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
7413 P/N 45N8295, P0C38732.&lt;/p&gt;
7414
7415 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
7416 SA, date and WNPP values. Mentioning all the details here in case
7417 someone is able to use the information to find a way to identify the
7418 failing disk among working ones (if any such working disk actually
7419 exist).&lt;/p&gt;
7420 </description>
7421 </item>
7422
7423 <item>
7424 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
7425 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
7426 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
7427 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
7428 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
7429 Debian Edu developer gathering and Debian and Ubuntu bug squashing
7430 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
7431 member assosiation NUUG&lt;/a&gt; and
7432 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
7433 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
7434 Bitraf&lt;/a&gt;.&lt;/p&gt;
7435
7436 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
7437 welcome, and there is no fee to participate. There is on the other
7438 hand limited space, and only room for 30 people. Please put your name
7439 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
7440 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
7441 </description>
7442 </item>
7443
7444 <item>
7445 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
7446 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
7447 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
7448 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
7449 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
7450 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
7451 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
7452 time to spend on it, and it took a while to find a model I believe
7453 will do the job, but two days ago the replacement finally arrived. I
7454 ended up picking a
7455 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
7456 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
7457 a roaming workstation, and it seemed to work flawlessly. But my
7458 second installation with encrypted disk was not as successful. More
7459 on that below.&lt;/p&gt;
7460
7461 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
7462 important requirements (robust and with a good keyboard) are never
7463 listed in the feature list. But I did get good help from the search
7464 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
7465 allowed me to limit the list of interesting laptops based on my other
7466 requirements. A bit surprising that SSD disk are not disks according
7467 to that search interface, so I had to drop specifying the number of
7468 disks from my search parameters. I also asked around among friends to
7469 get their impression on keyboards and robustness.&lt;/p&gt;
7470
7471 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
7472 X41. I am not quite convinced about the keyboard, as it is
7473 significantly wider than my old keyboard, and I have to stretch my
7474 hand a lot more to reach the edges. But the key response is fairly
7475 good and the individual key shape is fairly easy to handle, so I hope
7476 I will get used to it. My old X40 was starting to fail, and I really
7477 needed a new laptop now. :)&lt;/p&gt;
7478
7479 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
7480 visit to the BIOS during boot it disable it.&lt;/p&gt;
7481
7482 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
7483 lock up during load. And this happen when installing Debian Wheezy
7484 with encrypted disk, while the disk is being filled with random data.
7485 I also tested to install Ubuntu Raring, and it happen there too if I
7486 reenable the code to fill the disk with random data (it is disabled by
7487 default in Ubuntu). And the bug with is already known. It was
7488 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
7489 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
7490 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
7491 kernel developers as
7492 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
7493 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
7494 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
7495 Lenovo forums, both for
7496 &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
7497 2012-11-10&lt;/a&gt; and for
7498 &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
7499 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
7500 reports state that the disk lock up during use if many writes are done
7501 on the disk, so it is much no use to work around the installation
7502 problem and end up with a computer that can lock up at any moment.
7503 There is even a
7504 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
7505 available&lt;/a&gt; that will lock up the hard drive after running a few
7506 minutes by writing to a file.&lt;/p&gt;
7507
7508 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
7509 contacting PCHELP Norway (request 01D1FDP) which handle support
7510 requests for Lenovo, his first suggestion was to upgrade the disk
7511 firmware. Unfortunately there is no newer firmware available from
7512 Lenovo, as my disk already have the most recent one (version LF1i). I
7513 hope to hear more from him today and hope the problem can be
7514 fixed. :)&lt;/p&gt;
7515 </description>
7516 </item>
7517
7518 <item>
7519 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
7520 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
7521 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
7522 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
7523 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
7524 trusty old Thinkpad X41. Unfortunately I did not have much time to
7525 spend on it, but today the replacement finally arrived. I ended up
7526 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
7527 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
7528 Wheezy as a roaming workstation, and it worked flawlessly. As I write
7529 this, it is installing what I hope will be a more final installation,
7530 with a encrypted hard drive to ensure any dope head stealing it end up
7531 with an expencive door stop.&lt;/p&gt;
7532
7533 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
7534 important requirements (robust and with a good keyboard) are never
7535 listed in the feature list. But I did get good help from the search
7536 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
7537 allowed me to limit the list of interesting laptops based on my other
7538 requirements. A bit surprising that SSD disk are not disks, so I had
7539 to drop number of disks from my search parameters.&lt;/p&gt;
7540
7541 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
7542 wider than my old keyboard, and I have to stretch my hand a lot more
7543 to reach the edges. But the key response is fairly good and the
7544 individual key shape is fairly easy to handle, so I hope I will get
7545 used to it. My old X40 was starting to fail, and I really needed a
7546 new laptop now. :)&lt;/p&gt;
7547
7548 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
7549 </description>
7550 </item>
7551
7552 <item>
7553 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
7554 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
7555 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
7556 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
7557 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
7558 perfectly capable of, and I have to do it manually to get things
7559 working. One such task is to find out what firmware packages are
7560 needed to get the hardware on my computer working. Most often this
7561 affect the wifi card, but some times it even affect the RAID
7562 controller or the ethernet card. Today I pushed version 0.4 of the
7563 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
7564 including a new script isenkram-autoinstall-firmware handling the
7565 process of asking all the loaded kernel modules what firmware files
7566 they want, find debian packages providing these files and install the
7567 debian packages. Here is a test run on my laptop:&lt;/p&gt;
7568
7569 &lt;p&gt;&lt;pre&gt;
7570 # isenkram-autoinstall-firmware
7571 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
7572 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
7573 info: locating packages with the requested firmware files
7574 info: Updating APT sources after adding non-free APT source
7575 info: trying to install firmware-ipw2x00
7576 firmware-ipw2x00
7577 firmware-ipw2x00
7578 Preconfiguring packages ...
7579 Selecting previously deselected package firmware-ipw2x00.
7580 (Reading database ... 259727 files and directories currently installed.)
7581 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
7582 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
7583 #
7584 &lt;/pre&gt;&lt;/p&gt;
7585
7586 &lt;p&gt;When all the requested firmware is present, a simple message is
7587 printed instead:&lt;/p&gt;
7588
7589 &lt;p&gt;&lt;pre&gt;
7590 # isenkram-autoinstall-firmware
7591 info: did not find any firmware files requested by loaded kernel modules. exiting
7592 #
7593 &lt;/pre&gt;&lt;/p&gt;
7594
7595 &lt;p&gt;It could use some polish, but it is already working well and saving
7596 me some time when setting up new machines. :)&lt;/p&gt;
7597
7598 &lt;p&gt;So, how does it work? It look at the set of currently loaded
7599 kernel modules, and look up each one of them using modinfo, to find
7600 the firmware files listed in the module meta-information. Next, it
7601 download the Contents file from a nearby APT mirror, and search for
7602 the firmware files in this file to locate the package with the
7603 requested firmware file. If the package is in the non-free section, a
7604 non-free APT source is added and the package is installed using
7605 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
7606 machine.&lt;/p&gt;
7607
7608 &lt;p&gt;I hope someone find time to implement a more polished version of
7609 this script as part of the hw-detect debian-installer module, to
7610 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
7611 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
7612 firmware during a PXE install when the packages already are available
7613 from the nearby Debian mirror.&lt;/p&gt;
7614 </description>
7615 </item>
7616
7617 <item>
7618 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
7619 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
7620 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
7621 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
7622 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
7623 the screen just turn black when Linux boot, either during installation
7624 or on first boot from the hard disk. I&#39;ve seen it once in a while the
7625 last few years, but only recently understood the cause. I&#39;ve seen it
7626 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
7627 The reason seem to be in the wiring of some laptops. The system to
7628 control the screen background light is inverted, so when Linux try to
7629 turn the brightness fully on, it end up turning it off instead. I do
7630 not know which Linux drivers are affected, but this post is about the
7631 i915 driver used by the
7632 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
7633 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
7634
7635 &lt;p&gt;The problem can be worked around two ways. Either by adding
7636 i915.invert_brightness=1 as a kernel option, or by adding a file in
7637 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
7638 option when it load the i915 kernel module. On Debian and Ubuntu, it
7639 can be done by running these commands as root:&lt;/p&gt;
7640
7641 &lt;pre&gt;
7642 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
7643 update-initramfs -u -k all
7644 &lt;/pre&gt;
7645
7646 &lt;p&gt;Since March 2012 there is
7647 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
7648 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
7649 hardware have this problem, and get the driver to invert the
7650 brightness setting automatically. To use it, one need to add a row in
7651 &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
7652 intel_quirks array&lt;/a&gt; in the driver source
7653 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
7654 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
7655 number (vendor number 8086 is assumed) and subdevice vendor and device
7656 number.&lt;/p&gt;
7657
7658 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
7659 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
7660
7661 &lt;p&gt;&lt;pre&gt;
7662 00:02.0 VGA compatible controller [0300]: Intel Corporation \
7663 3rd Gen Core processor Graphics Controller [8086:0156] \
7664 (rev 09) (prog-if 00 [VGA controller])
7665 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
7666 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
7667 ParErr- Stepping- SE RR- FastB2B- DisINTx+
7668 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
7669 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
7670 Latency: 0
7671 Interrupt: pin A routed to IRQ 42
7672 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
7673 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
7674 Region 4: I/O ports at 4000 [size=64]
7675 Expansion ROM at &lt;unassigned&gt; [disabled]
7676 Capabilities: &lt;access denied&gt;
7677 Kernel driver in use: i915
7678 &lt;/pre&gt;&lt;/p&gt;
7679
7680 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
7681
7682 &lt;p&gt;&lt;pre&gt;
7683 struct intel_quirk intel_quirks[] = {
7684 ...
7685 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
7686 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
7687 ...
7688 }
7689 &lt;/pre&gt;&lt;/p&gt;
7690
7691 &lt;p&gt;According to the kernel module instructions (as seen using
7692 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
7693 invert_brightness flag should be sent to the
7694 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
7695 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
7696 developers. But my email about the laptop sent 2013-06-03 have not
7697 yet shown up in
7698 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
7699 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
7700 emails from non-subscribers. Because of this, I sent my patch also to
7701 the Debian bug tracking system instead as
7702 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
7703 sure the patch is not lost.&lt;/p&gt;
7704
7705 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
7706 with this problem working properly with Linux. If you use Gnome, your
7707 worries should be over at this point. But if you use KDE, there is
7708 something in KDE ignoring the invert_brightness setting and turning on
7709 the screen during login. I&#39;ve reported it to Debian as
7710 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
7711 have no idea yet how to figure out exactly what subsystem is doing
7712 this. Perhaps you can help? Perhaps you know what the Gnome
7713 developers did to handle this, and this can give a clue to the KDE
7714 developers? Or you know where in KDE the screen brightness is changed
7715 during login? If so, please update the BTS report (or get in touch if
7716 you do not know how to update BTS).&lt;/p&gt;
7717
7718 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
7719 acpi_backlight=vendor, to disable ACPI backlight support completely,
7720 as the ACPI information on the machine is trash and it is better to
7721 leave it to the intel video driver to control the screen
7722 backlight.&lt;/p&gt;
7723 </description>
7724 </item>
7725
7726 <item>
7727 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
7728 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
7729 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</guid>
7730 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
7731 <description>&lt;p&gt;Two days ago, I asked
7732 &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
7733 I could install Linux on a Packard Bell EasyNote LV computer
7734 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
7735 with the obstacles put in the way of Linux users on a laptop with UEFI
7736 and Windows 8.&lt;/p&gt;
7737
7738 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
7739 secure booting or fast boot. I suspect fast boot was the problem,
7740 causing the firmware to boot directly from HD without considering any
7741 key presses and alternative devices, but do not know UEFI settings
7742 enough to tell.&lt;/p&gt;
7743
7744 &lt;p&gt;There is no way to install Linux on the machine in question without
7745 opening the box and disconnecting the hard drive! This is as far as I
7746 can tell, the only way to get access to the firmware setup menu
7747 without accepting the Windows 8 license agreement. I am told (and
7748 found description on how to) that it is possible to configure the
7749 firmware setup once booted into Windows 8. But as I believe the terms
7750 of that agreement are completely unacceptable, accepting the license
7751 was never an alternative. I do not enter agreements I do not intend
7752 to follow.&lt;/p&gt;
7753
7754 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
7755 waste many hours on this, but luckily there was a way to get it to
7756 work. But I would not recommend it to anyone planning to run Linux on
7757 it, and I have become sceptical to Windows 8 certified laptops. Is
7758 this the way Linux will be forced out of the market place, by making
7759 it close to impossible for &quot;normal&quot; users to install Linux without
7760 accepting the Microsoft Windows license terms? Or at least not
7761 without risking to loose the warranty?&lt;/p&gt;
7762
7763 &lt;p&gt;I&#39;ve updated the
7764 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
7765 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
7766 do not have to struggle as much as I did to get Linux into the
7767 machine.&lt;/p&gt;
7768
7769 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
7770 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
7771 </description>
7772 </item>
7773
7774 <item>
7775 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
7776 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
7777 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</guid>
7778 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
7779 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
7780 new laptops for my parents and a few others. I bought Packard Bell
7781 Easynote LV to run Kubuntu on and use as their home computer. But I
7782 am completely unable to figure out how to install Linux on it. The
7783 computer is preinstalled with Windows 8, and I suspect it uses UEFI
7784 instead of a BIOS to boot.&lt;/p&gt;
7785
7786 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
7787 to get it to boot the Linux installer from my USB stick. I have yet
7788 to try the DVD install, and still hope it will work. when I turn on
7789 the computer, there is no information on what buttons to press to get
7790 the normal boot menu. I expect to get some boot menu to select PXE or
7791 USB stick booting. When booting, it first ask for the language to
7792 use, then for some regional settings, and finally if I will accept the
7793 Windows 8 terms of use. As these terms are completely unacceptable to
7794 me, I have no other choice but to turn off the computer and try again
7795 to get it to boot the Linux installer.&lt;/p&gt;
7796
7797 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
7798 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
7799 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
7800 installed on this machine, please get in touch or update that wiki
7801 page. If I can&#39;t find a way to install Linux, I will have to return
7802 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
7803
7804 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
7805 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
7806 on new Laptops?&lt;/p&gt;
7807 </description>
7808 </item>
7809
7810 <item>
7811 <title>How to transform a Debian based system to a Debian Edu installation</title>
7812 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
7813 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
7814 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
7815 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
7816 an operating system based on Debian intended for use in schools. It
7817 contain a turn-key solution for the computer network provided to
7818 pupils in the primary schools. It provide both the central server,
7819 network boot servers and desktop environments with heaps of
7820 educational software. The project was founded almost 12 years ago,
7821 2001-07-02. If you want to support the project, which is in need for
7822 cash to fund developer gatherings and other project related activity,
7823 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
7824 donate some money&lt;/a&gt;.
7825
7826 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
7827 lists and elsewhere, is the question on how to transform a Debian or
7828 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
7829 hard, and last week I wrote a script to replicate the steps done by
7830 the Debian Edu installer.&lt;/p&gt;
7831
7832 &lt;p&gt;The script,
7833 &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;
7834 in the debian-edu-config package, will go through these six steps and
7835 transform an existing Debian Wheezy or Ubuntu (untested) installation
7836 into a Debian Edu Workstation:&lt;/p&gt;
7837
7838 &lt;ol&gt;
7839
7840 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
7841 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
7842 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
7843 our configuration.&lt;/li&gt;
7844 &lt;li&gt;Preseed debconf database with profile setup in
7845 /etc/debian-edu/config, and run tasksel to install packages
7846 according to the profile specified in the config above,
7847 overriding some of the Debian automation machinery.&lt;/li&gt;
7848 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
7849 that could not be done using preseeding.&lt;/li&gt;
7850 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
7851
7852 &lt;/ol&gt;
7853
7854 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
7855 replicated like this. Disk partitioning and LVM setup, for example.
7856 So this script just assume there is enough disk space to install all
7857 the needed packages.&lt;/p&gt;
7858
7859 &lt;p&gt;The script was created to help a Debian Edu student working on
7860 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
7861 Debian Edu client, and using it he can take the existing
7862 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
7863 transform it into a fully functioning Debian Edu Workstation (or
7864 Roaming Workstation, or whatever :).&lt;/p&gt;
7865
7866 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
7867 If a LXDE based Roaming workstation is wanted instead, modify the
7868 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
7869
7870 &lt;p&gt;&lt;pre&gt;
7871 PROFILE=&quot;Roaming-Workstation&quot;
7872 DESKTOP=&quot;lxde&quot;
7873 &lt;/pre&gt;&lt;/p&gt;
7874
7875 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
7876 the cloud, by starting with a virtual Debian installation at some
7877 virtual hosting service and setting up all the services on first
7878 boot.&lt;/p&gt;
7879 </description>
7880 </item>
7881
7882 <item>
7883 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
7884 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
7885 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
7886 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
7887 <description>&lt;P&gt;In January,
7888 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
7889 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
7890 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
7891 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
7892 marvellous construction system from Denmark. We also created
7893 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
7894 a place to take notes and write down our plans and hopes. And several
7895 people showed up to help. I was very happy to see the effect of my
7896 call. Since the small start, we have a debtags tag
7897 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
7898 tag for LEGO related packages, and now count 10 packages related to
7899 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
7900
7901 &lt;p&gt;&lt;table&gt;
7902 &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;
7903 &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;
7904 &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;
7905 &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;
7906 &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;
7907 &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;
7908 &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;
7909 &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;
7910 &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;
7911 &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;
7912 &lt;/table&gt;&lt;/p&gt;
7913
7914 &lt;p&gt;Some of these are available in Wheezy, and all but one are
7915 currently available in Jessie/testing. leocad is so far only
7916 available in experimental.&lt;/p&gt;
7917
7918 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
7919 adding the rest of the great free software tools available on Linux
7920 for LEGO designers.&lt;/p&gt;
7921 </description>
7922 </item>
7923
7924 <item>
7925 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
7926 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
7927 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
7928 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
7929 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
7930 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
7931 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
7932 Debian release, and I expect to move my machines at home over to it fairly
7933 soon.&lt;/p&gt;
7934
7935 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
7936 in particular make me very happy to see included. The
7937 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
7938 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
7939 included for the first time. Alongside similar programs like
7940 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
7941 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
7942 it allow for visual programming where syntax errors can not happen,
7943 and a friendly programming environment for learning to control the
7944 computer. Scratch will also be included in the next release of Debian
7945 Edu.&lt;/a&gt;
7946
7947 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
7948 Edu/Skolelinux release too. The
7949 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
7950 alpha release&lt;/a&gt; went out last week, and the next should soon
7951 follow.&lt;p&gt;
7952 </description>
7953 </item>
7954
7955 <item>
7956 <title>Isenkram 0.2 finally in the Debian archive</title>
7957 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
7958 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
7959 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
7960 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
7961 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
7962 for many months. I uploaded it to the Debian experimental suite
7963 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
7964
7965 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
7966 install to work with a pluggable hardware device. The suggestion pop
7967 up when the device is plugged in. For example if a Lego Mindstorm NXT
7968 is inserted, it will suggest to install the program needed to program
7969 the NXT controller. Give it a go, and report bugs and suggestions to
7970 BTS. :)&lt;/p&gt;
7971 </description>
7972 </item>
7973
7974 <item>
7975 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
7976 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
7977 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
7978 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
7979 <description>&lt;p&gt;My
7980 &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
7981 bitcoin related blog post&lt;/a&gt; mentioned that the new
7982 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
7983 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
7984 2013-01-19, and have been available in unstable since then. It was
7985 automatically copied to Ubuntu, and is available in their Raring
7986 version too.&lt;/p&gt;
7987
7988 &lt;p&gt;But there is a strange problem with the build that block this new
7989 version from being available on the i386 and kfreebsd-i386
7990 architectures. For some strange reason, the autobuilders in Debian
7991 for these architectures fail to run the test suite on these
7992 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
7993 We are so far unable to reproduce it when building it manually, and
7994 no-one have been able to propose a fix. If you got an idea what is
7995 failing, please let us know via the BTS.&lt;/p&gt;
7996
7997 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
7998 I often run low on disk space, is the fact that the client will exit
7999 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
8000 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
8001 it. :)&lt;/p&gt;
8002
8003 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
8004 activities, please send Bitcoin donations to my address
8005 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8006 </description>
8007 </item>
8008
8009 <item>
8010 <title>Welcome to the world, Isenkram!</title>
8011 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
8012 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
8013 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
8014 <description>&lt;p&gt;Yesterday, I
8015 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
8016 for testers&lt;/a&gt; for my prototype for making Debian better at handling
8017 pluggable hardware devices, which I
8018 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
8019 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
8020 up, and caused me to really want to to open up the development to more
8021 people. But before I did this, I want to come up with a sensible name
8022 for this project. Today I finally decided on a new name, and I have
8023 renamed the project from hw-support-handler to this new name. In the
8024 process, I moved the source to git and made it available as a
8025 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
8026 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
8027 To fetch and build the latest version of the source, use&lt;/p&gt;
8028
8029 &lt;pre&gt;
8030 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8031 cd isenkram &amp;&amp; git-buildpackage -us -uc
8032 &lt;/pre&gt;
8033
8034 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
8035 want to hack on the source or improve the package, please go ahead.
8036 But please talk to me first on IRC or via email before you do major
8037 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
8038
8039 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
8040 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8041 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
8042 the German word eisenkram, for those that are familiar with that
8043 word.&lt;/p&gt;
8044
8045 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
8046 instructions, to avoid confusing people with an error from the signing
8047 process.&lt;/p&gt;
8048
8049 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
8050 clone argument to avoid the need for authentication.&lt;/p&gt;
8051 </description>
8052 </item>
8053
8054 <item>
8055 <title>First prototype ready making hardware easier to use in Debian</title>
8056 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
8057 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
8058 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
8059 <description>&lt;p&gt;Early this month I set out to try to
8060 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
8061 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
8062 prototype is working, and it is ready for a larger audience. To test
8063 it, fetch the
8064 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
8065 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
8066 package. You might have to log out and in again activate the
8067 autostart script.&lt;/p&gt;
8068
8069 &lt;p&gt;The design is simple:&lt;/p&gt;
8070
8071 &lt;ul&gt;
8072
8073 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
8074 hw-support-handlerd to start when the user log in.&lt;/li&gt;
8075
8076 &lt;li&gt;This program listen for kernel events about new hardware (directly
8077 from the kernel like udev does), not using HAL dbus events as I
8078 initially did.&lt;/li&gt;
8079
8080 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
8081 the APT database, a database
8082 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
8083 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
8084
8085 &lt;li&gt;If a package is mapped to the hardware in question, the package
8086 isn&#39;t installed yet and this is the first time the hardware was
8087 plugged in, show a desktop notification suggesting to install the
8088 package or packages.&lt;/li&gt;
8089
8090 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
8091 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
8092
8093 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
8094 package while showing progress information in a window.&lt;/li&gt;
8095
8096 &lt;/ul&gt;
8097
8098 &lt;p&gt;I still need to come up with a better name for the system. Here
8099 are some screen shots showing the prototype in action. First the
8100 notification, then the password request, and finally the request to
8101 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
8102
8103 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
8104 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
8105 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
8106 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
8107 &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;
8108
8109 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
8110 is already useful. The database of hardware to package mappings also
8111 need more work. It is currently compatible with the Ubuntu way of
8112 storing such information in the package control file, but could be
8113 changed to use other formats instead or in addition to the current
8114 method. I&#39;ve dropped the use of discover for this mapping, as the
8115 modalias approach is more flexible and easier to use on Linux as long
8116 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
8117
8118 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
8119 here is the command required to check out and build the source: Use
8120 &#39;&lt;tt&gt;svn checkout
8121 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8122 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
8123 devscripts package.&lt;/p&gt;
8124
8125 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
8126 renamed to Isenkram and the source moved from the Debian Edu
8127 subversion repository to a Debian collab-maint git repository. See
8128 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
8129 instructions&lt;/a&gt; for details.&lt;/p&gt;
8130 </description>
8131 </item>
8132
8133 <item>
8134 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
8135 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
8136 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
8137 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
8138 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
8139 suddenly in bed. With a quiet whimper, it went completely quiet and
8140 black. The power button was no longer able to turn it on. It was a
8141 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8142 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8143 Compaq I had before that. Now I need to find a replacement. To keep
8144 going during Christmas, I moved the one year old SSD disk to my old
8145 X40 where it fitted (only one I had left that could use it), but it is
8146 not a durable solution.
8147
8148 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
8149 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
8150
8151 &lt;ul&gt;
8152
8153 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
8154 than A4).&lt;/li&gt;
8155 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
8156 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
8157 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
8158 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
8159 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
8160 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
8161 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
8162 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
8163 size).&lt;/li&gt;
8164 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
8165 X.org packages.&lt;/li&gt;
8166 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
8167 the time).
8168
8169 &lt;/ul&gt;
8170
8171 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
8172 list. The reason is simply that the specifications on laptops the
8173 last 10-15 years have been sufficient for my needs, and I have to look
8174 at other features to choose my laptop. But are there still made as
8175 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8176 robust, and Thinkpads seem to be heading in the wrong direction since
8177 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
8178 still be useful.&lt;/p&gt;
8179
8180 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
8181 external keyboard? I&#39;ll have to check the
8182 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
8183 well-supported laptops, or perhaps just buy one preinstalled from one
8184 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
8185 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
8186 </description>
8187 </item>
8188
8189 <item>
8190 <title>How to find a browser plugin supporting a given MIME type</title>
8191 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
8192 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
8193 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
8194 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
8195 install to get support for a given MIME type. Thanks to
8196 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
8197 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
8198 Unfortunately, not very many packages provide the needed meta
8199 information, Anyway, here is a small script to look up all browser
8200 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
8201
8202 &lt;pre&gt;
8203 #!/usr/bin/python
8204 import sys
8205 import apt
8206 def pkgs_handling_mimetype(mimetype):
8207 cache = apt.Cache()
8208 cache.open(None)
8209 thepkgs = []
8210 for pkg in cache:
8211 version = pkg.candidate
8212 if version is None:
8213 version = pkg.installed
8214 if version is None:
8215 continue
8216 record = version.record
8217 if not record.has_key(&#39;Npp-MimeType&#39;):
8218 continue
8219 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
8220 for t in mime_types:
8221 t = t.rstrip().strip()
8222 if t == mimetype:
8223 thepkgs.append(pkg.name)
8224 return thepkgs
8225 mimetype = &quot;audio/ogg&quot;
8226 if 1 &lt; len(sys.argv):
8227 mimetype = sys.argv[1]
8228 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
8229 for pkg in pkgs_handling_mimetype(mimetype):
8230 print &quot; %s&quot; %pkg
8231 &lt;/pre&gt;
8232
8233 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
8234
8235 &lt;pre&gt;
8236 % ./apt-find-browserplug-for-mimetype
8237 Browser plugin packages supporting audio/ogg:
8238 gecko-mediaplayer
8239 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
8240 Browser plugin packages supporting application/x-shockwave-flash:
8241 browser-plugin-gnash
8242 %
8243 &lt;/pre&gt;
8244
8245 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
8246 itself to query for plugins and propose to install the needed
8247 packages. It would be great if Debian supported such feature too. Is
8248 anyone working on adding it?&lt;/p&gt;
8249
8250 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
8251 request for icweasel support for this feature is
8252 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
8253 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
8254 of manpower and wish for a different design is the reason thus feature
8255 is not yet in iceweasel from Debian.&lt;/p&gt;
8256 </description>
8257 </item>
8258
8259 <item>
8260 <title>What is the most supported MIME type in Debian?</title>
8261 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
8262 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
8263 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
8264 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
8265 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
8266 proposal to make it possible for a Desktop application to propose to
8267 the user some package to install to gain support for a given MIME
8268 type, font, library etc. that is currently missing. With such
8269 mechanism in place, it would be possible for the desktop to
8270 automatically propose and install leocad if some LDraw file is
8271 downloaded by the browser.&lt;/p&gt;
8272
8273 &lt;p&gt;To get some idea about the current content of the archive, I decided
8274 to write a simple program to extract all .desktop files from the
8275 Debian archive and look up the claimed MIME support there. The result
8276 can be found on the
8277 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
8278 site&lt;/a&gt;. Using the collected information, it become possible to
8279 answer the question in the title. Here are the 20 most supported MIME
8280 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
8281 The complete list is available from the link above.&lt;/p&gt;
8282
8283 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
8284
8285 &lt;pre&gt;
8286 count MIME type
8287 ----- -----------------------
8288 32 text/plain
8289 30 audio/mpeg
8290 29 image/png
8291 28 image/jpeg
8292 27 application/ogg
8293 26 audio/x-mp3
8294 25 image/tiff
8295 25 image/gif
8296 22 image/bmp
8297 22 audio/x-wav
8298 20 audio/x-flac
8299 19 audio/x-mpegurl
8300 18 video/x-ms-asf
8301 18 audio/x-musepack
8302 18 audio/x-mpeg
8303 18 application/x-ogg
8304 17 video/mpeg
8305 17 audio/x-scpls
8306 17 audio/ogg
8307 16 video/x-ms-wmv
8308 &lt;/pre&gt;
8309
8310 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
8311
8312 &lt;pre&gt;
8313 count MIME type
8314 ----- -----------------------
8315 33 text/plain
8316 32 image/png
8317 32 image/jpeg
8318 29 audio/mpeg
8319 27 image/gif
8320 26 image/tiff
8321 26 application/ogg
8322 25 audio/x-mp3
8323 22 image/bmp
8324 21 audio/x-wav
8325 19 audio/x-mpegurl
8326 19 audio/x-mpeg
8327 18 video/mpeg
8328 18 audio/x-scpls
8329 18 audio/x-flac
8330 18 application/x-ogg
8331 17 video/x-ms-asf
8332 17 text/html
8333 17 audio/x-musepack
8334 16 image/x-xbitmap
8335 &lt;/pre&gt;
8336
8337 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
8338
8339 &lt;pre&gt;
8340 count MIME type
8341 ----- -----------------------
8342 31 text/plain
8343 31 image/png
8344 31 image/jpeg
8345 29 audio/mpeg
8346 28 application/ogg
8347 27 image/gif
8348 26 image/tiff
8349 26 audio/x-mp3
8350 23 audio/x-wav
8351 22 image/bmp
8352 21 audio/x-flac
8353 20 audio/x-mpegurl
8354 19 audio/x-mpeg
8355 18 video/x-ms-asf
8356 18 video/mpeg
8357 18 audio/x-scpls
8358 18 application/x-ogg
8359 17 audio/x-musepack
8360 16 video/x-ms-wmv
8361 16 video/x-msvideo
8362 &lt;/pre&gt;
8363
8364 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
8365 information mentioned in DEP-11. I have not yet had time to look at
8366 it, but hope the PackageKit people in Debian are on top of these
8367 issues.&lt;/p&gt;
8368
8369 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
8370 discovering a typo in my script.&lt;/p&gt;
8371 </description>
8372 </item>
8373
8374 <item>
8375 <title>Using modalias info to find packages handling my hardware</title>
8376 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
8377 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
8378 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
8379 <description>&lt;p&gt;Yesterday, I wrote about the
8380 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
8381 values provided by the Linux kernel&lt;/a&gt; following my hope for
8382 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
8383 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
8384 modalias values attached to package names can be used to map packages
8385 to hardware. This allow the system to look up and suggest relevant
8386 packages when I plug in some new hardware into my machine, and replace
8387 discover and discover-data as the database used to map hardware to
8388 packages.&lt;/p&gt;
8389
8390 &lt;p&gt;I create a modaliases file with entries like the following,
8391 containing package name, kernel module name (if relevant, otherwise
8392 the package name) and globs matching the relevant hardware
8393 modalias.&lt;/p&gt;
8394
8395 &lt;p&gt;&lt;blockquote&gt;
8396 Package: package-name
8397 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
8398 &lt;/blockquote&gt;&lt;/p&gt;
8399
8400 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
8401 for a given modalias value using this file.&lt;/p&gt;
8402
8403 &lt;p&gt;An entry like this would suggest the video and picture application
8404 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
8405
8406 &lt;p&gt;&lt;blockquote&gt;
8407 Package: cheese
8408 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
8409 &lt;/blockquote&gt;&lt;/p&gt;
8410
8411 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
8412 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
8413
8414 &lt;p&gt;&lt;blockquote&gt;
8415 Package: pcmciautils
8416 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
8417 &lt;/blockquote&gt;&lt;/p&gt;
8418
8419 &lt;p&gt;An entry like this would suggest the package colorhug-client when
8420 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
8421
8422 &lt;p&gt;&lt;blockquote&gt;
8423 Package: colorhug-client
8424 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
8425 &lt;/blockquote&gt;&lt;/p&gt;
8426
8427 &lt;p&gt;I believe the format is compatible with the format of the Packages
8428 file in the Debian archive. Ubuntu already uses their Packages file
8429 to store their mappings from packages to hardware.&lt;/p&gt;
8430
8431 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
8432 announce the hardware it support in a way my prototype understand.
8433 This allow those publishing packages in an APT source outside the
8434 Debian archive as well as those backporting packages to make sure the
8435 hardware mapping are included in the package meta information. I&#39;ve
8436 tested such header in the pymissile package, and its modalias mapping
8437 is working as it should with my prototype. It even made it to Ubuntu
8438 Raring.&lt;/p&gt;
8439
8440 &lt;p&gt;To test if it was possible to look up supported hardware using only
8441 the shell tools available in the Debian installer, I wrote a shell
8442 implementation of the lookup code. The idea is to create files for
8443 each modalias and let the shell do the matching. Please check out and
8444 try the
8445 &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;
8446 shell script. It run without any extra dependencies and fetch the
8447 hardware mappings from the Debian archive and the subversion
8448 repository where I currently work on my prototype.&lt;/p&gt;
8449
8450 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
8451 install yubikey-personalization:&lt;/p&gt;
8452
8453 &lt;p&gt;&lt;blockquote&gt;
8454 % ./hw-support-lookup
8455 &lt;br&gt;yubikey-personalization
8456 &lt;br&gt;%
8457 &lt;/blockquote&gt;&lt;/p&gt;
8458
8459 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
8460 propose to install the pcmciautils package:&lt;/p&gt;
8461
8462 &lt;p&gt;&lt;blockquote&gt;
8463 % ./hw-support-lookup
8464 &lt;br&gt;pcmciautils
8465 &lt;br&gt;%
8466 &lt;/blockquote&gt;&lt;/p&gt;
8467
8468 &lt;p&gt;If you know of any hardware-package mapping that should be added to
8469 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
8470 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
8471
8472 &lt;p&gt;It could be possible to generate several of the mappings between
8473 packages and hardware. One source would be to look at packages with
8474 kernel modules, ie packages with *.ko files in /lib/modules/, and
8475 extract their modalias information. Another would be to look at
8476 packages with udev rules, ie packages with files in
8477 /lib/udev/rules.d/, and extract their vendor/model information to
8478 generate a modalias matching rule. I have not tested any of these to
8479 see if it work.&lt;/p&gt;
8480
8481 &lt;p&gt;If you want to help implementing a system to let us propose what
8482 packages to install when new hardware is plugged into a Debian
8483 machine, please send me an email or talk to me on
8484 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
8485 </description>
8486 </item>
8487
8488 <item>
8489 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
8490 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
8491 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
8492 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
8493 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
8494 information, to find the packages that support a given piece of
8495 hardware, I refreshed my memory regarding modalias values, and decided
8496 to document the details. Here are my findings so far, also available
8497 in
8498 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
8499 Debian Edu subversion repository&lt;/a&gt;:
8500
8501 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
8502
8503 &lt;p&gt;This document try to explain what the different types of modalias
8504 values stands for. It is in part based on information from
8505 &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;,
8506 &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;,
8507 &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
8508 &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;.
8509
8510 &lt;p&gt;The modalias entries for a given Linux machine can be found using
8511 this shell script:&lt;/p&gt;
8512
8513 &lt;pre&gt;
8514 find /sys -name modalias -print0 | xargs -0 cat | sort -u
8515 &lt;/pre&gt;
8516
8517 &lt;p&gt;The supported modalias globs for a given kernel module can be found
8518 using modinfo:&lt;/p&gt;
8519
8520 &lt;pre&gt;
8521 % /sbin/modinfo psmouse | grep alias:
8522 alias: serio:ty05pr*id*ex*
8523 alias: serio:ty01pr*id*ex*
8524 %
8525 &lt;/pre&gt;
8526
8527 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
8528
8529 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
8530 Bridge memory controller:&lt;/p&gt;
8531
8532 &lt;p&gt;&lt;blockquote&gt;
8533 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
8534 &lt;/blockquote&gt;&lt;/p&gt;
8535
8536 &lt;p&gt;This represent these values:&lt;/p&gt;
8537
8538 &lt;pre&gt;
8539 v 00008086 (vendor)
8540 d 00002770 (device)
8541 sv 00001028 (subvendor)
8542 sd 000001AD (subdevice)
8543 bc 06 (bus class)
8544 sc 00 (bus subclass)
8545 i 00 (interface)
8546 &lt;/pre&gt;
8547
8548 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
8549 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
8550 0600. The 0600 class is a host bridge. Other useful bus values are
8551 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
8552
8553 &lt;p&gt;Not sure how to figure out the interface value, nor what it
8554 means.&lt;/p&gt;
8555
8556 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
8557
8558 &lt;p&gt;Some typical USB entries can look like this. This is an internal
8559 USB hub in a laptop:&lt;/p&gt;
8560
8561 &lt;p&gt;&lt;blockquote&gt;
8562 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
8563 &lt;/blockquote&gt;&lt;/p&gt;
8564
8565 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
8566
8567 &lt;pre&gt;
8568 v 1D6B (device vendor)
8569 p 0001 (device product)
8570 d 0206 (bcddevice)
8571 dc 09 (device class)
8572 dsc 00 (device subclass)
8573 dp 00 (device protocol)
8574 ic 09 (interface class)
8575 isc 00 (interface subclass)
8576 ip 00 (interface protocol)
8577 &lt;/pre&gt;
8578
8579 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
8580 class is in the interface class section. For a simple USB web camera,
8581 these alias entries show up:&lt;/p&gt;
8582
8583 &lt;p&gt;&lt;blockquote&gt;
8584 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
8585 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
8586 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
8587 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
8588 &lt;/blockquote&gt;&lt;/p&gt;
8589
8590 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
8591 camera), 0101 is audio control device and 0102 is audio streaming (aka
8592 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
8593
8594 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
8595
8596 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
8597 receiver in a Thinkpad X40:&lt;/p&gt;
8598
8599 &lt;p&gt;&lt;blockquote&gt;
8600 acpi:IBM0071:PNP0511:
8601 &lt;/blockquote&gt;&lt;/p&gt;
8602
8603 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
8604
8605 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
8606
8607 &lt;p&gt;The DMI table contain lots of information about the computer case
8608 and model. This is an entry for a IBM Thinkpad X40, fetched from
8609 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
8610
8611 &lt;p&gt;&lt;blockquote&gt;
8612 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
8613 &lt;/blockquote&gt;&lt;/p&gt;
8614
8615 &lt;p&gt;The values present are&lt;/p&gt;
8616
8617 &lt;pre&gt;
8618 bvn IBM (BIOS vendor)
8619 bvr 1UETB6WW(1.66) (BIOS version)
8620 bd 06/15/2005 (BIOS date)
8621 svn IBM (system vendor)
8622 pn 2371H4G (product name)
8623 pvr ThinkPadX40 (product version)
8624 rvn IBM (board vendor)
8625 rn 2371H4G (board name)
8626 rvr NotAvailable (board version)
8627 cvn IBM (chassis vendor)
8628 ct 10 (chassis type)
8629 cvr NotAvailable (chassis version)
8630 &lt;/pre&gt;
8631
8632 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
8633 found in the dmidecode source:&lt;/p&gt;
8634
8635 &lt;pre&gt;
8636 3 Desktop
8637 4 Low Profile Desktop
8638 5 Pizza Box
8639 6 Mini Tower
8640 7 Tower
8641 8 Portable
8642 9 Laptop
8643 10 Notebook
8644 11 Hand Held
8645 12 Docking Station
8646 13 All In One
8647 14 Sub Notebook
8648 15 Space-saving
8649 16 Lunch Box
8650 17 Main Server Chassis
8651 18 Expansion Chassis
8652 19 Sub Chassis
8653 20 Bus Expansion Chassis
8654 21 Peripheral Chassis
8655 22 RAID Chassis
8656 23 Rack Mount Chassis
8657 24 Sealed-case PC
8658 25 Multi-system
8659 26 CompactPCI
8660 27 AdvancedTCA
8661 28 Blade
8662 29 Blade Enclosing
8663 &lt;/pre&gt;
8664
8665 &lt;p&gt;The chassis type values are not always accurately set in the DMI
8666 table. For example my home server is a tower, but the DMI modalias
8667 claim it is a desktop.&lt;/p&gt;
8668
8669 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
8670
8671 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
8672 test machine:&lt;/p&gt;
8673
8674 &lt;p&gt;&lt;blockquote&gt;
8675 serio:ty01pr00id00ex00
8676 &lt;/blockquote&gt;&lt;/p&gt;
8677
8678 &lt;p&gt;The values present are&lt;/p&gt;
8679
8680 &lt;pre&gt;
8681 ty 01 (type)
8682 pr 00 (prototype)
8683 id 00 (id)
8684 ex 00 (extra)
8685 &lt;/pre&gt;
8686
8687 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
8688 the valid values are.&lt;/p&gt;
8689
8690 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
8691
8692 &lt;p&gt;There are heaps of other modalias subtypes according to
8693 file2alias.c. There is the rest of the list from that source: amba,
8694 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
8695 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
8696 vmbus, x86cpu and zorro. I did not spend time documenting all of
8697 these, as they do not seem relevant for my intended use with mapping
8698 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
8699
8700 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
8701
8702 &lt;p&gt;To check which kernel modules provide support for a given modalias,
8703 one can use the following shell script:&lt;/p&gt;
8704
8705 &lt;pre&gt;
8706 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
8707 echo &quot;$id&quot; ; \
8708 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
8709 done
8710 &lt;/pre&gt;
8711
8712 &lt;p&gt;The output can look like this (only the first few entries as the
8713 list is very long on my test machine):&lt;/p&gt;
8714
8715 &lt;pre&gt;
8716 acpi:ACPI0003:
8717 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
8718 acpi:device:
8719 FATAL: Module acpi:device: not found.
8720 acpi:IBM0068:
8721 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
8722 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
8723 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
8724 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
8725 acpi:IBM0071:PNP0511:
8726 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
8727 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
8728 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
8729 [...]
8730 &lt;/pre&gt;
8731
8732 &lt;p&gt;If you want to help implementing a system to let us propose what
8733 packages to install when new hardware is plugged into a Debian
8734 machine, please send me an email or talk to me on
8735 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
8736
8737 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
8738 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
8739 in /sys/ with space in them.&lt;/p&gt;
8740 </description>
8741 </item>
8742
8743 <item>
8744 <title>Moved the pymissile Debian packaging to collab-maint</title>
8745 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
8746 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
8747 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
8748 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
8749 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
8750 Launcher and updated the Debian package
8751 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
8752 sure udev will fix the device permissions when it is plugged in. I
8753 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
8754 hopefully make the package be proposed by jockey in Ubuntu when a user
8755 plug in his rocket launcher. In the process I moved the source to a
8756 git repository under collab-maint, to make it easier for any DD to
8757 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
8758 is not very active, but the software still work for me even after five
8759 years of relative silence. The new git repository is not listed in
8760 the uploaded package yet, because I want to test the other changes a
8761 bit more before I upload the new version. If you want to check out
8762 the new version with a .desktop file included, visit the
8763 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
8764 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
8765 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
8766 </description>
8767 </item>
8768
8769 <item>
8770 <title>Lets make hardware dongles easier to use in Debian</title>
8771 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
8772 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
8773 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
8774 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
8775 general, is that there is a great package management system with the
8776 ability to automatically install software packages by downloading them
8777 from the distribution mirrors, but no way to get it to automatically
8778 install the packages I need to use the hardware I plug into my
8779 machine. Even if the package to use it is easily available from the
8780 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
8781 suggest to automatically install the python-nxt, nbc and t2n packages
8782 I need to talk to it. When I plug in a Yubikey, it could propose the
8783 yubikey-personalization package. The information required to do this
8784 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
8785
8786 &lt;p&gt;Some years ago, I proposed to
8787 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
8788 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
8789 simple:
8790
8791 &lt;ul&gt;
8792
8793 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
8794 starting when a user log in.&lt;/li&gt;
8795
8796 &lt;li&gt;Set this program up to listen for kernel events emitted when new
8797 hardware is inserted into the computer.&lt;/li&gt;
8798
8799 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
8800 database mapping to packages, and take note of any non-installed
8801 packages.&lt;/li&gt;
8802
8803 &lt;li&gt;Show a message to the user proposing to install the discovered
8804 package, and make it easy to install it.&lt;/li&gt;
8805
8806 &lt;/ul&gt;
8807
8808 &lt;p&gt;I am not sure what the best way to implement this is, but my
8809 initial idea was to use dbus events to discover new hardware, the
8810 discover database to find packages and
8811 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
8812 packages.&lt;/p&gt;
8813
8814 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
8815 draft package is now checked into
8816 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
8817 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
8818 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
8819 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
8820 the relevant packages in Debian, and uploaded a new version
8821 2.2013.01.09 to unstable. I also discovered that the current
8822 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
8823 package in Debian no longer discovered any USB devices, because
8824 /proc/bus/usb/devices is no longer present. I ported it to use
8825 libusb as a fall back option to get it working. The fixed package
8826 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
8827 because of the freeze).&lt;/p&gt;
8828
8829 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
8830 desktop notification to show up (only once, the first time it is
8831 inserted):&lt;/p&gt;
8832
8833 &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;
8834
8835 &lt;p&gt;For this prototype to be really useful, some way to automatically
8836 install the proposed packages by pressing the &quot;Please install
8837 program(s)&quot; button should to be implemented.&lt;/p&gt;
8838
8839 &lt;p&gt;If this idea seem useful to you, and you want to help make it
8840 happen, please help me update the discover-data database with mappings
8841 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
8842 list the package you would like to have installed when a given
8843 hardware device is inserted into your computer, and report bugs using
8844 reportbug if it isn&#39;t. Or, if you know of a better way to provide
8845 such mapping, please let me know.&lt;/p&gt;
8846
8847 &lt;p&gt;This prototype need more work, and there are several questions that
8848 should be considered before it is ready for production use. Is dbus
8849 the correct way to detect new hardware? At the moment I look for HAL
8850 dbus events on the system bus, because that is the events I could see
8851 on my Debian Squeeze KDE desktop. Are there better events to use?
8852 How should the user be notified? Is the desktop notification
8853 mechanism the best option, or should the background daemon raise a
8854 popup instead? How should packages be installed? When should they
8855 not be installed?&lt;/p&gt;
8856
8857 &lt;p&gt;If you want to help getting such feature implemented in Debian,
8858 please send me an email. :)&lt;/p&gt;
8859 </description>
8860 </item>
8861
8862 <item>
8863 <title>New IRC channel for LEGO designers using Debian</title>
8864 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
8865 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
8866 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
8867 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
8868 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
8869 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
8870 discovered I had to build all the tools myself because none were
8871 already in Debian Squeeze. If Debian support for LEGO is something
8872 you care about, please join me on the IRC channel
8873 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
8874 irc.debian.org). There is a lot that could be done to improve the
8875 Debian support for LEGO designers. For example both CAD software
8876 and Mindstorm compilers are missing. :)&lt;/p&gt;
8877
8878 &lt;p&gt;Update 2012-01-03: A
8879 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
8880 including links to Lego related packages is now available.&lt;/p&gt;
8881 </description>
8882 </item>
8883
8884 <item>
8885 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
8886 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
8887 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
8888 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
8889 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
8890 year! I hope next year will prove to be a good year.&lt;/p&gt;
8891
8892 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
8893 decentralised &quot;currency&quot; that allow people to transfer bitcoins
8894 between each other with minimal overhead, is a very interesting
8895 experiment. And as I wrote a few days ago, the bitcoin situation in
8896 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
8897 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
8898 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
8899 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
8900 for one of the ftpmasters to approve the new bitcoin-qt package
8901 name.&lt;/p&gt;
8902
8903 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
8904 team in Debian, you can easily test the package in Debian Squeeze
8905 using the following steps to get a set of working packages:&lt;/p&gt;
8906
8907 &lt;blockquote&gt;&lt;pre&gt;
8908 git clone git://git.debian.org/git/collab-maint/bitcoin
8909 cd bitcoin
8910 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
8911 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
8912 &lt;/pre&gt;&lt;/blockquote&gt;
8913
8914 &lt;p&gt;You might have to install some build dependencies as well. The
8915 list of commands should give you two packages, bitcoind and
8916 bitcoin-qt, ready for use in a Squeeze environment. Note that the
8917 client will download the complete set of bitcoin &quot;blocks&quot;, which need
8918 around 5.6 GiB of data on my machine at the moment. Make sure your
8919 ~/.bitcoin/ directory have lots of spare room if you want to download
8920 all the blocks. The client will warn if the disk is getting full, so
8921 there is not really a problem if you got too little room, but you will
8922 not be able to get all the features out of the client.&lt;/p&gt;
8923
8924 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
8925 activities, please send Bitcoin donations to my address
8926 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8927 </description>
8928 </item>
8929
8930 <item>
8931 <title>A word on bitcoin support in Debian</title>
8932 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
8933 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
8934 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
8935 <description>&lt;p&gt;It has been a while since I wrote about
8936 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
8937 peer-to-peer based crypto-currency, and the reason is simply that I
8938 have been busy elsewhere. But two days ago, I started looking at the
8939 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
8940 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
8941 is now maintained by a
8942 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
8943 people&lt;/a&gt;, and the grunt work had already been done by this team. We
8944 owe a huge thank you to all these team members. :)
8945 But I was sad to discover that the bitcoin client is missing in
8946 Wheezy. It is only available in Sid (and an outdated client from
8947 backports). The client had several RC bugs registered in BTS blocking
8948 it from entering testing. To try to help the team and improve the
8949 situation, I spent some time providing patches and triaging the bug
8950 reports. I also had a look at the bitcoin package available from Matt
8951 Corallo in a
8952 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
8953 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
8954 Debian package.&lt;/p&gt;
8955
8956 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
8957 IRC, I pushed several patches into the collab-maint git repository to
8958 improve the package. It now contains fixes for the RC issues (not from
8959 me, but fixed by Scott Howard), build rules for a Qt GUI client
8960 package, konqueror support for the bitcoin: URI and bash completion
8961 setup. As I work on Debian Squeeze, I also created
8962 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
8963 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
8964 it and try to integrate it into the git repository before uploading a
8965 new version to unstable.
8966
8967 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
8968 centralized control currently exercised in the monetary system. I
8969 find it completely unacceptable that the USA government is collecting
8970 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
8971 that the major credit card companies can block legal money
8972 transactions to Wikileaks. But for bitcoin to succeed, more people
8973 need to use bitcoins, and more people need to accept bitcoins when
8974 they sell products and services. Improving the bitcoin support in
8975 Debian is a small step in the right direction, but not enough.
8976 Unfortunately the user experience when browsing the web and wanting to
8977 pay with bitcoin is still not very good. The bitcoin: URI is a step
8978 in the right direction, but need to work in most or every browser in
8979 use. Also the bitcoin-qt client is too heavy to fire up to do a
8980 quick transaction. I believe there are other clients available, but
8981 have not tested them.&lt;/p&gt;
8982
8983 &lt;p&gt;My
8984 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
8985 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
8986 I received 20.15 BTC so far on the address I provided in my blog two
8987 years ago, as can be
8988 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
8989 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
8990 donation. The blockexplorer service demonstrates quite well that
8991 bitcoin is not quite anonymous and untracked. :) I wonder if the
8992 number of users have gone up since then. If you use bitcoin and want
8993 to show your support of my activity, please send Bitcoin donations to
8994 the same address as last time,
8995 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8996 </description>
8997 </item>
8998
8999 <item>
9000 <title>Git repository for song book for Computer Scientists</title>
9001 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
9002 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
9003 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
9004 <description>&lt;p&gt;As I
9005 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
9006 this summer&lt;/a&gt;, I have created a Computer Science song book a few
9007 years ago, and today I finally found time to create a public
9008 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
9009 repository for the project&lt;/a&gt;.&lt;/p&gt;
9010
9011 &lt;p&gt;If you want to help out, please clone the source and submit patches
9012 to the HTML version. To generate the PDF and PostScript version,
9013 please use prince XML, or let me know about a useful free software
9014 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
9015
9016 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
9017 PostScript formats at
9018 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
9019 Science Songbook&lt;/a&gt;.&lt;/p&gt;
9020 </description>
9021 </item>
9022
9023 <item>
9024 <title>Gratulerer med 19-årsdagen, Debian!</title>
9025 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
9026 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
9027 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
9028 <description>&lt;p&gt;I dag fyller
9029 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
9030 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
9031 si gratulerer med dagen, Debian!&lt;/p&gt;
9032 </description>
9033 </item>
9034
9035 <item>
9036 <title>Song book for Computer Scientists</title>
9037 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
9038 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
9039 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
9040 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
9041 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
9042 collecting computer related songs for use at parties. The original
9043 version was written in LaTeX, but a few years ago I got help from
9044 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9045 while keeping the ability to create a nice book in PDF format. I have
9046 not had time to maintain the book for a while now, and guess I should
9047 put it up on some public version control repository where others can
9048 help me extend and update the book. If anyone is volunteering to help
9049 me with this, send me an email. Also let me know if there are songs
9050 missing in my book.&lt;/p&gt;
9051
9052 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
9053 me today that I really should let all my readers share the joys of
9054 singing out load about programming, computers and computer networks.
9055 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
9056 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
9057 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
9058 Computer Science Songbook&lt;/a&gt;.
9059 </description>
9060 </item>
9061
9062 <item>
9063 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
9064 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
9065 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
9066 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
9067 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
9068 around 1000 at the moment. To be able to get help from the vendors
9069 when something go wrong, we want to keep the firmware on the servers
9070 up to date. If the firmware isn&#39;t the latest and greatest, the
9071 vendors typically refuse to start debugging any problems until the
9072 firmware is upgraded. So before every reboot, we want to upgrade the
9073 firmware, and we would really like everyone handling servers at the
9074 university to do this themselves when they plan to reboot a machine.
9075 For that to happen we at the unix server admin group need to provide
9076 the tools to do so.&lt;/p&gt;
9077
9078 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
9079 fetch and install the latest firmware for the servers we got. Most of
9080 our hardware are from Dell and HP, so I have focused on these servers
9081 so far. This blog post is about the Dell part.&lt;/P&gt;
9082
9083 &lt;p&gt;On the Dell FTP site I was lucky enough to find
9084 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
9085 with firmware information for all 11th generation servers, listing
9086 which firmware should be used on a given model and where on the FTP
9087 site I can find it. Using a simple perl XML parser I can then
9088 download the shell scripts Dell provides to do firmware upgrades from
9089 within Linux and reboot when all the firmware is primed and ready to
9090 be activated on the first reboot.&lt;/p&gt;
9091
9092 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
9093 Are there anyone working on similar tools for firmware upgrading all
9094 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
9095
9096 &lt;p&gt;&lt;pre&gt;
9097 #!/usr/bin/perl
9098 use strict;
9099 use warnings;
9100 use File::Temp qw(tempdir);
9101 BEGIN {
9102 # Install needed RHEL packages if missing
9103 my %rhelmodules = (
9104 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
9105 );
9106 for my $module (keys %rhelmodules) {
9107 eval &quot;use $module;&quot;;
9108 if ($@) {
9109 my $pkg = $rhelmodules{$module};
9110 system(&quot;yum install -y $pkg&quot;);
9111 eval &quot;use $module;&quot;;
9112 }
9113 }
9114 }
9115 my $errorsto = &#39;pere@hungry.com&#39;;
9116
9117 upgrade_dell();
9118
9119 exit 0;
9120
9121 sub run_firmware_script {
9122 my ($opts, $script) = @_;
9123 unless ($script) {
9124 print STDERR &quot;fail: missing script name\n&quot;;
9125 exit 1
9126 }
9127 print STDERR &quot;Running $script\n\n&quot;;
9128
9129 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
9130 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
9131 } else {
9132 print STDERR &quot;fail: firmware script returned error\n&quot;;
9133 }
9134 }
9135
9136 sub run_firmware_scripts {
9137 my ($opts, @dirs) = @_;
9138 # Run firmware packages
9139 for my $dir (@dirs) {
9140 print STDERR &quot;info: Running scripts in $dir\n&quot;;
9141 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
9142 while (my $s = readdir $dh) {
9143 next if $s =~ m/^\.\.?/;
9144 run_firmware_script($opts, &quot;$dir/$s&quot;);
9145 }
9146 closedir $dh;
9147 }
9148 }
9149
9150 sub download {
9151 my $url = shift;
9152 print STDERR &quot;info: Downloading $url\n&quot;;
9153 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
9154 }
9155
9156 sub upgrade_dell {
9157 my @dirs;
9158 my $product = `dmidecode -s system-product-name`;
9159 chomp $product;
9160
9161 if ($product =~ m/PowerEdge/) {
9162
9163 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9164 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
9165
9166 my $tmpdir = tempdir(
9167 CLEANUP =&gt; 1
9168 );
9169 chdir($tmpdir);
9170 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
9171 system(&#39;gunzip Catalog.xml.gz&#39;);
9172 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
9173 # -q is quiet, disabling interactivity and reducing console output
9174 my $fwopts = &quot;-q&quot;;
9175 if (@paths) {
9176 for my $url (@paths) {
9177 fetch_dell_fw($url);
9178 }
9179 run_firmware_scripts($fwopts, $tmpdir);
9180 } else {
9181 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9182 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9183 }
9184 chdir(&#39;/&#39;);
9185 } else {
9186 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9187 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9188 }
9189 }
9190
9191 sub fetch_dell_fw {
9192 my $path = shift;
9193 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
9194 download($url);
9195 }
9196
9197 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9198 # firmware packages to download from Dell. Only work for Linux
9199 # machines and 11th generation Dell servers.
9200 sub fetch_dell_fw_list {
9201 my $filename = shift;
9202
9203 my $product = `dmidecode -s system-product-name`;
9204 chomp $product;
9205 my ($mybrand, $mymodel) = split(/\s+/, $product);
9206
9207 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
9208
9209 my $xml = XMLin($filename);
9210 my @paths;
9211 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
9212 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
9213 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
9214 my $oscode;
9215 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
9216 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
9217 } else {
9218 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
9219 }
9220 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
9221 {
9222 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
9223 }
9224 }
9225 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
9226 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
9227
9228 # Drop application packages, only firmware and BIOS
9229 next if &#39;APAC&#39; eq $componenttype;
9230
9231 my $cpath = $component-&gt;{path};
9232 for my $path (@paths) {
9233 if ($cpath =~ m%/$path$%) {
9234 push(@paths, $cpath);
9235 }
9236 }
9237 }
9238 return @paths;
9239 }
9240 &lt;/pre&gt;
9241
9242 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
9243 it could work on other platforms with some tweaking. Anyone know a
9244 index like Catalog.xml is available from HP for HP servers? At the
9245 moment I maintain a similar list manually and it is quickly getting
9246 outdated.&lt;/p&gt;
9247 </description>
9248 </item>
9249
9250 <item>
9251 <title>How is booting into runlevel 1 different from single user boots?</title>
9252 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
9253 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
9254 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
9255 <description>&lt;p&gt;Wouter Verhelst have some
9256 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
9257 comments and opinions&lt;/a&gt; on my blog post on
9258 &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
9259 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
9260 &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
9261 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
9262 small piece of his comment now, and though it best to address the
9263 misunderstanding he bring forward:&lt;/p&gt;
9264
9265 &lt;p&gt;&lt;blockquote&gt;
9266 Currently, a system admin has four options: [...] boot to a
9267 single-user system (by adding &#39;single&#39; to the kernel command line;
9268 this runs rcS and rc1 scripts)
9269 &lt;/blockquote&gt;&lt;/p&gt;
9270
9271 &lt;p&gt;This make me believe Wouter believe booting into single user mode
9272 and booting into runlevel 1 is the same. I am not surprised he
9273 believe this, because it would make sense and is a quite sensible
9274 thing to believe. But because the boot in Debian is slightly broken,
9275 runlevel 1 do not work properly and it isn&#39;t the same as single user
9276 mode. I&#39;ll try to explain what is actually happing, but it is a bit
9277 hard to explain.&lt;/p&gt;
9278
9279 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
9280 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
9281 executed in single user mode is sulogin. Single user mode is a boot
9282 state &quot;between&quot; the runlevels, and when booting into single user mode,
9283 only the scripts in /etc/rcS.d/ are executed before the init process
9284 enters the single user state. When switching to runlevel 1, the state
9285 is in fact not ending in runlevel 1, but it passes through runlevel 1
9286 and end up in the single user mode (see /etc/rc1.d/S03single, which
9287 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
9288 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
9289 mode enabled by /etc/rcS.d/ (which is more like the initial boot
9290 mode).&lt;/p&gt;
9291
9292 &lt;p&gt;This summary might make it clearer. When booting for the first
9293 time into single user mode, the following commands are executed:
9294 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
9295 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
9296 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
9297 trying to continue after visiting single user mode. Not all services
9298 are started again as they should, causing the machine to end up in an
9299 unpredicatble state. This is why Debian admins recommend rebooting
9300 after visiting single user mode.&lt;/p&gt;
9301
9302 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
9303 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
9304 to runlevel 1, the services started from /etc/rcS.d/ are not properly
9305 stopped when passing through the scripts in /etc/rc1.d/, and not
9306 started again when switching away from runlevel 1 to the runlevels
9307 2-5. I believe the problem is best fixed by moving all the scripts
9308 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
9309 functioning single user mode during boot.&lt;/p&gt;
9310
9311 &lt;p&gt;I have spent several years investigating the Debian boot system,
9312 and discovered this problem a few years ago. I suspect it originates
9313 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
9314 </description>
9315 </item>
9316
9317 <item>
9318 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
9319 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
9320 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
9321 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
9322 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
9323 are started from /etc/rcS.d/. In fact, there is a bite more of them
9324 than make sense, and this causes a few problems. What kind of
9325 problems, you might ask. There are at least two problems. The first
9326 is that it is not possible to recover a machine after switching to
9327 runlevel 1. One need to actually reboot to get the machine back to
9328 the expected state. The other is that single user boot will sometimes
9329 run into problems because some of the subsystems are activated before
9330 the root login is presented, causing problems when trying to recover a
9331 machine from a problem in that subsystem. A minor additional point is
9332 that moving more scripts out of rcS.d/ and into the other rc#.d/
9333 directories will increase the amount of scripts that can run in
9334 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
9335
9336 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
9337 scripts that _have_ to execute before the root login prompt is
9338 presented during a single user boot should go there. Everything else
9339 should go into the numeric runlevels. This means things like
9340 lm-sensors, fuse and x11-common should not run from rcS.d, but from
9341 the numeric runlevels. Today in Debian, there are around 115 init.d
9342 scripts that are started from rcS.d/, and most of them should be moved
9343 out. Do your package have one of them? Please help us make single
9344 user and runlevel 1 better by moving it.&lt;/p&gt;
9345
9346 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
9347 etc. should still be started from rcS.d/, but there is for example no
9348 need to have the network enabled before the single user login prompt
9349 is presented.&lt;/p&gt;
9350
9351 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
9352 Debian systems working while scripts migrate and during upgrades, the
9353 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
9354 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
9355 and the next ones can only be moved when their dependencies have been
9356 moved first. This migration must be done sequentially while we ensure
9357 that the package system upgrade packages in the right order to keep
9358 the system state correct. This will require some coordination when it
9359 comes to network related packages, but most of the packages with
9360 scripts that should migrate do not have anything in rcS.d/ depending
9361 on them. Some packages have already been updated, like the sudo
9362 package, while others are still left to do. I wish I had time to work
9363 on this myself, but real live constrains make it unlikely that I will
9364 find time to push this forward.&lt;/p&gt;
9365 </description>
9366 </item>
9367
9368 <item>
9369 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
9370 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
9371 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
9372 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
9373 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
9374 mentioned the issues I believe should be improved in Debian for its
9375 desktop to be useful for more people. The use case for this is my
9376 parents, which are currently running Kubuntu which solve the
9377 issues.&lt;/p&gt;
9378
9379 &lt;p&gt;I suspect these four missing features are not very hard to
9380 implement. After all, they are present in Ubuntu, so if we wanted to
9381 do this in Debian we would have a source.&lt;/p&gt;
9382
9383 &lt;ol&gt;
9384
9385 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
9386 are new packages available for upgrades, a icon in the KDE status bar
9387 indicate this, and clicking on it will activate the simple upgrade
9388 tool to handle it. I have no problem guiding both of my parents
9389 through the process over the phone. If a kernel reboot is required,
9390 this too is indicated by the status bars and the upgrade tool. Last
9391 time I checked, nothing with the same features was working in KDE in
9392 Debian.&lt;/li&gt;
9393
9394 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
9395 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
9396 currently have a handler for, it will ask the user if the system
9397 should search for a package that would add support for this MIME type,
9398 and if the user say yes, the APT sources will be searched for packages
9399 advertising the MIME type in their control file (visible in the
9400 Packages file in the APT archive). If one or more packages are found,
9401 it is a simple click of the mouse to add support for the missing mime
9402 type. If the package require the user to accept some non-free
9403 license, this is explained to the user. The entire process make it
9404 more clear to the user why something do not work in the browser, and
9405 make the chances higher for the user to blame the web page authors and
9406 not the browser for any missing features.&lt;/li&gt;
9407
9408 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
9409 handlers.&lt;/strong&gt; When the media players encounter a format or codec
9410 it is not supporting, a dialog pop up asking the user if the system
9411 should search for a package that would add support for it. This
9412 happen with things like MP3, Windows Media or H.264. The selection
9413 and installation procedure is very similar to the Firefox browser
9414 plugin handling. This is as far as I know implemented using a
9415 gstreamer hook. The end result is that the user easily get access to
9416 the codecs that are present from the APT archives available, while
9417 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
9418
9419 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
9420 displaying a text/plain file in my Debian browser, it will propose to
9421 start emacs to show it. If I remember correctly, when doing the same
9422 in Kunbutu it show the file as a text file in the browser. At least I
9423 know Opera will show text files within the browser. I much prefer the
9424 latter behaviour.&lt;/li&gt;
9425
9426 &lt;/ol&gt;
9427
9428 &lt;p&gt;There are other nice features as well, like the simplified suite
9429 upgrader, but given that I am the one mostly doing the dist-upgrade,
9430 it do not matter much.&lt;/p&gt;
9431
9432 &lt;p&gt;I really hope we could get these features in place for the next
9433 Debian release. It would require the coordinated effort of several
9434 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
9435 </description>
9436 </item>
9437
9438 <item>
9439 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
9440 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
9441 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
9442 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
9443 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
9444 site is build on Debian/Squeeze, and this platform was chosen because
9445 I am most familiar with Debian (being a Debian Developer for around 10
9446 years) because it is the latest stable Debian release which should get
9447 security support for a few years.&lt;/p&gt;
9448
9449 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
9450 that are missing in Debian at the moment. It would be great if these
9451 modules were added to the Debian archive, allowing anyone to set up
9452 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
9453 in their own country using only Debian packages. The list of modules
9454 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
9455 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
9456 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
9457 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
9458 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
9459 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
9460 easier in the future.&lt;/p&gt;
9461
9462 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
9463 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
9464 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
9465 with the responsibility of tracking security problems, which I really
9466 do not have time for.&lt;/p&gt;
9467 </description>
9468 </item>
9469
9470 <item>
9471 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
9472 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
9473 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
9474 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
9475 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
9476 posts have been in Norwegian the last few weeks, so here is a short
9477 update in English.&lt;/p&gt;
9478
9479 &lt;p&gt;The kids still keep me too busy to get much free software work
9480 done, but I did manage to organise a project to get a Norwegian port
9481 of the British service
9482 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
9483 and it has been running for a month now. The entire project has been
9484 organised by me and two others. Around Christmas we gathered sponsors
9485 to fund the development work. In January I drafted a contract with
9486 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
9487 and in February the development took place. Most of it involved
9488 converting the source to use GPS coordinates instead of British
9489 easting/northing, and the resulting code should be a lot easier to get
9490 running in any country by now. The Norwegian
9491 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
9492 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
9493 source and the source for administrative borders in Norway, and
9494 support for this had to be added/fixed.&lt;/p&gt;
9495
9496 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
9497 polishing the system before we announced it March 7th. The system is
9498 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
9499 problem reports in a few weeks. Soon we hope to announce the Android
9500 and iPhone versions making it even easier to report problems with the
9501 public infrastructure.&lt;/p&gt;
9502
9503 &lt;p&gt;Perhaps something to consider for those of you in countries without
9504 such service?&lt;/p&gt;
9505 </description>
9506 </item>
9507
9508 <item>
9509 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
9510 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
9511 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
9512 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
9513 <description>&lt;p&gt;The last few days I have looked at ways to track open security
9514 issues here at my work with the University of Oslo. My idea is that
9515 it should be possible to use the information about security issues
9516 available on the Internet, and check our locally
9517 maintained/distributed software against this information. It should
9518 allow us to verify that no known security issues are forgotten. The
9519 CVE database listing vulnerabilities seem like a great central point,
9520 and by using the package lists from Debian mapped to CVEs provided by
9521 the testing security team, I believed it should be possible to figure
9522 out which security holes were present in our free software
9523 collection.&lt;/p&gt;
9524
9525 &lt;p&gt;After reading up on the topic, it became obvious that the first
9526 building block is to be able to name software packages in a unique and
9527 consistent way across data sources. I considered several ways to do
9528 this, for example coming up with my own naming scheme like using URLs
9529 to project home pages or URLs to the Freshmeat entries, or using some
9530 existing naming scheme. And it seem like I am not the first one to
9531 come across this problem, as MITRE already proposed and implemented a
9532 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
9533 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
9534 software, hardware and other platform components. The CPE ids are
9535 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
9536 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
9537 issues for any CPE name. With this in place, all I need to do is to
9538 locate the CPE id for the software packages we use at the university.
9539 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
9540 NVD entry if a CVE for the package exist).&lt;/p&gt;
9541
9542 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
9543 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
9544 check out, one could look up
9545 &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
9546 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
9547 The most recent one is
9548 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
9549 and at the bottom of the NVD page for this vulnerability the complete
9550 list of affected versions is provided.&lt;/p&gt;
9551
9552 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
9553 for offline processing of issues. Using this dump, I&#39;ve written a
9554 small script taking a list of CPEs as input and list all CVEs
9555 affecting the packages represented by these CPEs. One give it CPEs
9556 with version numbers as specified above and get a list of open
9557 security issues out.&lt;/p&gt;
9558
9559 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
9560 information need to be high. For that to happen, I believe as many as
9561 possible need to use and contribute to the NVD database. I notice
9562 RHEL is providing
9563 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
9564 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
9565 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
9566
9567 &lt;p&gt;To get an idea about the quality for free software, I spent some
9568 time making it possible to compare the CVE database from Debian with
9569 the CVE database in NVD. The result look fairly good, but there are
9570 some inconsistencies in NVD (same software package having several
9571 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
9572 Debian believe are affected by a CVE). Hope to find time to improve
9573 the quality of NVD, but that require being able to get in touch with
9574 someone maintaining it. So far my three emails with questions and
9575 corrections have not seen any reply, but I hope contact can be
9576 established soon.&lt;/p&gt;
9577
9578 &lt;p&gt;An interesting application for CPEs is cross platform package
9579 mapping. It would be useful to know which packages in for example
9580 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
9581 this would be trivial if all linux distributions provided CPE entries
9582 for their packages.&lt;/p&gt;
9583 </description>
9584 </item>
9585
9586 <item>
9587 <title>Which module is loaded for a given PCI and USB device?</title>
9588 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
9589 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
9590 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
9591 <description>&lt;p&gt;In the
9592 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
9593 package in Debian, there is a script to report useful information
9594 about the running hardware for use when people report missing
9595 information. One part of this script that I find very useful when
9596 debugging hardware problems, is the part mapping loaded kernel module
9597 to the PCI device it claims. It allow me to quickly see if the kernel
9598 module I expect is driving the hardware I am struggling with. To see
9599 the output, make sure discover-data is installed and run
9600 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
9601 one of my machines like this:&lt;/p&gt;
9602
9603 &lt;pre&gt;
9604 loaded modules:
9605 10de:03eb i2c_nforce2
9606 10de:03f1 ohci_hcd
9607 10de:03f2 ehci_hcd
9608 10de:03f0 snd_hda_intel
9609 10de:03ec pata_amd
9610 10de:03f6 sata_nv
9611 1022:1103 k8temp
9612 109e:036e bttv
9613 109e:0878 snd_bt87x
9614 11ab:4364 sky2
9615 &lt;/pre&gt;
9616
9617 &lt;p&gt;The code in question look like this, slightly modified for
9618 readability and to drop the output to file descriptor 3:&lt;/p&gt;
9619
9620 &lt;pre&gt;
9621 if [ -d /sys/bus/pci/devices/ ] ; then
9622 echo loaded pci modules:
9623 (
9624 cd /sys/bus/pci/devices/
9625 for address in * ; do
9626 if [ -d &quot;$address/driver/module&quot; ] ; then
9627 module=`cd $address/driver/module ; pwd -P | xargs basename`
9628 if grep -q &quot;^$module &quot; /proc/modules ; then
9629 address=$(echo $address |sed s/0000://)
9630 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
9631 echo &quot;$id $module&quot;
9632 fi
9633 fi
9634 done
9635 )
9636 echo
9637 fi
9638 &lt;/pre&gt;
9639
9640 &lt;p&gt;Similar code could be used to extract USB device module
9641 mappings:&lt;/p&gt;
9642
9643 &lt;pre&gt;
9644 if [ -d /sys/bus/usb/devices/ ] ; then
9645 echo loaded usb modules:
9646 (
9647 cd /sys/bus/usb/devices/
9648 for address in * ; do
9649 if [ -d &quot;$address/driver/module&quot; ] ; then
9650 module=`cd $address/driver/module ; pwd -P | xargs basename`
9651 if grep -q &quot;^$module &quot; /proc/modules ; then
9652 address=$(echo $address |sed s/0000://)
9653 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
9654 if [ &quot;$id&quot; ] ; then
9655 echo &quot;$id $module&quot;
9656 fi
9657 fi
9658 fi
9659 done
9660 )
9661 echo
9662 fi
9663 &lt;/pre&gt;
9664
9665 &lt;p&gt;This might perhaps be something to include in other tools as
9666 well.&lt;/p&gt;
9667 </description>
9668 </item>
9669
9670 <item>
9671 <title>How to test if a laptop is working with Linux</title>
9672 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
9673 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
9674 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
9675 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
9676 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
9677 batch of computers will work with Linux. Every year for the last few
9678 years the university have organised shared bid of a few thousand
9679 computers, and this year HP won the bid. Two different desktops and
9680 five different laptops are on the list this year. We in the UNIX
9681 group want to know which one of these computers work well with RHEL
9682 and Ubuntu, the two Linux distributions we currently handle at the
9683 university.&lt;/p&gt;
9684
9685 &lt;p&gt;My test method is simple, and I share it here to get feedback and
9686 perhaps inspire others to test hardware as well. To test, I PXE
9687 install the OS version of choice, and log in as my normal user and run
9688 a few applications and plug in selected pieces of hardware. When
9689 something fail, I make a note about this in the test matrix and move
9690 on. If I have some spare time I try to report the bug to the OS
9691 vendor, but as I only have the machines for a short time, I rarely
9692 have the time to do this for all the problems I find.&lt;/p&gt;
9693
9694 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
9695 I perform on a new model.&lt;/p&gt;
9696
9697 &lt;ul&gt;
9698
9699 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
9700 and Ubuntu Maverik at the moment. If I feel like it, I also test with
9701 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
9702
9703 &lt;li&gt;Is X.org working? If the graphical login screen show up after
9704 installation, X.org is working.&lt;/li&gt;
9705
9706 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
9707 package mesa-utils on Ubuntu) and writing down the frames per second
9708 reported by the program.&lt;/li&gt;
9709
9710 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
9711 logging in, and if I can hear this the test is successful. If there
9712 are several audio exits on the machine, I try them all and check if
9713 the Gnome/KDE audio mixer can control where to send the sound. I
9714 normally test this by playing
9715 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
9716 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
9717
9718 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
9719 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
9720
9721 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
9722 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
9723
9724 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
9725 picture from the v4l device show up.&lt;/li&gt;
9726
9727 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
9728 any bluetooth devices are discovered. In my office, I normally see a
9729 few.&lt;/li&gt;
9730
9731 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
9732 memory modules lying around, and stick them in and see if Gnome/KDE
9733 notice this.&lt;/li&gt;
9734
9735 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
9736 special button work, and if the laptop continue to work after
9737 resume.&lt;/li&gt;
9738
9739 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
9740 adjusting background light, switching on/off external video output,
9741 switching on/off wifi, bluetooth, etc? The set of buttons differ from
9742 laptop to laptop, so I just write down which are working and which are
9743 not.&lt;/li&gt;
9744
9745 &lt;li&gt;Some laptops have smart card readers, finger print readers,
9746 acceleration sensors etc. I rarely test these, as I do not know how
9747 to quickly test if they are working or not, so I only document their
9748 existence.&lt;/li&gt;
9749
9750 &lt;/ul&gt;
9751
9752 &lt;p&gt;By now I suspect you are really curious what the test results are
9753 for the HP machines I am testing. I&#39;m not done yet, so I will report
9754 the test results later. For now I can report that HP 8100 Elite work
9755 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
9756 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
9757 can see, I have most machines left to test. One interesting
9758 observation is that Ubuntu Lucid has almost twice the frame rate than
9759 RHEL6 with glxgears. No idea why.&lt;/p&gt;
9760 </description>
9761 </item>
9762
9763 <item>
9764 <title>Some thoughts on BitCoins</title>
9765 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
9766 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
9767 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
9768 <description>&lt;p&gt;As I continue to explore
9769 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
9770 what properties the system have, and how it will be affected by laws
9771 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
9772
9773 &lt;p&gt;One interesting thing to note is that since the transactions are
9774 verified using a peer to peer network, all details about a transaction
9775 is known to everyone. This means that if a BitCoin address has been
9776 published like I did with mine in my initial post about BitCoin, it is
9777 possible for everyone to see how many BitCoins have been transfered to
9778 that address. There is even a web service to look at the details for
9779 all transactions. There I can see that my address
9780 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
9781 have received 16.06 Bitcoin, the
9782 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
9783 address of Simon Phipps have received 181.97 BitCoin and the address
9784 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
9785 of EFF have received 2447.38 BitCoins so far. Thank you to each and
9786 every one of you that donated bitcoins to support my activity. The
9787 fact that anyone can see how much money was transfered to a given
9788 address make it more obvious why the BitCoin community recommend to
9789 generate and hand out a new address for each transaction. I&#39;m told
9790 there is no way to track which addresses belong to a given person or
9791 organisation without the person or organisation revealing it
9792 themselves, as Simon, EFF and I have done.&lt;/p&gt;
9793
9794 &lt;p&gt;In Norway, and in most other countries, there are laws and
9795 regulations limiting how much money one can transfer across the border
9796 without declaring it. There are money laundering, tax and accounting
9797 laws and regulations I would expect to apply to the use of BitCoin.
9798 If the Skolelinux foundation
9799 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
9800 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
9801 normal bank transfers like EFF is doing, how should this be accounted?
9802 Given that it is impossible to know if money can cross the border or
9803 not, should everything or nothing be declared? What exchange rate
9804 should be used when calculating taxes? Would receivers have to pay
9805 income tax if the foundation were to pay Skolelinux contributors in
9806 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
9807
9808 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
9809 accepted by a lot of users. It must be possible to get easy access to
9810 the currency (as a wage or using currency exchanges), and it must be
9811 easy to spend it. At the moment BitCoin seem fairly easy to get
9812 access to, but there are very few places to spend it. I am not really
9813 a regular user of any of the vendor types currently accepting BitCoin,
9814 so I wonder when my kind of shop would start accepting BitCoins. I
9815 would like to buy electronics, travels and subway tickets, not herbs
9816 and books. :) The currency is young, and this will improve over time
9817 if it become popular, but I suspect regular banks will start to lobby
9818 to get BitCoin declared illegal if it become popular. I&#39;m sure they
9819 will claim it is helping fund terrorism and money laundering (which
9820 probably would be true, as is any currency in existence), but I
9821 believe the problems should be solved elsewhere and not by blaming
9822 currencies.&lt;/p&gt;
9823
9824 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
9825 CPU intensive process that depend on a bit of luck as well (as one is
9826 competing against all the other miners currently spending CPU cycles
9827 to see which one get the next lump of cash). The &quot;winner&quot; get 50
9828 BitCoin when this happen. Yesterday I came across the obvious way to
9829 join forces to increase ones changes of getting at least some coins,
9830 by coordinating the work on mining BitCoins across several machines
9831 and people, and sharing the result if one is lucky and get the 50
9832 BitCoins. Check out
9833 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
9834 if this sounds interesting. I have not had time to try to set up a
9835 machine to participate there yet, but have seen that running on ones
9836 own for a few days have not yield any BitCoins througth mining
9837 yet.&lt;/p&gt;
9838
9839 &lt;p&gt;Update 2010-12-15: Found an &lt;a
9840 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
9841 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
9842 it was interesting to read. The arguments presented seem to be
9843 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
9844 </description>
9845 </item>
9846
9847 <item>
9848 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
9849 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
9850 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
9851 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
9852 <description>&lt;p&gt;With this weeks lawless
9853 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
9854 attacks&lt;/a&gt; on Wikileak and
9855 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
9856 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
9857 not be trusted to handle money transactions.
9858 A blog post from
9859 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
9860 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
9861 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
9862 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
9863 some help from my friend to get it all running, and he even handed me
9864 some bitcoins to get started. I even donated a few bitcoins to Simon
9865 for helping me remember BitCoin.&lt;/p&gt;
9866
9867 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
9868 crypto-currency, decentralised and handled using peer-to-peer
9869 networks. It allows anonymous transactions and prohibits central
9870 control over the transactions, making it impossible for governments
9871 and companies alike to block donations and other transactions. The
9872 source is free software, and while the key dependency wxWidgets 2.9
9873 for the graphical user interface is missing in Debian, the command
9874 line client builds just fine. Hopefully Jonas
9875 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
9876 Debian&lt;/a&gt; soon.&lt;/p&gt;
9877
9878 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
9879 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
9880 bitcoins&lt;/a&gt; when selling services and goods, and there are even
9881 currency &quot;stock&quot; markets where the exchange rate is decided. There
9882 are not many users so far, but the concept seems promising. If you
9883 want to get started and lack a friend with any bitcoins to spare,
9884 you can even get
9885 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
9886 bitcoin at the time of writing). Use
9887 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
9888 on the current exchange rates.&lt;/p&gt;
9889
9890 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
9891 machines. If you want to support my activity, please send Bitcoin
9892 donations to the address
9893 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
9894 </description>
9895 </item>
9896
9897 <item>
9898 <title>Why isn&#39;t Debian Edu using VLC?</title>
9899 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
9900 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
9901 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
9902 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
9903 presented, and the winner among the multimedia player were VLC.
9904 Personally, I like VLC, and it is my player of choice when I first try
9905 to play a video file or stream. Only if VLC fail will I drag out
9906 gmplayer to see if it can do better. The reason is mostly the failure
9907 model and trust. When VLC fail, it normally pop up a error message
9908 reporting the problem. When mplayer fail, it normally segfault or
9909 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
9910
9911 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
9912 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9913 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
9914 plugin to play web videos seamlessly, and the VLC browser plugin is
9915 not very good. For example, it lack in-line control buttons, so there
9916 is no way for the user to pause the video. Also, when I
9917 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
9918 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
9919 failed on several video pages where mplayer based plugins worked. If
9920 the browser plugin for VLC was as good as the gecko-mediaplayer
9921 package (which uses mplayer), we would switch.&lt;/P&gt;
9922
9923 &lt;p&gt;While VLC is a good player, its user interface is slightly
9924 annoying. The most annoying feature is its inconsistent use of
9925 keyboard shortcuts. When the player is in full screen mode, its
9926 shortcuts are different from when it is playing the video in a window.
9927 For example, space only work as pause when in full screen mode. I
9928 wish it had consisten shortcuts and that space also would work when in
9929 window mode. Another nice shortcut in gmplayer is [enter] to restart
9930 the current video. It is very nice when playing short videos from the
9931 web and want to restart it when new people arrive to have a look at
9932 what is going on.&lt;/p&gt;
9933 </description>
9934 </item>
9935
9936 <item>
9937 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
9938 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
9939 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</guid>
9940 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
9941 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
9942 upgrade testing of the
9943 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
9944 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
9945 This seem like a very good idea, so I adjusted by test scripts and
9946 can now present the updated result from today:&lt;/p&gt;
9947
9948 &lt;p&gt;This is for Gnome:&lt;/p&gt;
9949
9950 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9951
9952 &lt;blockquote&gt;&lt;p&gt;
9953 apache2.2-bin
9954 aptdaemon
9955 baobab
9956 binfmt-support
9957 browser-plugin-gnash
9958 cheese-common
9959 cli-common
9960 cups-pk-helper
9961 dmz-cursor-theme
9962 empathy
9963 empathy-common
9964 freedesktop-sound-theme
9965 freeglut3
9966 gconf-defaults-service
9967 gdm-themes
9968 gedit-plugins
9969 geoclue
9970 geoclue-hostip
9971 geoclue-localnet
9972 geoclue-manual
9973 geoclue-yahoo
9974 gnash
9975 gnash-common
9976 gnome
9977 gnome-backgrounds
9978 gnome-cards-data
9979 gnome-codec-install
9980 gnome-core
9981 gnome-desktop-environment
9982 gnome-disk-utility
9983 gnome-screenshot
9984 gnome-search-tool
9985 gnome-session-canberra
9986 gnome-system-log
9987 gnome-themes-extras
9988 gnome-themes-more
9989 gnome-user-share
9990 gstreamer0.10-fluendo-mp3
9991 gstreamer0.10-tools
9992 gtk2-engines
9993 gtk2-engines-pixbuf
9994 gtk2-engines-smooth
9995 hamster-applet
9996 libapache2-mod-dnssd
9997 libapr1
9998 libaprutil1
9999 libaprutil1-dbd-sqlite3
10000 libaprutil1-ldap
10001 libart2.0-cil
10002 libboost-date-time1.42.0
10003 libboost-python1.42.0
10004 libboost-thread1.42.0
10005 libchamplain-0.4-0
10006 libchamplain-gtk-0.4-0
10007 libcheese-gtk18
10008 libclutter-gtk-0.10-0
10009 libcryptui0
10010 libdiscid0
10011 libelf1
10012 libepc-1.0-2
10013 libepc-common
10014 libepc-ui-1.0-2
10015 libfreerdp-plugins-standard
10016 libfreerdp0
10017 libgconf2.0-cil
10018 libgdata-common
10019 libgdata7
10020 libgdu-gtk0
10021 libgee2
10022 libgeoclue0
10023 libgexiv2-0
10024 libgif4
10025 libglade2.0-cil
10026 libglib2.0-cil
10027 libgmime2.4-cil
10028 libgnome-vfs2.0-cil
10029 libgnome2.24-cil
10030 libgnomepanel2.24-cil
10031 libgpod-common
10032 libgpod4
10033 libgtk2.0-cil
10034 libgtkglext1
10035 libgtksourceview2.0-common
10036 libmono-addins-gui0.2-cil
10037 libmono-addins0.2-cil
10038 libmono-cairo2.0-cil
10039 libmono-corlib2.0-cil
10040 libmono-i18n-west2.0-cil
10041 libmono-posix2.0-cil
10042 libmono-security2.0-cil
10043 libmono-sharpzip2.84-cil
10044 libmono-system2.0-cil
10045 libmtp8
10046 libmusicbrainz3-6
10047 libndesk-dbus-glib1.0-cil
10048 libndesk-dbus1.0-cil
10049 libopal3.6.8
10050 libpolkit-gtk-1-0
10051 libpt2.6.7
10052 libpython2.6
10053 librpm1
10054 librpmio1
10055 libsdl1.2debian
10056 libsrtp0
10057 libssh-4
10058 libtelepathy-farsight0
10059 libtelepathy-glib0
10060 libtidy-0.99-0
10061 media-player-info
10062 mesa-utils
10063 mono-2.0-gac
10064 mono-gac
10065 mono-runtime
10066 nautilus-sendto
10067 nautilus-sendto-empathy
10068 p7zip-full
10069 pkg-config
10070 python-aptdaemon
10071 python-aptdaemon-gtk
10072 python-axiom
10073 python-beautifulsoup
10074 python-bugbuddy
10075 python-clientform
10076 python-coherence
10077 python-configobj
10078 python-crypto
10079 python-cupshelpers
10080 python-elementtree
10081 python-epsilon
10082 python-evolution
10083 python-feedparser
10084 python-gdata
10085 python-gdbm
10086 python-gst0.10
10087 python-gtkglext1
10088 python-gtksourceview2
10089 python-httplib2
10090 python-louie
10091 python-mako
10092 python-markupsafe
10093 python-mechanize
10094 python-nevow
10095 python-notify
10096 python-opengl
10097 python-openssl
10098 python-pam
10099 python-pkg-resources
10100 python-pyasn1
10101 python-pysqlite2
10102 python-rdflib
10103 python-serial
10104 python-tagpy
10105 python-twisted-bin
10106 python-twisted-conch
10107 python-twisted-core
10108 python-twisted-web
10109 python-utidylib
10110 python-webkit
10111 python-xdg
10112 python-zope.interface
10113 remmina
10114 remmina-plugin-data
10115 remmina-plugin-rdp
10116 remmina-plugin-vnc
10117 rhythmbox-plugin-cdrecorder
10118 rhythmbox-plugins
10119 rpm-common
10120 rpm2cpio
10121 seahorse-plugins
10122 shotwell
10123 software-center
10124 system-config-printer-udev
10125 telepathy-gabble
10126 telepathy-mission-control-5
10127 telepathy-salut
10128 tomboy
10129 totem
10130 totem-coherence
10131 totem-mozilla
10132 totem-plugins
10133 transmission-common
10134 xdg-user-dirs
10135 xdg-user-dirs-gtk
10136 xserver-xephyr
10137 &lt;/p&gt;&lt;/blockquote&gt;
10138
10139 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10140
10141 &lt;blockquote&gt;&lt;p&gt;
10142 cheese
10143 ekiga
10144 eog
10145 epiphany-extensions
10146 evolution-exchange
10147 fast-user-switch-applet
10148 file-roller
10149 gcalctool
10150 gconf-editor
10151 gdm
10152 gedit
10153 gedit-common
10154 gnome-games
10155 gnome-games-data
10156 gnome-nettool
10157 gnome-system-tools
10158 gnome-themes
10159 gnuchess
10160 gucharmap
10161 guile-1.8-libs
10162 libavahi-ui0
10163 libdmx1
10164 libgalago3
10165 libgtk-vnc-1.0-0
10166 libgtksourceview2.0-0
10167 liblircclient0
10168 libsdl1.2debian-alsa
10169 libspeexdsp1
10170 libsvga1
10171 rhythmbox
10172 seahorse
10173 sound-juicer
10174 system-config-printer
10175 totem-common
10176 transmission-gtk
10177 vinagre
10178 vino
10179 &lt;/p&gt;&lt;/blockquote&gt;
10180
10181 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10182
10183 &lt;blockquote&gt;&lt;p&gt;
10184 gstreamer0.10-gnomevfs
10185 &lt;/p&gt;&lt;/blockquote&gt;
10186
10187 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10188
10189 &lt;blockquote&gt;&lt;p&gt;
10190 [nothing]
10191 &lt;/p&gt;&lt;/blockquote&gt;
10192
10193 &lt;p&gt;This is for KDE:&lt;/p&gt;
10194
10195 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10196
10197 &lt;blockquote&gt;&lt;p&gt;
10198 ksmserver
10199 &lt;/p&gt;&lt;/blockquote&gt;
10200
10201 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10202
10203 &lt;blockquote&gt;&lt;p&gt;
10204 kwin
10205 network-manager-kde
10206 &lt;/p&gt;&lt;/blockquote&gt;
10207
10208 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10209
10210 &lt;blockquote&gt;&lt;p&gt;
10211 arts
10212 dolphin
10213 freespacenotifier
10214 google-gadgets-gst
10215 google-gadgets-xul
10216 kappfinder
10217 kcalc
10218 kcharselect
10219 kde-core
10220 kde-plasma-desktop
10221 kde-standard
10222 kde-window-manager
10223 kdeartwork
10224 kdeartwork-emoticons
10225 kdeartwork-style
10226 kdeartwork-theme-icon
10227 kdebase
10228 kdebase-apps
10229 kdebase-workspace
10230 kdebase-workspace-bin
10231 kdebase-workspace-data
10232 kdeeject
10233 kdelibs
10234 kdeplasma-addons
10235 kdeutils
10236 kdewallpapers
10237 kdf
10238 kfloppy
10239 kgpg
10240 khelpcenter4
10241 kinfocenter
10242 konq-plugins-l10n
10243 konqueror-nsplugins
10244 kscreensaver
10245 kscreensaver-xsavers
10246 ktimer
10247 kwrite
10248 libgle3
10249 libkde4-ruby1.8
10250 libkonq5
10251 libkonq5-templates
10252 libnetpbm10
10253 libplasma-ruby
10254 libplasma-ruby1.8
10255 libqt4-ruby1.8
10256 marble-data
10257 marble-plugins
10258 netpbm
10259 nuvola-icon-theme
10260 plasma-dataengines-workspace
10261 plasma-desktop
10262 plasma-desktopthemes-artwork
10263 plasma-runners-addons
10264 plasma-scriptengine-googlegadgets
10265 plasma-scriptengine-python
10266 plasma-scriptengine-qedje
10267 plasma-scriptengine-ruby
10268 plasma-scriptengine-webkit
10269 plasma-scriptengines
10270 plasma-wallpapers-addons
10271 plasma-widget-folderview
10272 plasma-widget-networkmanagement
10273 ruby
10274 sweeper
10275 update-notifier-kde
10276 xscreensaver-data-extra
10277 xscreensaver-gl
10278 xscreensaver-gl-extra
10279 xscreensaver-screensaver-bsod
10280 &lt;/p&gt;&lt;/blockquote&gt;
10281
10282 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10283
10284 &lt;blockquote&gt;&lt;p&gt;
10285 ark
10286 google-gadgets-common
10287 google-gadgets-qt
10288 htdig
10289 kate
10290 kdebase-bin
10291 kdebase-data
10292 kdepasswd
10293 kfind
10294 klipper
10295 konq-plugins
10296 konqueror
10297 ksysguard
10298 ksysguardd
10299 libarchive1
10300 libcln6
10301 libeet1
10302 libeina-svn-06
10303 libggadget-1.0-0b
10304 libggadget-qt-1.0-0b
10305 libgps19
10306 libkdecorations4
10307 libkephal4
10308 libkonq4
10309 libkonqsidebarplugin4a
10310 libkscreensaver5
10311 libksgrd4
10312 libksignalplotter4
10313 libkunitconversion4
10314 libkwineffects1a
10315 libmarblewidget4
10316 libntrack-qt4-1
10317 libntrack0
10318 libplasma-geolocation-interface4
10319 libplasmaclock4a
10320 libplasmagenericshell4
10321 libprocesscore4a
10322 libprocessui4a
10323 libqalculate5
10324 libqedje0a
10325 libqtruby4shared2
10326 libqzion0a
10327 libruby1.8
10328 libscim8c2a
10329 libsmokekdecore4-3
10330 libsmokekdeui4-3
10331 libsmokekfile3
10332 libsmokekhtml3
10333 libsmokekio3
10334 libsmokeknewstuff2-3
10335 libsmokeknewstuff3-3
10336 libsmokekparts3
10337 libsmokektexteditor3
10338 libsmokekutils3
10339 libsmokenepomuk3
10340 libsmokephonon3
10341 libsmokeplasma3
10342 libsmokeqtcore4-3
10343 libsmokeqtdbus4-3
10344 libsmokeqtgui4-3
10345 libsmokeqtnetwork4-3
10346 libsmokeqtopengl4-3
10347 libsmokeqtscript4-3
10348 libsmokeqtsql4-3
10349 libsmokeqtsvg4-3
10350 libsmokeqttest4-3
10351 libsmokeqtuitools4-3
10352 libsmokeqtwebkit4-3
10353 libsmokeqtxml4-3
10354 libsmokesolid3
10355 libsmokesoprano3
10356 libtaskmanager4a
10357 libtidy-0.99-0
10358 libweather-ion4a
10359 libxklavier16
10360 libxxf86misc1
10361 okteta
10362 oxygencursors
10363 plasma-dataengines-addons
10364 plasma-scriptengine-superkaramba
10365 plasma-widget-lancelot
10366 plasma-widgets-addons
10367 plasma-widgets-workspace
10368 polkit-kde-1
10369 ruby1.8
10370 systemsettings
10371 update-notifier-common
10372 &lt;/p&gt;&lt;/blockquote&gt;
10373
10374 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
10375 aptitude a bit more similar, but there are still quite a lott of
10376 differences. I have no idea what packages should be installed after
10377 the upgrade, but hope those that do can have a look.&lt;/p&gt;
10378 </description>
10379 </item>
10380
10381 <item>
10382 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
10383 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
10384 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
10385 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
10386 <description>&lt;p&gt;Most of the computers in use by the
10387 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
10388 are virtual machines. And they have been Xen machines running on a
10389 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
10390 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
10391 bit harder that it could have been, because we set up the Xen virtual
10392 machines to get the virtual partitions from LVM, which as far as I
10393 know is not supported by KVM. So to migrate, we had to convert
10394 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
10395
10396 &lt;p&gt;I found
10397 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
10398 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
10399 migration. It uses qemu-img from the qemu package to make the disk
10400 image, parted to partition it, losetup and kpartx to present the disk
10401 image partions as devices, and dd to copy the data. I NFS mounted the
10402 new servers storage area on the old server to do the migration.&lt;/p&gt;
10403
10404 &lt;pre&gt;
10405 #!/bin/sh
10406
10407 # Based on
10408 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
10409
10410 set -e
10411 set -x
10412
10413 if [ -z &quot;$1&quot; ] ; then
10414 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
10415 exit 1
10416 else
10417 host=&quot;$1&quot;
10418 fi
10419
10420 if [ ! -e /dev/vg_data/$host-disk ] ; then
10421 echo &quot;error: unable to find LVM volume for $host&quot;
10422 exit 1
10423 fi
10424
10425 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
10426 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
10427 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
10428 totalsize=$(( ( $disksize + $swapsize ) ))
10429
10430 img=$host.img
10431 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
10432 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
10433
10434 parted $img mklabel msdos
10435 parted $img mkpart primary linux-swap 0 $disksize
10436 parted $img mkpart primary ext2 $disksize $totalsize
10437 parted $img set 1 boot on
10438
10439 modprobe dm-mod
10440 losetup /dev/loop0 $img
10441 kpartx -a /dev/loop0
10442
10443 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
10444 fsck.ext3 -f /dev/mapper/loop0p1 || true
10445 mkswap /dev/mapper/loop0p2
10446
10447 kpartx -d /dev/loop0
10448 losetup -d /dev/loop0
10449 &lt;/pre&gt;
10450
10451 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
10452 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
10453
10454 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
10455 the new disk image attached, installed grub-pc and linux-image-686 and
10456 set up grub to boot from the disk image. After this, the KVM machines
10457 seem to work just fine.&lt;/p&gt;
10458 </description>
10459 </item>
10460
10461 <item>
10462 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
10463 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
10464 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
10465 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
10466 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
10467 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
10468 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
10469 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
10470
10471 &lt;p&gt;I still do not know what a correct migration should look like, so I
10472 report any differences between apt and aptitude and hope someone else
10473 can see if anything should be changed.&lt;/p&gt;
10474
10475 &lt;p&gt;This is for Gnome:&lt;/p&gt;
10476
10477 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10478
10479 &lt;blockquote&gt;&lt;p&gt;
10480 apache2.2-bin aptdaemon at-spi baobab binfmt-support
10481 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
10482 dmz-cursor-theme empathy empathy-common finger
10483 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
10484 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
10485 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
10486 gnome-cards-data gnome-codec-install gnome-core
10487 gnome-desktop-environment gnome-disk-utility gnome-screenshot
10488 gnome-search-tool gnome-session-canberra gnome-spell
10489 gnome-system-log gnome-themes-extras gnome-themes-more
10490 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
10491 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
10492 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
10493 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
10494 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
10495 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
10496 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
10497 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
10498 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
10499 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
10500 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
10501 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
10502 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
10503 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
10504 libgtk2.0-cil libgtkglext1 libgtksourceview-common
10505 libgtksourceview2.0-common libmono-addins-gui0.2-cil
10506 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
10507 libmono-i18n-west2.0-cil libmono-posix2.0-cil
10508 libmono-security2.0-cil libmono-sharpzip2.84-cil
10509 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
10510 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
10511 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
10512 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
10513 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
10514 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
10515 libxalan2-java libxerces2-java media-player-info mesa-utils
10516 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
10517 nautilus-sendto-empathy openoffice.org-writer2latex
10518 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
10519 python-aptdaemon python-aptdaemon-gtk python-axiom
10520 python-beautifulsoup python-bugbuddy python-clientform
10521 python-coherence python-configobj python-crypto python-cupshelpers
10522 python-cupsutils python-eggtrayicon python-elementtree
10523 python-epsilon python-evolution python-feedparser python-gdata
10524 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
10525 python-gtksourceview2 python-httplib2 python-louie python-mako
10526 python-markupsafe python-mechanize python-nevow python-notify
10527 python-opengl python-openssl python-pam python-pkg-resources
10528 python-pyasn1 python-pysqlite2 python-rdflib python-serial
10529 python-tagpy python-twisted-bin python-twisted-conch
10530 python-twisted-core python-twisted-web python-utidylib python-webkit
10531 python-xdg python-zope.interface remmina remmina-plugin-data
10532 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
10533 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
10534 software-center svgalibg1 system-config-printer-udev
10535 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
10536 totem totem-coherence totem-mozilla totem-plugins
10537 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
10538 zip
10539 &lt;/p&gt;&lt;/blockquote&gt;
10540
10541 Installed using apt-get, removed with aptitude
10542
10543 &lt;blockquote&gt;&lt;p&gt;
10544 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
10545 epiphany-extensions epiphany-gecko evolution-exchange
10546 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
10547 gedit-common gnome-app-install gnome-games gnome-games-data
10548 gnome-nettool gnome-system-tools gnome-themes gnome-utils
10549 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
10550 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
10551 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
10552 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
10553 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
10554 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
10555 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
10556 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
10557 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
10558 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
10559 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
10560 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
10561 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
10562 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
10563 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
10564 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
10565 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
10566 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
10567 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
10568 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
10569 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
10570 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
10571 sound-juicer swfdec-gnome system-config-printer totem-common
10572 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
10573 &lt;/p&gt;&lt;/blockquote&gt;
10574
10575 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10576
10577 &lt;blockquote&gt;&lt;p&gt;
10578 gstreamer0.10-gnomevfs
10579 &lt;/p&gt;&lt;/blockquote&gt;
10580
10581 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10582
10583 &lt;blockquote&gt;&lt;p&gt;
10584 [nothing]
10585 &lt;/p&gt;&lt;/blockquote&gt;
10586
10587 &lt;p&gt;This is for KDE:&lt;/p&gt;
10588
10589 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10590
10591 &lt;blockquote&gt;&lt;p&gt;
10592 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
10593 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
10594 ghostscript-x git gnome-audio gnugo granatier gs-common
10595 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
10596 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
10597 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
10598 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10599 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
10600 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
10601 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10602 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
10603 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
10604 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
10605 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
10606 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
10607 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
10608 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
10609 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
10610 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
10611 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
10612 libkrossui4 libmailtools-perl libmime-tools-perl
10613 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
10614 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
10615 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
10616 lirc luatex marble networkstatus noatun-plugins
10617 openoffice.org-writer2latex palapeli palapeli-data parley
10618 parley-data poster psutils pulseaudio pulseaudio-esound-compat
10619 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
10620 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
10621 ttf-sazanami-gothic
10622 &lt;/p&gt;&lt;/blockquote&gt;
10623
10624 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10625
10626 &lt;blockquote&gt;&lt;p&gt;
10627 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
10628 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
10629 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
10630 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
10631 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
10632 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
10633 kitchensync kiten kjumpingcube klatin klettres klickety klines
10634 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
10635 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
10636 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
10637 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
10638 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
10639 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
10640 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
10641 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
10642 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10643 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
10644 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
10645 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10646 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
10647 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
10648 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
10649 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
10650 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10651 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
10652 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
10653 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
10654 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
10655 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
10656 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
10657 mpeglib network-manager-kde noatun pmount tex-common texlive-base
10658 texlive-common texlive-doc-base texlive-fonts-recommended tidy
10659 ttf-dustin ttf-kochi-gothic ttf-sjfonts
10660 &lt;/p&gt;&lt;/blockquote&gt;
10661
10662 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10663
10664 &lt;blockquote&gt;&lt;p&gt;
10665 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
10666 kdeartwork kdebase kdebase-apps kdebase-workspace
10667 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
10668 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
10669 netpbm plasma-widget-folderview plasma-widget-networkmanagement
10670 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
10671 xscreensaver-screensaver-bsod
10672 &lt;/p&gt;&lt;/blockquote&gt;
10673
10674 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10675
10676 &lt;blockquote&gt;&lt;p&gt;
10677 kdebase-bin konq-plugins konqueror
10678 &lt;/p&gt;&lt;/blockquote&gt;
10679 </description>
10680 </item>
10681
10682 <item>
10683 <title>Gnash buildbot slave and Debian kfreebsd</title>
10684 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
10685 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
10686 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
10687 <description>&lt;p&gt;Answering
10688 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
10689 call from the Gnash project&lt;/a&gt; for
10690 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
10691 current source, I have set up a virtual KVM machine on the Debian
10692 Edu/Skolelinux virtualization host to test the git source on
10693 Debian/Squeeze. I hope this can help the developers in getting new
10694 releases out more often.&lt;/p&gt;
10695
10696 &lt;p&gt;As the developers want less main-stream build platforms tested to,
10697 I have considered setting up a &lt;a
10698 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
10699 machine as well. I have also considered using the kfreebsd
10700 architecture in Debian as a file server in NUUG to get access to the 5
10701 TB zfs volume we currently use to store DV video. Because of this, I
10702 finally got around to do a test installation of Debian/Squeeze with
10703 kfreebsd. Installation went fairly smooth, thought I noticed some
10704 visual glitches in the cdebconf dialogs (black cursor left on the
10705 screen at random locations). Have not gotten very far with the
10706 testing. Noticed cfdisk did not work, but fdisk did so it was not a
10707 fatal problem. Have to spend some more time on it to see if it is
10708 useful as a file server for NUUG. Will try to find time to set up a
10709 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
10710 </description>
10711 </item>
10712
10713 <item>
10714 <title>Debian in 3D</title>
10715 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
10716 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
10717 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
10718 <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;
10719
10720 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
10721 3D linked in from
10722 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
10723 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
10724 </description>
10725 </item>
10726
10727 <item>
10728 <title>Software updates 2010-10-24</title>
10729 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
10730 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
10731 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
10732 <description>&lt;p&gt;Some updates.&lt;/p&gt;
10733
10734 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
10735 raise money for the project is going well. The lower limit of 10
10736 signers was reached in 24 hours, and so far 13 people have signed it.
10737 More signers and more funding is most welcome, and I am really curious
10738 how far we can get before the time limit of December 24 is reached.
10739 :)&lt;/p&gt;
10740
10741 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
10742 about what appear to be a great code coverage tool capable of
10743 generating code coverage stats without any changes to the source code.
10744 It is called
10745 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
10746 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
10747 It is missing in Debian, but the git source built just fine in Squeeze
10748 after I installed libelf-dev, libdwarf-dev, pkg-config and
10749 libglib2.0-dev. Failed to build in Lenny, but suspect that is
10750 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
10751
10752 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
10753 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
10754 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
10755 alpha test release of the Squeeze based Debian Edu /
10756 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
10757 release. Give it a try if you need a complete linux solution for your
10758 school, including central infrastructure server, workstations, thin
10759 client servers and diskless workstations. A nice touch added
10760 yesterday is RDP support on the thin client servers, for windows
10761 clients to get a Linux desktop on request.&lt;/p&gt;
10762 </description>
10763 </item>
10764
10765 <item>
10766 <title>Some notes on Flash in Debian and Debian Edu</title>
10767 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
10768 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
10769 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
10770 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
10771 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
10772 second most popular used package that is missing in Debian. The sixth
10773 most popular is flashplayer-mozilla. This is a clear indication that
10774 working flash is important for Debian users. Around 10 percent of the
10775 users submitting data to popcon.debian.org have this package
10776 installed.&lt;/p&gt;
10777
10778 &lt;p&gt;In the report written by Lars Risan in August 2008
10779&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
10780 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
10781 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
10782 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
10783 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
10784 web sites require Flash to work, and lacking working Flash support in
10785 the web browser and the problems with installing it was perceived as a
10786 good reason to stay with Windows.&lt;/p&gt;
10787
10788 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
10789 said to be the retarded cousin that did not really understand
10790 everything you told him but could work fairly well. This was a
10791 comment regarding the problems Linux have with proprietary formats and
10792 non-standard web pages, and is sad because it exposes a fairly common
10793 understanding of whose fault it is if web pages that only work in for
10794 example Internet Explorer 6 fail to work on Firefox, and funny because
10795 it explain very well how annoying it is for users when Linux
10796 distributions do not work with the documents they receive or the web
10797 pages they want to visit.&lt;/p&gt;
10798
10799 &lt;p&gt;This is part of the reason why I believe it is important for Debian
10800 and Debian Edu to have a well working Flash implementation in the
10801 distribution, to get at least popular sites as Youtube and Google
10802 Video to working out of the box. For Squeeze, Debian have the chance
10803 to include the latest version of Gnash that will make this happen, as
10804 the new release 0.8.8 was published a few weeks ago and is resting in
10805 unstable. The new version work with more sites that version 0.8.7.
10806 The Gnash maintainers have asked for a freeze exception, but the
10807 release team have not had time to reply to it yet. I hope they agree
10808 with me that Flash is important for the Debian desktop users, and thus
10809 accept the new package into Squeeze.&lt;/p&gt;
10810 </description>
10811 </item>
10812
10813 <item>
10814 <title>Circular package dependencies harms apt recovery</title>
10815 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
10816 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
10817 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
10818 <description>&lt;p&gt;I discovered this while doing
10819 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
10820 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
10821 in Debian still got circular dependencies, and it is often claimed
10822 that apt and aptitude should be able to handle this just fine, but
10823 some times these dependency loops causes apt to fail.&lt;/p&gt;
10824
10825 &lt;p&gt;An example is from todays
10826 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
10827 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
10828 causes perl-modules to fail to upgrade. The cause is simple. If a
10829 package fail to unpack, then only part of packages with the circular
10830 dependency might end up being unpacked when unpacking aborts, and the
10831 ones already unpacked will fail to configure in the recovery phase
10832 because its dependencies are unavailable.&lt;/p&gt;
10833
10834 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
10835
10836 &lt;blockquote&gt;&lt;pre&gt;
10837 dpkg: dependency problems prevent configuration of perl-modules:
10838 perl-modules depends on perl (&gt;= 5.10.1-1); however:
10839 Version of perl on system is 5.10.0-19lenny2.
10840 dpkg: error processing perl-modules (--configure):
10841 dependency problems - leaving unconfigured
10842 &lt;/pre&gt;&lt;/blockquote&gt;
10843
10844 &lt;p&gt;The perl/perl-modules circular dependency is already
10845 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
10846 hopefully be solved as soon as possible, but it is not the only one,
10847 and each one of these loops in the dependency tree can cause similar
10848 failures. Of course, they only occur when there are bugs in other
10849 packages causing the unpacking to fail, but it is rather nasty when
10850 the failure of one package causes the problem to become worse because
10851 of dependency loops.&lt;/p&gt;
10852
10853 &lt;p&gt;Thanks to
10854 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
10855 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
10856 dependencies
10857 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
10858 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
10859
10860 &lt;p&gt;Todays testing also exposed a bug in
10861 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
10862 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
10863 apt-get and aptitude, the latter possibly caused by some circular
10864 dependency. Reported both to BTS to try to get someone to look at
10865 it.&lt;/p&gt;
10866 </description>
10867 </item>
10868
10869 <item>
10870 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
10871 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
10872 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
10873 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
10874 <description>&lt;p&gt;This is a
10875 &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;
10876 on my
10877 &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
10878 work&lt;/a&gt; on
10879 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
10880 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
10881
10882 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
10883 LDAP objects, I have had a look at how the packages pdns-backend-ldap
10884 and dhcp3-server-ldap in Debian use the LDAP server. The two
10885 implementations are quite different in how they use LDAP.&lt;/p&gt;
10886
10887 To get this information, I started slapd with debugging enabled and
10888 dumped the debug output to a file to get the LDAP searches performed
10889 on a Debian Edu main-server. Here is a summary.
10890
10891 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
10892
10893 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
10894 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
10895 the web.
10896
10897 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
10898 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
10899 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
10900 reverse entries are in two different subtrees in LDAP with a structure
10901 based on the DNS names, as in tjener.intern and
10902 2.2.0.10.in-addr.arpa.&lt;/p&gt;
10903
10904 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
10905 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
10906 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
10907 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
10908 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
10909 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
10910 forward entries, it is looking for attributes named dnsttl, arecord,
10911 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
10912 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
10913 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
10914 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
10915 spfrecord and modifytimestamp. For reverse entries it is looking for
10916 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
10917 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
10918 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
10919 ldapsearch commands could look like this:&lt;/p&gt;
10920
10921 &lt;blockquote&gt;&lt;pre&gt;
10922 ldapsearch -h ldap \
10923 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10924 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
10925 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10926 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10927 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10928 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10929
10930 ldapsearch -h ldap \
10931 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10932 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
10933 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
10934 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
10935 srvrecord naptrrecord modifytimestamp
10936 &lt;/pre&gt;&lt;/blockquote&gt;
10937
10938 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
10939 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
10940 example LDAP objects used there. In addition to these objects, the
10941 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
10942 also exist.&lt;/p&gt;
10943
10944 &lt;blockquote&gt;&lt;pre&gt;
10945 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
10946 objectclass: top
10947 objectclass: dnsdomain
10948 objectclass: domainrelatedobject
10949 dc: tjener
10950 arecord: 10.0.2.2
10951 associateddomain: tjener.intern
10952
10953 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
10954 objectclass: top
10955 objectclass: dnsdomain2
10956 objectclass: domainrelatedobject
10957 dc: 2
10958 ptrrecord: tjener.intern
10959 associateddomain: 2.2.0.10.in-addr.arpa
10960 &lt;/pre&gt;&lt;/blockquote&gt;
10961
10962 &lt;p&gt;In strict mode, the server behaves differently. When looking for
10963 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
10964 same base as in the tree mode for a object with filter
10965 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
10966 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
10967 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
10968 naptrrecord and modifytimestamp. For reverse entires it also do a
10969 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
10970 and the requested attributes are associateddomain, dnsttl and
10971 modifytimestamp. In short, in strict mode the objects with ptrrecord
10972 go away, and the arecord attribute in the forward object is used
10973 instead.&lt;/p&gt;
10974
10975 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
10976 like this:&lt;/p&gt;
10977
10978 &lt;blockquote&gt;&lt;pre&gt;
10979 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10980 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
10981 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10982 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10983 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10984 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10985
10986 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10987 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
10988 &lt;/pre&gt;&lt;/blockquote&gt;
10989
10990 &lt;p&gt;In addition to the forward and reverse searches , there is also a
10991 search for SOA records, which behave similar to the forward and
10992 reverse lookups.&lt;/p&gt;
10993
10994 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
10995 specify any objectclass names, and instead look for the attributes it
10996 need to generate a DNS reply. This make it able to work with any
10997 objectclass that provide the needed attributes.&lt;/p&gt;
10998
10999 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
11000 dnsdomain2 schemas. The latter is used for reverse entries like
11001 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
11002
11003 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
11004 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11005 attributes) and domainrelatedobject (for associatedDomain). The use
11006 of structural object classes make it impossible to combine these
11007 classes with the object classes used by DHCP.&lt;/p&gt;
11008
11009 &lt;p&gt;There are other schemas that could be used too, for example the
11010 dnszone structural object class used by Gosa and bind-sdb for the DNS
11011 attributes combined with the domainrelatedobject object class, but in
11012 this case some unused attributes would have to be included as well
11013 (zonename and relativedomainname).&lt;/p&gt;
11014
11015 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
11016 mode and not use any of the existing objectclasses (dnsdomain,
11017 dnsdomain2 and dnszone) when one want to combine the DNS information
11018 with DHCP information, and instead create a auxiliary object class
11019 defined something like this (using the attributes defined for
11020 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
11021
11022 &lt;blockquote&gt;&lt;pre&gt;
11023 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
11024 SUP top
11025 AUXILIARY
11026 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11027 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11028 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11029 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11030 A6Record $ DNAMERecord
11031 ))
11032 &lt;/pre&gt;&lt;/blockquote&gt;
11033
11034 &lt;p&gt;This will allow any object to become a DNS entry when combined with
11035 the domainrelatedobject object class, and allow any entity to include
11036 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
11037 developers asking for their view on this schema and if they are
11038 interested in providing such schema with PowerDNS, and I hope my
11039 message will be accepted into their mailing list soon.&lt;/p&gt;
11040
11041 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
11042
11043 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
11044 the object attributes, and then uses the attributes it want. This
11045 make it harder to figure out exactly what attributes are used, but
11046 thanks to the working example in Debian Edu I can at least get an idea
11047 what is needed without having to read the source code.&lt;/p&gt;
11048
11049 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
11050 search filter to use to locate the correct dhcpServer entity is
11051 stored. These are the relevant entries from
11052 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
11053
11054 &lt;blockquote&gt;&lt;pre&gt;
11055 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
11056 ldap-dhcp-server-cn &quot;dhcp&quot;;
11057 &lt;/pre&gt;&lt;/blockquote&gt;
11058
11059 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
11060 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
11061 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
11062 search result is this entry:&lt;/p&gt;
11063
11064 &lt;blockquote&gt;&lt;pre&gt;
11065 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11066 cn: dhcp
11067 objectClass: top
11068 objectClass: dhcpServer
11069 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11070 &lt;/pre&gt;&lt;/blockquote&gt;
11071
11072 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
11073 subtree with DHCP configuration. The DHCP configuration subtree base
11074 is located using a base scope search with base &quot;cn=DHCP
11075 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
11076 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
11077 The search result is this entry:&lt;/p&gt;
11078
11079 &lt;blockquote&gt;&lt;pre&gt;
11080 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11081 cn: DHCP Config
11082 objectClass: top
11083 objectClass: dhcpService
11084 objectClass: dhcpOptions
11085 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11086 dhcpStatements: ddns-update-style none
11087 dhcpStatements: authoritative
11088 dhcpOption: smtp-server code 69 = array of ip-address
11089 dhcpOption: www-server code 72 = array of ip-address
11090 dhcpOption: wpad-url code 252 = text
11091 &lt;/pre&gt;&lt;/blockquote&gt;
11092
11093 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
11094 all the DHCP configuration is loaded, it is ready to receive requests.
11095 The subtree in Debian Edu contain objects with object classes
11096 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11097 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11098 and information about netmasks, dynamic range etc. Leaving out the
11099 details here because it is not relevant for the focus of my
11100 investigation, which is to see if it is possible to merge dns and dhcp
11101 related computer objects.&lt;/p&gt;
11102
11103 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
11104 of the client (00:00:00:00:00:00 in this example), using a subtree
11105 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
11106 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11107 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
11108 like:&lt;/p&gt;
11109
11110 &lt;blockquote&gt;&lt;pre&gt;
11111 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11112 cn: hostname
11113 objectClass: top
11114 objectClass: dhcpHost
11115 dhcpHWAddress: ethernet 00:00:00:00:00:00
11116 dhcpStatements: fixed-address hostname
11117 &lt;/pre&gt;&lt;/blockquote&gt;
11118
11119 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
11120 The object classes need to have fixed names, and the configuration
11121 need to be stored in a fairly specific LDAP structure. On the
11122 positive side, the invidiual dhcpHost entires can be anywhere without
11123 the DN pointed to by the dhcpServer entries. The latter should make
11124 it possible to group all host entries in a subtree next to the
11125 configuration entries, and this subtree can also be shared with the
11126 DNS server if the schema proposed above is combined with the dhcpHost
11127 structural object class.
11128
11129 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
11130
11131 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
11132 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
11133 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
11134 allowing DNS objects to be stored anywhere under the base cn specified
11135 in the configuration.&lt;/p&gt;
11136
11137 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
11138 regarding which LDAP schemas to use and which LDAP structure to use.
11139 I guess one could implement ones own schema, as long as the
11140 objectclasses and attributes have the names used, but this do not
11141 really help when the DHCP subtree need to have a fairly fixed
11142 structure.&lt;/p&gt;
11143
11144 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
11145 this might work for Debian Edu:&lt;/p&gt;
11146
11147 &lt;blockquote&gt;&lt;pre&gt;
11148 ou=services
11149 cn=machine-info (dhcpService) - dhcpServiceDN points here
11150 cn=dhcp (dhcpServer)
11151 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11152 cn=10.0.2.0 (dhcpSubnet)
11153 cn=group1 (dhcpGroup/dhcpOptions)
11154 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11155 cn=192.168.0.0 (dhcpSubnet)
11156 cn=group1 (dhcpGroup/dhcpOptions)
11157 ou=machines - PowerDNS base points here
11158 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11159 &lt;/pre&gt;&lt;/blockquote&gt;
11160
11161 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
11162 entries to be in the dhcpGroup subtrees, the entries can be stored
11163 there instead of a common machines subtree, and the PowerDNS base
11164 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
11165
11166 &lt;p&gt;The combined object under the machines subtree would look something
11167 like this:&lt;/p&gt;
11168
11169 &lt;blockquote&gt;&lt;pre&gt;
11170 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11171 dc: hostname
11172 objectClass: top
11173 objectClass: dhcpHost
11174 objectclass: domainrelatedobject
11175 objectclass: dnsDomainAux
11176 associateddomain: hostname.intern
11177 arecord: 10.11.12.13
11178 dhcpHWAddress: ethernet 00:00:00:00:00:00
11179 dhcpStatements: fixed-address hostname.intern
11180 &lt;/pre&gt;&lt;/blockquote&gt;
11181
11182 &lt;/p&gt;One could even add the LTSP configuration associated with a given
11183 machine, as long as the required attributes are available in a
11184 auxiliary object class.&lt;/p&gt;
11185 </description>
11186 </item>
11187
11188 <item>
11189 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
11190 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
11191 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
11192 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
11193 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
11194 DHCP services in Debian Edu to use the same LDAP objects for a given
11195 computer, to avoid the possibility of having a inconsistent state for
11196 a computer in LDAP (as in DHCP but no DNS entry or the other way
11197 around) and make it easier to add computers to LDAP.&lt;/p&gt;
11198
11199 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
11200 information finally found a solution that seem to work.&lt;/p&gt;
11201
11202 &lt;p&gt;The old setup required three LDAP objects for a given computer.
11203 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11204 we switch powerdns to use its strict LDAP method (ldap-method=strict
11205 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11206 merged into one while making it impossible to transfer the reverse map
11207 to a slave DNS server.&lt;/p&gt;
11208
11209 &lt;p&gt;If we also replace the object class used to get the DNS related
11210 attributes to one allowing these attributes to be combined with the
11211 dhcphost object class, we can merge the DNS and DHCP entries into one.
11212 I&#39;ve written such object class in the dnsdomainaux.schema file (need
11213 proper OIDs, but that is a minor issue), and tested the setup. It
11214 seem to work.&lt;/p&gt;
11215
11216 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
11217 for both DNS and DHCP, and even the LTSP configuration I suggested in
11218 an earlier email. The combined LDAP object will look something like
11219 this:&lt;/p&gt;
11220
11221 &lt;blockquote&gt;&lt;pre&gt;
11222 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11223 cn: hostname
11224 objectClass: dhcphost
11225 objectclass: domainrelatedobject
11226 objectclass: dnsdomainaux
11227 associateddomain: hostname.intern
11228 arecord: 10.11.12.13
11229 dhcphwaddress: ethernet 00:00:00:00:00:00
11230 dhcpstatements: fixed-address hostname
11231 ldapconfigsound: Y
11232 &lt;/pre&gt;&lt;/blockquote&gt;
11233
11234 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
11235 the DHCP server uses the dhcphwaddress and dhcpstatements entries
11236 before asking DNS to resolve the fixed-adddress. LTSP will use
11237 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
11238
11239 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
11240 dhcphost in a different location, to allow us to put the objects
11241 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
11242 that. If I can&#39;t figure out a way to do that, we can still get rid of
11243 the hosts subtree and move all its content into the DHCP Config tree
11244 (which probably should be renamed to be more related to the new
11245 content. I suspect cn=dnsdhcp,ou=services or something like that
11246 might be a good place to put it.&lt;/p&gt;
11247
11248 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11249 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11250 </description>
11251 </item>
11252
11253 <item>
11254 <title>Idea for storing LTSP configuration in LDAP</title>
11255 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
11256 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
11257 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
11258 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
11259 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
11260 clients, and that this can be used to fetch configuration from LDAP if
11261 Debian Edu choose to store configuration there.&lt;/p&gt;
11262
11263 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
11264 to get configuration from LDAP. The idea is to look up the MAC
11265 address of the client in LDAP, and look for attributes on the form
11266 ltspconfigsetting=value, and use this to export SETTING=value to the
11267 LTSP clients.&lt;/p&gt;
11268
11269 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
11270 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
11271 allowing us to store all information about a computer in one place.&lt;/p&gt;
11272
11273 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
11274 this approach. A real LDAP schema for the ltspClientAux objectclass
11275 need to be written. Comments, suggestions, etc?&lt;/p&gt;
11276
11277 &lt;blockquote&gt;&lt;pre&gt;
11278 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
11279 #
11280 # Fetch LTSP client settings from LDAP based on MAC address
11281 #
11282 # Uses ethernet address as stored in the dhcpHost objectclass using
11283 # the dhcpHWAddress attribute or ethernet address stored in the
11284 # ieee802Device objectclass with the macAddress attribute.
11285 #
11286 # This module is written to be schema agnostic, and only depend on the
11287 # existence of attribute names.
11288 #
11289 # The LTSP configuration variables are saved directly using a
11290 # ltspConfig prefix and uppercasing the rest of the attribute name.
11291 # To set the SERVER variable, set the ltspConfigServer attribute.
11292 #
11293 # Some LDAP schema should be created with all the relevant
11294 # configuration settings. Something like this should work:
11295 #
11296 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
11297 # SUP top
11298 # AUXILIARY
11299 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
11300
11301 LDAPSERVER=$(debian-edu-ldapserver)
11302 if [ &quot;$LDAPSERVER&quot; ] ; then
11303 LDAPBASE=$(debian-edu-ldapserver -b)
11304 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
11305 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
11306 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
11307 grep &#39;^ltspConfig&#39; | while read attr value ; do
11308 # Remove prefix and convert to upper case
11309 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
11310 # bass value on to clients
11311 eval &quot;$attr=$value; export $attr&quot;
11312 done
11313 done
11314 fi
11315 &lt;/pre&gt;&lt;/blockquote&gt;
11316
11317 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
11318 the while block might end up in a subshell causing the variables set
11319 there to not show up in ltsp-config, but if that is the case I am sure
11320 the code can be restructured to make sure the variables are passed on.
11321 I expect that can be solved with some testing. :)&lt;/p&gt;
11322
11323 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11324 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11325
11326 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
11327 configuration in LDAP that was created around year 2000 by
11328 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
11329 Xperience, Inc., 2000&lt;/a&gt;. I found its
11330 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
11331 personal home page over at redhat.com.&lt;/p&gt;
11332 </description>
11333 </item>
11334
11335 <item>
11336 <title>jXplorer, a very nice LDAP GUI</title>
11337 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
11338 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
11339 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
11340 <description>&lt;p&gt;Since
11341 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
11342 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
11343 LDAP GUI that is even better than luma. The java application
11344 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
11345 moving LDAP objects and subtrees using drag-and-drop, and can
11346 authenticate using Kerberos. I have only tested the Kerberos
11347 authentication, but do not have a LDAP setup allowing me to rewrite
11348 LDAP with my test user yet. It is
11349 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
11350 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
11351 have with it is how it handle errors. If something go wrong, its
11352 non-intuitive behaviour require me to go through some query work list
11353 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
11354 </description>
11355 </item>
11356
11357 <item>
11358 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
11359 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
11360 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
11361 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
11362 <description>&lt;p&gt;Here is a short update on my &lt;a
11363 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
11364 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
11365 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
11366 not reporting the status for KDE, because the upgrade crashes when
11367 aptitude try because of missing conflicts
11368 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
11369 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
11370
11371 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
11372 complete list of the installed packages. Based on this I see these
11373 differences when I did a test run today. As usual, I do not really
11374 know what the correct set of packages would be, but thought it best to
11375 publish the difference.&lt;/p&gt;
11376
11377 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11378
11379 &lt;blockquote&gt;&lt;p&gt;
11380 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
11381 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
11382 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
11383 libgtksourceview-common libpt-1.10.10-plugins-alsa
11384 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
11385 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
11386 python-4suite-xml python-eggtrayicon python-gtkhtml2
11387 python-gtkmozembed svgalibg1 xserver-xephyr zip
11388 &lt;/p&gt;&lt;/blockquote&gt;
11389
11390 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11391
11392 &lt;blockquote&gt;&lt;p&gt;
11393 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
11394 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
11395 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
11396 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
11397 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
11398 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
11399 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
11400 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
11401 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
11402 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
11403 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
11404 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
11405 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
11406 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
11407 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
11408 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
11409 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
11410 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
11411 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
11412 mysql-common swfdec-gnome totem-gstreamer wodim
11413 &lt;/p&gt;&lt;/blockquote&gt;
11414
11415 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11416
11417 &lt;blockquote&gt;&lt;p&gt;
11418 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
11419 python-gnomekeyring python-wnck rhythmbox-plugins xorg
11420 xserver-xorg-input-all xserver-xorg-input-evdev
11421 xserver-xorg-input-kbd xserver-xorg-input-mouse
11422 xserver-xorg-input-synaptics xserver-xorg-video-all
11423 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
11424 xserver-xorg-video-chips xserver-xorg-video-cirrus
11425 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11426 xserver-xorg-video-glint xserver-xorg-video-i128
11427 xserver-xorg-video-i740 xserver-xorg-video-mach64
11428 xserver-xorg-video-mga xserver-xorg-video-neomagic
11429 xserver-xorg-video-nouveau xserver-xorg-video-nv
11430 xserver-xorg-video-r128 xserver-xorg-video-radeon
11431 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
11432 xserver-xorg-video-s3 xserver-xorg-video-s3virge
11433 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
11434 xserver-xorg-video-sis xserver-xorg-video-sisusb
11435 xserver-xorg-video-tdfx xserver-xorg-video-tga
11436 xserver-xorg-video-trident xserver-xorg-video-tseng
11437 xserver-xorg-video-vesa xserver-xorg-video-vmware
11438 xserver-xorg-video-voodoo
11439 &lt;/p&gt;&lt;/blockquote&gt;
11440
11441 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11442
11443 &lt;blockquote&gt;&lt;p&gt;
11444 deskbar-applet xserver-xorg xserver-xorg-core
11445 xserver-xorg-input-wacom xserver-xorg-video-intel
11446 xserver-xorg-video-openchrome
11447 &lt;/p&gt;&lt;/blockquote&gt;
11448
11449 &lt;p&gt;I was told on IRC that the xorg-xserver package was
11450 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
11451 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
11452 No idea when it hits Squeeze, but when it does I hope it will reduce
11453 the difference somewhat.
11454 </description>
11455 </item>
11456
11457 <item>
11458 <title>LUMA, a very nice LDAP GUI</title>
11459 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
11460 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
11461 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
11462 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
11463 directory in Debian Edu, and in the process I started to miss a GUI
11464 tool to browse the LDAP tree. The only one I was able to find in
11465 Debian/Squeeze and Lenny is
11466 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
11467 be a great tool to get a overview of the current LDAP directory
11468 populated by default in Skolelinux. Thanks to it, I have been able to
11469 find empty and obsolete subtrees, misplaced objects and duplicate
11470 objects. It will be installed by default in Debian/Squeeze. If you
11471 are working with LDAP, give it a go. :)&lt;/p&gt;
11472
11473 &lt;p&gt;I did notice one problem with it I have not had time to report to
11474 the BTS yet. There is no .desktop file in the package, so the tool do
11475 not show up in the Gnome and KDE menus, but only deep down in in the
11476 Debian submenu in KDE. I hope that can be fixed before Squeeze is
11477 released.&lt;/p&gt;
11478
11479 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
11480 like to move objects and remove subtrees directly in the GUI, but have
11481 not found a way to do that with LUMA yet. So in the mean time, I use
11482 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
11483
11484 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
11485 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11486
11487 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
11488 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
11489 useful GUI alternative. It seem like a good tool, but is unmaintained
11490 in Debian and got a RC bug keeping it out of Squeeze. Unless that
11491 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
11492 </description>
11493 </item>
11494
11495 <item>
11496 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
11497 <link>https://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>
11498 <guid isPermaLink="true">https://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>
11499 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
11500 <description>&lt;p&gt;A while back, I
11501 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
11502 about the fact&lt;/a&gt; that it is not possible with the provided schemas
11503 for storing DNS and DHCP information in LDAP to combine the two sets
11504 of information into one LDAP object representing a computer.&lt;/p&gt;
11505
11506 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
11507 the dhcpHost object class auxiliary, to allow it to be combined with
11508 the dNSDomain object class, and thus forming one object for one
11509 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
11510
11511 &lt;p&gt;If I understand this correctly, it is not safe to do this change
11512 without also changing the assigned number for the object class, and I
11513 do not know enough about LDAP schema design to do that properly for
11514 Debian Edu.&lt;/p&gt;
11515
11516 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
11517 the
11518 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
11519 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
11520 available today from IETF.&lt;/p&gt;
11521
11522 &lt;pre&gt;
11523 --- dhcp.schema (revision 65192)
11524 +++ dhcp.schema (working copy)
11525 @@ -376,7 +376,7 @@
11526 objectclass ( 2.16.840.1.113719.1.203.6.6
11527 NAME &#39;dhcpHost&#39;
11528 DESC &#39;This represents information about a particular client&#39;
11529 - SUP top
11530 + SUP top AUXILIARY
11531 MUST cn
11532 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
11533 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
11534 &lt;/pre&gt;
11535
11536 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
11537 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
11538 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
11539
11540 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11541 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11542 </description>
11543 </item>
11544
11545 <item>
11546 <title>Calling tasksel like the installer, while still getting useful output</title>
11547 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
11548 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
11549 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
11550 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
11551 installs packages during the normal debian-installer run. Until now,
11552 I have ended up letting tasksel do the work, with the annoying problem
11553 of not getting any feedback at all when something fails (like a
11554 conffile question from dpkg or a download that fails), using code like
11555 this:
11556
11557 &lt;blockquote&gt;&lt;pre&gt;
11558 export DEBIAN_FRONTEND=noninteractive
11559 tasksel --new-install
11560 &lt;/pre&gt;&lt;/blockquote&gt;
11561
11562 This would invoke tasksel, let its automatic task selection pick the
11563 tasks to install, and continue to install the requested tasks without
11564 any output what so ever.
11565
11566 Recently I revisited this problem while working on the automatic
11567 package upgrade testing, because tasksel would some times hang without
11568 any useful feedback, and I want to see what is going on when it
11569 happen. Then it occured to me, I can parse the output from tasksel
11570 when asked to run in test mode, and use that aptitude command line
11571 printed by tasksel then to simulate the tasksel run. I ended up using
11572 code like this:
11573
11574 &lt;blockquote&gt;&lt;pre&gt;
11575 export DEBIAN_FRONTEND=noninteractive
11576 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
11577 $cmd
11578 &lt;/pre&gt;&lt;/blockquote&gt;
11579
11580 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
11581 --without-recommends -o APT::Install-Recommends=no -y install
11582 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
11583 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
11584 laptop task and all packages with priority standard , required and
11585 important, just like tasksel would have done it during
11586 installation.&lt;/p&gt;
11587
11588 &lt;p&gt;A better approach is probably to extend tasksel to be able to
11589 install packages without using debconf-apt-progress, for use cases
11590 like this.&lt;/p&gt;
11591 </description>
11592 </item>
11593
11594 <item>
11595 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
11596 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
11597 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
11598 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
11599 <description>&lt;p&gt;My
11600 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
11601 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
11602 finally made the upgrade logs available from
11603 &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;.
11604 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
11605 apt and aptitude, and found their differences interesting. This time
11606 I will only focus on their removal plans.&lt;/p&gt;
11607
11608 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
11609 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
11610 surprising part is that it want to remove xorg and all
11611 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
11612 sure why. When asking aptitude to do the same, it want to remove 129
11613 packages, but most of them are library packages I suspect are no
11614 longer needed. Both of them want to remove bluetooth packages, which
11615 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
11616
11617 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
11618 which seem like a bad idea and xorg the same way as with Gnome. Asking
11619 aptitude for the same, it wants to remove 192 packages, none which are
11620 too surprising.&lt;/p&gt;
11621
11622 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
11623 and avoided, and perhaps others as well. Here are the complete list
11624 of planned removals. The complete logs is available from the URL
11625 above. Note if you want to repeat these tests, that the upgrade test
11626 for kde+apt-get hung in the tasksel setup because of dpkg asking
11627 conffile questions. No idea why. I worked around it by using
11628 &#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
11629 continue.&lt;/p&gt;
11630
11631 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
11632 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
11633 gnome-desktop-environment gnome-network-admin gtkhtml3.14
11634 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
11635 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
11636 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
11637 serpentine swfdec-mozilla update-manager xorg xserver-xorg
11638 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11639 xserver-xorg-input-kbd xserver-xorg-input-mouse
11640 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11641 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11642 xserver-xorg-video-ati xserver-xorg-video-chips
11643 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11644 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11645 xserver-xorg-video-glint xserver-xorg-video-i128
11646 xserver-xorg-video-i740 xserver-xorg-video-imstt
11647 xserver-xorg-video-intel xserver-xorg-video-mach64
11648 xserver-xorg-video-mga xserver-xorg-video-neomagic
11649 xserver-xorg-video-nsc xserver-xorg-video-nv
11650 xserver-xorg-video-openchrome xserver-xorg-video-r128
11651 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11652 xserver-xorg-video-rendition xserver-xorg-video-s3
11653 xserver-xorg-video-s3virge xserver-xorg-video-savage
11654 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11655 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11656 xserver-xorg-video-tga xserver-xorg-video-trident
11657 xserver-xorg-video-tseng xserver-xorg-video-v4l
11658 xserver-xorg-video-vesa xserver-xorg-video-vga
11659 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
11660 xulrunner-1.9-gnome-support&lt;/p&gt;
11661
11662 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
11663
11664 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
11665 djvulibre-desktop finger gnome-app-install gnome-mount
11666 gnome-network-admin gnome-spell gnome-vfs-obexftp
11667 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
11668 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
11669 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
11670 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
11671 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
11672 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
11673 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
11674 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
11675 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
11676 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
11677 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
11678 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
11679 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
11680 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
11681 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
11682 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
11683 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
11684 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
11685 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
11686 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
11687 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
11688 openoffice.org-writer2latex openssl-blacklist p7zip
11689 python-4suite-xml python-eggtrayicon python-gnome2-desktop
11690 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
11691 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
11692 swfdec-mozilla totem-gstreamer update-manager wodim
11693 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11694 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11695 zip&lt;/p&gt;
11696
11697 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
11698
11699 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
11700 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
11701 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
11702 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
11703 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
11704 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
11705 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11706 xserver-xorg-input-kbd xserver-xorg-input-mouse
11707 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11708 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11709 xserver-xorg-video-ati xserver-xorg-video-chips
11710 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11711 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11712 xserver-xorg-video-glint xserver-xorg-video-i128
11713 xserver-xorg-video-i740 xserver-xorg-video-imstt
11714 xserver-xorg-video-intel xserver-xorg-video-mach64
11715 xserver-xorg-video-mga xserver-xorg-video-neomagic
11716 xserver-xorg-video-nsc xserver-xorg-video-nv
11717 xserver-xorg-video-openchrome xserver-xorg-video-r128
11718 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11719 xserver-xorg-video-rendition xserver-xorg-video-s3
11720 xserver-xorg-video-s3virge xserver-xorg-video-savage
11721 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11722 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11723 xserver-xorg-video-tga xserver-xorg-video-trident
11724 xserver-xorg-video-tseng xserver-xorg-video-v4l
11725 xserver-xorg-video-vesa xserver-xorg-video-vga
11726 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
11727
11728 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
11729 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
11730 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
11731 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
11732 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
11733 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11734 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
11735 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
11736 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11737 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
11738 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
11739 kghostview khelpcenter khexedit kiconedit kitchensync klatin
11740 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
11741 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
11742 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
11743 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
11744 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
11745 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
11746 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11747 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
11748 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
11749 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11750 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
11751 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
11752 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
11753 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11754 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
11755 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
11756 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
11757 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
11758 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
11759 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
11760 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
11761 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
11762 texlive-common texlive-doc-base texlive-fonts-recommended
11763 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11764 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11765 xulrunner-1.9&lt;/p&gt;
11766
11767 </description>
11768 </item>
11769
11770 <item>
11771 <title>Automatic upgrade testing from Lenny to Squeeze</title>
11772 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
11773 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
11774 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
11775 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
11776 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
11777 have been discovered and reported in the process
11778 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
11779 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
11780 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
11781 kdebase-workspace-data), and to get a more regular testing going on, I
11782 am working on a script to automate the test.&lt;/p&gt;
11783
11784 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
11785 Gnome or KDE desktop installation inside the chroot before upgrading
11786 it. To ensure no services are started in the chroot, a policy-rc.d
11787 script is inserted. To make sure tasksel believe it is to install a
11788 desktop on a laptop, the tasksel tests are replaced in the chroot
11789 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
11790
11791 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
11792 currently always fail because udev refuses to upgrade with the kernel
11793 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
11794 is created. The bug report
11795 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
11796 this problem do not trigger in a chroot, but I touch the file anyway
11797 to make sure the upgrade go well. Testing on virtual and real
11798 hardware have failed me because of udev so far, and creating this file
11799 do the trick in such settings anyway. This is a
11800 &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
11801 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
11802 maintainer because he lack the resources to rewrite udev to keep
11803 working with old kernels or something like that. I really wish the
11804 udev upstream would keep udev backwards compatible, to avoid such
11805 upgrade problem, but given that they fail to do so, I guess
11806 documenting the way out of this mess is the best option we got for
11807 Debian Squeeze.&lt;/p&gt;
11808
11809 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
11810 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
11811 trick:&lt;/p&gt;
11812
11813 &lt;blockquote&gt;&lt;pre&gt;
11814 #!/bin/sh
11815 set -ex
11816
11817 if [ &quot;$1&quot; ] ; then
11818 desktop=$1
11819 else
11820 desktop=gnome
11821 fi
11822
11823 from=lenny
11824 to=squeeze
11825
11826 exec &amp;lt; /dev/null
11827 unset LANG
11828 mirror=http://ftp.skolelinux.org/debian
11829 tmpdir=chroot-$from-upgrade-$to-$desktop
11830 fuser -mv .
11831 debootstrap $from $tmpdir $mirror
11832 chroot $tmpdir aptitude update
11833 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
11834 #!/bin/sh
11835 exit 101
11836 EOF
11837 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
11838 exit_cleanup() {
11839 umount $tmpdir/proc
11840 }
11841 mount -t proc proc $tmpdir/proc
11842 # Make sure proc is unmounted also on failure
11843 trap exit_cleanup EXIT INT
11844
11845 chroot $tmpdir aptitude -y install debconf-utils
11846
11847 # Make sure tasksel autoselection trigger. It need the test scripts
11848 # to return the correct answers.
11849 echo tasksel tasksel/desktop multiselect $desktop | \
11850 chroot $tmpdir debconf-set-selections
11851
11852 # Include the desktop and laptop task
11853 for test in desktop laptop ; do
11854 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
11855 #!/bin/sh
11856 exit 2
11857 EOF
11858 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
11859 done
11860
11861 DEBIAN_FRONTEND=noninteractive
11862 DEBIAN_PRIORITY=critical
11863 export DEBIAN_FRONTEND DEBIAN_PRIORITY
11864 chroot $tmpdir tasksel --new-install
11865
11866 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
11867 chroot $tmpdir aptitude update
11868 touch $tmpdir/etc/udev/kernel-upgrade
11869 chroot $tmpdir aptitude -y dist-upgrade
11870 fuser -mv
11871 &lt;/pre&gt;&lt;/blockquote&gt;
11872
11873 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
11874 with aptitude, but I have not had time to look at how they behave
11875 differently so far. I hope to get a cron job running to do the test
11876 regularly and post the result on the web. The Gnome upgrade currently
11877 work, while the KDE upgrade fail because of the bug in
11878 kdebase-workspace-data&lt;/p&gt;
11879
11880 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
11881 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
11882 post, so I will refrain from trying. I can report that for Gnome,
11883 aptitude report 760 packages upgraded, 448 newly installed, 129 to
11884 remove and 1 not upgraded and 1024MB need to be downloaded while for
11885 KDE the same numbers are 702 packages upgraded, 507 newly installed,
11886 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
11887
11888 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
11889 is able to migrate to dependency based boot sequencing and parallel
11890 booting without a hitch. Was unsure if there were still bugs with
11891 packages failing to clean up their obsolete init.d script during
11892 upgrades, and no such problem seem to affect the Gnome desktop+laptop
11893 packages.&lt;/p&gt;
11894 </description>
11895 </item>
11896
11897 <item>
11898 <title>Upstart or sysvinit - as init.d scripts see it</title>
11899 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
11900 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
11901 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
11902 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
11903 scripts to migrate (some of) their operations to upstart job while
11904 keeping the init.d for hurd and kfreebsd. The packages with such
11905 needs will need a way to get their init.d scripts to behave
11906 differently when used with sysvinit and with upstart. Because of
11907 this, I had a look at the environment variables set when a init.d
11908 script is running under upstart, and when it is not.&lt;/p&gt;
11909
11910 &lt;p&gt;With upstart, I notice these environment variables are set when a
11911 script is started from rcS.d/ (ignoring some irrelevant ones like
11912 COLUMNS):&lt;/p&gt;
11913
11914 &lt;blockquote&gt;&lt;pre&gt;
11915 DEFAULT_RUNLEVEL=2
11916 previous=N
11917 PREVLEVEL=
11918 RUNLEVEL=
11919 runlevel=S
11920 UPSTART_EVENTS=startup
11921 UPSTART_INSTANCE=
11922 UPSTART_JOB=rc-sysinit
11923 &lt;/pre&gt;&lt;/blockquote&gt;
11924
11925 &lt;p&gt;With sysvinit, these environment variables are set for the same
11926 script.&lt;/p&gt;
11927
11928 &lt;blockquote&gt;&lt;pre&gt;
11929 INIT_VERSION=sysvinit-2.88
11930 previous=N
11931 PREVLEVEL=N
11932 RUNLEVEL=S
11933 runlevel=S
11934 &lt;/pre&gt;&lt;/blockquote&gt;
11935
11936 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
11937 sysvinit are not set by upstart. Not sure if it is intentional or not
11938 to not be compatible with sysvinit in this regard.&lt;/p&gt;
11939
11940 &lt;p&gt;For scripts needing to behave differently when upstart is used,
11941 looking for the UPSTART_JOB environment variable seem to be a good
11942 choice.&lt;/p&gt;
11943 </description>
11944 </item>
11945
11946 <item>
11947 <title>A manual for standards wars...</title>
11948 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
11949 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
11950 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
11951 <description>&lt;p&gt;Via the
11952 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
11953 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
11954 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
11955 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
11956 following the standards wars of today.&lt;/p&gt;
11957 </description>
11958 </item>
11959
11960 <item>
11961 <title>Sitesummary tip: Listing computer hardware models used at site</title>
11962 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
11963 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
11964 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
11965 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
11966 to get a list of the machine types in use thanks to the DMI
11967 information extracted from each machine. The script to do so is
11968 included in the sitesummary package, and here is example output from
11969 the Skolelinux build servers:&lt;/p&gt;
11970
11971 &lt;blockquote&gt;&lt;pre&gt;
11972 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
11973 vendor count
11974 Dell Computer Corporation 1
11975 PowerEdge 1750 1
11976 IBM 1
11977 eserver xSeries 345 -[8670M1X]- 1
11978 Intel 2
11979 [no-dmi-info] 3
11980 maintainer:~#
11981 &lt;/pre&gt;&lt;/blockquote&gt;
11982
11983 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
11984 provided in each machine. Here there are Intel machines without model
11985 information listed with Intel as vendor and no model, and virtual Xen
11986 machines listed as [no-dmi-info]. One can add -l as a command line
11987 option to list the individual machines.&lt;/p&gt;
11988
11989 &lt;p&gt;A larger list is
11990 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
11991 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
11992 provide the basic sitesummary report publicly. In their report there
11993 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
11994 their machines, and as sitesummary is available in both distributions,
11995 it is trivial to get all of them to report to the same central
11996 collector.&lt;/p&gt;
11997 </description>
11998 </item>
11999
12000 <item>
12001 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
12002 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
12003 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</guid>
12004 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
12005 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
12006 start at boot when an NVidia video card is used is handled. The
12007 problem seem to be that the nvidia X.org driver uses a long time to
12008 initialize, and this duration is longer than kdm is configured to
12009 wait.&lt;/p&gt;
12010
12011 &lt;p&gt;I came across two bugs related to this issue,
12012 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
12013 against initscripts and passed on to nvidia-glx when it became obvious
12014 that the nvidia drivers were involved, and
12015 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
12016 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
12017
12018 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
12019 problem nvidia video card owners experience and make sure the Debian
12020 distribution work out of the box for these users. The nvidia driver
12021 maintainers expect kdm to be set up to wait longer, while kdm expect
12022 the nvidia driver maintainers to fix the driver to start faster, and
12023 while they wait for each other I guess the users end up switching to a
12024 distribution that work for them. I have no idea what the solution is,
12025 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
12026
12027 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
12028 </description>
12029 </item>
12030
12031 <item>
12032 <title>Parallellized boot seem to hold up well in Debian/testing</title>
12033 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
12034 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
12035 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
12036 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
12037 The feature seem to hold up pretty well, but three fairly serious
12038 issues are known and should be solved:
12039
12040 &lt;p&gt;&lt;ul&gt;
12041
12042 &lt;li&gt;The wicd package seen to
12043 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
12044 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
12045 parallel booting is enabled. No idea why, but the wicd maintainer
12046 seem to be on the case.&lt;/li&gt;
12047
12048 &lt;li&gt;The nvidia X driver seem to
12049 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
12050 triggered more easily when parallel booting is in effect. The
12051 maintainer is on the case.&lt;/li&gt;
12052
12053 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
12054 sequencing (the shutdown is broken) when old file-rc users
12055 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
12056 sysv-rc. One way to solve it would be for file-rc to create
12057 /etc/init.d/.legacy-bootordering, and another is to try to make
12058 sysv-rc more robust. Will investigate some more and probably upload a
12059 workaround in sysv-rc to help those trying to move from file-rc to
12060 sysv-rc get a working shutdown.&lt;/li&gt;
12061
12062 &lt;/ul&gt;&lt;/p&gt;
12063
12064 &lt;p&gt;All in all not many surprising issues, and all of them seem
12065 solvable before Squeeze is released. In addition to these there are
12066 some packages with bugs in their dependencies and run level settings,
12067 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
12068
12069 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12070 the BTS, please usertag the report to get it to show up at
12071 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12072 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12073
12074 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
12075 </description>
12076 </item>
12077
12078 <item>
12079 <title>More flexible firmware handling in debian-installer</title>
12080 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
12081 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
12082 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
12083 <description>&lt;p&gt;After a long break from debian-installer development, I finally
12084 found time today to return to the project. Having to spend less time
12085 working dependency based boot in debian, as it is almost complete now,
12086 definitely helped freeing some time.&lt;/p&gt;
12087
12088 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
12089 include some firmware packages on the Debian Edu CDs, those needed to
12090 get disk and network controllers working. Without having these
12091 firmware packages available during installation, it is impossible to
12092 install Debian Edu on the given machine, and because our target group
12093 are non-technical people, asking them to provide firmware packages on
12094 an external medium is a support pain. Initially, I expected it to be
12095 enough to include the firmware packages on the CD to get
12096 debian-installer to find and use them. This proved to be wrong.
12097 Next, I hoped it was enough to symlink the relevant firmware packages
12098 to some useful location on the CD (tried /cdrom/ and
12099 /cdrom/firmware/). This also proved to not work, and at this point I
12100 found time to look at the debian-installer code to figure out what was
12101 going to work.&lt;/p&gt;
12102
12103 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
12104 look revealed that it would only look for firmware packages outside
12105 the installation media, so the CD was never checked for firmware
12106 packages. It would only check USB sticks, floppies and other
12107 &quot;external&quot; media devices. Today I changed it to also look in the
12108 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12109 solve the problem I ran into with Debian edu. I also changed it to
12110 look in /firmware/, to make sure the installer also find firmware
12111 provided in the initrd when booting the installer via PXE, to allow us
12112 to provide the same feature in the PXE setup included in Debian
12113 Edu.&lt;/p&gt;
12114
12115 &lt;p&gt;To make sure firmware deb packages with a license questions are not
12116 activated without asking if the license is accepted, I extended
12117 hw-detect to look for preinst scripts in the firmware packages, and
12118 run these before activating the firmware during installation. The
12119 license question is asked using debconf in the preinst, so this should
12120 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
12121
12122 &lt;p&gt;If you want to discuss the details of these features, please
12123 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
12124 </description>
12125 </item>
12126
12127 <item>
12128 <title>Parallellized boot is now the default in Debian/unstable</title>
12129 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
12130 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
12131 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
12132 <description>&lt;p&gt;Since this evening, parallel booting is the default in
12133 Debian/unstable for machines using dependency based boot sequencing.
12134 Apparently the testing of concurrent booting has been wider than
12135 expected, if I am to believe the
12136 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12137 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
12138 with the feature this weekend, to give us some time to detect any
12139 remaining problems before Squeeze is frozen. If serious problems are
12140 detected, it is simple to change the default back to sequential boot.
12141 The upload of the new sysvinit package also activate a new upstream
12142 version.&lt;/p&gt;
12143
12144 More information about
12145 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12146 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
12147 currently possible to disable parallel booting when one run into
12148 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
12149
12150 &lt;blockquote&gt;&lt;pre&gt;
12151 CONCURRENCY=none
12152 &lt;/pre&gt;&lt;/blockquote&gt;
12153
12154 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12155 the BTS, please usertag the report to get it to show up at
12156 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12157 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12158 </description>
12159 </item>
12160
12161 <item>
12162 <title>Sitesummary tip: Listing MAC address of all clients</title>
12163 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
12164 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
12165 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
12166 <description>&lt;p&gt;In the recent Debian Edu versions, the
12167 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
12168 system&lt;/a&gt; is used to keep track of the machines in the school
12169 network. Each machine will automatically report its status to the
12170 central server after boot and once per night. The network setup is
12171 also reported, and using this information it is possible to get the
12172 MAC address of all network interfaces in the machines. This is useful
12173 to update the DHCP configuration.&lt;/p&gt;
12174
12175 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
12176 ist all MAC addresses of all machines reporting to sitesummary. Run
12177 this on the collector host:&lt;/p&gt;
12178
12179 &lt;blockquote&gt;&lt;pre&gt;
12180 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
12181 &lt;/pre&gt;&lt;/blockquote&gt;
12182
12183 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
12184 line per machine and with space between the MAC addresses.&lt;/p&gt;
12185
12186 &lt;p&gt;To allow system administrators easier job at adding static DHCP
12187 addresses for hosts, it would be possible to extend this to fetch
12188 machine information from sitesummary and update the DHCP and DNS
12189 tables in LDAP using this information. Such tool is unfortunately not
12190 written yet.&lt;/p&gt;
12191 </description>
12192 </item>
12193
12194 <item>
12195 <title>systemd, an interesting alternative to upstart</title>
12196 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
12197 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
12198 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
12199 <description>&lt;p&gt;The last few days a new boot system called
12200 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
12201 has been
12202 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
12203
12204 to the free software world. I have not yet had time to play around
12205 with it, but it seem to be a very interesting alternative to
12206 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
12207 a good alternative for Debian when we are able to switch to an event
12208 based boot system. Tollef is
12209 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
12210 systemd into Debian, and I look forward to seeing how well it work. I
12211 like the fact that systemd handles init.d scripts with dependency
12212 information natively, allowing them to run in parallel where upstart
12213 at the moment do not.&lt;/p&gt;
12214
12215 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
12216 platform support. It only work on recent Linux kernels, and also need
12217 some new kernel features enabled to function properly. This means
12218 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12219 system. Not sure how that will be handled if systemd proves to be the
12220 way forward.&lt;/p&gt;
12221
12222 &lt;p&gt;In the mean time, based on the
12223 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12224 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
12225 decided to enable full parallel booting as the default in Debian as
12226 soon as possible (probably this weekend or early next week), to see if
12227 there are any remaining serious bugs in the init.d dependencies. A
12228 new version of the sysvinit package implementing this change is
12229 already in experimental. If all go well, Squeeze will be released
12230 with parallel booting enabled by default.&lt;/p&gt;
12231 </description>
12232 </item>
12233
12234 <item>
12235 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
12236 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
12237 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
12238 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
12239 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
12240 complete, so complete that it is actually possible to run all the
12241 init.d scripts in parallell based on these dependencies. If you want
12242 to test your Squeeze system, make sure
12243 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12244 based boot sequencing&lt;/a&gt; is enabled, and add this line to
12245 /etc/default/rcS:&lt;/p&gt;
12246
12247 &lt;blockquote&gt;&lt;pre&gt;
12248 CONCURRENCY=makefile
12249 &lt;/pre&gt;&lt;/blockquote&gt;
12250
12251 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
12252 scripts in parallel using the dependency information stored in
12253 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
12254 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
12255 to try to start the kdm and gdm scripts as early as possible, and will
12256 start the facilities required by kdm or gdm as early as possible to
12257 make this happen.&lt;/p&gt;
12258
12259 &lt;p&gt;Give it a try, and see if you like the result. If some services
12260 fail to start properly, it is most likely because they have incomplete
12261 init.d script dependencies in their startup script (or some of their
12262 dependent scripts have incomplete dependencies). Report bugs and get
12263 the package maintainers to fix it. :)&lt;/p&gt;
12264
12265 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
12266 manage to get the init.d script dependencies complete and correct. I
12267 expect we will get there in Squeeze+1, if we get manage to test and
12268 fix the remaining issues.&lt;/p&gt;
12269
12270 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12271 the BTS, please usertag the report to get it to show up at
12272 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12273 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12274 </description>
12275 </item>
12276
12277 <item>
12278 <title>Debian has switched to dependency based boot sequencing</title>
12279 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
12280 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
12281 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
12282 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
12283 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
12284 have been migrated to using dependency based boot sequencing. This
12285 conclude work me and others have been doing for the last three days.
12286 It feels great to see this finally part of the default Debian
12287 installation. Now we just need to weed out the last few problems that
12288 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
12289
12290 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
12291 fixing the more fundamental problem of handing the event based
12292 non-predictable kernel in the early boot.&lt;/p&gt;
12293 </description>
12294 </item>
12295
12296 <item>
12297 <title>Taking over sysvinit development</title>
12298 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
12299 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
12300 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
12301 <description>&lt;p&gt;After several years of frustration with the lack of activity from
12302 the existing sysvinit upstream developer, I decided a few weeks ago to
12303 take over the package and become the new upstream. The number of
12304 patches to track for the Debian package was becoming a burden, and the
12305 lack of synchronization between the distribution made it hard to keep
12306 the package up to date.&lt;/p&gt;
12307
12308 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
12309 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
12310 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
12311 and Fedora), based on the patches currently in use in these
12312 distributions. We Debian maintainers plan to move to this tarball as
12313 the new upstream as soon as we find time to do the merge. Since the
12314 new tarball was created, we agreed with Werner at SuSe to make a new
12315 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
12316 development there. The project is registered and currently waiting
12317 for approval by the Savannah administrators, and as soon as it is
12318 approved, we will import the old versions from svn and continue
12319 working on the future release.&lt;/p&gt;
12320
12321 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
12322 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
12323 </description>
12324 </item>
12325
12326 <item>
12327 <title>Debian boots quicker and quicker</title>
12328 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
12329 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
12330 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
12331 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
12332 people involved in the boot system on Debian and Ubuntu, to see if we
12333 could find more ways to speed up the boot system. This was an Ubuntu
12334 funded
12335 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
12336 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
12337 of boot systems, and ways to handle the increasing number of boot
12338 issues introduced by the Linux kernel becoming more and more
12339 asynchronous and event base. The Ubuntu approach using udev and
12340 upstart might be a good way forward. Time will show.&lt;/p&gt;
12341
12342 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
12343 process in Debian. All of these should be applied to get a quick
12344 boot:&lt;/p&gt;
12345
12346 &lt;ul&gt;
12347
12348 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
12349
12350 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
12351 clock is in UTC.&lt;/li&gt;
12352
12353 &lt;li&gt;Install and activate the insserv package to enable
12354 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12355 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
12356
12357 &lt;/ul&gt;
12358
12359 These points are based on the Google summer of code work done by
12360 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
12361 Villegas&lt;/a&gt;.
12362
12363 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
12364 unstable yesterday. When we tested it, we were able to cut 6 seconds
12365 from the boot sequence. It depend on very correct dependency
12366 declaration in all init.d scripts, so I expect us to find edge cases
12367 where the dependences in some scripts are slightly wrong when we start
12368 using this.&lt;/p&gt;
12369
12370 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
12371 introduced by Raphael Geissert today, one that could affect the
12372 startup speed as well. Instead of starting some scripts concurrently
12373 from rcS.d/ and another set of scripts from rc2.d/, it would be
12374 possible to run a of them in the same process. A quick way to test
12375 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
12376 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
12377 </description>
12378 </item>
12379
12380 <item>
12381 <title>BSAs påstander om piratkopiering møter motstand</title>
12382 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
12383 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
12384 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
12385 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
12386 programvareselskapene som Microsoft og Apple, publisert en rapport der
12387 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
12388 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
12389 dager siden kom
12390 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
12391 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
12392 dagene. Et spesielt interessant kommentar fra Sverige,
12393 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
12394 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
12395
12396 &lt;blockquote&gt;
12397 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
12398 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
12399 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
12400 exakta&quot;, säger BSAs Sverigechef John Hugosson.
12401 &lt;/blockquote&gt;
12402
12403 &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
12404 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
12405 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
12406 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
12407 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
12408
12409 &lt;p&gt;Fant lenkene via &lt;a
12410 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
12411 på Slashdot&lt;/a&gt;.&lt;/p&gt;
12412 </description>
12413 </item>
12414
12415 <item>
12416 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
12417 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
12418 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
12419 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
12420 <description>&lt;p&gt;Kom over
12421 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
12422 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
12423 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
12424 jobber til daglig. En rask opptelling forteller meg at vi har 490
12425 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
12426 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
12427 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
12428 </description>
12429 </item>
12430
12431 <item>
12432 <title>Kryptert harddisk - naturligvis</title>
12433 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
12434 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
12435 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
12436 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
12437 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
12438 når en tar tap av arbeidstid, fortrolige dokumenter,
12439 personopplysninger og alt annet det innebærer. Det er ingen tvil om
12440 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
12441 til at jeg har kryptert harddisken på både kontormaskinen og min
12442 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
12443 komme på avveie, den første informasjon relatert til jobben min ved
12444 Universitetet i Oslo, og den andre relatert til blant annet
12445 foreningsarbeide. Kryptering av diskene gjør at det er lite
12446 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
12447 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
12448 og en reboot vil gjøre at de ber om passord før de vil starte opp.
12449 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
12450 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
12451 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
12452 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
12453 det er gjort slik jeg gjør det er minimale, og gevinstene er
12454 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
12455 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
12456
12457 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
12458 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
12459 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
12460 er for min del høyere enn gevinsten. Jeg tror oddsene for at
12461 f.eks. etteretningsorganisasjoner har glede av å titte på mine
12462 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
12463 gjøre det vanskeligere for angripere med kompetanse og ressurser er
12464 betydelige.&lt;/p&gt;
12465 </description>
12466 </item>
12467
12468 <item>
12469 <title>Two projects that have improved the quality of free software a lot</title>
12470 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
12471 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
12472 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
12473 <description>&lt;p&gt;There are two software projects that have had huge influence on the
12474 quality of free software, and I wanted to mention both in case someone
12475 do not yet know them.&lt;/p&gt;
12476
12477 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
12478 tool to detect and expose errors in the memory handling of programs.
12479 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
12480 and it will report any problems on stdout. It is even better if the
12481 program include debug information. With debug information, it is able
12482 to report the source file name and line number where the problem
12483 occurs. It can report things like &#39;reading past memory block in file
12484 X line N, the memory block was allocated in file Y, line M&#39;, and
12485 &#39;using uninitialised value in control logic&#39;. This tool has made it
12486 trivial to investigate reproducible crash bugs in programs, and have
12487 reduced the number of this kind of bugs in free software a lot.
12488
12489 &lt;p&gt;The second one is
12490 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
12491 a source code checker. It is able to process the source of a program
12492 and find problems in the logic without running the program. It
12493 started out as the Stanford Checker and became well known when it was
12494 used to find bugs in the Linux kernel. It is now a commercial tool
12495 and the company behind it is running
12496 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
12497 free software community, where a lot of free software projects get
12498 their source checked for free. Several thousand defects have been
12499 found and fixed so far. It can find errors like &#39;lock L taken in file
12500 X line N is never released if exiting in line M&#39;, or &#39;the code in file
12501 Y lines O to P can never be executed&#39;. The projects included in the
12502 community service project have managed to get rid of a lot of
12503 reliability problems thanks to Coverity.&lt;/p&gt;
12504
12505 &lt;p&gt;I believe tools like this, that are able to automatically find
12506 errors in the source, are vital to improve the quality of software and
12507 make sure we can get rid of the crashing and failing software we are
12508 surrounded by today.&lt;/p&gt;
12509 </description>
12510 </item>
12511
12512 <item>
12513 <title>No patch is not better than a useless patch</title>
12514 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
12515 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
12516 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
12517 <description>&lt;p&gt;Julien Blache
12518 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
12519 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
12520 patch allow one to discuss a concrete and proposed solution, and also
12521 prove that the issue at hand is important enough for someone to spent
12522 time on fixing it. No patch do not provide any of these positive
12523 properties.&lt;/p&gt;
12524 </description>
12525 </item>
12526
12527 <item>
12528 <title>Standardize on protocols and formats, not vendors and applications</title>
12529 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
12530 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
12531 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
12532 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
12533 very good one to form a long lived computer infrastructure. It is the
12534 simple one, lost by many in todays computer industry: Standardize on
12535 open network protocols and open exchange/storage formats, not applications.
12536 Applications come and go, while protocols and files tend to stay, and
12537 thus one want to make it easy to change application and vendor, while
12538 avoiding conversion costs and locking users to a specific platform or
12539 application.&lt;/p&gt;
12540
12541 &lt;p&gt;This approach make it possible to replace the client applications
12542 independently of the server applications. One can even allow users to
12543 use several different applications as long as they handle the selected
12544 protocol and format. In the normal case, only one client application
12545 is recommended and users only get help if they choose to use this
12546 application, but those that want to deviate from the easy path are not
12547 blocked from doing so.&lt;/p&gt;
12548
12549 &lt;p&gt;It also allow us to replace the server side without forcing the
12550 users to replace their applications, and thus allow us to select the
12551 best server implementation at any moment, when scale and resouce
12552 requirements change.&lt;/p&gt;
12553
12554 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
12555 open formats, but I would never recommend standardizing on a single
12556 application that do not use open network protocol or open formats.&lt;/p&gt;
12557 </description>
12558 </item>
12559
12560 <item>
12561 <title>Returning from Skolelinux developer gathering</title>
12562 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
12563 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
12564 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
12565 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
12566 Edu/Skolelinux development gathering. I got a bit done tuning the
12567 desktop, and looked into the dynamic service location protocol
12568 implementation avahi. It look like it could be useful for us. Almost
12569 30 people participated, and I believe it was a great environment to
12570 get to know the Skolelinux system. Walter Bender, involved in the
12571 development of the Sugar educational platform, presented his stuff and
12572 also helped me improve my OLPC installation. He also showed me that
12573 his Turtle Art application can be used in standalone mode, and we
12574 agreed that I would help getting it packaged for Debian. As a
12575 standalone application it would be great for Debian Edu. We also
12576 tried to get the video conferencing working with two OLPCs, but that
12577 proved to be too hard for us. The application seem to need more work
12578 before it is ready for me. I look forward to getting home and relax
12579 now. :)&lt;/p&gt;
12580 </description>
12581 </item>
12582
12583 <item>
12584 <title>Time for new LDAP schemas replacing RFC 2307?</title>
12585 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
12586 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
12587 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
12588 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
12589 optimal. There is RFC 2307 documenting one way to store NIS maps in
12590 LDAP, and a modified version of this normally called RFC 2307bis, with
12591 some modifications to be compatible with Active Directory. The RFC
12592 specification handle the content of a lot of system databases, but do
12593 not handle DNS zones and DHCP configuration.&lt;/p&gt;
12594
12595 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
12596 we would like to store information about users, SMB clients/hosts,
12597 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
12598 and LTSP configuration in LDAP. These objects have a lot in common,
12599 but with the current LDAP schemas it is not possible to have one
12600 object per entity. For example, one need to have at least three LDAP
12601 objects for a given computer, one with the SMB related stuff, one with
12602 DNS information and another with DHCP information. The schemas
12603 provided for DNS and DHCP are impossible to combine into one LDAP
12604 object. In addition, it is impossible to implement quick queries for
12605 netgroup membership, because of the way NIS triples are implemented.
12606 It just do not scale. I believe it is time for a few RFC
12607 specifications to cleam up this mess.&lt;/p&gt;
12608
12609 &lt;p&gt;I would like to have one LDAP object representing each computer in
12610 the network, and this object can then keep the SMB (ie host key), DHCP
12611 (mac address/name) and DNS (name/IP address) settings in one place.
12612 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
12613
12614 &lt;p&gt;I would also like to have a quick way to map from a user or
12615 computer and to the net group this user or computer is a member.&lt;/p&gt;
12616
12617 &lt;p&gt;Active Directory have done a better job than unix heads like myself
12618 in this regard, and the unix side need to catch up. Time to start a
12619 new IETF work group?&lt;/p&gt;
12620 </description>
12621 </item>
12622
12623 <item>
12624 <title>Endelig er Debian Lenny gitt ut</title>
12625 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
12626 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
12627 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
12628 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
12629 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
12630 Et langt steg videre for Debian-prosjektet, og en rekke nye
12631 programpakker blir nå tilgjengelig for de av oss som bruker den
12632 stabile utgaven av Debian. Neste steg er nå å få
12633 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
12634 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
12635 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
12636 slippes løs på skolene. Takk til alle debian-utviklerne som har
12637 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
12638 bootsekvens tilgjengelig i stabil utgave, vha pakken
12639 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
12640 </description>
12641 </item>
12642
12643 <item>
12644 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
12645 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
12646 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
12647 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
12648 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
12649 Oslo. Most of Saturday was used for the general assemly for the
12650 member organization, but the rest of the weekend I used to tune the
12651 LTSP installation. LTSP now work out of the box on the 10-network.
12652 Acer Aspire One proved to be a very nice thin client, with both
12653 screen, mouse and keybard in a small box. Was working on getting the
12654 diskless workstation setup configured out of the box, but did not
12655 finish it before the weekend was up.&lt;/p&gt;
12656
12657 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
12658 the Brazilian group, so that will have to wait for the next
12659 development gathering. Would love to have the Debian Edu installer
12660 automatically detect and configure a multiseat setup when it find one
12661 of these cards.&lt;/p&gt;
12662 </description>
12663 </item>
12664
12665 <item>
12666 <title>The sorry state of multimedia browser plugins in Debian</title>
12667 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
12668 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
12669 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
12670 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
12671 plugins available in Debian Lenny, to see which one we should use by
12672 default in Debian Edu. We need an embedded video playing plugin with
12673 control buttons to pause or stop the video, and capable of streaming
12674 all the multimedia content available on the web. The test results and
12675 notes are available on
12676 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
12677 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
12678 fill this need. My personal video player favorite, VLC, has a really
12679 bad plugin which fail on a lot of the test pages. A lot of the MIME
12680 types I would expect to work with any free software player (like
12681 video/ogg), just do not work. And simple formats like the
12682 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
12683 totem and vlc plugins. I hope the situation will improve soon. No
12684 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
12685
12686 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
12687 be the only one fitting our needs. :/&lt;/p&gt;
12688 </description>
12689 </item>
12690
12691 </channel>
12692 </rss>