]> pere.pagekite.me Git - homepage.git/blob - blog/tags/debian/debian.rss
4394968cd3c6d35823f8fa5807e9a67641f6ece2
[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>Time to translate the Bullseye edition of the Debian Administrator&#39;s Handbook</title>
11 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</link>
12 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html</guid>
13 <pubDate>Mon, 12 Sep 2022 15:45:00 +0200</pubDate>
14 <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;
15
16 &lt;p&gt;(The picture is of the previous edition.)&lt;/p&gt;
17
18 &lt;p&gt;Almost two years after the previous Norwegian Bokmål translation of
19 the &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
20 Handbook&lt;/a&gt;&quot; was published, a new edition is finally being prepared. The
21 english text is updated, and it is time to start working on the
22 translations. Around 37 percent of the strings have been updated, one
23 way or another, and the translations starting from a complete Debian Buster
24 edition now need to bring their translation up from 63% to 100%. The
25 complete book is licensed using a Creative Commons license, and has
26 been published in several languages over the years. The translations
27 are done by volunteers to bring Linux in their native tongue. The
28 last time I checked, it complete text was available in English,
29 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
30 In addition, work has been started for Arabic (Morocco), Catalan,
31 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
32 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
33 Romanian, Russian, Swedish, Turkish and Vietnamese.&lt;/p&gt;
34
35 &lt;p&gt;The translation is conducted on
36 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
37 hosted weblate project page&lt;/a&gt;. Prospective translators are
38 recommeded to subscribe to
39 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
40 translators mailing list&lt;/a&gt; and should also check out
41 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
42 contributors&lt;/a&gt;.&lt;/p&gt;
43
44 &lt;p&gt;I am one of the Norwegian Bokmål translators of this book, and we
45 have just started. Your contribution is most welcome.&lt;/p&gt;
46
47 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
48 activities, please send Bitcoin donations to my address
49 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
50 </description>
51 </item>
52
53 <item>
54 <title>Automatic LinuxCNC servo PID tuning?</title>
55 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</link>
56 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html</guid>
57 <pubDate>Sat, 16 Jul 2022 22:30:00 +0200</pubDate>
58 <description>&lt;p&gt;While working on a CNC with servo motors controlled by the
59 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;
60 &lt;a href=&quot;https://en.wikipedia.org/wiki/PID_controller&quot;&gt;PID
61 controller&lt;/a&gt;, I recently had to learn how to tune the collection of values
62 that control such mathematical machinery that a PID controller is. It
63 proved to be a lot harder than I hoped, and I still have not succeeded
64 in getting the Z PID controller to successfully defy gravity, nor X
65 and Y to move accurately and reliably. But while climbing up this
66 rather steep learning curve, I discovered that some motor control
67 systems are able to tune their PID controllers. I got the impression
68 from the documentation that LinuxCNC were not. This proved to be not
69 true&lt;/p&gt;
70
71 &lt;p&gt;The LinuxCNC
72 &lt;a href=&quot;http://linuxcnc.org/docs/html/man/man9/pid.9.html&quot;&gt;pid
73 component&lt;/a&gt; is the recommended PID controller to use. It uses eight
74 constants &lt;tt&gt;Pgain&lt;/tt&gt;, &lt;tt&gt;Igain&lt;/tt&gt;, &lt;tt&gt;Dgain&lt;/tt&gt;,
75 &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
76 &lt;tt&gt;FF3&lt;/tt&gt; to calculate the output value based on current and wanted
77 state, and all of these need to have a sensible value for the
78 controller to behave properly. Note, there are even more values
79 involved, theser are just the most important ones. In my case I need
80 the X, Y and Z axes to follow the requested path with little error.
81 This has proved quite a challenge for someone who have never tuned a
82 PID controller before, but there is at least some help to be found.
83
84 &lt;p&gt;I discovered that included in LinuxCNC was this old PID component
85 at_pid claiming to have auto tuning capabilities. Sadly it had been
86 neglected since 2011, and could not be used as a plug in replacement
87 for the default pid component. One would have to rewriting the
88 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
89 to quickly test auto tuning to see if it did a better job than me at
90 figuring out good P, I and D values to use.&lt;/p&gt;
91
92 &lt;p&gt;I decided to have a look if the situation could be improved. This
93 involved trying to understand the code and history of the pid and
94 at_pid components. Apparently they had a common ancestor, as code
95 structure, comments and variable names were quite close to each other.
96 Sadly this was not reflected in the git history, making it hard to
97 figure out what really happened. My guess is that the author of
98 &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;
99 took a version of
100 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c&quot;&gt;pid.c&lt;/a&gt;,
101 rewrote it to follow the structure he wished pid.c to have, then added
102 support for auto tuning and finally got it included into the LinuxCNC
103 repository. The restructuring and lack of early history made it
104 harder to figure out which part of the code were relevant to the auto
105 tuning, and which part of the code needed to be updated to work the
106 same way as the current pid.c implementation. I started by trying to
107 isolate relevant changes in pid.c, and applying them to at_pid.c. My
108 aim was to make sure the at_pid component could replace the pid
109 component with a simple change in the HAL setup loadrt line, without
110 having to &quot;rewire&quot; the rest of the HAL configuration. After a few
111 hours following this approach, I had learned quite a lot about the
112 code structure of both components, while concluding I was heading down
113 the wrong rabbit hole, and should get back to the surface and find a
114 different path.&lt;/p&gt;
115
116 &lt;p&gt;For the second attempt, I decided to throw away all the PID control
117 related part of the original at_pid.c, and instead isolate and lift
118 the auto tuning part of the code and inject it into a copy of pid.c.
119 This ensured compatibility with the current pid component, while
120 adding auto tuning as a run time option. To make it easier to identify
121 the relevant parts in the future, I wrapped all the auto tuning code
122 with &#39;#ifdef AUTO_TUNER&#39;. The end result behave just like the current
123 pid component by default, as that part of the code is identical. The
124 &lt;a href=&quot;https://github.com/LinuxCNC/linuxcnc/pull/1820&quot;&gt;end result
125 entered the LinuxCNC master branch&lt;/a&gt; a few days ago.&lt;/p&gt;
126
127 &lt;p&gt;To enable auto tuning, one need to set a few HAL pins in the PID
128 component. The most important ones are &lt;tt&gt;tune-effort&lt;/tt&gt;,
129 &lt;tt&gt;tune-mode&lt;/tt&gt; and &lt;tt&gt;tune-start&lt;/tt&gt;. But lets take a step
130 back, and see what the auto tuning code will do. I do not know the
131 mathematical foundation of the at_pid algorithm, but from observation
132 I can tell that the algorithm will, when enabled, produce a square
133 wave pattern centered around the &lt;tt&gt;bias&lt;/tt&gt; value on the output pin
134 of the PID controller. This can be seen using the HAL Scope provided
135 by LinuxCNC. In my case, this is translated into voltage (+-10V) sent
136 to the motor controller, which in turn is translated into motor speed.
137 So at_pid will ask the motor to move the axis back and forth. The
138 number of cycles in the pattern is controlled by the
139 &lt;tt&gt;tune-cycles&lt;/tt&gt; pin, and the extremes of the wave pattern is
140 controlled by the &lt;tt&gt;tune-effort&lt;/tt&gt; pin. Of course, trying to
141 change the direction of a physical object instantly (as in going
142 directly from a positive voltage to the equivalent negative voltage)
143 do not change velocity instantly, and it take some time for the object
144 to slow down and move in the opposite direction. This result in a
145 more smooth movement wave form, as the axis in question were vibrating
146 back and forth. When the axis reached the target speed in the
147 opposing direction, the auto tuner change direction again. After
148 several of these changes, the average time delay between the &#39;peaks&#39;
149 and &#39;valleys&#39; of this movement graph is then used to calculate
150 proposed values for Pgain, Igain and Dgain, and insert them into the
151 HAL model to use by the pid controller. The auto tuned settings are
152 not great, but htye work a lot better than the values I had been able
153 to cook up on my own, at least for the horizontal X and Y axis. But I
154 had to use very small &lt;tt&gt;tune-effort&lt;tt&gt; values, as my motor
155 controllers error out if the voltage change too quickly. I&#39;ve been
156 less lucky with the Z axis, which is moving a heavy object up and
157 down, and seem to confuse the algorithm. The Z axis movement became a
158 lot better when I introduced a &lt;tt&gt;bias&lt;/tt&gt; value to counter the
159 gravitational drag, but I will have to work a lot more on the Z axis
160 PID values.&lt;/p&gt;
161
162 &lt;p&gt;Armed with this knowledge, it is time to look at how to do the
163 tuning. Lets say the HAL configuration in question load the PID
164 component for X, Y and Z like this:&lt;/p&gt;
165
166 &lt;blockquote&gt;&lt;pre&gt;
167 loadrt pid names=pid.x,pid.y,pid.z
168 &lt;/pre&gt;&lt;/blockquote&gt;
169
170 &lt;p&gt;Armed with the new and improved at_pid component, the new line will
171 look like this:&lt;/p&gt;
172
173 &lt;blockquote&gt;&lt;pre&gt;
174 loadrt at_pid names=pid.x,pid.y,pid.z
175 &lt;/pre&gt;&lt;/blockquote&gt;
176
177 &lt;p&gt;The rest of the HAL setup can stay the same. This work because the
178 components are referenced by name. If the component had used count=3
179 instead, all use of pid.# had to be changed to at_pid.#.&lt;/p&gt;
180
181 &lt;p&gt;To start tuning the X axis, move the axis to the middle of its
182 range, to make sure it do not hit anything when it start moving back
183 and forth. Next, set the &lt;tt&gt;tune-effort&lt;/tt&gt; to a low number in the
184 output range. I used 0.1 as my initial value. Next, assign 1 to the
185 &lt;tt&gt;tune-mode&lt;/tt&gt; value. Note, this will disable the pid controlling
186 part and feed 0 to the output pin, which in my case initially caused a
187 lot of drift. In my case it proved to be a good idea with X and Y to
188 tune the motor driver to make sure 0 voltage stopped the motor
189 rotation. On the other hand, for the Z axis this proved to be a bad
190 idea, so it will depend on your setup. It might help to set the
191 &lt;tt&gt;bias&lt;/tt&gt; value to a output value that reduce or eliminate the
192 axis drift. Finally, after setting &lt;tt&gt;tune-mode&lt;/tt&gt;, set
193 &lt;tt&gt;tune-start&lt;/tt&gt; to 1 to activate the auto tuning. If all go well,
194 your axis will vibrate for a few seconds and when it is done, new
195 values for Pgain, Igain and Dgain will be active. To test them,
196 change &lt;tt&gt;tune-mode&lt;/tt&gt; back to 0. Note that this might cause the
197 machine to suddenly jerk as it bring the axis back to its commanded
198 position, which it might have drifted away from during tuning. To
199 summarize with some halcmd lines:&lt;/p&gt;
200
201 &lt;blockquote&gt;&lt;pre&gt;
202 setp pid.x.tune-effort 0.1
203 setp pid.x.tune-mode 1
204 setp pid.x.tune-start 1
205 # wait for the tuning to complete
206 setp pid.x.tune-mode 0
207 &lt;/pre&gt;&lt;/blockquote&gt;
208
209 &lt;p&gt;After doing this task quite a few times while trying to figure out
210 how to properly tune the PID controllers on the machine in, I decided
211 to figure out if this process could be automated, and wrote a script
212 to do the entire tuning process from power on. The end result will
213 ensure the machine is powered on and ready to run, home all axis if it
214 is not already done, check that the extra tuning pins are available,
215 move the axis to its mid point, run the auto tuning and re-enable the
216 pid controller when it is done. It can be run several times. Check
217 out the
218 &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;
219 script on github if you want to learn how it is done.&lt;/p&gt;
220
221 &lt;p&gt;My hope is that this little adventure can inspire someone who know
222 more about motor PID controller tuning can implement even better
223 algorithms for automatic PID tuning in LinuxCNC, making life easier
224 for both me and all the others that want to use LinuxCNC but lack the
225 in depth knowledge needed to tune PID controllers well.&lt;/p&gt;
226
227 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
228 activities, please send Bitcoin donations to my address
229 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
230 </description>
231 </item>
232
233 <item>
234 <title>LinuxCNC translators life just got a bit easier</title>
235 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</link>
236 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html</guid>
237 <pubDate>Fri, 3 Jun 2022 21:10:00 +0200</pubDate>
238 <description>&lt;p&gt;Back in oktober last year, when I started looking at the
239 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt; system, I
240 proposed to change the documentation build system make life easier for
241 translators. The original system consisted of independently written
242 documentation files for each language, with no automated way to track
243 changes done in other translations and no help for the translators to
244 know how much was left to translated. By using
245 &lt;a href=&quot;https://po4a.org/&quot;&gt;the po4a system&lt;/a&gt; to generate POT and PO
246 files from the English documentation, this can be improved. A small
247 team of LinuxCNC contributors got together and today our labour
248 finally payed off. Since a few hours ago, it is now possible to
249 translate &lt;a href=&quot;https://hosted.weblate.org/projects/linuxcnc/&quot;&gt;the
250 LinuxCNC documentation on Weblate&lt;/a&gt;, alongside the program itself.&lt;/p&gt;
251
252 &lt;p&gt;The effort to migrate the documentation to use po4a has been both
253 slow and frustrating. I am very happy we finally made it.&lt;/p&gt;
254
255 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
256 activities, please send Bitcoin donations to my address
257 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
258 </description>
259 </item>
260
261 <item>
262 <title>geteltorito make CD firmware upgrades a breeze</title>
263 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</link>
264 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html</guid>
265 <pubDate>Wed, 20 Apr 2022 11:50:00 +0200</pubDate>
266 <description>&lt;p&gt;Recently I wanted to upgrade the firmware of my thinkpad, and
267 located the firmware download page from Lenovo (which annoyingly do
268 not allow access via Tor, forcing me to hand them more personal
269 information that I would like). The
270 &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
271 from Lenovo&lt;/a&gt; is a bootable ISO image, which is a bit of a problem
272 when all I got available is a USB memory stick. I tried booting the
273 ISO as a USB stick, but this did not work. But genisoimage came to
274 the rescue.&lt;/p&gt;
275
276 &lt;P&gt;The geteltorito program in
277 &lt;a href=&quot;http://tracker.debian.org/cdrkit&quot;&gt;the genisoimage binary
278 package&lt;/a&gt; is able to convert the bootable ISO image to a bootable
279 USB stick using a simple command line recipe, which I then can write
280 to the most recently inserted USB stick:&lt;/p&gt;
281
282 &lt;blockquote&gt;&lt;pre&gt;
283 geteltorito -o usbstick.img lenovo-firmware.iso
284 sudo dd bs=10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -1)
285 &lt;/pre&gt;&lt;/blockquote&gt;
286
287 &lt;p&gt;This USB stick booted the firmware upgrader just fine, and in a few
288 minutes my machine had the latest and greatest BIOS firmware in place.&lt;/p&gt;
289 </description>
290 </item>
291
292 <item>
293 <title>Run your industrial metal working machine using Debian?</title>
294 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</link>
295 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html</guid>
296 <pubDate>Wed, 2 Mar 2022 18:40:00 +0100</pubDate>
297 <description>&lt;p&gt;After many months of hard work by the good people involved in
298 &lt;a href=&quot;https://en.wikipedia.org/wiki/LinuxCNC&quot;&gt;LinuxCNC&lt;/a&gt;, the
299 system was accepted Sunday
300 &lt;a href=&quot;https://tracker.debian.org/pkg/linuxcnc&quot;&gt;into Debian&lt;/a&gt;.
301 Once it was available from Debian, I was surprised to discover from
302 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=linuxcnc&quot;&gt;its
303 popularity-contest numbers&lt;/a&gt; that people have been reporting its use
304 since 2012. &lt;a href=&quot;http://linuxcnc.org/&quot;&gt;Its project site&lt;/a&gt; might
305 be a good place to check out, but sadly is not working when visiting
306 via Tor.&lt;/p&gt;
307
308 &lt;p&gt;But what is LinuxCNC, you are probably wondering? Perhaps a
309 Wikipedia quote is in place?&lt;/p&gt;
310
311 &lt;blockquote&gt;
312 &quot;LinuxCNC is a software system for numerical control of
313 machines such as milling machines, lathes, plasma cutters, routers,
314 cutting machines, robots and hexapods. It can control up to 9 axes or
315 joints of a CNC machine using G-code (RS-274NGC) as input. It has
316 several GUIs suited to specific kinds of usage (touch screen,
317 interactive development).&quot;
318 &lt;/blockquote&gt;
319
320 &lt;p&gt;It can even control 3D printers. And even though the Wikipedia
321 page indicate that it can only work with hard real time kernel
322 features, it can also work with the user space soft real time features
323 provided by the Debian kernel.
324 &lt;a href=&quot;https://github.com/linuxcnc/linuxcnc&quot;&gt;The source code&lt;/a&gt; is
325 available from Github. The last few months I&#39;ve been involved in the
326 translation setup for the program and documentation. Translators are
327 most welcome to
328 &lt;a href=&quot;https://hosted.weblate.org/engage/linuxcnc/&quot;&gt;join the
329 effort&lt;/a&gt; using Weblate.&lt;/p&gt;
330
331 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
332 activities, please send Bitcoin donations to my address
333 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
334 </description>
335 </item>
336
337 <item>
338 <title>Debian still an excellent choice for Lego builders</title>
339 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</link>
340 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html</guid>
341 <pubDate>Sun, 24 Oct 2021 07:10:00 +0200</pubDate>
342 <description>&lt;p&gt;The Debian Lego team saw a lot of activity the last few weeks. All
343 the packages under the team umbrella has been updated to fix
344 packaging, lintian issues and BTS reports. In addition, a new and
345 inspiring team member appeared on both the
346 &lt;a href=&quot;https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team&quot;&gt;debian-lego-team
347 Team mailing list&lt;/a&gt; and
348 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC channel
349 #debian-lego&lt;/a&gt;. If you are interested in Lego CAD design and LEGO
350 Mindstorms programming, check out the
351 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;team wiki page&lt;/a&gt; to
352 see what Debian can offer the Lego enthusiast.&lt;/p&gt;
353
354 &lt;p&gt;Patches has been sent upstream, causing new upstream releases, one
355 even the first one in more than ten years, and old upstreams was
356 released with new ones. There are still a lot of work left, and the
357 team welcome more members to help us make sure Debian is the Linux
358 distribution of choice for Lego builders. If you want to contribute,
359 join us in the IRC channel and become part of
360 &lt;a href=&quot;https://salsa.debian.org/debian-lego-team/&quot;&gt;the team on
361 Salsa&lt;/a&gt;.&lt;/p&gt;
362
363 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
364 activities, please send Bitcoin donations to my address
365 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
366 </description>
367 </item>
368
369 <item>
370 <title>Six complete translations of The Debian Administrator&#39;s Handbook for Buster</title>
371 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</link>
372 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html</guid>
373 <pubDate>Mon, 5 Jul 2021 19:20:00 +0200</pubDate>
374 <description>&lt;p&gt;I am happy observe that the &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The
375 Debian Administrator&#39;s Handbook&lt;/a&gt; is available in six languages now.
376 I am not sure which one of these are completely proof read, but the
377 complete book is available in these languages:
378
379 &lt;ul&gt;
380
381 &lt;li&gt;English&lt;/li&gt;
382 &lt;li&gt;Norwegian Bokmål&lt;/li&gt;
383 &lt;li&gt;German&lt;/li&gt;
384 &lt;li&gt;Indonesian&lt;/li&gt;
385 &lt;li&gt;Brazil Portuguese&lt;/li&gt;
386 &lt;li&gt;Spanish&lt;/li&gt;
387
388 &lt;/ul&gt;
389
390 &lt;p&gt;This is the list of languages more than 70% complete, in other
391 words with not too much left to do:&lt;/p&gt;
392
393 &lt;ul&gt;
394
395 &lt;li&gt;Chinese (Simplified) - 90%&lt;/li&gt;
396 &lt;li&gt;French - 79%&lt;/li&gt;
397 &lt;li&gt;Italian - 79%&lt;/li&gt;
398 &lt;li&gt;Japanese - 77%&lt;/li&gt;
399 &lt;li&gt;Arabic (Morocco) - 75%&lt;/li&gt;
400 &lt;li&gt;Persian - 71%&lt;/li&gt;
401
402 &lt;/ul&gt;
403
404 &lt;p&gt;I wonder how long it will take to bring these to 100%.&lt;/p&gt;
405
406 &lt;p&gt;Then there is the list of languages about halfway done:&lt;/p&gt;
407
408 &lt;ul&gt;
409
410 &lt;li&gt;Russian - 63%&lt;/li&gt;
411 &lt;li&gt;Swedish - 53%&lt;/li&gt;
412 &lt;li&gt;Chinese (Traditional) - 46%&lt;/li&gt;
413 &lt;li&gt;Catalan - 45%&lt;/li&gt;
414
415 &lt;/ul&gt;
416
417 &lt;p&gt;Several are on to a good start:&lt;/p&gt;
418
419 &lt;ul&gt;
420
421 &lt;li&gt;Dutch - 26%&lt;/li&gt;
422 &lt;li&gt;Vietnamese - 25%&lt;/li&gt;
423 &lt;li&gt;Polish - 23%&lt;/li&gt;
424 &lt;li&gt;Czech - 22%&lt;/li&gt;
425 &lt;li&gt;Turkish - 18%&lt;/li&gt;
426
427 &lt;/ul&gt;
428
429 &lt;p&gt;Finally, there are the ones just getting started:&lt;/p&gt;
430
431 &lt;ul&gt;
432
433 &lt;li&gt;Korean - 4%&lt;/li&gt;
434 &lt;li&gt;Croatian - 2%&lt;/li&gt;
435 &lt;li&gt;Greek - 2%&lt;/li&gt;
436 &lt;li&gt;Danish - 1%&lt;/li&gt;
437 &lt;li&gt;Romanian - 1%&lt;/li&gt;
438
439 &lt;/ul&gt;
440
441 &lt;p&gt;If you want to help provide a Debian instruction book in your own
442 language, visit
443 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/#languages&quot;&gt;Weblate&lt;/a&gt;
444 to contribute to the translations.&lt;/p&gt;
445
446 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
447 activities, please send Bitcoin donations to my address
448 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
449 </description>
450 </item>
451
452 <item>
453 <title>Latest Jami back in Debian Testing, and scriptable using dbus</title>
454 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</link>
455 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html</guid>
456 <pubDate>Tue, 12 Jan 2021 17:00:00 +0100</pubDate>
457 <description>&lt;p&gt;After a lot of hard work by its maintainer Alexandre Viau and
458 others, the decentralized communication platform
459 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;
460 (earlier known as Ring), managed to get
461 &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;its latest version&lt;/a&gt;
462 into Debian Testing. Several of its dependencies has caused build and
463 propagation problems, which all seem to be solved now.&lt;/p&gt;
464
465 &lt;p&gt;In addition to the fact that Jami is decentralized, similar to how
466 bittorrent is decentralized, I first of all like how it is not
467 connected to external IDs like phone numbers. This allow me to set up
468 computers to send me notifications using Jami without having to find
469 get a phone number for each computer. Automatic notification via Jami
470 is also made trivial thanks to the provided client side API (as a DBus
471 service). Here is my bourne shell script demonstrating how to let any
472 system send a message to any Jami address. It will create a new
473 identity before sending the message, if no Jami identity exist
474 already:&lt;/p&gt;
475
476 &lt;p&gt;&lt;pre&gt;
477 #!/bin/sh
478 #
479 # Usage: $0 &lt;jami-address&gt; &lt;message&gt;
480 #
481 # Send &lt;message&gt; to &lt;jami-address&gt;, create local jami account if
482 # missing.
483 #
484 # License: GPL v2 or later at your choice
485 # Author: Petter Reinholdtsen
486
487
488 if [ -z &quot;$HOME&quot; ] ; then
489 echo &quot;error: missing \$HOME, required for dbus to work&quot;
490 exit 1
491 fi
492
493 # First, get dbus running if not already running
494 DBUSLAUNCH=/usr/bin/dbus-launch
495 PIDFILE=/run/asterisk/dbus-session.pid
496 if [ -e $PIDFILE ] ; then
497 . $PIDFILE
498 if ! kill -0 $DBUS_SESSION_BUS_PID 2&gt;/dev/null ; then
499 unset DBUS_SESSION_BUS_ADDRESS
500 fi
501 fi
502 if [ -z &quot;$DBUS_SESSION_BUS_ADDRESS&quot; ] &amp;&amp; [ -x &quot;$DBUSLAUNCH&quot; ]; then
503 DBUS_SESSION_BUS_ADDRESS=&quot;unix:path=$HOME/.dbus&quot;
504 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;
505 DBUS_SESSION_BUS_PID=$!
506 (
507 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
508 echo DBUS_SESSION_BUS_ADDRESS=\&quot;&quot;$DBUS_SESSION_BUS_ADDRESS&quot;\&quot;
509 echo export DBUS_SESSION_BUS_ADDRESS
510 ) &gt; $PIDFILE
511 . $PIDFILE
512 fi &amp;
513
514 dringop() {
515 part=&quot;$1&quot;; shift
516 op=&quot;$1&quot;; shift
517 dbus-send --session \
518 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
519 }
520
521 dringopreply() {
522 part=&quot;$1&quot;; shift
523 op=&quot;$1&quot;; shift
524 dbus-send --session --print-reply \
525 --dest=&quot;cx.ring.Ring&quot; /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
526 }
527
528 firstaccount() {
529 dringopreply ConfigurationManager getAccountList | \
530 grep string | awk -F&#39;&quot;&#39; &#39;{print $2}&#39; | head -n 1
531 }
532
533 account=$(firstaccount)
534
535 if [ -z &quot;$account&quot; ] ; then
536 echo &quot;Missing local account, trying to create it&quot;
537 dringop ConfigurationManager addAccount \
538 dict:string:string:&quot;Account.type&quot;,&quot;RING&quot;,&quot;Account.videoEnabled&quot;,&quot;false&quot;
539 account=$(firstaccount)
540 if [ -z &quot;$account&quot; ] ; then
541 echo &quot;unable to create local account&quot;
542 exit 1
543 fi
544 fi
545
546 # Not using dringopreply to ensure $2 can contain spaces
547 dbus-send --print-reply --session \
548 --dest=cx.ring.Ring \
549 /cx/ring/Ring/ConfigurationManager \
550 cx.ring.Ring.ConfigurationManager.sendTextMessage \
551 string:&quot;$account&quot; string:&quot;$1&quot; \
552 dict:string:string:&quot;text/plain&quot;,&quot;$2&quot;
553 &lt;/pre&gt;&lt;/p&gt;
554
555 &lt;p&gt;If you want to check it out yourself, visit the
556 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system project page&lt;/a&gt; to learn
557 more, and install the latest Jami client from Debian Unstable or
558 Testing.&lt;/p&gt;
559
560 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
561 activities, please send Bitcoin donations to my address
562 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
563 </description>
564 </item>
565
566 <item>
567 <title>Buster based Bokmål edition of Debian Administrator&#39;s Handbook</title>
568 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
569 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
570 <pubDate>Tue, 20 Oct 2020 18:35:00 +0200</pubDate>
571 <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;
572
573 &lt;p&gt;I am happy to report that we finally made it! Norwegian Bokmål
574 became the first translation published on paper of the new Buster
575 based edition of &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
576 Administrator&#39;s Handbook&lt;/a&gt;&quot;. The print proof reading copy arrived
577 some days ago, and it looked good, so now the book is approved for
578 general distribution. This updated paperback edition &lt;a
579 href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available from
580 lulu.com&lt;/a&gt;. The book is also available for download in electronic
581 form as PDF, EPUB and Mobipocket, and can also be
582 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online&lt;/a&gt;.&lt;/p&gt;
583
584 &lt;p&gt;I am very happy to wrap up this Creative Common licensed project,
585 which concludes several months of work by several volunteers. The
586 number of Linux related books published in Norwegian are few, and I
587 really hope this one will gain many readers, as it is packed with deep
588 knowledge on Linux and the Debian ecosystem. The book will be
589 available for various Internet book stores like Amazon and Barnes &amp;
590 Noble soon, but I recommend buying
591 &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
592 for Debian-administratoren&lt;/a&gt;&quot; directly from the source at Lulu.
593
594 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
595 activities, please send Bitcoin donations to my address
596 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
597 </description>
598 </item>
599
600 <item>
601 <title>Buster update of Norwegian Bokmål edition of Debian Administrator&#39;s Handbook almost done</title>
602 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html</link>
603 <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>
604 <pubDate>Fri, 11 Sep 2020 09:45:00 +0200</pubDate>
605 <description>&lt;p&gt;Thanks to the good work of several volunteers, the updated edition
606 of the Norwegian translation for
607 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
608 Handbook&lt;/a&gt;&quot; is now almost completed. After many months of proof
609 reading, I consider the proof reading complete enough for us to move
610 to the next step, and have asked for the print version to be prepared
611 and sent of to the print on demand service lulu.com. While it is
612 still not to late if you find any incorrect translations on
613 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
614 hosted Weblate service&lt;/a&gt;, but it will be soon. :) You can check out
615 &lt;a href=&quot; https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;the Buster
616 edition on the web&lt;/a&gt; until the print edition is ready.&lt;/p&gt;
617
618 &lt;p&gt;The book will be for sale on lulu.com and various web book stores,
619 with links available from the web site for the book linked to above.
620 I hope a lot of readers find it useful.&lt;/p&gt;
621
622 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
623 activities, please send Bitcoin donations to my address
624 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
625 </description>
626 </item>
627
628 <item>
629 <title>Working on updated Norwegian Bokmål edition of Debian Administrator&#39;s Handbook</title>
630 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</link>
631 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html</guid>
632 <pubDate>Sat, 4 Jul 2020 23:55:00 +0200</pubDate>
633 <description>&lt;p&gt;Three years ago, the first Norwegian Bokmål edition of
634 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
635 Handbook&lt;/a&gt;&quot; was published. This was based on Debian Jessie. Now a
636 new and updated version based on Buster is getting ready. Work on the
637 updated Norwegian Bokmål edition has been going on for a few months
638 now, and yesterday, we reached the first mile stone, with 100% of the
639 texts being translated. A lot of proof reading remains, of course,
640 but a major step towards a new edition has been taken.&lt;/p&gt;
641
642 &lt;p&gt;The book is translated by volunteers, and we would love to get some
643 help with the proof reading. The translation uses
644 &lt;a href=&quot;https://hosted.weblate.org/languages/nb_NO/debian-handbook/&quot;&gt;the
645 hosted Weblate service&lt;/a&gt;, and we welcome everyone to have a look and
646 submit improvements and suggestions. There is also a proof readers
647 PDF available on request, get in touch if you want to help out that
648 way.&lt;/p&gt;
649
650 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
651 activities, please send Bitcoin donations to my address
652 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
653 </description>
654 </item>
655
656 <item>
657 <title>Secure Socket API - a simple and powerful approach for TLS support in software</title>
658 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</link>
659 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html</guid>
660 <pubDate>Sat, 6 Jun 2020 12:40:00 +0200</pubDate>
661 <description>&lt;p&gt;As a member of the &lt;a href=&quot;https://www.nuug.no/&quot;&gt;Norwegian Unix
662 User Group&lt;/a&gt;, I have the pleasure of receiving the
663 &lt;a href=&quot;https://www.usenix.org/&quot;&gt;USENIX&lt;/a&gt; magazine
664 &lt;a href=&quot;https://www.usenix.org/publications/login/&quot;&gt;;login:&lt;/a&gt;
665 several times a year. I rarely have time to read all the articles,
666 but try to at least skim through them all as there is a lot of nice
667 knowledge passed on there. I even carry the latest issue with me most
668 of the time to try to get through all the articles when I have a few
669 spare minutes.&lt;/p&gt;
670
671 &lt;p&gt;The other day I came across a nice article titled
672 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/winter2018/oneill&quot;&gt;The
673 Secure Socket API: TLS as an Operating System Service&lt;/a&gt;&quot; with a
674 marvellous idea I hope can make it all the way into the POSIX standard.
675 The idea is as simple as it is powerful. By introducing a new
676 socket() option IPPROTO_TLS to use TLS, and a system wide service to
677 handle setting up TLS connections, one both make it trivial to add TLS
678 support to any program currently using the POSIX socket API, and gain
679 system wide control over certificates, TLS versions and encryption
680 systems used. Instead of doing this:&lt;/p&gt;
681
682 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
683 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
684 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
685
686 &lt;p&gt;the program code would be doing this:&lt;p&gt;
687
688 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
689 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
690 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
691
692 &lt;p&gt;According to the ;login: article, converting a C program to use TLS
693 would normally modify only 5-10 lines in the code, which is amazing
694 when compared to using for example the OpenSSL API.&lt;/p&gt;
695
696 &lt;p&gt;The project has set up the
697 &lt;a href=&quot;https://securesocketapi.org/&quot;&gt;https://securesocketapi.org/&lt;/a&gt;
698 web site to spread the idea, and the code for a kernel module and the
699 associated system daemon is available from two github repositories:
700 &lt;a href=&quot;https://github.com/markoneill/ssa&quot;&gt;ssa&lt;/a&gt; and
701 &lt;a href=&quot;https://github.com/markoneill/ssa-daemon&quot;&gt;ssa-daemon&lt;/a&gt;.
702 Unfortunately there is no explicit license information with the code,
703 so its copyright status is unclear. A
704 &lt;a href=&quot;https://github.com/markoneill/ssa/issues/2&quot;&gt;request to solve
705 this&lt;/a&gt; about it has been unsolved since 2018-08-17.&lt;/p&gt;
706
707 &lt;p&gt;I love the idea of extending socket() to gain TLS support, and
708 understand why it is an advantage to implement this as a kernel module
709 and system wide service daemon, but can not help to think that it
710 would be a lot easier to get projects to move to this way of setting
711 up TLS if it was done with a user space approach where programs
712 wanting to use this API approach could just link with a wrapper
713 library.&lt;/p&gt;
714
715 &lt;p&gt;I recommend you check out this simple and powerful approach to more
716 secure network connections. :)&lt;/p&gt;
717
718 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
719 activities, please send Bitcoin donations to my address
720 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
721 </description>
722 </item>
723
724 <item>
725 <title>Jami as a Zoom client, a trick for password protected rooms...</title>
726 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</link>
727 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html</guid>
728 <pubDate>Fri, 8 May 2020 13:30:00 +0200</pubDate>
729 <description>&lt;p&gt;Half a year ago,
730 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html&quot;&gt;I
731 wrote&lt;/a&gt; about &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami communication
732 client&lt;/a&gt;, capable of peer-to-peer encrypted communication. It
733 handle both messages, audio and video. It uses distributed hash
734 tables instead of central infrastructure to connect its users to each
735 other, which in my book is a plus. I mentioned briefly that it could
736 also work as a SIP client, which came in handy when the higher
737 educational sector in Norway started to promote Zoom as its video
738 conferencing solution. I am reluctant to use the official Zoom client
739 software, due to their &lt;a href=&quot;https://zoom.us/terms&quot;&gt;copyright
740 license clauses&lt;/a&gt; prohibiting users to reverse engineer (for example
741 to check the security) and benchmark it, and thus prefer to connect to
742 Zoom meetings with free software clients.&lt;/p&gt;
743
744 &lt;p&gt;Jami worked OK as a SIP client to Zoom as long as there was no
745 password set on the room. The Jami daemon leak memory like crazy
746 (approximately 1 GiB a minute) when I am connected to the video
747 conference, so I had to restart the client every 7-10 minutes, which
748 is not great. I tried to get other SIP Linux clients to work
749 without success, so I decided I would have to live with this wart
750 until someone managed to fix the leak in the dring code base. But
751 another problem showed up once the rooms were password protected. I
752 could not get my dial tone signaling through from Jami to Zoom, and
753 dial tone signaling is used to enter the password when connecting to
754 Zoom. I tried a lot of different permutations with my Jami and
755 Asterisk setup to try to figure out why the signaling did not get
756 through, only to finally discover that the fundamental problem seem to
757 be that Zoom is simply not able to receive dial tone signaling when
758 connecting via SIP. There seem to be nothing wrong with the Jami and
759 Asterisk end, it is simply broken in the Zoom end. I got help from a
760 very skilled VoIP engineer figuring out this last part. And being a
761 very skilled engineer, he was also able to locate a solution for me.
762 Or to be exact, a workaround that solve my initial problem of
763 connecting to password protected Zoom rooms using Jami.&lt;/p&gt;
764
765 &lt;p&gt;So, how do you do this, I am sure you are wondering by now. The
766 trick is already
767 &lt;a href=&quot;https://support.zoom.us/hc/en-us/articles/202405539-H-323-SIP-Room-Connector-Dial-Strings#sip&quot;&gt;documented
768 from Zoom&lt;/a&gt;, and it is to modify the SIP address to include the room
769 password. What is most surprising about this is that the
770 automatically generated email from Zoom with instructions on how to
771 connect via SIP do not mention this. The SIP address to use normally
772 consist of the room ID (a number), an @ character and the IP address
773 of the Zoom SIP gateway. But Zoom understand a lot more than just the
774 room ID in front of the at sign. The format is &quot;&lt;tt&gt;[Meeting
775 ID].[Password].[Layout].[Host Key]&lt;/tt&gt;&quot;, and you can here see how you
776 can both enter password, control the layout (full screen, active
777 presence and gallery) and specify the host key to start the meeting.
778 The full SIP address entered into Jami to provide the password will
779 then look like this (all using made up numbers):&lt;/p&gt;
780
781 &lt;p&gt;&lt;blockquote&gt;
782 &lt;tt&gt;sip:657837644.522827@192.168.169.170&lt;/tt&gt;
783 &lt;/blockquote&gt;&lt;/p&gt;
784
785 &lt;p&gt;Now if only jami would reduce its memory usage, I could even
786 recommend this setup to others. :)&lt;/p&gt;
787
788 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
789 activities, please send Bitcoin donations to my address
790 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
791 </description>
792 </item>
793
794 <item>
795 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software</title>
796 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</link>
797 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html</guid>
798 <pubDate>Wed, 29 Apr 2020 13:10:00 +0200</pubDate>
799 <description>&lt;p&gt;The curiosity got the better of me when
800 &lt;a href=&quot;https://developers.slashdot.org/story/20/04/06/1424246/new-jersey-desperately-needs-cobol-programmers&quot;&gt;Slashdot
801 reported&lt;/a&gt; that New Jersey was desperately looking for
802 &lt;a href=&quot;https://en.wikipedia.org/wiki/COBOL&quot;&gt;COBOL&lt;/a&gt; programmers,
803 and a few days later it was reported that
804 &lt;a href=&quot;https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce&quot;&gt;IBM
805 tried to locate COBOL programmers&lt;/a&gt;.&lt;/p&gt;
806
807 &lt;p&gt;I thus decided to have a look at free software alternatives to
808 learn COBOL, and had the pleasure to find
809 &lt;a href=&quot;https://sourceforge.net/projects/open-cobol/&quot;&gt;GnuCOBOL&lt;/a&gt; was
810 already &lt;a href=&quot;https://tracker.debian.org/pkg/gnucobol&quot;&gt;in
811 Debian&lt;/a&gt;. It used to be called Open Cobol, and is a &quot;compiler&quot;
812 transforming COBOL code to C or C++ before giving it to GCC or Visual
813 Studio to build binaries.&lt;/p&gt;
814
815 &lt;p&gt;I managed to get in touch with upstream, and was impressed with the
816 quick response, and also was happy to see a new Debian maintainer
817 taking over when the original one recently asked to be replaced. A
818 new Debian upload was done as recently as yesterday.&lt;/p&gt;
819
820 &lt;p&gt;Using the Debian package, I was able to follow a simple COBOL
821 introduction and make and run simple COBOL programs. It was fun to
822 learn a new programming language. If you want to test for yourself,
823 &lt;a href=&quot;https://en.wikipedia.org/wiki/GnuCOBOL&quot;&gt;the GnuCOBOL Wikipedia
824 page&lt;/a&gt; have a few simple examples to get you startet.&lt;/p&gt;
825
826 &lt;p&gt;As I do not have much experience with COBOL, I do not know how
827 standard compliant it is, but it claim to pass most tests from COBOL
828 test suite, which sound good to me. It is nice to know it is possible
829 to learn COBOL using software without any usage restrictions, and I am
830 very happy such nice free software project as this is available. If
831 you as me is curious about COBOL, check it out.&lt;/p&gt;
832
833 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
834 activities, please send Bitcoin donations to my address
835 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
836 </description>
837 </item>
838
839 <item>
840 <title>Jami/Ring, finally functioning peer to peer communication client</title>
841 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</link>
842 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html</guid>
843 <pubDate>Wed, 19 Jun 2019 08:50:00 +0200</pubDate>
844 <description>&lt;p&gt;Some years ago, in 2016, I
845 &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
846 for the first time about&lt;/a&gt; the Ring peer to peer messaging system.
847 It would provide messaging without any central server coordinating the
848 system and without requiring all users to register a phone number or
849 own a mobile phone. Back then, I could not get it to work, and put it
850 aside until it had seen more development. A few days ago I decided to
851 give it another try, and am happy to report that this time I am able
852 to not only send and receive messages, but also place audio and video
853 calls. But only if UDP is not blocked into your network.&lt;/p&gt;
854
855 &lt;p&gt;The Ring system changed name earlier this year to
856 &lt;a href=&quot;https://en.wikipedia.org/wiki/Jami_(software)&quot;&gt;Jami&lt;/a&gt;. I
857 tried doing web search for &#39;ring&#39; when I discovered it for the first
858 time, and can only applaud this change as it is impossible to find
859 something called Ring among the noise of other uses of that word. Now
860 you can search for &#39;jami&#39; and this client and
861 &lt;a href=&quot;https://jami.net/&quot;&gt;the Jami system&lt;/a&gt; is the first hit at
862 least on duckduckgo.&lt;/p&gt;
863
864 &lt;p&gt;Jami will by default encrypt messages as well as audio and video
865 calls, and try to send them directly between the communicating parties
866 if possible. If this proves impossible (for example if both ends are
867 behind NAT), it will use a central SIP TURN server maintained by the
868 Jami project. Jami can also be a normal SIP client. If the SIP
869 server is unencrypted, the audio and video calls will also be
870 unencrypted. This is as far as I know the only case where Jami will
871 do anything without encryption.&lt;/p&gt;
872
873 &lt;p&gt;Jami is available for several platforms: Linux, Windows, MacOSX,
874 Android, iOS, and Android TV. It is included in Debian already. Jami
875 also work for those using F-Droid without any Google connections,
876 while Signal do not.
877 &lt;a href=&quot;https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol&quot;&gt;The
878 protocol&lt;/a&gt; is described in the Ring project wiki. The system uses a
879 distributed hash table (DHT) system (similar to BitTorrent) running
880 over UDP. On one of the networks I use, I discovered Jami failed to
881 work. I tracked this down to the fact that incoming UDP packages
882 going to ports 1-49999 were blocked, and the DHT would pick a random
883 port and end up in the low range most of the time. After talking to
884 the developers, I solved this by enabling the dhtproxy in the
885 settings, thus using TCP to talk to a central DHT proxy instead of
886
887 peering directly with others. I&#39;ve been told the developers are
888 working on allowing DHT to use TCP to avoid this problem. I also ran
889 into a problem when trying to talk to the version of Ring included in
890 Debian Stable (Stretch). Apparently the protocol changed between
891 beta2 and the current version, making these clients incompatible.
892 Hopefully the protocol will not be made incompatible in the
893 future.&lt;/p&gt;
894
895 &lt;p&gt;It is worth noting that while looking at Jami and its features, I
896 came across another communication platform I have not tested yet. The
897 &lt;a href=&quot;https://en.wikipedia.org/wiki/Tox_(protocol)&quot;&gt;Tox protocol&lt;/a&gt;
898 and &lt;a href=&quot;https://tox.chat/&quot;&gt;family of Tox clients&lt;/a&gt;. It might
899 become the topic of a future blog post.&lt;/p&gt;
900
901 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
902 activities, please send Bitcoin donations to my address
903 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
904 </description>
905 </item>
906
907 <item>
908 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål</title>
909 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</link>
910 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html</guid>
911 <pubDate>Wed, 23 Jan 2019 07:50:00 +0100</pubDate>
912 <description>&lt;p&gt;I høst ble jeg inspirert til å bidra til oversettelsen av
913 &lt;a href=&quot;http://unknown-horizons.org/&quot;&gt;strategispillet Unknown
914 Horizons&lt;/a&gt;, og oversatte de nesten 200 strengene i prosjektet til
915 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
916 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
917 nye versjonen kom på nyåret, og ble
918 &lt;a href=&quot;https://tracker.debian.org/pkg/unknown-horizons&quot;&gt;lastet opp i
919 Debian&lt;/a&gt; for noen få dager siden. I går kveld fikk jeg testet det ut, og
920 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
921 måtte justeres, men ikke noe alvorlig. Har oppdatert
922 &lt;a href=&quot;https://hosted.weblate.org/projects/uh/&quot;&gt;oversettelsen på
923 Weblate&lt;/a&gt;, slik at neste utgave vil være enda bedre. :)&lt;/p&gt;
924
925 &lt;p&gt;Spillet er et ressursstyringsspill ala Civilization, og er morsomt
926 å spille for oss som liker slikt. :)&lt;/p&gt;
927
928 &lt;p&gt;Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
929 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
930 til min adresse
931 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.
932 Merk, betaling med bitcoin er ikke anonymt. :)&lt;/p&gt;
933 </description>
934 </item>
935
936 <item>
937 <title>Debian now got everything you need to program Micro:bit</title>
938 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</link>
939 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html</guid>
940 <pubDate>Tue, 22 Jan 2019 17:20:00 +0100</pubDate>
941 <description>&lt;p&gt;I am amazed and very pleased to discover that since a few days ago,
942 everything you need to program the &lt;a href=&quot;https://microbit.org/&quot;&gt;BBC
943 micro:bit&lt;/a&gt; is available from the Debian archive. All this is
944 thanks to the hard work of Nick Morrott and the Debian python
945 packaging team. The micro:bit project recommend the mu-editor to
946 program the microcomputer, as this editor will take care of all the
947 machinery required to injekt/flash micropython alongside the program
948 into the micro:bit, as long as the pieces are available.&lt;/p&gt;
949
950 &lt;p&gt;There are three main pieces involved. The first to enter Debian
951 was
952 &lt;a href=&quot;https://tracker.debian.org/pkg/python-uflash&quot;&gt;python-uflash&lt;/a&gt;,
953 which was accepted into the archive 2019-01-12. The next one was
954 &lt;a href=&quot;https://tracker.debian.org/pkg/mu-editor&quot;&gt;mu-editor&lt;/a&gt;, which
955 showed up 2019-01-13. The final and hardest part to to into the
956 archive was
957 &lt;a href=&quot;https://tracker.debian.org/pkg/firmware-microbit-micropython&quot;&gt;firmware-microbit-micropython&lt;/a&gt;,
958 which needed to get its build system and dependencies into Debian
959 before it was accepted 2019-01-20. The last one is already in Debian
960 Unstable and should enter Debian Testing / Buster in three days. This
961 all allow any user of the micro:bit to get going by simply running
962 &#39;apt install mu-editor&#39; when using Testing or Unstable, and once
963 Buster is released as stable, all the users of Debian stable will be
964 catered for.&lt;/p&gt;
965
966 &lt;p&gt;As a minor final touch, I added rules to
967 &lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;the isenkram
968 package&lt;/a&gt; for recognizing micro:bit and recommend the mu-editor
969 package. This make sure any user of the isenkram desktop daemon will
970 get a popup suggesting to install mu-editor then the USB cable from
971 the micro:bit is inserted for the first time.&lt;/p&gt;
972
973 &lt;p&gt;This should make it easier to have fun.&lt;/p&gt;
974
975 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
976 activities, please send Bitcoin donations to my address
977 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
978 </description>
979 </item>
980
981 <item>
982 <title>Learn to program with Minetest on Debian</title>
983 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</link>
984 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html</guid>
985 <pubDate>Sat, 15 Dec 2018 15:30:00 +0100</pubDate>
986 <description>&lt;p&gt;A fun way to learn how to program
987 &lt;a href=&quot;https://www.python.org/&quot;&gt;Python&lt;/a&gt; is to follow the
988 instructions in the book
989 &quot;&lt;a href=&quot;https://nostarch.com/programwithminecraft&quot;&gt;Learn to program
990 with Minecraft&lt;/a&gt;&quot;, which introduces programming in Python to people
991 who like to play with Minecraft. The book uses a Python library to
992 talk to a TCP/IP socket with an API accepting build instructions and
993 providing information about the current players in a Minecraft world.
994 The TCP/IP API was first created for the Minecraft implementation for
995 Raspberry Pi, and has since been ported to some server versions of
996 Minecraft. The book contain recipes for those using Windows, MacOSX
997 and Raspian. But a little known fact is that you can follow the same
998 recipes using the free software construction game
999 &lt;a href=&quot;https://minetest.net/&quot;&gt;Minetest&lt;/a&gt;.&lt;/p&gt;
1000
1001 &lt;p&gt;There is &lt;a href=&quot;https://github.com/sprintingkiwi/pycraft_mod&quot;&gt;a
1002 Minetest module implementing the same API&lt;/a&gt;, making it possible to
1003 use the Python programs coded to talk to Minecraft with Minetest too.
1004 I
1005 &lt;a href=&quot;https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%2Bgit20180331.0376a0a%2Bdfsg-1.html&quot;&gt;uploaded
1006 this module&lt;/a&gt; to Debian two weeks ago, and as soon as it clears the
1007 FTP masters NEW queue, learning to program Python with Minetest on
1008 Debian will be a simple &#39;apt install&#39; away. The Debian package is
1009 maintained as part of the Debian Games team, and
1010 &lt;a href=&quot;https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft&quot;&gt;the
1011 packaging rules&lt;/a&gt; are currently located under &#39;unfinished&#39; on
1012 Salsa.&lt;/p&gt;
1013
1014 &lt;p&gt;You will most likely need to install several of the Minetest
1015 modules in Debian for the examples included with the library to work
1016 well, as there are several blocks used by the example scripts that are
1017 provided via modules in Minetest. Without the required blocks, a
1018 simple stone block is used instead. My initial testing with a analog
1019 clock did not get gold arms as instructed in the python library, but
1020 instead used stone arms.&lt;/p&gt;
1021
1022 &lt;p&gt;I tried to find a way to add the API to the desktop version of
1023 Minecraft, but were unable to find any working recipes. The
1024 &lt;a href=&quot;https://www.epiphanydigest.com/tag/minecraft-python-api/&quot;&gt;recipes&lt;/a&gt;
1025 I &lt;a href=&quot;https://github.com/kbsriram/mcpiapi&quot;&gt;found&lt;/a&gt; are only
1026 working with a standalone Minecraft server setup. Are there any
1027 options to use with the normal desktop version?&lt;/p&gt;
1028
1029 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1030 activities, please send Bitcoin donations to my address
1031 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1032 </description>
1033 </item>
1034
1035 <item>
1036 <title>Time for an official MIME type for patches?</title>
1037 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</link>
1038 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html</guid>
1039 <pubDate>Thu, 1 Nov 2018 08:15:00 +0100</pubDate>
1040 <description>&lt;p&gt;As part of my involvement in
1041 &lt;a href=&quot;https://gitlab.com/OsloMet-ABI/nikita-noark5-core&quot;&gt;the Nikita
1042 archive API project&lt;/a&gt;, I&#39;ve been importing a fairly large lump of
1043 emails into a test instance of the archive to see how well this would
1044 go. I picked a subset of &lt;a href=&quot;https://notmuchmail.org/&quot;&gt;my
1045 notmuch email database&lt;/a&gt;, all public emails sent to me via
1046 @lists.debian.org, giving me a set of around 216 000 emails to import.
1047 In the process, I had a look at the various attachments included in
1048 these emails, to figure out what to do with attachments, and noticed
1049 that one of the most common attachment formats do not have
1050 &lt;a href=&quot;https://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;an
1051 official MIME type&lt;/a&gt; registered with IANA/IETF. The output from
1052 diff, ie the input for patch, is on the top 10 list of formats
1053 included in these emails. At the moment people seem to use either
1054 text/x-patch or text/x-diff, but neither is officially registered. It
1055 would be better if one official MIME type were registered and used
1056 everywhere.&lt;/p&gt;
1057
1058 &lt;p&gt;To try to get one official MIME type for these files, I&#39;ve brought
1059 up the topic on
1060 &lt;a href=&quot;https://www.ietf.org/mailman/listinfo/media-types&quot;&gt;the
1061 media-types mailing list&lt;/a&gt;. If you are interested in discussion
1062 which MIME type to use as the official for patch files, or involved in
1063 making software using a MIME type for patches, perhaps you would like
1064 to join the discussion?&lt;/p&gt;
1065
1066 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1067 activities, please send Bitcoin donations to my address
1068 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1069 </description>
1070 </item>
1071
1072 <item>
1073 <title>Automatic Google Drive sync using grive in Debian</title>
1074 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</link>
1075 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html</guid>
1076 <pubDate>Thu, 4 Oct 2018 15:20:00 +0200</pubDate>
1077 <description>&lt;p&gt;A few days, I rescued a Windows victim over to Debian. To try to
1078 rescue the remains, I helped set up automatic sync with Google Drive.
1079 I did not find any sensible Debian package handling this
1080 automatically, so I rebuild the grive2 source from
1081 &lt;a href=&quot;http://www.webupd8.org/&quot;&gt;the Ubuntu UPD8 PPA&lt;/a&gt; to do the
1082 task and added a autostart desktop entry and a small shell script to
1083 run in the background while the user is logged in to do the sync.
1084 Here is a sketch of the setup for future reference.&lt;/p&gt;
1085
1086 &lt;p&gt;I first created &lt;tt&gt;~/googledrive&lt;/tt&gt;, entered the directory and
1087 ran &#39;&lt;tt&gt;grive -a&lt;/tt&gt;&#39; to authenticate the machine/user. Next, I
1088 created a autostart hook in &lt;tt&gt;~/.config/autostart/grive.desktop&lt;/tt&gt;
1089 to start the sync when the user log in:&lt;/p&gt;
1090
1091 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1092 [Desktop Entry]
1093 Name=Google drive autosync
1094 Type=Application
1095 Exec=/home/user/bin/grive-sync
1096 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1097
1098 &lt;p&gt;Finally, I wrote the &lt;tt&gt;~/bin/grive-sync&lt;/tt&gt; script to sync
1099 ~/googledrive/ with the files in Google Drive.&lt;/p&gt;
1100
1101 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1102 #!/bin/sh
1103 set -e
1104 cd ~/
1105 cleanup() {
1106 if [ &quot;$syncpid&quot; ] ; then
1107 kill $syncpid
1108 fi
1109 }
1110 trap cleanup EXIT INT QUIT
1111 /usr/lib/grive/grive-sync.sh listen googledrive 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot; &amp;
1112 syncpdi=$!
1113 while true; do
1114 if ! xhost &gt;/dev/null 2&gt;&amp;1 ; then
1115 echo &quot;no DISPLAY, exiting as the user probably logged out&quot;
1116 exit 1
1117 fi
1118 if [ ! -e /run/user/1000/grive-sync.sh_googledrive ] ; then
1119 /usr/lib/grive/grive-sync.sh sync googledrive
1120 fi
1121 sleep 300
1122 done 2&gt;&amp;1 | sed &quot;s%^%$0:%&quot;
1123 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1124
1125 &lt;p&gt;Feel free to use the setup if you want. It can be assumed to be
1126 GNU GPL v2 licensed (or any later version, at your leisure), but I
1127 doubt this code is possible to claim copyright on.&lt;/p&gt;
1128
1129 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1130 activities, please send Bitcoin donations to my address
1131 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1132 </description>
1133 </item>
1134
1135 <item>
1136 <title>Using the Kodi API to play Youtube videos</title>
1137 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</link>
1138 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html</guid>
1139 <pubDate>Sun, 2 Sep 2018 23:40:00 +0200</pubDate>
1140 <description>&lt;p&gt;I continue to explore my Kodi installation, and today I wanted to
1141 tell it to play a youtube URL I received in a chat, without having to
1142 insert search terms using the on-screen keyboard. After searching the
1143 web for API access to the Youtube plugin and testing a bit, I managed
1144 to find a recipe that worked. If you got a kodi instance with its API
1145 available from http://kodihost/jsonrpc, you can try the following to
1146 have check out a nice cover band.&lt;/p&gt;
1147
1148 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;curl --silent --header &#39;Content-Type: application/json&#39; \
1149 --data-binary &#39;{ &quot;id&quot;: 1, &quot;jsonrpc&quot;: &quot;2.0&quot;, &quot;method&quot;: &quot;Player.Open&quot;,
1150 &quot;params&quot;: {&quot;item&quot;: { &quot;file&quot;:
1151 &quot;plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg&quot; } } }&#39; \
1152 http://projector.local/jsonrpc&lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1153
1154 &lt;p&gt;I&#39;ve extended kodi-stream program to take a video source as its
1155 first argument. It can now handle direct video links, youtube links
1156 and &#39;desktop&#39; to stream my desktop to Kodi. It is almost like a
1157 Chromecast. :)&lt;/p&gt;
1158
1159 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1160 activities, please send Bitcoin donations to my address
1161 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1162 </description>
1163 </item>
1164
1165 <item>
1166 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata</title>
1167 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</link>
1168 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html</guid>
1169 <pubDate>Tue, 31 Jul 2018 23:30:00 +0200</pubDate>
1170 <description>&lt;p&gt;For a while now, I have looked for a sensible way to share images
1171 with my family using a self hosted solution, as it is unacceptable to
1172 place images from my personal life under the control of strangers
1173 working for data hoarders like Google or Dropbox. The last few days I
1174 have drafted an approach that might work out, and I would like to
1175 share it with you. I would like to publish images on a server under
1176 my control, and point some Internet connected display units using some
1177 free and open standard to the images I published. As my primary
1178 language is not limited to ASCII, I need to store metadata using
1179 UTF-8. Many years ago, I hoped to find a digital photo frame capable
1180 of reading a RSS feed with image references (aka using the
1181 &amp;lt;enclosure&amp;gt; RSS tag), but was unable to find a current supplier
1182 of such frames. In the end I gave up that approach.&lt;/p&gt;
1183
1184 &lt;p&gt;Some months ago, I discovered that
1185 &lt;a href=&quot;https://www.jwz.org/xscreensaver/&quot;&gt;XScreensaver&lt;/a&gt; is able to
1186 read images from a RSS feed, and used it to set up a screen saver on
1187 my home info screen, showing images from the Daily images feed from
1188 NASA. This proved to work well. More recently I discovered that
1189 &lt;a href=&quot;https://kodi.tv&quot;&gt;Kodi&lt;/a&gt; (both using
1190 &lt;a href=&quot;https://www.openelec.tv/&quot;&gt;OpenELEC&lt;/a&gt; and
1191 &lt;a href=&quot;https://libreelec.tv&quot;&gt;LibreELEC&lt;/a&gt;) provide the
1192 &lt;a href=&quot;https://github.com/grinsted/script.screensaver.feedreader&quot;&gt;Feedreader&lt;/a&gt;
1193 screen saver capable of reading a RSS feed with images and news. For
1194 fun, I used it this summer to test Kodi on my parents TV by hooking up
1195 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
1196 screen saver showing selected pictures from my selection.&lt;/p&gt;
1197
1198 &lt;p&gt;Armed with motivation and a test photo frame, I set out to generate
1199 a RSS feed for the Kodi instance. I adjusted my &lt;a
1200 href=&quot;https://freedombox.org/&quot;&gt;Freedombox&lt;/a&gt; instance, created
1201 /var/www/html/privatepictures/, wrote a small Perl script to extract
1202 title and description metadata from the photo files and generate the
1203 RSS file. I ended up using Perl instead of python, as the
1204 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
1205 tags I ended up using, while python3-exif did not. The relevant EXIF
1206 tags only support ASCII, so I had to find better alternatives. XMP
1207 seem to have the support I need.&lt;/p&gt;
1208
1209 &lt;p&gt;I am a bit unsure which EXIF/XMP tags to use, as I would like to
1210 use tags that can be easily added/updated using normal free software
1211 photo managing software. I ended up using the tags set using this
1212 exiftool command, as these tags can also be set using digiKam:&lt;/p&gt;
1213
1214 &lt;blockquote&gt;&lt;pre&gt;
1215 exiftool -headline=&#39;The RSS image title&#39; \
1216 -description=&#39;The RSS image description.&#39; \
1217 -subject+=for-family photo.jpeg
1218 &lt;/pre&gt;&lt;/blockquote&gt;
1219
1220 &lt;p&gt;I initially tried the &quot;-title&quot; and &quot;keyword&quot; tags, but they were
1221 invisible in digiKam, so I changed to &quot;-headline&quot; and &quot;-subject&quot;. I
1222 use the keyword/subject &#39;for-family&#39; to flag that the photo should be
1223 shared with my family. Images with this keyword set are located and
1224 copied into my Freedombox for the RSS generating script to find.&lt;/p&gt;
1225
1226 &lt;p&gt;Are there better ways to do this? Get in touch if you have better
1227 suggestions.&lt;/p&gt;
1228
1229 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1230 activities, please send Bitcoin donations to my address
1231 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1232 </description>
1233 </item>
1234
1235 <item>
1236 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP</title>
1237 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</link>
1238 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html</guid>
1239 <pubDate>Thu, 12 Jul 2018 17:55:00 +0200</pubDate>
1240 <description>&lt;p&gt;Last night, I wrote
1241 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html&quot;&gt;a
1242 recipe to stream a Linux desktop using VLC to a instance of Kodi&lt;/a&gt;.
1243 During the day I received valuable feedback, and thanks to the
1244 suggestions I have been able to rewrite the recipe into a much simpler
1245 approach requiring no setup at all. It is a single script that take
1246 care of it all.&lt;/p&gt;
1247
1248 &lt;p&gt;This new script uses GStreamer instead of VLC to capture the
1249 desktop and stream it to Kodi. This fixed the video quality issue I
1250 saw initially. It further removes the need to add a m3u file on the
1251 Kodi machine, as it instead connects to
1252 &lt;a href=&quot;https://kodi.wiki/view/JSON-RPC_API/v8&quot;&gt;the JSON-RPC API in
1253 Kodi&lt;/a&gt; and simply ask Kodi to play from the stream created using
1254 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
1255 the script below, run it with the DNS name or IP address of the kodi
1256 server to stream to as the only argument, and watch your screen show
1257 up on the Kodi screen. Note, it depend on multicast on the local
1258 network, so if you need to stream outside the local network, the
1259 script must be modified. Also note, I have no idea if audio work, as
1260 I only care about the picture part.&lt;/p&gt;
1261
1262 &lt;blockquote&gt;&lt;pre&gt;
1263 #!/bin/sh
1264 #
1265 # Stream the Linux desktop view to Kodi. See
1266 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
1267 # for backgorund information.
1268
1269 # Make sure the stream is stopped in Kodi and the gstreamer process is
1270 # killed if something go wrong (for example if curl is unable to find the
1271 # kodi server). Do the same when interrupting this script.
1272 kodicmd() {
1273 host=&quot;$1&quot;
1274 cmd=&quot;$2&quot;
1275 params=&quot;$3&quot;
1276 curl --silent --header &#39;Content-Type: application/json&#39; \
1277 --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; \
1278 &quot;http://$host/jsonrpc&quot;
1279 }
1280 cleanup() {
1281 if [ -n &quot;$kodihost&quot; ] ; then
1282 # Stop the playing when we end
1283 playerid=$(kodicmd &quot;$kodihost&quot; Player.GetActivePlayers &quot;{}&quot; |
1284 jq .result[].playerid)
1285 kodicmd &quot;$kodihost&quot; Player.Stop &quot;{ \&quot;playerid\&quot; : $playerid }&quot; &gt; /dev/null
1286 fi
1287 if [ &quot;$gstpid&quot; ] &amp;&amp; kill -0 &quot;$gstpid&quot; &gt;/dev/null 2&gt;&amp;1; then
1288 kill &quot;$gstpid&quot;
1289 fi
1290 }
1291 trap cleanup EXIT INT
1292
1293 if [ -n &quot;$1&quot; ]; then
1294 kodihost=$1
1295 shift
1296 else
1297 kodihost=kodi.local
1298 fi
1299
1300 mcast=239.255.0.1
1301 mcastport=1234
1302 mcastttl=1
1303
1304 pasrc=$(pactl list | grep -A2 &#39;Source #&#39; | grep &#39;Name: .*\.monitor$&#39; | \
1305 cut -d&quot; &quot; -f2|head -1)
1306 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
1307 videoconvert ! queue2 ! \
1308 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
1309 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
1310 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
1311 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=1 sync=0 \
1312 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
1313 &gt; /dev/null 2&gt;&amp;1 &amp;
1314 gstpid=$!
1315
1316 # Give stream a second to get going
1317 sleep 1
1318
1319 # Ask kodi to start streaming using its JSON-RPC API
1320 kodicmd &quot;$kodihost&quot; Player.Open \
1321 &quot;{\&quot;item\&quot;: { \&quot;file\&quot;: \&quot;udp://@$mcast:$mcastport\&quot; } }&quot; &gt; /dev/null
1322
1323 # wait for gst to end
1324 wait &quot;$gstpid&quot;
1325 &lt;/pre&gt;&lt;/blockquote&gt;
1326
1327 &lt;p&gt;I hope you find the approach useful. I know I do.&lt;/p&gt;
1328
1329 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1330 activities, please send Bitcoin donations to my address
1331 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1332 </description>
1333 </item>
1334
1335 <item>
1336 <title>Streaming the Linux desktop to Kodi using VLC and RTSP</title>
1337 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</link>
1338 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html</guid>
1339 <pubDate>Thu, 12 Jul 2018 02:00:00 +0200</pubDate>
1340 <description>&lt;p&gt;PS: See
1341 &lt;ahref=&quot;http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html&quot;&gt;the
1342 followup post&lt;/a&gt; for a even better approach.&lt;/p&gt;
1343
1344 &lt;p&gt;A while back, I was asked by a friend how to stream the desktop to
1345 my projector connected to Kodi. I sadly had to admit that I had no
1346 idea, as it was a task I never had tried. Since then, I have been
1347 looking for a way to do so, preferable without much extra software to
1348 install on either side. Today I found a way that seem to kind of
1349 work. Not great, but it is a start.&lt;/p&gt;
1350
1351 &lt;p&gt;I had a look at several approaches, for example
1352 &lt;a href=&quot;https://github.com/mfoetsch/dlna_live_streaming&quot;&gt;using uPnP
1353 DLNA as described in 2011&lt;/a&gt;, but it required a uPnP server, fuse and
1354 local storage enough to store the stream locally. This is not going
1355 to work well for me, lacking enough free space, and it would
1356 impossible for my friend to get working.&lt;/p&gt;
1357
1358 &lt;p&gt;Next, it occurred to me that perhaps I could use VLC to create a
1359 video stream that Kodi could play. Preferably using
1360 broadcast/multicast, to avoid having to change any setup on the Kodi
1361 side when starting such stream. Unfortunately, the only recipe I
1362 could find using multicast used the rtp protocol, and this protocol
1363 seem to not be supported by Kodi.&lt;/p&gt;
1364
1365 &lt;p&gt;On the other hand, the rtsp protocol is working! Unfortunately I
1366 have to specify the IP address of the streaming machine in both the
1367 sending command and the file on the Kodi server. But it is showing my
1368 desktop, and thus allow us to have a shared look on the big screen at
1369 the programs I work on.&lt;/p&gt;
1370
1371 &lt;p&gt;I did not spend much time investigating codeces. I combined the
1372 rtp and rtsp recipes from
1373 &lt;a href=&quot;https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/&quot;&gt;the
1374 VLC Streaming HowTo/Command Line Examples&lt;/a&gt;, and was able to get
1375 this working on the desktop/streaming end.&lt;/p&gt;
1376
1377 &lt;blockquote&gt;&lt;pre&gt;
1378 vlc screen:// --sout \
1379 &#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;
1380 &lt;/pre&gt;&lt;/blockquote&gt;
1381
1382 &lt;p&gt;I ssh-ed into my Kodi box and created a file like this with the
1383 same IP address:&lt;/p&gt;
1384
1385 &lt;blockquote&gt;&lt;pre&gt;
1386 echo rtsp://192.168.11.4:8080/test.sdp \
1387 &gt; /storage/videos/screenstream.m3u
1388 &lt;/pre&gt;&lt;/blockquote&gt;
1389
1390 &lt;p&gt;Note the 192.168.11.4 IP address is my desktops IP address. As far
1391 as I can tell the IP must be hardcoded for this to work. In other
1392 words, if someone elses machine is going to do the steaming, you have
1393 to update screenstream.m3u on the Kodi machine and adjust the vlc
1394 recipe. To get started, locate the file in Kodi and select the m3u
1395 file while the VLC stream is running. The desktop then show up in my
1396 big screen. :)&lt;/p&gt;
1397
1398 &lt;p&gt;When using the same technique to stream a video file with audio,
1399 the audio quality is really bad. No idea if the problem is package
1400 loss or bad parameters for the transcode. I do not know VLC nor Kodi
1401 enough to tell.&lt;/p&gt;
1402
1403 &lt;p&gt;&lt;strong&gt;Update 2018-07-12&lt;/strong&gt;: Johannes Schauer send me a few
1404 succestions and reminded me about an important step. The &quot;screen:&quot;
1405 input source is only available once the vlc-plugin-access-extra
1406 package is installed on Debian. Without it, you will see this error
1407 message: &quot;VLC is unable to open the MRL &#39;screen://&#39;. Check the log
1408 for details.&quot; He further found that it is possible to drop some parts
1409 of the VLC command line to reduce the amount of hardcoded information.
1410 It is also useful to consider using cvlc to avoid having the VLC
1411 window in the desktop view. In sum, this give us this command line on
1412 the source end
1413
1414 &lt;blockquote&gt;&lt;pre&gt;
1415 cvlc screen:// --sout \
1416 &#39;#transcode{vcodec=mp4v,acodec=mpga,vb=800,ab=128}:rtp{sdp=rtsp://:8080/}&#39;
1417 &lt;/pre&gt;&lt;/blockquote&gt;
1418
1419 &lt;p&gt;and this on the Kodi end&lt;p&gt;
1420
1421 &lt;blockquote&gt;&lt;pre&gt;
1422 echo rtsp://192.168.11.4:8080/ \
1423 &gt; /storage/videos/screenstream.m3u
1424 &lt;/pre&gt;&lt;/blockquote&gt;
1425
1426 &lt;p&gt;Still bad image quality, though. But I did discover that streaming
1427 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
1428 audio quality, so I guess the issue is in the input or transcoding
1429 parts, not the rtsp part. I&#39;ve tried to change the vb and ab
1430 parameters to use more bandwidth, but it did not make a
1431 difference.&lt;/p&gt;
1432
1433 &lt;p&gt;I further received a suggestion from Einar Haraldseid to try using
1434 gstreamer instead of VLC, and this proved to work great! He also
1435 provided me with the trick to get Kodi to use a multicast stream as
1436 its source. By using this monstrous oneliner, I can stream my desktop
1437 with good video quality in reasonable framerate to the 239.255.0.1
1438 multicast address on port 1234:
1439
1440 &lt;blockquote&gt;&lt;pre&gt;
1441 gst-launch-1.0 ximagesrc use-damage=0 ! video/x-raw,framerate=30/1 ! \
1442 videoconvert ! queue2 ! \
1443 x264enc bitrate=8000 speed-preset=superfast tune=zerolatency qp-min=30 \
1444 key-int-max=15 bframes=2 ! video/x-h264,profile=high ! queue2 ! \
1445 mpegtsmux alignment=7 name=mux ! rndbuffersize max=1316 min=1316 ! \
1446 udpsink host=239.255.0.1 port=1234 ttl-mc=1 auto-multicast=1 sync=0 \
1447 pulsesrc device=$(pactl list | grep -A2 &#39;Source #&#39; | \
1448 grep &#39;Name: .*\.monitor$&#39; | cut -d&quot; &quot; -f2|head -1) ! \
1449 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
1450 &lt;/pre&gt;&lt;/blockquote&gt;
1451
1452 &lt;p&gt;and this on the Kodi end&lt;p&gt;
1453
1454 &lt;blockquote&gt;&lt;pre&gt;
1455 echo udp://@239.255.0.1:1234 \
1456 &gt; /storage/videos/screenstream.m3u
1457 &lt;/pre&gt;&lt;/blockquote&gt;
1458
1459 &lt;p&gt;Note the trick to pick a valid pulseaudio source. It might not
1460 pick the one you need. This approach will of course lead to trouble
1461 if more than one source uses the same multicast port and address.
1462 Note the ttl-mc=1 setting, which limit the multicast packages to the
1463 local network. If the value is increased, your screen will be
1464 broadcasted further, one network &quot;hop&quot; for each increase (read up on
1465 multicast to learn more. :)!&lt;/p&gt;
1466
1467 &lt;p&gt;Having cracked how to get Kodi to receive multicast streams, I
1468 could use this VLC command to stream to the same multicast address.
1469 The image quality is way better than the rtsp approach, but gstreamer
1470 seem to be doing a better job.&lt;/p&gt;
1471
1472 &lt;blockquote&gt;&lt;pre&gt;
1473 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;
1474 &lt;/pre&gt;&lt;/blockquote&gt;
1475
1476 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1477 activities, please send Bitcoin donations to my address
1478 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1479 </description>
1480 </item>
1481
1482 <item>
1483 <title>What is the most supported MIME type in Debian in 2018?</title>
1484 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</link>
1485 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html</guid>
1486 <pubDate>Mon, 9 Jul 2018 08:05:00 +0200</pubDate>
1487 <description>&lt;p&gt;Five years ago,
1488 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html&quot;&gt;I
1489 measured what the most supported MIME type in Debian was&lt;/a&gt;, by
1490 analysing the desktop files in all packages in the archive. Since
1491 then, the DEP-11 AppStream system has been put into production, making
1492 the task a lot easier. This made me want to repeat the measurement,
1493 to see how much things changed. Here are the new numbers, for
1494 unstable only this time:
1495
1496 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
1497
1498 &lt;pre&gt;
1499 count MIME type
1500 ----- -----------------------
1501 56 image/jpeg
1502 55 image/png
1503 49 image/tiff
1504 48 image/gif
1505 39 image/bmp
1506 38 text/plain
1507 37 audio/mpeg
1508 34 application/ogg
1509 33 audio/x-flac
1510 32 audio/x-mp3
1511 30 audio/x-wav
1512 30 audio/x-vorbis+ogg
1513 29 image/x-portable-pixmap
1514 27 inode/directory
1515 27 image/x-portable-bitmap
1516 27 audio/x-mpeg
1517 26 application/x-ogg
1518 25 audio/x-mpegurl
1519 25 audio/ogg
1520 24 text/html
1521 &lt;/pre&gt;
1522
1523 &lt;p&gt;The list was created like this using a sid chroot: &quot;cat
1524 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk &#39;/^
1525 - \S+\/\S+$/ {print $2 }&#39; | sort | uniq -c | sort -nr | head -20&quot;&lt;/p&gt;
1526
1527 &lt;p&gt;It is interesting to see how image formats have passed text/plain
1528 as the most announced supported MIME type. These days, thanks to the
1529 AppStream system, if you run into a file format you do not know, and
1530 want to figure out which packages support the format, you can find the
1531 MIME type of the file using &quot;file --mime &amp;lt;filename&amp;gt;&quot;, and then
1532 look up all packages announcing support for this format in their
1533 AppStream metadata (XML or .desktop file) using &quot;appstreamcli
1534 what-provides mimetype &amp;lt;mime-type&amp;gt;. For example if you, like
1535 me, want to know which packages support inode/directory, you can get a
1536 list like this:&lt;/p&gt;
1537
1538 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1539 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
1540 Package: anjuta
1541 Package: audacious
1542 Package: baobab
1543 Package: cervisia
1544 Package: chirp
1545 Package: dolphin
1546 Package: doublecmd-common
1547 Package: easytag
1548 Package: enlightenment
1549 Package: ephoto
1550 Package: filelight
1551 Package: gwenview
1552 Package: k4dirstat
1553 Package: kaffeine
1554 Package: kdesvn
1555 Package: kid3
1556 Package: kid3-qt
1557 Package: nautilus
1558 Package: nemo
1559 Package: pcmanfm
1560 Package: pcmanfm-qt
1561 Package: qweborf
1562 Package: ranger
1563 Package: sirikali
1564 Package: spacefm
1565 Package: spacefm
1566 Package: vifm
1567 %
1568 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1569
1570 &lt;p&gt;Using the same method, I can quickly discover that the Sketchup file
1571 format is not yet supported by any package in Debian:&lt;/p&gt;
1572
1573 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1574 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
1575 Could not find component providing &#39;mimetype::application/vnd.sketchup.skp&#39;.
1576 %
1577 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1578
1579 &lt;p&gt;Yesterday I used it to figure out which packages support the STL 3D
1580 format:&lt;/p&gt;
1581
1582 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1583 % appstreamcli what-provides mimetype application/sla|grep Package
1584 Package: cura
1585 Package: meshlab
1586 Package: printrun
1587 %
1588 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1589
1590 &lt;p&gt;PS: A new version of Cura was uploaded to Debian yesterday.&lt;/p&gt;
1591
1592 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1593 activities, please send Bitcoin donations to my address
1594 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1595 </description>
1596 </item>
1597
1598 <item>
1599 <title>Debian APT upgrade without enough free space on the disk...</title>
1600 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</link>
1601 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html</guid>
1602 <pubDate>Sun, 8 Jul 2018 12:10:00 +0200</pubDate>
1603 <description>&lt;p&gt;Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
1604 for a while, and when I need to update it there is not enough free
1605 space on the disk for apt to do a normal &#39;apt upgrade&#39;. I normally
1606 would resolve the issue by doing &#39;apt install &amp;lt;somepackages&amp;gt;&#39; to
1607 upgrade only some of the packages in one batch, until the amount of
1608 packages to download fall below the amount of free space available.
1609 Today, I had about 500 packages to upgrade, and after a while I got
1610 tired of trying to install chunks of packages manually. I concluded
1611 that I did not have the spare hours required to complete the task, and
1612 decided to see if I could automate it. I came up with this small
1613 script which I call &#39;apt-in-chunks&#39;:&lt;/p&gt;
1614
1615 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
1616 #!/bin/sh
1617 #
1618 # Upgrade packages when the disk is too full to upgrade every
1619 # upgradable package in one lump. Fetching packages to upgrade using
1620 # apt, and then installing using dpkg, to avoid changing the package
1621 # flag for manual/automatic.
1622
1623 set -e
1624
1625 ignore() {
1626 if [ &quot;$1&quot; ]; then
1627 grep -v &quot;$1&quot;
1628 else
1629 cat
1630 fi
1631 }
1632
1633 for p in $(apt list --upgradable | ignore &quot;$@&quot; |cut -d/ -f1 | grep -v &#39;^Listing...&#39;); do
1634 echo &quot;Upgrading $p&quot;
1635 apt clean
1636 apt install --download-only -y $p
1637 for f in /var/cache/apt/archives/*.deb; do
1638 if [ -e &quot;$f&quot; ]; then
1639 dpkg -i /var/cache/apt/archives/*.deb
1640 break
1641 fi
1642 done
1643 done
1644 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
1645
1646 &lt;p&gt;The script will extract the list of packages to upgrade, try to
1647 download the packages needed to upgrade one package, install the
1648 downloaded packages using dpkg. The idea is to upgrade packages
1649 without changing the APT mark for the package (ie the one recording of
1650 the package was manually requested or pulled in as a dependency). To
1651 use it, simply run it as root from the command line. If it fail, try
1652 &#39;apt install -f&#39; to clean up the mess and run the script again. This
1653 might happen if the new packages conflict with one of the old
1654 packages. dpkg is unable to remove, while apt can do this.&lt;/p&gt;
1655
1656 &lt;p&gt;It take one option, a package to ignore in the list of packages to
1657 upgrade. The option to ignore a package is there to be able to skip
1658 the packages that are simply too large to unpack. Today this was
1659 &#39;ghc&#39;, but I have run into other large packages causing similar
1660 problems earlier (like TeX).&lt;/p&gt;
1661
1662 &lt;p&gt;Update 2018-07-08: Thanks to Paul Wise, I am aware of two
1663 alternative ways to handle this. The &quot;unattended-upgrades
1664 --minimal-upgrade-steps&quot; option will try to calculate upgrade sets for
1665 each package to upgrade, and then upgrade them in order, smallest set
1666 first. It might be a better option than my above mentioned script.
1667 Also, &quot;aptutude upgrade&quot; can upgrade single packages, thus avoiding
1668 the need for using &quot;dpkg -i&quot; in the script above.&lt;/p&gt;
1669
1670 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1671 activities, please send Bitcoin donations to my address
1672 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1673 </description>
1674 </item>
1675
1676 <item>
1677 <title>Version 3.1 of Cura, the 3D print slicer, is now in Debian</title>
1678 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</link>
1679 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html</guid>
1680 <pubDate>Tue, 13 Feb 2018 06:20:00 +0100</pubDate>
1681 <description>&lt;p&gt;A new version of the
1682 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;3D printer slicer
1683 software Cura&lt;/a&gt;, version 3.1.0, is now available in Debian Testing
1684 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
1685 useful. It was uploaded the last few days, and the last update will
1686 enter testing tomorrow. See the
1687 &lt;a href=&quot;https://ultimaker.com/en/products/cura-software/release-notes&quot;&gt;release
1688 notes&lt;/a&gt; for the list of bug fixes and new features. Version 3.2
1689 was announced 6 days ago. We will try to get it into Debian as
1690 well.&lt;/p&gt;
1691
1692 &lt;p&gt;More information related to 3D printing is available on the
1693 &lt;a href=&quot;https://wiki.debian.org/3DPrinting&quot;&gt;3D printing&lt;/a&gt; and
1694 &lt;a href=&quot;https://wiki.debian.org/3D-printer&quot;&gt;3D printer&lt;/a&gt; wiki pages
1695 in Debian.&lt;/p&gt;
1696
1697 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1698 activities, please send Bitcoin donations to my address
1699 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1700 </description>
1701 </item>
1702
1703 <item>
1704 <title>Cura, the nice 3D print slicer, is now in Debian Unstable</title>
1705 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</link>
1706 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html</guid>
1707 <pubDate>Sun, 17 Dec 2017 07:00:00 +0100</pubDate>
1708 <description>&lt;p&gt;After several months of working and waiting, I am happy to report
1709 that the nice and user friendly 3D printer slicer software Cura just
1710 entered Debian Unstable. It consist of five packages,
1711 &lt;a href=&quot;https://tracker.debian.org/pkg/cura&quot;&gt;cura&lt;/a&gt;,
1712 &lt;a href=&quot;https://tracker.debian.org/pkg/cura-engine&quot;&gt;cura-engine&lt;/a&gt;,
1713 &lt;a href=&quot;https://tracker.debian.org/pkg/libarcus&quot;&gt;libarcus&lt;/a&gt;,
1714 &lt;a href=&quot;https://tracker.debian.org/pkg/fdm-materials&quot;&gt;fdm-materials&lt;/a&gt;,
1715 &lt;a href=&quot;https://tracker.debian.org/pkg/libsavitar&quot;&gt;libsavitar&lt;/a&gt; and
1716 &lt;a href=&quot;https://tracker.debian.org/pkg/uranium&quot;&gt;uranium&lt;/a&gt;. The last
1717 two, uranium and cura, entered Unstable yesterday. This should make
1718 it easier for Debian users to print on at least the Ultimaker class of
1719 3D printers. My nearest 3D printer is an Ultimaker 2+, so it will
1720 make life easier for at least me. :)&lt;/p&gt;
1721
1722 &lt;p&gt;The work to make this happen was done by Gregor Riepl, and I was
1723 happy to assist him in sponsoring the packages. With the introduction
1724 of Cura, Debian is up to three 3D printer slicers at your service,
1725 Cura, Slic3r and Slic3r Prusa. If you own or have access to a 3D
1726 printer, give it a go. :)&lt;/p&gt;
1727
1728 &lt;p&gt;The 3D printer software is maintained by the 3D printer Debian
1729 team, flocking together on the
1730 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/3dprinter-general&quot;&gt;3dprinter-general&lt;/a&gt;
1731 mailing list and the
1732 &lt;a href=&quot;irc://irc.debian.org/#debian-3dprinting&quot;&gt;#debian-3dprinting&lt;/a&gt;
1733 IRC channel.&lt;/p&gt;
1734
1735 &lt;p&gt;The next step for Cura in Debian is to update the cura package to
1736 version 3.0.3 and then update the entire set of packages to version
1737 3.1.0 which showed up the last few days.&lt;/p&gt;
1738 </description>
1739 </item>
1740
1741 <item>
1742 <title>Generating 3D prints in Debian using Cura and Slic3r(-prusa)</title>
1743 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</link>
1744 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html</guid>
1745 <pubDate>Mon, 9 Oct 2017 10:50:00 +0200</pubDate>
1746 <description>&lt;p&gt;At my nearby maker space,
1747 &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Sonen&lt;/a&gt;, I heard the story that it
1748 was easier to generate gcode files for theyr 3D printers (Ultimake 2+)
1749 on Windows and MacOS X than Linux, because the software involved had
1750 to be manually compiled and set up on Linux while premade packages
1751 worked out of the box on Windows and MacOS X. I found this annoying,
1752 as the software involved,
1753 &lt;a href=&quot;https://github.com/Ultimaker/Cura&quot;&gt;Cura&lt;/a&gt;, is free software
1754 and should be trivial to get up and running on Linux if someone took
1755 the time to package it for the relevant distributions. I even found
1756 &lt;a href=&quot;https://bugs.debian.org/706656&quot;&gt;a request for adding into
1757 Debian&lt;/a&gt; from 2013, which had seem some activity over the years but
1758 never resulted in the software showing up in Debian. So a few days
1759 ago I offered my help to try to improve the situation.&lt;/p&gt;
1760
1761 &lt;p&gt;Now I am very happy to see that all the packages required by a
1762 working Cura in Debian are uploaded into Debian and waiting in the NEW
1763 queue for the ftpmasters to have a look. You can track the progress
1764 on
1765 &lt;a href=&quot;https://qa.debian.org/developer.php?email=3dprinter-general%40lists.alioth.debian.org&quot;&gt;the
1766 status page for the 3D printer team&lt;/a&gt;.&lt;/p&gt;
1767
1768 &lt;p&gt;The uploaded packages are a bit behind upstream, and was uploaded
1769 now to get slots in &lt;a href=&quot;https://ftp-master.debian.org/new.html&quot;&gt;the NEW
1770 queue&lt;/a&gt; while we work up updating the packages to the latest
1771 upstream version.&lt;/p&gt;
1772
1773 &lt;p&gt;On a related note, two competitors for Cura, which I found harder
1774 to use and was unable to configure correctly for Ultimaker 2+ in the
1775 short time I spent on it, are already in Debian. If you are looking
1776 for 3D printer &quot;slicers&quot; and want something already available in
1777 Debian, check out
1778 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r&quot;&gt;slic3r&lt;/a&gt; and
1779 &lt;a href=&quot;https://tracker.debian.org/pkg/slic3r-prusa&quot;&gt;slic3r-prusa&lt;/a&gt;.
1780 The latter is a fork of the former.&lt;/p&gt;
1781
1782 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
1783 activities, please send Bitcoin donations to my address
1784 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
1785 </description>
1786 </item>
1787
1788 <item>
1789 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass</title>
1790 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</link>
1791 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html</guid>
1792 <pubDate>Fri, 29 Sep 2017 10:30:00 +0200</pubDate>
1793 <description>&lt;p&gt;Every mobile phone announce its existence over radio to the nearby
1794 mobile cell towers. And this radio chatter is available for anyone
1795 with a radio receiver capable of receiving them. Details about the
1796 mobile phones with very good accuracy is of course collected by the
1797 phone companies, but this is not the topic of this blog post. The
1798 mobile phone radio chatter make it possible to figure out when a cell
1799 phone is nearby, as it include the SIM card ID (IMSI). By paying
1800 attention over time, one can see when a phone arrive and when it leave
1801 an area. I believe it would be nice to make this information more
1802 available to the general public, to make more people aware of how
1803 their phones are announcing their whereabouts to anyone that care to
1804 listen.&lt;/p&gt;
1805
1806 &lt;p&gt;I am very happy to report that we managed to get something
1807 visualizing this information up and running for
1808 &lt;a href=&quot;http://norwaymakers.org/osf17&quot;&gt;Oslo Skaperfestival 2017&lt;/a&gt;
1809 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
1810 library. The solution is based on the
1811 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html&quot;&gt;simple
1812 recipe for listening to GSM chatter&lt;/a&gt; I posted a few days ago, and
1813 will show up at the stand of &lt;a href=&quot;http://sonen.ifi.uio.no/&quot;&gt;Åpen
1814 Sone from the Computer Science department of the University of
1815 Oslo&lt;/a&gt;. The presentation will show the nearby mobile phones (aka
1816 IMSIs) as dots in a web browser graph, with lines to the dot
1817 representing mobile base station it is talking to. It was working in
1818 the lab yesterday, and was moved into place this morning.&lt;/p&gt;
1819
1820 &lt;p&gt;We set up a fairly powerful desktop machine using Debian
1821 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
1822 connected and visualize the visible cell phone towers using an
1823 &lt;a href=&quot;https://github.com/marlow925/hopglass&quot;&gt;English version of
1824 Hopglass&lt;/a&gt;. A fairly powerfull machine is needed as the
1825 grgsm_livemon_headless processes from
1826 &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt; converting
1827 the radio signal to data packages is quite CPU intensive.&lt;/p&gt;
1828
1829 &lt;p&gt;The frequencies to listen to, are identified using a slightly
1830 patched scan-and-livemon (to set the --args values for each receiver),
1831 and the Hopglass data is generated using the
1832 &lt;a href=&quot;https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output&quot;&gt;patches
1833 in my meshviewer-output branch&lt;/a&gt;. For some reason we could not get
1834 more than four SDRs working. There is also a geographical map trying
1835 to show the location of the base stations, but I believe their
1836 coordinates are hardcoded to some random location in Germany, I
1837 believe. The code should be replaced with code to look up location in
1838 a text file, a sqlite database or one of the online databases
1839 mentioned in
1840 &lt;a href=&quot;https://github.com/Oros42/IMSI-catcher/issues/14&quot;&gt;the github
1841 issue for the topic&lt;/a&gt;.
1842
1843 &lt;p&gt;If this sound interesting, visit the stand at the festival!&lt;/p&gt;
1844 </description>
1845 </item>
1846
1847 <item>
1848 <title>Easier recipe to observe the cell phones around you</title>
1849 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</link>
1850 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html</guid>
1851 <pubDate>Sun, 24 Sep 2017 08:30:00 +0200</pubDate>
1852 <description>&lt;p&gt;A little more than a month ago I wrote
1853 &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
1854 to observe the SIM card ID (aka IMSI number) of mobile phones talking
1855 to nearby mobile phone base stations using Debian GNU/Linux and a
1856 cheap USB software defined radio&lt;/a&gt;, and thus being able to pinpoint
1857 the location of people and equipment (like cars and trains) with an
1858 accuracy of a few kilometer. Since then we have worked to make the
1859 procedure even simpler, and it is now possible to do this without any
1860 manual frequency tuning and without building your own packages.&lt;/p&gt;
1861
1862 &lt;p&gt;The &lt;a href=&quot;https://tracker.debian.org/pkg/gr-gsm&quot;&gt;gr-gsm&lt;/a&gt;
1863 package is now included in Debian testing and unstable, and the
1864 IMSI-catcher code no longer require root access to fetch and decode
1865 the GSM data collected using gr-gsm.&lt;/p&gt;
1866
1867 &lt;p&gt;Here is an updated recipe, using packages built by Debian and a git
1868 clone of two python scripts:&lt;/p&gt;
1869
1870 &lt;ol&gt;
1871
1872 &lt;li&gt;Start with a Debian machine running the Buster version (aka
1873 testing).&lt;/li&gt;
1874
1875 &lt;li&gt;Run &#39;&lt;tt&gt;apt install gr-gsm python-numpy python-scipy
1876 python-scapy&lt;/tt&gt;&#39; as root to install required packages.&lt;/li&gt;
1877
1878 &lt;li&gt;Fetch the code decoding GSM packages using &#39;&lt;tt&gt;git clone
1879 github.com/Oros42/IMSI-catcher.git&lt;/tt&gt;&#39;.&lt;/li&gt;
1880
1881 &lt;li&gt;Insert USB software defined radio supported by GNU Radio.&lt;/li&gt;
1882
1883 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
1884 scan-and-livemon&lt;/tt&gt;&#39; to locate the frequency of nearby base
1885 stations and start listening for GSM packages on one of them.&lt;/li&gt;
1886
1887 &lt;li&gt;Enter the IMSI-catcher directory and run &#39;&lt;tt&gt;python
1888 simple_IMSI-catcher.py&lt;/tt&gt;&#39; to display the collected information.&lt;/li&gt;
1889
1890 &lt;/ol&gt;
1891
1892 &lt;p&gt;Note, due to a bug somewhere the scan-and-livemon program (actually
1893 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/issues/336&quot;&gt;its underlying
1894 program grgsm_scanner&lt;/a&gt;) do not work with the HackRF radio. It does
1895 work with RTL 8232 and other similar USB radio receivers you can get
1896 very cheaply
1897 (&lt;a href=&quot;https://www.ebay.com/sch/items/?_nkw=rtl+2832&quot;&gt;for example
1898 from ebay&lt;/a&gt;), so for now the solution is to scan using the RTL radio
1899 and only use HackRF for fetching GSM data.&lt;/p&gt;
1900
1901 &lt;p&gt;As far as I can tell, a cell phone only show up on one of the
1902 frequencies at the time, so if you are going to track and count every
1903 cell phone around you, you need to listen to all the frequencies used.
1904 To listen to several frequencies, use the --numrecv argument to
1905 scan-and-livemon to use several receivers. Further, I am not sure if
1906 phones using 3G or 4G will show as talking GSM to base stations, so
1907 this approach might not see all phones around you. I typically see
1908 0-400 IMSI numbers an hour when looking around where I live.&lt;/p&gt;
1909
1910 &lt;p&gt;I&#39;ve tried to run the scanner on a
1911 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi 2 and 3
1912 running Debian Buster&lt;/a&gt;, but the grgsm_livemon_headless process seem
1913 to be too CPU intensive to keep up. When GNU Radio print &#39;O&#39; to
1914 stdout, I am told there it is caused by a buffer overflow between the
1915 radio and GNU Radio, caused by the program being unable to read the
1916 GSM data fast enough. If you see a stream of &#39;O&#39;s from the terminal
1917 where you started scan-and-livemon, you need a give the process more
1918 CPU power. Perhaps someone are able to optimize the code to a point
1919 where it become possible to set up RPi3 based GSM sniffers? I tried
1920 using Raspbian instead of Debian, but there seem to be something wrong
1921 with GNU Radio on raspbian, causing glibc to abort().&lt;/p&gt;
1922 </description>
1923 </item>
1924
1925 <item>
1926 <title>Simpler recipe on how to make a simple $7 IMSI Catcher using Debian</title>
1927 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</link>
1928 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html</guid>
1929 <pubDate>Wed, 9 Aug 2017 23:59:00 +0200</pubDate>
1930 <description>&lt;p&gt;On friday, I came across an interesting article in the Norwegian
1931 web based ICT news magazine digi.no on
1932 &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
1933 to collect the IMSI numbers of nearby cell phones&lt;/a&gt; using the cheap
1934 DVB-T software defined radios. The article refered to instructions
1935 and &lt;a href=&quot;https://www.youtube.com/watch?v=UjwgNd_as30&quot;&gt;a recipe by
1936 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;
1937
1938 &lt;p&gt;The instructions said to use Ubuntu, install pip using apt (to
1939 bypass apt), use pip to install pybombs (to bypass both apt and pip),
1940 and the ask pybombs to fetch and build everything you need from
1941 scratch. I wanted to see if I could do the same on the most recent
1942 Debian packages, but this did not work because pybombs tried to build
1943 stuff that no longer build with the most recent openssl library or
1944 some other version skew problem. While trying to get this recipe
1945 working, I learned that the apt-&gt;pip-&gt;pybombs route was a long detour,
1946 and the only piece of software dependency missing in Debian was the
1947 gr-gsm package. I also found out that the lead upstream developer of
1948 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
1949 Debian packages provided in an Ubuntu PPA repository. All I needed to
1950 do was to dget the Debian source package and built it.&lt;/p&gt;
1951
1952 &lt;p&gt;The IMSI collector is a python script listening for packages on the
1953 loopback network device and printing to the terminal some specific GSM
1954 packages with IMSI numbers in them. The code is fairly short and easy
1955 to understand. The reason this work is because gr-gsm include a tool
1956 to read GSM data from a software defined radio like a DVB-T USB stick
1957 and other software defined radios, decode them and inject them into a
1958 network device on your Linux machine (using the loopback device by
1959 default). This proved to work just fine, and I&#39;ve been testing the
1960 collector for a few days now.&lt;/p&gt;
1961
1962 &lt;p&gt;The updated and simpler recipe is thus to&lt;/p&gt;
1963
1964 &lt;ol&gt;
1965
1966 &lt;li&gt;start with a Debian machine running Stretch or newer,&lt;/li&gt;
1967
1968 &lt;li&gt;build and install the gr-gsm package available from
1969 &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;
1970
1971 &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;
1972
1973 &lt;li&gt;run grgsm_livemon and adjust the frequency until the terminal
1974 where it was started is filled with a stream of text (meaning you
1975 found a GSM station).&lt;/li&gt;
1976
1977 &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;
1978
1979 &lt;/ol&gt;
1980
1981 &lt;p&gt;To make it even easier in the future to get this sniffer up and
1982 running, I decided to package
1983 &lt;a href=&quot;https://github.com/ptrkrysik/gr-gsm/&quot;&gt;the gr-gsm project&lt;/a&gt;
1984 for Debian (&lt;a href=&quot;https://bugs.debian.org/871055&quot;&gt;WNPP
1985 #871055&lt;/a&gt;), and the package was uploaded into the NEW queue today.
1986 Luckily the gnuradio maintainer has promised to help me, as I do not
1987 know much about gnuradio stuff yet.&lt;/p&gt;
1988
1989 &lt;p&gt;I doubt this &quot;IMSI cacher&quot; is anywhere near as powerfull as
1990 commercial tools like
1991 &lt;a href=&quot;https://www.thespyphone.com/portable-imsi-imei-catcher/&quot;&gt;The
1992 Spy Phone Portable IMSI / IMEI Catcher&lt;/a&gt; or the
1993 &lt;a href=&quot;https://en.wikipedia.org/wiki/Stingray_phone_tracker&quot;&gt;Harris
1994 Stingray&lt;/a&gt;, but I hope the existance of cheap alternatives can make
1995 more people realise how their whereabouts when carrying a cell phone
1996 is easily tracked. Seeing the data flow on the screen, realizing that
1997 I live close to a police station and knowing that the police is also
1998 wearing cell phones, I wonder how hard it would be for criminals to
1999 track the position of the police officers to discover when there are
2000 police near by, or for foreign military forces to track the location
2001 of the Norwegian military forces, or for anyone to track the location
2002 of government officials...&lt;/p&gt;
2003
2004 &lt;p&gt;It is worth noting that the data reported by the IMSI-catcher
2005 script mentioned above is only a fraction of the data broadcasted on
2006 the GSM network. It will only collect one frequency at the time,
2007 while a typical phone will be using several frequencies, and not all
2008 phones will be using the frequencies tracked by the grgsm_livemod
2009 program. Also, there is a lot of radio chatter being ignored by the
2010 simple_IMSI-catcher script, which would be collected by extending the
2011 parser code. I wonder if gr-gsm can be set up to listen to more than
2012 one frequency?&lt;/p&gt;
2013 </description>
2014 </item>
2015
2016 <item>
2017 <title>Norwegian Bokmål edition of Debian Administrator&#39;s Handbook is now available</title>
2018 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</link>
2019 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html</guid>
2020 <pubDate>Tue, 25 Jul 2017 21:10:00 +0200</pubDate>
2021 <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;
2022
2023 &lt;p&gt;I finally received a copy of the Norwegian Bokmål edition of
2024 &quot;&lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian Administrator&#39;s
2025 Handbook&lt;/a&gt;&quot;. This test copy arrived in the mail a few days ago, and
2026 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2027 &lt;a href=&quot;https://debian-handbook.info/get/#norwegian&quot;&gt;is available
2028 from lulu.com&lt;/a&gt;. If you buy it quickly, you save 25% on the list
2029 price. The book is also available for download in electronic form as
2030 PDF, EPUB and Mobipocket, as can be
2031 &lt;a href=&quot;https://debian-handbook.info/browse/nb-NO/stable/&quot;&gt;read online
2032 as a web page&lt;/a&gt;.&lt;/p&gt;
2033
2034 &lt;p&gt;This is the second book I publish (the first was the book
2035 &quot;&lt;a href=&quot;http://free-culture.cc/&quot;&gt;Free Culture&lt;/a&gt;&quot; by Lawrence Lessig
2036 in
2037 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-22440520.html&quot;&gt;English&lt;/a&gt;,
2038 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-22645082.html&quot;&gt;French&lt;/a&gt;
2039 and
2040 &lt;a href=&quot;http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-22441576.html&quot;&gt;Norwegian
2041 Bokmål&lt;/a&gt;), and I am very excited to finally wrap up this
2042 project. I hope
2043 &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
2044 for Debian-administratoren&lt;/a&gt;&quot; will be well received.&lt;/p&gt;
2045 </description>
2046 </item>
2047
2048 <item>
2049 <title>Når nynorskoversettelsen svikter til eksamen...</title>
2050 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</link>
2051 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html</guid>
2052 <pubDate>Sat, 3 Jun 2017 08:20:00 +0200</pubDate>
2053 <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
2054 melder i dag&lt;/a&gt; om feil i eksamensoppgavene for eksamen i politikk og
2055 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2056 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2057 på om den fri oversetterløsningen
2058 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium&lt;/a&gt; ville gjort en bedre
2059 jobb enn Utdanningsdirektoratet. Det kan se slik ut.&lt;/p&gt;
2060
2061 &lt;p&gt;Her er bokmålsoppgaven fra eksamenen:&lt;/p&gt;
2062
2063 &lt;blockquote&gt;
2064 &lt;p&gt;Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2065 rolle og muligheter til å håndtere internasjonale utfordringer, som
2066 for eksempel flykningekrisen.&lt;/p&gt;
2067
2068 &lt;p&gt;Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2069 på temaet:&lt;/p&gt;
2070 &lt;ol&gt;
2071 &lt;li&gt;Flykningeregnskapet 2016, UNHCR og IDMC
2072 &lt;li&gt;«Grenseløst Europa for fall» A-Magasinet, 26. november 2015
2073 &lt;/ol&gt;
2074
2075 &lt;/blockquote&gt;
2076
2077 &lt;p&gt;Dette oversetter Apertium slik:&lt;/p&gt;
2078
2079 &lt;blockquote&gt;
2080 &lt;p&gt;Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2081 andre aktørar og høve til å handtera internasjonale utfordringar, som
2082 til dømes *flykningekrisen.&lt;/p&gt;
2083
2084 &lt;p&gt;Vedleggja er døme på tekster som kan gje relevante perspektiv på
2085 temaet:&lt;/p&gt;
2086
2087 &lt;ol&gt;
2088 &lt;li&gt;*Flykningeregnskapet 2016, *UNHCR og *IDMC&lt;/li&gt;
2089 &lt;li&gt;«*Grenseløst Europa for fall» A-Magasinet, 26. november 2015&lt;/li&gt;
2090 &lt;/ol&gt;
2091
2092 &lt;/blockquote&gt;
2093
2094 &lt;p&gt;Ord som ikke ble forstått er markert med stjerne (*), og trenger
2095 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2096 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2097 &quot;andre aktørers rolle og muligheter til ...&quot; burde vært oversatt til
2098 &quot;rolla til andre aktørar og deira høve til ...&quot; eller noe slikt, men
2099 det er kanskje flisespikking. Det understreker vel bare at det alltid
2100 trengs korrekturlesning etter automatisk oversettelse.&lt;/p&gt;
2101 </description>
2102 </item>
2103
2104 <item>
2105 <title>Detecting NFS hangs on Linux without hanging yourself...</title>
2106 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</link>
2107 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html</guid>
2108 <pubDate>Thu, 9 Mar 2017 15:20:00 +0100</pubDate>
2109 <description>&lt;p&gt;Over the years, administrating thousand of NFS mounting linux
2110 computers at the time, I often needed a way to detect if the machine
2111 was experiencing NFS hang. If you try to use &lt;tt&gt;df&lt;/tt&gt; or look at a
2112 file or directory affected by the hang, the process (and possibly the
2113 shell) will hang too. So you want to be able to detect this without
2114 risking the detection process getting stuck too. It has not been
2115 obvious how to do this. When the hang has lasted a while, it is
2116 possible to find messages like these in dmesg:&lt;/p&gt;
2117
2118 &lt;p&gt;&lt;blockquote&gt;
2119 nfs: server nfsserver not responding, still trying
2120 &lt;br&gt;nfs: server nfsserver OK
2121 &lt;/blockquote&gt;&lt;/p&gt;
2122
2123 &lt;p&gt;It is hard to know if the hang is still going on, and it is hard to
2124 be sure looking in dmesg is going to work. If there are lots of other
2125 messages in dmesg the lines might have rotated out of site before they
2126 are noticed.&lt;/p&gt;
2127
2128 &lt;p&gt;While reading through the nfs client implementation in linux kernel
2129 code, I came across some statistics that seem to give a way to detect
2130 it. The om_timeouts sunrpc value in the kernel will increase every
2131 time the above log entry is inserted into dmesg. And after digging a
2132 bit further, I discovered that this value show up in
2133 /proc/self/mountstats on Linux.&lt;/p&gt;
2134
2135 &lt;p&gt;The mountstats content seem to be shared between files using the
2136 same file system context, so it is enough to check one of the
2137 mountstats files to get the state of the mount point for the machine.
2138 I assume this will not show lazy umounted NFS points, nor NFS mount
2139 points in a different process context (ie with a different filesystem
2140 view), but that does not worry me.&lt;/p&gt;
2141
2142 &lt;p&gt;The content for a NFS mount point look similar to this:&lt;/p&gt;
2143
2144 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
2145 [...]
2146 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2147 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=1.1
2148 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
2149 age: 7863311
2150 caps: caps=0x3fe7,wtmult=4096,dtsize=8192,bsize=0,namlen=255
2151 sec: flavor=1,pseudoflavor=1
2152 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
2153 bytes: 166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2154 RPC iostats version: 1.0 p/v: 100003/3 (nfs)
2155 xprt: tcp 925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
2156 per-op statistics
2157 NULL: 0 0 0 0 0 0 0 0
2158 GETATTR: 61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
2159 SETATTR: 463469 463470 0 92005440 66739536 63787 603235 687943
2160 LOOKUP: 17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
2161 ACCESS: 14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
2162 READLINK: 125 125 0 20472 18620 0 1112 1118
2163 READ: 4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
2164 WRITE: 8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
2165 CREATE: 171708 171708 0 38084748 46702272 873 1041833 1050398
2166 MKDIR: 3680 3680 0 773980 993920 26 23990 24245
2167 SYMLINK: 903 903 0 233428 245488 6 5865 5917
2168 MKNOD: 80 80 0 20148 21760 0 299 304
2169 REMOVE: 429921 429921 0 79796004 61908192 3313 2710416 2741636
2170 RMDIR: 3367 3367 0 645112 484848 22 5782 6002
2171 RENAME: 466201 466201 0 130026184 121212260 7075 5935207 5961288
2172 LINK: 289155 289155 0 72775556 67083960 2199 2565060 2585579
2173 READDIR: 2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
2174 READDIRPLUS: 1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
2175 FSSTAT: 6144 6144 0 1010516 1032192 51 9654 10022
2176 FSINFO: 2 2 0 232 328 0 1 1
2177 PATHCONF: 1 1 0 116 140 0 0 0
2178 COMMIT: 0 0 0 0 0 0 0 0
2179
2180 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
2181 [...]
2182 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
2183
2184 &lt;p&gt;The key number to look at is the third number in the per-op list.
2185 It is the number of NFS timeouts experiences per file system
2186 operation. Here 22 write timeouts and 5 access timeouts. If these
2187 numbers are increasing, I believe the machine is experiencing NFS
2188 hang. Unfortunately the timeout value do not start to increase right
2189 away. The NFS operations need to time out first, and this can take a
2190 while. The exact timeout value depend on the setup. For example the
2191 defaults for TCP and UDP mount points are quite different, and the
2192 timeout value is affected by the soft, hard, timeo and retrans NFS
2193 mount options.&lt;/p&gt;
2194
2195 &lt;p&gt;The only way I have been able to get working on Debian and RedHat
2196 Enterprise Linux for getting the timeout count is to peek in /proc/.
2197 But according to
2198 &lt;ahref=&quot;http://docs.oracle.com/cd/E19253-01/816-4555/netmonitor-12/index.html&quot;&gt;Solaris
2199 10 System Administration Guide: Network Services&lt;/a&gt;, the &#39;nfsstat -c&#39;
2200 command can be used to get these timeout values. But this do not work
2201 on Linux, as far as I can tell. I
2202 &lt;ahref=&quot;http://bugs.debian.org/857043&quot;&gt;asked Debian about this&lt;/a&gt;,
2203 but have not seen any replies yet.&lt;/p&gt;
2204
2205 &lt;p&gt;Is there a better way to figure out if a Linux NFS client is
2206 experiencing NFS hangs? Is there a way to detect which processes are
2207 affected? Is there a way to get the NFS mount going quickly once the
2208 network problem causing the NFS hang has been cleared? I would very
2209 much welcome some clues, as we regularly run into NFS hangs.&lt;/p&gt;
2210 </description>
2211 </item>
2212
2213 <item>
2214 <title>Norwegian Bokmål translation of The Debian Administrator&#39;s Handbook complete, proofreading in progress</title>
2215 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html</link>
2216 <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>
2217 <pubDate>Fri, 3 Mar 2017 14:50:00 +0100</pubDate>
2218 <description>&lt;p&gt;For almost a year now, we have been working on making a Norwegian
2219 Bokmål edition of &lt;a href=&quot;https://debian-handbook.info/&quot;&gt;The Debian
2220 Administrator&#39;s Handbook&lt;/a&gt;. Now, thanks to the tireless effort of
2221 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
2222 we are working on the proof reading to ensure consistent language and
2223 use of correct computer science terms. The plan is to make the book
2224 available on paper, as well as in electronic form. For that to
2225 happen, the proof reading must be completed and all the figures need
2226 to be translated. If you want to help out, get in touch.&lt;/p&gt;
2227
2228 &lt;p&gt;&lt;a href=&quot;http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf&quot;&gt;A
2229
2230 fresh PDF edition&lt;/a&gt; in A4 format (the final book will have smaller
2231 pages) of the book created every morning is available for
2232 proofreading. If you find any errors, please
2233 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;visit
2234 Weblate and correct the error&lt;/a&gt;. The
2235 &lt;a href=&quot;http://l.github.io/debian-handbook/stat/nb-NO/index.html&quot;&gt;state
2236 of the translation including figures&lt;/a&gt; is a useful source for those
2237 provide Norwegian bokmål screen shots and figures.&lt;/p&gt;
2238 </description>
2239 </item>
2240
2241 <item>
2242 <title>Unlimited randomness with the ChaosKey?</title>
2243 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</link>
2244 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html</guid>
2245 <pubDate>Wed, 1 Mar 2017 20:50:00 +0100</pubDate>
2246 <description>&lt;p&gt;A few days ago I ordered a small batch of
2247 &lt;a href=&quot;http://altusmetrum.org/ChaosKey/&quot;&gt;the ChaosKey&lt;/a&gt;, a small
2248 USB dongle for generating entropy created by Bdale Garbee and Keith
2249 Packard. Yesterday it arrived, and I am very happy to report that it
2250 work great! According to its designers, to get it to work out of the
2251 box, you need the Linux kernel version 4.1 or later. I tested on a
2252 Debian Stretch machine (kernel version 4.9), and there it worked just
2253 fine, increasing the available entropy very quickly. I wrote a small
2254 test oneliner to test. It first print the current entropy level,
2255 drain /dev/random, and then print the entropy level for five seconds.
2256 Here is the situation without the ChaosKey inserted:&lt;/p&gt;
2257
2258 &lt;blockquote&gt;&lt;pre&gt;
2259 % cat /proc/sys/kernel/random/entropy_avail; \
2260 dd bs=1M if=/dev/random of=/dev/null count=1; \
2261 for n in $(seq 1 5); do \
2262 cat /proc/sys/kernel/random/entropy_avail; \
2263 sleep 1; \
2264 done
2265 300
2266 0+1 oppføringer inn
2267 0+1 oppføringer ut
2268 28 byte kopiert, 0,000264565 s, 106 kB/s
2269 4
2270 8
2271 12
2272 17
2273 21
2274 %
2275 &lt;/pre&gt;&lt;/blockquote&gt;
2276
2277 &lt;p&gt;The entropy level increases by 3-4 every second. In such case any
2278 application requiring random bits (like a HTTPS enabled web server)
2279 will halt and wait for more entrpy. And here is the situation with
2280 the ChaosKey inserted:&lt;/p&gt;
2281
2282 &lt;blockquote&gt;&lt;pre&gt;
2283 % cat /proc/sys/kernel/random/entropy_avail; \
2284 dd bs=1M if=/dev/random of=/dev/null count=1; \
2285 for n in $(seq 1 5); do \
2286 cat /proc/sys/kernel/random/entropy_avail; \
2287 sleep 1; \
2288 done
2289 1079
2290 0+1 oppføringer inn
2291 0+1 oppføringer ut
2292 104 byte kopiert, 0,000487647 s, 213 kB/s
2293 433
2294 1028
2295 1031
2296 1035
2297 1038
2298 %
2299 &lt;/pre&gt;&lt;/blockquote&gt;
2300
2301 &lt;p&gt;Quite the difference. :) I bought a few more than I need, in case
2302 someone want to buy one here in Norway. :)&lt;/p&gt;
2303
2304 &lt;p&gt;Update: The dongle was presented at Debconf last year. You might
2305 find &lt;a href=&quot;https://debconf16.debconf.org/talks/94/&quot;&gt;the talk
2306 recording illuminating&lt;/a&gt;. It explains exactly what the source of
2307 randomness is, if you are unable to spot it from the schema drawing
2308 available from the ChaosKey web site linked at the start of this blog
2309 post.&lt;/p&gt;
2310 </description>
2311 </item>
2312
2313 <item>
2314 <title>Where did that package go? &amp;mdash; geolocated IP traceroute</title>
2315 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</link>
2316 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html</guid>
2317 <pubDate>Mon, 9 Jan 2017 12:20:00 +0100</pubDate>
2318 <description>&lt;p&gt;Did you ever wonder where the web trafic really flow to reach the
2319 web servers, and who own the network equipment it is flowing through?
2320 It is possible to get a glimpse of this from using traceroute, but it
2321 is hard to find all the details. Many years ago, I wrote a system to
2322 map the Norwegian Internet (trying to figure out if our plans for a
2323 network game service would get low enough latency, and who we needed
2324 to talk to about setting up game servers close to the users. Back
2325 then I used traceroute output from many locations (I asked my friends
2326 to run a script and send me their traceroute output) to create the
2327 graph and the map. The output from traceroute typically look like
2328 this:
2329
2330 &lt;p&gt;&lt;pre&gt;
2331 traceroute to www.stortinget.no (85.88.67.10), 30 hops max, 60 byte packets
2332 1 uio-gw10.uio.no (129.240.202.1) 0.447 ms 0.486 ms 0.621 ms
2333 2 uio-gw8.uio.no (129.240.24.229) 0.467 ms 0.578 ms 0.675 ms
2334 3 oslo-gw1.uninett.no (128.39.65.17) 0.385 ms 0.373 ms 0.358 ms
2335 4 te3-1-2.br1.fn3.as2116.net (193.156.90.3) 1.174 ms 1.172 ms 1.153 ms
2336 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
2337 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
2338 7 89.191.10.146 (89.191.10.146) 0.931 ms 0.917 ms 0.955 ms
2339 8 * * *
2340 9 * * *
2341 [...]
2342 &lt;/pre&gt;&lt;/p&gt;
2343
2344 &lt;p&gt;This show the DNS names and IP addresses of (at least some of the)
2345 network equipment involved in getting the data traffic from me to the
2346 www.stortinget.no server, and how long it took in milliseconds for a
2347 package to reach the equipment and return to me. Three packages are
2348 sent, and some times the packages do not follow the same path. This
2349 is shown for hop 5, where three different IP addresses replied to the
2350 traceroute request.&lt;/p&gt;
2351
2352 &lt;p&gt;There are many ways to measure trace routes. Other good traceroute
2353 implementations I use are traceroute (using ICMP packages) mtr (can do
2354 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
2355 traceroute and a lot of other capabilities). All of them are easily
2356 available in &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt;.&lt;/p&gt;
2357
2358 &lt;p&gt;This time around, I wanted to know the geographic location of
2359 different route points, to visualize how visiting a web page spread
2360 information about the visit to a lot of servers around the globe. The
2361 background is that a web site today often will ask the browser to get
2362 from many servers the parts (for example HTML, JSON, fonts,
2363 JavaScript, CSS, video) required to display the content. This will
2364 leak information about the visit to those controlling these servers
2365 and anyone able to peek at the data traffic passing by (like your ISP,
2366 the ISPs backbone provider, FRA, GCHQ, NSA and others).&lt;/p&gt;
2367
2368 &lt;p&gt;Lets pick an example, the Norwegian parliament web site
2369 www.stortinget.no. It is read daily by all members of parliament and
2370 their staff, as well as political journalists, activits and many other
2371 citizens of Norway. A visit to the www.stortinget.no web site will
2372 ask your browser to contact 8 other servers: ajax.googleapis.com,
2373 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
2374 stats.g.doubleclick.net, www.google-analytics.com,
2375 www.googletagmanager.com and www.netigate.se. I extracted this by
2376 asking &lt;a href=&quot;http://phantomjs.org/&quot;&gt;PhantomJS&lt;/a&gt; to visit the
2377 Stortinget web page and tell me all the URLs PhantomJS downloaded to
2378 render the page (in HAR format using
2379 &lt;a href=&quot;https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js&quot;&gt;their
2380 netsniff example&lt;/a&gt;. I am very grateful to Gorm for showing me how
2381 to do this). My goal is to visualize network traces to all IP
2382 addresses behind these DNS names, do show where visitors personal
2383 information is spread when visiting the page.&lt;/p&gt;
2384
2385 &lt;p align=&quot;center&quot;&gt;&lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;&lt;img
2386 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;
2387
2388 &lt;p&gt;When I had a look around for options, I could not find any good
2389 free software tools to do this, and decided I needed my own traceroute
2390 wrapper outputting KML based on locations looked up using GeoIP. KML
2391 is easy to work with and easy to generate, and understood by several
2392 of the GIS tools I have available. I got good help from by NUUG
2393 colleague Anders Einar with this, and the result can be seen in
2394 &lt;a href=&quot;https://github.com/petterreinholdtsen/kmltraceroute&quot;&gt;my
2395 kmltraceroute git repository&lt;/a&gt;. Unfortunately, the quality of the
2396 free GeoIP databases I could find (and the for-pay databases my
2397 friends had access to) is not up to the task. The IP addresses of
2398 central Internet infrastructure would typically be placed near the
2399 controlling companies main office, and not where the router is really
2400 located, as you can see from &lt;a href=&quot;www.stortinget.no-geoip.kml&quot;&gt;the
2401 KML file I created&lt;/a&gt; using the GeoLite City dataset from MaxMind.
2402
2403 &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
2404 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;
2405
2406 &lt;p&gt;I also had a look at the visual traceroute graph created by
2407 &lt;a href=&quot;http://www.secdev.org/projects/scapy/&quot;&gt;the scrapy project&lt;/a&gt;,
2408 showing IP network ownership (aka AS owner) for the IP address in
2409 question.
2410 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2017-01-09-www.stortinget.no-scapy.svg&quot;&gt;The
2411 graph display a lot of useful information about the traceroute in SVG
2412 format&lt;/a&gt;, and give a good indication on who control the network
2413 equipment involved, but it do not include geolocation. This graph
2414 make it possible to see the information is made available at least for
2415 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
2416 3 Communications and NetDNA.&lt;/p&gt;
2417
2418 &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
2419 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;
2420
2421 &lt;p&gt;In the process, I came across the
2422 &lt;a href=&quot;https://geotraceroute.com/&quot;&gt;web service GeoTraceroute&lt;/a&gt; by
2423 Salim Gasmi. Its methology of combining guesses based on DNS names,
2424 various location databases and finally use latecy times to rule out
2425 candidate locations seemed to do a very good job of guessing correct
2426 geolocation. But it could only do one trace at the time, did not have
2427 a sensor in Norway and did not make the geolocations easily available
2428 for postprocessing. So I contacted the developer and asked if he
2429 would be willing to share the code (he refused until he had time to
2430 clean it up), but he was interested in providing the geolocations in a
2431 machine readable format, and willing to set up a sensor in Norway. So
2432 since yesterday, it is possible to run traces from Norway in this
2433 service thanks to a sensor node set up by
2434 &lt;a href=&quot;https://www.nuug.no/&quot;&gt;the NUUG assosiation&lt;/a&gt;, and get the
2435 trace in KML format for further processing.&lt;/p&gt;
2436
2437 &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
2438 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;
2439
2440 &lt;p&gt;Here we can see a lot of trafic passes Sweden on its way to
2441 Denmark, Germany, Holland and Ireland. Plenty of places where the
2442 Snowden confirmations verified the traffic is read by various actors
2443 without your best interest as their top priority.&lt;/p&gt;
2444
2445 &lt;p&gt;Combining KML files is trivial using a text editor, so I could loop
2446 over all the hosts behind the urls imported by www.stortinget.no and
2447 ask for the KML file from GeoTraceroute, and create a combined KML
2448 file with all the traces (unfortunately only one of the IP addresses
2449 behind the DNS name is traced this time. To get them all, one would
2450 have to request traces using IP number instead of DNS names from
2451 GeoTraceroute). That might be the next step in this project.&lt;/p&gt;
2452
2453 &lt;p&gt;Armed with these tools, I find it a lot easier to figure out where
2454 the IP traffic moves and who control the boxes involved in moving it.
2455 And every time the link crosses for example the Swedish border, we can
2456 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
2457 Britain and NSA in USA and cables around the globe. (Hm, what should
2458 we tell them? :) Keep that in mind if you ever send anything
2459 unencrypted over the Internet.&lt;/p&gt;
2460
2461 &lt;p&gt;PS: KML files are drawn using
2462 &lt;a href=&quot;http://ivanrublev.me/kml/&quot;&gt;the KML viewer from Ivan
2463 Rublev&lt;a/&gt;, as it was less cluttered than the local Linux application
2464 Marble. There are heaps of other options too.&lt;/p&gt;
2465
2466 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2467 activities, please send Bitcoin donations to my address
2468 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2469 </description>
2470 </item>
2471
2472 <item>
2473 <title>Appstream just learned how to map hardware to packages too!</title>
2474 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</link>
2475 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html</guid>
2476 <pubDate>Fri, 23 Dec 2016 10:30:00 +0100</pubDate>
2477 <description>&lt;p&gt;I received a very nice Christmas present today. As my regular
2478 readers probably know, I have been working on the
2479 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the Isenkram
2480 system&lt;/a&gt; for many years. The goal of the Isenkram system is to make
2481 it easier for users to figure out what to install to get a given piece
2482 of hardware to work in Debian, and a key part of this system is a way
2483 to map hardware to packages. Isenkram have its own mapping database,
2484 and also uses data provided by each package using the AppStream
2485 metadata format. And today,
2486 &lt;a href=&quot;https://tracker.debian.org/pkg/appstream&quot;&gt;AppStream&lt;/a&gt; in
2487 Debian learned to look up hardware the same way Isenkram is doing it,
2488 ie using fnmatch():&lt;/p&gt;
2489
2490 &lt;p&gt;&lt;pre&gt;
2491 % appstreamcli what-provides modalias \
2492 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2493 Identifier: pymissile [generic]
2494 Name: pymissile
2495 Summary: Control original Striker USB Missile Launcher
2496 Package: pymissile
2497 % appstreamcli what-provides modalias usb:v0694p0002d0000
2498 Identifier: libnxt [generic]
2499 Name: libnxt
2500 Summary: utility library for talking to the LEGO Mindstorms NXT brick
2501 Package: libnxt
2502 ---
2503 Identifier: t2n [generic]
2504 Name: t2n
2505 Summary: Simple command-line tool for Lego NXT
2506 Package: t2n
2507 ---
2508 Identifier: python-nxt [generic]
2509 Name: python-nxt
2510 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
2511 Package: python-nxt
2512 ---
2513 Identifier: nbc [generic]
2514 Name: nbc
2515 Summary: C compiler for LEGO Mindstorms NXT bricks
2516 Package: nbc
2517 %
2518 &lt;/pre&gt;&lt;/p&gt;
2519
2520 &lt;p&gt;A similar query can be done using the combined AppStream and
2521 Isenkram databases using the isenkram-lookup tool:&lt;/p&gt;
2522
2523 &lt;p&gt;&lt;pre&gt;
2524 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2525 pymissile
2526 % isenkram-lookup usb:v0694p0002d0000
2527 libnxt
2528 nbc
2529 python-nxt
2530 t2n
2531 %
2532 &lt;/pre&gt;&lt;/p&gt;
2533
2534 &lt;p&gt;You can find modalias values relevant for your machine using
2535 &lt;tt&gt;cat $(find /sys/devices/ -name modalias)&lt;/tt&gt;.
2536
2537 &lt;p&gt;If you want to make this system a success and help Debian users
2538 make the most of the hardware they have, please
2539 help&lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add
2540 AppStream metadata for your package following the guidelines&lt;/a&gt;
2541 documented in the wiki. So far only 11 packages provide such
2542 information, among the several hundred hardware specific packages in
2543 Debian. The Isenkram database on the other hand contain 101 packages,
2544 mostly related to USB dongles. Most of the packages with hardware
2545 mapping in AppStream are LEGO Mindstorms related, because I have, as
2546 part of my involvement in
2547 &lt;a href=&quot;https://wiki.debian.org/LegoDesigners&quot;&gt;the Debian LEGO
2548 team&lt;/a&gt; given priority to making sure LEGO users get proposed the
2549 complete set of packages in Debian for that particular hardware. The
2550 team also got a nice Christmas present today. The
2551 &lt;a href=&quot;https://tracker.debian.org/pkg/nxt-firmware&quot;&gt;nxt-firmware
2552 package&lt;/a&gt; made it into Debian. With this package in place, it is
2553 now possible to use the LEGO Mindstorms NXT unit with only free
2554 software, as the nxt-firmware package contain the source and firmware
2555 binaries for the NXT brick.&lt;/p&gt;
2556
2557 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2558 activities, please send Bitcoin donations to my address
2559 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2560 </description>
2561 </item>
2562
2563 <item>
2564 <title>Isenkram updated with a lot more hardware-package mappings</title>
2565 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</link>
2566 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html</guid>
2567 <pubDate>Tue, 20 Dec 2016 11:55:00 +0100</pubDate>
2568 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
2569 system&lt;/a&gt; I wrote two years ago to make it easier in Debian to find
2570 and install packages to get your hardware dongles to work, is still
2571 going strong. It is a system to look up the hardware present on or
2572 connected to the current system, and map the hardware to Debian
2573 packages. It can either be done using the tools in isenkram-cli or
2574 using the user space daemon in the isenkram package. The latter will
2575 notify you, when inserting new hardware, about what packages to
2576 install to get the dongle working. It will even provide a button to
2577 click on to ask packagekit to install the packages.&lt;/p&gt;
2578
2579 &lt;p&gt;Here is an command line example from my Thinkpad laptop:&lt;/p&gt;
2580
2581 &lt;p&gt;&lt;pre&gt;
2582 % isenkram-lookup
2583 bluez
2584 cheese
2585 ethtool
2586 fprintd
2587 fprintd-demo
2588 gkrellm-thinkbat
2589 hdapsd
2590 libpam-fprintd
2591 pidgin-blinklight
2592 thinkfan
2593 tlp
2594 tp-smapi-dkms
2595 tp-smapi-source
2596 tpb
2597 %
2598 &lt;/pre&gt;&lt;/p&gt;
2599
2600 &lt;p&gt;It can also list the firware package providing firmware requested
2601 by the load kernel modules, which in my case is an empty list because
2602 I have all the firmware my machine need:
2603
2604 &lt;p&gt;&lt;pre&gt;
2605 % /usr/sbin/isenkram-autoinstall-firmware -l
2606 info: did not find any firmware files requested by loaded kernel modules. exiting
2607 %
2608 &lt;/pre&gt;&lt;/p&gt;
2609
2610 &lt;p&gt;The last few days I had a look at several of the around 250
2611 packages in Debian with udev rules. These seem like good candidates
2612 to install when a given hardware dongle is inserted, and I found
2613 several that should be proposed by isenkram. I have not had time to
2614 check all of them, but am happy to report that now there are 97
2615 packages packages mapped to hardware by Isenkram. 11 of these
2616 packages provide hardware mapping using AppStream, while the rest are
2617 listed in the modaliases file provided in isenkram.&lt;/p&gt;
2618
2619 &lt;p&gt;These are the packages with hardware mappings at the moment. The
2620 &lt;strong&gt;marked packages&lt;/strong&gt; are also announcing their hardware
2621 support using AppStream, for everyone to use:&lt;/p&gt;
2622
2623 &lt;p&gt;air-quality-sensor, alsa-firmware-loaders, argyll,
2624 &lt;strong&gt;array-info&lt;/strong&gt;, avarice, avrdude, b43-fwcutter,
2625 bit-babbler, bluez, bluez-firmware, &lt;strong&gt;brltty&lt;/strong&gt;,
2626 &lt;strong&gt;broadcom-sta-dkms&lt;/strong&gt;, calibre, cgminer, cheese, colord,
2627 &lt;strong&gt;colorhug-client&lt;/strong&gt;, dahdi-firmware-nonfree, dahdi-linux,
2628 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
2629 fprintd-demo, &lt;strong&gt;galileo&lt;/strong&gt;, gkrellm-thinkbat, gphoto2,
2630 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
2631 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
2632 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
2633 &lt;strong&gt;libnxt&lt;/strong&gt;, libpam-fprintd, &lt;strong&gt;lomoco&lt;/strong&gt;,
2634 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
2635 &lt;strong&gt;nbc&lt;/strong&gt;, &lt;strong&gt;nqc&lt;/strong&gt;, nut-hal-drivers, ola,
2636 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
2637 pcscd, pidgin-blinklight, printer-driver-splix,
2638 &lt;strong&gt;pymissile&lt;/strong&gt;, python-nxt, qlandkartegt,
2639 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
2640 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
2641 &lt;strong&gt;t2n&lt;/strong&gt;, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
2642 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
2643 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
2644 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
2645 xserver-xorg-video-vmware, yubikey-personalization and
2646 zd1211-firmware&lt;/p&gt;
2647
2648 &lt;p&gt;If you know of other packages, please let me know with a wishlist
2649 bug report against the isenkram-cli package, and ask the package
2650 maintainer to
2651 &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;add AppStream
2652 metadata according to the guidelines&lt;/a&gt; to provide the information
2653 for everyone. In time, I hope to get rid of the isenkram specific
2654 hardware mapping and depend exclusively on AppStream.&lt;/p&gt;
2655
2656 &lt;p&gt;Note, the AppStream metadata for broadcom-sta-dkms is matching too
2657 much hardware, and suggest that the package with with any ethernet
2658 card. See &lt;a href=&quot;http://bugs.debian.org/838735&quot;&gt;bug #838735&lt;/a&gt; for
2659 the details. I hope the maintainer find time to address it soon. In
2660 the mean time I provide an override in isenkram.&lt;/p&gt;
2661 </description>
2662 </item>
2663
2664 <item>
2665 <title>Oolite, a life in space as vagabond and mercenary - nice free software</title>
2666 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</link>
2667 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html</guid>
2668 <pubDate>Sun, 11 Dec 2016 11:40:00 +0100</pubDate>
2669 <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;
2670
2671 &lt;p&gt;In my early years, I played
2672 &lt;a href=&quot;http://wiki.alioth.net/index.php/Classic_Elite&quot;&gt;the epic game
2673 Elite&lt;/a&gt; on my PC. I spent many months trading and fighting in
2674 space, and reached the &#39;elite&#39; fighting status before I moved on. The
2675 original Elite game was available on Commodore 64 and the IBM PC
2676 edition I played had a 64 KB executable. I am still impressed today
2677 that the authors managed to squeeze both a 3D engine and details about
2678 more than 2000 planet systems across 7 galaxies into a binary so
2679 small.&lt;/p&gt;
2680
2681 &lt;p&gt;I have known about &lt;a href=&quot;http://www.oolite.org/&quot;&gt;the free
2682 software game Oolite inspired by Elite&lt;/a&gt; for a while, but did not
2683 really have time to test it properly until a few days ago. It was
2684 great to discover that my old knowledge about trading routes were
2685 still valid. But my fighting and flying abilities were gone, so I had
2686 to retrain to be able to dock on a space station. And I am still not
2687 able to make much resistance when I am attacked by pirates, so I
2688 bougth and mounted the most powerful laser in the rear to be able to
2689 put up at least some resistance while fleeing for my life. :)&lt;/p&gt;
2690
2691 &lt;p&gt;When playing Elite in the late eighties, I had to discover
2692 everything on my own, and I had long lists of prices seen on different
2693 planets to be able to decide where to trade what. This time I had the
2694 advantages of the
2695 &lt;a href=&quot;http://wiki.alioth.net/index.php/Main_Page&quot;&gt;Elite wiki&lt;/a&gt;,
2696 where information about each planet is easily available with common
2697 price ranges and suggested trading routes. This improved my ability
2698 to earn money and I have been able to earn enough to buy a lot of
2699 useful equipent in a few days. I believe I originally played for
2700 months before I could get a docking computer, while now I could get it
2701 after less then a week.&lt;/p&gt;
2702
2703 &lt;p&gt;If you like science fiction and dreamed of a life as a vagabond in
2704 space, you should try out Oolite. It is available for Linux, MacOSX
2705 and Windows, and is included in Debian and derivatives since 2011.&lt;/p&gt;
2706
2707 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
2708 activities, please send Bitcoin donations to my address
2709 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
2710 </description>
2711 </item>
2712
2713 <item>
2714 <title>Quicker Debian installations using eatmydata</title>
2715 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</link>
2716 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html</guid>
2717 <pubDate>Fri, 25 Nov 2016 14:50:00 +0100</pubDate>
2718 <description>&lt;p&gt;Two years ago, I did some experiments with eatmydata and the Debian
2719 installation system, observing how using
2720 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html&quot;&gt;eatmydata
2721 could speed up the installation&lt;/a&gt; quite a bit. My testing measured
2722 speedup around 20-40 percent for Debian Edu, where we install around
2723 1000 packages from within the installer. The eatmydata package
2724 provide a way to disable/delay file system flushing. This is a bit
2725 risky in the general case, as files that should be stored on disk will
2726 stay only in memory a bit longer than expected, causing problems if a
2727 machine crashes at an inconvenient time. But for an installation, if
2728 the machine crashes during installation the process is normally
2729 restarted, and avoiding disk operations as much as possible to speed
2730 up the process make perfect sense.
2731
2732 &lt;p&gt;I added code in the Debian Edu specific installation code to enable
2733 &lt;a href=&quot;https://tracker.debian.org/pkg/libeatmydata&quot;&gt;eatmydata&lt;/a&gt;,
2734 but did not have time to push it any further. But a few months ago I
2735 picked it up again and worked with the libeatmydata package maintainer
2736 Mattia Rizzolo to make it easier for everyone to get this installation
2737 speedup in Debian. Thanks to our cooperation There is now an
2738 eatmydata-udeb package in Debian testing and unstable, and simply
2739 enabling/installing it in debian-installer (d-i) is enough to get the
2740 quicker installations. It can be enabled using preseeding. The
2741 following untested kernel argument should do the trick:&lt;/p&gt;
2742
2743 &lt;blockquote&gt;&lt;pre&gt;
2744 preseed/early_command=&quot;anna-install eatmydata-udeb&quot;
2745 &lt;/pre&gt;&lt;/blockquote&gt;
2746
2747 &lt;p&gt;This should ask d-i to install the package inside the d-i
2748 environment early in the installation sequence. Having it installed
2749 in d-i in turn will make sure the relevant scripts are called just
2750 after debootstrap filled /target/ with the freshly installed Debian
2751 system to configure apt to run dpkg with eatmydata. This is enough to
2752 speed up the installation process. There is a proposal to
2753 &lt;a href=&quot;https://bugs.debian.org/841153&quot;&gt;extend the idea a bit further
2754 by using /etc/ld.so.preload instead of apt.conf&lt;/a&gt;, but I have not
2755 tested its impact.&lt;/p&gt;
2756
2757 </description>
2758 </item>
2759
2760 <item>
2761 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium</title>
2762 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</link>
2763 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html</guid>
2764 <pubDate>Thu, 24 Nov 2016 10:50:00 +0100</pubDate>
2765 <description>&lt;p&gt;I Norge er det mange som trenger å skrive både bokmål og nynorsk.
2766 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
2767 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
2768 elever over det ganske land skal levere inn hvert år. Det mange ikke
2769 vet er at selv om de kommersielle alternativene
2770 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google Translate&lt;/a&gt; og
2771 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing Translator&lt;/a&gt; ikke kan
2772 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
2773 utmerket fri programvarealternativ som kan. Oversetterverktøyet
2774 Apertium har støtte for en rekke språkkombinasjoner, og takket være
2775 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
2776 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
2777 nynorsk, og få den automatoversatt til det andre skriftspråket.
2778 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
2779 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
2780 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
2781 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
2782 &lt;a href=&quot;https://www.apertium.org/&quot;&gt;Apertium.org&lt;/a&gt; og fyll inn
2783 teksten din i webskjemaet der.
2784
2785 &lt;p&gt;Hvis du trenger maskinell tilgang til den bakenforliggende
2786 teknologien kan du enten installere pakken
2787 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;apertium-nno-nob&lt;/a&gt;
2788 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
2789 api.apertium.org. Se
2790 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;API-dokumentasjonen&lt;/a&gt;
2791 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
2792 denne teksten som ble skrevet på bokmål over maskinoversatt til
2793 nynorsk.&lt;/p&gt;
2794
2795 &lt;hr/&gt;
2796
2797 &lt;p&gt;I Noreg er det mange som treng å skriva både bokmål og nynorsk.
2798 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
2799 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
2800 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
2801 veit er at sjølv om dei kommersielle alternativa
2802 &lt;a href=&quot;https://translate.google.com/&quot;&gt;Google *Translate&lt;/a&gt; og
2803 &lt;a href=&quot;https://www.bing.com/translator/&quot;&gt;Bing *Translator&lt;/a&gt; ikkje
2804 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
2805 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
2806 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
2807 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
2808 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
2809 nynorsk, og få den *automatoversatt til det andre skriftspråket.
2810 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
2811 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
2812 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
2813 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
2814 fall &lt;a href=&quot;https://www.apertium.org/&quot;&gt;*Apertium.org&lt;/a&gt; og fyll inn
2815 teksta di i *webskjemaet der.
2816
2817 &lt;p&gt;Viss du treng *maskinell tilgjenge til den *bakenforliggende
2818 teknologien kan du anten installera pakken
2819 &lt;a href=&quot;https://tracker.debian.org/apertium-nno-nob&quot;&gt;*apertium-*nno-*nob&lt;/a&gt;
2820 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
2821 *api.*apertium.org. Sjå
2822 &lt;a href=&quot;http://wiki.apertium.org/wiki/Apertium-apy&quot;&gt;*API-dokumentasjonen&lt;/a&gt;
2823 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
2824 for denne teksta som vart skreva på bokmål over *maskinoversatt til
2825 nynorsk.&lt;/p&gt;
2826 </description>
2827 </item>
2828
2829 <item>
2830 <title>Coz profiler for multi-threaded software is now in Debian</title>
2831 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</link>
2832 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html</guid>
2833 <pubDate>Sun, 13 Nov 2016 12:30:00 +0100</pubDate>
2834 <description>&lt;p&gt;&lt;a href=&quot;http://coz-profiler.org/&quot;&gt;The Coz profiler&lt;/a&gt;, a nice
2835 profiler able to run benchmarking experiments on the instrumented
2836 multi-threaded program, finally
2837 &lt;a href=&quot;https://tracker.debian.org/pkg/coz-profiler&quot;&gt;made it into
2838 Debian unstable yesterday&lt;/A&gt;. Lluís Vilanova and I have spent many
2839 months since
2840 &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
2841 blogged about the coz tool&lt;/a&gt; in August working with upstream to make
2842 it suitable for Debian. There are still issues with clang
2843 compatibility, inline assembly only working x86 and minimized
2844 JavaScript libraries.&lt;/p&gt;
2845
2846 &lt;p&gt;To test it, install &#39;coz-profiler&#39; using apt and run it like this:&lt;/p&gt;
2847
2848 &lt;p&gt;&lt;blockquote&gt;
2849 &lt;tt&gt;coz run --- /path/to/binary-with-debug-info&lt;/tt&gt;
2850 &lt;/blockquote&gt;&lt;/p&gt;
2851
2852 &lt;p&gt;This will produce a profile.coz file in the current working
2853 directory with the profiling information. This is then given to a
2854 JavaScript application provided in the package and available from
2855 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;a project web page&lt;/a&gt;.
2856 To start the local copy, invoke it in a browser like this:&lt;/p&gt;
2857
2858 &lt;p&gt;&lt;blockquote&gt;
2859 &lt;tt&gt;sensible-browser /usr/share/coz-profiler/viewer/index.htm&lt;/tt&gt;
2860 &lt;/blockquote&gt;&lt;/p&gt;
2861
2862 &lt;p&gt;See the project home page and the
2863 &lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;USENIX
2864 ;login: article on Coz&lt;/a&gt; for more information on how it is
2865 working.&lt;/p&gt;
2866 </description>
2867 </item>
2868
2869 <item>
2870 <title>My own self balancing Lego Segway</title>
2871 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</link>
2872 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html</guid>
2873 <pubDate>Fri, 4 Nov 2016 10:15:00 +0100</pubDate>
2874 <description>&lt;p&gt;A while back I received a Gyro sensor for the NXT
2875 &lt;a href=&quot;mindstorms.lego.com&quot;&gt;Mindstorms&lt;/a&gt; controller as a birthday
2876 present. It had been on my wishlist for a while, because I wanted to
2877 build a Segway like balancing lego robot. I had already built
2878 &lt;a href=&quot;http://www.nxtprograms.com/NXT2/segway/&quot;&gt;a simple balancing
2879 robot&lt;/a&gt; with the kids, using the light/color sensor included in the
2880 NXT kit as the balance sensor, but it was not working very well. It
2881 could balance for a while, but was very sensitive to the light
2882 condition in the room and the reflective properties of the surface and
2883 would fall over after a short while. I wanted something more robust,
2884 and had
2885 &lt;a href=&quot;https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action&amp;key=NGY1044&quot;&gt;the
2886 gyro sensor from HiTechnic&lt;/a&gt; I believed would solve it on my
2887 wishlist for some years before it suddenly showed up as a gift from my
2888 loved ones. :)&lt;/p&gt;
2889
2890 &lt;p&gt;Unfortunately I have not had time to sit down and play with it
2891 since then. But that changed some days ago, when I was searching for
2892 lego segway information and came across a recipe from HiTechnic for
2893 building
2894 &lt;a href=&quot;http://www.hitechnic.com/blog/gyro-sensor/htway/&quot;&gt;the
2895 HTWay&lt;/a&gt;, a segway like balancing robot. Build instructions and
2896 &lt;a href=&quot;https://www.hitechnic.com/upload/786-HTWayC.nxc&quot;&gt;source
2897 code&lt;/a&gt; was included, so it was just a question of putting it all
2898 together. And thanks to the great work of many Debian developers, the
2899 compiler needed to build the source for the NXT is already included in
2900 Debian, so I was read to go in less than an hour. The resulting robot
2901 do not look very impressive in its simplicity:&lt;/p&gt;
2902
2903 &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;
2904
2905 &lt;p&gt;Because I lack the infrared sensor used to control the robot in the
2906 design from HiTechnic, I had to comment out the last task
2907 (taskControl). I simply placed /* and */ around it get the program
2908 working without that sensor present. Now it balances just fine until
2909 the battery status run low:&lt;/p&gt;
2910
2911 &lt;p align=&quot;center&quot;&gt;&lt;video width=&quot;70%&quot; controls=&quot;true&quot;&gt;
2912 &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;
2913 &lt;/video&gt;&lt;/p&gt;
2914
2915 &lt;p&gt;Now we would like to teach it how to follow a line and take remote
2916 control instructions using the included Bluetooth receiver in the NXT.&lt;/p&gt;
2917
2918 &lt;p&gt;If you, like me, love LEGO and want to make sure we find the tools
2919 they need to work with LEGO in Debian and all our derivative
2920 distributions like Ubuntu, check out
2921 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;the LEGO designers
2922 project page&lt;/a&gt; and join the Debian LEGO team. Personally I own a
2923 RCX and NXT controller (no EV3), and would like to make sure the
2924 Debian tools needed to program the systems I own work as they
2925 should.&lt;/p&gt;
2926 </description>
2927 </item>
2928
2929 <item>
2930 <title>Experience and updated recipe for using the Signal app without a mobile phone</title>
2931 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</link>
2932 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html</guid>
2933 <pubDate>Mon, 10 Oct 2016 11:30:00 +0200</pubDate>
2934 <description>&lt;p&gt;In July
2935 &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
2936 wrote how to get the Signal Chrome/Chromium app working&lt;/a&gt; without
2937 the ability to receive SMS messages (aka without a cell phone). It is
2938 time to share some experiences and provide an updated setup.&lt;/p&gt;
2939
2940 &lt;p&gt;The Signal app have worked fine for several months now, and I use
2941 it regularly to chat with my loved ones. I had a major snag at the
2942 end of my summer vacation, when the the app completely forgot my
2943 setup, identity and keys. The reason behind this major mess was
2944 running out of disk space. To avoid that ever happening again I have
2945 started storing everything in &lt;tt&gt;userdata/&lt;/tt&gt; in git, to be able to
2946 roll back to an earlier version if the files are wiped by mistake. I
2947 had to use it once after introducing the git backup. When rolling
2948 back to an earlier version, one need to use the &#39;reset session&#39; option
2949 in Signal to get going, and notify the people you talk with about the
2950 problem. I assume there is some sequence number tracking in the
2951 protocol to detect rollback attacks. The git repository is rather big
2952 (674 MiB so far), but I have not tried to figure out if some of the
2953 content can be added to a .gitignore file due to lack of spare
2954 time.&lt;/p&gt;
2955
2956 &lt;p&gt;I&#39;ve also hit the 90 days timeout blocking, and noticed that this
2957 make it impossible to send messages using Signal. I could still
2958 receive them, but had to patch the code with a new timestamp to send.
2959 I believe the timeout is added by the developers to force people to
2960 upgrade to the latest version of the app, even when there is no
2961 protocol changes, to reduce the version skew among the user base and
2962 thus try to keep the number of support requests down.&lt;/p&gt;
2963
2964 &lt;p&gt;Since my original recipe, the Signal source code changed slightly,
2965 making the old patch fail to apply cleanly. Below is an updated
2966 patch, including the shell wrapper I use to start Signal. The
2967 original version required a new user to locate the JavaScript console
2968 and call a function from there. I got help from a friend with more
2969 JavaScript knowledge than me to modify the code to provide a GUI
2970 button instead. This mean that to get started you just need to run
2971 the wrapper and click the &#39;Register without mobile phone&#39; to get going
2972 now. I&#39;ve also modified the timeout code to always set it to 90 days
2973 in the future, to avoid having to patch the code regularly.&lt;/p&gt;
2974
2975 &lt;p&gt;So, the updated recipe for Debian Jessie:&lt;/p&gt;
2976
2977 &lt;ol&gt;
2978
2979 &lt;li&gt;First, install required packages to get the source code and the
2980 browser you need. Signal only work with Chrome/Chromium, as far as I
2981 know, so you need to install it.
2982
2983 &lt;pre&gt;
2984 apt install git tor chromium
2985 git clone https://github.com/WhisperSystems/Signal-Desktop.git
2986 &lt;/pre&gt;&lt;/li&gt;
2987
2988 &lt;li&gt;Modify the source code using command listed in the the patch
2989 block below.&lt;/li&gt;
2990
2991 &lt;li&gt;Start Signal using the run-signal-app wrapper (for example using
2992 &lt;tt&gt;`pwd`/run-signal-app&lt;/tt&gt;).
2993
2994 &lt;li&gt;Click on the &#39;Register without mobile phone&#39;, will in a phone
2995 number you can receive calls to the next minute, receive the
2996 verification code and enter it into the form field and press
2997 &#39;Register&#39;. Note, the phone number you use will be user Signal
2998 username, ie the way others can find you on Signal.&lt;/li&gt;
2999
3000 &lt;li&gt;You can now use Signal to contact others. Note, new contacts do
3001 not show up in the contact list until you restart Signal, and there is
3002 no way to assign names to Contacts. There is also no way to create or
3003 update chat groups. I suspect this is because the web app do not have
3004 a associated contact database.&lt;/li&gt;
3005
3006 &lt;/ol&gt;
3007
3008 &lt;p&gt;I am still a bit uneasy about using Signal, because of the way its
3009 main author moxie0 reject federation and accept dependencies to major
3010 corporations like Google (part of the code is fetched from Google) and
3011 Amazon (the central coordination point is owned by Amazon). See for
3012 example
3013 &lt;a href=&quot;https://github.com/LibreSignal/LibreSignal/issues/37&quot;&gt;the
3014 LibreSignal issue tracker&lt;/a&gt; for a thread documenting the authors
3015 view on these issues. But the network effect is strong in this case,
3016 and several of the people I want to communicate with already use
3017 Signal. Perhaps we can all move to &lt;a href=&quot;https://ring.cx/&quot;&gt;Ring&lt;/a&gt;
3018 once it &lt;a href=&quot;https://bugs.debian.org/830265&quot;&gt;work on my
3019 laptop&lt;/a&gt;? It already work on Windows and Android, and is included
3020 in &lt;a href=&quot;https://tracker.debian.org/pkg/ring&quot;&gt;Debian&lt;/a&gt; and
3021 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/ring&quot;&gt;Ubuntu&lt;/a&gt;, but not
3022 working on Debian Stable.&lt;/p&gt;
3023
3024 &lt;p&gt;Anyway, this is the patch I apply to the Signal code to get it
3025 working. It switch to the production servers, disable to timeout,
3026 make registration easier and add the shell wrapper:&lt;/p&gt;
3027
3028 &lt;pre&gt;
3029 cd Signal-Desktop; cat &amp;lt;&amp;lt;EOF | patch -p1
3030 diff --git a/js/background.js b/js/background.js
3031 index 24b4c1d..579345f 100644
3032 --- a/js/background.js
3033 +++ b/js/background.js
3034 @@ -33,9 +33,9 @@
3035 });
3036 });
3037
3038 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
3039 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org&#39;;
3040 var SERVER_PORTS = [80, 4433, 8443];
3041 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
3042 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
3043 var messageReceiver;
3044 window.getSocketStatus = function() {
3045 if (messageReceiver) {
3046 diff --git a/js/expire.js b/js/expire.js
3047 index 639aeae..beb91c3 100644
3048 --- a/js/expire.js
3049 +++ b/js/expire.js
3050 @@ -1,6 +1,6 @@
3051 ;(function() {
3052 &#39;use strict&#39;;
3053 - var BUILD_EXPIRATION = 0;
3054 + var BUILD_EXPIRATION = Date.now() + (90 * 24 * 60 * 60 * 1000);
3055
3056 window.extension = window.extension || {};
3057
3058 diff --git a/js/views/install_view.js b/js/views/install_view.js
3059 index 7816f4f..1d6233b 100644
3060 --- a/js/views/install_view.js
3061 +++ b/js/views/install_view.js
3062 @@ -38,7 +38,8 @@
3063 return {
3064 &#39;click .step1&#39;: this.selectStep.bind(this, 1),
3065 &#39;click .step2&#39;: this.selectStep.bind(this, 2),
3066 - &#39;click .step3&#39;: this.selectStep.bind(this, 3)
3067 + &#39;click .step3&#39;: this.selectStep.bind(this, 3),
3068 + &#39;click .callreg&#39;: function() { extension.install(&#39;standalone&#39;) },
3069 };
3070 },
3071 clearQR: function() {
3072 diff --git a/options.html b/options.html
3073 index dc0f28e..8d709f6 100644
3074 --- a/options.html
3075 +++ b/options.html
3076 @@ -14,7 +14,10 @@
3077 &amp;lt;div class=&#39;nav&#39;&gt;
3078 &amp;lt;h1&gt;{{ installWelcome }}&amp;lt;/h1&gt;
3079 &amp;lt;p&gt;{{ installTagline }}&amp;lt;/p&gt;
3080 - &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt; &amp;lt;/div&gt;
3081 + &amp;lt;div&gt; &amp;lt;a class=&#39;button step2&#39;&gt;{{ installGetStartedButton }}&amp;lt;/a&gt;
3082 + &amp;lt;br&gt; &amp;lt;a class=&quot;button callreg&quot;&gt;Register without mobile phone&amp;lt;/a&gt;
3083 +
3084 + &amp;lt;/div&gt;
3085 &amp;lt;span class=&#39;dot step1 selected&#39;&gt;&amp;lt;/span&gt;
3086 &amp;lt;span class=&#39;dot step2&#39;&gt;&amp;lt;/span&gt;
3087 &amp;lt;span class=&#39;dot step3&#39;&gt;&amp;lt;/span&gt;
3088 --- /dev/null 2016-10-07 09:55:13.730181472 +0200
3089 +++ b/run-signal-app 2016-10-10 08:54:09.434172391 +0200
3090 @@ -0,0 +1,12 @@
3091 +#!/bin/sh
3092 +set -e
3093 +cd $(dirname $0)
3094 +mkdir -p userdata
3095 +userdata=&quot;`pwd`/userdata&quot;
3096 +if [ -d &quot;$userdata&quot; ] &amp;&amp; [ ! -d &quot;$userdata/.git&quot; ] ; then
3097 + (cd $userdata &amp;&amp; git init)
3098 +fi
3099 +(cd $userdata &amp;&amp; git add . &amp;&amp; git commit -m &quot;Current status.&quot; || true)
3100 +exec chromium \
3101 + --proxy-server=&quot;socks://localhost:9050&quot; \
3102 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3103 EOF
3104 chmod a+rx run-signal-app
3105 &lt;/pre&gt;
3106
3107 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3108 activities, please send Bitcoin donations to my address
3109 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3110 </description>
3111 </item>
3112
3113 <item>
3114 <title>Isenkram, Appstream and udev make life as a LEGO builder easier</title>
3115 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</link>
3116 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html</guid>
3117 <pubDate>Fri, 7 Oct 2016 09:50:00 +0200</pubDate>
3118 <description>&lt;p&gt;&lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;The Isenkram
3119 system&lt;/a&gt; provide a practical and easy way to figure out which
3120 packages support the hardware in a given machine. The command line
3121 tool &lt;tt&gt;isenkram-lookup&lt;/tt&gt; and the tasksel options provide a
3122 convenient way to list and install packages relevant for the current
3123 hardware during system installation, both user space packages and
3124 firmware packages. The GUI background daemon on the other hand provide
3125 a pop-up proposing to install packages when a new dongle is inserted
3126 while using the computer. For example, if you plug in a smart card
3127 reader, the system will ask if you want to install &lt;tt&gt;pcscd&lt;/tt&gt; if
3128 that package isn&#39;t already installed, and if you plug in a USB video
3129 camera the system will ask if you want to install &lt;tt&gt;cheese&lt;/tt&gt; if
3130 cheese is currently missing. This already work just fine.&lt;/p&gt;
3131
3132 &lt;p&gt;But Isenkram depend on a database mapping from hardware IDs to
3133 package names. When I started no such database existed in Debian, so
3134 I made my own data set and included it with the isenkram package and
3135 made isenkram fetch the latest version of this database from git using
3136 http. This way the isenkram users would get updated package proposals
3137 as soon as I learned more about hardware related packages.&lt;/p&gt;
3138
3139 &lt;p&gt;The hardware is identified using modalias strings. The modalias
3140 design is from the Linux kernel where most hardware descriptors are
3141 made available as a strings that can be matched using filename style
3142 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3143 identifiers.&lt;/p&gt;
3144
3145 &lt;p&gt;The downside to the Isenkram specific database is that there is no
3146 information about relevant distribution / Debian version, making
3147 isenkram propose obsolete packages too. But along came AppStream, a
3148 cross distribution mechanism to store and collect metadata about
3149 software packages. When I heard about the proposal, I contacted the
3150 people involved and suggested to add a hardware matching rule using
3151 modalias strings in the specification, to be able to use AppStream for
3152 mapping hardware to packages. This idea was accepted and AppStream is
3153 now a great way for a package to announce the hardware it support in a
3154 distribution neutral way. I wrote
3155 &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
3156 recipe on how to add such meta-information&lt;/a&gt; in a blog post last
3157 December. If you have a hardware related package in Debian, please
3158 announce the relevant hardware IDs using AppStream.&lt;/p&gt;
3159
3160 &lt;p&gt;In Debian, almost all packages that can talk to a LEGO Mindestorms
3161 RCX or NXT unit, announce this support using AppStream. The effect is
3162 that when you insert such LEGO robot controller into your Debian
3163 machine, Isenkram will propose to install the packages needed to get
3164 it working. The intention is that this should allow the local user to
3165 start programming his robot controller right away without having to
3166 guess what packages to use or which permissions to fix.&lt;/p&gt;
3167
3168 &lt;p&gt;But when I sat down with my son the other day to program our NXT
3169 unit using his Debian Stretch computer, I discovered something
3170 annoying. The local console user (ie my son) did not get access to
3171 the USB device for programming the unit. This used to work, but no
3172 longer in Jessie and Stretch. After some investigation and asking
3173 around on #debian-devel, I discovered that this was because udev had
3174 changed the mechanism used to grant access to local devices. The
3175 ConsoleKit mechanism from &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;
3176 no longer applied, because LDAP users no longer was added to the
3177 plugdev group during login. Michael Biebl told me that this method
3178 was obsolete and the new method used ACLs instead. This was good
3179 news, as the plugdev mechanism is a mess when using a remote user
3180 directory like LDAP. Using ACLs would make sure a user lost device
3181 access when she logged out, even if the user left behind a background
3182 process which would retain the plugdev membership with the ConsoleKit
3183 setup. Armed with this knowledge I moved on to fix the access problem
3184 for the LEGO Mindstorms related packages.&lt;/p&gt;
3185
3186 &lt;p&gt;The new system uses a udev tag, &#39;uaccess&#39;. It can either be
3187 applied directly for a device, or is applied in
3188 /lib/udev/rules.d/70-uaccess.rules for classes of devices. As the
3189 LEGO Mindstorms udev rules did not have a class, I decided to add the
3190 tag directly in the udev rules files included in the packages. Here
3191 is one example. For the nqc C compiler for the RCX, the
3192 &lt;tt&gt;/lib/udev/rules.d/60-nqc.rules&lt;/tt&gt; file now look like this:
3193
3194 &lt;p&gt;&lt;pre&gt;
3195 SUBSYSTEM==&quot;usb&quot;, ACTION==&quot;add&quot;, ATTR{idVendor}==&quot;0694&quot;, ATTR{idProduct}==&quot;0001&quot;, \
3196 SYMLINK+=&quot;rcx-%k&quot;, TAG+=&quot;uaccess&quot;
3197 &lt;/pre&gt;&lt;/p&gt;
3198
3199 &lt;p&gt;The key part is the &#39;TAG+=&quot;uaccess&quot;&#39; at the end. I suspect all
3200 packages using plugdev in their /lib/udev/rules.d/ files should be
3201 changed to use this tag (either directly or indirectly via
3202 &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;). Perhaps a lintian check should be created
3203 to detect this?&lt;/p&gt;
3204
3205 &lt;p&gt;I&#39;ve been unable to find good documentation on the uaccess feature.
3206 It is unclear to me if the uaccess tag is an internal implementation
3207 detail like the udev-acl tag used by
3208 &lt;tt&gt;/lib/udev/rules.d/70-udev-acl.rules&lt;/tt&gt;. If it is, I guess the
3209 indirect method is the preferred way. Michael
3210 &lt;a href=&quot;https://github.com/systemd/systemd/issues/4288&quot;&gt;asked for more
3211 documentation from the systemd project&lt;/a&gt; and I hope it will make
3212 this clearer. For now I use the generic classes when they exist and
3213 is already handled by &lt;tt&gt;70-uaccess.rules&lt;/tt&gt;, and add the tag
3214 directly if no such class exist.&lt;/p&gt;
3215
3216 &lt;p&gt;To learn more about the isenkram system, please check out
3217 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
3218 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
3219
3220 &lt;p&gt;To help out making life for LEGO constructors in Debian easier,
3221 please join us on our IRC channel
3222 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; and join
3223 the &lt;a href=&quot;https://alioth.debian.org/projects/debian-lego/&quot;&gt;Debian
3224 LEGO team&lt;/a&gt; in the Alioth project we created yesterday. A mailing
3225 list is not yet created, but we are working on it. :)&lt;/p&gt;
3226
3227 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3228 activities, please send Bitcoin donations to my address
3229 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3230 </description>
3231 </item>
3232
3233 <item>
3234 <title>First draft Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook now public</title>
3235 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html</link>
3236 <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>
3237 <pubDate>Tue, 30 Aug 2016 10:10:00 +0200</pubDate>
3238 <description>&lt;p&gt;In April we
3239 &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
3240 to work&lt;/a&gt; on a Norwegian Bokmål edition of the &quot;open access&quot; book on
3241 how to set up and administrate a Debian system. Today I am happy to
3242 report that the first draft is now publicly available. You can find
3243 it on &lt;a href=&quot;https://debian-handbook.info/get/&quot;&gt;get the Debian
3244 Administrator&#39;s Handbook page&lt;/a&gt; (under Other languages). The first
3245 eight chapters have a first draft translation, and we are working on
3246 proofreading the content. If you want to help out, please start
3247 contributing using
3248 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3249 hosted weblate project page&lt;/a&gt;, and get in touch using
3250 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3251 translators mailing list&lt;/a&gt;. Please also check out
3252 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3253 contributors&lt;/a&gt;. A good way to contribute is to proofread the text
3254 and update weblate if you find errors.&lt;/p&gt;
3255
3256 &lt;p&gt;Our goal is still to make the Norwegian book available on paper as well as
3257 electronic form.&lt;/p&gt;
3258 </description>
3259 </item>
3260
3261 <item>
3262 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software</title>
3263 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</link>
3264 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html</guid>
3265 <pubDate>Thu, 11 Aug 2016 12:00:00 +0200</pubDate>
3266 <description>&lt;p&gt;This summer, I read a great article
3267 &quot;&lt;a href=&quot;https://www.usenix.org/publications/login/summer2016/curtsinger&quot;&gt;coz:
3268 This Is the Profiler You&#39;re Looking For&lt;/a&gt;&quot; in USENIX ;login: about
3269 how to profile multi-threaded programs. It presented a system for
3270 profiling software by running experiences in the running program,
3271 testing how run time performance is affected by &quot;speeding up&quot; parts of
3272 the code to various degrees compared to a normal run. It does this by
3273 slowing down parallel threads while the &quot;faster up&quot; code is running
3274 and measure how this affect processing time. The processing time is
3275 measured using probes inserted into the code, either using progress
3276 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
3277 can also measure unmodified code by measuring complete the program
3278 runtime and running the program several times instead.&lt;/p&gt;
3279
3280 &lt;p&gt;The project and presentation was so inspiring that I would like to
3281 get the system into Debian. I
3282 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830708&quot;&gt;created
3283 a WNPP request for it&lt;/a&gt; and contacted upstream to try to make the
3284 system ready for Debian by sending patches. The build process need to
3285 be changed a bit to avoid running &#39;git clone&#39; to get dependencies, and
3286 to include the JavaScript web page used to visualize the collected
3287 profiling information included in the source package.
3288 But I expect that should work out fairly soon.&lt;/p&gt;
3289
3290 &lt;p&gt;The way the system work is fairly simple. To run an coz experiment
3291 on a binary with debug symbols available, start the program like this:
3292
3293 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3294 coz run --- program-to-run
3295 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3296
3297 &lt;p&gt;This will create a text file profile.coz with the instrumentation
3298 information. To show what part of the code affect the performance
3299 most, use a web browser and either point it to
3300 &lt;a href=&quot;http://plasma-umass.github.io/coz/&quot;&gt;http://plasma-umass.github.io/coz/&lt;/a&gt;
3301 or use the copy from git (in the gh-pages branch). Check out this web
3302 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
3303 profiling more useful you include &amp;lt;coz.h&amp;gt; and insert the
3304 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
3305 code, rebuild and run the profiler. This allow coz to do more
3306 targeted experiments.&lt;/p&gt;
3307
3308 &lt;p&gt;A video published by ACM
3309 &lt;a href=&quot;https://www.youtube.com/watch?v=jE0V-p1odPg&quot;&gt;presenting the
3310 Coz profiler&lt;/a&gt; is available from Youtube. There is also a paper
3311 from the 25th Symposium on Operating Systems Principles available
3312 titled
3313 &lt;a href=&quot;https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger&quot;&gt;Coz:
3314 finding code that counts with causal profiling&lt;/a&gt;.&lt;/p&gt;
3315
3316 &lt;p&gt;&lt;a href=&quot;https://github.com/plasma-umass/coz&quot;&gt;The source code&lt;/a&gt;
3317 for Coz is available from github. It will only build with clang
3318 because it uses a
3319 &lt;a href=&quot;https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55606&quot;&gt;C++
3320 feature missing in GCC&lt;/a&gt;, but I&#39;ve submitted
3321 &lt;a href=&quot;https://github.com/plasma-umass/coz/pull/67&quot;&gt;a patch to solve
3322 it&lt;/a&gt; and hope it will be included in the upstream source soon.&lt;/p&gt;
3323
3324 &lt;p&gt;Please get in touch if you, like me, would like to see this piece
3325 of software in Debian. I would very much like some help with the
3326 packaging effort, as I lack the in depth knowledge on how to package
3327 C++ libraries.&lt;/p&gt;
3328 </description>
3329 </item>
3330
3331 <item>
3332 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot</title>
3333 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</link>
3334 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html</guid>
3335 <pubDate>Thu, 7 Jul 2016 11:30:00 +0200</pubDate>
3336 <description>&lt;p&gt;Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
3337 to be a slight challenge. Here is the recipe if I ever need to do it
3338 again. It all started by me wanting to try the recipe to set up
3339 &lt;a href=&quot;https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy&quot;&gt;an
3340 hardened Android installation&lt;/a&gt; from the Tor project blog on a
3341 device I had access to. It is a old mobile phone with a broken
3342 microphone The initial idea had been to just
3343 &lt;a href=&quot;http://wiki.cyanogenmod.org/w/Install_CM_for_ace&quot;&gt;install
3344 CyanogenMod on it&lt;/a&gt;, but did not quite find time to start on it
3345 until a few days ago.&lt;/p&gt;
3346
3347 &lt;p&gt;The unlock process is supposed to be simple: (1) Boot into the boot
3348 loader (press volume down and power at the same time), (2) select
3349 &#39;fastboot&#39; before (3) connecting the device via USB to a Linux
3350 machine, (4) request the device identifier token by running &#39;fastboot
3351 oem get_identifier_token&#39;, (5) request the device unlocking key using
3352 the &lt;a href=&quot;http://www.htcdev.com/bootloader/&quot;&gt;HTC developer web
3353 site&lt;/a&gt; and unlock the phone using the key file emailed to you.&lt;/p&gt;
3354
3355 &lt;p&gt;Unfortunately, this only work fi you have hboot version 2.00.0029
3356 or newer, and the device I was working on had 2.00.0027. This
3357 apparently can be easily fixed by downloading a Windows program and
3358 running it on your Windows machine, if you accept the terms Microsoft
3359 require you to accept to use Windows - which I do not. So I had to
3360 come up with a different approach. I got a lot of help from AndyCap
3361 on #nuug, and would not have been able to get this working without
3362 him.&lt;/p&gt;
3363
3364 &lt;p&gt;First I needed to extract the hboot firmware from
3365 &lt;a href=&quot;http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00.0029.exe&quot;&gt;the
3366 windows binary for HTC Desire HD&lt;/a&gt; downloaded as &#39;the RUU&#39; from HTC.
3367 For this there is is &lt;a href=&quot;https://github.com/kmdm/unruu/&quot;&gt;a github
3368 project named unruu&lt;/a&gt; using libunshield. The unshield tool did not
3369 recognise the file format, but unruu worked and extracted rom.zip,
3370 containing the new hboot firmware and a text file describing which
3371 devices it would work for.&lt;/p&gt;
3372
3373 &lt;p&gt;Next, I needed to get the new firmware into the device. For this I
3374 followed some instructions
3375 &lt;a href=&quot;http://www.htc1guru.com/2013/09/new-ruu-zips-posted/&quot;&gt;available
3376 from HTC1Guru.com&lt;/a&gt;, and ran these commands as root on a Linux
3377 machine with Debian testing:&lt;/p&gt;
3378
3379 &lt;p&gt;&lt;pre&gt;
3380 adb reboot-bootloader
3381 fastboot oem rebootRUU
3382 fastboot flash zip rom.zip
3383 fastboot flash zip rom.zip
3384 fastboot reboot
3385 &lt;/pre&gt;&lt;/p&gt;
3386
3387 &lt;p&gt;The flash command apparently need to be done twice to take effect,
3388 as the first is just preparations and the second one do the flashing.
3389 The adb command is just to get to the boot loader menu, so turning the
3390 device on while holding volume down and the power button should work
3391 too.&lt;/p&gt;
3392
3393 &lt;p&gt;With the new hboot version in place I could start following the
3394 instructions on the HTC developer web site. I got the device token
3395 like this:&lt;/p&gt;
3396
3397 &lt;p&gt;&lt;pre&gt;
3398 fastboot oem get_identifier_token 2&gt;&amp;1 | sed &#39;s/(bootloader) //&#39;
3399 &lt;/pre&gt;
3400
3401 &lt;p&gt;And once I got the unlock code via email, I could use it like
3402 this:&lt;/p&gt;
3403
3404 &lt;p&gt;&lt;pre&gt;
3405 fastboot flash unlocktoken Unlock_code.bin
3406 &lt;/pre&gt;&lt;/p&gt;
3407
3408 &lt;p&gt;And with that final step in place, the phone was unlocked and I
3409 could start stuffing the software of my own choosing into the device.
3410 So far I only inserted a replacement recovery image to wipe the phone
3411 before I start. We will see what happen next. Perhaps I should
3412 install &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; on it. :)&lt;/p&gt;
3413 </description>
3414 </item>
3415
3416 <item>
3417 <title>How to use the Signal app if you only have a land line (ie no mobile phone)</title>
3418 <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>
3419 <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>
3420 <pubDate>Sun, 3 Jul 2016 14:20:00 +0200</pubDate>
3421 <description>&lt;p&gt;For a while now, I have wanted to test
3422 &lt;a href=&quot;https://whispersystems.org/&quot;&gt;the Signal app&lt;/a&gt;, as it is
3423 said to provide end to end encrypted communication and several of my
3424 friends and family are already using it. As I by choice do not own a
3425 mobile phone, this proved to be harder than expected. And I wanted to
3426 have the source of the client and know that it was the code used on my
3427 machine. But yesterday I managed to get it working. I used the
3428 Github source, compared it to the source in
3429 &lt;a href=&quot;https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US&quot;&gt;the
3430 Signal Chrome app&lt;/a&gt; available from the Chrome web store, applied
3431 patches to use the production Signal servers, started the app and
3432 asked for the hidden &quot;register without a smart phone&quot; form. Here is
3433 the recipe how I did it.&lt;/p&gt;
3434
3435 &lt;p&gt;First, I fetched the Signal desktop source from Github, using
3436
3437 &lt;pre&gt;
3438 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3439 &lt;/pre&gt;
3440
3441 &lt;p&gt;Next, I patched the source to use the production servers, to be
3442 able to talk to other Signal users:&lt;/p&gt;
3443
3444 &lt;pre&gt;
3445 cat &amp;lt;&amp;lt;EOF | patch -p0
3446 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js
3447 --- ./js/background.js 2016-06-29 13:43:15.630344628 +0200
3448 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/background.js 2016-06-29 14:06:29.530300934 +0200
3449 @@ -47,8 +47,8 @@
3450 });
3451 });
3452
3453 - var SERVER_URL = &#39;https://textsecure-service-staging.whispersystems.org&#39;;
3454 - var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com&#39;;
3455 + var SERVER_URL = &#39;https://textsecure-service-ca.whispersystems.org:4433&#39;;
3456 + var ATTACHMENT_SERVER_URL = &#39;https://whispersystems-textsecure-attachments.s3.amazonaws.com&#39;;
3457 var messageReceiver;
3458 window.getSocketStatus = function() {
3459 if (messageReceiver) {
3460 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js
3461 --- ./js/expire.js 2016-06-29 13:43:15.630344628 +0200
3462 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/0.15.0_0/js/expire.js2016-06-29 14:06:29.530300934 +0200
3463 @@ -1,6 +1,6 @@
3464 ;(function() {
3465 &#39;use strict&#39;;
3466 - var BUILD_EXPIRATION = 0;
3467 + var BUILD_EXPIRATION = 1474492690000;
3468
3469 window.extension = window.extension || {};
3470
3471 EOF
3472 &lt;/pre&gt;
3473
3474 &lt;p&gt;The first part is changing the servers, and the second is updating
3475 an expiration timestamp. This timestamp need to be updated regularly.
3476 It is set 90 days in the future by the build process (Gruntfile.js).
3477 The value is seconds since 1970 times 1000, as far as I can tell.&lt;/p&gt;
3478
3479 &lt;p&gt;Based on a tip and good help from the #nuug IRC channel, I wrote a
3480 script to launch Signal in Chromium.&lt;/p&gt;
3481
3482 &lt;pre&gt;
3483 #!/bin/sh
3484 cd $(dirname $0)
3485 mkdir -p userdata
3486 exec chromium \
3487 --proxy-server=&quot;socks://localhost:9050&quot; \
3488 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
3489 &lt;/pre&gt;
3490
3491 &lt;p&gt; The script start the app and configure Chromium to use the Tor
3492 SOCKS5 proxy to make sure those controlling the Signal servers (today
3493 Amazon and Whisper Systems) as well as those listening on the lines
3494 will have a harder time location my laptop based on the Signal
3495 connections if they use source IP address.&lt;/p&gt;
3496
3497 &lt;p&gt;When the script starts, one need to follow the instructions under
3498 &quot;Standalone Registration&quot; in the CONTRIBUTING.md file in the git
3499 repository. I right clicked on the Signal window to get up the
3500 Chromium debugging tool, visited the &#39;Console&#39; tab and wrote
3501 &#39;extension.install(&quot;standalone&quot;)&#39; on the console prompt to get the
3502 registration form. Then I entered by land line phone number and
3503 pressed &#39;Call&#39;. 5 seconds later the phone rang and a robot voice
3504 repeated the verification code three times. After entering the number
3505 into the verification code field in the form, I could start using
3506 Signal from my laptop.
3507
3508 &lt;p&gt;As far as I can tell, The Signal app will leak who is talking to
3509 whom and thus who know who to those controlling the central server,
3510 but such leakage is hard to avoid with a centrally controlled server
3511 setup. It is something to keep in mind when using Signal - the
3512 content of your chats are harder to intercept, but the meta data
3513 exposing your contact network is available to people you do not know.
3514 So better than many options, but not great. And sadly the usage is
3515 connected to my land line, thus allowing those controlling the server
3516 to associate it to my home and person. I would prefer it if only
3517 those I knew could tell who I was on Signal. There are options
3518 avoiding such information leakage, but most of my friends are not
3519 using them, so I am stuck with Signal for now.&lt;/p&gt;
3520
3521 &lt;p&gt;&lt;strong&gt;Update 2017-01-10&lt;/strong&gt;: There is an updated blog post
3522 on this topic in
3523 &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
3524 and updated recipe for using the Signal app without a mobile
3525 phone&lt;/a&gt;.&lt;/p&gt;
3526 </description>
3527 </item>
3528
3529 <item>
3530 <title>The new &quot;best&quot; multimedia player in Debian?</title>
3531 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</link>
3532 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html</guid>
3533 <pubDate>Mon, 6 Jun 2016 12:50:00 +0200</pubDate>
3534 <description>&lt;p&gt;When I set out a few weeks ago to figure out
3535 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html&quot;&gt;which
3536 multimedia player in Debian claimed to support most file formats /
3537 MIME types&lt;/a&gt;, I was a bit surprised how varied the sets of MIME types
3538 the various players claimed support for. The range was from 55 to 130
3539 MIME types. I suspect most media formats are supported by all
3540 players, but this is not really reflected in the MimeTypes values in
3541 their desktop files. There are probably also some bogus MIME types
3542 listed, but it is hard to identify which one this is.&lt;/p&gt;
3543
3544 &lt;p&gt;Anyway, in the mean time I got in touch with upstream for some of
3545 the players suggesting to add more MIME types to their desktop files,
3546 and decided to spend some time myself improving the situation for my
3547 favorite media player VLC. The fixes for VLC entered Debian unstable
3548 yesterday. The complete list of MIME types can be seen on the
3549 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;Multimedia
3550 player MIME type support status&lt;/a&gt; Debian wiki page.&lt;/p&gt;
3551
3552 &lt;p&gt;The new &quot;best&quot; multimedia player in Debian? It is VLC, followed by
3553 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
3554 kmplayer. I am sure some of the other players desktop files support
3555 several of the formats currently listed as working only with vlc,
3556 toten and parole.&lt;/p&gt;
3557
3558 &lt;p&gt;A sad observation is that only 14 MIME types are listed as
3559 supported by all the tested multimedia players in Debian in their
3560 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
3561 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
3562 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
3563 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
3564 it sad that video/ogg and video/webm is not supported by all the media
3565 players in Debian. As far as I can tell, all of them can handle both
3566 formats.&lt;/p&gt;
3567 </description>
3568 </item>
3569
3570 <item>
3571 <title>A program should be able to open its own files on Linux</title>
3572 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</link>
3573 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html</guid>
3574 <pubDate>Sun, 5 Jun 2016 08:30:00 +0200</pubDate>
3575 <description>&lt;p&gt;Many years ago, when koffice was fresh and with few users, I
3576 decided to test its presentation tool when making the slides for a
3577 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
3578 wrote the first draft of the slides, saved the result and went to bed
3579 the day before I would give the talk. The next day I took a plane to
3580 the location where the meeting should take place, and on the plane I
3581 started up koffice again to polish the talk a bit, only to discover
3582 that kpresenter refused to load its own data file. I cursed a bit and
3583 started making the slides again from memory, to have something to
3584 present when I arrived. I tested that the saved files could be
3585 loaded, and the day seemed to be rescued. I continued to polish the
3586 slides until I suddenly discovered that the saved file could no longer
3587 be loaded into kpresenter. In the end I had to rewrite the slides
3588 three times, condensing the content until the talk became shorter and
3589 shorter. After the talk I was able to pinpoint the problem &amp;ndash;
3590 kpresenter wrote inline images in a way itself could not understand.
3591 Eventually that bug was fixed and kpresenter ended up being a great
3592 program to make slides. The point I&#39;m trying to make is that we
3593 expect a program to be able to load its own data files, and it is
3594 embarrassing to its developers if it can&#39;t.&lt;/p&gt;
3595
3596 &lt;p&gt;Did you ever experience a program failing to load its own data
3597 files from the desktop file browser? It is not a uncommon problem. A
3598 while back I discovered that the screencast recorder
3599 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
3600 browser would refuse to open. No video player claimed to understand
3601 such file. I tracked down the cause being &lt;tt&gt;file --mime-type&lt;/tt&gt;
3602 returning the application/ogg MIME type, which no video player I had
3603 installed listed as a MIME type they would understand. I asked for
3604 &lt;a href=&quot;http://bugs.gw.com/view.php?id=382&quot;&gt;file to change its
3605 behavour&lt;/a&gt; and use the MIME type video/ogg instead. I also asked
3606 several video players to add video/ogg to their desktop files, to give
3607 the file browser an idea what to do about Ogg Theora files. After a
3608 while, the desktop file browsers in Debian started to handle the
3609 output from gtk-recordmydesktop properly.&lt;/p&gt;
3610
3611 &lt;p&gt;But history repeats itself. A few days ago I tested the music
3612 system Rosegarden again, and I discovered that the KDE and xfce file
3613 browsers did not know what to do with the Rosegarden project files
3614 (*.rg). I&#39;ve reported &lt;a href=&quot;http://bugs.debian.org/825993&quot;&gt;the
3615 rosegarden problem to BTS&lt;/a&gt; and a fix is commited to git and will be
3616 included in the next upload. To increase the chance of me remembering
3617 how to fix the problem next time some program fail to load its files
3618 from the file browser, here are some notes on how to fix it.&lt;/p&gt;
3619
3620 &lt;p&gt;The file browsers in Debian in general operates on MIME types.
3621 There are two sources for the MIME type of a given file. The output from
3622 &lt;tt&gt;file --mime-type&lt;/tt&gt; mentioned above, and the content of the
3623 shared MIME type registry (under /usr/share/mime/). The file MIME
3624 type is mapped to programs supporting the MIME type, and this
3625 information is collected from
3626 &lt;a href=&quot;https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/&quot;&gt;the
3627 desktop files&lt;/a&gt; available in /usr/share/applications/. If there is
3628 one desktop file claiming support for the MIME type of the file, it is
3629 activated when asking to open a given file. If there are more, one
3630 can normally select which one to use by right-clicking on the file and
3631 selecting the wanted one using &#39;Open with&#39; or similar. In general
3632 this work well. But it depend on each program picking a good MIME
3633 type (preferably
3634 &lt;a href=&quot;http://www.iana.org/assignments/media-types/media-types.xhtml&quot;&gt;a
3635 MIME type registered with IANA&lt;/a&gt;), file and/or the shared MIME
3636 registry recognizing the file and the desktop file to list the MIME
3637 type in its list of supported MIME types.&lt;/p&gt;
3638
3639 &lt;p&gt;The &lt;tt&gt;/usr/share/mime/packages/rosegarden.xml&lt;/tt&gt; entry for
3640 &lt;a href=&quot;http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec&quot;&gt;the
3641 Shared MIME database&lt;/a&gt; look like this:&lt;/p&gt;
3642
3643 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3644 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
3645 &amp;lt;mime-info xmlns=&quot;http://www.freedesktop.org/standards/shared-mime-info&quot;&amp;gt;
3646 &amp;lt;mime-type type=&quot;audio/x-rosegarden&quot;&amp;gt;
3647 &amp;lt;sub-class-of type=&quot;application/x-gzip&quot;/&amp;gt;
3648 &amp;lt;comment&amp;gt;Rosegarden project file&amp;lt;/comment&amp;gt;
3649 &amp;lt;glob pattern=&quot;*.rg&quot;/&amp;gt;
3650 &amp;lt;/mime-type&amp;gt;
3651 &amp;lt;/mime-info&amp;gt;
3652 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3653
3654 &lt;p&gt;This states that audio/x-rosegarden is a kind of application/x-gzip
3655 (it is a gzipped XML file). Note, it is much better to use an
3656 official MIME type registered with IANA than it is to make up ones own
3657 unofficial ones like the x-rosegarden type used by rosegarden.&lt;/p&gt;
3658
3659 &lt;p&gt;The desktop file of the rosegarden program failed to list
3660 audio/x-rosegarden in its list of supported MIME types, causing the
3661 file browsers to have no idea what to do with *.rg files:&lt;/p&gt;
3662
3663 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3664 % grep Mime /usr/share/applications/rosegarden.desktop
3665 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
3666 X-KDE-NativeMimeType=audio/x-rosegarden-composition
3667 %
3668 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3669
3670 &lt;p&gt;The fix was to add &quot;audio/x-rosegarden;&quot; at the end of the
3671 MimeType= line.&lt;/p&gt;
3672
3673 &lt;p&gt;If you run into a file which fail to open the correct program when
3674 selected from the file browser, please check out the output from
3675 &lt;tt&gt;file --mime-type&lt;/tt&gt; for the file, ensure the file ending and
3676 MIME type is registered somewhere under /usr/share/mime/ and check
3677 that some desktop file under /usr/share/applications/ is claiming
3678 support for this MIME type. If not, please report a bug to have it
3679 fixed. :)&lt;/p&gt;
3680 </description>
3681 </item>
3682
3683 <item>
3684 <title>Isenkram with PackageKit support - new version 0.23 available in Debian unstable</title>
3685 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</link>
3686 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html</guid>
3687 <pubDate>Wed, 25 May 2016 10:20:00 +0200</pubDate>
3688 <description>&lt;p&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/isenkram&quot;&gt;The isenkram
3689 system&lt;/a&gt; is a user-focused solution in Debian for handling hardware
3690 related packages. The idea is to have a database of mappings between
3691 hardware and packages, and pop up a dialog suggesting for the user to
3692 install the packages to use a given hardware dongle. Some use cases
3693 are when you insert a Yubikey, it proposes to install the software
3694 needed to control it; when you insert a braille reader list it
3695 proposes to install the packages needed to send text to the reader;
3696 and when you insert a ColorHug screen calibrator it suggests to
3697 install the driver for it. The system work well, and even have a few
3698 command line tools to install firmware packages and packages for the
3699 hardware already in the machine (as opposed to hotpluggable hardware).&lt;/p&gt;
3700
3701 &lt;p&gt;The system was initially written using aptdaemon, because I found
3702 good documentation and example code on how to use it. But aptdaemon
3703 is going away and is generally being replaced by
3704 &lt;a href=&quot;http://www.freedesktop.org/software/PackageKit/&quot;&gt;PackageKit&lt;/a&gt;,
3705 so Isenkram needed a rewrite. And today, thanks to the great patch
3706 from my college Sunil Mohan Adapa in the FreedomBox project, the
3707 rewrite finally took place. I&#39;ve just uploaded a new version of
3708 Isenkram into Debian Unstable with the patch included, and the default
3709 for the background daemon is now to use PackageKit. To check it out,
3710 install the &lt;tt&gt;isenkram&lt;/tt&gt; package and insert some hardware dongle
3711 and see if it is recognised.&lt;/p&gt;
3712
3713 &lt;p&gt;If you want to know what kind of packages isenkram would propose for
3714 the machine it is running on, you can check out the isenkram-lookup
3715 program. This is what it look like on a Thinkpad X230:&lt;/p&gt;
3716
3717 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
3718 % isenkram-lookup
3719 bluez
3720 cheese
3721 fprintd
3722 fprintd-demo
3723 gkrellm-thinkbat
3724 hdapsd
3725 libpam-fprintd
3726 pidgin-blinklight
3727 thinkfan
3728 tleds
3729 tp-smapi-dkms
3730 tp-smapi-source
3731 tpb
3732 %p
3733 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
3734
3735 &lt;p&gt;The hardware mappings come from several places. The preferred way
3736 is for packages to announce their hardware support using
3737 &lt;a href=&quot;https://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
3738 cross distribution appstream system&lt;/a&gt;.
3739 See
3740 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;previous
3741 blog posts about isenkram&lt;/a&gt; to learn how to do that.&lt;/p&gt;
3742 </description>
3743 </item>
3744
3745 <item>
3746 <title>Discharge rate estimate in new battery statistics collector for Debian</title>
3747 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</link>
3748 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html</guid>
3749 <pubDate>Mon, 23 May 2016 09:35:00 +0200</pubDate>
3750 <description>&lt;p&gt;Yesterday I updated the
3751 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats
3752 package in Debian&lt;/a&gt; with a few patches sent to me by skilled and
3753 enterprising users. There were some nice user and visible changes.
3754 First of all, both desktop menu entries now work. A design flaw in
3755 one of the script made the history graph fail to show up (its PNG was
3756 dumped in ~/.xsession-errors) if no controlling TTY was available.
3757 The script worked when called from the command line, but not when
3758 called from the desktop menu. I changed this to look for a DISPLAY
3759 variable or a TTY before deciding where to draw the graph, and now the
3760 graph window pop up as expected.&lt;/p&gt;
3761
3762 &lt;p&gt;The next new feature is a discharge rate estimator in one of the
3763 graphs (the one showing the last few hours). New is also the user of
3764 colours showing charging in blue and discharge in red. The percentages
3765 of this graph is relative to last full charge, not battery design
3766 capacity.&lt;/p&gt;
3767
3768 &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;
3769
3770 &lt;p&gt;The other graph show the entire history of the collected battery
3771 statistics, comparing it to the design capacity of the battery to
3772 visualise how the battery life time get shorter over time. The red
3773 line in this graph is what the previous graph considers 100 percent:
3774
3775 &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;
3776
3777 &lt;p&gt;In this graph you can see that I only charge the battery to 80
3778 percent of last full capacity, and how the capacity of the battery is
3779 shrinking. :(&lt;/p&gt;
3780
3781 &lt;p&gt;The last new feature is in the collector, which now will handle
3782 more hardware models. On some hardware, Linux power supply
3783 information is stored in /sys/class/power_supply/ACAD/, while the
3784 collector previously only looked in /sys/class/power_supply/AC/. Now
3785 both are checked to figure if there is power connected to the
3786 machine.&lt;/p&gt;
3787
3788 &lt;p&gt;If you are interested in how your laptop battery is doing, please
3789 check out the
3790 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
3791 in Debian unstable, or rebuild it on Jessie to get it working on
3792 Debian stable. :) The upstream source is available from &lt;a
3793 href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
3794 Patches are very welcome.&lt;/p&gt;
3795
3796 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
3797 activities, please send Bitcoin donations to my address
3798 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
3799 </description>
3800 </item>
3801
3802 <item>
3803 <title>Debian now with ZFS on Linux included</title>
3804 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</link>
3805 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html</guid>
3806 <pubDate>Thu, 12 May 2016 07:30:00 +0200</pubDate>
3807 <description>&lt;p&gt;Today, after many years of hard work from many people,
3808 &lt;a href=&quot;http://zfsonlinux.org/&quot;&gt;ZFS for Linux&lt;/a&gt; finally entered
3809 Debian. The package status can be seen on
3810 &lt;a href=&quot;https://tracker.debian.org/pkg/zfs-linux&quot;&gt;the package tracker
3811 for zfs-linux&lt;/a&gt;. and
3812 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
3813 team status page&lt;/a&gt;. If you want to help out, please join us.
3814 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;The
3815 source code&lt;/a&gt; is available via git on Alioth. It would also be
3816 great if you could help out with
3817 &lt;a href=&quot;https://tracker.debian.org/pkg/dkms&quot;&gt;the dkms package&lt;/a&gt;, as
3818 it is an important piece of the puzzle to get ZFS working.&lt;/p&gt;
3819 </description>
3820 </item>
3821
3822 <item>
3823 <title>What is the best multimedia player in Debian?</title>
3824 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</link>
3825 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html</guid>
3826 <pubDate>Sun, 8 May 2016 09:40:00 +0200</pubDate>
3827 <description>&lt;p&gt;&lt;strong&gt;Where I set out to figure out which multimedia player in
3828 Debian claim support for most file formats.&lt;/strong&gt;&lt;/p&gt;
3829
3830 &lt;p&gt;A few years ago, I had a look at the media support for Browser
3831 plugins in Debian, to get an idea which plugins to include in Debian
3832 Edu. I created a script to extract the set of supported MIME types
3833 for each plugin, and used this to find out which multimedia browser
3834 plugin supported most file formats / media types.
3835 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;The
3836 result&lt;/a&gt; can still be seen on the Debian wiki, even though it have
3837 not been updated for a while. But browser plugins are less relevant
3838 these days, so I thought it was time to look at standalone
3839 players.&lt;/p&gt;
3840
3841 &lt;p&gt;A few days ago I was tired of VLC not being listed as a viable
3842 player when I wanted to play videos from the Norwegian National
3843 Broadcasting Company, and decided to investigate why. The cause is a
3844 &lt;a href=&quot;https://bugs.debian.org/822245&quot;&gt;missing MIME type in the VLC
3845 desktop file&lt;/a&gt;. In the process I wrote a script to compare the set
3846 of MIME types announced in the desktop file and the browser plugin,
3847 only to discover that there is quite a large difference between the
3848 two for VLC. This discovery made me dig up the script I used to
3849 compare browser plugins, and adjust it to compare desktop files
3850 instead, to try to figure out which multimedia player in Debian
3851 support most file formats.&lt;/p&gt;
3852
3853 &lt;p&gt;The result can be seen on the Debian Wiki, as
3854 &lt;a href=&quot;https://wiki.debian.org/DebianMultimedia/PlayerSupport&quot;&gt;a
3855 table listing all MIME types supported by one of the packages included
3856 in the table&lt;/a&gt;, with the package supporting most MIME types being
3857 listed first in the table.&lt;/p&gt;
3858
3859 &lt;/p&gt;The best multimedia player in Debian? It is totem, followed by
3860 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
3861 kmplayer. Time for the other players to update their announced MIME
3862 support?&lt;/p&gt;
3863 </description>
3864 </item>
3865
3866 <item>
3867 <title>The Pyra - handheld computer with Debian preinstalled</title>
3868 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</link>
3869 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html</guid>
3870 <pubDate>Wed, 4 May 2016 10:00:00 +0200</pubDate>
3871 <description>A friend of mine made me aware of
3872 &lt;a href=&quot;https://pyra-handheld.com/boards/pages/pyra/&quot;&gt;The Pyra&lt;/a&gt;, a
3873 handheld computer which will be delivered with Debian preinstalled. I
3874 would love to get one of those for my birthday. :)&lt;/p&gt;
3875
3876 &lt;p&gt;The machine is a complete ARM-based PC with micro HDMI, SATA, USB
3877 plugs and many others connectors, and include a full keyboard and a 5&quot;
3878 LCD touch screen. The 6000mAh battery is claimed to provide a whole
3879 day of battery life time, but I have not seen any independent tests
3880 confirming this. The vendor is still collecting preorders, and the
3881 last I heard last night was that 22 more orders were needed before
3882 production started.&lt;/p&gt;
3883
3884 &lt;p&gt;As far as I know, this is the first handheld preinstalled with
3885 Debian. Please let me know if you know of any others. Is it the
3886 first computer being sold with Debian preinstalled?&lt;/p&gt;
3887 </description>
3888 </item>
3889
3890 <item>
3891 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator&#39;s Handbook</title>
3892 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</link>
3893 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html</guid>
3894 <pubDate>Sun, 10 Apr 2016 23:20:00 +0200</pubDate>
3895 <description>&lt;p&gt;During this weekends
3896 &lt;a href=&quot;http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml&quot;&gt;bug
3897 squashing party and developer gathering&lt;/a&gt;, we decided to do our part
3898 to make sure there are good books about Debian available in Norwegian
3899 Bokmål, and got in touch with the people behind the
3900 &lt;a href=&quot;http://debian-handbook.info/&quot;&gt;Debian Administrator&#39;s Handbook
3901 project&lt;/a&gt; to get started. If you want to help out, please start
3902 contributing using
3903 &lt;a href=&quot;https://hosted.weblate.org/projects/debian-handbook/&quot;&gt;the
3904 hosted weblate project page&lt;/a&gt;, and get in touch using
3905 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators&quot;&gt;the
3906 translators mailing list&lt;/a&gt;. Please also check out
3907 &lt;a href=&quot;https://debian-handbook.info/contribute/&quot;&gt;the instructions for
3908 contributors&lt;/a&gt;.&lt;/p&gt;
3909
3910 &lt;p&gt;The book is already available on paper in English, French and
3911 Japanese, and our goal is to get it available on paper in Norwegian
3912 Bokmål too. In addition to the paper edition, there are also EPUB and
3913 Mobi versions available. And there are incomplete translations
3914 available for many more languages.&lt;/p&gt;
3915 </description>
3916 </item>
3917
3918 <item>
3919 <title>One in two hundred Debian users using ZFS on Linux?</title>
3920 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</link>
3921 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html</guid>
3922 <pubDate>Thu, 7 Apr 2016 22:30:00 +0200</pubDate>
3923 <description>&lt;p&gt;Just for fun I had a look at the popcon number of ZFS related
3924 packages in Debian, and was quite surprised with what I found. I use
3925 ZFS myself at home, but did not really expect many others to do so.
3926 But I might be wrong.&lt;/p&gt;
3927
3928 &lt;p&gt;According to
3929 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=spl-linux&quot;&gt;the popcon
3930 results for spl-linux&lt;/a&gt;, there are 1019 Debian installations, or
3931 0.53% of the population, with the package installed. As far as I know
3932 the only use of the spl-linux package is as a support library for ZFS
3933 on Linux, so I use it here as proxy for measuring the number of ZFS
3934 installation on Linux in Debian. In the kFreeBSD variant of Debian
3935 the ZFS feature is already available, and there
3936 &lt;a href=&quot;https://qa.debian.org/popcon.php?package=zfsutils&quot;&gt;the popcon
3937 results for zfsutils&lt;/a&gt; show 1625 Debian installations or 0.84% of
3938 the population. So I guess I am not alone in using ZFS on Debian.&lt;/p&gt;
3939
3940 &lt;p&gt;But even though the Debian project leader Lucas Nussbaum
3941 &lt;a href=&quot;https://lists.debian.org/debian-devel-announce/2015/04/msg00006.html&quot;&gt;announced
3942 in April 2015&lt;/a&gt; that the legal obstacles blocking ZFS on Debian were
3943 cleared, the package is still not in Debian. The package is again in
3944 the NEW queue. Several uploads have been rejected so far because the
3945 debian/copyright file was incomplete or wrong, but there is no reason
3946 to give up. The current status can be seen on
3947 &lt;a href=&quot;https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org&quot;&gt;the
3948 team status page&lt;/a&gt;, and
3949 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git&quot;&gt;the
3950 source code&lt;/a&gt; is available on Alioth.&lt;/p&gt;
3951
3952 &lt;p&gt;As I want ZFS to be included in next version of Debian to make sure
3953 my home server can function in the future using only official Debian
3954 packages, and the current blocker is to get the debian/copyright file
3955 accepted by the FTP masters in Debian, I decided a while back to try
3956 to help out the team. This was the background for my blog post about
3957 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html&quot;&gt;creating,
3958 updating and checking debian/copyright semi-automatically&lt;/a&gt;, and I
3959 used the techniques I explored there to try to find any errors in the
3960 copyright file. It is not very easy to check every one of the around
3961 2000 files in the source package, but I hope we this time got it
3962 right. If you want to help out, check out the git source and try to
3963 find missing entries in the debian/copyright file.&lt;/p&gt;
3964 </description>
3965 </item>
3966
3967 <item>
3968 <title>Full battery stats collector is now available in Debian</title>
3969 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</link>
3970 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html</guid>
3971 <pubDate>Wed, 23 Mar 2016 22:10:00 +0100</pubDate>
3972 <description>&lt;p&gt;Since this morning, the battery-stats package in Debian include an
3973 extended collector that will collect the complete battery history for
3974 later processing and graphing. The original collector store the
3975 battery level as percentage of last full level, while the new
3976 collector also record battery vendor, model, serial number, design
3977 full level, last full level and current battery level. This make it
3978 possible to predict the lifetime of the battery as well as visualise
3979 the energy flow when the battery is charging or discharging.&lt;/p&gt;
3980
3981 &lt;p&gt;The new tools are available in &lt;tt&gt;/usr/share/battery-stats/&lt;/tt&gt;
3982 in the version 0.5.1 package in unstable. Get the new battery level graph
3983 and lifetime prediction by running:
3984
3985 &lt;p&gt;&lt;pre&gt;
3986 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
3987 &lt;/pre&gt;&lt;/p&gt;
3988
3989 &lt;p&gt;Or select the &#39;Battery Level Graph&#39; from your application menu.&lt;/p&gt;
3990
3991 &lt;p&gt;The flow in/out of the battery can be seen by running (no menu
3992 entry yet):&lt;/p&gt;
3993
3994 &lt;p&gt;&lt;pre&gt;
3995 /usr/share/battery-stats/battery-stats-graph-flow
3996 &lt;/pre&gt;&lt;/p&gt;
3997
3998 &lt;p&gt;I&#39;m not quite happy with the way the data is visualised, at least
3999 when there are few data points. The graphs look a bit better with a
4000 few years of data.&lt;/p&gt;
4001
4002 &lt;p&gt;A while back one important feature I use in the battery stats
4003 collector broke in Debian. The scripts in
4004 &lt;tt&gt;/usr/lib/pm-utils/power.d/&lt;/tt&gt; were no longer executed. I
4005 suspect it happened when Jessie started using systemd, but I do not
4006 know. The issue is reported as
4007 &lt;a href=&quot;https://bugs.debian.org/818649&quot;&gt;bug #818649&lt;/a&gt; against
4008 pm-utils. I managed to work around it by adding an udev rule to call
4009 the collector script every time the power connector is connected and
4010 disconnected. With this fix in place it was finally time to make a
4011 new release of the package, and get it into Debian.&lt;/p&gt;
4012
4013 &lt;p&gt;If you are interested in how your laptop battery is doing, please
4014 check out the
4015 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;
4016 in Debian unstable, or rebuild it on Jessie to get it working on
4017 Debian stable. :) The upstream source is available from
4018 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4019 As always, patches are very welcome.&lt;/p&gt;
4020 </description>
4021 </item>
4022
4023 <item>
4024 <title>Making battery measurements a little easier in Debian</title>
4025 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</link>
4026 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html</guid>
4027 <pubDate>Tue, 15 Mar 2016 15:00:00 +0100</pubDate>
4028 <description>&lt;p&gt;Back in September, I blogged about
4029 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html&quot;&gt;the
4030 system I wrote to collect statistics about my laptop battery&lt;/a&gt;, and
4031 how it showed the decay and death of this battery (now replaced). I
4032 created a simple deb package to handle the collection and graphing,
4033 but did not want to upload it to Debian as there were already
4034 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;a battery-stats
4035 package in Debian&lt;/a&gt; that should do the same thing, and I did not see
4036 a point of uploading a competing package when battery-stats could be
4037 fixed instead. I reported a few bugs about its non-function, and
4038 hoped someone would step in and fix it. But no-one did.&lt;/p&gt;
4039
4040 &lt;p&gt;I got tired of waiting a few days ago, and took matters in my own
4041 hands. The end result is that I am now the new upstream developer of
4042 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
4043 battery-stats in Debian, and the package in Debian unstable is finally
4044 able to collect battery status using the &lt;tt&gt;/sys/class/power_supply/&lt;/tt&gt;
4045 information provided by the Linux kernel. If you install the
4046 battery-stats package from unstable now, you will be able to get a
4047 graph of the current battery fill level, to get some idea about the
4048 status of the battery. The source package build and work just fine in
4049 Debian testing and stable (and probably oldstable too, but I have not
4050 tested). The default graph you get for that system look like this:&lt;/p&gt;
4051
4052 &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;
4053
4054 &lt;p&gt;My plans for the future is to merge my old scripts into the
4055 battery-stats package, as my old scripts collected a lot more details
4056 about the battery. The scripts are merged into the upstream
4057 battery-stats git repository already, but I am not convinced they work
4058 yet, as I changed a lot of paths along the way. Will have to test a
4059 bit more before I make a new release.&lt;/p&gt;
4060
4061 &lt;p&gt;I will also consider changing the file format slightly, as I
4062 suspect the way I combine several values into one field might make it
4063 impossible to know the type of the value when using it for processing
4064 and graphing.&lt;/p&gt;
4065
4066 &lt;p&gt;If you would like I would like to keep an close eye on your laptop
4067 battery, check out the battery-stats package in
4068 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;Debian&lt;/a&gt; and
4069 on
4070 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-stats&quot;&gt;github&lt;/a&gt;.
4071 I would love some help to improve the system further.&lt;/p&gt;
4072 </description>
4073 </item>
4074
4075 <item>
4076 <title>Creating, updating and checking debian/copyright semi-automatically</title>
4077 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</link>
4078 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html</guid>
4079 <pubDate>Fri, 19 Feb 2016 15:00:00 +0100</pubDate>
4080 <description>&lt;p&gt;Making packages for Debian requires quite a lot of attention to
4081 details. And one of the details is the content of the
4082 debian/copyright file, which should list all relevant licenses used by
4083 the code in the package in question, preferably in
4084 &lt;a href=&quot;https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/&quot;&gt;machine
4085 readable DEP5 format&lt;/a&gt;.&lt;/p&gt;
4086
4087 &lt;p&gt;For large packages with lots of contributors it is hard to write
4088 and update this file manually, and if you get some detail wrong, the
4089 package is normally rejected by the ftpmasters. So getting it right
4090 the first time around get the package into Debian faster, and save
4091 both you and the ftpmasters some work.. Today, while trying to figure
4092 out what was wrong with
4093 &lt;a href=&quot;https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=686447&quot;&gt;the
4094 zfsonlinux copyright file&lt;/a&gt;, I decided to spend some time on
4095 figuring out the options for doing this job automatically, or at least
4096 semi-automatically.&lt;/p&gt;
4097
4098 &lt;p&gt;Lucikly, there are at least two tools available for generating the
4099 file based on the code in the source package,
4100 &lt;tt&gt;&lt;a href=&quot;https://tracker.debian.org/pkg/debmake&quot;&gt;debmake&lt;/a&gt;&lt;/tt&gt;
4101 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
4102 not sure which one of them came first, but both seem to be able to
4103 create a sensible draft file. As far as I can tell, none of them can
4104 be trusted to get the result just right, so the content need to be
4105 polished a bit before the file is OK to upload. I found the debmake
4106 option in
4107 &lt;a href=&quot;http://goofying-with-debian.blogspot.com/2014/07/debmake-checking-source-against-dep-5.html&quot;&gt;a
4108 blog posts from 2014&lt;/a&gt;.
4109
4110 &lt;p&gt;To generate using debmake, use the -cc option:
4111
4112 &lt;p&gt;&lt;pre&gt;
4113 debmake -cc &gt; debian/copyright
4114 &lt;/pre&gt;&lt;/p&gt;
4115
4116 &lt;p&gt;Note there are some problems with python and non-ASCII names, so
4117 this might not be the best option.&lt;/p&gt;
4118
4119 &lt;p&gt;The cme option is based on a config parsing library, and I found
4120 this approach in
4121 &lt;a href=&quot;https://ddumont.wordpress.com/2015/04/05/improving-creation-of-debian-copyright-file/&quot;&gt;a
4122 blog post from 2015&lt;/a&gt;. To generate using cme, use the &#39;update
4123 dpkg-copyright&#39; option:
4124
4125 &lt;p&gt;&lt;pre&gt;
4126 cme update dpkg-copyright
4127 &lt;/pre&gt;&lt;/p&gt;
4128
4129 &lt;p&gt;This will create or update debian/copyright. The cme tool seem to
4130 handle UTF-8 names better than debmake.&lt;/p&gt;
4131
4132 &lt;p&gt;When the copyright file is created, I would also like some help to
4133 check if the file is correct. For this I found two good options,
4134 &lt;tt&gt;debmake -k&lt;/tt&gt; and &lt;tt&gt;license-reconcile&lt;/tt&gt;. The former seem
4135 to focus on license types and file matching, and is able to detect
4136 ineffective blocks in the copyright file. The latter reports missing
4137 copyright holders and years, but was confused by inconsistent license
4138 names (like CDDL vs. CDDL-1.0). I suspect it is good to use both and
4139 fix all issues reported by them before uploading. But I do not know
4140 if the tools and the ftpmasters agree on what is important to fix in a
4141 copyright file, so the package might still be rejected.&lt;/p&gt;
4142
4143 &lt;p&gt;The devscripts tool &lt;tt&gt;licensecheck&lt;/tt&gt; deserve mentioning. It
4144 will read through the source and try to find all copyright statements.
4145 It is not comparing the result to the content of debian/copyright, but
4146 can be useful when verifying the content of the copyright file.&lt;/p&gt;
4147
4148 &lt;p&gt;Are you aware of better tools in Debian to create and update
4149 debian/copyright file. Please let me know, or blog about it on
4150 planet.debian.org.&lt;/p&gt;
4151
4152 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
4153 activities, please send Bitcoin donations to my address
4154 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
4155
4156 &lt;p&gt;&lt;strong&gt;Update 2016-02-20&lt;/strong&gt;: I got a tip from Mike Gabriel
4157 on how to use licensecheck and cdbs to create a draft copyright file
4158
4159 &lt;p&gt;&lt;pre&gt;
4160 licensecheck --copyright -r `find * -type f` | \
4161 /usr/lib/cdbs/licensecheck2dep5 &gt; debian/copyright.auto
4162 &lt;/pre&gt;&lt;/p&gt;
4163
4164 &lt;p&gt;He mentioned that he normally check the generated file into the
4165 version control system to make it easier to discover license and
4166 copyright changes in the upstream source. I will try to do the same
4167 with my packages in the future.&lt;/p&gt;
4168
4169 &lt;p&gt;&lt;strong&gt;Update 2016-02-21&lt;/strong&gt;: The cme author recommended
4170 against using -quiet for new users, so I removed it from the proposed
4171 command line.&lt;/p&gt;
4172 </description>
4173 </item>
4174
4175 <item>
4176 <title>Using appstream in Debian to locate packages with firmware and mime type support</title>
4177 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</link>
4178 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html</guid>
4179 <pubDate>Thu, 4 Feb 2016 16:40:00 +0100</pubDate>
4180 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;appstream system&lt;/a&gt;
4181 is taking shape in Debian, and one provided feature is a very
4182 convenient way to tell you which package to install to make a given
4183 firmware file available when the kernel is looking for it. This can
4184 be done using apt-file too, but that is for someone else to blog
4185 about. :)&lt;/p&gt;
4186
4187 &lt;p&gt;Here is a small recipe to find the package with a given firmware
4188 file, in this example I am looking for ctfw-3.2.3.0.bin, randomly
4189 picked from the set of firmware announced using appstream in Debian
4190 unstable. In general you would be looking for the firmware requested
4191 by the kernel during kernel module loading. To find the package
4192 providing the example file, do like this:&lt;/p&gt;
4193
4194 &lt;blockquote&gt;&lt;pre&gt;
4195 % apt install appstream
4196 [...]
4197 % apt update
4198 [...]
4199 % appstreamcli what-provides firmware:runtime ctfw-3.2.3.0.bin | \
4200 awk &#39;/Package:/ {print $2}&#39;
4201 firmware-qlogic
4202 %
4203 &lt;/pre&gt;&lt;/blockquote&gt;
4204
4205 &lt;p&gt;See &lt;a href=&quot;https://wiki.debian.org/AppStream/Guidelines&quot;&gt;the
4206 appstream wiki&lt;/a&gt; page to learn how to embed the package metadata in
4207 a way appstream can use.&lt;/p&gt;
4208
4209 &lt;p&gt;This same approach can be used to find any package supporting a
4210 given MIME type. This is very useful when you get a file you do not
4211 know how to handle. First find the mime type using &lt;tt&gt;file
4212 --mime-type&lt;/tt&gt;, and next look up the package providing support for
4213 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
4214 and you can find all packages handling this type like this:&lt;/p&gt;
4215
4216 &lt;blockquote&gt;&lt;pre&gt;
4217 % apt install appstream
4218 [...]
4219 % apt update
4220 [...]
4221 % appstreamcli what-provides mimetype image/svg+xml | \
4222 awk &#39;/Package:/ {print $2}&#39;
4223 bkchem
4224 phototonic
4225 inkscape
4226 shutter
4227 tetzle
4228 geeqie
4229 xia
4230 pinta
4231 gthumb
4232 karbon
4233 comix
4234 mirage
4235 viewnior
4236 postr
4237 ristretto
4238 kolourpaint4
4239 eog
4240 eom
4241 gimagereader
4242 midori
4243 %
4244 &lt;/pre&gt;&lt;/blockquote&gt;
4245
4246 &lt;p&gt;I believe the MIME types are fetched from the desktop file for
4247 packages providing appstream metadata.&lt;/p&gt;
4248 </description>
4249 </item>
4250
4251 <item>
4252 <title>Creepy, visualise geotagged social media information - nice free software</title>
4253 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</link>
4254 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html</guid>
4255 <pubDate>Sun, 24 Jan 2016 10:50:00 +0100</pubDate>
4256 <description>&lt;p&gt;Most people seem not to realise that every time they walk around
4257 with the computerised radio beacon known as a mobile phone their
4258 position is tracked by the phone company and often stored for a long
4259 time (like every time a SMS is received or sent). And if their
4260 computerised radio beacon is capable of running programs (often called
4261 mobile apps) downloaded from the Internet, these programs are often
4262 also capable of tracking their location (if the app requested access
4263 during installation). And when these programs send out information to
4264 central collection points, the location is often included, unless
4265 extra care is taken to not send the location. The provided
4266 information is used by several entities, for good and bad (what is
4267 good and bad, depend on your point of view). What is certain, is that
4268 the private sphere and the right to free movement is challenged and
4269 perhaps even eradicated for those announcing their location this way,
4270 when they share their whereabouts with private and public
4271 entities.&lt;/p&gt;
4272
4273 &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;
4274
4275 &lt;p&gt;The phone company logs provide a register of locations to check out
4276 when one want to figure out what the tracked person was doing. It is
4277 unavailable for most of us, but provided to selected government
4278 officials, company staff, those illegally buying information from
4279 unfaithful servants and crackers stealing the information. But the
4280 public information can be collected and analysed, and a free software
4281 tool to do so is called
4282 &lt;a href=&quot;http://www.geocreepy.com/&quot;&gt;Creepy or Cree.py&lt;/a&gt;. I
4283 discovered it when I read
4284 &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
4285 article about Creepy&lt;/a&gt; in the Norwegian newspaper Aftenposten i
4286 November 2014, and decided to check if it was available in Debian.
4287 The python program was in Debian, but
4288 &lt;a href=&quot;https://tracker.debian.org/pkg/creepy&quot;&gt;the version in
4289 Debian&lt;/a&gt; was completely broken and practically unmaintained. I
4290 uploaded a new version which did not work quite right, but did not
4291 have time to fix it then. This Christmas I decided to finally try to
4292 get Creepy operational in Debian. Now a fixed version is available in
4293 Debian unstable and testing, and almost all Debian specific patches
4294 are now included
4295 &lt;a href=&quot;https://github.com/jkakavas/creepy&quot;&gt;upstream&lt;/a&gt;.&lt;/p&gt;
4296
4297 &lt;p&gt;The Creepy program visualises geolocation information fetched from
4298 Twitter, Instagram, Flickr and Google+, and allow one to get a
4299 complete picture of every social media message posted recently in a
4300 given area, or track the movement of a given individual across all
4301 these services. Earlier it was possible to use the search API of at
4302 least some of these services without identifying oneself, but these
4303 days it is impossible. This mean that to use Creepy, you need to
4304 configure it to log in as yourself on these services, and provide
4305 information to them about your search interests. This should be taken
4306 into account when using Creepy, as it will also share information
4307 about yourself with the services.&lt;/p&gt;
4308
4309 &lt;p&gt;The picture above show the twitter messages sent from (or at least
4310 geotagged with a position from) the city centre of Oslo, the capital
4311 of Norway. One useful way to use Creepy is to first look at
4312 information tagged with an area of interest, and next look at all the
4313 information provided by one or more individuals who was in the area.
4314 I tested it by checking out which celebrity provide their location in
4315 twitter messages by checkout out who sent twitter messages near a
4316 Norwegian TV station, and next could track their position over time,
4317 making it possible to locate their home and work place, among other
4318 things. A similar technique have been
4319 &lt;a href=&quot;http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl&quot;&gt;used
4320 to locate Russian soldiers in Ukraine&lt;/a&gt;, and it is both a powerful
4321 tool to discover lying governments, and a useful tool to help people
4322 understand the value of the private information they provide to the
4323 public.&lt;/p&gt;
4324
4325 &lt;p&gt;The package is not trivial to backport to Debian Stable/Jessie, as
4326 it depend on several python modules currently missing in Jessie (at
4327 least python-instagram, python-flickrapi and
4328 python-requests-toolbelt).&lt;/p&gt;
4329
4330 &lt;p&gt;(I have uploaded
4331 &lt;a href=&quot;https://screenshots.debian.net/package/creepy&quot;&gt;the image to
4332 screenshots.debian.net&lt;/a&gt; and licensed it under the same terms as the
4333 Creepy program in Debian.)&lt;/p&gt;
4334 </description>
4335 </item>
4336
4337 <item>
4338 <title>Always download Debian packages using Tor - the simple recipe</title>
4339 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</link>
4340 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html</guid>
4341 <pubDate>Fri, 15 Jan 2016 00:30:00 +0100</pubDate>
4342 <description>&lt;p&gt;During his DebConf15 keynote, Jacob Appelbaum
4343 &lt;a href=&quot;https://summit.debconf.org/debconf15/meeting/331/what-is-to-be-done/&quot;&gt;observed
4344 that those listening on the Internet lines would have good reason to
4345 believe a computer have a given security hole&lt;/a&gt; if it download a
4346 security fix from a Debian mirror. This is a good reason to always
4347 use encrypted connections to the Debian mirror, to make sure those
4348 listening do not know which IP address to attack. In August, Richard
4349 Hartmann observed that encryption was not enough, when it was possible
4350 to interfere download size to security patches or the fact that
4351 download took place shortly after a security fix was released, and
4352 &lt;a href=&quot;http://richardhartmann.de/blog/posts/2015/08/24-Tor-enabled_Debian_mirror/&quot;&gt;proposed
4353 to always use Tor to download packages from the Debian mirror&lt;/a&gt;. He
4354 was not the first to propose this, as the
4355 &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;
4356 package by Tim Retout already existed to make it easy to convince apt
4357 to use &lt;a href=&quot;https://www.torproject.org/&quot;&gt;Tor&lt;/a&gt;, but I was not
4358 aware of that package when I read the blog post from Richard.&lt;/p&gt;
4359
4360 &lt;p&gt;Richard discussed the idea with Peter Palfrader, one of the Debian
4361 sysadmins, and he set up a Tor hidden service on one of the central
4362 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
4363 it possible to download packages directly between two tor nodes,
4364 making sure the network traffic always were encrypted.&lt;/p&gt;
4365
4366 &lt;p&gt;Here is a short recipe for enabling this on your machine, by
4367 installing &lt;tt&gt;apt-transport-tor&lt;/tt&gt; and replacing http and https
4368 urls with tor+http and tor+https, and using the hidden service instead
4369 of the official Debian mirror site. I recommend installing
4370 &lt;tt&gt;etckeeper&lt;/tt&gt; before you start to have a history of the changes
4371 done in /etc/.&lt;/p&gt;
4372
4373 &lt;blockquote&gt;&lt;pre&gt;
4374 apt install apt-transport-tor
4375 sed -i &#39;s% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%&#39; /etc/apt/sources.list
4376 sed -i &#39;s% http% tor+http%&#39; /etc/apt/sources.list
4377 &lt;/pre&gt;&lt;/blockquote&gt;
4378
4379 &lt;p&gt;If you have more sources listed in /etc/apt/sources.list.d/, run
4380 the sed commands for these too. The sed command is assuming your are
4381 using the ftp.debian.org Debian mirror. Adjust the command (or just
4382 edit the file manually) to match your mirror.&lt;/p&gt;
4383
4384 &lt;p&gt;This work in Debian Jessie and later. Note that tools like
4385 &lt;tt&gt;apt-file&lt;/tt&gt; only recently started using the apt transport
4386 system, and do not work with these tor+http URLs. For
4387 &lt;tt&gt;apt-file&lt;/tt&gt; you need the version currently in experimental,
4388 which need a recent apt version currently only in unstable. So if you
4389 need a working &lt;tt&gt;apt-file&lt;/tt&gt;, this is not for you.&lt;/p&gt;
4390
4391 &lt;p&gt;Another advantage from this change is that your machine will start
4392 using Tor regularly and at fairly random intervals (every time you
4393 update the package lists or upgrade or install a new package), thus
4394 masking other Tor traffic done from the same machine. Using Tor will
4395 become normal for the machine in question.&lt;/p&gt;
4396
4397 &lt;p&gt;On &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox&lt;/a&gt;, APT
4398 is set up by default to use &lt;tt&gt;apt-transport-tor&lt;/tt&gt; when Tor is
4399 enabled. It would be great if it was the default on any Debian
4400 system.&lt;/p&gt;
4401 </description>
4402 </item>
4403
4404 <item>
4405 <title>OpenALPR, find car license plates in video streams - nice free software</title>
4406 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</link>
4407 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html</guid>
4408 <pubDate>Wed, 23 Dec 2015 01:00:00 +0100</pubDate>
4409 <description>&lt;p&gt;When I was a kid, we used to collect &quot;car numbers&quot;, as we used to
4410 call the car license plate numbers in those days. I would write the
4411 numbers down in my little book and compare notes with the other kids
4412 to see how many region codes we had seen and if we had seen some
4413 exotic or special region codes and numbers. It was a fun game to pass
4414 time, as we kids have plenty of it.&lt;/p&gt;
4415
4416 &lt;p&gt;A few days I came across
4417 &lt;a href=&quot;https://github.com/openalpr/openalpr&quot;&gt;the OpenALPR
4418 project&lt;/a&gt;, a free software project to automatically discover and
4419 report license plates in images and video streams, and provide the
4420 &quot;car numbers&quot; in a machine readable format. I&#39;ve been looking for
4421 such system for a while now, because I believe it is a bad idea that the
4422 &lt;a href=&quot;https://en.wikipedia.org/wiki/Automatic_number_plate_recognition&quot;&gt;automatic
4423 number plate recognition&lt;/a&gt; tool only is available in the hands of
4424 the powerful, and want it to be available also for the powerless to
4425 even the score when it comes to surveillance and sousveillance. I
4426 discovered the developer
4427 &lt;a href=&quot;https://bugs.debian.org/747509&quot;&gt;wanted to get the tool into
4428 Debian&lt;/a&gt;, and as I too wanted it to be in Debian, I volunteered to
4429 help him get it into shape to get the package uploaded into the Debian
4430 archive.&lt;/p&gt;
4431
4432 &lt;p&gt;Today we finally managed to get the package into shape and uploaded
4433 it into Debian, where it currently
4434 &lt;a href=&quot;https://ftp-master.debian.org//new/openalpr_2.2.1-1.html&quot;&gt;waits
4435 in the NEW queue&lt;/a&gt; for review by the Debian ftpmasters.&lt;/p&gt;
4436
4437 &lt;p&gt;I guess you are wondering why on earth such tool would be useful
4438 for the common folks, ie those not running a large government
4439 surveillance system? Well, I plan to put it in a computer on my bike
4440 and in my car, tracking the cars nearby and allowing me to be notified
4441 when number plates on my watch list are discovered. Another use case
4442 was suggested by a friend of mine, who wanted to set it up at his home
4443 to open the car port automatically when it discovered the plate on his
4444 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
4445 capable of placing his license plate number of a piece of cardboard to
4446 open his car port, men replied that it was always unlocked anyway. I
4447 guess for such use case it make sense. I am sure there are other use
4448 cases too, for those with imagination and a vision.&lt;/p&gt;
4449
4450 &lt;p&gt;If you want to build your own version of the Debian package, check
4451 out the upstream git source and symlink ./distros/debian to ./debian/
4452 before running &quot;debuild&quot; to build the source. Or wait a bit until the
4453 package show up in unstable.&lt;/p&gt;
4454 </description>
4455 </item>
4456
4457 <item>
4458 <title>Using appstream with isenkram to install hardware related packages in Debian</title>
4459 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</link>
4460 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html</guid>
4461 <pubDate>Sun, 20 Dec 2015 12:20:00 +0100</pubDate>
4462 <description>&lt;p&gt;Around three years ago, I created
4463 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;the isenkram
4464 system&lt;/a&gt; to get a more practical solution in Debian for handing
4465 hardware related packages. A GUI system in the isenkram package will
4466 present a pop-up dialog when some hardware dongle supported by
4467 relevant packages in Debian is inserted into the machine. The same
4468 lookup mechanism to detect packages is available as command line
4469 tools in the isenkram-cli package. In addition to mapping hardware,
4470 it will also map kernel firmware files to packages and make it easy to
4471 install needed firmware packages automatically. The key for this
4472 system to work is a good way to map hardware to packages, in other
4473 words, allow packages to announce what hardware they will work
4474 with.&lt;/p&gt;
4475
4476 &lt;p&gt;I started by providing data files in the isenkram source, and
4477 adding code to download the latest version of these data files at run
4478 time, to ensure every user had the most up to date mapping available.
4479 I also added support for storing the mapping in the Packages file in
4480 the apt repositories, but did not push this approach because while I
4481 was trying to figure out how to best store hardware/package mappings,
4482 &lt;a href=&quot;http://www.freedesktop.org/software/appstream/docs/&quot;&gt;the
4483 appstream system&lt;/a&gt; was announced. I got in touch and suggested to
4484 add the hardware mapping into that data set to be able to use
4485 appstream as a data source, and this was accepted at least for the
4486 Debian version of appstream.&lt;/p&gt;
4487
4488 &lt;p&gt;A few days ago using appstream in Debian for this became possible,
4489 and today I uploaded a new version 0.20 of isenkram adding support for
4490 appstream as a data source for mapping hardware to packages. The only
4491 package so far using appstream to announce its hardware support is my
4492 pymissile package. I got help from Matthias Klumpp with figuring out
4493 how do add the required
4494 &lt;a href=&quot;https://appstream.debian.org/html/sid/main/metainfo/pymissile.html&quot;&gt;metadata
4495 in pymissile&lt;/a&gt;. I added a file debian/pymissile.metainfo.xml with
4496 this content:&lt;/p&gt;
4497
4498 &lt;blockquote&gt;&lt;pre&gt;
4499 &amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&amp;gt;
4500 &amp;lt;component&amp;gt;
4501 &amp;lt;id&amp;gt;pymissile&amp;lt;/id&amp;gt;
4502 &amp;lt;metadata_license&amp;gt;MIT&amp;lt;/metadata_license&amp;gt;
4503 &amp;lt;name&amp;gt;pymissile&amp;lt;/name&amp;gt;
4504 &amp;lt;summary&amp;gt;Control original Striker USB Missile Launcher&amp;lt;/summary&amp;gt;
4505 &amp;lt;description&amp;gt;
4506 &amp;lt;p&amp;gt;
4507 Pymissile provides a curses interface to control an original
4508 Marks and Spencer / Striker USB Missile Launcher, as well as a
4509 motion control script to allow a webcamera to control the
4510 launcher.
4511 &amp;lt;/p&amp;gt;
4512 &amp;lt;/description&amp;gt;
4513 &amp;lt;provides&amp;gt;
4514 &amp;lt;modalias&amp;gt;usb:v1130p0202d*&amp;lt;/modalias&amp;gt;
4515 &amp;lt;/provides&amp;gt;
4516 &amp;lt;/component&amp;gt;
4517 &lt;/pre&gt;&lt;/blockquote&gt;
4518
4519 &lt;p&gt;The key for isenkram is the component/provides/modalias value,
4520 which is a glob style match rule for hardware specific strings
4521 (modalias strings) provided by the Linux kernel. In this case, it
4522 will map to all USB devices with vendor code 1130 and product code
4523 0202.&lt;/p&gt;
4524
4525 &lt;p&gt;Note, it is important that the license of all the metadata files
4526 are compatible to have permissions to aggregate them into archive wide
4527 appstream files. Matthias suggested to use MIT or BSD licenses for
4528 these files. A challenge is figuring out a good id for the data, as
4529 it is supposed to be globally unique and shared across distributions
4530 (in other words, best to coordinate with upstream what to use). But
4531 it can be changed later or, so we went with the package name as
4532 upstream for this project is dormant.&lt;/p&gt;
4533
4534 &lt;p&gt;To get the metadata file installed in the correct location for the
4535 mirror update scripts to pick it up and include its content the
4536 appstream data source, the file must be installed in the binary
4537 package under /usr/share/appdata/. I did this by adding the following
4538 line to debian/pymissile.install:&lt;/p&gt;
4539
4540 &lt;blockquote&gt;&lt;pre&gt;
4541 debian/pymissile.metainfo.xml usr/share/appdata
4542 &lt;/pre&gt;&lt;/blockquote&gt;
4543
4544 &lt;p&gt;With that in place, the command line tool isenkram-lookup will list
4545 all packages useful on the current computer automatically, and the GUI
4546 pop-up handler will propose to install the package not already
4547 installed if a hardware dongle is inserted into the machine in
4548 question.&lt;/p&gt;
4549
4550 &lt;p&gt;Details of the modalias field in appstream is available from the
4551 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt; proposal.&lt;/p&gt;
4552
4553 &lt;p&gt;To locate the modalias values of all hardware present in a machine,
4554 try running this command on the command line:&lt;/p&gt;
4555
4556 &lt;blockquote&gt;&lt;pre&gt;
4557 cat $(find /sys/devices/|grep modalias)
4558 &lt;/pre&gt;&lt;/blockquote&gt;
4559
4560 &lt;p&gt;To learn more about the isenkram system, please check out
4561 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;my
4562 blog posts tagged isenkram&lt;/a&gt;.&lt;/p&gt;
4563 </description>
4564 </item>
4565
4566 <item>
4567 <title>The GNU General Public License is not magic pixie dust</title>
4568 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</link>
4569 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html</guid>
4570 <pubDate>Mon, 30 Nov 2015 09:55:00 +0100</pubDate>
4571 <description>&lt;p&gt;A blog post from my fellow Debian developer Paul Wise titled
4572 &quot;&lt;a href=&quot;http://bonedaddy.net/pabs3/log/2015/11/27/sfc-supporter/&quot;&gt;The
4573 GPL is not magic pixie dust&lt;/a&gt;&quot; explain the importance of making sure
4574 the &lt;a href=&quot;http://www.gnu.org/copyleft/gpl.html&quot;&gt;GPL&lt;/a&gt; is enforced.
4575 I quote the blog post from Paul in full here with his permission:&lt;p&gt;
4576
4577 &lt;blockquote&gt;
4578
4579 &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;
4580
4581 &lt;blockquote&gt;
4582 The GPL is not magic pixie dust. It does not work by itself.&lt;br/&gt;
4583
4584 The first step is to choose a
4585 &lt;a href=&quot;https://copyleft.org/&quot;&gt;copyleft&lt;/a&gt; license for your
4586 code.&lt;br/&gt;
4587
4588 The next step is, when someone fails to follow that copyleft license,
4589 &lt;b&gt;it must be enforced&lt;/b&gt;&lt;br/&gt;
4590
4591 and its a simple fact of our modern society that such type of
4592 work&lt;br/&gt;
4593
4594 is incredibly expensive to do and incredibly difficult to do.
4595 &lt;/blockquote&gt;
4596
4597 &lt;p&gt;&lt;small&gt;-- &lt;a href=&quot;http://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt;, in
4598 &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in Freedom&quot;&gt;FaiF&lt;/a&gt;
4599 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode
4600 0x57&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;
4601
4602 &lt;p&gt;As the Debian Website
4603 &lt;a href=&quot;https://bugs.debian.org/794116&quot;&gt;used&lt;/a&gt;
4604 &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;
4605 imply, public domain and permissively licensed software can lead to
4606 the production of more proprietary software as people discover useful
4607 software, extend it and or incorporate it into their hardware or
4608 software products. Copyleft licenses such as the GNU GPL were created
4609 to close off this avenue to the production of proprietary software but
4610 such licenses are not enough. With the ongoing adoption of Free
4611 Software by individuals and groups, inevitably the community&#39;s
4612 expectations of license compliance are violated, usually out of
4613 ignorance of the way Free Software works, but not always. As Karen
4614 and Bradley explained in &lt;a href=&quot;http://faif.us/&quot; title=&quot;Free as in
4615 Freedom&quot;&gt;FaiF&lt;/a&gt;
4616 &lt;a href=&quot;http://faif.us/cast/2015/nov/24/0x57/&quot;&gt;episode 0x57&lt;/a&gt;,
4617 copyleft is nothing if no-one is willing and able to stand up in court
4618 to protect it. The reality of today&#39;s world is that legal
4619 representation is expensive, difficult and time consuming. With
4620 &lt;a href=&quot;http://gpl-violations.org/&quot;&gt;gpl-violations.org&lt;/a&gt; in hiatus
4621 &lt;a href=&quot;http://gpl-violations.org/news/20151027-homepage-recovers/&quot;&gt;until&lt;/a&gt;
4622 some time in 2016, the &lt;a href=&quot;https://sfconservancy.org/&quot;&gt;Software
4623 Freedom Conservancy&lt;/a&gt; (a tax-exempt charity) is the major defender
4624 of the Linux project, Debian and other groups against GPL violations.
4625 In March the SFC supported a
4626 &lt;a href=&quot;https://sfconservancy.org/news/2015/mar/05/vmware-lawsuit/&quot;&gt;lawsuit
4627 by Christoph Hellwig&lt;/a&gt; against VMware for refusing to
4628 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html&quot;&gt;comply
4629 with the GPL&lt;/a&gt; in relation to their use of parts of the Linux
4630 kernel. Since then two of their sponsors pulled corporate funding and
4631 conferences
4632 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;blocked
4633 or cancelled their talks&lt;/a&gt;. As a result they have decided to rely
4634 less on corporate funding and more on the broad community of
4635 individuals who support Free Software and copyleft. So the SFC has
4636 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/23/2015fundraiser/&quot;&gt;launched&lt;/a&gt;
4637 a &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;campaign&lt;/a&gt; to create
4638 a community of folks who stand up for copyleft and the GPL by
4639 supporting their work on promoting and supporting copyleft and Free
4640 Software.&lt;/p&gt;
4641
4642 &lt;p&gt;If you support Free Software,
4643 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/26/like-what-I-do/&quot;&gt;like&lt;/a&gt;
4644 what the SFC do, agree with their
4645 &lt;a href=&quot;https://sfconservancy.org/linux-compliance/principles.html&quot;&gt;compliance
4646 principles&lt;/a&gt;, are happy about their
4647 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;successes&lt;/a&gt; in 2015,
4648 work on a project that is an SFC
4649 &lt;a href=&quot;https://sfconservancy.org/members/current/&quot;&gt;member&lt;/a&gt; and or
4650 just want to stand up for copyleft, please join
4651 &lt;a href=&quot;https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA&quot;&gt;Christopher
4652 Allan Webber&lt;/a&gt;,
4653 &lt;a href=&quot;https://sfconservancy.org/blog/2015/nov/24/faif-carols-fundraiser/&quot;&gt;Carol
4654 Smith&lt;/a&gt;,
4655 &lt;a href=&quot;http://www.jonobacon.org/2015/11/25/supporting-software-freedom-conservancy/&quot;&gt;Jono
4656 Bacon&lt;/a&gt;, myself and
4657 &lt;a href=&quot;https://sfconservancy.org/sponsors/#supporters&quot;&gt;others&lt;/a&gt; in
4658 becoming a
4659 &lt;a href=&quot;https://sfconservancy.org/supporter/&quot;&gt;supporter&lt;/a&gt;. For the
4660 next week your donation will be
4661 &lt;a href=&quot;https://sfconservancy.org/news/2015/nov/27/black-friday/&quot;&gt;matched&lt;/a&gt;
4662 by an anonymous donor. Please also consider asking your employer to
4663 match your donation or become a sponsor of SFC. Don&#39;t forget to
4664 spread the word about your support for SFC via email, your blog and or
4665 social media accounts.&lt;/p&gt;
4666
4667 &lt;/blockquote&gt;
4668
4669 &lt;p&gt;I agree with Paul on this topic and just signed up as a Supporter
4670 of Software Freedom Conservancy myself. Perhaps you should be a
4671 supporter too?&lt;/p&gt;
4672 </description>
4673 </item>
4674
4675 <item>
4676 <title>PGP key transition statement for key EE4E02F9</title>
4677 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</link>
4678 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html</guid>
4679 <pubDate>Tue, 17 Nov 2015 10:50:00 +0100</pubDate>
4680 <description>&lt;p&gt;I&#39;ve needed a new OpenPGP key for a while, but have not had time to
4681 set it up properly. I wanted to generate it offline and have it
4682 available on &lt;a href=&quot;http://shop.kernelconcepts.de/#openpgp&quot;&gt;a OpenPGP
4683 smart card&lt;/a&gt; for daily use, and learning how to do it and finding
4684 time to sit down with an offline machine almost took forever. But
4685 finally I&#39;ve been able to complete the process, and have now moved
4686 from my old GPG key to a new GPG key. See
4687 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/images/2015-11-17-new-gpg-key-transition.txt&quot;&gt;the
4688 full transition statement, signed with both my old and new key&lt;/a&gt; for
4689 the details. This is my new key:&lt;/p&gt;
4690
4691 &lt;pre&gt;
4692 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]
4693 Key fingerprint = 3AC7 B2E3 ACA5 DF87 78F1 D827 111D 6B29 EE4E 02F9
4694 uid Petter Reinholdtsen &amp;lt;pere@hungry.com&amp;gt;
4695 uid Petter Reinholdtsen &amp;lt;pere@debian.org&amp;gt;
4696 sub 4096R/87BAFB0E 2015-11-03 [expires: 2019-11-02]
4697 sub 4096R/F91E6DE9 2015-11-03 [expires: 2019-11-02]
4698 sub 4096R/A0439BAB 2015-11-03 [expires: 2019-11-02]
4699 &lt;/pre&gt;
4700
4701 &lt;p&gt;The key can be downloaded from the OpenPGP key servers, signed by
4702 my old key.&lt;/p&gt;
4703
4704 &lt;p&gt;If you signed my old key
4705 (&lt;a href=&quot;http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html&quot;&gt;DB4CCC4B2A30D729&lt;/a&gt;),
4706 I&#39;d very much appreciate a signature on my new key, details and
4707 instructions in the transition statement. I m happy to reciprocate if
4708 you have a similarly signed transition statement to present.&lt;/p&gt;
4709 </description>
4710 </item>
4711
4712 <item>
4713 <title>The life and death of a laptop battery</title>
4714 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</link>
4715 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html</guid>
4716 <pubDate>Thu, 24 Sep 2015 16:00:00 +0200</pubDate>
4717 <description>&lt;p&gt;When I get a new laptop, the battery life time at the start is OK.
4718 But this do not last. The last few laptops gave me a feeling that
4719 within a year, the life time is just a fraction of what it used to be,
4720 and it slowly become painful to use the laptop without power connected
4721 all the time. Because of this, when I got a new Thinkpad X230 laptop
4722 about two years ago, I decided to monitor its battery state to have
4723 more hard facts when the battery started to fail.&lt;/p&gt;
4724
4725 &lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2015-09-24-laptop-battery-graph.png&quot;/&gt;
4726
4727 &lt;p&gt;First I tried to find a sensible Debian package to record the
4728 battery status, assuming that this must be a problem already handled
4729 by someone else. I found
4730 &lt;a href=&quot;https://tracker.debian.org/pkg/battery-stats&quot;&gt;battery-stats&lt;/a&gt;,
4731 which collects statistics from the battery, but it was completely
4732 broken. I sent a few suggestions to the maintainer, but decided to
4733 write my own collector as a shell script while I waited for feedback
4734 from him. Via
4735 &lt;a href=&quot;http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html&quot;&gt;a
4736 blog post about the battery development on a MacBook Air&lt;/a&gt; I also
4737 discovered
4738 &lt;a href=&quot;https://github.com/jradavenport/batlog.git&quot;&gt;batlog&lt;/a&gt;, not
4739 available in Debian.&lt;/p&gt;
4740
4741 &lt;p&gt;I started my collector 2013-07-15, and it has been collecting
4742 battery stats ever since. Now my
4743 /var/log/hjemmenett-battery-status.log file contain around 115,000
4744 measurements, from the time the battery was working great until now,
4745 when it is unable to charge above 7% of original capacity. My
4746 collector shell script is quite simple and look like this:&lt;/p&gt;
4747
4748 &lt;pre&gt;
4749 #!/bin/sh
4750 # Inspired by
4751 # http://www.ifweassume.com/2013/08/the-de-evolution-of-my-laptop-battery.html
4752 # See also
4753 # http://blog.sleeplessbeastie.eu/2013/01/02/debian-how-to-monitor-battery-capacity/
4754 logfile=/var/log/hjemmenett-battery-status.log
4755
4756 files=&quot;manufacturer model_name technology serial_number \
4757 energy_full energy_full_design energy_now cycle_count status&quot;
4758
4759 if [ ! -e &quot;$logfile&quot; ] ; then
4760 (
4761 printf &quot;timestamp,&quot;
4762 for f in $files; do
4763 printf &quot;%s,&quot; $f
4764 done
4765 echo
4766 ) &gt; &quot;$logfile&quot;
4767 fi
4768
4769 log_battery() {
4770 # Print complete message in one echo call, to avoid race condition
4771 # when several log processes run in parallel.
4772 msg=$(printf &quot;%s,&quot; $(date +%s); \
4773 for f in $files; do \
4774 printf &quot;%s,&quot; $(cat $f); \
4775 done)
4776 echo &quot;$msg&quot;
4777 }
4778
4779 cd /sys/class/power_supply
4780
4781 for bat in BAT*; do
4782 (cd $bat &amp;&amp; log_battery &gt;&gt; &quot;$logfile&quot;)
4783 done
4784 &lt;/pre&gt;
4785
4786 &lt;p&gt;The script is called when the power management system detect a
4787 change in the power status (power plug in or out), and when going into
4788 and out of hibernation and suspend. In addition, it collect a value
4789 every 10 minutes. This make it possible for me know when the battery
4790 is discharging, charging and how the maximum charge change over time.
4791 The code for the Debian package
4792 &lt;a href=&quot;https://github.com/petterreinholdtsen/battery-status&quot;&gt;is now
4793 available on github&lt;/a&gt;.&lt;/p&gt;
4794
4795 &lt;p&gt;The collected log file look like this:&lt;/p&gt;
4796
4797 &lt;pre&gt;
4798 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
4799 1376591133,LGC,45N1025,Li-ion,974,62800000,62160000,39050000,0,Discharging,
4800 [...]
4801 1443090528,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
4802 1443090601,LGC,45N1025,Li-ion,974,4900000,62160000,4900000,0,Full,
4803 &lt;/pre&gt;
4804
4805 &lt;p&gt;I wrote a small script to create a graph of the charge development
4806 over time. This graph depicted above show the slow death of my laptop
4807 battery.&lt;/p&gt;
4808
4809 &lt;p&gt;But why is this happening? Why are my laptop batteries always
4810 dying in a year or two, while the batteries of space probes and
4811 satellites keep working year after year. If we are to believe
4812 &lt;a href=&quot;http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries&quot;&gt;Battery
4813 University&lt;/a&gt;, the cause is me charging the battery whenever I have a
4814 chance, and the fix is to not charge the Lithium-ion batteries to 100%
4815 all the time, but to stay below 90% of full charge most of the time.
4816 I&#39;ve been told that the Tesla electric cars
4817 &lt;a href=&quot;http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit&quot;&gt;limit
4818 the charge of their batteries to 80%&lt;/a&gt;, with the option to charge to
4819 100% when preparing for a longer trip (not that I would want a car
4820 like Tesla where rights to privacy is abandoned, but that is another
4821 story), which I guess is the option we should have for laptops on
4822 Linux too.&lt;/p&gt;
4823
4824 &lt;p&gt;Is there a good and generic way with Linux to tell the battery to
4825 stop charging at 80%, unless requested to charge to 100% once in
4826 preparation for a longer trip? I found
4827 &lt;a href=&quot;http://askubuntu.com/questions/34452/how-can-i-limit-battery-charging-to-80-capacity&quot;&gt;one
4828 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
4829 80%&lt;/a&gt;, but could not get it to work (kernel module refused to
4830 load).&lt;/p&gt;
4831
4832 &lt;p&gt;I wonder why the battery capacity was reported to be more than 100%
4833 at the start. I also wonder why the &quot;full capacity&quot; increases some
4834 times, and if it is possible to repeat the process to get the battery
4835 back to design capacity. And I wonder if the discharge and charge
4836 speed change over time, or if this stay the same. I did not yet try
4837 to write a tool to calculate the derivative values of the battery
4838 level, but suspect some interesting insights might be learned from
4839 those.&lt;/p&gt;
4840
4841 &lt;p&gt;Update 2015-09-24: I got a tip to install the packages
4842 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
4843 packages instead of the tp-smapi-dkms package I had tried to use
4844 initially, and use &#39;tlp setcharge 40 80&#39; to change when charging start
4845 and stop. I&#39;ve done so now, but expect my existing battery is toast
4846 and need to be replaced. The proposal is unfortunately Thinkpad
4847 specific.&lt;/p&gt;
4848 </description>
4849 </item>
4850
4851 <item>
4852 <title>New laptop - some more clues and ideas based on feedback</title>
4853 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</link>
4854 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html</guid>
4855 <pubDate>Sun, 5 Jul 2015 21:40:00 +0200</pubDate>
4856 <description>&lt;p&gt;Several people contacted me after my previous blog post about my
4857 need for a new laptop, and provided very useful feedback. I wish to
4858 thank every one of these. Several pointed me to the possibility of
4859 fixing my X230, and I am already in the process of getting Lenovo to
4860 do so thanks to the on site, next day support contract covering the
4861 machine. But the battery is almost useless (I expect to replace it
4862 with a non-official battery) and I do not expect the machine to live
4863 for many more years, so it is time to plan its replacement. If I did
4864 not have a support contract, it was suggested to find replacement parts
4865 using &lt;a href=&quot;http://www.francecrans.com/&quot;&gt;FrancEcrans&lt;/a&gt;, but it
4866 might present a language barrier as I do not understand French.&lt;/p&gt;
4867
4868 &lt;p&gt;One tip I got was to use the
4869 &lt;a href=&quot;https://skinflint.co.uk/?cat=nb&quot;&gt;Skinflint&lt;/a&gt; web service to
4870 compare laptop models. It seem to have more models available than
4871 prisjakt.no. Another tip I got from someone I know have similar
4872 keyboard preferences was that the HP EliteBook 840 keyboard is not
4873 very good, and this matches my experience with earlier EliteBook
4874 keyboards I tested. Because of this, I will not consider it any further.
4875
4876 &lt;p&gt;When I wrote my blog post, I was not aware of Thinkpad X250, the
4877 newest Thinkpad X model. The keyboard reintroduces mouse buttons
4878 (which is missing from the X240), and is working fairly well with
4879 Debian Sid/Unstable according to
4880 &lt;a href=&quot;http://www.corsac.net/X250/&quot;&gt;Corsac.net&lt;/a&gt;. The reports I
4881 got on the keyboard quality are not consistent. Some say the keyboard
4882 is good, others say it is ok, while others say it is not very good.
4883 Those with experience from X41 and and X60 agree that the X250
4884 keyboard is not as good as those trusty old laptops, and suggest I
4885 keep and fix my X230 instead of upgrading, or get a used X230 to
4886 replace it. I&#39;m also told that the X250 lack leds for caps lock, disk
4887 activity and battery status, which is very convenient on my X230. I&#39;m
4888 also told that the CPU fan is running very often, making it a bit
4889 noisy. In any case, the X250 do not work out of the box with Debian
4890 Stable/Jessie, one of my requirements.&lt;/p&gt;
4891
4892 &lt;p&gt;I have also gotten a few vendor proposals, one was
4893 &lt;a href=&quot;http://pro-star.com&quot;&gt;Pro-Star&lt;/a&gt;, another was
4894 &lt;a href=&quot;http://shop.gluglug.org.uk/product/libreboot-x200/&quot;&gt;Libreboot&lt;/a&gt;.
4895 The latter look very attractive to me.&lt;/p&gt;
4896
4897 &lt;p&gt;Again, thank you all for the very useful feedback. It help a lot
4898 as I keep looking for a replacement.&lt;/p&gt;
4899
4900 &lt;p&gt;Update 2015-07-06: I was recommended to check out the
4901 &lt;a href=&quot;&quot;&gt;lapstore.de&lt;/a&gt; web shop for used laptops. They got several
4902 different
4903 &lt;a href=&quot;http://www.lapstore.de/f.php/shop/lapstore/f/411/lang/x/kw/Lenovo_ThinkPad_X_Serie/&quot;&gt;old
4904 thinkpad X models&lt;/a&gt;, and provide one year warranty.&lt;/p&gt;
4905 </description>
4906 </item>
4907
4908 <item>
4909 <title>Time to find a new laptop, as the old one is broken after only two years</title>
4910 <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>
4911 <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>
4912 <pubDate>Fri, 3 Jul 2015 07:10:00 +0200</pubDate>
4913 <description>&lt;p&gt;My primary work horse laptop is failing, and will need a
4914 replacement soon. The left 5 cm of the screen on my Thinkpad X230
4915 started flickering yesterday, and I suspect the cause is a broken
4916 cable, as changing the angle of the screen some times get rid of the
4917 flickering.&lt;/p&gt;
4918
4919 &lt;p&gt;My requirements have not really changed since I bought it, and is
4920 still as
4921 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;I
4922 described them in 2013&lt;/a&gt;. The last time I bought a laptop, I had
4923 good help from
4924 &lt;a href=&quot;http://www.prisjakt.no/category.php?k=353&quot;&gt;prisjakt.no&lt;/a&gt;
4925 where I could select at least a few of the requirements (mouse pin,
4926 wifi, weight) and go through the rest manually. Three button mouse
4927 and a good keyboard is not available as an option, and all the three
4928 laptop models proposed today (Thinkpad X240, HP EliteBook 820 G1 and
4929 G2) lack three mouse buttons). It is also unclear to me how good the
4930 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
4931 the keyboard, even if the quality and robustness in the X series have
4932 deteriorated since X41.&lt;/p&gt;
4933
4934 &lt;p&gt;I wonder how I can find a sensible laptop when none of the options
4935 seem sensible to me? Are there better services around to search the
4936 set of available laptops for features? Please send me an email if you
4937 have suggestions.&lt;/p&gt;
4938
4939 &lt;p&gt;Update 2015-07-23: I got a suggestion to check out the FSF
4940 &lt;a href=&quot;http://www.fsf.org/resources/hw/endorsement/respects-your-freedom&quot;&gt;list
4941 of endorsed hardware&lt;/a&gt;, which is useful background information.&lt;/p&gt;
4942 </description>
4943 </item>
4944
4945 <item>
4946 <title>How to stay with sysvinit in Debian Jessie</title>
4947 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</link>
4948 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html</guid>
4949 <pubDate>Sat, 22 Nov 2014 01:00:00 +0100</pubDate>
4950 <description>&lt;p&gt;By now, it is well known that Debian Jessie will not be using
4951 sysvinit as its boot system by default. But how can one keep using
4952 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
4953 courtesy of
4954 &lt;a href=&quot;http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html&quot;&gt;Erich
4955 Schubert&lt;/a&gt; and
4956 &lt;a href=&quot;http://smcv.pseudorandom.co.uk/2014/still_universal/&quot;&gt;Simon
4957 McVittie&lt;/a&gt;.
4958
4959 &lt;p&gt;If you already are using Wheezy and want to upgrade to Jessie and
4960 keep sysvinit as your boot system, create a file
4961 &lt;tt&gt;/etc/apt/preferences.d/use-sysvinit&lt;/tt&gt; with this content before
4962 you upgrade:&lt;/p&gt;
4963
4964 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4965 Package: systemd-sysv
4966 Pin: release o=Debian
4967 Pin-Priority: -1
4968 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4969
4970 &lt;p&gt;This file content will tell apt and aptitude to not consider
4971 installing systemd-sysv as part of any installation and upgrade
4972 solution when resolving dependencies, and thus tell it to avoid
4973 systemd as a default boot system. The end result should be that the
4974 upgraded system keep using sysvinit.&lt;/p&gt;
4975
4976 &lt;p&gt;If you are installing Jessie for the first time, there is no way to
4977 get sysvinit installed by default (debootstrap used by
4978 debian-installer have no option for this), but one can tell the
4979 installer to switch to sysvinit before the first boot. Either by
4980 using a kernel argument to the installer, or by adding a line to the
4981 preseed file used. First, the kernel command line argument:
4982
4983 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4984 preseed/late_command=&quot;in-target apt-get install --purge -y sysvinit-core&quot;
4985 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4986
4987 &lt;p&gt;Next, the line to use in a preseed file:&lt;/p&gt;
4988
4989 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
4990 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
4991 &lt;/pre&gt;&lt;/blockquote&gt;&lt;p&gt;
4992
4993 &lt;p&gt;One can of course also do this after the first boot by installing
4994 the sysvinit-core package.&lt;/p&gt;
4995
4996 &lt;p&gt;I recommend only using sysvinit if you really need it, as the
4997 sysvinit boot sequence in Debian have several hardware specific bugs
4998 on Linux caused by the fact that it is unpredictable when hardware
4999 devices show up during boot. But on the other hand, the new default
5000 boot system still have a few rough edges I hope will be fixed before
5001 Jessie is released.&lt;/p&gt;
5002
5003 &lt;p&gt;Update 2014-11-26: Inspired by
5004 &lt;ahref=&quot;https://www.mirbsd.org/permalinks/wlog-10-tg_e20141125-tg.htm#e20141125-tg_wlog-10-tg&quot;&gt;a
5005 blog post by Torsten Glaser&lt;/a&gt;, added --purge to the preseed
5006 line.&lt;/p&gt;
5007 </description>
5008 </item>
5009
5010 <item>
5011 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4</title>
5012 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</link>
5013 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html</guid>
5014 <pubDate>Mon, 10 Nov 2014 13:40:00 +0100</pubDate>
5015 <description>&lt;p&gt;The right to communicate with your friends and family in private,
5016 without anyone snooping, is a right every citicen have in a liberal
5017 democracy. But this right is under serious attack these days.&lt;/p&gt;
5018
5019 &lt;p&gt;A while back it occurred to me that one way to make the dragnet
5020 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5021 the whisleblower Snowden) more expensive for Internet email,
5022 is to deliver all email using SMTP via Tor. Such SMTP option would be
5023 a nice addition to the FreedomBox project if we could send email
5024 between FreedomBox machines without leaking metadata about the emails
5025 to the people peeking on the wire. I
5026 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/freedombox-discuss/2014-October/006493.html&quot;&gt;proposed
5027 this on the FreedomBox project mailing list in October&lt;/a&gt; and got a
5028 lot of useful feedback and suggestions. It also became obvious to me
5029 that this was not a novel idea, as the same idea was tested and
5030 documented by Johannes Berg as early as 2006, and both
5031 &lt;a href=&quot;https://github.com/pagekite/Mailpile/wiki/SMTorP&quot;&gt;the
5032 Mailpile&lt;/a&gt; and &lt;a href=&quot;http://dee.su/cables&quot;&gt;the Cables&lt;/a&gt; systems
5033 propose a similar method / protocol to pass emails between users.&lt;/p&gt;
5034
5035 &lt;p&gt;To implement such system one need to set up a Tor hidden service
5036 providing the SMTP protocol on port 25, and use email addresses
5037 looking like username@hidden-service-name.onion. With such addresses
5038 the connections to port 25 on hidden-service-name.onion using Tor will
5039 go to the correct SMTP server. To do this, one need to configure the
5040 Tor daemon to provide the hidden service and the mail server to accept
5041 emails for this .onion domain. To learn more about Exim configuration
5042 in Debian and test the design provided by Johannes Berg in his FAQ, I
5043 set out yesterday to create a Debian package for making it trivial to
5044 set up such SMTP over Tor service based on Debian. Getting it to work
5045 were fairly easy, and
5046 &lt;a href=&quot;https://github.com/petterreinholdtsen/exim4-smtorp&quot;&gt;the
5047 source code for the Debian package&lt;/a&gt; is available from github. I
5048 plan to move it into Debian if further testing prove this to be a
5049 useful approach.&lt;/p&gt;
5050
5051 &lt;p&gt;If you want to test this, set up a blank Debian machine without any
5052 mail system installed (or run &lt;tt&gt;apt-get purge exim4-config&lt;/tt&gt; to
5053 get rid of exim4). Install tor, clone the git repository mentioned
5054 above, build the deb and install it on the machine. Next, run
5055 &lt;tt&gt;/usr/lib/exim4-smtorp/setup-exim-hidden-service&lt;/tt&gt; and follow
5056 the instructions to get the service up and running. Restart tor and
5057 exim when it is done, and test mail delivery using swaks like
5058 this:&lt;/p&gt;
5059
5060 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5061 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5062 --to fbx@dutlqrrmjhtfa3vp.onion
5063 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5064
5065 &lt;p&gt;This will test the SMTP delivery using tor. Replace the email
5066 address with your own address to test your server. :)&lt;/p&gt;
5067
5068 &lt;p&gt;The setup procedure is still to complex, and I hope it can be made
5069 easier and more automatic. Especially the tor setup need more work.
5070 Also, the package include a tor-smtp tool written in C, but its task
5071 should probably be rewritten in some script language to make the deb
5072 architecture independent. It would probably also make the code easier
5073 to review. The tor-smtp tool currently need to listen on a socket for
5074 exim to talk to it and is started using xinetd. It would be better if
5075 no daemon and no socket is needed. I suspect it is possible to get
5076 exim to run a command line tool for delivery instead of talking to a
5077 socket, and hope to figure out how in a future version of this
5078 system.&lt;/p&gt;
5079
5080 &lt;p&gt;Until I wipe my test machine, I can be reached using the
5081 &lt;tt&gt;fbx@dutlqrrmjhtfa3vp.onion&lt;/tt&gt; mail address, deliverable over
5082 SMTorP. :)&lt;/p&gt;
5083 </description>
5084 </item>
5085
5086 <item>
5087 <title>listadmin, the quick way to moderate mailman lists - nice free software</title>
5088 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</link>
5089 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html</guid>
5090 <pubDate>Wed, 22 Oct 2014 20:00:00 +0200</pubDate>
5091 <description>&lt;p&gt;If you ever had to moderate a mailman list, like the ones on
5092 alioth.debian.org, you know the web interface is fairly slow to
5093 operate. First you visit one web page, enter the moderation password
5094 and get a new page shown with a list of all the messages to moderate
5095 and various options for each email address. This take a while for
5096 every list you moderate, and you need to do it regularly to do a good
5097 job as a list moderator. But there is a quick alternative,
5098 &lt;a href=&quot;http://heim.ifi.uio.no/kjetilho/hacks/#listadmin&quot;&gt;the
5099 listadmin program&lt;/a&gt;. It allow you to check lists for new messages
5100 to moderate in a fraction of a second. Here is a test run on two
5101 lists I recently took over:&lt;/p&gt;
5102
5103 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5104 % time listadmin xiph
5105 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5106 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5107
5108 real 0m1.709s
5109 user 0m0.232s
5110 sys 0m0.012s
5111 %
5112 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5113
5114 &lt;p&gt;In 1.7 seconds I had checked two mailing lists and confirmed that
5115 there are no message in the moderation queue. Every morning I
5116 currently moderate 68 mailman lists, and it normally take around two
5117 minutes. When I took over the two pkg-xiph lists above a few days
5118 ago, there were 400 emails waiting in the moderator queue. It took me
5119 less than 15 minutes to process them all using the listadmin
5120 program.&lt;/p&gt;
5121
5122 &lt;p&gt;If you install
5123 &lt;a href=&quot;https://tracker.debian.org/pkg/listadmin&quot;&gt;the listadmin
5124 package&lt;/a&gt; from Debian and create a file &lt;tt&gt;~/.listadmin.ini&lt;/tt&gt;
5125 with content like this, the moderation task is a breeze:&lt;/p&gt;
5126
5127 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5128 username username@example.org
5129 spamlevel 23
5130 default discard
5131 discard_if_reason &quot;Posting restricted to members only. Remove us from your mail list.&quot;
5132
5133 password secret
5134 adminurl https://{domain}/mailman/admindb/{list}
5135 mailman-list@lists.example.com
5136
5137 password hidden
5138 other-list@otherserver.example.org
5139 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5140
5141 &lt;p&gt;There are other options to set as well. Check the manual page to
5142 learn the details.&lt;/p&gt;
5143
5144 &lt;p&gt;If you are forced to moderate lists on a mailman installation where
5145 the SSL certificate is self signed or not properly signed by a
5146 generally accepted signing authority, you can set a environment
5147 variable when calling listadmin to disable SSL verification:&lt;/p&gt;
5148
5149 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5150 PERL_LWP_SSL_VERIFY_HOSTNAME=0 listadmin
5151 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5152
5153 &lt;p&gt;If you want to moderate a subset of the lists you take care of, you
5154 can provide an argument to the listadmin script like I do in the
5155 initial screen dump (the xiph argument). Using an argument, only
5156 lists matching the argument string will be processed. This make it
5157 quick to accept messages if you notice the moderation request in your
5158 email.&lt;/p&gt;
5159
5160 &lt;p&gt;Without the listadmin program, I would never be the moderator of 68
5161 mailing lists, as I simply do not have time to spend on that if the
5162 process was any slower. The listadmin program have saved me hours of
5163 time I could spend elsewhere over the years. It truly is nice free
5164 software.&lt;/p&gt;
5165
5166 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
5167 activities, please send Bitcoin donations to my address
5168 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
5169
5170 &lt;p&gt;Update 2014-10-27: Added missing &#39;username&#39; statement in
5171 configuration example. Also, I&#39;ve been told that the
5172 PERL_LWP_SSL_VERIFY_HOSTNAME=0 setting do not work for everyone. Not
5173 sure why.&lt;/p&gt;
5174 </description>
5175 </item>
5176
5177 <item>
5178 <title>Debian Jessie, PXE and automatic firmware installation</title>
5179 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</link>
5180 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html</guid>
5181 <pubDate>Fri, 17 Oct 2014 14:10:00 +0200</pubDate>
5182 <description>&lt;p&gt;When PXE installing laptops with Debian, I often run into the
5183 problem that the WiFi card require some firmware to work properly.
5184 And it has been a pain to fix this using preseeding in Debian.
5185 Normally something more is needed. But thanks to
5186 &lt;a href=&quot;https://packages.qa.debian.org/i/isenkram.html&quot;&gt;my isenkram
5187 package&lt;/a&gt; and its recent tasksel extension, it has now become easy
5188 to do this using simple preseeding.&lt;/p&gt;
5189
5190 &lt;p&gt;The isenkram-cli package provide tasksel tasks which will install
5191 firmware for the hardware found in the machine (actually, requested by
5192 the kernel modules for the hardware). (It can also install user space
5193 programs supporting the hardware detected, but that is not the focus
5194 of this story.)&lt;/p&gt;
5195
5196 &lt;p&gt;To get this working in the default installation, two preeseding
5197 values are needed. First, the isenkram-cli package must be installed
5198 into the target chroot (aka the hard drive) before tasksel is executed
5199 in the pkgsel step of the debian-installer system. This is done by
5200 preseeding the base-installer/includes debconf value to include the
5201 isenkram-cli package. The package name is next passed to debootstrap
5202 for installation. With the isenkram-cli package in place, tasksel
5203 will automatically use the isenkram tasks to detect hardware specific
5204 packages for the machine being installed and install them, because
5205 isenkram-cli contain tasksel tasks.&lt;/p&gt;
5206
5207 &lt;p&gt;Second, one need to enable the non-free APT repository, because
5208 most firmware unfortunately is non-free. This is done by preseeding
5209 the apt-mirror-setup step. This is unfortunate, but for a lot of
5210 hardware it is the only option in Debian.&lt;/p&gt;
5211
5212 &lt;p&gt;The end result is two lines needed in your preseeding file to get
5213 firmware installed automatically by the installer:&lt;/p&gt;
5214
5215 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5216 base-installer base-installer/includes string isenkram-cli
5217 apt-mirror-setup apt-setup/non-free boolean true
5218 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5219
5220 &lt;p&gt;The current version of isenkram-cli in testing/jessie will install
5221 both firmware and user space packages when using this method. It also
5222 do not work well, so use version 0.15 or later. Installing both
5223 firmware and user space packages might give you a bit more than you
5224 want, so I decided to split the tasksel task in two, one for firmware
5225 and one for user space programs. The firmware task is enabled by
5226 default, while the one for user space programs is not. This split is
5227 implemented in the package currently in unstable.&lt;/p&gt;
5228
5229 &lt;p&gt;If you decide to give this a go, please let me know (via email) how
5230 this recipe work for you. :)&lt;/p&gt;
5231
5232 &lt;p&gt;So, I bet you are wondering, how can this work. First and
5233 foremost, it work because tasksel is modular, and driven by whatever
5234 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
5235 isenkram-cli package place two files for tasksel to find. First there
5236 is the task description file (/usr/share/tasksel/descs/isenkram.desc):&lt;/p&gt;
5237
5238 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5239 Task: isenkram-packages
5240 Section: hardware
5241 Description: Hardware specific packages (autodetected by isenkram)
5242 Based on the detected hardware various hardware specific packages are
5243 proposed.
5244 Test-new-install: show show
5245 Relevance: 8
5246 Packages: for-current-hardware
5247
5248 Task: isenkram-firmware
5249 Section: hardware
5250 Description: Hardware specific firmware packages (autodetected by isenkram)
5251 Based on the detected hardware various hardware specific firmware
5252 packages are proposed.
5253 Test-new-install: mark show
5254 Relevance: 8
5255 Packages: for-current-hardware-firmware
5256 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5257
5258 &lt;p&gt;The key parts are Test-new-install which indicate how the task
5259 should be handled and the Packages line referencing to a script in
5260 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
5261 list of packages to install. The for-current-hardware-firmware script
5262 look like this to list relevant firmware for the machine:
5263
5264 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5265 #!/bin/sh
5266 #
5267 PATH=/usr/sbin:$PATH
5268 export PATH
5269 isenkram-autoinstall-firmware -l
5270 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5271
5272 &lt;p&gt;With those two pieces in place, the firmware is installed by
5273 tasksel during the normal d-i run. :)&lt;/p&gt;
5274
5275 &lt;p&gt;If you want to test what tasksel will install when isenkram-cli is
5276 installed, run &lt;tt&gt;DEBIAN_PRIORITY=critical tasksel --test
5277 --new-install&lt;/tt&gt; to get the list of packages that tasksel would
5278 install.&lt;/p&gt;
5279
5280 &lt;p&gt;&lt;a href=&quot;https://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; will be
5281 pilots in testing this feature, as isenkram is used there now to
5282 install firmware, replacing the earlier scripts.&lt;/p&gt;
5283 </description>
5284 </item>
5285
5286 <item>
5287 <title>Ubuntu used to show the bread prizes at ICA Storo</title>
5288 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</link>
5289 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html</guid>
5290 <pubDate>Sat, 4 Oct 2014 15:20:00 +0200</pubDate>
5291 <description>&lt;p&gt;Today I came across an unexpected Ubuntu boot screen. Above the
5292 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
5293 with Linux kernel 3.2.0-23 (ie probably version 12.04 LTS) was stuck
5294 on a screen normally showing the bread types and prizes:&lt;/p&gt;
5295
5296 &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;
5297
5298 &lt;p&gt;If it had booted as it was supposed to, I would never had known
5299 about this hidden Linux installation. It is interesting what
5300 &lt;a href=&quot;http://revealingerrors.com/&quot;&gt;errors can reveal&lt;/a&gt;.&lt;/p&gt;
5301 </description>
5302 </item>
5303
5304 <item>
5305 <title>New lsdvd release version 0.17 is ready</title>
5306 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</link>
5307 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html</guid>
5308 <pubDate>Sat, 4 Oct 2014 08:40:00 +0200</pubDate>
5309 <description>&lt;p&gt;The &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd project&lt;/a&gt;
5310 got a new set of developers a few weeks ago, after the original
5311 developer decided to step down and pass the project to fresh blood.
5312 This project is now maintained by Petter Reinholdtsen and Steve
5313 Dibb.&lt;/p&gt;
5314
5315 &lt;p&gt;I just wrapped up
5316 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/message/32896061/&quot;&gt;a
5317 new lsdvd release&lt;/a&gt;, available in git or from
5318 &lt;a href=&quot;https://sourceforge.net/projects/lsdvd/files/lsdvd/&quot;&gt;the
5319 download page&lt;/a&gt;. This is the changelog dated 2014-10-03 for version
5320 0.17.&lt;/p&gt;
5321
5322 &lt;ul&gt;
5323
5324 &lt;li&gt;Ignore &#39;phantom&#39; audio, subtitle tracks&lt;/li&gt;
5325 &lt;li&gt;Check for garbage in the program chains, which indicate that a track is
5326 non-existant, to work around additional copy protection&lt;/li&gt;
5327 &lt;li&gt;Fix displaying content type for audio tracks, subtitles&lt;/li&gt;
5328 &lt;li&gt;Fix pallete display of first entry&lt;/li&gt;
5329 &lt;li&gt;Fix include orders&lt;/li&gt;
5330 &lt;li&gt;Ignore read errors in titles that would not be displayed anyway&lt;/li&gt;
5331 &lt;li&gt;Fix the chapter count&lt;/li&gt;
5332 &lt;li&gt;Make sure the array size and the array limit used when initialising
5333 the palette size is the same.&lt;/li&gt;
5334 &lt;li&gt;Fix array printing.&lt;/li&gt;
5335 &lt;li&gt;Correct subsecond calculations.&lt;/li&gt;
5336 &lt;li&gt;Add sector information to the output format.&lt;/li&gt;
5337 &lt;li&gt;Clean up code to be closer to ANSI C and compile without warnings
5338 with more GCC compiler warnings.&lt;/li&gt;
5339
5340 &lt;/ul&gt;
5341
5342 &lt;p&gt;This change bring together patches for lsdvd in use in various
5343 Linux and Unix distributions, as well as patches submitted to the
5344 project the last nine years. Please check it out. :)&lt;/p&gt;
5345 </description>
5346 </item>
5347
5348 <item>
5349 <title>How to test Debian Edu Jessie despite some fatal problems with the installer</title>
5350 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</link>
5351 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html</guid>
5352 <pubDate>Fri, 26 Sep 2014 12:20:00 +0200</pubDate>
5353 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
5354 project&lt;/a&gt; provide a Linux solution for schools, including a
5355 powerful desktop with education software, a central server providing
5356 web pages, user database, user home directories, central login and PXE
5357 boot of both clients without disk and the installation to install Debian
5358 Edu on machines with disk (and a few other services perhaps to small
5359 to mention here). We in the Debian Edu team are currently working on
5360 the Jessie based version, trying to get everything in shape before the
5361 freeze, to avoid having to maintain our own package repository in the
5362 future. The
5363 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Status/Jessie&quot;&gt;current
5364 status&lt;/a&gt; can be seen on the Debian wiki, and there is still heaps of
5365 work left. Some fatal problems block testing, breaking the installer,
5366 but it is possible to work around these to get anyway. Here is a
5367 recipe on how to get the installation limping along.&lt;/p&gt;
5368
5369 &lt;p&gt;First, download the test ISO via
5370 &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;,
5371 &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;
5372 or rsync (use
5373 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-1.iso).
5374 The ISO build was broken on Tuesday, so we do not get a new ISO every
5375 12 hours or so, but thankfully the ISO we already got we are able to
5376 install with some tweaking.&lt;/p&gt;
5377
5378 &lt;p&gt;When you get to the Debian Edu profile question, go to tty2
5379 (use Alt-Ctrl-F2), run&lt;/p&gt;
5380
5381 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5382 nano /usr/bin/edu-eatmydata-install
5383 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5384
5385 &lt;p&gt;and add &#39;exit 0&#39; as the second line, disabling the eatmydata
5386 optimization. Return to the installation, select the profile you want
5387 and continue. Without this change, exim4-config will fail to install
5388 due to a known bug in eatmydata.&lt;/p&gt;
5389
5390 &lt;p&gt;When you get the grub question at the end, answer /dev/sda (or if
5391 this do not work, figure out what your correct value would be. All my
5392 test machines need /dev/sda, so I have no advice if it do not fit
5393 your need.&lt;/p&gt;
5394
5395 &lt;p&gt;If you installed a profile including a graphical desktop, log in as
5396 root after the initial boot from hard drive, and install the
5397 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
5398 or mate. If you want several desktop options, install more than one
5399 metapackage. Once this is done, reboot and you should have a working
5400 graphical login screen. This workaround should no longer be needed
5401 once the education-tasks package version 1.801 enter testing in two
5402 days.&lt;/p&gt;
5403
5404 &lt;p&gt;I believe the ISO build will start working on two days when the new
5405 tasksel package enter testing and Steve McIntyre get a chance to
5406 update the debian-cd git repository. The eatmydata, grub and desktop
5407 issues are already fixed in unstable and testing, and should show up
5408 on the ISO as soon as the ISO build start working again. Well the
5409 eatmydata optimization is really just disabled. The proper fix
5410 require an upload by the eatmydata maintainer applying the patch
5411 provided in bug &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;#702711&lt;/a&gt;.
5412 The rest have proper fixes in unstable.&lt;/p&gt;
5413
5414 &lt;p&gt;I hope this get you going with the installation testing, as we are
5415 quickly running out of time trying to get our Jessie based
5416 installation ready before the distribution freeze in a month.&lt;/p&gt;
5417 </description>
5418 </item>
5419
5420 <item>
5421 <title>Suddenly I am the new upstream of the lsdvd command line tool</title>
5422 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</link>
5423 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html</guid>
5424 <pubDate>Thu, 25 Sep 2014 11:20:00 +0200</pubDate>
5425 <description>&lt;p&gt;I use the &lt;a href=&quot;https://sourceforge.net/p/lsdvd/&quot;&gt;lsdvd tool&lt;/a&gt;
5426 to handle my fairly large DVD collection. It is a nice command line
5427 tool to get details about a DVD, like title, tracks, track length,
5428 etc, in XML, Perl or human readable format. But lsdvd have not seen
5429 any new development since 2006 and had a few irritating bugs affecting
5430 its use with some DVDs. Upstream seemed to be dead, and in January I
5431 sent a small probe asking for a version control repository for the
5432 project, without any reply. But I use it regularly and would like to
5433 get &lt;a href=&quot;https://packages.qa.debian.org/lsdvd&quot;&gt;an updated version
5434 into Debian&lt;/a&gt;. So two weeks ago I tried harder to get in touch with
5435 the project admin, and after getting a reply from him explaining that
5436 he was no longer interested in the project, I asked if I could take
5437 over. And yesterday, I became project admin.&lt;/p&gt;
5438
5439 &lt;p&gt;I&#39;ve been in touch with a Gentoo developer and the Debian
5440 maintainer interested in joining forces to maintain the upstream
5441 project, and I hope we can get a new release out fairly quickly,
5442 collecting the patches spread around on the internet into on place.
5443 I&#39;ve added the relevant Debian patches to the freshly created git
5444 repository, and expect the Gentoo patches to make it too. If you got
5445 a DVD collection and care about command line tools, check out
5446 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/git/ci/master/tree/&quot;&gt;the git source&lt;/a&gt; and join
5447 &lt;a href=&quot;https://sourceforge.net/p/lsdvd/mailman/&quot;&gt;the project mailing
5448 list&lt;/a&gt;. :)&lt;/p&gt;
5449 </description>
5450 </item>
5451
5452 <item>
5453 <title>Speeding up the Debian installer using eatmydata and dpkg-divert</title>
5454 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</link>
5455 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html</guid>
5456 <pubDate>Tue, 16 Sep 2014 14:00:00 +0200</pubDate>
5457 <description>&lt;p&gt;The &lt;a href=&quot;https://www.debian.org/&quot;&gt;Debian&lt;/a&gt; installer could be
5458 a lot quicker. When we install more than 2000 packages in
5459 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux / Debian Edu&lt;/a&gt; using
5460 tasksel in the installer, unpacking the binary packages take forever.
5461 A part of the slow I/O issue was discussed in
5462 &lt;a href=&quot;https://bugs.debian.org/613428&quot;&gt;bug #613428&lt;/a&gt; about too
5463 much file system sync-ing done by dpkg, which is the package
5464 responsible for unpacking the binary packages. Other parts (like code
5465 executed by postinst scripts) might also sync to disk during
5466 installation. All this sync-ing to disk do not really make sense to
5467 me. If the machine crash half-way through, I start over, I do not try
5468 to salvage the half installed system. So the failure sync-ing is
5469 supposed to protect against, hardware or system crash, is not really
5470 relevant while the installer is running.&lt;/p&gt;
5471
5472 &lt;p&gt;A few days ago, I thought of a way to get rid of all the file
5473 system sync()-ing in a fairly non-intrusive way, without the need to
5474 change the code in several packages. The idea is not new, but I have
5475 not heard anyone propose the approach using dpkg-divert before. It
5476 depend on the small and clever package
5477 &lt;a href=&quot;https://packages.qa.debian.org/eatmydata&quot;&gt;eatmydata&lt;/a&gt;, which
5478 uses LD_PRELOAD to replace the system functions for syncing data to
5479 disk with functions doing nothing, thus allowing programs to live
5480 dangerous while speeding up disk I/O significantly. Instead of
5481 modifying the implementation of dpkg, apt and tasksel (which are the
5482 packages responsible for selecting, fetching and installing packages),
5483 it occurred to me that we could just divert the programs away, replace
5484 them with a simple shell wrapper calling
5485 &quot;eatmydata&amp;nbsp;$program&amp;nbsp;$@&quot;, to get the same effect.
5486 Two days ago I decided to test the idea, and wrapped up a simple
5487 implementation for the Debian Edu udeb.&lt;/p&gt;
5488
5489 &lt;p&gt;The effect was stunning. In my first test it reduced the running
5490 time of the pkgsel step (installing tasks) from 64 to less than 44
5491 minutes (20 minutes shaved off the installation) on an old Dell
5492 Latitude D505 machine. I am not quite sure what the optimised time
5493 would have been, as I messed up the testing a bit, causing the debconf
5494 priority to get low enough for two questions to pop up during
5495 installation. As soon as I saw the questions I moved the installation
5496 along, but do not know how long the question were holding up the
5497 installation. I did some more measurements using Debian Edu Jessie,
5498 and got these results. The time measured is the time stamp in
5499 /var/log/syslog between the &quot;pkgsel: starting tasksel&quot; and the
5500 &quot;pkgsel: finishing up&quot; lines, if you want to do the same measurement
5501 yourself. In Debian Edu, the tasksel dialog do not show up, and the
5502 timing thus do not depend on how quickly the user handle the tasksel
5503 dialog.&lt;/p&gt;
5504
5505 &lt;p&gt;&lt;table&gt;
5506
5507 &lt;tr&gt;
5508 &lt;th&gt;Machine/setup&lt;/th&gt;
5509 &lt;th&gt;Original tasksel&lt;/th&gt;
5510 &lt;th&gt;Optimised tasksel&lt;/th&gt;
5511 &lt;th&gt;Reduction&lt;/th&gt;
5512 &lt;/tr&gt;
5513
5514 &lt;tr&gt;
5515 &lt;td&gt;Latitude D505 Main+LTSP LXDE&lt;/td&gt;
5516 &lt;td&gt;64 min (07:46-08:50)&lt;/td&gt;
5517 &lt;td&gt;&lt;44 min (11:27-12:11)&lt;/td&gt;
5518 &lt;td&gt;&gt;20 min 18%&lt;/td&gt;
5519 &lt;/tr&gt;
5520
5521 &lt;tr&gt;
5522 &lt;td&gt;Latitude D505 Roaming LXDE&lt;/td&gt;
5523 &lt;td&gt;57 min (08:48-09:45)&lt;/td&gt;
5524 &lt;td&gt;34 min (07:43-08:17)&lt;/td&gt;
5525 &lt;td&gt;23 min 40%&lt;/td&gt;
5526 &lt;/tr&gt;
5527
5528 &lt;tr&gt;
5529 &lt;td&gt;Latitude D505 Minimal&lt;/td&gt;
5530 &lt;td&gt;22 min (10:37-10:59)&lt;/td&gt;
5531 &lt;td&gt;11 min (11:16-11:27)&lt;/td&gt;
5532 &lt;td&gt;11 min 50%&lt;/td&gt;
5533 &lt;/tr&gt;
5534
5535 &lt;tr&gt;
5536 &lt;td&gt;Thinkpad X200 Minimal&lt;/td&gt;
5537 &lt;td&gt;6 min (08:19-08:25)&lt;/td&gt;
5538 &lt;td&gt;4 min (08:04-08:08)&lt;/td&gt;
5539 &lt;td&gt;2 min 33%&lt;/td&gt;
5540 &lt;/tr&gt;
5541
5542 &lt;tr&gt;
5543 &lt;td&gt;Thinkpad X200 Roaming KDE&lt;/td&gt;
5544 &lt;td&gt;19 min (09:21-09:40)&lt;/td&gt;
5545 &lt;td&gt;15 min (10:25-10:40)&lt;/td&gt;
5546 &lt;td&gt;4 min 21%&lt;/td&gt;
5547 &lt;/tr&gt;
5548
5549 &lt;/table&gt;&lt;/p&gt;
5550
5551 &lt;p&gt;The test is done using a netinst ISO on a USB stick, so some of the
5552 time is spent downloading packages. The connection to the Internet
5553 was 100Mbit/s during testing, so downloading should not be a
5554 significant factor in the measurement. Download typically took a few
5555 seconds to a few minutes, depending on the amount of packages being
5556 installed.&lt;/p&gt;
5557
5558 &lt;p&gt;The speedup is implemented by using two hooks in
5559 &lt;a href=&quot;https://www.debian.org/devel/debian-installer/&quot;&gt;Debian
5560 Installer&lt;/a&gt;, the pre-pkgsel.d hook to set up the diverts, and the
5561 finish-install.d hook to remove the divert at the end of the
5562 installation. I picked the pre-pkgsel.d hook instead of the
5563 post-base-installer.d hook because I test using an ISO without the
5564 eatmydata package included, and the post-base-installer.d hook in
5565 Debian Edu can only operate on packages included in the ISO. The
5566 negative effect of this is that I am unable to activate this
5567 optimization for the kernel installation step in d-i. If the code is
5568 moved to the post-base-installer.d hook, the speedup would be larger
5569 for the entire installation.&lt;/p&gt;
5570
5571 &lt;p&gt;I&#39;ve implemented this in the
5572 &lt;a href=&quot;https://packages.qa.debian.org/debian-edu-install&quot;&gt;debian-edu-install&lt;/a&gt;
5573 git repository, and plan to provide the optimization as part of the
5574 Debian Edu installation. If you want to test this yourself, you can
5575 create two files in the installer (or in an udeb). One shell script
5576 need do go into /usr/lib/pre-pkgsel.d/, with content like this:&lt;/p&gt;
5577
5578 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5579 #!/bin/sh
5580 set -e
5581 . /usr/share/debconf/confmodule
5582 info() {
5583 logger -t my-pkgsel &quot;info: $*&quot;
5584 }
5585 error() {
5586 logger -t my-pkgsel &quot;error: $*&quot;
5587 }
5588 override_install() {
5589 apt-install eatmydata || true
5590 if [ -x /target/usr/bin/eatmydata ] ; then
5591 for bin in dpkg apt-get aptitude tasksel ; do
5592 file=/usr/bin/$bin
5593 # Test that the file exist and have not been diverted already.
5594 if [ -f /target$file ] ; then
5595 info &quot;diverting $file using eatmydata&quot;
5596 printf &quot;#!/bin/sh\neatmydata $bin.distrib \&quot;\$@\&quot;\n&quot; \
5597 &gt; /target$file.edu
5598 chmod 755 /target$file.edu
5599 in-target dpkg-divert --package debian-edu-config \
5600 --rename --quiet --add $file
5601 ln -sf ./$bin.edu /target$file
5602 else
5603 error &quot;unable to divert $file, as it is missing.&quot;
5604 fi
5605 done
5606 else
5607 error &quot;unable to find /usr/bin/eatmydata after installing the eatmydata pacage&quot;
5608 fi
5609 }
5610
5611 override_install
5612 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5613
5614 &lt;p&gt;To clean up, another shell script should go into
5615 /usr/lib/finish-install.d/ with code like this:
5616
5617 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5618 #! /bin/sh -e
5619 . /usr/share/debconf/confmodule
5620 error() {
5621 logger -t my-finish-install &quot;error: $@&quot;
5622 }
5623 remove_install_override() {
5624 for bin in dpkg apt-get aptitude tasksel ; do
5625 file=/usr/bin/$bin
5626 if [ -x /target$file.edu ] ; then
5627 rm /target$file
5628 in-target dpkg-divert --package debian-edu-config \
5629 --rename --quiet --remove $file
5630 rm /target$file.edu
5631 else
5632 error &quot;Missing divert for $file.&quot;
5633 fi
5634 done
5635 sync # Flush file buffers before continuing
5636 }
5637
5638 remove_install_override
5639 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5640
5641 &lt;p&gt;In Debian Edu, I placed both code fragments in a separate script
5642 edu-eatmydata-install and call it from the pre-pkgsel.d and
5643 finish-install.d scripts.&lt;/p&gt;
5644
5645 &lt;p&gt;By now you might ask if this change should get into the normal
5646 Debian installer too? I suspect it should, but am not sure the
5647 current debian-installer coordinators find it useful enough. It also
5648 depend on the side effects of the change. I&#39;m not aware of any, but I
5649 guess we will see if the change is safe after some more testing.
5650 Perhaps there is some package in Debian depending on sync() and
5651 fsync() having effect? Perhaps it should go into its own udeb, to
5652 allow those of us wanting to enable it to do so without affecting
5653 everyone.&lt;/p&gt;
5654
5655 &lt;p&gt;Update 2014-09-24: Since a few days ago, enabling this optimization
5656 will break installation of all programs using gnutls because of
5657 &lt;a href=&quot;https://bugs.debian.org/702711&quot;&gt;bug #702711&lt;/a&gt;. An updated
5658 eatmydata package in Debian will solve it.&lt;/p&gt;
5659
5660 &lt;p&gt;Update 2014-10-17: The bug mentioned above is fixed in testing and
5661 the optimization work again. And I have discovered that the
5662 dpkg-divert trick is not really needed and implemented a slightly
5663 simpler approach as part of the debian-edu-install package. See
5664 tools/edu-eatmydata-install in the source package.&lt;/p&gt;
5665
5666 &lt;p&gt;Update 2014-11-11: Unfortunately, a new
5667 &lt;a href=&quot;http://bugs.debian.org/765738&quot;&gt;bug #765738&lt;/a&gt; in eatmydata only
5668 triggering on i386 made it into testing, and broke this installation
5669 optimization again. If &lt;a href=&quot;http://bugs.debian.org/768893&quot;&gt;unblock
5670 request 768893&lt;/a&gt; is accepted, it should be working again.&lt;/p&gt;
5671 </description>
5672 </item>
5673
5674 <item>
5675 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net</title>
5676 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</link>
5677 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html</guid>
5678 <pubDate>Wed, 10 Sep 2014 13:10:00 +0200</pubDate>
5679 <description>&lt;p&gt;Yesterday, I had the pleasure of attending a talk with the
5680 &lt;a href=&quot;http://www.nuug.no/&quot;&gt;Norwegian Unix User Group&lt;/a&gt; about
5681 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20140909-sks-keyservers/&quot;&gt;the
5682 OpenPGP keyserver pool sks-keyservers.net&lt;/a&gt;, and was very happy to
5683 learn that there is a large set of publicly available key servers to
5684 use when looking for peoples public key. So far I have used
5685 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
5686 were misbehaving, but those days are ended. The servers I have used
5687 up until yesterday have been slow and some times unavailable. I hope
5688 those problems are gone now.&lt;/p&gt;
5689
5690 &lt;p&gt;Behind the round robin DNS entry of the
5691 &lt;a href=&quot;https://sks-keyservers.net/&quot;&gt;sks-keyservers.net&lt;/a&gt; service
5692 there is a pool of more than 100 keyservers which are checked every
5693 day to ensure they are well connected and up to date. It must be
5694 better than what I have used so far. :)&lt;/p&gt;
5695
5696 &lt;p&gt;Yesterdays speaker told me that the service is the default
5697 keyserver provided by the default configuration in GnuPG, but this do
5698 not seem to be used in Debian. Perhaps it should?&lt;/p&gt;
5699
5700 &lt;p&gt;Anyway, I&#39;ve updated my ~/.gnupg/options file to now include this
5701 line:&lt;/p&gt;
5702
5703 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5704 keyserver pool.sks-keyservers.net
5705 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5706
5707 &lt;p&gt;With GnuPG version 2 one can also locate the keyserver using SRV
5708 entries in DNS. Just for fun, I did just that at work, so now every
5709 user of GnuPG at the University of Oslo should find a OpenGPG
5710 keyserver automatically should their need it:&lt;/p&gt;
5711
5712 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5713 % host -t srv _pgpkey-http._tcp.uio.no
5714 _pgpkey-http._tcp.uio.no has SRV record 0 100 11371 pool.sks-keyservers.net.
5715 %
5716 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5717
5718 &lt;p&gt;Now if only
5719 &lt;a href=&quot;http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/&quot;&gt;the
5720 HKP lookup protocol&lt;/a&gt; supported finding signature paths, I would be
5721 very happy. It can look up a given key or search for a user ID, but I
5722 normally do not want that, but to find a trust path from my key to
5723 another key. Given a user ID or key ID, I would like to find (and
5724 download) the keys representing a signature path from my key to the
5725 key in question, to be able to get a trust path between the two keys.
5726 This is as far as I can tell not possible today. Perhaps something
5727 for a future version of the protocol?&lt;/p&gt;
5728 </description>
5729 </item>
5730
5731 <item>
5732 <title>From English wiki to translated PDF and epub via Docbook</title>
5733 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</link>
5734 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html</guid>
5735 <pubDate>Tue, 17 Jun 2014 11:30:00 +0200</pubDate>
5736 <description>&lt;p&gt;The &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux
5737 project&lt;/a&gt; provide an instruction manual for teachers, system
5738 administrators and other users that contain useful tips for setting up
5739 and maintaining a Debian Edu installation. This text is about how the
5740 text processing of this manual is handled in the project.&lt;/p&gt;
5741
5742 &lt;p&gt;One goal of the project is to provide information in the native
5743 language of its users, and for this we need to handle translations.
5744 But we also want to make sure each language contain the same
5745 information, so for this we need a good way to keep the translations
5746 in sync. And we want it to be easy for our users to improve the
5747 documentation, avoiding the need to learn special formats or tools to
5748 contribute, and the obvious way to do this is to make it possible to
5749 edit the documentation using a web browser. We also want it to be
5750 easy for translators to keep the translation up to date, and give them
5751 help in figuring out what need to be translated. Here is the list of
5752 tools and the process we have found trying to reach all these
5753 goals.&lt;/p&gt;
5754
5755 &lt;p&gt;We maintain the authoritative source of our manual in the
5756 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;Debian
5757 wiki&lt;/a&gt;, as several wiki pages written in English. It consist of one
5758 front page with references to the different chapters, several pages
5759 for each chapter, and finally one &quot;collection page&quot; gluing all the
5760 chapters together into one large web page (aka
5761 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne&quot;&gt;the
5762 AllInOne page&lt;/a&gt;). The AllInOne page is the one used for further
5763 processing and translations. Thanks to the fact that the
5764 &lt;a href=&quot;http://moinmo.in/&quot;&gt;MoinMoin&lt;/a&gt; installation on
5765 wiki.debian.org support exporting pages in
5766 &lt;a href=&quot;http://www.docbook.org/&quot;&gt;the Docbook format&lt;/a&gt;, we can fetch
5767 the list of pages to export using the raw version of the AllInOne
5768 page, loop over each of them to generate a Docbook XML version of the
5769 manual. This process also download images and transform image
5770 references to use the locally downloaded images. The generated
5771 Docbook XML files are slightly broken, so some post-processing is done
5772 using the &lt;tt&gt;documentation/scripts/get_manual&lt;/tt&gt; program, and the
5773 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
5774 a handfull of images. The XML file can now be used to generate PDF, HTML
5775 and epub versions of the English manual. This is the basic step of
5776 our process, making PDF (using dblatex), HTML (using xsltproc) and
5777 epub (using dbtoepub) version from Docbook XML, and the resulting files
5778 are placed in the debian-edu-doc-en binary package.&lt;/p&gt;
5779
5780 &lt;p&gt;But English documentation is not enough for us. We want translated
5781 documentation too, and we want to make it easy for translators to
5782 track the English original. For this we use the
5783 &lt;a href=&quot;http://packages.qa.debian.org/p/poxml.html&quot;&gt;poxml&lt;/a&gt; package,
5784 which allow us to transform the English Docbook XML file into a
5785 translation file (a .pot file), usable with the normal gettext based
5786 translation tools used by those translating free software. The pot
5787 file is used to create and maintain translation files (several .po
5788 files), which the translations update with the native language
5789 translations of all titles, paragraphs and blocks of text in the
5790 original. The next step is combining the original English Docbook XML
5791 and the translation file (say debian-edu-wheezy-manual.nb.po), to
5792 create a translated Docbook XML file (in this case
5793 debian-edu-wheezy-manual.nb.xml). This translated (or partly
5794 translated, if the translation is not complete) Docbook XML file can
5795 then be used like the original to create a PDF, HTML and epub version
5796 of the documentation.&lt;/p&gt;
5797
5798 &lt;p&gt;The translators use different tools to edit the .po files. We
5799 recommend using
5800 &lt;a href=&quot;http://www.kde.org/applications/development/lokalize/&quot;&gt;lokalize&lt;/a&gt;,
5801 while some use emacs and vi, others can use web based editors like
5802 &lt;a href=&quot;http://pootle.translatehouse.org/&quot;&gt;Poodle&lt;/a&gt; or
5803 &lt;a href=&quot;https://www.transifex.com/&quot;&gt;Transifex&lt;/a&gt;. All we care about
5804 is where the .po file end up, in our git repository. Updated
5805 translations can either be committed directly to git, or submitted as
5806 &lt;a href=&quot;https://bugs.debian.org/src:debian-edu-doc&quot;&gt;bug reports
5807 against the debian-edu-doc package&lt;/a&gt;.&lt;/p&gt;
5808
5809 &lt;p&gt;One challenge is images, which both might need to be translated (if
5810 they show translated user applications), and are needed in different
5811 formats when creating PDF and HTML versions (epub is a HTML version in
5812 this regard). For this we transform the original PNG images to the
5813 needed density and format during build, and have a way to provide
5814 translated images by storing translated versions in
5815 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
5816 package maintainers know more.&lt;/p&gt;
5817
5818 &lt;p&gt;If you wonder what the result look like, we provide
5819 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/&quot;&gt;the content
5820 of the documentation packages on the web&lt;/a&gt;. See for example the
5821 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf&quot;&gt;Italian
5822 PDF version&lt;/a&gt; or the
5823 &lt;a href=&quot;http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html&quot;&gt;German
5824 HTML version&lt;/a&gt;. We do not yet build the epub version by default,
5825 but perhaps it will be done in the future.&lt;/p&gt;
5826
5827 &lt;p&gt;To learn more, check out
5828 &lt;a href=&quot;http://packages.qa.debian.org/d/debian-edu-doc.html&quot;&gt;the
5829 debian-edu-doc package&lt;/a&gt;,
5830 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/&quot;&gt;the
5831 manual on the wiki&lt;/a&gt; and
5832 &lt;a href=&quot;https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations&quot;&gt;the
5833 translation instructions&lt;/a&gt; in the manual.&lt;/p&gt;
5834 </description>
5835 </item>
5836
5837 <item>
5838 <title>Install hardware dependent packages using tasksel (Isenkram 0.7)</title>
5839 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</link>
5840 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html</guid>
5841 <pubDate>Wed, 23 Apr 2014 14:50:00 +0200</pubDate>
5842 <description>&lt;p&gt;It would be nice if it was easier in Debian to get all the hardware
5843 related packages relevant for the computer installed automatically.
5844 So I implemented one, using
5845 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;my Isenkram
5846 package&lt;/a&gt;. To use it, install the tasksel and isenkram packages and
5847 run tasksel as user root. You should be presented with a new option,
5848 &quot;Hardware specific packages (autodetected by isenkram)&quot;. When you
5849 select it, tasksel will install the packages isenkram claim is fit for
5850 the current hardware, hot pluggable or not.&lt;p&gt;
5851
5852 &lt;p&gt;The implementation is in two files, one is the tasksel menu entry
5853 description, and the other is the script used to extract the list of
5854 packages to install. The first part is in
5855 &lt;tt&gt;/usr/share/tasksel/descs/isenkram.desc&lt;/tt&gt; and look like
5856 this:&lt;/p&gt;
5857
5858 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5859 Task: isenkram
5860 Section: hardware
5861 Description: Hardware specific packages (autodetected by isenkram)
5862 Based on the detected hardware various hardware specific packages are
5863 proposed.
5864 Test-new-install: mark show
5865 Relevance: 8
5866 Packages: for-current-hardware
5867 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5868
5869 &lt;p&gt;The second part is in
5870 &lt;tt&gt;/usr/lib/tasksel/packages/for-current-hardware&lt;/tt&gt; and look like
5871 this:&lt;/p&gt;
5872
5873 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
5874 #!/bin/sh
5875 #
5876 (
5877 isenkram-lookup
5878 isenkram-autoinstall-firmware -l
5879 ) | sort -u
5880 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
5881
5882 &lt;p&gt;All in all, a very short and simple implementation making it
5883 trivial to install the hardware dependent package we all may want to
5884 have installed on our machines. I&#39;ve not been able to find a way to
5885 get tasksel to tell you exactly which packages it plan to install
5886 before doing the installation. So if you are curious or careful,
5887 check the output from the isenkram-* command line tools first.&lt;/p&gt;
5888
5889 &lt;p&gt;The information about which packages are handling which hardware is
5890 fetched either from the isenkram package itself in
5891 /usr/share/isenkram/, from git.debian.org or from the APT package
5892 database (using the Modaliases header). The APT package database
5893 parsing have caused a nasty resource leak in the isenkram daemon (bugs
5894 &lt;a href=&quot;http://bugs.debian.org/719837&quot;&gt;#719837&lt;/a&gt; and
5895 &lt;a href=&quot;http://bugs.debian.org/730704&quot;&gt;#730704&lt;/a&gt;). The cause is in
5896 the python-apt code (bug
5897 &lt;a href=&quot;http://bugs.debian.org/745487&quot;&gt;#745487&lt;/a&gt;), but using a
5898 workaround I was able to get rid of the file descriptor leak and
5899 reduce the memory leak from ~30 MiB per hardware detection down to
5900 around 2 MiB per hardware detection. It should make the desktop
5901 daemon a lot more useful. The fix is in version 0.7 uploaded to
5902 unstable today.&lt;/p&gt;
5903
5904 &lt;p&gt;I believe the current way of mapping hardware to packages in
5905 Isenkram is is a good draft, but in the future I expect isenkram to
5906 use the AppStream data source for this. A proposal for getting proper
5907 AppStream support into Debian is floating around as
5908 &lt;a href=&quot;https://wiki.debian.org/DEP-11&quot;&gt;DEP-11&lt;/a&gt;, and
5909 &lt;a href=&quot;https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects.2FAppStreamDEP11Implementation.AppStream.2FDEP-11_for_the_Debian_Archive&quot;&gt;GSoC
5910 project&lt;/a&gt; will take place this summer to improve the situation. I
5911 look forward to seeing the result, and welcome patches for isenkram to
5912 start using the information when it is ready.&lt;/p&gt;
5913
5914 &lt;p&gt;If you want your package to map to some specific hardware, either
5915 add a &quot;Xb-Modaliases&quot; header to your control file like I did in
5916 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;the pymissile
5917 package&lt;/a&gt; or submit a bug report with the details to the isenkram
5918 package. See also
5919 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/tags/isenkram/&quot;&gt;all my
5920 blog posts tagged isenkram&lt;/a&gt; for details on the notation. I expect
5921 the information will be migrated to AppStream eventually, but for the
5922 moment I got no better place to store it.&lt;/p&gt;
5923 </description>
5924 </item>
5925
5926 <item>
5927 <title>FreedomBox milestone - all packages now in Debian Sid</title>
5928 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</link>
5929 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html</guid>
5930 <pubDate>Tue, 15 Apr 2014 22:10:00 +0200</pubDate>
5931 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
5932 project&lt;/a&gt; is working on providing the software and hardware to make
5933 it easy for non-technical people to host their data and communication
5934 at home, and being able to communicate with their friends and family
5935 encrypted and away from prying eyes. It is still going strong, and
5936 today a major mile stone was reached.&lt;/p&gt;
5937
5938 &lt;p&gt;Today, the last of the packages currently used by the project to
5939 created the system images were accepted into Debian Unstable. It was
5940 the freedombox-setup package, which is used to configure the images
5941 during build and on the first boot. Now all one need to get going is
5942 the build code from the freedom-maker git repository and packages from
5943 Debian. And once the freedombox-setup package enter testing, we can
5944 build everything directly from Debian. :)&lt;/p&gt;
5945
5946 &lt;p&gt;Some key packages used by Freedombox are
5947 &lt;a href=&quot;http://packages.qa.debian.org/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;,
5948 &lt;a href=&quot;http://packages.qa.debian.org/plinth&quot;&gt;plinth&lt;/a&gt;,
5949 &lt;a href=&quot;http://packages.qa.debian.org/pagekite&quot;&gt;pagekite&lt;/a&gt;,
5950 &lt;a href=&quot;http://packages.qa.debian.org/tor&quot;&gt;tor&lt;/a&gt;,
5951 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;,
5952 &lt;a href=&quot;http://packages.qa.debian.org/owncloud&quot;&gt;owncloud&lt;/a&gt; and
5953 &lt;a href=&quot;http://packages.qa.debian.org/dnsmasq&quot;&gt;dnsmasq&lt;/a&gt;. There
5954 are plans to integrate more packages into the setup. User
5955 documentation is maintained on the Debian wiki. Please
5956 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/Manual/Jessie&quot;&gt;check out
5957 the manual&lt;/a&gt; and help us improve it.&lt;/p&gt;
5958
5959 &lt;p&gt;To test for yourself and create boot images with the FreedomBox
5960 setup, run this on a Debian machine using a user with sudo rights to
5961 become root:&lt;/p&gt;
5962
5963 &lt;p&gt;&lt;pre&gt;
5964 sudo apt-get install git vmdebootstrap mercurial python-docutils \
5965 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
5966 u-boot-tools
5967 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
5968 freedom-maker
5969 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
5970 &lt;/pre&gt;&lt;/p&gt;
5971
5972 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
5973 devices. See the README in the freedom-maker git repo for more
5974 details on the build. If you do not want all three images, trim the
5975 make line. Note that the virtualbox-image target is not really
5976 virtualbox specific. It create a x86 image usable in kvm, qemu,
5977 vmware and any other x86 virtual machine environment. You might need
5978 the version of vmdebootstrap in Jessie to get the build working, as it
5979 include fixes for a race condition with kpartx.&lt;/p&gt;
5980
5981 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
5982 method, boot a Debian Wheezy ISO and use this boot argument to load
5983 the preseed values:&lt;/p&gt;
5984
5985 &lt;p&gt;&lt;pre&gt;
5986 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;
5987 &lt;/pre&gt;&lt;/p&gt;
5988
5989 &lt;p&gt;I have not tested it myself the last few weeks, so I do not know if
5990 it still work.&lt;/p&gt;
5991
5992 &lt;p&gt;If you wonder how to help, one task you could look at is using
5993 systemd as the boot system. It will become the default for Linux in
5994 Jessie, so we need to make sure it is usable on the Freedombox. I did
5995 a simple test a few weeks ago, and noticed dnsmasq failed to start
5996 during boot when using systemd. I suspect there are other problems
5997 too. :) To detect problems, there is a test suite included, which can
5998 be run from the plinth web interface.&lt;/p&gt;
5999
6000 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6001 us get the new release published. :) Please join us on
6002 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6003 irc.debian.org)&lt;/a&gt; and
6004 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6005 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6006 </description>
6007 </item>
6008
6009 <item>
6010 <title>S3QL, a locally mounted cloud file system - nice free software</title>
6011 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</link>
6012 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html</guid>
6013 <pubDate>Wed, 9 Apr 2014 11:30:00 +0200</pubDate>
6014 <description>&lt;p&gt;For a while now, I have been looking for a sensible offsite backup
6015 solution for use at home. My requirements are simple, it must be
6016 cheap and locally encrypted (in other words, I keep the encryption
6017 keys, the storage provider do not have access to my private files).
6018 One idea me and my friends had many years ago, before the cloud
6019 storage providers showed up, was to use Google mail as storage,
6020 writing a Linux block device storing blocks as emails in the mail
6021 service provided by Google, and thus get heaps of free space. On top
6022 of this one can add encryption, RAID and volume management to have
6023 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6024 I never found time to implement such system. But the last few weeks I
6025 have looked at a system called
6026 &lt;a href=&quot;https://bitbucket.org/nikratio/s3ql/&quot;&gt;S3QL&lt;/a&gt;, a locally
6027 mounted network backed file system with the features I need.&lt;/p&gt;
6028
6029 &lt;p&gt;S3QL is a fuse file system with a local cache and cloud storage,
6030 handling several different storage providers, any with Amazon S3,
6031 Google Drive or OpenStack API. There are heaps of such storage
6032 providers. S3QL can also use a local directory as storage, which
6033 combined with sshfs allow for file storage on any ssh server. S3QL
6034 include support for encryption, compression, de-duplication, snapshots
6035 and immutable file systems, allowing me to mount the remote storage as
6036 a local mount point, look at and use the files as if they were local,
6037 while the content is stored in the cloud as well. This allow me to
6038 have a backup that should survive fire. The file system can not be
6039 shared between several machines at the same time, as only one can
6040 mount it at the time, but any machine with the encryption key and
6041 access to the storage service can mount it if it is unmounted.&lt;/p&gt;
6042
6043 &lt;p&gt;It is simple to use. I&#39;m using it on Debian Wheezy, where the
6044 package is included already. So to get started, run &lt;tt&gt;apt-get
6045 install s3ql&lt;/tt&gt;. Next, pick a storage provider. I ended up picking
6046 Greenqloud, after reading their nice recipe on
6047 &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
6048 to use S3QL with their Amazon S3 service&lt;/a&gt;, because I trust the laws
6049 in Iceland more than those in USA when it come to keeping my personal
6050 data safe and private, and thus would rather spend money on a company
6051 in Iceland. Another nice recipe is available from the article
6052 &lt;a href=&quot;http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage&quot;&gt;S3QL
6053 Filesystem for HPC Storage&lt;/a&gt; by Jeff Layton in the HPC section of
6054 Admin magazine. When the provider is picked, figure out how to get
6055 the API key needed to connect to the storage API. With Greencloud,
6056 the key did not show up until I had added payment details to my
6057 account.&lt;/p&gt;
6058
6059 &lt;p&gt;Armed with the API access details, it is time to create the file
6060 system. First, create a new bucket in the cloud. This bucket is the
6061 file system storage area. I picked a bucket name reflecting the
6062 machine that was going to store data there, but any name will do.
6063 I&#39;ll refer to it as &lt;tt&gt;bucket-name&lt;/tt&gt; below. In addition, one need
6064 the API login and password, and a locally created password. Store it
6065 all in ~root/.s3ql/authinfo2 like this:
6066
6067 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6068 [s3c]
6069 storage-url: s3c://s.greenqloud.com:443/bucket-name
6070 backend-login: API-login
6071 backend-password: API-password
6072 fs-passphrase: local-password
6073 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6074
6075 &lt;p&gt;I create my local passphrase using &lt;tt&gt;pwget 50&lt;/tt&gt; or similar,
6076 but any sensible way to create a fairly random password should do it.
6077 Armed with these details, it is now time to run mkfs, entering the API
6078 details and password to create it:&lt;/p&gt;
6079
6080 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6081 # mkdir -m 700 /var/lib/s3ql-cache
6082 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6083 --ssl s3c://s.greenqloud.com:443/bucket-name
6084 Enter backend login:
6085 Enter backend password:
6086 Before using S3QL, make sure to read the user&#39;s guide, especially
6087 the &#39;Important Rules to Avoid Loosing Data&#39; section.
6088 Enter encryption password:
6089 Confirm encryption password:
6090 Generating random encryption key...
6091 Creating metadata tables...
6092 Dumping metadata...
6093 ..objects..
6094 ..blocks..
6095 ..inodes..
6096 ..inode_blocks..
6097 ..symlink_targets..
6098 ..names..
6099 ..contents..
6100 ..ext_attributes..
6101 Compressing and uploading metadata...
6102 Wrote 0.00 MB of compressed metadata.
6103 # &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6104
6105 &lt;p&gt;The next step is mounting the file system to make the storage available.
6106
6107 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6108 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6109 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6110 Using 4 upload threads.
6111 Downloading and decompressing metadata...
6112 Reading metadata...
6113 ..objects..
6114 ..blocks..
6115 ..inodes..
6116 ..inode_blocks..
6117 ..symlink_targets..
6118 ..names..
6119 ..contents..
6120 ..ext_attributes..
6121 Mounting filesystem...
6122 # df -h /s3ql
6123 Filesystem Size Used Avail Use% Mounted on
6124 s3c://s.greenqloud.com:443/bucket-name 1.0T 0 1.0T 0% /s3ql
6125 #
6126 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6127
6128 &lt;p&gt;The file system is now ready for use. I use rsync to store my
6129 backups in it, and as the metadata used by rsync is downloaded at
6130 mount time, no network traffic (and storage cost) is triggered by
6131 running rsync. To unmount, one should not use the normal umount
6132 command, as this will not flush the cache to the cloud storage, but
6133 instead running the umount.s3ql command like this:
6134
6135 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6136 # umount.s3ql /s3ql
6137 #
6138 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6139
6140 &lt;p&gt;There is a fsck command available to check the file system and
6141 correct any problems detected. This can be used if the local server
6142 crashes while the file system is mounted, to reset the &quot;already
6143 mounted&quot; flag. This is what it look like when processing a working
6144 file system:&lt;/p&gt;
6145
6146 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6147 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:443/bucket-name
6148 Using cached metadata.
6149 File system seems clean, checking anyway.
6150 Checking DB integrity...
6151 Creating temporary extra indices...
6152 Checking lost+found...
6153 Checking cached objects...
6154 Checking names (refcounts)...
6155 Checking contents (names)...
6156 Checking contents (inodes)...
6157 Checking contents (parent inodes)...
6158 Checking objects (reference counts)...
6159 Checking objects (backend)...
6160 ..processed 5000 objects so far..
6161 ..processed 10000 objects so far..
6162 ..processed 15000 objects so far..
6163 Checking objects (sizes)...
6164 Checking blocks (referenced objects)...
6165 Checking blocks (refcounts)...
6166 Checking inode-block mapping (blocks)...
6167 Checking inode-block mapping (inodes)...
6168 Checking inodes (refcounts)...
6169 Checking inodes (sizes)...
6170 Checking extended attributes (names)...
6171 Checking extended attributes (inodes)...
6172 Checking symlinks (inodes)...
6173 Checking directory reachability...
6174 Checking unix conventions...
6175 Checking referential integrity...
6176 Dropping temporary indices...
6177 Backing up old metadata...
6178 Dumping metadata...
6179 ..objects..
6180 ..blocks..
6181 ..inodes..
6182 ..inode_blocks..
6183 ..symlink_targets..
6184 ..names..
6185 ..contents..
6186 ..ext_attributes..
6187 Compressing and uploading metadata...
6188 Wrote 0.89 MB of compressed metadata.
6189 #
6190 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6191
6192 &lt;p&gt;Thanks to the cache, working on files that fit in the cache is very
6193 quick, about the same speed as local file access. Uploading large
6194 amount of data is to me limited by the bandwidth out of and into my
6195 house. Uploading 685 MiB with a 100 MiB cache gave me 305 kiB/s,
6196 which is very close to my upload speed, and downloading the same
6197 Debian installation ISO gave me 610 kiB/s, close to my download speed.
6198 Both were measured using &lt;tt&gt;dd&lt;/tt&gt;. So for me, the bottleneck is my
6199 network, not the file system code. I do not know what a good cache
6200 size would be, but suspect that the cache should e larger than your
6201 working set.&lt;/p&gt;
6202
6203 &lt;p&gt;I mentioned that only one machine can mount the file system at the
6204 time. If another machine try, it is told that the file system is
6205 busy:&lt;/p&gt;
6206
6207 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6208 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6209 --ssl --allow-root s3c://s.greenqloud.com:443/bucket-name /s3ql
6210 Using 8 upload threads.
6211 Backend reports that fs is still mounted elsewhere, aborting.
6212 #
6213 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6214
6215 &lt;p&gt;The file content is uploaded when the cache is full, while the
6216 metadata is uploaded once every 24 hour by default. To ensure the
6217 file system content is flushed to the cloud, one can either umount the
6218 file system, or ask S3QL to flush the cache and metadata using
6219 s3qlctrl:
6220
6221 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6222 # s3qlctrl upload-meta /s3ql
6223 # s3qlctrl flushcache /s3ql
6224 #
6225 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6226
6227 &lt;p&gt;If you are curious about how much space your data uses in the
6228 cloud, and how much compression and deduplication cut down on the
6229 storage usage, you can use s3qlstat on the mounted file system to get
6230 a report:&lt;/p&gt;
6231
6232 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6233 # s3qlstat /s3ql
6234 Directory entries: 9141
6235 Inodes: 9143
6236 Data blocks: 8851
6237 Total data size: 22049.38 MB
6238 After de-duplication: 21955.46 MB (99.57% of total)
6239 After compression: 21877.28 MB (99.22% of total, 99.64% of de-duplicated)
6240 Database size: 2.39 MB (uncompressed)
6241 (some values do not take into account not-yet-uploaded dirty blocks in cache)
6242 #
6243 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6244
6245 &lt;p&gt;I mentioned earlier that there are several possible suppliers of
6246 storage. I did not try to locate them all, but am aware of at least
6247 &lt;a href=&quot;https://www.greenqloud.com/&quot;&gt;Greenqloud&lt;/a&gt;,
6248 &lt;a href=&quot;http://drive.google.com/&quot;&gt;Google Drive&lt;/a&gt;,
6249 &lt;a href=&quot;http://aws.amazon.com/s3/&quot;&gt;Amazon S3 web serivces&lt;/a&gt;,
6250 &lt;a href=&quot;http://www.rackspace.com/&quot;&gt;Rackspace&lt;/a&gt; and
6251 &lt;a href=&quot;http://crowncloud.net/&quot;&gt;Crowncloud&lt;/A&gt;. The latter even
6252 accept payment in Bitcoin. Pick one that suit your need. Some of
6253 them provide several GiB of free storage, but the prize models are
6254 quite different and you will have to figure out what suits you
6255 best.&lt;/p&gt;
6256
6257 &lt;p&gt;While researching this blog post, I had a look at research papers
6258 and posters discussing the S3QL file system. There are several, which
6259 told me that the file system is getting a critical check by the
6260 science community and increased my confidence in using it. One nice
6261 poster is titled
6262 &quot;&lt;a href=&quot;http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf&quot;&gt;An
6263 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
6264 Store and Transformative Parallel I/O Approach&lt;/a&gt;&quot; by Hsing-Bung
6265 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
6266 and Pamela Smith. Please have a look.&lt;/p&gt;
6267
6268 &lt;p&gt;Given my problems with different file systems earlier, I decided to
6269 check out the mounted S3QL file system to see if it would be usable as
6270 a home directory (in other word, that it provided POSIX semantics when
6271 it come to locking and umask handling etc). Running
6272 &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
6273 test code to check file system semantics&lt;/a&gt;, I was happy to discover that
6274 no error was found. So the file system can be used for home
6275 directories, if one chooses to do so.&lt;/p&gt;
6276
6277 &lt;p&gt;If you do not want a locally file system, and want something that
6278 work without the Linux fuse file system, I would like to mention the
6279 &lt;a href=&quot;http://www.tarsnap.com/&quot;&gt;Tarsnap service&lt;/a&gt;, which also
6280 provide locally encrypted backup using a command line client. It have
6281 a nicer access control system, where one can split out read and write
6282 access, allowing some systems to write to the backup and others to
6283 only read from it.&lt;/p&gt;
6284
6285 &lt;p&gt;As usual, if you use Bitcoin and want to show your support of my
6286 activities, please send Bitcoin donations to my address
6287 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
6288 </description>
6289 </item>
6290
6291 <item>
6292 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine</title>
6293 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</link>
6294 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html</guid>
6295 <pubDate>Fri, 14 Mar 2014 11:00:00 +0100</pubDate>
6296 <description>&lt;p&gt;The &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;Freedombox
6297 project&lt;/a&gt; is working on providing the software and hardware for
6298 making it easy for non-technical people to host their data and
6299 communication at home, and being able to communicate with their
6300 friends and family encrypted and away from prying eyes. It has been
6301 going on for a while, and is slowly progressing towards a new test
6302 release (0.2).&lt;/p&gt;
6303
6304 &lt;p&gt;And what day could be better than the Pi day to announce that the
6305 new version will provide &quot;hard drive&quot; / SD card / USB stick images for
6306 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
6307 system), and can also be installed using a Debian installer preseed
6308 file. The Debian based Freedombox is now based on Debian Jessie,
6309 where most of the needed packages used are already present. Only one,
6310 the freedombox-setup package, is missing. To try to build your own
6311 boot image to test the current status, fetch the freedom-maker scripts
6312 and build using
6313 &lt;a href=&quot;http://packages.qa.debian.org/vmdebootstrap&quot;&gt;vmdebootstrap&lt;/a&gt;
6314 with a user with sudo access to become root:
6315
6316 &lt;pre&gt;
6317 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6318 freedom-maker
6319 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6320 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6321 u-boot-tools
6322 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6323 &lt;/pre&gt;
6324
6325 &lt;p&gt;Root access is needed to run debootstrap and mount loopback
6326 devices. See the README for more details on the build. If you do not
6327 want all three images, trim the make line. But note that thanks to &lt;a
6328 href=&quot;https://bugs.debian.org/741407&quot;&gt;a race condition in
6329 vmdebootstrap&lt;/a&gt;, the build might fail without the patch to the
6330 kpartx call.&lt;/p&gt;
6331
6332 &lt;p&gt;If you instead want to install using a Debian CD and the preseed
6333 method, boot a Debian Wheezy ISO and use this boot argument to load
6334 the preseed values:&lt;/p&gt;
6335
6336 &lt;pre&gt;
6337 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;
6338 &lt;/pre&gt;
6339
6340 &lt;p&gt;But note that due to &lt;a href=&quot;https://bugs.debian.org/740673&quot;&gt;a
6341 recently introduced bug in apt in Jessie&lt;/a&gt;, the installer will
6342 currently hang while setting up APT sources. Killing the
6343 &#39;&lt;tt&gt;apt-cdrom ident&lt;/tt&gt;&#39; process when it hang a few times during the
6344 installation will get the installation going. This affect all
6345 installations in Jessie, and I expect it will be fixed soon.&lt;/p&gt;
6346
6347 &lt;p&gt;Give it a go and let us know how it goes on the mailing list, and help
6348 us get the new release published. :) Please join us on
6349 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC (#freedombox on
6350 irc.debian.org)&lt;/a&gt; and
6351 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
6352 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
6353 </description>
6354 </item>
6355
6356 <item>
6357 <title>New home and release 1.0 for netgroup and innetgr (aka ng-utils)</title>
6358 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</link>
6359 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html</guid>
6360 <pubDate>Sat, 22 Feb 2014 21:45:00 +0100</pubDate>
6361 <description>&lt;p&gt;Many years ago, I wrote a GPL licensed version of the netgroup and
6362 innetgr tools, because I needed them in
6363 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;. I called the project
6364 ng-utils, and it has served me well. I placed the project under the
6365 &lt;a href=&quot;http://www.hungry.com/&quot;&gt;Hungry Programmer&lt;/a&gt; umbrella, and it was maintained in our CVS
6366 repository. But many years ago, the CVS repository was dropped (lost,
6367 not migrated to new hardware, not sure), and the project have lacked a
6368 proper home since then.&lt;/p&gt;
6369
6370 &lt;p&gt;Last summer, I had a look at the package and made a new release
6371 fixing a irritating crash bug, but was unable to store the changes in
6372 a proper source control system. I applied for a project on
6373 &lt;a href=&quot;https://alioth.debian.org/&quot;&gt;Alioth&lt;/a&gt;, but did not have time
6374 to follow up on it. Until today. :)&lt;/p&gt;
6375
6376 &lt;p&gt;After many hours of cleaning and migration, the ng-utils project
6377 now have a new home, and a git repository with the highlight of the
6378 history of the project. I published all release tarballs and imported
6379 them into the git repository. As the project is really stable and not
6380 expected to gain new features any time soon, I decided to make a new
6381 release and call it 1.0. Visit the new project home on
6382 &lt;a href=&quot;https://alioth.debian.org/projects/ng-utils/&quot;&gt;https://alioth.debian.org/projects/ng-utils/&lt;/a&gt;
6383 if you want to check it out. The new version is also uploaded into
6384 &lt;a href=&quot;http://packages.qa.debian.org/n/ng-utils.html&quot;&gt;Debian Unstable&lt;/a&gt;.&lt;/p&gt;
6385 </description>
6386 </item>
6387
6388 <item>
6389 <title>Testing sysvinit from experimental in Debian Hurd</title>
6390 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</link>
6391 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html</guid>
6392 <pubDate>Mon, 3 Feb 2014 13:40:00 +0100</pubDate>
6393 <description>&lt;p&gt;A few days ago I decided to try to help the Hurd people to get
6394 their changes into sysvinit, to allow them to use the normal sysvinit
6395 boot system instead of their old one. This follow up on the
6396 &lt;a href=&quot;https://teythoon.cryptobitch.de//categories/gsoc.html&quot;&gt;great
6397 Google Summer of Code work&lt;/a&gt; done last summer by Justus Winter to
6398 get Debian on Hurd working more like Debian on Linux. To get started,
6399 I downloaded a prebuilt hard disk image from
6400 &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;,
6401 and started it using virt-manager.&lt;/p&gt;
6402
6403 &lt;p&gt;The first think I had to do after logging in (root without any
6404 password) was to get the network operational. I followed
6405 &lt;a href=&quot;https://www.debian.org/ports/hurd/hurd-install&quot;&gt;the
6406 instructions on the Debian GNU/Hurd ports page&lt;/a&gt; and ran these
6407 commands as root to get the machine to accept a IP address from the
6408 kvm internal DHCP server:&lt;/p&gt;
6409
6410 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6411 settrans -fgap /dev/netdde /hurd/netdde
6412 kill $(ps -ef|awk &#39;/[p]finet/ { print $2}&#39;)
6413 kill $(ps -ef|awk &#39;/[d]evnode/ { print $2}&#39;)
6414 dhclient /dev/eth0
6415 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6416
6417 &lt;p&gt;After this, the machine had internet connectivity, and I could
6418 upgrade it and install the sysvinit packages from experimental and
6419 enable it as the default boot system in Hurd.&lt;/p&gt;
6420
6421 &lt;p&gt;But before I did that, I set a password on the root user, as ssh is
6422 running on the machine it for ssh login to work a password need to be
6423 set. Also, note that a bug somewhere in openssh on Hurd block
6424 compression from working. Remember to turn that off on the client
6425 side.&lt;/p&gt;
6426
6427 &lt;p&gt;Run these commands as root to upgrade and test the new sysvinit
6428 stuff:&lt;/p&gt;
6429
6430 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6431 cat &gt; /etc/apt/sources.list.d/experimental.list &amp;lt;&amp;lt;EOF
6432 deb http://http.debian.net/debian/ experimental main
6433 EOF
6434 apt-get update
6435 apt-get dist-upgrade
6436 apt-get install -t experimental initscripts sysv-rc sysvinit \
6437 sysvinit-core sysvinit-utils
6438 update-alternatives --config runsystem
6439 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6440
6441 &lt;p&gt;To reboot after switching boot system, you have to use
6442 &lt;tt&gt;reboot-hurd&lt;/tt&gt; instead of just &lt;tt&gt;reboot&lt;/tt&gt;, as there is not
6443 yet a sysvinit process able to receive the signals from the normal
6444 &#39;reboot&#39; command. After switching to sysvinit as the boot system,
6445 upgrading every package and rebooting, the network come up with DHCP
6446 after boot as it should, and the settrans/pkill hack mentioned at the
6447 start is no longer needed. But for some strange reason, there are no
6448 longer any login prompt in the virtual console, so I logged in using
6449 ssh instead.
6450
6451 &lt;p&gt;Note that there are some race conditions in Hurd making the boot
6452 fail some times. No idea what the cause is, but hope the Hurd porters
6453 figure it out. At least Justus said on IRC (#debian-hurd on
6454 irc.debian.org) that they are aware of the problem. A way to reduce
6455 the impact is to upgrade to the Hurd packages built by Justus by
6456 adding this repository to the machine:&lt;/p&gt;
6457
6458 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6459 cat &gt; /etc/apt/sources.list.d/hurd-ci.list &amp;lt;&amp;lt;EOF
6460 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
6461 EOF
6462 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6463
6464 &lt;p&gt;At the moment the prebuilt virtual machine get some packages from
6465 http://ftp.debian-ports.org/debian, because some of the packages in
6466 unstable do not yet include the required patches that are lingering in
6467 BTS. This is the completely list of &quot;unofficial&quot; packages installed:&lt;/p&gt;
6468
6469 &lt;p&gt;&lt;blockquote&gt;&lt;pre&gt;
6470 # aptitude search &#39;?narrow(?version(CURRENT),?origin(Debian Ports))&#39;
6471 i emacs - GNU Emacs editor (metapackage)
6472 i gdb - GNU Debugger
6473 i hurd-recommended - Miscellaneous translators
6474 i isc-dhcp-client - ISC DHCP client
6475 i isc-dhcp-common - common files used by all the isc-dhcp* packages
6476 i libc-bin - Embedded GNU C Library: Binaries
6477 i libc-dev-bin - Embedded GNU C Library: Development binaries
6478 i libc0.3 - Embedded GNU C Library: Shared libraries
6479 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
6480 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
6481 i multiarch-support - Transitional package to ensure multiarch compatibilit
6482 i A x11-common - X Window System (X.Org) infrastructure
6483 i xorg - X.Org X Window System
6484 i A xserver-xorg - X.Org X server
6485 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
6486 #
6487 &lt;/pre&gt;&lt;/blockquote&gt;&lt;/p&gt;
6488
6489 &lt;p&gt;All in all, testing hurd has been an interesting experience. :)
6490 X.org did not work out of the box and I never took the time to follow
6491 the porters instructions to fix it. This time I was interested in the
6492 command line stuff.&lt;p&gt;
6493 </description>
6494 </item>
6495
6496 <item>
6497 <title>New chrpath release 0.16</title>
6498 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</link>
6499 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html</guid>
6500 <pubDate>Tue, 14 Jan 2014 11:00:00 +0100</pubDate>
6501 <description>&lt;p&gt;&lt;a href=&quot;http://www.coverity.com/&quot;&gt;Coverity&lt;/a&gt; is a nice tool to
6502 find problems in C, C++ and Java code using static source code
6503 analysis. It can detect a lot of different problems, and is very
6504 useful to find memory and locking bugs in the error handling part of
6505 the source. The company behind it provide
6506 &lt;a href=&quot;https://scan.coverity.com/&quot;&gt;check of free software projects as
6507 a community service&lt;/a&gt;, and many hundred free software projects are
6508 already checked. A few days ago I decided to have a closer look at
6509 the Coverity system, and discovered that the
6510 &lt;a href=&quot;http://www.gnu.org/software/gnash/&quot;&gt;gnash&lt;/a&gt; and
6511 &lt;a href=&quot;http://sourceforge.net/projects/ipmitool/&quot;&gt;ipmitool&lt;/a&gt;
6512 projects I am involved with was already registered. But these are
6513 fairly big, and I would also like to have a small and easy project to
6514 check, and decided to &lt;a href=&quot;http://scan.coverity.com/projects/1179&quot;&gt;request
6515 checking of the chrpath project&lt;/a&gt;. It was
6516 added to the checker and discovered seven potential defects. Six of
6517 these were real, mostly resource &quot;leak&quot; when the program detected an
6518 error. Nothing serious, as the resources would be released a fraction
6519 of a second later when the program exited because of the error, but it
6520 is nice to do it right in case the source of the program some time in
6521 the future end up in a library. Having fixed all defects and added
6522 &lt;a href=&quot;https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel&quot;&gt;a
6523 mailing list for the chrpath developers&lt;/a&gt;, I decided it was time to
6524 publish a new release. These are the release notes:&lt;/p&gt;
6525
6526 &lt;p&gt;New in 0.16 released 2014-01-14:&lt;/p&gt;
6527
6528 &lt;ul&gt;
6529
6530 &lt;li&gt;Fixed all minor bugs discovered by Coverity.&lt;/li&gt;
6531 &lt;li&gt;Updated config.sub and config.guess from the GNU project.&lt;/li&gt;
6532 &lt;li&gt;Mention new project mailing list in the documentation.&lt;/li&gt;
6533
6534 &lt;/ul&gt;
6535
6536 &lt;p&gt;You can
6537 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
6538 new version 0.16 from alioth&lt;/a&gt;. Please let us know via the Alioth
6539 project if something is wrong with the new release. The test suite
6540 did not discover any old errors, so if you find a new one, please also
6541 include a test suite check.&lt;/p&gt;
6542 </description>
6543 </item>
6544
6545 <item>
6546 <title>New chrpath release 0.15</title>
6547 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</link>
6548 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html</guid>
6549 <pubDate>Sun, 24 Nov 2013 09:30:00 +0100</pubDate>
6550 <description>&lt;p&gt;After many years break from the package and a vain hope that
6551 development would be continued by someone else, I finally pulled my
6552 acts together this morning and wrapped up a new release of chrpath,
6553 the command line tool to modify the rpath and runpath of already
6554 compiled ELF programs. The update was triggered by the persistence of
6555 Isha Vishnoi at IBM, which needed a new config.guess file to get
6556 support for the ppc64le architecture (powerpc 64-bit Little Endian) he
6557 is working on. I checked the
6558 &lt;a href=&quot;http://packages.qa.debian.org/chrpath&quot;&gt;Debian&lt;/a&gt;,
6559 &lt;a href=&quot;https://launchpad.net/ubuntu/+source/chrpath&quot;&gt;Ubuntu&lt;/a&gt; and
6560 &lt;a href=&quot;https://admin.fedoraproject.org/pkgdb/acls/name/chrpath&quot;&gt;Fedora&lt;/a&gt;
6561 packages for interesting patches (failed to find the source from
6562 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
6563 These are the release notes:&lt;/p&gt;
6564
6565 &lt;p&gt;New in 0.15 released 2013-11-24:&lt;/p&gt;
6566
6567 &lt;ul&gt;
6568
6569 &lt;li&gt;Updated config.sub and config.guess from the GNU project to work
6570 with newer architectures. Thanks to isha vishnoi for the heads
6571 up.&lt;/li&gt;
6572
6573 &lt;li&gt;Updated README with current URLs.&lt;/li&gt;
6574
6575 &lt;li&gt;Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
6576 Matthias Klose.&lt;/li&gt;
6577
6578 &lt;li&gt;Added missing help for -k|--keepgoing option, using patch by
6579 Petr Machata found in Fedora.&lt;/li&gt;
6580
6581 &lt;li&gt;Rewrite removal of RPATH/RUNPATH to make sure the entry in
6582 .dynamic is a NULL terminated string. Based on patch found in
6583 Fedora credited Axel Thimm and Christian Krause.&lt;/li&gt;
6584
6585 &lt;/ul&gt;
6586
6587 &lt;p&gt;You can
6588 &lt;a href=&quot;https://alioth.debian.org/frs/?group_id=31052&quot;&gt;download the
6589 new version 0.15 from alioth&lt;/a&gt;. Please let us know via the Alioth
6590 project if something is wrong with the new release. The test suite
6591 did not discover any old errors, so if you find a new one, please also
6592 include a testsuite check.&lt;/p&gt;
6593 </description>
6594 </item>
6595
6596 <item>
6597 <title>Debian init.d boot script example for rsyslog</title>
6598 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</link>
6599 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html</guid>
6600 <pubDate>Sat, 2 Nov 2013 22:40:00 +0100</pubDate>
6601 <description>&lt;p&gt;If one of the points of switching to a new init system in Debian is
6602 &lt;a href=&quot;http://thomas.goirand.fr/blog/?p=147&quot;&gt;to get rid of huge
6603 init.d scripts&lt;/a&gt;, I doubt we need to switch away from sysvinit and
6604 init.d scripts at all. Here is an example init.d script, ie a rewrite
6605 of /etc/init.d/rsyslog:&lt;/p&gt;
6606
6607 &lt;p&gt;&lt;pre&gt;
6608 #!/lib/init/init-d-script
6609 ### BEGIN INIT INFO
6610 # Provides: rsyslog
6611 # Required-Start: $remote_fs $time
6612 # Required-Stop: umountnfs $time
6613 # X-Stop-After: sendsigs
6614 # Default-Start: 2 3 4 5
6615 # Default-Stop: 0 1 6
6616 # Short-Description: enhanced syslogd
6617 # Description: Rsyslog is an enhanced multi-threaded syslogd.
6618 # It is quite compatible to stock sysklogd and can be
6619 # used as a drop-in replacement.
6620 ### END INIT INFO
6621 DESC=&quot;enhanced syslogd&quot;
6622 DAEMON=/usr/sbin/rsyslogd
6623 &lt;/pre&gt;&lt;/p&gt;
6624
6625 &lt;p&gt;Pretty minimalistic to me... For the record, the original sysv-rc
6626 script was 137 lines, and the above is just 15 lines, most of it meta
6627 info/comments.&lt;/p&gt;
6628
6629 &lt;p&gt;How to do this, you ask? Well, one create a new script
6630 /lib/init/init-d-script looking something like this:
6631
6632 &lt;p&gt;&lt;pre&gt;
6633 #!/bin/sh
6634
6635 # Define LSB log_* functions.
6636 # Depend on lsb-base (&gt;= 3.2-14) to ensure that this file is present
6637 # and status_of_proc is working.
6638 . /lib/lsb/init-functions
6639
6640 #
6641 # Function that starts the daemon/service
6642
6643 #
6644 do_start()
6645 {
6646 # Return
6647 # 0 if daemon has been started
6648 # 1 if daemon was already running
6649 # 2 if daemon could not be started
6650 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test &gt; /dev/null \
6651 || return 1
6652 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
6653 $DAEMON_ARGS \
6654 || return 2
6655 # Add code here, if necessary, that waits for the process to be ready
6656 # to handle requests from services started subsequently which depend
6657 # on this one. As a last resort, sleep for some time.
6658 }
6659
6660 #
6661 # Function that stops the daemon/service
6662 #
6663 do_stop()
6664 {
6665 # Return
6666 # 0 if daemon has been stopped
6667 # 1 if daemon was already stopped
6668 # 2 if daemon could not be stopped
6669 # other if a failure occurred
6670 start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile $PIDFILE --name $NAME
6671 RETVAL=&quot;$?&quot;
6672 [ &quot;$RETVAL&quot; = 2 ] &amp;&amp; return 2
6673 # Wait for children to finish too if this is a daemon that forks
6674 # and if the daemon is only ever run from this initscript.
6675 # If the above conditions are not satisfied then add some other code
6676 # that waits for the process to drop all resources that could be
6677 # needed by services started subsequently. A last resort is to
6678 # sleep for some time.
6679 start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON
6680 [ &quot;$?&quot; = 2 ] &amp;&amp; return 2
6681 # Many daemons don&#39;t delete their pidfiles when they exit.
6682 rm -f $PIDFILE
6683 return &quot;$RETVAL&quot;
6684 }
6685
6686 #
6687 # Function that sends a SIGHUP to the daemon/service
6688 #
6689 do_reload() {
6690 #
6691 # If the daemon can reload its configuration without
6692 # restarting (for example, when it is sent a SIGHUP),
6693 # then implement that here.
6694 #
6695 start-stop-daemon --stop --signal 1 --quiet --pidfile $PIDFILE --name $NAME
6696 return 0
6697 }
6698
6699 SCRIPTNAME=$1
6700 scriptbasename=&quot;$(basename $1)&quot;
6701 echo &quot;SN: $scriptbasename&quot;
6702 if [ &quot;$scriptbasename&quot; != &quot;init-d-library&quot; ] ; then
6703 script=&quot;$1&quot;
6704 shift
6705 . $script
6706 else
6707 exit 0
6708 fi
6709
6710 NAME=$(basename $DAEMON)
6711 PIDFILE=/var/run/$NAME.pid
6712
6713 # Exit if the package is not installed
6714 #[ -x &quot;$DAEMON&quot; ] || exit 0
6715
6716 # Read configuration variable file if it is present
6717 [ -r /etc/default/$NAME ] &amp;&amp; . /etc/default/$NAME
6718
6719 # Load the VERBOSE setting and other rcS variables
6720 . /lib/init/vars.sh
6721
6722 case &quot;$1&quot; in
6723 start)
6724 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Starting $DESC&quot; &quot;$NAME&quot;
6725 do_start
6726 case &quot;$?&quot; in
6727 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
6728 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
6729 esac
6730 ;;
6731 stop)
6732 [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_daemon_msg &quot;Stopping $DESC&quot; &quot;$NAME&quot;
6733 do_stop
6734 case &quot;$?&quot; in
6735 0|1) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 0 ;;
6736 2) [ &quot;$VERBOSE&quot; != no ] &amp;&amp; log_end_msg 1 ;;
6737 esac
6738 ;;
6739 status)
6740 status_of_proc &quot;$DAEMON&quot; &quot;$NAME&quot; &amp;&amp; exit 0 || exit $?
6741 ;;
6742 #reload|force-reload)
6743 #
6744 # If do_reload() is not implemented then leave this commented out
6745 # and leave &#39;force-reload&#39; as an alias for &#39;restart&#39;.
6746 #
6747 #log_daemon_msg &quot;Reloading $DESC&quot; &quot;$NAME&quot;
6748 #do_reload
6749 #log_end_msg $?
6750 #;;
6751 restart|force-reload)
6752 #
6753 # If the &quot;reload&quot; option is implemented then remove the
6754 # &#39;force-reload&#39; alias
6755 #
6756 log_daemon_msg &quot;Restarting $DESC&quot; &quot;$NAME&quot;
6757 do_stop
6758 case &quot;$?&quot; in
6759 0|1)
6760 do_start
6761 case &quot;$?&quot; in
6762 0) log_end_msg 0 ;;
6763 1) log_end_msg 1 ;; # Old process is still running
6764 *) log_end_msg 1 ;; # Failed to start
6765 esac
6766 ;;
6767 *)
6768 # Failed to stop
6769 log_end_msg 1
6770 ;;
6771 esac
6772 ;;
6773 *)
6774 echo &quot;Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}&quot; &gt;&amp;2
6775 exit 3
6776 ;;
6777 esac
6778
6779 :
6780 &lt;/pre&gt;&lt;/p&gt;
6781
6782 &lt;p&gt;It is based on /etc/init.d/skeleton, and could be improved quite a
6783 lot. I did not really polish the approach, so it might not always
6784 work out of the box, but you get the idea. I did not try very hard to
6785 optimize it nor make it more robust either.&lt;/p&gt;
6786
6787 &lt;p&gt;A better argument for switching init system in Debian than reducing
6788 the size of init scripts (which is a good thing to do anyway), is to
6789 get boot system that is able to handle the kernel events sensibly and
6790 robustly, and do not depend on the boot to run sequentially. The boot
6791 and the kernel have not behaved sequentially in years.&lt;/p&gt;
6792 </description>
6793 </item>
6794
6795 <item>
6796 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian</title>
6797 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</link>
6798 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html</guid>
6799 <pubDate>Fri, 1 Nov 2013 11:00:00 +0100</pubDate>
6800 <description>&lt;p&gt;&lt;a href=&quot;http://www.spice-space.org/&quot;&gt;The SPICE protocol&lt;/a&gt; for
6801 remote display access is the preferred solution with oVirt and RedHat
6802 Enterprise Virtualization, and I was sad to discover the other day
6803 that the browser plugin needed to use these systems seamlessly was
6804 missing in Debian. The &lt;a href=&quot;http://bugs.debian.org/668284&quot;&gt;request
6805 for a package&lt;/a&gt; was from 2012-04-10 with no progress since
6806 2013-04-01, so I decided to wrap up a package based on the great work
6807 from Cajus Pollmeier and put it in a collab-maint maintained git
6808 repository to get a package I could use. I would very much like
6809 others to help me maintain the package (or just take over, I do not
6810 mind), but as no-one had volunteered so far, I just uploaded it to
6811 NEW. I hope it will be available in Debian in a few days.&lt;/p&gt;
6812
6813 &lt;p&gt;The source is now available from
6814 &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;
6815 </description>
6816 </item>
6817
6818 <item>
6819 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images</title>
6820 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</link>
6821 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html</guid>
6822 <pubDate>Sun, 27 Oct 2013 17:00:00 +0100</pubDate>
6823 <description>&lt;p&gt;The
6824 &lt;a href=&quot;http://packages.qa.debian.org/v/vmdebootstrap.html&quot;&gt;vmdebootstrap&lt;/a&gt;
6825 program is a a very nice system to create virtual machine images. It
6826 create a image file, add a partition table, mount it and run
6827 debootstrap in the mounted directory to create a Debian system on a
6828 stick. Yesterday, I decided to try to teach it how to make images for
6829 &lt;a href=&quot;https://wiki.debian.org/RaspberryPi&quot;&gt;Raspberry Pi&lt;/a&gt;, as part
6830 of a plan to simplify the build system for
6831 &lt;a href=&quot;https://wiki.debian.org/FreedomBox&quot;&gt;the FreedomBox
6832 project&lt;/a&gt;. The FreedomBox project already uses vmdebootstrap for
6833 the virtualbox images, but its current build system made multistrap
6834 based system for Dreamplug images, and it is lacking support for
6835 Raspberry Pi.&lt;/p&gt;
6836
6837 &lt;p&gt;Armed with the knowledge on how to build &quot;foreign&quot; (aka non-native
6838 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
6839 code and adjusted it to be able to build armel images on my amd64
6840 Debian laptop. I ended up giving vmdebootstrap five new options,
6841 allowing me to replicate the image creation process I use to make
6842 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html&quot;&gt;Debian
6843 Jessie based mesh node images for the Raspberry Pi&lt;/a&gt;. First, the
6844 &lt;tt&gt;--foreign /path/to/binfm_handler&lt;/tt&gt; option tell vmdebootstrap to
6845 call debootstrap with --foreign and to copy the handler into the
6846 generated chroot before running the second stage. This allow
6847 vmdebootstrap to create armel images on an amd64 host. Next I added
6848 two new options &lt;tt&gt;--bootsize size&lt;/tt&gt; and &lt;tt&gt;--boottype
6849 fstype&lt;/tt&gt; to teach it to create a separate /boot/ partition with the
6850 given file system type, allowing me to create an image with a vfat
6851 partition for the /boot/ stuff. I also added a &lt;tt&gt;--variant
6852 variant&lt;/tt&gt; option to allow me to create smaller images without the
6853 Debian base system packages installed. Finally, I added an option
6854 &lt;tt&gt;--no-extlinux&lt;/tt&gt; to tell vmdebootstrap to not install extlinux
6855 as a boot loader. It is not needed on the Raspberry Pi and probably
6856 most other non-x86 architectures. The changes were accepted by the
6857 upstream author of vmdebootstrap yesterday and today, and is now
6858 available from
6859 &lt;a href=&quot;http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/&quot;&gt;the
6860 upstream project page&lt;/a&gt;.&lt;/p&gt;
6861
6862 &lt;p&gt;To use it to build a Raspberry Pi image using Debian Jessie, first
6863 create a small script (the customize script) to add the non-free
6864 binary blob needed to boot the Raspberry Pi and the APT source
6865 list:&lt;/p&gt;
6866
6867 &lt;p&gt;&lt;pre&gt;
6868 #!/bin/sh
6869 set -e # Exit on first error
6870 rootdir=&quot;$1&quot;
6871 cd &quot;$rootdir&quot;
6872 cat &amp;lt;&amp;lt;EOF &gt; etc/apt/sources.list
6873 deb http://http.debian.net/debian/ jessie main contrib non-free
6874 EOF
6875 # Install non-free binary blob needed to boot Raspberry Pi. This
6876 # install a kernel somewhere too.
6877 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
6878 -O $rootdir/usr/bin/rpi-update
6879 chmod a+x $rootdir/usr/bin/rpi-update
6880 mkdir -p $rootdir/lib/modules
6881 touch $rootdir/boot/start.elf
6882 chroot $rootdir rpi-update
6883 &lt;/pre&gt;&lt;/p&gt;
6884
6885 &lt;p&gt;Next, fetch the latest vmdebootstrap script and call it like this
6886 to build the image:&lt;/p&gt;
6887
6888 &lt;pre&gt;
6889 sudo ./vmdebootstrap \
6890 --variant minbase \
6891 --arch armel \
6892 --distribution jessie \
6893 --mirror http://http.debian.net/debian \
6894 --image test.img \
6895 --size 600M \
6896 --bootsize 64M \
6897 --boottype vfat \
6898 --log-level debug \
6899 --verbose \
6900 --no-kernel \
6901 --no-extlinux \
6902 --root-password raspberry \
6903 --hostname raspberrypi \
6904 --foreign /usr/bin/qemu-arm-static \
6905 --customize `pwd`/customize \
6906 --package netbase \
6907 --package git-core \
6908 --package binutils \
6909 --package ca-certificates \
6910 --package wget \
6911 --package kmod
6912 &lt;/pre&gt;&lt;/p&gt;
6913
6914 &lt;p&gt;The list of packages being installed are the ones needed by
6915 rpi-update to make the image bootable on the Raspberry Pi, with the
6916 exception of netbase, which is needed by debootstrap to find
6917 /etc/hosts with the minbase variant. I really wish there was a way to
6918 set up an Raspberry Pi using only packages in the Debian archive, but
6919 that is not possible as far as I know, because it boots from the GPU
6920 using a non-free binary blob.&lt;/p&gt;
6921
6922 &lt;p&gt;The build host need debootstrap, kpartx and qemu-user-static and
6923 probably a few others installed. I have not checked the complete
6924 build dependency list.&lt;/p&gt;
6925
6926 &lt;p&gt;The resulting image will not use the hardware floating point unit
6927 on the Raspberry PI, because the armel architecture in Debian is not
6928 optimized for that use. So the images created will be a bit slower
6929 than &lt;a href=&quot;http://www.raspbian.org/&quot;&gt;Raspbian&lt;/a&gt; based images.&lt;/p&gt;
6930 </description>
6931 </item>
6932
6933 <item>
6934 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway</title>
6935 <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>
6936 <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>
6937 <pubDate>Tue, 15 Oct 2013 21:30:00 +0200</pubDate>
6938 <description>&lt;p&gt;The last few days I came across a few good causes that should get
6939 wider attention. I recommend signing and donating to each one of
6940 these. :)&lt;/p&gt;
6941
6942 &lt;p&gt;Via &lt;a href=&quot;http://www.debian.org/News/weekly/2013/18/&quot;&gt;Debian
6943 Project News for 2013-10-14&lt;/a&gt; I came across the Outreach Program for
6944 Women program which is a Google Summer of Code like initiative to get
6945 more women involved in free software. One debian sponsor has offered
6946 to match &lt;a href=&quot;http://debian.ch/opw2013&quot;&gt;any donation done to Debian
6947 earmarked&lt;/a&gt; for this initiative. I donated a few minutes ago, and
6948 hope you will to. :)&lt;/p&gt;
6949
6950 &lt;p&gt;And the Electronic Frontier Foundation just announced plans to
6951 create &lt;a href=&quot;https://supporters.eff.org/donate/nsa-videos&quot;&gt;video
6952 documentaries about the excessive spying&lt;/a&gt; on every Internet user that
6953 take place these days, and their need to fund the work. I&#39;ve already
6954 donated. Are you next?&lt;/p&gt;
6955
6956 &lt;p&gt;For my Norwegian audience, the organisation Studentenes og
6957 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
6958 statement under the heading
6959 &lt;a href=&quot;http://saih.no/Bloggers_United/&quot;&gt;Bloggers United for Open
6960 Access&lt;/a&gt; for those of us asking for more focus on open access in the
6961 Norwegian government. So far 499 signatures. I hope you will sign it
6962 too.&lt;/p&gt;
6963 </description>
6964 </item>
6965
6966 <item>
6967 <title>Videos about the Freedombox project - for inspiration and learning</title>
6968 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</link>
6969 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html</guid>
6970 <pubDate>Fri, 27 Sep 2013 14:10:00 +0200</pubDate>
6971 <description>&lt;p&gt;The &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox
6972 project&lt;/a&gt; have been going on for a while, and have presented the
6973 vision, ideas and solution several places. Here is a little
6974 collection of videos of talks and presentation of the project.&lt;/p&gt;
6975
6976 &lt;ul&gt;
6977
6978 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=ukvUz5taxvA&quot;&gt;FreedomBox -
6979 2,5 minute marketing film&lt;/a&gt; (Youtube)&lt;/li&gt;
6980
6981 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=SzW25QTVWsE&quot;&gt;Eben Moglen
6982 discusses the Freedombox on CBS news 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
6983
6984 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=Ae8SZbxfE0g&quot;&gt;Eben Moglen -
6985 Freedom in the Cloud - Software Freedom, Privacy and and Security for
6986 Web 2.0 and Cloud computing at ISOC-NY Public Meeting 2010&lt;/a&gt;
6987 (Youtube)&lt;/li&gt;
6988
6989 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=vNaIji_3xBE&quot;&gt;Fosdem 2011
6990 Keynote by Eben Moglen presenting the Freedombox&lt;/a&gt; (Youtube)&lt;/li&gt;
6991
6992 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=9bDDUyJSQ9s&quot;&gt;Presentation of
6993 the Freedombox by James Vasile at Elevate in Gratz 2011&lt;/a&gt; (Youtube)&lt;/li&gt;
6994
6995 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=zQTmnk27g9s&quot;&gt; Freedombox -
6996 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
6997 York City in 2012&lt;/a&gt; (Youtube)&lt;/li&gt;
6998
6999 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=tkbSB4Ba7Ck&quot;&gt;Introduction
7000 to the Freedombox at Freedombox Hackfest New York City in 2012&lt;/a&gt;
7001 (Youtube)&lt;/li&gt;
7002
7003 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=z-P2Jaeg0aQ&quot;&gt;Freedom, Out
7004 of the Box! by Bdale Garbee at linux.conf.au Ballarat, 2012&lt;/a&gt; (Youtube) &lt;/li&gt;
7005
7006 &lt;li&gt;&lt;a href=&quot;https://archive.fosdem.org/2013/schedule/event/freedombox/&quot;&gt;Freedombox
7007 1.0 by Eben Moglen and Bdale Garbee at Fosdem 2013&lt;/a&gt; (FOSDEM) &lt;/li&gt;
7008
7009 &lt;li&gt;&lt;a href=&quot;http://www.youtube.com/watch?v=e1LpYX2zVYg&quot;&gt;What is the
7010 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7011 2013&lt;/a&gt; (Youtube)&lt;/li&gt;
7012
7013 &lt;/ul&gt;
7014
7015 &lt;p&gt;A larger list is available from
7016 &lt;a href=&quot;https://wiki.debian.org/FreedomBox/TalksAndPresentations&quot;&gt;the
7017 Freedombox Wiki&lt;/a&gt;.&lt;/p&gt;
7018
7019 &lt;p&gt;On other news, I am happy to report that Freedombox based on Debian
7020 Jessie is coming along quite well, and soon both Owncloud and using
7021 Tor should be available for testers of the Freedombox solution. :) In
7022 a few weeks I hope everything needed to test it is included in Debian.
7023 The withsqlite package is already in Debian, and the plinth package is
7024 pending in NEW. The third and vital part of that puzzle is the
7025 metapackage/setup framework, which is still pending an upload. Join
7026 us on &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;IRC
7027 (#freedombox on irc.debian.org)&lt;/a&gt; and
7028 &lt;a href=&quot;http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss&quot;&gt;the
7029 mailing list&lt;/a&gt; if you want to help make this vision come true.&lt;/p&gt;
7030 </description>
7031 </item>
7032
7033 <item>
7034 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi</title>
7035 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</link>
7036 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html</guid>
7037 <pubDate>Tue, 10 Sep 2013 14:20:00 +0200</pubDate>
7038 <description>&lt;p&gt;I was introduced to the
7039 &lt;a href=&quot;http://www.freedomboxfoundation.org/&quot;&gt;Freedombox project&lt;/a&gt;
7040 in 2010, when Eben Moglen presented his vision about serving the need
7041 of non-technical people to keep their personal information private and
7042 within the legal protection of their own homes. The idea is to give
7043 people back the power over their network and machines, and return
7044 Internet back to its intended peer-to-peer architecture. Instead of
7045 depending on a central service, the Freedombox will give everyone
7046 control over their own basic infrastructure.&lt;/p&gt;
7047
7048 &lt;p&gt;I&#39;ve intended to join the effort since then, but other tasks have
7049 taken priority. But this summers nasty news about the misuse of trust
7050 and privilege exercised by the &quot;western&quot; intelligence gathering
7051 communities increased my eagerness to contribute to a point where I
7052 actually started working on the project a while back.&lt;/p&gt;
7053
7054 &lt;p&gt;The &lt;a href=&quot;https://alioth.debian.org/projects/freedombox/&quot;&gt;initial
7055 Debian initiative&lt;/a&gt; based on the vision from Eben Moglen, is to
7056 create a simple and cheap Debian based appliance that anyone can hook
7057 up in their home and get access to secure and private services and
7058 communication. The initial deployment platform have been the
7059 &lt;a href=&quot;http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx&quot;&gt;Dreamplug&lt;/a&gt;,
7060 which is a piece of hardware I do not own. So to be able to test what
7061 the current Freedombox setup look like, I had to come up with a way to install
7062 it on some hardware I do have access to. I have rewritten the
7063 &lt;a href=&quot;https://github.com/NickDaly/freedom-maker&quot;&gt;freedom-maker&lt;/a&gt;
7064 image build framework to use .deb packages instead of only copying
7065 setup into the boot images, and thanks to this rewrite I am able to
7066 set up any machine supported by Debian Wheezy as a Freedombox, using
7067 the previously mentioned deb (and a few support debs for packages
7068 missing in Debian).&lt;/p&gt;
7069
7070 &lt;p&gt;The current Freedombox setup consist of a set of bootstrapping
7071 scripts
7072 (&lt;a href=&quot;https://github.com/petterreinholdtsen/freedombox-setup&quot;&gt;freedombox-setup&lt;/a&gt;),
7073 and a administrative web interface
7074 (&lt;a href=&quot;https://github.com/NickDaly/Plinth&quot;&gt;plinth&lt;/a&gt; + exmachina +
7075 withsqlite), as well as a privacy enhancing proxy based on
7076 &lt;a href=&quot;http://packages.qa.debian.org/privoxy&quot;&gt;privoxy&lt;/a&gt;
7077 (freedombox-privoxy). There is also a web/javascript based XMPP
7078 client (&lt;a href=&quot;http://packages.qa.debian.org/jwchat&quot;&gt;jwchat&lt;/a&gt;)
7079 trying (unsuccessfully so far) to talk to the XMPP server
7080 (&lt;a href=&quot;http://packages.qa.debian.org/ejabberd&quot;&gt;ejabberd&lt;/a&gt;). The
7081 web interface is pluggable, and the goal is to use it to enable OpenID
7082 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7083 this is really working yet, see
7084 &lt;a href=&quot;https://github.com/NickDaly/freedombox-todos/blob/master/TODO&quot;&gt;the
7085 project TODO&lt;/a&gt; for links to GIT repositories. Most of the code is
7086 on github at the moment. The HTTP proxy is operational out of the
7087 box, and the admin web interface can be used to add/remove plinth
7088 users. I&#39;ve not been able to do anything else with it so far, but
7089 know there are several branches spread around github and other places
7090 with lots of half baked features.&lt;/p&gt;
7091
7092 &lt;p&gt;Anyway, if you want to have a look at the current state, the
7093 following recipes should work to give you a test machine to poke
7094 at.&lt;/p&gt;
7095
7096 &lt;p&gt;&lt;strong&gt;Debian Wheezy amd64&lt;/strong&gt;&lt;/p&gt;
7097
7098 &lt;ol&gt;
7099
7100 &lt;li&gt;Fetch normal Debian Wheezy installation ISO.&lt;/li&gt;
7101 &lt;li&gt;Boot from it, either as CD or USB stick.&lt;/li&gt;
7102 &lt;li&gt;&lt;p&gt;Press [tab] on the boot prompt and add this as a boot argument
7103 to the Debian installer:&lt;p&gt;
7104 &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;
7105
7106 &lt;li&gt;Answer the few language/region/password questions and pick disk to
7107 install on.&lt;/li&gt;
7108
7109 &lt;li&gt;When the installation is finished and the machine have rebooted a
7110 few times, your Freedombox is ready for testing.&lt;/li&gt;
7111
7112 &lt;/ol&gt;
7113
7114 &lt;p&gt;&lt;strong&gt;Raspberry Pi Raspbian&lt;/strong&gt;&lt;/p&gt;
7115
7116 &lt;ol&gt;
7117
7118 &lt;li&gt;Fetch a Raspbian SD card image, create SD card.&lt;/li&gt;
7119 &lt;li&gt;Boot from SD card, extend file system to fill the card completely.&lt;/li&gt;
7120 &lt;li&gt;&lt;p&gt;Log in and add this to /etc/sources.list:&lt;/p&gt;
7121 &lt;pre&gt;
7122 deb &lt;a href=&quot;http://www.reinholdtsen.name/freedombox/&quot;&gt;http://www.reinholdtsen.name/freedombox&lt;/a&gt; wheezy main
7123 &lt;/pre&gt;&lt;/li&gt;
7124 &lt;li&gt;&lt;p&gt;Run this as root:&lt;/p&gt;
7125 &lt;pre&gt;
7126 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7127 apt-key add -
7128 apt-get update
7129 apt-get install freedombox-setup
7130 /usr/lib/freedombox/setup
7131 &lt;/pre&gt;&lt;/li&gt;
7132 &lt;li&gt;Reboot into your freshly created Freedombox.&lt;/li&gt;
7133
7134 &lt;/ol&gt;
7135
7136 &lt;p&gt;You can test it on other architectures too, but because the
7137 freedombox-privoxy package is binary, it will only work as intended on
7138 the architectures where I have had time to build the binary and put it
7139 in my APT repository. But do not let this stop you. It is only a
7140 short &quot;&lt;tt&gt;apt-get source -b freedombox-privoxy&lt;/tt&gt;&quot; away. :)&lt;/p&gt;
7141
7142 &lt;p&gt;Note that by default Freedombox is a DHCP server on the
7143 192.168.1.0/24 subnet, so if this is your subnet be careful and turn
7144 off the DHCP server by running &quot;&lt;tt&gt;update-rc.d isc-dhcp-server
7145 disable&lt;/tt&gt;&quot; as root.&lt;/p&gt;
7146
7147 &lt;p&gt;Please let me know if this works for you, or if you have any
7148 problems. We gather on the IRC channel
7149 &lt;a href=&quot;irc://irc.debian.org:6667/%23freedombox&quot;&gt;#freedombox&lt;/a&gt; on
7150 irc.debian.org and the
7151 &lt;a href=&quot;http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss&quot;&gt;project
7152 mailing list&lt;/a&gt;.&lt;/p&gt;
7153
7154 &lt;p&gt;Once you get your freedombox operational, you can visit
7155 &lt;tt&gt;http://your-host-name:8001/&lt;/tt&gt; to see the state of the plint
7156 welcome screen (dead end - do not be surprised if you are unable to
7157 get past it), and next visit &lt;tt&gt;http://your-host-name:8001/help/&lt;/tt&gt;
7158 to look at the rest of plinth. The default user is &#39;admin&#39; and the
7159 default password is &#39;secret&#39;.&lt;/p&gt;
7160 </description>
7161 </item>
7162
7163 <item>
7164 <title>Intel 180 SSD disk with Lenovo firmware can not use Intel firmware</title>
7165 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</link>
7166 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html</guid>
7167 <pubDate>Sun, 18 Aug 2013 14:00:00 +0200</pubDate>
7168 <description>&lt;p&gt;Earlier, I reported about
7169 &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
7170 problems using an Intel SSD 520 Series 180 GB disk&lt;/a&gt;. Friday I was
7171 told by IBM that the original disk should be thrown away. And as
7172 there no longer was a problem if I bricked the firmware, I decided
7173 today to try to install Intel firmware to replace the Lenovo firmware
7174 currently on the disk.&lt;/p&gt;
7175
7176 &lt;p&gt;I searched the Intel site for firmware, and found
7177 &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;
7178 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
7179 according to the site should contain the latest firmware for SSD
7180 disks. I inserted the broken disk in one of my spare laptops and
7181 booted the ISO from a USB stick. The disk was recognized, but the
7182 program claimed the newest firmware already were installed and refused
7183 to insert any Intel firmware. So no change, and the disk is still
7184 unable to handle write load. :( I guess the only way to get them
7185 working would be if Lenovo releases new firmware. No idea how likely
7186 that is. Anyway, just blogging about this test for completeness. I
7187 got a working Samsung disk, and see no point in spending more time on
7188 the broken disks.&lt;/p&gt;
7189 </description>
7190 </item>
7191
7192 <item>
7193 <title>How to fix a Thinkpad X230 with a broken 180 GB SSD disk</title>
7194 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</link>
7195 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html</guid>
7196 <pubDate>Wed, 17 Jul 2013 23:50:00 +0200</pubDate>
7197 <description>&lt;p&gt;Today I switched to
7198 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;my
7199 new laptop&lt;/a&gt;. I&#39;ve previously written about the problems I had with
7200 my new Thinkpad X230, which was delivered with an
7201 &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
7202 GB Intel SSD disk with Lenovo firmware&lt;/a&gt; that did not handle
7203 sustained writes. My hardware supplier have been very forthcoming in
7204 trying to find a solution, and after first trying with another
7205 identical 180 GB disks they decided to send me a 256 GB Samsung SSD
7206 disk instead to fix it once and for all. The Samsung disk survived
7207 the installation of Debian with encrypted disks (filling the disk with
7208 random data during installation killed the first two), and I thus
7209 decided to trust it with my data. I have installed it as a Debian Edu
7210 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
7211 server at home using Kerberos and LDAP, and will use it as my work
7212 station from now on.&lt;/p&gt;
7213
7214 &lt;p&gt;As this is a solid state disk with no moving parts, I believe the
7215 Debian Wheezy default installation need to be tuned a bit to increase
7216 performance and increase life time of the disk. The Linux kernel and
7217 user space applications do not yet adjust automatically to such
7218 environment. To make it easier for my self, I created a draft Debian
7219 package &lt;tt&gt;ssd-setup&lt;/tt&gt; to handle this tuning. The
7220 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git&quot;&gt;source
7221 for the ssd-setup package&lt;/a&gt; is available from collab-maint, and it
7222 is set up to adjust the setup of the machine by just installing the
7223 package. If there is any non-SSD disk in the machine, the package
7224 will refuse to install, as I did not try to write any logic to sort
7225 file systems in SSD and non-SSD file systems.&lt;/p&gt;
7226
7227 &lt;p&gt;I consider the package a draft, as I am a bit unsure how to best
7228 set up Debian Wheezy with an SSD. It is adjusted to my use case,
7229 where I set up the machine with one large encrypted partition (in
7230 addition to /boot), put LVM on top of this and set up partitions on
7231 top of this again. See the README file in the package source for the
7232 references I used to pick the settings. At the moment these
7233 parameters are tuned:&lt;/p&gt;
7234
7235 &lt;ul&gt;
7236
7237 &lt;li&gt;Set up cryptsetup to pass TRIM commands to the physical disk
7238 (adding discard to /etc/crypttab)&lt;/li&gt;
7239
7240 &lt;li&gt;Set up LVM to pass on TRIM commands to the underlying device (in
7241 this case a cryptsetup partition) by changing issue_discards from
7242 0 to 1 in /etc/lvm/lvm.conf.&lt;/li&gt;
7243
7244 &lt;li&gt;Set relatime as a file system option for ext3 and ext4 file
7245 systems.&lt;/li&gt;
7246
7247 &lt;li&gt;Tell swap to use TRIM commands by adding &#39;discard&#39; to
7248 /etc/fstab.&lt;/li&gt;
7249
7250 &lt;li&gt;Change I/O scheduler from cfq to deadline using a udev rule.&lt;/li&gt;
7251
7252 &lt;li&gt;Run fstrim on every ext3 and ext4 file system every night (from
7253 cron.daily).&lt;/li&gt;
7254
7255 &lt;li&gt;Adjust sysctl values vm.swappiness to 1 and vm.vfs_cache_pressure
7256 to 50 to reduce the kernel eagerness to swap out processes.&lt;/li&gt;
7257
7258 &lt;/ul&gt;
7259
7260 &lt;p&gt;During installation, I cancelled the part where the installer fill
7261 the disk with random data, as this would kill the SSD performance for
7262 little gain. My goal with the encrypted file system is to ensure
7263 those stealing my laptop end up with a brick and not a working
7264 computer. I have no hope in keeping the really resourceful people
7265 from getting the data on the disk (see
7266 &lt;a href=&quot;http://xkcd.com/538/&quot;&gt;XKCD #538&lt;/a&gt; for an explanation why).
7267 Thus I concluded that adding the discard option to crypttab is the
7268 right thing to do.&lt;/p&gt;
7269
7270 &lt;p&gt;I considered using the noop I/O scheduler, as several recommended
7271 it for SSD, but others recommended deadline and a benchmark I found
7272 indicated that deadline might be better for interactive use.&lt;/p&gt;
7273
7274 &lt;p&gt;I also considered using the &#39;discard&#39; file system option for ext3
7275 and ext4, but read that it would give a performance hit ever time a
7276 file is removed, and thought it best to that that slowdown once a day
7277 instead of during my work.&lt;/p&gt;
7278
7279 &lt;p&gt;My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
7280 this is already done by Debian Edu.&lt;/p&gt;
7281
7282 &lt;p&gt;I have not yet started on the user space tuning. I expect
7283 iceweasel need some tuning, and perhaps other applications too, but
7284 have not yet had time to investigate those parts.&lt;/p&gt;
7285
7286 &lt;p&gt;The package should work on Ubuntu too, but I have not yet tested it
7287 there.&lt;/p&gt;
7288
7289 &lt;p&gt;As for the answer to the question in the title of this blog post,
7290 as far as I know, the only solution I know about is to replace the
7291 disk. It might be possible to flash it with Intel firmware instead of
7292 the Lenovo firmware. But I have not tried and did not want to do so
7293 without approval from Lenovo as I wanted to keep the warranty on the
7294 disk until a solution was found and they wanted the broken disks
7295 back.&lt;/p&gt;
7296 </description>
7297 </item>
7298
7299 <item>
7300 <title>Intel SSD 520 Series 180 GB with Lenovo firmware still lock up from sustained writes</title>
7301 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html</link>
7302 <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>
7303 <pubDate>Wed, 10 Jul 2013 13:30:00 +0200</pubDate>
7304 <description>&lt;p&gt;A few days ago, I wrote about
7305 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html&quot;&gt;the
7306 problems I experienced with my new X230 and its SSD disk&lt;/a&gt;, which
7307 was dying during installation because it is unable to cope with
7308 sustained write. My supplier is in contact with
7309 &lt;a href=&quot;http://www.lenovo.com/&quot;&gt;Lenovo&lt;/a&gt;, and they wanted to send a
7310 replacement disk to try to fix the problem. They decided to send an
7311 identical model, so my hopes for a permanent fix was slim.&lt;/p&gt;
7312
7313 &lt;p&gt;Anyway, today I got the replacement disk and tried to install
7314 Debian Edu Wheezy with encrypted disk on it. The new disk have the
7315 same firmware version as the original. This time my hope raised
7316 slightly as the installation progressed, as the original disk used to
7317 die after 4-7% of the disk was written to, while this time it kept
7318 going past 10%, 20%, 40% and even past 50%. But around 60%, the disk
7319 died again and I was back on square one. I still do not have a new
7320 laptop with a disk I can trust. I can not live with a disk that might
7321 lock up when I download a new
7322 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; ISO or
7323 other large files. I look forward to hearing from my supplier with
7324 the next proposal from Lenovo.&lt;/p&gt;
7325
7326 &lt;p&gt;The original disk is marked Intel SSD 520 Series 180 GB,
7327 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
7328 LF1i, 29MAY2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
7329 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40002756C4, Model:
7330 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
7331 P/N 45N8295, P0C38732.&lt;/p&gt;
7332
7333 &lt;p&gt;The replacement disk is marked Intel SSD 520 Series 180 GB,
7334 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-302, FW:
7335 LF1i, 22APR2013, PBA: G39779-300, LBA 351,651,888, LI P/N: 0C38722,
7336 Pb-free 2LI, LC P/N: 16-200366, WWN: 55CD2E40000AB69E, Model:
7337 SSDSC2BW180A3L 2.5&quot; 6Gb/s SATA SSD 180G 5V 1A, ASM P/N 0C38732, FRU
7338 P/N 45N8295, P0C38732.&lt;/p&gt;
7339
7340 &lt;p&gt;The only difference is in the first number (serial number?), ISN,
7341 SA, date and WNPP values. Mentioning all the details here in case
7342 someone is able to use the information to find a way to identify the
7343 failing disk among working ones (if any such working disk actually
7344 exist).&lt;/p&gt;
7345 </description>
7346 </item>
7347
7348 <item>
7349 <title>July 13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo</title>
7350 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</link>
7351 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html</guid>
7352 <pubDate>Tue, 9 Jul 2013 10:40:00 +0200</pubDate>
7353 <description>&lt;p&gt;The upcoming Saturday, 2013-07-13, we are organising a combined
7354 Debian Edu developer gathering and Debian and Ubuntu bug squashing
7355 party in Oslo. It is organised by &lt;a href=&quot;http://www.nuug.no/&quot;&gt;the
7356 member assosiation NUUG&lt;/a&gt; and
7357 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;the Debian Edu / Skolelinux
7358 project&lt;/a&gt; together with &lt;a href=&quot;http://bitraf.no/&quot;&gt;the hack space
7359 Bitraf&lt;/a&gt;.&lt;/p&gt;
7360
7361 &lt;p&gt;It starts 10:00 and continue until late evening. Everyone is
7362 welcome, and there is no fee to participate. There is on the other
7363 hand limited space, and only room for 30 people. Please put your name
7364 on &lt;a href=&quot;http://wiki.debian.org/BSP/2013/07/13/no/Oslo&quot;&gt;the event
7365 wiki page&lt;/a&gt; if you plan to join us.&lt;/p&gt;
7366 </description>
7367 </item>
7368
7369 <item>
7370 <title>The Thinkpad is dead, long live the Thinkpad X230?</title>
7371 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</link>
7372 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html</guid>
7373 <pubDate>Fri, 5 Jul 2013 08:30:00 +0200</pubDate>
7374 <description>&lt;p&gt;Half a year ago, I reported that I had to find a
7375 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html&quot;&gt;replacement
7376 for my trusty old Thinkpad X41&lt;/a&gt;. Unfortunately I did not have much
7377 time to spend on it, and it took a while to find a model I believe
7378 will do the job, but two days ago the replacement finally arrived. I
7379 ended up picking a
7380 &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad X230&lt;/a&gt;
7381 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
7382 a roaming workstation, and it seemed to work flawlessly. But my
7383 second installation with encrypted disk was not as successful. More
7384 on that below.&lt;/p&gt;
7385
7386 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
7387 important requirements (robust and with a good keyboard) are never
7388 listed in the feature list. But I did get good help from the search
7389 feature at &lt;a href=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
7390 allowed me to limit the list of interesting laptops based on my other
7391 requirements. A bit surprising that SSD disk are not disks according
7392 to that search interface, so I had to drop specifying the number of
7393 disks from my search parameters. I also asked around among friends to
7394 get their impression on keyboards and robustness.&lt;/p&gt;
7395
7396 &lt;p&gt;So the new laptop arrived, and it is quite a lot wider than the
7397 X41. I am not quite convinced about the keyboard, as it is
7398 significantly wider than my old keyboard, and I have to stretch my
7399 hand a lot more to reach the edges. But the key response is fairly
7400 good and the individual key shape is fairly easy to handle, so I hope
7401 I will get used to it. My old X40 was starting to fail, and I really
7402 needed a new laptop now. :)&lt;/p&gt;
7403
7404 &lt;p&gt;Turning off the touch pad was simple. All it took was a quick
7405 visit to the BIOS during boot it disable it.&lt;/p&gt;
7406
7407 &lt;p&gt;But there is a fatal problem with the laptop. The 180 GB SSD disk
7408 lock up during load. And this happen when installing Debian Wheezy
7409 with encrypted disk, while the disk is being filled with random data.
7410 I also tested to install Ubuntu Raring, and it happen there too if I
7411 reenable the code to fill the disk with random data (it is disabled by
7412 default in Ubuntu). And the bug with is already known. It was
7413 reported to Debian as &lt;a href=&quot;http://bugs.debian.org/691427&quot;&gt;BTS
7414 report #691427 2012-10-25&lt;/a&gt; (journal commit I/O error on brand-new
7415 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
7416 kernel developers as
7417 &lt;a href=&quot;https://bugzilla.kernel.org/show_bug.cgi?id=51861&quot;&gt;Kernel bugzilla
7418 report #51861 2012-12-20&lt;/a&gt; (Intel SSD 520 stops working under load
7419 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
7420 Lenovo forums, both for
7421 &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
7422 2012-11-10&lt;/a&gt; and for
7423 &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
7424 03-20-2013&lt;/a&gt;. The problem do not only affect installation. The
7425 reports state that the disk lock up during use if many writes are done
7426 on the disk, so it is much no use to work around the installation
7427 problem and end up with a computer that can lock up at any moment.
7428 There is even a
7429 &lt;a href=&quot;https://git.efficios.com/?p=test-ssd.git&quot;&gt;small C program
7430 available&lt;/a&gt; that will lock up the hard drive after running a few
7431 minutes by writing to a file.&lt;/p&gt;
7432
7433 &lt;p&gt;I&#39;ve contacted my supplier and asked how to handle this, and after
7434 contacting PCHELP Norway (request 01D1FDP) which handle support
7435 requests for Lenovo, his first suggestion was to upgrade the disk
7436 firmware. Unfortunately there is no newer firmware available from
7437 Lenovo, as my disk already have the most recent one (version LF1i). I
7438 hope to hear more from him today and hope the problem can be
7439 fixed. :)&lt;/p&gt;
7440 </description>
7441 </item>
7442
7443 <item>
7444 <title>The Thinkpad is dead, long live the Thinkpad X230</title>
7445 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</link>
7446 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html</guid>
7447 <pubDate>Thu, 4 Jul 2013 09:20:00 +0200</pubDate>
7448 <description>&lt;p&gt;Half a year ago, I reported that I had to find a replacement for my
7449 trusty old Thinkpad X41. Unfortunately I did not have much time to
7450 spend on it, but today the replacement finally arrived. I ended up
7451 picking a &lt;a href=&quot;http://www.linlap.com/lenovo_thinkpad_x230&quot;&gt;Thinkpad
7452 X230&lt;/a&gt; with SSD disk (NZDAJMN). I first test installed Debian Edu
7453 Wheezy as a roaming workstation, and it worked flawlessly. As I write
7454 this, it is installing what I hope will be a more final installation,
7455 with a encrypted hard drive to ensure any dope head stealing it end up
7456 with an expencive door stop.&lt;/p&gt;
7457
7458 &lt;p&gt;I had a hard time trying to track down a good laptop, as my most
7459 important requirements (robust and with a good keyboard) are never
7460 listed in the feature list. But I did get good help from the search
7461 feature at &lt;ahref=&quot;http://www.prisjakt.no/&quot;&gt;Prisjakt&lt;/a&gt;, which
7462 allowed me to limit the list of interesting laptops based on my other
7463 requirements. A bit surprising that SSD disk are not disks, so I had
7464 to drop number of disks from my search parameters.&lt;/p&gt;
7465
7466 &lt;p&gt;I am not quite convinced about the keyboard, as it is significantly
7467 wider than my old keyboard, and I have to stretch my hand a lot more
7468 to reach the edges. But the key response is fairly good and the
7469 individual key shape is fairly easy to handle, so I hope I will get
7470 used to it. My old X40 was starting to fail, and I really needed a
7471 new laptop now. :)&lt;/p&gt;
7472
7473 &lt;p&gt;I look forward to figuring out how to turn off the touch pad.&lt;/p&gt;
7474 </description>
7475 </item>
7476
7477 <item>
7478 <title>Automatically locate and install required firmware packages on Debian (Isenkram 0.4)</title>
7479 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</link>
7480 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html</guid>
7481 <pubDate>Tue, 25 Jun 2013 11:50:00 +0200</pubDate>
7482 <description>&lt;p&gt;It annoys me when the computer fail to do automatically what it is
7483 perfectly capable of, and I have to do it manually to get things
7484 working. One such task is to find out what firmware packages are
7485 needed to get the hardware on my computer working. Most often this
7486 affect the wifi card, but some times it even affect the RAID
7487 controller or the ethernet card. Today I pushed version 0.4 of the
7488 &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram package&lt;/a&gt;
7489 including a new script isenkram-autoinstall-firmware handling the
7490 process of asking all the loaded kernel modules what firmware files
7491 they want, find debian packages providing these files and install the
7492 debian packages. Here is a test run on my laptop:&lt;/p&gt;
7493
7494 &lt;p&gt;&lt;pre&gt;
7495 # isenkram-autoinstall-firmware
7496 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
7497 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
7498 info: locating packages with the requested firmware files
7499 info: Updating APT sources after adding non-free APT source
7500 info: trying to install firmware-ipw2x00
7501 firmware-ipw2x00
7502 firmware-ipw2x00
7503 Preconfiguring packages ...
7504 Selecting previously deselected package firmware-ipw2x00.
7505 (Reading database ... 259727 files and directories currently installed.)
7506 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
7507 Setting up firmware-ipw2x00 (0.28+squeeze1) ...
7508 #
7509 &lt;/pre&gt;&lt;/p&gt;
7510
7511 &lt;p&gt;When all the requested firmware is present, a simple message is
7512 printed instead:&lt;/p&gt;
7513
7514 &lt;p&gt;&lt;pre&gt;
7515 # isenkram-autoinstall-firmware
7516 info: did not find any firmware files requested by loaded kernel modules. exiting
7517 #
7518 &lt;/pre&gt;&lt;/p&gt;
7519
7520 &lt;p&gt;It could use some polish, but it is already working well and saving
7521 me some time when setting up new machines. :)&lt;/p&gt;
7522
7523 &lt;p&gt;So, how does it work? It look at the set of currently loaded
7524 kernel modules, and look up each one of them using modinfo, to find
7525 the firmware files listed in the module meta-information. Next, it
7526 download the Contents file from a nearby APT mirror, and search for
7527 the firmware files in this file to locate the package with the
7528 requested firmware file. If the package is in the non-free section, a
7529 non-free APT source is added and the package is installed using
7530 &lt;tt&gt;apt-get install&lt;/tt&gt;. The end result is a slightly better working
7531 machine.&lt;/p&gt;
7532
7533 &lt;p&gt;I hope someone find time to implement a more polished version of
7534 this script as part of the hw-detect debian-installer module, to
7535 finally fix &lt;a href=&quot;http://bugs.debian.org/655507&quot;&gt;BTS report
7536 #655507&lt;/a&gt;. There really is no need to insert USB sticks with
7537 firmware during a PXE install when the packages already are available
7538 from the nearby Debian mirror.&lt;/p&gt;
7539 </description>
7540 </item>
7541
7542 <item>
7543 <title>Fixing the Linux black screen of death on machines with Intel HD video</title>
7544 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</link>
7545 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html</guid>
7546 <pubDate>Tue, 11 Jun 2013 11:00:00 +0200</pubDate>
7547 <description>&lt;p&gt;When installing RedHat, Fedora, Debian and Ubuntu on some machines,
7548 the screen just turn black when Linux boot, either during installation
7549 or on first boot from the hard disk. I&#39;ve seen it once in a while the
7550 last few years, but only recently understood the cause. I&#39;ve seen it
7551 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
7552 The reason seem to be in the wiring of some laptops. The system to
7553 control the screen background light is inverted, so when Linux try to
7554 turn the brightness fully on, it end up turning it off instead. I do
7555 not know which Linux drivers are affected, but this post is about the
7556 i915 driver used by the
7557 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
7558 EasyNote LV&lt;/a&gt;, Thinkpad X40 and many other laptops.&lt;/p&gt;
7559
7560 &lt;p&gt;The problem can be worked around two ways. Either by adding
7561 i915.invert_brightness=1 as a kernel option, or by adding a file in
7562 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=1
7563 option when it load the i915 kernel module. On Debian and Ubuntu, it
7564 can be done by running these commands as root:&lt;/p&gt;
7565
7566 &lt;pre&gt;
7567 echo options i915 invert_brightness=1 | tee /etc/modprobe.d/i915.conf
7568 update-initramfs -u -k all
7569 &lt;/pre&gt;
7570
7571 &lt;p&gt;Since March 2012 there is
7572 &lt;a href=&quot;http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955&quot;&gt;a
7573 mechanism in the Linux kernel&lt;/a&gt; to tell the i915 driver which
7574 hardware have this problem, and get the driver to invert the
7575 brightness setting automatically. To use it, one need to add a row in
7576 &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
7577 intel_quirks array&lt;/a&gt; in the driver source
7578 &lt;tt&gt;drivers/gpu/drm/i915/intel_display.c&lt;/tt&gt; (look for &quot;&lt;tt&gt;static
7579 struct intel_quirk intel_quirks&lt;/tt&gt;&quot;), specifying the PCI device
7580 number (vendor number 8086 is assumed) and subdevice vendor and device
7581 number.&lt;/p&gt;
7582
7583 &lt;p&gt;My Packard Bell EasyNote LV got this output from &lt;tt&gt;lspci
7584 -vvnn&lt;/tt&gt; for the video card in question:&lt;/p&gt;
7585
7586 &lt;p&gt;&lt;pre&gt;
7587 00:02.0 VGA compatible controller [0300]: Intel Corporation \
7588 3rd Gen Core processor Graphics Controller [8086:0156] \
7589 (rev 09) (prog-if 00 [VGA controller])
7590 Subsystem: Acer Incorporated [ALI] Device [1025:0688]
7591 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
7592 ParErr- Stepping- SE RR- FastB2B- DisINTx+
7593 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast &gt;TAbort- \
7594 &lt;TAbort- &lt;MAbort-&gt;SERR- &lt;PERR- INTx-
7595 Latency: 0
7596 Interrupt: pin A routed to IRQ 42
7597 Region 0: Memory at c2000000 (64-bit, non-prefetchable) [size=4M]
7598 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
7599 Region 4: I/O ports at 4000 [size=64]
7600 Expansion ROM at &lt;unassigned&gt; [disabled]
7601 Capabilities: &lt;access denied&gt;
7602 Kernel driver in use: i915
7603 &lt;/pre&gt;&lt;/p&gt;
7604
7605 &lt;p&gt;The resulting intel_quirks entry would then look like this:&lt;/p&gt;
7606
7607 &lt;p&gt;&lt;pre&gt;
7608 struct intel_quirk intel_quirks[] = {
7609 ...
7610 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
7611 { 0x0156, 0x1025, 0x0688, quirk_invert_brightness },
7612 ...
7613 }
7614 &lt;/pre&gt;&lt;/p&gt;
7615
7616 &lt;p&gt;According to the kernel module instructions (as seen using
7617 &lt;tt&gt;modinfo i915&lt;/tt&gt;), information about hardware needing the
7618 invert_brightness flag should be sent to the
7619 &lt;a href=&quot;http://lists.freedesktop.org/mailman/listinfo/dri-devel&quot;&gt;dri-devel
7620 (at) lists.freedesktop.org&lt;/a&gt; mailing list to reach the kernel
7621 developers. But my email about the laptop sent 2013-06-03 have not
7622 yet shown up in
7623 &lt;a href=&quot;http://lists.freedesktop.org/archives/dri-devel/2013-June/thread.html&quot;&gt;the
7624 web archive for the mailing list&lt;/a&gt;, so I suspect they do not accept
7625 emails from non-subscribers. Because of this, I sent my patch also to
7626 the Debian bug tracking system instead as
7627 &lt;a href=&quot;http://bugs.debian.org/710938&quot;&gt;BTS report #710938&lt;/a&gt;, to make
7628 sure the patch is not lost.&lt;/p&gt;
7629
7630 &lt;p&gt;Unfortunately, it is not enough to fix the kernel to get Laptops
7631 with this problem working properly with Linux. If you use Gnome, your
7632 worries should be over at this point. But if you use KDE, there is
7633 something in KDE ignoring the invert_brightness setting and turning on
7634 the screen during login. I&#39;ve reported it to Debian as
7635 &lt;a href=&quot;http://bugs.debian.org/711237&quot;&gt;BTS report #711237&lt;/a&gt;, and
7636 have no idea yet how to figure out exactly what subsystem is doing
7637 this. Perhaps you can help? Perhaps you know what the Gnome
7638 developers did to handle this, and this can give a clue to the KDE
7639 developers? Or you know where in KDE the screen brightness is changed
7640 during login? If so, please update the BTS report (or get in touch if
7641 you do not know how to update BTS).&lt;/p&gt;
7642
7643 &lt;p&gt;Update 2013-07-19: The correct fix for this machine seem to be
7644 acpi_backlight=vendor, to disable ACPI backlight support completely,
7645 as the ACPI information on the machine is trash and it is better to
7646 leave it to the intel video driver to control the screen
7647 backlight.&lt;/p&gt;
7648 </description>
7649 </item>
7650
7651 <item>
7652 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows 8</title>
7653 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html</link>
7654 <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>
7655 <pubDate>Mon, 27 May 2013 15:20:00 +0200</pubDate>
7656 <description>&lt;p&gt;Two days ago, I asked
7657 &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
7658 I could install Linux on a Packard Bell EasyNote LV computer
7659 preinstalled with Windows 8&lt;/a&gt;. I found a solution, but am horrified
7660 with the obstacles put in the way of Linux users on a laptop with UEFI
7661 and Windows 8.&lt;/p&gt;
7662
7663 &lt;p&gt;I never found out if the cause of my problems were the use of UEFI
7664 secure booting or fast boot. I suspect fast boot was the problem,
7665 causing the firmware to boot directly from HD without considering any
7666 key presses and alternative devices, but do not know UEFI settings
7667 enough to tell.&lt;/p&gt;
7668
7669 &lt;p&gt;There is no way to install Linux on the machine in question without
7670 opening the box and disconnecting the hard drive! This is as far as I
7671 can tell, the only way to get access to the firmware setup menu
7672 without accepting the Windows 8 license agreement. I am told (and
7673 found description on how to) that it is possible to configure the
7674 firmware setup once booted into Windows 8. But as I believe the terms
7675 of that agreement are completely unacceptable, accepting the license
7676 was never an alternative. I do not enter agreements I do not intend
7677 to follow.&lt;/p&gt;
7678
7679 &lt;p&gt;I feared I had to return the laptops and ask for a refund, and
7680 waste many hours on this, but luckily there was a way to get it to
7681 work. But I would not recommend it to anyone planning to run Linux on
7682 it, and I have become sceptical to Windows 8 certified laptops. Is
7683 this the way Linux will be forced out of the market place, by making
7684 it close to impossible for &quot;normal&quot; users to install Linux without
7685 accepting the Microsoft Windows license terms? Or at least not
7686 without risking to loose the warranty?&lt;/p&gt;
7687
7688 &lt;p&gt;I&#39;ve updated the
7689 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Linux Laptop
7690 wiki page for Packard Bell EasyNote LV&lt;/a&gt;, to ensure the next person
7691 do not have to struggle as much as I did to get Linux into the
7692 machine.&lt;/p&gt;
7693
7694 &lt;p&gt;Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
7695 Michael Tokarev and others for feedback and ideas.&lt;/p&gt;
7696 </description>
7697 </item>
7698
7699 <item>
7700 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows 8?</title>
7701 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html</link>
7702 <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>
7703 <pubDate>Sat, 25 May 2013 18:20:00 +0200</pubDate>
7704 <description>&lt;p&gt;I&#39;ve run into quite a problem the last few days. I bought three
7705 new laptops for my parents and a few others. I bought Packard Bell
7706 Easynote LV to run Kubuntu on and use as their home computer. But I
7707 am completely unable to figure out how to install Linux on it. The
7708 computer is preinstalled with Windows 8, and I suspect it uses UEFI
7709 instead of a BIOS to boot.&lt;/p&gt;
7710
7711 &lt;p&gt;The problem is that I am unable to get it to PXE boot, and unable
7712 to get it to boot the Linux installer from my USB stick. I have yet
7713 to try the DVD install, and still hope it will work. when I turn on
7714 the computer, there is no information on what buttons to press to get
7715 the normal boot menu. I expect to get some boot menu to select PXE or
7716 USB stick booting. When booting, it first ask for the language to
7717 use, then for some regional settings, and finally if I will accept the
7718 Windows 8 terms of use. As these terms are completely unacceptable to
7719 me, I have no other choice but to turn off the computer and try again
7720 to get it to boot the Linux installer.&lt;/p&gt;
7721
7722 &lt;p&gt;I have gathered my findings so far on a Linlap page about the
7723 &lt;a href=&quot;http://www.linlap.com/packard_bell_easynote_lv&quot;&gt;Packard Bell
7724 EasyNote LV&lt;/a&gt; model. If you have any idea how to get Linux
7725 installed on this machine, please get in touch or update that wiki
7726 page. If I can&#39;t find a way to install Linux, I will have to return
7727 the laptop to the seller and find another machine for my parents.&lt;/p&gt;
7728
7729 &lt;p&gt;I wonder, is this the way Linux will be forced out of the market
7730 using UEFI and &quot;secure boot&quot; by making it impossible to install Linux
7731 on new Laptops?&lt;/p&gt;
7732 </description>
7733 </item>
7734
7735 <item>
7736 <title>How to transform a Debian based system to a Debian Edu installation</title>
7737 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</link>
7738 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html</guid>
7739 <pubDate>Fri, 17 May 2013 11:50:00 +0200</pubDate>
7740 <description>&lt;p&gt;&lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu / Skolelinux&lt;/a&gt; is
7741 an operating system based on Debian intended for use in schools. It
7742 contain a turn-key solution for the computer network provided to
7743 pupils in the primary schools. It provide both the central server,
7744 network boot servers and desktop environments with heaps of
7745 educational software. The project was founded almost 12 years ago,
7746 2001-07-02. If you want to support the project, which is in need for
7747 cash to fund developer gatherings and other project related activity,
7748 &lt;a href=&quot;http://www.linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;please
7749 donate some money&lt;/a&gt;.
7750
7751 &lt;p&gt;A topic that come up again and again on the Debian Edu mailing
7752 lists and elsewhere, is the question on how to transform a Debian or
7753 Ubuntu installation into a Debian Edu installation. It isn&#39;t very
7754 hard, and last week I wrote a script to replicate the steps done by
7755 the Debian Edu installer.&lt;/p&gt;
7756
7757 &lt;p&gt;The script,
7758 &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;
7759 in the debian-edu-config package, will go through these six steps and
7760 transform an existing Debian Wheezy or Ubuntu (untested) installation
7761 into a Debian Edu Workstation:&lt;/p&gt;
7762
7763 &lt;ol&gt;
7764
7765 &lt;li&gt;Add skolelinux related APT sources.&lt;/li&gt;
7766 &lt;li&gt;Create /etc/debian-edu/config with the wanted configuration.&lt;/li&gt;
7767 &lt;li&gt;Install debian-edu-install to load preseeding values and pull in
7768 our configuration.&lt;/li&gt;
7769 &lt;li&gt;Preseed debconf database with profile setup in
7770 /etc/debian-edu/config, and run tasksel to install packages
7771 according to the profile specified in the config above,
7772 overriding some of the Debian automation machinery.&lt;/li&gt;
7773 &lt;li&gt;Run debian-edu-cfengine-D installation to configure everything
7774 that could not be done using preseeding.&lt;/li&gt;
7775 &lt;li&gt;Ask for a reboot to enable all the configuration changes.&lt;/li&gt;
7776
7777 &lt;/ol&gt;
7778
7779 &lt;p&gt;There are some steps in the Debian Edu installation that can not be
7780 replicated like this. Disk partitioning and LVM setup, for example.
7781 So this script just assume there is enough disk space to install all
7782 the needed packages.&lt;/p&gt;
7783
7784 &lt;p&gt;The script was created to help a Debian Edu student working on
7785 setting up &lt;a href=&quot;http://www.raspberrypi.org&quot;&gt;Raspberry Pi&lt;/a&gt; as a
7786 Debian Edu client, and using it he can take the existing
7787 &lt;a href=&quot;http://www.raspbian.org/FrontPage‎&quot;&gt;Raspbian&lt;/a&gt; installation and
7788 transform it into a fully functioning Debian Edu Workstation (or
7789 Roaming Workstation, or whatever :).&lt;/p&gt;
7790
7791 &lt;p&gt;The default setting in the script is to create a KDE Workstation.
7792 If a LXDE based Roaming workstation is wanted instead, modify the
7793 PROFILE and DESKTOP values at the top to look like this instead:&lt;/p&gt;
7794
7795 &lt;p&gt;&lt;pre&gt;
7796 PROFILE=&quot;Roaming-Workstation&quot;
7797 DESKTOP=&quot;lxde&quot;
7798 &lt;/pre&gt;&lt;/p&gt;
7799
7800 &lt;p&gt;The script could even become useful to set up Debian Edu servers in
7801 the cloud, by starting with a virtual Debian installation at some
7802 virtual hosting service and setting up all the services on first
7803 boot.&lt;/p&gt;
7804 </description>
7805 </item>
7806
7807 <item>
7808 <title>Debian, the Linux distribution of choice for LEGO designers?</title>
7809 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</link>
7810 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html</guid>
7811 <pubDate>Sat, 11 May 2013 20:30:00 +0200</pubDate>
7812 <description>&lt;P&gt;In January,
7813 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html&quot;&gt;I
7814 announced a&lt;/a&gt; new &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;IRC
7815 channel #debian-lego&lt;/a&gt;, for those of us in the Debian and Linux
7816 community interested in &lt;a href=&quot;http://www.lego.com/&quot;&gt;LEGO&lt;/a&gt;, the
7817 marvellous construction system from Denmark. We also created
7818 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;a wiki page&lt;/a&gt; to have
7819 a place to take notes and write down our plans and hopes. And several
7820 people showed up to help. I was very happy to see the effect of my
7821 call. Since the small start, we have a debtags tag
7822 &lt;a href=&quot;http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego&quot;&gt;hardware::hobby:lego&lt;/a&gt;
7823 tag for LEGO related packages, and now count 10 packages related to
7824 LEGO and &lt;a href=&quot;http://mindstorms.lego.com/&quot;&gt;Mindstorms&lt;/a&gt;:&lt;/p&gt;
7825
7826 &lt;p&gt;&lt;table&gt;
7827 &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;
7828 &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;
7829 &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;
7830 &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;
7831 &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;
7832 &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;
7833 &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;
7834 &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;
7835 &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;
7836 &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;
7837 &lt;/table&gt;&lt;/p&gt;
7838
7839 &lt;p&gt;Some of these are available in Wheezy, and all but one are
7840 currently available in Jessie/testing. leocad is so far only
7841 available in experimental.&lt;/p&gt;
7842
7843 &lt;p&gt;If you care about LEGO in Debian, please join us on IRC and help
7844 adding the rest of the great free software tools available on Linux
7845 for LEGO designers.&lt;/p&gt;
7846 </description>
7847 </item>
7848
7849 <item>
7850 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy</title>
7851 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</link>
7852 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html</guid>
7853 <pubDate>Sun, 5 May 2013 07:40:00 +0200</pubDate>
7854 <description>&lt;p&gt;When I woke up this morning, I was very happy to see that the
7855 &lt;a href=&quot;http://www.debian.org/News/2013/20130504&quot;&gt;release announcement
7856 for Debian Wheezy&lt;/a&gt; was waiting in my mail box. This is a great
7857 Debian release, and I expect to move my machines at home over to it fairly
7858 soon.&lt;/p&gt;
7859
7860 &lt;p&gt;The new debian release contain heaps of new stuff, and one program
7861 in particular make me very happy to see included. The
7862 &lt;a href=&quot;http://scratch.mit.edu/&quot;&gt;Scratch&lt;/a&gt; program, made famous by
7863 the &lt;a href=&quot;http://www.code.org/&quot;&gt;Teach kids code&lt;/a&gt; movement, is
7864 included for the first time. Alongside similar programs like
7865 &lt;a href=&quot;http://edu.kde.org/kturtle/&quot;&gt;kturtle&lt;/a&gt; and
7866 &lt;a href=&quot;http://wiki.sugarlabs.org/go/Activities/Turtle_Art&quot;&gt;turtleart&lt;/a&gt;,
7867 it allow for visual programming where syntax errors can not happen,
7868 and a friendly programming environment for learning to control the
7869 computer. Scratch will also be included in the next release of Debian
7870 Edu.&lt;/a&gt;
7871
7872 &lt;p&gt;And now that Wheezy is wrapped up, we can wrap up the next Debian
7873 Edu/Skolelinux release too. The
7874 &lt;a href=&quot;http://lists.debian.org/debian-edu/2013/04/msg00132.html&quot;&gt;first
7875 alpha release&lt;/a&gt; went out last week, and the next should soon
7876 follow.&lt;p&gt;
7877 </description>
7878 </item>
7879
7880 <item>
7881 <title>Isenkram 0.2 finally in the Debian archive</title>
7882 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</link>
7883 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html</guid>
7884 <pubDate>Wed, 3 Apr 2013 23:40:00 +0200</pubDate>
7885 <description>&lt;p&gt;Today the &lt;a href=&quot;http://packages.qa.debian.org/isenkram&quot;&gt;Isenkram
7886 package&lt;/a&gt; finally made it into the archive, after lingering in NEW
7887 for many months. I uploaded it to the Debian experimental suite
7888 2013-01-27, and today it was accepted into the archive.&lt;/p&gt;
7889
7890 &lt;p&gt;Isenkram is a system for suggesting to users what packages to
7891 install to work with a pluggable hardware device. The suggestion pop
7892 up when the device is plugged in. For example if a Lego Mindstorm NXT
7893 is inserted, it will suggest to install the program needed to program
7894 the NXT controller. Give it a go, and report bugs and suggestions to
7895 BTS. :)&lt;/p&gt;
7896 </description>
7897 </item>
7898
7899 <item>
7900 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)</title>
7901 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</link>
7902 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html</guid>
7903 <pubDate>Sat, 2 Feb 2013 09:00:00 +0100</pubDate>
7904 <description>&lt;p&gt;My
7905 &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
7906 bitcoin related blog post&lt;/a&gt; mentioned that the new
7907 &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin package&lt;/a&gt; for
7908 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
7909 2013-01-19, and have been available in unstable since then. It was
7910 automatically copied to Ubuntu, and is available in their Raring
7911 version too.&lt;/p&gt;
7912
7913 &lt;p&gt;But there is a strange problem with the build that block this new
7914 version from being available on the i386 and kfreebsd-i386
7915 architectures. For some strange reason, the autobuilders in Debian
7916 for these architectures fail to run the test suite on these
7917 architectures (&lt;a href=&quot;http://bugs.debian.org/672524&quot;&gt;BTS #672524&lt;/a&gt;).
7918 We are so far unable to reproduce it when building it manually, and
7919 no-one have been able to propose a fix. If you got an idea what is
7920 failing, please let us know via the BTS.&lt;/p&gt;
7921
7922 &lt;p&gt;One feature that is annoying me with of the bitcoin client, because
7923 I often run low on disk space, is the fact that the client will exit
7924 if it run short on space (&lt;a href=&quot;http://bugs.debian.org/696715&quot;&gt;BTS
7925 #696715&lt;/a&gt;). So make sure you have enough disk space when you run
7926 it. :)&lt;/p&gt;
7927
7928 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
7929 activities, please send Bitcoin donations to my address
7930 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
7931 </description>
7932 </item>
7933
7934 <item>
7935 <title>Welcome to the world, Isenkram!</title>
7936 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</link>
7937 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html</guid>
7938 <pubDate>Tue, 22 Jan 2013 22:00:00 +0100</pubDate>
7939 <description>&lt;p&gt;Yesterday, I
7940 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html&quot;&gt;asked
7941 for testers&lt;/a&gt; for my prototype for making Debian better at handling
7942 pluggable hardware devices, which I
7943 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;set
7944 out to create&lt;/a&gt; earlier this month. Several valuable testers showed
7945 up, and caused me to really want to to open up the development to more
7946 people. But before I did this, I want to come up with a sensible name
7947 for this project. Today I finally decided on a new name, and I have
7948 renamed the project from hw-support-handler to this new name. In the
7949 process, I moved the source to git and made it available as a
7950 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git&quot;&gt;collab-maint&lt;/a&gt;
7951 repository in Debian. The new name? It is &lt;strong&gt;Isenkram&lt;/strong&gt;.
7952 To fetch and build the latest version of the source, use&lt;/p&gt;
7953
7954 &lt;pre&gt;
7955 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
7956 cd isenkram &amp;&amp; git-buildpackage -us -uc
7957 &lt;/pre&gt;
7958
7959 &lt;p&gt;I have not yet adjusted all files to use the new name yet. If you
7960 want to hack on the source or improve the package, please go ahead.
7961 But please talk to me first on IRC or via email before you do major
7962 changes, to make sure we do not step on each others toes. :)&lt;/p&gt;
7963
7964 &lt;p&gt;If you wonder what &#39;isenkram&#39; is, it is a Norwegian word for iron
7965 stuff, typically meaning tools, nails, screws, etc. Typical hardware
7966 stuff, in other words. I&#39;ve been told it is the Norwegian variant of
7967 the German word eisenkram, for those that are familiar with that
7968 word.&lt;/p&gt;
7969
7970 &lt;p&gt;&lt;strong&gt;Update 2013-01-26&lt;/strong&gt;: Added -us -us to build
7971 instructions, to avoid confusing people with an error from the signing
7972 process.&lt;/p&gt;
7973
7974 &lt;p&gt;&lt;strong&gt;Update 2013-01-27&lt;/strong&gt;: Switch to HTTP URL for the git
7975 clone argument to avoid the need for authentication.&lt;/p&gt;
7976 </description>
7977 </item>
7978
7979 <item>
7980 <title>First prototype ready making hardware easier to use in Debian</title>
7981 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</link>
7982 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html</guid>
7983 <pubDate>Mon, 21 Jan 2013 12:00:00 +0100</pubDate>
7984 <description>&lt;p&gt;Early this month I set out to try to
7985 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;improve
7986 the Debian support for pluggable hardware devices&lt;/a&gt;. Now my
7987 prototype is working, and it is ready for a larger audience. To test
7988 it, fetch the
7989 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;source
7990 from the Debian Edu subversion repository&lt;/a&gt;, build and install the
7991 package. You might have to log out and in again activate the
7992 autostart script.&lt;/p&gt;
7993
7994 &lt;p&gt;The design is simple:&lt;/p&gt;
7995
7996 &lt;ul&gt;
7997
7998 &lt;li&gt;Add desktop entry in /usr/share/autostart/ causing a program
7999 hw-support-handlerd to start when the user log in.&lt;/li&gt;
8000
8001 &lt;li&gt;This program listen for kernel events about new hardware (directly
8002 from the kernel like udev does), not using HAL dbus events as I
8003 initially did.&lt;/li&gt;
8004
8005 &lt;li&gt;When new hardware is inserted, look up the hardware modalias in
8006 the APT database, a database
8007 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup&quot;&gt;available
8008 via HTTP&lt;/a&gt; and a database available as part of the package.&lt;/li&gt;
8009
8010 &lt;li&gt;If a package is mapped to the hardware in question, the package
8011 isn&#39;t installed yet and this is the first time the hardware was
8012 plugged in, show a desktop notification suggesting to install the
8013 package or packages.&lt;/li&gt;
8014
8015 &lt;li&gt;If the user click on the &#39;install package now&#39; button, ask
8016 aptdaemon via the PackageKit API to install the requrired package.&lt;/li&gt;
8017
8018 &lt;li&gt;aptdaemon ask for root password or sudo password, and install the
8019 package while showing progress information in a window.&lt;/li&gt;
8020
8021 &lt;/ul&gt;
8022
8023 &lt;p&gt;I still need to come up with a better name for the system. Here
8024 are some screen shots showing the prototype in action. First the
8025 notification, then the password request, and finally the request to
8026 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.&lt;/p&gt;
8027
8028 &lt;p&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-1-notification.png&quot;&gt;
8029 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-2-password.png&quot;&gt;
8030 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-3-dependencies.png&quot;&gt;
8031 &lt;br&gt;&lt;img src=&quot;http://people.skolelinux.org/pere/blog/images/2013-01-21-hw-support-4-installing.png&quot;&gt;
8032 &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;
8033
8034 &lt;p&gt;The prototype still need to be improved with longer timeouts, but
8035 is already useful. The database of hardware to package mappings also
8036 need more work. It is currently compatible with the Ubuntu way of
8037 storing such information in the package control file, but could be
8038 changed to use other formats instead or in addition to the current
8039 method. I&#39;ve dropped the use of discover for this mapping, as the
8040 modalias approach is more flexible and easier to use on Linux as long
8041 as the Linux kernel expose its modalias strings directly.&lt;/p&gt;
8042
8043 &lt;p&gt;&lt;strong&gt;Update 2013-01-21 16:50&lt;/strong&gt;: Due to popular demand,
8044 here is the command required to check out and build the source: Use
8045 &#39;&lt;tt&gt;svn checkout
8046 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8047 hw-support-handler; debuild&lt;/tt&gt;&#39;. If you lack debuild, install the
8048 devscripts package.&lt;/p&gt;
8049
8050 &lt;p&gt;&lt;strong&gt;Update 2013-01-23 12:00&lt;/strong&gt;: The project is now
8051 renamed to Isenkram and the source moved from the Debian Edu
8052 subversion repository to a Debian collab-maint git repository. See
8053 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html&quot;&gt;build
8054 instructions&lt;/a&gt; for details.&lt;/p&gt;
8055 </description>
8056 </item>
8057
8058 <item>
8059 <title>Thank you Thinkpad X41, for your long and trustworthy service</title>
8060 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</link>
8061 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html</guid>
8062 <pubDate>Sat, 19 Jan 2013 09:20:00 +0100</pubDate>
8063 <description>&lt;p&gt;This Christmas my trusty old laptop died. It died quietly and
8064 suddenly in bed. With a quiet whimper, it went completely quiet and
8065 black. The power button was no longer able to turn it on. It was a
8066 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8067 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8068 Compaq I had before that. Now I need to find a replacement. To keep
8069 going during Christmas, I moved the one year old SSD disk to my old
8070 X40 where it fitted (only one I had left that could use it), but it is
8071 not a durable solution.
8072
8073 &lt;p&gt;My laptop needs are fairly modest. This is my wishlist from when I
8074 got a new one more than 10 years ago. It still holds true.:)&lt;/p&gt;
8075
8076 &lt;ul&gt;
8077
8078 &lt;li&gt;Lightweight (around 1 kg) and small volume (preferably smaller
8079 than A4).&lt;/li&gt;
8080 &lt;li&gt;Robust, it will be in my backpack every day.&lt;/li&gt;
8081 &lt;li&gt;Three button mouse and a mouse pin instead of touch pad.&lt;/li&gt;
8082 &lt;li&gt;Long battery life time. Preferable a week.&lt;/li&gt;
8083 &lt;li&gt;Internal WIFI network card.&lt;/li&gt;
8084 &lt;li&gt;Internal Twisted Pair network card.&lt;/li&gt;
8085 &lt;li&gt;Some USB slots (2-3 is plenty)&lt;/li&gt;
8086 &lt;li&gt;Good keyboard - similar to the Thinkpad.&lt;/li&gt;
8087 &lt;li&gt;Video resolution at least 1024x768, with size around 12&quot; (A4 paper
8088 size).&lt;/li&gt;
8089 &lt;li&gt;Hardware supported by Debian Stable, ie the default kernel and
8090 X.org packages.&lt;/li&gt;
8091 &lt;li&gt;Quiet, preferably fan free (or at least not using the fan most of
8092 the time).
8093
8094 &lt;/ul&gt;
8095
8096 &lt;p&gt;You will notice that there are no RAM and CPU requirements in the
8097 list. The reason is simply that the specifications on laptops the
8098 last 10-15 years have been sufficient for my needs, and I have to look
8099 at other features to choose my laptop. But are there still made as
8100 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8101 robust, and Thinkpads seem to be heading in the wrong direction since
8102 Lenovo took over. But I&#39;ve been told that X220 and X1 Carbon might
8103 still be useful.&lt;/p&gt;
8104
8105 &lt;p&gt;Perhaps I should rethink my needs, and look for a pad with an
8106 external keyboard? I&#39;ll have to check the
8107 &lt;a href=&quot;http://www.linux-laptop.net/&quot;&gt;Linux Laptops site&lt;/a&gt; for
8108 well-supported laptops, or perhaps just buy one preinstalled from one
8109 of the vendors listed on the &lt;a href=&quot;http://linuxpreloaded.com/&quot;&gt;Linux
8110 Pre-loaded site&lt;/a&gt;.&lt;/p&gt;
8111 </description>
8112 </item>
8113
8114 <item>
8115 <title>How to find a browser plugin supporting a given MIME type</title>
8116 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</link>
8117 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html</guid>
8118 <pubDate>Fri, 18 Jan 2013 10:40:00 +0100</pubDate>
8119 <description>&lt;p&gt;Some times I try to figure out which Iceweasel browser plugin to
8120 install to get support for a given MIME type. Thanks to
8121 &lt;a href=&quot;https://wiki.ubuntu.com/MozillaTeam/Plugins&quot;&gt;specifications
8122 done by Ubuntu&lt;/a&gt; and Mozilla, it is possible to do this in Debian.
8123 Unfortunately, not very many packages provide the needed meta
8124 information, Anyway, here is a small script to look up all browser
8125 plugin packages announcing ther MIME support using this specification:&lt;/p&gt;
8126
8127 &lt;pre&gt;
8128 #!/usr/bin/python
8129 import sys
8130 import apt
8131 def pkgs_handling_mimetype(mimetype):
8132 cache = apt.Cache()
8133 cache.open(None)
8134 thepkgs = []
8135 for pkg in cache:
8136 version = pkg.candidate
8137 if version is None:
8138 version = pkg.installed
8139 if version is None:
8140 continue
8141 record = version.record
8142 if not record.has_key(&#39;Npp-MimeType&#39;):
8143 continue
8144 mime_types = record[&#39;Npp-MimeType&#39;].split(&#39;,&#39;)
8145 for t in mime_types:
8146 t = t.rstrip().strip()
8147 if t == mimetype:
8148 thepkgs.append(pkg.name)
8149 return thepkgs
8150 mimetype = &quot;audio/ogg&quot;
8151 if 1 &lt; len(sys.argv):
8152 mimetype = sys.argv[1]
8153 print &quot;Browser plugin packages supporting %s:&quot; % mimetype
8154 for pkg in pkgs_handling_mimetype(mimetype):
8155 print &quot; %s&quot; %pkg
8156 &lt;/pre&gt;
8157
8158 &lt;p&gt;It can be used like this to look up a given MIME type:&lt;/p&gt;
8159
8160 &lt;pre&gt;
8161 % ./apt-find-browserplug-for-mimetype
8162 Browser plugin packages supporting audio/ogg:
8163 gecko-mediaplayer
8164 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
8165 Browser plugin packages supporting application/x-shockwave-flash:
8166 browser-plugin-gnash
8167 %
8168 &lt;/pre&gt;
8169
8170 &lt;p&gt;In Ubuntu this mechanism is combined with support in the browser
8171 itself to query for plugins and propose to install the needed
8172 packages. It would be great if Debian supported such feature too. Is
8173 anyone working on adding it?&lt;/p&gt;
8174
8175 &lt;p&gt;&lt;strong&gt;Update 2013-01-18 14:20&lt;/strong&gt;: The Debian BTS
8176 request for icweasel support for this feature is
8177 &lt;a href=&quot;http://bugs.debian.org/484010&quot;&gt;#484010&lt;/a&gt; from 2008 (and
8178 &lt;a href=&quot;http://bugs.debian.org/698426&quot;&gt;#698426&lt;/a&gt; from today). Lack
8179 of manpower and wish for a different design is the reason thus feature
8180 is not yet in iceweasel from Debian.&lt;/p&gt;
8181 </description>
8182 </item>
8183
8184 <item>
8185 <title>What is the most supported MIME type in Debian?</title>
8186 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</link>
8187 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html</guid>
8188 <pubDate>Wed, 16 Jan 2013 10:10:00 +0100</pubDate>
8189 <description>&lt;p&gt;The &lt;a href=&quot;http://wiki.debian.org/AppStreamDebianProposal&quot;&gt;DEP-11
8190 proposal to add AppStream information to the Debian archive&lt;/a&gt;, is a
8191 proposal to make it possible for a Desktop application to propose to
8192 the user some package to install to gain support for a given MIME
8193 type, font, library etc. that is currently missing. With such
8194 mechanism in place, it would be possible for the desktop to
8195 automatically propose and install leocad if some LDraw file is
8196 downloaded by the browser.&lt;/p&gt;
8197
8198 &lt;p&gt;To get some idea about the current content of the archive, I decided
8199 to write a simple program to extract all .desktop files from the
8200 Debian archive and look up the claimed MIME support there. The result
8201 can be found on the
8202 &lt;a href=&quot;http://ftp.skolelinux.org/pub/AppStreamTest&quot;&gt;Skolelinux FTP
8203 site&lt;/a&gt;. Using the collected information, it become possible to
8204 answer the question in the title. Here are the 20 most supported MIME
8205 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
8206 The complete list is available from the link above.&lt;/p&gt;
8207
8208 &lt;p&gt;&lt;strong&gt;Debian Stable:&lt;/strong&gt;&lt;/p&gt;
8209
8210 &lt;pre&gt;
8211 count MIME type
8212 ----- -----------------------
8213 32 text/plain
8214 30 audio/mpeg
8215 29 image/png
8216 28 image/jpeg
8217 27 application/ogg
8218 26 audio/x-mp3
8219 25 image/tiff
8220 25 image/gif
8221 22 image/bmp
8222 22 audio/x-wav
8223 20 audio/x-flac
8224 19 audio/x-mpegurl
8225 18 video/x-ms-asf
8226 18 audio/x-musepack
8227 18 audio/x-mpeg
8228 18 application/x-ogg
8229 17 video/mpeg
8230 17 audio/x-scpls
8231 17 audio/ogg
8232 16 video/x-ms-wmv
8233 &lt;/pre&gt;
8234
8235 &lt;p&gt;&lt;strong&gt;Debian Testing:&lt;/strong&gt;&lt;/p&gt;
8236
8237 &lt;pre&gt;
8238 count MIME type
8239 ----- -----------------------
8240 33 text/plain
8241 32 image/png
8242 32 image/jpeg
8243 29 audio/mpeg
8244 27 image/gif
8245 26 image/tiff
8246 26 application/ogg
8247 25 audio/x-mp3
8248 22 image/bmp
8249 21 audio/x-wav
8250 19 audio/x-mpegurl
8251 19 audio/x-mpeg
8252 18 video/mpeg
8253 18 audio/x-scpls
8254 18 audio/x-flac
8255 18 application/x-ogg
8256 17 video/x-ms-asf
8257 17 text/html
8258 17 audio/x-musepack
8259 16 image/x-xbitmap
8260 &lt;/pre&gt;
8261
8262 &lt;p&gt;&lt;strong&gt;Debian Unstable:&lt;/strong&gt;&lt;/p&gt;
8263
8264 &lt;pre&gt;
8265 count MIME type
8266 ----- -----------------------
8267 31 text/plain
8268 31 image/png
8269 31 image/jpeg
8270 29 audio/mpeg
8271 28 application/ogg
8272 27 image/gif
8273 26 image/tiff
8274 26 audio/x-mp3
8275 23 audio/x-wav
8276 22 image/bmp
8277 21 audio/x-flac
8278 20 audio/x-mpegurl
8279 19 audio/x-mpeg
8280 18 video/x-ms-asf
8281 18 video/mpeg
8282 18 audio/x-scpls
8283 18 application/x-ogg
8284 17 audio/x-musepack
8285 16 video/x-ms-wmv
8286 16 video/x-msvideo
8287 &lt;/pre&gt;
8288
8289 &lt;p&gt;I am told that PackageKit can provide an API to access the kind of
8290 information mentioned in DEP-11. I have not yet had time to look at
8291 it, but hope the PackageKit people in Debian are on top of these
8292 issues.&lt;/p&gt;
8293
8294 &lt;p&gt;&lt;strong&gt;Update 2013-01-16 13:35&lt;/strong&gt;: Updated numbers after
8295 discovering a typo in my script.&lt;/p&gt;
8296 </description>
8297 </item>
8298
8299 <item>
8300 <title>Using modalias info to find packages handling my hardware</title>
8301 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</link>
8302 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html</guid>
8303 <pubDate>Tue, 15 Jan 2013 08:00:00 +0100</pubDate>
8304 <description>&lt;p&gt;Yesterday, I wrote about the
8305 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html&quot;&gt;modalias
8306 values provided by the Linux kernel&lt;/a&gt; following my hope for
8307 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html&quot;&gt;better
8308 dongle support in Debian&lt;/a&gt;. Using this knowledge, I have tested how
8309 modalias values attached to package names can be used to map packages
8310 to hardware. This allow the system to look up and suggest relevant
8311 packages when I plug in some new hardware into my machine, and replace
8312 discover and discover-data as the database used to map hardware to
8313 packages.&lt;/p&gt;
8314
8315 &lt;p&gt;I create a modaliases file with entries like the following,
8316 containing package name, kernel module name (if relevant, otherwise
8317 the package name) and globs matching the relevant hardware
8318 modalias.&lt;/p&gt;
8319
8320 &lt;p&gt;&lt;blockquote&gt;
8321 Package: package-name
8322 &lt;br&gt;Modaliases: module(modaliasglob, modaliasglob, modaliasglob)&lt;/p&gt;
8323 &lt;/blockquote&gt;&lt;/p&gt;
8324
8325 &lt;p&gt;It is fairly trivial to write code to find the relevant packages
8326 for a given modalias value using this file.&lt;/p&gt;
8327
8328 &lt;p&gt;An entry like this would suggest the video and picture application
8329 cheese for many USB web cameras (interface bus class 0E01):&lt;/p&gt;
8330
8331 &lt;p&gt;&lt;blockquote&gt;
8332 Package: cheese
8333 &lt;br&gt;Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)&lt;/p&gt;
8334 &lt;/blockquote&gt;&lt;/p&gt;
8335
8336 &lt;p&gt;An entry like this would suggest the pcmciautils package when a
8337 CardBus bridge (bus class 0607) PCI device is present:&lt;/p&gt;
8338
8339 &lt;p&gt;&lt;blockquote&gt;
8340 Package: pcmciautils
8341 &lt;br&gt;Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
8342 &lt;/blockquote&gt;&lt;/p&gt;
8343
8344 &lt;p&gt;An entry like this would suggest the package colorhug-client when
8345 plugging in a ColorHug with USB IDs 04D8:F8DA:&lt;/p&gt;
8346
8347 &lt;p&gt;&lt;blockquote&gt;
8348 Package: colorhug-client
8349 &lt;br&gt;Modaliases: colorhug-client(usb:v04D8pF8DAd*)&lt;/p&gt;
8350 &lt;/blockquote&gt;&lt;/p&gt;
8351
8352 &lt;p&gt;I believe the format is compatible with the format of the Packages
8353 file in the Debian archive. Ubuntu already uses their Packages file
8354 to store their mappings from packages to hardware.&lt;/p&gt;
8355
8356 &lt;p&gt;By adding a XB-Modaliases: header in debian/control, any .deb can
8357 announce the hardware it support in a way my prototype understand.
8358 This allow those publishing packages in an APT source outside the
8359 Debian archive as well as those backporting packages to make sure the
8360 hardware mapping are included in the package meta information. I&#39;ve
8361 tested such header in the pymissile package, and its modalias mapping
8362 is working as it should with my prototype. It even made it to Ubuntu
8363 Raring.&lt;/p&gt;
8364
8365 &lt;p&gt;To test if it was possible to look up supported hardware using only
8366 the shell tools available in the Debian installer, I wrote a shell
8367 implementation of the lookup code. The idea is to create files for
8368 each modalias and let the shell do the matching. Please check out and
8369 try the
8370 &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;
8371 shell script. It run without any extra dependencies and fetch the
8372 hardware mappings from the Debian archive and the subversion
8373 repository where I currently work on my prototype.&lt;/p&gt;
8374
8375 &lt;p&gt;When I use it on a machine with a yubikey inserted, it suggest to
8376 install yubikey-personalization:&lt;/p&gt;
8377
8378 &lt;p&gt;&lt;blockquote&gt;
8379 % ./hw-support-lookup
8380 &lt;br&gt;yubikey-personalization
8381 &lt;br&gt;%
8382 &lt;/blockquote&gt;&lt;/p&gt;
8383
8384 &lt;p&gt;When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
8385 propose to install the pcmciautils package:&lt;/p&gt;
8386
8387 &lt;p&gt;&lt;blockquote&gt;
8388 % ./hw-support-lookup
8389 &lt;br&gt;pcmciautils
8390 &lt;br&gt;%
8391 &lt;/blockquote&gt;&lt;/p&gt;
8392
8393 &lt;p&gt;If you know of any hardware-package mapping that should be added to
8394 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co&quot;&gt;my
8395 database&lt;/a&gt;, please tell me about it.&lt;/p&gt;
8396
8397 &lt;p&gt;It could be possible to generate several of the mappings between
8398 packages and hardware. One source would be to look at packages with
8399 kernel modules, ie packages with *.ko files in /lib/modules/, and
8400 extract their modalias information. Another would be to look at
8401 packages with udev rules, ie packages with files in
8402 /lib/udev/rules.d/, and extract their vendor/model information to
8403 generate a modalias matching rule. I have not tested any of these to
8404 see if it work.&lt;/p&gt;
8405
8406 &lt;p&gt;If you want to help implementing a system to let us propose what
8407 packages to install when new hardware is plugged into a Debian
8408 machine, please send me an email or talk to me on
8409 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
8410 </description>
8411 </item>
8412
8413 <item>
8414 <title>Modalias strings - a practical way to map &quot;stuff&quot; to hardware</title>
8415 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</link>
8416 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html</guid>
8417 <pubDate>Mon, 14 Jan 2013 11:20:00 +0100</pubDate>
8418 <description>&lt;p&gt;While looking into how to look up Debian packages based on hardware
8419 information, to find the packages that support a given piece of
8420 hardware, I refreshed my memory regarding modalias values, and decided
8421 to document the details. Here are my findings so far, also available
8422 in
8423 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
8424 Debian Edu subversion repository&lt;/a&gt;:
8425
8426 &lt;p&gt;&lt;strong&gt;Modalias decoded&lt;/strong&gt;&lt;/p&gt;
8427
8428 &lt;p&gt;This document try to explain what the different types of modalias
8429 values stands for. It is in part based on information from
8430 &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;,
8431 &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;,
8432 &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
8433 &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;.
8434
8435 &lt;p&gt;The modalias entries for a given Linux machine can be found using
8436 this shell script:&lt;/p&gt;
8437
8438 &lt;pre&gt;
8439 find /sys -name modalias -print0 | xargs -0 cat | sort -u
8440 &lt;/pre&gt;
8441
8442 &lt;p&gt;The supported modalias globs for a given kernel module can be found
8443 using modinfo:&lt;/p&gt;
8444
8445 &lt;pre&gt;
8446 % /sbin/modinfo psmouse | grep alias:
8447 alias: serio:ty05pr*id*ex*
8448 alias: serio:ty01pr*id*ex*
8449 %
8450 &lt;/pre&gt;
8451
8452 &lt;p&gt;&lt;strong&gt;PCI subtype&lt;/strong&gt;&lt;/p&gt;
8453
8454 &lt;p&gt;A typical PCI entry can look like this. This is an Intel Host
8455 Bridge memory controller:&lt;/p&gt;
8456
8457 &lt;p&gt;&lt;blockquote&gt;
8458 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
8459 &lt;/blockquote&gt;&lt;/p&gt;
8460
8461 &lt;p&gt;This represent these values:&lt;/p&gt;
8462
8463 &lt;pre&gt;
8464 v 00008086 (vendor)
8465 d 00002770 (device)
8466 sv 00001028 (subvendor)
8467 sd 000001AD (subdevice)
8468 bc 06 (bus class)
8469 sc 00 (bus subclass)
8470 i 00 (interface)
8471 &lt;/pre&gt;
8472
8473 &lt;p&gt;The vendor/device values are the same values outputted from &#39;lspci
8474 -n&#39; as 8086:2770. The bus class/subclass is also shown by lspci as
8475 0600. The 0600 class is a host bridge. Other useful bus values are
8476 0300 (VGA compatible card) and 0200 (Ethernet controller).&lt;/p&gt;
8477
8478 &lt;p&gt;Not sure how to figure out the interface value, nor what it
8479 means.&lt;/p&gt;
8480
8481 &lt;p&gt;&lt;strong&gt;USB subtype&lt;/strong&gt;&lt;/p&gt;
8482
8483 &lt;p&gt;Some typical USB entries can look like this. This is an internal
8484 USB hub in a laptop:&lt;/p&gt;
8485
8486 &lt;p&gt;&lt;blockquote&gt;
8487 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
8488 &lt;/blockquote&gt;&lt;/p&gt;
8489
8490 &lt;p&gt;Here is the values included in this alias:&lt;/p&gt;
8491
8492 &lt;pre&gt;
8493 v 1D6B (device vendor)
8494 p 0001 (device product)
8495 d 0206 (bcddevice)
8496 dc 09 (device class)
8497 dsc 00 (device subclass)
8498 dp 00 (device protocol)
8499 ic 09 (interface class)
8500 isc 00 (interface subclass)
8501 ip 00 (interface protocol)
8502 &lt;/pre&gt;
8503
8504 &lt;p&gt;The 0900 device class/subclass means hub. Some times the relevant
8505 class is in the interface class section. For a simple USB web camera,
8506 these alias entries show up:&lt;/p&gt;
8507
8508 &lt;p&gt;&lt;blockquote&gt;
8509 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
8510 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
8511 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
8512 &lt;br&gt;usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
8513 &lt;/blockquote&gt;&lt;/p&gt;
8514
8515 &lt;p&gt;Interface class 0E01 is video control, 0E02 is video streaming (aka
8516 camera), 0101 is audio control device and 0102 is audio streaming (aka
8517 microphone). Thus this is a camera with microphone included.&lt;/p&gt;
8518
8519 &lt;p&gt;&lt;strong&gt;ACPI subtype&lt;/strong&gt;&lt;/p&gt;
8520
8521 &lt;p&gt;The ACPI type is used for several non-PCI/USB stuff. This is an IR
8522 receiver in a Thinkpad X40:&lt;/p&gt;
8523
8524 &lt;p&gt;&lt;blockquote&gt;
8525 acpi:IBM0071:PNP0511:
8526 &lt;/blockquote&gt;&lt;/p&gt;
8527
8528 &lt;p&gt;The values between the colons are IDs.&lt;/p&gt;
8529
8530 &lt;p&gt;&lt;strong&gt;DMI subtype&lt;/strong&gt;&lt;/p&gt;
8531
8532 &lt;p&gt;The DMI table contain lots of information about the computer case
8533 and model. This is an entry for a IBM Thinkpad X40, fetched from
8534 /sys/devices/virtual/dmi/id/modalias:&lt;/p&gt;
8535
8536 &lt;p&gt;&lt;blockquote&gt;
8537 dmi:bvnIBM:bvr1UETB6WW(1.66):bd06/15/2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
8538 &lt;/blockquote&gt;&lt;/p&gt;
8539
8540 &lt;p&gt;The values present are&lt;/p&gt;
8541
8542 &lt;pre&gt;
8543 bvn IBM (BIOS vendor)
8544 bvr 1UETB6WW(1.66) (BIOS version)
8545 bd 06/15/2005 (BIOS date)
8546 svn IBM (system vendor)
8547 pn 2371H4G (product name)
8548 pvr ThinkPadX40 (product version)
8549 rvn IBM (board vendor)
8550 rn 2371H4G (board name)
8551 rvr NotAvailable (board version)
8552 cvn IBM (chassis vendor)
8553 ct 10 (chassis type)
8554 cvr NotAvailable (chassis version)
8555 &lt;/pre&gt;
8556
8557 &lt;p&gt;The chassis type 10 is Notebook. Other interesting values can be
8558 found in the dmidecode source:&lt;/p&gt;
8559
8560 &lt;pre&gt;
8561 3 Desktop
8562 4 Low Profile Desktop
8563 5 Pizza Box
8564 6 Mini Tower
8565 7 Tower
8566 8 Portable
8567 9 Laptop
8568 10 Notebook
8569 11 Hand Held
8570 12 Docking Station
8571 13 All In One
8572 14 Sub Notebook
8573 15 Space-saving
8574 16 Lunch Box
8575 17 Main Server Chassis
8576 18 Expansion Chassis
8577 19 Sub Chassis
8578 20 Bus Expansion Chassis
8579 21 Peripheral Chassis
8580 22 RAID Chassis
8581 23 Rack Mount Chassis
8582 24 Sealed-case PC
8583 25 Multi-system
8584 26 CompactPCI
8585 27 AdvancedTCA
8586 28 Blade
8587 29 Blade Enclosing
8588 &lt;/pre&gt;
8589
8590 &lt;p&gt;The chassis type values are not always accurately set in the DMI
8591 table. For example my home server is a tower, but the DMI modalias
8592 claim it is a desktop.&lt;/p&gt;
8593
8594 &lt;p&gt;&lt;strong&gt;SerIO subtype&lt;/strong&gt;&lt;/p&gt;
8595
8596 &lt;p&gt;This type is used for PS/2 mouse plugs. One example is from my
8597 test machine:&lt;/p&gt;
8598
8599 &lt;p&gt;&lt;blockquote&gt;
8600 serio:ty01pr00id00ex00
8601 &lt;/blockquote&gt;&lt;/p&gt;
8602
8603 &lt;p&gt;The values present are&lt;/p&gt;
8604
8605 &lt;pre&gt;
8606 ty 01 (type)
8607 pr 00 (prototype)
8608 id 00 (id)
8609 ex 00 (extra)
8610 &lt;/pre&gt;
8611
8612 &lt;p&gt;This type is supported by the psmouse driver. I am not sure what
8613 the valid values are.&lt;/p&gt;
8614
8615 &lt;p&gt;&lt;strong&gt;Other subtypes&lt;/strong&gt;&lt;/p&gt;
8616
8617 &lt;p&gt;There are heaps of other modalias subtypes according to
8618 file2alias.c. There is the rest of the list from that source: amba,
8619 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
8620 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
8621 vmbus, x86cpu and zorro. I did not spend time documenting all of
8622 these, as they do not seem relevant for my intended use with mapping
8623 hardware to packages when new stuff is inserted during run time.&lt;/p&gt;
8624
8625 &lt;p&gt;&lt;strong&gt;Looking up kernel modules using modalias values&lt;/strong&gt;&lt;/p&gt;
8626
8627 &lt;p&gt;To check which kernel modules provide support for a given modalias,
8628 one can use the following shell script:&lt;/p&gt;
8629
8630 &lt;pre&gt;
8631 for id in $(find /sys -name modalias -print0 | xargs -0 cat | sort -u); do \
8632 echo &quot;$id&quot; ; \
8633 /sbin/modprobe --show-depends &quot;$id&quot;|sed &#39;s/^/ /&#39; ; \
8634 done
8635 &lt;/pre&gt;
8636
8637 &lt;p&gt;The output can look like this (only the first few entries as the
8638 list is very long on my test machine):&lt;/p&gt;
8639
8640 &lt;pre&gt;
8641 acpi:ACPI0003:
8642 insmod /lib/modules/2.6.32-5-686/kernel/drivers/acpi/ac.ko
8643 acpi:device:
8644 FATAL: Module acpi:device: not found.
8645 acpi:IBM0068:
8646 insmod /lib/modules/2.6.32-5-686/kernel/drivers/char/nvram.ko
8647 insmod /lib/modules/2.6.32-5-686/kernel/drivers/leds/led-class.ko
8648 insmod /lib/modules/2.6.32-5-686/kernel/net/rfkill/rfkill.ko
8649 insmod /lib/modules/2.6.32-5-686/kernel/drivers/platform/x86/thinkpad_acpi.ko
8650 acpi:IBM0071:PNP0511:
8651 insmod /lib/modules/2.6.32-5-686/kernel/lib/crc-ccitt.ko
8652 insmod /lib/modules/2.6.32-5-686/kernel/net/irda/irda.ko
8653 insmod /lib/modules/2.6.32-5-686/kernel/drivers/net/irda/nsc-ircc.ko
8654 [...]
8655 &lt;/pre&gt;
8656
8657 &lt;p&gt;If you want to help implementing a system to let us propose what
8658 packages to install when new hardware is plugged into a Debian
8659 machine, please send me an email or talk to me on
8660 &lt;a href=&quot;irc://irc.debian.org/%23debian-devel&quot;&gt;#debian-devel&lt;/a&gt;.&lt;/p&gt;
8661
8662 &lt;p&gt;&lt;strong&gt;Update 2013-01-15:&lt;/strong&gt; Rewrite &quot;cat $(find ...)&quot; to
8663 &quot;find ... -print0 | xargs -0 cat&quot; to make sure it handle directories
8664 in /sys/ with space in them.&lt;/p&gt;
8665 </description>
8666 </item>
8667
8668 <item>
8669 <title>Moved the pymissile Debian packaging to collab-maint</title>
8670 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</link>
8671 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html</guid>
8672 <pubDate>Thu, 10 Jan 2013 20:40:00 +0100</pubDate>
8673 <description>&lt;p&gt;As part of my investigation on how to improve the support in Debian
8674 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
8675 Launcher and updated the Debian package
8676 &lt;a href=&quot;http://packages.qa.debian.org/pymissile&quot;&gt;pymissile&lt;/a&gt; to make
8677 sure udev will fix the device permissions when it is plugged in. I
8678 also added a &quot;Modaliases&quot; header to test it in the Debian archive and
8679 hopefully make the package be proposed by jockey in Ubuntu when a user
8680 plug in his rocket launcher. In the process I moved the source to a
8681 git repository under collab-maint, to make it easier for any DD to
8682 contribute. &lt;a href=&quot;http://code.google.com/p/pymissile/&quot;&gt;Upstream&lt;/a&gt;
8683 is not very active, but the software still work for me even after five
8684 years of relative silence. The new git repository is not listed in
8685 the uploaded package yet, because I want to test the other changes a
8686 bit more before I upload the new version. If you want to check out
8687 the new version with a .desktop file included, visit the
8688 &lt;a href=&quot;http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git&quot;&gt;gitweb
8689 view&lt;/a&gt; or use &quot;&lt;tt&gt;git clone
8690 git://anonscm.debian.org/collab-maint/pymissile.git&lt;/tt&gt;&quot;.&lt;/p&gt;
8691 </description>
8692 </item>
8693
8694 <item>
8695 <title>Lets make hardware dongles easier to use in Debian</title>
8696 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</link>
8697 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html</guid>
8698 <pubDate>Wed, 9 Jan 2013 15:40:00 +0100</pubDate>
8699 <description>&lt;p&gt;One thing that annoys me with Debian and Linux distributions in
8700 general, is that there is a great package management system with the
8701 ability to automatically install software packages by downloading them
8702 from the distribution mirrors, but no way to get it to automatically
8703 install the packages I need to use the hardware I plug into my
8704 machine. Even if the package to use it is easily available from the
8705 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
8706 suggest to automatically install the python-nxt, nbc and t2n packages
8707 I need to talk to it. When I plug in a Yubikey, it could propose the
8708 yubikey-personalization package. The information required to do this
8709 is available, but no-one have pulled all the pieces together.&lt;/p&gt;
8710
8711 &lt;p&gt;Some years ago, I proposed to
8712 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg01206.html&quot;&gt;use
8713 the discover subsystem to implement this&lt;/a&gt;. The idea is fairly
8714 simple:
8715
8716 &lt;ul&gt;
8717
8718 &lt;li&gt;Add a desktop entry in /usr/share/autostart/ pointing to a program
8719 starting when a user log in.&lt;/li&gt;
8720
8721 &lt;li&gt;Set this program up to listen for kernel events emitted when new
8722 hardware is inserted into the computer.&lt;/li&gt;
8723
8724 &lt;li&gt;When new hardware is inserted, look up the hardware ID in a
8725 database mapping to packages, and take note of any non-installed
8726 packages.&lt;/li&gt;
8727
8728 &lt;li&gt;Show a message to the user proposing to install the discovered
8729 package, and make it easy to install it.&lt;/li&gt;
8730
8731 &lt;/ul&gt;
8732
8733 &lt;p&gt;I am not sure what the best way to implement this is, but my
8734 initial idea was to use dbus events to discover new hardware, the
8735 discover database to find packages and
8736 &lt;a href=&quot;http://www.packagekit.org/&quot;&gt;PackageKit&lt;/a&gt; to install
8737 packages.&lt;/p&gt;
8738
8739 &lt;p&gt;Yesterday, I found time to try to implement this idea, and the
8740 draft package is now checked into
8741 &lt;a href=&quot;http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/&quot;&gt;the
8742 Debian Edu subversion repository&lt;/a&gt;. In the process, I updated the
8743 &lt;a href=&quot;http://packages.qa.debian.org/d/discover-data.html&quot;&gt;discover-data&lt;/a&gt;
8744 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
8745 the relevant packages in Debian, and uploaded a new version
8746 2.2013.01.09 to unstable. I also discovered that the current
8747 &lt;a href=&quot;http://packages.qa.debian.org/d/discover.html&quot;&gt;discover&lt;/a&gt;
8748 package in Debian no longer discovered any USB devices, because
8749 /proc/bus/usb/devices is no longer present. I ported it to use
8750 libusb as a fall back option to get it working. The fixed package
8751 version 2.1.2-6 is now in experimental (didn&#39;t upload it to unstable
8752 because of the freeze).&lt;/p&gt;
8753
8754 &lt;p&gt;With this prototype in place, I can insert my Yubikey, and get this
8755 desktop notification to show up (only once, the first time it is
8756 inserted):&lt;/p&gt;
8757
8758 &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;
8759
8760 &lt;p&gt;For this prototype to be really useful, some way to automatically
8761 install the proposed packages by pressing the &quot;Please install
8762 program(s)&quot; button should to be implemented.&lt;/p&gt;
8763
8764 &lt;p&gt;If this idea seem useful to you, and you want to help make it
8765 happen, please help me update the discover-data database with mappings
8766 from hardware to Debian packages. Check if &#39;discover-pkginstall -l&#39;
8767 list the package you would like to have installed when a given
8768 hardware device is inserted into your computer, and report bugs using
8769 reportbug if it isn&#39;t. Or, if you know of a better way to provide
8770 such mapping, please let me know.&lt;/p&gt;
8771
8772 &lt;p&gt;This prototype need more work, and there are several questions that
8773 should be considered before it is ready for production use. Is dbus
8774 the correct way to detect new hardware? At the moment I look for HAL
8775 dbus events on the system bus, because that is the events I could see
8776 on my Debian Squeeze KDE desktop. Are there better events to use?
8777 How should the user be notified? Is the desktop notification
8778 mechanism the best option, or should the background daemon raise a
8779 popup instead? How should packages be installed? When should they
8780 not be installed?&lt;/p&gt;
8781
8782 &lt;p&gt;If you want to help getting such feature implemented in Debian,
8783 please send me an email. :)&lt;/p&gt;
8784 </description>
8785 </item>
8786
8787 <item>
8788 <title>New IRC channel for LEGO designers using Debian</title>
8789 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</link>
8790 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html</guid>
8791 <pubDate>Wed, 2 Jan 2013 15:40:00 +0100</pubDate>
8792 <description>&lt;p&gt;During Christmas, I have worked a bit on the Debian support for
8793 &lt;a href=&quot;http://mindstorms.lego.com/en-us/Default.aspx&quot;&gt;LEGO Mindstorm
8794 NXT&lt;/a&gt;. My son and I have played a bit with my NXT set, and I
8795 discovered I had to build all the tools myself because none were
8796 already in Debian Squeeze. If Debian support for LEGO is something
8797 you care about, please join me on the IRC channel
8798 &lt;a href=&quot;irc://irc.debian.org/%23debian-lego&quot;&gt;#debian-lego&lt;/a&gt; (server
8799 irc.debian.org). There is a lot that could be done to improve the
8800 Debian support for LEGO designers. For example both CAD software
8801 and Mindstorm compilers are missing. :)&lt;/p&gt;
8802
8803 &lt;p&gt;Update 2012-01-03: A
8804 &lt;a href=&quot;http://wiki.debian.org/LegoDesigners&quot;&gt;project page&lt;/a&gt;
8805 including links to Lego related packages is now available.&lt;/p&gt;
8806 </description>
8807 </item>
8808
8809 <item>
8810 <title>How to backport bitcoin-qt version 0.7.2-2 to Debian Squeeze</title>
8811 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</link>
8812 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html</guid>
8813 <pubDate>Tue, 25 Dec 2012 20:50:00 +0100</pubDate>
8814 <description>&lt;p&gt;Let me start by wishing you all marry Christmas and a happy new
8815 year! I hope next year will prove to be a good year.&lt;/p&gt;
8816
8817 &lt;p&gt;&lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;Bitcoin&lt;/a&gt;, the digital
8818 decentralised &quot;currency&quot; that allow people to transfer bitcoins
8819 between each other with minimal overhead, is a very interesting
8820 experiment. And as I wrote a few days ago, the bitcoin situation in
8821 &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt; is about to improve a bit.
8822 The &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;new debian source
8823 package&lt;/a&gt; (version 0.7.2-2) was uploaded yesterday, and is waiting
8824 in &lt;a href=&quot;http://ftp-master.debian.org/new.html&quot;&gt;the NEW queue&lt;/A&gt;
8825 for one of the ftpmasters to approve the new bitcoin-qt package
8826 name.&lt;/p&gt;
8827
8828 &lt;p&gt;And thanks to the great work of Jonas and the rest of the bitcoin
8829 team in Debian, you can easily test the package in Debian Squeeze
8830 using the following steps to get a set of working packages:&lt;/p&gt;
8831
8832 &lt;blockquote&gt;&lt;pre&gt;
8833 git clone git://git.debian.org/git/collab-maint/bitcoin
8834 cd bitcoin
8835 DEB_MAINTAINER_MODE=1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
8836 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
8837 &lt;/pre&gt;&lt;/blockquote&gt;
8838
8839 &lt;p&gt;You might have to install some build dependencies as well. The
8840 list of commands should give you two packages, bitcoind and
8841 bitcoin-qt, ready for use in a Squeeze environment. Note that the
8842 client will download the complete set of bitcoin &quot;blocks&quot;, which need
8843 around 5.6 GiB of data on my machine at the moment. Make sure your
8844 ~/.bitcoin/ directory have lots of spare room if you want to download
8845 all the blocks. The client will warn if the disk is getting full, so
8846 there is not really a problem if you got too little room, but you will
8847 not be able to get all the features out of the client.&lt;/p&gt;
8848
8849 &lt;p&gt;As usual, if you use bitcoin and want to show your support of my
8850 activities, please send Bitcoin donations to my address
8851 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8852 </description>
8853 </item>
8854
8855 <item>
8856 <title>A word on bitcoin support in Debian</title>
8857 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</link>
8858 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html</guid>
8859 <pubDate>Fri, 21 Dec 2012 23:59:00 +0100</pubDate>
8860 <description>&lt;p&gt;It has been a while since I wrote about
8861 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;bitcoin&lt;/a&gt;, the decentralised
8862 peer-to-peer based crypto-currency, and the reason is simply that I
8863 have been busy elsewhere. But two days ago, I started looking at the
8864 state of &lt;a href=&quot;http://packages.qa.debian.org/bitcoin&quot;&gt;bitcoin in
8865 Debian&lt;/a&gt; again to try to recover my old bitcoin wallet. The package
8866 is now maintained by a
8867 &lt;a href=&quot;https://alioth.debian.org/projects/pkg-bitcoin/&quot;&gt;team of
8868 people&lt;/a&gt;, and the grunt work had already been done by this team. We
8869 owe a huge thank you to all these team members. :)
8870 But I was sad to discover that the bitcoin client is missing in
8871 Wheezy. It is only available in Sid (and an outdated client from
8872 backports). The client had several RC bugs registered in BTS blocking
8873 it from entering testing. To try to help the team and improve the
8874 situation, I spent some time providing patches and triaging the bug
8875 reports. I also had a look at the bitcoin package available from Matt
8876 Corallo in a
8877 &lt;a href=&quot;https://launchpad.net/~bitcoin/+archive/bitcoin&quot;&gt;PPA for
8878 Ubuntu&lt;/a&gt;, and moved the useful pieces from that version into the
8879 Debian package.&lt;/p&gt;
8880
8881 &lt;p&gt;After checking with the main package maintainer Jonas Smedegaard on
8882 IRC, I pushed several patches into the collab-maint git repository to
8883 improve the package. It now contains fixes for the RC issues (not from
8884 me, but fixed by Scott Howard), build rules for a Qt GUI client
8885 package, konqueror support for the bitcoin: URI and bash completion
8886 setup. As I work on Debian Squeeze, I also created
8887 &lt;a href=&quot;http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-20121217/000041.html&quot;&gt;a
8888 patch to backport&lt;/a&gt; the latest version. Jonas is going to look at
8889 it and try to integrate it into the git repository before uploading a
8890 new version to unstable.
8891
8892 &lt;p&gt;I would very much like bitcoin to succeed, to get rid of the
8893 centralized control currently exercised in the monetary system. I
8894 find it completely unacceptable that the USA government is collecting
8895 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
8896 that the major credit card companies can block legal money
8897 transactions to Wikileaks. But for bitcoin to succeed, more people
8898 need to use bitcoins, and more people need to accept bitcoins when
8899 they sell products and services. Improving the bitcoin support in
8900 Debian is a small step in the right direction, but not enough.
8901 Unfortunately the user experience when browsing the web and wanting to
8902 pay with bitcoin is still not very good. The bitcoin: URI is a step
8903 in the right direction, but need to work in most or every browser in
8904 use. Also the bitcoin-qt client is too heavy to fire up to do a
8905 quick transaction. I believe there are other clients available, but
8906 have not tested them.&lt;/p&gt;
8907
8908 &lt;p&gt;My
8909 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html&quot;&gt;experiment
8910 with bitcoins&lt;/a&gt; showed that at least some of my readers use bitcoin.
8911 I received 20.15 BTC so far on the address I provided in my blog two
8912 years ago, as can be
8913 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;seen
8914 on the blockexplorer service&lt;/a&gt;. Thank you everyone for your
8915 donation. The blockexplorer service demonstrates quite well that
8916 bitcoin is not quite anonymous and untracked. :) I wonder if the
8917 number of users have gone up since then. If you use bitcoin and want
8918 to show your support of my activity, please send Bitcoin donations to
8919 the same address as last time,
8920 &lt;b&gt;&lt;a href=&quot;bitcoin:15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;&lt;/b&gt;.&lt;/p&gt;
8921 </description>
8922 </item>
8923
8924 <item>
8925 <title>Git repository for song book for Computer Scientists</title>
8926 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</link>
8927 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html</guid>
8928 <pubDate>Fri, 7 Sep 2012 13:50:00 +0200</pubDate>
8929 <description>&lt;p&gt;As I
8930 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html&quot;&gt;mentioned
8931 this summer&lt;/a&gt;, I have created a Computer Science song book a few
8932 years ago, and today I finally found time to create a public
8933 &lt;a href=&quot;https://gitorious.org/pere-cs-songbook/pere-cs-songbook&quot;&gt;Gitorious
8934 repository for the project&lt;/a&gt;.&lt;/p&gt;
8935
8936 &lt;p&gt;If you want to help out, please clone the source and submit patches
8937 to the HTML version. To generate the PDF and PostScript version,
8938 please use prince XML, or let me know about a useful free software
8939 processor capable of creating a good looking PDF from the HTML.&lt;/p&gt;
8940
8941 &lt;p&gt;Want to sing? You can still find the song book in HTML, PDF and
8942 PostScript formats at
8943 &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s Computer
8944 Science Songbook&lt;/a&gt;.&lt;/p&gt;
8945 </description>
8946 </item>
8947
8948 <item>
8949 <title>Gratulerer med 19-årsdagen, Debian!</title>
8950 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</link>
8951 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html</guid>
8952 <pubDate>Thu, 16 Aug 2012 11:20:00 +0200</pubDate>
8953 <description>&lt;p&gt;I dag fyller
8954 &lt;a href=&quot;http://www.debian.org/News/2012/20120813&quot;&gt;Debian-prosjektet 19
8955 år&lt;/a&gt;. Jeg har fulgt det de siste 12 årene, og er veldig glad for å kunne
8956 si gratulerer med dagen, Debian!&lt;/p&gt;
8957 </description>
8958 </item>
8959
8960 <item>
8961 <title>Song book for Computer Scientists</title>
8962 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</link>
8963 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html</guid>
8964 <pubDate>Sun, 24 Jun 2012 13:30:00 +0200</pubDate>
8965 <description>&lt;p&gt;Many years ago, while studying Computer Science at the
8966 &lt;a href=&quot;http://www.uit.no/&quot;&gt;University of Tromsø&lt;/a&gt;, I started
8967 collecting computer related songs for use at parties. The original
8968 version was written in LaTeX, but a few years ago I got help from
8969 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
8970 while keeping the ability to create a nice book in PDF format. I have
8971 not had time to maintain the book for a while now, and guess I should
8972 put it up on some public version control repository where others can
8973 help me extend and update the book. If anyone is volunteering to help
8974 me with this, send me an email. Also let me know if there are songs
8975 missing in my book.&lt;/p&gt;
8976
8977 &lt;p&gt;I have not mentioned the book on my blog so far, and it occured to
8978 me today that I really should let all my readers share the joys of
8979 singing out load about programming, computers and computer networks.
8980 Especially now that &lt;a href=&quot;http://debconf12.debconf.org/&quot;&gt;Debconf
8981 12&lt;/a&gt; is about to start (and I am not going). Want to sing? Check
8982 out &lt;a href=&quot;http://www.hungry.com/~pere/cs-songbook/&quot;&gt;Petter&#39;s
8983 Computer Science Songbook&lt;/a&gt;.
8984 </description>
8985 </item>
8986
8987 <item>
8988 <title>Automatically upgrading server firmware on Dell PowerEdge</title>
8989 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</link>
8990 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html</guid>
8991 <pubDate>Mon, 21 Nov 2011 12:00:00 +0100</pubDate>
8992 <description>&lt;p&gt;At work we have heaps of servers. I believe the total count is
8993 around 1000 at the moment. To be able to get help from the vendors
8994 when something go wrong, we want to keep the firmware on the servers
8995 up to date. If the firmware isn&#39;t the latest and greatest, the
8996 vendors typically refuse to start debugging any problems until the
8997 firmware is upgraded. So before every reboot, we want to upgrade the
8998 firmware, and we would really like everyone handling servers at the
8999 university to do this themselves when they plan to reboot a machine.
9000 For that to happen we at the unix server admin group need to provide
9001 the tools to do so.&lt;/p&gt;
9002
9003 &lt;p&gt;To make firmware upgrading easier, I am working on a script to
9004 fetch and install the latest firmware for the servers we got. Most of
9005 our hardware are from Dell and HP, so I have focused on these servers
9006 so far. This blog post is about the Dell part.&lt;/P&gt;
9007
9008 &lt;p&gt;On the Dell FTP site I was lucky enough to find
9009 &lt;a href=&quot;ftp://ftp.us.dell.com/catalog/Catalog.xml.gz&quot;&gt;an XML file&lt;/a&gt;
9010 with firmware information for all 11th generation servers, listing
9011 which firmware should be used on a given model and where on the FTP
9012 site I can find it. Using a simple perl XML parser I can then
9013 download the shell scripts Dell provides to do firmware upgrades from
9014 within Linux and reboot when all the firmware is primed and ready to
9015 be activated on the first reboot.&lt;/p&gt;
9016
9017 &lt;p&gt;This is the Dell related fragment of the perl code I am working on.
9018 Are there anyone working on similar tools for firmware upgrading all
9019 servers at a site? Please get in touch and lets share resources.&lt;/p&gt;
9020
9021 &lt;p&gt;&lt;pre&gt;
9022 #!/usr/bin/perl
9023 use strict;
9024 use warnings;
9025 use File::Temp qw(tempdir);
9026 BEGIN {
9027 # Install needed RHEL packages if missing
9028 my %rhelmodules = (
9029 &#39;XML::Simple&#39; =&gt; &#39;perl-XML-Simple&#39;,
9030 );
9031 for my $module (keys %rhelmodules) {
9032 eval &quot;use $module;&quot;;
9033 if ($@) {
9034 my $pkg = $rhelmodules{$module};
9035 system(&quot;yum install -y $pkg&quot;);
9036 eval &quot;use $module;&quot;;
9037 }
9038 }
9039 }
9040 my $errorsto = &#39;pere@hungry.com&#39;;
9041
9042 upgrade_dell();
9043
9044 exit 0;
9045
9046 sub run_firmware_script {
9047 my ($opts, $script) = @_;
9048 unless ($script) {
9049 print STDERR &quot;fail: missing script name\n&quot;;
9050 exit 1
9051 }
9052 print STDERR &quot;Running $script\n\n&quot;;
9053
9054 if (0 == system(&quot;sh $script $opts&quot;)) { # FIXME correct exit code handling
9055 print STDERR &quot;success: firmware script ran succcessfully\n&quot;;
9056 } else {
9057 print STDERR &quot;fail: firmware script returned error\n&quot;;
9058 }
9059 }
9060
9061 sub run_firmware_scripts {
9062 my ($opts, @dirs) = @_;
9063 # Run firmware packages
9064 for my $dir (@dirs) {
9065 print STDERR &quot;info: Running scripts in $dir\n&quot;;
9066 opendir(my $dh, $dir) or die &quot;Unable to open directory $dir: $!&quot;;
9067 while (my $s = readdir $dh) {
9068 next if $s =~ m/^\.\.?/;
9069 run_firmware_script($opts, &quot;$dir/$s&quot;);
9070 }
9071 closedir $dh;
9072 }
9073 }
9074
9075 sub download {
9076 my $url = shift;
9077 print STDERR &quot;info: Downloading $url\n&quot;;
9078 system(&quot;wget --quiet \&quot;$url\&quot;&quot;);
9079 }
9080
9081 sub upgrade_dell {
9082 my @dirs;
9083 my $product = `dmidecode -s system-product-name`;
9084 chomp $product;
9085
9086 if ($product =~ m/PowerEdge/) {
9087
9088 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9089 system(&#39;yum install -y compat-libstdc++-33.i686 libstdc++.i686 libxml2.i686 procmail&#39;);
9090
9091 my $tmpdir = tempdir(
9092 CLEANUP =&gt; 1
9093 );
9094 chdir($tmpdir);
9095 fetch_dell_fw(&#39;catalog/Catalog.xml.gz&#39;);
9096 system(&#39;gunzip Catalog.xml.gz&#39;);
9097 my @paths = fetch_dell_fw_list(&#39;Catalog.xml&#39;);
9098 # -q is quiet, disabling interactivity and reducing console output
9099 my $fwopts = &quot;-q&quot;;
9100 if (@paths) {
9101 for my $url (@paths) {
9102 fetch_dell_fw($url);
9103 }
9104 run_firmware_scripts($fwopts, $tmpdir);
9105 } else {
9106 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9107 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9108 }
9109 chdir(&#39;/&#39;);
9110 } else {
9111 print STDERR &quot;error: Unsupported Dell model &#39;$product&#39;.\n&quot;;
9112 print STDERR &quot;error: Please report to $errorsto.\n&quot;;
9113 }
9114 }
9115
9116 sub fetch_dell_fw {
9117 my $path = shift;
9118 my $url = &quot;ftp://ftp.us.dell.com/$path&quot;;
9119 download($url);
9120 }
9121
9122 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9123 # firmware packages to download from Dell. Only work for Linux
9124 # machines and 11th generation Dell servers.
9125 sub fetch_dell_fw_list {
9126 my $filename = shift;
9127
9128 my $product = `dmidecode -s system-product-name`;
9129 chomp $product;
9130 my ($mybrand, $mymodel) = split(/\s+/, $product);
9131
9132 print STDERR &quot;Finding firmware bundles for $mybrand $mymodel\n&quot;;
9133
9134 my $xml = XMLin($filename);
9135 my @paths;
9136 for my $bundle (@{$xml-&gt;{SoftwareBundle}}) {
9137 my $brand = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Display}-&gt;{content};
9138 my $model = $bundle-&gt;{TargetSystems}-&gt;{Brand}-&gt;{Model}-&gt;{Display}-&gt;{content};
9139 my $oscode;
9140 if (&quot;ARRAY&quot; eq ref $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}) {
9141 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}[0]-&gt;{osCode};
9142 } else {
9143 $oscode = $bundle-&gt;{TargetOSes}-&gt;{OperatingSystem}-&gt;{osCode};
9144 }
9145 if ($mybrand eq $brand &amp;&amp; $mymodel eq $model &amp;&amp; &quot;LIN&quot; eq $oscode)
9146 {
9147 @paths = map { $_-&gt;{path} } @{$bundle-&gt;{Contents}-&gt;{Package}};
9148 }
9149 }
9150 for my $component (@{$xml-&gt;{SoftwareComponent}}) {
9151 my $componenttype = $component-&gt;{ComponentType}-&gt;{value};
9152
9153 # Drop application packages, only firmware and BIOS
9154 next if &#39;APAC&#39; eq $componenttype;
9155
9156 my $cpath = $component-&gt;{path};
9157 for my $path (@paths) {
9158 if ($cpath =~ m%/$path$%) {
9159 push(@paths, $cpath);
9160 }
9161 }
9162 }
9163 return @paths;
9164 }
9165 &lt;/pre&gt;
9166
9167 &lt;p&gt;The code is only tested on RedHat Enterprise Linux, but I suspect
9168 it could work on other platforms with some tweaking. Anyone know a
9169 index like Catalog.xml is available from HP for HP servers? At the
9170 moment I maintain a similar list manually and it is quickly getting
9171 outdated.&lt;/p&gt;
9172 </description>
9173 </item>
9174
9175 <item>
9176 <title>How is booting into runlevel 1 different from single user boots?</title>
9177 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</link>
9178 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html</guid>
9179 <pubDate>Thu, 4 Aug 2011 12:40:00 +0200</pubDate>
9180 <description>&lt;p&gt;Wouter Verhelst have some
9181 &lt;a href=&quot;http://grep.be/blog/en/retorts/pere_kubuntu_boot&quot;&gt;interesting
9182 comments and opinions&lt;/a&gt; on my blog post on
9183 &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
9184 need to clean up /etc/rcS.d/ in Debian&lt;/a&gt; and my blog post about
9185 &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
9186 default KDE desktop in Debian&lt;/a&gt;. I only have time to address one
9187 small piece of his comment now, and though it best to address the
9188 misunderstanding he bring forward:&lt;/p&gt;
9189
9190 &lt;p&gt;&lt;blockquote&gt;
9191 Currently, a system admin has four options: [...] boot to a
9192 single-user system (by adding &#39;single&#39; to the kernel command line;
9193 this runs rcS and rc1 scripts)
9194 &lt;/blockquote&gt;&lt;/p&gt;
9195
9196 &lt;p&gt;This make me believe Wouter believe booting into single user mode
9197 and booting into runlevel 1 is the same. I am not surprised he
9198 believe this, because it would make sense and is a quite sensible
9199 thing to believe. But because the boot in Debian is slightly broken,
9200 runlevel 1 do not work properly and it isn&#39;t the same as single user
9201 mode. I&#39;ll try to explain what is actually happing, but it is a bit
9202 hard to explain.&lt;/p&gt;
9203
9204 &lt;p&gt;Single user mode is defined like this in /etc/inittab:
9205 &quot;&lt;tt&gt;~~:S:wait:/sbin/sulogin&lt;/tt&gt;&quot;. This means the only thing that is
9206 executed in single user mode is sulogin. Single user mode is a boot
9207 state &quot;between&quot; the runlevels, and when booting into single user mode,
9208 only the scripts in /etc/rcS.d/ are executed before the init process
9209 enters the single user state. When switching to runlevel 1, the state
9210 is in fact not ending in runlevel 1, but it passes through runlevel 1
9211 and end up in the single user mode (see /etc/rc1.d/S03single, which
9212 runs &quot;init -t1 S&quot; to switch to single user mode at the end of runlevel
9213 1. It is confusing that the &#39;S&#39; (single user) init mode is not the
9214 mode enabled by /etc/rcS.d/ (which is more like the initial boot
9215 mode).&lt;/p&gt;
9216
9217 &lt;p&gt;This summary might make it clearer. When booting for the first
9218 time into single user mode, the following commands are executed:
9219 &quot;&lt;tt&gt;/etc/init.d/rc S; /sbin/sulogin&lt;/tt&gt;&quot;. When booting into
9220 runlevel 1, the following commands are executed: &quot;&lt;tt&gt;/etc/init.d/rc
9221 S; /etc/init.d/rc 1; /sbin/sulogin&lt;/tt&gt;&quot;. A problem show up when
9222 trying to continue after visiting single user mode. Not all services
9223 are started again as they should, causing the machine to end up in an
9224 unpredicatble state. This is why Debian admins recommend rebooting
9225 after visiting single user mode.&lt;/p&gt;
9226
9227 &lt;p&gt;A similar problem with runlevel 1 is caused by the amount of
9228 scripts executed from /etc/rcS.d/. When switching from say runlevel 2
9229 to runlevel 1, the services started from /etc/rcS.d/ are not properly
9230 stopped when passing through the scripts in /etc/rc1.d/, and not
9231 started again when switching away from runlevel 1 to the runlevels
9232 2-5. I believe the problem is best fixed by moving all the scripts
9233 out of /etc/rcS.d/ that are not &lt;strong&gt;required&lt;/strong&gt; to get a
9234 functioning single user mode during boot.&lt;/p&gt;
9235
9236 &lt;p&gt;I have spent several years investigating the Debian boot system,
9237 and discovered this problem a few years ago. I suspect it originates
9238 from when sysvinit was introduced into Debian, a long time ago.&lt;/p&gt;
9239 </description>
9240 </item>
9241
9242 <item>
9243 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing</title>
9244 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</link>
9245 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html</guid>
9246 <pubDate>Sat, 30 Jul 2011 14:00:00 +0200</pubDate>
9247 <description>&lt;p&gt;In the Debian boot system, several packages include scripts that
9248 are started from /etc/rcS.d/. In fact, there is a bite more of them
9249 than make sense, and this causes a few problems. What kind of
9250 problems, you might ask. There are at least two problems. The first
9251 is that it is not possible to recover a machine after switching to
9252 runlevel 1. One need to actually reboot to get the machine back to
9253 the expected state. The other is that single user boot will sometimes
9254 run into problems because some of the subsystems are activated before
9255 the root login is presented, causing problems when trying to recover a
9256 machine from a problem in that subsystem. A minor additional point is
9257 that moving more scripts out of rcS.d/ and into the other rc#.d/
9258 directories will increase the amount of scripts that can run in
9259 parallel during boot, and thus decrease the boot time.&lt;/p&gt;
9260
9261 &lt;p&gt;So, which scripts should start from rcS.d/. In short, only the
9262 scripts that _have_ to execute before the root login prompt is
9263 presented during a single user boot should go there. Everything else
9264 should go into the numeric runlevels. This means things like
9265 lm-sensors, fuse and x11-common should not run from rcS.d, but from
9266 the numeric runlevels. Today in Debian, there are around 115 init.d
9267 scripts that are started from rcS.d/, and most of them should be moved
9268 out. Do your package have one of them? Please help us make single
9269 user and runlevel 1 better by moving it.&lt;/p&gt;
9270
9271 &lt;p&gt;Scripts setting up the screen, keyboard, system partitions
9272 etc. should still be started from rcS.d/, but there is for example no
9273 need to have the network enabled before the single user login prompt
9274 is presented.&lt;/p&gt;
9275
9276 &lt;p&gt;As always, things are not so easy to fix as they sound. To keep
9277 Debian systems working while scripts migrate and during upgrades, the
9278 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
9279 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
9280 and the next ones can only be moved when their dependencies have been
9281 moved first. This migration must be done sequentially while we ensure
9282 that the package system upgrade packages in the right order to keep
9283 the system state correct. This will require some coordination when it
9284 comes to network related packages, but most of the packages with
9285 scripts that should migrate do not have anything in rcS.d/ depending
9286 on them. Some packages have already been updated, like the sudo
9287 package, while others are still left to do. I wish I had time to work
9288 on this myself, but real live constrains make it unlikely that I will
9289 find time to push this forward.&lt;/p&gt;
9290 </description>
9291 </item>
9292
9293 <item>
9294 <title>What is missing in the Debian desktop, or why my parents use Kubuntu</title>
9295 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</link>
9296 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html</guid>
9297 <pubDate>Fri, 29 Jul 2011 08:10:00 +0200</pubDate>
9298 <description>&lt;p&gt;While at Debconf11, I have several times during discussions
9299 mentioned the issues I believe should be improved in Debian for its
9300 desktop to be useful for more people. The use case for this is my
9301 parents, which are currently running Kubuntu which solve the
9302 issues.&lt;/p&gt;
9303
9304 &lt;p&gt;I suspect these four missing features are not very hard to
9305 implement. After all, they are present in Ubuntu, so if we wanted to
9306 do this in Debian we would have a source.&lt;/p&gt;
9307
9308 &lt;ol&gt;
9309
9310 &lt;li&gt;&lt;strong&gt;Simple GUI based upgrade of packages.&lt;/strong&gt; When there
9311 are new packages available for upgrades, a icon in the KDE status bar
9312 indicate this, and clicking on it will activate the simple upgrade
9313 tool to handle it. I have no problem guiding both of my parents
9314 through the process over the phone. If a kernel reboot is required,
9315 this too is indicated by the status bars and the upgrade tool. Last
9316 time I checked, nothing with the same features was working in KDE in
9317 Debian.&lt;/li&gt;
9318
9319 &lt;li&gt;&lt;strong&gt;Simple handling of missing Firefox browser
9320 plugins.&lt;/strong&gt; When the browser encounter a MIME type it do not
9321 currently have a handler for, it will ask the user if the system
9322 should search for a package that would add support for this MIME type,
9323 and if the user say yes, the APT sources will be searched for packages
9324 advertising the MIME type in their control file (visible in the
9325 Packages file in the APT archive). If one or more packages are found,
9326 it is a simple click of the mouse to add support for the missing mime
9327 type. If the package require the user to accept some non-free
9328 license, this is explained to the user. The entire process make it
9329 more clear to the user why something do not work in the browser, and
9330 make the chances higher for the user to blame the web page authors and
9331 not the browser for any missing features.&lt;/li&gt;
9332
9333 &lt;li&gt;&lt;strong&gt;Simple handling of missing multimedia codec/format
9334 handlers.&lt;/strong&gt; When the media players encounter a format or codec
9335 it is not supporting, a dialog pop up asking the user if the system
9336 should search for a package that would add support for it. This
9337 happen with things like MP3, Windows Media or H.264. The selection
9338 and installation procedure is very similar to the Firefox browser
9339 plugin handling. This is as far as I know implemented using a
9340 gstreamer hook. The end result is that the user easily get access to
9341 the codecs that are present from the APT archives available, while
9342 explaining more on why a given format is unsupported by Ubuntu.&lt;/li&gt;
9343
9344 &lt;li&gt;&lt;strong&gt;Better browser handling of some MIME types.&lt;/strong&gt; When
9345 displaying a text/plain file in my Debian browser, it will propose to
9346 start emacs to show it. If I remember correctly, when doing the same
9347 in Kunbutu it show the file as a text file in the browser. At least I
9348 know Opera will show text files within the browser. I much prefer the
9349 latter behaviour.&lt;/li&gt;
9350
9351 &lt;/ol&gt;
9352
9353 &lt;p&gt;There are other nice features as well, like the simplified suite
9354 upgrader, but given that I am the one mostly doing the dist-upgrade,
9355 it do not matter much.&lt;/p&gt;
9356
9357 &lt;p&gt;I really hope we could get these features in place for the next
9358 Debian release. It would require the coordinated effort of several
9359 maintainers, but would make the end user experience a lot better.&lt;/p&gt;
9360 </description>
9361 </item>
9362
9363 <item>
9364 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze</title>
9365 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</link>
9366 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html</guid>
9367 <pubDate>Tue, 26 Jul 2011 12:25:00 +0200</pubDate>
9368 <description>&lt;p&gt;The Norwegian &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/A&gt;
9369 site is build on Debian/Squeeze, and this platform was chosen because
9370 I am most familiar with Debian (being a Debian Developer for around 10
9371 years) because it is the latest stable Debian release which should get
9372 security support for a few years.&lt;/p&gt;
9373
9374 &lt;p&gt;The web service is written in Perl, and depend on some perl modules
9375 that are missing in Debian at the moment. It would be great if these
9376 modules were added to the Debian archive, allowing anyone to set up
9377 their own &lt;a href=&quot;http://www.fixmystreet.com&quot;&gt;FixMyStreet&lt;/a&gt; clone
9378 in their own country using only Debian packages. The list of modules
9379 missing in Debian/Squeeze isn&#39;t very long, and I hope the perl group
9380 will find time to package the 12 modules Catalyst::Plugin::SmartURI,
9381 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
9382 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
9383 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
9384 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
9385 easier in the future.&lt;/p&gt;
9386
9387 &lt;p&gt;Thanks to the great tools in Debian, getting the missing modules
9388 installed on my server was a simple call to &#39;cpan2deb Module::Name&#39;
9389 and &#39;dpkg -i&#39; to install the resulting package. But this leave me
9390 with the responsibility of tracking security problems, which I really
9391 do not have time for.&lt;/p&gt;
9392 </description>
9393 </item>
9394
9395 <item>
9396 <title>A Norwegian FixMyStreet have kept me busy the last few weeks</title>
9397 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</link>
9398 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html</guid>
9399 <pubDate>Sun, 3 Apr 2011 22:50:00 +0200</pubDate>
9400 <description>&lt;p&gt;Here is a small update for my English readers. Most of my blog
9401 posts have been in Norwegian the last few weeks, so here is a short
9402 update in English.&lt;/p&gt;
9403
9404 &lt;p&gt;The kids still keep me too busy to get much free software work
9405 done, but I did manage to organise a project to get a Norwegian port
9406 of the British service
9407 &lt;a href=&quot;http://www.fixmystreet.com/&quot;&gt;FixMyStreet&lt;/a&gt; up and running,
9408 and it has been running for a month now. The entire project has been
9409 organised by me and two others. Around Christmas we gathered sponsors
9410 to fund the development work. In January I drafted a contract with
9411 &lt;a href=&quot;http://www.mysociety.org/&quot;&gt;mySociety&lt;/a&gt; on what to develop,
9412 and in February the development took place. Most of it involved
9413 converting the source to use GPS coordinates instead of British
9414 easting/northing, and the resulting code should be a lot easier to get
9415 running in any country by now. The Norwegian
9416 &lt;a href=&quot;http://www.fiksgatami.no/&quot;&gt;FiksGataMi&lt;/a&gt; is using
9417 &lt;a href=&quot;http://www.openstreetmap.org/&quot;&gt;OpenStreetmap&lt;/a&gt; as the map
9418 source and the source for administrative borders in Norway, and
9419 support for this had to be added/fixed.&lt;/p&gt;
9420
9421 &lt;p&gt;The Norwegian version went live March 3th, and we spent the weekend
9422 polishing the system before we announced it March 7th. The system is
9423 running on a KVM instance of Debian/Squeeze, and has seen almost 3000
9424 problem reports in a few weeks. Soon we hope to announce the Android
9425 and iPhone versions making it even easier to report problems with the
9426 public infrastructure.&lt;/p&gt;
9427
9428 &lt;p&gt;Perhaps something to consider for those of you in countries without
9429 such service?&lt;/p&gt;
9430 </description>
9431 </item>
9432
9433 <item>
9434 <title>Using NVD and CPE to track CVEs in locally maintained software</title>
9435 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</link>
9436 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html</guid>
9437 <pubDate>Fri, 28 Jan 2011 15:40:00 +0100</pubDate>
9438 <description>&lt;p&gt;The last few days I have looked at ways to track open security
9439 issues here at my work with the University of Oslo. My idea is that
9440 it should be possible to use the information about security issues
9441 available on the Internet, and check our locally
9442 maintained/distributed software against this information. It should
9443 allow us to verify that no known security issues are forgotten. The
9444 CVE database listing vulnerabilities seem like a great central point,
9445 and by using the package lists from Debian mapped to CVEs provided by
9446 the testing security team, I believed it should be possible to figure
9447 out which security holes were present in our free software
9448 collection.&lt;/p&gt;
9449
9450 &lt;p&gt;After reading up on the topic, it became obvious that the first
9451 building block is to be able to name software packages in a unique and
9452 consistent way across data sources. I considered several ways to do
9453 this, for example coming up with my own naming scheme like using URLs
9454 to project home pages or URLs to the Freshmeat entries, or using some
9455 existing naming scheme. And it seem like I am not the first one to
9456 come across this problem, as MITRE already proposed and implemented a
9457 solution. Enter the &lt;a href=&quot;http://cpe.mitre.org/index.html&quot;&gt;Common
9458 Platform Enumeration&lt;/a&gt; dictionary, a vocabulary for referring to
9459 software, hardware and other platform components. The CPE ids are
9460 mapped to CVEs in the &lt;a href=&quot;http://web.nvd.nist.gov/&quot;&gt;National
9461 Vulnerability Database&lt;/a&gt;, allowing me to look up know security
9462 issues for any CPE name. With this in place, all I need to do is to
9463 locate the CPE id for the software packages we use at the university.
9464 This is fairly trivial (I google for &#39;cve cpe $package&#39; and check the
9465 NVD entry if a CVE for the package exist).&lt;/p&gt;
9466
9467 &lt;p&gt;To give you an example. The GNU gzip source package have the CPE
9468 name cpe:/a:gnu:gzip. If the old version 1.3.3 was the package to
9469 check out, one could look up
9470 &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
9471 in NVD&lt;/a&gt; and get a list of 6 security holes with public CVE entries.
9472 The most recent one is
9473 &lt;a href=&quot;http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2010-0001&quot;&gt;CVE-2010-0001&lt;/a&gt;,
9474 and at the bottom of the NVD page for this vulnerability the complete
9475 list of affected versions is provided.&lt;/p&gt;
9476
9477 &lt;p&gt;The NVD database of CVEs is also available as a XML dump, allowing
9478 for offline processing of issues. Using this dump, I&#39;ve written a
9479 small script taking a list of CPEs as input and list all CVEs
9480 affecting the packages represented by these CPEs. One give it CPEs
9481 with version numbers as specified above and get a list of open
9482 security issues out.&lt;/p&gt;
9483
9484 &lt;p&gt;Of course for this approach to be useful, the quality of the NVD
9485 information need to be high. For that to happen, I believe as many as
9486 possible need to use and contribute to the NVD database. I notice
9487 RHEL is providing
9488 &lt;a href=&quot;https://www.redhat.com/security/data/metrics/rhsamapcpe.txt&quot;&gt;a
9489 map from CVE to CPE&lt;/a&gt;, indicating that they are using the CPE
9490 information. I&#39;m not aware of Debian and Ubuntu doing the same.&lt;/p&gt;
9491
9492 &lt;p&gt;To get an idea about the quality for free software, I spent some
9493 time making it possible to compare the CVE database from Debian with
9494 the CVE database in NVD. The result look fairly good, but there are
9495 some inconsistencies in NVD (same software package having several
9496 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
9497 Debian believe are affected by a CVE). Hope to find time to improve
9498 the quality of NVD, but that require being able to get in touch with
9499 someone maintaining it. So far my three emails with questions and
9500 corrections have not seen any reply, but I hope contact can be
9501 established soon.&lt;/p&gt;
9502
9503 &lt;p&gt;An interesting application for CPEs is cross platform package
9504 mapping. It would be useful to know which packages in for example
9505 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
9506 this would be trivial if all linux distributions provided CPE entries
9507 for their packages.&lt;/p&gt;
9508 </description>
9509 </item>
9510
9511 <item>
9512 <title>Which module is loaded for a given PCI and USB device?</title>
9513 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</link>
9514 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html</guid>
9515 <pubDate>Sun, 23 Jan 2011 00:20:00 +0100</pubDate>
9516 <description>&lt;p&gt;In the
9517 &lt;a href=&quot;http://packages.qa.debian.org/discover-data&quot;&gt;discover-data&lt;/a&gt;
9518 package in Debian, there is a script to report useful information
9519 about the running hardware for use when people report missing
9520 information. One part of this script that I find very useful when
9521 debugging hardware problems, is the part mapping loaded kernel module
9522 to the PCI device it claims. It allow me to quickly see if the kernel
9523 module I expect is driving the hardware I am struggling with. To see
9524 the output, make sure discover-data is installed and run
9525 &lt;tt&gt;/usr/share/bug/discover-data 3&gt;&amp;1&lt;/tt&gt;. The relevant output on
9526 one of my machines like this:&lt;/p&gt;
9527
9528 &lt;pre&gt;
9529 loaded modules:
9530 10de:03eb i2c_nforce2
9531 10de:03f1 ohci_hcd
9532 10de:03f2 ehci_hcd
9533 10de:03f0 snd_hda_intel
9534 10de:03ec pata_amd
9535 10de:03f6 sata_nv
9536 1022:1103 k8temp
9537 109e:036e bttv
9538 109e:0878 snd_bt87x
9539 11ab:4364 sky2
9540 &lt;/pre&gt;
9541
9542 &lt;p&gt;The code in question look like this, slightly modified for
9543 readability and to drop the output to file descriptor 3:&lt;/p&gt;
9544
9545 &lt;pre&gt;
9546 if [ -d /sys/bus/pci/devices/ ] ; then
9547 echo loaded pci modules:
9548 (
9549 cd /sys/bus/pci/devices/
9550 for address in * ; do
9551 if [ -d &quot;$address/driver/module&quot; ] ; then
9552 module=`cd $address/driver/module ; pwd -P | xargs basename`
9553 if grep -q &quot;^$module &quot; /proc/modules ; then
9554 address=$(echo $address |sed s/0000://)
9555 id=`lspci -n -s $address | tail -n 1 | awk &#39;{print $3}&#39;`
9556 echo &quot;$id $module&quot;
9557 fi
9558 fi
9559 done
9560 )
9561 echo
9562 fi
9563 &lt;/pre&gt;
9564
9565 &lt;p&gt;Similar code could be used to extract USB device module
9566 mappings:&lt;/p&gt;
9567
9568 &lt;pre&gt;
9569 if [ -d /sys/bus/usb/devices/ ] ; then
9570 echo loaded usb modules:
9571 (
9572 cd /sys/bus/usb/devices/
9573 for address in * ; do
9574 if [ -d &quot;$address/driver/module&quot; ] ; then
9575 module=`cd $address/driver/module ; pwd -P | xargs basename`
9576 if grep -q &quot;^$module &quot; /proc/modules ; then
9577 address=$(echo $address |sed s/0000://)
9578 id=$(lsusb -s $address | tail -n 1 | awk &#39;{print $6}&#39;)
9579 if [ &quot;$id&quot; ] ; then
9580 echo &quot;$id $module&quot;
9581 fi
9582 fi
9583 fi
9584 done
9585 )
9586 echo
9587 fi
9588 &lt;/pre&gt;
9589
9590 &lt;p&gt;This might perhaps be something to include in other tools as
9591 well.&lt;/p&gt;
9592 </description>
9593 </item>
9594
9595 <item>
9596 <title>How to test if a laptop is working with Linux</title>
9597 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</link>
9598 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html</guid>
9599 <pubDate>Wed, 22 Dec 2010 14:55:00 +0100</pubDate>
9600 <description>&lt;p&gt;The last few days I have spent at work here at the &lt;a
9601 href=&quot;http://www.uio.no/&quot;&gt;University of Oslo&lt;/a&gt; testing if the new
9602 batch of computers will work with Linux. Every year for the last few
9603 years the university have organised shared bid of a few thousand
9604 computers, and this year HP won the bid. Two different desktops and
9605 five different laptops are on the list this year. We in the UNIX
9606 group want to know which one of these computers work well with RHEL
9607 and Ubuntu, the two Linux distributions we currently handle at the
9608 university.&lt;/p&gt;
9609
9610 &lt;p&gt;My test method is simple, and I share it here to get feedback and
9611 perhaps inspire others to test hardware as well. To test, I PXE
9612 install the OS version of choice, and log in as my normal user and run
9613 a few applications and plug in selected pieces of hardware. When
9614 something fail, I make a note about this in the test matrix and move
9615 on. If I have some spare time I try to report the bug to the OS
9616 vendor, but as I only have the machines for a short time, I rarely
9617 have the time to do this for all the problems I find.&lt;/p&gt;
9618
9619 &lt;p&gt;Anyway, to get to the point of this post. Here is the simple tests
9620 I perform on a new model.&lt;/p&gt;
9621
9622 &lt;ul&gt;
9623
9624 &lt;li&gt;Is PXE installation working? I&#39;m testing with RHEL6, Ubuntu Lucid
9625 and Ubuntu Maverik at the moment. If I feel like it, I also test with
9626 RHEL5 and Debian Edu/Squeeze.&lt;/li&gt;
9627
9628 &lt;li&gt;Is X.org working? If the graphical login screen show up after
9629 installation, X.org is working.&lt;/li&gt;
9630
9631 &lt;li&gt;Is hardware accelerated OpenGL working? Running glxgears (in
9632 package mesa-utils on Ubuntu) and writing down the frames per second
9633 reported by the program.&lt;/li&gt;
9634
9635 &lt;li&gt;Is sound working? With Gnome and KDE, a sound is played when
9636 logging in, and if I can hear this the test is successful. If there
9637 are several audio exits on the machine, I try them all and check if
9638 the Gnome/KDE audio mixer can control where to send the sound. I
9639 normally test this by playing
9640 &lt;a href=&quot;http://www.nuug.no/aktiviteter/20101012-chef/ &quot;&gt;a HTML5
9641 video&lt;/a&gt; in Firefox/Iceweasel.&lt;/li&gt;
9642
9643 &lt;li&gt;Is the USB subsystem working? I test this by plugging in a USB
9644 memory stick and see if Gnome/KDE notices this.&lt;/li&gt;
9645
9646 &lt;li&gt;Is the CD/DVD player working? I test this by inserting any CD/DVD
9647 I have lying around, and see if Gnome/KDE notices this.&lt;/li&gt;
9648
9649 &lt;li&gt;Is any built in camera working? Test using cheese, and see if a
9650 picture from the v4l device show up.&lt;/li&gt;
9651
9652 &lt;li&gt;Is bluetooth working? Use the Gnome/KDE browsing tool to see if
9653 any bluetooth devices are discovered. In my office, I normally see a
9654 few.&lt;/li&gt;
9655
9656 &lt;li&gt;For laptops, is the SD or Compaq Flash reader working. I have
9657 memory modules lying around, and stick them in and see if Gnome/KDE
9658 notice this.&lt;/li&gt;
9659
9660 &lt;li&gt;For laptops, is suspend/hibernate working? I&#39;m testing if the
9661 special button work, and if the laptop continue to work after
9662 resume.&lt;/li&gt;
9663
9664 &lt;li&gt;For laptops, is the extra buttons working, like audio level,
9665 adjusting background light, switching on/off external video output,
9666 switching on/off wifi, bluetooth, etc? The set of buttons differ from
9667 laptop to laptop, so I just write down which are working and which are
9668 not.&lt;/li&gt;
9669
9670 &lt;li&gt;Some laptops have smart card readers, finger print readers,
9671 acceleration sensors etc. I rarely test these, as I do not know how
9672 to quickly test if they are working or not, so I only document their
9673 existence.&lt;/li&gt;
9674
9675 &lt;/ul&gt;
9676
9677 &lt;p&gt;By now I suspect you are really curious what the test results are
9678 for the HP machines I am testing. I&#39;m not done yet, so I will report
9679 the test results later. For now I can report that HP 8100 Elite work
9680 fine, and hibernation fail with HP EliteBook 8440p on Ubuntu Lucid,
9681 and audio fail on RHEL6. Ubuntu Maverik worked with 8440p. As you
9682 can see, I have most machines left to test. One interesting
9683 observation is that Ubuntu Lucid has almost twice the frame rate than
9684 RHEL6 with glxgears. No idea why.&lt;/p&gt;
9685 </description>
9686 </item>
9687
9688 <item>
9689 <title>Some thoughts on BitCoins</title>
9690 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</link>
9691 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html</guid>
9692 <pubDate>Sat, 11 Dec 2010 15:10:00 +0100</pubDate>
9693 <description>&lt;p&gt;As I continue to explore
9694 &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;, I&#39;ve starting to wonder
9695 what properties the system have, and how it will be affected by laws
9696 and regulations here in Norway. Here are some random notes.&lt;/p&gt;
9697
9698 &lt;p&gt;One interesting thing to note is that since the transactions are
9699 verified using a peer to peer network, all details about a transaction
9700 is known to everyone. This means that if a BitCoin address has been
9701 published like I did with mine in my initial post about BitCoin, it is
9702 possible for everyone to see how many BitCoins have been transfered to
9703 that address. There is even a web service to look at the details for
9704 all transactions. There I can see that my address
9705 &lt;a href=&quot;http://blockexplorer.com/address/15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&quot;&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/a&gt;
9706 have received 16.06 Bitcoin, the
9707 &lt;a href=&quot;http://blockexplorer.com/address/1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&quot;&gt;1LfdGnGuWkpSJgbQySxxCWhv8MHqvwst3&lt;/a&gt;
9708 address of Simon Phipps have received 181.97 BitCoin and the address
9709 &lt;a href=&quot;http://blockexplorer.com/address/1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&quot;&gt;1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt&lt;/A&gt;
9710 of EFF have received 2447.38 BitCoins so far. Thank you to each and
9711 every one of you that donated bitcoins to support my activity. The
9712 fact that anyone can see how much money was transfered to a given
9713 address make it more obvious why the BitCoin community recommend to
9714 generate and hand out a new address for each transaction. I&#39;m told
9715 there is no way to track which addresses belong to a given person or
9716 organisation without the person or organisation revealing it
9717 themselves, as Simon, EFF and I have done.&lt;/p&gt;
9718
9719 &lt;p&gt;In Norway, and in most other countries, there are laws and
9720 regulations limiting how much money one can transfer across the border
9721 without declaring it. There are money laundering, tax and accounting
9722 laws and regulations I would expect to apply to the use of BitCoin.
9723 If the Skolelinux foundation
9724 (&lt;a href=&quot;http://linuxiskolen.no/slxdebianlabs/donations.html&quot;&gt;SLX
9725 Debian Labs&lt;/a&gt;) were to accept donations in BitCoin in addition to
9726 normal bank transfers like EFF is doing, how should this be accounted?
9727 Given that it is impossible to know if money can cross the border or
9728 not, should everything or nothing be declared? What exchange rate
9729 should be used when calculating taxes? Would receivers have to pay
9730 income tax if the foundation were to pay Skolelinux contributors in
9731 BitCoin? I have no idea, but it would be interesting to know.&lt;/p&gt;
9732
9733 &lt;p&gt;For a currency to be useful and successful, it must be trusted and
9734 accepted by a lot of users. It must be possible to get easy access to
9735 the currency (as a wage or using currency exchanges), and it must be
9736 easy to spend it. At the moment BitCoin seem fairly easy to get
9737 access to, but there are very few places to spend it. I am not really
9738 a regular user of any of the vendor types currently accepting BitCoin,
9739 so I wonder when my kind of shop would start accepting BitCoins. I
9740 would like to buy electronics, travels and subway tickets, not herbs
9741 and books. :) The currency is young, and this will improve over time
9742 if it become popular, but I suspect regular banks will start to lobby
9743 to get BitCoin declared illegal if it become popular. I&#39;m sure they
9744 will claim it is helping fund terrorism and money laundering (which
9745 probably would be true, as is any currency in existence), but I
9746 believe the problems should be solved elsewhere and not by blaming
9747 currencies.&lt;/p&gt;
9748
9749 &lt;p&gt;The process of creating new BitCoins is called mining, and it is
9750 CPU intensive process that depend on a bit of luck as well (as one is
9751 competing against all the other miners currently spending CPU cycles
9752 to see which one get the next lump of cash). The &quot;winner&quot; get 50
9753 BitCoin when this happen. Yesterday I came across the obvious way to
9754 join forces to increase ones changes of getting at least some coins,
9755 by coordinating the work on mining BitCoins across several machines
9756 and people, and sharing the result if one is lucky and get the 50
9757 BitCoins. Check out
9758 &lt;a href=&quot;http://www.bluishcoder.co.nz/bitcoin-pool/&quot;&gt;BitCoin Pool&lt;/a&gt;
9759 if this sounds interesting. I have not had time to try to set up a
9760 machine to participate there yet, but have seen that running on ones
9761 own for a few days have not yield any BitCoins througth mining
9762 yet.&lt;/p&gt;
9763
9764 &lt;p&gt;Update 2010-12-15: Found an &lt;a
9765 href=&quot;http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi&quot;&gt;interesting
9766 criticism&lt;/a&gt; of bitcoin. Not quite sure how valid it is, but thought
9767 it was interesting to read. The arguments presented seem to be
9768 equally valid for gold, which was used as a currency for many years.&lt;/p&gt;
9769 </description>
9770 </item>
9771
9772 <item>
9773 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money</title>
9774 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</link>
9775 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html</guid>
9776 <pubDate>Fri, 10 Dec 2010 08:20:00 +0100</pubDate>
9777 <description>&lt;p&gt;With this weeks lawless
9778 &lt;a href=&quot;http://www.salon.com/news/opinion/glenn_greenwald/2010/12/06/wikileaks/index.html&quot;&gt;governmental
9779 attacks&lt;/a&gt; on Wikileak and
9780 &lt;a href=&quot;http://www.salon.com/technology/dan_gillmor/2010/12/06/war_on_speech&quot;&gt;free
9781 speech&lt;/a&gt;, it has become obvious that PayPal, visa and mastercard can
9782 not be trusted to handle money transactions.
9783 A blog post from
9784 &lt;a href=&quot;http://webmink.com/2010/12/06/now-accepting-bitcoin/&quot;&gt;Simon
9785 Phipps on bitcoin&lt;/a&gt; reminded me about a project that a friend of
9786 mine mentioned earlier. I decided to follow Simon&#39;s example, and get
9787 involved with &lt;a href=&quot;http://www.bitcoin.org/&quot;&gt;BitCoin&lt;/a&gt;. I got
9788 some help from my friend to get it all running, and he even handed me
9789 some bitcoins to get started. I even donated a few bitcoins to Simon
9790 for helping me remember BitCoin.&lt;/p&gt;
9791
9792 &lt;p&gt;So, what is bitcoins, you probably wonder? It is a digital
9793 crypto-currency, decentralised and handled using peer-to-peer
9794 networks. It allows anonymous transactions and prohibits central
9795 control over the transactions, making it impossible for governments
9796 and companies alike to block donations and other transactions. The
9797 source is free software, and while the key dependency wxWidgets 2.9
9798 for the graphical user interface is missing in Debian, the command
9799 line client builds just fine. Hopefully Jonas
9800 &lt;a href=&quot;http://bugs.debian.org/578157&quot;&gt;will get the package into
9801 Debian&lt;/a&gt; soon.&lt;/p&gt;
9802
9803 &lt;p&gt;Bitcoins can be converted to other currencies, like USD and EUR.
9804 There are &lt;a href=&quot;http://www.bitcoin.org/trade&quot;&gt;companies accepting
9805 bitcoins&lt;/a&gt; when selling services and goods, and there are even
9806 currency &quot;stock&quot; markets where the exchange rate is decided. There
9807 are not many users so far, but the concept seems promising. If you
9808 want to get started and lack a friend with any bitcoins to spare,
9809 you can even get
9810 &lt;a href=&quot;https://freebitcoins.appspot.com/&quot;&gt;some for free&lt;/a&gt; (0.05
9811 bitcoin at the time of writing). Use
9812 &lt;a href=&quot;http://www.bitcoinwatch.com/&quot;&gt;BitcoinWatch&lt;/a&gt; to keep an eye
9813 on the current exchange rates.&lt;/p&gt;
9814
9815 &lt;p&gt;As an experiment, I have decided to set up bitcoind on one of my
9816 machines. If you want to support my activity, please send Bitcoin
9817 donations to the address
9818 &lt;b&gt;15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b&lt;/b&gt;. Thank you!&lt;/p&gt;
9819 </description>
9820 </item>
9821
9822 <item>
9823 <title>Why isn&#39;t Debian Edu using VLC?</title>
9824 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</link>
9825 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html</guid>
9826 <pubDate>Sat, 27 Nov 2010 11:30:00 +0100</pubDate>
9827 <description>&lt;p&gt;In the latest issue of Linux Journal, the readers choices were
9828 presented, and the winner among the multimedia player were VLC.
9829 Personally, I like VLC, and it is my player of choice when I first try
9830 to play a video file or stream. Only if VLC fail will I drag out
9831 gmplayer to see if it can do better. The reason is mostly the failure
9832 model and trust. When VLC fail, it normally pop up a error message
9833 reporting the problem. When mplayer fail, it normally segfault or
9834 just hangs. The latter failure mode drain my trust in the program.&lt;p&gt;
9835
9836 &lt;p&gt;But even if VLC is my player of choice, we have choosen to use
9837 mplayer in &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
9838 Edu/Skolelinux&lt;/a&gt;. The reason is simple. We need a good browser
9839 plugin to play web videos seamlessly, and the VLC browser plugin is
9840 not very good. For example, it lack in-line control buttons, so there
9841 is no way for the user to pause the video. Also, when I
9842 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;last
9843 tested the browser plugins&lt;/a&gt; available in Debian, the VLC plugin
9844 failed on several video pages where mplayer based plugins worked. If
9845 the browser plugin for VLC was as good as the gecko-mediaplayer
9846 package (which uses mplayer), we would switch.&lt;/P&gt;
9847
9848 &lt;p&gt;While VLC is a good player, its user interface is slightly
9849 annoying. The most annoying feature is its inconsistent use of
9850 keyboard shortcuts. When the player is in full screen mode, its
9851 shortcuts are different from when it is playing the video in a window.
9852 For example, space only work as pause when in full screen mode. I
9853 wish it had consisten shortcuts and that space also would work when in
9854 window mode. Another nice shortcut in gmplayer is [enter] to restart
9855 the current video. It is very nice when playing short videos from the
9856 web and want to restart it when new people arrive to have a look at
9857 what is going on.&lt;/p&gt;
9858 </description>
9859 </item>
9860
9861 <item>
9862 <title>Lenny-&gt;Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove</title>
9863 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html</link>
9864 <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>
9865 <pubDate>Mon, 22 Nov 2010 14:15:00 +0100</pubDate>
9866 <description>&lt;p&gt;Michael Biebl suggested to me on IRC, that I changed my automated
9867 upgrade testing of the
9868 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
9869 Gnome and KDE Desktop&lt;/a&gt; to do &lt;tt&gt;apt-get autoremove&lt;/tt&gt; when using apt-get.
9870 This seem like a very good idea, so I adjusted by test scripts and
9871 can now present the updated result from today:&lt;/p&gt;
9872
9873 &lt;p&gt;This is for Gnome:&lt;/p&gt;
9874
9875 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
9876
9877 &lt;blockquote&gt;&lt;p&gt;
9878 apache2.2-bin
9879 aptdaemon
9880 baobab
9881 binfmt-support
9882 browser-plugin-gnash
9883 cheese-common
9884 cli-common
9885 cups-pk-helper
9886 dmz-cursor-theme
9887 empathy
9888 empathy-common
9889 freedesktop-sound-theme
9890 freeglut3
9891 gconf-defaults-service
9892 gdm-themes
9893 gedit-plugins
9894 geoclue
9895 geoclue-hostip
9896 geoclue-localnet
9897 geoclue-manual
9898 geoclue-yahoo
9899 gnash
9900 gnash-common
9901 gnome
9902 gnome-backgrounds
9903 gnome-cards-data
9904 gnome-codec-install
9905 gnome-core
9906 gnome-desktop-environment
9907 gnome-disk-utility
9908 gnome-screenshot
9909 gnome-search-tool
9910 gnome-session-canberra
9911 gnome-system-log
9912 gnome-themes-extras
9913 gnome-themes-more
9914 gnome-user-share
9915 gstreamer0.10-fluendo-mp3
9916 gstreamer0.10-tools
9917 gtk2-engines
9918 gtk2-engines-pixbuf
9919 gtk2-engines-smooth
9920 hamster-applet
9921 libapache2-mod-dnssd
9922 libapr1
9923 libaprutil1
9924 libaprutil1-dbd-sqlite3
9925 libaprutil1-ldap
9926 libart2.0-cil
9927 libboost-date-time1.42.0
9928 libboost-python1.42.0
9929 libboost-thread1.42.0
9930 libchamplain-0.4-0
9931 libchamplain-gtk-0.4-0
9932 libcheese-gtk18
9933 libclutter-gtk-0.10-0
9934 libcryptui0
9935 libdiscid0
9936 libelf1
9937 libepc-1.0-2
9938 libepc-common
9939 libepc-ui-1.0-2
9940 libfreerdp-plugins-standard
9941 libfreerdp0
9942 libgconf2.0-cil
9943 libgdata-common
9944 libgdata7
9945 libgdu-gtk0
9946 libgee2
9947 libgeoclue0
9948 libgexiv2-0
9949 libgif4
9950 libglade2.0-cil
9951 libglib2.0-cil
9952 libgmime2.4-cil
9953 libgnome-vfs2.0-cil
9954 libgnome2.24-cil
9955 libgnomepanel2.24-cil
9956 libgpod-common
9957 libgpod4
9958 libgtk2.0-cil
9959 libgtkglext1
9960 libgtksourceview2.0-common
9961 libmono-addins-gui0.2-cil
9962 libmono-addins0.2-cil
9963 libmono-cairo2.0-cil
9964 libmono-corlib2.0-cil
9965 libmono-i18n-west2.0-cil
9966 libmono-posix2.0-cil
9967 libmono-security2.0-cil
9968 libmono-sharpzip2.84-cil
9969 libmono-system2.0-cil
9970 libmtp8
9971 libmusicbrainz3-6
9972 libndesk-dbus-glib1.0-cil
9973 libndesk-dbus1.0-cil
9974 libopal3.6.8
9975 libpolkit-gtk-1-0
9976 libpt2.6.7
9977 libpython2.6
9978 librpm1
9979 librpmio1
9980 libsdl1.2debian
9981 libsrtp0
9982 libssh-4
9983 libtelepathy-farsight0
9984 libtelepathy-glib0
9985 libtidy-0.99-0
9986 media-player-info
9987 mesa-utils
9988 mono-2.0-gac
9989 mono-gac
9990 mono-runtime
9991 nautilus-sendto
9992 nautilus-sendto-empathy
9993 p7zip-full
9994 pkg-config
9995 python-aptdaemon
9996 python-aptdaemon-gtk
9997 python-axiom
9998 python-beautifulsoup
9999 python-bugbuddy
10000 python-clientform
10001 python-coherence
10002 python-configobj
10003 python-crypto
10004 python-cupshelpers
10005 python-elementtree
10006 python-epsilon
10007 python-evolution
10008 python-feedparser
10009 python-gdata
10010 python-gdbm
10011 python-gst0.10
10012 python-gtkglext1
10013 python-gtksourceview2
10014 python-httplib2
10015 python-louie
10016 python-mako
10017 python-markupsafe
10018 python-mechanize
10019 python-nevow
10020 python-notify
10021 python-opengl
10022 python-openssl
10023 python-pam
10024 python-pkg-resources
10025 python-pyasn1
10026 python-pysqlite2
10027 python-rdflib
10028 python-serial
10029 python-tagpy
10030 python-twisted-bin
10031 python-twisted-conch
10032 python-twisted-core
10033 python-twisted-web
10034 python-utidylib
10035 python-webkit
10036 python-xdg
10037 python-zope.interface
10038 remmina
10039 remmina-plugin-data
10040 remmina-plugin-rdp
10041 remmina-plugin-vnc
10042 rhythmbox-plugin-cdrecorder
10043 rhythmbox-plugins
10044 rpm-common
10045 rpm2cpio
10046 seahorse-plugins
10047 shotwell
10048 software-center
10049 system-config-printer-udev
10050 telepathy-gabble
10051 telepathy-mission-control-5
10052 telepathy-salut
10053 tomboy
10054 totem
10055 totem-coherence
10056 totem-mozilla
10057 totem-plugins
10058 transmission-common
10059 xdg-user-dirs
10060 xdg-user-dirs-gtk
10061 xserver-xephyr
10062 &lt;/p&gt;&lt;/blockquote&gt;
10063
10064 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10065
10066 &lt;blockquote&gt;&lt;p&gt;
10067 cheese
10068 ekiga
10069 eog
10070 epiphany-extensions
10071 evolution-exchange
10072 fast-user-switch-applet
10073 file-roller
10074 gcalctool
10075 gconf-editor
10076 gdm
10077 gedit
10078 gedit-common
10079 gnome-games
10080 gnome-games-data
10081 gnome-nettool
10082 gnome-system-tools
10083 gnome-themes
10084 gnuchess
10085 gucharmap
10086 guile-1.8-libs
10087 libavahi-ui0
10088 libdmx1
10089 libgalago3
10090 libgtk-vnc-1.0-0
10091 libgtksourceview2.0-0
10092 liblircclient0
10093 libsdl1.2debian-alsa
10094 libspeexdsp1
10095 libsvga1
10096 rhythmbox
10097 seahorse
10098 sound-juicer
10099 system-config-printer
10100 totem-common
10101 transmission-gtk
10102 vinagre
10103 vino
10104 &lt;/p&gt;&lt;/blockquote&gt;
10105
10106 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10107
10108 &lt;blockquote&gt;&lt;p&gt;
10109 gstreamer0.10-gnomevfs
10110 &lt;/p&gt;&lt;/blockquote&gt;
10111
10112 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10113
10114 &lt;blockquote&gt;&lt;p&gt;
10115 [nothing]
10116 &lt;/p&gt;&lt;/blockquote&gt;
10117
10118 &lt;p&gt;This is for KDE:&lt;/p&gt;
10119
10120 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10121
10122 &lt;blockquote&gt;&lt;p&gt;
10123 ksmserver
10124 &lt;/p&gt;&lt;/blockquote&gt;
10125
10126 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10127
10128 &lt;blockquote&gt;&lt;p&gt;
10129 kwin
10130 network-manager-kde
10131 &lt;/p&gt;&lt;/blockquote&gt;
10132
10133 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10134
10135 &lt;blockquote&gt;&lt;p&gt;
10136 arts
10137 dolphin
10138 freespacenotifier
10139 google-gadgets-gst
10140 google-gadgets-xul
10141 kappfinder
10142 kcalc
10143 kcharselect
10144 kde-core
10145 kde-plasma-desktop
10146 kde-standard
10147 kde-window-manager
10148 kdeartwork
10149 kdeartwork-emoticons
10150 kdeartwork-style
10151 kdeartwork-theme-icon
10152 kdebase
10153 kdebase-apps
10154 kdebase-workspace
10155 kdebase-workspace-bin
10156 kdebase-workspace-data
10157 kdeeject
10158 kdelibs
10159 kdeplasma-addons
10160 kdeutils
10161 kdewallpapers
10162 kdf
10163 kfloppy
10164 kgpg
10165 khelpcenter4
10166 kinfocenter
10167 konq-plugins-l10n
10168 konqueror-nsplugins
10169 kscreensaver
10170 kscreensaver-xsavers
10171 ktimer
10172 kwrite
10173 libgle3
10174 libkde4-ruby1.8
10175 libkonq5
10176 libkonq5-templates
10177 libnetpbm10
10178 libplasma-ruby
10179 libplasma-ruby1.8
10180 libqt4-ruby1.8
10181 marble-data
10182 marble-plugins
10183 netpbm
10184 nuvola-icon-theme
10185 plasma-dataengines-workspace
10186 plasma-desktop
10187 plasma-desktopthemes-artwork
10188 plasma-runners-addons
10189 plasma-scriptengine-googlegadgets
10190 plasma-scriptengine-python
10191 plasma-scriptengine-qedje
10192 plasma-scriptengine-ruby
10193 plasma-scriptengine-webkit
10194 plasma-scriptengines
10195 plasma-wallpapers-addons
10196 plasma-widget-folderview
10197 plasma-widget-networkmanagement
10198 ruby
10199 sweeper
10200 update-notifier-kde
10201 xscreensaver-data-extra
10202 xscreensaver-gl
10203 xscreensaver-gl-extra
10204 xscreensaver-screensaver-bsod
10205 &lt;/p&gt;&lt;/blockquote&gt;
10206
10207 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10208
10209 &lt;blockquote&gt;&lt;p&gt;
10210 ark
10211 google-gadgets-common
10212 google-gadgets-qt
10213 htdig
10214 kate
10215 kdebase-bin
10216 kdebase-data
10217 kdepasswd
10218 kfind
10219 klipper
10220 konq-plugins
10221 konqueror
10222 ksysguard
10223 ksysguardd
10224 libarchive1
10225 libcln6
10226 libeet1
10227 libeina-svn-06
10228 libggadget-1.0-0b
10229 libggadget-qt-1.0-0b
10230 libgps19
10231 libkdecorations4
10232 libkephal4
10233 libkonq4
10234 libkonqsidebarplugin4a
10235 libkscreensaver5
10236 libksgrd4
10237 libksignalplotter4
10238 libkunitconversion4
10239 libkwineffects1a
10240 libmarblewidget4
10241 libntrack-qt4-1
10242 libntrack0
10243 libplasma-geolocation-interface4
10244 libplasmaclock4a
10245 libplasmagenericshell4
10246 libprocesscore4a
10247 libprocessui4a
10248 libqalculate5
10249 libqedje0a
10250 libqtruby4shared2
10251 libqzion0a
10252 libruby1.8
10253 libscim8c2a
10254 libsmokekdecore4-3
10255 libsmokekdeui4-3
10256 libsmokekfile3
10257 libsmokekhtml3
10258 libsmokekio3
10259 libsmokeknewstuff2-3
10260 libsmokeknewstuff3-3
10261 libsmokekparts3
10262 libsmokektexteditor3
10263 libsmokekutils3
10264 libsmokenepomuk3
10265 libsmokephonon3
10266 libsmokeplasma3
10267 libsmokeqtcore4-3
10268 libsmokeqtdbus4-3
10269 libsmokeqtgui4-3
10270 libsmokeqtnetwork4-3
10271 libsmokeqtopengl4-3
10272 libsmokeqtscript4-3
10273 libsmokeqtsql4-3
10274 libsmokeqtsvg4-3
10275 libsmokeqttest4-3
10276 libsmokeqtuitools4-3
10277 libsmokeqtwebkit4-3
10278 libsmokeqtxml4-3
10279 libsmokesolid3
10280 libsmokesoprano3
10281 libtaskmanager4a
10282 libtidy-0.99-0
10283 libweather-ion4a
10284 libxklavier16
10285 libxxf86misc1
10286 okteta
10287 oxygencursors
10288 plasma-dataengines-addons
10289 plasma-scriptengine-superkaramba
10290 plasma-widget-lancelot
10291 plasma-widgets-addons
10292 plasma-widgets-workspace
10293 polkit-kde-1
10294 ruby1.8
10295 systemsettings
10296 update-notifier-common
10297 &lt;/p&gt;&lt;/blockquote&gt;
10298
10299 &lt;p&gt;Running apt-get autoremove made the results using apt-get and
10300 aptitude a bit more similar, but there are still quite a lott of
10301 differences. I have no idea what packages should be installed after
10302 the upgrade, but hope those that do can have a look.&lt;/p&gt;
10303 </description>
10304 </item>
10305
10306 <item>
10307 <title>Migrating Xen virtual machines using LVM to KVM using disk images</title>
10308 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</link>
10309 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html</guid>
10310 <pubDate>Mon, 22 Nov 2010 11:20:00 +0100</pubDate>
10311 <description>&lt;p&gt;Most of the computers in use by the
10312 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux project&lt;/a&gt;
10313 are virtual machines. And they have been Xen machines running on a
10314 fairly old IBM eserver xseries 345 machine, and we wanted to migrate
10315 them to KVM on a newer Dell PowerEdge 2950 host machine. This was a
10316 bit harder that it could have been, because we set up the Xen virtual
10317 machines to get the virtual partitions from LVM, which as far as I
10318 know is not supported by KVM. So to migrate, we had to convert
10319 several LVM logical volumes to partitions on a virtual disk file.&lt;/p&gt;
10320
10321 &lt;p&gt;I found
10322 &lt;a href=&quot;http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM&quot;&gt;a
10323 nice recipe&lt;/a&gt; to do this, and wrote the following script to do the
10324 migration. It uses qemu-img from the qemu package to make the disk
10325 image, parted to partition it, losetup and kpartx to present the disk
10326 image partions as devices, and dd to copy the data. I NFS mounted the
10327 new servers storage area on the old server to do the migration.&lt;/p&gt;
10328
10329 &lt;pre&gt;
10330 #!/bin/sh
10331
10332 # Based on
10333 # http://searchnetworking.techtarget.com.au/articles/35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
10334
10335 set -e
10336 set -x
10337
10338 if [ -z &quot;$1&quot; ] ; then
10339 echo &quot;Usage: $0 &amp;lt;hostname&amp;gt;&quot;
10340 exit 1
10341 else
10342 host=&quot;$1&quot;
10343 fi
10344
10345 if [ ! -e /dev/vg_data/$host-disk ] ; then
10346 echo &quot;error: unable to find LVM volume for $host&quot;
10347 exit 1
10348 fi
10349
10350 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
10351 disksize=$( lvs --units m | grep $host-disk | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
10352 swapsize=$( lvs --units m | grep $host-swap | awk &#39;{sum = sum + $4} END { print int(sum * 1.05) }&#39;)
10353 totalsize=$(( ( $disksize + $swapsize ) ))
10354
10355 img=$host.img
10356 #dd if=/dev/zero of=$img bs=1M count=$(( $disksize + $swapsize ))
10357 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
10358
10359 parted $img mklabel msdos
10360 parted $img mkpart primary linux-swap 0 $disksize
10361 parted $img mkpart primary ext2 $disksize $totalsize
10362 parted $img set 1 boot on
10363
10364 modprobe dm-mod
10365 losetup /dev/loop0 $img
10366 kpartx -a /dev/loop0
10367
10368 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=1M
10369 fsck.ext3 -f /dev/mapper/loop0p1 || true
10370 mkswap /dev/mapper/loop0p2
10371
10372 kpartx -d /dev/loop0
10373 losetup -d /dev/loop0
10374 &lt;/pre&gt;
10375
10376 &lt;p&gt;The script is perhaps so simple that it is not copyrightable, but
10377 if it is, it is licenced using GPL v2 or later at your discretion.&lt;/p&gt;
10378
10379 &lt;p&gt;After doing this, I booted a Debian CD in rescue mode in KVM with
10380 the new disk image attached, installed grub-pc and linux-image-686 and
10381 set up grub to boot from the disk image. After this, the KVM machines
10382 seem to work just fine.&lt;/p&gt;
10383 </description>
10384 </item>
10385
10386 <item>
10387 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop</title>
10388 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</link>
10389 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html</guid>
10390 <pubDate>Sat, 20 Nov 2010 22:50:00 +0100</pubDate>
10391 <description>&lt;p&gt;I&#39;m still running upgrade testing of the
10392 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;Lenny
10393 Gnome and KDE Desktop&lt;/a&gt;, but have not had time to spend on reporting the
10394 status. Here is a short update based on a test I ran 20101118.&lt;/p&gt;
10395
10396 &lt;p&gt;I still do not know what a correct migration should look like, so I
10397 report any differences between apt and aptitude and hope someone else
10398 can see if anything should be changed.&lt;/p&gt;
10399
10400 &lt;p&gt;This is for Gnome:&lt;/p&gt;
10401
10402 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10403
10404 &lt;blockquote&gt;&lt;p&gt;
10405 apache2.2-bin aptdaemon at-spi baobab binfmt-support
10406 browser-plugin-gnash cheese-common cli-common cpp-4.3 cups-pk-helper
10407 dmz-cursor-theme empathy empathy-common finger
10408 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
10409 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
10410 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
10411 gnome-cards-data gnome-codec-install gnome-core
10412 gnome-desktop-environment gnome-disk-utility gnome-screenshot
10413 gnome-search-tool gnome-session-canberra gnome-spell
10414 gnome-system-log gnome-themes-extras gnome-themes-more
10415 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
10416 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
10417 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
10418 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
10419 libart2.0-cil libatspi1.0-0 libboost-date-time1.42.0
10420 libboost-python1.42.0 libboost-thread1.42.0 libchamplain-0.4-0
10421 libchamplain-gtk-0.4-0 libcheese-gtk18 libclutter-gtk-0.10-0
10422 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-1.0-2
10423 libepc-common libepc-ui-1.0-2 libfreerdp-plugins-standard
10424 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
10425 libgdl-1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-0 libgif4
10426 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
10427 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
10428 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
10429 libgtk2.0-cil libgtkglext1 libgtksourceview-common
10430 libgtksourceview2.0-common libmono-addins-gui0.2-cil
10431 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
10432 libmono-i18n-west2.0-cil libmono-posix2.0-cil
10433 libmono-security2.0-cil libmono-sharpzip2.84-cil
10434 libmono-system2.0-cil libmtp8 libmusicbrainz3-6
10435 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6.8
10436 libpolkit-gtk-1-0 libpt-1.10.10-plugins-alsa
10437 libpt-1.10.10-plugins-v4l libpt2.6.7 libpython2.6 librpm1 librpmio1
10438 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-4
10439 libtelepathy-farsight0 libtelepathy-glib0 libtidy-0.99-0
10440 libxalan2-java libxerces2-java media-player-info mesa-utils
10441 mono-2.0-gac mono-gac mono-runtime nautilus-sendto
10442 nautilus-sendto-empathy openoffice.org-writer2latex
10443 openssl-blacklist p7zip p7zip-full pkg-config python-4suite-xml
10444 python-aptdaemon python-aptdaemon-gtk python-axiom
10445 python-beautifulsoup python-bugbuddy python-clientform
10446 python-coherence python-configobj python-crypto python-cupshelpers
10447 python-cupsutils python-eggtrayicon python-elementtree
10448 python-epsilon python-evolution python-feedparser python-gdata
10449 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
10450 python-gtksourceview2 python-httplib2 python-louie python-mako
10451 python-markupsafe python-mechanize python-nevow python-notify
10452 python-opengl python-openssl python-pam python-pkg-resources
10453 python-pyasn1 python-pysqlite2 python-rdflib python-serial
10454 python-tagpy python-twisted-bin python-twisted-conch
10455 python-twisted-core python-twisted-web python-utidylib python-webkit
10456 python-xdg python-zope.interface remmina remmina-plugin-data
10457 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
10458 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
10459 software-center svgalibg1 system-config-printer-udev
10460 telepathy-gabble telepathy-mission-control-5 telepathy-salut tomboy
10461 totem totem-coherence totem-mozilla totem-plugins
10462 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
10463 zip
10464 &lt;/p&gt;&lt;/blockquote&gt;
10465
10466 Installed using apt-get, removed with aptitude
10467
10468 &lt;blockquote&gt;&lt;p&gt;
10469 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
10470 epiphany-extensions epiphany-gecko evolution-exchange
10471 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
10472 gedit-common gnome-app-install gnome-games gnome-games-data
10473 gnome-nettool gnome-system-tools gnome-themes gnome-utils
10474 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
10475 guile-1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
10476 libavahi-ui0 libbind9-50 libbluetooth2 libcamel1.2-11 libcdio7
10477 libcucul0 libcurl3 libdirectfb-1.0-0 libdmx1 libdvdread3
10478 libedata-cal1.2-6 libedataserver1.2-9 libeel2-2.20 libepc-1.0-1
10479 libepc-ui-1.0-1 libexchange-storage1.2-3 libfaad0 libgadu3
10480 libgalago3 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
10481 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
10482 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
10483 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtk-vnc-1.0-0
10484 libgtkhtml2-0 libgtksourceview1.0-0 libgtksourceview2.0-0
10485 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
10486 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
10487 libmagick++10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
10488 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
10489 libnm-util0 libopal-2.2 libosp5 libparted1.8-10 libpisock9
10490 libpisync1 libpoppler-glib3 libpoppler3 libpt-1.10.10 libraw1394-8
10491 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-8
10492 libspeexdsp1 libssh2-1 libsuitesparse-3.1.0 libsvga1
10493 libswfdec-0.6-90 libtalloc1 libtotem-plparser10 libtrackerclient0
10494 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
10495 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
10496 sound-juicer swfdec-gnome system-config-printer totem-common
10497 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
10498 &lt;/p&gt;&lt;/blockquote&gt;
10499
10500 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10501
10502 &lt;blockquote&gt;&lt;p&gt;
10503 gstreamer0.10-gnomevfs
10504 &lt;/p&gt;&lt;/blockquote&gt;
10505
10506 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10507
10508 &lt;blockquote&gt;&lt;p&gt;
10509 [nothing]
10510 &lt;/p&gt;&lt;/blockquote&gt;
10511
10512 &lt;p&gt;This is for KDE:&lt;/p&gt;
10513
10514 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
10515
10516 &lt;blockquote&gt;&lt;p&gt;
10517 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-4.3 dcoprss
10518 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
10519 ghostscript-x git gnome-audio gnugo granatier gs-common
10520 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
10521 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
10522 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
10523 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10524 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
10525 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
10526 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10527 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
10528 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
10529 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
10530 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
10531 ksudoku kubrick kweather libasound2-plugins libboost-python1.42.0
10532 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
10533 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
10534 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
10535 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
10536 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
10537 libkrossui4 libmailtools-perl libmime-tools-perl
10538 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
10539 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
10540 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
10541 lirc luatex marble networkstatus noatun-plugins
10542 openoffice.org-writer2latex palapeli palapeli-data parley
10543 parley-data poster psutils pulseaudio pulseaudio-esound-compat
10544 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
10545 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
10546 ttf-sazanami-gothic
10547 &lt;/p&gt;&lt;/blockquote&gt;
10548
10549 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
10550
10551 &lt;blockquote&gt;&lt;p&gt;
10552 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
10553 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
10554 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
10555 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
10556 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
10557 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
10558 kitchensync kiten kjumpingcube klatin klettres klickety klines
10559 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
10560 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
10561 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
10562 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
10563 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
10564 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
10565 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
10566 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
10567 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10568 libavahi-core5 libavc1394-0 libbind9-50 libbluetooth2
10569 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0
10570 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10571 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0 libicu38
10572 libiec61883-0 libindex0 libisccc50 libisccfg50 libiw29
10573 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
10574 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
10575 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10576 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
10577 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
10578 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
10579 libpoppler-qt2 libpoppler3 libraw1394-8 librss1 libsensors3
10580 libsmbios2 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90
10581 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
10582 mpeglib network-manager-kde noatun pmount tex-common texlive-base
10583 texlive-common texlive-doc-base texlive-fonts-recommended tidy
10584 ttf-dustin ttf-kochi-gothic ttf-sjfonts
10585 &lt;/p&gt;&lt;/blockquote&gt;
10586
10587 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
10588
10589 &lt;blockquote&gt;&lt;p&gt;
10590 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
10591 kdeartwork kdebase kdebase-apps kdebase-workspace
10592 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
10593 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
10594 netpbm plasma-widget-folderview plasma-widget-networkmanagement
10595 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
10596 xscreensaver-screensaver-bsod
10597 &lt;/p&gt;&lt;/blockquote&gt;
10598
10599 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
10600
10601 &lt;blockquote&gt;&lt;p&gt;
10602 kdebase-bin konq-plugins konqueror
10603 &lt;/p&gt;&lt;/blockquote&gt;
10604 </description>
10605 </item>
10606
10607 <item>
10608 <title>Gnash buildbot slave and Debian kfreebsd</title>
10609 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</link>
10610 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html</guid>
10611 <pubDate>Sat, 20 Nov 2010 07:20:00 +0100</pubDate>
10612 <description>&lt;p&gt;Answering
10613 &lt;a href=&quot;http://www.listware.net/201011/gnash-dev/67431-gnash-dev-buildbot-looking-for-slaves.html&quot;&gt;the
10614 call from the Gnash project&lt;/a&gt; for
10615 &lt;a href=&quot;http://www.gnashdev.org:8010&quot;&gt;buildbot&lt;/a&gt; slaves to test the
10616 current source, I have set up a virtual KVM machine on the Debian
10617 Edu/Skolelinux virtualization host to test the git source on
10618 Debian/Squeeze. I hope this can help the developers in getting new
10619 releases out more often.&lt;/p&gt;
10620
10621 &lt;p&gt;As the developers want less main-stream build platforms tested to,
10622 I have considered setting up a &lt;a
10623 href=&quot;http://www.debian.org/ports/kfreebsd-gnu/&quot;&gt;Debian/kfreebsd&lt;/a&gt;
10624 machine as well. I have also considered using the kfreebsd
10625 architecture in Debian as a file server in NUUG to get access to the 5
10626 TB zfs volume we currently use to store DV video. Because of this, I
10627 finally got around to do a test installation of Debian/Squeeze with
10628 kfreebsd. Installation went fairly smooth, thought I noticed some
10629 visual glitches in the cdebconf dialogs (black cursor left on the
10630 screen at random locations). Have not gotten very far with the
10631 testing. Noticed cfdisk did not work, but fdisk did so it was not a
10632 fatal problem. Have to spend some more time on it to see if it is
10633 useful as a file server for NUUG. Will try to find time to set up a
10634 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.&lt;/p&gt;
10635 </description>
10636 </item>
10637
10638 <item>
10639 <title>Debian in 3D</title>
10640 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html</link>
10641 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html</guid>
10642 <pubDate>Tue, 9 Nov 2010 16:10:00 +0100</pubDate>
10643 <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;
10644
10645 &lt;p&gt;3D printing is just great. I just came across this Debian logo in
10646 3D linked in from
10647 &lt;a href=&quot;http://blog.thingiverse.com/2010/11/09/participatory-branding/&quot;&gt;the
10648 thingiverse blog&lt;/a&gt;.&lt;/p&gt;
10649 </description>
10650 </item>
10651
10652 <item>
10653 <title>Software updates 2010-10-24</title>
10654 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</link>
10655 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html</guid>
10656 <pubDate>Sun, 24 Oct 2010 22:45:00 +0200</pubDate>
10657 <description>&lt;p&gt;Some updates.&lt;/p&gt;
10658
10659 &lt;p&gt;My &lt;a href=&quot;http://pledgebank.com/gnash-avm2&quot;&gt;gnash pledge&lt;/a&gt; to
10660 raise money for the project is going well. The lower limit of 10
10661 signers was reached in 24 hours, and so far 13 people have signed it.
10662 More signers and more funding is most welcome, and I am really curious
10663 how far we can get before the time limit of December 24 is reached.
10664 :)&lt;/p&gt;
10665
10666 &lt;p&gt;On the #gnash IRC channel on irc.freenode.net, I was just tipped
10667 about what appear to be a great code coverage tool capable of
10668 generating code coverage stats without any changes to the source code.
10669 It is called
10670 &lt;a href=&quot;http://simonkagstrom.github.com/kcov/index.html&quot;&gt;kcov&lt;/a&gt;,
10671 and can be used using &lt;tt&gt;kcov &amp;lt;directory&amp;gt; &amp;lt;binary&amp;gt;&lt;/tt&gt;.
10672 It is missing in Debian, but the git source built just fine in Squeeze
10673 after I installed libelf-dev, libdwarf-dev, pkg-config and
10674 libglib2.0-dev. Failed to build in Lenny, but suspect that is
10675 solvable. I hope kcov make it into Debian soon.&lt;/p&gt;
10676
10677 &lt;p&gt;Finally found time to wrap up the release notes for &lt;a
10678 href=&quot;http://lists.debian.org/debian-edu-announce/2010/10/msg00002.html&quot;&gt;a
10679 new alpha release of Debian Edu&lt;/a&gt;, and just published the second
10680 alpha test release of the Squeeze based Debian Edu /
10681 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt;
10682 release. Give it a try if you need a complete linux solution for your
10683 school, including central infrastructure server, workstations, thin
10684 client servers and diskless workstations. A nice touch added
10685 yesterday is RDP support on the thin client servers, for windows
10686 clients to get a Linux desktop on request.&lt;/p&gt;
10687 </description>
10688 </item>
10689
10690 <item>
10691 <title>Some notes on Flash in Debian and Debian Edu</title>
10692 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</link>
10693 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html</guid>
10694 <pubDate>Sat, 4 Sep 2010 10:10:00 +0200</pubDate>
10695 <description>&lt;p&gt;In the &lt;a href=&quot;http://popcon.debian.org/unknown/by_vote&quot;&gt;Debian
10696 popularity-contest numbers&lt;/a&gt;, the adobe-flashplugin package the
10697 second most popular used package that is missing in Debian. The sixth
10698 most popular is flashplayer-mozilla. This is a clear indication that
10699 working flash is important for Debian users. Around 10 percent of the
10700 users submitting data to popcon.debian.org have this package
10701 installed.&lt;/p&gt;
10702
10703 &lt;p&gt;In the report written by Lars Risan in August 2008
10704&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
10705 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
10706 stiftelsen SLX Debian Labs&lt;/a&gt;»), one of the most important problems
10707 schools experienced with &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian
10708 Edu/Skolelinux&lt;/a&gt; was the lack of working Flash. A lot of educational
10709 web sites require Flash to work, and lacking working Flash support in
10710 the web browser and the problems with installing it was perceived as a
10711 good reason to stay with Windows.&lt;/p&gt;
10712
10713 &lt;p&gt;I once saw a funny and sad comment in a web forum, where Linux was
10714 said to be the retarded cousin that did not really understand
10715 everything you told him but could work fairly well. This was a
10716 comment regarding the problems Linux have with proprietary formats and
10717 non-standard web pages, and is sad because it exposes a fairly common
10718 understanding of whose fault it is if web pages that only work in for
10719 example Internet Explorer 6 fail to work on Firefox, and funny because
10720 it explain very well how annoying it is for users when Linux
10721 distributions do not work with the documents they receive or the web
10722 pages they want to visit.&lt;/p&gt;
10723
10724 &lt;p&gt;This is part of the reason why I believe it is important for Debian
10725 and Debian Edu to have a well working Flash implementation in the
10726 distribution, to get at least popular sites as Youtube and Google
10727 Video to working out of the box. For Squeeze, Debian have the chance
10728 to include the latest version of Gnash that will make this happen, as
10729 the new release 0.8.8 was published a few weeks ago and is resting in
10730 unstable. The new version work with more sites that version 0.8.7.
10731 The Gnash maintainers have asked for a freeze exception, but the
10732 release team have not had time to reply to it yet. I hope they agree
10733 with me that Flash is important for the Debian desktop users, and thus
10734 accept the new package into Squeeze.&lt;/p&gt;
10735 </description>
10736 </item>
10737
10738 <item>
10739 <title>Circular package dependencies harms apt recovery</title>
10740 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</link>
10741 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html</guid>
10742 <pubDate>Tue, 27 Jul 2010 23:50:00 +0200</pubDate>
10743 <description>&lt;p&gt;I discovered this while doing
10744 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;automated
10745 testing of upgrades from Debian Lenny to Squeeze&lt;/a&gt;. A few packages
10746 in Debian still got circular dependencies, and it is often claimed
10747 that apt and aptitude should be able to handle this just fine, but
10748 some times these dependency loops causes apt to fail.&lt;/p&gt;
10749
10750 &lt;p&gt;An example is from todays
10751 &lt;a href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing//test-20100727-lenny-squeeze-kde-aptitude.txt&quot;&gt;upgrade
10752 of KDE using aptitude&lt;/a&gt;. In it, a bug in kdebase-workspace-data
10753 causes perl-modules to fail to upgrade. The cause is simple. If a
10754 package fail to unpack, then only part of packages with the circular
10755 dependency might end up being unpacked when unpacking aborts, and the
10756 ones already unpacked will fail to configure in the recovery phase
10757 because its dependencies are unavailable.&lt;/p&gt;
10758
10759 &lt;p&gt;In this log, the problem manifest itself with this error:&lt;/p&gt;
10760
10761 &lt;blockquote&gt;&lt;pre&gt;
10762 dpkg: dependency problems prevent configuration of perl-modules:
10763 perl-modules depends on perl (&gt;= 5.10.1-1); however:
10764 Version of perl on system is 5.10.0-19lenny2.
10765 dpkg: error processing perl-modules (--configure):
10766 dependency problems - leaving unconfigured
10767 &lt;/pre&gt;&lt;/blockquote&gt;
10768
10769 &lt;p&gt;The perl/perl-modules circular dependency is already
10770 &lt;a href=&quot;http://bugs.debian.org/527917&quot;&gt;reported as a bug&lt;/a&gt;, and will
10771 hopefully be solved as soon as possible, but it is not the only one,
10772 and each one of these loops in the dependency tree can cause similar
10773 failures. Of course, they only occur when there are bugs in other
10774 packages causing the unpacking to fail, but it is rather nasty when
10775 the failure of one package causes the problem to become worse because
10776 of dependency loops.&lt;/p&gt;
10777
10778 &lt;p&gt;Thanks to
10779 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/06/msg00116.html&quot;&gt;the
10780 tireless effort by Bill Allombert&lt;/a&gt;, the number of circular
10781 dependencies
10782 &lt;a href=&quot;http://debian.semistable.com/debgraph.out.html&quot;&gt;left in Debian
10783 is dropping&lt;/a&gt;, and perhaps it will reach zero one day. :)&lt;/p&gt;
10784
10785 &lt;p&gt;Todays testing also exposed a bug in
10786 &lt;a href=&quot;http://bugs.debian.org/590605&quot;&gt;update-notifier&lt;/a&gt; and
10787 &lt;a href=&quot;http://bugs.debian.org/590604&quot;&gt;different behaviour&lt;/a&gt; between
10788 apt-get and aptitude, the latter possibly caused by some circular
10789 dependency. Reported both to BTS to try to get someone to look at
10790 it.&lt;/p&gt;
10791 </description>
10792 </item>
10793
10794 <item>
10795 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP</title>
10796 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</link>
10797 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html</guid>
10798 <pubDate>Sat, 17 Jul 2010 21:00:00 +0200</pubDate>
10799 <description>&lt;p&gt;This is a
10800 &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;
10801 on my
10802 &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
10803 work&lt;/a&gt; on
10804 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html&quot;&gt;merging
10805 all&lt;/a&gt; the computer related LDAP objects in Debian Edu.&lt;/p&gt;
10806
10807 &lt;p&gt;As a step to try to see if it possible to merge the DNS and DHCP
10808 LDAP objects, I have had a look at how the packages pdns-backend-ldap
10809 and dhcp3-server-ldap in Debian use the LDAP server. The two
10810 implementations are quite different in how they use LDAP.&lt;/p&gt;
10811
10812 To get this information, I started slapd with debugging enabled and
10813 dumped the debug output to a file to get the LDAP searches performed
10814 on a Debian Edu main-server. Here is a summary.
10815
10816 &lt;p&gt;&lt;strong&gt;powerdns&lt;/strong&gt;&lt;/p&gt;
10817
10818 &lt;a href=&quot;http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend&quot;&gt;Clues
10819 on how to&lt;/a&gt; set up PowerDNS to use a LDAP backend is available on
10820 the web.
10821
10822 &lt;p&gt;PowerDNS have two modes of operation using LDAP as its backend.
10823 One &quot;strict&quot; mode where the forward and reverse DNS lookups are done
10824 using the same LDAP objects, and a &quot;tree&quot; mode where the forward and
10825 reverse entries are in two different subtrees in LDAP with a structure
10826 based on the DNS names, as in tjener.intern and
10827 2.2.0.10.in-addr.arpa.&lt;/p&gt;
10828
10829 &lt;p&gt;In tree mode, the server is set up to use a LDAP subtree as its
10830 base, and uses a &quot;base&quot; scoped search for the DNS name by adding
10831 &quot;dc=tjener,dc=intern,&quot; to the base with a filter for
10832 &quot;(associateddomain=tjener.intern)&quot; for the forward entry and
10833 &quot;dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,&quot; with a filter for
10834 &quot;(associateddomain=2.2.0.10.in-addr.arpa)&quot; for the reverse entry. For
10835 forward entries, it is looking for attributes named dnsttl, arecord,
10836 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
10837 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
10838 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
10839 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
10840 spfrecord and modifytimestamp. For reverse entries it is looking for
10841 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
10842 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
10843 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
10844 ldapsearch commands could look like this:&lt;/p&gt;
10845
10846 &lt;blockquote&gt;&lt;pre&gt;
10847 ldapsearch -h ldap \
10848 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10849 -s base -x &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
10850 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10851 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10852 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10853 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10854
10855 ldapsearch -h ldap \
10856 -b dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10857 -s base -x &#39;(associateddomain=2.2.0.10.in-addr.arpa)&#39;
10858 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
10859 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
10860 srvrecord naptrrecord modifytimestamp
10861 &lt;/pre&gt;&lt;/blockquote&gt;
10862
10863 &lt;p&gt;In Debian Edu/Lenny, the PowerDNS tree mode is used with
10864 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
10865 example LDAP objects used there. In addition to these objects, the
10866 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
10867 also exist.&lt;/p&gt;
10868
10869 &lt;blockquote&gt;&lt;pre&gt;
10870 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
10871 objectclass: top
10872 objectclass: dnsdomain
10873 objectclass: domainrelatedobject
10874 dc: tjener
10875 arecord: 10.0.2.2
10876 associateddomain: tjener.intern
10877
10878 dn: dc=2,dc=2,dc=0,dc=10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
10879 objectclass: top
10880 objectclass: dnsdomain2
10881 objectclass: domainrelatedobject
10882 dc: 2
10883 ptrrecord: tjener.intern
10884 associateddomain: 2.2.0.10.in-addr.arpa
10885 &lt;/pre&gt;&lt;/blockquote&gt;
10886
10887 &lt;p&gt;In strict mode, the server behaves differently. When looking for
10888 forward DNS entries, it is doing a &quot;subtree&quot; scoped search with the
10889 same base as in the tree mode for a object with filter
10890 &quot;(associateddomain=tjener.intern)&quot; and requests the attributes dnsttl,
10891 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
10892 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
10893 naptrrecord and modifytimestamp. For reverse entires it also do a
10894 subtree scoped search but this time the filter is &quot;(arecord=10.0.2.2)&quot;
10895 and the requested attributes are associateddomain, dnsttl and
10896 modifytimestamp. In short, in strict mode the objects with ptrrecord
10897 go away, and the arecord attribute in the forward object is used
10898 instead.&lt;/p&gt;
10899
10900 &lt;p&gt;The forward and reverse searches can be simulated using ldapsearch
10901 like this:&lt;/p&gt;
10902
10903 &lt;blockquote&gt;&lt;pre&gt;
10904 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10905 &#39;(associateddomain=tjener.intern)&#39; dNSTTL aRecord nSRecord \
10906 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10907 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10908 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10909 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10910
10911 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10912 &#39;(arecord=10.0.2.2)&#39; associateddomain dnsttl modifytimestamp
10913 &lt;/pre&gt;&lt;/blockquote&gt;
10914
10915 &lt;p&gt;In addition to the forward and reverse searches , there is also a
10916 search for SOA records, which behave similar to the forward and
10917 reverse lookups.&lt;/p&gt;
10918
10919 &lt;p&gt;A thing to note with the PowerDNS behaviour is that it do not
10920 specify any objectclass names, and instead look for the attributes it
10921 need to generate a DNS reply. This make it able to work with any
10922 objectclass that provide the needed attributes.&lt;/p&gt;
10923
10924 &lt;p&gt;The attributes are normally provided in the cosine (RFC 1274) and
10925 dnsdomain2 schemas. The latter is used for reverse entries like
10926 ptrrecord and recent DNS additions like aaaarecord and srvrecord.&lt;/p&gt;
10927
10928 &lt;p&gt;In Debian Edu, we have created DNS objects using the object classes
10929 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
10930 attributes) and domainrelatedobject (for associatedDomain). The use
10931 of structural object classes make it impossible to combine these
10932 classes with the object classes used by DHCP.&lt;/p&gt;
10933
10934 &lt;p&gt;There are other schemas that could be used too, for example the
10935 dnszone structural object class used by Gosa and bind-sdb for the DNS
10936 attributes combined with the domainrelatedobject object class, but in
10937 this case some unused attributes would have to be included as well
10938 (zonename and relativedomainname).&lt;/p&gt;
10939
10940 &lt;p&gt;My proposal for Debian Edu would be to switch PowerDNS to strict
10941 mode and not use any of the existing objectclasses (dnsdomain,
10942 dnsdomain2 and dnszone) when one want to combine the DNS information
10943 with DHCP information, and instead create a auxiliary object class
10944 defined something like this (using the attributes defined for
10945 dnsdomain and dnsdomain2 or dnszone):&lt;/p&gt;
10946
10947 &lt;blockquote&gt;&lt;pre&gt;
10948 objectclass ( some-oid NAME &#39;dnsDomainAux&#39;
10949 SUP top
10950 AUXILIARY
10951 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
10952 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
10953 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
10954 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
10955 A6Record $ DNAMERecord
10956 ))
10957 &lt;/pre&gt;&lt;/blockquote&gt;
10958
10959 &lt;p&gt;This will allow any object to become a DNS entry when combined with
10960 the domainrelatedobject object class, and allow any entity to include
10961 all the attributes PowerDNS wants. I&#39;ve sent an email to the PowerDNS
10962 developers asking for their view on this schema and if they are
10963 interested in providing such schema with PowerDNS, and I hope my
10964 message will be accepted into their mailing list soon.&lt;/p&gt;
10965
10966 &lt;p&gt;&lt;strong&gt;ISC dhcp&lt;/strong&gt;&lt;/p&gt;
10967
10968 &lt;p&gt;The DHCP server searches for specific objectclass and requests all
10969 the object attributes, and then uses the attributes it want. This
10970 make it harder to figure out exactly what attributes are used, but
10971 thanks to the working example in Debian Edu I can at least get an idea
10972 what is needed without having to read the source code.&lt;/p&gt;
10973
10974 &lt;p&gt;In the DHCP server configuration, the LDAP base to use and the
10975 search filter to use to locate the correct dhcpServer entity is
10976 stored. These are the relevant entries from
10977 /etc/dhcp3/dhcpd.conf:&lt;/p&gt;
10978
10979 &lt;blockquote&gt;&lt;pre&gt;
10980 ldap-base-dn &quot;dc=skole,dc=skolelinux,dc=no&quot;;
10981 ldap-dhcp-server-cn &quot;dhcp&quot;;
10982 &lt;/pre&gt;&lt;/blockquote&gt;
10983
10984 &lt;p&gt;The DHCP server uses this information to nest all the DHCP
10985 configuration it need. The cn &quot;dhcp&quot; is located using the given LDAP
10986 base and the filter &quot;(&amp;(objectClass=dhcpServer)(cn=dhcp))&quot;. The
10987 search result is this entry:&lt;/p&gt;
10988
10989 &lt;blockquote&gt;&lt;pre&gt;
10990 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
10991 cn: dhcp
10992 objectClass: top
10993 objectClass: dhcpServer
10994 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
10995 &lt;/pre&gt;&lt;/blockquote&gt;
10996
10997 &lt;p&gt;The content of the dhcpServiceDN attribute is next used to locate the
10998 subtree with DHCP configuration. The DHCP configuration subtree base
10999 is located using a base scope search with base &quot;cn=DHCP
11000 Config,dc=skole,dc=skolelinux,dc=no&quot; and filter
11001 &quot;(&amp;(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))&quot;.
11002 The search result is this entry:&lt;/p&gt;
11003
11004 &lt;blockquote&gt;&lt;pre&gt;
11005 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11006 cn: DHCP Config
11007 objectClass: top
11008 objectClass: dhcpService
11009 objectClass: dhcpOptions
11010 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11011 dhcpStatements: ddns-update-style none
11012 dhcpStatements: authoritative
11013 dhcpOption: smtp-server code 69 = array of ip-address
11014 dhcpOption: www-server code 72 = array of ip-address
11015 dhcpOption: wpad-url code 252 = text
11016 &lt;/pre&gt;&lt;/blockquote&gt;
11017
11018 &lt;p&gt;Next, the entire subtree is processed, one level at the time. When
11019 all the DHCP configuration is loaded, it is ready to receive requests.
11020 The subtree in Debian Edu contain objects with object classes
11021 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11022 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11023 and information about netmasks, dynamic range etc. Leaving out the
11024 details here because it is not relevant for the focus of my
11025 investigation, which is to see if it is possible to merge dns and dhcp
11026 related computer objects.&lt;/p&gt;
11027
11028 &lt;p&gt;When a DHCP request come in, LDAP is searched for the MAC address
11029 of the client (00:00:00:00:00:00 in this example), using a subtree
11030 scoped search with &quot;cn=DHCP Config,dc=skole,dc=skolelinux,dc=no&quot; as
11031 the base and &quot;(&amp;(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11032 00:00:00:00:00:00))&quot; as the filter. This is what a host object look
11033 like:&lt;/p&gt;
11034
11035 &lt;blockquote&gt;&lt;pre&gt;
11036 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11037 cn: hostname
11038 objectClass: top
11039 objectClass: dhcpHost
11040 dhcpHWAddress: ethernet 00:00:00:00:00:00
11041 dhcpStatements: fixed-address hostname
11042 &lt;/pre&gt;&lt;/blockquote&gt;
11043
11044 &lt;p&gt;There is less flexiblity in the way LDAP searches are done here.
11045 The object classes need to have fixed names, and the configuration
11046 need to be stored in a fairly specific LDAP structure. On the
11047 positive side, the invidiual dhcpHost entires can be anywhere without
11048 the DN pointed to by the dhcpServer entries. The latter should make
11049 it possible to group all host entries in a subtree next to the
11050 configuration entries, and this subtree can also be shared with the
11051 DNS server if the schema proposed above is combined with the dhcpHost
11052 structural object class.
11053
11054 &lt;p&gt;&lt;strong&gt;Conclusion&lt;/strong&gt;&lt;/p&gt;
11055
11056 &lt;p&gt;The PowerDNS implementation seem to be very flexible when it come
11057 to which LDAP schemas to use. While its &quot;tree&quot; mode is rigid when it
11058 come to the the LDAP structure, the &quot;strict&quot; mode is very flexible,
11059 allowing DNS objects to be stored anywhere under the base cn specified
11060 in the configuration.&lt;/p&gt;
11061
11062 &lt;p&gt;The DHCP implementation on the other hand is very inflexible, both
11063 regarding which LDAP schemas to use and which LDAP structure to use.
11064 I guess one could implement ones own schema, as long as the
11065 objectclasses and attributes have the names used, but this do not
11066 really help when the DHCP subtree need to have a fairly fixed
11067 structure.&lt;/p&gt;
11068
11069 &lt;p&gt;Based on the observed behaviour, I suspect a LDAP structure like
11070 this might work for Debian Edu:&lt;/p&gt;
11071
11072 &lt;blockquote&gt;&lt;pre&gt;
11073 ou=services
11074 cn=machine-info (dhcpService) - dhcpServiceDN points here
11075 cn=dhcp (dhcpServer)
11076 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11077 cn=10.0.2.0 (dhcpSubnet)
11078 cn=group1 (dhcpGroup/dhcpOptions)
11079 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11080 cn=192.168.0.0 (dhcpSubnet)
11081 cn=group1 (dhcpGroup/dhcpOptions)
11082 ou=machines - PowerDNS base points here
11083 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11084 &lt;/pre&gt;&lt;/blockquote&gt;
11085
11086 &lt;P&gt;This is not tested yet. If the DHCP server require the dhcpHost
11087 entries to be in the dhcpGroup subtrees, the entries can be stored
11088 there instead of a common machines subtree, and the PowerDNS base
11089 would have to be moved one level up to the machine-info subtree.&lt;/p&gt;
11090
11091 &lt;p&gt;The combined object under the machines subtree would look something
11092 like this:&lt;/p&gt;
11093
11094 &lt;blockquote&gt;&lt;pre&gt;
11095 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11096 dc: hostname
11097 objectClass: top
11098 objectClass: dhcpHost
11099 objectclass: domainrelatedobject
11100 objectclass: dnsDomainAux
11101 associateddomain: hostname.intern
11102 arecord: 10.11.12.13
11103 dhcpHWAddress: ethernet 00:00:00:00:00:00
11104 dhcpStatements: fixed-address hostname.intern
11105 &lt;/pre&gt;&lt;/blockquote&gt;
11106
11107 &lt;/p&gt;One could even add the LTSP configuration associated with a given
11108 machine, as long as the required attributes are available in a
11109 auxiliary object class.&lt;/p&gt;
11110 </description>
11111 </item>
11112
11113 <item>
11114 <title>Combining PowerDNS and ISC DHCP LDAP objects</title>
11115 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</link>
11116 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html</guid>
11117 <pubDate>Wed, 14 Jul 2010 23:45:00 +0200</pubDate>
11118 <description>&lt;p&gt;For a while now, I have wanted to find a way to change the DNS and
11119 DHCP services in Debian Edu to use the same LDAP objects for a given
11120 computer, to avoid the possibility of having a inconsistent state for
11121 a computer in LDAP (as in DHCP but no DNS entry or the other way
11122 around) and make it easier to add computers to LDAP.&lt;/p&gt;
11123
11124 &lt;p&gt;I&#39;ve looked at how powerdns and dhcpd is using LDAP, and using this
11125 information finally found a solution that seem to work.&lt;/p&gt;
11126
11127 &lt;p&gt;The old setup required three LDAP objects for a given computer.
11128 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11129 we switch powerdns to use its strict LDAP method (ldap-method=strict
11130 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11131 merged into one while making it impossible to transfer the reverse map
11132 to a slave DNS server.&lt;/p&gt;
11133
11134 &lt;p&gt;If we also replace the object class used to get the DNS related
11135 attributes to one allowing these attributes to be combined with the
11136 dhcphost object class, we can merge the DNS and DHCP entries into one.
11137 I&#39;ve written such object class in the dnsdomainaux.schema file (need
11138 proper OIDs, but that is a minor issue), and tested the setup. It
11139 seem to work.&lt;/p&gt;
11140
11141 &lt;p&gt;With this test setup in place, we can get away with one LDAP object
11142 for both DNS and DHCP, and even the LTSP configuration I suggested in
11143 an earlier email. The combined LDAP object will look something like
11144 this:&lt;/p&gt;
11145
11146 &lt;blockquote&gt;&lt;pre&gt;
11147 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11148 cn: hostname
11149 objectClass: dhcphost
11150 objectclass: domainrelatedobject
11151 objectclass: dnsdomainaux
11152 associateddomain: hostname.intern
11153 arecord: 10.11.12.13
11154 dhcphwaddress: ethernet 00:00:00:00:00:00
11155 dhcpstatements: fixed-address hostname
11156 ldapconfigsound: Y
11157 &lt;/pre&gt;&lt;/blockquote&gt;
11158
11159 &lt;p&gt;The DNS server uses the associateddomain and arecord entries, while
11160 the DHCP server uses the dhcphwaddress and dhcpstatements entries
11161 before asking DNS to resolve the fixed-adddress. LTSP will use
11162 dhcphwaddress or associateddomain and the ldapconfig* attributes.&lt;/p&gt;
11163
11164 &lt;p&gt;I am not yet sure if I can get the DHCP server to look for its
11165 dhcphost in a different location, to allow us to put the objects
11166 outside the &quot;DHCP Config&quot; subtree, but hope to figure out a way to do
11167 that. If I can&#39;t figure out a way to do that, we can still get rid of
11168 the hosts subtree and move all its content into the DHCP Config tree
11169 (which probably should be renamed to be more related to the new
11170 content. I suspect cn=dnsdhcp,ou=services or something like that
11171 might be a good place to put it.&lt;/p&gt;
11172
11173 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11174 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11175 </description>
11176 </item>
11177
11178 <item>
11179 <title>Idea for storing LTSP configuration in LDAP</title>
11180 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</link>
11181 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html</guid>
11182 <pubDate>Sun, 11 Jul 2010 22:00:00 +0200</pubDate>
11183 <description>&lt;p&gt;Vagrant mentioned on IRC today that ltsp_config now support
11184 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
11185 clients, and that this can be used to fetch configuration from LDAP if
11186 Debian Edu choose to store configuration there.&lt;/p&gt;
11187
11188 &lt;p&gt;Armed with this information, I got inspired and wrote a test module
11189 to get configuration from LDAP. The idea is to look up the MAC
11190 address of the client in LDAP, and look for attributes on the form
11191 ltspconfigsetting=value, and use this to export SETTING=value to the
11192 LTSP clients.&lt;/p&gt;
11193
11194 &lt;p&gt;The goal is to be able to store the LTSP configuration attributes
11195 in a &quot;computer&quot; LDAP object used by both DNS and DHCP, and thus
11196 allowing us to store all information about a computer in one place.&lt;/p&gt;
11197
11198 &lt;p&gt;This is a untested draft implementation, and I welcome feedback on
11199 this approach. A real LDAP schema for the ltspClientAux objectclass
11200 need to be written. Comments, suggestions, etc?&lt;/p&gt;
11201
11202 &lt;blockquote&gt;&lt;pre&gt;
11203 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
11204 #
11205 # Fetch LTSP client settings from LDAP based on MAC address
11206 #
11207 # Uses ethernet address as stored in the dhcpHost objectclass using
11208 # the dhcpHWAddress attribute or ethernet address stored in the
11209 # ieee802Device objectclass with the macAddress attribute.
11210 #
11211 # This module is written to be schema agnostic, and only depend on the
11212 # existence of attribute names.
11213 #
11214 # The LTSP configuration variables are saved directly using a
11215 # ltspConfig prefix and uppercasing the rest of the attribute name.
11216 # To set the SERVER variable, set the ltspConfigServer attribute.
11217 #
11218 # Some LDAP schema should be created with all the relevant
11219 # configuration settings. Something like this should work:
11220 #
11221 # objectclass ( 1.1.2.2 NAME &#39;ltspClientAux&#39;
11222 # SUP top
11223 # AUXILIARY
11224 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
11225
11226 LDAPSERVER=$(debian-edu-ldapserver)
11227 if [ &quot;$LDAPSERVER&quot; ] ; then
11228 LDAPBASE=$(debian-edu-ldapserver -b)
11229 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk &#39;{print $5}&#39;|sort -u) ; do
11230 filter=&quot;(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))&quot;
11231 ldapsearch -h &quot;$LDAPSERVER&quot; -b &quot;$LDAPBASE&quot; -v -x &quot;$filter&quot; | \
11232 grep &#39;^ltspConfig&#39; | while read attr value ; do
11233 # Remove prefix and convert to upper case
11234 attr=$(echo $attr | sed &#39;s/^ltspConfig//i&#39; | tr a-z A-Z)
11235 # bass value on to clients
11236 eval &quot;$attr=$value; export $attr&quot;
11237 done
11238 done
11239 fi
11240 &lt;/pre&gt;&lt;/blockquote&gt;
11241
11242 &lt;p&gt;I&#39;m not sure this shell construction will work, because I suspect
11243 the while block might end up in a subshell causing the variables set
11244 there to not show up in ltsp-config, but if that is the case I am sure
11245 the code can be restructured to make sure the variables are passed on.
11246 I expect that can be solved with some testing. :)&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
11251 &lt;p&gt;Update 2010-07-17: I am aware of another effort to store LTSP
11252 configuration in LDAP that was created around year 2000 by
11253 &lt;a href=&quot;http://www.pcxperience.com/thinclient/documentation/ldap.html&quot;&gt;PC
11254 Xperience, Inc., 2000&lt;/a&gt;. I found its
11255 &lt;a href=&quot;http://people.redhat.com/alikins/ltsp/ldap/&quot;&gt;files&lt;/a&gt; on a
11256 personal home page over at redhat.com.&lt;/p&gt;
11257 </description>
11258 </item>
11259
11260 <item>
11261 <title>jXplorer, a very nice LDAP GUI</title>
11262 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</link>
11263 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html</guid>
11264 <pubDate>Fri, 9 Jul 2010 12:55:00 +0200</pubDate>
11265 <description>&lt;p&gt;Since
11266 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html&quot;&gt;my
11267 last post&lt;/a&gt; about available LDAP tools in Debian, I was told about a
11268 LDAP GUI that is even better than luma. The java application
11269 &lt;a href=&quot;http://jxplorer.org/&quot;&gt;jXplorer&lt;/a&gt; is claimed to be capable of
11270 moving LDAP objects and subtrees using drag-and-drop, and can
11271 authenticate using Kerberos. I have only tested the Kerberos
11272 authentication, but do not have a LDAP setup allowing me to rewrite
11273 LDAP with my test user yet. It is
11274 &lt;a href=&quot;http://packages.qa.debian.org/j/jxplorer.html&quot;&gt;available in
11275 Debian&lt;/a&gt; testing and unstable at the moment. The only problem I
11276 have with it is how it handle errors. If something go wrong, its
11277 non-intuitive behaviour require me to go through some query work list
11278 and remove the failing query. Nothing big, but very annoying.&lt;/p&gt;
11279 </description>
11280 </item>
11281
11282 <item>
11283 <title>Lenny-&gt;Squeeze upgrades, apt vs aptitude with the Gnome desktop</title>
11284 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</link>
11285 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html</guid>
11286 <pubDate>Sat, 3 Jul 2010 23:55:00 +0200</pubDate>
11287 <description>&lt;p&gt;Here is a short update on my &lt;a
11288 href=&quot;http://people.skolelinux.org/~pere/debian-upgrade-testing/&quot;&gt;my
11289 Debian Lenny-&gt;Squeeze upgrade testing&lt;/a&gt;. Here is a summary of the
11290 difference for Gnome when it is upgraded by apt-get and aptitude. I&#39;m
11291 not reporting the status for KDE, because the upgrade crashes when
11292 aptitude try because of missing conflicts
11293 (&lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; and
11294 &lt;a href=&quot;http://bugs.debian.org/585716&quot;&gt;#585716&lt;/a&gt;).&lt;/p&gt;
11295
11296 &lt;p&gt;At the end of the upgrade test script, dpkg -l is executed to get a
11297 complete list of the installed packages. Based on this I see these
11298 differences when I did a test run today. As usual, I do not really
11299 know what the correct set of packages would be, but thought it best to
11300 publish the difference.&lt;/p&gt;
11301
11302 &lt;p&gt;Installed using apt-get, missing with aptitude&lt;/p&gt;
11303
11304 &lt;blockquote&gt;&lt;p&gt;
11305 at-spi cpp-4.3 finger gnome-spell gstreamer0.10-gnomevfs
11306 libatspi1.0-0 libcupsys2 libeel2-data libgail-common libgdl-1-common
11307 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
11308 libgtksourceview-common libpt-1.10.10-plugins-alsa
11309 libpt-1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
11310 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
11311 python-4suite-xml python-eggtrayicon python-gtkhtml2
11312 python-gtkmozembed svgalibg1 xserver-xephyr zip
11313 &lt;/p&gt;&lt;/blockquote&gt;
11314
11315 &lt;p&gt;Installed using apt-get, removed with aptitude&lt;/p&gt;
11316
11317 &lt;blockquote&gt;&lt;p&gt;
11318 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
11319 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
11320 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-50
11321 libbluetooth2 libcamel1.2-11 libcdio7 libcucul0 libcurl3
11322 libdirectfb-1.0-0 libdvdread3 libedata-cal1.2-6 libedataserver1.2-9
11323 libeel2-2.20 libepc-1.0-1 libepc-ui-1.0-1 libexchange-storage1.2-3
11324 libfaad0 libgd2-noxpm libgda3-3 libgda3-common libggz2 libggzcore9
11325 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0 libgnome-desktop-2
11326 libgnome-pilot2 libgnomecups1.0-1 libgnomeprint2.2-0
11327 libgnomeprintui2.2-0 libgpod3 libgraphviz4 libgtkhtml2-0
11328 libgtksourceview1.0-0 libgucharmap6 libhesiod0 libicu38 libisccc50
11329 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++10
11330 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
11331 libneon27 libnm-glib0 libnm-util0 libopal-2.2 libosp5
11332 libparted1.8-10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
11333 libpt-1.10.10 libraw1394-8 libsensors3 libsmbios2 libsoup2.2-8
11334 libssh2-1 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1
11335 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
11336 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
11337 mysql-common swfdec-gnome totem-gstreamer wodim
11338 &lt;/p&gt;&lt;/blockquote&gt;
11339
11340 &lt;p&gt;Installed using aptitude, missing with apt-get&lt;/p&gt;
11341
11342 &lt;blockquote&gt;&lt;p&gt;
11343 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
11344 python-gnomekeyring python-wnck rhythmbox-plugins xorg
11345 xserver-xorg-input-all xserver-xorg-input-evdev
11346 xserver-xorg-input-kbd xserver-xorg-input-mouse
11347 xserver-xorg-input-synaptics xserver-xorg-video-all
11348 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
11349 xserver-xorg-video-chips xserver-xorg-video-cirrus
11350 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11351 xserver-xorg-video-glint xserver-xorg-video-i128
11352 xserver-xorg-video-i740 xserver-xorg-video-mach64
11353 xserver-xorg-video-mga xserver-xorg-video-neomagic
11354 xserver-xorg-video-nouveau xserver-xorg-video-nv
11355 xserver-xorg-video-r128 xserver-xorg-video-radeon
11356 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
11357 xserver-xorg-video-s3 xserver-xorg-video-s3virge
11358 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
11359 xserver-xorg-video-sis xserver-xorg-video-sisusb
11360 xserver-xorg-video-tdfx xserver-xorg-video-tga
11361 xserver-xorg-video-trident xserver-xorg-video-tseng
11362 xserver-xorg-video-vesa xserver-xorg-video-vmware
11363 xserver-xorg-video-voodoo
11364 &lt;/p&gt;&lt;/blockquote&gt;
11365
11366 &lt;p&gt;Installed using aptitude, removed with apt-get&lt;/p&gt;
11367
11368 &lt;blockquote&gt;&lt;p&gt;
11369 deskbar-applet xserver-xorg xserver-xorg-core
11370 xserver-xorg-input-wacom xserver-xorg-video-intel
11371 xserver-xorg-video-openchrome
11372 &lt;/p&gt;&lt;/blockquote&gt;
11373
11374 &lt;p&gt;I was told on IRC that the xorg-xserver package was
11375 &lt;a href=&quot;http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=9c8080d06c457932d3bfec021c69ac000aa60120&quot;&gt;changed
11376 in git&lt;/a&gt; today to try to get apt-get to not remove xorg completely.
11377 No idea when it hits Squeeze, but when it does I hope it will reduce
11378 the difference somewhat.
11379 </description>
11380 </item>
11381
11382 <item>
11383 <title>LUMA, a very nice LDAP GUI</title>
11384 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</link>
11385 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html</guid>
11386 <pubDate>Mon, 28 Jun 2010 00:30:00 +0200</pubDate>
11387 <description>&lt;p&gt;The last few days I have been looking into the status of the LDAP
11388 directory in Debian Edu, and in the process I started to miss a GUI
11389 tool to browse the LDAP tree. The only one I was able to find in
11390 Debian/Squeeze and Lenny is
11391 &lt;a href=&quot;http://luma.sourceforge.net/&quot;&gt;LUMA&lt;/a&gt;, which has proved to
11392 be a great tool to get a overview of the current LDAP directory
11393 populated by default in Skolelinux. Thanks to it, I have been able to
11394 find empty and obsolete subtrees, misplaced objects and duplicate
11395 objects. It will be installed by default in Debian/Squeeze. If you
11396 are working with LDAP, give it a go. :)&lt;/p&gt;
11397
11398 &lt;p&gt;I did notice one problem with it I have not had time to report to
11399 the BTS yet. There is no .desktop file in the package, so the tool do
11400 not show up in the Gnome and KDE menus, but only deep down in in the
11401 Debian submenu in KDE. I hope that can be fixed before Squeeze is
11402 released.&lt;/p&gt;
11403
11404 &lt;p&gt;I have not yet been able to get it to modify the tree yet. I would
11405 like to move objects and remove subtrees directly in the GUI, but have
11406 not found a way to do that with LUMA yet. So in the mean time, I use
11407 &lt;a href=&quot;http://www.lichteblau.com/ldapvi/&quot;&gt;ldapvi&lt;/a&gt; for that.&lt;/p&gt;
11408
11409 &lt;p&gt;If you have tips on other GUI tools for LDAP that might be useful
11410 in Debian Edu, please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11411
11412 &lt;p&gt;Update 2010-06-29: Ross Reedstrom tipped us about the
11413 &lt;a href=&quot;http://packages.qa.debian.org/g/gq.html&quot;&gt;gq&lt;/a&gt; package as a
11414 useful GUI alternative. It seem like a good tool, but is unmaintained
11415 in Debian and got a RC bug keeping it out of Squeeze. Unless that
11416 changes, it will not be an option for Debian Edu based on Squeeze.&lt;/p&gt;
11417 </description>
11418 </item>
11419
11420 <item>
11421 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object</title>
11422 <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>
11423 <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>
11424 <pubDate>Thu, 24 Jun 2010 00:35:00 +0200</pubDate>
11425 <description>&lt;p&gt;A while back, I
11426 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html&quot;&gt;complained
11427 about the fact&lt;/a&gt; that it is not possible with the provided schemas
11428 for storing DNS and DHCP information in LDAP to combine the two sets
11429 of information into one LDAP object representing a computer.&lt;/p&gt;
11430
11431 &lt;p&gt;In the mean time, I discovered that a simple fix would be to make
11432 the dhcpHost object class auxiliary, to allow it to be combined with
11433 the dNSDomain object class, and thus forming one object for one
11434 computer when storing both DHCP and DNS information in LDAP.&lt;/p&gt;
11435
11436 &lt;p&gt;If I understand this correctly, it is not safe to do this change
11437 without also changing the assigned number for the object class, and I
11438 do not know enough about LDAP schema design to do that properly for
11439 Debian Edu.&lt;/p&gt;
11440
11441 &lt;p&gt;Anyway, for future reference, this is how I believe we could change
11442 the
11443 &lt;a href=&quot;http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-00&quot;&gt;DHCP
11444 schema&lt;/a&gt; to solve at least part of the problem with the LDAP schemas
11445 available today from IETF.&lt;/p&gt;
11446
11447 &lt;pre&gt;
11448 --- dhcp.schema (revision 65192)
11449 +++ dhcp.schema (working copy)
11450 @@ -376,7 +376,7 @@
11451 objectclass ( 2.16.840.1.113719.1.203.6.6
11452 NAME &#39;dhcpHost&#39;
11453 DESC &#39;This represents information about a particular client&#39;
11454 - SUP top
11455 + SUP top AUXILIARY
11456 MUST cn
11457 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
11458 X-NDS_CONTAINMENT (&#39;dhcpService&#39; &#39;dhcpSubnet&#39; &#39;dhcpGroup&#39;) )
11459 &lt;/pre&gt;
11460
11461 &lt;p&gt;I very much welcome clues on how to do this properly for Debian
11462 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
11463 package, and should thus be free to rewrite it as we see fit.&lt;/p&gt;
11464
11465 &lt;p&gt;If you want to help out with implementing this for Debian Edu,
11466 please contact us on debian-edu@lists.debian.org.&lt;/p&gt;
11467 </description>
11468 </item>
11469
11470 <item>
11471 <title>Calling tasksel like the installer, while still getting useful output</title>
11472 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</link>
11473 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html</guid>
11474 <pubDate>Wed, 16 Jun 2010 14:55:00 +0200</pubDate>
11475 <description>&lt;p&gt;A few times I have had the need to simulate the way tasksel
11476 installs packages during the normal debian-installer run. Until now,
11477 I have ended up letting tasksel do the work, with the annoying problem
11478 of not getting any feedback at all when something fails (like a
11479 conffile question from dpkg or a download that fails), using code like
11480 this:
11481
11482 &lt;blockquote&gt;&lt;pre&gt;
11483 export DEBIAN_FRONTEND=noninteractive
11484 tasksel --new-install
11485 &lt;/pre&gt;&lt;/blockquote&gt;
11486
11487 This would invoke tasksel, let its automatic task selection pick the
11488 tasks to install, and continue to install the requested tasks without
11489 any output what so ever.
11490
11491 Recently I revisited this problem while working on the automatic
11492 package upgrade testing, because tasksel would some times hang without
11493 any useful feedback, and I want to see what is going on when it
11494 happen. Then it occured to me, I can parse the output from tasksel
11495 when asked to run in test mode, and use that aptitude command line
11496 printed by tasksel then to simulate the tasksel run. I ended up using
11497 code like this:
11498
11499 &lt;blockquote&gt;&lt;pre&gt;
11500 export DEBIAN_FRONTEND=noninteractive
11501 cmd=&quot;$(in_target tasksel -t --new-install | sed &#39;s/debconf-apt-progress -- //&#39;)&quot;
11502 $cmd
11503 &lt;/pre&gt;&lt;/blockquote&gt;
11504
11505 &lt;p&gt;The content of $cmd is typically something like &quot;&lt;tt&gt;aptitude -q
11506 --without-recommends -o APT::Install-Recommends=no -y install
11507 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
11508 ~pimportant&lt;/tt&gt;&quot;, which will install the gnome desktop task, the
11509 laptop task and all packages with priority standard , required and
11510 important, just like tasksel would have done it during
11511 installation.&lt;/p&gt;
11512
11513 &lt;p&gt;A better approach is probably to extend tasksel to be able to
11514 install packages without using debconf-apt-progress, for use cases
11515 like this.&lt;/p&gt;
11516 </description>
11517 </item>
11518
11519 <item>
11520 <title>Lenny-&gt;Squeeze upgrades, removals by apt and aptitude</title>
11521 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</link>
11522 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html</guid>
11523 <pubDate>Sun, 13 Jun 2010 09:05:00 +0200</pubDate>
11524 <description>&lt;p&gt;My
11525 &lt;a href=&quot;http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html&quot;&gt;testing
11526 of Debian upgrades&lt;/a&gt; from Lenny to Squeeze continues, and I&#39;ve
11527 finally made the upgrade logs available from
11528 &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;.
11529 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
11530 apt and aptitude, and found their differences interesting. This time
11531 I will only focus on their removal plans.&lt;/p&gt;
11532
11533 &lt;p&gt;After installing a Gnome desktop and the laptop task, apt-get wants
11534 to remove 72 packages when dist-upgrading from Lenny to Squeeze. The
11535 surprising part is that it want to remove xorg and all
11536 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
11537 sure why. When asking aptitude to do the same, it want to remove 129
11538 packages, but most of them are library packages I suspect are no
11539 longer needed. Both of them want to remove bluetooth packages, which
11540 I do not know. Perhaps these bluetooth packages are obsolete?&lt;/p&gt;
11541
11542 &lt;p&gt;For KDE, apt-get want to remove 82 packages, among them kdebase
11543 which seem like a bad idea and xorg the same way as with Gnome. Asking
11544 aptitude for the same, it wants to remove 192 packages, none which are
11545 too surprising.&lt;/p&gt;
11546
11547 &lt;p&gt;I guess the removal of xorg during upgrades should be investigated
11548 and avoided, and perhaps others as well. Here are the complete list
11549 of planned removals. The complete logs is available from the URL
11550 above. Note if you want to repeat these tests, that the upgrade test
11551 for kde+apt-get hung in the tasksel setup because of dpkg asking
11552 conffile questions. No idea why. I worked around it by using
11553 &#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
11554 continue.&lt;/p&gt;
11555
11556 &lt;p&gt;&lt;b&gt;apt-get gnome 72&lt;/b&gt;
11557 &lt;br&gt;bluez-gnome cupsddk-drivers deskbar-applet gnome
11558 gnome-desktop-environment gnome-network-admin gtkhtml3.14
11559 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-1-0
11560 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
11561 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
11562 serpentine swfdec-mozilla update-manager xorg xserver-xorg
11563 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11564 xserver-xorg-input-kbd xserver-xorg-input-mouse
11565 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11566 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11567 xserver-xorg-video-ati xserver-xorg-video-chips
11568 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11569 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11570 xserver-xorg-video-glint xserver-xorg-video-i128
11571 xserver-xorg-video-i740 xserver-xorg-video-imstt
11572 xserver-xorg-video-intel xserver-xorg-video-mach64
11573 xserver-xorg-video-mga xserver-xorg-video-neomagic
11574 xserver-xorg-video-nsc xserver-xorg-video-nv
11575 xserver-xorg-video-openchrome xserver-xorg-video-r128
11576 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11577 xserver-xorg-video-rendition xserver-xorg-video-s3
11578 xserver-xorg-video-s3virge xserver-xorg-video-savage
11579 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11580 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11581 xserver-xorg-video-tga xserver-xorg-video-trident
11582 xserver-xorg-video-tseng xserver-xorg-video-v4l
11583 xserver-xorg-video-vesa xserver-xorg-video-vga
11584 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9
11585 xulrunner-1.9-gnome-support&lt;/p&gt;
11586
11587 &lt;p&gt;&lt;b&gt;aptitude gnome 129&lt;/b&gt;
11588
11589 &lt;br&gt;bluez-gnome bluez-utils cpp-4.3 cupsddk-drivers dhcdbd
11590 djvulibre-desktop finger gnome-app-install gnome-mount
11591 gnome-network-admin gnome-spell gnome-vfs-obexftp
11592 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
11593 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
11594 libcamel1.2-11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
11595 libdirectfb-1.0-0 libdvdread3 libedataserver1.2-9 libeel2-2.20
11596 libeel2-data libepc-1.0-1 libepc-ui-1.0-1 libfaad0 libgail-common
11597 libgd2-noxpm libgda3-3 libgda3-common libgdl-1-0 libgdl-1-common
11598 libggz2 libggzcore9 libggzmod4 libgksu1.2-0 libgksuui1.0-1 libgmyth0
11599 libgnomecups1.0-1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-0
11600 libgnomeprint2.2-data libgnomeprintui2.2-0 libgnomeprintui2.2-common
11601 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-0
11602 libgtksourceview-common libgtksourceview1.0-0 libgucharmap6
11603 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++10
11604 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
11605 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-2.2
11606 libosp5 libparted1.8-10 libpoppler-glib3 libpoppler3 libpt-1.10.10
11607 libpt-1.10.10-plugins-alsa libpt-1.10.10-plugins-v4l libraw1394-8
11608 libsensors3 libslab0 libsmbios2 libsoup2.2-8 libssh2-1
11609 libsuitesparse-3.1.0 libswfdec-0.6-90 libtalloc1 libtotem-plparser10
11610 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
11611 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
11612 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
11613 openoffice.org-writer2latex openssl-blacklist p7zip
11614 python-4suite-xml python-eggtrayicon python-gnome2-desktop
11615 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
11616 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
11617 swfdec-mozilla totem-gstreamer update-manager wodim
11618 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11619 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11620 zip&lt;/p&gt;
11621
11622 &lt;p&gt;&lt;b&gt;apt-get kde 82&lt;/b&gt;
11623
11624 &lt;br&gt;cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
11625 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
11626 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
11627 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
11628 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
11629 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
11630 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11631 xserver-xorg-input-kbd xserver-xorg-input-mouse
11632 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11633 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11634 xserver-xorg-video-ati xserver-xorg-video-chips
11635 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11636 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11637 xserver-xorg-video-glint xserver-xorg-video-i128
11638 xserver-xorg-video-i740 xserver-xorg-video-imstt
11639 xserver-xorg-video-intel xserver-xorg-video-mach64
11640 xserver-xorg-video-mga xserver-xorg-video-neomagic
11641 xserver-xorg-video-nsc xserver-xorg-video-nv
11642 xserver-xorg-video-openchrome xserver-xorg-video-r128
11643 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11644 xserver-xorg-video-rendition xserver-xorg-video-s3
11645 xserver-xorg-video-s3virge xserver-xorg-video-savage
11646 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11647 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11648 xserver-xorg-video-tga xserver-xorg-video-trident
11649 xserver-xorg-video-tseng xserver-xorg-video-v4l
11650 xserver-xorg-video-vesa xserver-xorg-video-vga
11651 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-1.9&lt;/p&gt;
11652
11653 &lt;p&gt;&lt;b&gt;aptitude kde 192&lt;/b&gt;
11654 &lt;br&gt;bluez-utils cpp-4.3 cupsddk-drivers cvs dcoprss dhcdbd
11655 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
11656 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
11657 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
11658 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11659 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
11660 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
11661 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11662 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
11663 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
11664 kghostview khelpcenter khexedit kiconedit kitchensync klatin
11665 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
11666 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
11667 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
11668 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
11669 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
11670 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
11671 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11672 libavahi-core5 libavc1394-0 libavcodec51 libbluetooth2
11673 libboost-python1.34.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
11674 libdirectfb-1.0-0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11675 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-0
11676 libicu38 libiec61883-0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
11677 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
11678 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11679 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
11680 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
11681 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-8 libsmbios2
11682 libssh2-1 libsuitesparse-3.1.0 libtalloc1 libtiff-tools
11683 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
11684 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
11685 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
11686 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
11687 texlive-common texlive-doc-base texlive-fonts-recommended
11688 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11689 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11690 xulrunner-1.9&lt;/p&gt;
11691
11692 </description>
11693 </item>
11694
11695 <item>
11696 <title>Automatic upgrade testing from Lenny to Squeeze</title>
11697 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</link>
11698 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html</guid>
11699 <pubDate>Fri, 11 Jun 2010 22:50:00 +0200</pubDate>
11700 <description>&lt;p&gt;The last few days I have done some upgrade testing in Debian, to
11701 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
11702 have been discovered and reported in the process
11703 (&lt;a href=&quot;http://bugs.debian.org/585410&quot;&gt;#585410&lt;/a&gt; in nagios3-cgi,
11704 &lt;a href=&quot;http://bugs.debian.org/584879&quot;&gt;#584879&lt;/a&gt; already fixed in
11705 enscript and &lt;a href=&quot;http://bugs.debian.org/584861&quot;&gt;#584861&lt;/a&gt; in
11706 kdebase-workspace-data), and to get a more regular testing going on, I
11707 am working on a script to automate the test.&lt;/p&gt;
11708
11709 &lt;p&gt;The idea is to create a Lenny chroot and use tasksel to install a
11710 Gnome or KDE desktop installation inside the chroot before upgrading
11711 it. To ensure no services are started in the chroot, a policy-rc.d
11712 script is inserted. To make sure tasksel believe it is to install a
11713 desktop on a laptop, the tasksel tests are replaced in the chroot
11714 (only acceptable because this is a throw-away chroot).&lt;/p&gt;
11715
11716 &lt;p&gt;A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
11717 currently always fail because udev refuses to upgrade with the kernel
11718 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
11719 is created. The bug report
11720 &lt;a href=&quot;http://bugs.debian.org/566000&quot;&gt;#566000&lt;/a&gt; make me suspect
11721 this problem do not trigger in a chroot, but I touch the file anyway
11722 to make sure the upgrade go well. Testing on virtual and real
11723 hardware have failed me because of udev so far, and creating this file
11724 do the trick in such settings anyway. This is a
11725 &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
11726 issue&lt;/a&gt; and the current udev behaviour is intended by the udev
11727 maintainer because he lack the resources to rewrite udev to keep
11728 working with old kernels or something like that. I really wish the
11729 udev upstream would keep udev backwards compatible, to avoid such
11730 upgrade problem, but given that they fail to do so, I guess
11731 documenting the way out of this mess is the best option we got for
11732 Debian Squeeze.&lt;/p&gt;
11733
11734 &lt;p&gt;Anyway, back to the task at hand, testing upgrades. This test
11735 script, which I call &lt;tt&gt;upgrade-test&lt;/tt&gt; for now, is doing the
11736 trick:&lt;/p&gt;
11737
11738 &lt;blockquote&gt;&lt;pre&gt;
11739 #!/bin/sh
11740 set -ex
11741
11742 if [ &quot;$1&quot; ] ; then
11743 desktop=$1
11744 else
11745 desktop=gnome
11746 fi
11747
11748 from=lenny
11749 to=squeeze
11750
11751 exec &amp;lt; /dev/null
11752 unset LANG
11753 mirror=http://ftp.skolelinux.org/debian
11754 tmpdir=chroot-$from-upgrade-$to-$desktop
11755 fuser -mv .
11756 debootstrap $from $tmpdir $mirror
11757 chroot $tmpdir aptitude update
11758 cat &gt; $tmpdir/usr/sbin/policy-rc.d &amp;lt;&amp;lt;EOF
11759 #!/bin/sh
11760 exit 101
11761 EOF
11762 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
11763 exit_cleanup() {
11764 umount $tmpdir/proc
11765 }
11766 mount -t proc proc $tmpdir/proc
11767 # Make sure proc is unmounted also on failure
11768 trap exit_cleanup EXIT INT
11769
11770 chroot $tmpdir aptitude -y install debconf-utils
11771
11772 # Make sure tasksel autoselection trigger. It need the test scripts
11773 # to return the correct answers.
11774 echo tasksel tasksel/desktop multiselect $desktop | \
11775 chroot $tmpdir debconf-set-selections
11776
11777 # Include the desktop and laptop task
11778 for test in desktop laptop ; do
11779 echo &gt; $tmpdir/usr/lib/tasksel/tests/$test &amp;lt;&amp;lt;EOF
11780 #!/bin/sh
11781 exit 2
11782 EOF
11783 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
11784 done
11785
11786 DEBIAN_FRONTEND=noninteractive
11787 DEBIAN_PRIORITY=critical
11788 export DEBIAN_FRONTEND DEBIAN_PRIORITY
11789 chroot $tmpdir tasksel --new-install
11790
11791 echo deb $mirror $to main &gt; $tmpdir/etc/apt/sources.list
11792 chroot $tmpdir aptitude update
11793 touch $tmpdir/etc/udev/kernel-upgrade
11794 chroot $tmpdir aptitude -y dist-upgrade
11795 fuser -mv
11796 &lt;/pre&gt;&lt;/blockquote&gt;
11797
11798 &lt;p&gt;I suspect it would be useful to test upgrades with both apt-get and
11799 with aptitude, but I have not had time to look at how they behave
11800 differently so far. I hope to get a cron job running to do the test
11801 regularly and post the result on the web. The Gnome upgrade currently
11802 work, while the KDE upgrade fail because of the bug in
11803 kdebase-workspace-data&lt;/p&gt;
11804
11805 &lt;p&gt;I am not quite sure what kind of extract from the huge upgrade logs
11806 (KDE 167 KiB, Gnome 516 KiB) it make sense to include in this blog
11807 post, so I will refrain from trying. I can report that for Gnome,
11808 aptitude report 760 packages upgraded, 448 newly installed, 129 to
11809 remove and 1 not upgraded and 1024MB need to be downloaded while for
11810 KDE the same numbers are 702 packages upgraded, 507 newly installed,
11811 193 to remove and 0 not upgraded and 1117MB need to be downloaded&lt;/p&gt;
11812
11813 &lt;p&gt;I am very happy to notice that the Gnome desktop + laptop upgrade
11814 is able to migrate to dependency based boot sequencing and parallel
11815 booting without a hitch. Was unsure if there were still bugs with
11816 packages failing to clean up their obsolete init.d script during
11817 upgrades, and no such problem seem to affect the Gnome desktop+laptop
11818 packages.&lt;/p&gt;
11819 </description>
11820 </item>
11821
11822 <item>
11823 <title>Upstart or sysvinit - as init.d scripts see it</title>
11824 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</link>
11825 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html</guid>
11826 <pubDate>Sun, 6 Jun 2010 23:55:00 +0200</pubDate>
11827 <description>&lt;p&gt;If Debian is to migrate to upstart on Linux, I expect some init.d
11828 scripts to migrate (some of) their operations to upstart job while
11829 keeping the init.d for hurd and kfreebsd. The packages with such
11830 needs will need a way to get their init.d scripts to behave
11831 differently when used with sysvinit and with upstart. Because of
11832 this, I had a look at the environment variables set when a init.d
11833 script is running under upstart, and when it is not.&lt;/p&gt;
11834
11835 &lt;p&gt;With upstart, I notice these environment variables are set when a
11836 script is started from rcS.d/ (ignoring some irrelevant ones like
11837 COLUMNS):&lt;/p&gt;
11838
11839 &lt;blockquote&gt;&lt;pre&gt;
11840 DEFAULT_RUNLEVEL=2
11841 previous=N
11842 PREVLEVEL=
11843 RUNLEVEL=
11844 runlevel=S
11845 UPSTART_EVENTS=startup
11846 UPSTART_INSTANCE=
11847 UPSTART_JOB=rc-sysinit
11848 &lt;/pre&gt;&lt;/blockquote&gt;
11849
11850 &lt;p&gt;With sysvinit, these environment variables are set for the same
11851 script.&lt;/p&gt;
11852
11853 &lt;blockquote&gt;&lt;pre&gt;
11854 INIT_VERSION=sysvinit-2.88
11855 previous=N
11856 PREVLEVEL=N
11857 RUNLEVEL=S
11858 runlevel=S
11859 &lt;/pre&gt;&lt;/blockquote&gt;
11860
11861 &lt;p&gt;The RUNLEVEL and PREVLEVEL environment variables passed on from
11862 sysvinit are not set by upstart. Not sure if it is intentional or not
11863 to not be compatible with sysvinit in this regard.&lt;/p&gt;
11864
11865 &lt;p&gt;For scripts needing to behave differently when upstart is used,
11866 looking for the UPSTART_JOB environment variable seem to be a good
11867 choice.&lt;/p&gt;
11868 </description>
11869 </item>
11870
11871 <item>
11872 <title>A manual for standards wars...</title>
11873 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</link>
11874 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html</guid>
11875 <pubDate>Sun, 6 Jun 2010 14:15:00 +0200</pubDate>
11876 <description>&lt;p&gt;Via the
11877 &lt;a href=&quot;http://feedproxy.google.com/~r/robweir/antic-atom/~3/QzU4RgoAGMg/weekly-links-10.html&quot;&gt;blog
11878 of Rob Weir&lt;/a&gt; I came across the very interesting essay named
11879 &lt;a href=&quot;http://faculty.haas.berkeley.edu/shapiro/wars.pdf&quot;&gt;The Art of
11880 Standards Wars&lt;/a&gt; (PDF 25 pages). I recommend it for everyone
11881 following the standards wars of today.&lt;/p&gt;
11882 </description>
11883 </item>
11884
11885 <item>
11886 <title>Sitesummary tip: Listing computer hardware models used at site</title>
11887 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</link>
11888 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html</guid>
11889 <pubDate>Thu, 3 Jun 2010 12:05:00 +0200</pubDate>
11890 <description>&lt;p&gt;When using sitesummary at a site to track machines, it is possible
11891 to get a list of the machine types in use thanks to the DMI
11892 information extracted from each machine. The script to do so is
11893 included in the sitesummary package, and here is example output from
11894 the Skolelinux build servers:&lt;/p&gt;
11895
11896 &lt;blockquote&gt;&lt;pre&gt;
11897 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
11898 vendor count
11899 Dell Computer Corporation 1
11900 PowerEdge 1750 1
11901 IBM 1
11902 eserver xSeries 345 -[8670M1X]- 1
11903 Intel 2
11904 [no-dmi-info] 3
11905 maintainer:~#
11906 &lt;/pre&gt;&lt;/blockquote&gt;
11907
11908 &lt;p&gt;The quality of the report depend on the quality of the DMI tables
11909 provided in each machine. Here there are Intel machines without model
11910 information listed with Intel as vendor and no model, and virtual Xen
11911 machines listed as [no-dmi-info]. One can add -l as a command line
11912 option to list the individual machines.&lt;/p&gt;
11913
11914 &lt;p&gt;A larger list is
11915 &lt;a href=&quot;http://narvikskolen.no/sitesummary/&quot;&gt;available from the the
11916 city of Narvik&lt;/a&gt;, which uses Skolelinux on all their shools and also
11917 provide the basic sitesummary report publicly. In their report there
11918 are ~1400 machines. I know they use both Ubuntu and Skolelinux on
11919 their machines, and as sitesummary is available in both distributions,
11920 it is trivial to get all of them to report to the same central
11921 collector.&lt;/p&gt;
11922 </description>
11923 </item>
11924
11925 <item>
11926 <title>KDM fail at boot with NVidia cards - and no one try to fix it?</title>
11927 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html</link>
11928 <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>
11929 <pubDate>Tue, 1 Jun 2010 17:05:00 +0200</pubDate>
11930 <description>&lt;p&gt;It is strange to watch how a bug in Debian causing KDM to fail to
11931 start at boot when an NVidia video card is used is handled. The
11932 problem seem to be that the nvidia X.org driver uses a long time to
11933 initialize, and this duration is longer than kdm is configured to
11934 wait.&lt;/p&gt;
11935
11936 &lt;p&gt;I came across two bugs related to this issue,
11937 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;#583312&lt;/a&gt; initially filed
11938 against initscripts and passed on to nvidia-glx when it became obvious
11939 that the nvidia drivers were involved, and
11940 &lt;a href=&quot;http://bugs.debian.org/524751&quot;&gt;#524751&lt;/a&gt; initially filed against
11941 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.&lt;/p&gt;
11942
11943 &lt;p&gt;To me, it seem that no-one is interested in actually solving the
11944 problem nvidia video card owners experience and make sure the Debian
11945 distribution work out of the box for these users. The nvidia driver
11946 maintainers expect kdm to be set up to wait longer, while kdm expect
11947 the nvidia driver maintainers to fix the driver to start faster, and
11948 while they wait for each other I guess the users end up switching to a
11949 distribution that work for them. I have no idea what the solution is,
11950 but I am pretty sure that waiting for each other is not it.&lt;/p&gt;
11951
11952 &lt;p&gt;I wonder why we end up handling bugs this way.&lt;/p&gt;
11953 </description>
11954 </item>
11955
11956 <item>
11957 <title>Parallellized boot seem to hold up well in Debian/testing</title>
11958 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</link>
11959 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html</guid>
11960 <pubDate>Thu, 27 May 2010 23:55:00 +0200</pubDate>
11961 <description>&lt;p&gt;A few days ago, parallel booting was enabled in Debian/testing.
11962 The feature seem to hold up pretty well, but three fairly serious
11963 issues are known and should be solved:
11964
11965 &lt;p&gt;&lt;ul&gt;
11966
11967 &lt;li&gt;The wicd package seen to
11968 &lt;a href=&quot;http://bugs.debian.org/508289&quot;&gt;break NFS mounting&lt;/a&gt; and
11969 &lt;a href=&quot;http://bugs.debian.org/581586&quot;&gt;network setup&lt;/a&gt; when
11970 parallel booting is enabled. No idea why, but the wicd maintainer
11971 seem to be on the case.&lt;/li&gt;
11972
11973 &lt;li&gt;The nvidia X driver seem to
11974 &lt;a href=&quot;http://bugs.debian.org/583312&quot;&gt;have a race condition&lt;/a&gt;
11975 triggered more easily when parallel booting is in effect. The
11976 maintainer is on the case.&lt;/li&gt;
11977
11978 &lt;li&gt;The sysv-rc package fail to properly enable dependency based boot
11979 sequencing (the shutdown is broken) when old file-rc users
11980 &lt;a href=&quot;http://bugs.debian.org/575080&quot;&gt;try to switch back&lt;/a&gt; to
11981 sysv-rc. One way to solve it would be for file-rc to create
11982 /etc/init.d/.legacy-bootordering, and another is to try to make
11983 sysv-rc more robust. Will investigate some more and probably upload a
11984 workaround in sysv-rc to help those trying to move from file-rc to
11985 sysv-rc get a working shutdown.&lt;/li&gt;
11986
11987 &lt;/ul&gt;&lt;/p&gt;
11988
11989 &lt;p&gt;All in all not many surprising issues, and all of them seem
11990 solvable before Squeeze is released. In addition to these there are
11991 some packages with bugs in their dependencies and run level settings,
11992 which I expect will be fixed in a reasonable time span.&lt;/p&gt;
11993
11994 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
11995 the BTS, please usertag the report to get it to show up at
11996 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
11997 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
11998
11999 &lt;p&gt;Update: Correct bug number to file-rc issue.&lt;/p&gt;
12000 </description>
12001 </item>
12002
12003 <item>
12004 <title>More flexible firmware handling in debian-installer</title>
12005 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</link>
12006 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html</guid>
12007 <pubDate>Sat, 22 May 2010 21:30:00 +0200</pubDate>
12008 <description>&lt;p&gt;After a long break from debian-installer development, I finally
12009 found time today to return to the project. Having to spend less time
12010 working dependency based boot in debian, as it is almost complete now,
12011 definitely helped freeing some time.&lt;/p&gt;
12012
12013 &lt;p&gt;A while back, I ran into a problem while working on Debian Edu. We
12014 include some firmware packages on the Debian Edu CDs, those needed to
12015 get disk and network controllers working. Without having these
12016 firmware packages available during installation, it is impossible to
12017 install Debian Edu on the given machine, and because our target group
12018 are non-technical people, asking them to provide firmware packages on
12019 an external medium is a support pain. Initially, I expected it to be
12020 enough to include the firmware packages on the CD to get
12021 debian-installer to find and use them. This proved to be wrong.
12022 Next, I hoped it was enough to symlink the relevant firmware packages
12023 to some useful location on the CD (tried /cdrom/ and
12024 /cdrom/firmware/). This also proved to not work, and at this point I
12025 found time to look at the debian-installer code to figure out what was
12026 going to work.&lt;/p&gt;
12027
12028 &lt;p&gt;The firmware loading code is in the hw-detect package, and a closer
12029 look revealed that it would only look for firmware packages outside
12030 the installation media, so the CD was never checked for firmware
12031 packages. It would only check USB sticks, floppies and other
12032 &quot;external&quot; media devices. Today I changed it to also look in the
12033 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12034 solve the problem I ran into with Debian edu. I also changed it to
12035 look in /firmware/, to make sure the installer also find firmware
12036 provided in the initrd when booting the installer via PXE, to allow us
12037 to provide the same feature in the PXE setup included in Debian
12038 Edu.&lt;/p&gt;
12039
12040 &lt;p&gt;To make sure firmware deb packages with a license questions are not
12041 activated without asking if the license is accepted, I extended
12042 hw-detect to look for preinst scripts in the firmware packages, and
12043 run these before activating the firmware during installation. The
12044 license question is asked using debconf in the preinst, so this should
12045 solve the issue for the firmware packages I have looked at so far.&lt;/p&gt;
12046
12047 &lt;p&gt;If you want to discuss the details of these features, please
12048 contact us on debian-boot@lists.debian.org.&lt;/p&gt;
12049 </description>
12050 </item>
12051
12052 <item>
12053 <title>Parallellized boot is now the default in Debian/unstable</title>
12054 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</link>
12055 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html</guid>
12056 <pubDate>Fri, 14 May 2010 22:40:00 +0200</pubDate>
12057 <description>&lt;p&gt;Since this evening, parallel booting is the default in
12058 Debian/unstable for machines using dependency based boot sequencing.
12059 Apparently the testing of concurrent booting has been wider than
12060 expected, if I am to believe the
12061 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12062 on debian-devel@&lt;/a&gt;, and I concluded a few days ago to move forward
12063 with the feature this weekend, to give us some time to detect any
12064 remaining problems before Squeeze is frozen. If serious problems are
12065 detected, it is simple to change the default back to sequential boot.
12066 The upload of the new sysvinit package also activate a new upstream
12067 version.&lt;/p&gt;
12068
12069 More information about
12070 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12071 based boot sequencing&lt;/a&gt; is available from the Debian wiki. It is
12072 currently possible to disable parallel booting when one run into
12073 problems caused by it, by adding this line to /etc/default/rcS:&lt;/p&gt;
12074
12075 &lt;blockquote&gt;&lt;pre&gt;
12076 CONCURRENCY=none
12077 &lt;/pre&gt;&lt;/blockquote&gt;
12078
12079 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12080 the BTS, please usertag the report to get it to show up at
12081 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12082 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12083 </description>
12084 </item>
12085
12086 <item>
12087 <title>Sitesummary tip: Listing MAC address of all clients</title>
12088 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</link>
12089 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html</guid>
12090 <pubDate>Fri, 14 May 2010 21:10:00 +0200</pubDate>
12091 <description>&lt;p&gt;In the recent Debian Edu versions, the
12092 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/HowTo/SiteSummary&quot;&gt;sitesummary
12093 system&lt;/a&gt; is used to keep track of the machines in the school
12094 network. Each machine will automatically report its status to the
12095 central server after boot and once per night. The network setup is
12096 also reported, and using this information it is possible to get the
12097 MAC address of all network interfaces in the machines. This is useful
12098 to update the DHCP configuration.&lt;/p&gt;
12099
12100 &lt;p&gt;To give some idea how to use sitesummary, here is a one-liner to
12101 ist all MAC addresses of all machines reporting to sitesummary. Run
12102 this on the collector host:&lt;/p&gt;
12103
12104 &lt;blockquote&gt;&lt;pre&gt;
12105 perl -MSiteSummary -e &#39;for_all_hosts(sub { print join(&quot; &quot;, get_macaddresses(shift)), &quot;\n&quot;; });&#39;
12106 &lt;/pre&gt;&lt;/blockquote&gt;
12107
12108 &lt;p&gt;This will list all MAC addresses assosiated with all machine, one
12109 line per machine and with space between the MAC addresses.&lt;/p&gt;
12110
12111 &lt;p&gt;To allow system administrators easier job at adding static DHCP
12112 addresses for hosts, it would be possible to extend this to fetch
12113 machine information from sitesummary and update the DHCP and DNS
12114 tables in LDAP using this information. Such tool is unfortunately not
12115 written yet.&lt;/p&gt;
12116 </description>
12117 </item>
12118
12119 <item>
12120 <title>systemd, an interesting alternative to upstart</title>
12121 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</link>
12122 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html</guid>
12123 <pubDate>Thu, 13 May 2010 22:20:00 +0200</pubDate>
12124 <description>&lt;p&gt;The last few days a new boot system called
12125 &lt;a href=&quot;http://www.freedesktop.org/wiki/Software/systemd&quot;&gt;systemd&lt;/a&gt;
12126 has been
12127 &lt;a href=&quot;http://0pointer.de/blog/projects/systemd.html&quot;&gt;introduced&lt;/a&gt;
12128
12129 to the free software world. I have not yet had time to play around
12130 with it, but it seem to be a very interesting alternative to
12131 &lt;a href=&quot;http://upstart.ubuntu.com/&quot;&gt;upstart&lt;/a&gt;, and might prove to be
12132 a good alternative for Debian when we are able to switch to an event
12133 based boot system. Tollef is
12134 &lt;a href=&quot;http://bugs.debian.org/580814&quot;&gt;in the process&lt;/a&gt; of getting
12135 systemd into Debian, and I look forward to seeing how well it work. I
12136 like the fact that systemd handles init.d scripts with dependency
12137 information natively, allowing them to run in parallel where upstart
12138 at the moment do not.&lt;/p&gt;
12139
12140 &lt;p&gt;Unfortunately do systemd have the same problem as upstart regarding
12141 platform support. It only work on recent Linux kernels, and also need
12142 some new kernel features enabled to function properly. This means
12143 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12144 system. Not sure how that will be handled if systemd proves to be the
12145 way forward.&lt;/p&gt;
12146
12147 &lt;p&gt;In the mean time, based on the
12148 &lt;a href=&quot;http://lists.debian.org/debian-devel/2010/05/msg00122.html&quot;&gt;input
12149 on debian-devel@&lt;/a&gt; regarding parallel booting in Debian, I have
12150 decided to enable full parallel booting as the default in Debian as
12151 soon as possible (probably this weekend or early next week), to see if
12152 there are any remaining serious bugs in the init.d dependencies. A
12153 new version of the sysvinit package implementing this change is
12154 already in experimental. If all go well, Squeeze will be released
12155 with parallel booting enabled by default.&lt;/p&gt;
12156 </description>
12157 </item>
12158
12159 <item>
12160 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing</title>
12161 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</link>
12162 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html</guid>
12163 <pubDate>Thu, 6 May 2010 23:25:00 +0200</pubDate>
12164 <description>&lt;p&gt;These days, the init.d script dependencies in Squeeze are quite
12165 complete, so complete that it is actually possible to run all the
12166 init.d scripts in parallell based on these dependencies. If you want
12167 to test your Squeeze system, make sure
12168 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12169 based boot sequencing&lt;/a&gt; is enabled, and add this line to
12170 /etc/default/rcS:&lt;/p&gt;
12171
12172 &lt;blockquote&gt;&lt;pre&gt;
12173 CONCURRENCY=makefile
12174 &lt;/pre&gt;&lt;/blockquote&gt;
12175
12176 &lt;p&gt;That is it. It will cause sysv-rc to use the startpar tool to run
12177 scripts in parallel using the dependency information stored in
12178 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
12179 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
12180 to try to start the kdm and gdm scripts as early as possible, and will
12181 start the facilities required by kdm or gdm as early as possible to
12182 make this happen.&lt;/p&gt;
12183
12184 &lt;p&gt;Give it a try, and see if you like the result. If some services
12185 fail to start properly, it is most likely because they have incomplete
12186 init.d script dependencies in their startup script (or some of their
12187 dependent scripts have incomplete dependencies). Report bugs and get
12188 the package maintainers to fix it. :)&lt;/p&gt;
12189
12190 &lt;p&gt;Running scripts in parallel could be the default in Debian when we
12191 manage to get the init.d script dependencies complete and correct. I
12192 expect we will get there in Squeeze+1, if we get manage to test and
12193 fix the remaining issues.&lt;/p&gt;
12194
12195 &lt;p&gt;If you report any problems with dependencies in init.d scripts to
12196 the BTS, please usertag the report to get it to show up at
12197 &lt;a href=&quot;http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org&quot;&gt;the
12198 list of usertagged bugs related to this&lt;/a&gt;.&lt;/p&gt;
12199 </description>
12200 </item>
12201
12202 <item>
12203 <title>Debian has switched to dependency based boot sequencing</title>
12204 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</link>
12205 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html</guid>
12206 <pubDate>Mon, 27 Jul 2009 23:50:00 +0200</pubDate>
12207 <description>&lt;p&gt;Since this evening, with the upload of sysvinit version 2.87dsf-2,
12208 and the upload of insserv version 1.12.0-10 yesterday, Debian unstable
12209 have been migrated to using dependency based boot sequencing. This
12210 conclude work me and others have been doing for the last three days.
12211 It feels great to see this finally part of the default Debian
12212 installation. Now we just need to weed out the last few problems that
12213 are bound to show up, to get everything ready for Squeeze.&lt;/p&gt;
12214
12215 &lt;p&gt;The next step is migrating /sbin/init from sysvinit to upstart, and
12216 fixing the more fundamental problem of handing the event based
12217 non-predictable kernel in the early boot.&lt;/p&gt;
12218 </description>
12219 </item>
12220
12221 <item>
12222 <title>Taking over sysvinit development</title>
12223 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</link>
12224 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html</guid>
12225 <pubDate>Wed, 22 Jul 2009 23:00:00 +0200</pubDate>
12226 <description>&lt;p&gt;After several years of frustration with the lack of activity from
12227 the existing sysvinit upstream developer, I decided a few weeks ago to
12228 take over the package and become the new upstream. The number of
12229 patches to track for the Debian package was becoming a burden, and the
12230 lack of synchronization between the distribution made it hard to keep
12231 the package up to date.&lt;/p&gt;
12232
12233 &lt;p&gt;On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
12234 and my Debian co-maintainer Kel Modderman. About 10 days ago, I made
12235 a new upstream tarball with version number 2.87dsf (for Debian, SuSe
12236 and Fedora), based on the patches currently in use in these
12237 distributions. We Debian maintainers plan to move to this tarball as
12238 the new upstream as soon as we find time to do the merge. Since the
12239 new tarball was created, we agreed with Werner at SuSe to make a new
12240 upstream project at &lt;a href=&quot;http://savannah.nongnu.org/&quot;&gt;Savannah&lt;/a&gt;, and continue
12241 development there. The project is registered and currently waiting
12242 for approval by the Savannah administrators, and as soon as it is
12243 approved, we will import the old versions from svn and continue
12244 working on the future release.&lt;/p&gt;
12245
12246 &lt;p&gt;It is a bit ironic that this is done now, when some of the involved
12247 distributions are moving to upstart as a syvinit replacement.&lt;/p&gt;
12248 </description>
12249 </item>
12250
12251 <item>
12252 <title>Debian boots quicker and quicker</title>
12253 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</link>
12254 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html</guid>
12255 <pubDate>Wed, 24 Jun 2009 21:40:00 +0200</pubDate>
12256 <description>&lt;p&gt;I spent Monday and tuesday this week in London with a lot of the
12257 people involved in the boot system on Debian and Ubuntu, to see if we
12258 could find more ways to speed up the boot system. This was an Ubuntu
12259 funded
12260 &lt;a href=&quot;https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint&quot;&gt;developer
12261 gathering&lt;/a&gt;. It was quite productive. We also discussed the future
12262 of boot systems, and ways to handle the increasing number of boot
12263 issues introduced by the Linux kernel becoming more and more
12264 asynchronous and event base. The Ubuntu approach using udev and
12265 upstart might be a good way forward. Time will show.&lt;/p&gt;
12266
12267 &lt;p&gt;Anyway, there are a few ways at the moment to speed up the boot
12268 process in Debian. All of these should be applied to get a quick
12269 boot:&lt;/p&gt;
12270
12271 &lt;ul&gt;
12272
12273 &lt;li&gt;Use dash as /bin/sh.&lt;/li&gt;
12274
12275 &lt;li&gt;Disable the init.d/hwclock*.sh scripts and make sure the hardware
12276 clock is in UTC.&lt;/li&gt;
12277
12278 &lt;li&gt;Install and activate the insserv package to enable
12279 &lt;a href=&quot;http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot&quot;&gt;dependency
12280 based boot sequencing&lt;/a&gt;, and enable concurrent booting.&lt;/li&gt;
12281
12282 &lt;/ul&gt;
12283
12284 These points are based on the Google summer of code work done by
12285 &lt;a href=&quot;http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/&quot;&gt;Carlos
12286 Villegas&lt;/a&gt;.
12287
12288 &lt;p&gt;Support for makefile-style concurrency during boot was uploaded to
12289 unstable yesterday. When we tested it, we were able to cut 6 seconds
12290 from the boot sequence. It depend on very correct dependency
12291 declaration in all init.d scripts, so I expect us to find edge cases
12292 where the dependences in some scripts are slightly wrong when we start
12293 using this.&lt;/p&gt;
12294
12295 &lt;p&gt;On our IRC channel for this effort, #pkg-sysvinit, a new idea was
12296 introduced by Raphael Geissert today, one that could affect the
12297 startup speed as well. Instead of starting some scripts concurrently
12298 from rcS.d/ and another set of scripts from rc2.d/, it would be
12299 possible to run a of them in the same process. A quick way to test
12300 this would be to enable insserv and run &#39;mv /etc/rc2.d/S* /etc/rcS.d/;
12301 insserv&#39;. Will need to test if that work. :)&lt;/p&gt;
12302 </description>
12303 </item>
12304
12305 <item>
12306 <title>BSAs påstander om piratkopiering møter motstand</title>
12307 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</link>
12308 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html</guid>
12309 <pubDate>Sun, 17 May 2009 23:05:00 +0200</pubDate>
12310 <description>&lt;p&gt;Hvert år de siste årene har BSA, lobbyfronten til de store
12311 programvareselskapene som Microsoft og Apple, publisert en rapport der
12312 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
12313 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
12314 dager siden kom
12315 &lt;a href=&quot;http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf&quot;&gt;siste
12316 rapport&lt;/a&gt;, og det er flere kritiske kommentarer publisert de siste
12317 dagene. Et spesielt interessant kommentar fra Sverige,
12318 &lt;a href=&quot;http://www.idg.se/2.1085/1.229795/bsa-hoftade-sverigesiffror&quot;&gt;BSA
12319 höftade Sverigesiffror&lt;/a&gt;, oppsummeres slik:&lt;/p&gt;
12320
12321 &lt;blockquote&gt;
12322 I sin senaste rapport slår BSA fast att 25 procent av all mjukvara i
12323 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
12324 företag. &quot;Man bör nog kanske inte se de här siffrorna som helt
12325 exakta&quot;, säger BSAs Sverigechef John Hugosson.
12326 &lt;/blockquote&gt;
12327
12328 &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
12329 href=&quot;http://www.vnunet.com/vnunet/comment/2242134/bsa-piracy-figures-shot-reality&quot;&gt;BSA
12330 piracy figures need a shot of reality&lt;/a&gt; og &lt;a
12331 href=&quot;http://www.michaelgeist.ca/content/view/3958/125/&quot;&gt;Does The WIPO
12332 Copyright Treaty Work?&lt;/a&gt;&lt;/p&gt;
12333
12334 &lt;p&gt;Fant lenkene via &lt;a
12335 href=&quot;http://tech.slashdot.org/article.pl?sid=09/05/17/1632242&quot;&gt;oppslag
12336 på Slashdot&lt;/a&gt;.&lt;/p&gt;
12337 </description>
12338 </item>
12339
12340 <item>
12341 <title>IDG mener linux i servermarkedet vil vokse med 21% i 2009</title>
12342 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</link>
12343 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html</guid>
12344 <pubDate>Thu, 7 May 2009 22:30:00 +0200</pubDate>
12345 <description>&lt;p&gt;Kom over
12346 &lt;a href=&quot;http://news.cnet.com/8301-13505_3-10216873-16.html&quot;&gt;interessante
12347 tall&lt;/a&gt; fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
12348 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
12349 jobber til daglig. En rask opptelling forteller meg at vi har 490
12350 (61%) fysiske unix-tjener (mest linux men også noen solaris) og 196
12351 (25%) windowstjenere, samt 112 (14%) virtuelle unix-tjenere. Med den
12352 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.&lt;/p&gt;
12353 </description>
12354 </item>
12355
12356 <item>
12357 <title>Kryptert harddisk - naturligvis</title>
12358 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</link>
12359 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html</guid>
12360 <pubDate>Sat, 2 May 2009 15:30:00 +0200</pubDate>
12361 <description>&lt;p&gt;&lt;a href=&quot;http://www.dagensit.no/trender/article1658676.ece&quot;&gt;Dagens
12362 IT melder&lt;/a&gt; at Intel hevder at det er dyrt å miste en datamaskin,
12363 når en tar tap av arbeidstid, fortrolige dokumenter,
12364 personopplysninger og alt annet det innebærer. Det er ingen tvil om
12365 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
12366 til at jeg har kryptert harddisken på både kontormaskinen og min
12367 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
12368 komme på avveie, den første informasjon relatert til jobben min ved
12369 Universitetet i Oslo, og den andre relatert til blant annet
12370 foreningsarbeide. Kryptering av diskene gjør at det er lite
12371 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
12372 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
12373 og en reboot vil gjøre at de ber om passord før de vil starte opp.
12374 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
12375 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
12376 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
12377 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
12378 det er gjort slik jeg gjør det er minimale, og gevinstene er
12379 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
12380 maskinen reinstalleres og alt er tapt.&lt;/p&gt;
12381
12382 &lt;p&gt;Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
12383 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
12384 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
12385 er for min del høyere enn gevinsten. Jeg tror oddsene for at
12386 f.eks. etteretningsorganisasjoner har glede av å titte på mine
12387 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
12388 gjøre det vanskeligere for angripere med kompetanse og ressurser er
12389 betydelige.&lt;/p&gt;
12390 </description>
12391 </item>
12392
12393 <item>
12394 <title>Two projects that have improved the quality of free software a lot</title>
12395 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</link>
12396 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html</guid>
12397 <pubDate>Sat, 2 May 2009 15:00:00 +0200</pubDate>
12398 <description>&lt;p&gt;There are two software projects that have had huge influence on the
12399 quality of free software, and I wanted to mention both in case someone
12400 do not yet know them.&lt;/p&gt;
12401
12402 &lt;p&gt;The first one is &lt;a href=&quot;http://valgrind.org/&quot;&gt;valgrind&lt;/a&gt;, a
12403 tool to detect and expose errors in the memory handling of programs.
12404 It is easy to use, all one need to do is to run &#39;valgrind program&#39;,
12405 and it will report any problems on stdout. It is even better if the
12406 program include debug information. With debug information, it is able
12407 to report the source file name and line number where the problem
12408 occurs. It can report things like &#39;reading past memory block in file
12409 X line N, the memory block was allocated in file Y, line M&#39;, and
12410 &#39;using uninitialised value in control logic&#39;. This tool has made it
12411 trivial to investigate reproducible crash bugs in programs, and have
12412 reduced the number of this kind of bugs in free software a lot.
12413
12414 &lt;p&gt;The second one is
12415 &lt;a href=&quot;http://en.wikipedia.org/wiki/Coverity&quot;&gt;Coverity&lt;/a&gt; which is
12416 a source code checker. It is able to process the source of a program
12417 and find problems in the logic without running the program. It
12418 started out as the Stanford Checker and became well known when it was
12419 used to find bugs in the Linux kernel. It is now a commercial tool
12420 and the company behind it is running
12421 &lt;a href=&quot;http://www.scan.coverity.com/&quot;&gt;a community service&lt;/a&gt; for the
12422 free software community, where a lot of free software projects get
12423 their source checked for free. Several thousand defects have been
12424 found and fixed so far. It can find errors like &#39;lock L taken in file
12425 X line N is never released if exiting in line M&#39;, or &#39;the code in file
12426 Y lines O to P can never be executed&#39;. The projects included in the
12427 community service project have managed to get rid of a lot of
12428 reliability problems thanks to Coverity.&lt;/p&gt;
12429
12430 &lt;p&gt;I believe tools like this, that are able to automatically find
12431 errors in the source, are vital to improve the quality of software and
12432 make sure we can get rid of the crashing and failing software we are
12433 surrounded by today.&lt;/p&gt;
12434 </description>
12435 </item>
12436
12437 <item>
12438 <title>No patch is not better than a useless patch</title>
12439 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</link>
12440 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html</guid>
12441 <pubDate>Tue, 28 Apr 2009 09:30:00 +0200</pubDate>
12442 <description>&lt;p&gt;Julien Blache
12443 &lt;a href=&quot;http://blog.technologeek.org/2009/04/12/214&quot;&gt;claim that no
12444 patch is better than a useless patch&lt;/a&gt;. I completely disagree, as a
12445 patch allow one to discuss a concrete and proposed solution, and also
12446 prove that the issue at hand is important enough for someone to spent
12447 time on fixing it. No patch do not provide any of these positive
12448 properties.&lt;/p&gt;
12449 </description>
12450 </item>
12451
12452 <item>
12453 <title>Standardize on protocols and formats, not vendors and applications</title>
12454 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</link>
12455 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html</guid>
12456 <pubDate>Mon, 30 Mar 2009 11:50:00 +0200</pubDate>
12457 <description>&lt;p&gt;Where I work at the University of Oslo, one decision stand out as a
12458 very good one to form a long lived computer infrastructure. It is the
12459 simple one, lost by many in todays computer industry: Standardize on
12460 open network protocols and open exchange/storage formats, not applications.
12461 Applications come and go, while protocols and files tend to stay, and
12462 thus one want to make it easy to change application and vendor, while
12463 avoiding conversion costs and locking users to a specific platform or
12464 application.&lt;/p&gt;
12465
12466 &lt;p&gt;This approach make it possible to replace the client applications
12467 independently of the server applications. One can even allow users to
12468 use several different applications as long as they handle the selected
12469 protocol and format. In the normal case, only one client application
12470 is recommended and users only get help if they choose to use this
12471 application, but those that want to deviate from the easy path are not
12472 blocked from doing so.&lt;/p&gt;
12473
12474 &lt;p&gt;It also allow us to replace the server side without forcing the
12475 users to replace their applications, and thus allow us to select the
12476 best server implementation at any moment, when scale and resouce
12477 requirements change.&lt;/p&gt;
12478
12479 &lt;p&gt;I strongly recommend standardizing - on open network protocols and
12480 open formats, but I would never recommend standardizing on a single
12481 application that do not use open network protocol or open formats.&lt;/p&gt;
12482 </description>
12483 </item>
12484
12485 <item>
12486 <title>Returning from Skolelinux developer gathering</title>
12487 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</link>
12488 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html</guid>
12489 <pubDate>Sun, 29 Mar 2009 21:00:00 +0200</pubDate>
12490 <description>&lt;p&gt;I&#39;m sitting on the train going home from this weekends Debian
12491 Edu/Skolelinux development gathering. I got a bit done tuning the
12492 desktop, and looked into the dynamic service location protocol
12493 implementation avahi. It look like it could be useful for us. Almost
12494 30 people participated, and I believe it was a great environment to
12495 get to know the Skolelinux system. Walter Bender, involved in the
12496 development of the Sugar educational platform, presented his stuff and
12497 also helped me improve my OLPC installation. He also showed me that
12498 his Turtle Art application can be used in standalone mode, and we
12499 agreed that I would help getting it packaged for Debian. As a
12500 standalone application it would be great for Debian Edu. We also
12501 tried to get the video conferencing working with two OLPCs, but that
12502 proved to be too hard for us. The application seem to need more work
12503 before it is ready for me. I look forward to getting home and relax
12504 now. :)&lt;/p&gt;
12505 </description>
12506 </item>
12507
12508 <item>
12509 <title>Time for new LDAP schemas replacing RFC 2307?</title>
12510 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</link>
12511 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html</guid>
12512 <pubDate>Sun, 29 Mar 2009 20:30:00 +0200</pubDate>
12513 <description>&lt;p&gt;The state of standardized LDAP schemas on Linux is far from
12514 optimal. There is RFC 2307 documenting one way to store NIS maps in
12515 LDAP, and a modified version of this normally called RFC 2307bis, with
12516 some modifications to be compatible with Active Directory. The RFC
12517 specification handle the content of a lot of system databases, but do
12518 not handle DNS zones and DHCP configuration.&lt;/p&gt;
12519
12520 &lt;p&gt;In &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Debian Edu/Skolelinux&lt;/a&gt;,
12521 we would like to store information about users, SMB clients/hosts,
12522 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
12523 and LTSP configuration in LDAP. These objects have a lot in common,
12524 but with the current LDAP schemas it is not possible to have one
12525 object per entity. For example, one need to have at least three LDAP
12526 objects for a given computer, one with the SMB related stuff, one with
12527 DNS information and another with DHCP information. The schemas
12528 provided for DNS and DHCP are impossible to combine into one LDAP
12529 object. In addition, it is impossible to implement quick queries for
12530 netgroup membership, because of the way NIS triples are implemented.
12531 It just do not scale. I believe it is time for a few RFC
12532 specifications to cleam up this mess.&lt;/p&gt;
12533
12534 &lt;p&gt;I would like to have one LDAP object representing each computer in
12535 the network, and this object can then keep the SMB (ie host key), DHCP
12536 (mac address/name) and DNS (name/IP address) settings in one place.
12537 It need to be efficently stored to make sure it scale well.&lt;/p&gt;
12538
12539 &lt;p&gt;I would also like to have a quick way to map from a user or
12540 computer and to the net group this user or computer is a member.&lt;/p&gt;
12541
12542 &lt;p&gt;Active Directory have done a better job than unix heads like myself
12543 in this regard, and the unix side need to catch up. Time to start a
12544 new IETF work group?&lt;/p&gt;
12545 </description>
12546 </item>
12547
12548 <item>
12549 <title>Endelig er Debian Lenny gitt ut</title>
12550 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</link>
12551 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html</guid>
12552 <pubDate>Sun, 15 Feb 2009 11:50:00 +0100</pubDate>
12553 <description>&lt;p&gt;Endelig er &lt;a href=&quot;http://www.debian.org/&quot;&gt;Debian&lt;/a&gt;
12554 &lt;a href=&quot;http://www.debian.org/News/2009/20090214&quot;&gt;Lenny&lt;/a&gt; gitt ut.
12555 Et langt steg videre for Debian-prosjektet, og en rekke nye
12556 programpakker blir nå tilgjengelig for de av oss som bruker den
12557 stabile utgaven av Debian. Neste steg er nå å få
12558 &lt;a href=&quot;http://www.skolelinux.org/&quot;&gt;Skolelinux&lt;/a&gt; /
12559 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/&quot;&gt;Debian Edu&lt;/a&gt; ferdig
12560 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
12561 slippes løs på skolene. Takk til alle debian-utviklerne som har
12562 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
12563 bootsekvens tilgjengelig i stabil utgave, vha pakken
12564 &lt;tt&gt;insserv&lt;/tt&gt;.&lt;/p&gt;
12565 </description>
12566 </item>
12567
12568 <item>
12569 <title>Devcamp brought us closer to the Lenny based Debian Edu release</title>
12570 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</link>
12571 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html</guid>
12572 <pubDate>Sun, 7 Dec 2008 12:00:00 +0100</pubDate>
12573 <description>&lt;p&gt;This weekend we had a small developer gathering for Debian Edu in
12574 Oslo. Most of Saturday was used for the general assemly for the
12575 member organization, but the rest of the weekend I used to tune the
12576 LTSP installation. LTSP now work out of the box on the 10-network.
12577 Acer Aspire One proved to be a very nice thin client, with both
12578 screen, mouse and keybard in a small box. Was working on getting the
12579 diskless workstation setup configured out of the box, but did not
12580 finish it before the weekend was up.&lt;/p&gt;
12581
12582 &lt;p&gt;Did not find time to look at the 4 VGA cards in one box we got from
12583 the Brazilian group, so that will have to wait for the next
12584 development gathering. Would love to have the Debian Edu installer
12585 automatically detect and configure a multiseat setup when it find one
12586 of these cards.&lt;/p&gt;
12587 </description>
12588 </item>
12589
12590 <item>
12591 <title>The sorry state of multimedia browser plugins in Debian</title>
12592 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</link>
12593 <guid isPermaLink="true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html</guid>
12594 <pubDate>Tue, 25 Nov 2008 00:10:00 +0100</pubDate>
12595 <description>&lt;p&gt;Recently I have spent some time evaluating the multimedia browser
12596 plugins available in Debian Lenny, to see which one we should use by
12597 default in Debian Edu. We need an embedded video playing plugin with
12598 control buttons to pause or stop the video, and capable of streaming
12599 all the multimedia content available on the web. The test results and
12600 notes are available on
12601 &lt;a href=&quot;http://wiki.debian.org/DebianEdu/BrowserMultimedia&quot;&gt;the
12602 Debian wiki&lt;/a&gt;. I was surprised how few of the plugins are able to
12603 fill this need. My personal video player favorite, VLC, has a really
12604 bad plugin which fail on a lot of the test pages. A lot of the MIME
12605 types I would expect to work with any free software player (like
12606 video/ogg), just do not work. And simple formats like the
12607 audio/x-mplegurl format (m3u playlists), just isn&#39;t supported by the
12608 totem and vlc plugins. I hope the situation will improve soon. No
12609 wonder sites use the proprietary Adobe flash to play video.&lt;/p&gt;
12610
12611 &lt;p&gt;For Lenny, we seem to end up with the mplayer plugin. It seem to
12612 be the only one fitting our needs. :/&lt;/p&gt;
12613 </description>
12614 </item>
12615
12616 </channel>
12617 </rss>