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>Is the desktop recommending your program for opening its files?
</title>
11 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</link>
12 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</guid>
13 <pubDate>Sun,
29 Jan
2023 11:
00:
00 +
0100</pubDate>
14 <description><p
>Linux desktop systems
15 <a href=
"https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
">have
16 standardized
</a
> how programs present themselves to the desktop
17 system. If a package include a .desktop file in
18 /usr/share/application, Gnome, KDE, LXDE, Xfce and the other desktop
19 environments will pick up the file and use its content to generate the
20 menu of available programs in the system. A lesser known fact is that
21 a package can also explain to the desktop system how to recognize the
22 files created by the program in question, and use it to open these
23 files on request, for example via a GUI file browser.
</p
>
25 <p
>A while back I ran into a package that did not tell the desktop
26 system how to recognize its files and was not used to open its files
27 in the file browser and fixed it. In the process I wrote a simple
28 debian/tests/ script to ensure the setup keep working. It might be
29 useful for other packages too, to ensure any future version of the
30 package keep handling its own files.
</p
>
32 <p
>For this to work the file format need a useful MIME type that can
33 be used to identify the format. If the file format do not yet have a
34 MIME type, it should define one and preferably also
35 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">register
36 it with IANA
</a
> to ensure the MIME type string is reserved.
</p
>
38 <p
>The script uses the
<tt
>xdg-mime
</tt
> program from xdg-utils to
39 query the database of standardized package information and ensure it
40 return sensible values. It also need the location of an example file
41 for xdg-mime to guess the format of.
</p
>
46 # Author: Petter Reinholdtsen
47 # License: GPL v2 or later at your choice.
49 # Validate the MIME setup, making sure motor types have
50 # application/vnd.openmotor+yaml associated with them and is connected
51 # to the openmotor desktop file.
55 mimetype=
"application/vnd.openmotor+yaml
"
56 testfile=
"test/data/real/o3100/motor.ric
"
57 mydesktopfile=
"openmotor.desktop
"
59 filemime=
"$(xdg-mime query filetype
"$testfile
")
"
61 if [
"$mimetype
" !=
"$filemime
" ] ; then
63 echo
"error: xdg-mime claim motor file MIME type is $filemine, not $mimetype
"
65 echo
"success: xdg-mime report correct mime type $mimetype for motor file
"
68 desktop=$(xdg-mime query default
"$mimetype
")
70 if [
"$mydesktopfile
" !=
"$desktop
" ]; then
72 echo
"error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile
"
74 echo
"success: xdg-mime agree motor file should be handled by $mydesktopfile
"
80 <p
>It is a simple way to ensure your users are not very surprised when
81 they try to open one of your file formats in their file browser.
</p
>
83 <p
>As usual, if you use Bitcoin and want to show your support of my
84 activities, please send Bitcoin donations to my address
85 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
90 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive
</title>
91 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</link>
92 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</guid>
93 <pubDate>Sun,
22 Jan
2023 23:
55:
00 +
0100</pubDate>
94 <description><p
>While reading a
95 <a href=
"https://sneak.berlin/
20230115/macos-scans-your-local-files-now/
">blog
96 post claiming MacOS X recently started scanning local files and
97 reporting information about them to Apple
</a
>, even on a machine where
98 all such callback features had been disabled, I came across a
99 description of the Little Snitch application for MacOS X. It seemed
100 like a very nice tool to have in the tool box, and I decided to see if
101 something similar was available for Linux.
</p
>
103 <p
>It did not take long to find
104 <a href=
"https://github.com/evilsocket/opensnitch
">the OpenSnitch
105 package
</a
>, which has been in development since
2017, and now is in
106 version
1.5.0. It has had a
107 <a href=
"https://bugs.debian.org/
909567">request for Debian
108 packaging
</a
> since
2018, but no-one completed the job so far. Just
109 for fun, I decided to see if I could help, and I was very happy to
111 <a href=
"https://github.com/evilsocket/opensnitch/issues/
304">upstream
112 want a Debian package too
</a
>.
</p
>
114 <p
>After struggling a bit with getting the program to run, figuring
115 out building Go programs (and a little failed detour to look at eBPF
116 builds too - help needed), I am very happy to report that I am
117 sponsoring upstream to maintain the package in Debian, and it has
118 since this morning been waiting in NEW for the ftpmasters to have a
119 look. Perhaps it can get into the archive in time for the Bookworm
122 <p
>As usual, if you use Bitcoin and want to show your support of my
123 activities, please send Bitcoin donations to my address
124 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
129 <title>LinuxCNC MQTT publisher component
</title>
130 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</link>
131 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</guid>
132 <pubDate>Sun,
8 Jan
2023 19:
30:
00 +
0100</pubDate>
133 <description><p
>I watched
<a href=
"https://yewtu.be/watch?v=jmKUV3aNLjk
">a
2015
134 video from Andreas Schiffler
</a
> the other day, where he set up
135 <a href=
"https://linuxcnc.org/
">LinuxCNC
</a
> to send status
136 information to the MQTT broker IBM Bluemix. As I also use MQTT for
137 graphing, it occured to me that a generic MQTT LinuxCNC component
138 would be useful and I set out to implement it. Today I got the first
139 draft limping along and submitted as
140 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
2253">a patch to the
141 LinuxCNC project
</a
>.
</p
>
143 <p
>The simple part was setting up the MQTT publishing code in Python.
144 I already have set up other parts submitting data to my Mosquito MQTT
145 broker, so I could reuse that code. Writing a LinuxCNC component in
146 Python as new to me, but using existing examples in the code
147 repository and the extensive documentation, this was fairly straight
148 forward. The hardest part was creating a automated test for the
149 component to ensure it was working. Testing it in a simulated
150 LinuxCNC machine proved very useful, as I discovered features I needed
151 that I had not thought of yet, and adjusted the code quite a bit to
152 make it easier to test without a operational MQTT broker
155 <p
>The draft is ready and working, but I am unsure which LinuxCNC HAL
156 pins I should collect and publish by default (in other words, the
157 default set of information pieces published), and how to get the
158 machine name from the LinuxCNC INI file. The latter is a minor
159 detail, but I expect it would be useful in a setup with several
160 machines available. I am hoping for feedback from the experienced
161 LinuxCNC developers and users, to make the component even better
162 before it can go into the mainland LinuxCNC code base.
</p
>
164 <p
>Since I started on the MQTT component, I came across
165 <a href=
"https://yewtu.be/watch?v=Bqa2grG0XtA
">another video from Kent
166 VanderVelden
</a
> where he combine LinuxCNC with a set of screen glasses
167 controlled by a Raspberry Pi, and it occured to me that it would
168 be useful for such use cases if LinuxCNC also provided a REST API for
169 querying its status. I hope to start on such component once the MQTT
170 component is working well.
</p
>
172 <p
>As usual, if you use Bitcoin and want to show your support of my
173 activities, please send Bitcoin donations to my address
174 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
179 <title>ONVIF IP camera management tool finally in Debian
</title>
180 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</link>
181 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</guid>
182 <pubDate>Sat,
24 Dec
2022 08:
00:
00 +
0100</pubDate>
183 <description><p
>Merry Christmas to you all. Here is a small gift to all those with
184 IP cameras following the
<a href=
"https://www.onvif.org/
">ONVIF
185 specification
</a
>. There is finally a nice command line and GUI tool
186 in Debian to manage ONVIF IP cameras. After working with upstream for
187 a few months and sponsoring the upload, I am very happy to report that
188 the
<a href=
"https://tracker.debian.org/libonvif
">libonvif package
</a
>
189 entered Debian Sid last night.
</p
>
191 <p
>The package provide a C library to communicate with such cameras, a
192 command line tool to locate and update settings of (like password) the
193 cameras and a GUI tool to configure and control the units as well as
194 preview the video from the camera. Libonvif is available on Both
195 Linux and Windows and the GUI tool uses the Qt library. The main
196 competitors are non-free software, while libonvif is GNU GPL licensed.
197 I am very glad Debian users in the future can control their cameras
198 using a free software system provided by Debian. But the ONVIF world
199 is full of slightly broken firmware, where the cameras pretend to
200 follow the ONVIF specification but fail to set some configuration
201 values or refuse to provide video to more than one recipient at the
202 time, and the onvif project is quite young and might take a while
203 before it completely work with your camera. Upstream seem eager to
204 improve the library, so handling any broken camera might be just
<a
205 href=
"https://github.com/sr99622/libonvif/
">a bug report away
</a
>.
</p
>
207 <p
>The package just cleared NEW, and need a new source only upload
208 before it can enter testing. This will happen in the next few
211 <p
>As usual, if you use Bitcoin and want to show your support of my
212 activities, please send Bitcoin donations to my address
213 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
218 <title>Managing and using ONVIF IP cameras with Linux
</title>
219 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</link>
220 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</guid>
221 <pubDate>Wed,
19 Oct
2022 12:
30:
00 +
0200</pubDate>
222 <description><p
>Recently I have been looking at how to control and collect data
223 from a handful IP cameras using Linux. I both wanted to change their
224 settings and to make their imagery available via a free software
225 service under my control. Here is a summary of the tools I found.
</p
>
227 <p
>First I had to identify the cameras and their protocols. As far as
228 I could tell, they were using some SOAP looking protocol and their
229 internal web server seem to only work with Microsoft Internet Explorer
230 with some proprietary binary plugin, which in these days of course is
231 a security disaster and also made it impossible for me to use the
232 camera web interface. Luckily I discovered that the SOAP looking
233 protocol is actually following
<a href=
"https://www.onvif.org/
">the
234 ONVIF specification
</a
>, which seem to be supported by a lot of IP
235 cameras these days.
</p
>
237 <p
>Once the protocol was identified, I was able to find what appear to
238 be the most popular way to configure ONVIF cameras, the free software
240 <a href=
"https://sourceforge.net/projects/onvifdm/
">ONVIF Device
241 Manager
</a
>. Lacking any other options at the time, I tried
242 unsuccessfully to get it running using Wine, but was missing a dotnet
243 40 library and I found no way around it to run it on Linux.
</p
>
245 <p
>The next tool I found to configure the cameras were a non-free Linux Qt
246 client
<a href=
"https://www.lingodigit.com/onvif_nvcdemo.html
">ONVIF
247 Device Tool
</a
>. I did not like its terms of use, so did not spend
248 much time on it.
</p
>
250 <p
>To collect the video and make it available in a web interface, I
251 found the Zoneminder tool in Debian. A recent version was able to
252 automatically detect and configure ONVIF devices, so I could use it to
253 set up motion detection in and collection of the camera output. I had
254 initial problems getting the ONVIF autodetection to work, as both
255 Firefox and Chromium
<a href=
"https://bugs.debian.org/
1001188">refused
256 the inter-tab communication
</a
> being used by the Zoneminder web
257 pages, but managed to get konqueror to work. Apparently the
"Enhanced
258 Tracking Protection
" in Firefox cause the problem. I ended up
259 upgrading to the Bookworm edition of Zoneminder in the process to try
260 to fix the issue, and believe the problem might be solved now.
</p
>
262 <p
>In the process I came across the nice Linux GUI tool
263 <a href=
"https://gitlab.com/caspermeijn/onvifviewer/
">ONVIF Viewer
</a
>
264 allowing me to preview the camera output and validate the login
265 passwords required. Sadly its author has grown tired of maintaining
266 the software, so it might not see any future updates. Which is sad,
267 as the viewer is sightly unstable and the picture tend to lock up.
268 Note, this lockup might be due to limitations in the cameras and not
269 the viewer implementation. I suspect the camera is only able to
270 provide pictures to one client at the time, and the Zoneminder feed
271 might interfere with the GUI viewer. I have
272 <a href=
"https://bugs.debian.org/
1000820">asked for the tool to be
273 included in Debian
</a
>.
</p
>
275 <p
>Finally, I found what appear to be very nice Linux free software
276 replacement for the Windows tool, named
277 <a href=
"https://github.com/sr99622/libonvif/
">libonvif
</a
>. It
278 provide a C library to talk to ONVIF devices as well as a command line
279 and GUI tool using the library. Using the GUI tool I was able to change
280 the admin passwords and update other settings of the cameras. I have
281 <a href=
"https://bugs.debian.org/
1021980">asked for the package to be
282 included in Debian
</a
>.
</p
>
284 <p
>As usual, if you use Bitcoin and want to show your support of my
285 activities, please send Bitcoin donations to my address
286 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
288 <p
><strong
>Update
2022-
10-
20</strong
>: Since my initial publication of
289 this text, I got several suggestions for more free software Linux
290 tools. There is
<a href=
"https://github.com/quatanium/python-onvif
">a
291 ONVIF python library
</a
> (already
292 <a href=
"https://bugs.debian.org/
824240">requested into Debian
</a
>) and
293 <a href=
"https://github.com/FalkTannhaeuser/python-onvif-zeep
">a python
3
294 fork
</a
> using a different SOAP dependency. There is also
295 <a href=
"https://www.home-assistant.io/integrations/onvif/
">support for
296 ONVIF in Home Assistant
</a
>, and there is an alternative to Zoneminder
297 called
<a href=
"https://www.shinobi.video/
">Shinobi
</a
>. The latter
298 two are not included in Debian either. I have not tested any of these
304 <title>Time to translate the Bullseye edition of the Debian Administrator
's Handbook
</title>
305 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</link>
306 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</guid>
307 <pubDate>Mon,
12 Sep
2022 15:
45:
00 +
0200</pubDate>
308 <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
>
310 <p
>(The picture is of the previous edition.)
</p
>
312 <p
>Almost two years after the previous Norwegian Bokmål translation of
313 the
"<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
314 Handbook
</a
>" was published, a new edition is finally being prepared. The
315 english text is updated, and it is time to start working on the
316 translations. Around
37 percent of the strings have been updated, one
317 way or another, and the translations starting from a complete Debian Buster
318 edition now need to bring their translation up from
63% to
100%. The
319 complete book is licensed using a Creative Commons license, and has
320 been published in several languages over the years. The translations
321 are done by volunteers to bring Linux in their native tongue. The
322 last time I checked, it complete text was available in English,
323 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
324 In addition, work has been started for Arabic (Morocco), Catalan,
325 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
326 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
327 Romanian, Russian, Swedish, Turkish and Vietnamese.
</p
>
329 <p
>The translation is conducted on
330 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
331 hosted weblate project page
</a
>. Prospective translators are
332 recommeded to subscribe to
333 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
334 translators mailing list
</a
> and should also check out
335 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
336 contributors
</a
>.
</p
>
338 <p
>I am one of the Norwegian Bokmål translators of this book, and we
339 have just started. Your contribution is most welcome.
</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>Automatic LinuxCNC servo PID tuning?
</title>
349 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</link>
350 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</guid>
351 <pubDate>Sat,
16 Jul
2022 22:
30:
00 +
0200</pubDate>
352 <description><p
>While working on a CNC with servo motors controlled by the
353 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>
354 <a href=
"https://en.wikipedia.org/wiki/PID_controller
">PID
355 controller
</a
>, I recently had to learn how to tune the collection of values
356 that control such mathematical machinery that a PID controller is. It
357 proved to be a lot harder than I hoped, and I still have not succeeded
358 in getting the Z PID controller to successfully defy gravity, nor X
359 and Y to move accurately and reliably. But while climbing up this
360 rather steep learning curve, I discovered that some motor control
361 systems are able to tune their PID controllers. I got the impression
362 from the documentation that LinuxCNC were not. This proved to be not
365 <p
>The LinuxCNC
366 <a href=
"http://linuxcnc.org/docs/html/man/man9/pid
.9.html
">pid
367 component
</a
> is the recommended PID controller to use. It uses eight
368 constants
<tt
>Pgain
</tt
>,
<tt
>Igain
</tt
>,
<tt
>Dgain
</tt
>,
369 <tt
>bias
</tt
>,
<tt
>FF0
</tt
>,
<tt
>FF1
</tt
>,
<tt
>FF2
</tt
> and
370 <tt
>FF3
</tt
> to calculate the output value based on current and wanted
371 state, and all of these need to have a sensible value for the
372 controller to behave properly. Note, there are even more values
373 involved, theser are just the most important ones. In my case I need
374 the X, Y and Z axes to follow the requested path with little error.
375 This has proved quite a challenge for someone who have never tuned a
376 PID controller before, but there is at least some help to be found.
378 <p
>I discovered that included in LinuxCNC was this old PID component
379 at_pid claiming to have auto tuning capabilities. Sadly it had been
380 neglected since
2011, and could not be used as a plug in replacement
381 for the default pid component. One would have to rewriting the
382 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
383 to quickly test auto tuning to see if it did a better job than me at
384 figuring out good P, I and D values to use.
</p
>
386 <p
>I decided to have a look if the situation could be improved. This
387 involved trying to understand the code and history of the pid and
388 at_pid components. Apparently they had a common ancestor, as code
389 structure, comments and variable names were quite close to each other.
390 Sadly this was not reflected in the git history, making it hard to
391 figure out what really happened. My guess is that the author of
392 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c
">at_pid.c
</a
>
394 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c
">pid.c
</a
>,
395 rewrote it to follow the structure he wished pid.c to have, then added
396 support for auto tuning and finally got it included into the LinuxCNC
397 repository. The restructuring and lack of early history made it
398 harder to figure out which part of the code were relevant to the auto
399 tuning, and which part of the code needed to be updated to work the
400 same way as the current pid.c implementation. I started by trying to
401 isolate relevant changes in pid.c, and applying them to at_pid.c. My
402 aim was to make sure the at_pid component could replace the pid
403 component with a simple change in the HAL setup loadrt line, without
404 having to
"rewire
" the rest of the HAL configuration. After a few
405 hours following this approach, I had learned quite a lot about the
406 code structure of both components, while concluding I was heading down
407 the wrong rabbit hole, and should get back to the surface and find a
408 different path.
</p
>
410 <p
>For the second attempt, I decided to throw away all the PID control
411 related part of the original at_pid.c, and instead isolate and lift
412 the auto tuning part of the code and inject it into a copy of pid.c.
413 This ensured compatibility with the current pid component, while
414 adding auto tuning as a run time option. To make it easier to identify
415 the relevant parts in the future, I wrapped all the auto tuning code
416 with
'#ifdef AUTO_TUNER
'. The end result behave just like the current
417 pid component by default, as that part of the code is identical. The
418 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
1820">end result
419 entered the LinuxCNC master branch
</a
> a few days ago.
</p
>
421 <p
>To enable auto tuning, one need to set a few HAL pins in the PID
422 component. The most important ones are
<tt
>tune-effort
</tt
>,
423 <tt
>tune-mode
</tt
> and
<tt
>tune-start
</tt
>. But lets take a step
424 back, and see what the auto tuning code will do. I do not know the
425 mathematical foundation of the at_pid algorithm, but from observation
426 I can tell that the algorithm will, when enabled, produce a square
427 wave pattern centered around the
<tt
>bias
</tt
> value on the output pin
428 of the PID controller. This can be seen using the HAL Scope provided
429 by LinuxCNC. In my case, this is translated into voltage (+-
10V) sent
430 to the motor controller, which in turn is translated into motor speed.
431 So at_pid will ask the motor to move the axis back and forth. The
432 number of cycles in the pattern is controlled by the
433 <tt
>tune-cycles
</tt
> pin, and the extremes of the wave pattern is
434 controlled by the
<tt
>tune-effort
</tt
> pin. Of course, trying to
435 change the direction of a physical object instantly (as in going
436 directly from a positive voltage to the equivalent negative voltage)
437 do not change velocity instantly, and it take some time for the object
438 to slow down and move in the opposite direction. This result in a
439 more smooth movement wave form, as the axis in question were vibrating
440 back and forth. When the axis reached the target speed in the
441 opposing direction, the auto tuner change direction again. After
442 several of these changes, the average time delay between the
'peaks
'
443 and
'valleys
' of this movement graph is then used to calculate
444 proposed values for Pgain, Igain and Dgain, and insert them into the
445 HAL model to use by the pid controller. The auto tuned settings are
446 not great, but htye work a lot better than the values I had been able
447 to cook up on my own, at least for the horizontal X and Y axis. But I
448 had to use very small
<tt
>tune-effort
<tt
> values, as my motor
449 controllers error out if the voltage change too quickly. I
've been
450 less lucky with the Z axis, which is moving a heavy object up and
451 down, and seem to confuse the algorithm. The Z axis movement became a
452 lot better when I introduced a
<tt
>bias
</tt
> value to counter the
453 gravitational drag, but I will have to work a lot more on the Z axis
454 PID values.
</p
>
456 <p
>Armed with this knowledge, it is time to look at how to do the
457 tuning. Lets say the HAL configuration in question load the PID
458 component for X, Y and Z like this:
</p
>
460 <blockquote
><pre
>
461 loadrt pid names=pid.x,pid.y,pid.z
462 </pre
></blockquote
>
464 <p
>Armed with the new and improved at_pid component, the new line will
465 look like this:
</p
>
467 <blockquote
><pre
>
468 loadrt at_pid names=pid.x,pid.y,pid.z
469 </pre
></blockquote
>
471 <p
>The rest of the HAL setup can stay the same. This work because the
472 components are referenced by name. If the component had used count=
3
473 instead, all use of pid.# had to be changed to at_pid.#.
</p
>
475 <p
>To start tuning the X axis, move the axis to the middle of its
476 range, to make sure it do not hit anything when it start moving back
477 and forth. Next, set the
<tt
>tune-effort
</tt
> to a low number in the
478 output range. I used
0.1 as my initial value. Next, assign
1 to the
479 <tt
>tune-mode
</tt
> value. Note, this will disable the pid controlling
480 part and feed
0 to the output pin, which in my case initially caused a
481 lot of drift. In my case it proved to be a good idea with X and Y to
482 tune the motor driver to make sure
0 voltage stopped the motor
483 rotation. On the other hand, for the Z axis this proved to be a bad
484 idea, so it will depend on your setup. It might help to set the
485 <tt
>bias
</tt
> value to a output value that reduce or eliminate the
486 axis drift. Finally, after setting
<tt
>tune-mode
</tt
>, set
487 <tt
>tune-start
</tt
> to
1 to activate the auto tuning. If all go well,
488 your axis will vibrate for a few seconds and when it is done, new
489 values for Pgain, Igain and Dgain will be active. To test them,
490 change
<tt
>tune-mode
</tt
> back to
0. Note that this might cause the
491 machine to suddenly jerk as it bring the axis back to its commanded
492 position, which it might have drifted away from during tuning. To
493 summarize with some halcmd lines:
</p
>
495 <blockquote
><pre
>
496 setp pid.x.tune-effort
0.1
497 setp pid.x.tune-mode
1
498 setp pid.x.tune-start
1
499 # wait for the tuning to complete
500 setp pid.x.tune-mode
0
501 </pre
></blockquote
>
503 <p
>After doing this task quite a few times while trying to figure out
504 how to properly tune the PID controllers on the machine in, I decided
505 to figure out if this process could be automated, and wrote a script
506 to do the entire tuning process from power on. The end result will
507 ensure the machine is powered on and ready to run, home all axis if it
508 is not already done, check that the extra tuning pins are available,
509 move the axis to its mid point, run the auto tuning and re-enable the
510 pid controller when it is done. It can be run several times. Check
512 <a href=
"https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner
">run-auto-pid-tuner
</a
>
513 script on github if you want to learn how it is done.
</p
>
515 <p
>My hope is that this little adventure can inspire someone who know
516 more about motor PID controller tuning can implement even better
517 algorithms for automatic PID tuning in LinuxCNC, making life easier
518 for both me and all the others that want to use LinuxCNC but lack the
519 in depth knowledge needed to tune PID controllers well.
</p
>
521 <p
>As usual, if you use Bitcoin and want to show your support of my
522 activities, please send Bitcoin donations to my address
523 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
528 <title>LinuxCNC translators life just got a bit easier
</title>
529 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</link>
530 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</guid>
531 <pubDate>Fri,
3 Jun
2022 21:
10:
00 +
0200</pubDate>
532 <description><p
>Back in oktober last year, when I started looking at the
533 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
> system, I
534 proposed to change the documentation build system make life easier for
535 translators. The original system consisted of independently written
536 documentation files for each language, with no automated way to track
537 changes done in other translations and no help for the translators to
538 know how much was left to translated. By using
539 <a href=
"https://po4a.org/
">the po4a system
</a
> to generate POT and PO
540 files from the English documentation, this can be improved. A small
541 team of LinuxCNC contributors got together and today our labour
542 finally payed off. Since a few hours ago, it is now possible to
543 translate
<a href=
"https://hosted.weblate.org/projects/linuxcnc/
">the
544 LinuxCNC documentation on Weblate
</a
>, alongside the program itself.
</p
>
546 <p
>The effort to migrate the documentation to use po4a has been both
547 slow and frustrating. I am very happy we finally made it.
</p
>
549 <p
>As usual, if you use Bitcoin and want to show your support of my
550 activities, please send Bitcoin donations to my address
551 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
556 <title>geteltorito make CD firmware upgrades a breeze
</title>
557 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</link>
558 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</guid>
559 <pubDate>Wed,
20 Apr
2022 11:
50:
00 +
0200</pubDate>
560 <description><p
>Recently I wanted to upgrade the firmware of my thinkpad, and
561 located the firmware download page from Lenovo (which annoyingly do
562 not allow access via Tor, forcing me to hand them more personal
563 information that I would like). The
564 <a href=
"https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso
&SearchType=Customer search
&searchLocation=Masthead
">download
565 from Lenovo
</a
> is a bootable ISO image, which is a bit of a problem
566 when all I got available is a USB memory stick. I tried booting the
567 ISO as a USB stick, but this did not work. But genisoimage came to
568 the rescue.
</p
>
570 <P
>The geteltorito program in
571 <a href=
"http://tracker.debian.org/cdrkit
">the genisoimage binary
572 package
</a
> is able to convert the bootable ISO image to a bootable
573 USB stick using a simple command line recipe, which I then can write
574 to the most recently inserted USB stick:
</p
>
576 <blockquote
><pre
>
577 geteltorito -o usbstick.img lenovo-firmware.iso
578 sudo dd bs=
10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -
1)
579 </pre
></blockquote
>
581 <p
>This USB stick booted the firmware upgrader just fine, and in a few
582 minutes my machine had the latest and greatest BIOS firmware in place.
</p
>
587 <title>Run your industrial metal working machine using Debian?
</title>
588 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</link>
589 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</guid>
590 <pubDate>Wed,
2 Mar
2022 18:
40:
00 +
0100</pubDate>
591 <description><p
>After many months of hard work by the good people involved in
592 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>, the
593 system was accepted Sunday
594 <a href=
"https://tracker.debian.org/pkg/linuxcnc
">into Debian
</a
>.
595 Once it was available from Debian, I was surprised to discover from
596 <a href=
"https://qa.debian.org/popcon.php?package=linuxcnc
">its
597 popularity-contest numbers
</a
> that people have been reporting its use
598 since
2012.
<a href=
"http://linuxcnc.org/
">Its project site
</a
> might
599 be a good place to check out, but sadly is not working when visiting
602 <p
>But what is LinuxCNC, you are probably wondering? Perhaps a
603 Wikipedia quote is in place?
</p
>
606 "LinuxCNC is a software system for numerical control of
607 machines such as milling machines, lathes, plasma cutters, routers,
608 cutting machines, robots and hexapods. It can control up to
9 axes or
609 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
610 several GUIs suited to specific kinds of usage (touch screen,
611 interactive development).
"
614 <p
>It can even control
3D printers. And even though the Wikipedia
615 page indicate that it can only work with hard real time kernel
616 features, it can also work with the user space soft real time features
617 provided by the Debian kernel.
618 <a href=
"https://github.com/linuxcnc/linuxcnc
">The source code
</a
> is
619 available from Github. The last few months I
've been involved in the
620 translation setup for the program and documentation. Translators are
622 <a href=
"https://hosted.weblate.org/engage/linuxcnc/
">join the
623 effort
</a
> using Weblate.
</p
>
625 <p
>As usual, if you use Bitcoin and want to show your support of my
626 activities, please send Bitcoin donations to my address
627 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
632 <title>Debian still an excellent choice for Lego builders
</title>
633 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</link>
634 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</guid>
635 <pubDate>Sun,
24 Oct
2021 07:
10:
00 +
0200</pubDate>
636 <description><p
>The Debian Lego team saw a lot of activity the last few weeks. All
637 the packages under the team umbrella has been updated to fix
638 packaging, lintian issues and BTS reports. In addition, a new and
639 inspiring team member appeared on both the
640 <a href=
"https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team
">debian-lego-team
641 Team mailing list
</a
> and
642 <a href=
"irc://irc.debian.org/%
23debian-lego
">IRC channel
643 #debian-lego
</a
>. If you are interested in Lego CAD design and LEGO
644 Mindstorms programming, check out the
645 <a href=
"http://wiki.debian.org/LegoDesigners
">team wiki page
</a
> to
646 see what Debian can offer the Lego enthusiast.
</p
>
648 <p
>Patches has been sent upstream, causing new upstream releases, one
649 even the first one in more than ten years, and old upstreams was
650 released with new ones. There are still a lot of work left, and the
651 team welcome more members to help us make sure Debian is the Linux
652 distribution of choice for Lego builders. If you want to contribute,
653 join us in the IRC channel and become part of
654 <a href=
"https://salsa.debian.org/debian-lego-team/
">the team on
655 Salsa
</a
>.
</p
>
657 <p
>As usual, if you use Bitcoin and want to show your support of my
658 activities, please send Bitcoin donations to my address
659 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
664 <title>Six complete translations of The Debian Administrator
's Handbook for Buster
</title>
665 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</link>
666 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</guid>
667 <pubDate>Mon,
5 Jul
2021 19:
20:
00 +
0200</pubDate>
668 <description><p
>I am happy observe that the
<a href=
"https://debian-handbook.info/
">The
669 Debian Administrator
's Handbook
</a
> is available in six languages now.
670 I am not sure which one of these are completely proof read, but the
671 complete book is available in these languages:
675 <li
>English
</li
>
676 <li
>Norwegian Bokmål
</li
>
677 <li
>German
</li
>
678 <li
>Indonesian
</li
>
679 <li
>Brazil Portuguese
</li
>
680 <li
>Spanish
</li
>
684 <p
>This is the list of languages more than
70% complete, in other
685 words with not too much left to do:
</p
>
689 <li
>Chinese (Simplified) -
90%
</li
>
690 <li
>French -
79%
</li
>
691 <li
>Italian -
79%
</li
>
692 <li
>Japanese -
77%
</li
>
693 <li
>Arabic (Morocco) -
75%
</li
>
694 <li
>Persian -
71%
</li
>
698 <p
>I wonder how long it will take to bring these to
100%.
</p
>
700 <p
>Then there is the list of languages about halfway done:
</p
>
704 <li
>Russian -
63%
</li
>
705 <li
>Swedish -
53%
</li
>
706 <li
>Chinese (Traditional) -
46%
</li
>
707 <li
>Catalan -
45%
</li
>
711 <p
>Several are on to a good start:
</p
>
715 <li
>Dutch -
26%
</li
>
716 <li
>Vietnamese -
25%
</li
>
717 <li
>Polish -
23%
</li
>
718 <li
>Czech -
22%
</li
>
719 <li
>Turkish -
18%
</li
>
723 <p
>Finally, there are the ones just getting started:
</p
>
727 <li
>Korean -
4%
</li
>
728 <li
>Croatian -
2%
</li
>
729 <li
>Greek -
2%
</li
>
730 <li
>Danish -
1%
</li
>
731 <li
>Romanian -
1%
</li
>
735 <p
>If you want to help provide a Debian instruction book in your own
737 <a href=
"https://hosted.weblate.org/projects/debian-handbook/#languages
">Weblate
</a
>
738 to contribute to the translations.
</p
>
740 <p
>As usual, if you use Bitcoin and want to show your support of my
741 activities, please send Bitcoin donations to my address
742 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
747 <title>Latest Jami back in Debian Testing, and scriptable using dbus
</title>
748 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</link>
749 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</guid>
750 <pubDate>Tue,
12 Jan
2021 17:
00:
00 +
0100</pubDate>
751 <description><p
>After a lot of hard work by its maintainer Alexandre Viau and
752 others, the decentralized communication platform
753 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>
754 (earlier known as Ring), managed to get
755 <a href=
"https://tracker.debian.org/pkg/ring
">its latest version
</a
>
756 into Debian Testing. Several of its dependencies has caused build and
757 propagation problems, which all seem to be solved now.
</p
>
759 <p
>In addition to the fact that Jami is decentralized, similar to how
760 bittorrent is decentralized, I first of all like how it is not
761 connected to external IDs like phone numbers. This allow me to set up
762 computers to send me notifications using Jami without having to find
763 get a phone number for each computer. Automatic notification via Jami
764 is also made trivial thanks to the provided client side API (as a DBus
765 service). Here is my bourne shell script demonstrating how to let any
766 system send a message to any Jami address. It will create a new
767 identity before sending the message, if no Jami identity exist
773 # Usage: $
0 <jami-address
> <message
>
775 # Send
<message
> to
<jami-address
>, create local jami account if
778 # License: GPL v2 or later at your choice
779 # Author: Petter Reinholdtsen
782 if [ -z
"$HOME
" ] ; then
783 echo
"error: missing \$HOME, required for dbus to work
"
787 # First, get dbus running if not already running
788 DBUSLAUNCH=/usr/bin/dbus-launch
789 PIDFILE=/run/asterisk/dbus-session.pid
790 if [ -e $PIDFILE ] ; then
792 if ! kill -
0 $DBUS_SESSION_BUS_PID
2>/dev/null ; then
793 unset DBUS_SESSION_BUS_ADDRESS
796 if [ -z
"$DBUS_SESSION_BUS_ADDRESS
" ]
&& [ -x
"$DBUSLAUNCH
" ]; then
797 DBUS_SESSION_BUS_ADDRESS=
"unix:path=$HOME/.dbus
"
798 dbus-daemon --session --address=
"$DBUS_SESSION_BUS_ADDRESS
" --nofork --nopidfile --syslog-only
< /dev/null
> /dev/null
2>&1 3>&1 &
799 DBUS_SESSION_BUS_PID=$!
801 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
802 echo DBUS_SESSION_BUS_ADDRESS=\
""$DBUS_SESSION_BUS_ADDRESS
"\
"
803 echo export DBUS_SESSION_BUS_ADDRESS
809 part=
"$
1"; shift
810 op=
"$
1"; shift
811 dbus-send --session \
812 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
816 part=
"$
1"; shift
817 op=
"$
1"; shift
818 dbus-send --session --print-reply \
819 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
823 dringopreply ConfigurationManager getAccountList | \
824 grep string | awk -F
'"' '{print $
2}
' | head -n
1
827 account=$(firstaccount)
829 if [ -z
"$account
" ] ; then
830 echo
"Missing local account, trying to create it
"
831 dringop ConfigurationManager addAccount \
832 dict:string:string:
"Account.type
",
"RING
",
"Account.videoEnabled
",
"false
"
833 account=$(firstaccount)
834 if [ -z
"$account
" ] ; then
835 echo
"unable to create local account
"
840 # Not using dringopreply to ensure $
2 can contain spaces
841 dbus-send --print-reply --session \
842 --dest=cx.ring.Ring \
843 /cx/ring/Ring/ConfigurationManager \
844 cx.ring.Ring.ConfigurationManager.sendTextMessage \
845 string:
"$account
" string:
"$
1" \
846 dict:string:string:
"text/plain
",
"$
2"
847 </pre
></p
>
849 <p
>If you want to check it out yourself, visit the
850 <a href=
"https://jami.net/
">the Jami system project page
</a
> to learn
851 more, and install the latest Jami client from Debian Unstable or
854 <p
>As usual, if you use Bitcoin and want to show your support of my
855 activities, please send Bitcoin donations to my address
856 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
861 <title>Buster based Bokmål edition of Debian Administrator
's Handbook
</title>
862 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
863 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
864 <pubDate>Tue,
20 Oct
2020 18:
35:
00 +
0200</pubDate>
865 <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
>
867 <p
>I am happy to report that we finally made it! Norwegian Bokmål
868 became the first translation published on paper of the new Buster
869 based edition of
"<a href=
"https://debian-handbook.info/
">The Debian
870 Administrator
's Handbook
</a
>". The print proof reading copy arrived
871 some days ago, and it looked good, so now the book is approved for
872 general distribution. This updated paperback edition
<a
873 href=
"https://debian-handbook.info/get/#norwegian
">is available from
874 lulu.com
</a
>. The book is also available for download in electronic
875 form as PDF, EPUB and Mobipocket, and can also be
876 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
</a
>.
</p
>
878 <p
>I am very happy to wrap up this Creative Common licensed project,
879 which concludes several months of work by several volunteers. The
880 number of Linux related books published in Norwegian are few, and I
881 really hope this one will gain many readers, as it is packed with deep
882 knowledge on Linux and the Debian ecosystem. The book will be
883 available for various Internet book stores like Amazon and Barnes
&
884 Noble soon, but I recommend buying
885 "<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
886 for Debian-administratoren
</a
>" directly from the source at Lulu.
888 <p
>As usual, if you use Bitcoin and want to show your support of my
889 activities, please send Bitcoin donations to my address
890 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
895 <title>Buster update of Norwegian Bokmål edition of Debian Administrator
's Handbook almost done
</title>
896 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html
</link>
897 <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>
898 <pubDate>Fri,
11 Sep
2020 09:
45:
00 +
0200</pubDate>
899 <description><p
>Thanks to the good work of several volunteers, the updated edition
900 of the Norwegian translation for
901 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
902 Handbook
</a
>" is now almost completed. After many months of proof
903 reading, I consider the proof reading complete enough for us to move
904 to the next step, and have asked for the print version to be prepared
905 and sent of to the print on demand service lulu.com. While it is
906 still not to late if you find any incorrect translations on
907 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
908 hosted Weblate service
</a
>, but it will be soon. :) You can check out
909 <a href=
" https://debian-handbook.info/browse/nb-NO/stable/
">the Buster
910 edition on the web
</a
> until the print edition is ready.
</p
>
912 <p
>The book will be for sale on lulu.com and various web book stores,
913 with links available from the web site for the book linked to above.
914 I hope a lot of readers find it useful.
</p
>
916 <p
>As usual, if you use Bitcoin and want to show your support of my
917 activities, please send Bitcoin donations to my address
918 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
923 <title>Working on updated Norwegian Bokmål edition of Debian Administrator
's Handbook
</title>
924 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
925 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
926 <pubDate>Sat,
4 Jul
2020 23:
55:
00 +
0200</pubDate>
927 <description><p
>Three years ago, the first Norwegian Bokmål edition of
928 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
929 Handbook
</a
>" was published. This was based on Debian Jessie. Now a
930 new and updated version based on Buster is getting ready. Work on the
931 updated Norwegian Bokmål edition has been going on for a few months
932 now, and yesterday, we reached the first mile stone, with
100% of the
933 texts being translated. A lot of proof reading remains, of course,
934 but a major step towards a new edition has been taken.
</p
>
936 <p
>The book is translated by volunteers, and we would love to get some
937 help with the proof reading. The translation uses
938 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
939 hosted Weblate service
</a
>, and we welcome everyone to have a look and
940 submit improvements and suggestions. There is also a proof readers
941 PDF available on request, get in touch if you want to help out that
944 <p
>As usual, if you use Bitcoin and want to show your support of my
945 activities, please send Bitcoin donations to my address
946 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
951 <title>Secure Socket API - a simple and powerful approach for TLS support in software
</title>
952 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</link>
953 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</guid>
954 <pubDate>Sat,
6 Jun
2020 12:
40:
00 +
0200</pubDate>
955 <description><p
>As a member of the
<a href=
"https://www.nuug.no/
">Norwegian Unix
956 User Group
</a
>, I have the pleasure of receiving the
957 <a href=
"https://www.usenix.org/
">USENIX
</a
> magazine
958 <a href=
"https://www.usenix.org/publications/login/
">;login:
</a
>
959 several times a year. I rarely have time to read all the articles,
960 but try to at least skim through them all as there is a lot of nice
961 knowledge passed on there. I even carry the latest issue with me most
962 of the time to try to get through all the articles when I have a few
963 spare minutes.
</p
>
965 <p
>The other day I came across a nice article titled
966 "<a href=
"https://www.usenix.org/publications/login/winter2018/oneill
">The
967 Secure Socket API: TLS as an Operating System Service
</a
>" with a
968 marvellous idea I hope can make it all the way into the POSIX standard.
969 The idea is as simple as it is powerful. By introducing a new
970 socket() option IPPROTO_TLS to use TLS, and a system wide service to
971 handle setting up TLS connections, one both make it trivial to add TLS
972 support to any program currently using the POSIX socket API, and gain
973 system wide control over certificates, TLS versions and encryption
974 systems used. Instead of doing this:
</p
>
976 <p
><blockquote
><pre
>
977 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
978 </pre
></blockquote
></p
>
980 <p
>the program code would be doing this:
<p
>
982 <p
><blockquote
><pre
>
983 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
984 </pre
></blockquote
></p
>
986 <p
>According to the ;login: article, converting a C program to use TLS
987 would normally modify only
5-
10 lines in the code, which is amazing
988 when compared to using for example the OpenSSL API.
</p
>
990 <p
>The project has set up the
991 <a href=
"https://securesocketapi.org/
">https://securesocketapi.org/
</a
>
992 web site to spread the idea, and the code for a kernel module and the
993 associated system daemon is available from two github repositories:
994 <a href=
"https://github.com/markoneill/ssa
">ssa
</a
> and
995 <a href=
"https://github.com/markoneill/ssa-daemon
">ssa-daemon
</a
>.
996 Unfortunately there is no explicit license information with the code,
997 so its copyright status is unclear. A
998 <a href=
"https://github.com/markoneill/ssa/issues/
2">request to solve
999 this
</a
> about it has been unsolved since
2018-
08-
17.
</p
>
1001 <p
>I love the idea of extending socket() to gain TLS support, and
1002 understand why it is an advantage to implement this as a kernel module
1003 and system wide service daemon, but can not help to think that it
1004 would be a lot easier to get projects to move to this way of setting
1005 up TLS if it was done with a user space approach where programs
1006 wanting to use this API approach could just link with a wrapper
1009 <p
>I recommend you check out this simple and powerful approach to more
1010 secure network connections. :)
</p
>
1012 <p
>As usual, if you use Bitcoin and want to show your support of my
1013 activities, please send Bitcoin donations to my address
1014 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1019 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
1020 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
1021 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
1022 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
1023 <description><p
>Half a year ago,
1024 <a href=
"http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
1025 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
1026 client
</a
>, capable of peer-to-peer encrypted communication. It
1027 handle both messages, audio and video. It uses distributed hash
1028 tables instead of central infrastructure to connect its users to each
1029 other, which in my book is a plus. I mentioned briefly that it could
1030 also work as a SIP client, which came in handy when the higher
1031 educational sector in Norway started to promote Zoom as its video
1032 conferencing solution. I am reluctant to use the official Zoom client
1033 software, due to their
<a href=
"https://zoom.us/terms
">copyright
1034 license clauses
</a
> prohibiting users to reverse engineer (for example
1035 to check the security) and benchmark it, and thus prefer to connect to
1036 Zoom meetings with free software clients.
</p
>
1038 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
1039 password set on the room. The Jami daemon leak memory like crazy
1040 (approximately
1 GiB a minute) when I am connected to the video
1041 conference, so I had to restart the client every
7-
10 minutes, which
1042 is not great. I tried to get other SIP Linux clients to work
1043 without success, so I decided I would have to live with this wart
1044 until someone managed to fix the leak in the dring code base. But
1045 another problem showed up once the rooms were password protected. I
1046 could not get my dial tone signaling through from Jami to Zoom, and
1047 dial tone signaling is used to enter the password when connecting to
1048 Zoom. I tried a lot of different permutations with my Jami and
1049 Asterisk setup to try to figure out why the signaling did not get
1050 through, only to finally discover that the fundamental problem seem to
1051 be that Zoom is simply not able to receive dial tone signaling when
1052 connecting via SIP. There seem to be nothing wrong with the Jami and
1053 Asterisk end, it is simply broken in the Zoom end. I got help from a
1054 very skilled VoIP engineer figuring out this last part. And being a
1055 very skilled engineer, he was also able to locate a solution for me.
1056 Or to be exact, a workaround that solve my initial problem of
1057 connecting to password protected Zoom rooms using Jami.
</p
>
1059 <p
>So, how do you do this, I am sure you are wondering by now. The
1061 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
1062 from Zoom
</a
>, and it is to modify the SIP address to include the room
1063 password. What is most surprising about this is that the
1064 automatically generated email from Zoom with instructions on how to
1065 connect via SIP do not mention this. The SIP address to use normally
1066 consist of the room ID (a number), an @ character and the IP address
1067 of the Zoom SIP gateway. But Zoom understand a lot more than just the
1068 room ID in front of the at sign. The format is
"<tt
>[Meeting
1069 ID].[Password].[Layout].[Host Key]
</tt
>", and you can here see how you
1070 can both enter password, control the layout (full screen, active
1071 presence and gallery) and specify the host key to start the meeting.
1072 The full SIP address entered into Jami to provide the password will
1073 then look like this (all using made up numbers):
</p
>
1075 <p
><blockquote
>
1076 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
1077 </blockquote
></p
>
1079 <p
>Now if only jami would reduce its memory usage, I could even
1080 recommend this setup to others. :)
</p
>
1082 <p
>As usual, if you use Bitcoin and want to show your support of my
1083 activities, please send Bitcoin donations to my address
1084 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1089 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software
</title>
1090 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</link>
1091 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</guid>
1092 <pubDate>Wed,
29 Apr
2020 13:
10:
00 +
0200</pubDate>
1093 <description><p
>The curiosity got the better of me when
1094 <a href=
"https://developers.slashdot.org/story/
20/
04/
06/
1424246/new-jersey-desperately-needs-cobol-programmers
">Slashdot
1095 reported
</a
> that New Jersey was desperately looking for
1096 <a href=
"https://en.wikipedia.org/wiki/COBOL
">COBOL
</a
> programmers,
1097 and a few days later it was reported that
1098 <a href=
"https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce
">IBM
1099 tried to locate COBOL programmers
</a
>.
</p
>
1101 <p
>I thus decided to have a look at free software alternatives to
1102 learn COBOL, and had the pleasure to find
1103 <a href=
"https://sourceforge.net/projects/open-cobol/
">GnuCOBOL
</a
> was
1104 already
<a href=
"https://tracker.debian.org/pkg/gnucobol
">in
1105 Debian
</a
>. It used to be called Open Cobol, and is a
"compiler
"
1106 transforming COBOL code to C or C++ before giving it to GCC or Visual
1107 Studio to build binaries.
</p
>
1109 <p
>I managed to get in touch with upstream, and was impressed with the
1110 quick response, and also was happy to see a new Debian maintainer
1111 taking over when the original one recently asked to be replaced. A
1112 new Debian upload was done as recently as yesterday.
</p
>
1114 <p
>Using the Debian package, I was able to follow a simple COBOL
1115 introduction and make and run simple COBOL programs. It was fun to
1116 learn a new programming language. If you want to test for yourself,
1117 <a href=
"https://en.wikipedia.org/wiki/GnuCOBOL
">the GnuCOBOL Wikipedia
1118 page
</a
> have a few simple examples to get you startet.
</p
>
1120 <p
>As I do not have much experience with COBOL, I do not know how
1121 standard compliant it is, but it claim to pass most tests from COBOL
1122 test suite, which sound good to me. It is nice to know it is possible
1123 to learn COBOL using software without any usage restrictions, and I am
1124 very happy such nice free software project as this is available. If
1125 you as me is curious about COBOL, check it out.
</p
>
1127 <p
>As usual, if you use Bitcoin and want to show your support of my
1128 activities, please send Bitcoin donations to my address
1129 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1134 <title>Jami/Ring, finally functioning peer to peer communication client
</title>
1135 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</link>
1136 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</guid>
1137 <pubDate>Wed,
19 Jun
2019 08:
50:
00 +
0200</pubDate>
1138 <description><p
>Some years ago, in
2016, I
1139 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">wrote
1140 for the first time about
</a
> the Ring peer to peer messaging system.
1141 It would provide messaging without any central server coordinating the
1142 system and without requiring all users to register a phone number or
1143 own a mobile phone. Back then, I could not get it to work, and put it
1144 aside until it had seen more development. A few days ago I decided to
1145 give it another try, and am happy to report that this time I am able
1146 to not only send and receive messages, but also place audio and video
1147 calls. But only if UDP is not blocked into your network.
</p
>
1149 <p
>The Ring system changed name earlier this year to
1150 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>. I
1151 tried doing web search for
'ring
' when I discovered it for the first
1152 time, and can only applaud this change as it is impossible to find
1153 something called Ring among the noise of other uses of that word. Now
1154 you can search for
'jami
' and this client and
1155 <a href=
"https://jami.net/
">the Jami system
</a
> is the first hit at
1156 least on duckduckgo.
</p
>
1158 <p
>Jami will by default encrypt messages as well as audio and video
1159 calls, and try to send them directly between the communicating parties
1160 if possible. If this proves impossible (for example if both ends are
1161 behind NAT), it will use a central SIP TURN server maintained by the
1162 Jami project. Jami can also be a normal SIP client. If the SIP
1163 server is unencrypted, the audio and video calls will also be
1164 unencrypted. This is as far as I know the only case where Jami will
1165 do anything without encryption.
</p
>
1167 <p
>Jami is available for several platforms: Linux, Windows, MacOSX,
1168 Android, iOS, and Android TV. It is included in Debian already. Jami
1169 also work for those using F-Droid without any Google connections,
1170 while Signal do not.
1171 <a href=
"https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol
">The
1172 protocol
</a
> is described in the Ring project wiki. The system uses a
1173 distributed hash table (DHT) system (similar to BitTorrent) running
1174 over UDP. On one of the networks I use, I discovered Jami failed to
1175 work. I tracked this down to the fact that incoming UDP packages
1176 going to ports
1-
49999 were blocked, and the DHT would pick a random
1177 port and end up in the low range most of the time. After talking to
1178 the developers, I solved this by enabling the dhtproxy in the
1179 settings, thus using TCP to talk to a central DHT proxy instead of
1181 peering directly with others. I
've been told the developers are
1182 working on allowing DHT to use TCP to avoid this problem. I also ran
1183 into a problem when trying to talk to the version of Ring included in
1184 Debian Stable (Stretch). Apparently the protocol changed between
1185 beta2 and the current version, making these clients incompatible.
1186 Hopefully the protocol will not be made incompatible in the
1189 <p
>It is worth noting that while looking at Jami and its features, I
1190 came across another communication platform I have not tested yet. The
1191 <a href=
"https://en.wikipedia.org/wiki/Tox_(protocol)
">Tox protocol
</a
>
1192 and
<a href=
"https://tox.chat/
">family of Tox clients
</a
>. It might
1193 become the topic of a future blog post.
</p
>
1195 <p
>As usual, if you use Bitcoin and want to show your support of my
1196 activities, please send Bitcoin donations to my address
1197 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1202 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål
</title>
1203 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</link>
1204 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</guid>
1205 <pubDate>Wed,
23 Jan
2019 07:
50:
00 +
0100</pubDate>
1206 <description><p
>I høst ble jeg inspirert til å bidra til oversettelsen av
1207 <a href=
"http://unknown-horizons.org/
">strategispillet Unknown
1208 Horizons
</a
>, og oversatte de nesten
200 strengene i prosjektet til
1209 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
1210 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
1211 nye versjonen kom på nyåret, og ble
1212 <a href=
"https://tracker.debian.org/pkg/unknown-horizons
">lastet opp i
1213 Debian
</a
> for noen få dager siden. I går kveld fikk jeg testet det ut, og
1214 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
1215 måtte justeres, men ikke noe alvorlig. Har oppdatert
1216 <a href=
"https://hosted.weblate.org/projects/uh/
">oversettelsen på
1217 Weblate
</a
>, slik at neste utgave vil være enda bedre. :)
</p
>
1219 <p
>Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1220 å spille for oss som liker slikt. :)
</p
>
1222 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1223 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1225 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
1226 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
1231 <title>Debian now got everything you need to program Micro:bit
</title>
1232 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</link>
1233 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</guid>
1234 <pubDate>Tue,
22 Jan
2019 17:
20:
00 +
0100</pubDate>
1235 <description><p
>I am amazed and very pleased to discover that since a few days ago,
1236 everything you need to program the
<a href=
"https://microbit.org/
">BBC
1237 micro:bit
</a
> is available from the Debian archive. All this is
1238 thanks to the hard work of Nick Morrott and the Debian python
1239 packaging team. The micro:bit project recommend the mu-editor to
1240 program the microcomputer, as this editor will take care of all the
1241 machinery required to injekt/flash micropython alongside the program
1242 into the micro:bit, as long as the pieces are available.
</p
>
1244 <p
>There are three main pieces involved. The first to enter Debian
1246 <a href=
"https://tracker.debian.org/pkg/python-uflash
">python-uflash
</a
>,
1247 which was accepted into the archive
2019-
01-
12. The next one was
1248 <a href=
"https://tracker.debian.org/pkg/mu-editor
">mu-editor
</a
>, which
1249 showed up
2019-
01-
13. The final and hardest part to to into the
1251 <a href=
"https://tracker.debian.org/pkg/firmware-microbit-micropython
">firmware-microbit-micropython
</a
>,
1252 which needed to get its build system and dependencies into Debian
1253 before it was accepted
2019-
01-
20. The last one is already in Debian
1254 Unstable and should enter Debian Testing / Buster in three days. This
1255 all allow any user of the micro:bit to get going by simply running
1256 'apt install mu-editor
' when using Testing or Unstable, and once
1257 Buster is released as stable, all the users of Debian stable will be
1258 catered for.
</p
>
1260 <p
>As a minor final touch, I added rules to
1261 <a href=
"https://tracker.debian.org/pkg/isenkram
">the isenkram
1262 package
</a
> for recognizing micro:bit and recommend the mu-editor
1263 package. This make sure any user of the isenkram desktop daemon will
1264 get a popup suggesting to install mu-editor then the USB cable from
1265 the micro:bit is inserted for the first time.
</p
>
1267 <p
>This should make it easier to have fun.
</p
>
1269 <p
>As usual, if you use Bitcoin and want to show your support of my
1270 activities, please send Bitcoin donations to my address
1271 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1276 <title>Learn to program with Minetest on Debian
</title>
1277 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</link>
1278 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</guid>
1279 <pubDate>Sat,
15 Dec
2018 15:
30:
00 +
0100</pubDate>
1280 <description><p
>A fun way to learn how to program
1281 <a href=
"https://www.python.org/
">Python
</a
> is to follow the
1282 instructions in the book
1283 "<a href=
"https://nostarch.com/programwithminecraft
">Learn to program
1284 with Minecraft
</a
>", which introduces programming in Python to people
1285 who like to play with Minecraft. The book uses a Python library to
1286 talk to a TCP/IP socket with an API accepting build instructions and
1287 providing information about the current players in a Minecraft world.
1288 The TCP/IP API was first created for the Minecraft implementation for
1289 Raspberry Pi, and has since been ported to some server versions of
1290 Minecraft. The book contain recipes for those using Windows, MacOSX
1291 and Raspian. But a little known fact is that you can follow the same
1292 recipes using the free software construction game
1293 <a href=
"https://minetest.net/
">Minetest
</a
>.
</p
>
1295 <p
>There is
<a href=
"https://github.com/sprintingkiwi/pycraft_mod
">a
1296 Minetest module implementing the same API
</a
>, making it possible to
1297 use the Python programs coded to talk to Minecraft with Minetest too.
1299 <a href=
"https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%
2Bgit20180331.0376a0a%
2Bdfsg-
1.html
">uploaded
1300 this module
</a
> to Debian two weeks ago, and as soon as it clears the
1301 FTP masters NEW queue, learning to program Python with Minetest on
1302 Debian will be a simple
'apt install
' away. The Debian package is
1303 maintained as part of the Debian Games team, and
1304 <a href=
"https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft
">the
1305 packaging rules
</a
> are currently located under
'unfinished
' on
1308 <p
>You will most likely need to install several of the Minetest
1309 modules in Debian for the examples included with the library to work
1310 well, as there are several blocks used by the example scripts that are
1311 provided via modules in Minetest. Without the required blocks, a
1312 simple stone block is used instead. My initial testing with a analog
1313 clock did not get gold arms as instructed in the python library, but
1314 instead used stone arms.
</p
>
1316 <p
>I tried to find a way to add the API to the desktop version of
1317 Minecraft, but were unable to find any working recipes. The
1318 <a href=
"https://www.epiphanydigest.com/tag/minecraft-python-api/
">recipes
</a
>
1319 I
<a href=
"https://github.com/kbsriram/mcpiapi
">found
</a
> are only
1320 working with a standalone Minecraft server setup. Are there any
1321 options to use with the normal desktop version?
</p
>
1323 <p
>As usual, if you use Bitcoin and want to show your support of my
1324 activities, please send Bitcoin donations to my address
1325 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1330 <title>Time for an official MIME type for patches?
</title>
1331 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</link>
1332 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</guid>
1333 <pubDate>Thu,
1 Nov
2018 08:
15:
00 +
0100</pubDate>
1334 <description><p
>As part of my involvement in
1335 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core
">the Nikita
1336 archive API project
</a
>, I
've been importing a fairly large lump of
1337 emails into a test instance of the archive to see how well this would
1338 go. I picked a subset of
<a href=
"https://notmuchmail.org/
">my
1339 notmuch email database
</a
>, all public emails sent to me via
1340 @lists.debian.org, giving me a set of around
216 000 emails to import.
1341 In the process, I had a look at the various attachments included in
1342 these emails, to figure out what to do with attachments, and noticed
1343 that one of the most common attachment formats do not have
1344 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">an
1345 official MIME type
</a
> registered with IANA/IETF. The output from
1346 diff, ie the input for patch, is on the top
10 list of formats
1347 included in these emails. At the moment people seem to use either
1348 text/x-patch or text/x-diff, but neither is officially registered. It
1349 would be better if one official MIME type were registered and used
1350 everywhere.
</p
>
1352 <p
>To try to get one official MIME type for these files, I
've brought
1354 <a href=
"https://www.ietf.org/mailman/listinfo/media-types
">the
1355 media-types mailing list
</a
>. If you are interested in discussion
1356 which MIME type to use as the official for patch files, or involved in
1357 making software using a MIME type for patches, perhaps you would like
1358 to join the discussion?
</p
>
1360 <p
>As usual, if you use Bitcoin and want to show your support of my
1361 activities, please send Bitcoin donations to my address
1362 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1367 <title>Automatic Google Drive sync using grive in Debian
</title>
1368 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</link>
1369 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</guid>
1370 <pubDate>Thu,
4 Oct
2018 15:
20:
00 +
0200</pubDate>
1371 <description><p
>A few days, I rescued a Windows victim over to Debian. To try to
1372 rescue the remains, I helped set up automatic sync with Google Drive.
1373 I did not find any sensible Debian package handling this
1374 automatically, so I rebuild the grive2 source from
1375 <a href=
"http://www.webupd8.org/
">the Ubuntu UPD8 PPA
</a
> to do the
1376 task and added a autostart desktop entry and a small shell script to
1377 run in the background while the user is logged in to do the sync.
1378 Here is a sketch of the setup for future reference.
</p
>
1380 <p
>I first created
<tt
>~/googledrive
</tt
>, entered the directory and
1381 ran
'<tt
>grive -a
</tt
>' to authenticate the machine/user. Next, I
1382 created a autostart hook in
<tt
>~/.config/autostart/grive.desktop
</tt
>
1383 to start the sync when the user log in:
</p
>
1385 <p
><blockquote
><pre
>
1387 Name=Google drive autosync
1389 Exec=/home/user/bin/grive-sync
1390 </pre
></blockquote
></p
>
1392 <p
>Finally, I wrote the
<tt
>~/bin/grive-sync
</tt
> script to sync
1393 ~/googledrive/ with the files in Google Drive.
</p
>
1395 <p
><blockquote
><pre
>
1400 if [
"$syncpid
" ] ; then
1404 trap cleanup EXIT INT QUIT
1405 /usr/lib/grive/grive-sync.sh listen googledrive
2>&1 | sed
"s%^%$
0:%
" &
1408 if ! xhost
>/dev/null
2>&1 ; then
1409 echo
"no DISPLAY, exiting as the user probably logged out
"
1412 if [ ! -e /run/user/
1000/grive-sync.sh_googledrive ] ; then
1413 /usr/lib/grive/grive-sync.sh sync googledrive
1416 done
2>&1 | sed
"s%^%$
0:%
"
1417 </pre
></blockquote
></p
>
1419 <p
>Feel free to use the setup if you want. It can be assumed to be
1420 GNU GPL v2 licensed (or any later version, at your leisure), but I
1421 doubt this code is possible to claim copyright on.
</p
>
1423 <p
>As usual, if you use Bitcoin and want to show your support of my
1424 activities, please send Bitcoin donations to my address
1425 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1430 <title>Using the Kodi API to play Youtube videos
</title>
1431 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</link>
1432 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</guid>
1433 <pubDate>Sun,
2 Sep
2018 23:
40:
00 +
0200</pubDate>
1434 <description><p
>I continue to explore my Kodi installation, and today I wanted to
1435 tell it to play a youtube URL I received in a chat, without having to
1436 insert search terms using the on-screen keyboard. After searching the
1437 web for API access to the Youtube plugin and testing a bit, I managed
1438 to find a recipe that worked. If you got a kodi instance with its API
1439 available from http://kodihost/jsonrpc, you can try the following to
1440 have check out a nice cover band.
</p
>
1442 <p
><blockquote
><pre
>curl --silent --header
'Content-Type: application/json
' \
1443 --data-binary
'{
"id
":
1,
"jsonrpc
":
"2.0",
"method
":
"Player.Open
",
1444 "params
": {
"item
": {
"file
":
1445 "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg
" } } }
' \
1446 http://projector.local/jsonrpc
</pre
></blockquote
></p
>
1448 <p
>I
've extended kodi-stream program to take a video source as its
1449 first argument. It can now handle direct video links, youtube links
1450 and
'desktop
' to stream my desktop to Kodi. It is almost like a
1451 Chromecast. :)
</p
>
1453 <p
>As usual, if you use Bitcoin and want to show your support of my
1454 activities, please send Bitcoin donations to my address
1455 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1460 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
1461 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
1462 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
1463 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
1464 <description><p
>For a while now, I have looked for a sensible way to share images
1465 with my family using a self hosted solution, as it is unacceptable to
1466 place images from my personal life under the control of strangers
1467 working for data hoarders like Google or Dropbox. The last few days I
1468 have drafted an approach that might work out, and I would like to
1469 share it with you. I would like to publish images on a server under
1470 my control, and point some Internet connected display units using some
1471 free and open standard to the images I published. As my primary
1472 language is not limited to ASCII, I need to store metadata using
1473 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
1474 of reading a RSS feed with image references (aka using the
1475 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
1476 of such frames. In the end I gave up that approach.
</p
>
1478 <p
>Some months ago, I discovered that
1479 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
1480 read images from a RSS feed, and used it to set up a screen saver on
1481 my home info screen, showing images from the Daily images feed from
1482 NASA. This proved to work well. More recently I discovered that
1483 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
1484 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
1485 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
1486 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
1487 screen saver capable of reading a RSS feed with images and news. For
1488 fun, I used it this summer to test Kodi on my parents TV by hooking up
1489 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
1490 screen saver showing selected pictures from my selection.
</p
>
1492 <p
>Armed with motivation and a test photo frame, I set out to generate
1493 a RSS feed for the Kodi instance. I adjusted my
<a
1494 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
1495 /var/www/html/privatepictures/, wrote a small Perl script to extract
1496 title and description metadata from the photo files and generate the
1497 RSS file. I ended up using Perl instead of python, as the
1498 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
1499 tags I ended up using, while python3-exif did not. The relevant EXIF
1500 tags only support ASCII, so I had to find better alternatives. XMP
1501 seem to have the support I need.
</p
>
1503 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
1504 use tags that can be easily added/updated using normal free software
1505 photo managing software. I ended up using the tags set using this
1506 exiftool command, as these tags can also be set using digiKam:
</p
>
1508 <blockquote
><pre
>
1509 exiftool -headline=
'The RSS image title
' \
1510 -description=
'The RSS image description.
' \
1511 -subject+=for-family photo.jpeg
1512 </pre
></blockquote
>
1514 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
1515 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
1516 use the keyword/subject
'for-family
' to flag that the photo should be
1517 shared with my family. Images with this keyword set are located and
1518 copied into my Freedombox for the RSS generating script to find.
</p
>
1520 <p
>Are there better ways to do this? Get in touch if you have better
1521 suggestions.
</p
>
1523 <p
>As usual, if you use Bitcoin and want to show your support of my
1524 activities, please send Bitcoin donations to my address
1525 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1530 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
1531 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
1532 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
1533 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
1534 <description><p
>Last night, I wrote
1535 <a href=
"http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
1536 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
1537 During the day I received valuable feedback, and thanks to the
1538 suggestions I have been able to rewrite the recipe into a much simpler
1539 approach requiring no setup at all. It is a single script that take
1540 care of it all.
</p
>
1542 <p
>This new script uses GStreamer instead of VLC to capture the
1543 desktop and stream it to Kodi. This fixed the video quality issue I
1544 saw initially. It further removes the need to add a m3u file on the
1545 Kodi machine, as it instead connects to
1546 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
1547 Kodi
</a
> and simply ask Kodi to play from the stream created using
1548 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
1549 the script below, run it with the DNS name or IP address of the kodi
1550 server to stream to as the only argument, and watch your screen show
1551 up on the Kodi screen. Note, it depend on multicast on the local
1552 network, so if you need to stream outside the local network, the
1553 script must be modified. Also note, I have no idea if audio work, as
1554 I only care about the picture part.
</p
>
1556 <blockquote
><pre
>
1559 # Stream the Linux desktop view to Kodi. See
1560 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
1561 # for backgorund information.
1563 # Make sure the stream is stopped in Kodi and the gstreamer process is
1564 # killed if something go wrong (for example if curl is unable to find the
1565 # kodi server). Do the same when interrupting this script.
1569 params=
"$
3"
1570 curl --silent --header
'Content-Type: application/json
' \
1571 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
1572 "http://$host/jsonrpc
"
1575 if [ -n
"$kodihost
" ] ; then
1576 # Stop the playing when we end
1577 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
1578 jq .result[].playerid)
1579 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
1581 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
1582 kill
"$gstpid
"
1585 trap cleanup EXIT INT
1587 if [ -n
"$
1" ]; then
1598 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
1599 cut -d
" " -f2|head -
1)
1600 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
1601 videoconvert ! queue2 ! \
1602 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
1603 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
1604 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
1605 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
1606 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
1607 > /dev/null
2>&1 &
1610 # Give stream a second to get going
1613 # Ask kodi to start streaming using its JSON-RPC API
1614 kodicmd
"$kodihost
" Player.Open \
1615 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
1617 # wait for gst to end
1618 wait
"$gstpid
"
1619 </pre
></blockquote
>
1621 <p
>I hope you find the approach useful. I know I do.
</p
>
1623 <p
>As usual, if you use Bitcoin and want to show your support of my
1624 activities, please send Bitcoin donations to my address
1625 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1630 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
1631 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
1632 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
1633 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
1634 <description><p
>PS: See
1635 <ahref=
"http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
1636 followup post
</a
> for a even better approach.
</p
>
1638 <p
>A while back, I was asked by a friend how to stream the desktop to
1639 my projector connected to Kodi. I sadly had to admit that I had no
1640 idea, as it was a task I never had tried. Since then, I have been
1641 looking for a way to do so, preferable without much extra software to
1642 install on either side. Today I found a way that seem to kind of
1643 work. Not great, but it is a start.
</p
>
1645 <p
>I had a look at several approaches, for example
1646 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
1647 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
1648 local storage enough to store the stream locally. This is not going
1649 to work well for me, lacking enough free space, and it would
1650 impossible for my friend to get working.
</p
>
1652 <p
>Next, it occurred to me that perhaps I could use VLC to create a
1653 video stream that Kodi could play. Preferably using
1654 broadcast/multicast, to avoid having to change any setup on the Kodi
1655 side when starting such stream. Unfortunately, the only recipe I
1656 could find using multicast used the rtp protocol, and this protocol
1657 seem to not be supported by Kodi.
</p
>
1659 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
1660 have to specify the IP address of the streaming machine in both the
1661 sending command and the file on the Kodi server. But it is showing my
1662 desktop, and thus allow us to have a shared look on the big screen at
1663 the programs I work on.
</p
>
1665 <p
>I did not spend much time investigating codeces. I combined the
1666 rtp and rtsp recipes from
1667 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
1668 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
1669 this working on the desktop/streaming end.
</p
>
1671 <blockquote
><pre
>
1672 vlc screen:// --sout \
1673 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
1674 </pre
></blockquote
>
1676 <p
>I ssh-ed into my Kodi box and created a file like this with the
1677 same IP address:
</p
>
1679 <blockquote
><pre
>
1680 echo rtsp://
192.168.11.4:
8080/test.sdp \
1681 > /storage/videos/screenstream.m3u
1682 </pre
></blockquote
>
1684 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
1685 as I can tell the IP must be hardcoded for this to work. In other
1686 words, if someone elses machine is going to do the steaming, you have
1687 to update screenstream.m3u on the Kodi machine and adjust the vlc
1688 recipe. To get started, locate the file in Kodi and select the m3u
1689 file while the VLC stream is running. The desktop then show up in my
1690 big screen. :)
</p
>
1692 <p
>When using the same technique to stream a video file with audio,
1693 the audio quality is really bad. No idea if the problem is package
1694 loss or bad parameters for the transcode. I do not know VLC nor Kodi
1695 enough to tell.
</p
>
1697 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
1698 succestions and reminded me about an important step. The
"screen:
"
1699 input source is only available once the vlc-plugin-access-extra
1700 package is installed on Debian. Without it, you will see this error
1701 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
1702 for details.
" He further found that it is possible to drop some parts
1703 of the VLC command line to reduce the amount of hardcoded information.
1704 It is also useful to consider using cvlc to avoid having the VLC
1705 window in the desktop view. In sum, this give us this command line on
1708 <blockquote
><pre
>
1709 cvlc screen:// --sout \
1710 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
1711 </pre
></blockquote
>
1713 <p
>and this on the Kodi end
<p
>
1715 <blockquote
><pre
>
1716 echo rtsp://
192.168.11.4:
8080/ \
1717 > /storage/videos/screenstream.m3u
1718 </pre
></blockquote
>
1720 <p
>Still bad image quality, though. But I did discover that streaming
1721 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
1722 audio quality, so I guess the issue is in the input or transcoding
1723 parts, not the rtsp part. I
've tried to change the vb and ab
1724 parameters to use more bandwidth, but it did not make a
1725 difference.
</p
>
1727 <p
>I further received a suggestion from Einar Haraldseid to try using
1728 gstreamer instead of VLC, and this proved to work great! He also
1729 provided me with the trick to get Kodi to use a multicast stream as
1730 its source. By using this monstrous oneliner, I can stream my desktop
1731 with good video quality in reasonable framerate to the
239.255.0.1
1732 multicast address on port
1234:
1734 <blockquote
><pre
>
1735 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
1736 videoconvert ! queue2 ! \
1737 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
1738 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
1739 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
1740 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
1741 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
1742 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
1743 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
1744 </pre
></blockquote
>
1746 <p
>and this on the Kodi end
<p
>
1748 <blockquote
><pre
>
1749 echo udp://@
239.255.0.1:
1234 \
1750 > /storage/videos/screenstream.m3u
1751 </pre
></blockquote
>
1753 <p
>Note the trick to pick a valid pulseaudio source. It might not
1754 pick the one you need. This approach will of course lead to trouble
1755 if more than one source uses the same multicast port and address.
1756 Note the ttl-mc=
1 setting, which limit the multicast packages to the
1757 local network. If the value is increased, your screen will be
1758 broadcasted further, one network
"hop
" for each increase (read up on
1759 multicast to learn more. :)!
</p
>
1761 <p
>Having cracked how to get Kodi to receive multicast streams, I
1762 could use this VLC command to stream to the same multicast address.
1763 The image quality is way better than the rtsp approach, but gstreamer
1764 seem to be doing a better job.
</p
>
1766 <blockquote
><pre
>
1767 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
1768 </pre
></blockquote
>
1770 <p
>As usual, if you use Bitcoin and want to show your support of my
1771 activities, please send Bitcoin donations to my address
1772 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1777 <title>What is the most supported MIME type in Debian in
2018?
</title>
1778 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
1779 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
1780 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
1781 <description><p
>Five years ago,
1782 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
1783 measured what the most supported MIME type in Debian was
</a
>, by
1784 analysing the desktop files in all packages in the archive. Since
1785 then, the DEP-
11 AppStream system has been put into production, making
1786 the task a lot easier. This made me want to repeat the measurement,
1787 to see how much things changed. Here are the new numbers, for
1788 unstable only this time:
1790 <p
><strong
>Debian Unstable:
</strong
></p
>
1794 ----- -----------------------
1806 30 audio/x-vorbis+ogg
1807 29 image/x-portable-pixmap
1809 27 image/x-portable-bitmap
1811 26 application/x-ogg
1817 <p
>The list was created like this using a sid chroot:
"cat
1818 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
1819 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
1821 <p
>It is interesting to see how image formats have passed text/plain
1822 as the most announced supported MIME type. These days, thanks to the
1823 AppStream system, if you run into a file format you do not know, and
1824 want to figure out which packages support the format, you can find the
1825 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
1826 look up all packages announcing support for this format in their
1827 AppStream metadata (XML or .desktop file) using
"appstreamcli
1828 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
1829 me, want to know which packages support inode/directory, you can get a
1830 list like this:
</p
>
1832 <p
><blockquote
><pre
>
1833 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
1840 Package: doublecmd-common
1842 Package: enlightenment
1862 </pre
></blockquote
></p
>
1864 <p
>Using the same method, I can quickly discover that the Sketchup file
1865 format is not yet supported by any package in Debian:
</p
>
1867 <p
><blockquote
><pre
>
1868 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
1869 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
1871 </pre
></blockquote
></p
>
1873 <p
>Yesterday I used it to figure out which packages support the STL
3D
1876 <p
><blockquote
><pre
>
1877 % appstreamcli what-provides mimetype application/sla|grep Package
1882 </pre
></blockquote
></p
>
1884 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
1886 <p
>As usual, if you use Bitcoin and want to show your support of my
1887 activities, please send Bitcoin donations to my address
1888 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1893 <title>Debian APT upgrade without enough free space on the disk...
</title>
1894 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
1895 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
1896 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
1897 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
1898 for a while, and when I need to update it there is not enough free
1899 space on the disk for apt to do a normal
'apt upgrade
'. I normally
1900 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
1901 upgrade only some of the packages in one batch, until the amount of
1902 packages to download fall below the amount of free space available.
1903 Today, I had about
500 packages to upgrade, and after a while I got
1904 tired of trying to install chunks of packages manually. I concluded
1905 that I did not have the spare hours required to complete the task, and
1906 decided to see if I could automate it. I came up with this small
1907 script which I call
'apt-in-chunks
':
</p
>
1909 <p
><blockquote
><pre
>
1912 # Upgrade packages when the disk is too full to upgrade every
1913 # upgradable package in one lump. Fetching packages to upgrade using
1914 # apt, and then installing using dpkg, to avoid changing the package
1915 # flag for manual/automatic.
1920 if [
"$
1" ]; then
1921 grep -v
"$
1"
1927 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
1928 echo
"Upgrading $p
"
1930 apt install --download-only -y $p
1931 for f in /var/cache/apt/archives/*.deb; do
1932 if [ -e
"$f
" ]; then
1933 dpkg -i /var/cache/apt/archives/*.deb
1938 </pre
></blockquote
></p
>
1940 <p
>The script will extract the list of packages to upgrade, try to
1941 download the packages needed to upgrade one package, install the
1942 downloaded packages using dpkg. The idea is to upgrade packages
1943 without changing the APT mark for the package (ie the one recording of
1944 the package was manually requested or pulled in as a dependency). To
1945 use it, simply run it as root from the command line. If it fail, try
1946 'apt install -f
' to clean up the mess and run the script again. This
1947 might happen if the new packages conflict with one of the old
1948 packages. dpkg is unable to remove, while apt can do this.
</p
>
1950 <p
>It take one option, a package to ignore in the list of packages to
1951 upgrade. The option to ignore a package is there to be able to skip
1952 the packages that are simply too large to unpack. Today this was
1953 'ghc
', but I have run into other large packages causing similar
1954 problems earlier (like TeX).
</p
>
1956 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
1957 alternative ways to handle this. The
"unattended-upgrades
1958 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
1959 each package to upgrade, and then upgrade them in order, smallest set
1960 first. It might be a better option than my above mentioned script.
1961 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
1962 the need for using
"dpkg -i
" in the script above.
</p
>
1964 <p
>As usual, if you use Bitcoin and want to show your support of my
1965 activities, please send Bitcoin donations to my address
1966 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1971 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
1972 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
1973 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
1974 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
1975 <description><p
>A new version of the
1976 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
1977 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
1978 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
1979 useful. It was uploaded the last few days, and the last update will
1980 enter testing tomorrow. See the
1981 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
1982 notes
</a
> for the list of bug fixes and new features. Version
3.2
1983 was announced
6 days ago. We will try to get it into Debian as
1986 <p
>More information related to
3D printing is available on the
1987 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
1988 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
1989 in Debian.
</p
>
1991 <p
>As usual, if you use Bitcoin and want to show your support of my
1992 activities, please send Bitcoin donations to my address
1993 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1998 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
1999 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
2000 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
2001 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
2002 <description><p
>After several months of working and waiting, I am happy to report
2003 that the nice and user friendly
3D printer slicer software Cura just
2004 entered Debian Unstable. It consist of five packages,
2005 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
2006 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
2007 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
2008 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
2009 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
2010 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
2011 two, uranium and cura, entered Unstable yesterday. This should make
2012 it easier for Debian users to print on at least the Ultimaker class of
2013 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
2014 make life easier for at least me. :)
</p
>
2016 <p
>The work to make this happen was done by Gregor Riepl, and I was
2017 happy to assist him in sponsoring the packages. With the introduction
2018 of Cura, Debian is up to three
3D printer slicers at your service,
2019 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
2020 printer, give it a go. :)
</p
>
2022 <p
>The
3D printer software is maintained by the
3D printer Debian
2023 team, flocking together on the
2024 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
2025 mailing list and the
2026 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
2027 IRC channel.
</p
>
2029 <p
>The next step for Cura in Debian is to update the cura package to
2030 version
3.0.3 and then update the entire set of packages to version
2031 3.1.0 which showed up the last few days.
</p
>
2036 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
2037 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
2038 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
2039 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
2040 <description><p
>At my nearby maker space,
2041 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
2042 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
2043 on Windows and MacOS X than Linux, because the software involved had
2044 to be manually compiled and set up on Linux while premade packages
2045 worked out of the box on Windows and MacOS X. I found this annoying,
2046 as the software involved,
2047 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
2048 and should be trivial to get up and running on Linux if someone took
2049 the time to package it for the relevant distributions. I even found
2050 <a href=
"https://bugs.debian.org/
706656">a request for adding into
2051 Debian
</a
> from
2013, which had seem some activity over the years but
2052 never resulted in the software showing up in Debian. So a few days
2053 ago I offered my help to try to improve the situation.
</p
>
2055 <p
>Now I am very happy to see that all the packages required by a
2056 working Cura in Debian are uploaded into Debian and waiting in the NEW
2057 queue for the ftpmasters to have a look. You can track the progress
2059 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
2060 status page for the
3D printer team
</a
>.
</p
>
2062 <p
>The uploaded packages are a bit behind upstream, and was uploaded
2063 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
2064 queue
</a
> while we work up updating the packages to the latest
2065 upstream version.
</p
>
2067 <p
>On a related note, two competitors for Cura, which I found harder
2068 to use and was unable to configure correctly for Ultimaker
2+ in the
2069 short time I spent on it, are already in Debian. If you are looking
2070 for
3D printer
"slicers
" and want something already available in
2072 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
2073 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
2074 The latter is a fork of the former.
</p
>
2076 <p
>As usual, if you use Bitcoin and want to show your support of my
2077 activities, please send Bitcoin donations to my address
2078 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2083 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
2084 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
2085 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
2086 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
2087 <description><p
>Every mobile phone announce its existence over radio to the nearby
2088 mobile cell towers. And this radio chatter is available for anyone
2089 with a radio receiver capable of receiving them. Details about the
2090 mobile phones with very good accuracy is of course collected by the
2091 phone companies, but this is not the topic of this blog post. The
2092 mobile phone radio chatter make it possible to figure out when a cell
2093 phone is nearby, as it include the SIM card ID (IMSI). By paying
2094 attention over time, one can see when a phone arrive and when it leave
2095 an area. I believe it would be nice to make this information more
2096 available to the general public, to make more people aware of how
2097 their phones are announcing their whereabouts to anyone that care to
2100 <p
>I am very happy to report that we managed to get something
2101 visualizing this information up and running for
2102 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
2103 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
2104 library. The solution is based on the
2105 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
2106 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
2107 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
2108 Sone from the Computer Science department of the University of
2109 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
2110 IMSIs) as dots in a web browser graph, with lines to the dot
2111 representing mobile base station it is talking to. It was working in
2112 the lab yesterday, and was moved into place this morning.
</p
>
2114 <p
>We set up a fairly powerful desktop machine using Debian
2115 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
2116 connected and visualize the visible cell phone towers using an
2117 <a href=
"https://github.com/marlow925/hopglass
">English version of
2118 Hopglass
</a
>. A fairly powerfull machine is needed as the
2119 grgsm_livemon_headless processes from
2120 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
2121 the radio signal to data packages is quite CPU intensive.
</p
>
2123 <p
>The frequencies to listen to, are identified using a slightly
2124 patched scan-and-livemon (to set the --args values for each receiver),
2125 and the Hopglass data is generated using the
2126 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
2127 in my meshviewer-output branch
</a
>. For some reason we could not get
2128 more than four SDRs working. There is also a geographical map trying
2129 to show the location of the base stations, but I believe their
2130 coordinates are hardcoded to some random location in Germany, I
2131 believe. The code should be replaced with code to look up location in
2132 a text file, a sqlite database or one of the online databases
2134 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
2135 issue for the topic
</a
>.
2137 <p
>If this sound interesting, visit the stand at the festival!
</p
>
2142 <title>Easier recipe to observe the cell phones around you
</title>
2143 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
2144 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
2145 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
2146 <description><p
>A little more than a month ago I wrote
2147 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
2148 to observe the SIM card ID (aka IMSI number) of mobile phones talking
2149 to nearby mobile phone base stations using Debian GNU/Linux and a
2150 cheap USB software defined radio
</a
>, and thus being able to pinpoint
2151 the location of people and equipment (like cars and trains) with an
2152 accuracy of a few kilometer. Since then we have worked to make the
2153 procedure even simpler, and it is now possible to do this without any
2154 manual frequency tuning and without building your own packages.
</p
>
2156 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
2157 package is now included in Debian testing and unstable, and the
2158 IMSI-catcher code no longer require root access to fetch and decode
2159 the GSM data collected using gr-gsm.
</p
>
2161 <p
>Here is an updated recipe, using packages built by Debian and a git
2162 clone of two python scripts:
</p
>
2166 <li
>Start with a Debian machine running the Buster version (aka
2167 testing).
</li
>
2169 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
2170 python-scapy
</tt
>' as root to install required packages.
</li
>
2172 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
2173 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
2175 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
2177 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
2178 scan-and-livemon
</tt
>' to locate the frequency of nearby base
2179 stations and start listening for GSM packages on one of them.
</li
>
2181 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
2182 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
2186 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
2187 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
2188 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
2189 work with RTL
8232 and other similar USB radio receivers you can get
2191 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
2192 from ebay
</a
>), so for now the solution is to scan using the RTL radio
2193 and only use HackRF for fetching GSM data.
</p
>
2195 <p
>As far as I can tell, a cell phone only show up on one of the
2196 frequencies at the time, so if you are going to track and count every
2197 cell phone around you, you need to listen to all the frequencies used.
2198 To listen to several frequencies, use the --numrecv argument to
2199 scan-and-livemon to use several receivers. Further, I am not sure if
2200 phones using
3G or
4G will show as talking GSM to base stations, so
2201 this approach might not see all phones around you. I typically see
2202 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
2204 <p
>I
've tried to run the scanner on a
2205 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
2206 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
2207 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
2208 stdout, I am told there it is caused by a buffer overflow between the
2209 radio and GNU Radio, caused by the program being unable to read the
2210 GSM data fast enough. If you see a stream of
'O
's from the terminal
2211 where you started scan-and-livemon, you need a give the process more
2212 CPU power. Perhaps someone are able to optimize the code to a point
2213 where it become possible to set up RPi3 based GSM sniffers? I tried
2214 using Raspbian instead of Debian, but there seem to be something wrong
2215 with GNU Radio on raspbian, causing glibc to abort().
</p
>
2220 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
2221 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
2222 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
2223 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
2224 <description><p
>On friday, I came across an interesting article in the Norwegian
2225 web based ICT news magazine digi.no on
2226 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
2227 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
2228 DVB-T software defined radios. The article refered to instructions
2229 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
2230 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
2232 <p
>The instructions said to use Ubuntu, install pip using apt (to
2233 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2234 and the ask pybombs to fetch and build everything you need from
2235 scratch. I wanted to see if I could do the same on the most recent
2236 Debian packages, but this did not work because pybombs tried to build
2237 stuff that no longer build with the most recent openssl library or
2238 some other version skew problem. While trying to get this recipe
2239 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
2240 and the only piece of software dependency missing in Debian was the
2241 gr-gsm package. I also found out that the lead upstream developer of
2242 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2243 Debian packages provided in an Ubuntu PPA repository. All I needed to
2244 do was to dget the Debian source package and built it.
</p
>
2246 <p
>The IMSI collector is a python script listening for packages on the
2247 loopback network device and printing to the terminal some specific GSM
2248 packages with IMSI numbers in them. The code is fairly short and easy
2249 to understand. The reason this work is because gr-gsm include a tool
2250 to read GSM data from a software defined radio like a DVB-T USB stick
2251 and other software defined radios, decode them and inject them into a
2252 network device on your Linux machine (using the loopback device by
2253 default). This proved to work just fine, and I
've been testing the
2254 collector for a few days now.
</p
>
2256 <p
>The updated and simpler recipe is thus to
</p
>
2260 <li
>start with a Debian machine running Stretch or newer,
</li
>
2262 <li
>build and install the gr-gsm package available from
2263 <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
>
2265 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
2267 <li
>run grgsm_livemon and adjust the frequency until the terminal
2268 where it was started is filled with a stream of text (meaning you
2269 found a GSM station).
</li
>
2271 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
2275 <p
>To make it even easier in the future to get this sniffer up and
2276 running, I decided to package
2277 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
2278 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
2279 #
871055</a
>), and the package was uploaded into the NEW queue today.
2280 Luckily the gnuradio maintainer has promised to help me, as I do not
2281 know much about gnuradio stuff yet.
</p
>
2283 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
2284 commercial tools like
2285 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
2286 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
2287 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
2288 Stingray
</a
>, but I hope the existance of cheap alternatives can make
2289 more people realise how their whereabouts when carrying a cell phone
2290 is easily tracked. Seeing the data flow on the screen, realizing that
2291 I live close to a police station and knowing that the police is also
2292 wearing cell phones, I wonder how hard it would be for criminals to
2293 track the position of the police officers to discover when there are
2294 police near by, or for foreign military forces to track the location
2295 of the Norwegian military forces, or for anyone to track the location
2296 of government officials...
</p
>
2298 <p
>It is worth noting that the data reported by the IMSI-catcher
2299 script mentioned above is only a fraction of the data broadcasted on
2300 the GSM network. It will only collect one frequency at the time,
2301 while a typical phone will be using several frequencies, and not all
2302 phones will be using the frequencies tracked by the grgsm_livemod
2303 program. Also, there is a lot of radio chatter being ignored by the
2304 simple_IMSI-catcher script, which would be collected by extending the
2305 parser code. I wonder if gr-gsm can be set up to listen to more than
2306 one frequency?
</p
>
2311 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
2312 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
2313 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
2314 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
2315 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
2317 <p
>I finally received a copy of the Norwegian Bokmål edition of
2318 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
2319 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
2320 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2321 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
2322 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
2323 price. The book is also available for download in electronic form as
2324 PDF, EPUB and Mobipocket, as can be
2325 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
2326 as a web page
</a
>.
</p
>
2328 <p
>This is the second book I publish (the first was the book
2329 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
2331 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
2332 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
2334 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
2335 Bokmål
</a
>), and I am very excited to finally wrap up this
2337 "<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
2338 for Debian-administratoren
</a
>" will be well received.
</p
>
2343 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
2344 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
2345 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
2346 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
2347 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
2348 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
2349 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2350 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2351 på om den fri oversetterløsningen
2352 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
2353 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
2355 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
2358 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2359 rolle og muligheter til å håndtere internasjonale utfordringer, som
2360 for eksempel flykningekrisen.
</p
>
2362 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2363 på temaet:
</p
>
2365 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
2366 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
2371 <p
>Dette oversetter Apertium slik:
</p
>
2374 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2375 andre aktørar og høve til å handtera internasjonale utfordringar, som
2376 til dømes *flykningekrisen.
</p
>
2378 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
2382 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
2383 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
2388 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
2389 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2390 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2391 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
2392 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
2393 det er kanskje flisespikking. Det understreker vel bare at det alltid
2394 trengs korrekturlesning etter automatisk oversettelse.
</p
>
2399 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
2400 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
2401 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
2402 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
2403 <description><p
>Over the years, administrating thousand of NFS mounting linux
2404 computers at the time, I often needed a way to detect if the machine
2405 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
2406 file or directory affected by the hang, the process (and possibly the
2407 shell) will hang too. So you want to be able to detect this without
2408 risking the detection process getting stuck too. It has not been
2409 obvious how to do this. When the hang has lasted a while, it is
2410 possible to find messages like these in dmesg:
</p
>
2412 <p
><blockquote
>
2413 nfs: server nfsserver not responding, still trying
2414 <br
>nfs: server nfsserver OK
2415 </blockquote
></p
>
2417 <p
>It is hard to know if the hang is still going on, and it is hard to
2418 be sure looking in dmesg is going to work. If there are lots of other
2419 messages in dmesg the lines might have rotated out of site before they
2420 are noticed.
</p
>
2422 <p
>While reading through the nfs client implementation in linux kernel
2423 code, I came across some statistics that seem to give a way to detect
2424 it. The om_timeouts sunrpc value in the kernel will increase every
2425 time the above log entry is inserted into dmesg. And after digging a
2426 bit further, I discovered that this value show up in
2427 /proc/self/mountstats on Linux.
</p
>
2429 <p
>The mountstats content seem to be shared between files using the
2430 same file system context, so it is enough to check one of the
2431 mountstats files to get the state of the mount point for the machine.
2432 I assume this will not show lazy umounted NFS points, nor NFS mount
2433 points in a different process context (ie with a different filesystem
2434 view), but that does not worry me.
</p
>
2436 <p
>The content for a NFS mount point look similar to this:
</p
>
2438 <p
><blockquote
><pre
>
2440 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2441 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
2442 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
2444 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
2445 sec: flavor=
1,pseudoflavor=
1
2446 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
2447 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2448 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
2449 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
2451 NULL:
0 0 0 0 0 0 0 0
2452 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
2453 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
2454 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
2455 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
2456 READLINK:
125 125 0 20472 18620 0 1112 1118
2457 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
2458 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
2459 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
2460 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
2461 SYMLINK:
903 903 0 233428 245488 6 5865 5917
2462 MKNOD:
80 80 0 20148 21760 0 299 304
2463 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
2464 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
2465 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
2466 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
2467 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
2468 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
2469 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
2470 FSINFO:
2 2 0 232 328 0 1 1
2471 PATHCONF:
1 1 0 116 140 0 0 0
2472 COMMIT:
0 0 0 0 0 0 0 0
2474 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
2476 </pre
></blockquote
></p
>
2478 <p
>The key number to look at is the third number in the per-op list.
2479 It is the number of NFS timeouts experiences per file system
2480 operation. Here
22 write timeouts and
5 access timeouts. If these
2481 numbers are increasing, I believe the machine is experiencing NFS
2482 hang. Unfortunately the timeout value do not start to increase right
2483 away. The NFS operations need to time out first, and this can take a
2484 while. The exact timeout value depend on the setup. For example the
2485 defaults for TCP and UDP mount points are quite different, and the
2486 timeout value is affected by the soft, hard, timeo and retrans NFS
2487 mount options.
</p
>
2489 <p
>The only way I have been able to get working on Debian and RedHat
2490 Enterprise Linux for getting the timeout count is to peek in /proc/.
2492 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
2493 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
2494 command can be used to get these timeout values. But this do not work
2495 on Linux, as far as I can tell. I
2496 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
2497 but have not seen any replies yet.
</p
>
2499 <p
>Is there a better way to figure out if a Linux NFS client is
2500 experiencing NFS hangs? Is there a way to detect which processes are
2501 affected? Is there a way to get the NFS mount going quickly once the
2502 network problem causing the NFS hang has been cleared? I would very
2503 much welcome some clues, as we regularly run into NFS hangs.
</p
>
2508 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
2509 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
2510 <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>
2511 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
2512 <description><p
>For almost a year now, we have been working on making a Norwegian
2513 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
2514 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
2515 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
2516 we are working on the proof reading to ensure consistent language and
2517 use of correct computer science terms. The plan is to make the book
2518 available on paper, as well as in electronic form. For that to
2519 happen, the proof reading must be completed and all the figures need
2520 to be translated. If you want to help out, get in touch.
</p
>
2522 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
2524 fresh PDF edition
</a
> in A4 format (the final book will have smaller
2525 pages) of the book created every morning is available for
2526 proofreading. If you find any errors, please
2527 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
2528 Weblate and correct the error
</a
>. The
2529 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
2530 of the translation including figures
</a
> is a useful source for those
2531 provide Norwegian bokmål screen shots and figures.
</p
>
2536 <title>Unlimited randomness with the ChaosKey?
</title>
2537 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
2538 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
2539 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
2540 <description><p
>A few days ago I ordered a small batch of
2541 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
2542 USB dongle for generating entropy created by Bdale Garbee and Keith
2543 Packard. Yesterday it arrived, and I am very happy to report that it
2544 work great! According to its designers, to get it to work out of the
2545 box, you need the Linux kernel version
4.1 or later. I tested on a
2546 Debian Stretch machine (kernel version
4.9), and there it worked just
2547 fine, increasing the available entropy very quickly. I wrote a small
2548 test oneliner to test. It first print the current entropy level,
2549 drain /dev/random, and then print the entropy level for five seconds.
2550 Here is the situation without the ChaosKey inserted:
</p
>
2552 <blockquote
><pre
>
2553 % cat /proc/sys/kernel/random/entropy_avail; \
2554 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
2555 for n in $(seq
1 5); do \
2556 cat /proc/sys/kernel/random/entropy_avail; \
2562 28 byte kopiert,
0,
000264565 s,
106 kB/s
2569 </pre
></blockquote
>
2571 <p
>The entropy level increases by
3-
4 every second. In such case any
2572 application requiring random bits (like a HTTPS enabled web server)
2573 will halt and wait for more entrpy. And here is the situation with
2574 the ChaosKey inserted:
</p
>
2576 <blockquote
><pre
>
2577 % cat /proc/sys/kernel/random/entropy_avail; \
2578 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
2579 for n in $(seq
1 5); do \
2580 cat /proc/sys/kernel/random/entropy_avail; \
2586 104 byte kopiert,
0,
000487647 s,
213 kB/s
2593 </pre
></blockquote
>
2595 <p
>Quite the difference. :) I bought a few more than I need, in case
2596 someone want to buy one here in Norway. :)
</p
>
2598 <p
>Update: The dongle was presented at Debconf last year. You might
2599 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
2600 recording illuminating
</a
>. It explains exactly what the source of
2601 randomness is, if you are unable to spot it from the schema drawing
2602 available from the ChaosKey web site linked at the start of this blog
2608 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
2609 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
2610 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
2611 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
2612 <description><p
>Did you ever wonder where the web trafic really flow to reach the
2613 web servers, and who own the network equipment it is flowing through?
2614 It is possible to get a glimpse of this from using traceroute, but it
2615 is hard to find all the details. Many years ago, I wrote a system to
2616 map the Norwegian Internet (trying to figure out if our plans for a
2617 network game service would get low enough latency, and who we needed
2618 to talk to about setting up game servers close to the users. Back
2619 then I used traceroute output from many locations (I asked my friends
2620 to run a script and send me their traceroute output) to create the
2621 graph and the map. The output from traceroute typically look like
2624 <p
><pre
>
2625 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
2626 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
2627 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
2628 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
2629 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
2630 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
2631 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
2632 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
2636 </pre
></p
>
2638 <p
>This show the DNS names and IP addresses of (at least some of the)
2639 network equipment involved in getting the data traffic from me to the
2640 www.stortinget.no server, and how long it took in milliseconds for a
2641 package to reach the equipment and return to me. Three packages are
2642 sent, and some times the packages do not follow the same path. This
2643 is shown for hop
5, where three different IP addresses replied to the
2644 traceroute request.
</p
>
2646 <p
>There are many ways to measure trace routes. Other good traceroute
2647 implementations I use are traceroute (using ICMP packages) mtr (can do
2648 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
2649 traceroute and a lot of other capabilities). All of them are easily
2650 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
2652 <p
>This time around, I wanted to know the geographic location of
2653 different route points, to visualize how visiting a web page spread
2654 information about the visit to a lot of servers around the globe. The
2655 background is that a web site today often will ask the browser to get
2656 from many servers the parts (for example HTML, JSON, fonts,
2657 JavaScript, CSS, video) required to display the content. This will
2658 leak information about the visit to those controlling these servers
2659 and anyone able to peek at the data traffic passing by (like your ISP,
2660 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
2662 <p
>Lets pick an example, the Norwegian parliament web site
2663 www.stortinget.no. It is read daily by all members of parliament and
2664 their staff, as well as political journalists, activits and many other
2665 citizens of Norway. A visit to the www.stortinget.no web site will
2666 ask your browser to contact
8 other servers: ajax.googleapis.com,
2667 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
2668 stats.g.doubleclick.net, www.google-analytics.com,
2669 www.googletagmanager.com and www.netigate.se. I extracted this by
2670 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
2671 Stortinget web page and tell me all the URLs PhantomJS downloaded to
2672 render the page (in HAR format using
2673 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
2674 netsniff example
</a
>. I am very grateful to Gorm for showing me how
2675 to do this). My goal is to visualize network traces to all IP
2676 addresses behind these DNS names, do show where visitors personal
2677 information is spread when visiting the page.
</p
>
2679 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
2680 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
>
2682 <p
>When I had a look around for options, I could not find any good
2683 free software tools to do this, and decided I needed my own traceroute
2684 wrapper outputting KML based on locations looked up using GeoIP. KML
2685 is easy to work with and easy to generate, and understood by several
2686 of the GIS tools I have available. I got good help from by NUUG
2687 colleague Anders Einar with this, and the result can be seen in
2688 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
2689 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
2690 free GeoIP databases I could find (and the for-pay databases my
2691 friends had access to) is not up to the task. The IP addresses of
2692 central Internet infrastructure would typically be placed near the
2693 controlling companies main office, and not where the router is really
2694 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
2695 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
2697 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
2698 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
>
2700 <p
>I also had a look at the visual traceroute graph created by
2701 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
2702 showing IP network ownership (aka AS owner) for the IP address in
2704 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
2705 graph display a lot of useful information about the traceroute in SVG
2706 format
</a
>, and give a good indication on who control the network
2707 equipment involved, but it do not include geolocation. This graph
2708 make it possible to see the information is made available at least for
2709 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
2710 3 Communications and NetDNA.
</p
>
2712 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
2713 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
>
2715 <p
>In the process, I came across the
2716 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
2717 Salim Gasmi. Its methology of combining guesses based on DNS names,
2718 various location databases and finally use latecy times to rule out
2719 candidate locations seemed to do a very good job of guessing correct
2720 geolocation. But it could only do one trace at the time, did not have
2721 a sensor in Norway and did not make the geolocations easily available
2722 for postprocessing. So I contacted the developer and asked if he
2723 would be willing to share the code (he refused until he had time to
2724 clean it up), but he was interested in providing the geolocations in a
2725 machine readable format, and willing to set up a sensor in Norway. So
2726 since yesterday, it is possible to run traces from Norway in this
2727 service thanks to a sensor node set up by
2728 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
2729 trace in KML format for further processing.
</p
>
2731 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
2732 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
>
2734 <p
>Here we can see a lot of trafic passes Sweden on its way to
2735 Denmark, Germany, Holland and Ireland. Plenty of places where the
2736 Snowden confirmations verified the traffic is read by various actors
2737 without your best interest as their top priority.
</p
>
2739 <p
>Combining KML files is trivial using a text editor, so I could loop
2740 over all the hosts behind the urls imported by www.stortinget.no and
2741 ask for the KML file from GeoTraceroute, and create a combined KML
2742 file with all the traces (unfortunately only one of the IP addresses
2743 behind the DNS name is traced this time. To get them all, one would
2744 have to request traces using IP number instead of DNS names from
2745 GeoTraceroute). That might be the next step in this project.
</p
>
2747 <p
>Armed with these tools, I find it a lot easier to figure out where
2748 the IP traffic moves and who control the boxes involved in moving it.
2749 And every time the link crosses for example the Swedish border, we can
2750 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
2751 Britain and NSA in USA and cables around the globe. (Hm, what should
2752 we tell them? :) Keep that in mind if you ever send anything
2753 unencrypted over the Internet.
</p
>
2755 <p
>PS: KML files are drawn using
2756 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
2757 Rublev
<a/
>, as it was less cluttered than the local Linux application
2758 Marble. There are heaps of other options too.
</p
>
2760 <p
>As usual, if you use Bitcoin and want to show your support of my
2761 activities, please send Bitcoin donations to my address
2762 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2767 <title>Appstream just learned how to map hardware to packages too!
</title>
2768 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
2769 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
2770 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
2771 <description><p
>I received a very nice Christmas present today. As my regular
2772 readers probably know, I have been working on the
2773 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
2774 system
</a
> for many years. The goal of the Isenkram system is to make
2775 it easier for users to figure out what to install to get a given piece
2776 of hardware to work in Debian, and a key part of this system is a way
2777 to map hardware to packages. Isenkram have its own mapping database,
2778 and also uses data provided by each package using the AppStream
2779 metadata format. And today,
2780 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
2781 Debian learned to look up hardware the same way Isenkram is doing it,
2782 ie using fnmatch():
</p
>
2784 <p
><pre
>
2785 % appstreamcli what-provides modalias \
2786 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2787 Identifier: pymissile [generic]
2789 Summary: Control original Striker USB Missile Launcher
2791 % appstreamcli what-provides modalias usb:v0694p0002d0000
2792 Identifier: libnxt [generic]
2794 Summary: utility library for talking to the LEGO Mindstorms NXT brick
2797 Identifier: t2n [generic]
2799 Summary: Simple command-line tool for Lego NXT
2802 Identifier: python-nxt [generic]
2804 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
2807 Identifier: nbc [generic]
2809 Summary: C compiler for LEGO Mindstorms NXT bricks
2812 </pre
></p
>
2814 <p
>A similar query can be done using the combined AppStream and
2815 Isenkram databases using the isenkram-lookup tool:
</p
>
2817 <p
><pre
>
2818 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2820 % isenkram-lookup usb:v0694p0002d0000
2826 </pre
></p
>
2828 <p
>You can find modalias values relevant for your machine using
2829 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
2831 <p
>If you want to make this system a success and help Debian users
2832 make the most of the hardware they have, please
2833 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
2834 AppStream metadata for your package following the guidelines
</a
>
2835 documented in the wiki. So far only
11 packages provide such
2836 information, among the several hundred hardware specific packages in
2837 Debian. The Isenkram database on the other hand contain
101 packages,
2838 mostly related to USB dongles. Most of the packages with hardware
2839 mapping in AppStream are LEGO Mindstorms related, because I have, as
2840 part of my involvement in
2841 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
2842 team
</a
> given priority to making sure LEGO users get proposed the
2843 complete set of packages in Debian for that particular hardware. The
2844 team also got a nice Christmas present today. The
2845 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
2846 package
</a
> made it into Debian. With this package in place, it is
2847 now possible to use the LEGO Mindstorms NXT unit with only free
2848 software, as the nxt-firmware package contain the source and firmware
2849 binaries for the NXT brick.
</p
>
2851 <p
>As usual, if you use Bitcoin and want to show your support of my
2852 activities, please send Bitcoin donations to my address
2853 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2858 <title>Isenkram updated with a lot more hardware-package mappings
</title>
2859 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
2860 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
2861 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
2862 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
2863 system
</a
> I wrote two years ago to make it easier in Debian to find
2864 and install packages to get your hardware dongles to work, is still
2865 going strong. It is a system to look up the hardware present on or
2866 connected to the current system, and map the hardware to Debian
2867 packages. It can either be done using the tools in isenkram-cli or
2868 using the user space daemon in the isenkram package. The latter will
2869 notify you, when inserting new hardware, about what packages to
2870 install to get the dongle working. It will even provide a button to
2871 click on to ask packagekit to install the packages.
</p
>
2873 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
2875 <p
><pre
>
2892 </pre
></p
>
2894 <p
>It can also list the firware package providing firmware requested
2895 by the load kernel modules, which in my case is an empty list because
2896 I have all the firmware my machine need:
2898 <p
><pre
>
2899 % /usr/sbin/isenkram-autoinstall-firmware -l
2900 info: did not find any firmware files requested by loaded kernel modules. exiting
2902 </pre
></p
>
2904 <p
>The last few days I had a look at several of the around
250
2905 packages in Debian with udev rules. These seem like good candidates
2906 to install when a given hardware dongle is inserted, and I found
2907 several that should be proposed by isenkram. I have not had time to
2908 check all of them, but am happy to report that now there are
97
2909 packages packages mapped to hardware by Isenkram.
11 of these
2910 packages provide hardware mapping using AppStream, while the rest are
2911 listed in the modaliases file provided in isenkram.
</p
>
2913 <p
>These are the packages with hardware mappings at the moment. The
2914 <strong
>marked packages
</strong
> are also announcing their hardware
2915 support using AppStream, for everyone to use:
</p
>
2917 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
2918 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
2919 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
2920 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
2921 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
2922 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
2923 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
2924 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
2925 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
2926 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
2927 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
2928 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
2929 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
2930 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
2931 pcscd, pidgin-blinklight, printer-driver-splix,
2932 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
2933 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
2934 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
2935 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
2936 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
2937 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
2938 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
2939 xserver-xorg-video-vmware, yubikey-personalization and
2940 zd1211-firmware
</p
>
2942 <p
>If you know of other packages, please let me know with a wishlist
2943 bug report against the isenkram-cli package, and ask the package
2945 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
2946 metadata according to the guidelines
</a
> to provide the information
2947 for everyone. In time, I hope to get rid of the isenkram specific
2948 hardware mapping and depend exclusively on AppStream.
</p
>
2950 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
2951 much hardware, and suggest that the package with with any ethernet
2952 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
2953 the details. I hope the maintainer find time to address it soon. In
2954 the mean time I provide an override in isenkram.
</p
>
2959 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
2960 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
2961 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
2962 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
2963 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
2965 <p
>In my early years, I played
2966 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
2967 Elite
</a
> on my PC. I spent many months trading and fighting in
2968 space, and reached the
'elite
' fighting status before I moved on. The
2969 original Elite game was available on Commodore
64 and the IBM PC
2970 edition I played had a
64 KB executable. I am still impressed today
2971 that the authors managed to squeeze both a
3D engine and details about
2972 more than
2000 planet systems across
7 galaxies into a binary so
2975 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
2976 software game Oolite inspired by Elite
</a
> for a while, but did not
2977 really have time to test it properly until a few days ago. It was
2978 great to discover that my old knowledge about trading routes were
2979 still valid. But my fighting and flying abilities were gone, so I had
2980 to retrain to be able to dock on a space station. And I am still not
2981 able to make much resistance when I am attacked by pirates, so I
2982 bougth and mounted the most powerful laser in the rear to be able to
2983 put up at least some resistance while fleeing for my life. :)
</p
>
2985 <p
>When playing Elite in the late eighties, I had to discover
2986 everything on my own, and I had long lists of prices seen on different
2987 planets to be able to decide where to trade what. This time I had the
2989 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
2990 where information about each planet is easily available with common
2991 price ranges and suggested trading routes. This improved my ability
2992 to earn money and I have been able to earn enough to buy a lot of
2993 useful equipent in a few days. I believe I originally played for
2994 months before I could get a docking computer, while now I could get it
2995 after less then a week.
</p
>
2997 <p
>If you like science fiction and dreamed of a life as a vagabond in
2998 space, you should try out Oolite. It is available for Linux, MacOSX
2999 and Windows, and is included in Debian and derivatives since
2011.
</p
>
3001 <p
>As usual, if you use Bitcoin and want to show your support of my
3002 activities, please send Bitcoin donations to my address
3003 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3008 <title>Quicker Debian installations using eatmydata
</title>
3009 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
3010 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
3011 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
3012 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
3013 installation system, observing how using
3014 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
3015 could speed up the installation
</a
> quite a bit. My testing measured
3016 speedup around
20-
40 percent for Debian Edu, where we install around
3017 1000 packages from within the installer. The eatmydata package
3018 provide a way to disable/delay file system flushing. This is a bit
3019 risky in the general case, as files that should be stored on disk will
3020 stay only in memory a bit longer than expected, causing problems if a
3021 machine crashes at an inconvenient time. But for an installation, if
3022 the machine crashes during installation the process is normally
3023 restarted, and avoiding disk operations as much as possible to speed
3024 up the process make perfect sense.
3026 <p
>I added code in the Debian Edu specific installation code to enable
3027 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
3028 but did not have time to push it any further. But a few months ago I
3029 picked it up again and worked with the libeatmydata package maintainer
3030 Mattia Rizzolo to make it easier for everyone to get this installation
3031 speedup in Debian. Thanks to our cooperation There is now an
3032 eatmydata-udeb package in Debian testing and unstable, and simply
3033 enabling/installing it in debian-installer (d-i) is enough to get the
3034 quicker installations. It can be enabled using preseeding. The
3035 following untested kernel argument should do the trick:
</p
>
3037 <blockquote
><pre
>
3038 preseed/early_command=
"anna-install eatmydata-udeb
"
3039 </pre
></blockquote
>
3041 <p
>This should ask d-i to install the package inside the d-i
3042 environment early in the installation sequence. Having it installed
3043 in d-i in turn will make sure the relevant scripts are called just
3044 after debootstrap filled /target/ with the freshly installed Debian
3045 system to configure apt to run dpkg with eatmydata. This is enough to
3046 speed up the installation process. There is a proposal to
3047 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
3048 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
3049 tested its impact.
</p
>
3055 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
3056 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
3057 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
3058 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
3059 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
3060 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
3061 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
3062 elever over det ganske land skal levere inn hvert år. Det mange ikke
3063 vet er at selv om de kommersielle alternativene
3064 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
3065 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
3066 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
3067 utmerket fri programvarealternativ som kan. Oversetterverktøyet
3068 Apertium har støtte for en rekke språkkombinasjoner, og takket være
3069 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
3070 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
3071 nynorsk, og få den automatoversatt til det andre skriftspråket.
3072 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
3073 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
3074 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
3075 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
3076 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
3077 teksten din i webskjemaet der.
3079 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
3080 teknologien kan du enten installere pakken
3081 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
3082 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
3083 api.apertium.org. Se
3084 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
3085 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
3086 denne teksten som ble skrevet på bokmål over maskinoversatt til
3091 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
3092 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
3093 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
3094 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
3095 veit er at sjølv om dei kommersielle alternativa
3096 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
3097 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
3098 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
3099 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
3100 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
3101 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
3102 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
3103 nynorsk, og få den *automatoversatt til det andre skriftspråket.
3104 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
3105 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
3106 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
3107 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
3108 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
3109 teksta di i *webskjemaet der.
3111 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
3112 teknologien kan du anten installera pakken
3113 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
3114 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
3115 *api.*apertium.org. Sjå
3116 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
3117 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
3118 for denne teksta som vart skreva på bokmål over *maskinoversatt til
3124 <title>Coz profiler for multi-threaded software is now in Debian
</title>
3125 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
3126 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
3127 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
3128 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
3129 profiler able to run benchmarking experiments on the instrumented
3130 multi-threaded program, finally
3131 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
3132 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
3134 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
3135 blogged about the coz tool
</a
> in August working with upstream to make
3136 it suitable for Debian. There are still issues with clang
3137 compatibility, inline assembly only working x86 and minimized
3138 JavaScript libraries.
</p
>
3140 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
3142 <p
><blockquote
>
3143 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
3144 </blockquote
></p
>
3146 <p
>This will produce a profile.coz file in the current working
3147 directory with the profiling information. This is then given to a
3148 JavaScript application provided in the package and available from
3149 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
3150 To start the local copy, invoke it in a browser like this:
</p
>
3152 <p
><blockquote
>
3153 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
3154 </blockquote
></p
>
3156 <p
>See the project home page and the
3157 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
3158 ;login: article on Coz
</a
> for more information on how it is
3164 <title>My own self balancing Lego Segway
</title>
3165 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
3166 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
3167 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
3168 <description><p
>A while back I received a Gyro sensor for the NXT
3169 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
3170 present. It had been on my wishlist for a while, because I wanted to
3171 build a Segway like balancing lego robot. I had already built
3172 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
3173 robot
</a
> with the kids, using the light/color sensor included in the
3174 NXT kit as the balance sensor, but it was not working very well. It
3175 could balance for a while, but was very sensitive to the light
3176 condition in the room and the reflective properties of the surface and
3177 would fall over after a short while. I wanted something more robust,
3179 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
3180 gyro sensor from HiTechnic
</a
> I believed would solve it on my
3181 wishlist for some years before it suddenly showed up as a gift from my
3182 loved ones. :)
</p
>
3184 <p
>Unfortunately I have not had time to sit down and play with it
3185 since then. But that changed some days ago, when I was searching for
3186 lego segway information and came across a recipe from HiTechnic for
3188 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
3189 HTWay
</a
>, a segway like balancing robot. Build instructions and
3190 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
3191 code
</a
> was included, so it was just a question of putting it all
3192 together. And thanks to the great work of many Debian developers, the
3193 compiler needed to build the source for the NXT is already included in
3194 Debian, so I was read to go in less than an hour. The resulting robot
3195 do not look very impressive in its simplicity:
</p
>
3197 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
3199 <p
>Because I lack the infrared sensor used to control the robot in the
3200 design from HiTechnic, I had to comment out the last task
3201 (taskControl). I simply placed /* and */ around it get the program
3202 working without that sensor present. Now it balances just fine until
3203 the battery status run low:
</p
>
3205 <p align=
"center
"><video width=
"70%
" controls=
"true
">
3206 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
3207 </video
></p
>
3209 <p
>Now we would like to teach it how to follow a line and take remote
3210 control instructions using the included Bluetooth receiver in the NXT.
</p
>
3212 <p
>If you, like me, love LEGO and want to make sure we find the tools
3213 they need to work with LEGO in Debian and all our derivative
3214 distributions like Ubuntu, check out
3215 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
3216 project page
</a
> and join the Debian LEGO team. Personally I own a
3217 RCX and NXT controller (no EV3), and would like to make sure the
3218 Debian tools needed to program the systems I own work as they
3224 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
3225 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
3226 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
3227 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
3228 <description><p
>In July
3229 <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
3230 wrote how to get the Signal Chrome/Chromium app working
</a
> without
3231 the ability to receive SMS messages (aka without a cell phone). It is
3232 time to share some experiences and provide an updated setup.
</p
>
3234 <p
>The Signal app have worked fine for several months now, and I use
3235 it regularly to chat with my loved ones. I had a major snag at the
3236 end of my summer vacation, when the the app completely forgot my
3237 setup, identity and keys. The reason behind this major mess was
3238 running out of disk space. To avoid that ever happening again I have
3239 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
3240 roll back to an earlier version if the files are wiped by mistake. I
3241 had to use it once after introducing the git backup. When rolling
3242 back to an earlier version, one need to use the
'reset session
' option
3243 in Signal to get going, and notify the people you talk with about the
3244 problem. I assume there is some sequence number tracking in the
3245 protocol to detect rollback attacks. The git repository is rather big
3246 (
674 MiB so far), but I have not tried to figure out if some of the
3247 content can be added to a .gitignore file due to lack of spare
3250 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
3251 make it impossible to send messages using Signal. I could still
3252 receive them, but had to patch the code with a new timestamp to send.
3253 I believe the timeout is added by the developers to force people to
3254 upgrade to the latest version of the app, even when there is no
3255 protocol changes, to reduce the version skew among the user base and
3256 thus try to keep the number of support requests down.
</p
>
3258 <p
>Since my original recipe, the Signal source code changed slightly,
3259 making the old patch fail to apply cleanly. Below is an updated
3260 patch, including the shell wrapper I use to start Signal. The
3261 original version required a new user to locate the JavaScript console
3262 and call a function from there. I got help from a friend with more
3263 JavaScript knowledge than me to modify the code to provide a GUI
3264 button instead. This mean that to get started you just need to run
3265 the wrapper and click the
'Register without mobile phone
' to get going
3266 now. I
've also modified the timeout code to always set it to
90 days
3267 in the future, to avoid having to patch the code regularly.
</p
>
3269 <p
>So, the updated recipe for Debian Jessie:
</p
>
3273 <li
>First, install required packages to get the source code and the
3274 browser you need. Signal only work with Chrome/Chromium, as far as I
3275 know, so you need to install it.
3278 apt install git tor chromium
3279 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3280 </pre
></li
>
3282 <li
>Modify the source code using command listed in the the patch
3283 block below.
</li
>
3285 <li
>Start Signal using the run-signal-app wrapper (for example using
3286 <tt
>`pwd`/run-signal-app
</tt
>).
3288 <li
>Click on the
'Register without mobile phone
', will in a phone
3289 number you can receive calls to the next minute, receive the
3290 verification code and enter it into the form field and press
3291 'Register
'. Note, the phone number you use will be user Signal
3292 username, ie the way others can find you on Signal.
</li
>
3294 <li
>You can now use Signal to contact others. Note, new contacts do
3295 not show up in the contact list until you restart Signal, and there is
3296 no way to assign names to Contacts. There is also no way to create or
3297 update chat groups. I suspect this is because the web app do not have
3298 a associated contact database.
</li
>
3302 <p
>I am still a bit uneasy about using Signal, because of the way its
3303 main author moxie0 reject federation and accept dependencies to major
3304 corporations like Google (part of the code is fetched from Google) and
3305 Amazon (the central coordination point is owned by Amazon). See for
3307 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
3308 LibreSignal issue tracker
</a
> for a thread documenting the authors
3309 view on these issues. But the network effect is strong in this case,
3310 and several of the people I want to communicate with already use
3311 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
3312 once it
<a href=
"https://bugs.debian.org/
830265">work on my
3313 laptop
</a
>? It already work on Windows and Android, and is included
3314 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
3315 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
3316 working on Debian Stable.
</p
>
3318 <p
>Anyway, this is the patch I apply to the Signal code to get it
3319 working. It switch to the production servers, disable to timeout,
3320 make registration easier and add the shell wrapper:
</p
>
3323 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
3324 diff --git a/js/background.js b/js/background.js
3325 index
24b4c1d.
.579345f
100644
3326 --- a/js/background.js
3327 +++ b/js/background.js
3332 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
3333 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
3334 var SERVER_PORTS = [
80,
4433,
8443];
3335 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
3336 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
3337 var messageReceiver;
3338 window.getSocketStatus = function() {
3339 if (messageReceiver) {
3340 diff --git a/js/expire.js b/js/expire.js
3341 index
639aeae..beb91c3
100644
3346 'use strict
';
3347 - var BUILD_EXPIRATION =
0;
3348 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
3350 window.extension = window.extension || {};
3352 diff --git a/js/views/install_view.js b/js/views/install_view.js
3353 index
7816f4f.
.1d6233b
100644
3354 --- a/js/views/install_view.js
3355 +++ b/js/views/install_view.js
3358 'click .step1
': this.selectStep.bind(this,
1),
3359 'click .step2
': this.selectStep.bind(this,
2),
3360 -
'click .step3
': this.selectStep.bind(this,
3)
3361 +
'click .step3
': this.selectStep.bind(this,
3),
3362 +
'click .callreg
': function() { extension.install(
'standalone
') },
3365 clearQR: function() {
3366 diff --git a/options.html b/options.html
3367 index dc0f28e.
.8d709f6
100644
3371 &lt;div class=
'nav
'>
3372 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
3373 &lt;p
>{{ installTagline }}
&lt;/p
>
3374 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
3375 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
3376 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
3379 &lt;span class=
'dot step1 selected
'>&lt;/span
>
3380 &lt;span class=
'dot step2
'>&lt;/span
>
3381 &lt;span class=
'dot step3
'>&lt;/span
>
3382 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
3383 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
3389 +userdata=
"`pwd`/userdata
"
3390 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
3391 + (cd $userdata
&& git init)
3393 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
3395 + --proxy-server=
"socks://localhost:
9050" \
3396 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3398 chmod a+rx run-signal-app
3401 <p
>As usual, if you use Bitcoin and want to show your support of my
3402 activities, please send Bitcoin donations to my address
3403 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3408 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
3409 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
3410 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
3411 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
3412 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
3413 system
</a
> provide a practical and easy way to figure out which
3414 packages support the hardware in a given machine. The command line
3415 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
3416 convenient way to list and install packages relevant for the current
3417 hardware during system installation, both user space packages and
3418 firmware packages. The GUI background daemon on the other hand provide
3419 a pop-up proposing to install packages when a new dongle is inserted
3420 while using the computer. For example, if you plug in a smart card
3421 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
3422 that package isn
't already installed, and if you plug in a USB video
3423 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
3424 cheese is currently missing. This already work just fine.
</p
>
3426 <p
>But Isenkram depend on a database mapping from hardware IDs to
3427 package names. When I started no such database existed in Debian, so
3428 I made my own data set and included it with the isenkram package and
3429 made isenkram fetch the latest version of this database from git using
3430 http. This way the isenkram users would get updated package proposals
3431 as soon as I learned more about hardware related packages.
</p
>
3433 <p
>The hardware is identified using modalias strings. The modalias
3434 design is from the Linux kernel where most hardware descriptors are
3435 made available as a strings that can be matched using filename style
3436 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3437 identifiers.
</p
>
3439 <p
>The downside to the Isenkram specific database is that there is no
3440 information about relevant distribution / Debian version, making
3441 isenkram propose obsolete packages too. But along came AppStream, a
3442 cross distribution mechanism to store and collect metadata about
3443 software packages. When I heard about the proposal, I contacted the
3444 people involved and suggested to add a hardware matching rule using
3445 modalias strings in the specification, to be able to use AppStream for
3446 mapping hardware to packages. This idea was accepted and AppStream is
3447 now a great way for a package to announce the hardware it support in a
3448 distribution neutral way. I wrote
3449 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
3450 recipe on how to add such meta-information
</a
> in a blog post last
3451 December. If you have a hardware related package in Debian, please
3452 announce the relevant hardware IDs using AppStream.
</p
>
3454 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
3455 RCX or NXT unit, announce this support using AppStream. The effect is
3456 that when you insert such LEGO robot controller into your Debian
3457 machine, Isenkram will propose to install the packages needed to get
3458 it working. The intention is that this should allow the local user to
3459 start programming his robot controller right away without having to
3460 guess what packages to use or which permissions to fix.
</p
>
3462 <p
>But when I sat down with my son the other day to program our NXT
3463 unit using his Debian Stretch computer, I discovered something
3464 annoying. The local console user (ie my son) did not get access to
3465 the USB device for programming the unit. This used to work, but no
3466 longer in Jessie and Stretch. After some investigation and asking
3467 around on #debian-devel, I discovered that this was because udev had
3468 changed the mechanism used to grant access to local devices. The
3469 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
3470 no longer applied, because LDAP users no longer was added to the
3471 plugdev group during login. Michael Biebl told me that this method
3472 was obsolete and the new method used ACLs instead. This was good
3473 news, as the plugdev mechanism is a mess when using a remote user
3474 directory like LDAP. Using ACLs would make sure a user lost device
3475 access when she logged out, even if the user left behind a background
3476 process which would retain the plugdev membership with the ConsoleKit
3477 setup. Armed with this knowledge I moved on to fix the access problem
3478 for the LEGO Mindstorms related packages.
</p
>
3480 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
3481 applied directly for a device, or is applied in
3482 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
3483 LEGO Mindstorms udev rules did not have a class, I decided to add the
3484 tag directly in the udev rules files included in the packages. Here
3485 is one example. For the nqc C compiler for the RCX, the
3486 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
3488 <p
><pre
>
3489 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
3490 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
3491 </pre
></p
>
3493 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
3494 packages using plugdev in their /lib/udev/rules.d/ files should be
3495 changed to use this tag (either directly or indirectly via
3496 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
3497 to detect this?
</p
>
3499 <p
>I
've been unable to find good documentation on the uaccess feature.
3500 It is unclear to me if the uaccess tag is an internal implementation
3501 detail like the udev-acl tag used by
3502 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
3503 indirect method is the preferred way. Michael
3504 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
3505 documentation from the systemd project
</a
> and I hope it will make
3506 this clearer. For now I use the generic classes when they exist and
3507 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
3508 directly if no such class exist.
</p
>
3510 <p
>To learn more about the isenkram system, please check out
3511 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
3512 blog posts tagged isenkram
</a
>.
</p
>
3514 <p
>To help out making life for LEGO constructors in Debian easier,
3515 please join us on our IRC channel
3516 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
3517 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
3518 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
3519 list is not yet created, but we are working on it. :)
</p
>
3521 <p
>As usual, if you use Bitcoin and want to show your support of my
3522 activities, please send Bitcoin donations to my address
3523 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3528 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
3529 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
3530 <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>
3531 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
3532 <description><p
>In April we
3533 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
3534 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
3535 how to set up and administrate a Debian system. Today I am happy to
3536 report that the first draft is now publicly available. You can find
3537 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
3538 Administrator
's Handbook page
</a
> (under Other languages). The first
3539 eight chapters have a first draft translation, and we are working on
3540 proofreading the content. If you want to help out, please start
3542 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
3543 hosted weblate project page
</a
>, and get in touch using
3544 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
3545 translators mailing list
</a
>. Please also check out
3546 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
3547 contributors
</a
>. A good way to contribute is to proofread the text
3548 and update weblate if you find errors.
</p
>
3550 <p
>Our goal is still to make the Norwegian book available on paper as well as
3551 electronic form.
</p
>
3556 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
3557 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
3558 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
3559 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
3560 <description><p
>This summer, I read a great article
3561 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
3562 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
3563 how to profile multi-threaded programs. It presented a system for
3564 profiling software by running experiences in the running program,
3565 testing how run time performance is affected by
"speeding up
" parts of
3566 the code to various degrees compared to a normal run. It does this by
3567 slowing down parallel threads while the
"faster up
" code is running
3568 and measure how this affect processing time. The processing time is
3569 measured using probes inserted into the code, either using progress
3570 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
3571 can also measure unmodified code by measuring complete the program
3572 runtime and running the program several times instead.
</p
>
3574 <p
>The project and presentation was so inspiring that I would like to
3575 get the system into Debian. I
3576 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
3577 a WNPP request for it
</a
> and contacted upstream to try to make the
3578 system ready for Debian by sending patches. The build process need to
3579 be changed a bit to avoid running
'git clone
' to get dependencies, and
3580 to include the JavaScript web page used to visualize the collected
3581 profiling information included in the source package.
3582 But I expect that should work out fairly soon.
</p
>
3584 <p
>The way the system work is fairly simple. To run an coz experiment
3585 on a binary with debug symbols available, start the program like this:
3587 <p
><blockquote
><pre
>
3588 coz run --- program-to-run
3589 </pre
></blockquote
></p
>
3591 <p
>This will create a text file profile.coz with the instrumentation
3592 information. To show what part of the code affect the performance
3593 most, use a web browser and either point it to
3594 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
3595 or use the copy from git (in the gh-pages branch). Check out this web
3596 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
3597 profiling more useful you include
&lt;coz.h
&gt; and insert the
3598 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
3599 code, rebuild and run the profiler. This allow coz to do more
3600 targeted experiments.
</p
>
3602 <p
>A video published by ACM
3603 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
3604 Coz profiler
</a
> is available from Youtube. There is also a paper
3605 from the
25th Symposium on Operating Systems Principles available
3607 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
3608 finding code that counts with causal profiling
</a
>.
</p
>
3610 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
3611 for Coz is available from github. It will only build with clang
3613 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
3614 feature missing in GCC
</a
>, but I
've submitted
3615 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
3616 it
</a
> and hope it will be included in the upstream source soon.
</p
>
3618 <p
>Please get in touch if you, like me, would like to see this piece
3619 of software in Debian. I would very much like some help with the
3620 packaging effort, as I lack the in depth knowledge on how to package
3621 C++ libraries.
</p
>
3626 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
3627 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
3628 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
3629 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
3630 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
3631 to be a slight challenge. Here is the recipe if I ever need to do it
3632 again. It all started by me wanting to try the recipe to set up
3633 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
3634 hardened Android installation
</a
> from the Tor project blog on a
3635 device I had access to. It is a old mobile phone with a broken
3636 microphone The initial idea had been to just
3637 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
3638 CyanogenMod on it
</a
>, but did not quite find time to start on it
3639 until a few days ago.
</p
>
3641 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
3642 loader (press volume down and power at the same time), (
2) select
3643 'fastboot
' before (
3) connecting the device via USB to a Linux
3644 machine, (
4) request the device identifier token by running
'fastboot
3645 oem get_identifier_token
', (
5) request the device unlocking key using
3646 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
3647 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
3649 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
3650 or newer, and the device I was working on had
2.00.0027. This
3651 apparently can be easily fixed by downloading a Windows program and
3652 running it on your Windows machine, if you accept the terms Microsoft
3653 require you to accept to use Windows - which I do not. So I had to
3654 come up with a different approach. I got a lot of help from AndyCap
3655 on #nuug, and would not have been able to get this working without
3658 <p
>First I needed to extract the hboot firmware from
3659 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
3660 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
3661 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
3662 project named unruu
</a
> using libunshield. The unshield tool did not
3663 recognise the file format, but unruu worked and extracted rom.zip,
3664 containing the new hboot firmware and a text file describing which
3665 devices it would work for.
</p
>
3667 <p
>Next, I needed to get the new firmware into the device. For this I
3668 followed some instructions
3669 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
3670 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
3671 machine with Debian testing:
</p
>
3673 <p
><pre
>
3674 adb reboot-bootloader
3675 fastboot oem rebootRUU
3676 fastboot flash zip rom.zip
3677 fastboot flash zip rom.zip
3679 </pre
></p
>
3681 <p
>The flash command apparently need to be done twice to take effect,
3682 as the first is just preparations and the second one do the flashing.
3683 The adb command is just to get to the boot loader menu, so turning the
3684 device on while holding volume down and the power button should work
3687 <p
>With the new hboot version in place I could start following the
3688 instructions on the HTC developer web site. I got the device token
3689 like this:
</p
>
3691 <p
><pre
>
3692 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
3695 <p
>And once I got the unlock code via email, I could use it like
3698 <p
><pre
>
3699 fastboot flash unlocktoken Unlock_code.bin
3700 </pre
></p
>
3702 <p
>And with that final step in place, the phone was unlocked and I
3703 could start stuffing the software of my own choosing into the device.
3704 So far I only inserted a replacement recovery image to wipe the phone
3705 before I start. We will see what happen next. Perhaps I should
3706 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
3711 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
3712 <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>
3713 <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>
3714 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
3715 <description><p
>For a while now, I have wanted to test
3716 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
3717 said to provide end to end encrypted communication and several of my
3718 friends and family are already using it. As I by choice do not own a
3719 mobile phone, this proved to be harder than expected. And I wanted to
3720 have the source of the client and know that it was the code used on my
3721 machine. But yesterday I managed to get it working. I used the
3722 Github source, compared it to the source in
3723 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
3724 Signal Chrome app
</a
> available from the Chrome web store, applied
3725 patches to use the production Signal servers, started the app and
3726 asked for the hidden
"register without a smart phone
" form. Here is
3727 the recipe how I did it.
</p
>
3729 <p
>First, I fetched the Signal desktop source from Github, using
3732 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3735 <p
>Next, I patched the source to use the production servers, to be
3736 able to talk to other Signal users:
</p
>
3739 cat
&lt;
&lt;EOF | patch -p0
3740 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
3741 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
3742 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
3747 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
3748 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
3749 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
3750 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
3751 var messageReceiver;
3752 window.getSocketStatus = function() {
3753 if (messageReceiver) {
3754 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
3755 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
3756 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
3759 'use strict
';
3760 - var BUILD_EXPIRATION =
0;
3761 + var BUILD_EXPIRATION =
1474492690000;
3763 window.extension = window.extension || {};
3768 <p
>The first part is changing the servers, and the second is updating
3769 an expiration timestamp. This timestamp need to be updated regularly.
3770 It is set
90 days in the future by the build process (Gruntfile.js).
3771 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
3773 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
3774 script to launch Signal in Chromium.
</p
>
3781 --proxy-server=
"socks://localhost:
9050" \
3782 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
3785 <p
> The script start the app and configure Chromium to use the Tor
3786 SOCKS5 proxy to make sure those controlling the Signal servers (today
3787 Amazon and Whisper Systems) as well as those listening on the lines
3788 will have a harder time location my laptop based on the Signal
3789 connections if they use source IP address.
</p
>
3791 <p
>When the script starts, one need to follow the instructions under
3792 "Standalone Registration
" in the CONTRIBUTING.md file in the git
3793 repository. I right clicked on the Signal window to get up the
3794 Chromium debugging tool, visited the
'Console
' tab and wrote
3795 'extension.install(
"standalone
")
' on the console prompt to get the
3796 registration form. Then I entered by land line phone number and
3797 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
3798 repeated the verification code three times. After entering the number
3799 into the verification code field in the form, I could start using
3800 Signal from my laptop.
3802 <p
>As far as I can tell, The Signal app will leak who is talking to
3803 whom and thus who know who to those controlling the central server,
3804 but such leakage is hard to avoid with a centrally controlled server
3805 setup. It is something to keep in mind when using Signal - the
3806 content of your chats are harder to intercept, but the meta data
3807 exposing your contact network is available to people you do not know.
3808 So better than many options, but not great. And sadly the usage is
3809 connected to my land line, thus allowing those controlling the server
3810 to associate it to my home and person. I would prefer it if only
3811 those I knew could tell who I was on Signal. There are options
3812 avoiding such information leakage, but most of my friends are not
3813 using them, so I am stuck with Signal for now.
</p
>
3815 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
3817 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
3818 and updated recipe for using the Signal app without a mobile
3819 phone
</a
>.
</p
>
3824 <title>The new
"best
" multimedia player in Debian?
</title>
3825 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
3826 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
3827 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
3828 <description><p
>When I set out a few weeks ago to figure out
3829 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
3830 multimedia player in Debian claimed to support most file formats /
3831 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
3832 the various players claimed support for. The range was from
55 to
130
3833 MIME types. I suspect most media formats are supported by all
3834 players, but this is not really reflected in the MimeTypes values in
3835 their desktop files. There are probably also some bogus MIME types
3836 listed, but it is hard to identify which one this is.
</p
>
3838 <p
>Anyway, in the mean time I got in touch with upstream for some of
3839 the players suggesting to add more MIME types to their desktop files,
3840 and decided to spend some time myself improving the situation for my
3841 favorite media player VLC. The fixes for VLC entered Debian unstable
3842 yesterday. The complete list of MIME types can be seen on the
3843 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
3844 player MIME type support status
</a
> Debian wiki page.
</p
>
3846 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
3847 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
3848 kmplayer. I am sure some of the other players desktop files support
3849 several of the formats currently listed as working only with vlc,
3850 toten and parole.
</p
>
3852 <p
>A sad observation is that only
14 MIME types are listed as
3853 supported by all the tested multimedia players in Debian in their
3854 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
3855 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
3856 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
3857 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
3858 it sad that video/ogg and video/webm is not supported by all the media
3859 players in Debian. As far as I can tell, all of them can handle both
3865 <title>A program should be able to open its own files on Linux
</title>
3866 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
3867 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
3868 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
3869 <description><p
>Many years ago, when koffice was fresh and with few users, I
3870 decided to test its presentation tool when making the slides for a
3871 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
3872 wrote the first draft of the slides, saved the result and went to bed
3873 the day before I would give the talk. The next day I took a plane to
3874 the location where the meeting should take place, and on the plane I
3875 started up koffice again to polish the talk a bit, only to discover
3876 that kpresenter refused to load its own data file. I cursed a bit and
3877 started making the slides again from memory, to have something to
3878 present when I arrived. I tested that the saved files could be
3879 loaded, and the day seemed to be rescued. I continued to polish the
3880 slides until I suddenly discovered that the saved file could no longer
3881 be loaded into kpresenter. In the end I had to rewrite the slides
3882 three times, condensing the content until the talk became shorter and
3883 shorter. After the talk I was able to pinpoint the problem
&ndash;
3884 kpresenter wrote inline images in a way itself could not understand.
3885 Eventually that bug was fixed and kpresenter ended up being a great
3886 program to make slides. The point I
'm trying to make is that we
3887 expect a program to be able to load its own data files, and it is
3888 embarrassing to its developers if it can
't.
</p
>
3890 <p
>Did you ever experience a program failing to load its own data
3891 files from the desktop file browser? It is not a uncommon problem. A
3892 while back I discovered that the screencast recorder
3893 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
3894 browser would refuse to open. No video player claimed to understand
3895 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
3896 returning the application/ogg MIME type, which no video player I had
3897 installed listed as a MIME type they would understand. I asked for
3898 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
3899 behavour
</a
> and use the MIME type video/ogg instead. I also asked
3900 several video players to add video/ogg to their desktop files, to give
3901 the file browser an idea what to do about Ogg Theora files. After a
3902 while, the desktop file browsers in Debian started to handle the
3903 output from gtk-recordmydesktop properly.
</p
>
3905 <p
>But history repeats itself. A few days ago I tested the music
3906 system Rosegarden again, and I discovered that the KDE and xfce file
3907 browsers did not know what to do with the Rosegarden project files
3908 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
3909 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
3910 included in the next upload. To increase the chance of me remembering
3911 how to fix the problem next time some program fail to load its files
3912 from the file browser, here are some notes on how to fix it.
</p
>
3914 <p
>The file browsers in Debian in general operates on MIME types.
3915 There are two sources for the MIME type of a given file. The output from
3916 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
3917 shared MIME type registry (under /usr/share/mime/). The file MIME
3918 type is mapped to programs supporting the MIME type, and this
3919 information is collected from
3920 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
3921 desktop files
</a
> available in /usr/share/applications/. If there is
3922 one desktop file claiming support for the MIME type of the file, it is
3923 activated when asking to open a given file. If there are more, one
3924 can normally select which one to use by right-clicking on the file and
3925 selecting the wanted one using
'Open with
' or similar. In general
3926 this work well. But it depend on each program picking a good MIME
3928 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
3929 MIME type registered with IANA
</a
>), file and/or the shared MIME
3930 registry recognizing the file and the desktop file to list the MIME
3931 type in its list of supported MIME types.
</p
>
3933 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
3934 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
3935 Shared MIME database
</a
> look like this:
</p
>
3937 <p
><blockquote
><pre
>
3938 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
3939 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
3940 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
3941 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
3942 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
3943 &lt;glob pattern=
"*.rg
"/
&gt;
3944 &lt;/mime-type
&gt;
3945 &lt;/mime-info
&gt;
3946 </pre
></blockquote
></p
>
3948 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
3949 (it is a gzipped XML file). Note, it is much better to use an
3950 official MIME type registered with IANA than it is to make up ones own
3951 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
3953 <p
>The desktop file of the rosegarden program failed to list
3954 audio/x-rosegarden in its list of supported MIME types, causing the
3955 file browsers to have no idea what to do with *.rg files:
</p
>
3957 <p
><blockquote
><pre
>
3958 % grep Mime /usr/share/applications/rosegarden.desktop
3959 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
3960 X-KDE-NativeMimeType=audio/x-rosegarden-composition
3962 </pre
></blockquote
></p
>
3964 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
3965 MimeType= line.
</p
>
3967 <p
>If you run into a file which fail to open the correct program when
3968 selected from the file browser, please check out the output from
3969 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
3970 MIME type is registered somewhere under /usr/share/mime/ and check
3971 that some desktop file under /usr/share/applications/ is claiming
3972 support for this MIME type. If not, please report a bug to have it
3978 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
3979 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
3980 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
3981 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
3982 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
3983 system
</a
> is a user-focused solution in Debian for handling hardware
3984 related packages. The idea is to have a database of mappings between
3985 hardware and packages, and pop up a dialog suggesting for the user to
3986 install the packages to use a given hardware dongle. Some use cases
3987 are when you insert a Yubikey, it proposes to install the software
3988 needed to control it; when you insert a braille reader list it
3989 proposes to install the packages needed to send text to the reader;
3990 and when you insert a ColorHug screen calibrator it suggests to
3991 install the driver for it. The system work well, and even have a few
3992 command line tools to install firmware packages and packages for the
3993 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
3995 <p
>The system was initially written using aptdaemon, because I found
3996 good documentation and example code on how to use it. But aptdaemon
3997 is going away and is generally being replaced by
3998 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
3999 so Isenkram needed a rewrite. And today, thanks to the great patch
4000 from my college Sunil Mohan Adapa in the FreedomBox project, the
4001 rewrite finally took place. I
've just uploaded a new version of
4002 Isenkram into Debian Unstable with the patch included, and the default
4003 for the background daemon is now to use PackageKit. To check it out,
4004 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
4005 and see if it is recognised.
</p
>
4007 <p
>If you want to know what kind of packages isenkram would propose for
4008 the machine it is running on, you can check out the isenkram-lookup
4009 program. This is what it look like on a Thinkpad X230:
</p
>
4011 <p
><blockquote
><pre
>
4027 </pre
></blockquote
></p
>
4029 <p
>The hardware mappings come from several places. The preferred way
4030 is for packages to announce their hardware support using
4031 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
4032 cross distribution appstream system
</a
>.
4034 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
4035 blog posts about isenkram
</a
> to learn how to do that.
</p
>
4040 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
4041 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
4042 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
4043 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
4044 <description><p
>Yesterday I updated the
4045 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
4046 package in Debian
</a
> with a few patches sent to me by skilled and
4047 enterprising users. There were some nice user and visible changes.
4048 First of all, both desktop menu entries now work. A design flaw in
4049 one of the script made the history graph fail to show up (its PNG was
4050 dumped in ~/.xsession-errors) if no controlling TTY was available.
4051 The script worked when called from the command line, but not when
4052 called from the desktop menu. I changed this to look for a DISPLAY
4053 variable or a TTY before deciding where to draw the graph, and now the
4054 graph window pop up as expected.
</p
>
4056 <p
>The next new feature is a discharge rate estimator in one of the
4057 graphs (the one showing the last few hours). New is also the user of
4058 colours showing charging in blue and discharge in red. The percentages
4059 of this graph is relative to last full charge, not battery design
4062 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
4064 <p
>The other graph show the entire history of the collected battery
4065 statistics, comparing it to the design capacity of the battery to
4066 visualise how the battery life time get shorter over time. The red
4067 line in this graph is what the previous graph considers
100 percent:
4069 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
4071 <p
>In this graph you can see that I only charge the battery to
80
4072 percent of last full capacity, and how the capacity of the battery is
4073 shrinking. :(
</p
>
4075 <p
>The last new feature is in the collector, which now will handle
4076 more hardware models. On some hardware, Linux power supply
4077 information is stored in /sys/class/power_supply/ACAD/, while the
4078 collector previously only looked in /sys/class/power_supply/AC/. Now
4079 both are checked to figure if there is power connected to the
4082 <p
>If you are interested in how your laptop battery is doing, please
4084 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
4085 in Debian unstable, or rebuild it on Jessie to get it working on
4086 Debian stable. :) The upstream source is available from
<a
4087 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4088 Patches are very welcome.
</p
>
4090 <p
>As usual, if you use Bitcoin and want to show your support of my
4091 activities, please send Bitcoin donations to my address
4092 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4097 <title>Debian now with ZFS on Linux included
</title>
4098 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
4099 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
4100 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
4101 <description><p
>Today, after many years of hard work from many people,
4102 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
4103 Debian. The package status can be seen on
4104 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
4105 for zfs-linux
</a
>. and
4106 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
4107 team status page
</a
>. If you want to help out, please join us.
4108 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
4109 source code
</a
> is available via git on Alioth. It would also be
4110 great if you could help out with
4111 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
4112 it is an important piece of the puzzle to get ZFS working.
</p
>
4117 <title>What is the best multimedia player in Debian?
</title>
4118 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
4119 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
4120 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
4121 <description><p
><strong
>Where I set out to figure out which multimedia player in
4122 Debian claim support for most file formats.
</strong
></p
>
4124 <p
>A few years ago, I had a look at the media support for Browser
4125 plugins in Debian, to get an idea which plugins to include in Debian
4126 Edu. I created a script to extract the set of supported MIME types
4127 for each plugin, and used this to find out which multimedia browser
4128 plugin supported most file formats / media types.
4129 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
4130 result
</a
> can still be seen on the Debian wiki, even though it have
4131 not been updated for a while. But browser plugins are less relevant
4132 these days, so I thought it was time to look at standalone
4135 <p
>A few days ago I was tired of VLC not being listed as a viable
4136 player when I wanted to play videos from the Norwegian National
4137 Broadcasting Company, and decided to investigate why. The cause is a
4138 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
4139 desktop file
</a
>. In the process I wrote a script to compare the set
4140 of MIME types announced in the desktop file and the browser plugin,
4141 only to discover that there is quite a large difference between the
4142 two for VLC. This discovery made me dig up the script I used to
4143 compare browser plugins, and adjust it to compare desktop files
4144 instead, to try to figure out which multimedia player in Debian
4145 support most file formats.
</p
>
4147 <p
>The result can be seen on the Debian Wiki, as
4148 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
4149 table listing all MIME types supported by one of the packages included
4150 in the table
</a
>, with the package supporting most MIME types being
4151 listed first in the table.
</p
>
4153 </p
>The best multimedia player in Debian? It is totem, followed by
4154 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
4155 kmplayer. Time for the other players to update their announced MIME
4161 <title>The Pyra - handheld computer with Debian preinstalled
</title>
4162 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
4163 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
4164 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
4165 <description>A friend of mine made me aware of
4166 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
4167 handheld computer which will be delivered with Debian preinstalled. I
4168 would love to get one of those for my birthday. :)
</p
>
4170 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
4171 plugs and many others connectors, and include a full keyboard and a
5"
4172 LCD touch screen. The
6000mAh battery is claimed to provide a whole
4173 day of battery life time, but I have not seen any independent tests
4174 confirming this. The vendor is still collecting preorders, and the
4175 last I heard last night was that
22 more orders were needed before
4176 production started.
</p
>
4178 <p
>As far as I know, this is the first handheld preinstalled with
4179 Debian. Please let me know if you know of any others. Is it the
4180 first computer being sold with Debian preinstalled?
</p
>
4185 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
4186 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
4187 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
4188 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
4189 <description><p
>During this weekends
4190 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
4191 squashing party and developer gathering
</a
>, we decided to do our part
4192 to make sure there are good books about Debian available in Norwegian
4193 Bokmål, and got in touch with the people behind the
4194 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
4195 project
</a
> to get started. If you want to help out, please start
4197 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
4198 hosted weblate project page
</a
>, and get in touch using
4199 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
4200 translators mailing list
</a
>. Please also check out
4201 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
4202 contributors
</a
>.
</p
>
4204 <p
>The book is already available on paper in English, French and
4205 Japanese, and our goal is to get it available on paper in Norwegian
4206 Bokmål too. In addition to the paper edition, there are also EPUB and
4207 Mobi versions available. And there are incomplete translations
4208 available for many more languages.
</p
>
4213 <title>One in two hundred Debian users using ZFS on Linux?
</title>
4214 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
4215 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
4216 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
4217 <description><p
>Just for fun I had a look at the popcon number of ZFS related
4218 packages in Debian, and was quite surprised with what I found. I use
4219 ZFS myself at home, but did not really expect many others to do so.
4220 But I might be wrong.
</p
>
4222 <p
>According to
4223 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
4224 results for spl-linux
</a
>, there are
1019 Debian installations, or
4225 0.53% of the population, with the package installed. As far as I know
4226 the only use of the spl-linux package is as a support library for ZFS
4227 on Linux, so I use it here as proxy for measuring the number of ZFS
4228 installation on Linux in Debian. In the kFreeBSD variant of Debian
4229 the ZFS feature is already available, and there
4230 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
4231 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
4232 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
4234 <p
>But even though the Debian project leader Lucas Nussbaum
4235 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
4236 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
4237 cleared, the package is still not in Debian. The package is again in
4238 the NEW queue. Several uploads have been rejected so far because the
4239 debian/copyright file was incomplete or wrong, but there is no reason
4240 to give up. The current status can be seen on
4241 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
4242 team status page
</a
>, and
4243 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
4244 source code
</a
> is available on Alioth.
</p
>
4246 <p
>As I want ZFS to be included in next version of Debian to make sure
4247 my home server can function in the future using only official Debian
4248 packages, and the current blocker is to get the debian/copyright file
4249 accepted by the FTP masters in Debian, I decided a while back to try
4250 to help out the team. This was the background for my blog post about
4251 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
4252 updating and checking debian/copyright semi-automatically
</a
>, and I
4253 used the techniques I explored there to try to find any errors in the
4254 copyright file. It is not very easy to check every one of the around
4255 2000 files in the source package, but I hope we this time got it
4256 right. If you want to help out, check out the git source and try to
4257 find missing entries in the debian/copyright file.
</p
>
4262 <title>Full battery stats collector is now available in Debian
</title>
4263 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
4264 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
4265 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
4266 <description><p
>Since this morning, the battery-stats package in Debian include an
4267 extended collector that will collect the complete battery history for
4268 later processing and graphing. The original collector store the
4269 battery level as percentage of last full level, while the new
4270 collector also record battery vendor, model, serial number, design
4271 full level, last full level and current battery level. This make it
4272 possible to predict the lifetime of the battery as well as visualise
4273 the energy flow when the battery is charging or discharging.
</p
>
4275 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
4276 in the version
0.5.1 package in unstable. Get the new battery level graph
4277 and lifetime prediction by running:
4279 <p
><pre
>
4280 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4281 </pre
></p
>
4283 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
4285 <p
>The flow in/out of the battery can be seen by running (no menu
4286 entry yet):
</p
>
4288 <p
><pre
>
4289 /usr/share/battery-stats/battery-stats-graph-flow
4290 </pre
></p
>
4292 <p
>I
'm not quite happy with the way the data is visualised, at least
4293 when there are few data points. The graphs look a bit better with a
4294 few years of data.
</p
>
4296 <p
>A while back one important feature I use in the battery stats
4297 collector broke in Debian. The scripts in
4298 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
4299 suspect it happened when Jessie started using systemd, but I do not
4300 know. The issue is reported as
4301 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
4302 pm-utils. I managed to work around it by adding an udev rule to call
4303 the collector script every time the power connector is connected and
4304 disconnected. With this fix in place it was finally time to make a
4305 new release of the package, and get it into Debian.
</p
>
4307 <p
>If you are interested in how your laptop battery is doing, please
4309 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
4310 in Debian unstable, or rebuild it on Jessie to get it working on
4311 Debian stable. :) The upstream source is available from
4312 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4313 As always, patches are very welcome.
</p
>
4318 <title>Making battery measurements a little easier in Debian
</title>
4319 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
4320 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
4321 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
4322 <description><p
>Back in September, I blogged about
4323 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
4324 system I wrote to collect statistics about my laptop battery
</a
>, and
4325 how it showed the decay and death of this battery (now replaced). I
4326 created a simple deb package to handle the collection and graphing,
4327 but did not want to upload it to Debian as there were already
4328 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
4329 package in Debian
</a
> that should do the same thing, and I did not see
4330 a point of uploading a competing package when battery-stats could be
4331 fixed instead. I reported a few bugs about its non-function, and
4332 hoped someone would step in and fix it. But no-one did.
</p
>
4334 <p
>I got tired of waiting a few days ago, and took matters in my own
4335 hands. The end result is that I am now the new upstream developer of
4336 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
4337 battery-stats in Debian, and the package in Debian unstable is finally
4338 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
4339 information provided by the Linux kernel. If you install the
4340 battery-stats package from unstable now, you will be able to get a
4341 graph of the current battery fill level, to get some idea about the
4342 status of the battery. The source package build and work just fine in
4343 Debian testing and stable (and probably oldstable too, but I have not
4344 tested). The default graph you get for that system look like this:
</p
>
4346 <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
>
4348 <p
>My plans for the future is to merge my old scripts into the
4349 battery-stats package, as my old scripts collected a lot more details
4350 about the battery. The scripts are merged into the upstream
4351 battery-stats git repository already, but I am not convinced they work
4352 yet, as I changed a lot of paths along the way. Will have to test a
4353 bit more before I make a new release.
</p
>
4355 <p
>I will also consider changing the file format slightly, as I
4356 suspect the way I combine several values into one field might make it
4357 impossible to know the type of the value when using it for processing
4358 and graphing.
</p
>
4360 <p
>If you would like I would like to keep an close eye on your laptop
4361 battery, check out the battery-stats package in
4362 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
4364 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4365 I would love some help to improve the system further.
</p
>
4370 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
4371 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
4372 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
4373 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
4374 <description><p
>Making packages for Debian requires quite a lot of attention to
4375 details. And one of the details is the content of the
4376 debian/copyright file, which should list all relevant licenses used by
4377 the code in the package in question, preferably in
4378 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
4379 readable DEP5 format
</a
>.
</p
>
4381 <p
>For large packages with lots of contributors it is hard to write
4382 and update this file manually, and if you get some detail wrong, the
4383 package is normally rejected by the ftpmasters. So getting it right
4384 the first time around get the package into Debian faster, and save
4385 both you and the ftpmasters some work.. Today, while trying to figure
4386 out what was wrong with
4387 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
4388 zfsonlinux copyright file
</a
>, I decided to spend some time on
4389 figuring out the options for doing this job automatically, or at least
4390 semi-automatically.
</p
>
4392 <p
>Lucikly, there are at least two tools available for generating the
4393 file based on the code in the source package,
4394 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
4395 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
4396 not sure which one of them came first, but both seem to be able to
4397 create a sensible draft file. As far as I can tell, none of them can
4398 be trusted to get the result just right, so the content need to be
4399 polished a bit before the file is OK to upload. I found the debmake
4401 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
4402 blog posts from
2014</a
>.
4404 <p
>To generate using debmake, use the -cc option:
4406 <p
><pre
>
4407 debmake -cc
> debian/copyright
4408 </pre
></p
>
4410 <p
>Note there are some problems with python and non-ASCII names, so
4411 this might not be the best option.
</p
>
4413 <p
>The cme option is based on a config parsing library, and I found
4415 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
4416 blog post from
2015</a
>. To generate using cme, use the
'update
4417 dpkg-copyright
' option:
4419 <p
><pre
>
4420 cme update dpkg-copyright
4421 </pre
></p
>
4423 <p
>This will create or update debian/copyright. The cme tool seem to
4424 handle UTF-
8 names better than debmake.
</p
>
4426 <p
>When the copyright file is created, I would also like some help to
4427 check if the file is correct. For this I found two good options,
4428 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
4429 to focus on license types and file matching, and is able to detect
4430 ineffective blocks in the copyright file. The latter reports missing
4431 copyright holders and years, but was confused by inconsistent license
4432 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
4433 fix all issues reported by them before uploading. But I do not know
4434 if the tools and the ftpmasters agree on what is important to fix in a
4435 copyright file, so the package might still be rejected.
</p
>
4437 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
4438 will read through the source and try to find all copyright statements.
4439 It is not comparing the result to the content of debian/copyright, but
4440 can be useful when verifying the content of the copyright file.
</p
>
4442 <p
>Are you aware of better tools in Debian to create and update
4443 debian/copyright file. Please let me know, or blog about it on
4444 planet.debian.org.
</p
>
4446 <p
>As usual, if you use Bitcoin and want to show your support of my
4447 activities, please send Bitcoin donations to my address
4448 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4450 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
4451 on how to use licensecheck and cdbs to create a draft copyright file
4453 <p
><pre
>
4454 licensecheck --copyright -r `find * -type f` | \
4455 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
4456 </pre
></p
>
4458 <p
>He mentioned that he normally check the generated file into the
4459 version control system to make it easier to discover license and
4460 copyright changes in the upstream source. I will try to do the same
4461 with my packages in the future.
</p
>
4463 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
4464 against using -quiet for new users, so I removed it from the proposed
4465 command line.
</p
>
4470 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
4471 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
4472 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
4473 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
4474 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
4475 is taking shape in Debian, and one provided feature is a very
4476 convenient way to tell you which package to install to make a given
4477 firmware file available when the kernel is looking for it. This can
4478 be done using apt-file too, but that is for someone else to blog
4481 <p
>Here is a small recipe to find the package with a given firmware
4482 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
4483 picked from the set of firmware announced using appstream in Debian
4484 unstable. In general you would be looking for the firmware requested
4485 by the kernel during kernel module loading. To find the package
4486 providing the example file, do like this:
</p
>
4488 <blockquote
><pre
>
4489 % apt install appstream
4493 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
4494 awk
'/Package:/ {print $
2}
'
4497 </pre
></blockquote
>
4499 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
4500 appstream wiki
</a
> page to learn how to embed the package metadata in
4501 a way appstream can use.
</p
>
4503 <p
>This same approach can be used to find any package supporting a
4504 given MIME type. This is very useful when you get a file you do not
4505 know how to handle. First find the mime type using
<tt
>file
4506 --mime-type
</tt
>, and next look up the package providing support for
4507 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
4508 and you can find all packages handling this type like this:
</p
>
4510 <blockquote
><pre
>
4511 % apt install appstream
4515 % appstreamcli what-provides mimetype image/svg+xml | \
4516 awk
'/Package:/ {print $
2}
'
4538 </pre
></blockquote
>
4540 <p
>I believe the MIME types are fetched from the desktop file for
4541 packages providing appstream metadata.
</p
>
4546 <title>Creepy, visualise geotagged social media information - nice free software
</title>
4547 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
4548 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
4549 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
4550 <description><p
>Most people seem not to realise that every time they walk around
4551 with the computerised radio beacon known as a mobile phone their
4552 position is tracked by the phone company and often stored for a long
4553 time (like every time a SMS is received or sent). And if their
4554 computerised radio beacon is capable of running programs (often called
4555 mobile apps) downloaded from the Internet, these programs are often
4556 also capable of tracking their location (if the app requested access
4557 during installation). And when these programs send out information to
4558 central collection points, the location is often included, unless
4559 extra care is taken to not send the location. The provided
4560 information is used by several entities, for good and bad (what is
4561 good and bad, depend on your point of view). What is certain, is that
4562 the private sphere and the right to free movement is challenged and
4563 perhaps even eradicated for those announcing their location this way,
4564 when they share their whereabouts with private and public
4567 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
4569 <p
>The phone company logs provide a register of locations to check out
4570 when one want to figure out what the tracked person was doing. It is
4571 unavailable for most of us, but provided to selected government
4572 officials, company staff, those illegally buying information from
4573 unfaithful servants and crackers stealing the information. But the
4574 public information can be collected and analysed, and a free software
4575 tool to do so is called
4576 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
4577 discovered it when I read
4578 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
4579 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
4580 November
2014, and decided to check if it was available in Debian.
4581 The python program was in Debian, but
4582 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
4583 Debian
</a
> was completely broken and practically unmaintained. I
4584 uploaded a new version which did not work quite right, but did not
4585 have time to fix it then. This Christmas I decided to finally try to
4586 get Creepy operational in Debian. Now a fixed version is available in
4587 Debian unstable and testing, and almost all Debian specific patches
4589 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
4591 <p
>The Creepy program visualises geolocation information fetched from
4592 Twitter, Instagram, Flickr and Google+, and allow one to get a
4593 complete picture of every social media message posted recently in a
4594 given area, or track the movement of a given individual across all
4595 these services. Earlier it was possible to use the search API of at
4596 least some of these services without identifying oneself, but these
4597 days it is impossible. This mean that to use Creepy, you need to
4598 configure it to log in as yourself on these services, and provide
4599 information to them about your search interests. This should be taken
4600 into account when using Creepy, as it will also share information
4601 about yourself with the services.
</p
>
4603 <p
>The picture above show the twitter messages sent from (or at least
4604 geotagged with a position from) the city centre of Oslo, the capital
4605 of Norway. One useful way to use Creepy is to first look at
4606 information tagged with an area of interest, and next look at all the
4607 information provided by one or more individuals who was in the area.
4608 I tested it by checking out which celebrity provide their location in
4609 twitter messages by checkout out who sent twitter messages near a
4610 Norwegian TV station, and next could track their position over time,
4611 making it possible to locate their home and work place, among other
4612 things. A similar technique have been
4613 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
4614 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
4615 tool to discover lying governments, and a useful tool to help people
4616 understand the value of the private information they provide to the
4619 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
4620 it depend on several python modules currently missing in Jessie (at
4621 least python-instagram, python-flickrapi and
4622 python-requests-toolbelt).
</p
>
4624 <p
>(I have uploaded
4625 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
4626 screenshots.debian.net
</a
> and licensed it under the same terms as the
4627 Creepy program in Debian.)
</p
>
4632 <title>Always download Debian packages using Tor - the simple recipe
</title>
4633 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
4634 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
4635 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
4636 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
4637 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
4638 that those listening on the Internet lines would have good reason to
4639 believe a computer have a given security hole
</a
> if it download a
4640 security fix from a Debian mirror. This is a good reason to always
4641 use encrypted connections to the Debian mirror, to make sure those
4642 listening do not know which IP address to attack. In August, Richard
4643 Hartmann observed that encryption was not enough, when it was possible
4644 to interfere download size to security patches or the fact that
4645 download took place shortly after a security fix was released, and
4646 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
4647 to always use Tor to download packages from the Debian mirror
</a
>. He
4648 was not the first to propose this, as the
4649 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
4650 package by Tim Retout already existed to make it easy to convince apt
4651 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
4652 aware of that package when I read the blog post from Richard.
</p
>
4654 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
4655 sysadmins, and he set up a Tor hidden service on one of the central
4656 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
4657 it possible to download packages directly between two tor nodes,
4658 making sure the network traffic always were encrypted.
</p
>
4660 <p
>Here is a short recipe for enabling this on your machine, by
4661 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
4662 urls with tor+http and tor+https, and using the hidden service instead
4663 of the official Debian mirror site. I recommend installing
4664 <tt
>etckeeper
</tt
> before you start to have a history of the changes
4665 done in /etc/.
</p
>
4667 <blockquote
><pre
>
4668 apt install apt-transport-tor
4669 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
4670 sed -i
's% http% tor+http%
' /etc/apt/sources.list
4671 </pre
></blockquote
>
4673 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
4674 the sed commands for these too. The sed command is assuming your are
4675 using the ftp.debian.org Debian mirror. Adjust the command (or just
4676 edit the file manually) to match your mirror.
</p
>
4678 <p
>This work in Debian Jessie and later. Note that tools like
4679 <tt
>apt-file
</tt
> only recently started using the apt transport
4680 system, and do not work with these tor+http URLs. For
4681 <tt
>apt-file
</tt
> you need the version currently in experimental,
4682 which need a recent apt version currently only in unstable. So if you
4683 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
4685 <p
>Another advantage from this change is that your machine will start
4686 using Tor regularly and at fairly random intervals (every time you
4687 update the package lists or upgrade or install a new package), thus
4688 masking other Tor traffic done from the same machine. Using Tor will
4689 become normal for the machine in question.
</p
>
4691 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
4692 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
4693 enabled. It would be great if it was the default on any Debian
4699 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
4700 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
4701 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
4702 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
4703 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
4704 call the car license plate numbers in those days. I would write the
4705 numbers down in my little book and compare notes with the other kids
4706 to see how many region codes we had seen and if we had seen some
4707 exotic or special region codes and numbers. It was a fun game to pass
4708 time, as we kids have plenty of it.
</p
>
4710 <p
>A few days I came across
4711 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
4712 project
</a
>, a free software project to automatically discover and
4713 report license plates in images and video streams, and provide the
4714 "car numbers
" in a machine readable format. I
've been looking for
4715 such system for a while now, because I believe it is a bad idea that the
4716 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
4717 number plate recognition
</a
> tool only is available in the hands of
4718 the powerful, and want it to be available also for the powerless to
4719 even the score when it comes to surveillance and sousveillance. I
4720 discovered the developer
4721 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
4722 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
4723 help him get it into shape to get the package uploaded into the Debian
4726 <p
>Today we finally managed to get the package into shape and uploaded
4727 it into Debian, where it currently
4728 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
4729 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
4731 <p
>I guess you are wondering why on earth such tool would be useful
4732 for the common folks, ie those not running a large government
4733 surveillance system? Well, I plan to put it in a computer on my bike
4734 and in my car, tracking the cars nearby and allowing me to be notified
4735 when number plates on my watch list are discovered. Another use case
4736 was suggested by a friend of mine, who wanted to set it up at his home
4737 to open the car port automatically when it discovered the plate on his
4738 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
4739 capable of placing his license plate number of a piece of cardboard to
4740 open his car port, men replied that it was always unlocked anyway. I
4741 guess for such use case it make sense. I am sure there are other use
4742 cases too, for those with imagination and a vision.
</p
>
4744 <p
>If you want to build your own version of the Debian package, check
4745 out the upstream git source and symlink ./distros/debian to ./debian/
4746 before running
"debuild
" to build the source. Or wait a bit until the
4747 package show up in unstable.
</p
>
4752 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
4753 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
4754 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
4755 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
4756 <description><p
>Around three years ago, I created
4757 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
4758 system
</a
> to get a more practical solution in Debian for handing
4759 hardware related packages. A GUI system in the isenkram package will
4760 present a pop-up dialog when some hardware dongle supported by
4761 relevant packages in Debian is inserted into the machine. The same
4762 lookup mechanism to detect packages is available as command line
4763 tools in the isenkram-cli package. In addition to mapping hardware,
4764 it will also map kernel firmware files to packages and make it easy to
4765 install needed firmware packages automatically. The key for this
4766 system to work is a good way to map hardware to packages, in other
4767 words, allow packages to announce what hardware they will work
4770 <p
>I started by providing data files in the isenkram source, and
4771 adding code to download the latest version of these data files at run
4772 time, to ensure every user had the most up to date mapping available.
4773 I also added support for storing the mapping in the Packages file in
4774 the apt repositories, but did not push this approach because while I
4775 was trying to figure out how to best store hardware/package mappings,
4776 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
4777 appstream system
</a
> was announced. I got in touch and suggested to
4778 add the hardware mapping into that data set to be able to use
4779 appstream as a data source, and this was accepted at least for the
4780 Debian version of appstream.
</p
>
4782 <p
>A few days ago using appstream in Debian for this became possible,
4783 and today I uploaded a new version
0.20 of isenkram adding support for
4784 appstream as a data source for mapping hardware to packages. The only
4785 package so far using appstream to announce its hardware support is my
4786 pymissile package. I got help from Matthias Klumpp with figuring out
4787 how do add the required
4788 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
4789 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
4790 this content:
</p
>
4792 <blockquote
><pre
>
4793 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
4794 &lt;component
&gt;
4795 &lt;id
&gt;pymissile
&lt;/id
&gt;
4796 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
4797 &lt;name
&gt;pymissile
&lt;/name
&gt;
4798 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
4799 &lt;description
&gt;
4801 Pymissile provides a curses interface to control an original
4802 Marks and Spencer / Striker USB Missile Launcher, as well as a
4803 motion control script to allow a webcamera to control the
4806 &lt;/description
&gt;
4807 &lt;provides
&gt;
4808 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
4809 &lt;/provides
&gt;
4810 &lt;/component
&gt;
4811 </pre
></blockquote
>
4813 <p
>The key for isenkram is the component/provides/modalias value,
4814 which is a glob style match rule for hardware specific strings
4815 (modalias strings) provided by the Linux kernel. In this case, it
4816 will map to all USB devices with vendor code
1130 and product code
4819 <p
>Note, it is important that the license of all the metadata files
4820 are compatible to have permissions to aggregate them into archive wide
4821 appstream files. Matthias suggested to use MIT or BSD licenses for
4822 these files. A challenge is figuring out a good id for the data, as
4823 it is supposed to be globally unique and shared across distributions
4824 (in other words, best to coordinate with upstream what to use). But
4825 it can be changed later or, so we went with the package name as
4826 upstream for this project is dormant.
</p
>
4828 <p
>To get the metadata file installed in the correct location for the
4829 mirror update scripts to pick it up and include its content the
4830 appstream data source, the file must be installed in the binary
4831 package under /usr/share/appdata/. I did this by adding the following
4832 line to debian/pymissile.install:
</p
>
4834 <blockquote
><pre
>
4835 debian/pymissile.metainfo.xml usr/share/appdata
4836 </pre
></blockquote
>
4838 <p
>With that in place, the command line tool isenkram-lookup will list
4839 all packages useful on the current computer automatically, and the GUI
4840 pop-up handler will propose to install the package not already
4841 installed if a hardware dongle is inserted into the machine in
4844 <p
>Details of the modalias field in appstream is available from the
4845 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
4847 <p
>To locate the modalias values of all hardware present in a machine,
4848 try running this command on the command line:
</p
>
4850 <blockquote
><pre
>
4851 cat $(find /sys/devices/|grep modalias)
4852 </pre
></blockquote
>
4854 <p
>To learn more about the isenkram system, please check out
4855 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
4856 blog posts tagged isenkram
</a
>.
</p
>
4861 <title>The GNU General Public License is not magic pixie dust
</title>
4862 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
4863 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
4864 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
4865 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
4866 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
4867 GPL is not magic pixie dust
</a
>" explain the importance of making sure
4868 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
4869 I quote the blog post from Paul in full here with his permission:
<p
>
4873 <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
>
4876 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
4878 The first step is to choose a
4879 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
4882 The next step is, when someone fails to follow that copyleft license,
4883 <b
>it must be enforced
</b
><br/
>
4885 and its a simple fact of our modern society that such type of
4888 is incredibly expensive to do and incredibly difficult to do.
4891 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
4892 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
4893 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
4894 0x57</a
></small
></p
>
4896 <p
>As the Debian Website
4897 <a href=
"https://bugs.debian.org/
794116">used
</a
>
4898 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
4899 imply, public domain and permissively licensed software can lead to
4900 the production of more proprietary software as people discover useful
4901 software, extend it and or incorporate it into their hardware or
4902 software products. Copyleft licenses such as the GNU GPL were created
4903 to close off this avenue to the production of proprietary software but
4904 such licenses are not enough. With the ongoing adoption of Free
4905 Software by individuals and groups, inevitably the community
's
4906 expectations of license compliance are violated, usually out of
4907 ignorance of the way Free Software works, but not always. As Karen
4908 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
4909 Freedom
">FaiF
</a
>
4910 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
4911 copyleft is nothing if no-one is willing and able to stand up in court
4912 to protect it. The reality of today
's world is that legal
4913 representation is expensive, difficult and time consuming. With
4914 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
4915 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
4916 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
4917 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
4918 of the Linux project, Debian and other groups against GPL violations.
4919 In March the SFC supported a
4920 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
4921 by Christoph Hellwig
</a
> against VMware for refusing to
4922 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
4923 with the GPL
</a
> in relation to their use of parts of the Linux
4924 kernel. Since then two of their sponsors pulled corporate funding and
4926 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
4927 or cancelled their talks
</a
>. As a result they have decided to rely
4928 less on corporate funding and more on the broad community of
4929 individuals who support Free Software and copyleft. So the SFC has
4930 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
4931 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
4932 a community of folks who stand up for copyleft and the GPL by
4933 supporting their work on promoting and supporting copyleft and Free
4936 <p
>If you support Free Software,
4937 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
4938 what the SFC do, agree with their
4939 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
4940 principles
</a
>, are happy about their
4941 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
4942 work on a project that is an SFC
4943 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
4944 just want to stand up for copyleft, please join
4945 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
4946 Allan Webber
</a
>,
4947 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
4949 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
4950 Bacon
</a
>, myself and
4951 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
4953 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
4954 next week your donation will be
4955 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
4956 by an anonymous donor. Please also consider asking your employer to
4957 match your donation or become a sponsor of SFC. Don
't forget to
4958 spread the word about your support for SFC via email, your blog and or
4959 social media accounts.
</p
>
4963 <p
>I agree with Paul on this topic and just signed up as a Supporter
4964 of Software Freedom Conservancy myself. Perhaps you should be a
4965 supporter too?
</p
>
4970 <title>PGP key transition statement for key EE4E02F9
</title>
4971 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
4972 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
4973 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
4974 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
4975 set it up properly. I wanted to generate it offline and have it
4976 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
4977 smart card
</a
> for daily use, and learning how to do it and finding
4978 time to sit down with an offline machine almost took forever. But
4979 finally I
've been able to complete the process, and have now moved
4980 from my old GPG key to a new GPG key. See
4981 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
4982 full transition statement, signed with both my old and new key
</a
> for
4983 the details. This is my new key:
</p
>
4986 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
4987 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
4988 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
4989 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
4990 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
4991 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
4992 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
4995 <p
>The key can be downloaded from the OpenPGP key servers, signed by
4996 my old key.
</p
>
4998 <p
>If you signed my old key
4999 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
5000 I
'd very much appreciate a signature on my new key, details and
5001 instructions in the transition statement. I m happy to reciprocate if
5002 you have a similarly signed transition statement to present.
</p
>
5007 <title>The life and death of a laptop battery
</title>
5008 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
5009 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
5010 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
5011 <description><p
>When I get a new laptop, the battery life time at the start is OK.
5012 But this do not last. The last few laptops gave me a feeling that
5013 within a year, the life time is just a fraction of what it used to be,
5014 and it slowly become painful to use the laptop without power connected
5015 all the time. Because of this, when I got a new Thinkpad X230 laptop
5016 about two years ago, I decided to monitor its battery state to have
5017 more hard facts when the battery started to fail.
</p
>
5019 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
5021 <p
>First I tried to find a sensible Debian package to record the
5022 battery status, assuming that this must be a problem already handled
5023 by someone else. I found
5024 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
5025 which collects statistics from the battery, but it was completely
5026 broken. I sent a few suggestions to the maintainer, but decided to
5027 write my own collector as a shell script while I waited for feedback
5029 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
5030 blog post about the battery development on a MacBook Air
</a
> I also
5032 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
5033 available in Debian.
</p
>
5035 <p
>I started my collector
2013-
07-
15, and it has been collecting
5036 battery stats ever since. Now my
5037 /var/log/hjemmenett-battery-status.log file contain around
115,
000
5038 measurements, from the time the battery was working great until now,
5039 when it is unable to charge above
7% of original capacity. My
5040 collector shell script is quite simple and look like this:
</p
>
5045 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
5047 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
5048 logfile=/var/log/hjemmenett-battery-status.log
5050 files=
"manufacturer model_name technology serial_number \
5051 energy_full energy_full_design energy_now cycle_count status
"
5053 if [ ! -e
"$logfile
" ] ; then
5055 printf
"timestamp,
"
5057 printf
"%s,
" $f
5060 )
> "$logfile
"
5064 # Print complete message in one echo call, to avoid race condition
5065 # when several log processes run in parallel.
5066 msg=$(printf
"%s,
" $(date +%s); \
5067 for f in $files; do \
5068 printf
"%s,
" $(cat $f); \
5070 echo
"$msg
"
5073 cd /sys/class/power_supply
5076 (cd $bat
&& log_battery
>> "$logfile
")
5080 <p
>The script is called when the power management system detect a
5081 change in the power status (power plug in or out), and when going into
5082 and out of hibernation and suspend. In addition, it collect a value
5083 every
10 minutes. This make it possible for me know when the battery
5084 is discharging, charging and how the maximum charge change over time.
5085 The code for the Debian package
5086 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
5087 available on github
</a
>.
</p
>
5089 <p
>The collected log file look like this:
</p
>
5092 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
5093 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
5095 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
5096 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
5099 <p
>I wrote a small script to create a graph of the charge development
5100 over time. This graph depicted above show the slow death of my laptop
5103 <p
>But why is this happening? Why are my laptop batteries always
5104 dying in a year or two, while the batteries of space probes and
5105 satellites keep working year after year. If we are to believe
5106 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
5107 University
</a
>, the cause is me charging the battery whenever I have a
5108 chance, and the fix is to not charge the Lithium-ion batteries to
100%
5109 all the time, but to stay below
90% of full charge most of the time.
5110 I
've been told that the Tesla electric cars
5111 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
5112 the charge of their batteries to
80%
</a
>, with the option to charge to
5113 100% when preparing for a longer trip (not that I would want a car
5114 like Tesla where rights to privacy is abandoned, but that is another
5115 story), which I guess is the option we should have for laptops on
5116 Linux too.
</p
>
5118 <p
>Is there a good and generic way with Linux to tell the battery to
5119 stop charging at
80%, unless requested to charge to
100% once in
5120 preparation for a longer trip? I found
5121 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
5122 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
5123 80%
</a
>, but could not get it to work (kernel module refused to
5126 <p
>I wonder why the battery capacity was reported to be more than
100%
5127 at the start. I also wonder why the
"full capacity
" increases some
5128 times, and if it is possible to repeat the process to get the battery
5129 back to design capacity. And I wonder if the discharge and charge
5130 speed change over time, or if this stay the same. I did not yet try
5131 to write a tool to calculate the derivative values of the battery
5132 level, but suspect some interesting insights might be learned from
5135 <p
>Update
2015-
09-
24: I got a tip to install the packages
5136 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
5137 packages instead of the tp-smapi-dkms package I had tried to use
5138 initially, and use
'tlp setcharge
40 80' to change when charging start
5139 and stop. I
've done so now, but expect my existing battery is toast
5140 and need to be replaced. The proposal is unfortunately Thinkpad
5146 <title>New laptop - some more clues and ideas based on feedback
</title>
5147 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
5148 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
5149 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
5150 <description><p
>Several people contacted me after my previous blog post about my
5151 need for a new laptop, and provided very useful feedback. I wish to
5152 thank every one of these. Several pointed me to the possibility of
5153 fixing my X230, and I am already in the process of getting Lenovo to
5154 do so thanks to the on site, next day support contract covering the
5155 machine. But the battery is almost useless (I expect to replace it
5156 with a non-official battery) and I do not expect the machine to live
5157 for many more years, so it is time to plan its replacement. If I did
5158 not have a support contract, it was suggested to find replacement parts
5159 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
5160 might present a language barrier as I do not understand French.
</p
>
5162 <p
>One tip I got was to use the
5163 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
5164 compare laptop models. It seem to have more models available than
5165 prisjakt.no. Another tip I got from someone I know have similar
5166 keyboard preferences was that the HP EliteBook
840 keyboard is not
5167 very good, and this matches my experience with earlier EliteBook
5168 keyboards I tested. Because of this, I will not consider it any further.
5170 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
5171 newest Thinkpad X model. The keyboard reintroduces mouse buttons
5172 (which is missing from the X240), and is working fairly well with
5173 Debian Sid/Unstable according to
5174 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
5175 got on the keyboard quality are not consistent. Some say the keyboard
5176 is good, others say it is ok, while others say it is not very good.
5177 Those with experience from X41 and and X60 agree that the X250
5178 keyboard is not as good as those trusty old laptops, and suggest I
5179 keep and fix my X230 instead of upgrading, or get a used X230 to
5180 replace it. I
'm also told that the X250 lack leds for caps lock, disk
5181 activity and battery status, which is very convenient on my X230. I
'm
5182 also told that the CPU fan is running very often, making it a bit
5183 noisy. In any case, the X250 do not work out of the box with Debian
5184 Stable/Jessie, one of my requirements.
</p
>
5186 <p
>I have also gotten a few vendor proposals, one was
5187 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
5188 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
5189 The latter look very attractive to me.
</p
>
5191 <p
>Again, thank you all for the very useful feedback. It help a lot
5192 as I keep looking for a replacement.
</p
>
5194 <p
>Update
2015-
07-
06: I was recommended to check out the
5195 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
5197 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
5198 thinkpad X models
</a
>, and provide one year warranty.
</p
>
5203 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
5204 <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>
5205 <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>
5206 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
5207 <description><p
>My primary work horse laptop is failing, and will need a
5208 replacement soon. The left
5 cm of the screen on my Thinkpad X230
5209 started flickering yesterday, and I suspect the cause is a broken
5210 cable, as changing the angle of the screen some times get rid of the
5211 flickering.
</p
>
5213 <p
>My requirements have not really changed since I bought it, and is
5215 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
5216 described them in
2013</a
>. The last time I bought a laptop, I had
5218 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
5219 where I could select at least a few of the requirements (mouse pin,
5220 wifi, weight) and go through the rest manually. Three button mouse
5221 and a good keyboard is not available as an option, and all the three
5222 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
5223 G2) lack three mouse buttons). It is also unclear to me how good the
5224 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5225 the keyboard, even if the quality and robustness in the X series have
5226 deteriorated since X41.
</p
>
5228 <p
>I wonder how I can find a sensible laptop when none of the options
5229 seem sensible to me? Are there better services around to search the
5230 set of available laptops for features? Please send me an email if you
5231 have suggestions.
</p
>
5233 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
5234 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
5235 of endorsed hardware
</a
>, which is useful background information.
</p
>
5240 <title>How to stay with sysvinit in Debian Jessie
</title>
5241 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
5242 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
5243 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
5244 <description><p
>By now, it is well known that Debian Jessie will not be using
5245 sysvinit as its boot system by default. But how can one keep using
5246 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5248 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
5249 Schubert
</a
> and
5250 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
5253 <p
>If you already are using Wheezy and want to upgrade to Jessie and
5254 keep sysvinit as your boot system, create a file
5255 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
5256 you upgrade:
</p
>
5258 <p
><blockquote
><pre
>
5259 Package: systemd-sysv
5260 Pin: release o=Debian
5262 </pre
></blockquote
><p
>
5264 <p
>This file content will tell apt and aptitude to not consider
5265 installing systemd-sysv as part of any installation and upgrade
5266 solution when resolving dependencies, and thus tell it to avoid
5267 systemd as a default boot system. The end result should be that the
5268 upgraded system keep using sysvinit.
</p
>
5270 <p
>If you are installing Jessie for the first time, there is no way to
5271 get sysvinit installed by default (debootstrap used by
5272 debian-installer have no option for this), but one can tell the
5273 installer to switch to sysvinit before the first boot. Either by
5274 using a kernel argument to the installer, or by adding a line to the
5275 preseed file used. First, the kernel command line argument:
5277 <p
><blockquote
><pre
>
5278 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
5279 </pre
></blockquote
><p
>
5281 <p
>Next, the line to use in a preseed file:
</p
>
5283 <p
><blockquote
><pre
>
5284 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5285 </pre
></blockquote
><p
>
5287 <p
>One can of course also do this after the first boot by installing
5288 the sysvinit-core package.
</p
>
5290 <p
>I recommend only using sysvinit if you really need it, as the
5291 sysvinit boot sequence in Debian have several hardware specific bugs
5292 on Linux caused by the fact that it is unpredictable when hardware
5293 devices show up during boot. But on the other hand, the new default
5294 boot system still have a few rough edges I hope will be fixed before
5295 Jessie is released.
</p
>
5297 <p
>Update
2014-
11-
26: Inspired by
5298 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
5299 blog post by Torsten Glaser
</a
>, added --purge to the preseed
5305 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
5306 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
5307 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
5308 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
5309 <description><p
>The right to communicate with your friends and family in private,
5310 without anyone snooping, is a right every citicen have in a liberal
5311 democracy. But this right is under serious attack these days.
</p
>
5313 <p
>A while back it occurred to me that one way to make the dragnet
5314 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5315 the whisleblower Snowden) more expensive for Internet email,
5316 is to deliver all email using SMTP via Tor. Such SMTP option would be
5317 a nice addition to the FreedomBox project if we could send email
5318 between FreedomBox machines without leaking metadata about the emails
5319 to the people peeking on the wire. I
5320 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
5321 this on the FreedomBox project mailing list in October
</a
> and got a
5322 lot of useful feedback and suggestions. It also became obvious to me
5323 that this was not a novel idea, as the same idea was tested and
5324 documented by Johannes Berg as early as
2006, and both
5325 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
5326 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
5327 propose a similar method / protocol to pass emails between users.
</p
>
5329 <p
>To implement such system one need to set up a Tor hidden service
5330 providing the SMTP protocol on port
25, and use email addresses
5331 looking like username@hidden-service-name.onion. With such addresses
5332 the connections to port
25 on hidden-service-name.onion using Tor will
5333 go to the correct SMTP server. To do this, one need to configure the
5334 Tor daemon to provide the hidden service and the mail server to accept
5335 emails for this .onion domain. To learn more about Exim configuration
5336 in Debian and test the design provided by Johannes Berg in his FAQ, I
5337 set out yesterday to create a Debian package for making it trivial to
5338 set up such SMTP over Tor service based on Debian. Getting it to work
5339 were fairly easy, and
5340 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
5341 source code for the Debian package
</a
> is available from github. I
5342 plan to move it into Debian if further testing prove this to be a
5343 useful approach.
</p
>
5345 <p
>If you want to test this, set up a blank Debian machine without any
5346 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
5347 get rid of exim4). Install tor, clone the git repository mentioned
5348 above, build the deb and install it on the machine. Next, run
5349 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
5350 the instructions to get the service up and running. Restart tor and
5351 exim when it is done, and test mail delivery using swaks like
5354 <p
><blockquote
><pre
>
5355 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5356 --to fbx@dutlqrrmjhtfa3vp.onion
5357 </pre
></blockquote
></p
>
5359 <p
>This will test the SMTP delivery using tor. Replace the email
5360 address with your own address to test your server. :)
</p
>
5362 <p
>The setup procedure is still to complex, and I hope it can be made
5363 easier and more automatic. Especially the tor setup need more work.
5364 Also, the package include a tor-smtp tool written in C, but its task
5365 should probably be rewritten in some script language to make the deb
5366 architecture independent. It would probably also make the code easier
5367 to review. The tor-smtp tool currently need to listen on a socket for
5368 exim to talk to it and is started using xinetd. It would be better if
5369 no daemon and no socket is needed. I suspect it is possible to get
5370 exim to run a command line tool for delivery instead of talking to a
5371 socket, and hope to figure out how in a future version of this
5374 <p
>Until I wipe my test machine, I can be reached using the
5375 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
5376 SMTorP. :)
</p
>
5381 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
5382 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
5383 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
5384 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
5385 <description><p
>If you ever had to moderate a mailman list, like the ones on
5386 alioth.debian.org, you know the web interface is fairly slow to
5387 operate. First you visit one web page, enter the moderation password
5388 and get a new page shown with a list of all the messages to moderate
5389 and various options for each email address. This take a while for
5390 every list you moderate, and you need to do it regularly to do a good
5391 job as a list moderator. But there is a quick alternative,
5392 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
5393 listadmin program
</a
>. It allow you to check lists for new messages
5394 to moderate in a fraction of a second. Here is a test run on two
5395 lists I recently took over:
</p
>
5397 <p
><blockquote
><pre
>
5398 % time listadmin xiph
5399 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5400 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5406 </pre
></blockquote
></p
>
5408 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
5409 there are no message in the moderation queue. Every morning I
5410 currently moderate
68 mailman lists, and it normally take around two
5411 minutes. When I took over the two pkg-xiph lists above a few days
5412 ago, there were
400 emails waiting in the moderator queue. It took me
5413 less than
15 minutes to process them all using the listadmin
5416 <p
>If you install
5417 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
5418 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
5419 with content like this, the moderation task is a breeze:
</p
>
5421 <p
><blockquote
><pre
>
5422 username username@example.org
5425 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
5428 adminurl https://{domain}/mailman/admindb/{list}
5429 mailman-list@lists.example.com
5432 other-list@otherserver.example.org
5433 </pre
></blockquote
></p
>
5435 <p
>There are other options to set as well. Check the manual page to
5436 learn the details.
</p
>
5438 <p
>If you are forced to moderate lists on a mailman installation where
5439 the SSL certificate is self signed or not properly signed by a
5440 generally accepted signing authority, you can set a environment
5441 variable when calling listadmin to disable SSL verification:
</p
>
5443 <p
><blockquote
><pre
>
5444 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
5445 </pre
></blockquote
></p
>
5447 <p
>If you want to moderate a subset of the lists you take care of, you
5448 can provide an argument to the listadmin script like I do in the
5449 initial screen dump (the xiph argument). Using an argument, only
5450 lists matching the argument string will be processed. This make it
5451 quick to accept messages if you notice the moderation request in your
5454 <p
>Without the listadmin program, I would never be the moderator of
68
5455 mailing lists, as I simply do not have time to spend on that if the
5456 process was any slower. The listadmin program have saved me hours of
5457 time I could spend elsewhere over the years. It truly is nice free
5460 <p
>As usual, if you use Bitcoin and want to show your support of my
5461 activities, please send Bitcoin donations to my address
5462 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5464 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
5465 configuration example. Also, I
've been told that the
5466 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
5472 <title>Debian Jessie, PXE and automatic firmware installation
</title>
5473 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
5474 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
5475 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
5476 <description><p
>When PXE installing laptops with Debian, I often run into the
5477 problem that the WiFi card require some firmware to work properly.
5478 And it has been a pain to fix this using preseeding in Debian.
5479 Normally something more is needed. But thanks to
5480 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
5481 package
</a
> and its recent tasksel extension, it has now become easy
5482 to do this using simple preseeding.
</p
>
5484 <p
>The isenkram-cli package provide tasksel tasks which will install
5485 firmware for the hardware found in the machine (actually, requested by
5486 the kernel modules for the hardware). (It can also install user space
5487 programs supporting the hardware detected, but that is not the focus
5488 of this story.)
</p
>
5490 <p
>To get this working in the default installation, two preeseding
5491 values are needed. First, the isenkram-cli package must be installed
5492 into the target chroot (aka the hard drive) before tasksel is executed
5493 in the pkgsel step of the debian-installer system. This is done by
5494 preseeding the base-installer/includes debconf value to include the
5495 isenkram-cli package. The package name is next passed to debootstrap
5496 for installation. With the isenkram-cli package in place, tasksel
5497 will automatically use the isenkram tasks to detect hardware specific
5498 packages for the machine being installed and install them, because
5499 isenkram-cli contain tasksel tasks.
</p
>
5501 <p
>Second, one need to enable the non-free APT repository, because
5502 most firmware unfortunately is non-free. This is done by preseeding
5503 the apt-mirror-setup step. This is unfortunate, but for a lot of
5504 hardware it is the only option in Debian.
</p
>
5506 <p
>The end result is two lines needed in your preseeding file to get
5507 firmware installed automatically by the installer:
</p
>
5509 <p
><blockquote
><pre
>
5510 base-installer base-installer/includes string isenkram-cli
5511 apt-mirror-setup apt-setup/non-free boolean true
5512 </pre
></blockquote
></p
>
5514 <p
>The current version of isenkram-cli in testing/jessie will install
5515 both firmware and user space packages when using this method. It also
5516 do not work well, so use version
0.15 or later. Installing both
5517 firmware and user space packages might give you a bit more than you
5518 want, so I decided to split the tasksel task in two, one for firmware
5519 and one for user space programs. The firmware task is enabled by
5520 default, while the one for user space programs is not. This split is
5521 implemented in the package currently in unstable.
</p
>
5523 <p
>If you decide to give this a go, please let me know (via email) how
5524 this recipe work for you. :)
</p
>
5526 <p
>So, I bet you are wondering, how can this work. First and
5527 foremost, it work because tasksel is modular, and driven by whatever
5528 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
5529 isenkram-cli package place two files for tasksel to find. First there
5530 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
5532 <p
><blockquote
><pre
>
5533 Task: isenkram-packages
5535 Description: Hardware specific packages (autodetected by isenkram)
5536 Based on the detected hardware various hardware specific packages are
5538 Test-new-install: show show
5540 Packages: for-current-hardware
5542 Task: isenkram-firmware
5544 Description: Hardware specific firmware packages (autodetected by isenkram)
5545 Based on the detected hardware various hardware specific firmware
5546 packages are proposed.
5547 Test-new-install: mark show
5549 Packages: for-current-hardware-firmware
5550 </pre
></blockquote
></p
>
5552 <p
>The key parts are Test-new-install which indicate how the task
5553 should be handled and the Packages line referencing to a script in
5554 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
5555 list of packages to install. The for-current-hardware-firmware script
5556 look like this to list relevant firmware for the machine:
5558 <p
><blockquote
><pre
>
5561 PATH=/usr/sbin:$PATH
5563 isenkram-autoinstall-firmware -l
5564 </pre
></blockquote
></p
>
5566 <p
>With those two pieces in place, the firmware is installed by
5567 tasksel during the normal d-i run. :)
</p
>
5569 <p
>If you want to test what tasksel will install when isenkram-cli is
5570 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
5571 --new-install
</tt
> to get the list of packages that tasksel would
5574 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
5575 pilots in testing this feature, as isenkram is used there now to
5576 install firmware, replacing the earlier scripts.
</p
>
5581 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
5582 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
5583 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
5584 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
5585 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
5586 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
5587 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
5588 on a screen normally showing the bread types and prizes:
</p
>
5590 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
5592 <p
>If it had booted as it was supposed to, I would never had known
5593 about this hidden Linux installation. It is interesting what
5594 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
5599 <title>New lsdvd release version
0.17 is ready
</title>
5600 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
5601 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
5602 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
5603 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
5604 got a new set of developers a few weeks ago, after the original
5605 developer decided to step down and pass the project to fresh blood.
5606 This project is now maintained by Petter Reinholdtsen and Steve
5609 <p
>I just wrapped up
5610 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
5611 new lsdvd release
</a
>, available in git or from
5612 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
5613 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
5618 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
5619 <li
>Check for garbage in the program chains, which indicate that a track is
5620 non-existant, to work around additional copy protection
</li
>
5621 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
5622 <li
>Fix pallete display of first entry
</li
>
5623 <li
>Fix include orders
</li
>
5624 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
5625 <li
>Fix the chapter count
</li
>
5626 <li
>Make sure the array size and the array limit used when initialising
5627 the palette size is the same.
</li
>
5628 <li
>Fix array printing.
</li
>
5629 <li
>Correct subsecond calculations.
</li
>
5630 <li
>Add sector information to the output format.
</li
>
5631 <li
>Clean up code to be closer to ANSI C and compile without warnings
5632 with more GCC compiler warnings.
</li
>
5636 <p
>This change bring together patches for lsdvd in use in various
5637 Linux and Unix distributions, as well as patches submitted to the
5638 project the last nine years. Please check it out. :)
</p
>
5643 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
5644 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
5645 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
5646 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
5647 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
5648 project
</a
> provide a Linux solution for schools, including a
5649 powerful desktop with education software, a central server providing
5650 web pages, user database, user home directories, central login and PXE
5651 boot of both clients without disk and the installation to install Debian
5652 Edu on machines with disk (and a few other services perhaps to small
5653 to mention here). We in the Debian Edu team are currently working on
5654 the Jessie based version, trying to get everything in shape before the
5655 freeze, to avoid having to maintain our own package repository in the
5657 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
5658 status
</a
> can be seen on the Debian wiki, and there is still heaps of
5659 work left. Some fatal problems block testing, breaking the installer,
5660 but it is possible to work around these to get anyway. Here is a
5661 recipe on how to get the installation limping along.
</p
>
5663 <p
>First, download the test ISO via
5664 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
5665 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
5667 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
5668 The ISO build was broken on Tuesday, so we do not get a new ISO every
5669 12 hours or so, but thankfully the ISO we already got we are able to
5670 install with some tweaking.
</p
>
5672 <p
>When you get to the Debian Edu profile question, go to tty2
5673 (use Alt-Ctrl-F2), run
</p
>
5675 <p
><blockquote
><pre
>
5676 nano /usr/bin/edu-eatmydata-install
5677 </pre
></blockquote
></p
>
5679 <p
>and add
'exit
0' as the second line, disabling the eatmydata
5680 optimization. Return to the installation, select the profile you want
5681 and continue. Without this change, exim4-config will fail to install
5682 due to a known bug in eatmydata.
</p
>
5684 <p
>When you get the grub question at the end, answer /dev/sda (or if
5685 this do not work, figure out what your correct value would be. All my
5686 test machines need /dev/sda, so I have no advice if it do not fit
5687 your need.
</p
>
5689 <p
>If you installed a profile including a graphical desktop, log in as
5690 root after the initial boot from hard drive, and install the
5691 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
5692 or mate. If you want several desktop options, install more than one
5693 metapackage. Once this is done, reboot and you should have a working
5694 graphical login screen. This workaround should no longer be needed
5695 once the education-tasks package version
1.801 enter testing in two
5698 <p
>I believe the ISO build will start working on two days when the new
5699 tasksel package enter testing and Steve McIntyre get a chance to
5700 update the debian-cd git repository. The eatmydata, grub and desktop
5701 issues are already fixed in unstable and testing, and should show up
5702 on the ISO as soon as the ISO build start working again. Well the
5703 eatmydata optimization is really just disabled. The proper fix
5704 require an upload by the eatmydata maintainer applying the patch
5705 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
5706 The rest have proper fixes in unstable.
</p
>
5708 <p
>I hope this get you going with the installation testing, as we are
5709 quickly running out of time trying to get our Jessie based
5710 installation ready before the distribution freeze in a month.
</p
>
5715 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
5716 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
5717 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
5718 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
5719 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
5720 to handle my fairly large DVD collection. It is a nice command line
5721 tool to get details about a DVD, like title, tracks, track length,
5722 etc, in XML, Perl or human readable format. But lsdvd have not seen
5723 any new development since
2006 and had a few irritating bugs affecting
5724 its use with some DVDs. Upstream seemed to be dead, and in January I
5725 sent a small probe asking for a version control repository for the
5726 project, without any reply. But I use it regularly and would like to
5727 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
5728 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
5729 the project admin, and after getting a reply from him explaining that
5730 he was no longer interested in the project, I asked if I could take
5731 over. And yesterday, I became project admin.
</p
>
5733 <p
>I
've been in touch with a Gentoo developer and the Debian
5734 maintainer interested in joining forces to maintain the upstream
5735 project, and I hope we can get a new release out fairly quickly,
5736 collecting the patches spread around on the internet into on place.
5737 I
've added the relevant Debian patches to the freshly created git
5738 repository, and expect the Gentoo patches to make it too. If you got
5739 a DVD collection and care about command line tools, check out
5740 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
5741 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
5742 list
</a
>. :)
</p
>
5747 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
5748 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
5749 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
5750 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
5751 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
5752 a lot quicker. When we install more than
2000 packages in
5753 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
5754 tasksel in the installer, unpacking the binary packages take forever.
5755 A part of the slow I/O issue was discussed in
5756 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
5757 much file system sync-ing done by dpkg, which is the package
5758 responsible for unpacking the binary packages. Other parts (like code
5759 executed by postinst scripts) might also sync to disk during
5760 installation. All this sync-ing to disk do not really make sense to
5761 me. If the machine crash half-way through, I start over, I do not try
5762 to salvage the half installed system. So the failure sync-ing is
5763 supposed to protect against, hardware or system crash, is not really
5764 relevant while the installer is running.
</p
>
5766 <p
>A few days ago, I thought of a way to get rid of all the file
5767 system sync()-ing in a fairly non-intrusive way, without the need to
5768 change the code in several packages. The idea is not new, but I have
5769 not heard anyone propose the approach using dpkg-divert before. It
5770 depend on the small and clever package
5771 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
5772 uses LD_PRELOAD to replace the system functions for syncing data to
5773 disk with functions doing nothing, thus allowing programs to live
5774 dangerous while speeding up disk I/O significantly. Instead of
5775 modifying the implementation of dpkg, apt and tasksel (which are the
5776 packages responsible for selecting, fetching and installing packages),
5777 it occurred to me that we could just divert the programs away, replace
5778 them with a simple shell wrapper calling
5779 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
5780 Two days ago I decided to test the idea, and wrapped up a simple
5781 implementation for the Debian Edu udeb.
</p
>
5783 <p
>The effect was stunning. In my first test it reduced the running
5784 time of the pkgsel step (installing tasks) from
64 to less than
44
5785 minutes (
20 minutes shaved off the installation) on an old Dell
5786 Latitude D505 machine. I am not quite sure what the optimised time
5787 would have been, as I messed up the testing a bit, causing the debconf
5788 priority to get low enough for two questions to pop up during
5789 installation. As soon as I saw the questions I moved the installation
5790 along, but do not know how long the question were holding up the
5791 installation. I did some more measurements using Debian Edu Jessie,
5792 and got these results. The time measured is the time stamp in
5793 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
5794 "pkgsel: finishing up
" lines, if you want to do the same measurement
5795 yourself. In Debian Edu, the tasksel dialog do not show up, and the
5796 timing thus do not depend on how quickly the user handle the tasksel
5799 <p
><table
>
5802 <th
>Machine/setup
</th
>
5803 <th
>Original tasksel
</th
>
5804 <th
>Optimised tasksel
</th
>
5805 <th
>Reduction
</th
>
5809 <td
>Latitude D505 Main+LTSP LXDE
</td
>
5810 <td
>64 min (
07:
46-
08:
50)
</td
>
5811 <td
><44 min (
11:
27-
12:
11)
</td
>
5812 <td
>>20 min
18%
</td
>
5816 <td
>Latitude D505 Roaming LXDE
</td
>
5817 <td
>57 min (
08:
48-
09:
45)
</td
>
5818 <td
>34 min (
07:
43-
08:
17)
</td
>
5819 <td
>23 min
40%
</td
>
5823 <td
>Latitude D505 Minimal
</td
>
5824 <td
>22 min (
10:
37-
10:
59)
</td
>
5825 <td
>11 min (
11:
16-
11:
27)
</td
>
5826 <td
>11 min
50%
</td
>
5830 <td
>Thinkpad X200 Minimal
</td
>
5831 <td
>6 min (
08:
19-
08:
25)
</td
>
5832 <td
>4 min (
08:
04-
08:
08)
</td
>
5833 <td
>2 min
33%
</td
>
5837 <td
>Thinkpad X200 Roaming KDE
</td
>
5838 <td
>19 min (
09:
21-
09:
40)
</td
>
5839 <td
>15 min (
10:
25-
10:
40)
</td
>
5840 <td
>4 min
21%
</td
>
5843 </table
></p
>
5845 <p
>The test is done using a netinst ISO on a USB stick, so some of the
5846 time is spent downloading packages. The connection to the Internet
5847 was
100Mbit/s during testing, so downloading should not be a
5848 significant factor in the measurement. Download typically took a few
5849 seconds to a few minutes, depending on the amount of packages being
5850 installed.
</p
>
5852 <p
>The speedup is implemented by using two hooks in
5853 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
5854 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
5855 finish-install.d hook to remove the divert at the end of the
5856 installation. I picked the pre-pkgsel.d hook instead of the
5857 post-base-installer.d hook because I test using an ISO without the
5858 eatmydata package included, and the post-base-installer.d hook in
5859 Debian Edu can only operate on packages included in the ISO. The
5860 negative effect of this is that I am unable to activate this
5861 optimization for the kernel installation step in d-i. If the code is
5862 moved to the post-base-installer.d hook, the speedup would be larger
5863 for the entire installation.
</p
>
5865 <p
>I
've implemented this in the
5866 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
5867 git repository, and plan to provide the optimization as part of the
5868 Debian Edu installation. If you want to test this yourself, you can
5869 create two files in the installer (or in an udeb). One shell script
5870 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
5872 <p
><blockquote
><pre
>
5875 . /usr/share/debconf/confmodule
5877 logger -t my-pkgsel
"info: $*
"
5880 logger -t my-pkgsel
"error: $*
"
5882 override_install() {
5883 apt-install eatmydata || true
5884 if [ -x /target/usr/bin/eatmydata ] ; then
5885 for bin in dpkg apt-get aptitude tasksel ; do
5887 # Test that the file exist and have not been diverted already.
5888 if [ -f /target$file ] ; then
5889 info
"diverting $file using eatmydata
"
5890 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
5891 > /target$file.edu
5892 chmod
755 /target$file.edu
5893 in-target dpkg-divert --package debian-edu-config \
5894 --rename --quiet --add $file
5895 ln -sf ./$bin.edu /target$file
5897 error
"unable to divert $file, as it is missing.
"
5901 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
5906 </pre
></blockquote
></p
>
5908 <p
>To clean up, another shell script should go into
5909 /usr/lib/finish-install.d/ with code like this:
5911 <p
><blockquote
><pre
>
5913 . /usr/share/debconf/confmodule
5915 logger -t my-finish-install
"error: $@
"
5917 remove_install_override() {
5918 for bin in dpkg apt-get aptitude tasksel ; do
5920 if [ -x /target$file.edu ] ; then
5922 in-target dpkg-divert --package debian-edu-config \
5923 --rename --quiet --remove $file
5926 error
"Missing divert for $file.
"
5929 sync # Flush file buffers before continuing
5932 remove_install_override
5933 </pre
></blockquote
></p
>
5935 <p
>In Debian Edu, I placed both code fragments in a separate script
5936 edu-eatmydata-install and call it from the pre-pkgsel.d and
5937 finish-install.d scripts.
</p
>
5939 <p
>By now you might ask if this change should get into the normal
5940 Debian installer too? I suspect it should, but am not sure the
5941 current debian-installer coordinators find it useful enough. It also
5942 depend on the side effects of the change. I
'm not aware of any, but I
5943 guess we will see if the change is safe after some more testing.
5944 Perhaps there is some package in Debian depending on sync() and
5945 fsync() having effect? Perhaps it should go into its own udeb, to
5946 allow those of us wanting to enable it to do so without affecting
5949 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
5950 will break installation of all programs using gnutls because of
5951 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
5952 eatmydata package in Debian will solve it.
</p
>
5954 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
5955 the optimization work again. And I have discovered that the
5956 dpkg-divert trick is not really needed and implemented a slightly
5957 simpler approach as part of the debian-edu-install package. See
5958 tools/edu-eatmydata-install in the source package.
</p
>
5960 <p
>Update
2014-
11-
11: Unfortunately, a new
5961 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
5962 triggering on i386 made it into testing, and broke this installation
5963 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
5964 request
768893</a
> is accepted, it should be working again.
</p
>
5969 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
5970 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
5971 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
5972 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
5973 <description><p
>Yesterday, I had the pleasure of attending a talk with the
5974 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
5975 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
5976 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
5977 learn that there is a large set of publicly available key servers to
5978 use when looking for peoples public key. So far I have used
5979 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
5980 were misbehaving, but those days are ended. The servers I have used
5981 up until yesterday have been slow and some times unavailable. I hope
5982 those problems are gone now.
</p
>
5984 <p
>Behind the round robin DNS entry of the
5985 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
5986 there is a pool of more than
100 keyservers which are checked every
5987 day to ensure they are well connected and up to date. It must be
5988 better than what I have used so far. :)
</p
>
5990 <p
>Yesterdays speaker told me that the service is the default
5991 keyserver provided by the default configuration in GnuPG, but this do
5992 not seem to be used in Debian. Perhaps it should?
</p
>
5994 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
5997 <p
><blockquote
><pre
>
5998 keyserver pool.sks-keyservers.net
5999 </pre
></blockquote
></p
>
6001 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
6002 entries in DNS. Just for fun, I did just that at work, so now every
6003 user of GnuPG at the University of Oslo should find a OpenGPG
6004 keyserver automatically should their need it:
</p
>
6006 <p
><blockquote
><pre
>
6007 % host -t srv _pgpkey-http._tcp.uio.no
6008 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
6010 </pre
></blockquote
></p
>
6012 <p
>Now if only
6013 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
6014 HKP lookup protocol
</a
> supported finding signature paths, I would be
6015 very happy. It can look up a given key or search for a user ID, but I
6016 normally do not want that, but to find a trust path from my key to
6017 another key. Given a user ID or key ID, I would like to find (and
6018 download) the keys representing a signature path from my key to the
6019 key in question, to be able to get a trust path between the two keys.
6020 This is as far as I can tell not possible today. Perhaps something
6021 for a future version of the protocol?
</p
>
6026 <title>From English wiki to translated PDF and epub via Docbook
</title>
6027 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
6028 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
6029 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
6030 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
6031 project
</a
> provide an instruction manual for teachers, system
6032 administrators and other users that contain useful tips for setting up
6033 and maintaining a Debian Edu installation. This text is about how the
6034 text processing of this manual is handled in the project.
</p
>
6036 <p
>One goal of the project is to provide information in the native
6037 language of its users, and for this we need to handle translations.
6038 But we also want to make sure each language contain the same
6039 information, so for this we need a good way to keep the translations
6040 in sync. And we want it to be easy for our users to improve the
6041 documentation, avoiding the need to learn special formats or tools to
6042 contribute, and the obvious way to do this is to make it possible to
6043 edit the documentation using a web browser. We also want it to be
6044 easy for translators to keep the translation up to date, and give them
6045 help in figuring out what need to be translated. Here is the list of
6046 tools and the process we have found trying to reach all these
6049 <p
>We maintain the authoritative source of our manual in the
6050 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
6051 wiki
</a
>, as several wiki pages written in English. It consist of one
6052 front page with references to the different chapters, several pages
6053 for each chapter, and finally one
"collection page
" gluing all the
6054 chapters together into one large web page (aka
6055 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
6056 AllInOne page
</a
>). The AllInOne page is the one used for further
6057 processing and translations. Thanks to the fact that the
6058 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
6059 wiki.debian.org support exporting pages in
6060 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
6061 the list of pages to export using the raw version of the AllInOne
6062 page, loop over each of them to generate a Docbook XML version of the
6063 manual. This process also download images and transform image
6064 references to use the locally downloaded images. The generated
6065 Docbook XML files are slightly broken, so some post-processing is done
6066 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
6067 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
6068 a handfull of images. The XML file can now be used to generate PDF, HTML
6069 and epub versions of the English manual. This is the basic step of
6070 our process, making PDF (using dblatex), HTML (using xsltproc) and
6071 epub (using dbtoepub) version from Docbook XML, and the resulting files
6072 are placed in the debian-edu-doc-en binary package.
</p
>
6074 <p
>But English documentation is not enough for us. We want translated
6075 documentation too, and we want to make it easy for translators to
6076 track the English original. For this we use the
6077 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
6078 which allow us to transform the English Docbook XML file into a
6079 translation file (a .pot file), usable with the normal gettext based
6080 translation tools used by those translating free software. The pot
6081 file is used to create and maintain translation files (several .po
6082 files), which the translations update with the native language
6083 translations of all titles, paragraphs and blocks of text in the
6084 original. The next step is combining the original English Docbook XML
6085 and the translation file (say debian-edu-wheezy-manual.nb.po), to
6086 create a translated Docbook XML file (in this case
6087 debian-edu-wheezy-manual.nb.xml). This translated (or partly
6088 translated, if the translation is not complete) Docbook XML file can
6089 then be used like the original to create a PDF, HTML and epub version
6090 of the documentation.
</p
>
6092 <p
>The translators use different tools to edit the .po files. We
6094 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
6095 while some use emacs and vi, others can use web based editors like
6096 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
6097 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
6098 is where the .po file end up, in our git repository. Updated
6099 translations can either be committed directly to git, or submitted as
6100 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
6101 against the debian-edu-doc package
</a
>.
</p
>
6103 <p
>One challenge is images, which both might need to be translated (if
6104 they show translated user applications), and are needed in different
6105 formats when creating PDF and HTML versions (epub is a HTML version in
6106 this regard). For this we transform the original PNG images to the
6107 needed density and format during build, and have a way to provide
6108 translated images by storing translated versions in
6109 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
6110 package maintainers know more.
</p
>
6112 <p
>If you wonder what the result look like, we provide
6113 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
6114 of the documentation packages on the web
</a
>. See for example the
6115 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
6116 PDF version
</a
> or the
6117 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
6118 HTML version
</a
>. We do not yet build the epub version by default,
6119 but perhaps it will be done in the future.
</p
>
6121 <p
>To learn more, check out
6122 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
6123 debian-edu-doc package
</a
>,
6124 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
6125 manual on the wiki
</a
> and
6126 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
6127 translation instructions
</a
> in the manual.
</p
>
6132 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
6133 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
6134 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
6135 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
6136 <description><p
>It would be nice if it was easier in Debian to get all the hardware
6137 related packages relevant for the computer installed automatically.
6138 So I implemented one, using
6139 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
6140 package
</a
>. To use it, install the tasksel and isenkram packages and
6141 run tasksel as user root. You should be presented with a new option,
6142 "Hardware specific packages (autodetected by isenkram)
". When you
6143 select it, tasksel will install the packages isenkram claim is fit for
6144 the current hardware, hot pluggable or not.
<p
>
6146 <p
>The implementation is in two files, one is the tasksel menu entry
6147 description, and the other is the script used to extract the list of
6148 packages to install. The first part is in
6149 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
6152 <p
><blockquote
><pre
>
6155 Description: Hardware specific packages (autodetected by isenkram)
6156 Based on the detected hardware various hardware specific packages are
6158 Test-new-install: mark show
6160 Packages: for-current-hardware
6161 </pre
></blockquote
></p
>
6163 <p
>The second part is in
6164 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
6167 <p
><blockquote
><pre
>
6172 isenkram-autoinstall-firmware -l
6174 </pre
></blockquote
></p
>
6176 <p
>All in all, a very short and simple implementation making it
6177 trivial to install the hardware dependent package we all may want to
6178 have installed on our machines. I
've not been able to find a way to
6179 get tasksel to tell you exactly which packages it plan to install
6180 before doing the installation. So if you are curious or careful,
6181 check the output from the isenkram-* command line tools first.
</p
>
6183 <p
>The information about which packages are handling which hardware is
6184 fetched either from the isenkram package itself in
6185 /usr/share/isenkram/, from git.debian.org or from the APT package
6186 database (using the Modaliases header). The APT package database
6187 parsing have caused a nasty resource leak in the isenkram daemon (bugs
6188 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
6189 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
6190 the python-apt code (bug
6191 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
6192 workaround I was able to get rid of the file descriptor leak and
6193 reduce the memory leak from ~
30 MiB per hardware detection down to
6194 around
2 MiB per hardware detection. It should make the desktop
6195 daemon a lot more useful. The fix is in version
0.7 uploaded to
6196 unstable today.
</p
>
6198 <p
>I believe the current way of mapping hardware to packages in
6199 Isenkram is is a good draft, but in the future I expect isenkram to
6200 use the AppStream data source for this. A proposal for getting proper
6201 AppStream support into Debian is floating around as
6202 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
6203 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
6204 project
</a
> will take place this summer to improve the situation. I
6205 look forward to seeing the result, and welcome patches for isenkram to
6206 start using the information when it is ready.
</p
>
6208 <p
>If you want your package to map to some specific hardware, either
6209 add a
"Xb-Modaliases
" header to your control file like I did in
6210 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
6211 package
</a
> or submit a bug report with the details to the isenkram
6213 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
6214 blog posts tagged isenkram
</a
> for details on the notation. I expect
6215 the information will be migrated to AppStream eventually, but for the
6216 moment I got no better place to store it.
</p
>
6221 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
6222 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
6223 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
6224 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
6225 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
6226 project
</a
> is working on providing the software and hardware to make
6227 it easy for non-technical people to host their data and communication
6228 at home, and being able to communicate with their friends and family
6229 encrypted and away from prying eyes. It is still going strong, and
6230 today a major mile stone was reached.
</p
>
6232 <p
>Today, the last of the packages currently used by the project to
6233 created the system images were accepted into Debian Unstable. It was
6234 the freedombox-setup package, which is used to configure the images
6235 during build and on the first boot. Now all one need to get going is
6236 the build code from the freedom-maker git repository and packages from
6237 Debian. And once the freedombox-setup package enter testing, we can
6238 build everything directly from Debian. :)
</p
>
6240 <p
>Some key packages used by Freedombox are
6241 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
6242 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
6243 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
6244 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
6245 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
6246 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
6247 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
6248 are plans to integrate more packages into the setup. User
6249 documentation is maintained on the Debian wiki. Please
6250 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
6251 the manual
</a
> and help us improve it.
</p
>
6253 <p
>To test for yourself and create boot images with the FreedomBox
6254 setup, run this on a Debian machine using a user with sudo rights to
6255 become root:
</p
>
6257 <p
><pre
>
6258 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6259 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6261 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6263 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6264 </pre
></p
>
6266 <p
>Root access is needed to run debootstrap and mount loopback
6267 devices. See the README in the freedom-maker git repo for more
6268 details on the build. If you do not want all three images, trim the
6269 make line. Note that the virtualbox-image target is not really
6270 virtualbox specific. It create a x86 image usable in kvm, qemu,
6271 vmware and any other x86 virtual machine environment. You might need
6272 the version of vmdebootstrap in Jessie to get the build working, as it
6273 include fixes for a race condition with kpartx.
</p
>
6275 <p
>If you instead want to install using a Debian CD and the preseed
6276 method, boot a Debian Wheezy ISO and use this boot argument to load
6277 the preseed values:
</p
>
6279 <p
><pre
>
6280 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
6281 </pre
></p
>
6283 <p
>I have not tested it myself the last few weeks, so I do not know if
6284 it still work.
</p
>
6286 <p
>If you wonder how to help, one task you could look at is using
6287 systemd as the boot system. It will become the default for Linux in
6288 Jessie, so we need to make sure it is usable on the Freedombox. I did
6289 a simple test a few weeks ago, and noticed dnsmasq failed to start
6290 during boot when using systemd. I suspect there are other problems
6291 too. :) To detect problems, there is a test suite included, which can
6292 be run from the plinth web interface.
</p
>
6294 <p
>Give it a go and let us know how it goes on the mailing list, and help
6295 us get the new release published. :) Please join us on
6296 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
6297 irc.debian.org)
</a
> and
6298 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6299 mailing list
</a
> if you want to help make this vision come true.
</p
>
6304 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
6305 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
6306 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
6307 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
6308 <description><p
>For a while now, I have been looking for a sensible offsite backup
6309 solution for use at home. My requirements are simple, it must be
6310 cheap and locally encrypted (in other words, I keep the encryption
6311 keys, the storage provider do not have access to my private files).
6312 One idea me and my friends had many years ago, before the cloud
6313 storage providers showed up, was to use Google mail as storage,
6314 writing a Linux block device storing blocks as emails in the mail
6315 service provided by Google, and thus get heaps of free space. On top
6316 of this one can add encryption, RAID and volume management to have
6317 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6318 I never found time to implement such system. But the last few weeks I
6319 have looked at a system called
6320 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
6321 mounted network backed file system with the features I need.
</p
>
6323 <p
>S3QL is a fuse file system with a local cache and cloud storage,
6324 handling several different storage providers, any with Amazon S3,
6325 Google Drive or OpenStack API. There are heaps of such storage
6326 providers. S3QL can also use a local directory as storage, which
6327 combined with sshfs allow for file storage on any ssh server. S3QL
6328 include support for encryption, compression, de-duplication, snapshots
6329 and immutable file systems, allowing me to mount the remote storage as
6330 a local mount point, look at and use the files as if they were local,
6331 while the content is stored in the cloud as well. This allow me to
6332 have a backup that should survive fire. The file system can not be
6333 shared between several machines at the same time, as only one can
6334 mount it at the time, but any machine with the encryption key and
6335 access to the storage service can mount it if it is unmounted.
</p
>
6337 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
6338 package is included already. So to get started, run
<tt
>apt-get
6339 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
6340 Greenqloud, after reading their nice recipe on
6341 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
6342 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
6343 in Iceland more than those in USA when it come to keeping my personal
6344 data safe and private, and thus would rather spend money on a company
6345 in Iceland. Another nice recipe is available from the article
6346 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
6347 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
6348 Admin magazine. When the provider is picked, figure out how to get
6349 the API key needed to connect to the storage API. With Greencloud,
6350 the key did not show up until I had added payment details to my
6353 <p
>Armed with the API access details, it is time to create the file
6354 system. First, create a new bucket in the cloud. This bucket is the
6355 file system storage area. I picked a bucket name reflecting the
6356 machine that was going to store data there, but any name will do.
6357 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
6358 the API login and password, and a locally created password. Store it
6359 all in ~root/.s3ql/authinfo2 like this:
6361 <p
><blockquote
><pre
>
6363 storage-url: s3c://s.greenqloud.com:
443/bucket-name
6364 backend-login: API-login
6365 backend-password: API-password
6366 fs-passphrase: local-password
6367 </pre
></blockquote
></p
>
6369 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
6370 but any sensible way to create a fairly random password should do it.
6371 Armed with these details, it is now time to run mkfs, entering the API
6372 details and password to create it:
</p
>
6374 <p
><blockquote
><pre
>
6375 # mkdir -m
700 /var/lib/s3ql-cache
6376 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6377 --ssl s3c://s.greenqloud.com:
443/bucket-name
6378 Enter backend login:
6379 Enter backend password:
6380 Before using S3QL, make sure to read the user
's guide, especially
6381 the
'Important Rules to Avoid Loosing Data
' section.
6382 Enter encryption password:
6383 Confirm encryption password:
6384 Generating random encryption key...
6385 Creating metadata tables...
6395 Compressing and uploading metadata...
6396 Wrote
0.00 MB of compressed metadata.
6397 #
</pre
></blockquote
></p
>
6399 <p
>The next step is mounting the file system to make the storage available.
6401 <p
><blockquote
><pre
>
6402 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6403 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
6404 Using
4 upload threads.
6405 Downloading and decompressing metadata...
6415 Mounting filesystem...
6417 Filesystem Size Used Avail Use% Mounted on
6418 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
6420 </pre
></blockquote
></p
>
6422 <p
>The file system is now ready for use. I use rsync to store my
6423 backups in it, and as the metadata used by rsync is downloaded at
6424 mount time, no network traffic (and storage cost) is triggered by
6425 running rsync. To unmount, one should not use the normal umount
6426 command, as this will not flush the cache to the cloud storage, but
6427 instead running the umount.s3ql command like this:
6429 <p
><blockquote
><pre
>
6432 </pre
></blockquote
></p
>
6434 <p
>There is a fsck command available to check the file system and
6435 correct any problems detected. This can be used if the local server
6436 crashes while the file system is mounted, to reset the
"already
6437 mounted
" flag. This is what it look like when processing a working
6438 file system:
</p
>
6440 <p
><blockquote
><pre
>
6441 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
6442 Using cached metadata.
6443 File system seems clean, checking anyway.
6444 Checking DB integrity...
6445 Creating temporary extra indices...
6446 Checking lost+found...
6447 Checking cached objects...
6448 Checking names (refcounts)...
6449 Checking contents (names)...
6450 Checking contents (inodes)...
6451 Checking contents (parent inodes)...
6452 Checking objects (reference counts)...
6453 Checking objects (backend)...
6454 ..processed
5000 objects so far..
6455 ..processed
10000 objects so far..
6456 ..processed
15000 objects so far..
6457 Checking objects (sizes)...
6458 Checking blocks (referenced objects)...
6459 Checking blocks (refcounts)...
6460 Checking inode-block mapping (blocks)...
6461 Checking inode-block mapping (inodes)...
6462 Checking inodes (refcounts)...
6463 Checking inodes (sizes)...
6464 Checking extended attributes (names)...
6465 Checking extended attributes (inodes)...
6466 Checking symlinks (inodes)...
6467 Checking directory reachability...
6468 Checking unix conventions...
6469 Checking referential integrity...
6470 Dropping temporary indices...
6471 Backing up old metadata...
6481 Compressing and uploading metadata...
6482 Wrote
0.89 MB of compressed metadata.
6484 </pre
></blockquote
></p
>
6486 <p
>Thanks to the cache, working on files that fit in the cache is very
6487 quick, about the same speed as local file access. Uploading large
6488 amount of data is to me limited by the bandwidth out of and into my
6489 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
6490 which is very close to my upload speed, and downloading the same
6491 Debian installation ISO gave me
610 kiB/s, close to my download speed.
6492 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
6493 network, not the file system code. I do not know what a good cache
6494 size would be, but suspect that the cache should e larger than your
6495 working set.
</p
>
6497 <p
>I mentioned that only one machine can mount the file system at the
6498 time. If another machine try, it is told that the file system is
6501 <p
><blockquote
><pre
>
6502 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6503 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
6504 Using
8 upload threads.
6505 Backend reports that fs is still mounted elsewhere, aborting.
6507 </pre
></blockquote
></p
>
6509 <p
>The file content is uploaded when the cache is full, while the
6510 metadata is uploaded once every
24 hour by default. To ensure the
6511 file system content is flushed to the cloud, one can either umount the
6512 file system, or ask S3QL to flush the cache and metadata using
6515 <p
><blockquote
><pre
>
6516 # s3qlctrl upload-meta /s3ql
6517 # s3qlctrl flushcache /s3ql
6519 </pre
></blockquote
></p
>
6521 <p
>If you are curious about how much space your data uses in the
6522 cloud, and how much compression and deduplication cut down on the
6523 storage usage, you can use s3qlstat on the mounted file system to get
6526 <p
><blockquote
><pre
>
6528 Directory entries:
9141
6531 Total data size:
22049.38 MB
6532 After de-duplication:
21955.46 MB (
99.57% of total)
6533 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
6534 Database size:
2.39 MB (uncompressed)
6535 (some values do not take into account not-yet-uploaded dirty blocks in cache)
6537 </pre
></blockquote
></p
>
6539 <p
>I mentioned earlier that there are several possible suppliers of
6540 storage. I did not try to locate them all, but am aware of at least
6541 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
6542 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
6543 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
6544 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
6545 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
6546 accept payment in Bitcoin. Pick one that suit your need. Some of
6547 them provide several GiB of free storage, but the prize models are
6548 quite different and you will have to figure out what suits you
6551 <p
>While researching this blog post, I had a look at research papers
6552 and posters discussing the S3QL file system. There are several, which
6553 told me that the file system is getting a critical check by the
6554 science community and increased my confidence in using it. One nice
6556 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
6557 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
6558 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
6559 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
6560 and Pamela Smith. Please have a look.
</p
>
6562 <p
>Given my problems with different file systems earlier, I decided to
6563 check out the mounted S3QL file system to see if it would be usable as
6564 a home directory (in other word, that it provided POSIX semantics when
6565 it come to locking and umask handling etc). Running
6566 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
6567 test code to check file system semantics
</a
>, I was happy to discover that
6568 no error was found. So the file system can be used for home
6569 directories, if one chooses to do so.
</p
>
6571 <p
>If you do not want a locally file system, and want something that
6572 work without the Linux fuse file system, I would like to mention the
6573 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
6574 provide locally encrypted backup using a command line client. It have
6575 a nicer access control system, where one can split out read and write
6576 access, allowing some systems to write to the backup and others to
6577 only read from it.
</p
>
6579 <p
>As usual, if you use Bitcoin and want to show your support of my
6580 activities, please send Bitcoin donations to my address
6581 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6586 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
6587 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
6588 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
6589 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
6590 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
6591 project
</a
> is working on providing the software and hardware for
6592 making it easy for non-technical people to host their data and
6593 communication at home, and being able to communicate with their
6594 friends and family encrypted and away from prying eyes. It has been
6595 going on for a while, and is slowly progressing towards a new test
6596 release (
0.2).
</p
>
6598 <p
>And what day could be better than the Pi day to announce that the
6599 new version will provide
"hard drive
" / SD card / USB stick images for
6600 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
6601 system), and can also be installed using a Debian installer preseed
6602 file. The Debian based Freedombox is now based on Debian Jessie,
6603 where most of the needed packages used are already present. Only one,
6604 the freedombox-setup package, is missing. To try to build your own
6605 boot image to test the current status, fetch the freedom-maker scripts
6607 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
6608 with a user with sudo access to become root:
6611 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6613 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6614 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6616 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6619 <p
>Root access is needed to run debootstrap and mount loopback
6620 devices. See the README for more details on the build. If you do not
6621 want all three images, trim the make line. But note that thanks to
<a
6622 href=
"https://bugs.debian.org/
741407">a race condition in
6623 vmdebootstrap
</a
>, the build might fail without the patch to the
6624 kpartx call.
</p
>
6626 <p
>If you instead want to install using a Debian CD and the preseed
6627 method, boot a Debian Wheezy ISO and use this boot argument to load
6628 the preseed values:
</p
>
6631 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
6634 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
6635 recently introduced bug in apt in Jessie
</a
>, the installer will
6636 currently hang while setting up APT sources. Killing the
6637 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
6638 installation will get the installation going. This affect all
6639 installations in Jessie, and I expect it will be fixed soon.
</p
>
6641 <p
>Give it a go and let us know how it goes on the mailing list, and help
6642 us get the new release published. :) Please join us on
6643 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
6644 irc.debian.org)
</a
> and
6645 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6646 mailing list
</a
> if you want to help make this vision come true.
</p
>
6651 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
6652 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
6653 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
6654 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
6655 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
6656 innetgr tools, because I needed them in
6657 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
6658 ng-utils, and it has served me well. I placed the project under the
6659 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
6660 repository. But many years ago, the CVS repository was dropped (lost,
6661 not migrated to new hardware, not sure), and the project have lacked a
6662 proper home since then.
</p
>
6664 <p
>Last summer, I had a look at the package and made a new release
6665 fixing a irritating crash bug, but was unable to store the changes in
6666 a proper source control system. I applied for a project on
6667 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
6668 to follow up on it. Until today. :)
</p
>
6670 <p
>After many hours of cleaning and migration, the ng-utils project
6671 now have a new home, and a git repository with the highlight of the
6672 history of the project. I published all release tarballs and imported
6673 them into the git repository. As the project is really stable and not
6674 expected to gain new features any time soon, I decided to make a new
6675 release and call it
1.0. Visit the new project home on
6676 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
6677 if you want to check it out. The new version is also uploaded into
6678 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
6683 <title>Testing sysvinit from experimental in Debian Hurd
</title>
6684 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
6685 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
6686 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
6687 <description><p
>A few days ago I decided to try to help the Hurd people to get
6688 their changes into sysvinit, to allow them to use the normal sysvinit
6689 boot system instead of their old one. This follow up on the
6690 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
6691 Google Summer of Code work
</a
> done last summer by Justus Winter to
6692 get Debian on Hurd working more like Debian on Linux. To get started,
6693 I downloaded a prebuilt hard disk image from
6694 <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
>,
6695 and started it using virt-manager.
</p
>
6697 <p
>The first think I had to do after logging in (root without any
6698 password) was to get the network operational. I followed
6699 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
6700 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
6701 commands as root to get the machine to accept a IP address from the
6702 kvm internal DHCP server:
</p
>
6704 <p
><blockquote
><pre
>
6705 settrans -fgap /dev/netdde /hurd/netdde
6706 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
6707 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
6709 </pre
></blockquote
></p
>
6711 <p
>After this, the machine had internet connectivity, and I could
6712 upgrade it and install the sysvinit packages from experimental and
6713 enable it as the default boot system in Hurd.
</p
>
6715 <p
>But before I did that, I set a password on the root user, as ssh is
6716 running on the machine it for ssh login to work a password need to be
6717 set. Also, note that a bug somewhere in openssh on Hurd block
6718 compression from working. Remember to turn that off on the client
6721 <p
>Run these commands as root to upgrade and test the new sysvinit
6724 <p
><blockquote
><pre
>
6725 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
6726 deb http://http.debian.net/debian/ experimental main
6729 apt-get dist-upgrade
6730 apt-get install -t experimental initscripts sysv-rc sysvinit \
6731 sysvinit-core sysvinit-utils
6732 update-alternatives --config runsystem
6733 </pre
></blockquote
></p
>
6735 <p
>To reboot after switching boot system, you have to use
6736 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
6737 yet a sysvinit process able to receive the signals from the normal
6738 'reboot
' command. After switching to sysvinit as the boot system,
6739 upgrading every package and rebooting, the network come up with DHCP
6740 after boot as it should, and the settrans/pkill hack mentioned at the
6741 start is no longer needed. But for some strange reason, there are no
6742 longer any login prompt in the virtual console, so I logged in using
6745 <p
>Note that there are some race conditions in Hurd making the boot
6746 fail some times. No idea what the cause is, but hope the Hurd porters
6747 figure it out. At least Justus said on IRC (#debian-hurd on
6748 irc.debian.org) that they are aware of the problem. A way to reduce
6749 the impact is to upgrade to the Hurd packages built by Justus by
6750 adding this repository to the machine:
</p
>
6752 <p
><blockquote
><pre
>
6753 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
6754 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
6756 </pre
></blockquote
></p
>
6758 <p
>At the moment the prebuilt virtual machine get some packages from
6759 http://ftp.debian-ports.org/debian, because some of the packages in
6760 unstable do not yet include the required patches that are lingering in
6761 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
6763 <p
><blockquote
><pre
>
6764 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
6765 i emacs - GNU Emacs editor (metapackage)
6766 i gdb - GNU Debugger
6767 i hurd-recommended - Miscellaneous translators
6768 i isc-dhcp-client - ISC DHCP client
6769 i isc-dhcp-common - common files used by all the isc-dhcp* packages
6770 i libc-bin - Embedded GNU C Library: Binaries
6771 i libc-dev-bin - Embedded GNU C Library: Development binaries
6772 i libc0.3 - Embedded GNU C Library: Shared libraries
6773 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
6774 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
6775 i multiarch-support - Transitional package to ensure multiarch compatibilit
6776 i A x11-common - X Window System (X.Org) infrastructure
6777 i xorg - X.Org X Window System
6778 i A xserver-xorg - X.Org X server
6779 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
6781 </pre
></blockquote
></p
>
6783 <p
>All in all, testing hurd has been an interesting experience. :)
6784 X.org did not work out of the box and I never took the time to follow
6785 the porters instructions to fix it. This time I was interested in the
6786 command line stuff.
<p
>
6791 <title>New chrpath release
0.16</title>
6792 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
6793 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
6794 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
6795 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
6796 find problems in C, C++ and Java code using static source code
6797 analysis. It can detect a lot of different problems, and is very
6798 useful to find memory and locking bugs in the error handling part of
6799 the source. The company behind it provide
6800 <a href=
"https://scan.coverity.com/
">check of free software projects as
6801 a community service
</a
>, and many hundred free software projects are
6802 already checked. A few days ago I decided to have a closer look at
6803 the Coverity system, and discovered that the
6804 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
6805 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
6806 projects I am involved with was already registered. But these are
6807 fairly big, and I would also like to have a small and easy project to
6808 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
6809 checking of the chrpath project
</a
>. It was
6810 added to the checker and discovered seven potential defects. Six of
6811 these were real, mostly resource
"leak
" when the program detected an
6812 error. Nothing serious, as the resources would be released a fraction
6813 of a second later when the program exited because of the error, but it
6814 is nice to do it right in case the source of the program some time in
6815 the future end up in a library. Having fixed all defects and added
6816 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
6817 mailing list for the chrpath developers
</a
>, I decided it was time to
6818 publish a new release. These are the release notes:
</p
>
6820 <p
>New in
0.16 released
2014-
01-
14:
</p
>
6824 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
6825 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
6826 <li
>Mention new project mailing list in the documentation.
</li
>
6831 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
6832 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
6833 project if something is wrong with the new release. The test suite
6834 did not discover any old errors, so if you find a new one, please also
6835 include a test suite check.
</p
>
6840 <title>New chrpath release
0.15</title>
6841 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
6842 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
6843 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
6844 <description><p
>After many years break from the package and a vain hope that
6845 development would be continued by someone else, I finally pulled my
6846 acts together this morning and wrapped up a new release of chrpath,
6847 the command line tool to modify the rpath and runpath of already
6848 compiled ELF programs. The update was triggered by the persistence of
6849 Isha Vishnoi at IBM, which needed a new config.guess file to get
6850 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
6851 is working on. I checked the
6852 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
6853 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
6854 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
6855 packages for interesting patches (failed to find the source from
6856 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
6857 These are the release notes:
</p
>
6859 <p
>New in
0.15 released
2013-
11-
24:
</p
>
6863 <li
>Updated config.sub and config.guess from the GNU project to work
6864 with newer architectures. Thanks to isha vishnoi for the heads
6867 <li
>Updated README with current URLs.
</li
>
6869 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
6870 Matthias Klose.
</li
>
6872 <li
>Added missing help for -k|--keepgoing option, using patch by
6873 Petr Machata found in Fedora.
</li
>
6875 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
6876 .dynamic is a NULL terminated string. Based on patch found in
6877 Fedora credited Axel Thimm and Christian Krause.
</li
>
6882 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
6883 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
6884 project if something is wrong with the new release. The test suite
6885 did not discover any old errors, so if you find a new one, please also
6886 include a testsuite check.
</p
>
6891 <title>Debian init.d boot script example for rsyslog
</title>
6892 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
6893 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
6894 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
6895 <description><p
>If one of the points of switching to a new init system in Debian is
6896 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
6897 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
6898 init.d scripts at all. Here is an example init.d script, ie a rewrite
6899 of /etc/init.d/rsyslog:
</p
>
6901 <p
><pre
>
6902 #!/lib/init/init-d-script
6905 # Required-Start: $remote_fs $time
6906 # Required-Stop: umountnfs $time
6907 # X-Stop-After: sendsigs
6908 # Default-Start:
2 3 4 5
6909 # Default-Stop:
0 1 6
6910 # Short-Description: enhanced syslogd
6911 # Description: Rsyslog is an enhanced multi-threaded syslogd.
6912 # It is quite compatible to stock sysklogd and can be
6913 # used as a drop-in replacement.
6915 DESC=
"enhanced syslogd
"
6916 DAEMON=/usr/sbin/rsyslogd
6917 </pre
></p
>
6919 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
6920 script was
137 lines, and the above is just
15 lines, most of it meta
6921 info/comments.
</p
>
6923 <p
>How to do this, you ask? Well, one create a new script
6924 /lib/init/init-d-script looking something like this:
6926 <p
><pre
>
6929 # Define LSB log_* functions.
6930 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
6931 # and status_of_proc is working.
6932 . /lib/lsb/init-functions
6935 # Function that starts the daemon/service
6941 #
0 if daemon has been started
6942 #
1 if daemon was already running
6943 #
2 if daemon could not be started
6944 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
6946 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
6949 # Add code here, if necessary, that waits for the process to be ready
6950 # to handle requests from services started subsequently which depend
6951 # on this one. As a last resort, sleep for some time.
6955 # Function that stops the daemon/service
6960 #
0 if daemon has been stopped
6961 #
1 if daemon was already stopped
6962 #
2 if daemon could not be stopped
6963 # other if a failure occurred
6964 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
6965 RETVAL=
"$?
"
6966 [
"$RETVAL
" =
2 ]
&& return
2
6967 # Wait for children to finish too if this is a daemon that forks
6968 # and if the daemon is only ever run from this initscript.
6969 # If the above conditions are not satisfied then add some other code
6970 # that waits for the process to drop all resources that could be
6971 # needed by services started subsequently. A last resort is to
6972 # sleep for some time.
6973 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
6974 [
"$?
" =
2 ]
&& return
2
6975 # Many daemons don
't delete their pidfiles when they exit.
6977 return
"$RETVAL
"
6981 # Function that sends a SIGHUP to the daemon/service
6985 # If the daemon can reload its configuration without
6986 # restarting (for example, when it is sent a SIGHUP),
6987 # then implement that here.
6989 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
6994 scriptbasename=
"$(basename $
1)
"
6995 echo
"SN: $scriptbasename
"
6996 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
6997 script=
"$
1"
7004 NAME=$(basename $DAEMON)
7005 PIDFILE=/var/run/$NAME.pid
7007 # Exit if the package is not installed
7008 #[ -x
"$DAEMON
" ] || exit
0
7010 # Read configuration variable file if it is present
7011 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
7013 # Load the VERBOSE setting and other rcS variables
7016 case
"$
1" in
7018 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
7020 case
"$?
" in
7021 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
7022 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
7026 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
7028 case
"$?
" in
7029 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
7030 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
7034 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
7036 #reload|force-reload)
7038 # If do_reload() is not implemented then leave this commented out
7039 # and leave
'force-reload
' as an alias for
'restart
'.
7041 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
7045 restart|force-reload)
7047 # If the
"reload
" option is implemented then remove the
7048 #
'force-reload
' alias
7050 log_daemon_msg
"Restarting $DESC
" "$NAME
"
7052 case
"$?
" in
7055 case
"$?
" in
7057 1) log_end_msg
1 ;; # Old process is still running
7058 *) log_end_msg
1 ;; # Failed to start
7068 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
7074 </pre
></p
>
7076 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
7077 lot. I did not really polish the approach, so it might not always
7078 work out of the box, but you get the idea. I did not try very hard to
7079 optimize it nor make it more robust either.
</p
>
7081 <p
>A better argument for switching init system in Debian than reducing
7082 the size of init scripts (which is a good thing to do anyway), is to
7083 get boot system that is able to handle the kernel events sensibly and
7084 robustly, and do not depend on the boot to run sequentially. The boot
7085 and the kernel have not behaved sequentially in years.
</p
>
7090 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
7091 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
7092 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
7093 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
7094 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
7095 remote display access is the preferred solution with oVirt and RedHat
7096 Enterprise Virtualization, and I was sad to discover the other day
7097 that the browser plugin needed to use these systems seamlessly was
7098 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
7099 for a package
</a
> was from
2012-
04-
10 with no progress since
7100 2013-
04-
01, so I decided to wrap up a package based on the great work
7101 from Cajus Pollmeier and put it in a collab-maint maintained git
7102 repository to get a package I could use. I would very much like
7103 others to help me maintain the package (or just take over, I do not
7104 mind), but as no-one had volunteered so far, I just uploaded it to
7105 NEW. I hope it will be available in Debian in a few days.
</p
>
7107 <p
>The source is now available from
7108 <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
>
7113 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
7114 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
7115 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
7116 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
7117 <description><p
>The
7118 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
7119 program is a a very nice system to create virtual machine images. It
7120 create a image file, add a partition table, mount it and run
7121 debootstrap in the mounted directory to create a Debian system on a
7122 stick. Yesterday, I decided to try to teach it how to make images for
7123 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
7124 of a plan to simplify the build system for
7125 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
7126 project
</a
>. The FreedomBox project already uses vmdebootstrap for
7127 the virtualbox images, but its current build system made multistrap
7128 based system for Dreamplug images, and it is lacking support for
7129 Raspberry Pi.
</p
>
7131 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
7132 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
7133 code and adjusted it to be able to build armel images on my amd64
7134 Debian laptop. I ended up giving vmdebootstrap five new options,
7135 allowing me to replicate the image creation process I use to make
7136 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
7137 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
7138 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
7139 call debootstrap with --foreign and to copy the handler into the
7140 generated chroot before running the second stage. This allow
7141 vmdebootstrap to create armel images on an amd64 host. Next I added
7142 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
7143 fstype
</tt
> to teach it to create a separate /boot/ partition with the
7144 given file system type, allowing me to create an image with a vfat
7145 partition for the /boot/ stuff. I also added a
<tt
>--variant
7146 variant
</tt
> option to allow me to create smaller images without the
7147 Debian base system packages installed. Finally, I added an option
7148 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
7149 as a boot loader. It is not needed on the Raspberry Pi and probably
7150 most other non-x86 architectures. The changes were accepted by the
7151 upstream author of vmdebootstrap yesterday and today, and is now
7153 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
7154 upstream project page
</a
>.
</p
>
7156 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
7157 create a small script (the customize script) to add the non-free
7158 binary blob needed to boot the Raspberry Pi and the APT source
7161 <p
><pre
>
7163 set -e # Exit on first error
7164 rootdir=
"$
1"
7165 cd
"$rootdir
"
7166 cat
&lt;
&lt;EOF
> etc/apt/sources.list
7167 deb http://http.debian.net/debian/ jessie main contrib non-free
7169 # Install non-free binary blob needed to boot Raspberry Pi. This
7170 # install a kernel somewhere too.
7171 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
7172 -O $rootdir/usr/bin/rpi-update
7173 chmod a+x $rootdir/usr/bin/rpi-update
7174 mkdir -p $rootdir/lib/modules
7175 touch $rootdir/boot/start.elf
7176 chroot $rootdir rpi-update
7177 </pre
></p
>
7179 <p
>Next, fetch the latest vmdebootstrap script and call it like this
7180 to build the image:
</p
>
7183 sudo ./vmdebootstrap \
7186 --distribution jessie \
7187 --mirror http://http.debian.net/debian \
7196 --root-password raspberry \
7197 --hostname raspberrypi \
7198 --foreign /usr/bin/qemu-arm-static \
7199 --customize `pwd`/customize \
7201 --package git-core \
7202 --package binutils \
7203 --package ca-certificates \
7206 </pre
></p
>
7208 <p
>The list of packages being installed are the ones needed by
7209 rpi-update to make the image bootable on the Raspberry Pi, with the
7210 exception of netbase, which is needed by debootstrap to find
7211 /etc/hosts with the minbase variant. I really wish there was a way to
7212 set up an Raspberry Pi using only packages in the Debian archive, but
7213 that is not possible as far as I know, because it boots from the GPU
7214 using a non-free binary blob.
</p
>
7216 <p
>The build host need debootstrap, kpartx and qemu-user-static and
7217 probably a few others installed. I have not checked the complete
7218 build dependency list.
</p
>
7220 <p
>The resulting image will not use the hardware floating point unit
7221 on the Raspberry PI, because the armel architecture in Debian is not
7222 optimized for that use. So the images created will be a bit slower
7223 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
7228 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
7229 <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>
7230 <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>
7231 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
7232 <description><p
>The last few days I came across a few good causes that should get
7233 wider attention. I recommend signing and donating to each one of
7236 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
7237 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
7238 Women program which is a Google Summer of Code like initiative to get
7239 more women involved in free software. One debian sponsor has offered
7240 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
7241 earmarked
</a
> for this initiative. I donated a few minutes ago, and
7242 hope you will to. :)
</p
>
7244 <p
>And the Electronic Frontier Foundation just announced plans to
7245 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
7246 documentaries about the excessive spying
</a
> on every Internet user that
7247 take place these days, and their need to fund the work. I
've already
7248 donated. Are you next?
</p
>
7250 <p
>For my Norwegian audience, the organisation Studentenes og
7251 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7252 statement under the heading
7253 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
7254 Access
</a
> for those of us asking for more focus on open access in the
7255 Norwegian government. So far
499 signatures. I hope you will sign it
7261 <title>Videos about the Freedombox project - for inspiration and learning
</title>
7262 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
7263 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
7264 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
7265 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
7266 project
</a
> have been going on for a while, and have presented the
7267 vision, ideas and solution several places. Here is a little
7268 collection of videos of talks and presentation of the project.
</p
>
7272 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
7273 2,
5 minute marketing film
</a
> (Youtube)
</li
>
7275 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
7276 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
7278 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
7279 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7280 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
7281 (Youtube)
</li
>
7283 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
7284 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
7286 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
7287 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
7289 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
7290 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7291 York City in
2012</a
> (Youtube)
</li
>
7293 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
7294 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
7295 (Youtube)
</li
>
7297 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
7298 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
7300 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
7301 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
7303 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
7304 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7305 2013</a
> (Youtube)
</li
>
7309 <p
>A larger list is available from
7310 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
7311 Freedombox Wiki
</a
>.
</p
>
7313 <p
>On other news, I am happy to report that Freedombox based on Debian
7314 Jessie is coming along quite well, and soon both Owncloud and using
7315 Tor should be available for testers of the Freedombox solution. :) In
7316 a few weeks I hope everything needed to test it is included in Debian.
7317 The withsqlite package is already in Debian, and the plinth package is
7318 pending in NEW. The third and vital part of that puzzle is the
7319 metapackage/setup framework, which is still pending an upload. Join
7320 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
7321 (#freedombox on irc.debian.org)
</a
> and
7322 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7323 mailing list
</a
> if you want to help make this vision come true.
</p
>
7328 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
7329 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
7330 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
7331 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
7332 <description><p
>I was introduced to the
7333 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
7334 in
2010, when Eben Moglen presented his vision about serving the need
7335 of non-technical people to keep their personal information private and
7336 within the legal protection of their own homes. The idea is to give
7337 people back the power over their network and machines, and return
7338 Internet back to its intended peer-to-peer architecture. Instead of
7339 depending on a central service, the Freedombox will give everyone
7340 control over their own basic infrastructure.
</p
>
7342 <p
>I
've intended to join the effort since then, but other tasks have
7343 taken priority. But this summers nasty news about the misuse of trust
7344 and privilege exercised by the
"western
" intelligence gathering
7345 communities increased my eagerness to contribute to a point where I
7346 actually started working on the project a while back.
</p
>
7348 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
7349 Debian initiative
</a
> based on the vision from Eben Moglen, is to
7350 create a simple and cheap Debian based appliance that anyone can hook
7351 up in their home and get access to secure and private services and
7352 communication. The initial deployment platform have been the
7353 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
7354 which is a piece of hardware I do not own. So to be able to test what
7355 the current Freedombox setup look like, I had to come up with a way to install
7356 it on some hardware I do have access to. I have rewritten the
7357 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
7358 image build framework to use .deb packages instead of only copying
7359 setup into the boot images, and thanks to this rewrite I am able to
7360 set up any machine supported by Debian Wheezy as a Freedombox, using
7361 the previously mentioned deb (and a few support debs for packages
7362 missing in Debian).
</p
>
7364 <p
>The current Freedombox setup consist of a set of bootstrapping
7366 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
7367 and a administrative web interface
7368 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
7369 withsqlite), as well as a privacy enhancing proxy based on
7370 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
7371 (freedombox-privoxy). There is also a web/javascript based XMPP
7372 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
7373 trying (unsuccessfully so far) to talk to the XMPP server
7374 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
7375 web interface is pluggable, and the goal is to use it to enable OpenID
7376 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7377 this is really working yet, see
7378 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
7379 project TODO
</a
> for links to GIT repositories. Most of the code is
7380 on github at the moment. The HTTP proxy is operational out of the
7381 box, and the admin web interface can be used to add/remove plinth
7382 users. I
've not been able to do anything else with it so far, but
7383 know there are several branches spread around github and other places
7384 with lots of half baked features.
</p
>
7386 <p
>Anyway, if you want to have a look at the current state, the
7387 following recipes should work to give you a test machine to poke
7390 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
7394 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
7395 <li
>Boot from it, either as CD or USB stick.
</li
>
7396 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
7397 to the Debian installer:
<p
>
7398 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
7400 <li
>Answer the few language/region/password questions and pick disk to
7401 install on.
</li
>
7403 <li
>When the installation is finished and the machine have rebooted a
7404 few times, your Freedombox is ready for testing.
</li
>
7408 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
7412 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
7413 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
7414 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
7416 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
7417 </pre
></li
>
7418 <li
><p
>Run this as root:
</p
>
7420 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7423 apt-get install freedombox-setup
7424 /usr/lib/freedombox/setup
7425 </pre
></li
>
7426 <li
>Reboot into your freshly created Freedombox.
</li
>
7430 <p
>You can test it on other architectures too, but because the
7431 freedombox-privoxy package is binary, it will only work as intended on
7432 the architectures where I have had time to build the binary and put it
7433 in my APT repository. But do not let this stop you. It is only a
7434 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
7436 <p
>Note that by default Freedombox is a DHCP server on the
7437 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
7438 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
7439 disable
</tt
>" as root.
</p
>
7441 <p
>Please let me know if this works for you, or if you have any
7442 problems. We gather on the IRC channel
7443 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
7444 irc.debian.org and the
7445 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
7446 mailing list
</a
>.
</p
>
7448 <p
>Once you get your freedombox operational, you can visit
7449 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
7450 welcome screen (dead end - do not be surprised if you are unable to
7451 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
7452 to look at the rest of plinth. The default user is
'admin
' and the
7453 default password is
'secret
'.
</p
>
7458 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
7459 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
7460 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
7461 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
7462 <description><p
>Earlier, I reported about
7463 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
7464 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
7465 told by IBM that the original disk should be thrown away. And as
7466 there no longer was a problem if I bricked the firmware, I decided
7467 today to try to install Intel firmware to replace the Lenovo firmware
7468 currently on the disk.
</p
>
7470 <p
>I searched the Intel site for firmware, and found
7471 <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
>
7472 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
7473 according to the site should contain the latest firmware for SSD
7474 disks. I inserted the broken disk in one of my spare laptops and
7475 booted the ISO from a USB stick. The disk was recognized, but the
7476 program claimed the newest firmware already were installed and refused
7477 to insert any Intel firmware. So no change, and the disk is still
7478 unable to handle write load. :( I guess the only way to get them
7479 working would be if Lenovo releases new firmware. No idea how likely
7480 that is. Anyway, just blogging about this test for completeness. I
7481 got a working Samsung disk, and see no point in spending more time on
7482 the broken disks.
</p
>
7487 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
7488 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
7489 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
7490 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
7491 <description><p
>Today I switched to
7492 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
7493 new laptop
</a
>. I
've previously written about the problems I had with
7494 my new Thinkpad X230, which was delivered with an
7495 <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
7496 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
7497 sustained writes. My hardware supplier have been very forthcoming in
7498 trying to find a solution, and after first trying with another
7499 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
7500 disk instead to fix it once and for all. The Samsung disk survived
7501 the installation of Debian with encrypted disks (filling the disk with
7502 random data during installation killed the first two), and I thus
7503 decided to trust it with my data. I have installed it as a Debian Edu
7504 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
7505 server at home using Kerberos and LDAP, and will use it as my work
7506 station from now on.
</p
>
7508 <p
>As this is a solid state disk with no moving parts, I believe the
7509 Debian Wheezy default installation need to be tuned a bit to increase
7510 performance and increase life time of the disk. The Linux kernel and
7511 user space applications do not yet adjust automatically to such
7512 environment. To make it easier for my self, I created a draft Debian
7513 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
7514 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
7515 for the ssd-setup package
</a
> is available from collab-maint, and it
7516 is set up to adjust the setup of the machine by just installing the
7517 package. If there is any non-SSD disk in the machine, the package
7518 will refuse to install, as I did not try to write any logic to sort
7519 file systems in SSD and non-SSD file systems.
</p
>
7521 <p
>I consider the package a draft, as I am a bit unsure how to best
7522 set up Debian Wheezy with an SSD. It is adjusted to my use case,
7523 where I set up the machine with one large encrypted partition (in
7524 addition to /boot), put LVM on top of this and set up partitions on
7525 top of this again. See the README file in the package source for the
7526 references I used to pick the settings. At the moment these
7527 parameters are tuned:
</p
>
7531 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
7532 (adding discard to /etc/crypttab)
</li
>
7534 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
7535 this case a cryptsetup partition) by changing issue_discards from
7536 0 to
1 in /etc/lvm/lvm.conf.
</li
>
7538 <li
>Set relatime as a file system option for ext3 and ext4 file
7541 <li
>Tell swap to use TRIM commands by adding
'discard
' to
7542 /etc/fstab.
</li
>
7544 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
7546 <li
>Run fstrim on every ext3 and ext4 file system every night (from
7547 cron.daily).
</li
>
7549 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
7550 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
7554 <p
>During installation, I cancelled the part where the installer fill
7555 the disk with random data, as this would kill the SSD performance for
7556 little gain. My goal with the encrypted file system is to ensure
7557 those stealing my laptop end up with a brick and not a working
7558 computer. I have no hope in keeping the really resourceful people
7559 from getting the data on the disk (see
7560 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
7561 Thus I concluded that adding the discard option to crypttab is the
7562 right thing to do.
</p
>
7564 <p
>I considered using the noop I/O scheduler, as several recommended
7565 it for SSD, but others recommended deadline and a benchmark I found
7566 indicated that deadline might be better for interactive use.
</p
>
7568 <p
>I also considered using the
'discard
' file system option for ext3
7569 and ext4, but read that it would give a performance hit ever time a
7570 file is removed, and thought it best to that that slowdown once a day
7571 instead of during my work.
</p
>
7573 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
7574 this is already done by Debian Edu.
</p
>
7576 <p
>I have not yet started on the user space tuning. I expect
7577 iceweasel need some tuning, and perhaps other applications too, but
7578 have not yet had time to investigate those parts.
</p
>
7580 <p
>The package should work on Ubuntu too, but I have not yet tested it
7583 <p
>As for the answer to the question in the title of this blog post,
7584 as far as I know, the only solution I know about is to replace the
7585 disk. It might be possible to flash it with Intel firmware instead of
7586 the Lenovo firmware. But I have not tried and did not want to do so
7587 without approval from Lenovo as I wanted to keep the warranty on the
7588 disk until a solution was found and they wanted the broken disks
7594 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
7595 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
7596 <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>
7597 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
7598 <description><p
>A few days ago, I wrote about
7599 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
7600 problems I experienced with my new X230 and its SSD disk
</a
>, which
7601 was dying during installation because it is unable to cope with
7602 sustained write. My supplier is in contact with
7603 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
7604 replacement disk to try to fix the problem. They decided to send an
7605 identical model, so my hopes for a permanent fix was slim.
</p
>
7607 <p
>Anyway, today I got the replacement disk and tried to install
7608 Debian Edu Wheezy with encrypted disk on it. The new disk have the
7609 same firmware version as the original. This time my hope raised
7610 slightly as the installation progressed, as the original disk used to
7611 die after
4-
7% of the disk was written to, while this time it kept
7612 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
7613 died again and I was back on square one. I still do not have a new
7614 laptop with a disk I can trust. I can not live with a disk that might
7615 lock up when I download a new
7616 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
7617 other large files. I look forward to hearing from my supplier with
7618 the next proposal from Lenovo.
</p
>
7620 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
7621 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
7622 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
7623 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
7624 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
7625 P/N
45N8295, P0C38732.
</p
>
7627 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
7628 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
7629 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
7630 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
7631 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
7632 P/N
45N8295, P0C38732.
</p
>
7634 <p
>The only difference is in the first number (serial number?), ISN,
7635 SA, date and WNPP values. Mentioning all the details here in case
7636 someone is able to use the information to find a way to identify the
7637 failing disk among working ones (if any such working disk actually
7643 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
7644 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
7645 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
7646 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
7647 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
7648 Debian Edu developer gathering and Debian and Ubuntu bug squashing
7649 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
7650 member assosiation NUUG
</a
> and
7651 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
7652 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
7653 Bitraf
</a
>.
</p
>
7655 <p
>It starts
10:
00 and continue until late evening. Everyone is
7656 welcome, and there is no fee to participate. There is on the other
7657 hand limited space, and only room for
30 people. Please put your name
7658 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
7659 wiki page
</a
> if you plan to join us.
</p
>
7664 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
7665 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
7666 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
7667 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
7668 <description><p
>Half a year ago, I reported that I had to find a
7669 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
7670 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
7671 time to spend on it, and it took a while to find a model I believe
7672 will do the job, but two days ago the replacement finally arrived. I
7674 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
7675 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
7676 a roaming workstation, and it seemed to work flawlessly. But my
7677 second installation with encrypted disk was not as successful. More
7678 on that below.
</p
>
7680 <p
>I had a hard time trying to track down a good laptop, as my most
7681 important requirements (robust and with a good keyboard) are never
7682 listed in the feature list. But I did get good help from the search
7683 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
7684 allowed me to limit the list of interesting laptops based on my other
7685 requirements. A bit surprising that SSD disk are not disks according
7686 to that search interface, so I had to drop specifying the number of
7687 disks from my search parameters. I also asked around among friends to
7688 get their impression on keyboards and robustness.
</p
>
7690 <p
>So the new laptop arrived, and it is quite a lot wider than the
7691 X41. I am not quite convinced about the keyboard, as it is
7692 significantly wider than my old keyboard, and I have to stretch my
7693 hand a lot more to reach the edges. But the key response is fairly
7694 good and the individual key shape is fairly easy to handle, so I hope
7695 I will get used to it. My old X40 was starting to fail, and I really
7696 needed a new laptop now. :)
</p
>
7698 <p
>Turning off the touch pad was simple. All it took was a quick
7699 visit to the BIOS during boot it disable it.
</p
>
7701 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
7702 lock up during load. And this happen when installing Debian Wheezy
7703 with encrypted disk, while the disk is being filled with random data.
7704 I also tested to install Ubuntu Raring, and it happen there too if I
7705 reenable the code to fill the disk with random data (it is disabled by
7706 default in Ubuntu). And the bug with is already known. It was
7707 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
7708 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
7709 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
7710 kernel developers as
7711 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
7712 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
7713 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
7714 Lenovo forums, both for
7715 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
7716 2012-
11-
10</a
> and for
7717 <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
7718 03-
20-
2013</a
>. The problem do not only affect installation. The
7719 reports state that the disk lock up during use if many writes are done
7720 on the disk, so it is much no use to work around the installation
7721 problem and end up with a computer that can lock up at any moment.
7723 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
7724 available
</a
> that will lock up the hard drive after running a few
7725 minutes by writing to a file.
</p
>
7727 <p
>I
've contacted my supplier and asked how to handle this, and after
7728 contacting PCHELP Norway (request
01D1FDP) which handle support
7729 requests for Lenovo, his first suggestion was to upgrade the disk
7730 firmware. Unfortunately there is no newer firmware available from
7731 Lenovo, as my disk already have the most recent one (version LF1i). I
7732 hope to hear more from him today and hope the problem can be
7738 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
7739 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
7740 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
7741 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
7742 <description><p
>Half a year ago, I reported that I had to find a replacement for my
7743 trusty old Thinkpad X41. Unfortunately I did not have much time to
7744 spend on it, but today the replacement finally arrived. I ended up
7745 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
7746 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
7747 Wheezy as a roaming workstation, and it worked flawlessly. As I write
7748 this, it is installing what I hope will be a more final installation,
7749 with a encrypted hard drive to ensure any dope head stealing it end up
7750 with an expencive door stop.
</p
>
7752 <p
>I had a hard time trying to track down a good laptop, as my most
7753 important requirements (robust and with a good keyboard) are never
7754 listed in the feature list. But I did get good help from the search
7755 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
7756 allowed me to limit the list of interesting laptops based on my other
7757 requirements. A bit surprising that SSD disk are not disks, so I had
7758 to drop number of disks from my search parameters.
</p
>
7760 <p
>I am not quite convinced about the keyboard, as it is significantly
7761 wider than my old keyboard, and I have to stretch my hand a lot more
7762 to reach the edges. But the key response is fairly good and the
7763 individual key shape is fairly easy to handle, so I hope I will get
7764 used to it. My old X40 was starting to fail, and I really needed a
7765 new laptop now. :)
</p
>
7767 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
7772 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
7773 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
7774 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
7775 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
7776 <description><p
>It annoys me when the computer fail to do automatically what it is
7777 perfectly capable of, and I have to do it manually to get things
7778 working. One such task is to find out what firmware packages are
7779 needed to get the hardware on my computer working. Most often this
7780 affect the wifi card, but some times it even affect the RAID
7781 controller or the ethernet card. Today I pushed version
0.4 of the
7782 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
7783 including a new script isenkram-autoinstall-firmware handling the
7784 process of asking all the loaded kernel modules what firmware files
7785 they want, find debian packages providing these files and install the
7786 debian packages. Here is a test run on my laptop:
</p
>
7788 <p
><pre
>
7789 # isenkram-autoinstall-firmware
7790 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
7791 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
7792 info: locating packages with the requested firmware files
7793 info: Updating APT sources after adding non-free APT source
7794 info: trying to install firmware-ipw2x00
7797 Preconfiguring packages ...
7798 Selecting previously deselected package firmware-ipw2x00.
7799 (Reading database ...
259727 files and directories currently installed.)
7800 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
7801 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
7803 </pre
></p
>
7805 <p
>When all the requested firmware is present, a simple message is
7806 printed instead:
</p
>
7808 <p
><pre
>
7809 # isenkram-autoinstall-firmware
7810 info: did not find any firmware files requested by loaded kernel modules. exiting
7812 </pre
></p
>
7814 <p
>It could use some polish, but it is already working well and saving
7815 me some time when setting up new machines. :)
</p
>
7817 <p
>So, how does it work? It look at the set of currently loaded
7818 kernel modules, and look up each one of them using modinfo, to find
7819 the firmware files listed in the module meta-information. Next, it
7820 download the Contents file from a nearby APT mirror, and search for
7821 the firmware files in this file to locate the package with the
7822 requested firmware file. If the package is in the non-free section, a
7823 non-free APT source is added and the package is installed using
7824 <tt
>apt-get install
</tt
>. The end result is a slightly better working
7827 <p
>I hope someone find time to implement a more polished version of
7828 this script as part of the hw-detect debian-installer module, to
7829 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
7830 #
655507</a
>. There really is no need to insert USB sticks with
7831 firmware during a PXE install when the packages already are available
7832 from the nearby Debian mirror.
</p
>
7837 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
7838 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
7839 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
7840 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
7841 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
7842 the screen just turn black when Linux boot, either during installation
7843 or on first boot from the hard disk. I
've seen it once in a while the
7844 last few years, but only recently understood the cause. I
've seen it
7845 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
7846 The reason seem to be in the wiring of some laptops. The system to
7847 control the screen background light is inverted, so when Linux try to
7848 turn the brightness fully on, it end up turning it off instead. I do
7849 not know which Linux drivers are affected, but this post is about the
7850 i915 driver used by the
7851 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
7852 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
7854 <p
>The problem can be worked around two ways. Either by adding
7855 i915.invert_brightness=
1 as a kernel option, or by adding a file in
7856 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
7857 option when it load the i915 kernel module. On Debian and Ubuntu, it
7858 can be done by running these commands as root:
</p
>
7861 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
7862 update-initramfs -u -k all
7865 <p
>Since March
2012 there is
7866 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
7867 mechanism in the Linux kernel
</a
> to tell the i915 driver which
7868 hardware have this problem, and get the driver to invert the
7869 brightness setting automatically. To use it, one need to add a row in
7870 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
7871 intel_quirks array
</a
> in the driver source
7872 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
7873 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
7874 number (vendor number
8086 is assumed) and subdevice vendor and device
7877 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
7878 -vvnn
</tt
> for the video card in question:
</p
>
7880 <p
><pre
>
7881 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
7882 3rd Gen Core processor Graphics Controller [
8086:
0156] \
7883 (rev
09) (prog-if
00 [VGA controller])
7884 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
7885 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
7886 ParErr- Stepping- SE RR- FastB2B- DisINTx+
7887 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
7888 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
7890 Interrupt: pin A routed to IRQ
42
7891 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
7892 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
7893 Region
4: I/O ports at
4000 [size=
64]
7894 Expansion ROM at
<unassigned
> [disabled]
7895 Capabilities:
<access denied
>
7896 Kernel driver in use: i915
7897 </pre
></p
>
7899 <p
>The resulting intel_quirks entry would then look like this:
</p
>
7901 <p
><pre
>
7902 struct intel_quirk intel_quirks[] = {
7904 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
7905 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
7908 </pre
></p
>
7910 <p
>According to the kernel module instructions (as seen using
7911 <tt
>modinfo i915
</tt
>), information about hardware needing the
7912 invert_brightness flag should be sent to the
7913 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
7914 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
7915 developers. But my email about the laptop sent
2013-
06-
03 have not
7917 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
7918 web archive for the mailing list
</a
>, so I suspect they do not accept
7919 emails from non-subscribers. Because of this, I sent my patch also to
7920 the Debian bug tracking system instead as
7921 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
7922 sure the patch is not lost.
</p
>
7924 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
7925 with this problem working properly with Linux. If you use Gnome, your
7926 worries should be over at this point. But if you use KDE, there is
7927 something in KDE ignoring the invert_brightness setting and turning on
7928 the screen during login. I
've reported it to Debian as
7929 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
7930 have no idea yet how to figure out exactly what subsystem is doing
7931 this. Perhaps you can help? Perhaps you know what the Gnome
7932 developers did to handle this, and this can give a clue to the KDE
7933 developers? Or you know where in KDE the screen brightness is changed
7934 during login? If so, please update the BTS report (or get in touch if
7935 you do not know how to update BTS).
</p
>
7937 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
7938 acpi_backlight=vendor, to disable ACPI backlight support completely,
7939 as the ACPI information on the machine is trash and it is better to
7940 leave it to the intel video driver to control the screen
7941 backlight.
</p
>
7946 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
7947 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
7948 <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>
7949 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
7950 <description><p
>Two days ago, I asked
7951 <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
7952 I could install Linux on a Packard Bell EasyNote LV computer
7953 preinstalled with Windows
8</a
>. I found a solution, but am horrified
7954 with the obstacles put in the way of Linux users on a laptop with UEFI
7955 and Windows
8.
</p
>
7957 <p
>I never found out if the cause of my problems were the use of UEFI
7958 secure booting or fast boot. I suspect fast boot was the problem,
7959 causing the firmware to boot directly from HD without considering any
7960 key presses and alternative devices, but do not know UEFI settings
7961 enough to tell.
</p
>
7963 <p
>There is no way to install Linux on the machine in question without
7964 opening the box and disconnecting the hard drive! This is as far as I
7965 can tell, the only way to get access to the firmware setup menu
7966 without accepting the Windows
8 license agreement. I am told (and
7967 found description on how to) that it is possible to configure the
7968 firmware setup once booted into Windows
8. But as I believe the terms
7969 of that agreement are completely unacceptable, accepting the license
7970 was never an alternative. I do not enter agreements I do not intend
7971 to follow.
</p
>
7973 <p
>I feared I had to return the laptops and ask for a refund, and
7974 waste many hours on this, but luckily there was a way to get it to
7975 work. But I would not recommend it to anyone planning to run Linux on
7976 it, and I have become sceptical to Windows
8 certified laptops. Is
7977 this the way Linux will be forced out of the market place, by making
7978 it close to impossible for
"normal
" users to install Linux without
7979 accepting the Microsoft Windows license terms? Or at least not
7980 without risking to loose the warranty?
</p
>
7982 <p
>I
've updated the
7983 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
7984 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
7985 do not have to struggle as much as I did to get Linux into the
7988 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
7989 Michael Tokarev and others for feedback and ideas.
</p
>
7994 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
7995 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
7996 <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>
7997 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
7998 <description><p
>I
've run into quite a problem the last few days. I bought three
7999 new laptops for my parents and a few others. I bought Packard Bell
8000 Easynote LV to run Kubuntu on and use as their home computer. But I
8001 am completely unable to figure out how to install Linux on it. The
8002 computer is preinstalled with Windows
8, and I suspect it uses UEFI
8003 instead of a BIOS to boot.
</p
>
8005 <p
>The problem is that I am unable to get it to PXE boot, and unable
8006 to get it to boot the Linux installer from my USB stick. I have yet
8007 to try the DVD install, and still hope it will work. when I turn on
8008 the computer, there is no information on what buttons to press to get
8009 the normal boot menu. I expect to get some boot menu to select PXE or
8010 USB stick booting. When booting, it first ask for the language to
8011 use, then for some regional settings, and finally if I will accept the
8012 Windows
8 terms of use. As these terms are completely unacceptable to
8013 me, I have no other choice but to turn off the computer and try again
8014 to get it to boot the Linux installer.
</p
>
8016 <p
>I have gathered my findings so far on a Linlap page about the
8017 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
8018 EasyNote LV
</a
> model. If you have any idea how to get Linux
8019 installed on this machine, please get in touch or update that wiki
8020 page. If I can
't find a way to install Linux, I will have to return
8021 the laptop to the seller and find another machine for my parents.
</p
>
8023 <p
>I wonder, is this the way Linux will be forced out of the market
8024 using UEFI and
"secure boot
" by making it impossible to install Linux
8025 on new Laptops?
</p
>
8030 <title>How to transform a Debian based system to a Debian Edu installation
</title>
8031 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
8032 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
8033 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
8034 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
8035 an operating system based on Debian intended for use in schools. It
8036 contain a turn-key solution for the computer network provided to
8037 pupils in the primary schools. It provide both the central server,
8038 network boot servers and desktop environments with heaps of
8039 educational software. The project was founded almost
12 years ago,
8040 2001-
07-
02. If you want to support the project, which is in need for
8041 cash to fund developer gatherings and other project related activity,
8042 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
8043 donate some money
</a
>.
8045 <p
>A topic that come up again and again on the Debian Edu mailing
8046 lists and elsewhere, is the question on how to transform a Debian or
8047 Ubuntu installation into a Debian Edu installation. It isn
't very
8048 hard, and last week I wrote a script to replicate the steps done by
8049 the Debian Edu installer.
</p
>
8051 <p
>The script,
8052 <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/
>
8053 in the debian-edu-config package, will go through these six steps and
8054 transform an existing Debian Wheezy or Ubuntu (untested) installation
8055 into a Debian Edu Workstation:
</p
>
8059 <li
>Add skolelinux related APT sources.
</li
>
8060 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
8061 <li
>Install debian-edu-install to load preseeding values and pull in
8062 our configuration.
</li
>
8063 <li
>Preseed debconf database with profile setup in
8064 /etc/debian-edu/config, and run tasksel to install packages
8065 according to the profile specified in the config above,
8066 overriding some of the Debian automation machinery.
</li
>
8067 <li
>Run debian-edu-cfengine-D installation to configure everything
8068 that could not be done using preseeding.
</li
>
8069 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
8073 <p
>There are some steps in the Debian Edu installation that can not be
8074 replicated like this. Disk partitioning and LVM setup, for example.
8075 So this script just assume there is enough disk space to install all
8076 the needed packages.
</p
>
8078 <p
>The script was created to help a Debian Edu student working on
8079 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
8080 Debian Edu client, and using it he can take the existing
8081 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
8082 transform it into a fully functioning Debian Edu Workstation (or
8083 Roaming Workstation, or whatever :).
</p
>
8085 <p
>The default setting in the script is to create a KDE Workstation.
8086 If a LXDE based Roaming workstation is wanted instead, modify the
8087 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
8089 <p
><pre
>
8090 PROFILE=
"Roaming-Workstation
"
8091 DESKTOP=
"lxde
"
8092 </pre
></p
>
8094 <p
>The script could even become useful to set up Debian Edu servers in
8095 the cloud, by starting with a virtual Debian installation at some
8096 virtual hosting service and setting up all the services on first
8102 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
8103 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
8104 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
8105 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
8106 <description><P
>In January,
8107 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
8108 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
8109 channel #debian-lego
</a
>, for those of us in the Debian and Linux
8110 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
8111 marvellous construction system from Denmark. We also created
8112 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
8113 a place to take notes and write down our plans and hopes. And several
8114 people showed up to help. I was very happy to see the effect of my
8115 call. Since the small start, we have a debtags tag
8116 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
8117 tag for LEGO related packages, and now count
10 packages related to
8118 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
8120 <p
><table
>
8121 <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
>
8122 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
8123 <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
>
8124 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
8125 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
8126 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
8127 <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
>
8128 <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
>
8129 <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
>
8130 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
8131 </table
></p
>
8133 <p
>Some of these are available in Wheezy, and all but one are
8134 currently available in Jessie/testing. leocad is so far only
8135 available in experimental.
</p
>
8137 <p
>If you care about LEGO in Debian, please join us on IRC and help
8138 adding the rest of the great free software tools available on Linux
8139 for LEGO designers.
</p
>
8144 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
8145 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
8146 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
8147 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
8148 <description><p
>When I woke up this morning, I was very happy to see that the
8149 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
8150 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
8151 Debian release, and I expect to move my machines at home over to it fairly
8154 <p
>The new debian release contain heaps of new stuff, and one program
8155 in particular make me very happy to see included. The
8156 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
8157 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
8158 included for the first time. Alongside similar programs like
8159 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
8160 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
8161 it allow for visual programming where syntax errors can not happen,
8162 and a friendly programming environment for learning to control the
8163 computer. Scratch will also be included in the next release of Debian
8166 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
8167 Edu/Skolelinux release too. The
8168 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
8169 alpha release
</a
> went out last week, and the next should soon
8175 <title>Isenkram
0.2 finally in the Debian archive
</title>
8176 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
8177 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
8178 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
8179 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
8180 package
</a
> finally made it into the archive, after lingering in NEW
8181 for many months. I uploaded it to the Debian experimental suite
8182 2013-
01-
27, and today it was accepted into the archive.
</p
>
8184 <p
>Isenkram is a system for suggesting to users what packages to
8185 install to work with a pluggable hardware device. The suggestion pop
8186 up when the device is plugged in. For example if a Lego Mindstorm NXT
8187 is inserted, it will suggest to install the program needed to program
8188 the NXT controller. Give it a go, and report bugs and suggestions to
8194 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
8195 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
8196 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
8197 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
8198 <description><p
>My
8199 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
8200 bitcoin related blog post
</a
> mentioned that the new
8201 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
8202 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
8203 2013-
01-
19, and have been available in unstable since then. It was
8204 automatically copied to Ubuntu, and is available in their Raring
8205 version too.
</p
>
8207 <p
>But there is a strange problem with the build that block this new
8208 version from being available on the i386 and kfreebsd-i386
8209 architectures. For some strange reason, the autobuilders in Debian
8210 for these architectures fail to run the test suite on these
8211 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
8212 We are so far unable to reproduce it when building it manually, and
8213 no-one have been able to propose a fix. If you got an idea what is
8214 failing, please let us know via the BTS.
</p
>
8216 <p
>One feature that is annoying me with of the bitcoin client, because
8217 I often run low on disk space, is the fact that the client will exit
8218 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
8219 #
696715</a
>). So make sure you have enough disk space when you run
8222 <p
>As usual, if you use bitcoin and want to show your support of my
8223 activities, please send Bitcoin donations to my address
8224 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
8229 <title>Welcome to the world, Isenkram!
</title>
8230 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
8231 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
8232 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
8233 <description><p
>Yesterday, I
8234 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
8235 for testers
</a
> for my prototype for making Debian better at handling
8236 pluggable hardware devices, which I
8237 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
8238 out to create
</a
> earlier this month. Several valuable testers showed
8239 up, and caused me to really want to to open up the development to more
8240 people. But before I did this, I want to come up with a sensible name
8241 for this project. Today I finally decided on a new name, and I have
8242 renamed the project from hw-support-handler to this new name. In the
8243 process, I moved the source to git and made it available as a
8244 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
8245 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
8246 To fetch and build the latest version of the source, use
</p
>
8249 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8250 cd isenkram
&& git-buildpackage -us -uc
8253 <p
>I have not yet adjusted all files to use the new name yet. If you
8254 want to hack on the source or improve the package, please go ahead.
8255 But please talk to me first on IRC or via email before you do major
8256 changes, to make sure we do not step on each others toes. :)
</p
>
8258 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
8259 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8260 stuff, in other words. I
've been told it is the Norwegian variant of
8261 the German word eisenkram, for those that are familiar with that
8264 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
8265 instructions, to avoid confusing people with an error from the signing
8268 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
8269 clone argument to avoid the need for authentication.
</p
>
8274 <title>First prototype ready making hardware easier to use in Debian
</title>
8275 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
8276 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
8277 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
8278 <description><p
>Early this month I set out to try to
8279 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
8280 the Debian support for pluggable hardware devices
</a
>. Now my
8281 prototype is working, and it is ready for a larger audience. To test
8283 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
8284 from the Debian Edu subversion repository
</a
>, build and install the
8285 package. You might have to log out and in again activate the
8286 autostart script.
</p
>
8288 <p
>The design is simple:
</p
>
8292 <li
>Add desktop entry in /usr/share/autostart/ causing a program
8293 hw-support-handlerd to start when the user log in.
</li
>
8295 <li
>This program listen for kernel events about new hardware (directly
8296 from the kernel like udev does), not using HAL dbus events as I
8297 initially did.
</li
>
8299 <li
>When new hardware is inserted, look up the hardware modalias in
8300 the APT database, a database
8301 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
8302 via HTTP
</a
> and a database available as part of the package.
</li
>
8304 <li
>If a package is mapped to the hardware in question, the package
8305 isn
't installed yet and this is the first time the hardware was
8306 plugged in, show a desktop notification suggesting to install the
8307 package or packages.
</li
>
8309 <li
>If the user click on the
'install package now
' button, ask
8310 aptdaemon via the PackageKit API to install the requrired package.
</li
>
8312 <li
>aptdaemon ask for root password or sudo password, and install the
8313 package while showing progress information in a window.
</li
>
8317 <p
>I still need to come up with a better name for the system. Here
8318 are some screen shots showing the prototype in action. First the
8319 notification, then the password request, and finally the request to
8320 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
8322 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
8323 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
8324 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
8325 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
8326 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
8328 <p
>The prototype still need to be improved with longer timeouts, but
8329 is already useful. The database of hardware to package mappings also
8330 need more work. It is currently compatible with the Ubuntu way of
8331 storing such information in the package control file, but could be
8332 changed to use other formats instead or in addition to the current
8333 method. I
've dropped the use of discover for this mapping, as the
8334 modalias approach is more flexible and easier to use on Linux as long
8335 as the Linux kernel expose its modalias strings directly.
</p
>
8337 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
8338 here is the command required to check out and build the source: Use
8339 '<tt
>svn checkout
8340 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8341 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
8342 devscripts package.
</p
>
8344 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
8345 renamed to Isenkram and the source moved from the Debian Edu
8346 subversion repository to a Debian collab-maint git repository. See
8347 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
8348 instructions
</a
> for details.
</p
>
8353 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
8354 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
8355 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
8356 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
8357 <description><p
>This Christmas my trusty old laptop died. It died quietly and
8358 suddenly in bed. With a quiet whimper, it went completely quiet and
8359 black. The power button was no longer able to turn it on. It was a
8360 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8361 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8362 Compaq I had before that. Now I need to find a replacement. To keep
8363 going during Christmas, I moved the one year old SSD disk to my old
8364 X40 where it fitted (only one I had left that could use it), but it is
8365 not a durable solution.
8367 <p
>My laptop needs are fairly modest. This is my wishlist from when I
8368 got a new one more than
10 years ago. It still holds true.:)
</p
>
8372 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
8373 than A4).
</li
>
8374 <li
>Robust, it will be in my backpack every day.
</li
>
8375 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
8376 <li
>Long battery life time. Preferable a week.
</li
>
8377 <li
>Internal WIFI network card.
</li
>
8378 <li
>Internal Twisted Pair network card.
</li
>
8379 <li
>Some USB slots (
2-
3 is plenty)
</li
>
8380 <li
>Good keyboard - similar to the Thinkpad.
</li
>
8381 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
8383 <li
>Hardware supported by Debian Stable, ie the default kernel and
8384 X.org packages.
</li
>
8385 <li
>Quiet, preferably fan free (or at least not using the fan most of
8390 <p
>You will notice that there are no RAM and CPU requirements in the
8391 list. The reason is simply that the specifications on laptops the
8392 last
10-
15 years have been sufficient for my needs, and I have to look
8393 at other features to choose my laptop. But are there still made as
8394 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8395 robust, and Thinkpads seem to be heading in the wrong direction since
8396 Lenovo took over. But I
've been told that X220 and X1 Carbon might
8397 still be useful.
</p
>
8399 <p
>Perhaps I should rethink my needs, and look for a pad with an
8400 external keyboard? I
'll have to check the
8401 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
8402 well-supported laptops, or perhaps just buy one preinstalled from one
8403 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
8404 Pre-loaded site
</a
>.
</p
>
8409 <title>How to find a browser plugin supporting a given MIME type
</title>
8410 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
8411 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
8412 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
8413 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
8414 install to get support for a given MIME type. Thanks to
8415 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
8416 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
8417 Unfortunately, not very many packages provide the needed meta
8418 information, Anyway, here is a small script to look up all browser
8419 plugin packages announcing ther MIME support using this specification:
</p
>
8425 def pkgs_handling_mimetype(mimetype):
8430 version = pkg.candidate
8432 version = pkg.installed
8435 record = version.record
8436 if not record.has_key(
'Npp-MimeType
'):
8438 mime_types = record[
'Npp-MimeType
'].split(
',
')
8439 for t in mime_types:
8440 t = t.rstrip().strip()
8442 thepkgs.append(pkg.name)
8444 mimetype =
"audio/ogg
"
8445 if
1 < len(sys.argv):
8446 mimetype = sys.argv[
1]
8447 print
"Browser plugin packages supporting %s:
" % mimetype
8448 for pkg in pkgs_handling_mimetype(mimetype):
8449 print
" %s
" %pkg
8452 <p
>It can be used like this to look up a given MIME type:
</p
>
8455 % ./apt-find-browserplug-for-mimetype
8456 Browser plugin packages supporting audio/ogg:
8458 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
8459 Browser plugin packages supporting application/x-shockwave-flash:
8460 browser-plugin-gnash
8464 <p
>In Ubuntu this mechanism is combined with support in the browser
8465 itself to query for plugins and propose to install the needed
8466 packages. It would be great if Debian supported such feature too. Is
8467 anyone working on adding it?
</p
>
8469 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
8470 request for icweasel support for this feature is
8471 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
8472 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
8473 of manpower and wish for a different design is the reason thus feature
8474 is not yet in iceweasel from Debian.
</p
>
8479 <title>What is the most supported MIME type in Debian?
</title>
8480 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
8481 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
8482 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
8483 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
8484 proposal to add AppStream information to the Debian archive
</a
>, is a
8485 proposal to make it possible for a Desktop application to propose to
8486 the user some package to install to gain support for a given MIME
8487 type, font, library etc. that is currently missing. With such
8488 mechanism in place, it would be possible for the desktop to
8489 automatically propose and install leocad if some LDraw file is
8490 downloaded by the browser.
</p
>
8492 <p
>To get some idea about the current content of the archive, I decided
8493 to write a simple program to extract all .desktop files from the
8494 Debian archive and look up the claimed MIME support there. The result
8496 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
8497 site
</a
>. Using the collected information, it become possible to
8498 answer the question in the title. Here are the
20 most supported MIME
8499 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
8500 The complete list is available from the link above.
</p
>
8502 <p
><strong
>Debian Stable:
</strong
></p
>
8506 ----- -----------------------
8522 18 application/x-ogg
8529 <p
><strong
>Debian Testing:
</strong
></p
>
8533 ----- -----------------------
8549 18 application/x-ogg
8556 <p
><strong
>Debian Unstable:
</strong
></p
>
8560 ----- -----------------------
8577 18 application/x-ogg
8583 <p
>I am told that PackageKit can provide an API to access the kind of
8584 information mentioned in DEP-
11. I have not yet had time to look at
8585 it, but hope the PackageKit people in Debian are on top of these
8588 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
8589 discovering a typo in my script.
</p
>
8594 <title>Using modalias info to find packages handling my hardware
</title>
8595 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
8596 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
8597 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
8598 <description><p
>Yesterday, I wrote about the
8599 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
8600 values provided by the Linux kernel
</a
> following my hope for
8601 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
8602 dongle support in Debian
</a
>. Using this knowledge, I have tested how
8603 modalias values attached to package names can be used to map packages
8604 to hardware. This allow the system to look up and suggest relevant
8605 packages when I plug in some new hardware into my machine, and replace
8606 discover and discover-data as the database used to map hardware to
8609 <p
>I create a modaliases file with entries like the following,
8610 containing package name, kernel module name (if relevant, otherwise
8611 the package name) and globs matching the relevant hardware
8614 <p
><blockquote
>
8615 Package: package-name
8616 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
8617 </blockquote
></p
>
8619 <p
>It is fairly trivial to write code to find the relevant packages
8620 for a given modalias value using this file.
</p
>
8622 <p
>An entry like this would suggest the video and picture application
8623 cheese for many USB web cameras (interface bus class
0E01):
</p
>
8625 <p
><blockquote
>
8627 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
8628 </blockquote
></p
>
8630 <p
>An entry like this would suggest the pcmciautils package when a
8631 CardBus bridge (bus class
0607) PCI device is present:
</p
>
8633 <p
><blockquote
>
8634 Package: pcmciautils
8635 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
8636 </blockquote
></p
>
8638 <p
>An entry like this would suggest the package colorhug-client when
8639 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
8641 <p
><blockquote
>
8642 Package: colorhug-client
8643 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
8644 </blockquote
></p
>
8646 <p
>I believe the format is compatible with the format of the Packages
8647 file in the Debian archive. Ubuntu already uses their Packages file
8648 to store their mappings from packages to hardware.
</p
>
8650 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
8651 announce the hardware it support in a way my prototype understand.
8652 This allow those publishing packages in an APT source outside the
8653 Debian archive as well as those backporting packages to make sure the
8654 hardware mapping are included in the package meta information. I
've
8655 tested such header in the pymissile package, and its modalias mapping
8656 is working as it should with my prototype. It even made it to Ubuntu
8659 <p
>To test if it was possible to look up supported hardware using only
8660 the shell tools available in the Debian installer, I wrote a shell
8661 implementation of the lookup code. The idea is to create files for
8662 each modalias and let the shell do the matching. Please check out and
8664 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
8665 shell script. It run without any extra dependencies and fetch the
8666 hardware mappings from the Debian archive and the subversion
8667 repository where I currently work on my prototype.
</p
>
8669 <p
>When I use it on a machine with a yubikey inserted, it suggest to
8670 install yubikey-personalization:
</p
>
8672 <p
><blockquote
>
8673 % ./hw-support-lookup
8674 <br
>yubikey-personalization
8676 </blockquote
></p
>
8678 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
8679 propose to install the pcmciautils package:
</p
>
8681 <p
><blockquote
>
8682 % ./hw-support-lookup
8683 <br
>pcmciautils
8685 </blockquote
></p
>
8687 <p
>If you know of any hardware-package mapping that should be added to
8688 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
8689 database
</a
>, please tell me about it.
</p
>
8691 <p
>It could be possible to generate several of the mappings between
8692 packages and hardware. One source would be to look at packages with
8693 kernel modules, ie packages with *.ko files in /lib/modules/, and
8694 extract their modalias information. Another would be to look at
8695 packages with udev rules, ie packages with files in
8696 /lib/udev/rules.d/, and extract their vendor/model information to
8697 generate a modalias matching rule. I have not tested any of these to
8698 see if it work.
</p
>
8700 <p
>If you want to help implementing a system to let us propose what
8701 packages to install when new hardware is plugged into a Debian
8702 machine, please send me an email or talk to me on
8703 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
8708 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
8709 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
8710 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
8711 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
8712 <description><p
>While looking into how to look up Debian packages based on hardware
8713 information, to find the packages that support a given piece of
8714 hardware, I refreshed my memory regarding modalias values, and decided
8715 to document the details. Here are my findings so far, also available
8717 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
8718 Debian Edu subversion repository
</a
>:
8720 <p
><strong
>Modalias decoded
</strong
></p
>
8722 <p
>This document try to explain what the different types of modalias
8723 values stands for. It is in part based on information from
8724 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
8725 &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;,
8726 &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
8727 &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;.
8729 <p
>The modalias entries for a given Linux machine can be found using
8730 this shell script:
</p
>
8733 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
8736 <p
>The supported modalias globs for a given kernel module can be found
8737 using modinfo:
</p
>
8740 % /sbin/modinfo psmouse | grep alias:
8741 alias: serio:ty05pr*id*ex*
8742 alias: serio:ty01pr*id*ex*
8746 <p
><strong
>PCI subtype
</strong
></p
>
8748 <p
>A typical PCI entry can look like this. This is an Intel Host
8749 Bridge memory controller:
</p
>
8751 <p
><blockquote
>
8752 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
8753 </blockquote
></p
>
8755 <p
>This represent these values:
</p
>
8760 sv
00001028 (subvendor)
8761 sd
000001AD (subdevice)
8763 sc
00 (bus subclass)
8767 <p
>The vendor/device values are the same values outputted from
'lspci
8768 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
8769 0600. The
0600 class is a host bridge. Other useful bus values are
8770 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
8772 <p
>Not sure how to figure out the interface value, nor what it
8775 <p
><strong
>USB subtype
</strong
></p
>
8777 <p
>Some typical USB entries can look like this. This is an internal
8778 USB hub in a laptop:
</p
>
8780 <p
><blockquote
>
8781 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
8782 </blockquote
></p
>
8784 <p
>Here is the values included in this alias:
</p
>
8787 v
1D6B (device vendor)
8788 p
0001 (device product)
8790 dc
09 (device class)
8791 dsc
00 (device subclass)
8792 dp
00 (device protocol)
8793 ic
09 (interface class)
8794 isc
00 (interface subclass)
8795 ip
00 (interface protocol)
8798 <p
>The
0900 device class/subclass means hub. Some times the relevant
8799 class is in the interface class section. For a simple USB web camera,
8800 these alias entries show up:
</p
>
8802 <p
><blockquote
>
8803 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
8804 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
8805 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
8806 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
8807 </blockquote
></p
>
8809 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
8810 camera),
0101 is audio control device and
0102 is audio streaming (aka
8811 microphone). Thus this is a camera with microphone included.
</p
>
8813 <p
><strong
>ACPI subtype
</strong
></p
>
8815 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
8816 receiver in a Thinkpad X40:
</p
>
8818 <p
><blockquote
>
8819 acpi:IBM0071:PNP0511:
8820 </blockquote
></p
>
8822 <p
>The values between the colons are IDs.
</p
>
8824 <p
><strong
>DMI subtype
</strong
></p
>
8826 <p
>The DMI table contain lots of information about the computer case
8827 and model. This is an entry for a IBM Thinkpad X40, fetched from
8828 /sys/devices/virtual/dmi/id/modalias:
</p
>
8830 <p
><blockquote
>
8831 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
8832 </blockquote
></p
>
8834 <p
>The values present are
</p
>
8837 bvn IBM (BIOS vendor)
8838 bvr
1UETB
6WW(
1.66) (BIOS version)
8839 bd
06/
15/
2005 (BIOS date)
8840 svn IBM (system vendor)
8841 pn
2371H4G (product name)
8842 pvr ThinkPadX40 (product version)
8843 rvn IBM (board vendor)
8844 rn
2371H4G (board name)
8845 rvr NotAvailable (board version)
8846 cvn IBM (chassis vendor)
8847 ct
10 (chassis type)
8848 cvr NotAvailable (chassis version)
8851 <p
>The chassis type
10 is Notebook. Other interesting values can be
8852 found in the dmidecode source:
</p
>
8856 4 Low Profile Desktop
8869 17 Main Server Chassis
8870 18 Expansion Chassis
8872 20 Bus Expansion Chassis
8873 21 Peripheral Chassis
8875 23 Rack Mount Chassis
8884 <p
>The chassis type values are not always accurately set in the DMI
8885 table. For example my home server is a tower, but the DMI modalias
8886 claim it is a desktop.
</p
>
8888 <p
><strong
>SerIO subtype
</strong
></p
>
8890 <p
>This type is used for PS/
2 mouse plugs. One example is from my
8891 test machine:
</p
>
8893 <p
><blockquote
>
8894 serio:ty01pr00id00ex00
8895 </blockquote
></p
>
8897 <p
>The values present are
</p
>
8906 <p
>This type is supported by the psmouse driver. I am not sure what
8907 the valid values are.
</p
>
8909 <p
><strong
>Other subtypes
</strong
></p
>
8911 <p
>There are heaps of other modalias subtypes according to
8912 file2alias.c. There is the rest of the list from that source: amba,
8913 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
8914 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
8915 vmbus, x86cpu and zorro. I did not spend time documenting all of
8916 these, as they do not seem relevant for my intended use with mapping
8917 hardware to packages when new stuff is inserted during run time.
</p
>
8919 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
8921 <p
>To check which kernel modules provide support for a given modalias,
8922 one can use the following shell script:
</p
>
8925 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
8926 echo
"$id
" ; \
8927 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
8931 <p
>The output can look like this (only the first few entries as the
8932 list is very long on my test machine):
</p
>
8936 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
8938 FATAL: Module acpi:device: not found.
8940 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
8941 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
8942 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
8943 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
8944 acpi:IBM0071:PNP0511:
8945 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
8946 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
8947 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
8951 <p
>If you want to help implementing a system to let us propose what
8952 packages to install when new hardware is plugged into a Debian
8953 machine, please send me an email or talk to me on
8954 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
8956 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
8957 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
8958 in /sys/ with space in them.
</p
>
8963 <title>Moved the pymissile Debian packaging to collab-maint
</title>
8964 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
8965 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
8966 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
8967 <description><p
>As part of my investigation on how to improve the support in Debian
8968 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
8969 Launcher and updated the Debian package
8970 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
8971 sure udev will fix the device permissions when it is plugged in. I
8972 also added a
"Modaliases
" header to test it in the Debian archive and
8973 hopefully make the package be proposed by jockey in Ubuntu when a user
8974 plug in his rocket launcher. In the process I moved the source to a
8975 git repository under collab-maint, to make it easier for any DD to
8976 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
8977 is not very active, but the software still work for me even after five
8978 years of relative silence. The new git repository is not listed in
8979 the uploaded package yet, because I want to test the other changes a
8980 bit more before I upload the new version. If you want to check out
8981 the new version with a .desktop file included, visit the
8982 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
8983 view
</a
> or use
"<tt
>git clone
8984 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
8989 <title>Lets make hardware dongles easier to use in Debian
</title>
8990 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
8991 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
8992 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
8993 <description><p
>One thing that annoys me with Debian and Linux distributions in
8994 general, is that there is a great package management system with the
8995 ability to automatically install software packages by downloading them
8996 from the distribution mirrors, but no way to get it to automatically
8997 install the packages I need to use the hardware I plug into my
8998 machine. Even if the package to use it is easily available from the
8999 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
9000 suggest to automatically install the python-nxt, nbc and t2n packages
9001 I need to talk to it. When I plug in a Yubikey, it could propose the
9002 yubikey-personalization package. The information required to do this
9003 is available, but no-one have pulled all the pieces together.
</p
>
9005 <p
>Some years ago, I proposed to
9006 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
9007 the discover subsystem to implement this
</a
>. The idea is fairly
9012 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
9013 starting when a user log in.
</li
>
9015 <li
>Set this program up to listen for kernel events emitted when new
9016 hardware is inserted into the computer.
</li
>
9018 <li
>When new hardware is inserted, look up the hardware ID in a
9019 database mapping to packages, and take note of any non-installed
9020 packages.
</li
>
9022 <li
>Show a message to the user proposing to install the discovered
9023 package, and make it easy to install it.
</li
>
9027 <p
>I am not sure what the best way to implement this is, but my
9028 initial idea was to use dbus events to discover new hardware, the
9029 discover database to find packages and
9030 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
9033 <p
>Yesterday, I found time to try to implement this idea, and the
9034 draft package is now checked into
9035 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
9036 Debian Edu subversion repository
</a
>. In the process, I updated the
9037 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
9038 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
9039 the relevant packages in Debian, and uploaded a new version
9040 2.2013.01.09 to unstable. I also discovered that the current
9041 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
9042 package in Debian no longer discovered any USB devices, because
9043 /proc/bus/usb/devices is no longer present. I ported it to use
9044 libusb as a fall back option to get it working. The fixed package
9045 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
9046 because of the freeze).
</p
>
9048 <p
>With this prototype in place, I can insert my Yubikey, and get this
9049 desktop notification to show up (only once, the first time it is
9050 inserted):
</p
>
9052 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
9054 <p
>For this prototype to be really useful, some way to automatically
9055 install the proposed packages by pressing the
"Please install
9056 program(s)
" button should to be implemented.
</p
>
9058 <p
>If this idea seem useful to you, and you want to help make it
9059 happen, please help me update the discover-data database with mappings
9060 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
9061 list the package you would like to have installed when a given
9062 hardware device is inserted into your computer, and report bugs using
9063 reportbug if it isn
't. Or, if you know of a better way to provide
9064 such mapping, please let me know.
</p
>
9066 <p
>This prototype need more work, and there are several questions that
9067 should be considered before it is ready for production use. Is dbus
9068 the correct way to detect new hardware? At the moment I look for HAL
9069 dbus events on the system bus, because that is the events I could see
9070 on my Debian Squeeze KDE desktop. Are there better events to use?
9071 How should the user be notified? Is the desktop notification
9072 mechanism the best option, or should the background daemon raise a
9073 popup instead? How should packages be installed? When should they
9074 not be installed?
</p
>
9076 <p
>If you want to help getting such feature implemented in Debian,
9077 please send me an email. :)
</p
>
9082 <title>New IRC channel for LEGO designers using Debian
</title>
9083 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
9084 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
9085 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
9086 <description><p
>During Christmas, I have worked a bit on the Debian support for
9087 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
9088 NXT
</a
>. My son and I have played a bit with my NXT set, and I
9089 discovered I had to build all the tools myself because none were
9090 already in Debian Squeeze. If Debian support for LEGO is something
9091 you care about, please join me on the IRC channel
9092 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
9093 irc.debian.org). There is a lot that could be done to improve the
9094 Debian support for LEGO designers. For example both CAD software
9095 and Mindstorm compilers are missing. :)
</p
>
9097 <p
>Update
2012-
01-
03: A
9098 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
9099 including links to Lego related packages is now available.
</p
>
9104 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
9105 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
9106 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
9107 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
9108 <description><p
>Let me start by wishing you all marry Christmas and a happy new
9109 year! I hope next year will prove to be a good year.
</p
>
9111 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
9112 decentralised
"currency
" that allow people to transfer bitcoins
9113 between each other with minimal overhead, is a very interesting
9114 experiment. And as I wrote a few days ago, the bitcoin situation in
9115 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
9116 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
9117 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
9118 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
9119 for one of the ftpmasters to approve the new bitcoin-qt package
9122 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
9123 team in Debian, you can easily test the package in Debian Squeeze
9124 using the following steps to get a set of working packages:
</p
>
9126 <blockquote
><pre
>
9127 git clone git://git.debian.org/git/collab-maint/bitcoin
9129 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
9130 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
9131 </pre
></blockquote
>
9133 <p
>You might have to install some build dependencies as well. The
9134 list of commands should give you two packages, bitcoind and
9135 bitcoin-qt, ready for use in a Squeeze environment. Note that the
9136 client will download the complete set of bitcoin
"blocks
", which need
9137 around
5.6 GiB of data on my machine at the moment. Make sure your
9138 ~/.bitcoin/ directory have lots of spare room if you want to download
9139 all the blocks. The client will warn if the disk is getting full, so
9140 there is not really a problem if you got too little room, but you will
9141 not be able to get all the features out of the client.
</p
>
9143 <p
>As usual, if you use bitcoin and want to show your support of my
9144 activities, please send Bitcoin donations to my address
9145 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9150 <title>A word on bitcoin support in Debian
</title>
9151 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
9152 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
9153 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
9154 <description><p
>It has been a while since I wrote about
9155 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
9156 peer-to-peer based crypto-currency, and the reason is simply that I
9157 have been busy elsewhere. But two days ago, I started looking at the
9158 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
9159 Debian
</a
> again to try to recover my old bitcoin wallet. The package
9160 is now maintained by a
9161 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
9162 people
</a
>, and the grunt work had already been done by this team. We
9163 owe a huge thank you to all these team members. :)
9164 But I was sad to discover that the bitcoin client is missing in
9165 Wheezy. It is only available in Sid (and an outdated client from
9166 backports). The client had several RC bugs registered in BTS blocking
9167 it from entering testing. To try to help the team and improve the
9168 situation, I spent some time providing patches and triaging the bug
9169 reports. I also had a look at the bitcoin package available from Matt
9171 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
9172 Ubuntu
</a
>, and moved the useful pieces from that version into the
9173 Debian package.
</p
>
9175 <p
>After checking with the main package maintainer Jonas Smedegaard on
9176 IRC, I pushed several patches into the collab-maint git repository to
9177 improve the package. It now contains fixes for the RC issues (not from
9178 me, but fixed by Scott Howard), build rules for a Qt GUI client
9179 package, konqueror support for the bitcoin: URI and bash completion
9180 setup. As I work on Debian Squeeze, I also created
9181 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
9182 patch to backport
</a
> the latest version. Jonas is going to look at
9183 it and try to integrate it into the git repository before uploading a
9184 new version to unstable.
9186 <p
>I would very much like bitcoin to succeed, to get rid of the
9187 centralized control currently exercised in the monetary system. I
9188 find it completely unacceptable that the USA government is collecting
9189 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
9190 that the major credit card companies can block legal money
9191 transactions to Wikileaks. But for bitcoin to succeed, more people
9192 need to use bitcoins, and more people need to accept bitcoins when
9193 they sell products and services. Improving the bitcoin support in
9194 Debian is a small step in the right direction, but not enough.
9195 Unfortunately the user experience when browsing the web and wanting to
9196 pay with bitcoin is still not very good. The bitcoin: URI is a step
9197 in the right direction, but need to work in most or every browser in
9198 use. Also the bitcoin-qt client is too heavy to fire up to do a
9199 quick transaction. I believe there are other clients available, but
9200 have not tested them.
</p
>
9203 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
9204 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
9205 I received
20.15 BTC so far on the address I provided in my blog two
9206 years ago, as can be
9207 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
9208 on the blockexplorer service
</a
>. Thank you everyone for your
9209 donation. The blockexplorer service demonstrates quite well that
9210 bitcoin is not quite anonymous and untracked. :) I wonder if the
9211 number of users have gone up since then. If you use bitcoin and want
9212 to show your support of my activity, please send Bitcoin donations to
9213 the same address as last time,
9214 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9219 <title>Git repository for song book for Computer Scientists
</title>
9220 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
9221 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
9222 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
9223 <description><p
>As I
9224 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
9225 this summer
</a
>, I have created a Computer Science song book a few
9226 years ago, and today I finally found time to create a public
9227 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
9228 repository for the project
</a
>.
</p
>
9230 <p
>If you want to help out, please clone the source and submit patches
9231 to the HTML version. To generate the PDF and PostScript version,
9232 please use prince XML, or let me know about a useful free software
9233 processor capable of creating a good looking PDF from the HTML.
</p
>
9235 <p
>Want to sing? You can still find the song book in HTML, PDF and
9236 PostScript formats at
9237 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
9238 Science Songbook
</a
>.
</p
>
9243 <title>Gratulerer med
19-årsdagen, Debian!
</title>
9244 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
9245 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
9246 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
9247 <description><p
>I dag fyller
9248 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
9249 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
9250 si gratulerer med dagen, Debian!
</p
>
9255 <title>Song book for Computer Scientists
</title>
9256 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
9257 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
9258 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
9259 <description><p
>Many years ago, while studying Computer Science at the
9260 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
9261 collecting computer related songs for use at parties. The original
9262 version was written in LaTeX, but a few years ago I got help from
9263 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9264 while keeping the ability to create a nice book in PDF format. I have
9265 not had time to maintain the book for a while now, and guess I should
9266 put it up on some public version control repository where others can
9267 help me extend and update the book. If anyone is volunteering to help
9268 me with this, send me an email. Also let me know if there are songs
9269 missing in my book.
</p
>
9271 <p
>I have not mentioned the book on my blog so far, and it occured to
9272 me today that I really should let all my readers share the joys of
9273 singing out load about programming, computers and computer networks.
9274 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
9275 12</a
> is about to start (and I am not going). Want to sing? Check
9276 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
9277 Computer Science Songbook
</a
>.
9282 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
9283 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
9284 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
9285 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
9286 <description><p
>At work we have heaps of servers. I believe the total count is
9287 around
1000 at the moment. To be able to get help from the vendors
9288 when something go wrong, we want to keep the firmware on the servers
9289 up to date. If the firmware isn
't the latest and greatest, the
9290 vendors typically refuse to start debugging any problems until the
9291 firmware is upgraded. So before every reboot, we want to upgrade the
9292 firmware, and we would really like everyone handling servers at the
9293 university to do this themselves when they plan to reboot a machine.
9294 For that to happen we at the unix server admin group need to provide
9295 the tools to do so.
</p
>
9297 <p
>To make firmware upgrading easier, I am working on a script to
9298 fetch and install the latest firmware for the servers we got. Most of
9299 our hardware are from Dell and HP, so I have focused on these servers
9300 so far. This blog post is about the Dell part.
</P
>
9302 <p
>On the Dell FTP site I was lucky enough to find
9303 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
9304 with firmware information for all
11th generation servers, listing
9305 which firmware should be used on a given model and where on the FTP
9306 site I can find it. Using a simple perl XML parser I can then
9307 download the shell scripts Dell provides to do firmware upgrades from
9308 within Linux and reboot when all the firmware is primed and ready to
9309 be activated on the first reboot.
</p
>
9311 <p
>This is the Dell related fragment of the perl code I am working on.
9312 Are there anyone working on similar tools for firmware upgrading all
9313 servers at a site? Please get in touch and lets share resources.
</p
>
9315 <p
><pre
>
9319 use File::Temp qw(tempdir);
9321 # Install needed RHEL packages if missing
9323 'XML::Simple
' =
> 'perl-XML-Simple
',
9325 for my $module (keys %rhelmodules) {
9326 eval
"use $module;
";
9328 my $pkg = $rhelmodules{$module};
9329 system(
"yum install -y $pkg
");
9330 eval
"use $module;
";
9334 my $errorsto =
'pere@hungry.com
';
9340 sub run_firmware_script {
9341 my ($opts, $script) = @_;
9343 print STDERR
"fail: missing script name\n
";
9346 print STDERR
"Running $script\n\n
";
9348 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
9349 print STDERR
"success: firmware script ran succcessfully\n
";
9351 print STDERR
"fail: firmware script returned error\n
";
9355 sub run_firmware_scripts {
9356 my ($opts, @dirs) = @_;
9357 # Run firmware packages
9358 for my $dir (@dirs) {
9359 print STDERR
"info: Running scripts in $dir\n
";
9360 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
9361 while (my $s = readdir $dh) {
9362 next if $s =~ m/^\.\.?/;
9363 run_firmware_script($opts,
"$dir/$s
");
9371 print STDERR
"info: Downloading $url\n
";
9372 system(
"wget --quiet \
"$url\
"");
9377 my $product = `dmidecode -s system-product-name`;
9380 if ($product =~ m/PowerEdge/) {
9382 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9383 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
9385 my $tmpdir = tempdir(
9389 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
9390 system(
'gunzip Catalog.xml.gz
');
9391 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
9392 # -q is quiet, disabling interactivity and reducing console output
9393 my $fwopts =
"-q
";
9395 for my $url (@paths) {
9396 fetch_dell_fw($url);
9398 run_firmware_scripts($fwopts, $tmpdir);
9400 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9401 print STDERR
"error: Please report to $errorsto.\n
";
9405 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9406 print STDERR
"error: Please report to $errorsto.\n
";
9412 my $url =
"ftp://ftp.us.dell.com/$path
";
9416 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9417 # firmware packages to download from Dell. Only work for Linux
9418 # machines and
11th generation Dell servers.
9419 sub fetch_dell_fw_list {
9420 my $filename = shift;
9422 my $product = `dmidecode -s system-product-name`;
9424 my ($mybrand, $mymodel) = split(/\s+/, $product);
9426 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
9428 my $xml = XMLin($filename);
9430 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
9431 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
9432 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
9434 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
9435 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
9437 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
9439 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
9441 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
9444 for my $component (@{$xml-
>{SoftwareComponent}}) {
9445 my $componenttype = $component-
>{ComponentType}-
>{value};
9447 # Drop application packages, only firmware and BIOS
9448 next if
'APAC
' eq $componenttype;
9450 my $cpath = $component-
>{path};
9451 for my $path (@paths) {
9452 if ($cpath =~ m%/$path$%) {
9453 push(@paths, $cpath);
9461 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
9462 it could work on other platforms with some tweaking. Anyone know a
9463 index like Catalog.xml is available from HP for HP servers? At the
9464 moment I maintain a similar list manually and it is quickly getting
9470 <title>How is booting into runlevel
1 different from single user boots?
</title>
9471 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
9472 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
9473 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
9474 <description><p
>Wouter Verhelst have some
9475 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
9476 comments and opinions
</a
> on my blog post on
9477 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
9478 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
9479 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
9480 default KDE desktop in Debian
</a
>. I only have time to address one
9481 small piece of his comment now, and though it best to address the
9482 misunderstanding he bring forward:
</p
>
9484 <p
><blockquote
>
9485 Currently, a system admin has four options: [...] boot to a
9486 single-user system (by adding
'single
' to the kernel command line;
9487 this runs rcS and rc1 scripts)
9488 </blockquote
></p
>
9490 <p
>This make me believe Wouter believe booting into single user mode
9491 and booting into runlevel
1 is the same. I am not surprised he
9492 believe this, because it would make sense and is a quite sensible
9493 thing to believe. But because the boot in Debian is slightly broken,
9494 runlevel
1 do not work properly and it isn
't the same as single user
9495 mode. I
'll try to explain what is actually happing, but it is a bit
9496 hard to explain.
</p
>
9498 <p
>Single user mode is defined like this in /etc/inittab:
9499 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
9500 executed in single user mode is sulogin. Single user mode is a boot
9501 state
"between
" the runlevels, and when booting into single user mode,
9502 only the scripts in /etc/rcS.d/ are executed before the init process
9503 enters the single user state. When switching to runlevel
1, the state
9504 is in fact not ending in runlevel
1, but it passes through runlevel
1
9505 and end up in the single user mode (see /etc/rc1.d/S03single, which
9506 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
9507 1. It is confusing that the
'S
' (single user) init mode is not the
9508 mode enabled by /etc/rcS.d/ (which is more like the initial boot
9511 <p
>This summary might make it clearer. When booting for the first
9512 time into single user mode, the following commands are executed:
9513 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
9514 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
9515 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
9516 trying to continue after visiting single user mode. Not all services
9517 are started again as they should, causing the machine to end up in an
9518 unpredicatble state. This is why Debian admins recommend rebooting
9519 after visiting single user mode.
</p
>
9521 <p
>A similar problem with runlevel
1 is caused by the amount of
9522 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
9523 to runlevel
1, the services started from /etc/rcS.d/ are not properly
9524 stopped when passing through the scripts in /etc/rc1.d/, and not
9525 started again when switching away from runlevel
1 to the runlevels
9526 2-
5. I believe the problem is best fixed by moving all the scripts
9527 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
9528 functioning single user mode during boot.
</p
>
9530 <p
>I have spent several years investigating the Debian boot system,
9531 and discovered this problem a few years ago. I suspect it originates
9532 from when sysvinit was introduced into Debian, a long time ago.
</p
>
9537 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
9538 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
9539 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
9540 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
9541 <description><p
>In the Debian boot system, several packages include scripts that
9542 are started from /etc/rcS.d/. In fact, there is a bite more of them
9543 than make sense, and this causes a few problems. What kind of
9544 problems, you might ask. There are at least two problems. The first
9545 is that it is not possible to recover a machine after switching to
9546 runlevel
1. One need to actually reboot to get the machine back to
9547 the expected state. The other is that single user boot will sometimes
9548 run into problems because some of the subsystems are activated before
9549 the root login is presented, causing problems when trying to recover a
9550 machine from a problem in that subsystem. A minor additional point is
9551 that moving more scripts out of rcS.d/ and into the other rc#.d/
9552 directories will increase the amount of scripts that can run in
9553 parallel during boot, and thus decrease the boot time.
</p
>
9555 <p
>So, which scripts should start from rcS.d/. In short, only the
9556 scripts that _have_ to execute before the root login prompt is
9557 presented during a single user boot should go there. Everything else
9558 should go into the numeric runlevels. This means things like
9559 lm-sensors, fuse and x11-common should not run from rcS.d, but from
9560 the numeric runlevels. Today in Debian, there are around
115 init.d
9561 scripts that are started from rcS.d/, and most of them should be moved
9562 out. Do your package have one of them? Please help us make single
9563 user and runlevel
1 better by moving it.
</p
>
9565 <p
>Scripts setting up the screen, keyboard, system partitions
9566 etc. should still be started from rcS.d/, but there is for example no
9567 need to have the network enabled before the single user login prompt
9568 is presented.
</p
>
9570 <p
>As always, things are not so easy to fix as they sound. To keep
9571 Debian systems working while scripts migrate and during upgrades, the
9572 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
9573 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
9574 and the next ones can only be moved when their dependencies have been
9575 moved first. This migration must be done sequentially while we ensure
9576 that the package system upgrade packages in the right order to keep
9577 the system state correct. This will require some coordination when it
9578 comes to network related packages, but most of the packages with
9579 scripts that should migrate do not have anything in rcS.d/ depending
9580 on them. Some packages have already been updated, like the sudo
9581 package, while others are still left to do. I wish I had time to work
9582 on this myself, but real live constrains make it unlikely that I will
9583 find time to push this forward.
</p
>
9588 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
9589 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
9590 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
9591 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
9592 <description><p
>While at Debconf11, I have several times during discussions
9593 mentioned the issues I believe should be improved in Debian for its
9594 desktop to be useful for more people. The use case for this is my
9595 parents, which are currently running Kubuntu which solve the
9598 <p
>I suspect these four missing features are not very hard to
9599 implement. After all, they are present in Ubuntu, so if we wanted to
9600 do this in Debian we would have a source.
</p
>
9604 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
9605 are new packages available for upgrades, a icon in the KDE status bar
9606 indicate this, and clicking on it will activate the simple upgrade
9607 tool to handle it. I have no problem guiding both of my parents
9608 through the process over the phone. If a kernel reboot is required,
9609 this too is indicated by the status bars and the upgrade tool. Last
9610 time I checked, nothing with the same features was working in KDE in
9613 <li
><strong
>Simple handling of missing Firefox browser
9614 plugins.
</strong
> When the browser encounter a MIME type it do not
9615 currently have a handler for, it will ask the user if the system
9616 should search for a package that would add support for this MIME type,
9617 and if the user say yes, the APT sources will be searched for packages
9618 advertising the MIME type in their control file (visible in the
9619 Packages file in the APT archive). If one or more packages are found,
9620 it is a simple click of the mouse to add support for the missing mime
9621 type. If the package require the user to accept some non-free
9622 license, this is explained to the user. The entire process make it
9623 more clear to the user why something do not work in the browser, and
9624 make the chances higher for the user to blame the web page authors and
9625 not the browser for any missing features.
</li
>
9627 <li
><strong
>Simple handling of missing multimedia codec/format
9628 handlers.
</strong
> When the media players encounter a format or codec
9629 it is not supporting, a dialog pop up asking the user if the system
9630 should search for a package that would add support for it. This
9631 happen with things like MP3, Windows Media or H
.264. The selection
9632 and installation procedure is very similar to the Firefox browser
9633 plugin handling. This is as far as I know implemented using a
9634 gstreamer hook. The end result is that the user easily get access to
9635 the codecs that are present from the APT archives available, while
9636 explaining more on why a given format is unsupported by Ubuntu.
</li
>
9638 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
9639 displaying a text/plain file in my Debian browser, it will propose to
9640 start emacs to show it. If I remember correctly, when doing the same
9641 in Kunbutu it show the file as a text file in the browser. At least I
9642 know Opera will show text files within the browser. I much prefer the
9643 latter behaviour.
</li
>
9647 <p
>There are other nice features as well, like the simplified suite
9648 upgrader, but given that I am the one mostly doing the dist-upgrade,
9649 it do not matter much.
</p
>
9651 <p
>I really hope we could get these features in place for the next
9652 Debian release. It would require the coordinated effort of several
9653 maintainers, but would make the end user experience a lot better.
</p
>
9658 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
9659 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
9660 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
9661 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
9662 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
9663 site is build on Debian/Squeeze, and this platform was chosen because
9664 I am most familiar with Debian (being a Debian Developer for around
10
9665 years) because it is the latest stable Debian release which should get
9666 security support for a few years.
</p
>
9668 <p
>The web service is written in Perl, and depend on some perl modules
9669 that are missing in Debian at the moment. It would be great if these
9670 modules were added to the Debian archive, allowing anyone to set up
9671 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
9672 in their own country using only Debian packages. The list of modules
9673 missing in Debian/Squeeze isn
't very long, and I hope the perl group
9674 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
9675 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
9676 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
9677 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
9678 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
9679 easier in the future.
</p
>
9681 <p
>Thanks to the great tools in Debian, getting the missing modules
9682 installed on my server was a simple call to
'cpan2deb Module::Name
'
9683 and
'dpkg -i
' to install the resulting package. But this leave me
9684 with the responsibility of tracking security problems, which I really
9685 do not have time for.
</p
>
9690 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
9691 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
9692 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
9693 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
9694 <description><p
>Here is a small update for my English readers. Most of my blog
9695 posts have been in Norwegian the last few weeks, so here is a short
9696 update in English.
</p
>
9698 <p
>The kids still keep me too busy to get much free software work
9699 done, but I did manage to organise a project to get a Norwegian port
9700 of the British service
9701 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
9702 and it has been running for a month now. The entire project has been
9703 organised by me and two others. Around Christmas we gathered sponsors
9704 to fund the development work. In January I drafted a contract with
9705 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
9706 and in February the development took place. Most of it involved
9707 converting the source to use GPS coordinates instead of British
9708 easting/northing, and the resulting code should be a lot easier to get
9709 running in any country by now. The Norwegian
9710 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
9711 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
9712 source and the source for administrative borders in Norway, and
9713 support for this had to be added/fixed.
</p
>
9715 <p
>The Norwegian version went live March
3th, and we spent the weekend
9716 polishing the system before we announced it March
7th. The system is
9717 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
9718 problem reports in a few weeks. Soon we hope to announce the Android
9719 and iPhone versions making it even easier to report problems with the
9720 public infrastructure.
</p
>
9722 <p
>Perhaps something to consider for those of you in countries without
9723 such service?
</p
>
9728 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
9729 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
9730 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
9731 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
9732 <description><p
>The last few days I have looked at ways to track open security
9733 issues here at my work with the University of Oslo. My idea is that
9734 it should be possible to use the information about security issues
9735 available on the Internet, and check our locally
9736 maintained/distributed software against this information. It should
9737 allow us to verify that no known security issues are forgotten. The
9738 CVE database listing vulnerabilities seem like a great central point,
9739 and by using the package lists from Debian mapped to CVEs provided by
9740 the testing security team, I believed it should be possible to figure
9741 out which security holes were present in our free software
9742 collection.
</p
>
9744 <p
>After reading up on the topic, it became obvious that the first
9745 building block is to be able to name software packages in a unique and
9746 consistent way across data sources. I considered several ways to do
9747 this, for example coming up with my own naming scheme like using URLs
9748 to project home pages or URLs to the Freshmeat entries, or using some
9749 existing naming scheme. And it seem like I am not the first one to
9750 come across this problem, as MITRE already proposed and implemented a
9751 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
9752 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
9753 software, hardware and other platform components. The CPE ids are
9754 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
9755 Vulnerability Database
</a
>, allowing me to look up know security
9756 issues for any CPE name. With this in place, all I need to do is to
9757 locate the CPE id for the software packages we use at the university.
9758 This is fairly trivial (I google for
'cve cpe $package
' and check the
9759 NVD entry if a CVE for the package exist).
</p
>
9761 <p
>To give you an example. The GNU gzip source package have the CPE
9762 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
9763 check out, one could look up
9764 <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
9765 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
9766 The most recent one is
9767 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
9768 and at the bottom of the NVD page for this vulnerability the complete
9769 list of affected versions is provided.
</p
>
9771 <p
>The NVD database of CVEs is also available as a XML dump, allowing
9772 for offline processing of issues. Using this dump, I
've written a
9773 small script taking a list of CPEs as input and list all CVEs
9774 affecting the packages represented by these CPEs. One give it CPEs
9775 with version numbers as specified above and get a list of open
9776 security issues out.
</p
>
9778 <p
>Of course for this approach to be useful, the quality of the NVD
9779 information need to be high. For that to happen, I believe as many as
9780 possible need to use and contribute to the NVD database. I notice
9782 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
9783 map from CVE to CPE
</a
>, indicating that they are using the CPE
9784 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
9786 <p
>To get an idea about the quality for free software, I spent some
9787 time making it possible to compare the CVE database from Debian with
9788 the CVE database in NVD. The result look fairly good, but there are
9789 some inconsistencies in NVD (same software package having several
9790 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
9791 Debian believe are affected by a CVE). Hope to find time to improve
9792 the quality of NVD, but that require being able to get in touch with
9793 someone maintaining it. So far my three emails with questions and
9794 corrections have not seen any reply, but I hope contact can be
9795 established soon.
</p
>
9797 <p
>An interesting application for CPEs is cross platform package
9798 mapping. It would be useful to know which packages in for example
9799 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
9800 this would be trivial if all linux distributions provided CPE entries
9801 for their packages.
</p
>
9806 <title>Which module is loaded for a given PCI and USB device?
</title>
9807 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
9808 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
9809 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
9810 <description><p
>In the
9811 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
9812 package in Debian, there is a script to report useful information
9813 about the running hardware for use when people report missing
9814 information. One part of this script that I find very useful when
9815 debugging hardware problems, is the part mapping loaded kernel module
9816 to the PCI device it claims. It allow me to quickly see if the kernel
9817 module I expect is driving the hardware I am struggling with. To see
9818 the output, make sure discover-data is installed and run
9819 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
9820 one of my machines like this:
</p
>
9824 10de:
03eb i2c_nforce2
9827 10de:
03f0 snd_hda_intel
9836 <p
>The code in question look like this, slightly modified for
9837 readability and to drop the output to file descriptor
3:
</p
>
9840 if [ -d /sys/bus/pci/devices/ ] ; then
9841 echo loaded pci modules:
9843 cd /sys/bus/pci/devices/
9844 for address in * ; do
9845 if [ -d
"$address/driver/module
" ] ; then
9846 module=`cd $address/driver/module ; pwd -P | xargs basename`
9847 if grep -q
"^$module
" /proc/modules ; then
9848 address=$(echo $address |sed s/
0000://)
9849 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
9850 echo
"$id $module
"
9859 <p
>Similar code could be used to extract USB device module
9863 if [ -d /sys/bus/usb/devices/ ] ; then
9864 echo loaded usb modules:
9866 cd /sys/bus/usb/devices/
9867 for address in * ; do
9868 if [ -d
"$address/driver/module
" ] ; then
9869 module=`cd $address/driver/module ; pwd -P | xargs basename`
9870 if grep -q
"^$module
" /proc/modules ; then
9871 address=$(echo $address |sed s/
0000://)
9872 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
9873 if [
"$id
" ] ; then
9874 echo
"$id $module
"
9884 <p
>This might perhaps be something to include in other tools as
9890 <title>How to test if a laptop is working with Linux
</title>
9891 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
9892 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
9893 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
9894 <description><p
>The last few days I have spent at work here at the
<a
9895 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
9896 batch of computers will work with Linux. Every year for the last few
9897 years the university have organised shared bid of a few thousand
9898 computers, and this year HP won the bid. Two different desktops and
9899 five different laptops are on the list this year. We in the UNIX
9900 group want to know which one of these computers work well with RHEL
9901 and Ubuntu, the two Linux distributions we currently handle at the
9902 university.
</p
>
9904 <p
>My test method is simple, and I share it here to get feedback and
9905 perhaps inspire others to test hardware as well. To test, I PXE
9906 install the OS version of choice, and log in as my normal user and run
9907 a few applications and plug in selected pieces of hardware. When
9908 something fail, I make a note about this in the test matrix and move
9909 on. If I have some spare time I try to report the bug to the OS
9910 vendor, but as I only have the machines for a short time, I rarely
9911 have the time to do this for all the problems I find.
</p
>
9913 <p
>Anyway, to get to the point of this post. Here is the simple tests
9914 I perform on a new model.
</p
>
9918 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
9919 and Ubuntu Maverik at the moment. If I feel like it, I also test with
9920 RHEL5 and Debian Edu/Squeeze.
</li
>
9922 <li
>Is X.org working? If the graphical login screen show up after
9923 installation, X.org is working.
</li
>
9925 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
9926 package mesa-utils on Ubuntu) and writing down the frames per second
9927 reported by the program.
</li
>
9929 <li
>Is sound working? With Gnome and KDE, a sound is played when
9930 logging in, and if I can hear this the test is successful. If there
9931 are several audio exits on the machine, I try them all and check if
9932 the Gnome/KDE audio mixer can control where to send the sound. I
9933 normally test this by playing
9934 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
9935 video
</a
> in Firefox/Iceweasel.
</li
>
9937 <li
>Is the USB subsystem working? I test this by plugging in a USB
9938 memory stick and see if Gnome/KDE notices this.
</li
>
9940 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
9941 I have lying around, and see if Gnome/KDE notices this.
</li
>
9943 <li
>Is any built in camera working? Test using cheese, and see if a
9944 picture from the v4l device show up.
</li
>
9946 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
9947 any bluetooth devices are discovered. In my office, I normally see a
9950 <li
>For laptops, is the SD or Compaq Flash reader working. I have
9951 memory modules lying around, and stick them in and see if Gnome/KDE
9952 notice this.
</li
>
9954 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
9955 special button work, and if the laptop continue to work after
9958 <li
>For laptops, is the extra buttons working, like audio level,
9959 adjusting background light, switching on/off external video output,
9960 switching on/off wifi, bluetooth, etc? The set of buttons differ from
9961 laptop to laptop, so I just write down which are working and which are
9964 <li
>Some laptops have smart card readers, finger print readers,
9965 acceleration sensors etc. I rarely test these, as I do not know how
9966 to quickly test if they are working or not, so I only document their
9967 existence.
</li
>
9971 <p
>By now I suspect you are really curious what the test results are
9972 for the HP machines I am testing. I
'm not done yet, so I will report
9973 the test results later. For now I can report that HP
8100 Elite work
9974 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
9975 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
9976 can see, I have most machines left to test. One interesting
9977 observation is that Ubuntu Lucid has almost twice the frame rate than
9978 RHEL6 with glxgears. No idea why.
</p
>
9983 <title>Some thoughts on BitCoins
</title>
9984 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
9985 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
9986 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
9987 <description><p
>As I continue to explore
9988 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
9989 what properties the system have, and how it will be affected by laws
9990 and regulations here in Norway. Here are some random notes.
</p
>
9992 <p
>One interesting thing to note is that since the transactions are
9993 verified using a peer to peer network, all details about a transaction
9994 is known to everyone. This means that if a BitCoin address has been
9995 published like I did with mine in my initial post about BitCoin, it is
9996 possible for everyone to see how many BitCoins have been transfered to
9997 that address. There is even a web service to look at the details for
9998 all transactions. There I can see that my address
9999 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
10000 have received
16.06 Bitcoin, the
10001 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
10002 address of Simon Phipps have received
181.97 BitCoin and the address
10003 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
10004 of EFF have received
2447.38 BitCoins so far. Thank you to each and
10005 every one of you that donated bitcoins to support my activity. The
10006 fact that anyone can see how much money was transfered to a given
10007 address make it more obvious why the BitCoin community recommend to
10008 generate and hand out a new address for each transaction. I
'm told
10009 there is no way to track which addresses belong to a given person or
10010 organisation without the person or organisation revealing it
10011 themselves, as Simon, EFF and I have done.
</p
>
10013 <p
>In Norway, and in most other countries, there are laws and
10014 regulations limiting how much money one can transfer across the border
10015 without declaring it. There are money laundering, tax and accounting
10016 laws and regulations I would expect to apply to the use of BitCoin.
10017 If the Skolelinux foundation
10018 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
10019 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
10020 normal bank transfers like EFF is doing, how should this be accounted?
10021 Given that it is impossible to know if money can cross the border or
10022 not, should everything or nothing be declared? What exchange rate
10023 should be used when calculating taxes? Would receivers have to pay
10024 income tax if the foundation were to pay Skolelinux contributors in
10025 BitCoin? I have no idea, but it would be interesting to know.
</p
>
10027 <p
>For a currency to be useful and successful, it must be trusted and
10028 accepted by a lot of users. It must be possible to get easy access to
10029 the currency (as a wage or using currency exchanges), and it must be
10030 easy to spend it. At the moment BitCoin seem fairly easy to get
10031 access to, but there are very few places to spend it. I am not really
10032 a regular user of any of the vendor types currently accepting BitCoin,
10033 so I wonder when my kind of shop would start accepting BitCoins. I
10034 would like to buy electronics, travels and subway tickets, not herbs
10035 and books. :) The currency is young, and this will improve over time
10036 if it become popular, but I suspect regular banks will start to lobby
10037 to get BitCoin declared illegal if it become popular. I
'm sure they
10038 will claim it is helping fund terrorism and money laundering (which
10039 probably would be true, as is any currency in existence), but I
10040 believe the problems should be solved elsewhere and not by blaming
10041 currencies.
</p
>
10043 <p
>The process of creating new BitCoins is called mining, and it is
10044 CPU intensive process that depend on a bit of luck as well (as one is
10045 competing against all the other miners currently spending CPU cycles
10046 to see which one get the next lump of cash). The
"winner
" get
50
10047 BitCoin when this happen. Yesterday I came across the obvious way to
10048 join forces to increase ones changes of getting at least some coins,
10049 by coordinating the work on mining BitCoins across several machines
10050 and people, and sharing the result if one is lucky and get the
50
10051 BitCoins. Check out
10052 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
10053 if this sounds interesting. I have not had time to try to set up a
10054 machine to participate there yet, but have seen that running on ones
10055 own for a few days have not yield any BitCoins througth mining
10058 <p
>Update
2010-
12-
15: Found an
<a
10059 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
10060 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
10061 it was interesting to read. The arguments presented seem to be
10062 equally valid for gold, which was used as a currency for many years.
</p
>
10067 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
10068 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
10069 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
10070 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
10071 <description><p
>With this weeks lawless
10072 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
10073 attacks
</a
> on Wikileak and
10074 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
10075 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
10076 not be trusted to handle money transactions.
10078 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
10079 Phipps on bitcoin
</a
> reminded me about a project that a friend of
10080 mine mentioned earlier. I decided to follow Simon
's example, and get
10081 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
10082 some help from my friend to get it all running, and he even handed me
10083 some bitcoins to get started. I even donated a few bitcoins to Simon
10084 for helping me remember BitCoin.
</p
>
10086 <p
>So, what is bitcoins, you probably wonder? It is a digital
10087 crypto-currency, decentralised and handled using peer-to-peer
10088 networks. It allows anonymous transactions and prohibits central
10089 control over the transactions, making it impossible for governments
10090 and companies alike to block donations and other transactions. The
10091 source is free software, and while the key dependency wxWidgets
2.9
10092 for the graphical user interface is missing in Debian, the command
10093 line client builds just fine. Hopefully Jonas
10094 <a href=
"http://bugs.debian.org/
578157">will get the package into
10095 Debian
</a
> soon.
</p
>
10097 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
10098 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
10099 bitcoins
</a
> when selling services and goods, and there are even
10100 currency
"stock
" markets where the exchange rate is decided. There
10101 are not many users so far, but the concept seems promising. If you
10102 want to get started and lack a friend with any bitcoins to spare,
10104 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
10105 bitcoin at the time of writing). Use
10106 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
10107 on the current exchange rates.
</p
>
10109 <p
>As an experiment, I have decided to set up bitcoind on one of my
10110 machines. If you want to support my activity, please send Bitcoin
10111 donations to the address
10112 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
10117 <title>Why isn
't Debian Edu using VLC?
</title>
10118 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
10119 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
10120 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
10121 <description><p
>In the latest issue of Linux Journal, the readers choices were
10122 presented, and the winner among the multimedia player were VLC.
10123 Personally, I like VLC, and it is my player of choice when I first try
10124 to play a video file or stream. Only if VLC fail will I drag out
10125 gmplayer to see if it can do better. The reason is mostly the failure
10126 model and trust. When VLC fail, it normally pop up a error message
10127 reporting the problem. When mplayer fail, it normally segfault or
10128 just hangs. The latter failure mode drain my trust in the program.
<p
>
10130 <p
>But even if VLC is my player of choice, we have choosen to use
10131 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
10132 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
10133 plugin to play web videos seamlessly, and the VLC browser plugin is
10134 not very good. For example, it lack in-line control buttons, so there
10135 is no way for the user to pause the video. Also, when I
10136 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
10137 tested the browser plugins
</a
> available in Debian, the VLC plugin
10138 failed on several video pages where mplayer based plugins worked. If
10139 the browser plugin for VLC was as good as the gecko-mediaplayer
10140 package (which uses mplayer), we would switch.
</P
>
10142 <p
>While VLC is a good player, its user interface is slightly
10143 annoying. The most annoying feature is its inconsistent use of
10144 keyboard shortcuts. When the player is in full screen mode, its
10145 shortcuts are different from when it is playing the video in a window.
10146 For example, space only work as pause when in full screen mode. I
10147 wish it had consisten shortcuts and that space also would work when in
10148 window mode. Another nice shortcut in gmplayer is [enter] to restart
10149 the current video. It is very nice when playing short videos from the
10150 web and want to restart it when new people arrive to have a look at
10151 what is going on.
</p
>
10156 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
10157 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
10158 <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>
10159 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
10160 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
10161 upgrade testing of the
10162 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
10163 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
10164 This seem like a very good idea, so I adjusted by test scripts and
10165 can now present the updated result from today:
</p
>
10167 <p
>This is for Gnome:
</p
>
10169 <p
>Installed using apt-get, missing with aptitude
</p
>
10171 <blockquote
><p
>
10176 browser-plugin-gnash
10183 freedesktop-sound-theme
10185 gconf-defaults-service
10198 gnome-codec-install
10200 gnome-desktop-environment
10204 gnome-session-canberra
10206 gnome-themes-extras
10209 gstreamer0.10-fluendo-mp3
10210 gstreamer0.10-tools
10212 gtk2-engines-pixbuf
10213 gtk2-engines-smooth
10215 libapache2-mod-dnssd
10218 libaprutil1-dbd-sqlite3
10221 libboost-date-time1.42
.0
10222 libboost-python1.42
.0
10223 libboost-thread1.42
.0
10225 libchamplain-gtk-
0.4-
0
10227 libclutter-gtk-
0.10-
0
10234 libfreerdp-plugins-standard
10247 libgnome-vfs2.0-cil
10249 libgnomepanel2.24-cil
10254 libgtksourceview2.0-common
10255 libmono-addins-gui0.2-cil
10256 libmono-addins0.2-cil
10257 libmono-cairo2.0-cil
10258 libmono-corlib2.0-cil
10259 libmono-i18n-west2.0-cil
10260 libmono-posix2.0-cil
10261 libmono-security2.0-cil
10262 libmono-sharpzip2.84-cil
10263 libmono-system2.0-cil
10266 libndesk-dbus-glib1.0-cil
10267 libndesk-dbus1.0-cil
10277 libtelepathy-farsight0
10286 nautilus-sendto-empathy
10290 python-aptdaemon-gtk
10292 python-beautifulsoup
10307 python-gtksourceview2
10318 python-pkg-resources
10325 python-twisted-conch
10326 python-twisted-core
10331 python-zope.interface
10333 remmina-plugin-data
10336 rhythmbox-plugin-cdrecorder
10343 system-config-printer-udev
10345 telepathy-mission-control-
5
10352 transmission-common
10356 </p
></blockquote
>
10358 <p
>Installed using apt-get, removed with aptitude
</p
>
10360 <blockquote
><p
>
10364 epiphany-extensions
10366 fast-user-switch-applet
10385 libgtksourceview2.0-
0
10387 libsdl1.2debian-alsa
10393 system-config-printer
10398 </p
></blockquote
>
10400 <p
>Installed using aptitude, missing with apt-get
</p
>
10402 <blockquote
><p
>
10403 gstreamer0.10-gnomevfs
10404 </p
></blockquote
>
10406 <p
>Installed using aptitude, removed with apt-get
</p
>
10408 <blockquote
><p
>
10410 </p
></blockquote
>
10412 <p
>This is for KDE:
</p
>
10414 <p
>Installed using apt-get, missing with aptitude
</p
>
10416 <blockquote
><p
>
10418 </p
></blockquote
>
10420 <p
>Installed using apt-get, removed with aptitude
</p
>
10422 <blockquote
><p
>
10424 network-manager-kde
10425 </p
></blockquote
>
10427 <p
>Installed using aptitude, missing with apt-get
</p
>
10429 <blockquote
><p
>
10443 kdeartwork-emoticons
10445 kdeartwork-theme-icon
10449 kdebase-workspace-bin
10450 kdebase-workspace-data
10462 konqueror-nsplugins
10464 kscreensaver-xsavers
10479 plasma-dataengines-workspace
10481 plasma-desktopthemes-artwork
10482 plasma-runners-addons
10483 plasma-scriptengine-googlegadgets
10484 plasma-scriptengine-python
10485 plasma-scriptengine-qedje
10486 plasma-scriptengine-ruby
10487 plasma-scriptengine-webkit
10488 plasma-scriptengines
10489 plasma-wallpapers-addons
10490 plasma-widget-folderview
10491 plasma-widget-networkmanagement
10494 update-notifier-kde
10495 xscreensaver-data-extra
10497 xscreensaver-gl-extra
10498 xscreensaver-screensaver-bsod
10499 </p
></blockquote
>
10501 <p
>Installed using aptitude, removed with apt-get
</p
>
10503 <blockquote
><p
>
10505 google-gadgets-common
10523 libggadget-qt-
1.0-
0b
10528 libkonqsidebarplugin4a
10532 libkunitconversion4
10537 libplasma-geolocation-interface4
10539 libplasmagenericshell4
10553 libsmokeknewstuff2-
3
10554 libsmokeknewstuff3-
3
10556 libsmokektexteditor3
10564 libsmokeqtnetwork4-
3
10565 libsmokeqtopengl4-
3
10566 libsmokeqtscript4-
3
10570 libsmokeqtuitools4-
3
10571 libsmokeqtwebkit4-
3
10582 plasma-dataengines-addons
10583 plasma-scriptengine-superkaramba
10584 plasma-widget-lancelot
10585 plasma-widgets-addons
10586 plasma-widgets-workspace
10590 update-notifier-common
10591 </p
></blockquote
>
10593 <p
>Running apt-get autoremove made the results using apt-get and
10594 aptitude a bit more similar, but there are still quite a lott of
10595 differences. I have no idea what packages should be installed after
10596 the upgrade, but hope those that do can have a look.
</p
>
10601 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
10602 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
10603 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
10604 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
10605 <description><p
>Most of the computers in use by the
10606 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
10607 are virtual machines. And they have been Xen machines running on a
10608 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
10609 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
10610 bit harder that it could have been, because we set up the Xen virtual
10611 machines to get the virtual partitions from LVM, which as far as I
10612 know is not supported by KVM. So to migrate, we had to convert
10613 several LVM logical volumes to partitions on a virtual disk file.
</p
>
10616 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
10617 nice recipe
</a
> to do this, and wrote the following script to do the
10618 migration. It uses qemu-img from the qemu package to make the disk
10619 image, parted to partition it, losetup and kpartx to present the disk
10620 image partions as devices, and dd to copy the data. I NFS mounted the
10621 new servers storage area on the old server to do the migration.
</p
>
10627 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
10632 if [ -z
"$
1" ] ; then
10633 echo
"Usage: $
0 &lt;hostname
&gt;
"
10636 host=
"$
1"
10639 if [ ! -e /dev/vg_data/$host-disk ] ; then
10640 echo
"error: unable to find LVM volume for $host
"
10644 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
10645 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
10646 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
10647 totalsize=$(( ( $disksize + $swapsize ) ))
10650 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
10651 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
10653 parted $img mklabel msdos
10654 parted $img mkpart primary linux-swap
0 $disksize
10655 parted $img mkpart primary ext2 $disksize $totalsize
10656 parted $img set
1 boot on
10659 losetup /dev/loop0 $img
10660 kpartx -a /dev/loop0
10662 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
10663 fsck.ext3 -f /dev/mapper/loop0p1 || true
10664 mkswap /dev/mapper/loop0p2
10666 kpartx -d /dev/loop0
10667 losetup -d /dev/loop0
10670 <p
>The script is perhaps so simple that it is not copyrightable, but
10671 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
10673 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
10674 the new disk image attached, installed grub-pc and linux-image-
686 and
10675 set up grub to boot from the disk image. After this, the KVM machines
10676 seem to work just fine.
</p
>
10681 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
10682 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
10683 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
10684 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
10685 <description><p
>I
'm still running upgrade testing of the
10686 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
10687 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
10688 status. Here is a short update based on a test I ran
20101118.
</p
>
10690 <p
>I still do not know what a correct migration should look like, so I
10691 report any differences between apt and aptitude and hope someone else
10692 can see if anything should be changed.
</p
>
10694 <p
>This is for Gnome:
</p
>
10696 <p
>Installed using apt-get, missing with aptitude
</p
>
10698 <blockquote
><p
>
10699 apache2.2-bin aptdaemon at-spi baobab binfmt-support
10700 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
10701 dmz-cursor-theme empathy empathy-common finger
10702 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
10703 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
10704 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
10705 gnome-cards-data gnome-codec-install gnome-core
10706 gnome-desktop-environment gnome-disk-utility gnome-screenshot
10707 gnome-search-tool gnome-session-canberra gnome-spell
10708 gnome-system-log gnome-themes-extras gnome-themes-more
10709 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
10710 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
10711 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
10712 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
10713 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
10714 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
10715 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
10716 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
10717 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
10718 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
10719 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
10720 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
10721 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
10722 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
10723 libgtk2.0-cil libgtkglext1 libgtksourceview-common
10724 libgtksourceview2.0-common libmono-addins-gui0.2-cil
10725 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
10726 libmono-i18n-west2.0-cil libmono-posix2.0-cil
10727 libmono-security2.0-cil libmono-sharpzip2.84-cil
10728 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
10729 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
10730 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
10731 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
10732 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
10733 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
10734 libxalan2-java libxerces2-java media-player-info mesa-utils
10735 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
10736 nautilus-sendto-empathy openoffice.org-writer2latex
10737 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
10738 python-aptdaemon python-aptdaemon-gtk python-axiom
10739 python-beautifulsoup python-bugbuddy python-clientform
10740 python-coherence python-configobj python-crypto python-cupshelpers
10741 python-cupsutils python-eggtrayicon python-elementtree
10742 python-epsilon python-evolution python-feedparser python-gdata
10743 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
10744 python-gtksourceview2 python-httplib2 python-louie python-mako
10745 python-markupsafe python-mechanize python-nevow python-notify
10746 python-opengl python-openssl python-pam python-pkg-resources
10747 python-pyasn1 python-pysqlite2 python-rdflib python-serial
10748 python-tagpy python-twisted-bin python-twisted-conch
10749 python-twisted-core python-twisted-web python-utidylib python-webkit
10750 python-xdg python-zope.interface remmina remmina-plugin-data
10751 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
10752 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
10753 software-center svgalibg1 system-config-printer-udev
10754 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
10755 totem totem-coherence totem-mozilla totem-plugins
10756 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
10758 </p
></blockquote
>
10760 Installed using apt-get, removed with aptitude
10762 <blockquote
><p
>
10763 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
10764 epiphany-extensions epiphany-gecko evolution-exchange
10765 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
10766 gedit-common gnome-app-install gnome-games gnome-games-data
10767 gnome-nettool gnome-system-tools gnome-themes gnome-utils
10768 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
10769 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
10770 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
10771 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
10772 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
10773 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
10774 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
10775 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
10776 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
10777 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
10778 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
10779 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
10780 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
10781 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
10782 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
10783 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
10784 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
10785 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
10786 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
10787 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
10788 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
10789 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
10790 sound-juicer swfdec-gnome system-config-printer totem-common
10791 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
10792 </p
></blockquote
>
10794 <p
>Installed using aptitude, missing with apt-get
</p
>
10796 <blockquote
><p
>
10797 gstreamer0.10-gnomevfs
10798 </p
></blockquote
>
10800 <p
>Installed using aptitude, removed with apt-get
</p
>
10802 <blockquote
><p
>
10804 </p
></blockquote
>
10806 <p
>This is for KDE:
</p
>
10808 <p
>Installed using apt-get, missing with aptitude
</p
>
10810 <blockquote
><p
>
10811 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
10812 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
10813 ghostscript-x git gnome-audio gnugo granatier gs-common
10814 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
10815 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
10816 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
10817 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10818 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
10819 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
10820 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10821 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
10822 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
10823 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
10824 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
10825 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
10826 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
10827 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
10828 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
10829 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
10830 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
10831 libkrossui4 libmailtools-perl libmime-tools-perl
10832 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
10833 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
10834 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
10835 lirc luatex marble networkstatus noatun-plugins
10836 openoffice.org-writer2latex palapeli palapeli-data parley
10837 parley-data poster psutils pulseaudio pulseaudio-esound-compat
10838 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
10839 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
10840 ttf-sazanami-gothic
10841 </p
></blockquote
>
10843 <p
>Installed using apt-get, removed with aptitude
</p
>
10845 <blockquote
><p
>
10846 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
10847 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
10848 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
10849 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
10850 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
10851 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
10852 kitchensync kiten kjumpingcube klatin klettres klickety klines
10853 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
10854 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
10855 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
10856 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
10857 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
10858 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
10859 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
10860 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
10861 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10862 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
10863 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
10864 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10865 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
10866 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
10867 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
10868 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
10869 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10870 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
10871 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
10872 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
10873 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
10874 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
10875 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
10876 mpeglib network-manager-kde noatun pmount tex-common texlive-base
10877 texlive-common texlive-doc-base texlive-fonts-recommended tidy
10878 ttf-dustin ttf-kochi-gothic ttf-sjfonts
10879 </p
></blockquote
>
10881 <p
>Installed using aptitude, missing with apt-get
</p
>
10883 <blockquote
><p
>
10884 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
10885 kdeartwork kdebase kdebase-apps kdebase-workspace
10886 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
10887 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
10888 netpbm plasma-widget-folderview plasma-widget-networkmanagement
10889 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
10890 xscreensaver-screensaver-bsod
10891 </p
></blockquote
>
10893 <p
>Installed using aptitude, removed with apt-get
</p
>
10895 <blockquote
><p
>
10896 kdebase-bin konq-plugins konqueror
10897 </p
></blockquote
>
10902 <title>Gnash buildbot slave and Debian kfreebsd
</title>
10903 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
10904 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
10905 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
10906 <description><p
>Answering
10907 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
10908 call from the Gnash project
</a
> for
10909 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
10910 current source, I have set up a virtual KVM machine on the Debian
10911 Edu/Skolelinux virtualization host to test the git source on
10912 Debian/Squeeze. I hope this can help the developers in getting new
10913 releases out more often.
</p
>
10915 <p
>As the developers want less main-stream build platforms tested to,
10916 I have considered setting up a
<a
10917 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
10918 machine as well. I have also considered using the kfreebsd
10919 architecture in Debian as a file server in NUUG to get access to the
5
10920 TB zfs volume we currently use to store DV video. Because of this, I
10921 finally got around to do a test installation of Debian/Squeeze with
10922 kfreebsd. Installation went fairly smooth, thought I noticed some
10923 visual glitches in the cdebconf dialogs (black cursor left on the
10924 screen at random locations). Have not gotten very far with the
10925 testing. Noticed cfdisk did not work, but fdisk did so it was not a
10926 fatal problem. Have to spend some more time on it to see if it is
10927 useful as a file server for NUUG. Will try to find time to set up a
10928 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
10933 <title>Debian in
3D
</title>
10934 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
10935 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
10936 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
10937 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
10939 <p
>3D printing is just great. I just came across this Debian logo in
10941 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
10942 thingiverse blog
</a
>.
</p
>
10947 <title>Software updates
2010-
10-
24</title>
10948 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
10949 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
10950 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
10951 <description><p
>Some updates.
</p
>
10953 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
10954 raise money for the project is going well. The lower limit of
10
10955 signers was reached in
24 hours, and so far
13 people have signed it.
10956 More signers and more funding is most welcome, and I am really curious
10957 how far we can get before the time limit of December
24 is reached.
10960 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
10961 about what appear to be a great code coverage tool capable of
10962 generating code coverage stats without any changes to the source code.
10964 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
10965 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
10966 It is missing in Debian, but the git source built just fine in Squeeze
10967 after I installed libelf-dev, libdwarf-dev, pkg-config and
10968 libglib2.0-dev. Failed to build in Lenny, but suspect that is
10969 solvable. I hope kcov make it into Debian soon.
</p
>
10971 <p
>Finally found time to wrap up the release notes for
<a
10972 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
10973 new alpha release of Debian Edu
</a
>, and just published the second
10974 alpha test release of the Squeeze based Debian Edu /
10975 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
10976 release. Give it a try if you need a complete linux solution for your
10977 school, including central infrastructure server, workstations, thin
10978 client servers and diskless workstations. A nice touch added
10979 yesterday is RDP support on the thin client servers, for windows
10980 clients to get a Linux desktop on request.
</p
>
10985 <title>Some notes on Flash in Debian and Debian Edu
</title>
10986 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
10987 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
10988 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
10989 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
10990 popularity-contest numbers
</a
>, the adobe-flashplugin package the
10991 second most popular used package that is missing in Debian. The sixth
10992 most popular is flashplayer-mozilla. This is a clear indication that
10993 working flash is important for Debian users. Around
10 percent of the
10994 users submitting data to popcon.debian.org have this package
10995 installed.
</p
>
10997 <p
>In the report written by Lars Risan in August
2008
10998 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
10999 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
11000 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
11001 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
11002 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
11003 web sites require Flash to work, and lacking working Flash support in
11004 the web browser and the problems with installing it was perceived as a
11005 good reason to stay with Windows.
</p
>
11007 <p
>I once saw a funny and sad comment in a web forum, where Linux was
11008 said to be the retarded cousin that did not really understand
11009 everything you told him but could work fairly well. This was a
11010 comment regarding the problems Linux have with proprietary formats and
11011 non-standard web pages, and is sad because it exposes a fairly common
11012 understanding of whose fault it is if web pages that only work in for
11013 example Internet Explorer
6 fail to work on Firefox, and funny because
11014 it explain very well how annoying it is for users when Linux
11015 distributions do not work with the documents they receive or the web
11016 pages they want to visit.
</p
>
11018 <p
>This is part of the reason why I believe it is important for Debian
11019 and Debian Edu to have a well working Flash implementation in the
11020 distribution, to get at least popular sites as Youtube and Google
11021 Video to working out of the box. For Squeeze, Debian have the chance
11022 to include the latest version of Gnash that will make this happen, as
11023 the new release
0.8.8 was published a few weeks ago and is resting in
11024 unstable. The new version work with more sites that version
0.8.7.
11025 The Gnash maintainers have asked for a freeze exception, but the
11026 release team have not had time to reply to it yet. I hope they agree
11027 with me that Flash is important for the Debian desktop users, and thus
11028 accept the new package into Squeeze.
</p
>
11033 <title>Circular package dependencies harms apt recovery
</title>
11034 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
11035 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
11036 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
11037 <description><p
>I discovered this while doing
11038 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
11039 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
11040 in Debian still got circular dependencies, and it is often claimed
11041 that apt and aptitude should be able to handle this just fine, but
11042 some times these dependency loops causes apt to fail.
</p
>
11044 <p
>An example is from todays
11045 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
11046 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
11047 causes perl-modules to fail to upgrade. The cause is simple. If a
11048 package fail to unpack, then only part of packages with the circular
11049 dependency might end up being unpacked when unpacking aborts, and the
11050 ones already unpacked will fail to configure in the recovery phase
11051 because its dependencies are unavailable.
</p
>
11053 <p
>In this log, the problem manifest itself with this error:
</p
>
11055 <blockquote
><pre
>
11056 dpkg: dependency problems prevent configuration of perl-modules:
11057 perl-modules depends on perl (
>=
5.10.1-
1); however:
11058 Version of perl on system is
5.10.0-
19lenny
2.
11059 dpkg: error processing perl-modules (--configure):
11060 dependency problems - leaving unconfigured
11061 </pre
></blockquote
>
11063 <p
>The perl/perl-modules circular dependency is already
11064 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
11065 hopefully be solved as soon as possible, but it is not the only one,
11066 and each one of these loops in the dependency tree can cause similar
11067 failures. Of course, they only occur when there are bugs in other
11068 packages causing the unpacking to fail, but it is rather nasty when
11069 the failure of one package causes the problem to become worse because
11070 of dependency loops.
</p
>
11073 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
11074 tireless effort by Bill Allombert
</a
>, the number of circular
11076 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
11077 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
11079 <p
>Todays testing also exposed a bug in
11080 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
11081 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
11082 apt-get and aptitude, the latter possibly caused by some circular
11083 dependency. Reported both to BTS to try to get someone to look at
11089 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
11090 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
11091 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
11092 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
11093 <description><p
>This is a
11094 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
11096 <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
11098 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
11099 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
11101 <p
>As a step to try to see if it possible to merge the DNS and DHCP
11102 LDAP objects, I have had a look at how the packages pdns-backend-ldap
11103 and dhcp3-server-ldap in Debian use the LDAP server. The two
11104 implementations are quite different in how they use LDAP.
</p
>
11106 To get this information, I started slapd with debugging enabled and
11107 dumped the debug output to a file to get the LDAP searches performed
11108 on a Debian Edu main-server. Here is a summary.
11110 <p
><strong
>powerdns
</strong
></p
>
11112 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
11113 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
11116 <p
>PowerDNS have two modes of operation using LDAP as its backend.
11117 One
"strict
" mode where the forward and reverse DNS lookups are done
11118 using the same LDAP objects, and a
"tree
" mode where the forward and
11119 reverse entries are in two different subtrees in LDAP with a structure
11120 based on the DNS names, as in tjener.intern and
11121 2.2.0.10.in-addr.arpa.
</p
>
11123 <p
>In tree mode, the server is set up to use a LDAP subtree as its
11124 base, and uses a
"base
" scoped search for the DNS name by adding
11125 "dc=tjener,dc=intern,
" to the base with a filter for
11126 "(associateddomain=tjener.intern)
" for the forward entry and
11127 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
11128 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
11129 forward entries, it is looking for attributes named dnsttl, arecord,
11130 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
11131 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
11132 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
11133 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
11134 spfrecord and modifytimestamp. For reverse entries it is looking for
11135 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
11136 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
11137 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
11138 ldapsearch commands could look like this:
</p
>
11140 <blockquote
><pre
>
11141 ldapsearch -h ldap \
11142 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11143 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
11144 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11145 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11146 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11147 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11149 ldapsearch -h ldap \
11150 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11151 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
11152 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
11153 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
11154 srvrecord naptrrecord modifytimestamp
11155 </pre
></blockquote
>
11157 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
11158 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
11159 example LDAP objects used there. In addition to these objects, the
11160 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
11161 also exist.
</p
>
11163 <blockquote
><pre
>
11164 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
11166 objectclass: dnsdomain
11167 objectclass: domainrelatedobject
11170 associateddomain: tjener.intern
11172 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
11174 objectclass: dnsdomain2
11175 objectclass: domainrelatedobject
11177 ptrrecord: tjener.intern
11178 associateddomain:
2.2.0.10.in-addr.arpa
11179 </pre
></blockquote
>
11181 <p
>In strict mode, the server behaves differently. When looking for
11182 forward DNS entries, it is doing a
"subtree
" scoped search with the
11183 same base as in the tree mode for a object with filter
11184 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
11185 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
11186 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
11187 naptrrecord and modifytimestamp. For reverse entires it also do a
11188 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
11189 and the requested attributes are associateddomain, dnsttl and
11190 modifytimestamp. In short, in strict mode the objects with ptrrecord
11191 go away, and the arecord attribute in the forward object is used
11194 <p
>The forward and reverse searches can be simulated using ldapsearch
11195 like this:
</p
>
11197 <blockquote
><pre
>
11198 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11199 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
11200 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11201 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11202 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11203 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11205 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11206 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
11207 </pre
></blockquote
>
11209 <p
>In addition to the forward and reverse searches , there is also a
11210 search for SOA records, which behave similar to the forward and
11211 reverse lookups.
</p
>
11213 <p
>A thing to note with the PowerDNS behaviour is that it do not
11214 specify any objectclass names, and instead look for the attributes it
11215 need to generate a DNS reply. This make it able to work with any
11216 objectclass that provide the needed attributes.
</p
>
11218 <p
>The attributes are normally provided in the cosine (RFC
1274) and
11219 dnsdomain2 schemas. The latter is used for reverse entries like
11220 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
11222 <p
>In Debian Edu, we have created DNS objects using the object classes
11223 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11224 attributes) and domainrelatedobject (for associatedDomain). The use
11225 of structural object classes make it impossible to combine these
11226 classes with the object classes used by DHCP.
</p
>
11228 <p
>There are other schemas that could be used too, for example the
11229 dnszone structural object class used by Gosa and bind-sdb for the DNS
11230 attributes combined with the domainrelatedobject object class, but in
11231 this case some unused attributes would have to be included as well
11232 (zonename and relativedomainname).
</p
>
11234 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
11235 mode and not use any of the existing objectclasses (dnsdomain,
11236 dnsdomain2 and dnszone) when one want to combine the DNS information
11237 with DHCP information, and instead create a auxiliary object class
11238 defined something like this (using the attributes defined for
11239 dnsdomain and dnsdomain2 or dnszone):
</p
>
11241 <blockquote
><pre
>
11242 objectclass ( some-oid NAME
'dnsDomainAux
'
11245 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11246 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11247 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11248 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11249 A6Record $ DNAMERecord
11251 </pre
></blockquote
>
11253 <p
>This will allow any object to become a DNS entry when combined with
11254 the domainrelatedobject object class, and allow any entity to include
11255 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
11256 developers asking for their view on this schema and if they are
11257 interested in providing such schema with PowerDNS, and I hope my
11258 message will be accepted into their mailing list soon.
</p
>
11260 <p
><strong
>ISC dhcp
</strong
></p
>
11262 <p
>The DHCP server searches for specific objectclass and requests all
11263 the object attributes, and then uses the attributes it want. This
11264 make it harder to figure out exactly what attributes are used, but
11265 thanks to the working example in Debian Edu I can at least get an idea
11266 what is needed without having to read the source code.
</p
>
11268 <p
>In the DHCP server configuration, the LDAP base to use and the
11269 search filter to use to locate the correct dhcpServer entity is
11270 stored. These are the relevant entries from
11271 /etc/dhcp3/dhcpd.conf:
</p
>
11273 <blockquote
><pre
>
11274 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
11275 ldap-dhcp-server-cn
"dhcp
";
11276 </pre
></blockquote
>
11278 <p
>The DHCP server uses this information to nest all the DHCP
11279 configuration it need. The cn
"dhcp
" is located using the given LDAP
11280 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
11281 search result is this entry:
</p
>
11283 <blockquote
><pre
>
11284 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11287 objectClass: dhcpServer
11288 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11289 </pre
></blockquote
>
11291 <p
>The content of the dhcpServiceDN attribute is next used to locate the
11292 subtree with DHCP configuration. The DHCP configuration subtree base
11293 is located using a base scope search with base
"cn=DHCP
11294 Config,dc=skole,dc=skolelinux,dc=no
" and filter
11295 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
11296 The search result is this entry:
</p
>
11298 <blockquote
><pre
>
11299 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11302 objectClass: dhcpService
11303 objectClass: dhcpOptions
11304 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11305 dhcpStatements: ddns-update-style none
11306 dhcpStatements: authoritative
11307 dhcpOption: smtp-server code
69 = array of ip-address
11308 dhcpOption: www-server code
72 = array of ip-address
11309 dhcpOption: wpad-url code
252 = text
11310 </pre
></blockquote
>
11312 <p
>Next, the entire subtree is processed, one level at the time. When
11313 all the DHCP configuration is loaded, it is ready to receive requests.
11314 The subtree in Debian Edu contain objects with object classes
11315 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11316 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11317 and information about netmasks, dynamic range etc. Leaving out the
11318 details here because it is not relevant for the focus of my
11319 investigation, which is to see if it is possible to merge dns and dhcp
11320 related computer objects.
</p
>
11322 <p
>When a DHCP request come in, LDAP is searched for the MAC address
11323 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
11324 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
11325 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11326 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
11329 <blockquote
><pre
>
11330 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11333 objectClass: dhcpHost
11334 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11335 dhcpStatements: fixed-address hostname
11336 </pre
></blockquote
>
11338 <p
>There is less flexiblity in the way LDAP searches are done here.
11339 The object classes need to have fixed names, and the configuration
11340 need to be stored in a fairly specific LDAP structure. On the
11341 positive side, the invidiual dhcpHost entires can be anywhere without
11342 the DN pointed to by the dhcpServer entries. The latter should make
11343 it possible to group all host entries in a subtree next to the
11344 configuration entries, and this subtree can also be shared with the
11345 DNS server if the schema proposed above is combined with the dhcpHost
11346 structural object class.
11348 <p
><strong
>Conclusion
</strong
></p
>
11350 <p
>The PowerDNS implementation seem to be very flexible when it come
11351 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
11352 come to the the LDAP structure, the
"strict
" mode is very flexible,
11353 allowing DNS objects to be stored anywhere under the base cn specified
11354 in the configuration.
</p
>
11356 <p
>The DHCP implementation on the other hand is very inflexible, both
11357 regarding which LDAP schemas to use and which LDAP structure to use.
11358 I guess one could implement ones own schema, as long as the
11359 objectclasses and attributes have the names used, but this do not
11360 really help when the DHCP subtree need to have a fairly fixed
11361 structure.
</p
>
11363 <p
>Based on the observed behaviour, I suspect a LDAP structure like
11364 this might work for Debian Edu:
</p
>
11366 <blockquote
><pre
>
11368 cn=machine-info (dhcpService) - dhcpServiceDN points here
11369 cn=dhcp (dhcpServer)
11370 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11371 cn=
10.0.2.0 (dhcpSubnet)
11372 cn=group1 (dhcpGroup/dhcpOptions)
11373 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11374 cn=
192.168.0.0 (dhcpSubnet)
11375 cn=group1 (dhcpGroup/dhcpOptions)
11376 ou=machines - PowerDNS base points here
11377 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11378 </pre
></blockquote
>
11380 <P
>This is not tested yet. If the DHCP server require the dhcpHost
11381 entries to be in the dhcpGroup subtrees, the entries can be stored
11382 there instead of a common machines subtree, and the PowerDNS base
11383 would have to be moved one level up to the machine-info subtree.
</p
>
11385 <p
>The combined object under the machines subtree would look something
11386 like this:
</p
>
11388 <blockquote
><pre
>
11389 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11392 objectClass: dhcpHost
11393 objectclass: domainrelatedobject
11394 objectclass: dnsDomainAux
11395 associateddomain: hostname.intern
11396 arecord:
10.11.12.13
11397 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11398 dhcpStatements: fixed-address hostname.intern
11399 </pre
></blockquote
>
11401 </p
>One could even add the LTSP configuration associated with a given
11402 machine, as long as the required attributes are available in a
11403 auxiliary object class.
</p
>
11408 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
11409 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
11410 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
11411 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
11412 <description><p
>For a while now, I have wanted to find a way to change the DNS and
11413 DHCP services in Debian Edu to use the same LDAP objects for a given
11414 computer, to avoid the possibility of having a inconsistent state for
11415 a computer in LDAP (as in DHCP but no DNS entry or the other way
11416 around) and make it easier to add computers to LDAP.
</p
>
11418 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
11419 information finally found a solution that seem to work.
</p
>
11421 <p
>The old setup required three LDAP objects for a given computer.
11422 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11423 we switch powerdns to use its strict LDAP method (ldap-method=strict
11424 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11425 merged into one while making it impossible to transfer the reverse map
11426 to a slave DNS server.
</p
>
11428 <p
>If we also replace the object class used to get the DNS related
11429 attributes to one allowing these attributes to be combined with the
11430 dhcphost object class, we can merge the DNS and DHCP entries into one.
11431 I
've written such object class in the dnsdomainaux.schema file (need
11432 proper OIDs, but that is a minor issue), and tested the setup. It
11433 seem to work.
</p
>
11435 <p
>With this test setup in place, we can get away with one LDAP object
11436 for both DNS and DHCP, and even the LTSP configuration I suggested in
11437 an earlier email. The combined LDAP object will look something like
11440 <blockquote
><pre
>
11441 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11443 objectClass: dhcphost
11444 objectclass: domainrelatedobject
11445 objectclass: dnsdomainaux
11446 associateddomain: hostname.intern
11447 arecord:
10.11.12.13
11448 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
11449 dhcpstatements: fixed-address hostname
11451 </pre
></blockquote
>
11453 <p
>The DNS server uses the associateddomain and arecord entries, while
11454 the DHCP server uses the dhcphwaddress and dhcpstatements entries
11455 before asking DNS to resolve the fixed-adddress. LTSP will use
11456 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
11458 <p
>I am not yet sure if I can get the DHCP server to look for its
11459 dhcphost in a different location, to allow us to put the objects
11460 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
11461 that. If I can
't figure out a way to do that, we can still get rid of
11462 the hosts subtree and move all its content into the DHCP Config tree
11463 (which probably should be renamed to be more related to the new
11464 content. I suspect cn=dnsdhcp,ou=services or something like that
11465 might be a good place to put it.
</p
>
11467 <p
>If you want to help out with implementing this for Debian Edu,
11468 please contact us on debian-edu@lists.debian.org.
</p
>
11473 <title>Idea for storing LTSP configuration in LDAP
</title>
11474 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
11475 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
11476 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
11477 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
11478 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
11479 clients, and that this can be used to fetch configuration from LDAP if
11480 Debian Edu choose to store configuration there.
</p
>
11482 <p
>Armed with this information, I got inspired and wrote a test module
11483 to get configuration from LDAP. The idea is to look up the MAC
11484 address of the client in LDAP, and look for attributes on the form
11485 ltspconfigsetting=value, and use this to export SETTING=value to the
11486 LTSP clients.
</p
>
11488 <p
>The goal is to be able to store the LTSP configuration attributes
11489 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
11490 allowing us to store all information about a computer in one place.
</p
>
11492 <p
>This is a untested draft implementation, and I welcome feedback on
11493 this approach. A real LDAP schema for the ltspClientAux objectclass
11494 need to be written. Comments, suggestions, etc?
</p
>
11496 <blockquote
><pre
>
11497 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
11499 # Fetch LTSP client settings from LDAP based on MAC address
11501 # Uses ethernet address as stored in the dhcpHost objectclass using
11502 # the dhcpHWAddress attribute or ethernet address stored in the
11503 # ieee802Device objectclass with the macAddress attribute.
11505 # This module is written to be schema agnostic, and only depend on the
11506 # existence of attribute names.
11508 # The LTSP configuration variables are saved directly using a
11509 # ltspConfig prefix and uppercasing the rest of the attribute name.
11510 # To set the SERVER variable, set the ltspConfigServer attribute.
11512 # Some LDAP schema should be created with all the relevant
11513 # configuration settings. Something like this should work:
11515 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
11518 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
11520 LDAPSERVER=$(debian-edu-ldapserver)
11521 if [
"$LDAPSERVER
" ] ; then
11522 LDAPBASE=$(debian-edu-ldapserver -b)
11523 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
11524 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
11525 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
11526 grep
'^ltspConfig
' | while read attr value ; do
11527 # Remove prefix and convert to upper case
11528 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
11529 # bass value on to clients
11530 eval
"$attr=$value; export $attr
"
11534 </pre
></blockquote
>
11536 <p
>I
'm not sure this shell construction will work, because I suspect
11537 the while block might end up in a subshell causing the variables set
11538 there to not show up in ltsp-config, but if that is the case I am sure
11539 the code can be restructured to make sure the variables are passed on.
11540 I expect that can be solved with some testing. :)
</p
>
11542 <p
>If you want to help out with implementing this for Debian Edu,
11543 please contact us on debian-edu@lists.debian.org.
</p
>
11545 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
11546 configuration in LDAP that was created around year
2000 by
11547 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
11548 Xperience, Inc.,
2000</a
>. I found its
11549 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
11550 personal home page over at redhat.com.
</p
>
11555 <title>jXplorer, a very nice LDAP GUI
</title>
11556 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
11557 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
11558 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
11559 <description><p
>Since
11560 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
11561 last post
</a
> about available LDAP tools in Debian, I was told about a
11562 LDAP GUI that is even better than luma. The java application
11563 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
11564 moving LDAP objects and subtrees using drag-and-drop, and can
11565 authenticate using Kerberos. I have only tested the Kerberos
11566 authentication, but do not have a LDAP setup allowing me to rewrite
11567 LDAP with my test user yet. It is
11568 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
11569 Debian
</a
> testing and unstable at the moment. The only problem I
11570 have with it is how it handle errors. If something go wrong, its
11571 non-intuitive behaviour require me to go through some query work list
11572 and remove the failing query. Nothing big, but very annoying.
</p
>
11577 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
11578 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
11579 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
11580 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
11581 <description><p
>Here is a short update on my
<a
11582 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
11583 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
11584 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
11585 not reporting the status for KDE, because the upgrade crashes when
11586 aptitude try because of missing conflicts
11587 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
11588 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
11590 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
11591 complete list of the installed packages. Based on this I see these
11592 differences when I did a test run today. As usual, I do not really
11593 know what the correct set of packages would be, but thought it best to
11594 publish the difference.
</p
>
11596 <p
>Installed using apt-get, missing with aptitude
</p
>
11598 <blockquote
><p
>
11599 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
11600 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
11601 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
11602 libgtksourceview-common libpt-
1.10.10-plugins-alsa
11603 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
11604 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
11605 python-
4suite-xml python-eggtrayicon python-gtkhtml2
11606 python-gtkmozembed svgalibg1 xserver-xephyr zip
11607 </p
></blockquote
>
11609 <p
>Installed using apt-get, removed with aptitude
</p
>
11611 <blockquote
><p
>
11612 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
11613 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
11614 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
11615 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
11616 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
11617 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
11618 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
11619 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
11620 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
11621 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
11622 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
11623 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
11624 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
11625 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
11626 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
11627 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
11628 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
11629 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
11630 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
11631 mysql-common swfdec-gnome totem-gstreamer wodim
11632 </p
></blockquote
>
11634 <p
>Installed using aptitude, missing with apt-get
</p
>
11636 <blockquote
><p
>
11637 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
11638 python-gnomekeyring python-wnck rhythmbox-plugins xorg
11639 xserver-xorg-input-all xserver-xorg-input-evdev
11640 xserver-xorg-input-kbd xserver-xorg-input-mouse
11641 xserver-xorg-input-synaptics xserver-xorg-video-all
11642 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
11643 xserver-xorg-video-chips xserver-xorg-video-cirrus
11644 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11645 xserver-xorg-video-glint xserver-xorg-video-i128
11646 xserver-xorg-video-i740 xserver-xorg-video-mach64
11647 xserver-xorg-video-mga xserver-xorg-video-neomagic
11648 xserver-xorg-video-nouveau xserver-xorg-video-nv
11649 xserver-xorg-video-r128 xserver-xorg-video-radeon
11650 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
11651 xserver-xorg-video-s3 xserver-xorg-video-s3virge
11652 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
11653 xserver-xorg-video-sis xserver-xorg-video-sisusb
11654 xserver-xorg-video-tdfx xserver-xorg-video-tga
11655 xserver-xorg-video-trident xserver-xorg-video-tseng
11656 xserver-xorg-video-vesa xserver-xorg-video-vmware
11657 xserver-xorg-video-voodoo
11658 </p
></blockquote
>
11660 <p
>Installed using aptitude, removed with apt-get
</p
>
11662 <blockquote
><p
>
11663 deskbar-applet xserver-xorg xserver-xorg-core
11664 xserver-xorg-input-wacom xserver-xorg-video-intel
11665 xserver-xorg-video-openchrome
11666 </p
></blockquote
>
11668 <p
>I was told on IRC that the xorg-xserver package was
11669 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
11670 in git
</a
> today to try to get apt-get to not remove xorg completely.
11671 No idea when it hits Squeeze, but when it does I hope it will reduce
11672 the difference somewhat.
11677 <title>LUMA, a very nice LDAP GUI
</title>
11678 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
11679 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
11680 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
11681 <description><p
>The last few days I have been looking into the status of the LDAP
11682 directory in Debian Edu, and in the process I started to miss a GUI
11683 tool to browse the LDAP tree. The only one I was able to find in
11684 Debian/Squeeze and Lenny is
11685 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
11686 be a great tool to get a overview of the current LDAP directory
11687 populated by default in Skolelinux. Thanks to it, I have been able to
11688 find empty and obsolete subtrees, misplaced objects and duplicate
11689 objects. It will be installed by default in Debian/Squeeze. If you
11690 are working with LDAP, give it a go. :)
</p
>
11692 <p
>I did notice one problem with it I have not had time to report to
11693 the BTS yet. There is no .desktop file in the package, so the tool do
11694 not show up in the Gnome and KDE menus, but only deep down in in the
11695 Debian submenu in KDE. I hope that can be fixed before Squeeze is
11696 released.
</p
>
11698 <p
>I have not yet been able to get it to modify the tree yet. I would
11699 like to move objects and remove subtrees directly in the GUI, but have
11700 not found a way to do that with LUMA yet. So in the mean time, I use
11701 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
11703 <p
>If you have tips on other GUI tools for LDAP that might be useful
11704 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
11706 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
11707 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
11708 useful GUI alternative. It seem like a good tool, but is unmaintained
11709 in Debian and got a RC bug keeping it out of Squeeze. Unless that
11710 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
11715 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
11716 <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>
11717 <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>
11718 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
11719 <description><p
>A while back, I
11720 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
11721 about the fact
</a
> that it is not possible with the provided schemas
11722 for storing DNS and DHCP information in LDAP to combine the two sets
11723 of information into one LDAP object representing a computer.
</p
>
11725 <p
>In the mean time, I discovered that a simple fix would be to make
11726 the dhcpHost object class auxiliary, to allow it to be combined with
11727 the dNSDomain object class, and thus forming one object for one
11728 computer when storing both DHCP and DNS information in LDAP.
</p
>
11730 <p
>If I understand this correctly, it is not safe to do this change
11731 without also changing the assigned number for the object class, and I
11732 do not know enough about LDAP schema design to do that properly for
11733 Debian Edu.
</p
>
11735 <p
>Anyway, for future reference, this is how I believe we could change
11737 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
11738 schema
</a
> to solve at least part of the problem with the LDAP schemas
11739 available today from IETF.
</p
>
11742 --- dhcp.schema (revision
65192)
11743 +++ dhcp.schema (working copy)
11744 @@ -
376,
7 +
376,
7 @@
11745 objectclass (
2.16.840.1.113719.1.203.6.6
11746 NAME
'dhcpHost
'
11747 DESC
'This represents information about a particular client
'
11749 + SUP top AUXILIARY
11751 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
11752 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
11755 <p
>I very much welcome clues on how to do this properly for Debian
11756 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
11757 package, and should thus be free to rewrite it as we see fit.
</p
>
11759 <p
>If you want to help out with implementing this for Debian Edu,
11760 please contact us on debian-edu@lists.debian.org.
</p
>
11765 <title>Calling tasksel like the installer, while still getting useful output
</title>
11766 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
11767 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
11768 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
11769 <description><p
>A few times I have had the need to simulate the way tasksel
11770 installs packages during the normal debian-installer run. Until now,
11771 I have ended up letting tasksel do the work, with the annoying problem
11772 of not getting any feedback at all when something fails (like a
11773 conffile question from dpkg or a download that fails), using code like
11776 <blockquote
><pre
>
11777 export DEBIAN_FRONTEND=noninteractive
11778 tasksel --new-install
11779 </pre
></blockquote
>
11781 This would invoke tasksel, let its automatic task selection pick the
11782 tasks to install, and continue to install the requested tasks without
11783 any output what so ever.
11785 Recently I revisited this problem while working on the automatic
11786 package upgrade testing, because tasksel would some times hang without
11787 any useful feedback, and I want to see what is going on when it
11788 happen. Then it occured to me, I can parse the output from tasksel
11789 when asked to run in test mode, and use that aptitude command line
11790 printed by tasksel then to simulate the tasksel run. I ended up using
11793 <blockquote
><pre
>
11794 export DEBIAN_FRONTEND=noninteractive
11795 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
11797 </pre
></blockquote
>
11799 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
11800 --without-recommends -o APT::Install-Recommends=no -y install
11801 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
11802 ~pimportant
</tt
>", which will install the gnome desktop task, the
11803 laptop task and all packages with priority standard , required and
11804 important, just like tasksel would have done it during
11805 installation.
</p
>
11807 <p
>A better approach is probably to extend tasksel to be able to
11808 install packages without using debconf-apt-progress, for use cases
11809 like this.
</p
>
11814 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
11815 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
11816 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
11817 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
11818 <description><p
>My
11819 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
11820 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
11821 finally made the upgrade logs available from
11822 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
11823 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
11824 apt and aptitude, and found their differences interesting. This time
11825 I will only focus on their removal plans.
</p
>
11827 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
11828 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
11829 surprising part is that it want to remove xorg and all
11830 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
11831 sure why. When asking aptitude to do the same, it want to remove
129
11832 packages, but most of them are library packages I suspect are no
11833 longer needed. Both of them want to remove bluetooth packages, which
11834 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
11836 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
11837 which seem like a bad idea and xorg the same way as with Gnome. Asking
11838 aptitude for the same, it wants to remove
192 packages, none which are
11839 too surprising.
</p
>
11841 <p
>I guess the removal of xorg during upgrades should be investigated
11842 and avoided, and perhaps others as well. Here are the complete list
11843 of planned removals. The complete logs is available from the URL
11844 above. Note if you want to repeat these tests, that the upgrade test
11845 for kde+apt-get hung in the tasksel setup because of dpkg asking
11846 conffile questions. No idea why. I worked around it by using
11847 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
11848 continue.
</p
>
11850 <p
><b
>apt-get gnome
72</b
>
11851 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
11852 gnome-desktop-environment gnome-network-admin gtkhtml3.14
11853 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
11854 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
11855 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
11856 serpentine swfdec-mozilla update-manager xorg xserver-xorg
11857 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11858 xserver-xorg-input-kbd xserver-xorg-input-mouse
11859 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11860 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11861 xserver-xorg-video-ati xserver-xorg-video-chips
11862 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11863 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11864 xserver-xorg-video-glint xserver-xorg-video-i128
11865 xserver-xorg-video-i740 xserver-xorg-video-imstt
11866 xserver-xorg-video-intel xserver-xorg-video-mach64
11867 xserver-xorg-video-mga xserver-xorg-video-neomagic
11868 xserver-xorg-video-nsc xserver-xorg-video-nv
11869 xserver-xorg-video-openchrome xserver-xorg-video-r128
11870 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11871 xserver-xorg-video-rendition xserver-xorg-video-s3
11872 xserver-xorg-video-s3virge xserver-xorg-video-savage
11873 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11874 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11875 xserver-xorg-video-tga xserver-xorg-video-trident
11876 xserver-xorg-video-tseng xserver-xorg-video-v4l
11877 xserver-xorg-video-vesa xserver-xorg-video-vga
11878 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
11879 xulrunner-
1.9-gnome-support
</p
>
11881 <p
><b
>aptitude gnome
129</b
>
11883 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
11884 djvulibre-desktop finger gnome-app-install gnome-mount
11885 gnome-network-admin gnome-spell gnome-vfs-obexftp
11886 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
11887 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
11888 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
11889 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
11890 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
11891 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
11892 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
11893 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
11894 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
11895 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
11896 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
11897 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
11898 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
11899 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
11900 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
11901 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
11902 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
11903 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
11904 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
11905 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
11906 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
11907 openoffice.org-writer2latex openssl-blacklist p7zip
11908 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
11909 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
11910 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
11911 swfdec-mozilla totem-gstreamer update-manager wodim
11912 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11913 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11916 <p
><b
>apt-get kde
82</b
>
11918 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
11919 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
11920 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
11921 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
11922 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
11923 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
11924 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11925 xserver-xorg-input-kbd xserver-xorg-input-mouse
11926 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11927 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11928 xserver-xorg-video-ati xserver-xorg-video-chips
11929 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11930 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11931 xserver-xorg-video-glint xserver-xorg-video-i128
11932 xserver-xorg-video-i740 xserver-xorg-video-imstt
11933 xserver-xorg-video-intel xserver-xorg-video-mach64
11934 xserver-xorg-video-mga xserver-xorg-video-neomagic
11935 xserver-xorg-video-nsc xserver-xorg-video-nv
11936 xserver-xorg-video-openchrome xserver-xorg-video-r128
11937 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11938 xserver-xorg-video-rendition xserver-xorg-video-s3
11939 xserver-xorg-video-s3virge xserver-xorg-video-savage
11940 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11941 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11942 xserver-xorg-video-tga xserver-xorg-video-trident
11943 xserver-xorg-video-tseng xserver-xorg-video-v4l
11944 xserver-xorg-video-vesa xserver-xorg-video-vga
11945 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
11947 <p
><b
>aptitude kde
192</b
>
11948 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
11949 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
11950 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
11951 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
11952 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
11953 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
11954 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
11955 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
11956 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
11957 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
11958 kghostview khelpcenter khexedit kiconedit kitchensync klatin
11959 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
11960 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
11961 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
11962 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
11963 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
11964 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
11965 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
11966 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
11967 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
11968 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
11969 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
11970 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
11971 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
11972 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
11973 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
11974 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
11975 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
11976 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
11977 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
11978 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
11979 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
11980 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
11981 texlive-common texlive-doc-base texlive-fonts-recommended
11982 xserver-xorg-video-cyrix xserver-xorg-video-imstt
11983 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
11984 xulrunner-
1.9</p
>
11990 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
11991 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
11992 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
11993 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
11994 <description><p
>The last few days I have done some upgrade testing in Debian, to
11995 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
11996 have been discovered and reported in the process
11997 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
11998 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
11999 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
12000 kdebase-workspace-data), and to get a more regular testing going on, I
12001 am working on a script to automate the test.
</p
>
12003 <p
>The idea is to create a Lenny chroot and use tasksel to install a
12004 Gnome or KDE desktop installation inside the chroot before upgrading
12005 it. To ensure no services are started in the chroot, a policy-rc.d
12006 script is inserted. To make sure tasksel believe it is to install a
12007 desktop on a laptop, the tasksel tests are replaced in the chroot
12008 (only acceptable because this is a throw-away chroot).
</p
>
12010 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
12011 currently always fail because udev refuses to upgrade with the kernel
12012 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
12013 is created. The bug report
12014 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
12015 this problem do not trigger in a chroot, but I touch the file anyway
12016 to make sure the upgrade go well. Testing on virtual and real
12017 hardware have failed me because of udev so far, and creating this file
12018 do the trick in such settings anyway. This is a
12019 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
12020 issue
</a
> and the current udev behaviour is intended by the udev
12021 maintainer because he lack the resources to rewrite udev to keep
12022 working with old kernels or something like that. I really wish the
12023 udev upstream would keep udev backwards compatible, to avoid such
12024 upgrade problem, but given that they fail to do so, I guess
12025 documenting the way out of this mess is the best option we got for
12026 Debian Squeeze.
</p
>
12028 <p
>Anyway, back to the task at hand, testing upgrades. This test
12029 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
12032 <blockquote
><pre
>
12036 if [
"$
1" ] ; then
12045 exec
&lt; /dev/null
12047 mirror=http://ftp.skolelinux.org/debian
12048 tmpdir=chroot-$from-upgrade-$to-$desktop
12050 debootstrap $from $tmpdir $mirror
12051 chroot $tmpdir aptitude update
12052 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
12056 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
12058 umount $tmpdir/proc
12060 mount -t proc proc $tmpdir/proc
12061 # Make sure proc is unmounted also on failure
12062 trap exit_cleanup EXIT INT
12064 chroot $tmpdir aptitude -y install debconf-utils
12066 # Make sure tasksel autoselection trigger. It need the test scripts
12067 # to return the correct answers.
12068 echo tasksel tasksel/desktop multiselect $desktop | \
12069 chroot $tmpdir debconf-set-selections
12071 # Include the desktop and laptop task
12072 for test in desktop laptop ; do
12073 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
12077 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
12080 DEBIAN_FRONTEND=noninteractive
12081 DEBIAN_PRIORITY=critical
12082 export DEBIAN_FRONTEND DEBIAN_PRIORITY
12083 chroot $tmpdir tasksel --new-install
12085 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
12086 chroot $tmpdir aptitude update
12087 touch $tmpdir/etc/udev/kernel-upgrade
12088 chroot $tmpdir aptitude -y dist-upgrade
12090 </pre
></blockquote
>
12092 <p
>I suspect it would be useful to test upgrades with both apt-get and
12093 with aptitude, but I have not had time to look at how they behave
12094 differently so far. I hope to get a cron job running to do the test
12095 regularly and post the result on the web. The Gnome upgrade currently
12096 work, while the KDE upgrade fail because of the bug in
12097 kdebase-workspace-data
</p
>
12099 <p
>I am not quite sure what kind of extract from the huge upgrade logs
12100 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
12101 post, so I will refrain from trying. I can report that for Gnome,
12102 aptitude report
760 packages upgraded,
448 newly installed,
129 to
12103 remove and
1 not upgraded and
1024MB need to be downloaded while for
12104 KDE the same numbers are
702 packages upgraded,
507 newly installed,
12105 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
12107 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
12108 is able to migrate to dependency based boot sequencing and parallel
12109 booting without a hitch. Was unsure if there were still bugs with
12110 packages failing to clean up their obsolete init.d script during
12111 upgrades, and no such problem seem to affect the Gnome desktop+laptop
12112 packages.
</p
>
12117 <title>Upstart or sysvinit - as init.d scripts see it
</title>
12118 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
12119 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
12120 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
12121 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
12122 scripts to migrate (some of) their operations to upstart job while
12123 keeping the init.d for hurd and kfreebsd. The packages with such
12124 needs will need a way to get their init.d scripts to behave
12125 differently when used with sysvinit and with upstart. Because of
12126 this, I had a look at the environment variables set when a init.d
12127 script is running under upstart, and when it is not.
</p
>
12129 <p
>With upstart, I notice these environment variables are set when a
12130 script is started from rcS.d/ (ignoring some irrelevant ones like
12131 COLUMNS):
</p
>
12133 <blockquote
><pre
>
12139 UPSTART_EVENTS=startup
12141 UPSTART_JOB=rc-sysinit
12142 </pre
></blockquote
>
12144 <p
>With sysvinit, these environment variables are set for the same
12147 <blockquote
><pre
>
12148 INIT_VERSION=sysvinit-
2.88
12153 </pre
></blockquote
>
12155 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
12156 sysvinit are not set by upstart. Not sure if it is intentional or not
12157 to not be compatible with sysvinit in this regard.
</p
>
12159 <p
>For scripts needing to behave differently when upstart is used,
12160 looking for the UPSTART_JOB environment variable seem to be a good
12166 <title>A manual for standards wars...
</title>
12167 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
12168 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
12169 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
12170 <description><p
>Via the
12171 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
12172 of Rob Weir
</a
> I came across the very interesting essay named
12173 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
12174 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
12175 following the standards wars of today.
</p
>
12180 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
12181 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
12182 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
12183 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
12184 <description><p
>When using sitesummary at a site to track machines, it is possible
12185 to get a list of the machine types in use thanks to the DMI
12186 information extracted from each machine. The script to do so is
12187 included in the sitesummary package, and here is example output from
12188 the Skolelinux build servers:
</p
>
12190 <blockquote
><pre
>
12191 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
12193 Dell Computer Corporation
1
12196 eserver xSeries
345 -[
8670M1X]-
1
12200 </pre
></blockquote
>
12202 <p
>The quality of the report depend on the quality of the DMI tables
12203 provided in each machine. Here there are Intel machines without model
12204 information listed with Intel as vendor and no model, and virtual Xen
12205 machines listed as [no-dmi-info]. One can add -l as a command line
12206 option to list the individual machines.
</p
>
12208 <p
>A larger list is
12209 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
12210 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
12211 provide the basic sitesummary report publicly. In their report there
12212 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
12213 their machines, and as sitesummary is available in both distributions,
12214 it is trivial to get all of them to report to the same central
12215 collector.
</p
>
12220 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
12221 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
12222 <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>
12223 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
12224 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
12225 start at boot when an NVidia video card is used is handled. The
12226 problem seem to be that the nvidia X.org driver uses a long time to
12227 initialize, and this duration is longer than kdm is configured to
12230 <p
>I came across two bugs related to this issue,
12231 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
12232 against initscripts and passed on to nvidia-glx when it became obvious
12233 that the nvidia drivers were involved, and
12234 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
12235 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
12237 <p
>To me, it seem that no-one is interested in actually solving the
12238 problem nvidia video card owners experience and make sure the Debian
12239 distribution work out of the box for these users. The nvidia driver
12240 maintainers expect kdm to be set up to wait longer, while kdm expect
12241 the nvidia driver maintainers to fix the driver to start faster, and
12242 while they wait for each other I guess the users end up switching to a
12243 distribution that work for them. I have no idea what the solution is,
12244 but I am pretty sure that waiting for each other is not it.
</p
>
12246 <p
>I wonder why we end up handling bugs this way.
</p
>
12251 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
12252 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
12253 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
12254 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
12255 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
12256 The feature seem to hold up pretty well, but three fairly serious
12257 issues are known and should be solved:
12259 <p
><ul
>
12261 <li
>The wicd package seen to
12262 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
12263 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
12264 parallel booting is enabled. No idea why, but the wicd maintainer
12265 seem to be on the case.
</li
>
12267 <li
>The nvidia X driver seem to
12268 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
12269 triggered more easily when parallel booting is in effect. The
12270 maintainer is on the case.
</li
>
12272 <li
>The sysv-rc package fail to properly enable dependency based boot
12273 sequencing (the shutdown is broken) when old file-rc users
12274 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
12275 sysv-rc. One way to solve it would be for file-rc to create
12276 /etc/init.d/.legacy-bootordering, and another is to try to make
12277 sysv-rc more robust. Will investigate some more and probably upload a
12278 workaround in sysv-rc to help those trying to move from file-rc to
12279 sysv-rc get a working shutdown.
</li
>
12281 </ul
></p
>
12283 <p
>All in all not many surprising issues, and all of them seem
12284 solvable before Squeeze is released. In addition to these there are
12285 some packages with bugs in their dependencies and run level settings,
12286 which I expect will be fixed in a reasonable time span.
</p
>
12288 <p
>If you report any problems with dependencies in init.d scripts to
12289 the BTS, please usertag the report to get it to show up at
12290 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12291 list of usertagged bugs related to this
</a
>.
</p
>
12293 <p
>Update: Correct bug number to file-rc issue.
</p
>
12298 <title>More flexible firmware handling in debian-installer
</title>
12299 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
12300 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
12301 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
12302 <description><p
>After a long break from debian-installer development, I finally
12303 found time today to return to the project. Having to spend less time
12304 working dependency based boot in debian, as it is almost complete now,
12305 definitely helped freeing some time.
</p
>
12307 <p
>A while back, I ran into a problem while working on Debian Edu. We
12308 include some firmware packages on the Debian Edu CDs, those needed to
12309 get disk and network controllers working. Without having these
12310 firmware packages available during installation, it is impossible to
12311 install Debian Edu on the given machine, and because our target group
12312 are non-technical people, asking them to provide firmware packages on
12313 an external medium is a support pain. Initially, I expected it to be
12314 enough to include the firmware packages on the CD to get
12315 debian-installer to find and use them. This proved to be wrong.
12316 Next, I hoped it was enough to symlink the relevant firmware packages
12317 to some useful location on the CD (tried /cdrom/ and
12318 /cdrom/firmware/). This also proved to not work, and at this point I
12319 found time to look at the debian-installer code to figure out what was
12320 going to work.
</p
>
12322 <p
>The firmware loading code is in the hw-detect package, and a closer
12323 look revealed that it would only look for firmware packages outside
12324 the installation media, so the CD was never checked for firmware
12325 packages. It would only check USB sticks, floppies and other
12326 "external
" media devices. Today I changed it to also look in the
12327 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12328 solve the problem I ran into with Debian edu. I also changed it to
12329 look in /firmware/, to make sure the installer also find firmware
12330 provided in the initrd when booting the installer via PXE, to allow us
12331 to provide the same feature in the PXE setup included in Debian
12334 <p
>To make sure firmware deb packages with a license questions are not
12335 activated without asking if the license is accepted, I extended
12336 hw-detect to look for preinst scripts in the firmware packages, and
12337 run these before activating the firmware during installation. The
12338 license question is asked using debconf in the preinst, so this should
12339 solve the issue for the firmware packages I have looked at so far.
</p
>
12341 <p
>If you want to discuss the details of these features, please
12342 contact us on debian-boot@lists.debian.org.
</p
>
12347 <title>Parallellized boot is now the default in Debian/unstable
</title>
12348 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
12349 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
12350 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
12351 <description><p
>Since this evening, parallel booting is the default in
12352 Debian/unstable for machines using dependency based boot sequencing.
12353 Apparently the testing of concurrent booting has been wider than
12354 expected, if I am to believe the
12355 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12356 on debian-devel@
</a
>, and I concluded a few days ago to move forward
12357 with the feature this weekend, to give us some time to detect any
12358 remaining problems before Squeeze is frozen. If serious problems are
12359 detected, it is simple to change the default back to sequential boot.
12360 The upload of the new sysvinit package also activate a new upstream
12363 More information about
12364 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12365 based boot sequencing
</a
> is available from the Debian wiki. It is
12366 currently possible to disable parallel booting when one run into
12367 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
12369 <blockquote
><pre
>
12371 </pre
></blockquote
>
12373 <p
>If you report any problems with dependencies in init.d scripts to
12374 the BTS, please usertag the report to get it to show up at
12375 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12376 list of usertagged bugs related to this
</a
>.
</p
>
12381 <title>Sitesummary tip: Listing MAC address of all clients
</title>
12382 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
12383 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
12384 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
12385 <description><p
>In the recent Debian Edu versions, the
12386 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
12387 system
</a
> is used to keep track of the machines in the school
12388 network. Each machine will automatically report its status to the
12389 central server after boot and once per night. The network setup is
12390 also reported, and using this information it is possible to get the
12391 MAC address of all network interfaces in the machines. This is useful
12392 to update the DHCP configuration.
</p
>
12394 <p
>To give some idea how to use sitesummary, here is a one-liner to
12395 ist all MAC addresses of all machines reporting to sitesummary. Run
12396 this on the collector host:
</p
>
12398 <blockquote
><pre
>
12399 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
12400 </pre
></blockquote
>
12402 <p
>This will list all MAC addresses assosiated with all machine, one
12403 line per machine and with space between the MAC addresses.
</p
>
12405 <p
>To allow system administrators easier job at adding static DHCP
12406 addresses for hosts, it would be possible to extend this to fetch
12407 machine information from sitesummary and update the DHCP and DNS
12408 tables in LDAP using this information. Such tool is unfortunately not
12409 written yet.
</p
>
12414 <title>systemd, an interesting alternative to upstart
</title>
12415 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
12416 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
12417 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
12418 <description><p
>The last few days a new boot system called
12419 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
12421 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
12423 to the free software world. I have not yet had time to play around
12424 with it, but it seem to be a very interesting alternative to
12425 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
12426 a good alternative for Debian when we are able to switch to an event
12427 based boot system. Tollef is
12428 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
12429 systemd into Debian, and I look forward to seeing how well it work. I
12430 like the fact that systemd handles init.d scripts with dependency
12431 information natively, allowing them to run in parallel where upstart
12432 at the moment do not.
</p
>
12434 <p
>Unfortunately do systemd have the same problem as upstart regarding
12435 platform support. It only work on recent Linux kernels, and also need
12436 some new kernel features enabled to function properly. This means
12437 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12438 system. Not sure how that will be handled if systemd proves to be the
12439 way forward.
</p
>
12441 <p
>In the mean time, based on the
12442 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12443 on debian-devel@
</a
> regarding parallel booting in Debian, I have
12444 decided to enable full parallel booting as the default in Debian as
12445 soon as possible (probably this weekend or early next week), to see if
12446 there are any remaining serious bugs in the init.d dependencies. A
12447 new version of the sysvinit package implementing this change is
12448 already in experimental. If all go well, Squeeze will be released
12449 with parallel booting enabled by default.
</p
>
12454 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
12455 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
12456 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
12457 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
12458 <description><p
>These days, the init.d script dependencies in Squeeze are quite
12459 complete, so complete that it is actually possible to run all the
12460 init.d scripts in parallell based on these dependencies. If you want
12461 to test your Squeeze system, make sure
12462 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12463 based boot sequencing
</a
> is enabled, and add this line to
12464 /etc/default/rcS:
</p
>
12466 <blockquote
><pre
>
12467 CONCURRENCY=makefile
12468 </pre
></blockquote
>
12470 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
12471 scripts in parallel using the dependency information stored in
12472 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
12473 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
12474 to try to start the kdm and gdm scripts as early as possible, and will
12475 start the facilities required by kdm or gdm as early as possible to
12476 make this happen.
</p
>
12478 <p
>Give it a try, and see if you like the result. If some services
12479 fail to start properly, it is most likely because they have incomplete
12480 init.d script dependencies in their startup script (or some of their
12481 dependent scripts have incomplete dependencies). Report bugs and get
12482 the package maintainers to fix it. :)
</p
>
12484 <p
>Running scripts in parallel could be the default in Debian when we
12485 manage to get the init.d script dependencies complete and correct. I
12486 expect we will get there in Squeeze+
1, if we get manage to test and
12487 fix the remaining issues.
</p
>
12489 <p
>If you report any problems with dependencies in init.d scripts to
12490 the BTS, please usertag the report to get it to show up at
12491 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12492 list of usertagged bugs related to this
</a
>.
</p
>
12497 <title>Debian has switched to dependency based boot sequencing
</title>
12498 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
12499 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
12500 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
12501 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
12502 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
12503 have been migrated to using dependency based boot sequencing. This
12504 conclude work me and others have been doing for the last three days.
12505 It feels great to see this finally part of the default Debian
12506 installation. Now we just need to weed out the last few problems that
12507 are bound to show up, to get everything ready for Squeeze.
</p
>
12509 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
12510 fixing the more fundamental problem of handing the event based
12511 non-predictable kernel in the early boot.
</p
>
12516 <title>Taking over sysvinit development
</title>
12517 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
12518 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
12519 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
12520 <description><p
>After several years of frustration with the lack of activity from
12521 the existing sysvinit upstream developer, I decided a few weeks ago to
12522 take over the package and become the new upstream. The number of
12523 patches to track for the Debian package was becoming a burden, and the
12524 lack of synchronization between the distribution made it hard to keep
12525 the package up to date.
</p
>
12527 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
12528 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
12529 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
12530 and Fedora), based on the patches currently in use in these
12531 distributions. We Debian maintainers plan to move to this tarball as
12532 the new upstream as soon as we find time to do the merge. Since the
12533 new tarball was created, we agreed with Werner at SuSe to make a new
12534 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
12535 development there. The project is registered and currently waiting
12536 for approval by the Savannah administrators, and as soon as it is
12537 approved, we will import the old versions from svn and continue
12538 working on the future release.
</p
>
12540 <p
>It is a bit ironic that this is done now, when some of the involved
12541 distributions are moving to upstart as a syvinit replacement.
</p
>
12546 <title>Debian boots quicker and quicker
</title>
12547 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
12548 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
12549 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
12550 <description><p
>I spent Monday and tuesday this week in London with a lot of the
12551 people involved in the boot system on Debian and Ubuntu, to see if we
12552 could find more ways to speed up the boot system. This was an Ubuntu
12554 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
12555 gathering
</a
>. It was quite productive. We also discussed the future
12556 of boot systems, and ways to handle the increasing number of boot
12557 issues introduced by the Linux kernel becoming more and more
12558 asynchronous and event base. The Ubuntu approach using udev and
12559 upstart might be a good way forward. Time will show.
</p
>
12561 <p
>Anyway, there are a few ways at the moment to speed up the boot
12562 process in Debian. All of these should be applied to get a quick
12567 <li
>Use dash as /bin/sh.
</li
>
12569 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
12570 clock is in UTC.
</li
>
12572 <li
>Install and activate the insserv package to enable
12573 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12574 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
12578 These points are based on the Google summer of code work done by
12579 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
12580 Villegas
</a
>.
12582 <p
>Support for makefile-style concurrency during boot was uploaded to
12583 unstable yesterday. When we tested it, we were able to cut
6 seconds
12584 from the boot sequence. It depend on very correct dependency
12585 declaration in all init.d scripts, so I expect us to find edge cases
12586 where the dependences in some scripts are slightly wrong when we start
12587 using this.
</p
>
12589 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
12590 introduced by Raphael Geissert today, one that could affect the
12591 startup speed as well. Instead of starting some scripts concurrently
12592 from rcS.d/ and another set of scripts from rc2.d/, it would be
12593 possible to run a of them in the same process. A quick way to test
12594 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
12595 insserv
'. Will need to test if that work. :)
</p
>
12600 <title>BSAs påstander om piratkopiering møter motstand
</title>
12601 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
12602 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
12603 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
12604 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
12605 programvareselskapene som Microsoft og Apple, publisert en rapport der
12606 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
12607 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
12609 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
12610 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
12611 dagene. Et spesielt interessant kommentar fra Sverige,
12612 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
12613 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
12616 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
12617 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
12618 företag.
"Man bör nog kanske inte se de här siffrorna som helt
12619 exakta
", säger BSAs Sverigechef John Hugosson.
12620 </blockquote
>
12622 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
12623 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
12624 piracy figures need a shot of reality
</a
> og
<a
12625 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
12626 Copyright Treaty Work?
</a
></p
>
12628 <p
>Fant lenkene via
<a
12629 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
12630 på Slashdot
</a
>.
</p
>
12635 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
12636 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
12637 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
12638 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
12639 <description><p
>Kom over
12640 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
12641 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
12642 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
12643 jobber til daglig. En rask opptelling forteller meg at vi har
490
12644 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
12645 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
12646 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
12651 <title>Kryptert harddisk - naturligvis
</title>
12652 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
12653 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
12654 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
12655 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
12656 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
12657 når en tar tap av arbeidstid, fortrolige dokumenter,
12658 personopplysninger og alt annet det innebærer. Det er ingen tvil om
12659 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
12660 til at jeg har kryptert harddisken på både kontormaskinen og min
12661 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
12662 komme på avveie, den første informasjon relatert til jobben min ved
12663 Universitetet i Oslo, og den andre relatert til blant annet
12664 foreningsarbeide. Kryptering av diskene gjør at det er lite
12665 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
12666 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
12667 og en reboot vil gjøre at de ber om passord før de vil starte opp.
12668 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
12669 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
12670 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
12671 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
12672 det er gjort slik jeg gjør det er minimale, og gevinstene er
12673 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
12674 maskinen reinstalleres og alt er tapt.
</p
>
12676 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
12677 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
12678 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
12679 er for min del høyere enn gevinsten. Jeg tror oddsene for at
12680 f.eks. etteretningsorganisasjoner har glede av å titte på mine
12681 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
12682 gjøre det vanskeligere for angripere med kompetanse og ressurser er
12683 betydelige.
</p
>
12688 <title>Two projects that have improved the quality of free software a lot
</title>
12689 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
12690 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
12691 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
12692 <description><p
>There are two software projects that have had huge influence on the
12693 quality of free software, and I wanted to mention both in case someone
12694 do not yet know them.
</p
>
12696 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
12697 tool to detect and expose errors in the memory handling of programs.
12698 It is easy to use, all one need to do is to run
'valgrind program
',
12699 and it will report any problems on stdout. It is even better if the
12700 program include debug information. With debug information, it is able
12701 to report the source file name and line number where the problem
12702 occurs. It can report things like
'reading past memory block in file
12703 X line N, the memory block was allocated in file Y, line M
', and
12704 'using uninitialised value in control logic
'. This tool has made it
12705 trivial to investigate reproducible crash bugs in programs, and have
12706 reduced the number of this kind of bugs in free software a lot.
12708 <p
>The second one is
12709 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
12710 a source code checker. It is able to process the source of a program
12711 and find problems in the logic without running the program. It
12712 started out as the Stanford Checker and became well known when it was
12713 used to find bugs in the Linux kernel. It is now a commercial tool
12714 and the company behind it is running
12715 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
12716 free software community, where a lot of free software projects get
12717 their source checked for free. Several thousand defects have been
12718 found and fixed so far. It can find errors like
'lock L taken in file
12719 X line N is never released if exiting in line M
', or
'the code in file
12720 Y lines O to P can never be executed
'. The projects included in the
12721 community service project have managed to get rid of a lot of
12722 reliability problems thanks to Coverity.
</p
>
12724 <p
>I believe tools like this, that are able to automatically find
12725 errors in the source, are vital to improve the quality of software and
12726 make sure we can get rid of the crashing and failing software we are
12727 surrounded by today.
</p
>
12732 <title>No patch is not better than a useless patch
</title>
12733 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
12734 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
12735 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
12736 <description><p
>Julien Blache
12737 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
12738 patch is better than a useless patch
</a
>. I completely disagree, as a
12739 patch allow one to discuss a concrete and proposed solution, and also
12740 prove that the issue at hand is important enough for someone to spent
12741 time on fixing it. No patch do not provide any of these positive
12742 properties.
</p
>
12747 <title>Standardize on protocols and formats, not vendors and applications
</title>
12748 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
12749 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
12750 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
12751 <description><p
>Where I work at the University of Oslo, one decision stand out as a
12752 very good one to form a long lived computer infrastructure. It is the
12753 simple one, lost by many in todays computer industry: Standardize on
12754 open network protocols and open exchange/storage formats, not applications.
12755 Applications come and go, while protocols and files tend to stay, and
12756 thus one want to make it easy to change application and vendor, while
12757 avoiding conversion costs and locking users to a specific platform or
12758 application.
</p
>
12760 <p
>This approach make it possible to replace the client applications
12761 independently of the server applications. One can even allow users to
12762 use several different applications as long as they handle the selected
12763 protocol and format. In the normal case, only one client application
12764 is recommended and users only get help if they choose to use this
12765 application, but those that want to deviate from the easy path are not
12766 blocked from doing so.
</p
>
12768 <p
>It also allow us to replace the server side without forcing the
12769 users to replace their applications, and thus allow us to select the
12770 best server implementation at any moment, when scale and resouce
12771 requirements change.
</p
>
12773 <p
>I strongly recommend standardizing - on open network protocols and
12774 open formats, but I would never recommend standardizing on a single
12775 application that do not use open network protocol or open formats.
</p
>
12780 <title>Returning from Skolelinux developer gathering
</title>
12781 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
12782 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
12783 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
12784 <description><p
>I
'm sitting on the train going home from this weekends Debian
12785 Edu/Skolelinux development gathering. I got a bit done tuning the
12786 desktop, and looked into the dynamic service location protocol
12787 implementation avahi. It look like it could be useful for us. Almost
12788 30 people participated, and I believe it was a great environment to
12789 get to know the Skolelinux system. Walter Bender, involved in the
12790 development of the Sugar educational platform, presented his stuff and
12791 also helped me improve my OLPC installation. He also showed me that
12792 his Turtle Art application can be used in standalone mode, and we
12793 agreed that I would help getting it packaged for Debian. As a
12794 standalone application it would be great for Debian Edu. We also
12795 tried to get the video conferencing working with two OLPCs, but that
12796 proved to be too hard for us. The application seem to need more work
12797 before it is ready for me. I look forward to getting home and relax
12803 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
12804 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
12805 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
12806 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
12807 <description><p
>The state of standardized LDAP schemas on Linux is far from
12808 optimal. There is RFC
2307 documenting one way to store NIS maps in
12809 LDAP, and a modified version of this normally called RFC
2307bis, with
12810 some modifications to be compatible with Active Directory. The RFC
12811 specification handle the content of a lot of system databases, but do
12812 not handle DNS zones and DHCP configuration.
</p
>
12814 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
12815 we would like to store information about users, SMB clients/hosts,
12816 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
12817 and LTSP configuration in LDAP. These objects have a lot in common,
12818 but with the current LDAP schemas it is not possible to have one
12819 object per entity. For example, one need to have at least three LDAP
12820 objects for a given computer, one with the SMB related stuff, one with
12821 DNS information and another with DHCP information. The schemas
12822 provided for DNS and DHCP are impossible to combine into one LDAP
12823 object. In addition, it is impossible to implement quick queries for
12824 netgroup membership, because of the way NIS triples are implemented.
12825 It just do not scale. I believe it is time for a few RFC
12826 specifications to cleam up this mess.
</p
>
12828 <p
>I would like to have one LDAP object representing each computer in
12829 the network, and this object can then keep the SMB (ie host key), DHCP
12830 (mac address/name) and DNS (name/IP address) settings in one place.
12831 It need to be efficently stored to make sure it scale well.
</p
>
12833 <p
>I would also like to have a quick way to map from a user or
12834 computer and to the net group this user or computer is a member.
</p
>
12836 <p
>Active Directory have done a better job than unix heads like myself
12837 in this regard, and the unix side need to catch up. Time to start a
12838 new IETF work group?
</p
>
12843 <title>Endelig er Debian Lenny gitt ut
</title>
12844 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
12845 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
12846 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
12847 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
12848 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
12849 Et langt steg videre for Debian-prosjektet, og en rekke nye
12850 programpakker blir nå tilgjengelig for de av oss som bruker den
12851 stabile utgaven av Debian. Neste steg er nå å få
12852 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
12853 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
12854 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
12855 slippes løs på skolene. Takk til alle debian-utviklerne som har
12856 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
12857 bootsekvens tilgjengelig i stabil utgave, vha pakken
12858 <tt
>insserv
</tt
>.
</p
>
12863 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
12864 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
12865 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
12866 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
12867 <description><p
>This weekend we had a small developer gathering for Debian Edu in
12868 Oslo. Most of Saturday was used for the general assemly for the
12869 member organization, but the rest of the weekend I used to tune the
12870 LTSP installation. LTSP now work out of the box on the
10-network.
12871 Acer Aspire One proved to be a very nice thin client, with both
12872 screen, mouse and keybard in a small box. Was working on getting the
12873 diskless workstation setup configured out of the box, but did not
12874 finish it before the weekend was up.
</p
>
12876 <p
>Did not find time to look at the
4 VGA cards in one box we got from
12877 the Brazilian group, so that will have to wait for the next
12878 development gathering. Would love to have the Debian Edu installer
12879 automatically detect and configure a multiseat setup when it find one
12880 of these cards.
</p
>
12885 <title>The sorry state of multimedia browser plugins in Debian
</title>
12886 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
12887 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
12888 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
12889 <description><p
>Recently I have spent some time evaluating the multimedia browser
12890 plugins available in Debian Lenny, to see which one we should use by
12891 default in Debian Edu. We need an embedded video playing plugin with
12892 control buttons to pause or stop the video, and capable of streaming
12893 all the multimedia content available on the web. The test results and
12894 notes are available on
12895 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
12896 Debian wiki
</a
>. I was surprised how few of the plugins are able to
12897 fill this need. My personal video player favorite, VLC, has a really
12898 bad plugin which fail on a lot of the test pages. A lot of the MIME
12899 types I would expect to work with any free software player (like
12900 video/ogg), just do not work. And simple formats like the
12901 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
12902 totem and vlc plugins. I hope the situation will improve soon. No
12903 wonder sites use the proprietary Adobe flash to play video.
</p
>
12905 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
12906 be the only one fitting our needs. :/
</p
>