1 <?xml version=
"1.0" encoding=
"utf-8"?>
2 <rss version='
2.0' xmlns:lj='http://www.livejournal.org/rss/lj/
1.0/'
>
4 <title>Petter Reinholdtsen - Entries tagged debian
</title>
5 <description>Entries tagged debian
</description>
6 <link>https://people.skolelinux.org/pere/blog/
</link>
10 <title>Managing and using ONVIF IP cameras with Linux
</title>
11 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</link>
12 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</guid>
13 <pubDate>Wed,
19 Oct
2022 12:
30:
00 +
0200</pubDate>
14 <description><p
>Recently I have been looking at how to control and collect data
15 from a handful IP cameras using Linux. I both wanted to change their
16 settings and to make their imagery available via a free software
17 service under my control. Here is a summary of the tools I found.
</p
>
19 <p
>First I had to identify the cameras and their protocols. As far as
20 I could tell, they were using some SOAP looking protocol and their
21 internal web server seem to only work with Microsoft Internet Explorer
22 with some proprietary binary plugin, which in these days of course is
23 a security disaster and also made it impossible for me to use the
24 camera web interface. Luckily I discovered that the SOAP looking
25 protocol is actually following
<a href=
"https://www.onvif.org/
">the
26 ONVIF specification
</a
>, which seem to be supported by a lot of IP
27 cameras these days.
</p
>
29 <p
>Once the protocol was identified, I was able to find what appear to
30 be the most popular way to configure ONVIF cameras, the free software
32 <a href=
"https://sourceforge.net/projects/onvifdm/
">ONVIF Device
33 Manager
</a
>. Lacking any other options at the time, I tried
34 unsuccessfully to get it running using Wine, but was missing a dotnet
35 40 library and I found no way around it to run it on Linux.
</p
>
37 <p
>The next tool I found to configure the cameras were a non-free Linux Qt
38 client
<a href=
"https://www.lingodigit.com/onvif_nvcdemo.html
">ONVIF
39 Device Tool
</a
>. I did not like its terms of use, so did not spend
40 much time on it.
</p
>
42 <p
>To collect the video and make it available in a web interface, I
43 found the Zoneminder tool in Debian. A recent version was able to
44 automatically detect and configure ONVIF devices, so I could use it to
45 set up motion detection in and collection of the camera output. I had
46 initial problems getting the ONVIF autodetection to work, as both
47 Firefox and Chromium
<a href=
"https://bugs.debian.org/
1001188">refused
48 the inter-tab communication
</a
> being used by the Zoneminder web
49 pages, but managed to get konqueror to work. Apparently the
"Enhanced
50 Tracking Protection
" in Firefox cause the problem. I ended up
51 upgrading to the Bookworm edition of Zoneminder in the process to try
52 to fix the issue, and believe the problem might be solved now.
</p
>
54 <p
>In the process I came across the nice Linux GUI tool
55 <a href=
"https://gitlab.com/caspermeijn/onvifviewer/
">ONVIF Viewer
</a
>
56 allowing me to preview the camera output and validate the login
57 passwords required. Sadly its author has grown tired of maintaining
58 the software, so it might not see any future updates. Which is sad,
59 as the viewer is sightly unstable and the picture tend to lock up.
60 Note, this lockup might be due to limitations in the cameras and not
61 the viewer implementation. I suspect the camera is only able to
62 provide pictures to one client at the time, and the Zoneminder feed
63 might interfere with the GUI viewer. I have
64 <a href=
"https://bugs.debian.org/
1000820">asked for the tool to be
65 included in Debian
</a
>.
</p
>
67 <p
>Finally, I found what appear to be very nice Linux free software
68 replacement for the Windows tool, named
69 <a href=
"https://github.com/sr99622/libonvif/
">libonvif
</a
>. It
70 provide a C library to talk to ONVIF devices as well as a command line
71 and GUI tool using the library. Using the GUI tool I was able to change
72 the admin passwords and update other settings of the cameras. I have
73 <a href=
"https://bugs.debian.org/
1021980">asked for the package to be
74 included in Debian
</a
>.
</p
>
76 <p
>As usual, if you use Bitcoin and want to show your support of my
77 activities, please send Bitcoin donations to my address
78 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
80 <p
><strong
>Update
2022-
10-
20</strong
>: Since my initial publication of
81 this text, I got several suggestions for more free software Linux
82 tools. There is
<a href=
"https://github.com/quatanium/python-onvif
">a
83 ONVIF python library
</a
> (already
84 <a href=
"https://bugs.debian.org/
824240">requested into Debian
</a
>) and
85 <a href=
"https://github.com/FalkTannhaeuser/python-onvif-zeep
">a python
3
86 fork
</a
> using a different SOAP dependency. There is also
87 <a href=
"https://www.home-assistant.io/integrations/onvif/
">support for
88 ONVIF in Home Assistant
</a
>, and there is an alternative to Zoneminder
89 called
<a href=
"https://www.shinobi.video/
">Shinobi
</a
>. The latter
90 two are not included in Debian either. I have not tested any of these
96 <title>Time to translate the Bullseye edition of the Debian Administrator
's Handbook
</title>
97 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</link>
98 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</guid>
99 <pubDate>Mon,
12 Sep
2022 15:
45:
00 +
0200</pubDate>
100 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2020-
10-
20-debian-handbook-nb-testprint.jpeg
" width=
"60%
"/
></p
>
102 <p
>(The picture is of the previous edition.)
</p
>
104 <p
>Almost two years after the previous Norwegian Bokmål translation of
105 the
"<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
106 Handbook
</a
>" was published, a new edition is finally being prepared. The
107 english text is updated, and it is time to start working on the
108 translations. Around
37 percent of the strings have been updated, one
109 way or another, and the translations starting from a complete Debian Buster
110 edition now need to bring their translation up from
63% to
100%. The
111 complete book is licensed using a Creative Commons license, and has
112 been published in several languages over the years. The translations
113 are done by volunteers to bring Linux in their native tongue. The
114 last time I checked, it complete text was available in English,
115 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
116 In addition, work has been started for Arabic (Morocco), Catalan,
117 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
118 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
119 Romanian, Russian, Swedish, Turkish and Vietnamese.
</p
>
121 <p
>The translation is conducted on
122 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
123 hosted weblate project page
</a
>. Prospective translators are
124 recommeded to subscribe to
125 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
126 translators mailing list
</a
> and should also check out
127 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
128 contributors
</a
>.
</p
>
130 <p
>I am one of the Norwegian Bokmål translators of this book, and we
131 have just started. Your contribution is most welcome.
</p
>
133 <p
>As usual, if you use Bitcoin and want to show your support of my
134 activities, please send Bitcoin donations to my address
135 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
140 <title>Automatic LinuxCNC servo PID tuning?
</title>
141 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</link>
142 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</guid>
143 <pubDate>Sat,
16 Jul
2022 22:
30:
00 +
0200</pubDate>
144 <description><p
>While working on a CNC with servo motors controlled by the
145 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>
146 <a href=
"https://en.wikipedia.org/wiki/PID_controller
">PID
147 controller
</a
>, I recently had to learn how to tune the collection of values
148 that control such mathematical machinery that a PID controller is. It
149 proved to be a lot harder than I hoped, and I still have not succeeded
150 in getting the Z PID controller to successfully defy gravity, nor X
151 and Y to move accurately and reliably. But while climbing up this
152 rather steep learning curve, I discovered that some motor control
153 systems are able to tune their PID controllers. I got the impression
154 from the documentation that LinuxCNC were not. This proved to be not
157 <p
>The LinuxCNC
158 <a href=
"http://linuxcnc.org/docs/html/man/man9/pid
.9.html
">pid
159 component
</a
> is the recommended PID controller to use. It uses eight
160 constants
<tt
>Pgain
</tt
>,
<tt
>Igain
</tt
>,
<tt
>Dgain
</tt
>,
161 <tt
>bias
</tt
>,
<tt
>FF0
</tt
>,
<tt
>FF1
</tt
>,
<tt
>FF2
</tt
> and
162 <tt
>FF3
</tt
> to calculate the output value based on current and wanted
163 state, and all of these need to have a sensible value for the
164 controller to behave properly. Note, there are even more values
165 involved, theser are just the most important ones. In my case I need
166 the X, Y and Z axes to follow the requested path with little error.
167 This has proved quite a challenge for someone who have never tuned a
168 PID controller before, but there is at least some help to be found.
170 <p
>I discovered that included in LinuxCNC was this old PID component
171 at_pid claiming to have auto tuning capabilities. Sadly it had been
172 neglected since
2011, and could not be used as a plug in replacement
173 for the default pid component. One would have to rewriting the
174 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
175 to quickly test auto tuning to see if it did a better job than me at
176 figuring out good P, I and D values to use.
</p
>
178 <p
>I decided to have a look if the situation could be improved. This
179 involved trying to understand the code and history of the pid and
180 at_pid components. Apparently they had a common ancestor, as code
181 structure, comments and variable names were quite close to each other.
182 Sadly this was not reflected in the git history, making it hard to
183 figure out what really happened. My guess is that the author of
184 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c
">at_pid.c
</a
>
186 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c
">pid.c
</a
>,
187 rewrote it to follow the structure he wished pid.c to have, then added
188 support for auto tuning and finally got it included into the LinuxCNC
189 repository. The restructuring and lack of early history made it
190 harder to figure out which part of the code were relevant to the auto
191 tuning, and which part of the code needed to be updated to work the
192 same way as the current pid.c implementation. I started by trying to
193 isolate relevant changes in pid.c, and applying them to at_pid.c. My
194 aim was to make sure the at_pid component could replace the pid
195 component with a simple change in the HAL setup loadrt line, without
196 having to
"rewire
" the rest of the HAL configuration. After a few
197 hours following this approach, I had learned quite a lot about the
198 code structure of both components, while concluding I was heading down
199 the wrong rabbit hole, and should get back to the surface and find a
200 different path.
</p
>
202 <p
>For the second attempt, I decided to throw away all the PID control
203 related part of the original at_pid.c, and instead isolate and lift
204 the auto tuning part of the code and inject it into a copy of pid.c.
205 This ensured compatibility with the current pid component, while
206 adding auto tuning as a run time option. To make it easier to identify
207 the relevant parts in the future, I wrapped all the auto tuning code
208 with
'#ifdef AUTO_TUNER
'. The end result behave just like the current
209 pid component by default, as that part of the code is identical. The
210 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
1820">end result
211 entered the LinuxCNC master branch
</a
> a few days ago.
</p
>
213 <p
>To enable auto tuning, one need to set a few HAL pins in the PID
214 component. The most important ones are
<tt
>tune-effort
</tt
>,
215 <tt
>tune-mode
</tt
> and
<tt
>tune-start
</tt
>. But lets take a step
216 back, and see what the auto tuning code will do. I do not know the
217 mathematical foundation of the at_pid algorithm, but from observation
218 I can tell that the algorithm will, when enabled, produce a square
219 wave pattern centered around the
<tt
>bias
</tt
> value on the output pin
220 of the PID controller. This can be seen using the HAL Scope provided
221 by LinuxCNC. In my case, this is translated into voltage (+-
10V) sent
222 to the motor controller, which in turn is translated into motor speed.
223 So at_pid will ask the motor to move the axis back and forth. The
224 number of cycles in the pattern is controlled by the
225 <tt
>tune-cycles
</tt
> pin, and the extremes of the wave pattern is
226 controlled by the
<tt
>tune-effort
</tt
> pin. Of course, trying to
227 change the direction of a physical object instantly (as in going
228 directly from a positive voltage to the equivalent negative voltage)
229 do not change velocity instantly, and it take some time for the object
230 to slow down and move in the opposite direction. This result in a
231 more smooth movement wave form, as the axis in question were vibrating
232 back and forth. When the axis reached the target speed in the
233 opposing direction, the auto tuner change direction again. After
234 several of these changes, the average time delay between the
'peaks
'
235 and
'valleys
' of this movement graph is then used to calculate
236 proposed values for Pgain, Igain and Dgain, and insert them into the
237 HAL model to use by the pid controller. The auto tuned settings are
238 not great, but htye work a lot better than the values I had been able
239 to cook up on my own, at least for the horizontal X and Y axis. But I
240 had to use very small
<tt
>tune-effort
<tt
> values, as my motor
241 controllers error out if the voltage change too quickly. I
've been
242 less lucky with the Z axis, which is moving a heavy object up and
243 down, and seem to confuse the algorithm. The Z axis movement became a
244 lot better when I introduced a
<tt
>bias
</tt
> value to counter the
245 gravitational drag, but I will have to work a lot more on the Z axis
246 PID values.
</p
>
248 <p
>Armed with this knowledge, it is time to look at how to do the
249 tuning. Lets say the HAL configuration in question load the PID
250 component for X, Y and Z like this:
</p
>
252 <blockquote
><pre
>
253 loadrt pid names=pid.x,pid.y,pid.z
254 </pre
></blockquote
>
256 <p
>Armed with the new and improved at_pid component, the new line will
257 look like this:
</p
>
259 <blockquote
><pre
>
260 loadrt at_pid names=pid.x,pid.y,pid.z
261 </pre
></blockquote
>
263 <p
>The rest of the HAL setup can stay the same. This work because the
264 components are referenced by name. If the component had used count=
3
265 instead, all use of pid.# had to be changed to at_pid.#.
</p
>
267 <p
>To start tuning the X axis, move the axis to the middle of its
268 range, to make sure it do not hit anything when it start moving back
269 and forth. Next, set the
<tt
>tune-effort
</tt
> to a low number in the
270 output range. I used
0.1 as my initial value. Next, assign
1 to the
271 <tt
>tune-mode
</tt
> value. Note, this will disable the pid controlling
272 part and feed
0 to the output pin, which in my case initially caused a
273 lot of drift. In my case it proved to be a good idea with X and Y to
274 tune the motor driver to make sure
0 voltage stopped the motor
275 rotation. On the other hand, for the Z axis this proved to be a bad
276 idea, so it will depend on your setup. It might help to set the
277 <tt
>bias
</tt
> value to a output value that reduce or eliminate the
278 axis drift. Finally, after setting
<tt
>tune-mode
</tt
>, set
279 <tt
>tune-start
</tt
> to
1 to activate the auto tuning. If all go well,
280 your axis will vibrate for a few seconds and when it is done, new
281 values for Pgain, Igain and Dgain will be active. To test them,
282 change
<tt
>tune-mode
</tt
> back to
0. Note that this might cause the
283 machine to suddenly jerk as it bring the axis back to its commanded
284 position, which it might have drifted away from during tuning. To
285 summarize with some halcmd lines:
</p
>
287 <blockquote
><pre
>
288 setp pid.x.tune-effort
0.1
289 setp pid.x.tune-mode
1
290 setp pid.x.tune-start
1
291 # wait for the tuning to complete
292 setp pid.x.tune-mode
0
293 </pre
></blockquote
>
295 <p
>After doing this task quite a few times while trying to figure out
296 how to properly tune the PID controllers on the machine in, I decided
297 to figure out if this process could be automated, and wrote a script
298 to do the entire tuning process from power on. The end result will
299 ensure the machine is powered on and ready to run, home all axis if it
300 is not already done, check that the extra tuning pins are available,
301 move the axis to its mid point, run the auto tuning and re-enable the
302 pid controller when it is done. It can be run several times. Check
304 <a href=
"https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner
">run-auto-pid-tuner
</a
>
305 script on github if you want to learn how it is done.
</p
>
307 <p
>My hope is that this little adventure can inspire someone who know
308 more about motor PID controller tuning can implement even better
309 algorithms for automatic PID tuning in LinuxCNC, making life easier
310 for both me and all the others that want to use LinuxCNC but lack the
311 in depth knowledge needed to tune PID controllers well.
</p
>
313 <p
>As usual, if you use Bitcoin and want to show your support of my
314 activities, please send Bitcoin donations to my address
315 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
320 <title>LinuxCNC translators life just got a bit easier
</title>
321 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</link>
322 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</guid>
323 <pubDate>Fri,
3 Jun
2022 21:
10:
00 +
0200</pubDate>
324 <description><p
>Back in oktober last year, when I started looking at the
325 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
> system, I
326 proposed to change the documentation build system make life easier for
327 translators. The original system consisted of independently written
328 documentation files for each language, with no automated way to track
329 changes done in other translations and no help for the translators to
330 know how much was left to translated. By using
331 <a href=
"https://po4a.org/
">the po4a system
</a
> to generate POT and PO
332 files from the English documentation, this can be improved. A small
333 team of LinuxCNC contributors got together and today our labour
334 finally payed off. Since a few hours ago, it is now possible to
335 translate
<a href=
"https://hosted.weblate.org/projects/linuxcnc/
">the
336 LinuxCNC documentation on Weblate
</a
>, alongside the program itself.
</p
>
338 <p
>The effort to migrate the documentation to use po4a has been both
339 slow and frustrating. I am very happy we finally made it.
</p
>
341 <p
>As usual, if you use Bitcoin and want to show your support of my
342 activities, please send Bitcoin donations to my address
343 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
348 <title>geteltorito make CD firmware upgrades a breeze
</title>
349 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</link>
350 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</guid>
351 <pubDate>Wed,
20 Apr
2022 11:
50:
00 +
0200</pubDate>
352 <description><p
>Recently I wanted to upgrade the firmware of my thinkpad, and
353 located the firmware download page from Lenovo (which annoyingly do
354 not allow access via Tor, forcing me to hand them more personal
355 information that I would like). The
356 <a href=
"https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso
&SearchType=Customer search
&searchLocation=Masthead
">download
357 from Lenovo
</a
> is a bootable ISO image, which is a bit of a problem
358 when all I got available is a USB memory stick. I tried booting the
359 ISO as a USB stick, but this did not work. But genisoimage came to
360 the rescue.
</p
>
362 <P
>The geteltorito program in
363 <a href=
"http://tracker.debian.org/cdrkit
">the genisoimage binary
364 package
</a
> is able to convert the bootable ISO image to a bootable
365 USB stick using a simple command line recipe, which I then can write
366 to the most recently inserted USB stick:
</p
>
368 <blockquote
><pre
>
369 geteltorito -o usbstick.img lenovo-firmware.iso
370 sudo dd bs=
10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -
1)
371 </pre
></blockquote
>
373 <p
>This USB stick booted the firmware upgrader just fine, and in a few
374 minutes my machine had the latest and greatest BIOS firmware in place.
</p
>
379 <title>Run your industrial metal working machine using Debian?
</title>
380 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</link>
381 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</guid>
382 <pubDate>Wed,
2 Mar
2022 18:
40:
00 +
0100</pubDate>
383 <description><p
>After many months of hard work by the good people involved in
384 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>, the
385 system was accepted Sunday
386 <a href=
"https://tracker.debian.org/pkg/linuxcnc
">into Debian
</a
>.
387 Once it was available from Debian, I was surprised to discover from
388 <a href=
"https://qa.debian.org/popcon.php?package=linuxcnc
">its
389 popularity-contest numbers
</a
> that people have been reporting its use
390 since
2012.
<a href=
"http://linuxcnc.org/
">Its project site
</a
> might
391 be a good place to check out, but sadly is not working when visiting
394 <p
>But what is LinuxCNC, you are probably wondering? Perhaps a
395 Wikipedia quote is in place?
</p
>
398 "LinuxCNC is a software system for numerical control of
399 machines such as milling machines, lathes, plasma cutters, routers,
400 cutting machines, robots and hexapods. It can control up to
9 axes or
401 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
402 several GUIs suited to specific kinds of usage (touch screen,
403 interactive development).
"
406 <p
>It can even control
3D printers. And even though the Wikipedia
407 page indicate that it can only work with hard real time kernel
408 features, it can also work with the user space soft real time features
409 provided by the Debian kernel.
410 <a href=
"https://github.com/linuxcnc/linuxcnc
">The source code
</a
> is
411 available from Github. The last few months I
've been involved in the
412 translation setup for the program and documentation. Translators are
414 <a href=
"https://hosted.weblate.org/engage/linuxcnc/
">join the
415 effort
</a
> using Weblate.
</p
>
417 <p
>As usual, if you use Bitcoin and want to show your support of my
418 activities, please send Bitcoin donations to my address
419 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
424 <title>Debian still an excellent choice for Lego builders
</title>
425 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</link>
426 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</guid>
427 <pubDate>Sun,
24 Oct
2021 07:
10:
00 +
0200</pubDate>
428 <description><p
>The Debian Lego team saw a lot of activity the last few weeks. All
429 the packages under the team umbrella has been updated to fix
430 packaging, lintian issues and BTS reports. In addition, a new and
431 inspiring team member appeared on both the
432 <a href=
"https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team
">debian-lego-team
433 Team mailing list
</a
> and
434 <a href=
"irc://irc.debian.org/%
23debian-lego
">IRC channel
435 #debian-lego
</a
>. If you are interested in Lego CAD design and LEGO
436 Mindstorms programming, check out the
437 <a href=
"http://wiki.debian.org/LegoDesigners
">team wiki page
</a
> to
438 see what Debian can offer the Lego enthusiast.
</p
>
440 <p
>Patches has been sent upstream, causing new upstream releases, one
441 even the first one in more than ten years, and old upstreams was
442 released with new ones. There are still a lot of work left, and the
443 team welcome more members to help us make sure Debian is the Linux
444 distribution of choice for Lego builders. If you want to contribute,
445 join us in the IRC channel and become part of
446 <a href=
"https://salsa.debian.org/debian-lego-team/
">the team on
447 Salsa
</a
>.
</p
>
449 <p
>As usual, if you use Bitcoin and want to show your support of my
450 activities, please send Bitcoin donations to my address
451 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
456 <title>Six complete translations of The Debian Administrator
's Handbook for Buster
</title>
457 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</link>
458 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</guid>
459 <pubDate>Mon,
5 Jul
2021 19:
20:
00 +
0200</pubDate>
460 <description><p
>I am happy observe that the
<a href=
"https://debian-handbook.info/
">The
461 Debian Administrator
's Handbook
</a
> is available in six languages now.
462 I am not sure which one of these are completely proof read, but the
463 complete book is available in these languages:
467 <li
>English
</li
>
468 <li
>Norwegian Bokmål
</li
>
469 <li
>German
</li
>
470 <li
>Indonesian
</li
>
471 <li
>Brazil Portuguese
</li
>
472 <li
>Spanish
</li
>
476 <p
>This is the list of languages more than
70% complete, in other
477 words with not too much left to do:
</p
>
481 <li
>Chinese (Simplified) -
90%
</li
>
482 <li
>French -
79%
</li
>
483 <li
>Italian -
79%
</li
>
484 <li
>Japanese -
77%
</li
>
485 <li
>Arabic (Morocco) -
75%
</li
>
486 <li
>Persian -
71%
</li
>
490 <p
>I wonder how long it will take to bring these to
100%.
</p
>
492 <p
>Then there is the list of languages about halfway done:
</p
>
496 <li
>Russian -
63%
</li
>
497 <li
>Swedish -
53%
</li
>
498 <li
>Chinese (Traditional) -
46%
</li
>
499 <li
>Catalan -
45%
</li
>
503 <p
>Several are on to a good start:
</p
>
507 <li
>Dutch -
26%
</li
>
508 <li
>Vietnamese -
25%
</li
>
509 <li
>Polish -
23%
</li
>
510 <li
>Czech -
22%
</li
>
511 <li
>Turkish -
18%
</li
>
515 <p
>Finally, there are the ones just getting started:
</p
>
519 <li
>Korean -
4%
</li
>
520 <li
>Croatian -
2%
</li
>
521 <li
>Greek -
2%
</li
>
522 <li
>Danish -
1%
</li
>
523 <li
>Romanian -
1%
</li
>
527 <p
>If you want to help provide a Debian instruction book in your own
529 <a href=
"https://hosted.weblate.org/projects/debian-handbook/#languages
">Weblate
</a
>
530 to contribute to the translations.
</p
>
532 <p
>As usual, if you use Bitcoin and want to show your support of my
533 activities, please send Bitcoin donations to my address
534 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
539 <title>Latest Jami back in Debian Testing, and scriptable using dbus
</title>
540 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</link>
541 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</guid>
542 <pubDate>Tue,
12 Jan
2021 17:
00:
00 +
0100</pubDate>
543 <description><p
>After a lot of hard work by its maintainer Alexandre Viau and
544 others, the decentralized communication platform
545 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>
546 (earlier known as Ring), managed to get
547 <a href=
"https://tracker.debian.org/pkg/ring
">its latest version
</a
>
548 into Debian Testing. Several of its dependencies has caused build and
549 propagation problems, which all seem to be solved now.
</p
>
551 <p
>In addition to the fact that Jami is decentralized, similar to how
552 bittorrent is decentralized, I first of all like how it is not
553 connected to external IDs like phone numbers. This allow me to set up
554 computers to send me notifications using Jami without having to find
555 get a phone number for each computer. Automatic notification via Jami
556 is also made trivial thanks to the provided client side API (as a DBus
557 service). Here is my bourne shell script demonstrating how to let any
558 system send a message to any Jami address. It will create a new
559 identity before sending the message, if no Jami identity exist
565 # Usage: $
0 <jami-address
> <message
>
567 # Send
<message
> to
<jami-address
>, create local jami account if
570 # License: GPL v2 or later at your choice
571 # Author: Petter Reinholdtsen
574 if [ -z
"$HOME
" ] ; then
575 echo
"error: missing \$HOME, required for dbus to work
"
579 # First, get dbus running if not already running
580 DBUSLAUNCH=/usr/bin/dbus-launch
581 PIDFILE=/run/asterisk/dbus-session.pid
582 if [ -e $PIDFILE ] ; then
584 if ! kill -
0 $DBUS_SESSION_BUS_PID
2>/dev/null ; then
585 unset DBUS_SESSION_BUS_ADDRESS
588 if [ -z
"$DBUS_SESSION_BUS_ADDRESS
" ]
&& [ -x
"$DBUSLAUNCH
" ]; then
589 DBUS_SESSION_BUS_ADDRESS=
"unix:path=$HOME/.dbus
"
590 dbus-daemon --session --address=
"$DBUS_SESSION_BUS_ADDRESS
" --nofork --nopidfile --syslog-only
< /dev/null
> /dev/null
2>&1 3>&1 &
591 DBUS_SESSION_BUS_PID=$!
593 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
594 echo DBUS_SESSION_BUS_ADDRESS=\
""$DBUS_SESSION_BUS_ADDRESS
"\
"
595 echo export DBUS_SESSION_BUS_ADDRESS
601 part=
"$
1"; shift
602 op=
"$
1"; shift
603 dbus-send --session \
604 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
608 part=
"$
1"; shift
609 op=
"$
1"; shift
610 dbus-send --session --print-reply \
611 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
615 dringopreply ConfigurationManager getAccountList | \
616 grep string | awk -F
'"' '{print $
2}
' | head -n
1
619 account=$(firstaccount)
621 if [ -z
"$account
" ] ; then
622 echo
"Missing local account, trying to create it
"
623 dringop ConfigurationManager addAccount \
624 dict:string:string:
"Account.type
",
"RING
",
"Account.videoEnabled
",
"false
"
625 account=$(firstaccount)
626 if [ -z
"$account
" ] ; then
627 echo
"unable to create local account
"
632 # Not using dringopreply to ensure $
2 can contain spaces
633 dbus-send --print-reply --session \
634 --dest=cx.ring.Ring \
635 /cx/ring/Ring/ConfigurationManager \
636 cx.ring.Ring.ConfigurationManager.sendTextMessage \
637 string:
"$account
" string:
"$
1" \
638 dict:string:string:
"text/plain
",
"$
2"
639 </pre
></p
>
641 <p
>If you want to check it out yourself, visit the
642 <a href=
"https://jami.net/
">the Jami system project page
</a
> to learn
643 more, and install the latest Jami client from Debian Unstable or
646 <p
>As usual, if you use Bitcoin and want to show your support of my
647 activities, please send Bitcoin donations to my address
648 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
653 <title>Buster based Bokmål edition of Debian Administrator
's Handbook
</title>
654 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
655 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
656 <pubDate>Tue,
20 Oct
2020 18:
35:
00 +
0200</pubDate>
657 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2020-
10-
20-debian-handbook-nb-testprint.jpeg
" width=
"60%
"/
></p
>
659 <p
>I am happy to report that we finally made it! Norwegian Bokmål
660 became the first translation published on paper of the new Buster
661 based edition of
"<a href=
"https://debian-handbook.info/
">The Debian
662 Administrator
's Handbook
</a
>". The print proof reading copy arrived
663 some days ago, and it looked good, so now the book is approved for
664 general distribution. This updated paperback edition
<a
665 href=
"https://debian-handbook.info/get/#norwegian
">is available from
666 lulu.com
</a
>. The book is also available for download in electronic
667 form as PDF, EPUB and Mobipocket, and can also be
668 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
</a
>.
</p
>
670 <p
>I am very happy to wrap up this Creative Common licensed project,
671 which concludes several months of work by several volunteers. The
672 number of Linux related books published in Norwegian are few, and I
673 really hope this one will gain many readers, as it is packed with deep
674 knowledge on Linux and the Debian ecosystem. The book will be
675 available for various Internet book stores like Amazon and Barnes
&
676 Noble soon, but I recommend buying
677 "<a href=
"https://www.lulu.com/en/us/shop/roland-mas-and-rapha%C3%ABl-hertzog/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
9j7qwq.html
">Håndbok
678 for Debian-administratoren
</a
>" directly from the source at Lulu.
680 <p
>As usual, if you use Bitcoin and want to show your support of my
681 activities, please send Bitcoin donations to my address
682 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
687 <title>Buster update of Norwegian Bokmål edition of Debian Administrator
's Handbook almost done
</title>
688 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html
</link>
689 <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>
690 <pubDate>Fri,
11 Sep
2020 09:
45:
00 +
0200</pubDate>
691 <description><p
>Thanks to the good work of several volunteers, the updated edition
692 of the Norwegian translation for
693 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
694 Handbook
</a
>" is now almost completed. After many months of proof
695 reading, I consider the proof reading complete enough for us to move
696 to the next step, and have asked for the print version to be prepared
697 and sent of to the print on demand service lulu.com. While it is
698 still not to late if you find any incorrect translations on
699 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
700 hosted Weblate service
</a
>, but it will be soon. :) You can check out
701 <a href=
" https://debian-handbook.info/browse/nb-NO/stable/
">the Buster
702 edition on the web
</a
> until the print edition is ready.
</p
>
704 <p
>The book will be for sale on lulu.com and various web book stores,
705 with links available from the web site for the book linked to above.
706 I hope a lot of readers find it useful.
</p
>
708 <p
>As usual, if you use Bitcoin and want to show your support of my
709 activities, please send Bitcoin donations to my address
710 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
715 <title>Working on updated Norwegian Bokmål edition of Debian Administrator
's Handbook
</title>
716 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
717 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
718 <pubDate>Sat,
4 Jul
2020 23:
55:
00 +
0200</pubDate>
719 <description><p
>Three years ago, the first Norwegian Bokmål edition of
720 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
721 Handbook
</a
>" was published. This was based on Debian Jessie. Now a
722 new and updated version based on Buster is getting ready. Work on the
723 updated Norwegian Bokmål edition has been going on for a few months
724 now, and yesterday, we reached the first mile stone, with
100% of the
725 texts being translated. A lot of proof reading remains, of course,
726 but a major step towards a new edition has been taken.
</p
>
728 <p
>The book is translated by volunteers, and we would love to get some
729 help with the proof reading. The translation uses
730 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
731 hosted Weblate service
</a
>, and we welcome everyone to have a look and
732 submit improvements and suggestions. There is also a proof readers
733 PDF available on request, get in touch if you want to help out that
736 <p
>As usual, if you use Bitcoin and want to show your support of my
737 activities, please send Bitcoin donations to my address
738 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
743 <title>Secure Socket API - a simple and powerful approach for TLS support in software
</title>
744 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</link>
745 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</guid>
746 <pubDate>Sat,
6 Jun
2020 12:
40:
00 +
0200</pubDate>
747 <description><p
>As a member of the
<a href=
"https://www.nuug.no/
">Norwegian Unix
748 User Group
</a
>, I have the pleasure of receiving the
749 <a href=
"https://www.usenix.org/
">USENIX
</a
> magazine
750 <a href=
"https://www.usenix.org/publications/login/
">;login:
</a
>
751 several times a year. I rarely have time to read all the articles,
752 but try to at least skim through them all as there is a lot of nice
753 knowledge passed on there. I even carry the latest issue with me most
754 of the time to try to get through all the articles when I have a few
755 spare minutes.
</p
>
757 <p
>The other day I came across a nice article titled
758 "<a href=
"https://www.usenix.org/publications/login/winter2018/oneill
">The
759 Secure Socket API: TLS as an Operating System Service
</a
>" with a
760 marvellous idea I hope can make it all the way into the POSIX standard.
761 The idea is as simple as it is powerful. By introducing a new
762 socket() option IPPROTO_TLS to use TLS, and a system wide service to
763 handle setting up TLS connections, one both make it trivial to add TLS
764 support to any program currently using the POSIX socket API, and gain
765 system wide control over certificates, TLS versions and encryption
766 systems used. Instead of doing this:
</p
>
768 <p
><blockquote
><pre
>
769 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
770 </pre
></blockquote
></p
>
772 <p
>the program code would be doing this:
<p
>
774 <p
><blockquote
><pre
>
775 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
776 </pre
></blockquote
></p
>
778 <p
>According to the ;login: article, converting a C program to use TLS
779 would normally modify only
5-
10 lines in the code, which is amazing
780 when compared to using for example the OpenSSL API.
</p
>
782 <p
>The project has set up the
783 <a href=
"https://securesocketapi.org/
">https://securesocketapi.org/
</a
>
784 web site to spread the idea, and the code for a kernel module and the
785 associated system daemon is available from two github repositories:
786 <a href=
"https://github.com/markoneill/ssa
">ssa
</a
> and
787 <a href=
"https://github.com/markoneill/ssa-daemon
">ssa-daemon
</a
>.
788 Unfortunately there is no explicit license information with the code,
789 so its copyright status is unclear. A
790 <a href=
"https://github.com/markoneill/ssa/issues/
2">request to solve
791 this
</a
> about it has been unsolved since
2018-
08-
17.
</p
>
793 <p
>I love the idea of extending socket() to gain TLS support, and
794 understand why it is an advantage to implement this as a kernel module
795 and system wide service daemon, but can not help to think that it
796 would be a lot easier to get projects to move to this way of setting
797 up TLS if it was done with a user space approach where programs
798 wanting to use this API approach could just link with a wrapper
801 <p
>I recommend you check out this simple and powerful approach to more
802 secure network connections. :)
</p
>
804 <p
>As usual, if you use Bitcoin and want to show your support of my
805 activities, please send Bitcoin donations to my address
806 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
811 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
812 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
813 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
814 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
815 <description><p
>Half a year ago,
816 <a href=
"http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
817 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
818 client
</a
>, capable of peer-to-peer encrypted communication. It
819 handle both messages, audio and video. It uses distributed hash
820 tables instead of central infrastructure to connect its users to each
821 other, which in my book is a plus. I mentioned briefly that it could
822 also work as a SIP client, which came in handy when the higher
823 educational sector in Norway started to promote Zoom as its video
824 conferencing solution. I am reluctant to use the official Zoom client
825 software, due to their
<a href=
"https://zoom.us/terms
">copyright
826 license clauses
</a
> prohibiting users to reverse engineer (for example
827 to check the security) and benchmark it, and thus prefer to connect to
828 Zoom meetings with free software clients.
</p
>
830 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
831 password set on the room. The Jami daemon leak memory like crazy
832 (approximately
1 GiB a minute) when I am connected to the video
833 conference, so I had to restart the client every
7-
10 minutes, which
834 is not great. I tried to get other SIP Linux clients to work
835 without success, so I decided I would have to live with this wart
836 until someone managed to fix the leak in the dring code base. But
837 another problem showed up once the rooms were password protected. I
838 could not get my dial tone signaling through from Jami to Zoom, and
839 dial tone signaling is used to enter the password when connecting to
840 Zoom. I tried a lot of different permutations with my Jami and
841 Asterisk setup to try to figure out why the signaling did not get
842 through, only to finally discover that the fundamental problem seem to
843 be that Zoom is simply not able to receive dial tone signaling when
844 connecting via SIP. There seem to be nothing wrong with the Jami and
845 Asterisk end, it is simply broken in the Zoom end. I got help from a
846 very skilled VoIP engineer figuring out this last part. And being a
847 very skilled engineer, he was also able to locate a solution for me.
848 Or to be exact, a workaround that solve my initial problem of
849 connecting to password protected Zoom rooms using Jami.
</p
>
851 <p
>So, how do you do this, I am sure you are wondering by now. The
853 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
854 from Zoom
</a
>, and it is to modify the SIP address to include the room
855 password. What is most surprising about this is that the
856 automatically generated email from Zoom with instructions on how to
857 connect via SIP do not mention this. The SIP address to use normally
858 consist of the room ID (a number), an @ character and the IP address
859 of the Zoom SIP gateway. But Zoom understand a lot more than just the
860 room ID in front of the at sign. The format is
"<tt
>[Meeting
861 ID].[Password].[Layout].[Host Key]
</tt
>", and you can here see how you
862 can both enter password, control the layout (full screen, active
863 presence and gallery) and specify the host key to start the meeting.
864 The full SIP address entered into Jami to provide the password will
865 then look like this (all using made up numbers):
</p
>
867 <p
><blockquote
>
868 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
869 </blockquote
></p
>
871 <p
>Now if only jami would reduce its memory usage, I could even
872 recommend this setup to others. :)
</p
>
874 <p
>As usual, if you use Bitcoin and want to show your support of my
875 activities, please send Bitcoin donations to my address
876 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
881 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software
</title>
882 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</link>
883 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</guid>
884 <pubDate>Wed,
29 Apr
2020 13:
10:
00 +
0200</pubDate>
885 <description><p
>The curiosity got the better of me when
886 <a href=
"https://developers.slashdot.org/story/
20/
04/
06/
1424246/new-jersey-desperately-needs-cobol-programmers
">Slashdot
887 reported
</a
> that New Jersey was desperately looking for
888 <a href=
"https://en.wikipedia.org/wiki/COBOL
">COBOL
</a
> programmers,
889 and a few days later it was reported that
890 <a href=
"https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce
">IBM
891 tried to locate COBOL programmers
</a
>.
</p
>
893 <p
>I thus decided to have a look at free software alternatives to
894 learn COBOL, and had the pleasure to find
895 <a href=
"https://sourceforge.net/projects/open-cobol/
">GnuCOBOL
</a
> was
896 already
<a href=
"https://tracker.debian.org/pkg/gnucobol
">in
897 Debian
</a
>. It used to be called Open Cobol, and is a
"compiler
"
898 transforming COBOL code to C or C++ before giving it to GCC or Visual
899 Studio to build binaries.
</p
>
901 <p
>I managed to get in touch with upstream, and was impressed with the
902 quick response, and also was happy to see a new Debian maintainer
903 taking over when the original one recently asked to be replaced. A
904 new Debian upload was done as recently as yesterday.
</p
>
906 <p
>Using the Debian package, I was able to follow a simple COBOL
907 introduction and make and run simple COBOL programs. It was fun to
908 learn a new programming language. If you want to test for yourself,
909 <a href=
"https://en.wikipedia.org/wiki/GnuCOBOL
">the GnuCOBOL Wikipedia
910 page
</a
> have a few simple examples to get you startet.
</p
>
912 <p
>As I do not have much experience with COBOL, I do not know how
913 standard compliant it is, but it claim to pass most tests from COBOL
914 test suite, which sound good to me. It is nice to know it is possible
915 to learn COBOL using software without any usage restrictions, and I am
916 very happy such nice free software project as this is available. If
917 you as me is curious about COBOL, check it out.
</p
>
919 <p
>As usual, if you use Bitcoin and want to show your support of my
920 activities, please send Bitcoin donations to my address
921 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
926 <title>Jami/Ring, finally functioning peer to peer communication client
</title>
927 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</link>
928 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</guid>
929 <pubDate>Wed,
19 Jun
2019 08:
50:
00 +
0200</pubDate>
930 <description><p
>Some years ago, in
2016, I
931 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">wrote
932 for the first time about
</a
> the Ring peer to peer messaging system.
933 It would provide messaging without any central server coordinating the
934 system and without requiring all users to register a phone number or
935 own a mobile phone. Back then, I could not get it to work, and put it
936 aside until it had seen more development. A few days ago I decided to
937 give it another try, and am happy to report that this time I am able
938 to not only send and receive messages, but also place audio and video
939 calls. But only if UDP is not blocked into your network.
</p
>
941 <p
>The Ring system changed name earlier this year to
942 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>. I
943 tried doing web search for
'ring
' when I discovered it for the first
944 time, and can only applaud this change as it is impossible to find
945 something called Ring among the noise of other uses of that word. Now
946 you can search for
'jami
' and this client and
947 <a href=
"https://jami.net/
">the Jami system
</a
> is the first hit at
948 least on duckduckgo.
</p
>
950 <p
>Jami will by default encrypt messages as well as audio and video
951 calls, and try to send them directly between the communicating parties
952 if possible. If this proves impossible (for example if both ends are
953 behind NAT), it will use a central SIP TURN server maintained by the
954 Jami project. Jami can also be a normal SIP client. If the SIP
955 server is unencrypted, the audio and video calls will also be
956 unencrypted. This is as far as I know the only case where Jami will
957 do anything without encryption.
</p
>
959 <p
>Jami is available for several platforms: Linux, Windows, MacOSX,
960 Android, iOS, and Android TV. It is included in Debian already. Jami
961 also work for those using F-Droid without any Google connections,
963 <a href=
"https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol
">The
964 protocol
</a
> is described in the Ring project wiki. The system uses a
965 distributed hash table (DHT) system (similar to BitTorrent) running
966 over UDP. On one of the networks I use, I discovered Jami failed to
967 work. I tracked this down to the fact that incoming UDP packages
968 going to ports
1-
49999 were blocked, and the DHT would pick a random
969 port and end up in the low range most of the time. After talking to
970 the developers, I solved this by enabling the dhtproxy in the
971 settings, thus using TCP to talk to a central DHT proxy instead of
973 peering directly with others. I
've been told the developers are
974 working on allowing DHT to use TCP to avoid this problem. I also ran
975 into a problem when trying to talk to the version of Ring included in
976 Debian Stable (Stretch). Apparently the protocol changed between
977 beta2 and the current version, making these clients incompatible.
978 Hopefully the protocol will not be made incompatible in the
981 <p
>It is worth noting that while looking at Jami and its features, I
982 came across another communication platform I have not tested yet. The
983 <a href=
"https://en.wikipedia.org/wiki/Tox_(protocol)
">Tox protocol
</a
>
984 and
<a href=
"https://tox.chat/
">family of Tox clients
</a
>. It might
985 become the topic of a future blog post.
</p
>
987 <p
>As usual, if you use Bitcoin and want to show your support of my
988 activities, please send Bitcoin donations to my address
989 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
994 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål
</title>
995 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</link>
996 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</guid>
997 <pubDate>Wed,
23 Jan
2019 07:
50:
00 +
0100</pubDate>
998 <description><p
>I høst ble jeg inspirert til å bidra til oversettelsen av
999 <a href=
"http://unknown-horizons.org/
">strategispillet Unknown
1000 Horizons
</a
>, og oversatte de nesten
200 strengene i prosjektet til
1001 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
1002 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
1003 nye versjonen kom på nyåret, og ble
1004 <a href=
"https://tracker.debian.org/pkg/unknown-horizons
">lastet opp i
1005 Debian
</a
> for noen få dager siden. I går kveld fikk jeg testet det ut, og
1006 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
1007 måtte justeres, men ikke noe alvorlig. Har oppdatert
1008 <a href=
"https://hosted.weblate.org/projects/uh/
">oversettelsen på
1009 Weblate
</a
>, slik at neste utgave vil være enda bedre. :)
</p
>
1011 <p
>Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1012 å spille for oss som liker slikt. :)
</p
>
1014 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1015 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1017 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
1018 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
1023 <title>Debian now got everything you need to program Micro:bit
</title>
1024 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</link>
1025 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</guid>
1026 <pubDate>Tue,
22 Jan
2019 17:
20:
00 +
0100</pubDate>
1027 <description><p
>I am amazed and very pleased to discover that since a few days ago,
1028 everything you need to program the
<a href=
"https://microbit.org/
">BBC
1029 micro:bit
</a
> is available from the Debian archive. All this is
1030 thanks to the hard work of Nick Morrott and the Debian python
1031 packaging team. The micro:bit project recommend the mu-editor to
1032 program the microcomputer, as this editor will take care of all the
1033 machinery required to injekt/flash micropython alongside the program
1034 into the micro:bit, as long as the pieces are available.
</p
>
1036 <p
>There are three main pieces involved. The first to enter Debian
1038 <a href=
"https://tracker.debian.org/pkg/python-uflash
">python-uflash
</a
>,
1039 which was accepted into the archive
2019-
01-
12. The next one was
1040 <a href=
"https://tracker.debian.org/pkg/mu-editor
">mu-editor
</a
>, which
1041 showed up
2019-
01-
13. The final and hardest part to to into the
1043 <a href=
"https://tracker.debian.org/pkg/firmware-microbit-micropython
">firmware-microbit-micropython
</a
>,
1044 which needed to get its build system and dependencies into Debian
1045 before it was accepted
2019-
01-
20. The last one is already in Debian
1046 Unstable and should enter Debian Testing / Buster in three days. This
1047 all allow any user of the micro:bit to get going by simply running
1048 'apt install mu-editor
' when using Testing or Unstable, and once
1049 Buster is released as stable, all the users of Debian stable will be
1050 catered for.
</p
>
1052 <p
>As a minor final touch, I added rules to
1053 <a href=
"https://tracker.debian.org/pkg/isenkram
">the isenkram
1054 package
</a
> for recognizing micro:bit and recommend the mu-editor
1055 package. This make sure any user of the isenkram desktop daemon will
1056 get a popup suggesting to install mu-editor then the USB cable from
1057 the micro:bit is inserted for the first time.
</p
>
1059 <p
>This should make it easier to have fun.
</p
>
1061 <p
>As usual, if you use Bitcoin and want to show your support of my
1062 activities, please send Bitcoin donations to my address
1063 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1068 <title>Learn to program with Minetest on Debian
</title>
1069 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</link>
1070 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</guid>
1071 <pubDate>Sat,
15 Dec
2018 15:
30:
00 +
0100</pubDate>
1072 <description><p
>A fun way to learn how to program
1073 <a href=
"https://www.python.org/
">Python
</a
> is to follow the
1074 instructions in the book
1075 "<a href=
"https://nostarch.com/programwithminecraft
">Learn to program
1076 with Minecraft
</a
>", which introduces programming in Python to people
1077 who like to play with Minecraft. The book uses a Python library to
1078 talk to a TCP/IP socket with an API accepting build instructions and
1079 providing information about the current players in a Minecraft world.
1080 The TCP/IP API was first created for the Minecraft implementation for
1081 Raspberry Pi, and has since been ported to some server versions of
1082 Minecraft. The book contain recipes for those using Windows, MacOSX
1083 and Raspian. But a little known fact is that you can follow the same
1084 recipes using the free software construction game
1085 <a href=
"https://minetest.net/
">Minetest
</a
>.
</p
>
1087 <p
>There is
<a href=
"https://github.com/sprintingkiwi/pycraft_mod
">a
1088 Minetest module implementing the same API
</a
>, making it possible to
1089 use the Python programs coded to talk to Minecraft with Minetest too.
1091 <a href=
"https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%
2Bgit20180331.0376a0a%
2Bdfsg-
1.html
">uploaded
1092 this module
</a
> to Debian two weeks ago, and as soon as it clears the
1093 FTP masters NEW queue, learning to program Python with Minetest on
1094 Debian will be a simple
'apt install
' away. The Debian package is
1095 maintained as part of the Debian Games team, and
1096 <a href=
"https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft
">the
1097 packaging rules
</a
> are currently located under
'unfinished
' on
1100 <p
>You will most likely need to install several of the Minetest
1101 modules in Debian for the examples included with the library to work
1102 well, as there are several blocks used by the example scripts that are
1103 provided via modules in Minetest. Without the required blocks, a
1104 simple stone block is used instead. My initial testing with a analog
1105 clock did not get gold arms as instructed in the python library, but
1106 instead used stone arms.
</p
>
1108 <p
>I tried to find a way to add the API to the desktop version of
1109 Minecraft, but were unable to find any working recipes. The
1110 <a href=
"https://www.epiphanydigest.com/tag/minecraft-python-api/
">recipes
</a
>
1111 I
<a href=
"https://github.com/kbsriram/mcpiapi
">found
</a
> are only
1112 working with a standalone Minecraft server setup. Are there any
1113 options to use with the normal desktop version?
</p
>
1115 <p
>As usual, if you use Bitcoin and want to show your support of my
1116 activities, please send Bitcoin donations to my address
1117 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1122 <title>Time for an official MIME type for patches?
</title>
1123 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</link>
1124 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</guid>
1125 <pubDate>Thu,
1 Nov
2018 08:
15:
00 +
0100</pubDate>
1126 <description><p
>As part of my involvement in
1127 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core
">the Nikita
1128 archive API project
</a
>, I
've been importing a fairly large lump of
1129 emails into a test instance of the archive to see how well this would
1130 go. I picked a subset of
<a href=
"https://notmuchmail.org/
">my
1131 notmuch email database
</a
>, all public emails sent to me via
1132 @lists.debian.org, giving me a set of around
216 000 emails to import.
1133 In the process, I had a look at the various attachments included in
1134 these emails, to figure out what to do with attachments, and noticed
1135 that one of the most common attachment formats do not have
1136 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">an
1137 official MIME type
</a
> registered with IANA/IETF. The output from
1138 diff, ie the input for patch, is on the top
10 list of formats
1139 included in these emails. At the moment people seem to use either
1140 text/x-patch or text/x-diff, but neither is officially registered. It
1141 would be better if one official MIME type were registered and used
1142 everywhere.
</p
>
1144 <p
>To try to get one official MIME type for these files, I
've brought
1146 <a href=
"https://www.ietf.org/mailman/listinfo/media-types
">the
1147 media-types mailing list
</a
>. If you are interested in discussion
1148 which MIME type to use as the official for patch files, or involved in
1149 making software using a MIME type for patches, perhaps you would like
1150 to join the discussion?
</p
>
1152 <p
>As usual, if you use Bitcoin and want to show your support of my
1153 activities, please send Bitcoin donations to my address
1154 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1159 <title>Automatic Google Drive sync using grive in Debian
</title>
1160 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</link>
1161 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</guid>
1162 <pubDate>Thu,
4 Oct
2018 15:
20:
00 +
0200</pubDate>
1163 <description><p
>A few days, I rescued a Windows victim over to Debian. To try to
1164 rescue the remains, I helped set up automatic sync with Google Drive.
1165 I did not find any sensible Debian package handling this
1166 automatically, so I rebuild the grive2 source from
1167 <a href=
"http://www.webupd8.org/
">the Ubuntu UPD8 PPA
</a
> to do the
1168 task and added a autostart desktop entry and a small shell script to
1169 run in the background while the user is logged in to do the sync.
1170 Here is a sketch of the setup for future reference.
</p
>
1172 <p
>I first created
<tt
>~/googledrive
</tt
>, entered the directory and
1173 ran
'<tt
>grive -a
</tt
>' to authenticate the machine/user. Next, I
1174 created a autostart hook in
<tt
>~/.config/autostart/grive.desktop
</tt
>
1175 to start the sync when the user log in:
</p
>
1177 <p
><blockquote
><pre
>
1179 Name=Google drive autosync
1181 Exec=/home/user/bin/grive-sync
1182 </pre
></blockquote
></p
>
1184 <p
>Finally, I wrote the
<tt
>~/bin/grive-sync
</tt
> script to sync
1185 ~/googledrive/ with the files in Google Drive.
</p
>
1187 <p
><blockquote
><pre
>
1192 if [
"$syncpid
" ] ; then
1196 trap cleanup EXIT INT QUIT
1197 /usr/lib/grive/grive-sync.sh listen googledrive
2>&1 | sed
"s%^%$
0:%
" &
1200 if ! xhost
>/dev/null
2>&1 ; then
1201 echo
"no DISPLAY, exiting as the user probably logged out
"
1204 if [ ! -e /run/user/
1000/grive-sync.sh_googledrive ] ; then
1205 /usr/lib/grive/grive-sync.sh sync googledrive
1208 done
2>&1 | sed
"s%^%$
0:%
"
1209 </pre
></blockquote
></p
>
1211 <p
>Feel free to use the setup if you want. It can be assumed to be
1212 GNU GPL v2 licensed (or any later version, at your leisure), but I
1213 doubt this code is possible to claim copyright on.
</p
>
1215 <p
>As usual, if you use Bitcoin and want to show your support of my
1216 activities, please send Bitcoin donations to my address
1217 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1222 <title>Using the Kodi API to play Youtube videos
</title>
1223 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</link>
1224 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</guid>
1225 <pubDate>Sun,
2 Sep
2018 23:
40:
00 +
0200</pubDate>
1226 <description><p
>I continue to explore my Kodi installation, and today I wanted to
1227 tell it to play a youtube URL I received in a chat, without having to
1228 insert search terms using the on-screen keyboard. After searching the
1229 web for API access to the Youtube plugin and testing a bit, I managed
1230 to find a recipe that worked. If you got a kodi instance with its API
1231 available from http://kodihost/jsonrpc, you can try the following to
1232 have check out a nice cover band.
</p
>
1234 <p
><blockquote
><pre
>curl --silent --header
'Content-Type: application/json
' \
1235 --data-binary
'{
"id
":
1,
"jsonrpc
":
"2.0",
"method
":
"Player.Open
",
1236 "params
": {
"item
": {
"file
":
1237 "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg
" } } }
' \
1238 http://projector.local/jsonrpc
</pre
></blockquote
></p
>
1240 <p
>I
've extended kodi-stream program to take a video source as its
1241 first argument. It can now handle direct video links, youtube links
1242 and
'desktop
' to stream my desktop to Kodi. It is almost like a
1243 Chromecast. :)
</p
>
1245 <p
>As usual, if you use Bitcoin and want to show your support of my
1246 activities, please send Bitcoin donations to my address
1247 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1252 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
1253 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
1254 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
1255 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
1256 <description><p
>For a while now, I have looked for a sensible way to share images
1257 with my family using a self hosted solution, as it is unacceptable to
1258 place images from my personal life under the control of strangers
1259 working for data hoarders like Google or Dropbox. The last few days I
1260 have drafted an approach that might work out, and I would like to
1261 share it with you. I would like to publish images on a server under
1262 my control, and point some Internet connected display units using some
1263 free and open standard to the images I published. As my primary
1264 language is not limited to ASCII, I need to store metadata using
1265 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
1266 of reading a RSS feed with image references (aka using the
1267 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
1268 of such frames. In the end I gave up that approach.
</p
>
1270 <p
>Some months ago, I discovered that
1271 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
1272 read images from a RSS feed, and used it to set up a screen saver on
1273 my home info screen, showing images from the Daily images feed from
1274 NASA. This proved to work well. More recently I discovered that
1275 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
1276 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
1277 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
1278 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
1279 screen saver capable of reading a RSS feed with images and news. For
1280 fun, I used it this summer to test Kodi on my parents TV by hooking up
1281 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
1282 screen saver showing selected pictures from my selection.
</p
>
1284 <p
>Armed with motivation and a test photo frame, I set out to generate
1285 a RSS feed for the Kodi instance. I adjusted my
<a
1286 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
1287 /var/www/html/privatepictures/, wrote a small Perl script to extract
1288 title and description metadata from the photo files and generate the
1289 RSS file. I ended up using Perl instead of python, as the
1290 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
1291 tags I ended up using, while python3-exif did not. The relevant EXIF
1292 tags only support ASCII, so I had to find better alternatives. XMP
1293 seem to have the support I need.
</p
>
1295 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
1296 use tags that can be easily added/updated using normal free software
1297 photo managing software. I ended up using the tags set using this
1298 exiftool command, as these tags can also be set using digiKam:
</p
>
1300 <blockquote
><pre
>
1301 exiftool -headline=
'The RSS image title
' \
1302 -description=
'The RSS image description.
' \
1303 -subject+=for-family photo.jpeg
1304 </pre
></blockquote
>
1306 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
1307 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
1308 use the keyword/subject
'for-family
' to flag that the photo should be
1309 shared with my family. Images with this keyword set are located and
1310 copied into my Freedombox for the RSS generating script to find.
</p
>
1312 <p
>Are there better ways to do this? Get in touch if you have better
1313 suggestions.
</p
>
1315 <p
>As usual, if you use Bitcoin and want to show your support of my
1316 activities, please send Bitcoin donations to my address
1317 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1322 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
1323 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
1324 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
1325 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
1326 <description><p
>Last night, I wrote
1327 <a href=
"http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
1328 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
1329 During the day I received valuable feedback, and thanks to the
1330 suggestions I have been able to rewrite the recipe into a much simpler
1331 approach requiring no setup at all. It is a single script that take
1332 care of it all.
</p
>
1334 <p
>This new script uses GStreamer instead of VLC to capture the
1335 desktop and stream it to Kodi. This fixed the video quality issue I
1336 saw initially. It further removes the need to add a m3u file on the
1337 Kodi machine, as it instead connects to
1338 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
1339 Kodi
</a
> and simply ask Kodi to play from the stream created using
1340 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
1341 the script below, run it with the DNS name or IP address of the kodi
1342 server to stream to as the only argument, and watch your screen show
1343 up on the Kodi screen. Note, it depend on multicast on the local
1344 network, so if you need to stream outside the local network, the
1345 script must be modified. Also note, I have no idea if audio work, as
1346 I only care about the picture part.
</p
>
1348 <blockquote
><pre
>
1351 # Stream the Linux desktop view to Kodi. See
1352 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
1353 # for backgorund information.
1355 # Make sure the stream is stopped in Kodi and the gstreamer process is
1356 # killed if something go wrong (for example if curl is unable to find the
1357 # kodi server). Do the same when interrupting this script.
1361 params=
"$
3"
1362 curl --silent --header
'Content-Type: application/json
' \
1363 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
1364 "http://$host/jsonrpc
"
1367 if [ -n
"$kodihost
" ] ; then
1368 # Stop the playing when we end
1369 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
1370 jq .result[].playerid)
1371 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
1373 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
1374 kill
"$gstpid
"
1377 trap cleanup EXIT INT
1379 if [ -n
"$
1" ]; then
1390 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
1391 cut -d
" " -f2|head -
1)
1392 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
1393 videoconvert ! queue2 ! \
1394 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
1395 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
1396 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
1397 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
1398 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
1399 > /dev/null
2>&1 &
1402 # Give stream a second to get going
1405 # Ask kodi to start streaming using its JSON-RPC API
1406 kodicmd
"$kodihost
" Player.Open \
1407 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
1409 # wait for gst to end
1410 wait
"$gstpid
"
1411 </pre
></blockquote
>
1413 <p
>I hope you find the approach useful. I know I do.
</p
>
1415 <p
>As usual, if you use Bitcoin and want to show your support of my
1416 activities, please send Bitcoin donations to my address
1417 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1422 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
1423 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
1424 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
1425 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
1426 <description><p
>PS: See
1427 <ahref=
"http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
1428 followup post
</a
> for a even better approach.
</p
>
1430 <p
>A while back, I was asked by a friend how to stream the desktop to
1431 my projector connected to Kodi. I sadly had to admit that I had no
1432 idea, as it was a task I never had tried. Since then, I have been
1433 looking for a way to do so, preferable without much extra software to
1434 install on either side. Today I found a way that seem to kind of
1435 work. Not great, but it is a start.
</p
>
1437 <p
>I had a look at several approaches, for example
1438 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
1439 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
1440 local storage enough to store the stream locally. This is not going
1441 to work well for me, lacking enough free space, and it would
1442 impossible for my friend to get working.
</p
>
1444 <p
>Next, it occurred to me that perhaps I could use VLC to create a
1445 video stream that Kodi could play. Preferably using
1446 broadcast/multicast, to avoid having to change any setup on the Kodi
1447 side when starting such stream. Unfortunately, the only recipe I
1448 could find using multicast used the rtp protocol, and this protocol
1449 seem to not be supported by Kodi.
</p
>
1451 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
1452 have to specify the IP address of the streaming machine in both the
1453 sending command and the file on the Kodi server. But it is showing my
1454 desktop, and thus allow us to have a shared look on the big screen at
1455 the programs I work on.
</p
>
1457 <p
>I did not spend much time investigating codeces. I combined the
1458 rtp and rtsp recipes from
1459 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
1460 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
1461 this working on the desktop/streaming end.
</p
>
1463 <blockquote
><pre
>
1464 vlc screen:// --sout \
1465 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
1466 </pre
></blockquote
>
1468 <p
>I ssh-ed into my Kodi box and created a file like this with the
1469 same IP address:
</p
>
1471 <blockquote
><pre
>
1472 echo rtsp://
192.168.11.4:
8080/test.sdp \
1473 > /storage/videos/screenstream.m3u
1474 </pre
></blockquote
>
1476 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
1477 as I can tell the IP must be hardcoded for this to work. In other
1478 words, if someone elses machine is going to do the steaming, you have
1479 to update screenstream.m3u on the Kodi machine and adjust the vlc
1480 recipe. To get started, locate the file in Kodi and select the m3u
1481 file while the VLC stream is running. The desktop then show up in my
1482 big screen. :)
</p
>
1484 <p
>When using the same technique to stream a video file with audio,
1485 the audio quality is really bad. No idea if the problem is package
1486 loss or bad parameters for the transcode. I do not know VLC nor Kodi
1487 enough to tell.
</p
>
1489 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
1490 succestions and reminded me about an important step. The
"screen:
"
1491 input source is only available once the vlc-plugin-access-extra
1492 package is installed on Debian. Without it, you will see this error
1493 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
1494 for details.
" He further found that it is possible to drop some parts
1495 of the VLC command line to reduce the amount of hardcoded information.
1496 It is also useful to consider using cvlc to avoid having the VLC
1497 window in the desktop view. In sum, this give us this command line on
1500 <blockquote
><pre
>
1501 cvlc screen:// --sout \
1502 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
1503 </pre
></blockquote
>
1505 <p
>and this on the Kodi end
<p
>
1507 <blockquote
><pre
>
1508 echo rtsp://
192.168.11.4:
8080/ \
1509 > /storage/videos/screenstream.m3u
1510 </pre
></blockquote
>
1512 <p
>Still bad image quality, though. But I did discover that streaming
1513 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
1514 audio quality, so I guess the issue is in the input or transcoding
1515 parts, not the rtsp part. I
've tried to change the vb and ab
1516 parameters to use more bandwidth, but it did not make a
1517 difference.
</p
>
1519 <p
>I further received a suggestion from Einar Haraldseid to try using
1520 gstreamer instead of VLC, and this proved to work great! He also
1521 provided me with the trick to get Kodi to use a multicast stream as
1522 its source. By using this monstrous oneliner, I can stream my desktop
1523 with good video quality in reasonable framerate to the
239.255.0.1
1524 multicast address on port
1234:
1526 <blockquote
><pre
>
1527 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
1528 videoconvert ! queue2 ! \
1529 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
1530 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
1531 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
1532 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
1533 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
1534 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
1535 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
1536 </pre
></blockquote
>
1538 <p
>and this on the Kodi end
<p
>
1540 <blockquote
><pre
>
1541 echo udp://@
239.255.0.1:
1234 \
1542 > /storage/videos/screenstream.m3u
1543 </pre
></blockquote
>
1545 <p
>Note the trick to pick a valid pulseaudio source. It might not
1546 pick the one you need. This approach will of course lead to trouble
1547 if more than one source uses the same multicast port and address.
1548 Note the ttl-mc=
1 setting, which limit the multicast packages to the
1549 local network. If the value is increased, your screen will be
1550 broadcasted further, one network
"hop
" for each increase (read up on
1551 multicast to learn more. :)!
</p
>
1553 <p
>Having cracked how to get Kodi to receive multicast streams, I
1554 could use this VLC command to stream to the same multicast address.
1555 The image quality is way better than the rtsp approach, but gstreamer
1556 seem to be doing a better job.
</p
>
1558 <blockquote
><pre
>
1559 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
1560 </pre
></blockquote
>
1562 <p
>As usual, if you use Bitcoin and want to show your support of my
1563 activities, please send Bitcoin donations to my address
1564 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1569 <title>What is the most supported MIME type in Debian in
2018?
</title>
1570 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
1571 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
1572 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
1573 <description><p
>Five years ago,
1574 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
1575 measured what the most supported MIME type in Debian was
</a
>, by
1576 analysing the desktop files in all packages in the archive. Since
1577 then, the DEP-
11 AppStream system has been put into production, making
1578 the task a lot easier. This made me want to repeat the measurement,
1579 to see how much things changed. Here are the new numbers, for
1580 unstable only this time:
1582 <p
><strong
>Debian Unstable:
</strong
></p
>
1586 ----- -----------------------
1598 30 audio/x-vorbis+ogg
1599 29 image/x-portable-pixmap
1601 27 image/x-portable-bitmap
1603 26 application/x-ogg
1609 <p
>The list was created like this using a sid chroot:
"cat
1610 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
1611 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
1613 <p
>It is interesting to see how image formats have passed text/plain
1614 as the most announced supported MIME type. These days, thanks to the
1615 AppStream system, if you run into a file format you do not know, and
1616 want to figure out which packages support the format, you can find the
1617 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
1618 look up all packages announcing support for this format in their
1619 AppStream metadata (XML or .desktop file) using
"appstreamcli
1620 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
1621 me, want to know which packages support inode/directory, you can get a
1622 list like this:
</p
>
1624 <p
><blockquote
><pre
>
1625 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
1632 Package: doublecmd-common
1634 Package: enlightenment
1654 </pre
></blockquote
></p
>
1656 <p
>Using the same method, I can quickly discover that the Sketchup file
1657 format is not yet supported by any package in Debian:
</p
>
1659 <p
><blockquote
><pre
>
1660 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
1661 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
1663 </pre
></blockquote
></p
>
1665 <p
>Yesterday I used it to figure out which packages support the STL
3D
1668 <p
><blockquote
><pre
>
1669 % appstreamcli what-provides mimetype application/sla|grep Package
1674 </pre
></blockquote
></p
>
1676 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
1678 <p
>As usual, if you use Bitcoin and want to show your support of my
1679 activities, please send Bitcoin donations to my address
1680 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1685 <title>Debian APT upgrade without enough free space on the disk...
</title>
1686 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
1687 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
1688 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
1689 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
1690 for a while, and when I need to update it there is not enough free
1691 space on the disk for apt to do a normal
'apt upgrade
'. I normally
1692 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
1693 upgrade only some of the packages in one batch, until the amount of
1694 packages to download fall below the amount of free space available.
1695 Today, I had about
500 packages to upgrade, and after a while I got
1696 tired of trying to install chunks of packages manually. I concluded
1697 that I did not have the spare hours required to complete the task, and
1698 decided to see if I could automate it. I came up with this small
1699 script which I call
'apt-in-chunks
':
</p
>
1701 <p
><blockquote
><pre
>
1704 # Upgrade packages when the disk is too full to upgrade every
1705 # upgradable package in one lump. Fetching packages to upgrade using
1706 # apt, and then installing using dpkg, to avoid changing the package
1707 # flag for manual/automatic.
1712 if [
"$
1" ]; then
1713 grep -v
"$
1"
1719 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
1720 echo
"Upgrading $p
"
1722 apt install --download-only -y $p
1723 for f in /var/cache/apt/archives/*.deb; do
1724 if [ -e
"$f
" ]; then
1725 dpkg -i /var/cache/apt/archives/*.deb
1730 </pre
></blockquote
></p
>
1732 <p
>The script will extract the list of packages to upgrade, try to
1733 download the packages needed to upgrade one package, install the
1734 downloaded packages using dpkg. The idea is to upgrade packages
1735 without changing the APT mark for the package (ie the one recording of
1736 the package was manually requested or pulled in as a dependency). To
1737 use it, simply run it as root from the command line. If it fail, try
1738 'apt install -f
' to clean up the mess and run the script again. This
1739 might happen if the new packages conflict with one of the old
1740 packages. dpkg is unable to remove, while apt can do this.
</p
>
1742 <p
>It take one option, a package to ignore in the list of packages to
1743 upgrade. The option to ignore a package is there to be able to skip
1744 the packages that are simply too large to unpack. Today this was
1745 'ghc
', but I have run into other large packages causing similar
1746 problems earlier (like TeX).
</p
>
1748 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
1749 alternative ways to handle this. The
"unattended-upgrades
1750 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
1751 each package to upgrade, and then upgrade them in order, smallest set
1752 first. It might be a better option than my above mentioned script.
1753 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
1754 the need for using
"dpkg -i
" in the script above.
</p
>
1756 <p
>As usual, if you use Bitcoin and want to show your support of my
1757 activities, please send Bitcoin donations to my address
1758 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1763 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
1764 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
1765 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
1766 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
1767 <description><p
>A new version of the
1768 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
1769 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
1770 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
1771 useful. It was uploaded the last few days, and the last update will
1772 enter testing tomorrow. See the
1773 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
1774 notes
</a
> for the list of bug fixes and new features. Version
3.2
1775 was announced
6 days ago. We will try to get it into Debian as
1778 <p
>More information related to
3D printing is available on the
1779 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
1780 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
1781 in Debian.
</p
>
1783 <p
>As usual, if you use Bitcoin and want to show your support of my
1784 activities, please send Bitcoin donations to my address
1785 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1790 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
1791 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
1792 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
1793 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
1794 <description><p
>After several months of working and waiting, I am happy to report
1795 that the nice and user friendly
3D printer slicer software Cura just
1796 entered Debian Unstable. It consist of five packages,
1797 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
1798 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
1799 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
1800 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
1801 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
1802 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
1803 two, uranium and cura, entered Unstable yesterday. This should make
1804 it easier for Debian users to print on at least the Ultimaker class of
1805 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
1806 make life easier for at least me. :)
</p
>
1808 <p
>The work to make this happen was done by Gregor Riepl, and I was
1809 happy to assist him in sponsoring the packages. With the introduction
1810 of Cura, Debian is up to three
3D printer slicers at your service,
1811 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
1812 printer, give it a go. :)
</p
>
1814 <p
>The
3D printer software is maintained by the
3D printer Debian
1815 team, flocking together on the
1816 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
1817 mailing list and the
1818 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
1819 IRC channel.
</p
>
1821 <p
>The next step for Cura in Debian is to update the cura package to
1822 version
3.0.3 and then update the entire set of packages to version
1823 3.1.0 which showed up the last few days.
</p
>
1828 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
1829 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
1830 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
1831 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
1832 <description><p
>At my nearby maker space,
1833 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
1834 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
1835 on Windows and MacOS X than Linux, because the software involved had
1836 to be manually compiled and set up on Linux while premade packages
1837 worked out of the box on Windows and MacOS X. I found this annoying,
1838 as the software involved,
1839 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
1840 and should be trivial to get up and running on Linux if someone took
1841 the time to package it for the relevant distributions. I even found
1842 <a href=
"https://bugs.debian.org/
706656">a request for adding into
1843 Debian
</a
> from
2013, which had seem some activity over the years but
1844 never resulted in the software showing up in Debian. So a few days
1845 ago I offered my help to try to improve the situation.
</p
>
1847 <p
>Now I am very happy to see that all the packages required by a
1848 working Cura in Debian are uploaded into Debian and waiting in the NEW
1849 queue for the ftpmasters to have a look. You can track the progress
1851 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
1852 status page for the
3D printer team
</a
>.
</p
>
1854 <p
>The uploaded packages are a bit behind upstream, and was uploaded
1855 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
1856 queue
</a
> while we work up updating the packages to the latest
1857 upstream version.
</p
>
1859 <p
>On a related note, two competitors for Cura, which I found harder
1860 to use and was unable to configure correctly for Ultimaker
2+ in the
1861 short time I spent on it, are already in Debian. If you are looking
1862 for
3D printer
"slicers
" and want something already available in
1864 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
1865 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
1866 The latter is a fork of the former.
</p
>
1868 <p
>As usual, if you use Bitcoin and want to show your support of my
1869 activities, please send Bitcoin donations to my address
1870 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1875 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
1876 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
1877 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
1878 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
1879 <description><p
>Every mobile phone announce its existence over radio to the nearby
1880 mobile cell towers. And this radio chatter is available for anyone
1881 with a radio receiver capable of receiving them. Details about the
1882 mobile phones with very good accuracy is of course collected by the
1883 phone companies, but this is not the topic of this blog post. The
1884 mobile phone radio chatter make it possible to figure out when a cell
1885 phone is nearby, as it include the SIM card ID (IMSI). By paying
1886 attention over time, one can see when a phone arrive and when it leave
1887 an area. I believe it would be nice to make this information more
1888 available to the general public, to make more people aware of how
1889 their phones are announcing their whereabouts to anyone that care to
1892 <p
>I am very happy to report that we managed to get something
1893 visualizing this information up and running for
1894 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
1895 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
1896 library. The solution is based on the
1897 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
1898 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
1899 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
1900 Sone from the Computer Science department of the University of
1901 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
1902 IMSIs) as dots in a web browser graph, with lines to the dot
1903 representing mobile base station it is talking to. It was working in
1904 the lab yesterday, and was moved into place this morning.
</p
>
1906 <p
>We set up a fairly powerful desktop machine using Debian
1907 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
1908 connected and visualize the visible cell phone towers using an
1909 <a href=
"https://github.com/marlow925/hopglass
">English version of
1910 Hopglass
</a
>. A fairly powerfull machine is needed as the
1911 grgsm_livemon_headless processes from
1912 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
1913 the radio signal to data packages is quite CPU intensive.
</p
>
1915 <p
>The frequencies to listen to, are identified using a slightly
1916 patched scan-and-livemon (to set the --args values for each receiver),
1917 and the Hopglass data is generated using the
1918 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
1919 in my meshviewer-output branch
</a
>. For some reason we could not get
1920 more than four SDRs working. There is also a geographical map trying
1921 to show the location of the base stations, but I believe their
1922 coordinates are hardcoded to some random location in Germany, I
1923 believe. The code should be replaced with code to look up location in
1924 a text file, a sqlite database or one of the online databases
1926 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
1927 issue for the topic
</a
>.
1929 <p
>If this sound interesting, visit the stand at the festival!
</p
>
1934 <title>Easier recipe to observe the cell phones around you
</title>
1935 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
1936 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
1937 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
1938 <description><p
>A little more than a month ago I wrote
1939 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
1940 to observe the SIM card ID (aka IMSI number) of mobile phones talking
1941 to nearby mobile phone base stations using Debian GNU/Linux and a
1942 cheap USB software defined radio
</a
>, and thus being able to pinpoint
1943 the location of people and equipment (like cars and trains) with an
1944 accuracy of a few kilometer. Since then we have worked to make the
1945 procedure even simpler, and it is now possible to do this without any
1946 manual frequency tuning and without building your own packages.
</p
>
1948 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
1949 package is now included in Debian testing and unstable, and the
1950 IMSI-catcher code no longer require root access to fetch and decode
1951 the GSM data collected using gr-gsm.
</p
>
1953 <p
>Here is an updated recipe, using packages built by Debian and a git
1954 clone of two python scripts:
</p
>
1958 <li
>Start with a Debian machine running the Buster version (aka
1959 testing).
</li
>
1961 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
1962 python-scapy
</tt
>' as root to install required packages.
</li
>
1964 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
1965 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
1967 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
1969 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
1970 scan-and-livemon
</tt
>' to locate the frequency of nearby base
1971 stations and start listening for GSM packages on one of them.
</li
>
1973 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
1974 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
1978 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
1979 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
1980 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
1981 work with RTL
8232 and other similar USB radio receivers you can get
1983 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
1984 from ebay
</a
>), so for now the solution is to scan using the RTL radio
1985 and only use HackRF for fetching GSM data.
</p
>
1987 <p
>As far as I can tell, a cell phone only show up on one of the
1988 frequencies at the time, so if you are going to track and count every
1989 cell phone around you, you need to listen to all the frequencies used.
1990 To listen to several frequencies, use the --numrecv argument to
1991 scan-and-livemon to use several receivers. Further, I am not sure if
1992 phones using
3G or
4G will show as talking GSM to base stations, so
1993 this approach might not see all phones around you. I typically see
1994 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
1996 <p
>I
've tried to run the scanner on a
1997 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
1998 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
1999 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
2000 stdout, I am told there it is caused by a buffer overflow between the
2001 radio and GNU Radio, caused by the program being unable to read the
2002 GSM data fast enough. If you see a stream of
'O
's from the terminal
2003 where you started scan-and-livemon, you need a give the process more
2004 CPU power. Perhaps someone are able to optimize the code to a point
2005 where it become possible to set up RPi3 based GSM sniffers? I tried
2006 using Raspbian instead of Debian, but there seem to be something wrong
2007 with GNU Radio on raspbian, causing glibc to abort().
</p
>
2012 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
2013 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
2014 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
2015 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
2016 <description><p
>On friday, I came across an interesting article in the Norwegian
2017 web based ICT news magazine digi.no on
2018 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
2019 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
2020 DVB-T software defined radios. The article refered to instructions
2021 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
2022 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
2024 <p
>The instructions said to use Ubuntu, install pip using apt (to
2025 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2026 and the ask pybombs to fetch and build everything you need from
2027 scratch. I wanted to see if I could do the same on the most recent
2028 Debian packages, but this did not work because pybombs tried to build
2029 stuff that no longer build with the most recent openssl library or
2030 some other version skew problem. While trying to get this recipe
2031 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
2032 and the only piece of software dependency missing in Debian was the
2033 gr-gsm package. I also found out that the lead upstream developer of
2034 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2035 Debian packages provided in an Ubuntu PPA repository. All I needed to
2036 do was to dget the Debian source package and built it.
</p
>
2038 <p
>The IMSI collector is a python script listening for packages on the
2039 loopback network device and printing to the terminal some specific GSM
2040 packages with IMSI numbers in them. The code is fairly short and easy
2041 to understand. The reason this work is because gr-gsm include a tool
2042 to read GSM data from a software defined radio like a DVB-T USB stick
2043 and other software defined radios, decode them and inject them into a
2044 network device on your Linux machine (using the loopback device by
2045 default). This proved to work just fine, and I
've been testing the
2046 collector for a few days now.
</p
>
2048 <p
>The updated and simpler recipe is thus to
</p
>
2052 <li
>start with a Debian machine running Stretch or newer,
</li
>
2054 <li
>build and install the gr-gsm package available from
2055 <a href=
"http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
">http://ppa.launchpad.net/ptrkrysik/gr-gsm/ubuntu/pool/main/g/gr-gsm/
</a
>,
</li
>
2057 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
2059 <li
>run grgsm_livemon and adjust the frequency until the terminal
2060 where it was started is filled with a stream of text (meaning you
2061 found a GSM station).
</li
>
2063 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
2067 <p
>To make it even easier in the future to get this sniffer up and
2068 running, I decided to package
2069 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
2070 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
2071 #
871055</a
>), and the package was uploaded into the NEW queue today.
2072 Luckily the gnuradio maintainer has promised to help me, as I do not
2073 know much about gnuradio stuff yet.
</p
>
2075 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
2076 commercial tools like
2077 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
2078 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
2079 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
2080 Stingray
</a
>, but I hope the existance of cheap alternatives can make
2081 more people realise how their whereabouts when carrying a cell phone
2082 is easily tracked. Seeing the data flow on the screen, realizing that
2083 I live close to a police station and knowing that the police is also
2084 wearing cell phones, I wonder how hard it would be for criminals to
2085 track the position of the police officers to discover when there are
2086 police near by, or for foreign military forces to track the location
2087 of the Norwegian military forces, or for anyone to track the location
2088 of government officials...
</p
>
2090 <p
>It is worth noting that the data reported by the IMSI-catcher
2091 script mentioned above is only a fraction of the data broadcasted on
2092 the GSM network. It will only collect one frequency at the time,
2093 while a typical phone will be using several frequencies, and not all
2094 phones will be using the frequencies tracked by the grgsm_livemod
2095 program. Also, there is a lot of radio chatter being ignored by the
2096 simple_IMSI-catcher script, which would be collected by extending the
2097 parser code. I wonder if gr-gsm can be set up to listen to more than
2098 one frequency?
</p
>
2103 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
2104 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
2105 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
2106 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
2107 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
2109 <p
>I finally received a copy of the Norwegian Bokmål edition of
2110 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
2111 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
2112 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2113 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
2114 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
2115 price. The book is also available for download in electronic form as
2116 PDF, EPUB and Mobipocket, as can be
2117 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
2118 as a web page
</a
>.
</p
>
2120 <p
>This is the second book I publish (the first was the book
2121 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
2123 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
2124 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
2126 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
2127 Bokmål
</a
>), and I am very excited to finally wrap up this
2129 "<a href=
"http://www.lulu.com/shop/rapha%C3%ABl-hertzog-and-roland-mas/h%C3%A5ndbok-for-debian-administratoren/paperback/product-
23262290.html
">Håndbok
2130 for Debian-administratoren
</a
>" will be well received.
</p
>
2135 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
2136 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
2137 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
2138 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
2139 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
2140 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
2141 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2142 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2143 på om den fri oversetterløsningen
2144 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
2145 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
2147 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
2150 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2151 rolle og muligheter til å håndtere internasjonale utfordringer, som
2152 for eksempel flykningekrisen.
</p
>
2154 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2155 på temaet:
</p
>
2157 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
2158 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
2163 <p
>Dette oversetter Apertium slik:
</p
>
2166 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2167 andre aktørar og høve til å handtera internasjonale utfordringar, som
2168 til dømes *flykningekrisen.
</p
>
2170 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
2174 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
2175 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
2180 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
2181 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2182 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2183 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
2184 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
2185 det er kanskje flisespikking. Det understreker vel bare at det alltid
2186 trengs korrekturlesning etter automatisk oversettelse.
</p
>
2191 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
2192 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
2193 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
2194 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
2195 <description><p
>Over the years, administrating thousand of NFS mounting linux
2196 computers at the time, I often needed a way to detect if the machine
2197 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
2198 file or directory affected by the hang, the process (and possibly the
2199 shell) will hang too. So you want to be able to detect this without
2200 risking the detection process getting stuck too. It has not been
2201 obvious how to do this. When the hang has lasted a while, it is
2202 possible to find messages like these in dmesg:
</p
>
2204 <p
><blockquote
>
2205 nfs: server nfsserver not responding, still trying
2206 <br
>nfs: server nfsserver OK
2207 </blockquote
></p
>
2209 <p
>It is hard to know if the hang is still going on, and it is hard to
2210 be sure looking in dmesg is going to work. If there are lots of other
2211 messages in dmesg the lines might have rotated out of site before they
2212 are noticed.
</p
>
2214 <p
>While reading through the nfs client implementation in linux kernel
2215 code, I came across some statistics that seem to give a way to detect
2216 it. The om_timeouts sunrpc value in the kernel will increase every
2217 time the above log entry is inserted into dmesg. And after digging a
2218 bit further, I discovered that this value show up in
2219 /proc/self/mountstats on Linux.
</p
>
2221 <p
>The mountstats content seem to be shared between files using the
2222 same file system context, so it is enough to check one of the
2223 mountstats files to get the state of the mount point for the machine.
2224 I assume this will not show lazy umounted NFS points, nor NFS mount
2225 points in a different process context (ie with a different filesystem
2226 view), but that does not worry me.
</p
>
2228 <p
>The content for a NFS mount point look similar to this:
</p
>
2230 <p
><blockquote
><pre
>
2232 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2233 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
2234 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
2236 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
2237 sec: flavor=
1,pseudoflavor=
1
2238 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
2239 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2240 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
2241 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
2243 NULL:
0 0 0 0 0 0 0 0
2244 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
2245 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
2246 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
2247 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
2248 READLINK:
125 125 0 20472 18620 0 1112 1118
2249 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
2250 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
2251 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
2252 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
2253 SYMLINK:
903 903 0 233428 245488 6 5865 5917
2254 MKNOD:
80 80 0 20148 21760 0 299 304
2255 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
2256 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
2257 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
2258 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
2259 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
2260 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
2261 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
2262 FSINFO:
2 2 0 232 328 0 1 1
2263 PATHCONF:
1 1 0 116 140 0 0 0
2264 COMMIT:
0 0 0 0 0 0 0 0
2266 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
2268 </pre
></blockquote
></p
>
2270 <p
>The key number to look at is the third number in the per-op list.
2271 It is the number of NFS timeouts experiences per file system
2272 operation. Here
22 write timeouts and
5 access timeouts. If these
2273 numbers are increasing, I believe the machine is experiencing NFS
2274 hang. Unfortunately the timeout value do not start to increase right
2275 away. The NFS operations need to time out first, and this can take a
2276 while. The exact timeout value depend on the setup. For example the
2277 defaults for TCP and UDP mount points are quite different, and the
2278 timeout value is affected by the soft, hard, timeo and retrans NFS
2279 mount options.
</p
>
2281 <p
>The only way I have been able to get working on Debian and RedHat
2282 Enterprise Linux for getting the timeout count is to peek in /proc/.
2284 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
2285 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
2286 command can be used to get these timeout values. But this do not work
2287 on Linux, as far as I can tell. I
2288 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
2289 but have not seen any replies yet.
</p
>
2291 <p
>Is there a better way to figure out if a Linux NFS client is
2292 experiencing NFS hangs? Is there a way to detect which processes are
2293 affected? Is there a way to get the NFS mount going quickly once the
2294 network problem causing the NFS hang has been cleared? I would very
2295 much welcome some clues, as we regularly run into NFS hangs.
</p
>
2300 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
2301 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
2302 <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>
2303 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
2304 <description><p
>For almost a year now, we have been working on making a Norwegian
2305 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
2306 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
2307 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
2308 we are working on the proof reading to ensure consistent language and
2309 use of correct computer science terms. The plan is to make the book
2310 available on paper, as well as in electronic form. For that to
2311 happen, the proof reading must be completed and all the figures need
2312 to be translated. If you want to help out, get in touch.
</p
>
2314 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
2316 fresh PDF edition
</a
> in A4 format (the final book will have smaller
2317 pages) of the book created every morning is available for
2318 proofreading. If you find any errors, please
2319 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
2320 Weblate and correct the error
</a
>. The
2321 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
2322 of the translation including figures
</a
> is a useful source for those
2323 provide Norwegian bokmål screen shots and figures.
</p
>
2328 <title>Unlimited randomness with the ChaosKey?
</title>
2329 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
2330 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
2331 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
2332 <description><p
>A few days ago I ordered a small batch of
2333 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
2334 USB dongle for generating entropy created by Bdale Garbee and Keith
2335 Packard. Yesterday it arrived, and I am very happy to report that it
2336 work great! According to its designers, to get it to work out of the
2337 box, you need the Linux kernel version
4.1 or later. I tested on a
2338 Debian Stretch machine (kernel version
4.9), and there it worked just
2339 fine, increasing the available entropy very quickly. I wrote a small
2340 test oneliner to test. It first print the current entropy level,
2341 drain /dev/random, and then print the entropy level for five seconds.
2342 Here is the situation without the ChaosKey inserted:
</p
>
2344 <blockquote
><pre
>
2345 % cat /proc/sys/kernel/random/entropy_avail; \
2346 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
2347 for n in $(seq
1 5); do \
2348 cat /proc/sys/kernel/random/entropy_avail; \
2354 28 byte kopiert,
0,
000264565 s,
106 kB/s
2361 </pre
></blockquote
>
2363 <p
>The entropy level increases by
3-
4 every second. In such case any
2364 application requiring random bits (like a HTTPS enabled web server)
2365 will halt and wait for more entrpy. And here is the situation with
2366 the ChaosKey inserted:
</p
>
2368 <blockquote
><pre
>
2369 % cat /proc/sys/kernel/random/entropy_avail; \
2370 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
2371 for n in $(seq
1 5); do \
2372 cat /proc/sys/kernel/random/entropy_avail; \
2378 104 byte kopiert,
0,
000487647 s,
213 kB/s
2385 </pre
></blockquote
>
2387 <p
>Quite the difference. :) I bought a few more than I need, in case
2388 someone want to buy one here in Norway. :)
</p
>
2390 <p
>Update: The dongle was presented at Debconf last year. You might
2391 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
2392 recording illuminating
</a
>. It explains exactly what the source of
2393 randomness is, if you are unable to spot it from the schema drawing
2394 available from the ChaosKey web site linked at the start of this blog
2400 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
2401 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
2402 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
2403 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
2404 <description><p
>Did you ever wonder where the web trafic really flow to reach the
2405 web servers, and who own the network equipment it is flowing through?
2406 It is possible to get a glimpse of this from using traceroute, but it
2407 is hard to find all the details. Many years ago, I wrote a system to
2408 map the Norwegian Internet (trying to figure out if our plans for a
2409 network game service would get low enough latency, and who we needed
2410 to talk to about setting up game servers close to the users. Back
2411 then I used traceroute output from many locations (I asked my friends
2412 to run a script and send me their traceroute output) to create the
2413 graph and the map. The output from traceroute typically look like
2416 <p
><pre
>
2417 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
2418 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
2419 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
2420 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
2421 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
2422 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
2423 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
2424 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
2428 </pre
></p
>
2430 <p
>This show the DNS names and IP addresses of (at least some of the)
2431 network equipment involved in getting the data traffic from me to the
2432 www.stortinget.no server, and how long it took in milliseconds for a
2433 package to reach the equipment and return to me. Three packages are
2434 sent, and some times the packages do not follow the same path. This
2435 is shown for hop
5, where three different IP addresses replied to the
2436 traceroute request.
</p
>
2438 <p
>There are many ways to measure trace routes. Other good traceroute
2439 implementations I use are traceroute (using ICMP packages) mtr (can do
2440 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
2441 traceroute and a lot of other capabilities). All of them are easily
2442 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
2444 <p
>This time around, I wanted to know the geographic location of
2445 different route points, to visualize how visiting a web page spread
2446 information about the visit to a lot of servers around the globe. The
2447 background is that a web site today often will ask the browser to get
2448 from many servers the parts (for example HTML, JSON, fonts,
2449 JavaScript, CSS, video) required to display the content. This will
2450 leak information about the visit to those controlling these servers
2451 and anyone able to peek at the data traffic passing by (like your ISP,
2452 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
2454 <p
>Lets pick an example, the Norwegian parliament web site
2455 www.stortinget.no. It is read daily by all members of parliament and
2456 their staff, as well as political journalists, activits and many other
2457 citizens of Norway. A visit to the www.stortinget.no web site will
2458 ask your browser to contact
8 other servers: ajax.googleapis.com,
2459 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
2460 stats.g.doubleclick.net, www.google-analytics.com,
2461 www.googletagmanager.com and www.netigate.se. I extracted this by
2462 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
2463 Stortinget web page and tell me all the URLs PhantomJS downloaded to
2464 render the page (in HAR format using
2465 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
2466 netsniff example
</a
>. I am very grateful to Gorm for showing me how
2467 to do this). My goal is to visualize network traces to all IP
2468 addresses behind these DNS names, do show where visitors personal
2469 information is spread when visiting the page.
</p
>
2471 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
2472 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geoip-small.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using GeoIP
"/
></a
></p
>
2474 <p
>When I had a look around for options, I could not find any good
2475 free software tools to do this, and decided I needed my own traceroute
2476 wrapper outputting KML based on locations looked up using GeoIP. KML
2477 is easy to work with and easy to generate, and understood by several
2478 of the GIS tools I have available. I got good help from by NUUG
2479 colleague Anders Einar with this, and the result can be seen in
2480 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
2481 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
2482 free GeoIP databases I could find (and the for-pay databases my
2483 friends had access to) is not up to the task. The IP addresses of
2484 central Internet infrastructure would typically be placed near the
2485 controlling companies main office, and not where the router is really
2486 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
2487 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
2489 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
2490 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy-small.png
" alt=
"scapy traceroute graph for URLs used by www.stortinget.no
"/
></a
></p
>
2492 <p
>I also had a look at the visual traceroute graph created by
2493 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
2494 showing IP network ownership (aka AS owner) for the IP address in
2496 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
2497 graph display a lot of useful information about the traceroute in SVG
2498 format
</a
>, and give a good indication on who control the network
2499 equipment involved, but it do not include geolocation. This graph
2500 make it possible to see the information is made available at least for
2501 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
2502 3 Communications and NetDNA.
</p
>
2504 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
2505 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-small.png
" alt=
"example geotraceroute view for www.stortinget.no
"/
></a
></p
>
2507 <p
>In the process, I came across the
2508 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
2509 Salim Gasmi. Its methology of combining guesses based on DNS names,
2510 various location databases and finally use latecy times to rule out
2511 candidate locations seemed to do a very good job of guessing correct
2512 geolocation. But it could only do one trace at the time, did not have
2513 a sensor in Norway and did not make the geolocations easily available
2514 for postprocessing. So I contacted the developer and asked if he
2515 would be willing to share the code (he refused until he had time to
2516 clean it up), but he was interested in providing the geolocations in a
2517 machine readable format, and willing to set up a sensor in Norway. So
2518 since yesterday, it is possible to run traces from Norway in this
2519 service thanks to a sensor node set up by
2520 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
2521 trace in KML format for further processing.
</p
>
2523 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
2524 src=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.png
" alt=
"map of combined traces for URLs used by www.stortinget.no using geotraceroute
"/
></a
></p
>
2526 <p
>Here we can see a lot of trafic passes Sweden on its way to
2527 Denmark, Germany, Holland and Ireland. Plenty of places where the
2528 Snowden confirmations verified the traffic is read by various actors
2529 without your best interest as their top priority.
</p
>
2531 <p
>Combining KML files is trivial using a text editor, so I could loop
2532 over all the hosts behind the urls imported by www.stortinget.no and
2533 ask for the KML file from GeoTraceroute, and create a combined KML
2534 file with all the traces (unfortunately only one of the IP addresses
2535 behind the DNS name is traced this time. To get them all, one would
2536 have to request traces using IP number instead of DNS names from
2537 GeoTraceroute). That might be the next step in this project.
</p
>
2539 <p
>Armed with these tools, I find it a lot easier to figure out where
2540 the IP traffic moves and who control the boxes involved in moving it.
2541 And every time the link crosses for example the Swedish border, we can
2542 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
2543 Britain and NSA in USA and cables around the globe. (Hm, what should
2544 we tell them? :) Keep that in mind if you ever send anything
2545 unencrypted over the Internet.
</p
>
2547 <p
>PS: KML files are drawn using
2548 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
2549 Rublev
<a/
>, as it was less cluttered than the local Linux application
2550 Marble. There are heaps of other options too.
</p
>
2552 <p
>As usual, if you use Bitcoin and want to show your support of my
2553 activities, please send Bitcoin donations to my address
2554 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2559 <title>Appstream just learned how to map hardware to packages too!
</title>
2560 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
2561 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
2562 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
2563 <description><p
>I received a very nice Christmas present today. As my regular
2564 readers probably know, I have been working on the
2565 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
2566 system
</a
> for many years. The goal of the Isenkram system is to make
2567 it easier for users to figure out what to install to get a given piece
2568 of hardware to work in Debian, and a key part of this system is a way
2569 to map hardware to packages. Isenkram have its own mapping database,
2570 and also uses data provided by each package using the AppStream
2571 metadata format. And today,
2572 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
2573 Debian learned to look up hardware the same way Isenkram is doing it,
2574 ie using fnmatch():
</p
>
2576 <p
><pre
>
2577 % appstreamcli what-provides modalias \
2578 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2579 Identifier: pymissile [generic]
2581 Summary: Control original Striker USB Missile Launcher
2583 % appstreamcli what-provides modalias usb:v0694p0002d0000
2584 Identifier: libnxt [generic]
2586 Summary: utility library for talking to the LEGO Mindstorms NXT brick
2589 Identifier: t2n [generic]
2591 Summary: Simple command-line tool for Lego NXT
2594 Identifier: python-nxt [generic]
2596 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
2599 Identifier: nbc [generic]
2601 Summary: C compiler for LEGO Mindstorms NXT bricks
2604 </pre
></p
>
2606 <p
>A similar query can be done using the combined AppStream and
2607 Isenkram databases using the isenkram-lookup tool:
</p
>
2609 <p
><pre
>
2610 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2612 % isenkram-lookup usb:v0694p0002d0000
2618 </pre
></p
>
2620 <p
>You can find modalias values relevant for your machine using
2621 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
2623 <p
>If you want to make this system a success and help Debian users
2624 make the most of the hardware they have, please
2625 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
2626 AppStream metadata for your package following the guidelines
</a
>
2627 documented in the wiki. So far only
11 packages provide such
2628 information, among the several hundred hardware specific packages in
2629 Debian. The Isenkram database on the other hand contain
101 packages,
2630 mostly related to USB dongles. Most of the packages with hardware
2631 mapping in AppStream are LEGO Mindstorms related, because I have, as
2632 part of my involvement in
2633 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
2634 team
</a
> given priority to making sure LEGO users get proposed the
2635 complete set of packages in Debian for that particular hardware. The
2636 team also got a nice Christmas present today. The
2637 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
2638 package
</a
> made it into Debian. With this package in place, it is
2639 now possible to use the LEGO Mindstorms NXT unit with only free
2640 software, as the nxt-firmware package contain the source and firmware
2641 binaries for the NXT brick.
</p
>
2643 <p
>As usual, if you use Bitcoin and want to show your support of my
2644 activities, please send Bitcoin donations to my address
2645 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2650 <title>Isenkram updated with a lot more hardware-package mappings
</title>
2651 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
2652 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
2653 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
2654 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
2655 system
</a
> I wrote two years ago to make it easier in Debian to find
2656 and install packages to get your hardware dongles to work, is still
2657 going strong. It is a system to look up the hardware present on or
2658 connected to the current system, and map the hardware to Debian
2659 packages. It can either be done using the tools in isenkram-cli or
2660 using the user space daemon in the isenkram package. The latter will
2661 notify you, when inserting new hardware, about what packages to
2662 install to get the dongle working. It will even provide a button to
2663 click on to ask packagekit to install the packages.
</p
>
2665 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
2667 <p
><pre
>
2684 </pre
></p
>
2686 <p
>It can also list the firware package providing firmware requested
2687 by the load kernel modules, which in my case is an empty list because
2688 I have all the firmware my machine need:
2690 <p
><pre
>
2691 % /usr/sbin/isenkram-autoinstall-firmware -l
2692 info: did not find any firmware files requested by loaded kernel modules. exiting
2694 </pre
></p
>
2696 <p
>The last few days I had a look at several of the around
250
2697 packages in Debian with udev rules. These seem like good candidates
2698 to install when a given hardware dongle is inserted, and I found
2699 several that should be proposed by isenkram. I have not had time to
2700 check all of them, but am happy to report that now there are
97
2701 packages packages mapped to hardware by Isenkram.
11 of these
2702 packages provide hardware mapping using AppStream, while the rest are
2703 listed in the modaliases file provided in isenkram.
</p
>
2705 <p
>These are the packages with hardware mappings at the moment. The
2706 <strong
>marked packages
</strong
> are also announcing their hardware
2707 support using AppStream, for everyone to use:
</p
>
2709 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
2710 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
2711 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
2712 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
2713 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
2714 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
2715 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
2716 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
2717 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
2718 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
2719 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
2720 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
2721 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
2722 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
2723 pcscd, pidgin-blinklight, printer-driver-splix,
2724 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
2725 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
2726 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
2727 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
2728 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
2729 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
2730 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
2731 xserver-xorg-video-vmware, yubikey-personalization and
2732 zd1211-firmware
</p
>
2734 <p
>If you know of other packages, please let me know with a wishlist
2735 bug report against the isenkram-cli package, and ask the package
2737 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
2738 metadata according to the guidelines
</a
> to provide the information
2739 for everyone. In time, I hope to get rid of the isenkram specific
2740 hardware mapping and depend exclusively on AppStream.
</p
>
2742 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
2743 much hardware, and suggest that the package with with any ethernet
2744 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
2745 the details. I hope the maintainer find time to address it soon. In
2746 the mean time I provide an override in isenkram.
</p
>
2751 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
2752 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
2753 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
2754 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
2755 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
2757 <p
>In my early years, I played
2758 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
2759 Elite
</a
> on my PC. I spent many months trading and fighting in
2760 space, and reached the
'elite
' fighting status before I moved on. The
2761 original Elite game was available on Commodore
64 and the IBM PC
2762 edition I played had a
64 KB executable. I am still impressed today
2763 that the authors managed to squeeze both a
3D engine and details about
2764 more than
2000 planet systems across
7 galaxies into a binary so
2767 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
2768 software game Oolite inspired by Elite
</a
> for a while, but did not
2769 really have time to test it properly until a few days ago. It was
2770 great to discover that my old knowledge about trading routes were
2771 still valid. But my fighting and flying abilities were gone, so I had
2772 to retrain to be able to dock on a space station. And I am still not
2773 able to make much resistance when I am attacked by pirates, so I
2774 bougth and mounted the most powerful laser in the rear to be able to
2775 put up at least some resistance while fleeing for my life. :)
</p
>
2777 <p
>When playing Elite in the late eighties, I had to discover
2778 everything on my own, and I had long lists of prices seen on different
2779 planets to be able to decide where to trade what. This time I had the
2781 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
2782 where information about each planet is easily available with common
2783 price ranges and suggested trading routes. This improved my ability
2784 to earn money and I have been able to earn enough to buy a lot of
2785 useful equipent in a few days. I believe I originally played for
2786 months before I could get a docking computer, while now I could get it
2787 after less then a week.
</p
>
2789 <p
>If you like science fiction and dreamed of a life as a vagabond in
2790 space, you should try out Oolite. It is available for Linux, MacOSX
2791 and Windows, and is included in Debian and derivatives since
2011.
</p
>
2793 <p
>As usual, if you use Bitcoin and want to show your support of my
2794 activities, please send Bitcoin donations to my address
2795 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2800 <title>Quicker Debian installations using eatmydata
</title>
2801 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
2802 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
2803 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
2804 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
2805 installation system, observing how using
2806 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
2807 could speed up the installation
</a
> quite a bit. My testing measured
2808 speedup around
20-
40 percent for Debian Edu, where we install around
2809 1000 packages from within the installer. The eatmydata package
2810 provide a way to disable/delay file system flushing. This is a bit
2811 risky in the general case, as files that should be stored on disk will
2812 stay only in memory a bit longer than expected, causing problems if a
2813 machine crashes at an inconvenient time. But for an installation, if
2814 the machine crashes during installation the process is normally
2815 restarted, and avoiding disk operations as much as possible to speed
2816 up the process make perfect sense.
2818 <p
>I added code in the Debian Edu specific installation code to enable
2819 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
2820 but did not have time to push it any further. But a few months ago I
2821 picked it up again and worked with the libeatmydata package maintainer
2822 Mattia Rizzolo to make it easier for everyone to get this installation
2823 speedup in Debian. Thanks to our cooperation There is now an
2824 eatmydata-udeb package in Debian testing and unstable, and simply
2825 enabling/installing it in debian-installer (d-i) is enough to get the
2826 quicker installations. It can be enabled using preseeding. The
2827 following untested kernel argument should do the trick:
</p
>
2829 <blockquote
><pre
>
2830 preseed/early_command=
"anna-install eatmydata-udeb
"
2831 </pre
></blockquote
>
2833 <p
>This should ask d-i to install the package inside the d-i
2834 environment early in the installation sequence. Having it installed
2835 in d-i in turn will make sure the relevant scripts are called just
2836 after debootstrap filled /target/ with the freshly installed Debian
2837 system to configure apt to run dpkg with eatmydata. This is enough to
2838 speed up the installation process. There is a proposal to
2839 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
2840 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
2841 tested its impact.
</p
>
2847 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
2848 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
2849 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
2850 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
2851 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
2852 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
2853 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
2854 elever over det ganske land skal levere inn hvert år. Det mange ikke
2855 vet er at selv om de kommersielle alternativene
2856 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
2857 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
2858 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
2859 utmerket fri programvarealternativ som kan. Oversetterverktøyet
2860 Apertium har støtte for en rekke språkkombinasjoner, og takket være
2861 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
2862 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
2863 nynorsk, og få den automatoversatt til det andre skriftspråket.
2864 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
2865 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
2866 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
2867 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
2868 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
2869 teksten din i webskjemaet der.
2871 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
2872 teknologien kan du enten installere pakken
2873 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
2874 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
2875 api.apertium.org. Se
2876 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
2877 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
2878 denne teksten som ble skrevet på bokmål over maskinoversatt til
2883 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
2884 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
2885 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
2886 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
2887 veit er at sjølv om dei kommersielle alternativa
2888 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
2889 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
2890 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
2891 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
2892 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
2893 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
2894 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
2895 nynorsk, og få den *automatoversatt til det andre skriftspråket.
2896 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
2897 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
2898 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
2899 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
2900 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
2901 teksta di i *webskjemaet der.
2903 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
2904 teknologien kan du anten installera pakken
2905 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
2906 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
2907 *api.*apertium.org. Sjå
2908 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
2909 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
2910 for denne teksta som vart skreva på bokmål over *maskinoversatt til
2916 <title>Coz profiler for multi-threaded software is now in Debian
</title>
2917 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
2918 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
2919 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
2920 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
2921 profiler able to run benchmarking experiments on the instrumented
2922 multi-threaded program, finally
2923 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
2924 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
2926 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
2927 blogged about the coz tool
</a
> in August working with upstream to make
2928 it suitable for Debian. There are still issues with clang
2929 compatibility, inline assembly only working x86 and minimized
2930 JavaScript libraries.
</p
>
2932 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
2934 <p
><blockquote
>
2935 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
2936 </blockquote
></p
>
2938 <p
>This will produce a profile.coz file in the current working
2939 directory with the profiling information. This is then given to a
2940 JavaScript application provided in the package and available from
2941 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
2942 To start the local copy, invoke it in a browser like this:
</p
>
2944 <p
><blockquote
>
2945 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
2946 </blockquote
></p
>
2948 <p
>See the project home page and the
2949 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
2950 ;login: article on Coz
</a
> for more information on how it is
2956 <title>My own self balancing Lego Segway
</title>
2957 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
2958 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
2959 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
2960 <description><p
>A while back I received a Gyro sensor for the NXT
2961 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
2962 present. It had been on my wishlist for a while, because I wanted to
2963 build a Segway like balancing lego robot. I had already built
2964 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
2965 robot
</a
> with the kids, using the light/color sensor included in the
2966 NXT kit as the balance sensor, but it was not working very well. It
2967 could balance for a while, but was very sensitive to the light
2968 condition in the room and the reflective properties of the surface and
2969 would fall over after a short while. I wanted something more robust,
2971 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
2972 gyro sensor from HiTechnic
</a
> I believed would solve it on my
2973 wishlist for some years before it suddenly showed up as a gift from my
2974 loved ones. :)
</p
>
2976 <p
>Unfortunately I have not had time to sit down and play with it
2977 since then. But that changed some days ago, when I was searching for
2978 lego segway information and came across a recipe from HiTechnic for
2980 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
2981 HTWay
</a
>, a segway like balancing robot. Build instructions and
2982 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
2983 code
</a
> was included, so it was just a question of putting it all
2984 together. And thanks to the great work of many Debian developers, the
2985 compiler needed to build the source for the NXT is already included in
2986 Debian, so I was read to go in less than an hour. The resulting robot
2987 do not look very impressive in its simplicity:
</p
>
2989 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
2991 <p
>Because I lack the infrared sensor used to control the robot in the
2992 design from HiTechnic, I had to comment out the last task
2993 (taskControl). I simply placed /* and */ around it get the program
2994 working without that sensor present. Now it balances just fine until
2995 the battery status run low:
</p
>
2997 <p align=
"center
"><video width=
"70%
" controls=
"true
">
2998 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
2999 </video
></p
>
3001 <p
>Now we would like to teach it how to follow a line and take remote
3002 control instructions using the included Bluetooth receiver in the NXT.
</p
>
3004 <p
>If you, like me, love LEGO and want to make sure we find the tools
3005 they need to work with LEGO in Debian and all our derivative
3006 distributions like Ubuntu, check out
3007 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
3008 project page
</a
> and join the Debian LEGO team. Personally I own a
3009 RCX and NXT controller (no EV3), and would like to make sure the
3010 Debian tools needed to program the systems I own work as they
3016 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
3017 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
3018 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
3019 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
3020 <description><p
>In July
3021 <a href=
"http://people.skolelinux.org/pere/blog/How_to_use_the_Signal_app_if_you_only_have_a_land_line__ie_no_mobile_phone_.html
">I
3022 wrote how to get the Signal Chrome/Chromium app working
</a
> without
3023 the ability to receive SMS messages (aka without a cell phone). It is
3024 time to share some experiences and provide an updated setup.
</p
>
3026 <p
>The Signal app have worked fine for several months now, and I use
3027 it regularly to chat with my loved ones. I had a major snag at the
3028 end of my summer vacation, when the the app completely forgot my
3029 setup, identity and keys. The reason behind this major mess was
3030 running out of disk space. To avoid that ever happening again I have
3031 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
3032 roll back to an earlier version if the files are wiped by mistake. I
3033 had to use it once after introducing the git backup. When rolling
3034 back to an earlier version, one need to use the
'reset session
' option
3035 in Signal to get going, and notify the people you talk with about the
3036 problem. I assume there is some sequence number tracking in the
3037 protocol to detect rollback attacks. The git repository is rather big
3038 (
674 MiB so far), but I have not tried to figure out if some of the
3039 content can be added to a .gitignore file due to lack of spare
3042 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
3043 make it impossible to send messages using Signal. I could still
3044 receive them, but had to patch the code with a new timestamp to send.
3045 I believe the timeout is added by the developers to force people to
3046 upgrade to the latest version of the app, even when there is no
3047 protocol changes, to reduce the version skew among the user base and
3048 thus try to keep the number of support requests down.
</p
>
3050 <p
>Since my original recipe, the Signal source code changed slightly,
3051 making the old patch fail to apply cleanly. Below is an updated
3052 patch, including the shell wrapper I use to start Signal. The
3053 original version required a new user to locate the JavaScript console
3054 and call a function from there. I got help from a friend with more
3055 JavaScript knowledge than me to modify the code to provide a GUI
3056 button instead. This mean that to get started you just need to run
3057 the wrapper and click the
'Register without mobile phone
' to get going
3058 now. I
've also modified the timeout code to always set it to
90 days
3059 in the future, to avoid having to patch the code regularly.
</p
>
3061 <p
>So, the updated recipe for Debian Jessie:
</p
>
3065 <li
>First, install required packages to get the source code and the
3066 browser you need. Signal only work with Chrome/Chromium, as far as I
3067 know, so you need to install it.
3070 apt install git tor chromium
3071 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3072 </pre
></li
>
3074 <li
>Modify the source code using command listed in the the patch
3075 block below.
</li
>
3077 <li
>Start Signal using the run-signal-app wrapper (for example using
3078 <tt
>`pwd`/run-signal-app
</tt
>).
3080 <li
>Click on the
'Register without mobile phone
', will in a phone
3081 number you can receive calls to the next minute, receive the
3082 verification code and enter it into the form field and press
3083 'Register
'. Note, the phone number you use will be user Signal
3084 username, ie the way others can find you on Signal.
</li
>
3086 <li
>You can now use Signal to contact others. Note, new contacts do
3087 not show up in the contact list until you restart Signal, and there is
3088 no way to assign names to Contacts. There is also no way to create or
3089 update chat groups. I suspect this is because the web app do not have
3090 a associated contact database.
</li
>
3094 <p
>I am still a bit uneasy about using Signal, because of the way its
3095 main author moxie0 reject federation and accept dependencies to major
3096 corporations like Google (part of the code is fetched from Google) and
3097 Amazon (the central coordination point is owned by Amazon). See for
3099 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
3100 LibreSignal issue tracker
</a
> for a thread documenting the authors
3101 view on these issues. But the network effect is strong in this case,
3102 and several of the people I want to communicate with already use
3103 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
3104 once it
<a href=
"https://bugs.debian.org/
830265">work on my
3105 laptop
</a
>? It already work on Windows and Android, and is included
3106 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
3107 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
3108 working on Debian Stable.
</p
>
3110 <p
>Anyway, this is the patch I apply to the Signal code to get it
3111 working. It switch to the production servers, disable to timeout,
3112 make registration easier and add the shell wrapper:
</p
>
3115 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
3116 diff --git a/js/background.js b/js/background.js
3117 index
24b4c1d.
.579345f
100644
3118 --- a/js/background.js
3119 +++ b/js/background.js
3124 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
3125 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
3126 var SERVER_PORTS = [
80,
4433,
8443];
3127 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
3128 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
3129 var messageReceiver;
3130 window.getSocketStatus = function() {
3131 if (messageReceiver) {
3132 diff --git a/js/expire.js b/js/expire.js
3133 index
639aeae..beb91c3
100644
3138 'use strict
';
3139 - var BUILD_EXPIRATION =
0;
3140 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
3142 window.extension = window.extension || {};
3144 diff --git a/js/views/install_view.js b/js/views/install_view.js
3145 index
7816f4f.
.1d6233b
100644
3146 --- a/js/views/install_view.js
3147 +++ b/js/views/install_view.js
3150 'click .step1
': this.selectStep.bind(this,
1),
3151 'click .step2
': this.selectStep.bind(this,
2),
3152 -
'click .step3
': this.selectStep.bind(this,
3)
3153 +
'click .step3
': this.selectStep.bind(this,
3),
3154 +
'click .callreg
': function() { extension.install(
'standalone
') },
3157 clearQR: function() {
3158 diff --git a/options.html b/options.html
3159 index dc0f28e.
.8d709f6
100644
3163 &lt;div class=
'nav
'>
3164 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
3165 &lt;p
>{{ installTagline }}
&lt;/p
>
3166 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
3167 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
3168 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
3171 &lt;span class=
'dot step1 selected
'>&lt;/span
>
3172 &lt;span class=
'dot step2
'>&lt;/span
>
3173 &lt;span class=
'dot step3
'>&lt;/span
>
3174 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
3175 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
3181 +userdata=
"`pwd`/userdata
"
3182 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
3183 + (cd $userdata
&& git init)
3185 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
3187 + --proxy-server=
"socks://localhost:
9050" \
3188 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3190 chmod a+rx run-signal-app
3193 <p
>As usual, if you use Bitcoin and want to show your support of my
3194 activities, please send Bitcoin donations to my address
3195 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3200 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
3201 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
3202 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
3203 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
3204 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
3205 system
</a
> provide a practical and easy way to figure out which
3206 packages support the hardware in a given machine. The command line
3207 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
3208 convenient way to list and install packages relevant for the current
3209 hardware during system installation, both user space packages and
3210 firmware packages. The GUI background daemon on the other hand provide
3211 a pop-up proposing to install packages when a new dongle is inserted
3212 while using the computer. For example, if you plug in a smart card
3213 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
3214 that package isn
't already installed, and if you plug in a USB video
3215 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
3216 cheese is currently missing. This already work just fine.
</p
>
3218 <p
>But Isenkram depend on a database mapping from hardware IDs to
3219 package names. When I started no such database existed in Debian, so
3220 I made my own data set and included it with the isenkram package and
3221 made isenkram fetch the latest version of this database from git using
3222 http. This way the isenkram users would get updated package proposals
3223 as soon as I learned more about hardware related packages.
</p
>
3225 <p
>The hardware is identified using modalias strings. The modalias
3226 design is from the Linux kernel where most hardware descriptors are
3227 made available as a strings that can be matched using filename style
3228 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3229 identifiers.
</p
>
3231 <p
>The downside to the Isenkram specific database is that there is no
3232 information about relevant distribution / Debian version, making
3233 isenkram propose obsolete packages too. But along came AppStream, a
3234 cross distribution mechanism to store and collect metadata about
3235 software packages. When I heard about the proposal, I contacted the
3236 people involved and suggested to add a hardware matching rule using
3237 modalias strings in the specification, to be able to use AppStream for
3238 mapping hardware to packages. This idea was accepted and AppStream is
3239 now a great way for a package to announce the hardware it support in a
3240 distribution neutral way. I wrote
3241 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
3242 recipe on how to add such meta-information
</a
> in a blog post last
3243 December. If you have a hardware related package in Debian, please
3244 announce the relevant hardware IDs using AppStream.
</p
>
3246 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
3247 RCX or NXT unit, announce this support using AppStream. The effect is
3248 that when you insert such LEGO robot controller into your Debian
3249 machine, Isenkram will propose to install the packages needed to get
3250 it working. The intention is that this should allow the local user to
3251 start programming his robot controller right away without having to
3252 guess what packages to use or which permissions to fix.
</p
>
3254 <p
>But when I sat down with my son the other day to program our NXT
3255 unit using his Debian Stretch computer, I discovered something
3256 annoying. The local console user (ie my son) did not get access to
3257 the USB device for programming the unit. This used to work, but no
3258 longer in Jessie and Stretch. After some investigation and asking
3259 around on #debian-devel, I discovered that this was because udev had
3260 changed the mechanism used to grant access to local devices. The
3261 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
3262 no longer applied, because LDAP users no longer was added to the
3263 plugdev group during login. Michael Biebl told me that this method
3264 was obsolete and the new method used ACLs instead. This was good
3265 news, as the plugdev mechanism is a mess when using a remote user
3266 directory like LDAP. Using ACLs would make sure a user lost device
3267 access when she logged out, even if the user left behind a background
3268 process which would retain the plugdev membership with the ConsoleKit
3269 setup. Armed with this knowledge I moved on to fix the access problem
3270 for the LEGO Mindstorms related packages.
</p
>
3272 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
3273 applied directly for a device, or is applied in
3274 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
3275 LEGO Mindstorms udev rules did not have a class, I decided to add the
3276 tag directly in the udev rules files included in the packages. Here
3277 is one example. For the nqc C compiler for the RCX, the
3278 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
3280 <p
><pre
>
3281 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
3282 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
3283 </pre
></p
>
3285 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
3286 packages using plugdev in their /lib/udev/rules.d/ files should be
3287 changed to use this tag (either directly or indirectly via
3288 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
3289 to detect this?
</p
>
3291 <p
>I
've been unable to find good documentation on the uaccess feature.
3292 It is unclear to me if the uaccess tag is an internal implementation
3293 detail like the udev-acl tag used by
3294 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
3295 indirect method is the preferred way. Michael
3296 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
3297 documentation from the systemd project
</a
> and I hope it will make
3298 this clearer. For now I use the generic classes when they exist and
3299 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
3300 directly if no such class exist.
</p
>
3302 <p
>To learn more about the isenkram system, please check out
3303 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
3304 blog posts tagged isenkram
</a
>.
</p
>
3306 <p
>To help out making life for LEGO constructors in Debian easier,
3307 please join us on our IRC channel
3308 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
3309 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
3310 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
3311 list is not yet created, but we are working on it. :)
</p
>
3313 <p
>As usual, if you use Bitcoin and want to show your support of my
3314 activities, please send Bitcoin donations to my address
3315 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3320 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
3321 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
3322 <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>
3323 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
3324 <description><p
>In April we
3325 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
3326 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
3327 how to set up and administrate a Debian system. Today I am happy to
3328 report that the first draft is now publicly available. You can find
3329 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
3330 Administrator
's Handbook page
</a
> (under Other languages). The first
3331 eight chapters have a first draft translation, and we are working on
3332 proofreading the content. If you want to help out, please start
3334 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
3335 hosted weblate project page
</a
>, and get in touch using
3336 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
3337 translators mailing list
</a
>. Please also check out
3338 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
3339 contributors
</a
>. A good way to contribute is to proofread the text
3340 and update weblate if you find errors.
</p
>
3342 <p
>Our goal is still to make the Norwegian book available on paper as well as
3343 electronic form.
</p
>
3348 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
3349 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
3350 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
3351 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
3352 <description><p
>This summer, I read a great article
3353 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
3354 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
3355 how to profile multi-threaded programs. It presented a system for
3356 profiling software by running experiences in the running program,
3357 testing how run time performance is affected by
"speeding up
" parts of
3358 the code to various degrees compared to a normal run. It does this by
3359 slowing down parallel threads while the
"faster up
" code is running
3360 and measure how this affect processing time. The processing time is
3361 measured using probes inserted into the code, either using progress
3362 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
3363 can also measure unmodified code by measuring complete the program
3364 runtime and running the program several times instead.
</p
>
3366 <p
>The project and presentation was so inspiring that I would like to
3367 get the system into Debian. I
3368 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
3369 a WNPP request for it
</a
> and contacted upstream to try to make the
3370 system ready for Debian by sending patches. The build process need to
3371 be changed a bit to avoid running
'git clone
' to get dependencies, and
3372 to include the JavaScript web page used to visualize the collected
3373 profiling information included in the source package.
3374 But I expect that should work out fairly soon.
</p
>
3376 <p
>The way the system work is fairly simple. To run an coz experiment
3377 on a binary with debug symbols available, start the program like this:
3379 <p
><blockquote
><pre
>
3380 coz run --- program-to-run
3381 </pre
></blockquote
></p
>
3383 <p
>This will create a text file profile.coz with the instrumentation
3384 information. To show what part of the code affect the performance
3385 most, use a web browser and either point it to
3386 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
3387 or use the copy from git (in the gh-pages branch). Check out this web
3388 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
3389 profiling more useful you include
&lt;coz.h
&gt; and insert the
3390 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
3391 code, rebuild and run the profiler. This allow coz to do more
3392 targeted experiments.
</p
>
3394 <p
>A video published by ACM
3395 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
3396 Coz profiler
</a
> is available from Youtube. There is also a paper
3397 from the
25th Symposium on Operating Systems Principles available
3399 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
3400 finding code that counts with causal profiling
</a
>.
</p
>
3402 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
3403 for Coz is available from github. It will only build with clang
3405 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
3406 feature missing in GCC
</a
>, but I
've submitted
3407 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
3408 it
</a
> and hope it will be included in the upstream source soon.
</p
>
3410 <p
>Please get in touch if you, like me, would like to see this piece
3411 of software in Debian. I would very much like some help with the
3412 packaging effort, as I lack the in depth knowledge on how to package
3413 C++ libraries.
</p
>
3418 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
3419 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
3420 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
3421 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
3422 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
3423 to be a slight challenge. Here is the recipe if I ever need to do it
3424 again. It all started by me wanting to try the recipe to set up
3425 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
3426 hardened Android installation
</a
> from the Tor project blog on a
3427 device I had access to. It is a old mobile phone with a broken
3428 microphone The initial idea had been to just
3429 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
3430 CyanogenMod on it
</a
>, but did not quite find time to start on it
3431 until a few days ago.
</p
>
3433 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
3434 loader (press volume down and power at the same time), (
2) select
3435 'fastboot
' before (
3) connecting the device via USB to a Linux
3436 machine, (
4) request the device identifier token by running
'fastboot
3437 oem get_identifier_token
', (
5) request the device unlocking key using
3438 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
3439 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
3441 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
3442 or newer, and the device I was working on had
2.00.0027. This
3443 apparently can be easily fixed by downloading a Windows program and
3444 running it on your Windows machine, if you accept the terms Microsoft
3445 require you to accept to use Windows - which I do not. So I had to
3446 come up with a different approach. I got a lot of help from AndyCap
3447 on #nuug, and would not have been able to get this working without
3450 <p
>First I needed to extract the hboot firmware from
3451 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
3452 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
3453 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
3454 project named unruu
</a
> using libunshield. The unshield tool did not
3455 recognise the file format, but unruu worked and extracted rom.zip,
3456 containing the new hboot firmware and a text file describing which
3457 devices it would work for.
</p
>
3459 <p
>Next, I needed to get the new firmware into the device. For this I
3460 followed some instructions
3461 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
3462 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
3463 machine with Debian testing:
</p
>
3465 <p
><pre
>
3466 adb reboot-bootloader
3467 fastboot oem rebootRUU
3468 fastboot flash zip rom.zip
3469 fastboot flash zip rom.zip
3471 </pre
></p
>
3473 <p
>The flash command apparently need to be done twice to take effect,
3474 as the first is just preparations and the second one do the flashing.
3475 The adb command is just to get to the boot loader menu, so turning the
3476 device on while holding volume down and the power button should work
3479 <p
>With the new hboot version in place I could start following the
3480 instructions on the HTC developer web site. I got the device token
3481 like this:
</p
>
3483 <p
><pre
>
3484 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
3487 <p
>And once I got the unlock code via email, I could use it like
3490 <p
><pre
>
3491 fastboot flash unlocktoken Unlock_code.bin
3492 </pre
></p
>
3494 <p
>And with that final step in place, the phone was unlocked and I
3495 could start stuffing the software of my own choosing into the device.
3496 So far I only inserted a replacement recovery image to wipe the phone
3497 before I start. We will see what happen next. Perhaps I should
3498 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
3503 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
3504 <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>
3505 <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>
3506 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
3507 <description><p
>For a while now, I have wanted to test
3508 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
3509 said to provide end to end encrypted communication and several of my
3510 friends and family are already using it. As I by choice do not own a
3511 mobile phone, this proved to be harder than expected. And I wanted to
3512 have the source of the client and know that it was the code used on my
3513 machine. But yesterday I managed to get it working. I used the
3514 Github source, compared it to the source in
3515 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
3516 Signal Chrome app
</a
> available from the Chrome web store, applied
3517 patches to use the production Signal servers, started the app and
3518 asked for the hidden
"register without a smart phone
" form. Here is
3519 the recipe how I did it.
</p
>
3521 <p
>First, I fetched the Signal desktop source from Github, using
3524 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3527 <p
>Next, I patched the source to use the production servers, to be
3528 able to talk to other Signal users:
</p
>
3531 cat
&lt;
&lt;EOF | patch -p0
3532 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
3533 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
3534 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
3539 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
3540 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
3541 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
3542 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
3543 var messageReceiver;
3544 window.getSocketStatus = function() {
3545 if (messageReceiver) {
3546 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
3547 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
3548 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
3551 'use strict
';
3552 - var BUILD_EXPIRATION =
0;
3553 + var BUILD_EXPIRATION =
1474492690000;
3555 window.extension = window.extension || {};
3560 <p
>The first part is changing the servers, and the second is updating
3561 an expiration timestamp. This timestamp need to be updated regularly.
3562 It is set
90 days in the future by the build process (Gruntfile.js).
3563 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
3565 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
3566 script to launch Signal in Chromium.
</p
>
3573 --proxy-server=
"socks://localhost:
9050" \
3574 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
3577 <p
> The script start the app and configure Chromium to use the Tor
3578 SOCKS5 proxy to make sure those controlling the Signal servers (today
3579 Amazon and Whisper Systems) as well as those listening on the lines
3580 will have a harder time location my laptop based on the Signal
3581 connections if they use source IP address.
</p
>
3583 <p
>When the script starts, one need to follow the instructions under
3584 "Standalone Registration
" in the CONTRIBUTING.md file in the git
3585 repository. I right clicked on the Signal window to get up the
3586 Chromium debugging tool, visited the
'Console
' tab and wrote
3587 'extension.install(
"standalone
")
' on the console prompt to get the
3588 registration form. Then I entered by land line phone number and
3589 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
3590 repeated the verification code three times. After entering the number
3591 into the verification code field in the form, I could start using
3592 Signal from my laptop.
3594 <p
>As far as I can tell, The Signal app will leak who is talking to
3595 whom and thus who know who to those controlling the central server,
3596 but such leakage is hard to avoid with a centrally controlled server
3597 setup. It is something to keep in mind when using Signal - the
3598 content of your chats are harder to intercept, but the meta data
3599 exposing your contact network is available to people you do not know.
3600 So better than many options, but not great. And sadly the usage is
3601 connected to my land line, thus allowing those controlling the server
3602 to associate it to my home and person. I would prefer it if only
3603 those I knew could tell who I was on Signal. There are options
3604 avoiding such information leakage, but most of my friends are not
3605 using them, so I am stuck with Signal for now.
</p
>
3607 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
3609 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
3610 and updated recipe for using the Signal app without a mobile
3611 phone
</a
>.
</p
>
3616 <title>The new
"best
" multimedia player in Debian?
</title>
3617 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
3618 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
3619 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
3620 <description><p
>When I set out a few weeks ago to figure out
3621 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
3622 multimedia player in Debian claimed to support most file formats /
3623 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
3624 the various players claimed support for. The range was from
55 to
130
3625 MIME types. I suspect most media formats are supported by all
3626 players, but this is not really reflected in the MimeTypes values in
3627 their desktop files. There are probably also some bogus MIME types
3628 listed, but it is hard to identify which one this is.
</p
>
3630 <p
>Anyway, in the mean time I got in touch with upstream for some of
3631 the players suggesting to add more MIME types to their desktop files,
3632 and decided to spend some time myself improving the situation for my
3633 favorite media player VLC. The fixes for VLC entered Debian unstable
3634 yesterday. The complete list of MIME types can be seen on the
3635 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
3636 player MIME type support status
</a
> Debian wiki page.
</p
>
3638 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
3639 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
3640 kmplayer. I am sure some of the other players desktop files support
3641 several of the formats currently listed as working only with vlc,
3642 toten and parole.
</p
>
3644 <p
>A sad observation is that only
14 MIME types are listed as
3645 supported by all the tested multimedia players in Debian in their
3646 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
3647 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
3648 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
3649 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
3650 it sad that video/ogg and video/webm is not supported by all the media
3651 players in Debian. As far as I can tell, all of them can handle both
3657 <title>A program should be able to open its own files on Linux
</title>
3658 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
3659 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
3660 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
3661 <description><p
>Many years ago, when koffice was fresh and with few users, I
3662 decided to test its presentation tool when making the slides for a
3663 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
3664 wrote the first draft of the slides, saved the result and went to bed
3665 the day before I would give the talk. The next day I took a plane to
3666 the location where the meeting should take place, and on the plane I
3667 started up koffice again to polish the talk a bit, only to discover
3668 that kpresenter refused to load its own data file. I cursed a bit and
3669 started making the slides again from memory, to have something to
3670 present when I arrived. I tested that the saved files could be
3671 loaded, and the day seemed to be rescued. I continued to polish the
3672 slides until I suddenly discovered that the saved file could no longer
3673 be loaded into kpresenter. In the end I had to rewrite the slides
3674 three times, condensing the content until the talk became shorter and
3675 shorter. After the talk I was able to pinpoint the problem
&ndash;
3676 kpresenter wrote inline images in a way itself could not understand.
3677 Eventually that bug was fixed and kpresenter ended up being a great
3678 program to make slides. The point I
'm trying to make is that we
3679 expect a program to be able to load its own data files, and it is
3680 embarrassing to its developers if it can
't.
</p
>
3682 <p
>Did you ever experience a program failing to load its own data
3683 files from the desktop file browser? It is not a uncommon problem. A
3684 while back I discovered that the screencast recorder
3685 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
3686 browser would refuse to open. No video player claimed to understand
3687 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
3688 returning the application/ogg MIME type, which no video player I had
3689 installed listed as a MIME type they would understand. I asked for
3690 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
3691 behavour
</a
> and use the MIME type video/ogg instead. I also asked
3692 several video players to add video/ogg to their desktop files, to give
3693 the file browser an idea what to do about Ogg Theora files. After a
3694 while, the desktop file browsers in Debian started to handle the
3695 output from gtk-recordmydesktop properly.
</p
>
3697 <p
>But history repeats itself. A few days ago I tested the music
3698 system Rosegarden again, and I discovered that the KDE and xfce file
3699 browsers did not know what to do with the Rosegarden project files
3700 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
3701 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
3702 included in the next upload. To increase the chance of me remembering
3703 how to fix the problem next time some program fail to load its files
3704 from the file browser, here are some notes on how to fix it.
</p
>
3706 <p
>The file browsers in Debian in general operates on MIME types.
3707 There are two sources for the MIME type of a given file. The output from
3708 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
3709 shared MIME type registry (under /usr/share/mime/). The file MIME
3710 type is mapped to programs supporting the MIME type, and this
3711 information is collected from
3712 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
3713 desktop files
</a
> available in /usr/share/applications/. If there is
3714 one desktop file claiming support for the MIME type of the file, it is
3715 activated when asking to open a given file. If there are more, one
3716 can normally select which one to use by right-clicking on the file and
3717 selecting the wanted one using
'Open with
' or similar. In general
3718 this work well. But it depend on each program picking a good MIME
3720 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
3721 MIME type registered with IANA
</a
>), file and/or the shared MIME
3722 registry recognizing the file and the desktop file to list the MIME
3723 type in its list of supported MIME types.
</p
>
3725 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
3726 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
3727 Shared MIME database
</a
> look like this:
</p
>
3729 <p
><blockquote
><pre
>
3730 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
3731 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
3732 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
3733 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
3734 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
3735 &lt;glob pattern=
"*.rg
"/
&gt;
3736 &lt;/mime-type
&gt;
3737 &lt;/mime-info
&gt;
3738 </pre
></blockquote
></p
>
3740 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
3741 (it is a gzipped XML file). Note, it is much better to use an
3742 official MIME type registered with IANA than it is to make up ones own
3743 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
3745 <p
>The desktop file of the rosegarden program failed to list
3746 audio/x-rosegarden in its list of supported MIME types, causing the
3747 file browsers to have no idea what to do with *.rg files:
</p
>
3749 <p
><blockquote
><pre
>
3750 % grep Mime /usr/share/applications/rosegarden.desktop
3751 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
3752 X-KDE-NativeMimeType=audio/x-rosegarden-composition
3754 </pre
></blockquote
></p
>
3756 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
3757 MimeType= line.
</p
>
3759 <p
>If you run into a file which fail to open the correct program when
3760 selected from the file browser, please check out the output from
3761 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
3762 MIME type is registered somewhere under /usr/share/mime/ and check
3763 that some desktop file under /usr/share/applications/ is claiming
3764 support for this MIME type. If not, please report a bug to have it
3770 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
3771 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
3772 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
3773 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
3774 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
3775 system
</a
> is a user-focused solution in Debian for handling hardware
3776 related packages. The idea is to have a database of mappings between
3777 hardware and packages, and pop up a dialog suggesting for the user to
3778 install the packages to use a given hardware dongle. Some use cases
3779 are when you insert a Yubikey, it proposes to install the software
3780 needed to control it; when you insert a braille reader list it
3781 proposes to install the packages needed to send text to the reader;
3782 and when you insert a ColorHug screen calibrator it suggests to
3783 install the driver for it. The system work well, and even have a few
3784 command line tools to install firmware packages and packages for the
3785 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
3787 <p
>The system was initially written using aptdaemon, because I found
3788 good documentation and example code on how to use it. But aptdaemon
3789 is going away and is generally being replaced by
3790 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
3791 so Isenkram needed a rewrite. And today, thanks to the great patch
3792 from my college Sunil Mohan Adapa in the FreedomBox project, the
3793 rewrite finally took place. I
've just uploaded a new version of
3794 Isenkram into Debian Unstable with the patch included, and the default
3795 for the background daemon is now to use PackageKit. To check it out,
3796 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
3797 and see if it is recognised.
</p
>
3799 <p
>If you want to know what kind of packages isenkram would propose for
3800 the machine it is running on, you can check out the isenkram-lookup
3801 program. This is what it look like on a Thinkpad X230:
</p
>
3803 <p
><blockquote
><pre
>
3819 </pre
></blockquote
></p
>
3821 <p
>The hardware mappings come from several places. The preferred way
3822 is for packages to announce their hardware support using
3823 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
3824 cross distribution appstream system
</a
>.
3826 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
3827 blog posts about isenkram
</a
> to learn how to do that.
</p
>
3832 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
3833 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
3834 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
3835 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
3836 <description><p
>Yesterday I updated the
3837 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
3838 package in Debian
</a
> with a few patches sent to me by skilled and
3839 enterprising users. There were some nice user and visible changes.
3840 First of all, both desktop menu entries now work. A design flaw in
3841 one of the script made the history graph fail to show up (its PNG was
3842 dumped in ~/.xsession-errors) if no controlling TTY was available.
3843 The script worked when called from the command line, but not when
3844 called from the desktop menu. I changed this to look for a DISPLAY
3845 variable or a TTY before deciding where to draw the graph, and now the
3846 graph window pop up as expected.
</p
>
3848 <p
>The next new feature is a discharge rate estimator in one of the
3849 graphs (the one showing the last few hours). New is also the user of
3850 colours showing charging in blue and discharge in red. The percentages
3851 of this graph is relative to last full charge, not battery design
3854 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
3856 <p
>The other graph show the entire history of the collected battery
3857 statistics, comparing it to the design capacity of the battery to
3858 visualise how the battery life time get shorter over time. The red
3859 line in this graph is what the previous graph considers
100 percent:
3861 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
3863 <p
>In this graph you can see that I only charge the battery to
80
3864 percent of last full capacity, and how the capacity of the battery is
3865 shrinking. :(
</p
>
3867 <p
>The last new feature is in the collector, which now will handle
3868 more hardware models. On some hardware, Linux power supply
3869 information is stored in /sys/class/power_supply/ACAD/, while the
3870 collector previously only looked in /sys/class/power_supply/AC/. Now
3871 both are checked to figure if there is power connected to the
3874 <p
>If you are interested in how your laptop battery is doing, please
3876 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
3877 in Debian unstable, or rebuild it on Jessie to get it working on
3878 Debian stable. :) The upstream source is available from
<a
3879 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
3880 Patches are very welcome.
</p
>
3882 <p
>As usual, if you use Bitcoin and want to show your support of my
3883 activities, please send Bitcoin donations to my address
3884 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3889 <title>Debian now with ZFS on Linux included
</title>
3890 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
3891 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
3892 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
3893 <description><p
>Today, after many years of hard work from many people,
3894 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
3895 Debian. The package status can be seen on
3896 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
3897 for zfs-linux
</a
>. and
3898 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
3899 team status page
</a
>. If you want to help out, please join us.
3900 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
3901 source code
</a
> is available via git on Alioth. It would also be
3902 great if you could help out with
3903 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
3904 it is an important piece of the puzzle to get ZFS working.
</p
>
3909 <title>What is the best multimedia player in Debian?
</title>
3910 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
3911 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
3912 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
3913 <description><p
><strong
>Where I set out to figure out which multimedia player in
3914 Debian claim support for most file formats.
</strong
></p
>
3916 <p
>A few years ago, I had a look at the media support for Browser
3917 plugins in Debian, to get an idea which plugins to include in Debian
3918 Edu. I created a script to extract the set of supported MIME types
3919 for each plugin, and used this to find out which multimedia browser
3920 plugin supported most file formats / media types.
3921 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
3922 result
</a
> can still be seen on the Debian wiki, even though it have
3923 not been updated for a while. But browser plugins are less relevant
3924 these days, so I thought it was time to look at standalone
3927 <p
>A few days ago I was tired of VLC not being listed as a viable
3928 player when I wanted to play videos from the Norwegian National
3929 Broadcasting Company, and decided to investigate why. The cause is a
3930 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
3931 desktop file
</a
>. In the process I wrote a script to compare the set
3932 of MIME types announced in the desktop file and the browser plugin,
3933 only to discover that there is quite a large difference between the
3934 two for VLC. This discovery made me dig up the script I used to
3935 compare browser plugins, and adjust it to compare desktop files
3936 instead, to try to figure out which multimedia player in Debian
3937 support most file formats.
</p
>
3939 <p
>The result can be seen on the Debian Wiki, as
3940 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
3941 table listing all MIME types supported by one of the packages included
3942 in the table
</a
>, with the package supporting most MIME types being
3943 listed first in the table.
</p
>
3945 </p
>The best multimedia player in Debian? It is totem, followed by
3946 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
3947 kmplayer. Time for the other players to update their announced MIME
3953 <title>The Pyra - handheld computer with Debian preinstalled
</title>
3954 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
3955 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
3956 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
3957 <description>A friend of mine made me aware of
3958 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
3959 handheld computer which will be delivered with Debian preinstalled. I
3960 would love to get one of those for my birthday. :)
</p
>
3962 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
3963 plugs and many others connectors, and include a full keyboard and a
5"
3964 LCD touch screen. The
6000mAh battery is claimed to provide a whole
3965 day of battery life time, but I have not seen any independent tests
3966 confirming this. The vendor is still collecting preorders, and the
3967 last I heard last night was that
22 more orders were needed before
3968 production started.
</p
>
3970 <p
>As far as I know, this is the first handheld preinstalled with
3971 Debian. Please let me know if you know of any others. Is it the
3972 first computer being sold with Debian preinstalled?
</p
>
3977 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
3978 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
3979 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
3980 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
3981 <description><p
>During this weekends
3982 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
3983 squashing party and developer gathering
</a
>, we decided to do our part
3984 to make sure there are good books about Debian available in Norwegian
3985 Bokmål, and got in touch with the people behind the
3986 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
3987 project
</a
> to get started. If you want to help out, please start
3989 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
3990 hosted weblate project page
</a
>, and get in touch using
3991 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
3992 translators mailing list
</a
>. Please also check out
3993 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
3994 contributors
</a
>.
</p
>
3996 <p
>The book is already available on paper in English, French and
3997 Japanese, and our goal is to get it available on paper in Norwegian
3998 Bokmål too. In addition to the paper edition, there are also EPUB and
3999 Mobi versions available. And there are incomplete translations
4000 available for many more languages.
</p
>
4005 <title>One in two hundred Debian users using ZFS on Linux?
</title>
4006 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
4007 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
4008 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
4009 <description><p
>Just for fun I had a look at the popcon number of ZFS related
4010 packages in Debian, and was quite surprised with what I found. I use
4011 ZFS myself at home, but did not really expect many others to do so.
4012 But I might be wrong.
</p
>
4014 <p
>According to
4015 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
4016 results for spl-linux
</a
>, there are
1019 Debian installations, or
4017 0.53% of the population, with the package installed. As far as I know
4018 the only use of the spl-linux package is as a support library for ZFS
4019 on Linux, so I use it here as proxy for measuring the number of ZFS
4020 installation on Linux in Debian. In the kFreeBSD variant of Debian
4021 the ZFS feature is already available, and there
4022 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
4023 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
4024 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
4026 <p
>But even though the Debian project leader Lucas Nussbaum
4027 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
4028 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
4029 cleared, the package is still not in Debian. The package is again in
4030 the NEW queue. Several uploads have been rejected so far because the
4031 debian/copyright file was incomplete or wrong, but there is no reason
4032 to give up. The current status can be seen on
4033 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
4034 team status page
</a
>, and
4035 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
4036 source code
</a
> is available on Alioth.
</p
>
4038 <p
>As I want ZFS to be included in next version of Debian to make sure
4039 my home server can function in the future using only official Debian
4040 packages, and the current blocker is to get the debian/copyright file
4041 accepted by the FTP masters in Debian, I decided a while back to try
4042 to help out the team. This was the background for my blog post about
4043 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
4044 updating and checking debian/copyright semi-automatically
</a
>, and I
4045 used the techniques I explored there to try to find any errors in the
4046 copyright file. It is not very easy to check every one of the around
4047 2000 files in the source package, but I hope we this time got it
4048 right. If you want to help out, check out the git source and try to
4049 find missing entries in the debian/copyright file.
</p
>
4054 <title>Full battery stats collector is now available in Debian
</title>
4055 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
4056 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
4057 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
4058 <description><p
>Since this morning, the battery-stats package in Debian include an
4059 extended collector that will collect the complete battery history for
4060 later processing and graphing. The original collector store the
4061 battery level as percentage of last full level, while the new
4062 collector also record battery vendor, model, serial number, design
4063 full level, last full level and current battery level. This make it
4064 possible to predict the lifetime of the battery as well as visualise
4065 the energy flow when the battery is charging or discharging.
</p
>
4067 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
4068 in the version
0.5.1 package in unstable. Get the new battery level graph
4069 and lifetime prediction by running:
4071 <p
><pre
>
4072 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4073 </pre
></p
>
4075 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
4077 <p
>The flow in/out of the battery can be seen by running (no menu
4078 entry yet):
</p
>
4080 <p
><pre
>
4081 /usr/share/battery-stats/battery-stats-graph-flow
4082 </pre
></p
>
4084 <p
>I
'm not quite happy with the way the data is visualised, at least
4085 when there are few data points. The graphs look a bit better with a
4086 few years of data.
</p
>
4088 <p
>A while back one important feature I use in the battery stats
4089 collector broke in Debian. The scripts in
4090 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
4091 suspect it happened when Jessie started using systemd, but I do not
4092 know. The issue is reported as
4093 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
4094 pm-utils. I managed to work around it by adding an udev rule to call
4095 the collector script every time the power connector is connected and
4096 disconnected. With this fix in place it was finally time to make a
4097 new release of the package, and get it into Debian.
</p
>
4099 <p
>If you are interested in how your laptop battery is doing, please
4101 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
4102 in Debian unstable, or rebuild it on Jessie to get it working on
4103 Debian stable. :) The upstream source is available from
4104 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4105 As always, patches are very welcome.
</p
>
4110 <title>Making battery measurements a little easier in Debian
</title>
4111 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
4112 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
4113 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
4114 <description><p
>Back in September, I blogged about
4115 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
4116 system I wrote to collect statistics about my laptop battery
</a
>, and
4117 how it showed the decay and death of this battery (now replaced). I
4118 created a simple deb package to handle the collection and graphing,
4119 but did not want to upload it to Debian as there were already
4120 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
4121 package in Debian
</a
> that should do the same thing, and I did not see
4122 a point of uploading a competing package when battery-stats could be
4123 fixed instead. I reported a few bugs about its non-function, and
4124 hoped someone would step in and fix it. But no-one did.
</p
>
4126 <p
>I got tired of waiting a few days ago, and took matters in my own
4127 hands. The end result is that I am now the new upstream developer of
4128 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
4129 battery-stats in Debian, and the package in Debian unstable is finally
4130 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
4131 information provided by the Linux kernel. If you install the
4132 battery-stats package from unstable now, you will be able to get a
4133 graph of the current battery fill level, to get some idea about the
4134 status of the battery. The source package build and work just fine in
4135 Debian testing and stable (and probably oldstable too, but I have not
4136 tested). The default graph you get for that system look like this:
</p
>
4138 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
03-
15-battery-stats-graph-example.png
" width=
"70%
" align=
"center
"></p
>
4140 <p
>My plans for the future is to merge my old scripts into the
4141 battery-stats package, as my old scripts collected a lot more details
4142 about the battery. The scripts are merged into the upstream
4143 battery-stats git repository already, but I am not convinced they work
4144 yet, as I changed a lot of paths along the way. Will have to test a
4145 bit more before I make a new release.
</p
>
4147 <p
>I will also consider changing the file format slightly, as I
4148 suspect the way I combine several values into one field might make it
4149 impossible to know the type of the value when using it for processing
4150 and graphing.
</p
>
4152 <p
>If you would like I would like to keep an close eye on your laptop
4153 battery, check out the battery-stats package in
4154 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
4156 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4157 I would love some help to improve the system further.
</p
>
4162 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
4163 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
4164 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
4165 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
4166 <description><p
>Making packages for Debian requires quite a lot of attention to
4167 details. And one of the details is the content of the
4168 debian/copyright file, which should list all relevant licenses used by
4169 the code in the package in question, preferably in
4170 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
4171 readable DEP5 format
</a
>.
</p
>
4173 <p
>For large packages with lots of contributors it is hard to write
4174 and update this file manually, and if you get some detail wrong, the
4175 package is normally rejected by the ftpmasters. So getting it right
4176 the first time around get the package into Debian faster, and save
4177 both you and the ftpmasters some work.. Today, while trying to figure
4178 out what was wrong with
4179 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
4180 zfsonlinux copyright file
</a
>, I decided to spend some time on
4181 figuring out the options for doing this job automatically, or at least
4182 semi-automatically.
</p
>
4184 <p
>Lucikly, there are at least two tools available for generating the
4185 file based on the code in the source package,
4186 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
4187 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
4188 not sure which one of them came first, but both seem to be able to
4189 create a sensible draft file. As far as I can tell, none of them can
4190 be trusted to get the result just right, so the content need to be
4191 polished a bit before the file is OK to upload. I found the debmake
4193 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
4194 blog posts from
2014</a
>.
4196 <p
>To generate using debmake, use the -cc option:
4198 <p
><pre
>
4199 debmake -cc
> debian/copyright
4200 </pre
></p
>
4202 <p
>Note there are some problems with python and non-ASCII names, so
4203 this might not be the best option.
</p
>
4205 <p
>The cme option is based on a config parsing library, and I found
4207 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
4208 blog post from
2015</a
>. To generate using cme, use the
'update
4209 dpkg-copyright
' option:
4211 <p
><pre
>
4212 cme update dpkg-copyright
4213 </pre
></p
>
4215 <p
>This will create or update debian/copyright. The cme tool seem to
4216 handle UTF-
8 names better than debmake.
</p
>
4218 <p
>When the copyright file is created, I would also like some help to
4219 check if the file is correct. For this I found two good options,
4220 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
4221 to focus on license types and file matching, and is able to detect
4222 ineffective blocks in the copyright file. The latter reports missing
4223 copyright holders and years, but was confused by inconsistent license
4224 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
4225 fix all issues reported by them before uploading. But I do not know
4226 if the tools and the ftpmasters agree on what is important to fix in a
4227 copyright file, so the package might still be rejected.
</p
>
4229 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
4230 will read through the source and try to find all copyright statements.
4231 It is not comparing the result to the content of debian/copyright, but
4232 can be useful when verifying the content of the copyright file.
</p
>
4234 <p
>Are you aware of better tools in Debian to create and update
4235 debian/copyright file. Please let me know, or blog about it on
4236 planet.debian.org.
</p
>
4238 <p
>As usual, if you use Bitcoin and want to show your support of my
4239 activities, please send Bitcoin donations to my address
4240 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4242 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
4243 on how to use licensecheck and cdbs to create a draft copyright file
4245 <p
><pre
>
4246 licensecheck --copyright -r `find * -type f` | \
4247 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
4248 </pre
></p
>
4250 <p
>He mentioned that he normally check the generated file into the
4251 version control system to make it easier to discover license and
4252 copyright changes in the upstream source. I will try to do the same
4253 with my packages in the future.
</p
>
4255 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
4256 against using -quiet for new users, so I removed it from the proposed
4257 command line.
</p
>
4262 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
4263 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
4264 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
4265 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
4266 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
4267 is taking shape in Debian, and one provided feature is a very
4268 convenient way to tell you which package to install to make a given
4269 firmware file available when the kernel is looking for it. This can
4270 be done using apt-file too, but that is for someone else to blog
4273 <p
>Here is a small recipe to find the package with a given firmware
4274 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
4275 picked from the set of firmware announced using appstream in Debian
4276 unstable. In general you would be looking for the firmware requested
4277 by the kernel during kernel module loading. To find the package
4278 providing the example file, do like this:
</p
>
4280 <blockquote
><pre
>
4281 % apt install appstream
4285 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
4286 awk
'/Package:/ {print $
2}
'
4289 </pre
></blockquote
>
4291 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
4292 appstream wiki
</a
> page to learn how to embed the package metadata in
4293 a way appstream can use.
</p
>
4295 <p
>This same approach can be used to find any package supporting a
4296 given MIME type. This is very useful when you get a file you do not
4297 know how to handle. First find the mime type using
<tt
>file
4298 --mime-type
</tt
>, and next look up the package providing support for
4299 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
4300 and you can find all packages handling this type like this:
</p
>
4302 <blockquote
><pre
>
4303 % apt install appstream
4307 % appstreamcli what-provides mimetype image/svg+xml | \
4308 awk
'/Package:/ {print $
2}
'
4330 </pre
></blockquote
>
4332 <p
>I believe the MIME types are fetched from the desktop file for
4333 packages providing appstream metadata.
</p
>
4338 <title>Creepy, visualise geotagged social media information - nice free software
</title>
4339 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
4340 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
4341 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
4342 <description><p
>Most people seem not to realise that every time they walk around
4343 with the computerised radio beacon known as a mobile phone their
4344 position is tracked by the phone company and often stored for a long
4345 time (like every time a SMS is received or sent). And if their
4346 computerised radio beacon is capable of running programs (often called
4347 mobile apps) downloaded from the Internet, these programs are often
4348 also capable of tracking their location (if the app requested access
4349 during installation). And when these programs send out information to
4350 central collection points, the location is often included, unless
4351 extra care is taken to not send the location. The provided
4352 information is used by several entities, for good and bad (what is
4353 good and bad, depend on your point of view). What is certain, is that
4354 the private sphere and the right to free movement is challenged and
4355 perhaps even eradicated for those announcing their location this way,
4356 when they share their whereabouts with private and public
4359 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
4361 <p
>The phone company logs provide a register of locations to check out
4362 when one want to figure out what the tracked person was doing. It is
4363 unavailable for most of us, but provided to selected government
4364 officials, company staff, those illegally buying information from
4365 unfaithful servants and crackers stealing the information. But the
4366 public information can be collected and analysed, and a free software
4367 tool to do so is called
4368 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
4369 discovered it when I read
4370 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
4371 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
4372 November
2014, and decided to check if it was available in Debian.
4373 The python program was in Debian, but
4374 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
4375 Debian
</a
> was completely broken and practically unmaintained. I
4376 uploaded a new version which did not work quite right, but did not
4377 have time to fix it then. This Christmas I decided to finally try to
4378 get Creepy operational in Debian. Now a fixed version is available in
4379 Debian unstable and testing, and almost all Debian specific patches
4381 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
4383 <p
>The Creepy program visualises geolocation information fetched from
4384 Twitter, Instagram, Flickr and Google+, and allow one to get a
4385 complete picture of every social media message posted recently in a
4386 given area, or track the movement of a given individual across all
4387 these services. Earlier it was possible to use the search API of at
4388 least some of these services without identifying oneself, but these
4389 days it is impossible. This mean that to use Creepy, you need to
4390 configure it to log in as yourself on these services, and provide
4391 information to them about your search interests. This should be taken
4392 into account when using Creepy, as it will also share information
4393 about yourself with the services.
</p
>
4395 <p
>The picture above show the twitter messages sent from (or at least
4396 geotagged with a position from) the city centre of Oslo, the capital
4397 of Norway. One useful way to use Creepy is to first look at
4398 information tagged with an area of interest, and next look at all the
4399 information provided by one or more individuals who was in the area.
4400 I tested it by checking out which celebrity provide their location in
4401 twitter messages by checkout out who sent twitter messages near a
4402 Norwegian TV station, and next could track their position over time,
4403 making it possible to locate their home and work place, among other
4404 things. A similar technique have been
4405 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
4406 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
4407 tool to discover lying governments, and a useful tool to help people
4408 understand the value of the private information they provide to the
4411 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
4412 it depend on several python modules currently missing in Jessie (at
4413 least python-instagram, python-flickrapi and
4414 python-requests-toolbelt).
</p
>
4416 <p
>(I have uploaded
4417 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
4418 screenshots.debian.net
</a
> and licensed it under the same terms as the
4419 Creepy program in Debian.)
</p
>
4424 <title>Always download Debian packages using Tor - the simple recipe
</title>
4425 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
4426 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
4427 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
4428 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
4429 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
4430 that those listening on the Internet lines would have good reason to
4431 believe a computer have a given security hole
</a
> if it download a
4432 security fix from a Debian mirror. This is a good reason to always
4433 use encrypted connections to the Debian mirror, to make sure those
4434 listening do not know which IP address to attack. In August, Richard
4435 Hartmann observed that encryption was not enough, when it was possible
4436 to interfere download size to security patches or the fact that
4437 download took place shortly after a security fix was released, and
4438 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
4439 to always use Tor to download packages from the Debian mirror
</a
>. He
4440 was not the first to propose this, as the
4441 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
4442 package by Tim Retout already existed to make it easy to convince apt
4443 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
4444 aware of that package when I read the blog post from Richard.
</p
>
4446 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
4447 sysadmins, and he set up a Tor hidden service on one of the central
4448 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
4449 it possible to download packages directly between two tor nodes,
4450 making sure the network traffic always were encrypted.
</p
>
4452 <p
>Here is a short recipe for enabling this on your machine, by
4453 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
4454 urls with tor+http and tor+https, and using the hidden service instead
4455 of the official Debian mirror site. I recommend installing
4456 <tt
>etckeeper
</tt
> before you start to have a history of the changes
4457 done in /etc/.
</p
>
4459 <blockquote
><pre
>
4460 apt install apt-transport-tor
4461 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
4462 sed -i
's% http% tor+http%
' /etc/apt/sources.list
4463 </pre
></blockquote
>
4465 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
4466 the sed commands for these too. The sed command is assuming your are
4467 using the ftp.debian.org Debian mirror. Adjust the command (or just
4468 edit the file manually) to match your mirror.
</p
>
4470 <p
>This work in Debian Jessie and later. Note that tools like
4471 <tt
>apt-file
</tt
> only recently started using the apt transport
4472 system, and do not work with these tor+http URLs. For
4473 <tt
>apt-file
</tt
> you need the version currently in experimental,
4474 which need a recent apt version currently only in unstable. So if you
4475 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
4477 <p
>Another advantage from this change is that your machine will start
4478 using Tor regularly and at fairly random intervals (every time you
4479 update the package lists or upgrade or install a new package), thus
4480 masking other Tor traffic done from the same machine. Using Tor will
4481 become normal for the machine in question.
</p
>
4483 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
4484 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
4485 enabled. It would be great if it was the default on any Debian
4491 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
4492 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
4493 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
4494 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
4495 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
4496 call the car license plate numbers in those days. I would write the
4497 numbers down in my little book and compare notes with the other kids
4498 to see how many region codes we had seen and if we had seen some
4499 exotic or special region codes and numbers. It was a fun game to pass
4500 time, as we kids have plenty of it.
</p
>
4502 <p
>A few days I came across
4503 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
4504 project
</a
>, a free software project to automatically discover and
4505 report license plates in images and video streams, and provide the
4506 "car numbers
" in a machine readable format. I
've been looking for
4507 such system for a while now, because I believe it is a bad idea that the
4508 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
4509 number plate recognition
</a
> tool only is available in the hands of
4510 the powerful, and want it to be available also for the powerless to
4511 even the score when it comes to surveillance and sousveillance. I
4512 discovered the developer
4513 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
4514 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
4515 help him get it into shape to get the package uploaded into the Debian
4518 <p
>Today we finally managed to get the package into shape and uploaded
4519 it into Debian, where it currently
4520 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
4521 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
4523 <p
>I guess you are wondering why on earth such tool would be useful
4524 for the common folks, ie those not running a large government
4525 surveillance system? Well, I plan to put it in a computer on my bike
4526 and in my car, tracking the cars nearby and allowing me to be notified
4527 when number plates on my watch list are discovered. Another use case
4528 was suggested by a friend of mine, who wanted to set it up at his home
4529 to open the car port automatically when it discovered the plate on his
4530 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
4531 capable of placing his license plate number of a piece of cardboard to
4532 open his car port, men replied that it was always unlocked anyway. I
4533 guess for such use case it make sense. I am sure there are other use
4534 cases too, for those with imagination and a vision.
</p
>
4536 <p
>If you want to build your own version of the Debian package, check
4537 out the upstream git source and symlink ./distros/debian to ./debian/
4538 before running
"debuild
" to build the source. Or wait a bit until the
4539 package show up in unstable.
</p
>
4544 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
4545 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
4546 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
4547 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
4548 <description><p
>Around three years ago, I created
4549 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
4550 system
</a
> to get a more practical solution in Debian for handing
4551 hardware related packages. A GUI system in the isenkram package will
4552 present a pop-up dialog when some hardware dongle supported by
4553 relevant packages in Debian is inserted into the machine. The same
4554 lookup mechanism to detect packages is available as command line
4555 tools in the isenkram-cli package. In addition to mapping hardware,
4556 it will also map kernel firmware files to packages and make it easy to
4557 install needed firmware packages automatically. The key for this
4558 system to work is a good way to map hardware to packages, in other
4559 words, allow packages to announce what hardware they will work
4562 <p
>I started by providing data files in the isenkram source, and
4563 adding code to download the latest version of these data files at run
4564 time, to ensure every user had the most up to date mapping available.
4565 I also added support for storing the mapping in the Packages file in
4566 the apt repositories, but did not push this approach because while I
4567 was trying to figure out how to best store hardware/package mappings,
4568 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
4569 appstream system
</a
> was announced. I got in touch and suggested to
4570 add the hardware mapping into that data set to be able to use
4571 appstream as a data source, and this was accepted at least for the
4572 Debian version of appstream.
</p
>
4574 <p
>A few days ago using appstream in Debian for this became possible,
4575 and today I uploaded a new version
0.20 of isenkram adding support for
4576 appstream as a data source for mapping hardware to packages. The only
4577 package so far using appstream to announce its hardware support is my
4578 pymissile package. I got help from Matthias Klumpp with figuring out
4579 how do add the required
4580 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
4581 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
4582 this content:
</p
>
4584 <blockquote
><pre
>
4585 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
4586 &lt;component
&gt;
4587 &lt;id
&gt;pymissile
&lt;/id
&gt;
4588 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
4589 &lt;name
&gt;pymissile
&lt;/name
&gt;
4590 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
4591 &lt;description
&gt;
4593 Pymissile provides a curses interface to control an original
4594 Marks and Spencer / Striker USB Missile Launcher, as well as a
4595 motion control script to allow a webcamera to control the
4598 &lt;/description
&gt;
4599 &lt;provides
&gt;
4600 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
4601 &lt;/provides
&gt;
4602 &lt;/component
&gt;
4603 </pre
></blockquote
>
4605 <p
>The key for isenkram is the component/provides/modalias value,
4606 which is a glob style match rule for hardware specific strings
4607 (modalias strings) provided by the Linux kernel. In this case, it
4608 will map to all USB devices with vendor code
1130 and product code
4611 <p
>Note, it is important that the license of all the metadata files
4612 are compatible to have permissions to aggregate them into archive wide
4613 appstream files. Matthias suggested to use MIT or BSD licenses for
4614 these files. A challenge is figuring out a good id for the data, as
4615 it is supposed to be globally unique and shared across distributions
4616 (in other words, best to coordinate with upstream what to use). But
4617 it can be changed later or, so we went with the package name as
4618 upstream for this project is dormant.
</p
>
4620 <p
>To get the metadata file installed in the correct location for the
4621 mirror update scripts to pick it up and include its content the
4622 appstream data source, the file must be installed in the binary
4623 package under /usr/share/appdata/. I did this by adding the following
4624 line to debian/pymissile.install:
</p
>
4626 <blockquote
><pre
>
4627 debian/pymissile.metainfo.xml usr/share/appdata
4628 </pre
></blockquote
>
4630 <p
>With that in place, the command line tool isenkram-lookup will list
4631 all packages useful on the current computer automatically, and the GUI
4632 pop-up handler will propose to install the package not already
4633 installed if a hardware dongle is inserted into the machine in
4636 <p
>Details of the modalias field in appstream is available from the
4637 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
4639 <p
>To locate the modalias values of all hardware present in a machine,
4640 try running this command on the command line:
</p
>
4642 <blockquote
><pre
>
4643 cat $(find /sys/devices/|grep modalias)
4644 </pre
></blockquote
>
4646 <p
>To learn more about the isenkram system, please check out
4647 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
4648 blog posts tagged isenkram
</a
>.
</p
>
4653 <title>The GNU General Public License is not magic pixie dust
</title>
4654 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
4655 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
4656 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
4657 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
4658 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
4659 GPL is not magic pixie dust
</a
>" explain the importance of making sure
4660 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
4661 I quote the blog post from Paul in full here with his permission:
<p
>
4665 <p
><a href=
"https://sfconservancy.org/supporter/
"><img src=
"https://sfconservancy.org/img/supporter-badge.png
" width=
"194" height=
"90" alt=
"Become a Software Freedom Conservancy Supporter!
" align=
"right
" border=
"0" /
></a
></p
>
4668 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
4670 The first step is to choose a
4671 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
4674 The next step is, when someone fails to follow that copyleft license,
4675 <b
>it must be enforced
</b
><br/
>
4677 and its a simple fact of our modern society that such type of
4680 is incredibly expensive to do and incredibly difficult to do.
4683 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
4684 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
4685 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
4686 0x57</a
></small
></p
>
4688 <p
>As the Debian Website
4689 <a href=
"https://bugs.debian.org/
794116">used
</a
>
4690 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
4691 imply, public domain and permissively licensed software can lead to
4692 the production of more proprietary software as people discover useful
4693 software, extend it and or incorporate it into their hardware or
4694 software products. Copyleft licenses such as the GNU GPL were created
4695 to close off this avenue to the production of proprietary software but
4696 such licenses are not enough. With the ongoing adoption of Free
4697 Software by individuals and groups, inevitably the community
's
4698 expectations of license compliance are violated, usually out of
4699 ignorance of the way Free Software works, but not always. As Karen
4700 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
4701 Freedom
">FaiF
</a
>
4702 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
4703 copyleft is nothing if no-one is willing and able to stand up in court
4704 to protect it. The reality of today
's world is that legal
4705 representation is expensive, difficult and time consuming. With
4706 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
4707 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
4708 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
4709 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
4710 of the Linux project, Debian and other groups against GPL violations.
4711 In March the SFC supported a
4712 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
4713 by Christoph Hellwig
</a
> against VMware for refusing to
4714 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
4715 with the GPL
</a
> in relation to their use of parts of the Linux
4716 kernel. Since then two of their sponsors pulled corporate funding and
4718 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
4719 or cancelled their talks
</a
>. As a result they have decided to rely
4720 less on corporate funding and more on the broad community of
4721 individuals who support Free Software and copyleft. So the SFC has
4722 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
4723 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
4724 a community of folks who stand up for copyleft and the GPL by
4725 supporting their work on promoting and supporting copyleft and Free
4728 <p
>If you support Free Software,
4729 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
4730 what the SFC do, agree with their
4731 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
4732 principles
</a
>, are happy about their
4733 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
4734 work on a project that is an SFC
4735 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
4736 just want to stand up for copyleft, please join
4737 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
4738 Allan Webber
</a
>,
4739 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
4741 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
4742 Bacon
</a
>, myself and
4743 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
4745 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
4746 next week your donation will be
4747 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
4748 by an anonymous donor. Please also consider asking your employer to
4749 match your donation or become a sponsor of SFC. Don
't forget to
4750 spread the word about your support for SFC via email, your blog and or
4751 social media accounts.
</p
>
4755 <p
>I agree with Paul on this topic and just signed up as a Supporter
4756 of Software Freedom Conservancy myself. Perhaps you should be a
4757 supporter too?
</p
>
4762 <title>PGP key transition statement for key EE4E02F9
</title>
4763 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
4764 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
4765 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
4766 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
4767 set it up properly. I wanted to generate it offline and have it
4768 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
4769 smart card
</a
> for daily use, and learning how to do it and finding
4770 time to sit down with an offline machine almost took forever. But
4771 finally I
've been able to complete the process, and have now moved
4772 from my old GPG key to a new GPG key. See
4773 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
4774 full transition statement, signed with both my old and new key
</a
> for
4775 the details. This is my new key:
</p
>
4778 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
4779 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
4780 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
4781 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
4782 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
4783 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
4784 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
4787 <p
>The key can be downloaded from the OpenPGP key servers, signed by
4788 my old key.
</p
>
4790 <p
>If you signed my old key
4791 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
4792 I
'd very much appreciate a signature on my new key, details and
4793 instructions in the transition statement. I m happy to reciprocate if
4794 you have a similarly signed transition statement to present.
</p
>
4799 <title>The life and death of a laptop battery
</title>
4800 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
4801 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
4802 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
4803 <description><p
>When I get a new laptop, the battery life time at the start is OK.
4804 But this do not last. The last few laptops gave me a feeling that
4805 within a year, the life time is just a fraction of what it used to be,
4806 and it slowly become painful to use the laptop without power connected
4807 all the time. Because of this, when I got a new Thinkpad X230 laptop
4808 about two years ago, I decided to monitor its battery state to have
4809 more hard facts when the battery started to fail.
</p
>
4811 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
4813 <p
>First I tried to find a sensible Debian package to record the
4814 battery status, assuming that this must be a problem already handled
4815 by someone else. I found
4816 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
4817 which collects statistics from the battery, but it was completely
4818 broken. I sent a few suggestions to the maintainer, but decided to
4819 write my own collector as a shell script while I waited for feedback
4821 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
4822 blog post about the battery development on a MacBook Air
</a
> I also
4824 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
4825 available in Debian.
</p
>
4827 <p
>I started my collector
2013-
07-
15, and it has been collecting
4828 battery stats ever since. Now my
4829 /var/log/hjemmenett-battery-status.log file contain around
115,
000
4830 measurements, from the time the battery was working great until now,
4831 when it is unable to charge above
7% of original capacity. My
4832 collector shell script is quite simple and look like this:
</p
>
4837 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
4839 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
4840 logfile=/var/log/hjemmenett-battery-status.log
4842 files=
"manufacturer model_name technology serial_number \
4843 energy_full energy_full_design energy_now cycle_count status
"
4845 if [ ! -e
"$logfile
" ] ; then
4847 printf
"timestamp,
"
4849 printf
"%s,
" $f
4852 )
> "$logfile
"
4856 # Print complete message in one echo call, to avoid race condition
4857 # when several log processes run in parallel.
4858 msg=$(printf
"%s,
" $(date +%s); \
4859 for f in $files; do \
4860 printf
"%s,
" $(cat $f); \
4862 echo
"$msg
"
4865 cd /sys/class/power_supply
4868 (cd $bat
&& log_battery
>> "$logfile
")
4872 <p
>The script is called when the power management system detect a
4873 change in the power status (power plug in or out), and when going into
4874 and out of hibernation and suspend. In addition, it collect a value
4875 every
10 minutes. This make it possible for me know when the battery
4876 is discharging, charging and how the maximum charge change over time.
4877 The code for the Debian package
4878 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
4879 available on github
</a
>.
</p
>
4881 <p
>The collected log file look like this:
</p
>
4884 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
4885 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
4887 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
4888 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
4891 <p
>I wrote a small script to create a graph of the charge development
4892 over time. This graph depicted above show the slow death of my laptop
4895 <p
>But why is this happening? Why are my laptop batteries always
4896 dying in a year or two, while the batteries of space probes and
4897 satellites keep working year after year. If we are to believe
4898 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
4899 University
</a
>, the cause is me charging the battery whenever I have a
4900 chance, and the fix is to not charge the Lithium-ion batteries to
100%
4901 all the time, but to stay below
90% of full charge most of the time.
4902 I
've been told that the Tesla electric cars
4903 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
4904 the charge of their batteries to
80%
</a
>, with the option to charge to
4905 100% when preparing for a longer trip (not that I would want a car
4906 like Tesla where rights to privacy is abandoned, but that is another
4907 story), which I guess is the option we should have for laptops on
4908 Linux too.
</p
>
4910 <p
>Is there a good and generic way with Linux to tell the battery to
4911 stop charging at
80%, unless requested to charge to
100% once in
4912 preparation for a longer trip? I found
4913 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
4914 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
4915 80%
</a
>, but could not get it to work (kernel module refused to
4918 <p
>I wonder why the battery capacity was reported to be more than
100%
4919 at the start. I also wonder why the
"full capacity
" increases some
4920 times, and if it is possible to repeat the process to get the battery
4921 back to design capacity. And I wonder if the discharge and charge
4922 speed change over time, or if this stay the same. I did not yet try
4923 to write a tool to calculate the derivative values of the battery
4924 level, but suspect some interesting insights might be learned from
4927 <p
>Update
2015-
09-
24: I got a tip to install the packages
4928 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
4929 packages instead of the tp-smapi-dkms package I had tried to use
4930 initially, and use
'tlp setcharge
40 80' to change when charging start
4931 and stop. I
've done so now, but expect my existing battery is toast
4932 and need to be replaced. The proposal is unfortunately Thinkpad
4938 <title>New laptop - some more clues and ideas based on feedback
</title>
4939 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
4940 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
4941 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
4942 <description><p
>Several people contacted me after my previous blog post about my
4943 need for a new laptop, and provided very useful feedback. I wish to
4944 thank every one of these. Several pointed me to the possibility of
4945 fixing my X230, and I am already in the process of getting Lenovo to
4946 do so thanks to the on site, next day support contract covering the
4947 machine. But the battery is almost useless (I expect to replace it
4948 with a non-official battery) and I do not expect the machine to live
4949 for many more years, so it is time to plan its replacement. If I did
4950 not have a support contract, it was suggested to find replacement parts
4951 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
4952 might present a language barrier as I do not understand French.
</p
>
4954 <p
>One tip I got was to use the
4955 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
4956 compare laptop models. It seem to have more models available than
4957 prisjakt.no. Another tip I got from someone I know have similar
4958 keyboard preferences was that the HP EliteBook
840 keyboard is not
4959 very good, and this matches my experience with earlier EliteBook
4960 keyboards I tested. Because of this, I will not consider it any further.
4962 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
4963 newest Thinkpad X model. The keyboard reintroduces mouse buttons
4964 (which is missing from the X240), and is working fairly well with
4965 Debian Sid/Unstable according to
4966 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
4967 got on the keyboard quality are not consistent. Some say the keyboard
4968 is good, others say it is ok, while others say it is not very good.
4969 Those with experience from X41 and and X60 agree that the X250
4970 keyboard is not as good as those trusty old laptops, and suggest I
4971 keep and fix my X230 instead of upgrading, or get a used X230 to
4972 replace it. I
'm also told that the X250 lack leds for caps lock, disk
4973 activity and battery status, which is very convenient on my X230. I
'm
4974 also told that the CPU fan is running very often, making it a bit
4975 noisy. In any case, the X250 do not work out of the box with Debian
4976 Stable/Jessie, one of my requirements.
</p
>
4978 <p
>I have also gotten a few vendor proposals, one was
4979 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
4980 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
4981 The latter look very attractive to me.
</p
>
4983 <p
>Again, thank you all for the very useful feedback. It help a lot
4984 as I keep looking for a replacement.
</p
>
4986 <p
>Update
2015-
07-
06: I was recommended to check out the
4987 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
4989 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
4990 thinkpad X models
</a
>, and provide one year warranty.
</p
>
4995 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
4996 <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>
4997 <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>
4998 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
4999 <description><p
>My primary work horse laptop is failing, and will need a
5000 replacement soon. The left
5 cm of the screen on my Thinkpad X230
5001 started flickering yesterday, and I suspect the cause is a broken
5002 cable, as changing the angle of the screen some times get rid of the
5003 flickering.
</p
>
5005 <p
>My requirements have not really changed since I bought it, and is
5007 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
5008 described them in
2013</a
>. The last time I bought a laptop, I had
5010 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
5011 where I could select at least a few of the requirements (mouse pin,
5012 wifi, weight) and go through the rest manually. Three button mouse
5013 and a good keyboard is not available as an option, and all the three
5014 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
5015 G2) lack three mouse buttons). It is also unclear to me how good the
5016 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5017 the keyboard, even if the quality and robustness in the X series have
5018 deteriorated since X41.
</p
>
5020 <p
>I wonder how I can find a sensible laptop when none of the options
5021 seem sensible to me? Are there better services around to search the
5022 set of available laptops for features? Please send me an email if you
5023 have suggestions.
</p
>
5025 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
5026 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
5027 of endorsed hardware
</a
>, which is useful background information.
</p
>
5032 <title>How to stay with sysvinit in Debian Jessie
</title>
5033 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
5034 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
5035 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
5036 <description><p
>By now, it is well known that Debian Jessie will not be using
5037 sysvinit as its boot system by default. But how can one keep using
5038 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5040 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
5041 Schubert
</a
> and
5042 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
5045 <p
>If you already are using Wheezy and want to upgrade to Jessie and
5046 keep sysvinit as your boot system, create a file
5047 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
5048 you upgrade:
</p
>
5050 <p
><blockquote
><pre
>
5051 Package: systemd-sysv
5052 Pin: release o=Debian
5054 </pre
></blockquote
><p
>
5056 <p
>This file content will tell apt and aptitude to not consider
5057 installing systemd-sysv as part of any installation and upgrade
5058 solution when resolving dependencies, and thus tell it to avoid
5059 systemd as a default boot system. The end result should be that the
5060 upgraded system keep using sysvinit.
</p
>
5062 <p
>If you are installing Jessie for the first time, there is no way to
5063 get sysvinit installed by default (debootstrap used by
5064 debian-installer have no option for this), but one can tell the
5065 installer to switch to sysvinit before the first boot. Either by
5066 using a kernel argument to the installer, or by adding a line to the
5067 preseed file used. First, the kernel command line argument:
5069 <p
><blockquote
><pre
>
5070 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
5071 </pre
></blockquote
><p
>
5073 <p
>Next, the line to use in a preseed file:
</p
>
5075 <p
><blockquote
><pre
>
5076 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5077 </pre
></blockquote
><p
>
5079 <p
>One can of course also do this after the first boot by installing
5080 the sysvinit-core package.
</p
>
5082 <p
>I recommend only using sysvinit if you really need it, as the
5083 sysvinit boot sequence in Debian have several hardware specific bugs
5084 on Linux caused by the fact that it is unpredictable when hardware
5085 devices show up during boot. But on the other hand, the new default
5086 boot system still have a few rough edges I hope will be fixed before
5087 Jessie is released.
</p
>
5089 <p
>Update
2014-
11-
26: Inspired by
5090 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
5091 blog post by Torsten Glaser
</a
>, added --purge to the preseed
5097 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
5098 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
5099 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
5100 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
5101 <description><p
>The right to communicate with your friends and family in private,
5102 without anyone snooping, is a right every citicen have in a liberal
5103 democracy. But this right is under serious attack these days.
</p
>
5105 <p
>A while back it occurred to me that one way to make the dragnet
5106 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5107 the whisleblower Snowden) more expensive for Internet email,
5108 is to deliver all email using SMTP via Tor. Such SMTP option would be
5109 a nice addition to the FreedomBox project if we could send email
5110 between FreedomBox machines without leaking metadata about the emails
5111 to the people peeking on the wire. I
5112 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
5113 this on the FreedomBox project mailing list in October
</a
> and got a
5114 lot of useful feedback and suggestions. It also became obvious to me
5115 that this was not a novel idea, as the same idea was tested and
5116 documented by Johannes Berg as early as
2006, and both
5117 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
5118 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
5119 propose a similar method / protocol to pass emails between users.
</p
>
5121 <p
>To implement such system one need to set up a Tor hidden service
5122 providing the SMTP protocol on port
25, and use email addresses
5123 looking like username@hidden-service-name.onion. With such addresses
5124 the connections to port
25 on hidden-service-name.onion using Tor will
5125 go to the correct SMTP server. To do this, one need to configure the
5126 Tor daemon to provide the hidden service and the mail server to accept
5127 emails for this .onion domain. To learn more about Exim configuration
5128 in Debian and test the design provided by Johannes Berg in his FAQ, I
5129 set out yesterday to create a Debian package for making it trivial to
5130 set up such SMTP over Tor service based on Debian. Getting it to work
5131 were fairly easy, and
5132 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
5133 source code for the Debian package
</a
> is available from github. I
5134 plan to move it into Debian if further testing prove this to be a
5135 useful approach.
</p
>
5137 <p
>If you want to test this, set up a blank Debian machine without any
5138 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
5139 get rid of exim4). Install tor, clone the git repository mentioned
5140 above, build the deb and install it on the machine. Next, run
5141 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
5142 the instructions to get the service up and running. Restart tor and
5143 exim when it is done, and test mail delivery using swaks like
5146 <p
><blockquote
><pre
>
5147 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5148 --to fbx@dutlqrrmjhtfa3vp.onion
5149 </pre
></blockquote
></p
>
5151 <p
>This will test the SMTP delivery using tor. Replace the email
5152 address with your own address to test your server. :)
</p
>
5154 <p
>The setup procedure is still to complex, and I hope it can be made
5155 easier and more automatic. Especially the tor setup need more work.
5156 Also, the package include a tor-smtp tool written in C, but its task
5157 should probably be rewritten in some script language to make the deb
5158 architecture independent. It would probably also make the code easier
5159 to review. The tor-smtp tool currently need to listen on a socket for
5160 exim to talk to it and is started using xinetd. It would be better if
5161 no daemon and no socket is needed. I suspect it is possible to get
5162 exim to run a command line tool for delivery instead of talking to a
5163 socket, and hope to figure out how in a future version of this
5166 <p
>Until I wipe my test machine, I can be reached using the
5167 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
5168 SMTorP. :)
</p
>
5173 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
5174 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
5175 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
5176 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
5177 <description><p
>If you ever had to moderate a mailman list, like the ones on
5178 alioth.debian.org, you know the web interface is fairly slow to
5179 operate. First you visit one web page, enter the moderation password
5180 and get a new page shown with a list of all the messages to moderate
5181 and various options for each email address. This take a while for
5182 every list you moderate, and you need to do it regularly to do a good
5183 job as a list moderator. But there is a quick alternative,
5184 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
5185 listadmin program
</a
>. It allow you to check lists for new messages
5186 to moderate in a fraction of a second. Here is a test run on two
5187 lists I recently took over:
</p
>
5189 <p
><blockquote
><pre
>
5190 % time listadmin xiph
5191 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5192 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5198 </pre
></blockquote
></p
>
5200 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
5201 there are no message in the moderation queue. Every morning I
5202 currently moderate
68 mailman lists, and it normally take around two
5203 minutes. When I took over the two pkg-xiph lists above a few days
5204 ago, there were
400 emails waiting in the moderator queue. It took me
5205 less than
15 minutes to process them all using the listadmin
5208 <p
>If you install
5209 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
5210 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
5211 with content like this, the moderation task is a breeze:
</p
>
5213 <p
><blockquote
><pre
>
5214 username username@example.org
5217 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
5220 adminurl https://{domain}/mailman/admindb/{list}
5221 mailman-list@lists.example.com
5224 other-list@otherserver.example.org
5225 </pre
></blockquote
></p
>
5227 <p
>There are other options to set as well. Check the manual page to
5228 learn the details.
</p
>
5230 <p
>If you are forced to moderate lists on a mailman installation where
5231 the SSL certificate is self signed or not properly signed by a
5232 generally accepted signing authority, you can set a environment
5233 variable when calling listadmin to disable SSL verification:
</p
>
5235 <p
><blockquote
><pre
>
5236 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
5237 </pre
></blockquote
></p
>
5239 <p
>If you want to moderate a subset of the lists you take care of, you
5240 can provide an argument to the listadmin script like I do in the
5241 initial screen dump (the xiph argument). Using an argument, only
5242 lists matching the argument string will be processed. This make it
5243 quick to accept messages if you notice the moderation request in your
5246 <p
>Without the listadmin program, I would never be the moderator of
68
5247 mailing lists, as I simply do not have time to spend on that if the
5248 process was any slower. The listadmin program have saved me hours of
5249 time I could spend elsewhere over the years. It truly is nice free
5252 <p
>As usual, if you use Bitcoin and want to show your support of my
5253 activities, please send Bitcoin donations to my address
5254 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5256 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
5257 configuration example. Also, I
've been told that the
5258 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
5264 <title>Debian Jessie, PXE and automatic firmware installation
</title>
5265 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
5266 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
5267 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
5268 <description><p
>When PXE installing laptops with Debian, I often run into the
5269 problem that the WiFi card require some firmware to work properly.
5270 And it has been a pain to fix this using preseeding in Debian.
5271 Normally something more is needed. But thanks to
5272 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
5273 package
</a
> and its recent tasksel extension, it has now become easy
5274 to do this using simple preseeding.
</p
>
5276 <p
>The isenkram-cli package provide tasksel tasks which will install
5277 firmware for the hardware found in the machine (actually, requested by
5278 the kernel modules for the hardware). (It can also install user space
5279 programs supporting the hardware detected, but that is not the focus
5280 of this story.)
</p
>
5282 <p
>To get this working in the default installation, two preeseding
5283 values are needed. First, the isenkram-cli package must be installed
5284 into the target chroot (aka the hard drive) before tasksel is executed
5285 in the pkgsel step of the debian-installer system. This is done by
5286 preseeding the base-installer/includes debconf value to include the
5287 isenkram-cli package. The package name is next passed to debootstrap
5288 for installation. With the isenkram-cli package in place, tasksel
5289 will automatically use the isenkram tasks to detect hardware specific
5290 packages for the machine being installed and install them, because
5291 isenkram-cli contain tasksel tasks.
</p
>
5293 <p
>Second, one need to enable the non-free APT repository, because
5294 most firmware unfortunately is non-free. This is done by preseeding
5295 the apt-mirror-setup step. This is unfortunate, but for a lot of
5296 hardware it is the only option in Debian.
</p
>
5298 <p
>The end result is two lines needed in your preseeding file to get
5299 firmware installed automatically by the installer:
</p
>
5301 <p
><blockquote
><pre
>
5302 base-installer base-installer/includes string isenkram-cli
5303 apt-mirror-setup apt-setup/non-free boolean true
5304 </pre
></blockquote
></p
>
5306 <p
>The current version of isenkram-cli in testing/jessie will install
5307 both firmware and user space packages when using this method. It also
5308 do not work well, so use version
0.15 or later. Installing both
5309 firmware and user space packages might give you a bit more than you
5310 want, so I decided to split the tasksel task in two, one for firmware
5311 and one for user space programs. The firmware task is enabled by
5312 default, while the one for user space programs is not. This split is
5313 implemented in the package currently in unstable.
</p
>
5315 <p
>If you decide to give this a go, please let me know (via email) how
5316 this recipe work for you. :)
</p
>
5318 <p
>So, I bet you are wondering, how can this work. First and
5319 foremost, it work because tasksel is modular, and driven by whatever
5320 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
5321 isenkram-cli package place two files for tasksel to find. First there
5322 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
5324 <p
><blockquote
><pre
>
5325 Task: isenkram-packages
5327 Description: Hardware specific packages (autodetected by isenkram)
5328 Based on the detected hardware various hardware specific packages are
5330 Test-new-install: show show
5332 Packages: for-current-hardware
5334 Task: isenkram-firmware
5336 Description: Hardware specific firmware packages (autodetected by isenkram)
5337 Based on the detected hardware various hardware specific firmware
5338 packages are proposed.
5339 Test-new-install: mark show
5341 Packages: for-current-hardware-firmware
5342 </pre
></blockquote
></p
>
5344 <p
>The key parts are Test-new-install which indicate how the task
5345 should be handled and the Packages line referencing to a script in
5346 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
5347 list of packages to install. The for-current-hardware-firmware script
5348 look like this to list relevant firmware for the machine:
5350 <p
><blockquote
><pre
>
5353 PATH=/usr/sbin:$PATH
5355 isenkram-autoinstall-firmware -l
5356 </pre
></blockquote
></p
>
5358 <p
>With those two pieces in place, the firmware is installed by
5359 tasksel during the normal d-i run. :)
</p
>
5361 <p
>If you want to test what tasksel will install when isenkram-cli is
5362 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
5363 --new-install
</tt
> to get the list of packages that tasksel would
5366 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
5367 pilots in testing this feature, as isenkram is used there now to
5368 install firmware, replacing the earlier scripts.
</p
>
5373 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
5374 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
5375 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
5376 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
5377 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
5378 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
5379 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
5380 on a screen normally showing the bread types and prizes:
</p
>
5382 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
5384 <p
>If it had booted as it was supposed to, I would never had known
5385 about this hidden Linux installation. It is interesting what
5386 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
5391 <title>New lsdvd release version
0.17 is ready
</title>
5392 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
5393 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
5394 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
5395 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
5396 got a new set of developers a few weeks ago, after the original
5397 developer decided to step down and pass the project to fresh blood.
5398 This project is now maintained by Petter Reinholdtsen and Steve
5401 <p
>I just wrapped up
5402 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
5403 new lsdvd release
</a
>, available in git or from
5404 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
5405 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
5410 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
5411 <li
>Check for garbage in the program chains, which indicate that a track is
5412 non-existant, to work around additional copy protection
</li
>
5413 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
5414 <li
>Fix pallete display of first entry
</li
>
5415 <li
>Fix include orders
</li
>
5416 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
5417 <li
>Fix the chapter count
</li
>
5418 <li
>Make sure the array size and the array limit used when initialising
5419 the palette size is the same.
</li
>
5420 <li
>Fix array printing.
</li
>
5421 <li
>Correct subsecond calculations.
</li
>
5422 <li
>Add sector information to the output format.
</li
>
5423 <li
>Clean up code to be closer to ANSI C and compile without warnings
5424 with more GCC compiler warnings.
</li
>
5428 <p
>This change bring together patches for lsdvd in use in various
5429 Linux and Unix distributions, as well as patches submitted to the
5430 project the last nine years. Please check it out. :)
</p
>
5435 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
5436 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
5437 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
5438 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
5439 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
5440 project
</a
> provide a Linux solution for schools, including a
5441 powerful desktop with education software, a central server providing
5442 web pages, user database, user home directories, central login and PXE
5443 boot of both clients without disk and the installation to install Debian
5444 Edu on machines with disk (and a few other services perhaps to small
5445 to mention here). We in the Debian Edu team are currently working on
5446 the Jessie based version, trying to get everything in shape before the
5447 freeze, to avoid having to maintain our own package repository in the
5449 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
5450 status
</a
> can be seen on the Debian wiki, and there is still heaps of
5451 work left. Some fatal problems block testing, breaking the installer,
5452 but it is possible to work around these to get anyway. Here is a
5453 recipe on how to get the installation limping along.
</p
>
5455 <p
>First, download the test ISO via
5456 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
5457 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
5459 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
5460 The ISO build was broken on Tuesday, so we do not get a new ISO every
5461 12 hours or so, but thankfully the ISO we already got we are able to
5462 install with some tweaking.
</p
>
5464 <p
>When you get to the Debian Edu profile question, go to tty2
5465 (use Alt-Ctrl-F2), run
</p
>
5467 <p
><blockquote
><pre
>
5468 nano /usr/bin/edu-eatmydata-install
5469 </pre
></blockquote
></p
>
5471 <p
>and add
'exit
0' as the second line, disabling the eatmydata
5472 optimization. Return to the installation, select the profile you want
5473 and continue. Without this change, exim4-config will fail to install
5474 due to a known bug in eatmydata.
</p
>
5476 <p
>When you get the grub question at the end, answer /dev/sda (or if
5477 this do not work, figure out what your correct value would be. All my
5478 test machines need /dev/sda, so I have no advice if it do not fit
5479 your need.
</p
>
5481 <p
>If you installed a profile including a graphical desktop, log in as
5482 root after the initial boot from hard drive, and install the
5483 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
5484 or mate. If you want several desktop options, install more than one
5485 metapackage. Once this is done, reboot and you should have a working
5486 graphical login screen. This workaround should no longer be needed
5487 once the education-tasks package version
1.801 enter testing in two
5490 <p
>I believe the ISO build will start working on two days when the new
5491 tasksel package enter testing and Steve McIntyre get a chance to
5492 update the debian-cd git repository. The eatmydata, grub and desktop
5493 issues are already fixed in unstable and testing, and should show up
5494 on the ISO as soon as the ISO build start working again. Well the
5495 eatmydata optimization is really just disabled. The proper fix
5496 require an upload by the eatmydata maintainer applying the patch
5497 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
5498 The rest have proper fixes in unstable.
</p
>
5500 <p
>I hope this get you going with the installation testing, as we are
5501 quickly running out of time trying to get our Jessie based
5502 installation ready before the distribution freeze in a month.
</p
>
5507 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
5508 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
5509 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
5510 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
5511 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
5512 to handle my fairly large DVD collection. It is a nice command line
5513 tool to get details about a DVD, like title, tracks, track length,
5514 etc, in XML, Perl or human readable format. But lsdvd have not seen
5515 any new development since
2006 and had a few irritating bugs affecting
5516 its use with some DVDs. Upstream seemed to be dead, and in January I
5517 sent a small probe asking for a version control repository for the
5518 project, without any reply. But I use it regularly and would like to
5519 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
5520 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
5521 the project admin, and after getting a reply from him explaining that
5522 he was no longer interested in the project, I asked if I could take
5523 over. And yesterday, I became project admin.
</p
>
5525 <p
>I
've been in touch with a Gentoo developer and the Debian
5526 maintainer interested in joining forces to maintain the upstream
5527 project, and I hope we can get a new release out fairly quickly,
5528 collecting the patches spread around on the internet into on place.
5529 I
've added the relevant Debian patches to the freshly created git
5530 repository, and expect the Gentoo patches to make it too. If you got
5531 a DVD collection and care about command line tools, check out
5532 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
5533 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
5534 list
</a
>. :)
</p
>
5539 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
5540 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
5541 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
5542 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
5543 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
5544 a lot quicker. When we install more than
2000 packages in
5545 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
5546 tasksel in the installer, unpacking the binary packages take forever.
5547 A part of the slow I/O issue was discussed in
5548 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
5549 much file system sync-ing done by dpkg, which is the package
5550 responsible for unpacking the binary packages. Other parts (like code
5551 executed by postinst scripts) might also sync to disk during
5552 installation. All this sync-ing to disk do not really make sense to
5553 me. If the machine crash half-way through, I start over, I do not try
5554 to salvage the half installed system. So the failure sync-ing is
5555 supposed to protect against, hardware or system crash, is not really
5556 relevant while the installer is running.
</p
>
5558 <p
>A few days ago, I thought of a way to get rid of all the file
5559 system sync()-ing in a fairly non-intrusive way, without the need to
5560 change the code in several packages. The idea is not new, but I have
5561 not heard anyone propose the approach using dpkg-divert before. It
5562 depend on the small and clever package
5563 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
5564 uses LD_PRELOAD to replace the system functions for syncing data to
5565 disk with functions doing nothing, thus allowing programs to live
5566 dangerous while speeding up disk I/O significantly. Instead of
5567 modifying the implementation of dpkg, apt and tasksel (which are the
5568 packages responsible for selecting, fetching and installing packages),
5569 it occurred to me that we could just divert the programs away, replace
5570 them with a simple shell wrapper calling
5571 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
5572 Two days ago I decided to test the idea, and wrapped up a simple
5573 implementation for the Debian Edu udeb.
</p
>
5575 <p
>The effect was stunning. In my first test it reduced the running
5576 time of the pkgsel step (installing tasks) from
64 to less than
44
5577 minutes (
20 minutes shaved off the installation) on an old Dell
5578 Latitude D505 machine. I am not quite sure what the optimised time
5579 would have been, as I messed up the testing a bit, causing the debconf
5580 priority to get low enough for two questions to pop up during
5581 installation. As soon as I saw the questions I moved the installation
5582 along, but do not know how long the question were holding up the
5583 installation. I did some more measurements using Debian Edu Jessie,
5584 and got these results. The time measured is the time stamp in
5585 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
5586 "pkgsel: finishing up
" lines, if you want to do the same measurement
5587 yourself. In Debian Edu, the tasksel dialog do not show up, and the
5588 timing thus do not depend on how quickly the user handle the tasksel
5591 <p
><table
>
5594 <th
>Machine/setup
</th
>
5595 <th
>Original tasksel
</th
>
5596 <th
>Optimised tasksel
</th
>
5597 <th
>Reduction
</th
>
5601 <td
>Latitude D505 Main+LTSP LXDE
</td
>
5602 <td
>64 min (
07:
46-
08:
50)
</td
>
5603 <td
><44 min (
11:
27-
12:
11)
</td
>
5604 <td
>>20 min
18%
</td
>
5608 <td
>Latitude D505 Roaming LXDE
</td
>
5609 <td
>57 min (
08:
48-
09:
45)
</td
>
5610 <td
>34 min (
07:
43-
08:
17)
</td
>
5611 <td
>23 min
40%
</td
>
5615 <td
>Latitude D505 Minimal
</td
>
5616 <td
>22 min (
10:
37-
10:
59)
</td
>
5617 <td
>11 min (
11:
16-
11:
27)
</td
>
5618 <td
>11 min
50%
</td
>
5622 <td
>Thinkpad X200 Minimal
</td
>
5623 <td
>6 min (
08:
19-
08:
25)
</td
>
5624 <td
>4 min (
08:
04-
08:
08)
</td
>
5625 <td
>2 min
33%
</td
>
5629 <td
>Thinkpad X200 Roaming KDE
</td
>
5630 <td
>19 min (
09:
21-
09:
40)
</td
>
5631 <td
>15 min (
10:
25-
10:
40)
</td
>
5632 <td
>4 min
21%
</td
>
5635 </table
></p
>
5637 <p
>The test is done using a netinst ISO on a USB stick, so some of the
5638 time is spent downloading packages. The connection to the Internet
5639 was
100Mbit/s during testing, so downloading should not be a
5640 significant factor in the measurement. Download typically took a few
5641 seconds to a few minutes, depending on the amount of packages being
5642 installed.
</p
>
5644 <p
>The speedup is implemented by using two hooks in
5645 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
5646 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
5647 finish-install.d hook to remove the divert at the end of the
5648 installation. I picked the pre-pkgsel.d hook instead of the
5649 post-base-installer.d hook because I test using an ISO without the
5650 eatmydata package included, and the post-base-installer.d hook in
5651 Debian Edu can only operate on packages included in the ISO. The
5652 negative effect of this is that I am unable to activate this
5653 optimization for the kernel installation step in d-i. If the code is
5654 moved to the post-base-installer.d hook, the speedup would be larger
5655 for the entire installation.
</p
>
5657 <p
>I
've implemented this in the
5658 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
5659 git repository, and plan to provide the optimization as part of the
5660 Debian Edu installation. If you want to test this yourself, you can
5661 create two files in the installer (or in an udeb). One shell script
5662 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
5664 <p
><blockquote
><pre
>
5667 . /usr/share/debconf/confmodule
5669 logger -t my-pkgsel
"info: $*
"
5672 logger -t my-pkgsel
"error: $*
"
5674 override_install() {
5675 apt-install eatmydata || true
5676 if [ -x /target/usr/bin/eatmydata ] ; then
5677 for bin in dpkg apt-get aptitude tasksel ; do
5679 # Test that the file exist and have not been diverted already.
5680 if [ -f /target$file ] ; then
5681 info
"diverting $file using eatmydata
"
5682 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
5683 > /target$file.edu
5684 chmod
755 /target$file.edu
5685 in-target dpkg-divert --package debian-edu-config \
5686 --rename --quiet --add $file
5687 ln -sf ./$bin.edu /target$file
5689 error
"unable to divert $file, as it is missing.
"
5693 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
5698 </pre
></blockquote
></p
>
5700 <p
>To clean up, another shell script should go into
5701 /usr/lib/finish-install.d/ with code like this:
5703 <p
><blockquote
><pre
>
5705 . /usr/share/debconf/confmodule
5707 logger -t my-finish-install
"error: $@
"
5709 remove_install_override() {
5710 for bin in dpkg apt-get aptitude tasksel ; do
5712 if [ -x /target$file.edu ] ; then
5714 in-target dpkg-divert --package debian-edu-config \
5715 --rename --quiet --remove $file
5718 error
"Missing divert for $file.
"
5721 sync # Flush file buffers before continuing
5724 remove_install_override
5725 </pre
></blockquote
></p
>
5727 <p
>In Debian Edu, I placed both code fragments in a separate script
5728 edu-eatmydata-install and call it from the pre-pkgsel.d and
5729 finish-install.d scripts.
</p
>
5731 <p
>By now you might ask if this change should get into the normal
5732 Debian installer too? I suspect it should, but am not sure the
5733 current debian-installer coordinators find it useful enough. It also
5734 depend on the side effects of the change. I
'm not aware of any, but I
5735 guess we will see if the change is safe after some more testing.
5736 Perhaps there is some package in Debian depending on sync() and
5737 fsync() having effect? Perhaps it should go into its own udeb, to
5738 allow those of us wanting to enable it to do so without affecting
5741 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
5742 will break installation of all programs using gnutls because of
5743 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
5744 eatmydata package in Debian will solve it.
</p
>
5746 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
5747 the optimization work again. And I have discovered that the
5748 dpkg-divert trick is not really needed and implemented a slightly
5749 simpler approach as part of the debian-edu-install package. See
5750 tools/edu-eatmydata-install in the source package.
</p
>
5752 <p
>Update
2014-
11-
11: Unfortunately, a new
5753 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
5754 triggering on i386 made it into testing, and broke this installation
5755 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
5756 request
768893</a
> is accepted, it should be working again.
</p
>
5761 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
5762 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
5763 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
5764 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
5765 <description><p
>Yesterday, I had the pleasure of attending a talk with the
5766 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
5767 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
5768 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
5769 learn that there is a large set of publicly available key servers to
5770 use when looking for peoples public key. So far I have used
5771 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
5772 were misbehaving, but those days are ended. The servers I have used
5773 up until yesterday have been slow and some times unavailable. I hope
5774 those problems are gone now.
</p
>
5776 <p
>Behind the round robin DNS entry of the
5777 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
5778 there is a pool of more than
100 keyservers which are checked every
5779 day to ensure they are well connected and up to date. It must be
5780 better than what I have used so far. :)
</p
>
5782 <p
>Yesterdays speaker told me that the service is the default
5783 keyserver provided by the default configuration in GnuPG, but this do
5784 not seem to be used in Debian. Perhaps it should?
</p
>
5786 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
5789 <p
><blockquote
><pre
>
5790 keyserver pool.sks-keyservers.net
5791 </pre
></blockquote
></p
>
5793 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
5794 entries in DNS. Just for fun, I did just that at work, so now every
5795 user of GnuPG at the University of Oslo should find a OpenGPG
5796 keyserver automatically should their need it:
</p
>
5798 <p
><blockquote
><pre
>
5799 % host -t srv _pgpkey-http._tcp.uio.no
5800 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
5802 </pre
></blockquote
></p
>
5804 <p
>Now if only
5805 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
5806 HKP lookup protocol
</a
> supported finding signature paths, I would be
5807 very happy. It can look up a given key or search for a user ID, but I
5808 normally do not want that, but to find a trust path from my key to
5809 another key. Given a user ID or key ID, I would like to find (and
5810 download) the keys representing a signature path from my key to the
5811 key in question, to be able to get a trust path between the two keys.
5812 This is as far as I can tell not possible today. Perhaps something
5813 for a future version of the protocol?
</p
>
5818 <title>From English wiki to translated PDF and epub via Docbook
</title>
5819 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
5820 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
5821 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
5822 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
5823 project
</a
> provide an instruction manual for teachers, system
5824 administrators and other users that contain useful tips for setting up
5825 and maintaining a Debian Edu installation. This text is about how the
5826 text processing of this manual is handled in the project.
</p
>
5828 <p
>One goal of the project is to provide information in the native
5829 language of its users, and for this we need to handle translations.
5830 But we also want to make sure each language contain the same
5831 information, so for this we need a good way to keep the translations
5832 in sync. And we want it to be easy for our users to improve the
5833 documentation, avoiding the need to learn special formats or tools to
5834 contribute, and the obvious way to do this is to make it possible to
5835 edit the documentation using a web browser. We also want it to be
5836 easy for translators to keep the translation up to date, and give them
5837 help in figuring out what need to be translated. Here is the list of
5838 tools and the process we have found trying to reach all these
5841 <p
>We maintain the authoritative source of our manual in the
5842 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
5843 wiki
</a
>, as several wiki pages written in English. It consist of one
5844 front page with references to the different chapters, several pages
5845 for each chapter, and finally one
"collection page
" gluing all the
5846 chapters together into one large web page (aka
5847 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
5848 AllInOne page
</a
>). The AllInOne page is the one used for further
5849 processing and translations. Thanks to the fact that the
5850 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
5851 wiki.debian.org support exporting pages in
5852 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
5853 the list of pages to export using the raw version of the AllInOne
5854 page, loop over each of them to generate a Docbook XML version of the
5855 manual. This process also download images and transform image
5856 references to use the locally downloaded images. The generated
5857 Docbook XML files are slightly broken, so some post-processing is done
5858 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
5859 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
5860 a handfull of images. The XML file can now be used to generate PDF, HTML
5861 and epub versions of the English manual. This is the basic step of
5862 our process, making PDF (using dblatex), HTML (using xsltproc) and
5863 epub (using dbtoepub) version from Docbook XML, and the resulting files
5864 are placed in the debian-edu-doc-en binary package.
</p
>
5866 <p
>But English documentation is not enough for us. We want translated
5867 documentation too, and we want to make it easy for translators to
5868 track the English original. For this we use the
5869 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
5870 which allow us to transform the English Docbook XML file into a
5871 translation file (a .pot file), usable with the normal gettext based
5872 translation tools used by those translating free software. The pot
5873 file is used to create and maintain translation files (several .po
5874 files), which the translations update with the native language
5875 translations of all titles, paragraphs and blocks of text in the
5876 original. The next step is combining the original English Docbook XML
5877 and the translation file (say debian-edu-wheezy-manual.nb.po), to
5878 create a translated Docbook XML file (in this case
5879 debian-edu-wheezy-manual.nb.xml). This translated (or partly
5880 translated, if the translation is not complete) Docbook XML file can
5881 then be used like the original to create a PDF, HTML and epub version
5882 of the documentation.
</p
>
5884 <p
>The translators use different tools to edit the .po files. We
5886 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
5887 while some use emacs and vi, others can use web based editors like
5888 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
5889 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
5890 is where the .po file end up, in our git repository. Updated
5891 translations can either be committed directly to git, or submitted as
5892 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
5893 against the debian-edu-doc package
</a
>.
</p
>
5895 <p
>One challenge is images, which both might need to be translated (if
5896 they show translated user applications), and are needed in different
5897 formats when creating PDF and HTML versions (epub is a HTML version in
5898 this regard). For this we transform the original PNG images to the
5899 needed density and format during build, and have a way to provide
5900 translated images by storing translated versions in
5901 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
5902 package maintainers know more.
</p
>
5904 <p
>If you wonder what the result look like, we provide
5905 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
5906 of the documentation packages on the web
</a
>. See for example the
5907 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
5908 PDF version
</a
> or the
5909 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
5910 HTML version
</a
>. We do not yet build the epub version by default,
5911 but perhaps it will be done in the future.
</p
>
5913 <p
>To learn more, check out
5914 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
5915 debian-edu-doc package
</a
>,
5916 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
5917 manual on the wiki
</a
> and
5918 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
5919 translation instructions
</a
> in the manual.
</p
>
5924 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
5925 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
5926 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
5927 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
5928 <description><p
>It would be nice if it was easier in Debian to get all the hardware
5929 related packages relevant for the computer installed automatically.
5930 So I implemented one, using
5931 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
5932 package
</a
>. To use it, install the tasksel and isenkram packages and
5933 run tasksel as user root. You should be presented with a new option,
5934 "Hardware specific packages (autodetected by isenkram)
". When you
5935 select it, tasksel will install the packages isenkram claim is fit for
5936 the current hardware, hot pluggable or not.
<p
>
5938 <p
>The implementation is in two files, one is the tasksel menu entry
5939 description, and the other is the script used to extract the list of
5940 packages to install. The first part is in
5941 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
5944 <p
><blockquote
><pre
>
5947 Description: Hardware specific packages (autodetected by isenkram)
5948 Based on the detected hardware various hardware specific packages are
5950 Test-new-install: mark show
5952 Packages: for-current-hardware
5953 </pre
></blockquote
></p
>
5955 <p
>The second part is in
5956 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
5959 <p
><blockquote
><pre
>
5964 isenkram-autoinstall-firmware -l
5966 </pre
></blockquote
></p
>
5968 <p
>All in all, a very short and simple implementation making it
5969 trivial to install the hardware dependent package we all may want to
5970 have installed on our machines. I
've not been able to find a way to
5971 get tasksel to tell you exactly which packages it plan to install
5972 before doing the installation. So if you are curious or careful,
5973 check the output from the isenkram-* command line tools first.
</p
>
5975 <p
>The information about which packages are handling which hardware is
5976 fetched either from the isenkram package itself in
5977 /usr/share/isenkram/, from git.debian.org or from the APT package
5978 database (using the Modaliases header). The APT package database
5979 parsing have caused a nasty resource leak in the isenkram daemon (bugs
5980 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
5981 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
5982 the python-apt code (bug
5983 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
5984 workaround I was able to get rid of the file descriptor leak and
5985 reduce the memory leak from ~
30 MiB per hardware detection down to
5986 around
2 MiB per hardware detection. It should make the desktop
5987 daemon a lot more useful. The fix is in version
0.7 uploaded to
5988 unstable today.
</p
>
5990 <p
>I believe the current way of mapping hardware to packages in
5991 Isenkram is is a good draft, but in the future I expect isenkram to
5992 use the AppStream data source for this. A proposal for getting proper
5993 AppStream support into Debian is floating around as
5994 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
5995 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
5996 project
</a
> will take place this summer to improve the situation. I
5997 look forward to seeing the result, and welcome patches for isenkram to
5998 start using the information when it is ready.
</p
>
6000 <p
>If you want your package to map to some specific hardware, either
6001 add a
"Xb-Modaliases
" header to your control file like I did in
6002 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
6003 package
</a
> or submit a bug report with the details to the isenkram
6005 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
6006 blog posts tagged isenkram
</a
> for details on the notation. I expect
6007 the information will be migrated to AppStream eventually, but for the
6008 moment I got no better place to store it.
</p
>
6013 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
6014 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
6015 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
6016 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
6017 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
6018 project
</a
> is working on providing the software and hardware to make
6019 it easy for non-technical people to host their data and communication
6020 at home, and being able to communicate with their friends and family
6021 encrypted and away from prying eyes. It is still going strong, and
6022 today a major mile stone was reached.
</p
>
6024 <p
>Today, the last of the packages currently used by the project to
6025 created the system images were accepted into Debian Unstable. It was
6026 the freedombox-setup package, which is used to configure the images
6027 during build and on the first boot. Now all one need to get going is
6028 the build code from the freedom-maker git repository and packages from
6029 Debian. And once the freedombox-setup package enter testing, we can
6030 build everything directly from Debian. :)
</p
>
6032 <p
>Some key packages used by Freedombox are
6033 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
6034 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
6035 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
6036 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
6037 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
6038 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
6039 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
6040 are plans to integrate more packages into the setup. User
6041 documentation is maintained on the Debian wiki. Please
6042 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
6043 the manual
</a
> and help us improve it.
</p
>
6045 <p
>To test for yourself and create boot images with the FreedomBox
6046 setup, run this on a Debian machine using a user with sudo rights to
6047 become root:
</p
>
6049 <p
><pre
>
6050 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6051 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6053 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6055 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6056 </pre
></p
>
6058 <p
>Root access is needed to run debootstrap and mount loopback
6059 devices. See the README in the freedom-maker git repo for more
6060 details on the build. If you do not want all three images, trim the
6061 make line. Note that the virtualbox-image target is not really
6062 virtualbox specific. It create a x86 image usable in kvm, qemu,
6063 vmware and any other x86 virtual machine environment. You might need
6064 the version of vmdebootstrap in Jessie to get the build working, as it
6065 include fixes for a race condition with kpartx.
</p
>
6067 <p
>If you instead want to install using a Debian CD and the preseed
6068 method, boot a Debian Wheezy ISO and use this boot argument to load
6069 the preseed values:
</p
>
6071 <p
><pre
>
6072 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
6073 </pre
></p
>
6075 <p
>I have not tested it myself the last few weeks, so I do not know if
6076 it still work.
</p
>
6078 <p
>If you wonder how to help, one task you could look at is using
6079 systemd as the boot system. It will become the default for Linux in
6080 Jessie, so we need to make sure it is usable on the Freedombox. I did
6081 a simple test a few weeks ago, and noticed dnsmasq failed to start
6082 during boot when using systemd. I suspect there are other problems
6083 too. :) To detect problems, there is a test suite included, which can
6084 be run from the plinth web interface.
</p
>
6086 <p
>Give it a go and let us know how it goes on the mailing list, and help
6087 us get the new release published. :) Please join us on
6088 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
6089 irc.debian.org)
</a
> and
6090 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6091 mailing list
</a
> if you want to help make this vision come true.
</p
>
6096 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
6097 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
6098 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
6099 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
6100 <description><p
>For a while now, I have been looking for a sensible offsite backup
6101 solution for use at home. My requirements are simple, it must be
6102 cheap and locally encrypted (in other words, I keep the encryption
6103 keys, the storage provider do not have access to my private files).
6104 One idea me and my friends had many years ago, before the cloud
6105 storage providers showed up, was to use Google mail as storage,
6106 writing a Linux block device storing blocks as emails in the mail
6107 service provided by Google, and thus get heaps of free space. On top
6108 of this one can add encryption, RAID and volume management to have
6109 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6110 I never found time to implement such system. But the last few weeks I
6111 have looked at a system called
6112 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
6113 mounted network backed file system with the features I need.
</p
>
6115 <p
>S3QL is a fuse file system with a local cache and cloud storage,
6116 handling several different storage providers, any with Amazon S3,
6117 Google Drive or OpenStack API. There are heaps of such storage
6118 providers. S3QL can also use a local directory as storage, which
6119 combined with sshfs allow for file storage on any ssh server. S3QL
6120 include support for encryption, compression, de-duplication, snapshots
6121 and immutable file systems, allowing me to mount the remote storage as
6122 a local mount point, look at and use the files as if they were local,
6123 while the content is stored in the cloud as well. This allow me to
6124 have a backup that should survive fire. The file system can not be
6125 shared between several machines at the same time, as only one can
6126 mount it at the time, but any machine with the encryption key and
6127 access to the storage service can mount it if it is unmounted.
</p
>
6129 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
6130 package is included already. So to get started, run
<tt
>apt-get
6131 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
6132 Greenqloud, after reading their nice recipe on
6133 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
6134 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
6135 in Iceland more than those in USA when it come to keeping my personal
6136 data safe and private, and thus would rather spend money on a company
6137 in Iceland. Another nice recipe is available from the article
6138 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
6139 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
6140 Admin magazine. When the provider is picked, figure out how to get
6141 the API key needed to connect to the storage API. With Greencloud,
6142 the key did not show up until I had added payment details to my
6145 <p
>Armed with the API access details, it is time to create the file
6146 system. First, create a new bucket in the cloud. This bucket is the
6147 file system storage area. I picked a bucket name reflecting the
6148 machine that was going to store data there, but any name will do.
6149 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
6150 the API login and password, and a locally created password. Store it
6151 all in ~root/.s3ql/authinfo2 like this:
6153 <p
><blockquote
><pre
>
6155 storage-url: s3c://s.greenqloud.com:
443/bucket-name
6156 backend-login: API-login
6157 backend-password: API-password
6158 fs-passphrase: local-password
6159 </pre
></blockquote
></p
>
6161 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
6162 but any sensible way to create a fairly random password should do it.
6163 Armed with these details, it is now time to run mkfs, entering the API
6164 details and password to create it:
</p
>
6166 <p
><blockquote
><pre
>
6167 # mkdir -m
700 /var/lib/s3ql-cache
6168 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6169 --ssl s3c://s.greenqloud.com:
443/bucket-name
6170 Enter backend login:
6171 Enter backend password:
6172 Before using S3QL, make sure to read the user
's guide, especially
6173 the
'Important Rules to Avoid Loosing Data
' section.
6174 Enter encryption password:
6175 Confirm encryption password:
6176 Generating random encryption key...
6177 Creating metadata tables...
6187 Compressing and uploading metadata...
6188 Wrote
0.00 MB of compressed metadata.
6189 #
</pre
></blockquote
></p
>
6191 <p
>The next step is mounting the file system to make the storage available.
6193 <p
><blockquote
><pre
>
6194 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6195 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
6196 Using
4 upload threads.
6197 Downloading and decompressing metadata...
6207 Mounting filesystem...
6209 Filesystem Size Used Avail Use% Mounted on
6210 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
6212 </pre
></blockquote
></p
>
6214 <p
>The file system is now ready for use. I use rsync to store my
6215 backups in it, and as the metadata used by rsync is downloaded at
6216 mount time, no network traffic (and storage cost) is triggered by
6217 running rsync. To unmount, one should not use the normal umount
6218 command, as this will not flush the cache to the cloud storage, but
6219 instead running the umount.s3ql command like this:
6221 <p
><blockquote
><pre
>
6224 </pre
></blockquote
></p
>
6226 <p
>There is a fsck command available to check the file system and
6227 correct any problems detected. This can be used if the local server
6228 crashes while the file system is mounted, to reset the
"already
6229 mounted
" flag. This is what it look like when processing a working
6230 file system:
</p
>
6232 <p
><blockquote
><pre
>
6233 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
6234 Using cached metadata.
6235 File system seems clean, checking anyway.
6236 Checking DB integrity...
6237 Creating temporary extra indices...
6238 Checking lost+found...
6239 Checking cached objects...
6240 Checking names (refcounts)...
6241 Checking contents (names)...
6242 Checking contents (inodes)...
6243 Checking contents (parent inodes)...
6244 Checking objects (reference counts)...
6245 Checking objects (backend)...
6246 ..processed
5000 objects so far..
6247 ..processed
10000 objects so far..
6248 ..processed
15000 objects so far..
6249 Checking objects (sizes)...
6250 Checking blocks (referenced objects)...
6251 Checking blocks (refcounts)...
6252 Checking inode-block mapping (blocks)...
6253 Checking inode-block mapping (inodes)...
6254 Checking inodes (refcounts)...
6255 Checking inodes (sizes)...
6256 Checking extended attributes (names)...
6257 Checking extended attributes (inodes)...
6258 Checking symlinks (inodes)...
6259 Checking directory reachability...
6260 Checking unix conventions...
6261 Checking referential integrity...
6262 Dropping temporary indices...
6263 Backing up old metadata...
6273 Compressing and uploading metadata...
6274 Wrote
0.89 MB of compressed metadata.
6276 </pre
></blockquote
></p
>
6278 <p
>Thanks to the cache, working on files that fit in the cache is very
6279 quick, about the same speed as local file access. Uploading large
6280 amount of data is to me limited by the bandwidth out of and into my
6281 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
6282 which is very close to my upload speed, and downloading the same
6283 Debian installation ISO gave me
610 kiB/s, close to my download speed.
6284 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
6285 network, not the file system code. I do not know what a good cache
6286 size would be, but suspect that the cache should e larger than your
6287 working set.
</p
>
6289 <p
>I mentioned that only one machine can mount the file system at the
6290 time. If another machine try, it is told that the file system is
6293 <p
><blockquote
><pre
>
6294 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6295 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
6296 Using
8 upload threads.
6297 Backend reports that fs is still mounted elsewhere, aborting.
6299 </pre
></blockquote
></p
>
6301 <p
>The file content is uploaded when the cache is full, while the
6302 metadata is uploaded once every
24 hour by default. To ensure the
6303 file system content is flushed to the cloud, one can either umount the
6304 file system, or ask S3QL to flush the cache and metadata using
6307 <p
><blockquote
><pre
>
6308 # s3qlctrl upload-meta /s3ql
6309 # s3qlctrl flushcache /s3ql
6311 </pre
></blockquote
></p
>
6313 <p
>If you are curious about how much space your data uses in the
6314 cloud, and how much compression and deduplication cut down on the
6315 storage usage, you can use s3qlstat on the mounted file system to get
6318 <p
><blockquote
><pre
>
6320 Directory entries:
9141
6323 Total data size:
22049.38 MB
6324 After de-duplication:
21955.46 MB (
99.57% of total)
6325 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
6326 Database size:
2.39 MB (uncompressed)
6327 (some values do not take into account not-yet-uploaded dirty blocks in cache)
6329 </pre
></blockquote
></p
>
6331 <p
>I mentioned earlier that there are several possible suppliers of
6332 storage. I did not try to locate them all, but am aware of at least
6333 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
6334 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
6335 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
6336 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
6337 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
6338 accept payment in Bitcoin. Pick one that suit your need. Some of
6339 them provide several GiB of free storage, but the prize models are
6340 quite different and you will have to figure out what suits you
6343 <p
>While researching this blog post, I had a look at research papers
6344 and posters discussing the S3QL file system. There are several, which
6345 told me that the file system is getting a critical check by the
6346 science community and increased my confidence in using it. One nice
6348 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
6349 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
6350 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
6351 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
6352 and Pamela Smith. Please have a look.
</p
>
6354 <p
>Given my problems with different file systems earlier, I decided to
6355 check out the mounted S3QL file system to see if it would be usable as
6356 a home directory (in other word, that it provided POSIX semantics when
6357 it come to locking and umask handling etc). Running
6358 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
6359 test code to check file system semantics
</a
>, I was happy to discover that
6360 no error was found. So the file system can be used for home
6361 directories, if one chooses to do so.
</p
>
6363 <p
>If you do not want a locally file system, and want something that
6364 work without the Linux fuse file system, I would like to mention the
6365 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
6366 provide locally encrypted backup using a command line client. It have
6367 a nicer access control system, where one can split out read and write
6368 access, allowing some systems to write to the backup and others to
6369 only read from it.
</p
>
6371 <p
>As usual, if you use Bitcoin and want to show your support of my
6372 activities, please send Bitcoin donations to my address
6373 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6378 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
6379 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
6380 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
6381 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
6382 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
6383 project
</a
> is working on providing the software and hardware for
6384 making it easy for non-technical people to host their data and
6385 communication at home, and being able to communicate with their
6386 friends and family encrypted and away from prying eyes. It has been
6387 going on for a while, and is slowly progressing towards a new test
6388 release (
0.2).
</p
>
6390 <p
>And what day could be better than the Pi day to announce that the
6391 new version will provide
"hard drive
" / SD card / USB stick images for
6392 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
6393 system), and can also be installed using a Debian installer preseed
6394 file. The Debian based Freedombox is now based on Debian Jessie,
6395 where most of the needed packages used are already present. Only one,
6396 the freedombox-setup package, is missing. To try to build your own
6397 boot image to test the current status, fetch the freedom-maker scripts
6399 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
6400 with a user with sudo access to become root:
6403 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6405 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6406 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6408 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6411 <p
>Root access is needed to run debootstrap and mount loopback
6412 devices. See the README for more details on the build. If you do not
6413 want all three images, trim the make line. But note that thanks to
<a
6414 href=
"https://bugs.debian.org/
741407">a race condition in
6415 vmdebootstrap
</a
>, the build might fail without the patch to the
6416 kpartx call.
</p
>
6418 <p
>If you instead want to install using a Debian CD and the preseed
6419 method, boot a Debian Wheezy ISO and use this boot argument to load
6420 the preseed values:
</p
>
6423 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
6426 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
6427 recently introduced bug in apt in Jessie
</a
>, the installer will
6428 currently hang while setting up APT sources. Killing the
6429 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
6430 installation will get the installation going. This affect all
6431 installations in Jessie, and I expect it will be fixed soon.
</p
>
6433 <p
>Give it a go and let us know how it goes on the mailing list, and help
6434 us get the new release published. :) Please join us on
6435 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
6436 irc.debian.org)
</a
> and
6437 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6438 mailing list
</a
> if you want to help make this vision come true.
</p
>
6443 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
6444 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
6445 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
6446 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
6447 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
6448 innetgr tools, because I needed them in
6449 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
6450 ng-utils, and it has served me well. I placed the project under the
6451 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
6452 repository. But many years ago, the CVS repository was dropped (lost,
6453 not migrated to new hardware, not sure), and the project have lacked a
6454 proper home since then.
</p
>
6456 <p
>Last summer, I had a look at the package and made a new release
6457 fixing a irritating crash bug, but was unable to store the changes in
6458 a proper source control system. I applied for a project on
6459 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
6460 to follow up on it. Until today. :)
</p
>
6462 <p
>After many hours of cleaning and migration, the ng-utils project
6463 now have a new home, and a git repository with the highlight of the
6464 history of the project. I published all release tarballs and imported
6465 them into the git repository. As the project is really stable and not
6466 expected to gain new features any time soon, I decided to make a new
6467 release and call it
1.0. Visit the new project home on
6468 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
6469 if you want to check it out. The new version is also uploaded into
6470 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
6475 <title>Testing sysvinit from experimental in Debian Hurd
</title>
6476 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
6477 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
6478 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
6479 <description><p
>A few days ago I decided to try to help the Hurd people to get
6480 their changes into sysvinit, to allow them to use the normal sysvinit
6481 boot system instead of their old one. This follow up on the
6482 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
6483 Google Summer of Code work
</a
> done last summer by Justus Winter to
6484 get Debian on Hurd working more like Debian on Linux. To get started,
6485 I downloaded a prebuilt hard disk image from
6486 <a href=
"http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz
">http://ftp.debian-ports.org/debian-cd/hurd-i386/current/debian-hurd.img.tar.gz
</a
>,
6487 and started it using virt-manager.
</p
>
6489 <p
>The first think I had to do after logging in (root without any
6490 password) was to get the network operational. I followed
6491 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
6492 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
6493 commands as root to get the machine to accept a IP address from the
6494 kvm internal DHCP server:
</p
>
6496 <p
><blockquote
><pre
>
6497 settrans -fgap /dev/netdde /hurd/netdde
6498 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
6499 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
6501 </pre
></blockquote
></p
>
6503 <p
>After this, the machine had internet connectivity, and I could
6504 upgrade it and install the sysvinit packages from experimental and
6505 enable it as the default boot system in Hurd.
</p
>
6507 <p
>But before I did that, I set a password on the root user, as ssh is
6508 running on the machine it for ssh login to work a password need to be
6509 set. Also, note that a bug somewhere in openssh on Hurd block
6510 compression from working. Remember to turn that off on the client
6513 <p
>Run these commands as root to upgrade and test the new sysvinit
6516 <p
><blockquote
><pre
>
6517 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
6518 deb http://http.debian.net/debian/ experimental main
6521 apt-get dist-upgrade
6522 apt-get install -t experimental initscripts sysv-rc sysvinit \
6523 sysvinit-core sysvinit-utils
6524 update-alternatives --config runsystem
6525 </pre
></blockquote
></p
>
6527 <p
>To reboot after switching boot system, you have to use
6528 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
6529 yet a sysvinit process able to receive the signals from the normal
6530 'reboot
' command. After switching to sysvinit as the boot system,
6531 upgrading every package and rebooting, the network come up with DHCP
6532 after boot as it should, and the settrans/pkill hack mentioned at the
6533 start is no longer needed. But for some strange reason, there are no
6534 longer any login prompt in the virtual console, so I logged in using
6537 <p
>Note that there are some race conditions in Hurd making the boot
6538 fail some times. No idea what the cause is, but hope the Hurd porters
6539 figure it out. At least Justus said on IRC (#debian-hurd on
6540 irc.debian.org) that they are aware of the problem. A way to reduce
6541 the impact is to upgrade to the Hurd packages built by Justus by
6542 adding this repository to the machine:
</p
>
6544 <p
><blockquote
><pre
>
6545 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
6546 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
6548 </pre
></blockquote
></p
>
6550 <p
>At the moment the prebuilt virtual machine get some packages from
6551 http://ftp.debian-ports.org/debian, because some of the packages in
6552 unstable do not yet include the required patches that are lingering in
6553 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
6555 <p
><blockquote
><pre
>
6556 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
6557 i emacs - GNU Emacs editor (metapackage)
6558 i gdb - GNU Debugger
6559 i hurd-recommended - Miscellaneous translators
6560 i isc-dhcp-client - ISC DHCP client
6561 i isc-dhcp-common - common files used by all the isc-dhcp* packages
6562 i libc-bin - Embedded GNU C Library: Binaries
6563 i libc-dev-bin - Embedded GNU C Library: Development binaries
6564 i libc0.3 - Embedded GNU C Library: Shared libraries
6565 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
6566 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
6567 i multiarch-support - Transitional package to ensure multiarch compatibilit
6568 i A x11-common - X Window System (X.Org) infrastructure
6569 i xorg - X.Org X Window System
6570 i A xserver-xorg - X.Org X server
6571 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
6573 </pre
></blockquote
></p
>
6575 <p
>All in all, testing hurd has been an interesting experience. :)
6576 X.org did not work out of the box and I never took the time to follow
6577 the porters instructions to fix it. This time I was interested in the
6578 command line stuff.
<p
>
6583 <title>New chrpath release
0.16</title>
6584 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
6585 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
6586 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
6587 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
6588 find problems in C, C++ and Java code using static source code
6589 analysis. It can detect a lot of different problems, and is very
6590 useful to find memory and locking bugs in the error handling part of
6591 the source. The company behind it provide
6592 <a href=
"https://scan.coverity.com/
">check of free software projects as
6593 a community service
</a
>, and many hundred free software projects are
6594 already checked. A few days ago I decided to have a closer look at
6595 the Coverity system, and discovered that the
6596 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
6597 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
6598 projects I am involved with was already registered. But these are
6599 fairly big, and I would also like to have a small and easy project to
6600 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
6601 checking of the chrpath project
</a
>. It was
6602 added to the checker and discovered seven potential defects. Six of
6603 these were real, mostly resource
"leak
" when the program detected an
6604 error. Nothing serious, as the resources would be released a fraction
6605 of a second later when the program exited because of the error, but it
6606 is nice to do it right in case the source of the program some time in
6607 the future end up in a library. Having fixed all defects and added
6608 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
6609 mailing list for the chrpath developers
</a
>, I decided it was time to
6610 publish a new release. These are the release notes:
</p
>
6612 <p
>New in
0.16 released
2014-
01-
14:
</p
>
6616 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
6617 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
6618 <li
>Mention new project mailing list in the documentation.
</li
>
6623 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
6624 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
6625 project if something is wrong with the new release. The test suite
6626 did not discover any old errors, so if you find a new one, please also
6627 include a test suite check.
</p
>
6632 <title>New chrpath release
0.15</title>
6633 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
6634 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
6635 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
6636 <description><p
>After many years break from the package and a vain hope that
6637 development would be continued by someone else, I finally pulled my
6638 acts together this morning and wrapped up a new release of chrpath,
6639 the command line tool to modify the rpath and runpath of already
6640 compiled ELF programs. The update was triggered by the persistence of
6641 Isha Vishnoi at IBM, which needed a new config.guess file to get
6642 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
6643 is working on. I checked the
6644 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
6645 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
6646 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
6647 packages for interesting patches (failed to find the source from
6648 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
6649 These are the release notes:
</p
>
6651 <p
>New in
0.15 released
2013-
11-
24:
</p
>
6655 <li
>Updated config.sub and config.guess from the GNU project to work
6656 with newer architectures. Thanks to isha vishnoi for the heads
6659 <li
>Updated README with current URLs.
</li
>
6661 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
6662 Matthias Klose.
</li
>
6664 <li
>Added missing help for -k|--keepgoing option, using patch by
6665 Petr Machata found in Fedora.
</li
>
6667 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
6668 .dynamic is a NULL terminated string. Based on patch found in
6669 Fedora credited Axel Thimm and Christian Krause.
</li
>
6674 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
6675 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
6676 project if something is wrong with the new release. The test suite
6677 did not discover any old errors, so if you find a new one, please also
6678 include a testsuite check.
</p
>
6683 <title>Debian init.d boot script example for rsyslog
</title>
6684 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
6685 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
6686 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
6687 <description><p
>If one of the points of switching to a new init system in Debian is
6688 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
6689 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
6690 init.d scripts at all. Here is an example init.d script, ie a rewrite
6691 of /etc/init.d/rsyslog:
</p
>
6693 <p
><pre
>
6694 #!/lib/init/init-d-script
6697 # Required-Start: $remote_fs $time
6698 # Required-Stop: umountnfs $time
6699 # X-Stop-After: sendsigs
6700 # Default-Start:
2 3 4 5
6701 # Default-Stop:
0 1 6
6702 # Short-Description: enhanced syslogd
6703 # Description: Rsyslog is an enhanced multi-threaded syslogd.
6704 # It is quite compatible to stock sysklogd and can be
6705 # used as a drop-in replacement.
6707 DESC=
"enhanced syslogd
"
6708 DAEMON=/usr/sbin/rsyslogd
6709 </pre
></p
>
6711 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
6712 script was
137 lines, and the above is just
15 lines, most of it meta
6713 info/comments.
</p
>
6715 <p
>How to do this, you ask? Well, one create a new script
6716 /lib/init/init-d-script looking something like this:
6718 <p
><pre
>
6721 # Define LSB log_* functions.
6722 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
6723 # and status_of_proc is working.
6724 . /lib/lsb/init-functions
6727 # Function that starts the daemon/service
6733 #
0 if daemon has been started
6734 #
1 if daemon was already running
6735 #
2 if daemon could not be started
6736 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
6738 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
6741 # Add code here, if necessary, that waits for the process to be ready
6742 # to handle requests from services started subsequently which depend
6743 # on this one. As a last resort, sleep for some time.
6747 # Function that stops the daemon/service
6752 #
0 if daemon has been stopped
6753 #
1 if daemon was already stopped
6754 #
2 if daemon could not be stopped
6755 # other if a failure occurred
6756 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
6757 RETVAL=
"$?
"
6758 [
"$RETVAL
" =
2 ]
&& return
2
6759 # Wait for children to finish too if this is a daemon that forks
6760 # and if the daemon is only ever run from this initscript.
6761 # If the above conditions are not satisfied then add some other code
6762 # that waits for the process to drop all resources that could be
6763 # needed by services started subsequently. A last resort is to
6764 # sleep for some time.
6765 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
6766 [
"$?
" =
2 ]
&& return
2
6767 # Many daemons don
't delete their pidfiles when they exit.
6769 return
"$RETVAL
"
6773 # Function that sends a SIGHUP to the daemon/service
6777 # If the daemon can reload its configuration without
6778 # restarting (for example, when it is sent a SIGHUP),
6779 # then implement that here.
6781 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
6786 scriptbasename=
"$(basename $
1)
"
6787 echo
"SN: $scriptbasename
"
6788 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
6789 script=
"$
1"
6796 NAME=$(basename $DAEMON)
6797 PIDFILE=/var/run/$NAME.pid
6799 # Exit if the package is not installed
6800 #[ -x
"$DAEMON
" ] || exit
0
6802 # Read configuration variable file if it is present
6803 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
6805 # Load the VERBOSE setting and other rcS variables
6808 case
"$
1" in
6810 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
6812 case
"$?
" in
6813 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
6814 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
6818 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
6820 case
"$?
" in
6821 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
6822 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
6826 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
6828 #reload|force-reload)
6830 # If do_reload() is not implemented then leave this commented out
6831 # and leave
'force-reload
' as an alias for
'restart
'.
6833 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
6837 restart|force-reload)
6839 # If the
"reload
" option is implemented then remove the
6840 #
'force-reload
' alias
6842 log_daemon_msg
"Restarting $DESC
" "$NAME
"
6844 case
"$?
" in
6847 case
"$?
" in
6849 1) log_end_msg
1 ;; # Old process is still running
6850 *) log_end_msg
1 ;; # Failed to start
6860 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
6866 </pre
></p
>
6868 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
6869 lot. I did not really polish the approach, so it might not always
6870 work out of the box, but you get the idea. I did not try very hard to
6871 optimize it nor make it more robust either.
</p
>
6873 <p
>A better argument for switching init system in Debian than reducing
6874 the size of init scripts (which is a good thing to do anyway), is to
6875 get boot system that is able to handle the kernel events sensibly and
6876 robustly, and do not depend on the boot to run sequentially. The boot
6877 and the kernel have not behaved sequentially in years.
</p
>
6882 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
6883 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
6884 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
6885 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
6886 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
6887 remote display access is the preferred solution with oVirt and RedHat
6888 Enterprise Virtualization, and I was sad to discover the other day
6889 that the browser plugin needed to use these systems seamlessly was
6890 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
6891 for a package
</a
> was from
2012-
04-
10 with no progress since
6892 2013-
04-
01, so I decided to wrap up a package based on the great work
6893 from Cajus Pollmeier and put it in a collab-maint maintained git
6894 repository to get a package I could use. I would very much like
6895 others to help me maintain the package (or just take over, I do not
6896 mind), but as no-one had volunteered so far, I just uploaded it to
6897 NEW. I hope it will be available in Debian in a few days.
</p
>
6899 <p
>The source is now available from
6900 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
">http://anonscm.debian.org/gitweb/?p=collab-maint/spice-xpi.git;a=summary
</a
>.
</p
>
6905 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
6906 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
6907 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
6908 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
6909 <description><p
>The
6910 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
6911 program is a a very nice system to create virtual machine images. It
6912 create a image file, add a partition table, mount it and run
6913 debootstrap in the mounted directory to create a Debian system on a
6914 stick. Yesterday, I decided to try to teach it how to make images for
6915 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
6916 of a plan to simplify the build system for
6917 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
6918 project
</a
>. The FreedomBox project already uses vmdebootstrap for
6919 the virtualbox images, but its current build system made multistrap
6920 based system for Dreamplug images, and it is lacking support for
6921 Raspberry Pi.
</p
>
6923 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
6924 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
6925 code and adjusted it to be able to build armel images on my amd64
6926 Debian laptop. I ended up giving vmdebootstrap five new options,
6927 allowing me to replicate the image creation process I use to make
6928 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
6929 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
6930 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
6931 call debootstrap with --foreign and to copy the handler into the
6932 generated chroot before running the second stage. This allow
6933 vmdebootstrap to create armel images on an amd64 host. Next I added
6934 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
6935 fstype
</tt
> to teach it to create a separate /boot/ partition with the
6936 given file system type, allowing me to create an image with a vfat
6937 partition for the /boot/ stuff. I also added a
<tt
>--variant
6938 variant
</tt
> option to allow me to create smaller images without the
6939 Debian base system packages installed. Finally, I added an option
6940 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
6941 as a boot loader. It is not needed on the Raspberry Pi and probably
6942 most other non-x86 architectures. The changes were accepted by the
6943 upstream author of vmdebootstrap yesterday and today, and is now
6945 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
6946 upstream project page
</a
>.
</p
>
6948 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
6949 create a small script (the customize script) to add the non-free
6950 binary blob needed to boot the Raspberry Pi and the APT source
6953 <p
><pre
>
6955 set -e # Exit on first error
6956 rootdir=
"$
1"
6957 cd
"$rootdir
"
6958 cat
&lt;
&lt;EOF
> etc/apt/sources.list
6959 deb http://http.debian.net/debian/ jessie main contrib non-free
6961 # Install non-free binary blob needed to boot Raspberry Pi. This
6962 # install a kernel somewhere too.
6963 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
6964 -O $rootdir/usr/bin/rpi-update
6965 chmod a+x $rootdir/usr/bin/rpi-update
6966 mkdir -p $rootdir/lib/modules
6967 touch $rootdir/boot/start.elf
6968 chroot $rootdir rpi-update
6969 </pre
></p
>
6971 <p
>Next, fetch the latest vmdebootstrap script and call it like this
6972 to build the image:
</p
>
6975 sudo ./vmdebootstrap \
6978 --distribution jessie \
6979 --mirror http://http.debian.net/debian \
6988 --root-password raspberry \
6989 --hostname raspberrypi \
6990 --foreign /usr/bin/qemu-arm-static \
6991 --customize `pwd`/customize \
6993 --package git-core \
6994 --package binutils \
6995 --package ca-certificates \
6998 </pre
></p
>
7000 <p
>The list of packages being installed are the ones needed by
7001 rpi-update to make the image bootable on the Raspberry Pi, with the
7002 exception of netbase, which is needed by debootstrap to find
7003 /etc/hosts with the minbase variant. I really wish there was a way to
7004 set up an Raspberry Pi using only packages in the Debian archive, but
7005 that is not possible as far as I know, because it boots from the GPU
7006 using a non-free binary blob.
</p
>
7008 <p
>The build host need debootstrap, kpartx and qemu-user-static and
7009 probably a few others installed. I have not checked the complete
7010 build dependency list.
</p
>
7012 <p
>The resulting image will not use the hardware floating point unit
7013 on the Raspberry PI, because the armel architecture in Debian is not
7014 optimized for that use. So the images created will be a bit slower
7015 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
7020 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
7021 <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>
7022 <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>
7023 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
7024 <description><p
>The last few days I came across a few good causes that should get
7025 wider attention. I recommend signing and donating to each one of
7028 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
7029 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
7030 Women program which is a Google Summer of Code like initiative to get
7031 more women involved in free software. One debian sponsor has offered
7032 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
7033 earmarked
</a
> for this initiative. I donated a few minutes ago, and
7034 hope you will to. :)
</p
>
7036 <p
>And the Electronic Frontier Foundation just announced plans to
7037 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
7038 documentaries about the excessive spying
</a
> on every Internet user that
7039 take place these days, and their need to fund the work. I
've already
7040 donated. Are you next?
</p
>
7042 <p
>For my Norwegian audience, the organisation Studentenes og
7043 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7044 statement under the heading
7045 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
7046 Access
</a
> for those of us asking for more focus on open access in the
7047 Norwegian government. So far
499 signatures. I hope you will sign it
7053 <title>Videos about the Freedombox project - for inspiration and learning
</title>
7054 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
7055 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
7056 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
7057 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
7058 project
</a
> have been going on for a while, and have presented the
7059 vision, ideas and solution several places. Here is a little
7060 collection of videos of talks and presentation of the project.
</p
>
7064 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
7065 2,
5 minute marketing film
</a
> (Youtube)
</li
>
7067 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
7068 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
7070 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
7071 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7072 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
7073 (Youtube)
</li
>
7075 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
7076 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
7078 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
7079 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
7081 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
7082 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7083 York City in
2012</a
> (Youtube)
</li
>
7085 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
7086 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
7087 (Youtube)
</li
>
7089 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
7090 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
7092 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
7093 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
7095 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
7096 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7097 2013</a
> (Youtube)
</li
>
7101 <p
>A larger list is available from
7102 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
7103 Freedombox Wiki
</a
>.
</p
>
7105 <p
>On other news, I am happy to report that Freedombox based on Debian
7106 Jessie is coming along quite well, and soon both Owncloud and using
7107 Tor should be available for testers of the Freedombox solution. :) In
7108 a few weeks I hope everything needed to test it is included in Debian.
7109 The withsqlite package is already in Debian, and the plinth package is
7110 pending in NEW. The third and vital part of that puzzle is the
7111 metapackage/setup framework, which is still pending an upload. Join
7112 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
7113 (#freedombox on irc.debian.org)
</a
> and
7114 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7115 mailing list
</a
> if you want to help make this vision come true.
</p
>
7120 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
7121 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
7122 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
7123 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
7124 <description><p
>I was introduced to the
7125 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
7126 in
2010, when Eben Moglen presented his vision about serving the need
7127 of non-technical people to keep their personal information private and
7128 within the legal protection of their own homes. The idea is to give
7129 people back the power over their network and machines, and return
7130 Internet back to its intended peer-to-peer architecture. Instead of
7131 depending on a central service, the Freedombox will give everyone
7132 control over their own basic infrastructure.
</p
>
7134 <p
>I
've intended to join the effort since then, but other tasks have
7135 taken priority. But this summers nasty news about the misuse of trust
7136 and privilege exercised by the
"western
" intelligence gathering
7137 communities increased my eagerness to contribute to a point where I
7138 actually started working on the project a while back.
</p
>
7140 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
7141 Debian initiative
</a
> based on the vision from Eben Moglen, is to
7142 create a simple and cheap Debian based appliance that anyone can hook
7143 up in their home and get access to secure and private services and
7144 communication. The initial deployment platform have been the
7145 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
7146 which is a piece of hardware I do not own. So to be able to test what
7147 the current Freedombox setup look like, I had to come up with a way to install
7148 it on some hardware I do have access to. I have rewritten the
7149 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
7150 image build framework to use .deb packages instead of only copying
7151 setup into the boot images, and thanks to this rewrite I am able to
7152 set up any machine supported by Debian Wheezy as a Freedombox, using
7153 the previously mentioned deb (and a few support debs for packages
7154 missing in Debian).
</p
>
7156 <p
>The current Freedombox setup consist of a set of bootstrapping
7158 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
7159 and a administrative web interface
7160 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
7161 withsqlite), as well as a privacy enhancing proxy based on
7162 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
7163 (freedombox-privoxy). There is also a web/javascript based XMPP
7164 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
7165 trying (unsuccessfully so far) to talk to the XMPP server
7166 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
7167 web interface is pluggable, and the goal is to use it to enable OpenID
7168 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7169 this is really working yet, see
7170 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
7171 project TODO
</a
> for links to GIT repositories. Most of the code is
7172 on github at the moment. The HTTP proxy is operational out of the
7173 box, and the admin web interface can be used to add/remove plinth
7174 users. I
've not been able to do anything else with it so far, but
7175 know there are several branches spread around github and other places
7176 with lots of half baked features.
</p
>
7178 <p
>Anyway, if you want to have a look at the current state, the
7179 following recipes should work to give you a test machine to poke
7182 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
7186 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
7187 <li
>Boot from it, either as CD or USB stick.
</li
>
7188 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
7189 to the Debian installer:
<p
>
7190 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
7192 <li
>Answer the few language/region/password questions and pick disk to
7193 install on.
</li
>
7195 <li
>When the installation is finished and the machine have rebooted a
7196 few times, your Freedombox is ready for testing.
</li
>
7200 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
7204 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
7205 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
7206 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
7208 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
7209 </pre
></li
>
7210 <li
><p
>Run this as root:
</p
>
7212 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7215 apt-get install freedombox-setup
7216 /usr/lib/freedombox/setup
7217 </pre
></li
>
7218 <li
>Reboot into your freshly created Freedombox.
</li
>
7222 <p
>You can test it on other architectures too, but because the
7223 freedombox-privoxy package is binary, it will only work as intended on
7224 the architectures where I have had time to build the binary and put it
7225 in my APT repository. But do not let this stop you. It is only a
7226 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
7228 <p
>Note that by default Freedombox is a DHCP server on the
7229 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
7230 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
7231 disable
</tt
>" as root.
</p
>
7233 <p
>Please let me know if this works for you, or if you have any
7234 problems. We gather on the IRC channel
7235 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
7236 irc.debian.org and the
7237 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
7238 mailing list
</a
>.
</p
>
7240 <p
>Once you get your freedombox operational, you can visit
7241 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
7242 welcome screen (dead end - do not be surprised if you are unable to
7243 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
7244 to look at the rest of plinth. The default user is
'admin
' and the
7245 default password is
'secret
'.
</p
>
7250 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
7251 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
7252 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
7253 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
7254 <description><p
>Earlier, I reported about
7255 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
7256 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
7257 told by IBM that the original disk should be thrown away. And as
7258 there no longer was a problem if I bricked the firmware, I decided
7259 today to try to install Intel firmware to replace the Lenovo firmware
7260 currently on the disk.
</p
>
7262 <p
>I searched the Intel site for firmware, and found
7263 <a href=
"https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y
&ProdId=
3472&DwnldID=
18363&ProductFamily=Solid-State+Drives+and+Caching
&ProductLine=Intel%c2%ae+High+Performance+Solid-State+Drive
&ProductProduct=Intel%c2%ae+SSD+
520+Series+(
180GB%
2c+
2.5in+SATA+
6Gb%
2fs%
2c+
25nm%
2c+MLC)
&lang=eng
">issdfut_2.0
.4.iso
</a
>
7264 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
7265 according to the site should contain the latest firmware for SSD
7266 disks. I inserted the broken disk in one of my spare laptops and
7267 booted the ISO from a USB stick. The disk was recognized, but the
7268 program claimed the newest firmware already were installed and refused
7269 to insert any Intel firmware. So no change, and the disk is still
7270 unable to handle write load. :( I guess the only way to get them
7271 working would be if Lenovo releases new firmware. No idea how likely
7272 that is. Anyway, just blogging about this test for completeness. I
7273 got a working Samsung disk, and see no point in spending more time on
7274 the broken disks.
</p
>
7279 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
7280 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
7281 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
7282 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
7283 <description><p
>Today I switched to
7284 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
7285 new laptop
</a
>. I
've previously written about the problems I had with
7286 my new Thinkpad X230, which was delivered with an
7287 <a href=
"http://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
">180
7288 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
7289 sustained writes. My hardware supplier have been very forthcoming in
7290 trying to find a solution, and after first trying with another
7291 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
7292 disk instead to fix it once and for all. The Samsung disk survived
7293 the installation of Debian with encrypted disks (filling the disk with
7294 random data during installation killed the first two), and I thus
7295 decided to trust it with my data. I have installed it as a Debian Edu
7296 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
7297 server at home using Kerberos and LDAP, and will use it as my work
7298 station from now on.
</p
>
7300 <p
>As this is a solid state disk with no moving parts, I believe the
7301 Debian Wheezy default installation need to be tuned a bit to increase
7302 performance and increase life time of the disk. The Linux kernel and
7303 user space applications do not yet adjust automatically to such
7304 environment. To make it easier for my self, I created a draft Debian
7305 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
7306 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
7307 for the ssd-setup package
</a
> is available from collab-maint, and it
7308 is set up to adjust the setup of the machine by just installing the
7309 package. If there is any non-SSD disk in the machine, the package
7310 will refuse to install, as I did not try to write any logic to sort
7311 file systems in SSD and non-SSD file systems.
</p
>
7313 <p
>I consider the package a draft, as I am a bit unsure how to best
7314 set up Debian Wheezy with an SSD. It is adjusted to my use case,
7315 where I set up the machine with one large encrypted partition (in
7316 addition to /boot), put LVM on top of this and set up partitions on
7317 top of this again. See the README file in the package source for the
7318 references I used to pick the settings. At the moment these
7319 parameters are tuned:
</p
>
7323 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
7324 (adding discard to /etc/crypttab)
</li
>
7326 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
7327 this case a cryptsetup partition) by changing issue_discards from
7328 0 to
1 in /etc/lvm/lvm.conf.
</li
>
7330 <li
>Set relatime as a file system option for ext3 and ext4 file
7333 <li
>Tell swap to use TRIM commands by adding
'discard
' to
7334 /etc/fstab.
</li
>
7336 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
7338 <li
>Run fstrim on every ext3 and ext4 file system every night (from
7339 cron.daily).
</li
>
7341 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
7342 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
7346 <p
>During installation, I cancelled the part where the installer fill
7347 the disk with random data, as this would kill the SSD performance for
7348 little gain. My goal with the encrypted file system is to ensure
7349 those stealing my laptop end up with a brick and not a working
7350 computer. I have no hope in keeping the really resourceful people
7351 from getting the data on the disk (see
7352 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
7353 Thus I concluded that adding the discard option to crypttab is the
7354 right thing to do.
</p
>
7356 <p
>I considered using the noop I/O scheduler, as several recommended
7357 it for SSD, but others recommended deadline and a benchmark I found
7358 indicated that deadline might be better for interactive use.
</p
>
7360 <p
>I also considered using the
'discard
' file system option for ext3
7361 and ext4, but read that it would give a performance hit ever time a
7362 file is removed, and thought it best to that that slowdown once a day
7363 instead of during my work.
</p
>
7365 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
7366 this is already done by Debian Edu.
</p
>
7368 <p
>I have not yet started on the user space tuning. I expect
7369 iceweasel need some tuning, and perhaps other applications too, but
7370 have not yet had time to investigate those parts.
</p
>
7372 <p
>The package should work on Ubuntu too, but I have not yet tested it
7375 <p
>As for the answer to the question in the title of this blog post,
7376 as far as I know, the only solution I know about is to replace the
7377 disk. It might be possible to flash it with Intel firmware instead of
7378 the Lenovo firmware. But I have not tried and did not want to do so
7379 without approval from Lenovo as I wanted to keep the warranty on the
7380 disk until a solution was found and they wanted the broken disks
7386 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
7387 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
7388 <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>
7389 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
7390 <description><p
>A few days ago, I wrote about
7391 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
7392 problems I experienced with my new X230 and its SSD disk
</a
>, which
7393 was dying during installation because it is unable to cope with
7394 sustained write. My supplier is in contact with
7395 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
7396 replacement disk to try to fix the problem. They decided to send an
7397 identical model, so my hopes for a permanent fix was slim.
</p
>
7399 <p
>Anyway, today I got the replacement disk and tried to install
7400 Debian Edu Wheezy with encrypted disk on it. The new disk have the
7401 same firmware version as the original. This time my hope raised
7402 slightly as the installation progressed, as the original disk used to
7403 die after
4-
7% of the disk was written to, while this time it kept
7404 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
7405 died again and I was back on square one. I still do not have a new
7406 laptop with a disk I can trust. I can not live with a disk that might
7407 lock up when I download a new
7408 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
7409 other large files. I look forward to hearing from my supplier with
7410 the next proposal from Lenovo.
</p
>
7412 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
7413 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
7414 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
7415 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
7416 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
7417 P/N
45N8295, P0C38732.
</p
>
7419 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
7420 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
7421 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
7422 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
7423 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
7424 P/N
45N8295, P0C38732.
</p
>
7426 <p
>The only difference is in the first number (serial number?), ISN,
7427 SA, date and WNPP values. Mentioning all the details here in case
7428 someone is able to use the information to find a way to identify the
7429 failing disk among working ones (if any such working disk actually
7435 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
7436 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
7437 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
7438 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
7439 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
7440 Debian Edu developer gathering and Debian and Ubuntu bug squashing
7441 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
7442 member assosiation NUUG
</a
> and
7443 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
7444 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
7445 Bitraf
</a
>.
</p
>
7447 <p
>It starts
10:
00 and continue until late evening. Everyone is
7448 welcome, and there is no fee to participate. There is on the other
7449 hand limited space, and only room for
30 people. Please put your name
7450 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
7451 wiki page
</a
> if you plan to join us.
</p
>
7456 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
7457 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
7458 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
7459 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
7460 <description><p
>Half a year ago, I reported that I had to find a
7461 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
7462 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
7463 time to spend on it, and it took a while to find a model I believe
7464 will do the job, but two days ago the replacement finally arrived. I
7466 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
7467 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
7468 a roaming workstation, and it seemed to work flawlessly. But my
7469 second installation with encrypted disk was not as successful. More
7470 on that below.
</p
>
7472 <p
>I had a hard time trying to track down a good laptop, as my most
7473 important requirements (robust and with a good keyboard) are never
7474 listed in the feature list. But I did get good help from the search
7475 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
7476 allowed me to limit the list of interesting laptops based on my other
7477 requirements. A bit surprising that SSD disk are not disks according
7478 to that search interface, so I had to drop specifying the number of
7479 disks from my search parameters. I also asked around among friends to
7480 get their impression on keyboards and robustness.
</p
>
7482 <p
>So the new laptop arrived, and it is quite a lot wider than the
7483 X41. I am not quite convinced about the keyboard, as it is
7484 significantly wider than my old keyboard, and I have to stretch my
7485 hand a lot more to reach the edges. But the key response is fairly
7486 good and the individual key shape is fairly easy to handle, so I hope
7487 I will get used to it. My old X40 was starting to fail, and I really
7488 needed a new laptop now. :)
</p
>
7490 <p
>Turning off the touch pad was simple. All it took was a quick
7491 visit to the BIOS during boot it disable it.
</p
>
7493 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
7494 lock up during load. And this happen when installing Debian Wheezy
7495 with encrypted disk, while the disk is being filled with random data.
7496 I also tested to install Ubuntu Raring, and it happen there too if I
7497 reenable the code to fill the disk with random data (it is disabled by
7498 default in Ubuntu). And the bug with is already known. It was
7499 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
7500 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
7501 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
7502 kernel developers as
7503 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
7504 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
7505 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
7506 Lenovo forums, both for
7507 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
7508 2012-
11-
10</a
> and for
7509 <a href=
"http://forums.lenovo.com/t5/X-Series-ThinkPad-Laptops/x230-SATA-errors-with-
180GB-Intel-
520-SSD-under-heavy-write-load/m-p/
1068147">X230
7510 03-
20-
2013</a
>. The problem do not only affect installation. The
7511 reports state that the disk lock up during use if many writes are done
7512 on the disk, so it is much no use to work around the installation
7513 problem and end up with a computer that can lock up at any moment.
7515 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
7516 available
</a
> that will lock up the hard drive after running a few
7517 minutes by writing to a file.
</p
>
7519 <p
>I
've contacted my supplier and asked how to handle this, and after
7520 contacting PCHELP Norway (request
01D1FDP) which handle support
7521 requests for Lenovo, his first suggestion was to upgrade the disk
7522 firmware. Unfortunately there is no newer firmware available from
7523 Lenovo, as my disk already have the most recent one (version LF1i). I
7524 hope to hear more from him today and hope the problem can be
7530 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
7531 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
7532 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
7533 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
7534 <description><p
>Half a year ago, I reported that I had to find a replacement for my
7535 trusty old Thinkpad X41. Unfortunately I did not have much time to
7536 spend on it, but today the replacement finally arrived. I ended up
7537 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
7538 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
7539 Wheezy as a roaming workstation, and it worked flawlessly. As I write
7540 this, it is installing what I hope will be a more final installation,
7541 with a encrypted hard drive to ensure any dope head stealing it end up
7542 with an expencive door stop.
</p
>
7544 <p
>I had a hard time trying to track down a good laptop, as my most
7545 important requirements (robust and with a good keyboard) are never
7546 listed in the feature list. But I did get good help from the search
7547 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
7548 allowed me to limit the list of interesting laptops based on my other
7549 requirements. A bit surprising that SSD disk are not disks, so I had
7550 to drop number of disks from my search parameters.
</p
>
7552 <p
>I am not quite convinced about the keyboard, as it is significantly
7553 wider than my old keyboard, and I have to stretch my hand a lot more
7554 to reach the edges. But the key response is fairly good and the
7555 individual key shape is fairly easy to handle, so I hope I will get
7556 used to it. My old X40 was starting to fail, and I really needed a
7557 new laptop now. :)
</p
>
7559 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
7564 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
7565 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
7566 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
7567 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
7568 <description><p
>It annoys me when the computer fail to do automatically what it is
7569 perfectly capable of, and I have to do it manually to get things
7570 working. One such task is to find out what firmware packages are
7571 needed to get the hardware on my computer working. Most often this
7572 affect the wifi card, but some times it even affect the RAID
7573 controller or the ethernet card. Today I pushed version
0.4 of the
7574 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
7575 including a new script isenkram-autoinstall-firmware handling the
7576 process of asking all the loaded kernel modules what firmware files
7577 they want, find debian packages providing these files and install the
7578 debian packages. Here is a test run on my laptop:
</p
>
7580 <p
><pre
>
7581 # isenkram-autoinstall-firmware
7582 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
7583 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
7584 info: locating packages with the requested firmware files
7585 info: Updating APT sources after adding non-free APT source
7586 info: trying to install firmware-ipw2x00
7589 Preconfiguring packages ...
7590 Selecting previously deselected package firmware-ipw2x00.
7591 (Reading database ...
259727 files and directories currently installed.)
7592 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
7593 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
7595 </pre
></p
>
7597 <p
>When all the requested firmware is present, a simple message is
7598 printed instead:
</p
>
7600 <p
><pre
>
7601 # isenkram-autoinstall-firmware
7602 info: did not find any firmware files requested by loaded kernel modules. exiting
7604 </pre
></p
>
7606 <p
>It could use some polish, but it is already working well and saving
7607 me some time when setting up new machines. :)
</p
>
7609 <p
>So, how does it work? It look at the set of currently loaded
7610 kernel modules, and look up each one of them using modinfo, to find
7611 the firmware files listed in the module meta-information. Next, it
7612 download the Contents file from a nearby APT mirror, and search for
7613 the firmware files in this file to locate the package with the
7614 requested firmware file. If the package is in the non-free section, a
7615 non-free APT source is added and the package is installed using
7616 <tt
>apt-get install
</tt
>. The end result is a slightly better working
7619 <p
>I hope someone find time to implement a more polished version of
7620 this script as part of the hw-detect debian-installer module, to
7621 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
7622 #
655507</a
>. There really is no need to insert USB sticks with
7623 firmware during a PXE install when the packages already are available
7624 from the nearby Debian mirror.
</p
>
7629 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
7630 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
7631 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
7632 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
7633 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
7634 the screen just turn black when Linux boot, either during installation
7635 or on first boot from the hard disk. I
've seen it once in a while the
7636 last few years, but only recently understood the cause. I
've seen it
7637 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
7638 The reason seem to be in the wiring of some laptops. The system to
7639 control the screen background light is inverted, so when Linux try to
7640 turn the brightness fully on, it end up turning it off instead. I do
7641 not know which Linux drivers are affected, but this post is about the
7642 i915 driver used by the
7643 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
7644 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
7646 <p
>The problem can be worked around two ways. Either by adding
7647 i915.invert_brightness=
1 as a kernel option, or by adding a file in
7648 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
7649 option when it load the i915 kernel module. On Debian and Ubuntu, it
7650 can be done by running these commands as root:
</p
>
7653 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
7654 update-initramfs -u -k all
7657 <p
>Since March
2012 there is
7658 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
7659 mechanism in the Linux kernel
</a
> to tell the i915 driver which
7660 hardware have this problem, and get the driver to invert the
7661 brightness setting automatically. To use it, one need to add a row in
7662 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
7663 intel_quirks array
</a
> in the driver source
7664 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
7665 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
7666 number (vendor number
8086 is assumed) and subdevice vendor and device
7669 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
7670 -vvnn
</tt
> for the video card in question:
</p
>
7672 <p
><pre
>
7673 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
7674 3rd Gen Core processor Graphics Controller [
8086:
0156] \
7675 (rev
09) (prog-if
00 [VGA controller])
7676 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
7677 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
7678 ParErr- Stepping- SE RR- FastB2B- DisINTx+
7679 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
7680 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
7682 Interrupt: pin A routed to IRQ
42
7683 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
7684 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
7685 Region
4: I/O ports at
4000 [size=
64]
7686 Expansion ROM at
<unassigned
> [disabled]
7687 Capabilities:
<access denied
>
7688 Kernel driver in use: i915
7689 </pre
></p
>
7691 <p
>The resulting intel_quirks entry would then look like this:
</p
>
7693 <p
><pre
>
7694 struct intel_quirk intel_quirks[] = {
7696 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
7697 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
7700 </pre
></p
>
7702 <p
>According to the kernel module instructions (as seen using
7703 <tt
>modinfo i915
</tt
>), information about hardware needing the
7704 invert_brightness flag should be sent to the
7705 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
7706 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
7707 developers. But my email about the laptop sent
2013-
06-
03 have not
7709 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
7710 web archive for the mailing list
</a
>, so I suspect they do not accept
7711 emails from non-subscribers. Because of this, I sent my patch also to
7712 the Debian bug tracking system instead as
7713 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
7714 sure the patch is not lost.
</p
>
7716 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
7717 with this problem working properly with Linux. If you use Gnome, your
7718 worries should be over at this point. But if you use KDE, there is
7719 something in KDE ignoring the invert_brightness setting and turning on
7720 the screen during login. I
've reported it to Debian as
7721 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
7722 have no idea yet how to figure out exactly what subsystem is doing
7723 this. Perhaps you can help? Perhaps you know what the Gnome
7724 developers did to handle this, and this can give a clue to the KDE
7725 developers? Or you know where in KDE the screen brightness is changed
7726 during login? If so, please update the BTS report (or get in touch if
7727 you do not know how to update BTS).
</p
>
7729 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
7730 acpi_backlight=vendor, to disable ACPI backlight support completely,
7731 as the ACPI information on the machine is trash and it is better to
7732 leave it to the intel video driver to control the screen
7733 backlight.
</p
>
7738 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
7739 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
7740 <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>
7741 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
7742 <description><p
>Two days ago, I asked
7743 <a href=
"http://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
">how
7744 I could install Linux on a Packard Bell EasyNote LV computer
7745 preinstalled with Windows
8</a
>. I found a solution, but am horrified
7746 with the obstacles put in the way of Linux users on a laptop with UEFI
7747 and Windows
8.
</p
>
7749 <p
>I never found out if the cause of my problems were the use of UEFI
7750 secure booting or fast boot. I suspect fast boot was the problem,
7751 causing the firmware to boot directly from HD without considering any
7752 key presses and alternative devices, but do not know UEFI settings
7753 enough to tell.
</p
>
7755 <p
>There is no way to install Linux on the machine in question without
7756 opening the box and disconnecting the hard drive! This is as far as I
7757 can tell, the only way to get access to the firmware setup menu
7758 without accepting the Windows
8 license agreement. I am told (and
7759 found description on how to) that it is possible to configure the
7760 firmware setup once booted into Windows
8. But as I believe the terms
7761 of that agreement are completely unacceptable, accepting the license
7762 was never an alternative. I do not enter agreements I do not intend
7763 to follow.
</p
>
7765 <p
>I feared I had to return the laptops and ask for a refund, and
7766 waste many hours on this, but luckily there was a way to get it to
7767 work. But I would not recommend it to anyone planning to run Linux on
7768 it, and I have become sceptical to Windows
8 certified laptops. Is
7769 this the way Linux will be forced out of the market place, by making
7770 it close to impossible for
"normal
" users to install Linux without
7771 accepting the Microsoft Windows license terms? Or at least not
7772 without risking to loose the warranty?
</p
>
7774 <p
>I
've updated the
7775 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
7776 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
7777 do not have to struggle as much as I did to get Linux into the
7780 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
7781 Michael Tokarev and others for feedback and ideas.
</p
>
7786 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
7787 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
7788 <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>
7789 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
7790 <description><p
>I
've run into quite a problem the last few days. I bought three
7791 new laptops for my parents and a few others. I bought Packard Bell
7792 Easynote LV to run Kubuntu on and use as their home computer. But I
7793 am completely unable to figure out how to install Linux on it. The
7794 computer is preinstalled with Windows
8, and I suspect it uses UEFI
7795 instead of a BIOS to boot.
</p
>
7797 <p
>The problem is that I am unable to get it to PXE boot, and unable
7798 to get it to boot the Linux installer from my USB stick. I have yet
7799 to try the DVD install, and still hope it will work. when I turn on
7800 the computer, there is no information on what buttons to press to get
7801 the normal boot menu. I expect to get some boot menu to select PXE or
7802 USB stick booting. When booting, it first ask for the language to
7803 use, then for some regional settings, and finally if I will accept the
7804 Windows
8 terms of use. As these terms are completely unacceptable to
7805 me, I have no other choice but to turn off the computer and try again
7806 to get it to boot the Linux installer.
</p
>
7808 <p
>I have gathered my findings so far on a Linlap page about the
7809 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
7810 EasyNote LV
</a
> model. If you have any idea how to get Linux
7811 installed on this machine, please get in touch or update that wiki
7812 page. If I can
't find a way to install Linux, I will have to return
7813 the laptop to the seller and find another machine for my parents.
</p
>
7815 <p
>I wonder, is this the way Linux will be forced out of the market
7816 using UEFI and
"secure boot
" by making it impossible to install Linux
7817 on new Laptops?
</p
>
7822 <title>How to transform a Debian based system to a Debian Edu installation
</title>
7823 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
7824 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
7825 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
7826 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
7827 an operating system based on Debian intended for use in schools. It
7828 contain a turn-key solution for the computer network provided to
7829 pupils in the primary schools. It provide both the central server,
7830 network boot servers and desktop environments with heaps of
7831 educational software. The project was founded almost
12 years ago,
7832 2001-
07-
02. If you want to support the project, which is in need for
7833 cash to fund developer gatherings and other project related activity,
7834 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
7835 donate some money
</a
>.
7837 <p
>A topic that come up again and again on the Debian Edu mailing
7838 lists and elsewhere, is the question on how to transform a Debian or
7839 Ubuntu installation into a Debian Edu installation. It isn
't very
7840 hard, and last week I wrote a script to replicate the steps done by
7841 the Debian Edu installer.
</p
>
7843 <p
>The script,
7844 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/branches/wheezy/debian-edu-config/share/debian-edu-config/tools/debian-edu-bless?view=markup
">debian-edu-bless
<a/
>
7845 in the debian-edu-config package, will go through these six steps and
7846 transform an existing Debian Wheezy or Ubuntu (untested) installation
7847 into a Debian Edu Workstation:
</p
>
7851 <li
>Add skolelinux related APT sources.
</li
>
7852 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
7853 <li
>Install debian-edu-install to load preseeding values and pull in
7854 our configuration.
</li
>
7855 <li
>Preseed debconf database with profile setup in
7856 /etc/debian-edu/config, and run tasksel to install packages
7857 according to the profile specified in the config above,
7858 overriding some of the Debian automation machinery.
</li
>
7859 <li
>Run debian-edu-cfengine-D installation to configure everything
7860 that could not be done using preseeding.
</li
>
7861 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
7865 <p
>There are some steps in the Debian Edu installation that can not be
7866 replicated like this. Disk partitioning and LVM setup, for example.
7867 So this script just assume there is enough disk space to install all
7868 the needed packages.
</p
>
7870 <p
>The script was created to help a Debian Edu student working on
7871 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
7872 Debian Edu client, and using it he can take the existing
7873 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
7874 transform it into a fully functioning Debian Edu Workstation (or
7875 Roaming Workstation, or whatever :).
</p
>
7877 <p
>The default setting in the script is to create a KDE Workstation.
7878 If a LXDE based Roaming workstation is wanted instead, modify the
7879 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
7881 <p
><pre
>
7882 PROFILE=
"Roaming-Workstation
"
7883 DESKTOP=
"lxde
"
7884 </pre
></p
>
7886 <p
>The script could even become useful to set up Debian Edu servers in
7887 the cloud, by starting with a virtual Debian installation at some
7888 virtual hosting service and setting up all the services on first
7894 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
7895 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
7896 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
7897 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
7898 <description><P
>In January,
7899 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
7900 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
7901 channel #debian-lego
</a
>, for those of us in the Debian and Linux
7902 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
7903 marvellous construction system from Denmark. We also created
7904 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
7905 a place to take notes and write down our plans and hopes. And several
7906 people showed up to help. I was very happy to see the effect of my
7907 call. Since the small start, we have a debtags tag
7908 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
7909 tag for LEGO related packages, and now count
10 packages related to
7910 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
7912 <p
><table
>
7913 <tr
><td
><a href=
"http://packages.qa.debian.org/brickos
">brickos
</a
></td
><td
>alternative OS for LEGO Mindstorms RCX. Supports development in C/C++
</td
></tr
>
7914 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
7915 <tr
><td
><a href=
"http://packages.qa.debian.org/libnxt
">libnxt
</a
></td
><td
>utility library for talking to the LEGO Mindstorms NX
</td
></tr
>
7916 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
7917 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
7918 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
7919 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt
">python-nxt
</a
></td
><td
>python driver/interface/wrapper for the Lego Mindstorms NXT robot
</td
></tr
>
7920 <tr
><td
><a href=
"http://packages.qa.debian.org/python-nxt-filer
">python-nxt-filer
</a
></td
><td
>simple GUI to manage files on a LEGO Mindstorms NXT
</td
></tr
>
7921 <tr
><td
><a href=
"http://packages.qa.debian.org/scratch
">scratch
</a
></td
><td
>easy to use programming environment for ages
8 and up
</td
></tr
>
7922 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
7923 </table
></p
>
7925 <p
>Some of these are available in Wheezy, and all but one are
7926 currently available in Jessie/testing. leocad is so far only
7927 available in experimental.
</p
>
7929 <p
>If you care about LEGO in Debian, please join us on IRC and help
7930 adding the rest of the great free software tools available on Linux
7931 for LEGO designers.
</p
>
7936 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
7937 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
7938 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
7939 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
7940 <description><p
>When I woke up this morning, I was very happy to see that the
7941 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
7942 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
7943 Debian release, and I expect to move my machines at home over to it fairly
7946 <p
>The new debian release contain heaps of new stuff, and one program
7947 in particular make me very happy to see included. The
7948 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
7949 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
7950 included for the first time. Alongside similar programs like
7951 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
7952 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
7953 it allow for visual programming where syntax errors can not happen,
7954 and a friendly programming environment for learning to control the
7955 computer. Scratch will also be included in the next release of Debian
7958 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
7959 Edu/Skolelinux release too. The
7960 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
7961 alpha release
</a
> went out last week, and the next should soon
7967 <title>Isenkram
0.2 finally in the Debian archive
</title>
7968 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
7969 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
7970 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
7971 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
7972 package
</a
> finally made it into the archive, after lingering in NEW
7973 for many months. I uploaded it to the Debian experimental suite
7974 2013-
01-
27, and today it was accepted into the archive.
</p
>
7976 <p
>Isenkram is a system for suggesting to users what packages to
7977 install to work with a pluggable hardware device. The suggestion pop
7978 up when the device is plugged in. For example if a Lego Mindstorm NXT
7979 is inserted, it will suggest to install the program needed to program
7980 the NXT controller. Give it a go, and report bugs and suggestions to
7986 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
7987 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
7988 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
7989 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
7990 <description><p
>My
7991 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
7992 bitcoin related blog post
</a
> mentioned that the new
7993 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
7994 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
7995 2013-
01-
19, and have been available in unstable since then. It was
7996 automatically copied to Ubuntu, and is available in their Raring
7997 version too.
</p
>
7999 <p
>But there is a strange problem with the build that block this new
8000 version from being available on the i386 and kfreebsd-i386
8001 architectures. For some strange reason, the autobuilders in Debian
8002 for these architectures fail to run the test suite on these
8003 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
8004 We are so far unable to reproduce it when building it manually, and
8005 no-one have been able to propose a fix. If you got an idea what is
8006 failing, please let us know via the BTS.
</p
>
8008 <p
>One feature that is annoying me with of the bitcoin client, because
8009 I often run low on disk space, is the fact that the client will exit
8010 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
8011 #
696715</a
>). So make sure you have enough disk space when you run
8014 <p
>As usual, if you use bitcoin and want to show your support of my
8015 activities, please send Bitcoin donations to my address
8016 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
8021 <title>Welcome to the world, Isenkram!
</title>
8022 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
8023 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
8024 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
8025 <description><p
>Yesterday, I
8026 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
8027 for testers
</a
> for my prototype for making Debian better at handling
8028 pluggable hardware devices, which I
8029 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
8030 out to create
</a
> earlier this month. Several valuable testers showed
8031 up, and caused me to really want to to open up the development to more
8032 people. But before I did this, I want to come up with a sensible name
8033 for this project. Today I finally decided on a new name, and I have
8034 renamed the project from hw-support-handler to this new name. In the
8035 process, I moved the source to git and made it available as a
8036 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
8037 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
8038 To fetch and build the latest version of the source, use
</p
>
8041 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8042 cd isenkram
&& git-buildpackage -us -uc
8045 <p
>I have not yet adjusted all files to use the new name yet. If you
8046 want to hack on the source or improve the package, please go ahead.
8047 But please talk to me first on IRC or via email before you do major
8048 changes, to make sure we do not step on each others toes. :)
</p
>
8050 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
8051 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8052 stuff, in other words. I
've been told it is the Norwegian variant of
8053 the German word eisenkram, for those that are familiar with that
8056 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
8057 instructions, to avoid confusing people with an error from the signing
8060 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
8061 clone argument to avoid the need for authentication.
</p
>
8066 <title>First prototype ready making hardware easier to use in Debian
</title>
8067 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
8068 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
8069 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
8070 <description><p
>Early this month I set out to try to
8071 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
8072 the Debian support for pluggable hardware devices
</a
>. Now my
8073 prototype is working, and it is ready for a larger audience. To test
8075 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
8076 from the Debian Edu subversion repository
</a
>, build and install the
8077 package. You might have to log out and in again activate the
8078 autostart script.
</p
>
8080 <p
>The design is simple:
</p
>
8084 <li
>Add desktop entry in /usr/share/autostart/ causing a program
8085 hw-support-handlerd to start when the user log in.
</li
>
8087 <li
>This program listen for kernel events about new hardware (directly
8088 from the kernel like udev does), not using HAL dbus events as I
8089 initially did.
</li
>
8091 <li
>When new hardware is inserted, look up the hardware modalias in
8092 the APT database, a database
8093 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
8094 via HTTP
</a
> and a database available as part of the package.
</li
>
8096 <li
>If a package is mapped to the hardware in question, the package
8097 isn
't installed yet and this is the first time the hardware was
8098 plugged in, show a desktop notification suggesting to install the
8099 package or packages.
</li
>
8101 <li
>If the user click on the
'install package now
' button, ask
8102 aptdaemon via the PackageKit API to install the requrired package.
</li
>
8104 <li
>aptdaemon ask for root password or sudo password, and install the
8105 package while showing progress information in a window.
</li
>
8109 <p
>I still need to come up with a better name for the system. Here
8110 are some screen shots showing the prototype in action. First the
8111 notification, then the password request, and finally the request to
8112 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
8114 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
8115 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
8116 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
8117 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
8118 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
8120 <p
>The prototype still need to be improved with longer timeouts, but
8121 is already useful. The database of hardware to package mappings also
8122 need more work. It is currently compatible with the Ubuntu way of
8123 storing such information in the package control file, but could be
8124 changed to use other formats instead or in addition to the current
8125 method. I
've dropped the use of discover for this mapping, as the
8126 modalias approach is more flexible and easier to use on Linux as long
8127 as the Linux kernel expose its modalias strings directly.
</p
>
8129 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
8130 here is the command required to check out and build the source: Use
8131 '<tt
>svn checkout
8132 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8133 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
8134 devscripts package.
</p
>
8136 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
8137 renamed to Isenkram and the source moved from the Debian Edu
8138 subversion repository to a Debian collab-maint git repository. See
8139 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
8140 instructions
</a
> for details.
</p
>
8145 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
8146 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
8147 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
8148 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
8149 <description><p
>This Christmas my trusty old laptop died. It died quietly and
8150 suddenly in bed. With a quiet whimper, it went completely quiet and
8151 black. The power button was no longer able to turn it on. It was a
8152 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8153 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8154 Compaq I had before that. Now I need to find a replacement. To keep
8155 going during Christmas, I moved the one year old SSD disk to my old
8156 X40 where it fitted (only one I had left that could use it), but it is
8157 not a durable solution.
8159 <p
>My laptop needs are fairly modest. This is my wishlist from when I
8160 got a new one more than
10 years ago. It still holds true.:)
</p
>
8164 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
8165 than A4).
</li
>
8166 <li
>Robust, it will be in my backpack every day.
</li
>
8167 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
8168 <li
>Long battery life time. Preferable a week.
</li
>
8169 <li
>Internal WIFI network card.
</li
>
8170 <li
>Internal Twisted Pair network card.
</li
>
8171 <li
>Some USB slots (
2-
3 is plenty)
</li
>
8172 <li
>Good keyboard - similar to the Thinkpad.
</li
>
8173 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
8175 <li
>Hardware supported by Debian Stable, ie the default kernel and
8176 X.org packages.
</li
>
8177 <li
>Quiet, preferably fan free (or at least not using the fan most of
8182 <p
>You will notice that there are no RAM and CPU requirements in the
8183 list. The reason is simply that the specifications on laptops the
8184 last
10-
15 years have been sufficient for my needs, and I have to look
8185 at other features to choose my laptop. But are there still made as
8186 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8187 robust, and Thinkpads seem to be heading in the wrong direction since
8188 Lenovo took over. But I
've been told that X220 and X1 Carbon might
8189 still be useful.
</p
>
8191 <p
>Perhaps I should rethink my needs, and look for a pad with an
8192 external keyboard? I
'll have to check the
8193 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
8194 well-supported laptops, or perhaps just buy one preinstalled from one
8195 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
8196 Pre-loaded site
</a
>.
</p
>
8201 <title>How to find a browser plugin supporting a given MIME type
</title>
8202 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
8203 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
8204 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
8205 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
8206 install to get support for a given MIME type. Thanks to
8207 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
8208 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
8209 Unfortunately, not very many packages provide the needed meta
8210 information, Anyway, here is a small script to look up all browser
8211 plugin packages announcing ther MIME support using this specification:
</p
>
8217 def pkgs_handling_mimetype(mimetype):
8222 version = pkg.candidate
8224 version = pkg.installed
8227 record = version.record
8228 if not record.has_key(
'Npp-MimeType
'):
8230 mime_types = record[
'Npp-MimeType
'].split(
',
')
8231 for t in mime_types:
8232 t = t.rstrip().strip()
8234 thepkgs.append(pkg.name)
8236 mimetype =
"audio/ogg
"
8237 if
1 < len(sys.argv):
8238 mimetype = sys.argv[
1]
8239 print
"Browser plugin packages supporting %s:
" % mimetype
8240 for pkg in pkgs_handling_mimetype(mimetype):
8241 print
" %s
" %pkg
8244 <p
>It can be used like this to look up a given MIME type:
</p
>
8247 % ./apt-find-browserplug-for-mimetype
8248 Browser plugin packages supporting audio/ogg:
8250 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
8251 Browser plugin packages supporting application/x-shockwave-flash:
8252 browser-plugin-gnash
8256 <p
>In Ubuntu this mechanism is combined with support in the browser
8257 itself to query for plugins and propose to install the needed
8258 packages. It would be great if Debian supported such feature too. Is
8259 anyone working on adding it?
</p
>
8261 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
8262 request for icweasel support for this feature is
8263 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
8264 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
8265 of manpower and wish for a different design is the reason thus feature
8266 is not yet in iceweasel from Debian.
</p
>
8271 <title>What is the most supported MIME type in Debian?
</title>
8272 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
8273 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
8274 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
8275 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
8276 proposal to add AppStream information to the Debian archive
</a
>, is a
8277 proposal to make it possible for a Desktop application to propose to
8278 the user some package to install to gain support for a given MIME
8279 type, font, library etc. that is currently missing. With such
8280 mechanism in place, it would be possible for the desktop to
8281 automatically propose and install leocad if some LDraw file is
8282 downloaded by the browser.
</p
>
8284 <p
>To get some idea about the current content of the archive, I decided
8285 to write a simple program to extract all .desktop files from the
8286 Debian archive and look up the claimed MIME support there. The result
8288 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
8289 site
</a
>. Using the collected information, it become possible to
8290 answer the question in the title. Here are the
20 most supported MIME
8291 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
8292 The complete list is available from the link above.
</p
>
8294 <p
><strong
>Debian Stable:
</strong
></p
>
8298 ----- -----------------------
8314 18 application/x-ogg
8321 <p
><strong
>Debian Testing:
</strong
></p
>
8325 ----- -----------------------
8341 18 application/x-ogg
8348 <p
><strong
>Debian Unstable:
</strong
></p
>
8352 ----- -----------------------
8369 18 application/x-ogg
8375 <p
>I am told that PackageKit can provide an API to access the kind of
8376 information mentioned in DEP-
11. I have not yet had time to look at
8377 it, but hope the PackageKit people in Debian are on top of these
8380 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
8381 discovering a typo in my script.
</p
>
8386 <title>Using modalias info to find packages handling my hardware
</title>
8387 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
8388 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
8389 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
8390 <description><p
>Yesterday, I wrote about the
8391 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
8392 values provided by the Linux kernel
</a
> following my hope for
8393 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
8394 dongle support in Debian
</a
>. Using this knowledge, I have tested how
8395 modalias values attached to package names can be used to map packages
8396 to hardware. This allow the system to look up and suggest relevant
8397 packages when I plug in some new hardware into my machine, and replace
8398 discover and discover-data as the database used to map hardware to
8401 <p
>I create a modaliases file with entries like the following,
8402 containing package name, kernel module name (if relevant, otherwise
8403 the package name) and globs matching the relevant hardware
8406 <p
><blockquote
>
8407 Package: package-name
8408 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
8409 </blockquote
></p
>
8411 <p
>It is fairly trivial to write code to find the relevant packages
8412 for a given modalias value using this file.
</p
>
8414 <p
>An entry like this would suggest the video and picture application
8415 cheese for many USB web cameras (interface bus class
0E01):
</p
>
8417 <p
><blockquote
>
8419 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
8420 </blockquote
></p
>
8422 <p
>An entry like this would suggest the pcmciautils package when a
8423 CardBus bridge (bus class
0607) PCI device is present:
</p
>
8425 <p
><blockquote
>
8426 Package: pcmciautils
8427 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
8428 </blockquote
></p
>
8430 <p
>An entry like this would suggest the package colorhug-client when
8431 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
8433 <p
><blockquote
>
8434 Package: colorhug-client
8435 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
8436 </blockquote
></p
>
8438 <p
>I believe the format is compatible with the format of the Packages
8439 file in the Debian archive. Ubuntu already uses their Packages file
8440 to store their mappings from packages to hardware.
</p
>
8442 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
8443 announce the hardware it support in a way my prototype understand.
8444 This allow those publishing packages in an APT source outside the
8445 Debian archive as well as those backporting packages to make sure the
8446 hardware mapping are included in the package meta information. I
've
8447 tested such header in the pymissile package, and its modalias mapping
8448 is working as it should with my prototype. It even made it to Ubuntu
8451 <p
>To test if it was possible to look up supported hardware using only
8452 the shell tools available in the Debian installer, I wrote a shell
8453 implementation of the lookup code. The idea is to create files for
8454 each modalias and let the shell do the matching. Please check out and
8456 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
8457 shell script. It run without any extra dependencies and fetch the
8458 hardware mappings from the Debian archive and the subversion
8459 repository where I currently work on my prototype.
</p
>
8461 <p
>When I use it on a machine with a yubikey inserted, it suggest to
8462 install yubikey-personalization:
</p
>
8464 <p
><blockquote
>
8465 % ./hw-support-lookup
8466 <br
>yubikey-personalization
8468 </blockquote
></p
>
8470 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
8471 propose to install the pcmciautils package:
</p
>
8473 <p
><blockquote
>
8474 % ./hw-support-lookup
8475 <br
>pcmciautils
8477 </blockquote
></p
>
8479 <p
>If you know of any hardware-package mapping that should be added to
8480 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
8481 database
</a
>, please tell me about it.
</p
>
8483 <p
>It could be possible to generate several of the mappings between
8484 packages and hardware. One source would be to look at packages with
8485 kernel modules, ie packages with *.ko files in /lib/modules/, and
8486 extract their modalias information. Another would be to look at
8487 packages with udev rules, ie packages with files in
8488 /lib/udev/rules.d/, and extract their vendor/model information to
8489 generate a modalias matching rule. I have not tested any of these to
8490 see if it work.
</p
>
8492 <p
>If you want to help implementing a system to let us propose what
8493 packages to install when new hardware is plugged into a Debian
8494 machine, please send me an email or talk to me on
8495 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
8500 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
8501 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
8502 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
8503 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
8504 <description><p
>While looking into how to look up Debian packages based on hardware
8505 information, to find the packages that support a given piece of
8506 hardware, I refreshed my memory regarding modalias values, and decided
8507 to document the details. Here are my findings so far, also available
8509 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
8510 Debian Edu subversion repository
</a
>:
8512 <p
><strong
>Modalias decoded
</strong
></p
>
8514 <p
>This document try to explain what the different types of modalias
8515 values stands for. It is in part based on information from
8516 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
8517 &lt;URL:
<a href=
"http://unix.stackexchange.com/questions/
26132/how-to-assign-usb-driver-to-device
">http://unix.stackexchange.com/questions/
26132/how-to-assign-usb-driver-to-device
</a
> &gt;,
8518 &lt;URL:
<a href=
"http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c
">http://code.metager.de/source/history/linux/stable/scripts/mod/file2alias.c
</a
> &gt; and
8519 &lt;URL:
<a href=
"http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode
&view=markup
">http://cvs.savannah.gnu.org/viewvc/dmidecode/dmidecode.c?root=dmidecode
&view=markup
</a
> &gt;.
8521 <p
>The modalias entries for a given Linux machine can be found using
8522 this shell script:
</p
>
8525 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
8528 <p
>The supported modalias globs for a given kernel module can be found
8529 using modinfo:
</p
>
8532 % /sbin/modinfo psmouse | grep alias:
8533 alias: serio:ty05pr*id*ex*
8534 alias: serio:ty01pr*id*ex*
8538 <p
><strong
>PCI subtype
</strong
></p
>
8540 <p
>A typical PCI entry can look like this. This is an Intel Host
8541 Bridge memory controller:
</p
>
8543 <p
><blockquote
>
8544 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
8545 </blockquote
></p
>
8547 <p
>This represent these values:
</p
>
8552 sv
00001028 (subvendor)
8553 sd
000001AD (subdevice)
8555 sc
00 (bus subclass)
8559 <p
>The vendor/device values are the same values outputted from
'lspci
8560 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
8561 0600. The
0600 class is a host bridge. Other useful bus values are
8562 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
8564 <p
>Not sure how to figure out the interface value, nor what it
8567 <p
><strong
>USB subtype
</strong
></p
>
8569 <p
>Some typical USB entries can look like this. This is an internal
8570 USB hub in a laptop:
</p
>
8572 <p
><blockquote
>
8573 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
8574 </blockquote
></p
>
8576 <p
>Here is the values included in this alias:
</p
>
8579 v
1D6B (device vendor)
8580 p
0001 (device product)
8582 dc
09 (device class)
8583 dsc
00 (device subclass)
8584 dp
00 (device protocol)
8585 ic
09 (interface class)
8586 isc
00 (interface subclass)
8587 ip
00 (interface protocol)
8590 <p
>The
0900 device class/subclass means hub. Some times the relevant
8591 class is in the interface class section. For a simple USB web camera,
8592 these alias entries show up:
</p
>
8594 <p
><blockquote
>
8595 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
8596 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
8597 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
8598 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
8599 </blockquote
></p
>
8601 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
8602 camera),
0101 is audio control device and
0102 is audio streaming (aka
8603 microphone). Thus this is a camera with microphone included.
</p
>
8605 <p
><strong
>ACPI subtype
</strong
></p
>
8607 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
8608 receiver in a Thinkpad X40:
</p
>
8610 <p
><blockquote
>
8611 acpi:IBM0071:PNP0511:
8612 </blockquote
></p
>
8614 <p
>The values between the colons are IDs.
</p
>
8616 <p
><strong
>DMI subtype
</strong
></p
>
8618 <p
>The DMI table contain lots of information about the computer case
8619 and model. This is an entry for a IBM Thinkpad X40, fetched from
8620 /sys/devices/virtual/dmi/id/modalias:
</p
>
8622 <p
><blockquote
>
8623 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
8624 </blockquote
></p
>
8626 <p
>The values present are
</p
>
8629 bvn IBM (BIOS vendor)
8630 bvr
1UETB
6WW(
1.66) (BIOS version)
8631 bd
06/
15/
2005 (BIOS date)
8632 svn IBM (system vendor)
8633 pn
2371H4G (product name)
8634 pvr ThinkPadX40 (product version)
8635 rvn IBM (board vendor)
8636 rn
2371H4G (board name)
8637 rvr NotAvailable (board version)
8638 cvn IBM (chassis vendor)
8639 ct
10 (chassis type)
8640 cvr NotAvailable (chassis version)
8643 <p
>The chassis type
10 is Notebook. Other interesting values can be
8644 found in the dmidecode source:
</p
>
8648 4 Low Profile Desktop
8661 17 Main Server Chassis
8662 18 Expansion Chassis
8664 20 Bus Expansion Chassis
8665 21 Peripheral Chassis
8667 23 Rack Mount Chassis
8676 <p
>The chassis type values are not always accurately set in the DMI
8677 table. For example my home server is a tower, but the DMI modalias
8678 claim it is a desktop.
</p
>
8680 <p
><strong
>SerIO subtype
</strong
></p
>
8682 <p
>This type is used for PS/
2 mouse plugs. One example is from my
8683 test machine:
</p
>
8685 <p
><blockquote
>
8686 serio:ty01pr00id00ex00
8687 </blockquote
></p
>
8689 <p
>The values present are
</p
>
8698 <p
>This type is supported by the psmouse driver. I am not sure what
8699 the valid values are.
</p
>
8701 <p
><strong
>Other subtypes
</strong
></p
>
8703 <p
>There are heaps of other modalias subtypes according to
8704 file2alias.c. There is the rest of the list from that source: amba,
8705 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
8706 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
8707 vmbus, x86cpu and zorro. I did not spend time documenting all of
8708 these, as they do not seem relevant for my intended use with mapping
8709 hardware to packages when new stuff is inserted during run time.
</p
>
8711 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
8713 <p
>To check which kernel modules provide support for a given modalias,
8714 one can use the following shell script:
</p
>
8717 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
8718 echo
"$id
" ; \
8719 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
8723 <p
>The output can look like this (only the first few entries as the
8724 list is very long on my test machine):
</p
>
8728 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
8730 FATAL: Module acpi:device: not found.
8732 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
8733 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
8734 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
8735 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
8736 acpi:IBM0071:PNP0511:
8737 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
8738 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
8739 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
8743 <p
>If you want to help implementing a system to let us propose what
8744 packages to install when new hardware is plugged into a Debian
8745 machine, please send me an email or talk to me on
8746 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
8748 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
8749 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
8750 in /sys/ with space in them.
</p
>
8755 <title>Moved the pymissile Debian packaging to collab-maint
</title>
8756 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
8757 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
8758 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
8759 <description><p
>As part of my investigation on how to improve the support in Debian
8760 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
8761 Launcher and updated the Debian package
8762 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
8763 sure udev will fix the device permissions when it is plugged in. I
8764 also added a
"Modaliases
" header to test it in the Debian archive and
8765 hopefully make the package be proposed by jockey in Ubuntu when a user
8766 plug in his rocket launcher. In the process I moved the source to a
8767 git repository under collab-maint, to make it easier for any DD to
8768 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
8769 is not very active, but the software still work for me even after five
8770 years of relative silence. The new git repository is not listed in
8771 the uploaded package yet, because I want to test the other changes a
8772 bit more before I upload the new version. If you want to check out
8773 the new version with a .desktop file included, visit the
8774 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
8775 view
</a
> or use
"<tt
>git clone
8776 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
8781 <title>Lets make hardware dongles easier to use in Debian
</title>
8782 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
8783 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
8784 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
8785 <description><p
>One thing that annoys me with Debian and Linux distributions in
8786 general, is that there is a great package management system with the
8787 ability to automatically install software packages by downloading them
8788 from the distribution mirrors, but no way to get it to automatically
8789 install the packages I need to use the hardware I plug into my
8790 machine. Even if the package to use it is easily available from the
8791 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
8792 suggest to automatically install the python-nxt, nbc and t2n packages
8793 I need to talk to it. When I plug in a Yubikey, it could propose the
8794 yubikey-personalization package. The information required to do this
8795 is available, but no-one have pulled all the pieces together.
</p
>
8797 <p
>Some years ago, I proposed to
8798 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
8799 the discover subsystem to implement this
</a
>. The idea is fairly
8804 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
8805 starting when a user log in.
</li
>
8807 <li
>Set this program up to listen for kernel events emitted when new
8808 hardware is inserted into the computer.
</li
>
8810 <li
>When new hardware is inserted, look up the hardware ID in a
8811 database mapping to packages, and take note of any non-installed
8812 packages.
</li
>
8814 <li
>Show a message to the user proposing to install the discovered
8815 package, and make it easy to install it.
</li
>
8819 <p
>I am not sure what the best way to implement this is, but my
8820 initial idea was to use dbus events to discover new hardware, the
8821 discover database to find packages and
8822 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
8825 <p
>Yesterday, I found time to try to implement this idea, and the
8826 draft package is now checked into
8827 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
8828 Debian Edu subversion repository
</a
>. In the process, I updated the
8829 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
8830 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
8831 the relevant packages in Debian, and uploaded a new version
8832 2.2013.01.09 to unstable. I also discovered that the current
8833 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
8834 package in Debian no longer discovered any USB devices, because
8835 /proc/bus/usb/devices is no longer present. I ported it to use
8836 libusb as a fall back option to get it working. The fixed package
8837 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
8838 because of the freeze).
</p
>
8840 <p
>With this prototype in place, I can insert my Yubikey, and get this
8841 desktop notification to show up (only once, the first time it is
8842 inserted):
</p
>
8844 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
8846 <p
>For this prototype to be really useful, some way to automatically
8847 install the proposed packages by pressing the
"Please install
8848 program(s)
" button should to be implemented.
</p
>
8850 <p
>If this idea seem useful to you, and you want to help make it
8851 happen, please help me update the discover-data database with mappings
8852 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
8853 list the package you would like to have installed when a given
8854 hardware device is inserted into your computer, and report bugs using
8855 reportbug if it isn
't. Or, if you know of a better way to provide
8856 such mapping, please let me know.
</p
>
8858 <p
>This prototype need more work, and there are several questions that
8859 should be considered before it is ready for production use. Is dbus
8860 the correct way to detect new hardware? At the moment I look for HAL
8861 dbus events on the system bus, because that is the events I could see
8862 on my Debian Squeeze KDE desktop. Are there better events to use?
8863 How should the user be notified? Is the desktop notification
8864 mechanism the best option, or should the background daemon raise a
8865 popup instead? How should packages be installed? When should they
8866 not be installed?
</p
>
8868 <p
>If you want to help getting such feature implemented in Debian,
8869 please send me an email. :)
</p
>
8874 <title>New IRC channel for LEGO designers using Debian
</title>
8875 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
8876 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
8877 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
8878 <description><p
>During Christmas, I have worked a bit on the Debian support for
8879 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
8880 NXT
</a
>. My son and I have played a bit with my NXT set, and I
8881 discovered I had to build all the tools myself because none were
8882 already in Debian Squeeze. If Debian support for LEGO is something
8883 you care about, please join me on the IRC channel
8884 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
8885 irc.debian.org). There is a lot that could be done to improve the
8886 Debian support for LEGO designers. For example both CAD software
8887 and Mindstorm compilers are missing. :)
</p
>
8889 <p
>Update
2012-
01-
03: A
8890 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
8891 including links to Lego related packages is now available.
</p
>
8896 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
8897 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
8898 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
8899 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
8900 <description><p
>Let me start by wishing you all marry Christmas and a happy new
8901 year! I hope next year will prove to be a good year.
</p
>
8903 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
8904 decentralised
"currency
" that allow people to transfer bitcoins
8905 between each other with minimal overhead, is a very interesting
8906 experiment. And as I wrote a few days ago, the bitcoin situation in
8907 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
8908 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
8909 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
8910 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
8911 for one of the ftpmasters to approve the new bitcoin-qt package
8914 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
8915 team in Debian, you can easily test the package in Debian Squeeze
8916 using the following steps to get a set of working packages:
</p
>
8918 <blockquote
><pre
>
8919 git clone git://git.debian.org/git/collab-maint/bitcoin
8921 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
8922 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
8923 </pre
></blockquote
>
8925 <p
>You might have to install some build dependencies as well. The
8926 list of commands should give you two packages, bitcoind and
8927 bitcoin-qt, ready for use in a Squeeze environment. Note that the
8928 client will download the complete set of bitcoin
"blocks
", which need
8929 around
5.6 GiB of data on my machine at the moment. Make sure your
8930 ~/.bitcoin/ directory have lots of spare room if you want to download
8931 all the blocks. The client will warn if the disk is getting full, so
8932 there is not really a problem if you got too little room, but you will
8933 not be able to get all the features out of the client.
</p
>
8935 <p
>As usual, if you use bitcoin and want to show your support of my
8936 activities, please send Bitcoin donations to my address
8937 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
8942 <title>A word on bitcoin support in Debian
</title>
8943 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
8944 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
8945 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
8946 <description><p
>It has been a while since I wrote about
8947 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
8948 peer-to-peer based crypto-currency, and the reason is simply that I
8949 have been busy elsewhere. But two days ago, I started looking at the
8950 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
8951 Debian
</a
> again to try to recover my old bitcoin wallet. The package
8952 is now maintained by a
8953 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
8954 people
</a
>, and the grunt work had already been done by this team. We
8955 owe a huge thank you to all these team members. :)
8956 But I was sad to discover that the bitcoin client is missing in
8957 Wheezy. It is only available in Sid (and an outdated client from
8958 backports). The client had several RC bugs registered in BTS blocking
8959 it from entering testing. To try to help the team and improve the
8960 situation, I spent some time providing patches and triaging the bug
8961 reports. I also had a look at the bitcoin package available from Matt
8963 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
8964 Ubuntu
</a
>, and moved the useful pieces from that version into the
8965 Debian package.
</p
>
8967 <p
>After checking with the main package maintainer Jonas Smedegaard on
8968 IRC, I pushed several patches into the collab-maint git repository to
8969 improve the package. It now contains fixes for the RC issues (not from
8970 me, but fixed by Scott Howard), build rules for a Qt GUI client
8971 package, konqueror support for the bitcoin: URI and bash completion
8972 setup. As I work on Debian Squeeze, I also created
8973 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
8974 patch to backport
</a
> the latest version. Jonas is going to look at
8975 it and try to integrate it into the git repository before uploading a
8976 new version to unstable.
8978 <p
>I would very much like bitcoin to succeed, to get rid of the
8979 centralized control currently exercised in the monetary system. I
8980 find it completely unacceptable that the USA government is collecting
8981 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
8982 that the major credit card companies can block legal money
8983 transactions to Wikileaks. But for bitcoin to succeed, more people
8984 need to use bitcoins, and more people need to accept bitcoins when
8985 they sell products and services. Improving the bitcoin support in
8986 Debian is a small step in the right direction, but not enough.
8987 Unfortunately the user experience when browsing the web and wanting to
8988 pay with bitcoin is still not very good. The bitcoin: URI is a step
8989 in the right direction, but need to work in most or every browser in
8990 use. Also the bitcoin-qt client is too heavy to fire up to do a
8991 quick transaction. I believe there are other clients available, but
8992 have not tested them.
</p
>
8995 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
8996 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
8997 I received
20.15 BTC so far on the address I provided in my blog two
8998 years ago, as can be
8999 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
9000 on the blockexplorer service
</a
>. Thank you everyone for your
9001 donation. The blockexplorer service demonstrates quite well that
9002 bitcoin is not quite anonymous and untracked. :) I wonder if the
9003 number of users have gone up since then. If you use bitcoin and want
9004 to show your support of my activity, please send Bitcoin donations to
9005 the same address as last time,
9006 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9011 <title>Git repository for song book for Computer Scientists
</title>
9012 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
9013 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
9014 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
9015 <description><p
>As I
9016 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
9017 this summer
</a
>, I have created a Computer Science song book a few
9018 years ago, and today I finally found time to create a public
9019 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
9020 repository for the project
</a
>.
</p
>
9022 <p
>If you want to help out, please clone the source and submit patches
9023 to the HTML version. To generate the PDF and PostScript version,
9024 please use prince XML, or let me know about a useful free software
9025 processor capable of creating a good looking PDF from the HTML.
</p
>
9027 <p
>Want to sing? You can still find the song book in HTML, PDF and
9028 PostScript formats at
9029 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
9030 Science Songbook
</a
>.
</p
>
9035 <title>Gratulerer med
19-årsdagen, Debian!
</title>
9036 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
9037 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
9038 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
9039 <description><p
>I dag fyller
9040 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
9041 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
9042 si gratulerer med dagen, Debian!
</p
>
9047 <title>Song book for Computer Scientists
</title>
9048 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
9049 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
9050 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
9051 <description><p
>Many years ago, while studying Computer Science at the
9052 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
9053 collecting computer related songs for use at parties. The original
9054 version was written in LaTeX, but a few years ago I got help from
9055 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9056 while keeping the ability to create a nice book in PDF format. I have
9057 not had time to maintain the book for a while now, and guess I should
9058 put it up on some public version control repository where others can
9059 help me extend and update the book. If anyone is volunteering to help
9060 me with this, send me an email. Also let me know if there are songs
9061 missing in my book.
</p
>
9063 <p
>I have not mentioned the book on my blog so far, and it occured to
9064 me today that I really should let all my readers share the joys of
9065 singing out load about programming, computers and computer networks.
9066 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
9067 12</a
> is about to start (and I am not going). Want to sing? Check
9068 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
9069 Computer Science Songbook
</a
>.
9074 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
9075 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
9076 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
9077 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
9078 <description><p
>At work we have heaps of servers. I believe the total count is
9079 around
1000 at the moment. To be able to get help from the vendors
9080 when something go wrong, we want to keep the firmware on the servers
9081 up to date. If the firmware isn
't the latest and greatest, the
9082 vendors typically refuse to start debugging any problems until the
9083 firmware is upgraded. So before every reboot, we want to upgrade the
9084 firmware, and we would really like everyone handling servers at the
9085 university to do this themselves when they plan to reboot a machine.
9086 For that to happen we at the unix server admin group need to provide
9087 the tools to do so.
</p
>
9089 <p
>To make firmware upgrading easier, I am working on a script to
9090 fetch and install the latest firmware for the servers we got. Most of
9091 our hardware are from Dell and HP, so I have focused on these servers
9092 so far. This blog post is about the Dell part.
</P
>
9094 <p
>On the Dell FTP site I was lucky enough to find
9095 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
9096 with firmware information for all
11th generation servers, listing
9097 which firmware should be used on a given model and where on the FTP
9098 site I can find it. Using a simple perl XML parser I can then
9099 download the shell scripts Dell provides to do firmware upgrades from
9100 within Linux and reboot when all the firmware is primed and ready to
9101 be activated on the first reboot.
</p
>
9103 <p
>This is the Dell related fragment of the perl code I am working on.
9104 Are there anyone working on similar tools for firmware upgrading all
9105 servers at a site? Please get in touch and lets share resources.
</p
>
9107 <p
><pre
>
9111 use File::Temp qw(tempdir);
9113 # Install needed RHEL packages if missing
9115 'XML::Simple
' =
> 'perl-XML-Simple
',
9117 for my $module (keys %rhelmodules) {
9118 eval
"use $module;
";
9120 my $pkg = $rhelmodules{$module};
9121 system(
"yum install -y $pkg
");
9122 eval
"use $module;
";
9126 my $errorsto =
'pere@hungry.com
';
9132 sub run_firmware_script {
9133 my ($opts, $script) = @_;
9135 print STDERR
"fail: missing script name\n
";
9138 print STDERR
"Running $script\n\n
";
9140 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
9141 print STDERR
"success: firmware script ran succcessfully\n
";
9143 print STDERR
"fail: firmware script returned error\n
";
9147 sub run_firmware_scripts {
9148 my ($opts, @dirs) = @_;
9149 # Run firmware packages
9150 for my $dir (@dirs) {
9151 print STDERR
"info: Running scripts in $dir\n
";
9152 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
9153 while (my $s = readdir $dh) {
9154 next if $s =~ m/^\.\.?/;
9155 run_firmware_script($opts,
"$dir/$s
");
9163 print STDERR
"info: Downloading $url\n
";
9164 system(
"wget --quiet \
"$url\
"");
9169 my $product = `dmidecode -s system-product-name`;
9172 if ($product =~ m/PowerEdge/) {
9174 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9175 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
9177 my $tmpdir = tempdir(
9181 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
9182 system(
'gunzip Catalog.xml.gz
');
9183 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
9184 # -q is quiet, disabling interactivity and reducing console output
9185 my $fwopts =
"-q
";
9187 for my $url (@paths) {
9188 fetch_dell_fw($url);
9190 run_firmware_scripts($fwopts, $tmpdir);
9192 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9193 print STDERR
"error: Please report to $errorsto.\n
";
9197 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9198 print STDERR
"error: Please report to $errorsto.\n
";
9204 my $url =
"ftp://ftp.us.dell.com/$path
";
9208 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9209 # firmware packages to download from Dell. Only work for Linux
9210 # machines and
11th generation Dell servers.
9211 sub fetch_dell_fw_list {
9212 my $filename = shift;
9214 my $product = `dmidecode -s system-product-name`;
9216 my ($mybrand, $mymodel) = split(/\s+/, $product);
9218 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
9220 my $xml = XMLin($filename);
9222 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
9223 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
9224 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
9226 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
9227 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
9229 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
9231 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
9233 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
9236 for my $component (@{$xml-
>{SoftwareComponent}}) {
9237 my $componenttype = $component-
>{ComponentType}-
>{value};
9239 # Drop application packages, only firmware and BIOS
9240 next if
'APAC
' eq $componenttype;
9242 my $cpath = $component-
>{path};
9243 for my $path (@paths) {
9244 if ($cpath =~ m%/$path$%) {
9245 push(@paths, $cpath);
9253 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
9254 it could work on other platforms with some tweaking. Anyone know a
9255 index like Catalog.xml is available from HP for HP servers? At the
9256 moment I maintain a similar list manually and it is quickly getting
9262 <title>How is booting into runlevel
1 different from single user boots?
</title>
9263 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
9264 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
9265 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
9266 <description><p
>Wouter Verhelst have some
9267 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
9268 comments and opinions
</a
> on my blog post on
9269 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
9270 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
9271 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
9272 default KDE desktop in Debian
</a
>. I only have time to address one
9273 small piece of his comment now, and though it best to address the
9274 misunderstanding he bring forward:
</p
>
9276 <p
><blockquote
>
9277 Currently, a system admin has four options: [...] boot to a
9278 single-user system (by adding
'single
' to the kernel command line;
9279 this runs rcS and rc1 scripts)
9280 </blockquote
></p
>
9282 <p
>This make me believe Wouter believe booting into single user mode
9283 and booting into runlevel
1 is the same. I am not surprised he
9284 believe this, because it would make sense and is a quite sensible
9285 thing to believe. But because the boot in Debian is slightly broken,
9286 runlevel
1 do not work properly and it isn
't the same as single user
9287 mode. I
'll try to explain what is actually happing, but it is a bit
9288 hard to explain.
</p
>
9290 <p
>Single user mode is defined like this in /etc/inittab:
9291 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
9292 executed in single user mode is sulogin. Single user mode is a boot
9293 state
"between
" the runlevels, and when booting into single user mode,
9294 only the scripts in /etc/rcS.d/ are executed before the init process
9295 enters the single user state. When switching to runlevel
1, the state
9296 is in fact not ending in runlevel
1, but it passes through runlevel
1
9297 and end up in the single user mode (see /etc/rc1.d/S03single, which
9298 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
9299 1. It is confusing that the
'S
' (single user) init mode is not the
9300 mode enabled by /etc/rcS.d/ (which is more like the initial boot
9303 <p
>This summary might make it clearer. When booting for the first
9304 time into single user mode, the following commands are executed:
9305 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
9306 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
9307 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
9308 trying to continue after visiting single user mode. Not all services
9309 are started again as they should, causing the machine to end up in an
9310 unpredicatble state. This is why Debian admins recommend rebooting
9311 after visiting single user mode.
</p
>
9313 <p
>A similar problem with runlevel
1 is caused by the amount of
9314 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
9315 to runlevel
1, the services started from /etc/rcS.d/ are not properly
9316 stopped when passing through the scripts in /etc/rc1.d/, and not
9317 started again when switching away from runlevel
1 to the runlevels
9318 2-
5. I believe the problem is best fixed by moving all the scripts
9319 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
9320 functioning single user mode during boot.
</p
>
9322 <p
>I have spent several years investigating the Debian boot system,
9323 and discovered this problem a few years ago. I suspect it originates
9324 from when sysvinit was introduced into Debian, a long time ago.
</p
>
9329 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
9330 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
9331 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
9332 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
9333 <description><p
>In the Debian boot system, several packages include scripts that
9334 are started from /etc/rcS.d/. In fact, there is a bite more of them
9335 than make sense, and this causes a few problems. What kind of
9336 problems, you might ask. There are at least two problems. The first
9337 is that it is not possible to recover a machine after switching to
9338 runlevel
1. One need to actually reboot to get the machine back to
9339 the expected state. The other is that single user boot will sometimes
9340 run into problems because some of the subsystems are activated before
9341 the root login is presented, causing problems when trying to recover a
9342 machine from a problem in that subsystem. A minor additional point is
9343 that moving more scripts out of rcS.d/ and into the other rc#.d/
9344 directories will increase the amount of scripts that can run in
9345 parallel during boot, and thus decrease the boot time.
</p
>
9347 <p
>So, which scripts should start from rcS.d/. In short, only the
9348 scripts that _have_ to execute before the root login prompt is
9349 presented during a single user boot should go there. Everything else
9350 should go into the numeric runlevels. This means things like
9351 lm-sensors, fuse and x11-common should not run from rcS.d, but from
9352 the numeric runlevels. Today in Debian, there are around
115 init.d
9353 scripts that are started from rcS.d/, and most of them should be moved
9354 out. Do your package have one of them? Please help us make single
9355 user and runlevel
1 better by moving it.
</p
>
9357 <p
>Scripts setting up the screen, keyboard, system partitions
9358 etc. should still be started from rcS.d/, but there is for example no
9359 need to have the network enabled before the single user login prompt
9360 is presented.
</p
>
9362 <p
>As always, things are not so easy to fix as they sound. To keep
9363 Debian systems working while scripts migrate and during upgrades, the
9364 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
9365 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
9366 and the next ones can only be moved when their dependencies have been
9367 moved first. This migration must be done sequentially while we ensure
9368 that the package system upgrade packages in the right order to keep
9369 the system state correct. This will require some coordination when it
9370 comes to network related packages, but most of the packages with
9371 scripts that should migrate do not have anything in rcS.d/ depending
9372 on them. Some packages have already been updated, like the sudo
9373 package, while others are still left to do. I wish I had time to work
9374 on this myself, but real live constrains make it unlikely that I will
9375 find time to push this forward.
</p
>
9380 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
9381 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
9382 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
9383 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
9384 <description><p
>While at Debconf11, I have several times during discussions
9385 mentioned the issues I believe should be improved in Debian for its
9386 desktop to be useful for more people. The use case for this is my
9387 parents, which are currently running Kubuntu which solve the
9390 <p
>I suspect these four missing features are not very hard to
9391 implement. After all, they are present in Ubuntu, so if we wanted to
9392 do this in Debian we would have a source.
</p
>
9396 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
9397 are new packages available for upgrades, a icon in the KDE status bar
9398 indicate this, and clicking on it will activate the simple upgrade
9399 tool to handle it. I have no problem guiding both of my parents
9400 through the process over the phone. If a kernel reboot is required,
9401 this too is indicated by the status bars and the upgrade tool. Last
9402 time I checked, nothing with the same features was working in KDE in
9405 <li
><strong
>Simple handling of missing Firefox browser
9406 plugins.
</strong
> When the browser encounter a MIME type it do not
9407 currently have a handler for, it will ask the user if the system
9408 should search for a package that would add support for this MIME type,
9409 and if the user say yes, the APT sources will be searched for packages
9410 advertising the MIME type in their control file (visible in the
9411 Packages file in the APT archive). If one or more packages are found,
9412 it is a simple click of the mouse to add support for the missing mime
9413 type. If the package require the user to accept some non-free
9414 license, this is explained to the user. The entire process make it
9415 more clear to the user why something do not work in the browser, and
9416 make the chances higher for the user to blame the web page authors and
9417 not the browser for any missing features.
</li
>
9419 <li
><strong
>Simple handling of missing multimedia codec/format
9420 handlers.
</strong
> When the media players encounter a format or codec
9421 it is not supporting, a dialog pop up asking the user if the system
9422 should search for a package that would add support for it. This
9423 happen with things like MP3, Windows Media or H
.264. The selection
9424 and installation procedure is very similar to the Firefox browser
9425 plugin handling. This is as far as I know implemented using a
9426 gstreamer hook. The end result is that the user easily get access to
9427 the codecs that are present from the APT archives available, while
9428 explaining more on why a given format is unsupported by Ubuntu.
</li
>
9430 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
9431 displaying a text/plain file in my Debian browser, it will propose to
9432 start emacs to show it. If I remember correctly, when doing the same
9433 in Kunbutu it show the file as a text file in the browser. At least I
9434 know Opera will show text files within the browser. I much prefer the
9435 latter behaviour.
</li
>
9439 <p
>There are other nice features as well, like the simplified suite
9440 upgrader, but given that I am the one mostly doing the dist-upgrade,
9441 it do not matter much.
</p
>
9443 <p
>I really hope we could get these features in place for the next
9444 Debian release. It would require the coordinated effort of several
9445 maintainers, but would make the end user experience a lot better.
</p
>
9450 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
9451 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
9452 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
9453 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
9454 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
9455 site is build on Debian/Squeeze, and this platform was chosen because
9456 I am most familiar with Debian (being a Debian Developer for around
10
9457 years) because it is the latest stable Debian release which should get
9458 security support for a few years.
</p
>
9460 <p
>The web service is written in Perl, and depend on some perl modules
9461 that are missing in Debian at the moment. It would be great if these
9462 modules were added to the Debian archive, allowing anyone to set up
9463 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
9464 in their own country using only Debian packages. The list of modules
9465 missing in Debian/Squeeze isn
't very long, and I hope the perl group
9466 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
9467 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
9468 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
9469 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
9470 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
9471 easier in the future.
</p
>
9473 <p
>Thanks to the great tools in Debian, getting the missing modules
9474 installed on my server was a simple call to
'cpan2deb Module::Name
'
9475 and
'dpkg -i
' to install the resulting package. But this leave me
9476 with the responsibility of tracking security problems, which I really
9477 do not have time for.
</p
>
9482 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
9483 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
9484 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
9485 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
9486 <description><p
>Here is a small update for my English readers. Most of my blog
9487 posts have been in Norwegian the last few weeks, so here is a short
9488 update in English.
</p
>
9490 <p
>The kids still keep me too busy to get much free software work
9491 done, but I did manage to organise a project to get a Norwegian port
9492 of the British service
9493 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
9494 and it has been running for a month now. The entire project has been
9495 organised by me and two others. Around Christmas we gathered sponsors
9496 to fund the development work. In January I drafted a contract with
9497 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
9498 and in February the development took place. Most of it involved
9499 converting the source to use GPS coordinates instead of British
9500 easting/northing, and the resulting code should be a lot easier to get
9501 running in any country by now. The Norwegian
9502 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
9503 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
9504 source and the source for administrative borders in Norway, and
9505 support for this had to be added/fixed.
</p
>
9507 <p
>The Norwegian version went live March
3th, and we spent the weekend
9508 polishing the system before we announced it March
7th. The system is
9509 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
9510 problem reports in a few weeks. Soon we hope to announce the Android
9511 and iPhone versions making it even easier to report problems with the
9512 public infrastructure.
</p
>
9514 <p
>Perhaps something to consider for those of you in countries without
9515 such service?
</p
>
9520 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
9521 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
9522 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
9523 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
9524 <description><p
>The last few days I have looked at ways to track open security
9525 issues here at my work with the University of Oslo. My idea is that
9526 it should be possible to use the information about security issues
9527 available on the Internet, and check our locally
9528 maintained/distributed software against this information. It should
9529 allow us to verify that no known security issues are forgotten. The
9530 CVE database listing vulnerabilities seem like a great central point,
9531 and by using the package lists from Debian mapped to CVEs provided by
9532 the testing security team, I believed it should be possible to figure
9533 out which security holes were present in our free software
9534 collection.
</p
>
9536 <p
>After reading up on the topic, it became obvious that the first
9537 building block is to be able to name software packages in a unique and
9538 consistent way across data sources. I considered several ways to do
9539 this, for example coming up with my own naming scheme like using URLs
9540 to project home pages or URLs to the Freshmeat entries, or using some
9541 existing naming scheme. And it seem like I am not the first one to
9542 come across this problem, as MITRE already proposed and implemented a
9543 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
9544 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
9545 software, hardware and other platform components. The CPE ids are
9546 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
9547 Vulnerability Database
</a
>, allowing me to look up know security
9548 issues for any CPE name. With this in place, all I need to do is to
9549 locate the CPE id for the software packages we use at the university.
9550 This is fairly trivial (I google for
'cve cpe $package
' and check the
9551 NVD entry if a CVE for the package exist).
</p
>
9553 <p
>To give you an example. The GNU gzip source package have the CPE
9554 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
9555 check out, one could look up
9556 <a href=
"http://web.nvd.nist.gov/view/vuln/search?cpe=cpe%
3A%
2Fa%
3Agnu%
3Agzip:
1.3.3">cpe:/a:gnu:gzip:
1.3.3
9557 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
9558 The most recent one is
9559 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
9560 and at the bottom of the NVD page for this vulnerability the complete
9561 list of affected versions is provided.
</p
>
9563 <p
>The NVD database of CVEs is also available as a XML dump, allowing
9564 for offline processing of issues. Using this dump, I
've written a
9565 small script taking a list of CPEs as input and list all CVEs
9566 affecting the packages represented by these CPEs. One give it CPEs
9567 with version numbers as specified above and get a list of open
9568 security issues out.
</p
>
9570 <p
>Of course for this approach to be useful, the quality of the NVD
9571 information need to be high. For that to happen, I believe as many as
9572 possible need to use and contribute to the NVD database. I notice
9574 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
9575 map from CVE to CPE
</a
>, indicating that they are using the CPE
9576 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
9578 <p
>To get an idea about the quality for free software, I spent some
9579 time making it possible to compare the CVE database from Debian with
9580 the CVE database in NVD. The result look fairly good, but there are
9581 some inconsistencies in NVD (same software package having several
9582 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
9583 Debian believe are affected by a CVE). Hope to find time to improve
9584 the quality of NVD, but that require being able to get in touch with
9585 someone maintaining it. So far my three emails with questions and
9586 corrections have not seen any reply, but I hope contact can be
9587 established soon.
</p
>
9589 <p
>An interesting application for CPEs is cross platform package
9590 mapping. It would be useful to know which packages in for example
9591 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
9592 this would be trivial if all linux distributions provided CPE entries
9593 for their packages.
</p
>
9598 <title>Which module is loaded for a given PCI and USB device?
</title>
9599 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
9600 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
9601 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
9602 <description><p
>In the
9603 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
9604 package in Debian, there is a script to report useful information
9605 about the running hardware for use when people report missing
9606 information. One part of this script that I find very useful when
9607 debugging hardware problems, is the part mapping loaded kernel module
9608 to the PCI device it claims. It allow me to quickly see if the kernel
9609 module I expect is driving the hardware I am struggling with. To see
9610 the output, make sure discover-data is installed and run
9611 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
9612 one of my machines like this:
</p
>
9616 10de:
03eb i2c_nforce2
9619 10de:
03f0 snd_hda_intel
9628 <p
>The code in question look like this, slightly modified for
9629 readability and to drop the output to file descriptor
3:
</p
>
9632 if [ -d /sys/bus/pci/devices/ ] ; then
9633 echo loaded pci modules:
9635 cd /sys/bus/pci/devices/
9636 for address in * ; do
9637 if [ -d
"$address/driver/module
" ] ; then
9638 module=`cd $address/driver/module ; pwd -P | xargs basename`
9639 if grep -q
"^$module
" /proc/modules ; then
9640 address=$(echo $address |sed s/
0000://)
9641 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
9642 echo
"$id $module
"
9651 <p
>Similar code could be used to extract USB device module
9655 if [ -d /sys/bus/usb/devices/ ] ; then
9656 echo loaded usb modules:
9658 cd /sys/bus/usb/devices/
9659 for address in * ; do
9660 if [ -d
"$address/driver/module
" ] ; then
9661 module=`cd $address/driver/module ; pwd -P | xargs basename`
9662 if grep -q
"^$module
" /proc/modules ; then
9663 address=$(echo $address |sed s/
0000://)
9664 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
9665 if [
"$id
" ] ; then
9666 echo
"$id $module
"
9676 <p
>This might perhaps be something to include in other tools as
9682 <title>How to test if a laptop is working with Linux
</title>
9683 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
9684 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
9685 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
9686 <description><p
>The last few days I have spent at work here at the
<a
9687 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
9688 batch of computers will work with Linux. Every year for the last few
9689 years the university have organised shared bid of a few thousand
9690 computers, and this year HP won the bid. Two different desktops and
9691 five different laptops are on the list this year. We in the UNIX
9692 group want to know which one of these computers work well with RHEL
9693 and Ubuntu, the two Linux distributions we currently handle at the
9694 university.
</p
>
9696 <p
>My test method is simple, and I share it here to get feedback and
9697 perhaps inspire others to test hardware as well. To test, I PXE
9698 install the OS version of choice, and log in as my normal user and run
9699 a few applications and plug in selected pieces of hardware. When
9700 something fail, I make a note about this in the test matrix and move
9701 on. If I have some spare time I try to report the bug to the OS
9702 vendor, but as I only have the machines for a short time, I rarely
9703 have the time to do this for all the problems I find.
</p
>
9705 <p
>Anyway, to get to the point of this post. Here is the simple tests
9706 I perform on a new model.
</p
>
9710 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
9711 and Ubuntu Maverik at the moment. If I feel like it, I also test with
9712 RHEL5 and Debian Edu/Squeeze.
</li
>
9714 <li
>Is X.org working? If the graphical login screen show up after
9715 installation, X.org is working.
</li
>
9717 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
9718 package mesa-utils on Ubuntu) and writing down the frames per second
9719 reported by the program.
</li
>
9721 <li
>Is sound working? With Gnome and KDE, a sound is played when
9722 logging in, and if I can hear this the test is successful. If there
9723 are several audio exits on the machine, I try them all and check if
9724 the Gnome/KDE audio mixer can control where to send the sound. I
9725 normally test this by playing
9726 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
9727 video
</a
> in Firefox/Iceweasel.
</li
>
9729 <li
>Is the USB subsystem working? I test this by plugging in a USB
9730 memory stick and see if Gnome/KDE notices this.
</li
>
9732 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
9733 I have lying around, and see if Gnome/KDE notices this.
</li
>
9735 <li
>Is any built in camera working? Test using cheese, and see if a
9736 picture from the v4l device show up.
</li
>
9738 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
9739 any bluetooth devices are discovered. In my office, I normally see a
9742 <li
>For laptops, is the SD or Compaq Flash reader working. I have
9743 memory modules lying around, and stick them in and see if Gnome/KDE
9744 notice this.
</li
>
9746 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
9747 special button work, and if the laptop continue to work after
9750 <li
>For laptops, is the extra buttons working, like audio level,
9751 adjusting background light, switching on/off external video output,
9752 switching on/off wifi, bluetooth, etc? The set of buttons differ from
9753 laptop to laptop, so I just write down which are working and which are
9756 <li
>Some laptops have smart card readers, finger print readers,
9757 acceleration sensors etc. I rarely test these, as I do not know how
9758 to quickly test if they are working or not, so I only document their
9759 existence.
</li
>
9763 <p
>By now I suspect you are really curious what the test results are
9764 for the HP machines I am testing. I
'm not done yet, so I will report
9765 the test results later. For now I can report that HP
8100 Elite work
9766 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
9767 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
9768 can see, I have most machines left to test. One interesting
9769 observation is that Ubuntu Lucid has almost twice the frame rate than
9770 RHEL6 with glxgears. No idea why.
</p
>
9775 <title>Some thoughts on BitCoins
</title>
9776 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
9777 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
9778 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
9779 <description><p
>As I continue to explore
9780 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
9781 what properties the system have, and how it will be affected by laws
9782 and regulations here in Norway. Here are some random notes.
</p
>
9784 <p
>One interesting thing to note is that since the transactions are
9785 verified using a peer to peer network, all details about a transaction
9786 is known to everyone. This means that if a BitCoin address has been
9787 published like I did with mine in my initial post about BitCoin, it is
9788 possible for everyone to see how many BitCoins have been transfered to
9789 that address. There is even a web service to look at the details for
9790 all transactions. There I can see that my address
9791 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
9792 have received
16.06 Bitcoin, the
9793 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
9794 address of Simon Phipps have received
181.97 BitCoin and the address
9795 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
9796 of EFF have received
2447.38 BitCoins so far. Thank you to each and
9797 every one of you that donated bitcoins to support my activity. The
9798 fact that anyone can see how much money was transfered to a given
9799 address make it more obvious why the BitCoin community recommend to
9800 generate and hand out a new address for each transaction. I
'm told
9801 there is no way to track which addresses belong to a given person or
9802 organisation without the person or organisation revealing it
9803 themselves, as Simon, EFF and I have done.
</p
>
9805 <p
>In Norway, and in most other countries, there are laws and
9806 regulations limiting how much money one can transfer across the border
9807 without declaring it. There are money laundering, tax and accounting
9808 laws and regulations I would expect to apply to the use of BitCoin.
9809 If the Skolelinux foundation
9810 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
9811 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
9812 normal bank transfers like EFF is doing, how should this be accounted?
9813 Given that it is impossible to know if money can cross the border or
9814 not, should everything or nothing be declared? What exchange rate
9815 should be used when calculating taxes? Would receivers have to pay
9816 income tax if the foundation were to pay Skolelinux contributors in
9817 BitCoin? I have no idea, but it would be interesting to know.
</p
>
9819 <p
>For a currency to be useful and successful, it must be trusted and
9820 accepted by a lot of users. It must be possible to get easy access to
9821 the currency (as a wage or using currency exchanges), and it must be
9822 easy to spend it. At the moment BitCoin seem fairly easy to get
9823 access to, but there are very few places to spend it. I am not really
9824 a regular user of any of the vendor types currently accepting BitCoin,
9825 so I wonder when my kind of shop would start accepting BitCoins. I
9826 would like to buy electronics, travels and subway tickets, not herbs
9827 and books. :) The currency is young, and this will improve over time
9828 if it become popular, but I suspect regular banks will start to lobby
9829 to get BitCoin declared illegal if it become popular. I
'm sure they
9830 will claim it is helping fund terrorism and money laundering (which
9831 probably would be true, as is any currency in existence), but I
9832 believe the problems should be solved elsewhere and not by blaming
9833 currencies.
</p
>
9835 <p
>The process of creating new BitCoins is called mining, and it is
9836 CPU intensive process that depend on a bit of luck as well (as one is
9837 competing against all the other miners currently spending CPU cycles
9838 to see which one get the next lump of cash). The
"winner
" get
50
9839 BitCoin when this happen. Yesterday I came across the obvious way to
9840 join forces to increase ones changes of getting at least some coins,
9841 by coordinating the work on mining BitCoins across several machines
9842 and people, and sharing the result if one is lucky and get the
50
9844 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
9845 if this sounds interesting. I have not had time to try to set up a
9846 machine to participate there yet, but have seen that running on ones
9847 own for a few days have not yield any BitCoins througth mining
9850 <p
>Update
2010-
12-
15: Found an
<a
9851 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
9852 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
9853 it was interesting to read. The arguments presented seem to be
9854 equally valid for gold, which was used as a currency for many years.
</p
>
9859 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
9860 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
9861 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
9862 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
9863 <description><p
>With this weeks lawless
9864 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
9865 attacks
</a
> on Wikileak and
9866 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
9867 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
9868 not be trusted to handle money transactions.
9870 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
9871 Phipps on bitcoin
</a
> reminded me about a project that a friend of
9872 mine mentioned earlier. I decided to follow Simon
's example, and get
9873 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
9874 some help from my friend to get it all running, and he even handed me
9875 some bitcoins to get started. I even donated a few bitcoins to Simon
9876 for helping me remember BitCoin.
</p
>
9878 <p
>So, what is bitcoins, you probably wonder? It is a digital
9879 crypto-currency, decentralised and handled using peer-to-peer
9880 networks. It allows anonymous transactions and prohibits central
9881 control over the transactions, making it impossible for governments
9882 and companies alike to block donations and other transactions. The
9883 source is free software, and while the key dependency wxWidgets
2.9
9884 for the graphical user interface is missing in Debian, the command
9885 line client builds just fine. Hopefully Jonas
9886 <a href=
"http://bugs.debian.org/
578157">will get the package into
9887 Debian
</a
> soon.
</p
>
9889 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
9890 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
9891 bitcoins
</a
> when selling services and goods, and there are even
9892 currency
"stock
" markets where the exchange rate is decided. There
9893 are not many users so far, but the concept seems promising. If you
9894 want to get started and lack a friend with any bitcoins to spare,
9896 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
9897 bitcoin at the time of writing). Use
9898 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
9899 on the current exchange rates.
</p
>
9901 <p
>As an experiment, I have decided to set up bitcoind on one of my
9902 machines. If you want to support my activity, please send Bitcoin
9903 donations to the address
9904 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
9909 <title>Why isn
't Debian Edu using VLC?
</title>
9910 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
9911 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
9912 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
9913 <description><p
>In the latest issue of Linux Journal, the readers choices were
9914 presented, and the winner among the multimedia player were VLC.
9915 Personally, I like VLC, and it is my player of choice when I first try
9916 to play a video file or stream. Only if VLC fail will I drag out
9917 gmplayer to see if it can do better. The reason is mostly the failure
9918 model and trust. When VLC fail, it normally pop up a error message
9919 reporting the problem. When mplayer fail, it normally segfault or
9920 just hangs. The latter failure mode drain my trust in the program.
<p
>
9922 <p
>But even if VLC is my player of choice, we have choosen to use
9923 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
9924 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
9925 plugin to play web videos seamlessly, and the VLC browser plugin is
9926 not very good. For example, it lack in-line control buttons, so there
9927 is no way for the user to pause the video. Also, when I
9928 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
9929 tested the browser plugins
</a
> available in Debian, the VLC plugin
9930 failed on several video pages where mplayer based plugins worked. If
9931 the browser plugin for VLC was as good as the gecko-mediaplayer
9932 package (which uses mplayer), we would switch.
</P
>
9934 <p
>While VLC is a good player, its user interface is slightly
9935 annoying. The most annoying feature is its inconsistent use of
9936 keyboard shortcuts. When the player is in full screen mode, its
9937 shortcuts are different from when it is playing the video in a window.
9938 For example, space only work as pause when in full screen mode. I
9939 wish it had consisten shortcuts and that space also would work when in
9940 window mode. Another nice shortcut in gmplayer is [enter] to restart
9941 the current video. It is very nice when playing short videos from the
9942 web and want to restart it when new people arrive to have a look at
9943 what is going on.
</p
>
9948 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
9949 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
9950 <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>
9951 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
9952 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
9953 upgrade testing of the
9954 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
9955 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
9956 This seem like a very good idea, so I adjusted by test scripts and
9957 can now present the updated result from today:
</p
>
9959 <p
>This is for Gnome:
</p
>
9961 <p
>Installed using apt-get, missing with aptitude
</p
>
9963 <blockquote
><p
>
9968 browser-plugin-gnash
9975 freedesktop-sound-theme
9977 gconf-defaults-service
9992 gnome-desktop-environment
9996 gnome-session-canberra
10001 gstreamer0.10-fluendo-mp3
10002 gstreamer0.10-tools
10004 gtk2-engines-pixbuf
10005 gtk2-engines-smooth
10007 libapache2-mod-dnssd
10010 libaprutil1-dbd-sqlite3
10013 libboost-date-time1.42
.0
10014 libboost-python1.42
.0
10015 libboost-thread1.42
.0
10017 libchamplain-gtk-
0.4-
0
10019 libclutter-gtk-
0.10-
0
10026 libfreerdp-plugins-standard
10039 libgnome-vfs2.0-cil
10041 libgnomepanel2.24-cil
10046 libgtksourceview2.0-common
10047 libmono-addins-gui0.2-cil
10048 libmono-addins0.2-cil
10049 libmono-cairo2.0-cil
10050 libmono-corlib2.0-cil
10051 libmono-i18n-west2.0-cil
10052 libmono-posix2.0-cil
10053 libmono-security2.0-cil
10054 libmono-sharpzip2.84-cil
10055 libmono-system2.0-cil
10058 libndesk-dbus-glib1.0-cil
10059 libndesk-dbus1.0-cil
10069 libtelepathy-farsight0
10078 nautilus-sendto-empathy
10082 python-aptdaemon-gtk
10084 python-beautifulsoup
10099 python-gtksourceview2
10110 python-pkg-resources
10117 python-twisted-conch
10118 python-twisted-core
10123 python-zope.interface
10125 remmina-plugin-data
10128 rhythmbox-plugin-cdrecorder
10135 system-config-printer-udev
10137 telepathy-mission-control-
5
10144 transmission-common
10148 </p
></blockquote
>
10150 <p
>Installed using apt-get, removed with aptitude
</p
>
10152 <blockquote
><p
>
10156 epiphany-extensions
10158 fast-user-switch-applet
10177 libgtksourceview2.0-
0
10179 libsdl1.2debian-alsa
10185 system-config-printer
10190 </p
></blockquote
>
10192 <p
>Installed using aptitude, missing with apt-get
</p
>
10194 <blockquote
><p
>
10195 gstreamer0.10-gnomevfs
10196 </p
></blockquote
>
10198 <p
>Installed using aptitude, removed with apt-get
</p
>
10200 <blockquote
><p
>
10202 </p
></blockquote
>
10204 <p
>This is for KDE:
</p
>
10206 <p
>Installed using apt-get, missing with aptitude
</p
>
10208 <blockquote
><p
>
10210 </p
></blockquote
>
10212 <p
>Installed using apt-get, removed with aptitude
</p
>
10214 <blockquote
><p
>
10216 network-manager-kde
10217 </p
></blockquote
>
10219 <p
>Installed using aptitude, missing with apt-get
</p
>
10221 <blockquote
><p
>
10235 kdeartwork-emoticons
10237 kdeartwork-theme-icon
10241 kdebase-workspace-bin
10242 kdebase-workspace-data
10254 konqueror-nsplugins
10256 kscreensaver-xsavers
10271 plasma-dataengines-workspace
10273 plasma-desktopthemes-artwork
10274 plasma-runners-addons
10275 plasma-scriptengine-googlegadgets
10276 plasma-scriptengine-python
10277 plasma-scriptengine-qedje
10278 plasma-scriptengine-ruby
10279 plasma-scriptengine-webkit
10280 plasma-scriptengines
10281 plasma-wallpapers-addons
10282 plasma-widget-folderview
10283 plasma-widget-networkmanagement
10286 update-notifier-kde
10287 xscreensaver-data-extra
10289 xscreensaver-gl-extra
10290 xscreensaver-screensaver-bsod
10291 </p
></blockquote
>
10293 <p
>Installed using aptitude, removed with apt-get
</p
>
10295 <blockquote
><p
>
10297 google-gadgets-common
10315 libggadget-qt-
1.0-
0b
10320 libkonqsidebarplugin4a
10324 libkunitconversion4
10329 libplasma-geolocation-interface4
10331 libplasmagenericshell4
10345 libsmokeknewstuff2-
3
10346 libsmokeknewstuff3-
3
10348 libsmokektexteditor3
10356 libsmokeqtnetwork4-
3
10357 libsmokeqtopengl4-
3
10358 libsmokeqtscript4-
3
10362 libsmokeqtuitools4-
3
10363 libsmokeqtwebkit4-
3
10374 plasma-dataengines-addons
10375 plasma-scriptengine-superkaramba
10376 plasma-widget-lancelot
10377 plasma-widgets-addons
10378 plasma-widgets-workspace
10382 update-notifier-common
10383 </p
></blockquote
>
10385 <p
>Running apt-get autoremove made the results using apt-get and
10386 aptitude a bit more similar, but there are still quite a lott of
10387 differences. I have no idea what packages should be installed after
10388 the upgrade, but hope those that do can have a look.
</p
>
10393 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
10394 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
10395 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
10396 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
10397 <description><p
>Most of the computers in use by the
10398 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
10399 are virtual machines. And they have been Xen machines running on a
10400 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
10401 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
10402 bit harder that it could have been, because we set up the Xen virtual
10403 machines to get the virtual partitions from LVM, which as far as I
10404 know is not supported by KVM. So to migrate, we had to convert
10405 several LVM logical volumes to partitions on a virtual disk file.
</p
>
10408 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
10409 nice recipe
</a
> to do this, and wrote the following script to do the
10410 migration. It uses qemu-img from the qemu package to make the disk
10411 image, parted to partition it, losetup and kpartx to present the disk
10412 image partions as devices, and dd to copy the data. I NFS mounted the
10413 new servers storage area on the old server to do the migration.
</p
>
10419 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
10424 if [ -z
"$
1" ] ; then
10425 echo
"Usage: $
0 &lt;hostname
&gt;
"
10428 host=
"$
1"
10431 if [ ! -e /dev/vg_data/$host-disk ] ; then
10432 echo
"error: unable to find LVM volume for $host
"
10436 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
10437 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
10438 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
10439 totalsize=$(( ( $disksize + $swapsize ) ))
10442 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
10443 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
10445 parted $img mklabel msdos
10446 parted $img mkpart primary linux-swap
0 $disksize
10447 parted $img mkpart primary ext2 $disksize $totalsize
10448 parted $img set
1 boot on
10451 losetup /dev/loop0 $img
10452 kpartx -a /dev/loop0
10454 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
10455 fsck.ext3 -f /dev/mapper/loop0p1 || true
10456 mkswap /dev/mapper/loop0p2
10458 kpartx -d /dev/loop0
10459 losetup -d /dev/loop0
10462 <p
>The script is perhaps so simple that it is not copyrightable, but
10463 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
10465 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
10466 the new disk image attached, installed grub-pc and linux-image-
686 and
10467 set up grub to boot from the disk image. After this, the KVM machines
10468 seem to work just fine.
</p
>
10473 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
10474 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
10475 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
10476 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
10477 <description><p
>I
'm still running upgrade testing of the
10478 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
10479 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
10480 status. Here is a short update based on a test I ran
20101118.
</p
>
10482 <p
>I still do not know what a correct migration should look like, so I
10483 report any differences between apt and aptitude and hope someone else
10484 can see if anything should be changed.
</p
>
10486 <p
>This is for Gnome:
</p
>
10488 <p
>Installed using apt-get, missing with aptitude
</p
>
10490 <blockquote
><p
>
10491 apache2.2-bin aptdaemon at-spi baobab binfmt-support
10492 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
10493 dmz-cursor-theme empathy empathy-common finger
10494 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
10495 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
10496 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
10497 gnome-cards-data gnome-codec-install gnome-core
10498 gnome-desktop-environment gnome-disk-utility gnome-screenshot
10499 gnome-search-tool gnome-session-canberra gnome-spell
10500 gnome-system-log gnome-themes-extras gnome-themes-more
10501 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
10502 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
10503 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
10504 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
10505 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
10506 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
10507 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
10508 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
10509 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
10510 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
10511 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
10512 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
10513 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
10514 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
10515 libgtk2.0-cil libgtkglext1 libgtksourceview-common
10516 libgtksourceview2.0-common libmono-addins-gui0.2-cil
10517 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
10518 libmono-i18n-west2.0-cil libmono-posix2.0-cil
10519 libmono-security2.0-cil libmono-sharpzip2.84-cil
10520 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
10521 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
10522 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
10523 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
10524 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
10525 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
10526 libxalan2-java libxerces2-java media-player-info mesa-utils
10527 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
10528 nautilus-sendto-empathy openoffice.org-writer2latex
10529 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
10530 python-aptdaemon python-aptdaemon-gtk python-axiom
10531 python-beautifulsoup python-bugbuddy python-clientform
10532 python-coherence python-configobj python-crypto python-cupshelpers
10533 python-cupsutils python-eggtrayicon python-elementtree
10534 python-epsilon python-evolution python-feedparser python-gdata
10535 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
10536 python-gtksourceview2 python-httplib2 python-louie python-mako
10537 python-markupsafe python-mechanize python-nevow python-notify
10538 python-opengl python-openssl python-pam python-pkg-resources
10539 python-pyasn1 python-pysqlite2 python-rdflib python-serial
10540 python-tagpy python-twisted-bin python-twisted-conch
10541 python-twisted-core python-twisted-web python-utidylib python-webkit
10542 python-xdg python-zope.interface remmina remmina-plugin-data
10543 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
10544 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
10545 software-center svgalibg1 system-config-printer-udev
10546 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
10547 totem totem-coherence totem-mozilla totem-plugins
10548 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
10550 </p
></blockquote
>
10552 Installed using apt-get, removed with aptitude
10554 <blockquote
><p
>
10555 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
10556 epiphany-extensions epiphany-gecko evolution-exchange
10557 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
10558 gedit-common gnome-app-install gnome-games gnome-games-data
10559 gnome-nettool gnome-system-tools gnome-themes gnome-utils
10560 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
10561 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
10562 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
10563 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
10564 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
10565 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
10566 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
10567 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
10568 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
10569 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
10570 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
10571 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
10572 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
10573 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
10574 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
10575 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
10576 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
10577 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
10578 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
10579 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
10580 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
10581 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
10582 sound-juicer swfdec-gnome system-config-printer totem-common
10583 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
10584 </p
></blockquote
>
10586 <p
>Installed using aptitude, missing with apt-get
</p
>
10588 <blockquote
><p
>
10589 gstreamer0.10-gnomevfs
10590 </p
></blockquote
>
10592 <p
>Installed using aptitude, removed with apt-get
</p
>
10594 <blockquote
><p
>
10596 </p
></blockquote
>
10598 <p
>This is for KDE:
</p
>
10600 <p
>Installed using apt-get, missing with aptitude
</p
>
10602 <blockquote
><p
>
10603 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
10604 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
10605 ghostscript-x git gnome-audio gnugo granatier gs-common
10606 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
10607 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
10608 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
10609 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10610 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
10611 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
10612 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10613 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
10614 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
10615 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
10616 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
10617 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
10618 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
10619 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
10620 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
10621 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
10622 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
10623 libkrossui4 libmailtools-perl libmime-tools-perl
10624 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
10625 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
10626 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
10627 lirc luatex marble networkstatus noatun-plugins
10628 openoffice.org-writer2latex palapeli palapeli-data parley
10629 parley-data poster psutils pulseaudio pulseaudio-esound-compat
10630 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
10631 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
10632 ttf-sazanami-gothic
10633 </p
></blockquote
>
10635 <p
>Installed using apt-get, removed with aptitude
</p
>
10637 <blockquote
><p
>
10638 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
10639 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
10640 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
10641 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
10642 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
10643 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
10644 kitchensync kiten kjumpingcube klatin klettres klickety klines
10645 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
10646 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
10647 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
10648 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
10649 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
10650 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
10651 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
10652 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
10653 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10654 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
10655 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
10656 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10657 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
10658 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
10659 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
10660 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
10661 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10662 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
10663 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
10664 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
10665 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
10666 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
10667 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
10668 mpeglib network-manager-kde noatun pmount tex-common texlive-base
10669 texlive-common texlive-doc-base texlive-fonts-recommended tidy
10670 ttf-dustin ttf-kochi-gothic ttf-sjfonts
10671 </p
></blockquote
>
10673 <p
>Installed using aptitude, missing with apt-get
</p
>
10675 <blockquote
><p
>
10676 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
10677 kdeartwork kdebase kdebase-apps kdebase-workspace
10678 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
10679 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
10680 netpbm plasma-widget-folderview plasma-widget-networkmanagement
10681 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
10682 xscreensaver-screensaver-bsod
10683 </p
></blockquote
>
10685 <p
>Installed using aptitude, removed with apt-get
</p
>
10687 <blockquote
><p
>
10688 kdebase-bin konq-plugins konqueror
10689 </p
></blockquote
>
10694 <title>Gnash buildbot slave and Debian kfreebsd
</title>
10695 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
10696 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
10697 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
10698 <description><p
>Answering
10699 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
10700 call from the Gnash project
</a
> for
10701 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
10702 current source, I have set up a virtual KVM machine on the Debian
10703 Edu/Skolelinux virtualization host to test the git source on
10704 Debian/Squeeze. I hope this can help the developers in getting new
10705 releases out more often.
</p
>
10707 <p
>As the developers want less main-stream build platforms tested to,
10708 I have considered setting up a
<a
10709 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
10710 machine as well. I have also considered using the kfreebsd
10711 architecture in Debian as a file server in NUUG to get access to the
5
10712 TB zfs volume we currently use to store DV video. Because of this, I
10713 finally got around to do a test installation of Debian/Squeeze with
10714 kfreebsd. Installation went fairly smooth, thought I noticed some
10715 visual glitches in the cdebconf dialogs (black cursor left on the
10716 screen at random locations). Have not gotten very far with the
10717 testing. Noticed cfdisk did not work, but fdisk did so it was not a
10718 fatal problem. Have to spend some more time on it to see if it is
10719 useful as a file server for NUUG. Will try to find time to set up a
10720 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
10725 <title>Debian in
3D
</title>
10726 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
10727 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
10728 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
10729 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
10731 <p
>3D printing is just great. I just came across this Debian logo in
10733 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
10734 thingiverse blog
</a
>.
</p
>
10739 <title>Software updates
2010-
10-
24</title>
10740 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
10741 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
10742 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
10743 <description><p
>Some updates.
</p
>
10745 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
10746 raise money for the project is going well. The lower limit of
10
10747 signers was reached in
24 hours, and so far
13 people have signed it.
10748 More signers and more funding is most welcome, and I am really curious
10749 how far we can get before the time limit of December
24 is reached.
10752 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
10753 about what appear to be a great code coverage tool capable of
10754 generating code coverage stats without any changes to the source code.
10756 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
10757 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
10758 It is missing in Debian, but the git source built just fine in Squeeze
10759 after I installed libelf-dev, libdwarf-dev, pkg-config and
10760 libglib2.0-dev. Failed to build in Lenny, but suspect that is
10761 solvable. I hope kcov make it into Debian soon.
</p
>
10763 <p
>Finally found time to wrap up the release notes for
<a
10764 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
10765 new alpha release of Debian Edu
</a
>, and just published the second
10766 alpha test release of the Squeeze based Debian Edu /
10767 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
10768 release. Give it a try if you need a complete linux solution for your
10769 school, including central infrastructure server, workstations, thin
10770 client servers and diskless workstations. A nice touch added
10771 yesterday is RDP support on the thin client servers, for windows
10772 clients to get a Linux desktop on request.
</p
>
10777 <title>Some notes on Flash in Debian and Debian Edu
</title>
10778 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
10779 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
10780 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
10781 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
10782 popularity-contest numbers
</a
>, the adobe-flashplugin package the
10783 second most popular used package that is missing in Debian. The sixth
10784 most popular is flashplayer-mozilla. This is a clear indication that
10785 working flash is important for Debian users. Around
10 percent of the
10786 users submitting data to popcon.debian.org have this package
10787 installed.
</p
>
10789 <p
>In the report written by Lars Risan in August
2008
10790 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
10791 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
10792 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
10793 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
10794 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
10795 web sites require Flash to work, and lacking working Flash support in
10796 the web browser and the problems with installing it was perceived as a
10797 good reason to stay with Windows.
</p
>
10799 <p
>I once saw a funny and sad comment in a web forum, where Linux was
10800 said to be the retarded cousin that did not really understand
10801 everything you told him but could work fairly well. This was a
10802 comment regarding the problems Linux have with proprietary formats and
10803 non-standard web pages, and is sad because it exposes a fairly common
10804 understanding of whose fault it is if web pages that only work in for
10805 example Internet Explorer
6 fail to work on Firefox, and funny because
10806 it explain very well how annoying it is for users when Linux
10807 distributions do not work with the documents they receive or the web
10808 pages they want to visit.
</p
>
10810 <p
>This is part of the reason why I believe it is important for Debian
10811 and Debian Edu to have a well working Flash implementation in the
10812 distribution, to get at least popular sites as Youtube and Google
10813 Video to working out of the box. For Squeeze, Debian have the chance
10814 to include the latest version of Gnash that will make this happen, as
10815 the new release
0.8.8 was published a few weeks ago and is resting in
10816 unstable. The new version work with more sites that version
0.8.7.
10817 The Gnash maintainers have asked for a freeze exception, but the
10818 release team have not had time to reply to it yet. I hope they agree
10819 with me that Flash is important for the Debian desktop users, and thus
10820 accept the new package into Squeeze.
</p
>
10825 <title>Circular package dependencies harms apt recovery
</title>
10826 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
10827 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
10828 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
10829 <description><p
>I discovered this while doing
10830 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
10831 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
10832 in Debian still got circular dependencies, and it is often claimed
10833 that apt and aptitude should be able to handle this just fine, but
10834 some times these dependency loops causes apt to fail.
</p
>
10836 <p
>An example is from todays
10837 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
10838 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
10839 causes perl-modules to fail to upgrade. The cause is simple. If a
10840 package fail to unpack, then only part of packages with the circular
10841 dependency might end up being unpacked when unpacking aborts, and the
10842 ones already unpacked will fail to configure in the recovery phase
10843 because its dependencies are unavailable.
</p
>
10845 <p
>In this log, the problem manifest itself with this error:
</p
>
10847 <blockquote
><pre
>
10848 dpkg: dependency problems prevent configuration of perl-modules:
10849 perl-modules depends on perl (
>=
5.10.1-
1); however:
10850 Version of perl on system is
5.10.0-
19lenny
2.
10851 dpkg: error processing perl-modules (--configure):
10852 dependency problems - leaving unconfigured
10853 </pre
></blockquote
>
10855 <p
>The perl/perl-modules circular dependency is already
10856 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
10857 hopefully be solved as soon as possible, but it is not the only one,
10858 and each one of these loops in the dependency tree can cause similar
10859 failures. Of course, they only occur when there are bugs in other
10860 packages causing the unpacking to fail, but it is rather nasty when
10861 the failure of one package causes the problem to become worse because
10862 of dependency loops.
</p
>
10865 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
10866 tireless effort by Bill Allombert
</a
>, the number of circular
10868 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
10869 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
10871 <p
>Todays testing also exposed a bug in
10872 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
10873 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
10874 apt-get and aptitude, the latter possibly caused by some circular
10875 dependency. Reported both to BTS to try to get someone to look at
10881 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
10882 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
10883 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
10884 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
10885 <description><p
>This is a
10886 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
10888 <a href=
"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
">previous
10890 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
10891 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
10893 <p
>As a step to try to see if it possible to merge the DNS and DHCP
10894 LDAP objects, I have had a look at how the packages pdns-backend-ldap
10895 and dhcp3-server-ldap in Debian use the LDAP server. The two
10896 implementations are quite different in how they use LDAP.
</p
>
10898 To get this information, I started slapd with debugging enabled and
10899 dumped the debug output to a file to get the LDAP searches performed
10900 on a Debian Edu main-server. Here is a summary.
10902 <p
><strong
>powerdns
</strong
></p
>
10904 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
10905 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
10908 <p
>PowerDNS have two modes of operation using LDAP as its backend.
10909 One
"strict
" mode where the forward and reverse DNS lookups are done
10910 using the same LDAP objects, and a
"tree
" mode where the forward and
10911 reverse entries are in two different subtrees in LDAP with a structure
10912 based on the DNS names, as in tjener.intern and
10913 2.2.0.10.in-addr.arpa.
</p
>
10915 <p
>In tree mode, the server is set up to use a LDAP subtree as its
10916 base, and uses a
"base
" scoped search for the DNS name by adding
10917 "dc=tjener,dc=intern,
" to the base with a filter for
10918 "(associateddomain=tjener.intern)
" for the forward entry and
10919 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
10920 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
10921 forward entries, it is looking for attributes named dnsttl, arecord,
10922 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
10923 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
10924 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
10925 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
10926 spfrecord and modifytimestamp. For reverse entries it is looking for
10927 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
10928 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
10929 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
10930 ldapsearch commands could look like this:
</p
>
10932 <blockquote
><pre
>
10933 ldapsearch -h ldap \
10934 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10935 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
10936 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10937 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10938 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10939 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10941 ldapsearch -h ldap \
10942 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
10943 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
10944 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
10945 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
10946 srvrecord naptrrecord modifytimestamp
10947 </pre
></blockquote
>
10949 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
10950 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
10951 example LDAP objects used there. In addition to these objects, the
10952 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
10953 also exist.
</p
>
10955 <blockquote
><pre
>
10956 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
10958 objectclass: dnsdomain
10959 objectclass: domainrelatedobject
10962 associateddomain: tjener.intern
10964 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
10966 objectclass: dnsdomain2
10967 objectclass: domainrelatedobject
10969 ptrrecord: tjener.intern
10970 associateddomain:
2.2.0.10.in-addr.arpa
10971 </pre
></blockquote
>
10973 <p
>In strict mode, the server behaves differently. When looking for
10974 forward DNS entries, it is doing a
"subtree
" scoped search with the
10975 same base as in the tree mode for a object with filter
10976 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
10977 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
10978 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
10979 naptrrecord and modifytimestamp. For reverse entires it also do a
10980 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
10981 and the requested attributes are associateddomain, dnsttl and
10982 modifytimestamp. In short, in strict mode the objects with ptrrecord
10983 go away, and the arecord attribute in the forward object is used
10986 <p
>The forward and reverse searches can be simulated using ldapsearch
10987 like this:
</p
>
10989 <blockquote
><pre
>
10990 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10991 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
10992 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
10993 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
10994 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
10995 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
10997 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
10998 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
10999 </pre
></blockquote
>
11001 <p
>In addition to the forward and reverse searches , there is also a
11002 search for SOA records, which behave similar to the forward and
11003 reverse lookups.
</p
>
11005 <p
>A thing to note with the PowerDNS behaviour is that it do not
11006 specify any objectclass names, and instead look for the attributes it
11007 need to generate a DNS reply. This make it able to work with any
11008 objectclass that provide the needed attributes.
</p
>
11010 <p
>The attributes are normally provided in the cosine (RFC
1274) and
11011 dnsdomain2 schemas. The latter is used for reverse entries like
11012 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
11014 <p
>In Debian Edu, we have created DNS objects using the object classes
11015 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11016 attributes) and domainrelatedobject (for associatedDomain). The use
11017 of structural object classes make it impossible to combine these
11018 classes with the object classes used by DHCP.
</p
>
11020 <p
>There are other schemas that could be used too, for example the
11021 dnszone structural object class used by Gosa and bind-sdb for the DNS
11022 attributes combined with the domainrelatedobject object class, but in
11023 this case some unused attributes would have to be included as well
11024 (zonename and relativedomainname).
</p
>
11026 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
11027 mode and not use any of the existing objectclasses (dnsdomain,
11028 dnsdomain2 and dnszone) when one want to combine the DNS information
11029 with DHCP information, and instead create a auxiliary object class
11030 defined something like this (using the attributes defined for
11031 dnsdomain and dnsdomain2 or dnszone):
</p
>
11033 <blockquote
><pre
>
11034 objectclass ( some-oid NAME
'dnsDomainAux
'
11037 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11038 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11039 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11040 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11041 A6Record $ DNAMERecord
11043 </pre
></blockquote
>
11045 <p
>This will allow any object to become a DNS entry when combined with
11046 the domainrelatedobject object class, and allow any entity to include
11047 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
11048 developers asking for their view on this schema and if they are
11049 interested in providing such schema with PowerDNS, and I hope my
11050 message will be accepted into their mailing list soon.
</p
>
11052 <p
><strong
>ISC dhcp
</strong
></p
>
11054 <p
>The DHCP server searches for specific objectclass and requests all
11055 the object attributes, and then uses the attributes it want. This
11056 make it harder to figure out exactly what attributes are used, but
11057 thanks to the working example in Debian Edu I can at least get an idea
11058 what is needed without having to read the source code.
</p
>
11060 <p
>In the DHCP server configuration, the LDAP base to use and the
11061 search filter to use to locate the correct dhcpServer entity is
11062 stored. These are the relevant entries from
11063 /etc/dhcp3/dhcpd.conf:
</p
>
11065 <blockquote
><pre
>
11066 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
11067 ldap-dhcp-server-cn
"dhcp
";
11068 </pre
></blockquote
>
11070 <p
>The DHCP server uses this information to nest all the DHCP
11071 configuration it need. The cn
"dhcp
" is located using the given LDAP
11072 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
11073 search result is this entry:
</p
>
11075 <blockquote
><pre
>
11076 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11079 objectClass: dhcpServer
11080 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11081 </pre
></blockquote
>
11083 <p
>The content of the dhcpServiceDN attribute is next used to locate the
11084 subtree with DHCP configuration. The DHCP configuration subtree base
11085 is located using a base scope search with base
"cn=DHCP
11086 Config,dc=skole,dc=skolelinux,dc=no
" and filter
11087 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
11088 The search result is this entry:
</p
>
11090 <blockquote
><pre
>
11091 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11094 objectClass: dhcpService
11095 objectClass: dhcpOptions
11096 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11097 dhcpStatements: ddns-update-style none
11098 dhcpStatements: authoritative
11099 dhcpOption: smtp-server code
69 = array of ip-address
11100 dhcpOption: www-server code
72 = array of ip-address
11101 dhcpOption: wpad-url code
252 = text
11102 </pre
></blockquote
>
11104 <p
>Next, the entire subtree is processed, one level at the time. When
11105 all the DHCP configuration is loaded, it is ready to receive requests.
11106 The subtree in Debian Edu contain objects with object classes
11107 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11108 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11109 and information about netmasks, dynamic range etc. Leaving out the
11110 details here because it is not relevant for the focus of my
11111 investigation, which is to see if it is possible to merge dns and dhcp
11112 related computer objects.
</p
>
11114 <p
>When a DHCP request come in, LDAP is searched for the MAC address
11115 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
11116 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
11117 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11118 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
11121 <blockquote
><pre
>
11122 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11125 objectClass: dhcpHost
11126 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11127 dhcpStatements: fixed-address hostname
11128 </pre
></blockquote
>
11130 <p
>There is less flexiblity in the way LDAP searches are done here.
11131 The object classes need to have fixed names, and the configuration
11132 need to be stored in a fairly specific LDAP structure. On the
11133 positive side, the invidiual dhcpHost entires can be anywhere without
11134 the DN pointed to by the dhcpServer entries. The latter should make
11135 it possible to group all host entries in a subtree next to the
11136 configuration entries, and this subtree can also be shared with the
11137 DNS server if the schema proposed above is combined with the dhcpHost
11138 structural object class.
11140 <p
><strong
>Conclusion
</strong
></p
>
11142 <p
>The PowerDNS implementation seem to be very flexible when it come
11143 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
11144 come to the the LDAP structure, the
"strict
" mode is very flexible,
11145 allowing DNS objects to be stored anywhere under the base cn specified
11146 in the configuration.
</p
>
11148 <p
>The DHCP implementation on the other hand is very inflexible, both
11149 regarding which LDAP schemas to use and which LDAP structure to use.
11150 I guess one could implement ones own schema, as long as the
11151 objectclasses and attributes have the names used, but this do not
11152 really help when the DHCP subtree need to have a fairly fixed
11153 structure.
</p
>
11155 <p
>Based on the observed behaviour, I suspect a LDAP structure like
11156 this might work for Debian Edu:
</p
>
11158 <blockquote
><pre
>
11160 cn=machine-info (dhcpService) - dhcpServiceDN points here
11161 cn=dhcp (dhcpServer)
11162 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11163 cn=
10.0.2.0 (dhcpSubnet)
11164 cn=group1 (dhcpGroup/dhcpOptions)
11165 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11166 cn=
192.168.0.0 (dhcpSubnet)
11167 cn=group1 (dhcpGroup/dhcpOptions)
11168 ou=machines - PowerDNS base points here
11169 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11170 </pre
></blockquote
>
11172 <P
>This is not tested yet. If the DHCP server require the dhcpHost
11173 entries to be in the dhcpGroup subtrees, the entries can be stored
11174 there instead of a common machines subtree, and the PowerDNS base
11175 would have to be moved one level up to the machine-info subtree.
</p
>
11177 <p
>The combined object under the machines subtree would look something
11178 like this:
</p
>
11180 <blockquote
><pre
>
11181 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11184 objectClass: dhcpHost
11185 objectclass: domainrelatedobject
11186 objectclass: dnsDomainAux
11187 associateddomain: hostname.intern
11188 arecord:
10.11.12.13
11189 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11190 dhcpStatements: fixed-address hostname.intern
11191 </pre
></blockquote
>
11193 </p
>One could even add the LTSP configuration associated with a given
11194 machine, as long as the required attributes are available in a
11195 auxiliary object class.
</p
>
11200 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
11201 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
11202 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
11203 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
11204 <description><p
>For a while now, I have wanted to find a way to change the DNS and
11205 DHCP services in Debian Edu to use the same LDAP objects for a given
11206 computer, to avoid the possibility of having a inconsistent state for
11207 a computer in LDAP (as in DHCP but no DNS entry or the other way
11208 around) and make it easier to add computers to LDAP.
</p
>
11210 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
11211 information finally found a solution that seem to work.
</p
>
11213 <p
>The old setup required three LDAP objects for a given computer.
11214 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11215 we switch powerdns to use its strict LDAP method (ldap-method=strict
11216 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11217 merged into one while making it impossible to transfer the reverse map
11218 to a slave DNS server.
</p
>
11220 <p
>If we also replace the object class used to get the DNS related
11221 attributes to one allowing these attributes to be combined with the
11222 dhcphost object class, we can merge the DNS and DHCP entries into one.
11223 I
've written such object class in the dnsdomainaux.schema file (need
11224 proper OIDs, but that is a minor issue), and tested the setup. It
11225 seem to work.
</p
>
11227 <p
>With this test setup in place, we can get away with one LDAP object
11228 for both DNS and DHCP, and even the LTSP configuration I suggested in
11229 an earlier email. The combined LDAP object will look something like
11232 <blockquote
><pre
>
11233 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11235 objectClass: dhcphost
11236 objectclass: domainrelatedobject
11237 objectclass: dnsdomainaux
11238 associateddomain: hostname.intern
11239 arecord:
10.11.12.13
11240 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
11241 dhcpstatements: fixed-address hostname
11243 </pre
></blockquote
>
11245 <p
>The DNS server uses the associateddomain and arecord entries, while
11246 the DHCP server uses the dhcphwaddress and dhcpstatements entries
11247 before asking DNS to resolve the fixed-adddress. LTSP will use
11248 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
11250 <p
>I am not yet sure if I can get the DHCP server to look for its
11251 dhcphost in a different location, to allow us to put the objects
11252 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
11253 that. If I can
't figure out a way to do that, we can still get rid of
11254 the hosts subtree and move all its content into the DHCP Config tree
11255 (which probably should be renamed to be more related to the new
11256 content. I suspect cn=dnsdhcp,ou=services or something like that
11257 might be a good place to put it.
</p
>
11259 <p
>If you want to help out with implementing this for Debian Edu,
11260 please contact us on debian-edu@lists.debian.org.
</p
>
11265 <title>Idea for storing LTSP configuration in LDAP
</title>
11266 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
11267 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
11268 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
11269 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
11270 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
11271 clients, and that this can be used to fetch configuration from LDAP if
11272 Debian Edu choose to store configuration there.
</p
>
11274 <p
>Armed with this information, I got inspired and wrote a test module
11275 to get configuration from LDAP. The idea is to look up the MAC
11276 address of the client in LDAP, and look for attributes on the form
11277 ltspconfigsetting=value, and use this to export SETTING=value to the
11278 LTSP clients.
</p
>
11280 <p
>The goal is to be able to store the LTSP configuration attributes
11281 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
11282 allowing us to store all information about a computer in one place.
</p
>
11284 <p
>This is a untested draft implementation, and I welcome feedback on
11285 this approach. A real LDAP schema for the ltspClientAux objectclass
11286 need to be written. Comments, suggestions, etc?
</p
>
11288 <blockquote
><pre
>
11289 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
11291 # Fetch LTSP client settings from LDAP based on MAC address
11293 # Uses ethernet address as stored in the dhcpHost objectclass using
11294 # the dhcpHWAddress attribute or ethernet address stored in the
11295 # ieee802Device objectclass with the macAddress attribute.
11297 # This module is written to be schema agnostic, and only depend on the
11298 # existence of attribute names.
11300 # The LTSP configuration variables are saved directly using a
11301 # ltspConfig prefix and uppercasing the rest of the attribute name.
11302 # To set the SERVER variable, set the ltspConfigServer attribute.
11304 # Some LDAP schema should be created with all the relevant
11305 # configuration settings. Something like this should work:
11307 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
11310 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
11312 LDAPSERVER=$(debian-edu-ldapserver)
11313 if [
"$LDAPSERVER
" ] ; then
11314 LDAPBASE=$(debian-edu-ldapserver -b)
11315 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
11316 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
11317 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
11318 grep
'^ltspConfig
' | while read attr value ; do
11319 # Remove prefix and convert to upper case
11320 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
11321 # bass value on to clients
11322 eval
"$attr=$value; export $attr
"
11326 </pre
></blockquote
>
11328 <p
>I
'm not sure this shell construction will work, because I suspect
11329 the while block might end up in a subshell causing the variables set
11330 there to not show up in ltsp-config, but if that is the case I am sure
11331 the code can be restructured to make sure the variables are passed on.
11332 I expect that can be solved with some testing. :)
</p
>
11334 <p
>If you want to help out with implementing this for Debian Edu,
11335 please contact us on debian-edu@lists.debian.org.
</p
>
11337 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
11338 configuration in LDAP that was created around year
2000 by
11339 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
11340 Xperience, Inc.,
2000</a
>. I found its
11341 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
11342 personal home page over at redhat.com.
</p
>
11347 <title>jXplorer, a very nice LDAP GUI
</title>
11348 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
11349 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
11350 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
11351 <description><p
>Since
11352 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
11353 last post
</a
> about available LDAP tools in Debian, I was told about a
11354 LDAP GUI that is even better than luma. The java application
11355 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
11356 moving LDAP objects and subtrees using drag-and-drop, and can
11357 authenticate using Kerberos. I have only tested the Kerberos
11358 authentication, but do not have a LDAP setup allowing me to rewrite
11359 LDAP with my test user yet. It is
11360 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
11361 Debian
</a
> testing and unstable at the moment. The only problem I
11362 have with it is how it handle errors. If something go wrong, its
11363 non-intuitive behaviour require me to go through some query work list
11364 and remove the failing query. Nothing big, but very annoying.
</p
>
11369 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
11370 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
11371 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
11372 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
11373 <description><p
>Here is a short update on my
<a
11374 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
11375 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
11376 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
11377 not reporting the status for KDE, because the upgrade crashes when
11378 aptitude try because of missing conflicts
11379 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
11380 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
11382 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
11383 complete list of the installed packages. Based on this I see these
11384 differences when I did a test run today. As usual, I do not really
11385 know what the correct set of packages would be, but thought it best to
11386 publish the difference.
</p
>
11388 <p
>Installed using apt-get, missing with aptitude
</p
>
11390 <blockquote
><p
>
11391 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
11392 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
11393 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
11394 libgtksourceview-common libpt-
1.10.10-plugins-alsa
11395 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
11396 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
11397 python-
4suite-xml python-eggtrayicon python-gtkhtml2
11398 python-gtkmozembed svgalibg1 xserver-xephyr zip
11399 </p
></blockquote
>
11401 <p
>Installed using apt-get, removed with aptitude
</p
>
11403 <blockquote
><p
>
11404 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
11405 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
11406 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
11407 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
11408 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
11409 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
11410 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
11411 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
11412 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
11413 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
11414 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
11415 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
11416 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
11417 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
11418 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
11419 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
11420 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
11421 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
11422 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
11423 mysql-common swfdec-gnome totem-gstreamer wodim
11424 </p
></blockquote
>
11426 <p
>Installed using aptitude, missing with apt-get
</p
>
11428 <blockquote
><p
>
11429 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
11430 python-gnomekeyring python-wnck rhythmbox-plugins xorg
11431 xserver-xorg-input-all xserver-xorg-input-evdev
11432 xserver-xorg-input-kbd xserver-xorg-input-mouse
11433 xserver-xorg-input-synaptics xserver-xorg-video-all
11434 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
11435 xserver-xorg-video-chips xserver-xorg-video-cirrus
11436 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11437 xserver-xorg-video-glint xserver-xorg-video-i128
11438 xserver-xorg-video-i740 xserver-xorg-video-mach64
11439 xserver-xorg-video-mga xserver-xorg-video-neomagic
11440 xserver-xorg-video-nouveau xserver-xorg-video-nv
11441 xserver-xorg-video-r128 xserver-xorg-video-radeon
11442 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
11443 xserver-xorg-video-s3 xserver-xorg-video-s3virge
11444 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
11445 xserver-xorg-video-sis xserver-xorg-video-sisusb
11446 xserver-xorg-video-tdfx xserver-xorg-video-tga
11447 xserver-xorg-video-trident xserver-xorg-video-tseng
11448 xserver-xorg-video-vesa xserver-xorg-video-vmware
11449 xserver-xorg-video-voodoo
11450 </p
></blockquote
>
11452 <p
>Installed using aptitude, removed with apt-get
</p
>
11454 <blockquote
><p
>
11455 deskbar-applet xserver-xorg xserver-xorg-core
11456 xserver-xorg-input-wacom xserver-xorg-video-intel
11457 xserver-xorg-video-openchrome
11458 </p
></blockquote
>
11460 <p
>I was told on IRC that the xorg-xserver package was
11461 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
11462 in git
</a
> today to try to get apt-get to not remove xorg completely.
11463 No idea when it hits Squeeze, but when it does I hope it will reduce
11464 the difference somewhat.
11469 <title>LUMA, a very nice LDAP GUI
</title>
11470 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
11471 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
11472 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
11473 <description><p
>The last few days I have been looking into the status of the LDAP
11474 directory in Debian Edu, and in the process I started to miss a GUI
11475 tool to browse the LDAP tree. The only one I was able to find in
11476 Debian/Squeeze and Lenny is
11477 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
11478 be a great tool to get a overview of the current LDAP directory
11479 populated by default in Skolelinux. Thanks to it, I have been able to
11480 find empty and obsolete subtrees, misplaced objects and duplicate
11481 objects. It will be installed by default in Debian/Squeeze. If you
11482 are working with LDAP, give it a go. :)
</p
>
11484 <p
>I did notice one problem with it I have not had time to report to
11485 the BTS yet. There is no .desktop file in the package, so the tool do
11486 not show up in the Gnome and KDE menus, but only deep down in in the
11487 Debian submenu in KDE. I hope that can be fixed before Squeeze is
11488 released.
</p
>
11490 <p
>I have not yet been able to get it to modify the tree yet. I would
11491 like to move objects and remove subtrees directly in the GUI, but have
11492 not found a way to do that with LUMA yet. So in the mean time, I use
11493 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
11495 <p
>If you have tips on other GUI tools for LDAP that might be useful
11496 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
11498 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
11499 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
11500 useful GUI alternative. It seem like a good tool, but is unmaintained
11501 in Debian and got a RC bug keeping it out of Squeeze. Unless that
11502 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
11507 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
11508 <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>
11509 <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>
11510 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
11511 <description><p
>A while back, I
11512 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
11513 about the fact
</a
> that it is not possible with the provided schemas
11514 for storing DNS and DHCP information in LDAP to combine the two sets
11515 of information into one LDAP object representing a computer.
</p
>
11517 <p
>In the mean time, I discovered that a simple fix would be to make
11518 the dhcpHost object class auxiliary, to allow it to be combined with
11519 the dNSDomain object class, and thus forming one object for one
11520 computer when storing both DHCP and DNS information in LDAP.
</p
>
11522 <p
>If I understand this correctly, it is not safe to do this change
11523 without also changing the assigned number for the object class, and I
11524 do not know enough about LDAP schema design to do that properly for
11525 Debian Edu.
</p
>
11527 <p
>Anyway, for future reference, this is how I believe we could change
11529 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
11530 schema
</a
> to solve at least part of the problem with the LDAP schemas
11531 available today from IETF.
</p
>
11534 --- dhcp.schema (revision
65192)
11535 +++ dhcp.schema (working copy)
11536 @@ -
376,
7 +
376,
7 @@
11537 objectclass (
2.16.840.1.113719.1.203.6.6
11538 NAME
'dhcpHost
'
11539 DESC
'This represents information about a particular client
'
11541 + SUP top AUXILIARY
11543 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
11544 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
11547 <p
>I very much welcome clues on how to do this properly for Debian
11548 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
11549 package, and should thus be free to rewrite it as we see fit.
</p
>
11551 <p
>If you want to help out with implementing this for Debian Edu,
11552 please contact us on debian-edu@lists.debian.org.
</p
>
11557 <title>Calling tasksel like the installer, while still getting useful output
</title>
11558 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
11559 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
11560 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
11561 <description><p
>A few times I have had the need to simulate the way tasksel
11562 installs packages during the normal debian-installer run. Until now,
11563 I have ended up letting tasksel do the work, with the annoying problem
11564 of not getting any feedback at all when something fails (like a
11565 conffile question from dpkg or a download that fails), using code like
11568 <blockquote
><pre
>
11569 export DEBIAN_FRONTEND=noninteractive
11570 tasksel --new-install
11571 </pre
></blockquote
>
11573 This would invoke tasksel, let its automatic task selection pick the
11574 tasks to install, and continue to install the requested tasks without
11575 any output what so ever.
11577 Recently I revisited this problem while working on the automatic
11578 package upgrade testing, because tasksel would some times hang without
11579 any useful feedback, and I want to see what is going on when it
11580 happen. Then it occured to me, I can parse the output from tasksel
11581 when asked to run in test mode, and use that aptitude command line
11582 printed by tasksel then to simulate the tasksel run. I ended up using
11585 <blockquote
><pre
>
11586 export DEBIAN_FRONTEND=noninteractive
11587 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
11589 </pre
></blockquote
>
11591 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
11592 --without-recommends -o APT::Install-Recommends=no -y install
11593 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
11594 ~pimportant
</tt
>", which will install the gnome desktop task, the
11595 laptop task and all packages with priority standard , required and
11596 important, just like tasksel would have done it during
11597 installation.
</p
>
11599 <p
>A better approach is probably to extend tasksel to be able to
11600 install packages without using debconf-apt-progress, for use cases
11601 like this.
</p
>
11606 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
11607 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
11608 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
11609 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
11610 <description><p
>My
11611 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
11612 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
11613 finally made the upgrade logs available from
11614 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
11615 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
11616 apt and aptitude, and found their differences interesting. This time
11617 I will only focus on their removal plans.
</p
>
11619 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
11620 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
11621 surprising part is that it want to remove xorg and all
11622 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
11623 sure why. When asking aptitude to do the same, it want to remove
129
11624 packages, but most of them are library packages I suspect are no
11625 longer needed. Both of them want to remove bluetooth packages, which
11626 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
11628 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
11629 which seem like a bad idea and xorg the same way as with Gnome. Asking
11630 aptitude for the same, it wants to remove
192 packages, none which are
11631 too surprising.
</p
>
11633 <p
>I guess the removal of xorg during upgrades should be investigated
11634 and avoided, and perhaps others as well. Here are the complete list
11635 of planned removals. The complete logs is available from the URL
11636 above. Note if you want to repeat these tests, that the upgrade test
11637 for kde+apt-get hung in the tasksel setup because of dpkg asking
11638 conffile questions. No idea why. I worked around it by using
11639 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
11640 continue.
</p
>
11642 <p
><b
>apt-get gnome
72</b
>
11643 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
11644 gnome-desktop-environment gnome-network-admin gtkhtml3.14
11645 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
11646 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
11647 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
11648 serpentine swfdec-mozilla update-manager xorg xserver-xorg
11649 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11650 xserver-xorg-input-kbd xserver-xorg-input-mouse
11651 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11652 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11653 xserver-xorg-video-ati xserver-xorg-video-chips
11654 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11655 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11656 xserver-xorg-video-glint xserver-xorg-video-i128
11657 xserver-xorg-video-i740 xserver-xorg-video-imstt
11658 xserver-xorg-video-intel xserver-xorg-video-mach64
11659 xserver-xorg-video-mga xserver-xorg-video-neomagic
11660 xserver-xorg-video-nsc xserver-xorg-video-nv
11661 xserver-xorg-video-openchrome xserver-xorg-video-r128
11662 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11663 xserver-xorg-video-rendition xserver-xorg-video-s3
11664 xserver-xorg-video-s3virge xserver-xorg-video-savage
11665 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11666 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11667 xserver-xorg-video-tga xserver-xorg-video-trident
11668 xserver-xorg-video-tseng xserver-xorg-video-v4l
11669 xserver-xorg-video-vesa xserver-xorg-video-vga
11670 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
11671 xulrunner-
1.9-gnome-support
</p
>
11673 <p
><b
>aptitude gnome
129</b
>
11675 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
11676 djvulibre-desktop finger gnome-app-install gnome-mount
11677 gnome-network-admin gnome-spell gnome-vfs-obexftp
11678 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
11679 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
11680 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
11681 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
11682 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
11683 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
11684 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
11685 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
11686 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
11687 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
11688 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
11689 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
11690 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
11691 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
11692 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
11693 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
11694 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
11695 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
11696 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
11697 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
11698 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
11699 openoffice.org-writer2latex openssl-blacklist p7zip
11700 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
11701 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
11702 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
11703 swfdec-mozilla totem-gstreamer update-manager wodim
11704 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11705 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11708 <p
><b
>apt-get kde
82</b
>
11710 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
11711 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
11712 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
11713 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
11714 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
11715 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
11716 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11717 xserver-xorg-input-kbd xserver-xorg-input-mouse
11718 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11719 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11720 xserver-xorg-video-ati xserver-xorg-video-chips
11721 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11722 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11723 xserver-xorg-video-glint xserver-xorg-video-i128
11724 xserver-xorg-video-i740 xserver-xorg-video-imstt
11725 xserver-xorg-video-intel xserver-xorg-video-mach64
11726 xserver-xorg-video-mga xserver-xorg-video-neomagic
11727 xserver-xorg-video-nsc xserver-xorg-video-nv
11728 xserver-xorg-video-openchrome xserver-xorg-video-r128
11729 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11730 xserver-xorg-video-rendition xserver-xorg-video-s3
11731 xserver-xorg-video-s3virge xserver-xorg-video-savage
11732 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11733 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11734 xserver-xorg-video-tga xserver-xorg-video-trident
11735 xserver-xorg-video-tseng xserver-xorg-video-v4l
11736 xserver-xorg-video-vesa xserver-xorg-video-vga
11737 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
11739 <p
><b
>aptitude kde
192</b
>
11740 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
11741 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
11742 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
11743 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
11744 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11745 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
11746 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
11747 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11748 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
11749 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
11750 kghostview khelpcenter khexedit kiconedit kitchensync klatin
11751 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
11752 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
11753 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
11754 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
11755 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
11756 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
11757 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11758 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
11759 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
11760 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11761 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
11762 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
11763 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
11764 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11765 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
11766 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
11767 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
11768 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
11769 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
11770 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
11771 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
11772 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
11773 texlive-common texlive-doc-base texlive-fonts-recommended
11774 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11775 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11776 xulrunner-
1.9</p
>
11782 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
11783 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
11784 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
11785 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
11786 <description><p
>The last few days I have done some upgrade testing in Debian, to
11787 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
11788 have been discovered and reported in the process
11789 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
11790 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
11791 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
11792 kdebase-workspace-data), and to get a more regular testing going on, I
11793 am working on a script to automate the test.
</p
>
11795 <p
>The idea is to create a Lenny chroot and use tasksel to install a
11796 Gnome or KDE desktop installation inside the chroot before upgrading
11797 it. To ensure no services are started in the chroot, a policy-rc.d
11798 script is inserted. To make sure tasksel believe it is to install a
11799 desktop on a laptop, the tasksel tests are replaced in the chroot
11800 (only acceptable because this is a throw-away chroot).
</p
>
11802 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
11803 currently always fail because udev refuses to upgrade with the kernel
11804 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
11805 is created. The bug report
11806 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
11807 this problem do not trigger in a chroot, but I touch the file anyway
11808 to make sure the upgrade go well. Testing on virtual and real
11809 hardware have failed me because of udev so far, and creating this file
11810 do the trick in such settings anyway. This is a
11811 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
11812 issue
</a
> and the current udev behaviour is intended by the udev
11813 maintainer because he lack the resources to rewrite udev to keep
11814 working with old kernels or something like that. I really wish the
11815 udev upstream would keep udev backwards compatible, to avoid such
11816 upgrade problem, but given that they fail to do so, I guess
11817 documenting the way out of this mess is the best option we got for
11818 Debian Squeeze.
</p
>
11820 <p
>Anyway, back to the task at hand, testing upgrades. This test
11821 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
11824 <blockquote
><pre
>
11828 if [
"$
1" ] ; then
11837 exec
&lt; /dev/null
11839 mirror=http://ftp.skolelinux.org/debian
11840 tmpdir=chroot-$from-upgrade-$to-$desktop
11842 debootstrap $from $tmpdir $mirror
11843 chroot $tmpdir aptitude update
11844 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
11848 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
11850 umount $tmpdir/proc
11852 mount -t proc proc $tmpdir/proc
11853 # Make sure proc is unmounted also on failure
11854 trap exit_cleanup EXIT INT
11856 chroot $tmpdir aptitude -y install debconf-utils
11858 # Make sure tasksel autoselection trigger. It need the test scripts
11859 # to return the correct answers.
11860 echo tasksel tasksel/desktop multiselect $desktop | \
11861 chroot $tmpdir debconf-set-selections
11863 # Include the desktop and laptop task
11864 for test in desktop laptop ; do
11865 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
11869 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
11872 DEBIAN_FRONTEND=noninteractive
11873 DEBIAN_PRIORITY=critical
11874 export DEBIAN_FRONTEND DEBIAN_PRIORITY
11875 chroot $tmpdir tasksel --new-install
11877 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
11878 chroot $tmpdir aptitude update
11879 touch $tmpdir/etc/udev/kernel-upgrade
11880 chroot $tmpdir aptitude -y dist-upgrade
11882 </pre
></blockquote
>
11884 <p
>I suspect it would be useful to test upgrades with both apt-get and
11885 with aptitude, but I have not had time to look at how they behave
11886 differently so far. I hope to get a cron job running to do the test
11887 regularly and post the result on the web. The Gnome upgrade currently
11888 work, while the KDE upgrade fail because of the bug in
11889 kdebase-workspace-data
</p
>
11891 <p
>I am not quite sure what kind of extract from the huge upgrade logs
11892 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
11893 post, so I will refrain from trying. I can report that for Gnome,
11894 aptitude report
760 packages upgraded,
448 newly installed,
129 to
11895 remove and
1 not upgraded and
1024MB need to be downloaded while for
11896 KDE the same numbers are
702 packages upgraded,
507 newly installed,
11897 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
11899 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
11900 is able to migrate to dependency based boot sequencing and parallel
11901 booting without a hitch. Was unsure if there were still bugs with
11902 packages failing to clean up their obsolete init.d script during
11903 upgrades, and no such problem seem to affect the Gnome desktop+laptop
11904 packages.
</p
>
11909 <title>Upstart or sysvinit - as init.d scripts see it
</title>
11910 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
11911 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
11912 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
11913 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
11914 scripts to migrate (some of) their operations to upstart job while
11915 keeping the init.d for hurd and kfreebsd. The packages with such
11916 needs will need a way to get their init.d scripts to behave
11917 differently when used with sysvinit and with upstart. Because of
11918 this, I had a look at the environment variables set when a init.d
11919 script is running under upstart, and when it is not.
</p
>
11921 <p
>With upstart, I notice these environment variables are set when a
11922 script is started from rcS.d/ (ignoring some irrelevant ones like
11923 COLUMNS):
</p
>
11925 <blockquote
><pre
>
11931 UPSTART_EVENTS=startup
11933 UPSTART_JOB=rc-sysinit
11934 </pre
></blockquote
>
11936 <p
>With sysvinit, these environment variables are set for the same
11939 <blockquote
><pre
>
11940 INIT_VERSION=sysvinit-
2.88
11945 </pre
></blockquote
>
11947 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
11948 sysvinit are not set by upstart. Not sure if it is intentional or not
11949 to not be compatible with sysvinit in this regard.
</p
>
11951 <p
>For scripts needing to behave differently when upstart is used,
11952 looking for the UPSTART_JOB environment variable seem to be a good
11958 <title>A manual for standards wars...
</title>
11959 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
11960 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
11961 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
11962 <description><p
>Via the
11963 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
11964 of Rob Weir
</a
> I came across the very interesting essay named
11965 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
11966 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
11967 following the standards wars of today.
</p
>
11972 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
11973 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
11974 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
11975 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
11976 <description><p
>When using sitesummary at a site to track machines, it is possible
11977 to get a list of the machine types in use thanks to the DMI
11978 information extracted from each machine. The script to do so is
11979 included in the sitesummary package, and here is example output from
11980 the Skolelinux build servers:
</p
>
11982 <blockquote
><pre
>
11983 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
11985 Dell Computer Corporation
1
11988 eserver xSeries
345 -[
8670M1X]-
1
11992 </pre
></blockquote
>
11994 <p
>The quality of the report depend on the quality of the DMI tables
11995 provided in each machine. Here there are Intel machines without model
11996 information listed with Intel as vendor and no model, and virtual Xen
11997 machines listed as [no-dmi-info]. One can add -l as a command line
11998 option to list the individual machines.
</p
>
12000 <p
>A larger list is
12001 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
12002 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
12003 provide the basic sitesummary report publicly. In their report there
12004 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
12005 their machines, and as sitesummary is available in both distributions,
12006 it is trivial to get all of them to report to the same central
12007 collector.
</p
>
12012 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
12013 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
12014 <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>
12015 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
12016 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
12017 start at boot when an NVidia video card is used is handled. The
12018 problem seem to be that the nvidia X.org driver uses a long time to
12019 initialize, and this duration is longer than kdm is configured to
12022 <p
>I came across two bugs related to this issue,
12023 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
12024 against initscripts and passed on to nvidia-glx when it became obvious
12025 that the nvidia drivers were involved, and
12026 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
12027 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
12029 <p
>To me, it seem that no-one is interested in actually solving the
12030 problem nvidia video card owners experience and make sure the Debian
12031 distribution work out of the box for these users. The nvidia driver
12032 maintainers expect kdm to be set up to wait longer, while kdm expect
12033 the nvidia driver maintainers to fix the driver to start faster, and
12034 while they wait for each other I guess the users end up switching to a
12035 distribution that work for them. I have no idea what the solution is,
12036 but I am pretty sure that waiting for each other is not it.
</p
>
12038 <p
>I wonder why we end up handling bugs this way.
</p
>
12043 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
12044 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
12045 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
12046 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
12047 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
12048 The feature seem to hold up pretty well, but three fairly serious
12049 issues are known and should be solved:
12051 <p
><ul
>
12053 <li
>The wicd package seen to
12054 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
12055 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
12056 parallel booting is enabled. No idea why, but the wicd maintainer
12057 seem to be on the case.
</li
>
12059 <li
>The nvidia X driver seem to
12060 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
12061 triggered more easily when parallel booting is in effect. The
12062 maintainer is on the case.
</li
>
12064 <li
>The sysv-rc package fail to properly enable dependency based boot
12065 sequencing (the shutdown is broken) when old file-rc users
12066 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
12067 sysv-rc. One way to solve it would be for file-rc to create
12068 /etc/init.d/.legacy-bootordering, and another is to try to make
12069 sysv-rc more robust. Will investigate some more and probably upload a
12070 workaround in sysv-rc to help those trying to move from file-rc to
12071 sysv-rc get a working shutdown.
</li
>
12073 </ul
></p
>
12075 <p
>All in all not many surprising issues, and all of them seem
12076 solvable before Squeeze is released. In addition to these there are
12077 some packages with bugs in their dependencies and run level settings,
12078 which I expect will be fixed in a reasonable time span.
</p
>
12080 <p
>If you report any problems with dependencies in init.d scripts to
12081 the BTS, please usertag the report to get it to show up at
12082 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12083 list of usertagged bugs related to this
</a
>.
</p
>
12085 <p
>Update: Correct bug number to file-rc issue.
</p
>
12090 <title>More flexible firmware handling in debian-installer
</title>
12091 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
12092 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
12093 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
12094 <description><p
>After a long break from debian-installer development, I finally
12095 found time today to return to the project. Having to spend less time
12096 working dependency based boot in debian, as it is almost complete now,
12097 definitely helped freeing some time.
</p
>
12099 <p
>A while back, I ran into a problem while working on Debian Edu. We
12100 include some firmware packages on the Debian Edu CDs, those needed to
12101 get disk and network controllers working. Without having these
12102 firmware packages available during installation, it is impossible to
12103 install Debian Edu on the given machine, and because our target group
12104 are non-technical people, asking them to provide firmware packages on
12105 an external medium is a support pain. Initially, I expected it to be
12106 enough to include the firmware packages on the CD to get
12107 debian-installer to find and use them. This proved to be wrong.
12108 Next, I hoped it was enough to symlink the relevant firmware packages
12109 to some useful location on the CD (tried /cdrom/ and
12110 /cdrom/firmware/). This also proved to not work, and at this point I
12111 found time to look at the debian-installer code to figure out what was
12112 going to work.
</p
>
12114 <p
>The firmware loading code is in the hw-detect package, and a closer
12115 look revealed that it would only look for firmware packages outside
12116 the installation media, so the CD was never checked for firmware
12117 packages. It would only check USB sticks, floppies and other
12118 "external
" media devices. Today I changed it to also look in the
12119 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12120 solve the problem I ran into with Debian edu. I also changed it to
12121 look in /firmware/, to make sure the installer also find firmware
12122 provided in the initrd when booting the installer via PXE, to allow us
12123 to provide the same feature in the PXE setup included in Debian
12126 <p
>To make sure firmware deb packages with a license questions are not
12127 activated without asking if the license is accepted, I extended
12128 hw-detect to look for preinst scripts in the firmware packages, and
12129 run these before activating the firmware during installation. The
12130 license question is asked using debconf in the preinst, so this should
12131 solve the issue for the firmware packages I have looked at so far.
</p
>
12133 <p
>If you want to discuss the details of these features, please
12134 contact us on debian-boot@lists.debian.org.
</p
>
12139 <title>Parallellized boot is now the default in Debian/unstable
</title>
12140 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
12141 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
12142 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
12143 <description><p
>Since this evening, parallel booting is the default in
12144 Debian/unstable for machines using dependency based boot sequencing.
12145 Apparently the testing of concurrent booting has been wider than
12146 expected, if I am to believe the
12147 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12148 on debian-devel@
</a
>, and I concluded a few days ago to move forward
12149 with the feature this weekend, to give us some time to detect any
12150 remaining problems before Squeeze is frozen. If serious problems are
12151 detected, it is simple to change the default back to sequential boot.
12152 The upload of the new sysvinit package also activate a new upstream
12155 More information about
12156 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12157 based boot sequencing
</a
> is available from the Debian wiki. It is
12158 currently possible to disable parallel booting when one run into
12159 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
12161 <blockquote
><pre
>
12163 </pre
></blockquote
>
12165 <p
>If you report any problems with dependencies in init.d scripts to
12166 the BTS, please usertag the report to get it to show up at
12167 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12168 list of usertagged bugs related to this
</a
>.
</p
>
12173 <title>Sitesummary tip: Listing MAC address of all clients
</title>
12174 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
12175 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
12176 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
12177 <description><p
>In the recent Debian Edu versions, the
12178 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
12179 system
</a
> is used to keep track of the machines in the school
12180 network. Each machine will automatically report its status to the
12181 central server after boot and once per night. The network setup is
12182 also reported, and using this information it is possible to get the
12183 MAC address of all network interfaces in the machines. This is useful
12184 to update the DHCP configuration.
</p
>
12186 <p
>To give some idea how to use sitesummary, here is a one-liner to
12187 ist all MAC addresses of all machines reporting to sitesummary. Run
12188 this on the collector host:
</p
>
12190 <blockquote
><pre
>
12191 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
12192 </pre
></blockquote
>
12194 <p
>This will list all MAC addresses assosiated with all machine, one
12195 line per machine and with space between the MAC addresses.
</p
>
12197 <p
>To allow system administrators easier job at adding static DHCP
12198 addresses for hosts, it would be possible to extend this to fetch
12199 machine information from sitesummary and update the DHCP and DNS
12200 tables in LDAP using this information. Such tool is unfortunately not
12201 written yet.
</p
>
12206 <title>systemd, an interesting alternative to upstart
</title>
12207 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
12208 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
12209 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
12210 <description><p
>The last few days a new boot system called
12211 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
12213 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
12215 to the free software world. I have not yet had time to play around
12216 with it, but it seem to be a very interesting alternative to
12217 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
12218 a good alternative for Debian when we are able to switch to an event
12219 based boot system. Tollef is
12220 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
12221 systemd into Debian, and I look forward to seeing how well it work. I
12222 like the fact that systemd handles init.d scripts with dependency
12223 information natively, allowing them to run in parallel where upstart
12224 at the moment do not.
</p
>
12226 <p
>Unfortunately do systemd have the same problem as upstart regarding
12227 platform support. It only work on recent Linux kernels, and also need
12228 some new kernel features enabled to function properly. This means
12229 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12230 system. Not sure how that will be handled if systemd proves to be the
12231 way forward.
</p
>
12233 <p
>In the mean time, based on the
12234 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12235 on debian-devel@
</a
> regarding parallel booting in Debian, I have
12236 decided to enable full parallel booting as the default in Debian as
12237 soon as possible (probably this weekend or early next week), to see if
12238 there are any remaining serious bugs in the init.d dependencies. A
12239 new version of the sysvinit package implementing this change is
12240 already in experimental. If all go well, Squeeze will be released
12241 with parallel booting enabled by default.
</p
>
12246 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
12247 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
12248 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
12249 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
12250 <description><p
>These days, the init.d script dependencies in Squeeze are quite
12251 complete, so complete that it is actually possible to run all the
12252 init.d scripts in parallell based on these dependencies. If you want
12253 to test your Squeeze system, make sure
12254 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12255 based boot sequencing
</a
> is enabled, and add this line to
12256 /etc/default/rcS:
</p
>
12258 <blockquote
><pre
>
12259 CONCURRENCY=makefile
12260 </pre
></blockquote
>
12262 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
12263 scripts in parallel using the dependency information stored in
12264 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
12265 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
12266 to try to start the kdm and gdm scripts as early as possible, and will
12267 start the facilities required by kdm or gdm as early as possible to
12268 make this happen.
</p
>
12270 <p
>Give it a try, and see if you like the result. If some services
12271 fail to start properly, it is most likely because they have incomplete
12272 init.d script dependencies in their startup script (or some of their
12273 dependent scripts have incomplete dependencies). Report bugs and get
12274 the package maintainers to fix it. :)
</p
>
12276 <p
>Running scripts in parallel could be the default in Debian when we
12277 manage to get the init.d script dependencies complete and correct. I
12278 expect we will get there in Squeeze+
1, if we get manage to test and
12279 fix the remaining issues.
</p
>
12281 <p
>If you report any problems with dependencies in init.d scripts to
12282 the BTS, please usertag the report to get it to show up at
12283 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12284 list of usertagged bugs related to this
</a
>.
</p
>
12289 <title>Debian has switched to dependency based boot sequencing
</title>
12290 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
12291 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
12292 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
12293 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
12294 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
12295 have been migrated to using dependency based boot sequencing. This
12296 conclude work me and others have been doing for the last three days.
12297 It feels great to see this finally part of the default Debian
12298 installation. Now we just need to weed out the last few problems that
12299 are bound to show up, to get everything ready for Squeeze.
</p
>
12301 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
12302 fixing the more fundamental problem of handing the event based
12303 non-predictable kernel in the early boot.
</p
>
12308 <title>Taking over sysvinit development
</title>
12309 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
12310 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
12311 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
12312 <description><p
>After several years of frustration with the lack of activity from
12313 the existing sysvinit upstream developer, I decided a few weeks ago to
12314 take over the package and become the new upstream. The number of
12315 patches to track for the Debian package was becoming a burden, and the
12316 lack of synchronization between the distribution made it hard to keep
12317 the package up to date.
</p
>
12319 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
12320 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
12321 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
12322 and Fedora), based on the patches currently in use in these
12323 distributions. We Debian maintainers plan to move to this tarball as
12324 the new upstream as soon as we find time to do the merge. Since the
12325 new tarball was created, we agreed with Werner at SuSe to make a new
12326 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
12327 development there. The project is registered and currently waiting
12328 for approval by the Savannah administrators, and as soon as it is
12329 approved, we will import the old versions from svn and continue
12330 working on the future release.
</p
>
12332 <p
>It is a bit ironic that this is done now, when some of the involved
12333 distributions are moving to upstart as a syvinit replacement.
</p
>
12338 <title>Debian boots quicker and quicker
</title>
12339 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
12340 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
12341 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
12342 <description><p
>I spent Monday and tuesday this week in London with a lot of the
12343 people involved in the boot system on Debian and Ubuntu, to see if we
12344 could find more ways to speed up the boot system. This was an Ubuntu
12346 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
12347 gathering
</a
>. It was quite productive. We also discussed the future
12348 of boot systems, and ways to handle the increasing number of boot
12349 issues introduced by the Linux kernel becoming more and more
12350 asynchronous and event base. The Ubuntu approach using udev and
12351 upstart might be a good way forward. Time will show.
</p
>
12353 <p
>Anyway, there are a few ways at the moment to speed up the boot
12354 process in Debian. All of these should be applied to get a quick
12359 <li
>Use dash as /bin/sh.
</li
>
12361 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
12362 clock is in UTC.
</li
>
12364 <li
>Install and activate the insserv package to enable
12365 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12366 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
12370 These points are based on the Google summer of code work done by
12371 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
12372 Villegas
</a
>.
12374 <p
>Support for makefile-style concurrency during boot was uploaded to
12375 unstable yesterday. When we tested it, we were able to cut
6 seconds
12376 from the boot sequence. It depend on very correct dependency
12377 declaration in all init.d scripts, so I expect us to find edge cases
12378 where the dependences in some scripts are slightly wrong when we start
12379 using this.
</p
>
12381 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
12382 introduced by Raphael Geissert today, one that could affect the
12383 startup speed as well. Instead of starting some scripts concurrently
12384 from rcS.d/ and another set of scripts from rc2.d/, it would be
12385 possible to run a of them in the same process. A quick way to test
12386 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
12387 insserv
'. Will need to test if that work. :)
</p
>
12392 <title>BSAs påstander om piratkopiering møter motstand
</title>
12393 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
12394 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
12395 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
12396 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
12397 programvareselskapene som Microsoft og Apple, publisert en rapport der
12398 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
12399 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
12401 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
12402 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
12403 dagene. Et spesielt interessant kommentar fra Sverige,
12404 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
12405 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
12408 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
12409 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
12410 företag.
"Man bör nog kanske inte se de här siffrorna som helt
12411 exakta
", säger BSAs Sverigechef John Hugosson.
12412 </blockquote
>
12414 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
12415 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
12416 piracy figures need a shot of reality
</a
> og
<a
12417 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
12418 Copyright Treaty Work?
</a
></p
>
12420 <p
>Fant lenkene via
<a
12421 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
12422 på Slashdot
</a
>.
</p
>
12427 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
12428 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
12429 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
12430 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
12431 <description><p
>Kom over
12432 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
12433 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
12434 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
12435 jobber til daglig. En rask opptelling forteller meg at vi har
490
12436 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
12437 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
12438 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
12443 <title>Kryptert harddisk - naturligvis
</title>
12444 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
12445 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
12446 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
12447 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
12448 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
12449 når en tar tap av arbeidstid, fortrolige dokumenter,
12450 personopplysninger og alt annet det innebærer. Det er ingen tvil om
12451 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
12452 til at jeg har kryptert harddisken på både kontormaskinen og min
12453 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
12454 komme på avveie, den første informasjon relatert til jobben min ved
12455 Universitetet i Oslo, og den andre relatert til blant annet
12456 foreningsarbeide. Kryptering av diskene gjør at det er lite
12457 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
12458 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
12459 og en reboot vil gjøre at de ber om passord før de vil starte opp.
12460 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
12461 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
12462 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
12463 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
12464 det er gjort slik jeg gjør det er minimale, og gevinstene er
12465 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
12466 maskinen reinstalleres og alt er tapt.
</p
>
12468 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
12469 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
12470 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
12471 er for min del høyere enn gevinsten. Jeg tror oddsene for at
12472 f.eks. etteretningsorganisasjoner har glede av å titte på mine
12473 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
12474 gjøre det vanskeligere for angripere med kompetanse og ressurser er
12475 betydelige.
</p
>
12480 <title>Two projects that have improved the quality of free software a lot
</title>
12481 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
12482 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
12483 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
12484 <description><p
>There are two software projects that have had huge influence on the
12485 quality of free software, and I wanted to mention both in case someone
12486 do not yet know them.
</p
>
12488 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
12489 tool to detect and expose errors in the memory handling of programs.
12490 It is easy to use, all one need to do is to run
'valgrind program
',
12491 and it will report any problems on stdout. It is even better if the
12492 program include debug information. With debug information, it is able
12493 to report the source file name and line number where the problem
12494 occurs. It can report things like
'reading past memory block in file
12495 X line N, the memory block was allocated in file Y, line M
', and
12496 'using uninitialised value in control logic
'. This tool has made it
12497 trivial to investigate reproducible crash bugs in programs, and have
12498 reduced the number of this kind of bugs in free software a lot.
12500 <p
>The second one is
12501 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
12502 a source code checker. It is able to process the source of a program
12503 and find problems in the logic without running the program. It
12504 started out as the Stanford Checker and became well known when it was
12505 used to find bugs in the Linux kernel. It is now a commercial tool
12506 and the company behind it is running
12507 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
12508 free software community, where a lot of free software projects get
12509 their source checked for free. Several thousand defects have been
12510 found and fixed so far. It can find errors like
'lock L taken in file
12511 X line N is never released if exiting in line M
', or
'the code in file
12512 Y lines O to P can never be executed
'. The projects included in the
12513 community service project have managed to get rid of a lot of
12514 reliability problems thanks to Coverity.
</p
>
12516 <p
>I believe tools like this, that are able to automatically find
12517 errors in the source, are vital to improve the quality of software and
12518 make sure we can get rid of the crashing and failing software we are
12519 surrounded by today.
</p
>
12524 <title>No patch is not better than a useless patch
</title>
12525 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
12526 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
12527 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
12528 <description><p
>Julien Blache
12529 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
12530 patch is better than a useless patch
</a
>. I completely disagree, as a
12531 patch allow one to discuss a concrete and proposed solution, and also
12532 prove that the issue at hand is important enough for someone to spent
12533 time on fixing it. No patch do not provide any of these positive
12534 properties.
</p
>
12539 <title>Standardize on protocols and formats, not vendors and applications
</title>
12540 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
12541 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
12542 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
12543 <description><p
>Where I work at the University of Oslo, one decision stand out as a
12544 very good one to form a long lived computer infrastructure. It is the
12545 simple one, lost by many in todays computer industry: Standardize on
12546 open network protocols and open exchange/storage formats, not applications.
12547 Applications come and go, while protocols and files tend to stay, and
12548 thus one want to make it easy to change application and vendor, while
12549 avoiding conversion costs and locking users to a specific platform or
12550 application.
</p
>
12552 <p
>This approach make it possible to replace the client applications
12553 independently of the server applications. One can even allow users to
12554 use several different applications as long as they handle the selected
12555 protocol and format. In the normal case, only one client application
12556 is recommended and users only get help if they choose to use this
12557 application, but those that want to deviate from the easy path are not
12558 blocked from doing so.
</p
>
12560 <p
>It also allow us to replace the server side without forcing the
12561 users to replace their applications, and thus allow us to select the
12562 best server implementation at any moment, when scale and resouce
12563 requirements change.
</p
>
12565 <p
>I strongly recommend standardizing - on open network protocols and
12566 open formats, but I would never recommend standardizing on a single
12567 application that do not use open network protocol or open formats.
</p
>
12572 <title>Returning from Skolelinux developer gathering
</title>
12573 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
12574 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
12575 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
12576 <description><p
>I
'm sitting on the train going home from this weekends Debian
12577 Edu/Skolelinux development gathering. I got a bit done tuning the
12578 desktop, and looked into the dynamic service location protocol
12579 implementation avahi. It look like it could be useful for us. Almost
12580 30 people participated, and I believe it was a great environment to
12581 get to know the Skolelinux system. Walter Bender, involved in the
12582 development of the Sugar educational platform, presented his stuff and
12583 also helped me improve my OLPC installation. He also showed me that
12584 his Turtle Art application can be used in standalone mode, and we
12585 agreed that I would help getting it packaged for Debian. As a
12586 standalone application it would be great for Debian Edu. We also
12587 tried to get the video conferencing working with two OLPCs, but that
12588 proved to be too hard for us. The application seem to need more work
12589 before it is ready for me. I look forward to getting home and relax
12595 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
12596 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
12597 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
12598 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
12599 <description><p
>The state of standardized LDAP schemas on Linux is far from
12600 optimal. There is RFC
2307 documenting one way to store NIS maps in
12601 LDAP, and a modified version of this normally called RFC
2307bis, with
12602 some modifications to be compatible with Active Directory. The RFC
12603 specification handle the content of a lot of system databases, but do
12604 not handle DNS zones and DHCP configuration.
</p
>
12606 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
12607 we would like to store information about users, SMB clients/hosts,
12608 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
12609 and LTSP configuration in LDAP. These objects have a lot in common,
12610 but with the current LDAP schemas it is not possible to have one
12611 object per entity. For example, one need to have at least three LDAP
12612 objects for a given computer, one with the SMB related stuff, one with
12613 DNS information and another with DHCP information. The schemas
12614 provided for DNS and DHCP are impossible to combine into one LDAP
12615 object. In addition, it is impossible to implement quick queries for
12616 netgroup membership, because of the way NIS triples are implemented.
12617 It just do not scale. I believe it is time for a few RFC
12618 specifications to cleam up this mess.
</p
>
12620 <p
>I would like to have one LDAP object representing each computer in
12621 the network, and this object can then keep the SMB (ie host key), DHCP
12622 (mac address/name) and DNS (name/IP address) settings in one place.
12623 It need to be efficently stored to make sure it scale well.
</p
>
12625 <p
>I would also like to have a quick way to map from a user or
12626 computer and to the net group this user or computer is a member.
</p
>
12628 <p
>Active Directory have done a better job than unix heads like myself
12629 in this regard, and the unix side need to catch up. Time to start a
12630 new IETF work group?
</p
>
12635 <title>Endelig er Debian Lenny gitt ut
</title>
12636 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
12637 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
12638 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
12639 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
12640 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
12641 Et langt steg videre for Debian-prosjektet, og en rekke nye
12642 programpakker blir nå tilgjengelig for de av oss som bruker den
12643 stabile utgaven av Debian. Neste steg er nå å få
12644 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
12645 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
12646 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
12647 slippes løs på skolene. Takk til alle debian-utviklerne som har
12648 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
12649 bootsekvens tilgjengelig i stabil utgave, vha pakken
12650 <tt
>insserv
</tt
>.
</p
>
12655 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
12656 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
12657 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
12658 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
12659 <description><p
>This weekend we had a small developer gathering for Debian Edu in
12660 Oslo. Most of Saturday was used for the general assemly for the
12661 member organization, but the rest of the weekend I used to tune the
12662 LTSP installation. LTSP now work out of the box on the
10-network.
12663 Acer Aspire One proved to be a very nice thin client, with both
12664 screen, mouse and keybard in a small box. Was working on getting the
12665 diskless workstation setup configured out of the box, but did not
12666 finish it before the weekend was up.
</p
>
12668 <p
>Did not find time to look at the
4 VGA cards in one box we got from
12669 the Brazilian group, so that will have to wait for the next
12670 development gathering. Would love to have the Debian Edu installer
12671 automatically detect and configure a multiseat setup when it find one
12672 of these cards.
</p
>
12677 <title>The sorry state of multimedia browser plugins in Debian
</title>
12678 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
12679 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
12680 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
12681 <description><p
>Recently I have spent some time evaluating the multimedia browser
12682 plugins available in Debian Lenny, to see which one we should use by
12683 default in Debian Edu. We need an embedded video playing plugin with
12684 control buttons to pause or stop the video, and capable of streaming
12685 all the multimedia content available on the web. The test results and
12686 notes are available on
12687 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
12688 Debian wiki
</a
>. I was surprised how few of the plugins are able to
12689 fill this need. My personal video player favorite, VLC, has a really
12690 bad plugin which fail on a lot of the test pages. A lot of the MIME
12691 types I would expect to work with any free software player (like
12692 video/ogg), just do not work. And simple formats like the
12693 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
12694 totem and vlc plugins. I hope the situation will improve soon. No
12695 wonder sites use the proprietary Adobe flash to play video.
</p
>
12697 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
12698 be the only one fitting our needs. :/
</p
>