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>rtlsdr-scanner, software defined radio frequency scanner for Linux - nice free software
</title>
11 <link>https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</link>
12 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/rtlsdr_scanner__software_defined_radio_frequency_scanner_for_Linux____nice_free_software.html
</guid>
13 <pubDate>Tue,
7 Mar
2023 23:
10:
00 +
0100</pubDate>
14 <description><p
>Today I finally found time to track down a useful radio frequency
15 scanner for my software defined radio. Just for fun I tried to locate
16 the radios used in the areas, and a good start would be to scan all
17 the frequencies to see what is in use. I
've tried to find a useful
18 program earlier, but ran out of time before I managed to find a useful
19 tool. This time I was more successful, and after a few false leads I
20 found a description of
21 <a href=
"https://www.kali.org/tools/rtlsdr-scanner/
">rtlsdr-scanner
22 over at the Kali site
</a
>, and was able to track down
23 <a href=
"https://gitlab.com/kalilinux/packages/rtlsdr-scanner.git
">the
24 Kali package git repository
</a
> to build a deb package for the
25 scanner. Sadly the package is missing from the Debian project itself,
26 at least in Debian Bullseye. Two runtime dependencies,
27 <a href=
"https://gitlab.com/kalilinux/packages/python-visvis.git
">python-visvis
</a
>
29 <a href=
"https://gitlab.com/kalilinux/packages/python-rtlsdr.git
">python-rtlsdr
</a
>
30 had to be built and installed separately. Luckily
'<tt
>gbp
31 buildpackage
</tt
>' handled them just fine and no further packages had
32 to be manually built. The end result worked out of the box after
33 installation.
</p
>
35 <p
>My initial scans for FM channels worked just fine, so I knew the
36 scanner was functioning. But when I tried to scan every frequency
37 from
100 to
1000 MHz, the program stopped unexpectedly near the
38 completion. After some debugging I discovered USB software radio I
39 used rejected frequencies above
948 MHz, triggering a unreported
40 exception breaking the scan. Changing the scan to end at
957 worked
41 better. I similarly found the lower limit to be around
15, and ended
42 up with the following full scan:
</p
>
44 <p
><a href=
"https://people.skolelinux.org/pere/blog/images/
2023-
04-
07-radio-freq-scanning.png
"><img src=
"https://people.skolelinux.org/pere/blog/images/
2023-
04-
07-radio-freq-scanning.png
" width=
"100%
"></a
></p
>
46 <p
>Saving the scan did not work, but exporting it as a CSV file worked
47 just fine. I ended up with around
477k CVS lines with dB level for
48 the given frequency.
</p
>
50 <p
>The save failure seem to be a missing UTF-
8 encoding issue in the
51 python code. Will see if I can find time to send a patch
52 <a href=
"https://github.com/CdeMills/RTLSDR-Scanner/
">upstream
</a
>
53 later to fix this exception:
</p
>
56 Traceback (most recent call last):
57 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
58 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
59 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
60 handle.write(json.dumps(data, indent=
4))
61 TypeError: a bytes-like object is required, not
'str
'
62 Traceback (most recent call last):
63 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/main_window.py
", line
485, in __on_save
64 save_plot(fullName, self.scanInfo, self.spectrum, self.locations)
65 File
"/usr/lib/python3/dist-packages/rtlsdr_scanner/file.py
", line
408, in save_plot
66 handle.write(json.dumps(data, indent=
4))
67 TypeError: a bytes-like object is required, not
'str
'
70 <p
>As usual, if you use Bitcoin and want to show your support of my
71 activities, please send Bitcoin donations to my address
72 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
77 <title>OpenSnitch available in Debian Sid and Bookworm
</title>
78 <link>https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</link>
79 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenSnitch_available_in_Debian_Sid_and_Bookworm.html
</guid>
80 <pubDate>Sat,
25 Feb
2023 20:
30:
00 +
0100</pubDate>
81 <description><p
>Thanks to the efforts of the OpenSnitch lead developer Gustavo
82 Iñiguez Goya allowing me to sponsor the upload,
83 <a href=
"https://tracker.debian.org/pkg/opensnitch
">the interactive
84 application firewall OpenSnitch
</a
> is now available in Debian
85 Testing, soon to become the next stable release of Debian.
</p
>
87 <p
>This is a package which set up a network firewall on one or more
88 machines, which is controlled by a graphical user interface that will
89 ask the user if a program should be allowed to connect to the local
90 network or the Internet. If some background daemon is trying to dial
91 home, it can be blocked from doing so with a simple mouse click, or by
92 default simply by not doing anything when the GUI question dialog pop
93 up. A list of all programs discovered using the network is provided
94 in the GUI, giving the user an overview of how the machine(s) programs
95 use the network.
</p
>
97 <p
>OpenSnitch was uploaded for NEW processing about a month ago, and I
98 had little hope of it getting accepted and shaping up in time for the
99 package freeze, but the Debian ftpmasters proved to be amazingly quick
100 at checking out the package and it was accepted into the archive about
101 week after the first upload. It is now team maintained under the Go
102 language team umbrella. A few fixes to the default setup is only in
103 Sid, and should migrate to Testing/Bookworm in a week.
</p
>
105 <p
>During testing I ran into an
106 <a href=
"https://github.com/evilsocket/opensnitch/issues/
813">issue
107 with Minecraft server broadcasts disappearing
</a
>, which was quickly
108 resolved by the developer with a patch and a proposed configuration
109 change. I
've been told this was caused by the Debian packages default
110 use if /proc/ information to track down kernel status, instead of the
111 newer eBPF module that can be used. The reason is simply that
112 upstream and I have failed to find a way to build the eBPF modules for
113 OpenSnitch without a complete configured Linux kernel source tree,
114 which as far as we can tell is unavailable as a build dependency in
115 Debian. We tried unsuccessfully so far to use the kernel-headers
116 package. It would be great if someone could provide some clues how to
117 build eBPF modules on build daemons in Debian, possibly without the full
118 kernel source.
</p
>
120 <p
>As usual, if you use Bitcoin and want to show your support of my
121 activities, please send Bitcoin donations to my address
122 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
127 <title>Is the desktop recommending your program for opening its files?
</title>
128 <link>https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</link>
129 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Is_the_desktop_recommending_your_program_for_opening_its_files_.html
</guid>
130 <pubDate>Sun,
29 Jan
2023 11:
00:
00 +
0100</pubDate>
131 <description><p
>Linux desktop systems
132 <a href=
"https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
">have
133 standardized
</a
> how programs present themselves to the desktop
134 system. If a package include a .desktop file in
135 /usr/share/applications/, Gnome, KDE, LXDE, Xfce and the other desktop
136 environments will pick up the file and use its content to generate the
137 menu of available programs in the system. A lesser known fact is that
138 a package can also explain to the desktop system how to recognize the
139 files created by the program in question, and use it to open these
140 files on request, for example via a GUI file browser.
</p
>
142 <p
>A while back I ran into a package that did not tell the desktop
143 system how to recognize its files and was not used to open its files
144 in the file browser and fixed it. In the process I wrote a simple
145 debian/tests/ script to ensure the setup keep working. It might be
146 useful for other packages too, to ensure any future version of the
147 package keep handling its own files.
</p
>
149 <p
>For this to work the file format need a useful MIME type that can
150 be used to identify the format. If the file format do not yet have a
151 MIME type, it should define one and preferably also
152 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">register
153 it with IANA
</a
> to ensure the MIME type string is reserved.
</p
>
155 <p
>The script uses the
<tt
>xdg-mime
</tt
> program from xdg-utils to
156 query the database of standardized package information and ensure it
157 return sensible values. It also need the location of an example file
158 for xdg-mime to guess the format of.
</p
>
163 # Author: Petter Reinholdtsen
164 # License: GPL v2 or later at your choice.
166 # Validate the MIME setup, making sure motor types have
167 # application/vnd.openmotor+yaml associated with them and is connected
168 # to the openmotor desktop file.
172 mimetype=
"application/vnd.openmotor+yaml
"
173 testfile=
"test/data/real/o3100/motor.ric
"
174 mydesktopfile=
"openmotor.desktop
"
176 filemime=
"$(xdg-mime query filetype
"$testfile
")
"
178 if [
"$mimetype
" !=
"$filemime
" ] ; then
180 echo
"error: xdg-mime claim motor file MIME type is $filemine, not $mimetype
"
182 echo
"success: xdg-mime report correct mime type $mimetype for motor file
"
185 desktop=$(xdg-mime query default
"$mimetype
")
187 if [
"$mydesktopfile
" !=
"$desktop
" ]; then
189 echo
"error: xdg-mime claim motor file should be handled by $desktop, not $mydesktopfile
"
191 echo
"success: xdg-mime agree motor file should be handled by $mydesktopfile
"
197 <p
>It is a simple way to ensure your users are not very surprised when
198 they try to open one of your file formats in their file browser.
</p
>
200 <p
>As usual, if you use Bitcoin and want to show your support of my
201 activities, please send Bitcoin donations to my address
202 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
207 <title>Opensnitch, the application level interactive firewall, heading into the Debian archive
</title>
208 <link>https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</link>
209 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Opensnitch__the_application_level_interactive_firewall__heading_into_the_Debian_archive.html
</guid>
210 <pubDate>Sun,
22 Jan
2023 23:
55:
00 +
0100</pubDate>
211 <description><p
>While reading a
212 <a href=
"https://sneak.berlin/
20230115/macos-scans-your-local-files-now/
">blog
213 post claiming MacOS X recently started scanning local files and
214 reporting information about them to Apple
</a
>, even on a machine where
215 all such callback features had been disabled, I came across a
216 description of the Little Snitch application for MacOS X. It seemed
217 like a very nice tool to have in the tool box, and I decided to see if
218 something similar was available for Linux.
</p
>
220 <p
>It did not take long to find
221 <a href=
"https://github.com/evilsocket/opensnitch
">the OpenSnitch
222 package
</a
>, which has been in development since
2017, and now is in
223 version
1.5.0. It has had a
224 <a href=
"https://bugs.debian.org/
909567">request for Debian
225 packaging
</a
> since
2018, but no-one completed the job so far. Just
226 for fun, I decided to see if I could help, and I was very happy to
228 <a href=
"https://github.com/evilsocket/opensnitch/issues/
304">upstream
229 want a Debian package too
</a
>.
</p
>
231 <p
>After struggling a bit with getting the program to run, figuring
232 out building Go programs (and a little failed detour to look at eBPF
233 builds too - help needed), I am very happy to report that I am
234 sponsoring upstream to maintain the package in Debian, and it has
235 since this morning been waiting in NEW for the ftpmasters to have a
236 look. Perhaps it can get into the archive in time for the Bookworm
239 <p
>As usual, if you use Bitcoin and want to show your support of my
240 activities, please send Bitcoin donations to my address
241 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
246 <title>LinuxCNC MQTT publisher component
</title>
247 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</link>
248 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_MQTT_publisher_component.html
</guid>
249 <pubDate>Sun,
8 Jan
2023 19:
30:
00 +
0100</pubDate>
250 <description><p
>I watched
<a href=
"https://yewtu.be/watch?v=jmKUV3aNLjk
">a
2015
251 video from Andreas Schiffler
</a
> the other day, where he set up
252 <a href=
"https://linuxcnc.org/
">LinuxCNC
</a
> to send status
253 information to the MQTT broker IBM Bluemix. As I also use MQTT for
254 graphing, it occured to me that a generic MQTT LinuxCNC component
255 would be useful and I set out to implement it. Today I got the first
256 draft limping along and submitted as
257 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
2253">a patch to the
258 LinuxCNC project
</a
>.
</p
>
260 <p
>The simple part was setting up the MQTT publishing code in Python.
261 I already have set up other parts submitting data to my Mosquito MQTT
262 broker, so I could reuse that code. Writing a LinuxCNC component in
263 Python as new to me, but using existing examples in the code
264 repository and the extensive documentation, this was fairly straight
265 forward. The hardest part was creating a automated test for the
266 component to ensure it was working. Testing it in a simulated
267 LinuxCNC machine proved very useful, as I discovered features I needed
268 that I had not thought of yet, and adjusted the code quite a bit to
269 make it easier to test without a operational MQTT broker
272 <p
>The draft is ready and working, but I am unsure which LinuxCNC HAL
273 pins I should collect and publish by default (in other words, the
274 default set of information pieces published), and how to get the
275 machine name from the LinuxCNC INI file. The latter is a minor
276 detail, but I expect it would be useful in a setup with several
277 machines available. I am hoping for feedback from the experienced
278 LinuxCNC developers and users, to make the component even better
279 before it can go into the mainland LinuxCNC code base.
</p
>
281 <p
>Since I started on the MQTT component, I came across
282 <a href=
"https://yewtu.be/watch?v=Bqa2grG0XtA
">another video from Kent
283 VanderVelden
</a
> where he combine LinuxCNC with a set of screen glasses
284 controlled by a Raspberry Pi, and it occured to me that it would
285 be useful for such use cases if LinuxCNC also provided a REST API for
286 querying its status. I hope to start on such component once the MQTT
287 component is working well.
</p
>
289 <p
>As usual, if you use Bitcoin and want to show your support of my
290 activities, please send Bitcoin donations to my address
291 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
296 <title>ONVIF IP camera management tool finally in Debian
</title>
297 <link>https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</link>
298 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/ONVIF_IP_camera_management_tool_finally_in_Debian.html
</guid>
299 <pubDate>Sat,
24 Dec
2022 08:
00:
00 +
0100</pubDate>
300 <description><p
>Merry Christmas to you all. Here is a small gift to all those with
301 IP cameras following the
<a href=
"https://www.onvif.org/
">ONVIF
302 specification
</a
>. There is finally a nice command line and GUI tool
303 in Debian to manage ONVIF IP cameras. After working with upstream for
304 a few months and sponsoring the upload, I am very happy to report that
305 the
<a href=
"https://tracker.debian.org/libonvif
">libonvif package
</a
>
306 entered Debian Sid last night.
</p
>
308 <p
>The package provide a C library to communicate with such cameras, a
309 command line tool to locate and update settings of (like password) the
310 cameras and a GUI tool to configure and control the units as well as
311 preview the video from the camera. Libonvif is available on Both
312 Linux and Windows and the GUI tool uses the Qt library. The main
313 competitors are non-free software, while libonvif is GNU GPL licensed.
314 I am very glad Debian users in the future can control their cameras
315 using a free software system provided by Debian. But the ONVIF world
316 is full of slightly broken firmware, where the cameras pretend to
317 follow the ONVIF specification but fail to set some configuration
318 values or refuse to provide video to more than one recipient at the
319 time, and the onvif project is quite young and might take a while
320 before it completely work with your camera. Upstream seem eager to
321 improve the library, so handling any broken camera might be just
<a
322 href=
"https://github.com/sr99622/libonvif/
">a bug report away
</a
>.
</p
>
324 <p
>The package just cleared NEW, and need a new source only upload
325 before it can enter testing. This will happen in the next few
328 <p
>As usual, if you use Bitcoin and want to show your support of my
329 activities, please send Bitcoin donations to my address
330 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
335 <title>Managing and using ONVIF IP cameras with Linux
</title>
336 <link>https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</link>
337 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Managing_and_using_ONVIF_IP_cameras_with_Linux.html
</guid>
338 <pubDate>Wed,
19 Oct
2022 12:
30:
00 +
0200</pubDate>
339 <description><p
>Recently I have been looking at how to control and collect data
340 from a handful IP cameras using Linux. I both wanted to change their
341 settings and to make their imagery available via a free software
342 service under my control. Here is a summary of the tools I found.
</p
>
344 <p
>First I had to identify the cameras and their protocols. As far as
345 I could tell, they were using some SOAP looking protocol and their
346 internal web server seem to only work with Microsoft Internet Explorer
347 with some proprietary binary plugin, which in these days of course is
348 a security disaster and also made it impossible for me to use the
349 camera web interface. Luckily I discovered that the SOAP looking
350 protocol is actually following
<a href=
"https://www.onvif.org/
">the
351 ONVIF specification
</a
>, which seem to be supported by a lot of IP
352 cameras these days.
</p
>
354 <p
>Once the protocol was identified, I was able to find what appear to
355 be the most popular way to configure ONVIF cameras, the free software
357 <a href=
"https://sourceforge.net/projects/onvifdm/
">ONVIF Device
358 Manager
</a
>. Lacking any other options at the time, I tried
359 unsuccessfully to get it running using Wine, but was missing a dotnet
360 40 library and I found no way around it to run it on Linux.
</p
>
362 <p
>The next tool I found to configure the cameras were a non-free Linux Qt
363 client
<a href=
"https://www.lingodigit.com/onvif_nvcdemo.html
">ONVIF
364 Device Tool
</a
>. I did not like its terms of use, so did not spend
365 much time on it.
</p
>
367 <p
>To collect the video and make it available in a web interface, I
368 found the Zoneminder tool in Debian. A recent version was able to
369 automatically detect and configure ONVIF devices, so I could use it to
370 set up motion detection in and collection of the camera output. I had
371 initial problems getting the ONVIF autodetection to work, as both
372 Firefox and Chromium
<a href=
"https://bugs.debian.org/
1001188">refused
373 the inter-tab communication
</a
> being used by the Zoneminder web
374 pages, but managed to get konqueror to work. Apparently the
"Enhanced
375 Tracking Protection
" in Firefox cause the problem. I ended up
376 upgrading to the Bookworm edition of Zoneminder in the process to try
377 to fix the issue, and believe the problem might be solved now.
</p
>
379 <p
>In the process I came across the nice Linux GUI tool
380 <a href=
"https://gitlab.com/caspermeijn/onvifviewer/
">ONVIF Viewer
</a
>
381 allowing me to preview the camera output and validate the login
382 passwords required. Sadly its author has grown tired of maintaining
383 the software, so it might not see any future updates. Which is sad,
384 as the viewer is sightly unstable and the picture tend to lock up.
385 Note, this lockup might be due to limitations in the cameras and not
386 the viewer implementation. I suspect the camera is only able to
387 provide pictures to one client at the time, and the Zoneminder feed
388 might interfere with the GUI viewer. I have
389 <a href=
"https://bugs.debian.org/
1000820">asked for the tool to be
390 included in Debian
</a
>.
</p
>
392 <p
>Finally, I found what appear to be very nice Linux free software
393 replacement for the Windows tool, named
394 <a href=
"https://github.com/sr99622/libonvif/
">libonvif
</a
>. It
395 provide a C library to talk to ONVIF devices as well as a command line
396 and GUI tool using the library. Using the GUI tool I was able to change
397 the admin passwords and update other settings of the cameras. I have
398 <a href=
"https://bugs.debian.org/
1021980">asked for the package to be
399 included in Debian
</a
>.
</p
>
401 <p
>As usual, if you use Bitcoin and want to show your support of my
402 activities, please send Bitcoin donations to my address
403 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
405 <p
><strong
>Update
2022-
10-
20</strong
>: Since my initial publication of
406 this text, I got several suggestions for more free software Linux
407 tools. There is
<a href=
"https://github.com/quatanium/python-onvif
">a
408 ONVIF python library
</a
> (already
409 <a href=
"https://bugs.debian.org/
824240">requested into Debian
</a
>) and
410 <a href=
"https://github.com/FalkTannhaeuser/python-onvif-zeep
">a python
3
411 fork
</a
> using a different SOAP dependency. There is also
412 <a href=
"https://www.home-assistant.io/integrations/onvif/
">support for
413 ONVIF in Home Assistant
</a
>, and there is an alternative to Zoneminder
414 called
<a href=
"https://www.shinobi.video/
">Shinobi
</a
>. The latter
415 two are not included in Debian either. I have not tested any of these
421 <title>Time to translate the Bullseye edition of the Debian Administrator
's Handbook
</title>
422 <link>https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</link>
423 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_to_translate_the_Bullseye_edition_of_the_Debian_Administrator_s_Handbook.html
</guid>
424 <pubDate>Mon,
12 Sep
2022 15:
45:
00 +
0200</pubDate>
425 <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
>
427 <p
>(The picture is of the previous edition.)
</p
>
429 <p
>Almost two years after the previous Norwegian Bokmål translation of
430 the
"<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
431 Handbook
</a
>" was published, a new edition is finally being prepared. The
432 english text is updated, and it is time to start working on the
433 translations. Around
37 percent of the strings have been updated, one
434 way or another, and the translations starting from a complete Debian Buster
435 edition now need to bring their translation up from
63% to
100%. The
436 complete book is licensed using a Creative Commons license, and has
437 been published in several languages over the years. The translations
438 are done by volunteers to bring Linux in their native tongue. The
439 last time I checked, it complete text was available in English,
440 Norwegian Bokmål, German, Indonesian, Brazil Portuguese and Spanish.
441 In addition, work has been started for Arabic (Morocco), Catalan,
442 Chinese (Simplified), Chinese (Traditional), Croatian, Czech, Danish,
443 Dutch, French, Greek, Italian, Japanese, Korean, Persian, Polish,
444 Romanian, Russian, Swedish, Turkish and Vietnamese.
</p
>
446 <p
>The translation is conducted on
447 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
448 hosted weblate project page
</a
>. Prospective translators are
449 recommeded to subscribe to
450 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
451 translators mailing list
</a
> and should also check out
452 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
453 contributors
</a
>.
</p
>
455 <p
>I am one of the Norwegian Bokmål translators of this book, and we
456 have just started. Your contribution is most welcome.
</p
>
458 <p
>As usual, if you use Bitcoin and want to show your support of my
459 activities, please send Bitcoin donations to my address
460 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
465 <title>Automatic LinuxCNC servo PID tuning?
</title>
466 <link>https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</link>
467 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_LinuxCNC_servo_PID_tuning_.html
</guid>
468 <pubDate>Sat,
16 Jul
2022 22:
30:
00 +
0200</pubDate>
469 <description><p
>While working on a CNC with servo motors controlled by the
470 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>
471 <a href=
"https://en.wikipedia.org/wiki/PID_controller
">PID
472 controller
</a
>, I recently had to learn how to tune the collection of values
473 that control such mathematical machinery that a PID controller is. It
474 proved to be a lot harder than I hoped, and I still have not succeeded
475 in getting the Z PID controller to successfully defy gravity, nor X
476 and Y to move accurately and reliably. But while climbing up this
477 rather steep learning curve, I discovered that some motor control
478 systems are able to tune their PID controllers. I got the impression
479 from the documentation that LinuxCNC were not. This proved to be not
482 <p
>The LinuxCNC
483 <a href=
"http://linuxcnc.org/docs/html/man/man9/pid
.9.html
">pid
484 component
</a
> is the recommended PID controller to use. It uses eight
485 constants
<tt
>Pgain
</tt
>,
<tt
>Igain
</tt
>,
<tt
>Dgain
</tt
>,
486 <tt
>bias
</tt
>,
<tt
>FF0
</tt
>,
<tt
>FF1
</tt
>,
<tt
>FF2
</tt
> and
487 <tt
>FF3
</tt
> to calculate the output value based on current and wanted
488 state, and all of these need to have a sensible value for the
489 controller to behave properly. Note, there are even more values
490 involved, theser are just the most important ones. In my case I need
491 the X, Y and Z axes to follow the requested path with little error.
492 This has proved quite a challenge for someone who have never tuned a
493 PID controller before, but there is at least some help to be found.
495 <p
>I discovered that included in LinuxCNC was this old PID component
496 at_pid claiming to have auto tuning capabilities. Sadly it had been
497 neglected since
2011, and could not be used as a plug in replacement
498 for the default pid component. One would have to rewriting the
499 LinuxCNC HAL setup to test at_pid. This was rather sad, when I wanted
500 to quickly test auto tuning to see if it did a better job than me at
501 figuring out good P, I and D values to use.
</p
>
503 <p
>I decided to have a look if the situation could be improved. This
504 involved trying to understand the code and history of the pid and
505 at_pid components. Apparently they had a common ancestor, as code
506 structure, comments and variable names were quite close to each other.
507 Sadly this was not reflected in the git history, making it hard to
508 figure out what really happened. My guess is that the author of
509 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/at_pid.c
">at_pid.c
</a
>
511 <a href=
"https://github.com/LinuxCNC/linuxcnc/blob/master/src/hal/components/pid.c
">pid.c
</a
>,
512 rewrote it to follow the structure he wished pid.c to have, then added
513 support for auto tuning and finally got it included into the LinuxCNC
514 repository. The restructuring and lack of early history made it
515 harder to figure out which part of the code were relevant to the auto
516 tuning, and which part of the code needed to be updated to work the
517 same way as the current pid.c implementation. I started by trying to
518 isolate relevant changes in pid.c, and applying them to at_pid.c. My
519 aim was to make sure the at_pid component could replace the pid
520 component with a simple change in the HAL setup loadrt line, without
521 having to
"rewire
" the rest of the HAL configuration. After a few
522 hours following this approach, I had learned quite a lot about the
523 code structure of both components, while concluding I was heading down
524 the wrong rabbit hole, and should get back to the surface and find a
525 different path.
</p
>
527 <p
>For the second attempt, I decided to throw away all the PID control
528 related part of the original at_pid.c, and instead isolate and lift
529 the auto tuning part of the code and inject it into a copy of pid.c.
530 This ensured compatibility with the current pid component, while
531 adding auto tuning as a run time option. To make it easier to identify
532 the relevant parts in the future, I wrapped all the auto tuning code
533 with
'#ifdef AUTO_TUNER
'. The end result behave just like the current
534 pid component by default, as that part of the code is identical. The
535 <a href=
"https://github.com/LinuxCNC/linuxcnc/pull/
1820">end result
536 entered the LinuxCNC master branch
</a
> a few days ago.
</p
>
538 <p
>To enable auto tuning, one need to set a few HAL pins in the PID
539 component. The most important ones are
<tt
>tune-effort
</tt
>,
540 <tt
>tune-mode
</tt
> and
<tt
>tune-start
</tt
>. But lets take a step
541 back, and see what the auto tuning code will do. I do not know the
542 mathematical foundation of the at_pid algorithm, but from observation
543 I can tell that the algorithm will, when enabled, produce a square
544 wave pattern centered around the
<tt
>bias
</tt
> value on the output pin
545 of the PID controller. This can be seen using the HAL Scope provided
546 by LinuxCNC. In my case, this is translated into voltage (+-
10V) sent
547 to the motor controller, which in turn is translated into motor speed.
548 So at_pid will ask the motor to move the axis back and forth. The
549 number of cycles in the pattern is controlled by the
550 <tt
>tune-cycles
</tt
> pin, and the extremes of the wave pattern is
551 controlled by the
<tt
>tune-effort
</tt
> pin. Of course, trying to
552 change the direction of a physical object instantly (as in going
553 directly from a positive voltage to the equivalent negative voltage)
554 do not change velocity instantly, and it take some time for the object
555 to slow down and move in the opposite direction. This result in a
556 more smooth movement wave form, as the axis in question were vibrating
557 back and forth. When the axis reached the target speed in the
558 opposing direction, the auto tuner change direction again. After
559 several of these changes, the average time delay between the
'peaks
'
560 and
'valleys
' of this movement graph is then used to calculate
561 proposed values for Pgain, Igain and Dgain, and insert them into the
562 HAL model to use by the pid controller. The auto tuned settings are
563 not great, but htye work a lot better than the values I had been able
564 to cook up on my own, at least for the horizontal X and Y axis. But I
565 had to use very small
<tt
>tune-effort
<tt
> values, as my motor
566 controllers error out if the voltage change too quickly. I
've been
567 less lucky with the Z axis, which is moving a heavy object up and
568 down, and seem to confuse the algorithm. The Z axis movement became a
569 lot better when I introduced a
<tt
>bias
</tt
> value to counter the
570 gravitational drag, but I will have to work a lot more on the Z axis
571 PID values.
</p
>
573 <p
>Armed with this knowledge, it is time to look at how to do the
574 tuning. Lets say the HAL configuration in question load the PID
575 component for X, Y and Z like this:
</p
>
577 <blockquote
><pre
>
578 loadrt pid names=pid.x,pid.y,pid.z
579 </pre
></blockquote
>
581 <p
>Armed with the new and improved at_pid component, the new line will
582 look like this:
</p
>
584 <blockquote
><pre
>
585 loadrt at_pid names=pid.x,pid.y,pid.z
586 </pre
></blockquote
>
588 <p
>The rest of the HAL setup can stay the same. This work because the
589 components are referenced by name. If the component had used count=
3
590 instead, all use of pid.# had to be changed to at_pid.#.
</p
>
592 <p
>To start tuning the X axis, move the axis to the middle of its
593 range, to make sure it do not hit anything when it start moving back
594 and forth. Next, set the
<tt
>tune-effort
</tt
> to a low number in the
595 output range. I used
0.1 as my initial value. Next, assign
1 to the
596 <tt
>tune-mode
</tt
> value. Note, this will disable the pid controlling
597 part and feed
0 to the output pin, which in my case initially caused a
598 lot of drift. In my case it proved to be a good idea with X and Y to
599 tune the motor driver to make sure
0 voltage stopped the motor
600 rotation. On the other hand, for the Z axis this proved to be a bad
601 idea, so it will depend on your setup. It might help to set the
602 <tt
>bias
</tt
> value to a output value that reduce or eliminate the
603 axis drift. Finally, after setting
<tt
>tune-mode
</tt
>, set
604 <tt
>tune-start
</tt
> to
1 to activate the auto tuning. If all go well,
605 your axis will vibrate for a few seconds and when it is done, new
606 values for Pgain, Igain and Dgain will be active. To test them,
607 change
<tt
>tune-mode
</tt
> back to
0. Note that this might cause the
608 machine to suddenly jerk as it bring the axis back to its commanded
609 position, which it might have drifted away from during tuning. To
610 summarize with some halcmd lines:
</p
>
612 <blockquote
><pre
>
613 setp pid.x.tune-effort
0.1
614 setp pid.x.tune-mode
1
615 setp pid.x.tune-start
1
616 # wait for the tuning to complete
617 setp pid.x.tune-mode
0
618 </pre
></blockquote
>
620 <p
>After doing this task quite a few times while trying to figure out
621 how to properly tune the PID controllers on the machine in, I decided
622 to figure out if this process could be automated, and wrote a script
623 to do the entire tuning process from power on. The end result will
624 ensure the machine is powered on and ready to run, home all axis if it
625 is not already done, check that the extra tuning pins are available,
626 move the axis to its mid point, run the auto tuning and re-enable the
627 pid controller when it is done. It can be run several times. Check
629 <a href=
"https://github.com/SebKuzminsky/MazakVQC1540/blob/bon-dev/scripts/run-auto-pid-tuner
">run-auto-pid-tuner
</a
>
630 script on github if you want to learn how it is done.
</p
>
632 <p
>My hope is that this little adventure can inspire someone who know
633 more about motor PID controller tuning can implement even better
634 algorithms for automatic PID tuning in LinuxCNC, making life easier
635 for both me and all the others that want to use LinuxCNC but lack the
636 in depth knowledge needed to tune PID controllers well.
</p
>
638 <p
>As usual, if you use Bitcoin and want to show your support of my
639 activities, please send Bitcoin donations to my address
640 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
645 <title>LinuxCNC translators life just got a bit easier
</title>
646 <link>https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</link>
647 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LinuxCNC_translators_life_just_got_a_bit_easier.html
</guid>
648 <pubDate>Fri,
3 Jun
2022 21:
10:
00 +
0200</pubDate>
649 <description><p
>Back in oktober last year, when I started looking at the
650 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
> system, I
651 proposed to change the documentation build system make life easier for
652 translators. The original system consisted of independently written
653 documentation files for each language, with no automated way to track
654 changes done in other translations and no help for the translators to
655 know how much was left to translated. By using
656 <a href=
"https://po4a.org/
">the po4a system
</a
> to generate POT and PO
657 files from the English documentation, this can be improved. A small
658 team of LinuxCNC contributors got together and today our labour
659 finally payed off. Since a few hours ago, it is now possible to
660 translate
<a href=
"https://hosted.weblate.org/projects/linuxcnc/
">the
661 LinuxCNC documentation on Weblate
</a
>, alongside the program itself.
</p
>
663 <p
>The effort to migrate the documentation to use po4a has been both
664 slow and frustrating. I am very happy we finally made it.
</p
>
666 <p
>As usual, if you use Bitcoin and want to show your support of my
667 activities, please send Bitcoin donations to my address
668 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
673 <title>geteltorito make CD firmware upgrades a breeze
</title>
674 <link>https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</link>
675 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/geteltorito_make_CD_firmware_upgrades_a_breeze.html
</guid>
676 <pubDate>Wed,
20 Apr
2022 11:
50:
00 +
0200</pubDate>
677 <description><p
>Recently I wanted to upgrade the firmware of my thinkpad, and
678 located the firmware download page from Lenovo (which annoyingly do
679 not allow access via Tor, forcing me to hand them more personal
680 information that I would like). The
681 <a href=
"https://support.lenovo.com/no/en/search?query=thinkpad firmware bios upgrade iso
&SearchType=Customer search
&searchLocation=Masthead
">download
682 from Lenovo
</a
> is a bootable ISO image, which is a bit of a problem
683 when all I got available is a USB memory stick. I tried booting the
684 ISO as a USB stick, but this did not work. But genisoimage came to
685 the rescue.
</p
>
687 <P
>The geteltorito program in
688 <a href=
"http://tracker.debian.org/cdrkit
">the genisoimage binary
689 package
</a
> is able to convert the bootable ISO image to a bootable
690 USB stick using a simple command line recipe, which I then can write
691 to the most recently inserted USB stick:
</p
>
693 <blockquote
><pre
>
694 geteltorito -o usbstick.img lenovo-firmware.iso
695 sudo dd bs=
10M if=usbstick.img of=$(ls -tr /dev/sd?|tail -
1)
696 </pre
></blockquote
>
698 <p
>This USB stick booted the firmware upgrader just fine, and in a few
699 minutes my machine had the latest and greatest BIOS firmware in place.
</p
>
704 <title>Run your industrial metal working machine using Debian?
</title>
705 <link>https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</link>
706 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Run_your_industrial_metal_working_machine_using_Debian_.html
</guid>
707 <pubDate>Wed,
2 Mar
2022 18:
40:
00 +
0100</pubDate>
708 <description><p
>After many months of hard work by the good people involved in
709 <a href=
"https://en.wikipedia.org/wiki/LinuxCNC
">LinuxCNC
</a
>, the
710 system was accepted Sunday
711 <a href=
"https://tracker.debian.org/pkg/linuxcnc
">into Debian
</a
>.
712 Once it was available from Debian, I was surprised to discover from
713 <a href=
"https://qa.debian.org/popcon.php?package=linuxcnc
">its
714 popularity-contest numbers
</a
> that people have been reporting its use
715 since
2012.
<a href=
"http://linuxcnc.org/
">Its project site
</a
> might
716 be a good place to check out, but sadly is not working when visiting
719 <p
>But what is LinuxCNC, you are probably wondering? Perhaps a
720 Wikipedia quote is in place?
</p
>
723 "LinuxCNC is a software system for numerical control of
724 machines such as milling machines, lathes, plasma cutters, routers,
725 cutting machines, robots and hexapods. It can control up to
9 axes or
726 joints of a CNC machine using G-code (RS-
274NGC) as input. It has
727 several GUIs suited to specific kinds of usage (touch screen,
728 interactive development).
"
731 <p
>It can even control
3D printers. And even though the Wikipedia
732 page indicate that it can only work with hard real time kernel
733 features, it can also work with the user space soft real time features
734 provided by the Debian kernel.
735 <a href=
"https://github.com/linuxcnc/linuxcnc
">The source code
</a
> is
736 available from Github. The last few months I
've been involved in the
737 translation setup for the program and documentation. Translators are
739 <a href=
"https://hosted.weblate.org/engage/linuxcnc/
">join the
740 effort
</a
> using Weblate.
</p
>
742 <p
>As usual, if you use Bitcoin and want to show your support of my
743 activities, please send Bitcoin donations to my address
744 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
749 <title>Debian still an excellent choice for Lego builders
</title>
750 <link>https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</link>
751 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_still_an_excellent_choice_for_Lego_builders.html
</guid>
752 <pubDate>Sun,
24 Oct
2021 07:
10:
00 +
0200</pubDate>
753 <description><p
>The Debian Lego team saw a lot of activity the last few weeks. All
754 the packages under the team umbrella has been updated to fix
755 packaging, lintian issues and BTS reports. In addition, a new and
756 inspiring team member appeared on both the
757 <a href=
"https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-lego-team
">debian-lego-team
758 Team mailing list
</a
> and
759 <a href=
"irc://irc.debian.org/%
23debian-lego
">IRC channel
760 #debian-lego
</a
>. If you are interested in Lego CAD design and LEGO
761 Mindstorms programming, check out the
762 <a href=
"http://wiki.debian.org/LegoDesigners
">team wiki page
</a
> to
763 see what Debian can offer the Lego enthusiast.
</p
>
765 <p
>Patches has been sent upstream, causing new upstream releases, one
766 even the first one in more than ten years, and old upstreams was
767 released with new ones. There are still a lot of work left, and the
768 team welcome more members to help us make sure Debian is the Linux
769 distribution of choice for Lego builders. If you want to contribute,
770 join us in the IRC channel and become part of
771 <a href=
"https://salsa.debian.org/debian-lego-team/
">the team on
772 Salsa
</a
>.
</p
>
774 <p
>As usual, if you use Bitcoin and want to show your support of my
775 activities, please send Bitcoin donations to my address
776 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
781 <title>Six complete translations of The Debian Administrator
's Handbook for Buster
</title>
782 <link>https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</link>
783 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Six_complete_translations_of_The_Debian_Administrator_s_Handbook_for_Buster.html
</guid>
784 <pubDate>Mon,
5 Jul
2021 19:
20:
00 +
0200</pubDate>
785 <description><p
>I am happy observe that the
<a href=
"https://debian-handbook.info/
">The
786 Debian Administrator
's Handbook
</a
> is available in six languages now.
787 I am not sure which one of these are completely proof read, but the
788 complete book is available in these languages:
792 <li
>English
</li
>
793 <li
>Norwegian Bokmål
</li
>
794 <li
>German
</li
>
795 <li
>Indonesian
</li
>
796 <li
>Brazil Portuguese
</li
>
797 <li
>Spanish
</li
>
801 <p
>This is the list of languages more than
70% complete, in other
802 words with not too much left to do:
</p
>
806 <li
>Chinese (Simplified) -
90%
</li
>
807 <li
>French -
79%
</li
>
808 <li
>Italian -
79%
</li
>
809 <li
>Japanese -
77%
</li
>
810 <li
>Arabic (Morocco) -
75%
</li
>
811 <li
>Persian -
71%
</li
>
815 <p
>I wonder how long it will take to bring these to
100%.
</p
>
817 <p
>Then there is the list of languages about halfway done:
</p
>
821 <li
>Russian -
63%
</li
>
822 <li
>Swedish -
53%
</li
>
823 <li
>Chinese (Traditional) -
46%
</li
>
824 <li
>Catalan -
45%
</li
>
828 <p
>Several are on to a good start:
</p
>
832 <li
>Dutch -
26%
</li
>
833 <li
>Vietnamese -
25%
</li
>
834 <li
>Polish -
23%
</li
>
835 <li
>Czech -
22%
</li
>
836 <li
>Turkish -
18%
</li
>
840 <p
>Finally, there are the ones just getting started:
</p
>
844 <li
>Korean -
4%
</li
>
845 <li
>Croatian -
2%
</li
>
846 <li
>Greek -
2%
</li
>
847 <li
>Danish -
1%
</li
>
848 <li
>Romanian -
1%
</li
>
852 <p
>If you want to help provide a Debian instruction book in your own
854 <a href=
"https://hosted.weblate.org/projects/debian-handbook/#languages
">Weblate
</a
>
855 to contribute to the translations.
</p
>
857 <p
>As usual, if you use Bitcoin and want to show your support of my
858 activities, please send Bitcoin donations to my address
859 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
864 <title>Latest Jami back in Debian Testing, and scriptable using dbus
</title>
865 <link>https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</link>
866 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Latest_Jami_back_in_Debian_Testing__and_scriptable_using_dbus.html
</guid>
867 <pubDate>Tue,
12 Jan
2021 17:
00:
00 +
0100</pubDate>
868 <description><p
>After a lot of hard work by its maintainer Alexandre Viau and
869 others, the decentralized communication platform
870 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>
871 (earlier known as Ring), managed to get
872 <a href=
"https://tracker.debian.org/pkg/ring
">its latest version
</a
>
873 into Debian Testing. Several of its dependencies has caused build and
874 propagation problems, which all seem to be solved now.
</p
>
876 <p
>In addition to the fact that Jami is decentralized, similar to how
877 bittorrent is decentralized, I first of all like how it is not
878 connected to external IDs like phone numbers. This allow me to set up
879 computers to send me notifications using Jami without having to find
880 get a phone number for each computer. Automatic notification via Jami
881 is also made trivial thanks to the provided client side API (as a DBus
882 service). Here is my bourne shell script demonstrating how to let any
883 system send a message to any Jami address. It will create a new
884 identity before sending the message, if no Jami identity exist
890 # Usage: $
0 <jami-address
> <message
>
892 # Send
<message
> to
<jami-address
>, create local jami account if
895 # License: GPL v2 or later at your choice
896 # Author: Petter Reinholdtsen
899 if [ -z
"$HOME
" ] ; then
900 echo
"error: missing \$HOME, required for dbus to work
"
904 # First, get dbus running if not already running
905 DBUSLAUNCH=/usr/bin/dbus-launch
906 PIDFILE=/run/asterisk/dbus-session.pid
907 if [ -e $PIDFILE ] ; then
909 if ! kill -
0 $DBUS_SESSION_BUS_PID
2>/dev/null ; then
910 unset DBUS_SESSION_BUS_ADDRESS
913 if [ -z
"$DBUS_SESSION_BUS_ADDRESS
" ]
&& [ -x
"$DBUSLAUNCH
" ]; then
914 DBUS_SESSION_BUS_ADDRESS=
"unix:path=$HOME/.dbus
"
915 dbus-daemon --session --address=
"$DBUS_SESSION_BUS_ADDRESS
" --nofork --nopidfile --syslog-only
< /dev/null
> /dev/null
2>&1 3>&1 &
916 DBUS_SESSION_BUS_PID=$!
918 echo DBUS_SESSION_BUS_PID=$DBUS_SESSION_BUS_PID
919 echo DBUS_SESSION_BUS_ADDRESS=\
""$DBUS_SESSION_BUS_ADDRESS
"\
"
920 echo export DBUS_SESSION_BUS_ADDRESS
926 part=
"$
1"; shift
927 op=
"$
1"; shift
928 dbus-send --session \
929 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
933 part=
"$
1"; shift
934 op=
"$
1"; shift
935 dbus-send --session --print-reply \
936 --dest=
"cx.ring.Ring
" /cx/ring/Ring/$part cx.ring.Ring.$part.$op $*
940 dringopreply ConfigurationManager getAccountList | \
941 grep string | awk -F
'"' '{print $
2}
' | head -n
1
944 account=$(firstaccount)
946 if [ -z
"$account
" ] ; then
947 echo
"Missing local account, trying to create it
"
948 dringop ConfigurationManager addAccount \
949 dict:string:string:
"Account.type
",
"RING
",
"Account.videoEnabled
",
"false
"
950 account=$(firstaccount)
951 if [ -z
"$account
" ] ; then
952 echo
"unable to create local account
"
957 # Not using dringopreply to ensure $
2 can contain spaces
958 dbus-send --print-reply --session \
959 --dest=cx.ring.Ring \
960 /cx/ring/Ring/ConfigurationManager \
961 cx.ring.Ring.ConfigurationManager.sendTextMessage \
962 string:
"$account
" string:
"$
1" \
963 dict:string:string:
"text/plain
",
"$
2"
964 </pre
></p
>
966 <p
>If you want to check it out yourself, visit the
967 <a href=
"https://jami.net/
">the Jami system project page
</a
> to learn
968 more, and install the latest Jami client from Debian Unstable or
971 <p
>As usual, if you use Bitcoin and want to show your support of my
972 activities, please send Bitcoin donations to my address
973 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
978 <title>Buster based Bokmål edition of Debian Administrator
's Handbook
</title>
979 <link>https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
980 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Buster_based_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
981 <pubDate>Tue,
20 Oct
2020 18:
35:
00 +
0200</pubDate>
982 <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
>
984 <p
>I am happy to report that we finally made it! Norwegian Bokmål
985 became the first translation published on paper of the new Buster
986 based edition of
"<a href=
"https://debian-handbook.info/
">The Debian
987 Administrator
's Handbook
</a
>". The print proof reading copy arrived
988 some days ago, and it looked good, so now the book is approved for
989 general distribution. This updated paperback edition
<a
990 href=
"https://debian-handbook.info/get/#norwegian
">is available from
991 lulu.com
</a
>. The book is also available for download in electronic
992 form as PDF, EPUB and Mobipocket, and can also be
993 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
</a
>.
</p
>
995 <p
>I am very happy to wrap up this Creative Common licensed project,
996 which concludes several months of work by several volunteers. The
997 number of Linux related books published in Norwegian are few, and I
998 really hope this one will gain many readers, as it is packed with deep
999 knowledge on Linux and the Debian ecosystem. The book will be
1000 available for various Internet book stores like Amazon and Barnes
&
1001 Noble soon, but I recommend buying
1002 "<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
1003 for Debian-administratoren
</a
>" directly from the source at Lulu.
1005 <p
>As usual, if you use Bitcoin and want to show your support of my
1006 activities, please send Bitcoin donations to my address
1007 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1012 <title>Buster update of Norwegian Bokmål edition of Debian Administrator
's Handbook almost done
</title>
1013 <link>https://people.skolelinux.org/pere/blog/Buster_update_of_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_almost_done.html
</link>
1014 <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>
1015 <pubDate>Fri,
11 Sep
2020 09:
45:
00 +
0200</pubDate>
1016 <description><p
>Thanks to the good work of several volunteers, the updated edition
1017 of the Norwegian translation for
1018 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1019 Handbook
</a
>" is now almost completed. After many months of proof
1020 reading, I consider the proof reading complete enough for us to move
1021 to the next step, and have asked for the print version to be prepared
1022 and sent of to the print on demand service lulu.com. While it is
1023 still not to late if you find any incorrect translations on
1024 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
1025 hosted Weblate service
</a
>, but it will be soon. :) You can check out
1026 <a href=
" https://debian-handbook.info/browse/nb-NO/stable/
">the Buster
1027 edition on the web
</a
> until the print edition is ready.
</p
>
1029 <p
>The book will be for sale on lulu.com and various web book stores,
1030 with links available from the web site for the book linked to above.
1031 I hope a lot of readers find it useful.
</p
>
1033 <p
>As usual, if you use Bitcoin and want to show your support of my
1034 activities, please send Bitcoin donations to my address
1035 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1040 <title>Working on updated Norwegian Bokmål edition of Debian Administrator
's Handbook
</title>
1041 <link>https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</link>
1042 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Working_on_updated_Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook.html
</guid>
1043 <pubDate>Sat,
4 Jul
2020 23:
55:
00 +
0200</pubDate>
1044 <description><p
>Three years ago, the first Norwegian Bokmål edition of
1045 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
1046 Handbook
</a
>" was published. This was based on Debian Jessie. Now a
1047 new and updated version based on Buster is getting ready. Work on the
1048 updated Norwegian Bokmål edition has been going on for a few months
1049 now, and yesterday, we reached the first mile stone, with
100% of the
1050 texts being translated. A lot of proof reading remains, of course,
1051 but a major step towards a new edition has been taken.
</p
>
1053 <p
>The book is translated by volunteers, and we would love to get some
1054 help with the proof reading. The translation uses
1055 <a href=
"https://hosted.weblate.org/languages/nb_NO/debian-handbook/
">the
1056 hosted Weblate service
</a
>, and we welcome everyone to have a look and
1057 submit improvements and suggestions. There is also a proof readers
1058 PDF available on request, get in touch if you want to help out that
1061 <p
>As usual, if you use Bitcoin and want to show your support of my
1062 activities, please send Bitcoin donations to my address
1063 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1068 <title>Secure Socket API - a simple and powerful approach for TLS support in software
</title>
1069 <link>https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</link>
1070 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Secure_Socket_API___a_simple_and_powerful_approach_for_TLS_support_in_software.html
</guid>
1071 <pubDate>Sat,
6 Jun
2020 12:
40:
00 +
0200</pubDate>
1072 <description><p
>As a member of the
<a href=
"https://www.nuug.no/
">Norwegian Unix
1073 User Group
</a
>, I have the pleasure of receiving the
1074 <a href=
"https://www.usenix.org/
">USENIX
</a
> magazine
1075 <a href=
"https://www.usenix.org/publications/login/
">;login:
</a
>
1076 several times a year. I rarely have time to read all the articles,
1077 but try to at least skim through them all as there is a lot of nice
1078 knowledge passed on there. I even carry the latest issue with me most
1079 of the time to try to get through all the articles when I have a few
1080 spare minutes.
</p
>
1082 <p
>The other day I came across a nice article titled
1083 "<a href=
"https://www.usenix.org/publications/login/winter2018/oneill
">The
1084 Secure Socket API: TLS as an Operating System Service
</a
>" with a
1085 marvellous idea I hope can make it all the way into the POSIX standard.
1086 The idea is as simple as it is powerful. By introducing a new
1087 socket() option IPPROTO_TLS to use TLS, and a system wide service to
1088 handle setting up TLS connections, one both make it trivial to add TLS
1089 support to any program currently using the POSIX socket API, and gain
1090 system wide control over certificates, TLS versions and encryption
1091 systems used. Instead of doing this:
</p
>
1093 <p
><blockquote
><pre
>
1094 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TCP);
1095 </pre
></blockquote
></p
>
1097 <p
>the program code would be doing this:
<p
>
1099 <p
><blockquote
><pre
>
1100 int socket = socket(PF_INET, SOCK_STREAM, IPPROTO_TLS);
1101 </pre
></blockquote
></p
>
1103 <p
>According to the ;login: article, converting a C program to use TLS
1104 would normally modify only
5-
10 lines in the code, which is amazing
1105 when compared to using for example the OpenSSL API.
</p
>
1107 <p
>The project has set up the
1108 <a href=
"https://securesocketapi.org/
">https://securesocketapi.org/
</a
>
1109 web site to spread the idea, and the code for a kernel module and the
1110 associated system daemon is available from two github repositories:
1111 <a href=
"https://github.com/markoneill/ssa
">ssa
</a
> and
1112 <a href=
"https://github.com/markoneill/ssa-daemon
">ssa-daemon
</a
>.
1113 Unfortunately there is no explicit license information with the code,
1114 so its copyright status is unclear. A
1115 <a href=
"https://github.com/markoneill/ssa/issues/
2">request to solve
1116 this
</a
> about it has been unsolved since
2018-
08-
17.
</p
>
1118 <p
>I love the idea of extending socket() to gain TLS support, and
1119 understand why it is an advantage to implement this as a kernel module
1120 and system wide service daemon, but can not help to think that it
1121 would be a lot easier to get projects to move to this way of setting
1122 up TLS if it was done with a user space approach where programs
1123 wanting to use this API approach could just link with a wrapper
1126 <p
>I recommend you check out this simple and powerful approach to more
1127 secure network connections. :)
</p
>
1129 <p
>As usual, if you use Bitcoin and want to show your support of my
1130 activities, please send Bitcoin donations to my address
1131 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1136 <title>Jami as a Zoom client, a trick for password protected rooms...
</title>
1137 <link>https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</link>
1138 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_as_a_Zoom_client__a_trick_for_password_protected_rooms___.html
</guid>
1139 <pubDate>Fri,
8 May
2020 13:
30:
00 +
0200</pubDate>
1140 <description><p
>Half a year ago,
1141 <a href=
"http://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
">I
1142 wrote
</a
> about
<a href=
"https://jami.net/
">the Jami communication
1143 client
</a
>, capable of peer-to-peer encrypted communication. It
1144 handle both messages, audio and video. It uses distributed hash
1145 tables instead of central infrastructure to connect its users to each
1146 other, which in my book is a plus. I mentioned briefly that it could
1147 also work as a SIP client, which came in handy when the higher
1148 educational sector in Norway started to promote Zoom as its video
1149 conferencing solution. I am reluctant to use the official Zoom client
1150 software, due to their
<a href=
"https://zoom.us/terms
">copyright
1151 license clauses
</a
> prohibiting users to reverse engineer (for example
1152 to check the security) and benchmark it, and thus prefer to connect to
1153 Zoom meetings with free software clients.
</p
>
1155 <p
>Jami worked OK as a SIP client to Zoom as long as there was no
1156 password set on the room. The Jami daemon leak memory like crazy
1157 (approximately
1 GiB a minute) when I am connected to the video
1158 conference, so I had to restart the client every
7-
10 minutes, which
1159 is not great. I tried to get other SIP Linux clients to work
1160 without success, so I decided I would have to live with this wart
1161 until someone managed to fix the leak in the dring code base. But
1162 another problem showed up once the rooms were password protected. I
1163 could not get my dial tone signaling through from Jami to Zoom, and
1164 dial tone signaling is used to enter the password when connecting to
1165 Zoom. I tried a lot of different permutations with my Jami and
1166 Asterisk setup to try to figure out why the signaling did not get
1167 through, only to finally discover that the fundamental problem seem to
1168 be that Zoom is simply not able to receive dial tone signaling when
1169 connecting via SIP. There seem to be nothing wrong with the Jami and
1170 Asterisk end, it is simply broken in the Zoom end. I got help from a
1171 very skilled VoIP engineer figuring out this last part. And being a
1172 very skilled engineer, he was also able to locate a solution for me.
1173 Or to be exact, a workaround that solve my initial problem of
1174 connecting to password protected Zoom rooms using Jami.
</p
>
1176 <p
>So, how do you do this, I am sure you are wondering by now. The
1178 <a href=
"https://support.zoom.us/hc/en-us/articles/
202405539-H-
323-SIP-Room-Connector-Dial-Strings#sip
">documented
1179 from Zoom
</a
>, and it is to modify the SIP address to include the room
1180 password. What is most surprising about this is that the
1181 automatically generated email from Zoom with instructions on how to
1182 connect via SIP do not mention this. The SIP address to use normally
1183 consist of the room ID (a number), an @ character and the IP address
1184 of the Zoom SIP gateway. But Zoom understand a lot more than just the
1185 room ID in front of the at sign. The format is
"<tt
>[Meeting
1186 ID].[Password].[Layout].[Host Key]
</tt
>", and you can here see how you
1187 can both enter password, control the layout (full screen, active
1188 presence and gallery) and specify the host key to start the meeting.
1189 The full SIP address entered into Jami to provide the password will
1190 then look like this (all using made up numbers):
</p
>
1192 <p
><blockquote
>
1193 <tt
>sip:
657837644.522827@
192.168.169.170</tt
>
1194 </blockquote
></p
>
1196 <p
>Now if only jami would reduce its memory usage, I could even
1197 recommend this setup to others. :)
</p
>
1199 <p
>As usual, if you use Bitcoin and want to show your support of my
1200 activities, please send Bitcoin donations to my address
1201 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1206 <title>GnuCOBOL, a free platform to learn and use COBOL - nice free software
</title>
1207 <link>https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</link>
1208 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/GnuCOBOL__a_free_platform_to_learn_and_use_COBOL___nice_free_software.html
</guid>
1209 <pubDate>Wed,
29 Apr
2020 13:
10:
00 +
0200</pubDate>
1210 <description><p
>The curiosity got the better of me when
1211 <a href=
"https://developers.slashdot.org/story/
20/
04/
06/
1424246/new-jersey-desperately-needs-cobol-programmers
">Slashdot
1212 reported
</a
> that New Jersey was desperately looking for
1213 <a href=
"https://en.wikipedia.org/wiki/COBOL
">COBOL
</a
> programmers,
1214 and a few days later it was reported that
1215 <a href=
"https://onezero.medium.com/ibm-rallies-cobol-engineers-to-save-overloaded-unemployment-systems-eeadf13eddce
">IBM
1216 tried to locate COBOL programmers
</a
>.
</p
>
1218 <p
>I thus decided to have a look at free software alternatives to
1219 learn COBOL, and had the pleasure to find
1220 <a href=
"https://sourceforge.net/projects/open-cobol/
">GnuCOBOL
</a
> was
1221 already
<a href=
"https://tracker.debian.org/pkg/gnucobol
">in
1222 Debian
</a
>. It used to be called Open Cobol, and is a
"compiler
"
1223 transforming COBOL code to C or C++ before giving it to GCC or Visual
1224 Studio to build binaries.
</p
>
1226 <p
>I managed to get in touch with upstream, and was impressed with the
1227 quick response, and also was happy to see a new Debian maintainer
1228 taking over when the original one recently asked to be replaced. A
1229 new Debian upload was done as recently as yesterday.
</p
>
1231 <p
>Using the Debian package, I was able to follow a simple COBOL
1232 introduction and make and run simple COBOL programs. It was fun to
1233 learn a new programming language. If you want to test for yourself,
1234 <a href=
"https://en.wikipedia.org/wiki/GnuCOBOL
">the GnuCOBOL Wikipedia
1235 page
</a
> have a few simple examples to get you startet.
</p
>
1237 <p
>As I do not have much experience with COBOL, I do not know how
1238 standard compliant it is, but it claim to pass most tests from COBOL
1239 test suite, which sound good to me. It is nice to know it is possible
1240 to learn COBOL using software without any usage restrictions, and I am
1241 very happy such nice free software project as this is available. If
1242 you as me is curious about COBOL, check it out.
</p
>
1244 <p
>As usual, if you use Bitcoin and want to show your support of my
1245 activities, please send Bitcoin donations to my address
1246 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1251 <title>Jami/Ring, finally functioning peer to peer communication client
</title>
1252 <link>https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</link>
1253 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Jami_Ring__finally_functioning_peer_to_peer_communication_client.html
</guid>
1254 <pubDate>Wed,
19 Jun
2019 08:
50:
00 +
0200</pubDate>
1255 <description><p
>Some years ago, in
2016, I
1256 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">wrote
1257 for the first time about
</a
> the Ring peer to peer messaging system.
1258 It would provide messaging without any central server coordinating the
1259 system and without requiring all users to register a phone number or
1260 own a mobile phone. Back then, I could not get it to work, and put it
1261 aside until it had seen more development. A few days ago I decided to
1262 give it another try, and am happy to report that this time I am able
1263 to not only send and receive messages, but also place audio and video
1264 calls. But only if UDP is not blocked into your network.
</p
>
1266 <p
>The Ring system changed name earlier this year to
1267 <a href=
"https://en.wikipedia.org/wiki/Jami_(software)
">Jami
</a
>. I
1268 tried doing web search for
'ring
' when I discovered it for the first
1269 time, and can only applaud this change as it is impossible to find
1270 something called Ring among the noise of other uses of that word. Now
1271 you can search for
'jami
' and this client and
1272 <a href=
"https://jami.net/
">the Jami system
</a
> is the first hit at
1273 least on duckduckgo.
</p
>
1275 <p
>Jami will by default encrypt messages as well as audio and video
1276 calls, and try to send them directly between the communicating parties
1277 if possible. If this proves impossible (for example if both ends are
1278 behind NAT), it will use a central SIP TURN server maintained by the
1279 Jami project. Jami can also be a normal SIP client. If the SIP
1280 server is unencrypted, the audio and video calls will also be
1281 unencrypted. This is as far as I know the only case where Jami will
1282 do anything without encryption.
</p
>
1284 <p
>Jami is available for several platforms: Linux, Windows, MacOSX,
1285 Android, iOS, and Android TV. It is included in Debian already. Jami
1286 also work for those using F-Droid without any Google connections,
1287 while Signal do not.
1288 <a href=
"https://git.jami.net/savoirfairelinux/ring-project/wikis/technical/Protocol
">The
1289 protocol
</a
> is described in the Ring project wiki. The system uses a
1290 distributed hash table (DHT) system (similar to BitTorrent) running
1291 over UDP. On one of the networks I use, I discovered Jami failed to
1292 work. I tracked this down to the fact that incoming UDP packages
1293 going to ports
1-
49999 were blocked, and the DHT would pick a random
1294 port and end up in the low range most of the time. After talking to
1295 the developers, I solved this by enabling the dhtproxy in the
1296 settings, thus using TCP to talk to a central DHT proxy instead of
1298 peering directly with others. I
've been told the developers are
1299 working on allowing DHT to use TCP to avoid this problem. I also ran
1300 into a problem when trying to talk to the version of Ring included in
1301 Debian Stable (Stretch). Apparently the protocol changed between
1302 beta2 and the current version, making these clients incompatible.
1303 Hopefully the protocol will not be made incompatible in the
1306 <p
>It is worth noting that while looking at Jami and its features, I
1307 came across another communication platform I have not tested yet. The
1308 <a href=
"https://en.wikipedia.org/wiki/Tox_(protocol)
">Tox protocol
</a
>
1309 and
<a href=
"https://tox.chat/
">family of Tox clients
</a
>. It might
1310 become the topic of a future blog post.
</p
>
1312 <p
>As usual, if you use Bitcoin and want to show your support of my
1313 activities, please send Bitcoin donations to my address
1314 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1319 <title>Strategispillet Unknown Horizons nå tilgjengelig på bokmål
</title>
1320 <link>https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</link>
1321 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Strategispillet_Unknown_Horizons_n__tilgjengelig_p__bokm_l.html
</guid>
1322 <pubDate>Wed,
23 Jan
2019 07:
50:
00 +
0100</pubDate>
1323 <description><p
>I høst ble jeg inspirert til å bidra til oversettelsen av
1324 <a href=
"http://unknown-horizons.org/
">strategispillet Unknown
1325 Horizons
</a
>, og oversatte de nesten
200 strengene i prosjektet til
1326 bokmål. Deretter har jeg gått å ventet på at det kom en ny utgave som
1327 inneholdt disse oversettelsene. Nå er endelig ventetiden over. Den
1328 nye versjonen kom på nyåret, og ble
1329 <a href=
"https://tracker.debian.org/pkg/unknown-horizons
">lastet opp i
1330 Debian
</a
> for noen få dager siden. I går kveld fikk jeg testet det ut, og
1331 må innrømme at oversettelsene fungerer fint. Fant noen få tekster som
1332 måtte justeres, men ikke noe alvorlig. Har oppdatert
1333 <a href=
"https://hosted.weblate.org/projects/uh/
">oversettelsen på
1334 Weblate
</a
>, slik at neste utgave vil være enda bedre. :)
</p
>
1336 <p
>Spillet er et ressursstyringsspill ala Civilization, og er morsomt
1337 å spille for oss som liker slikt. :)
</p
>
1339 <p
>Som vanlig, hvis du bruker Bitcoin og ønsker å vise din støtte til
1340 det jeg driver med, setter jeg pris på om du sender Bitcoin-donasjoner
1342 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
1343 Merk, betaling med bitcoin er ikke anonymt. :)
</p
>
1348 <title>Debian now got everything you need to program Micro:bit
</title>
1349 <link>https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</link>
1350 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_got_everything_you_need_to_program_Micro_bit.html
</guid>
1351 <pubDate>Tue,
22 Jan
2019 17:
20:
00 +
0100</pubDate>
1352 <description><p
>I am amazed and very pleased to discover that since a few days ago,
1353 everything you need to program the
<a href=
"https://microbit.org/
">BBC
1354 micro:bit
</a
> is available from the Debian archive. All this is
1355 thanks to the hard work of Nick Morrott and the Debian python
1356 packaging team. The micro:bit project recommend the mu-editor to
1357 program the microcomputer, as this editor will take care of all the
1358 machinery required to injekt/flash micropython alongside the program
1359 into the micro:bit, as long as the pieces are available.
</p
>
1361 <p
>There are three main pieces involved. The first to enter Debian
1363 <a href=
"https://tracker.debian.org/pkg/python-uflash
">python-uflash
</a
>,
1364 which was accepted into the archive
2019-
01-
12. The next one was
1365 <a href=
"https://tracker.debian.org/pkg/mu-editor
">mu-editor
</a
>, which
1366 showed up
2019-
01-
13. The final and hardest part to to into the
1368 <a href=
"https://tracker.debian.org/pkg/firmware-microbit-micropython
">firmware-microbit-micropython
</a
>,
1369 which needed to get its build system and dependencies into Debian
1370 before it was accepted
2019-
01-
20. The last one is already in Debian
1371 Unstable and should enter Debian Testing / Buster in three days. This
1372 all allow any user of the micro:bit to get going by simply running
1373 'apt install mu-editor
' when using Testing or Unstable, and once
1374 Buster is released as stable, all the users of Debian stable will be
1375 catered for.
</p
>
1377 <p
>As a minor final touch, I added rules to
1378 <a href=
"https://tracker.debian.org/pkg/isenkram
">the isenkram
1379 package
</a
> for recognizing micro:bit and recommend the mu-editor
1380 package. This make sure any user of the isenkram desktop daemon will
1381 get a popup suggesting to install mu-editor then the USB cable from
1382 the micro:bit is inserted for the first time.
</p
>
1384 <p
>This should make it easier to have fun.
</p
>
1386 <p
>As usual, if you use Bitcoin and want to show your support of my
1387 activities, please send Bitcoin donations to my address
1388 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1393 <title>Learn to program with Minetest on Debian
</title>
1394 <link>https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</link>
1395 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Learn_to_program_with_Minetest_on_Debian.html
</guid>
1396 <pubDate>Sat,
15 Dec
2018 15:
30:
00 +
0100</pubDate>
1397 <description><p
>A fun way to learn how to program
1398 <a href=
"https://www.python.org/
">Python
</a
> is to follow the
1399 instructions in the book
1400 "<a href=
"https://nostarch.com/programwithminecraft
">Learn to program
1401 with Minecraft
</a
>", which introduces programming in Python to people
1402 who like to play with Minecraft. The book uses a Python library to
1403 talk to a TCP/IP socket with an API accepting build instructions and
1404 providing information about the current players in a Minecraft world.
1405 The TCP/IP API was first created for the Minecraft implementation for
1406 Raspberry Pi, and has since been ported to some server versions of
1407 Minecraft. The book contain recipes for those using Windows, MacOSX
1408 and Raspian. But a little known fact is that you can follow the same
1409 recipes using the free software construction game
1410 <a href=
"https://minetest.net/
">Minetest
</a
>.
</p
>
1412 <p
>There is
<a href=
"https://github.com/sprintingkiwi/pycraft_mod
">a
1413 Minetest module implementing the same API
</a
>, making it possible to
1414 use the Python programs coded to talk to Minecraft with Minetest too.
1416 <a href=
"https://ftp-master.debian.org/new/minetest-mod-pycraft_0.20%
2Bgit20180331.0376a0a%
2Bdfsg-
1.html
">uploaded
1417 this module
</a
> to Debian two weeks ago, and as soon as it clears the
1418 FTP masters NEW queue, learning to program Python with Minetest on
1419 Debian will be a simple
'apt install
' away. The Debian package is
1420 maintained as part of the Debian Games team, and
1421 <a href=
"https://salsa.debian.org/games-team/unfinished/minetest-mod-pycraft
">the
1422 packaging rules
</a
> are currently located under
'unfinished
' on
1425 <p
>You will most likely need to install several of the Minetest
1426 modules in Debian for the examples included with the library to work
1427 well, as there are several blocks used by the example scripts that are
1428 provided via modules in Minetest. Without the required blocks, a
1429 simple stone block is used instead. My initial testing with a analog
1430 clock did not get gold arms as instructed in the python library, but
1431 instead used stone arms.
</p
>
1433 <p
>I tried to find a way to add the API to the desktop version of
1434 Minecraft, but were unable to find any working recipes. The
1435 <a href=
"https://www.epiphanydigest.com/tag/minecraft-python-api/
">recipes
</a
>
1436 I
<a href=
"https://github.com/kbsriram/mcpiapi
">found
</a
> are only
1437 working with a standalone Minecraft server setup. Are there any
1438 options to use with the normal desktop version?
</p
>
1440 <p
>As usual, if you use Bitcoin and want to show your support of my
1441 activities, please send Bitcoin donations to my address
1442 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1447 <title>Time for an official MIME type for patches?
</title>
1448 <link>https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</link>
1449 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_an_official_MIME_type_for_patches_.html
</guid>
1450 <pubDate>Thu,
1 Nov
2018 08:
15:
00 +
0100</pubDate>
1451 <description><p
>As part of my involvement in
1452 <a href=
"https://gitlab.com/OsloMet-ABI/nikita-noark5-core
">the Nikita
1453 archive API project
</a
>, I
've been importing a fairly large lump of
1454 emails into a test instance of the archive to see how well this would
1455 go. I picked a subset of
<a href=
"https://notmuchmail.org/
">my
1456 notmuch email database
</a
>, all public emails sent to me via
1457 @lists.debian.org, giving me a set of around
216 000 emails to import.
1458 In the process, I had a look at the various attachments included in
1459 these emails, to figure out what to do with attachments, and noticed
1460 that one of the most common attachment formats do not have
1461 <a href=
"https://www.iana.org/assignments/media-types/media-types.xhtml
">an
1462 official MIME type
</a
> registered with IANA/IETF. The output from
1463 diff, ie the input for patch, is on the top
10 list of formats
1464 included in these emails. At the moment people seem to use either
1465 text/x-patch or text/x-diff, but neither is officially registered. It
1466 would be better if one official MIME type were registered and used
1467 everywhere.
</p
>
1469 <p
>To try to get one official MIME type for these files, I
've brought
1471 <a href=
"https://www.ietf.org/mailman/listinfo/media-types
">the
1472 media-types mailing list
</a
>. If you are interested in discussion
1473 which MIME type to use as the official for patch files, or involved in
1474 making software using a MIME type for patches, perhaps you would like
1475 to join the discussion?
</p
>
1477 <p
>As usual, if you use Bitcoin and want to show your support of my
1478 activities, please send Bitcoin donations to my address
1479 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1484 <title>Automatic Google Drive sync using grive in Debian
</title>
1485 <link>https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</link>
1486 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_Google_Drive_sync_using_grive_in_Debian.html
</guid>
1487 <pubDate>Thu,
4 Oct
2018 15:
20:
00 +
0200</pubDate>
1488 <description><p
>A few days, I rescued a Windows victim over to Debian. To try to
1489 rescue the remains, I helped set up automatic sync with Google Drive.
1490 I did not find any sensible Debian package handling this
1491 automatically, so I rebuild the grive2 source from
1492 <a href=
"http://www.webupd8.org/
">the Ubuntu UPD8 PPA
</a
> to do the
1493 task and added a autostart desktop entry and a small shell script to
1494 run in the background while the user is logged in to do the sync.
1495 Here is a sketch of the setup for future reference.
</p
>
1497 <p
>I first created
<tt
>~/googledrive
</tt
>, entered the directory and
1498 ran
'<tt
>grive -a
</tt
>' to authenticate the machine/user. Next, I
1499 created a autostart hook in
<tt
>~/.config/autostart/grive.desktop
</tt
>
1500 to start the sync when the user log in:
</p
>
1502 <p
><blockquote
><pre
>
1504 Name=Google drive autosync
1506 Exec=/home/user/bin/grive-sync
1507 </pre
></blockquote
></p
>
1509 <p
>Finally, I wrote the
<tt
>~/bin/grive-sync
</tt
> script to sync
1510 ~/googledrive/ with the files in Google Drive.
</p
>
1512 <p
><blockquote
><pre
>
1517 if [
"$syncpid
" ] ; then
1521 trap cleanup EXIT INT QUIT
1522 /usr/lib/grive/grive-sync.sh listen googledrive
2>&1 | sed
"s%^%$
0:%
" &
1525 if ! xhost
>/dev/null
2>&1 ; then
1526 echo
"no DISPLAY, exiting as the user probably logged out
"
1529 if [ ! -e /run/user/
1000/grive-sync.sh_googledrive ] ; then
1530 /usr/lib/grive/grive-sync.sh sync googledrive
1533 done
2>&1 | sed
"s%^%$
0:%
"
1534 </pre
></blockquote
></p
>
1536 <p
>Feel free to use the setup if you want. It can be assumed to be
1537 GNU GPL v2 licensed (or any later version, at your leisure), but I
1538 doubt this code is possible to claim copyright on.
</p
>
1540 <p
>As usual, if you use Bitcoin and want to show your support of my
1541 activities, please send Bitcoin donations to my address
1542 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1547 <title>Using the Kodi API to play Youtube videos
</title>
1548 <link>https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</link>
1549 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_the_Kodi_API_to_play_Youtube_videos.html
</guid>
1550 <pubDate>Sun,
2 Sep
2018 23:
40:
00 +
0200</pubDate>
1551 <description><p
>I continue to explore my Kodi installation, and today I wanted to
1552 tell it to play a youtube URL I received in a chat, without having to
1553 insert search terms using the on-screen keyboard. After searching the
1554 web for API access to the Youtube plugin and testing a bit, I managed
1555 to find a recipe that worked. If you got a kodi instance with its API
1556 available from http://kodihost/jsonrpc, you can try the following to
1557 have check out a nice cover band.
</p
>
1559 <p
><blockquote
><pre
>curl --silent --header
'Content-Type: application/json
' \
1560 --data-binary
'{
"id
":
1,
"jsonrpc
":
"2.0",
"method
":
"Player.Open
",
1561 "params
": {
"item
": {
"file
":
1562 "plugin://plugin.video.youtube/play/?video_id=LuRGVM9O0qg
" } } }
' \
1563 http://projector.local/jsonrpc
</pre
></blockquote
></p
>
1565 <p
>I
've extended kodi-stream program to take a video source as its
1566 first argument. It can now handle direct video links, youtube links
1567 and
'desktop
' to stream my desktop to Kodi. It is almost like a
1568 Chromecast. :)
</p
>
1570 <p
>As usual, if you use Bitcoin and want to show your support of my
1571 activities, please send Bitcoin donations to my address
1572 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1577 <title>Sharing images with friends and family using RSS and EXIF/XMP metadata
</title>
1578 <link>https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</link>
1579 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sharing_images_with_friends_and_family_using_RSS_and_EXIF_XMP_metadata.html
</guid>
1580 <pubDate>Tue,
31 Jul
2018 23:
30:
00 +
0200</pubDate>
1581 <description><p
>For a while now, I have looked for a sensible way to share images
1582 with my family using a self hosted solution, as it is unacceptable to
1583 place images from my personal life under the control of strangers
1584 working for data hoarders like Google or Dropbox. The last few days I
1585 have drafted an approach that might work out, and I would like to
1586 share it with you. I would like to publish images on a server under
1587 my control, and point some Internet connected display units using some
1588 free and open standard to the images I published. As my primary
1589 language is not limited to ASCII, I need to store metadata using
1590 UTF-
8. Many years ago, I hoped to find a digital photo frame capable
1591 of reading a RSS feed with image references (aka using the
1592 &lt;enclosure
&gt; RSS tag), but was unable to find a current supplier
1593 of such frames. In the end I gave up that approach.
</p
>
1595 <p
>Some months ago, I discovered that
1596 <a href=
"https://www.jwz.org/xscreensaver/
">XScreensaver
</a
> is able to
1597 read images from a RSS feed, and used it to set up a screen saver on
1598 my home info screen, showing images from the Daily images feed from
1599 NASA. This proved to work well. More recently I discovered that
1600 <a href=
"https://kodi.tv
">Kodi
</a
> (both using
1601 <a href=
"https://www.openelec.tv/
">OpenELEC
</a
> and
1602 <a href=
"https://libreelec.tv
">LibreELEC
</a
>) provide the
1603 <a href=
"https://github.com/grinsted/script.screensaver.feedreader
">Feedreader
</a
>
1604 screen saver capable of reading a RSS feed with images and news. For
1605 fun, I used it this summer to test Kodi on my parents TV by hooking up
1606 a Raspberry PI unit with LibreELEC, and wanted to provide them with a
1607 screen saver showing selected pictures from my selection.
</p
>
1609 <p
>Armed with motivation and a test photo frame, I set out to generate
1610 a RSS feed for the Kodi instance. I adjusted my
<a
1611 href=
"https://freedombox.org/
">Freedombox
</a
> instance, created
1612 /var/www/html/privatepictures/, wrote a small Perl script to extract
1613 title and description metadata from the photo files and generate the
1614 RSS file. I ended up using Perl instead of python, as the
1615 libimage-exiftool-perl Debian package seemed to handle the EXIF/XMP
1616 tags I ended up using, while python3-exif did not. The relevant EXIF
1617 tags only support ASCII, so I had to find better alternatives. XMP
1618 seem to have the support I need.
</p
>
1620 <p
>I am a bit unsure which EXIF/XMP tags to use, as I would like to
1621 use tags that can be easily added/updated using normal free software
1622 photo managing software. I ended up using the tags set using this
1623 exiftool command, as these tags can also be set using digiKam:
</p
>
1625 <blockquote
><pre
>
1626 exiftool -headline=
'The RSS image title
' \
1627 -description=
'The RSS image description.
' \
1628 -subject+=for-family photo.jpeg
1629 </pre
></blockquote
>
1631 <p
>I initially tried the
"-title
" and
"keyword
" tags, but they were
1632 invisible in digiKam, so I changed to
"-headline
" and
"-subject
". I
1633 use the keyword/subject
'for-family
' to flag that the photo should be
1634 shared with my family. Images with this keyword set are located and
1635 copied into my Freedombox for the RSS generating script to find.
</p
>
1637 <p
>Are there better ways to do this? Get in touch if you have better
1638 suggestions.
</p
>
1640 <p
>As usual, if you use Bitcoin and want to show your support of my
1641 activities, please send Bitcoin donations to my address
1642 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1647 <title>Simple streaming the Linux desktop to Kodi using GStreamer and RTP
</title>
1648 <link>https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</link>
1649 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
</guid>
1650 <pubDate>Thu,
12 Jul
2018 17:
55:
00 +
0200</pubDate>
1651 <description><p
>Last night, I wrote
1652 <a href=
"http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
">a
1653 recipe to stream a Linux desktop using VLC to a instance of Kodi
</a
>.
1654 During the day I received valuable feedback, and thanks to the
1655 suggestions I have been able to rewrite the recipe into a much simpler
1656 approach requiring no setup at all. It is a single script that take
1657 care of it all.
</p
>
1659 <p
>This new script uses GStreamer instead of VLC to capture the
1660 desktop and stream it to Kodi. This fixed the video quality issue I
1661 saw initially. It further removes the need to add a m3u file on the
1662 Kodi machine, as it instead connects to
1663 <a href=
"https://kodi.wiki/view/JSON-RPC_API/v8
">the JSON-RPC API in
1664 Kodi
</a
> and simply ask Kodi to play from the stream created using
1665 GStreamer. Streaming the desktop to Kodi now become trivial. Copy
1666 the script below, run it with the DNS name or IP address of the kodi
1667 server to stream to as the only argument, and watch your screen show
1668 up on the Kodi screen. Note, it depend on multicast on the local
1669 network, so if you need to stream outside the local network, the
1670 script must be modified. Also note, I have no idea if audio work, as
1671 I only care about the picture part.
</p
>
1673 <blockquote
><pre
>
1676 # Stream the Linux desktop view to Kodi. See
1677 # http://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
1678 # for backgorund information.
1680 # Make sure the stream is stopped in Kodi and the gstreamer process is
1681 # killed if something go wrong (for example if curl is unable to find the
1682 # kodi server). Do the same when interrupting this script.
1686 params=
"$
3"
1687 curl --silent --header
'Content-Type: application/json
' \
1688 --data-binary
"{ \
"id\
":
1, \
"jsonrpc\
": \
"2.0\
", \
"method\
": \
"$cmd\
", \
"params\
": $params }
" \
1689 "http://$host/jsonrpc
"
1692 if [ -n
"$kodihost
" ] ; then
1693 # Stop the playing when we end
1694 playerid=$(kodicmd
"$kodihost
" Player.GetActivePlayers
"{}
" |
1695 jq .result[].playerid)
1696 kodicmd
"$kodihost
" Player.Stop
"{ \
"playerid\
" : $playerid }
" > /dev/null
1698 if [
"$gstpid
" ]
&& kill -
0 "$gstpid
" >/dev/null
2>&1; then
1699 kill
"$gstpid
"
1702 trap cleanup EXIT INT
1704 if [ -n
"$
1" ]; then
1715 pasrc=$(pactl list | grep -A2
'Source #
' | grep
'Name: .*\.monitor$
' | \
1716 cut -d
" " -f2|head -
1)
1717 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
1718 videoconvert ! queue2 ! \
1719 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
1720 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
1721 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
1722 udpsink host=$mcast port=$mcastport ttl-mc=$mcastttl auto-multicast=
1 sync=
0 \
1723 pulsesrc device=$pasrc ! audioconvert ! queue2 ! avenc_aac ! queue2 ! mux. \
1724 > /dev/null
2>&1 &
1727 # Give stream a second to get going
1730 # Ask kodi to start streaming using its JSON-RPC API
1731 kodicmd
"$kodihost
" Player.Open \
1732 "{\
"item\
": { \
"file\
": \
"udp://@$mcast:$mcastport\
" } }
" > /dev/null
1734 # wait for gst to end
1735 wait
"$gstpid
"
1736 </pre
></blockquote
>
1738 <p
>I hope you find the approach useful. I know I do.
</p
>
1740 <p
>As usual, if you use Bitcoin and want to show your support of my
1741 activities, please send Bitcoin donations to my address
1742 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1747 <title>Streaming the Linux desktop to Kodi using VLC and RTSP
</title>
1748 <link>https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</link>
1749 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Streaming_the_Linux_desktop_to_Kodi_using_VLC_and_RTSP.html
</guid>
1750 <pubDate>Thu,
12 Jul
2018 02:
00:
00 +
0200</pubDate>
1751 <description><p
>PS: See
1752 <ahref=
"http://people.skolelinux.org/pere/blog/Simple_streaming_the_Linux_desktop_to_Kodi_using_GStreamer_and_RTP.html
">the
1753 followup post
</a
> for a even better approach.
</p
>
1755 <p
>A while back, I was asked by a friend how to stream the desktop to
1756 my projector connected to Kodi. I sadly had to admit that I had no
1757 idea, as it was a task I never had tried. Since then, I have been
1758 looking for a way to do so, preferable without much extra software to
1759 install on either side. Today I found a way that seem to kind of
1760 work. Not great, but it is a start.
</p
>
1762 <p
>I had a look at several approaches, for example
1763 <a href=
"https://github.com/mfoetsch/dlna_live_streaming
">using uPnP
1764 DLNA as described in
2011</a
>, but it required a uPnP server, fuse and
1765 local storage enough to store the stream locally. This is not going
1766 to work well for me, lacking enough free space, and it would
1767 impossible for my friend to get working.
</p
>
1769 <p
>Next, it occurred to me that perhaps I could use VLC to create a
1770 video stream that Kodi could play. Preferably using
1771 broadcast/multicast, to avoid having to change any setup on the Kodi
1772 side when starting such stream. Unfortunately, the only recipe I
1773 could find using multicast used the rtp protocol, and this protocol
1774 seem to not be supported by Kodi.
</p
>
1776 <p
>On the other hand, the rtsp protocol is working! Unfortunately I
1777 have to specify the IP address of the streaming machine in both the
1778 sending command and the file on the Kodi server. But it is showing my
1779 desktop, and thus allow us to have a shared look on the big screen at
1780 the programs I work on.
</p
>
1782 <p
>I did not spend much time investigating codeces. I combined the
1783 rtp and rtsp recipes from
1784 <a href=
"https://wiki.videolan.org/Documentation:Streaming_HowTo/Command_Line_Examples/
">the
1785 VLC Streaming HowTo/Command Line Examples
</a
>, and was able to get
1786 this working on the desktop/streaming end.
</p
>
1788 <blockquote
><pre
>
1789 vlc screen:// --sout \
1790 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{dst=projector.local,port=
1234,sdp=rtsp://
192.168.11.4:
8080/test.sdp}
'
1791 </pre
></blockquote
>
1793 <p
>I ssh-ed into my Kodi box and created a file like this with the
1794 same IP address:
</p
>
1796 <blockquote
><pre
>
1797 echo rtsp://
192.168.11.4:
8080/test.sdp \
1798 > /storage/videos/screenstream.m3u
1799 </pre
></blockquote
>
1801 <p
>Note the
192.168.11.4 IP address is my desktops IP address. As far
1802 as I can tell the IP must be hardcoded for this to work. In other
1803 words, if someone elses machine is going to do the steaming, you have
1804 to update screenstream.m3u on the Kodi machine and adjust the vlc
1805 recipe. To get started, locate the file in Kodi and select the m3u
1806 file while the VLC stream is running. The desktop then show up in my
1807 big screen. :)
</p
>
1809 <p
>When using the same technique to stream a video file with audio,
1810 the audio quality is really bad. No idea if the problem is package
1811 loss or bad parameters for the transcode. I do not know VLC nor Kodi
1812 enough to tell.
</p
>
1814 <p
><strong
>Update
2018-
07-
12</strong
>: Johannes Schauer send me a few
1815 succestions and reminded me about an important step. The
"screen:
"
1816 input source is only available once the vlc-plugin-access-extra
1817 package is installed on Debian. Without it, you will see this error
1818 message:
"VLC is unable to open the MRL
'screen://
'. Check the log
1819 for details.
" He further found that it is possible to drop some parts
1820 of the VLC command line to reduce the amount of hardcoded information.
1821 It is also useful to consider using cvlc to avoid having the VLC
1822 window in the desktop view. In sum, this give us this command line on
1825 <blockquote
><pre
>
1826 cvlc screen:// --sout \
1827 '#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{sdp=rtsp://:
8080/}
'
1828 </pre
></blockquote
>
1830 <p
>and this on the Kodi end
<p
>
1832 <blockquote
><pre
>
1833 echo rtsp://
192.168.11.4:
8080/ \
1834 > /storage/videos/screenstream.m3u
1835 </pre
></blockquote
>
1837 <p
>Still bad image quality, though. But I did discover that streaming
1838 a DVD using dvdsimple:///dev/dvd as the source had excellent video and
1839 audio quality, so I guess the issue is in the input or transcoding
1840 parts, not the rtsp part. I
've tried to change the vb and ab
1841 parameters to use more bandwidth, but it did not make a
1842 difference.
</p
>
1844 <p
>I further received a suggestion from Einar Haraldseid to try using
1845 gstreamer instead of VLC, and this proved to work great! He also
1846 provided me with the trick to get Kodi to use a multicast stream as
1847 its source. By using this monstrous oneliner, I can stream my desktop
1848 with good video quality in reasonable framerate to the
239.255.0.1
1849 multicast address on port
1234:
1851 <blockquote
><pre
>
1852 gst-launch-
1.0 ximagesrc use-damage=
0 ! video/x-raw,framerate=
30/
1 ! \
1853 videoconvert ! queue2 ! \
1854 x264enc bitrate=
8000 speed-preset=superfast tune=zerolatency qp-min=
30 \
1855 key-int-max=
15 bframes=
2 ! video/x-h264,profile=high ! queue2 ! \
1856 mpegtsmux alignment=
7 name=mux ! rndbuffersize max=
1316 min=
1316 ! \
1857 udpsink host=
239.255.0.1 port=
1234 ttl-mc=
1 auto-multicast=
1 sync=
0 \
1858 pulsesrc device=$(pactl list | grep -A2
'Source #
' | \
1859 grep
'Name: .*\.monitor$
' | cut -d
" " -f2|head -
1) ! \
1860 audioconvert ! queue2 ! avenc_aac ! queue2 ! mux.
1861 </pre
></blockquote
>
1863 <p
>and this on the Kodi end
<p
>
1865 <blockquote
><pre
>
1866 echo udp://@
239.255.0.1:
1234 \
1867 > /storage/videos/screenstream.m3u
1868 </pre
></blockquote
>
1870 <p
>Note the trick to pick a valid pulseaudio source. It might not
1871 pick the one you need. This approach will of course lead to trouble
1872 if more than one source uses the same multicast port and address.
1873 Note the ttl-mc=
1 setting, which limit the multicast packages to the
1874 local network. If the value is increased, your screen will be
1875 broadcasted further, one network
"hop
" for each increase (read up on
1876 multicast to learn more. :)!
</p
>
1878 <p
>Having cracked how to get Kodi to receive multicast streams, I
1879 could use this VLC command to stream to the same multicast address.
1880 The image quality is way better than the rtsp approach, but gstreamer
1881 seem to be doing a better job.
</p
>
1883 <blockquote
><pre
>
1884 cvlc screen:// --sout
'#transcode{vcodec=mp4v,acodec=mpga,vb=
800,ab=
128}:rtp{mux=ts,dst=
239.255.0.1,port=
1234,sdp=sap}
'
1885 </pre
></blockquote
>
1887 <p
>As usual, if you use Bitcoin and want to show your support of my
1888 activities, please send Bitcoin donations to my address
1889 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
1894 <title>What is the most supported MIME type in Debian in
2018?
</title>
1895 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</link>
1896 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_in_2018_.html
</guid>
1897 <pubDate>Mon,
9 Jul
2018 08:
05:
00 +
0200</pubDate>
1898 <description><p
>Five years ago,
1899 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
">I
1900 measured what the most supported MIME type in Debian was
</a
>, by
1901 analysing the desktop files in all packages in the archive. Since
1902 then, the DEP-
11 AppStream system has been put into production, making
1903 the task a lot easier. This made me want to repeat the measurement,
1904 to see how much things changed. Here are the new numbers, for
1905 unstable only this time:
1907 <p
><strong
>Debian Unstable:
</strong
></p
>
1911 ----- -----------------------
1923 30 audio/x-vorbis+ogg
1924 29 image/x-portable-pixmap
1926 27 image/x-portable-bitmap
1928 26 application/x-ogg
1934 <p
>The list was created like this using a sid chroot:
"cat
1935 /var/lib/apt/lists/*sid*_dep11_Components-amd64.yml.gz| zcat | awk
'/^
1936 - \S+\/\S+$/ {print $
2 }
' | sort | uniq -c | sort -nr | head -
20"</p
>
1938 <p
>It is interesting to see how image formats have passed text/plain
1939 as the most announced supported MIME type. These days, thanks to the
1940 AppStream system, if you run into a file format you do not know, and
1941 want to figure out which packages support the format, you can find the
1942 MIME type of the file using
"file --mime
&lt;filename
&gt;
", and then
1943 look up all packages announcing support for this format in their
1944 AppStream metadata (XML or .desktop file) using
"appstreamcli
1945 what-provides mimetype
&lt;mime-type
&gt;. For example if you, like
1946 me, want to know which packages support inode/directory, you can get a
1947 list like this:
</p
>
1949 <p
><blockquote
><pre
>
1950 % appstreamcli what-provides mimetype inode/directory | grep Package: | sort
1957 Package: doublecmd-common
1959 Package: enlightenment
1979 </pre
></blockquote
></p
>
1981 <p
>Using the same method, I can quickly discover that the Sketchup file
1982 format is not yet supported by any package in Debian:
</p
>
1984 <p
><blockquote
><pre
>
1985 % appstreamcli what-provides mimetype application/vnd.sketchup.skp
1986 Could not find component providing
'mimetype::application/vnd.sketchup.skp
'.
1988 </pre
></blockquote
></p
>
1990 <p
>Yesterday I used it to figure out which packages support the STL
3D
1993 <p
><blockquote
><pre
>
1994 % appstreamcli what-provides mimetype application/sla|grep Package
1999 </pre
></blockquote
></p
>
2001 <p
>PS: A new version of Cura was uploaded to Debian yesterday.
</p
>
2003 <p
>As usual, if you use Bitcoin and want to show your support of my
2004 activities, please send Bitcoin donations to my address
2005 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2010 <title>Debian APT upgrade without enough free space on the disk...
</title>
2011 <link>https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</link>
2012 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_APT_upgrade_without_enough_free_space_on_the_disk___.html
</guid>
2013 <pubDate>Sun,
8 Jul
2018 12:
10:
00 +
0200</pubDate>
2014 <description><p
>Quite regularly, I let my Debian Sid/Unstable chroot stay untouch
2015 for a while, and when I need to update it there is not enough free
2016 space on the disk for apt to do a normal
'apt upgrade
'. I normally
2017 would resolve the issue by doing
'apt install
&lt;somepackages
&gt;
' to
2018 upgrade only some of the packages in one batch, until the amount of
2019 packages to download fall below the amount of free space available.
2020 Today, I had about
500 packages to upgrade, and after a while I got
2021 tired of trying to install chunks of packages manually. I concluded
2022 that I did not have the spare hours required to complete the task, and
2023 decided to see if I could automate it. I came up with this small
2024 script which I call
'apt-in-chunks
':
</p
>
2026 <p
><blockquote
><pre
>
2029 # Upgrade packages when the disk is too full to upgrade every
2030 # upgradable package in one lump. Fetching packages to upgrade using
2031 # apt, and then installing using dpkg, to avoid changing the package
2032 # flag for manual/automatic.
2037 if [
"$
1" ]; then
2038 grep -v
"$
1"
2044 for p in $(apt list --upgradable | ignore
"$@
" |cut -d/ -f1 | grep -v
'^Listing...
'); do
2045 echo
"Upgrading $p
"
2047 apt install --download-only -y $p
2048 for f in /var/cache/apt/archives/*.deb; do
2049 if [ -e
"$f
" ]; then
2050 dpkg -i /var/cache/apt/archives/*.deb
2055 </pre
></blockquote
></p
>
2057 <p
>The script will extract the list of packages to upgrade, try to
2058 download the packages needed to upgrade one package, install the
2059 downloaded packages using dpkg. The idea is to upgrade packages
2060 without changing the APT mark for the package (ie the one recording of
2061 the package was manually requested or pulled in as a dependency). To
2062 use it, simply run it as root from the command line. If it fail, try
2063 'apt install -f
' to clean up the mess and run the script again. This
2064 might happen if the new packages conflict with one of the old
2065 packages. dpkg is unable to remove, while apt can do this.
</p
>
2067 <p
>It take one option, a package to ignore in the list of packages to
2068 upgrade. The option to ignore a package is there to be able to skip
2069 the packages that are simply too large to unpack. Today this was
2070 'ghc
', but I have run into other large packages causing similar
2071 problems earlier (like TeX).
</p
>
2073 <p
>Update
2018-
07-
08: Thanks to Paul Wise, I am aware of two
2074 alternative ways to handle this. The
"unattended-upgrades
2075 --minimal-upgrade-steps
" option will try to calculate upgrade sets for
2076 each package to upgrade, and then upgrade them in order, smallest set
2077 first. It might be a better option than my above mentioned script.
2078 Also,
"aptutude upgrade
" can upgrade single packages, thus avoiding
2079 the need for using
"dpkg -i
" in the script above.
</p
>
2081 <p
>As usual, if you use Bitcoin and want to show your support of my
2082 activities, please send Bitcoin donations to my address
2083 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2088 <title>Version
3.1 of Cura, the
3D print slicer, is now in Debian
</title>
2089 <link>https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</link>
2090 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Version_3_1_of_Cura__the_3D_print_slicer__is_now_in_Debian.html
</guid>
2091 <pubDate>Tue,
13 Feb
2018 06:
20:
00 +
0100</pubDate>
2092 <description><p
>A new version of the
2093 <a href=
"https://tracker.debian.org/pkg/cura
">3D printer slicer
2094 software Cura
</a
>, version
3.1.0, is now available in Debian Testing
2095 (aka Buster) and Debian Unstable (aka Sid). I hope you find it
2096 useful. It was uploaded the last few days, and the last update will
2097 enter testing tomorrow. See the
2098 <a href=
"https://ultimaker.com/en/products/cura-software/release-notes
">release
2099 notes
</a
> for the list of bug fixes and new features. Version
3.2
2100 was announced
6 days ago. We will try to get it into Debian as
2103 <p
>More information related to
3D printing is available on the
2104 <a href=
"https://wiki.debian.org/
3DPrinting
">3D printing
</a
> and
2105 <a href=
"https://wiki.debian.org/
3D-printer
">3D printer
</a
> wiki pages
2106 in Debian.
</p
>
2108 <p
>As usual, if you use Bitcoin and want to show your support of my
2109 activities, please send Bitcoin donations to my address
2110 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2115 <title>Cura, the nice
3D print slicer, is now in Debian Unstable
</title>
2116 <link>https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</link>
2117 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Cura__the_nice_3D_print_slicer__is_now_in_Debian_Unstable.html
</guid>
2118 <pubDate>Sun,
17 Dec
2017 07:
00:
00 +
0100</pubDate>
2119 <description><p
>After several months of working and waiting, I am happy to report
2120 that the nice and user friendly
3D printer slicer software Cura just
2121 entered Debian Unstable. It consist of five packages,
2122 <a href=
"https://tracker.debian.org/pkg/cura
">cura
</a
>,
2123 <a href=
"https://tracker.debian.org/pkg/cura-engine
">cura-engine
</a
>,
2124 <a href=
"https://tracker.debian.org/pkg/libarcus
">libarcus
</a
>,
2125 <a href=
"https://tracker.debian.org/pkg/fdm-materials
">fdm-materials
</a
>,
2126 <a href=
"https://tracker.debian.org/pkg/libsavitar
">libsavitar
</a
> and
2127 <a href=
"https://tracker.debian.org/pkg/uranium
">uranium
</a
>. The last
2128 two, uranium and cura, entered Unstable yesterday. This should make
2129 it easier for Debian users to print on at least the Ultimaker class of
2130 3D printers. My nearest
3D printer is an Ultimaker
2+, so it will
2131 make life easier for at least me. :)
</p
>
2133 <p
>The work to make this happen was done by Gregor Riepl, and I was
2134 happy to assist him in sponsoring the packages. With the introduction
2135 of Cura, Debian is up to three
3D printer slicers at your service,
2136 Cura, Slic3r and Slic3r Prusa. If you own or have access to a
3D
2137 printer, give it a go. :)
</p
>
2139 <p
>The
3D printer software is maintained by the
3D printer Debian
2140 team, flocking together on the
2141 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
3dprinter-general
">3dprinter-general
</a
>
2142 mailing list and the
2143 <a href=
"irc://irc.debian.org/#debian-
3dprinting
">#debian-
3dprinting
</a
>
2144 IRC channel.
</p
>
2146 <p
>The next step for Cura in Debian is to update the cura package to
2147 version
3.0.3 and then update the entire set of packages to version
2148 3.1.0 which showed up the last few days.
</p
>
2153 <title>Generating
3D prints in Debian using Cura and Slic3r(-prusa)
</title>
2154 <link>https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</link>
2155 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Generating_3D_prints_in_Debian_using_Cura_and_Slic3r__prusa_.html
</guid>
2156 <pubDate>Mon,
9 Oct
2017 10:
50:
00 +
0200</pubDate>
2157 <description><p
>At my nearby maker space,
2158 <a href=
"http://sonen.ifi.uio.no/
">Sonen
</a
>, I heard the story that it
2159 was easier to generate gcode files for theyr
3D printers (Ultimake
2+)
2160 on Windows and MacOS X than Linux, because the software involved had
2161 to be manually compiled and set up on Linux while premade packages
2162 worked out of the box on Windows and MacOS X. I found this annoying,
2163 as the software involved,
2164 <a href=
"https://github.com/Ultimaker/Cura
">Cura
</a
>, is free software
2165 and should be trivial to get up and running on Linux if someone took
2166 the time to package it for the relevant distributions. I even found
2167 <a href=
"https://bugs.debian.org/
706656">a request for adding into
2168 Debian
</a
> from
2013, which had seem some activity over the years but
2169 never resulted in the software showing up in Debian. So a few days
2170 ago I offered my help to try to improve the situation.
</p
>
2172 <p
>Now I am very happy to see that all the packages required by a
2173 working Cura in Debian are uploaded into Debian and waiting in the NEW
2174 queue for the ftpmasters to have a look. You can track the progress
2176 <a href=
"https://qa.debian.org/developer.php?email=
3dprinter-general%
40lists.alioth.debian.org
">the
2177 status page for the
3D printer team
</a
>.
</p
>
2179 <p
>The uploaded packages are a bit behind upstream, and was uploaded
2180 now to get slots in
<a href=
"https://ftp-master.debian.org/new.html
">the NEW
2181 queue
</a
> while we work up updating the packages to the latest
2182 upstream version.
</p
>
2184 <p
>On a related note, two competitors for Cura, which I found harder
2185 to use and was unable to configure correctly for Ultimaker
2+ in the
2186 short time I spent on it, are already in Debian. If you are looking
2187 for
3D printer
"slicers
" and want something already available in
2189 <a href=
"https://tracker.debian.org/pkg/slic3r
">slic3r
</a
> and
2190 <a href=
"https://tracker.debian.org/pkg/slic3r-prusa
">slic3r-prusa
</a
>.
2191 The latter is a fork of the former.
</p
>
2193 <p
>As usual, if you use Bitcoin and want to show your support of my
2194 activities, please send Bitcoin donations to my address
2195 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2200 <title>Visualizing GSM radio chatter using gr-gsm and Hopglass
</title>
2201 <link>https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</link>
2202 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Visualizing_GSM_radio_chatter_using_gr_gsm_and_Hopglass.html
</guid>
2203 <pubDate>Fri,
29 Sep
2017 10:
30:
00 +
0200</pubDate>
2204 <description><p
>Every mobile phone announce its existence over radio to the nearby
2205 mobile cell towers. And this radio chatter is available for anyone
2206 with a radio receiver capable of receiving them. Details about the
2207 mobile phones with very good accuracy is of course collected by the
2208 phone companies, but this is not the topic of this blog post. The
2209 mobile phone radio chatter make it possible to figure out when a cell
2210 phone is nearby, as it include the SIM card ID (IMSI). By paying
2211 attention over time, one can see when a phone arrive and when it leave
2212 an area. I believe it would be nice to make this information more
2213 available to the general public, to make more people aware of how
2214 their phones are announcing their whereabouts to anyone that care to
2217 <p
>I am very happy to report that we managed to get something
2218 visualizing this information up and running for
2219 <a href=
"http://norwaymakers.org/osf17
">Oslo Skaperfestival
2017</a
>
2220 (Oslo Makers Festival) taking place today and tomorrow at Deichmanske
2221 library. The solution is based on the
2222 <a href=
"http://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
">simple
2223 recipe for listening to GSM chatter
</a
> I posted a few days ago, and
2224 will show up at the stand of
<a href=
"http://sonen.ifi.uio.no/
">Åpen
2225 Sone from the Computer Science department of the University of
2226 Oslo
</a
>. The presentation will show the nearby mobile phones (aka
2227 IMSIs) as dots in a web browser graph, with lines to the dot
2228 representing mobile base station it is talking to. It was working in
2229 the lab yesterday, and was moved into place this morning.
</p
>
2231 <p
>We set up a fairly powerful desktop machine using Debian
2232 Buster/Testing with several (five, I believe) RTL2838 DVB-T receivers
2233 connected and visualize the visible cell phone towers using an
2234 <a href=
"https://github.com/marlow925/hopglass
">English version of
2235 Hopglass
</a
>. A fairly powerfull machine is needed as the
2236 grgsm_livemon_headless processes from
2237 <a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
> converting
2238 the radio signal to data packages is quite CPU intensive.
</p
>
2240 <p
>The frequencies to listen to, are identified using a slightly
2241 patched scan-and-livemon (to set the --args values for each receiver),
2242 and the Hopglass data is generated using the
2243 <a href=
"https://github.com/petterreinholdtsen/IMSI-catcher/tree/meshviewer-output
">patches
2244 in my meshviewer-output branch
</a
>. For some reason we could not get
2245 more than four SDRs working. There is also a geographical map trying
2246 to show the location of the base stations, but I believe their
2247 coordinates are hardcoded to some random location in Germany, I
2248 believe. The code should be replaced with code to look up location in
2249 a text file, a sqlite database or one of the online databases
2251 <a href=
"https://github.com/Oros42/IMSI-catcher/issues/
14">the github
2252 issue for the topic
</a
>.
2254 <p
>If this sound interesting, visit the stand at the festival!
</p
>
2259 <title>Easier recipe to observe the cell phones around you
</title>
2260 <link>https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</link>
2261 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Easier_recipe_to_observe_the_cell_phones_around_you.html
</guid>
2262 <pubDate>Sun,
24 Sep
2017 08:
30:
00 +
0200</pubDate>
2263 <description><p
>A little more than a month ago I wrote
2264 <a href=
"http://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
">how
2265 to observe the SIM card ID (aka IMSI number) of mobile phones talking
2266 to nearby mobile phone base stations using Debian GNU/Linux and a
2267 cheap USB software defined radio
</a
>, and thus being able to pinpoint
2268 the location of people and equipment (like cars and trains) with an
2269 accuracy of a few kilometer. Since then we have worked to make the
2270 procedure even simpler, and it is now possible to do this without any
2271 manual frequency tuning and without building your own packages.
</p
>
2273 <p
>The
<a href=
"https://tracker.debian.org/pkg/gr-gsm
">gr-gsm
</a
>
2274 package is now included in Debian testing and unstable, and the
2275 IMSI-catcher code no longer require root access to fetch and decode
2276 the GSM data collected using gr-gsm.
</p
>
2278 <p
>Here is an updated recipe, using packages built by Debian and a git
2279 clone of two python scripts:
</p
>
2283 <li
>Start with a Debian machine running the Buster version (aka
2284 testing).
</li
>
2286 <li
>Run
'<tt
>apt install gr-gsm python-numpy python-scipy
2287 python-scapy
</tt
>' as root to install required packages.
</li
>
2289 <li
>Fetch the code decoding GSM packages using
'<tt
>git clone
2290 github.com/Oros42/IMSI-catcher.git
</tt
>'.
</li
>
2292 <li
>Insert USB software defined radio supported by GNU Radio.
</li
>
2294 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
2295 scan-and-livemon
</tt
>' to locate the frequency of nearby base
2296 stations and start listening for GSM packages on one of them.
</li
>
2298 <li
>Enter the IMSI-catcher directory and run
'<tt
>python
2299 simple_IMSI-catcher.py
</tt
>' to display the collected information.
</li
>
2303 <p
>Note, due to a bug somewhere the scan-and-livemon program (actually
2304 <a href=
"https://github.com/ptrkrysik/gr-gsm/issues/
336">its underlying
2305 program grgsm_scanner
</a
>) do not work with the HackRF radio. It does
2306 work with RTL
8232 and other similar USB radio receivers you can get
2308 (
<a href=
"https://www.ebay.com/sch/items/?_nkw=rtl+
2832">for example
2309 from ebay
</a
>), so for now the solution is to scan using the RTL radio
2310 and only use HackRF for fetching GSM data.
</p
>
2312 <p
>As far as I can tell, a cell phone only show up on one of the
2313 frequencies at the time, so if you are going to track and count every
2314 cell phone around you, you need to listen to all the frequencies used.
2315 To listen to several frequencies, use the --numrecv argument to
2316 scan-and-livemon to use several receivers. Further, I am not sure if
2317 phones using
3G or
4G will show as talking GSM to base stations, so
2318 this approach might not see all phones around you. I typically see
2319 0-
400 IMSI numbers an hour when looking around where I live.
</p
>
2321 <p
>I
've tried to run the scanner on a
2322 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
2 and
3
2323 running Debian Buster
</a
>, but the grgsm_livemon_headless process seem
2324 to be too CPU intensive to keep up. When GNU Radio print
'O
' to
2325 stdout, I am told there it is caused by a buffer overflow between the
2326 radio and GNU Radio, caused by the program being unable to read the
2327 GSM data fast enough. If you see a stream of
'O
's from the terminal
2328 where you started scan-and-livemon, you need a give the process more
2329 CPU power. Perhaps someone are able to optimize the code to a point
2330 where it become possible to set up RPi3 based GSM sniffers? I tried
2331 using Raspbian instead of Debian, but there seem to be something wrong
2332 with GNU Radio on raspbian, causing glibc to abort().
</p
>
2337 <title>Simpler recipe on how to make a simple $
7 IMSI Catcher using Debian
</title>
2338 <link>https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</link>
2339 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Simpler_recipe_on_how_to_make_a_simple__7_IMSI_Catcher_using_Debian.html
</guid>
2340 <pubDate>Wed,
9 Aug
2017 23:
59:
00 +
0200</pubDate>
2341 <description><p
>On friday, I came across an interesting article in the Norwegian
2342 web based ICT news magazine digi.no on
2343 <a href=
"https://www.digi.no/artikler/sikkerhetsforsker-lagde-enkel-imsi-catcher-for-
60-kroner-na-kan-mobiler-kartlegges-av-alle/
398588">how
2344 to collect the IMSI numbers of nearby cell phones
</a
> using the cheap
2345 DVB-T software defined radios. The article refered to instructions
2346 and
<a href=
"https://www.youtube.com/watch?v=UjwgNd_as30
">a recipe by
2347 Keld Norman on Youtube on how to make a simple $
7 IMSI Catcher
</a
>, and I decided to test them out.
</p
>
2349 <p
>The instructions said to use Ubuntu, install pip using apt (to
2350 bypass apt), use pip to install pybombs (to bypass both apt and pip),
2351 and the ask pybombs to fetch and build everything you need from
2352 scratch. I wanted to see if I could do the same on the most recent
2353 Debian packages, but this did not work because pybombs tried to build
2354 stuff that no longer build with the most recent openssl library or
2355 some other version skew problem. While trying to get this recipe
2356 working, I learned that the apt-
>pip-
>pybombs route was a long detour,
2357 and the only piece of software dependency missing in Debian was the
2358 gr-gsm package. I also found out that the lead upstream developer of
2359 gr-gsm (the name stand for GNU Radio GSM) project already had a set of
2360 Debian packages provided in an Ubuntu PPA repository. All I needed to
2361 do was to dget the Debian source package and built it.
</p
>
2363 <p
>The IMSI collector is a python script listening for packages on the
2364 loopback network device and printing to the terminal some specific GSM
2365 packages with IMSI numbers in them. The code is fairly short and easy
2366 to understand. The reason this work is because gr-gsm include a tool
2367 to read GSM data from a software defined radio like a DVB-T USB stick
2368 and other software defined radios, decode them and inject them into a
2369 network device on your Linux machine (using the loopback device by
2370 default). This proved to work just fine, and I
've been testing the
2371 collector for a few days now.
</p
>
2373 <p
>The updated and simpler recipe is thus to
</p
>
2377 <li
>start with a Debian machine running Stretch or newer,
</li
>
2379 <li
>build and install the gr-gsm package available from
2380 <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
>
2382 <li
>clone the git repostory from
<a href=
"https://github.com/Oros42/IMSI-catcher
">https://github.com/Oros42/IMSI-catcher
</a
>,
</li
>
2384 <li
>run grgsm_livemon and adjust the frequency until the terminal
2385 where it was started is filled with a stream of text (meaning you
2386 found a GSM station).
</li
>
2388 <li
>go into the IMSI-catcher directory and run
'sudo python simple_IMSI-catcher.py
' to extract the IMSI numbers.
</li
>
2392 <p
>To make it even easier in the future to get this sniffer up and
2393 running, I decided to package
2394 <a href=
"https://github.com/ptrkrysik/gr-gsm/
">the gr-gsm project
</a
>
2395 for Debian (
<a href=
"https://bugs.debian.org/
871055">WNPP
2396 #
871055</a
>), and the package was uploaded into the NEW queue today.
2397 Luckily the gnuradio maintainer has promised to help me, as I do not
2398 know much about gnuradio stuff yet.
</p
>
2400 <p
>I doubt this
"IMSI cacher
" is anywhere near as powerfull as
2401 commercial tools like
2402 <a href=
"https://www.thespyphone.com/portable-imsi-imei-catcher/
">The
2403 Spy Phone Portable IMSI / IMEI Catcher
</a
> or the
2404 <a href=
"https://en.wikipedia.org/wiki/Stingray_phone_tracker
">Harris
2405 Stingray
</a
>, but I hope the existance of cheap alternatives can make
2406 more people realise how their whereabouts when carrying a cell phone
2407 is easily tracked. Seeing the data flow on the screen, realizing that
2408 I live close to a police station and knowing that the police is also
2409 wearing cell phones, I wonder how hard it would be for criminals to
2410 track the position of the police officers to discover when there are
2411 police near by, or for foreign military forces to track the location
2412 of the Norwegian military forces, or for anyone to track the location
2413 of government officials...
</p
>
2415 <p
>It is worth noting that the data reported by the IMSI-catcher
2416 script mentioned above is only a fraction of the data broadcasted on
2417 the GSM network. It will only collect one frequency at the time,
2418 while a typical phone will be using several frequencies, and not all
2419 phones will be using the frequencies tracked by the grgsm_livemod
2420 program. Also, there is a lot of radio chatter being ignored by the
2421 simple_IMSI-catcher script, which would be collected by extending the
2422 parser code. I wonder if gr-gsm can be set up to listen to more than
2423 one frequency?
</p
>
2428 <title>Norwegian Bokmål edition of Debian Administrator
's Handbook is now available
</title>
2429 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</link>
2430 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_edition_of_Debian_Administrator_s_Handbook_is_now_available.html
</guid>
2431 <pubDate>Tue,
25 Jul
2017 21:
10:
00 +
0200</pubDate>
2432 <description><p align=
"center
"><img align=
"center
" src=
"http://people.skolelinux.org/pere/blog/images/
2017-
07-
25-debian-handbook-nb-testprint.png
"/
></p
>
2434 <p
>I finally received a copy of the Norwegian Bokmål edition of
2435 "<a href=
"https://debian-handbook.info/
">The Debian Administrator
's
2436 Handbook
</a
>". This test copy arrived in the mail a few days ago, and
2437 I am very happy to hold the result in my hand. We spent around one and a half year translating it. This paperbook edition
2438 <a href=
"https://debian-handbook.info/get/#norwegian
">is available
2439 from lulu.com
</a
>. If you buy it quickly, you save
25% on the list
2440 price. The book is also available for download in electronic form as
2441 PDF, EPUB and Mobipocket, as can be
2442 <a href=
"https://debian-handbook.info/browse/nb-NO/stable/
">read online
2443 as a web page
</a
>.
</p
>
2445 <p
>This is the second book I publish (the first was the book
2446 "<a href=
"http://free-culture.cc/
">Free Culture
</a
>" by Lawrence Lessig
2448 <a href=
"http://www.lulu.com/shop/lawrence-lessig/free-culture/paperback/product-
22440520.html
">English
</a
>,
2449 <a href=
"http://www.lulu.com/shop/lawrence-lessig/culture-libre/paperback/product-
22645082.html
">French
</a
>
2451 <a href=
"http://www.lulu.com/shop/lawrence-lessig/fri-kultur/paperback/product-
22441576.html
">Norwegian
2452 Bokmål
</a
>), and I am very excited to finally wrap up this
2454 "<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
2455 for Debian-administratoren
</a
>" will be well received.
</p
>
2460 <title>Når nynorskoversettelsen svikter til eksamen...
</title>
2461 <link>https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</link>
2462 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/N_r_nynorskoversettelsen_svikter_til_eksamen___.html
</guid>
2463 <pubDate>Sat,
3 Jun
2017 08:
20:
00 +
0200</pubDate>
2464 <description><p
><a href=
"http://www.aftenposten.no/norge/Krever-at-elever-ma-fa-annullert-eksamen-etter-rot-med-oppgavetekster-
622459b.html
">Aftenposten
2465 melder i dag
</a
> om feil i eksamensoppgavene for eksamen i politikk og
2466 menneskerettigheter, der teksten i bokmåls og nynorskutgaven ikke var
2467 like. Oppgaveteksten er gjengitt i artikkelen, og jeg ble nysgjerring
2468 på om den fri oversetterløsningen
2469 <a href=
"https://www.apertium.org/
">Apertium
</a
> ville gjort en bedre
2470 jobb enn Utdanningsdirektoratet. Det kan se slik ut.
</p
>
2472 <p
>Her er bokmålsoppgaven fra eksamenen:
</p
>
2475 <p
>Drøft utfordringene knyttet til nasjonalstatenes og andre aktørers
2476 rolle og muligheter til å håndtere internasjonale utfordringer, som
2477 for eksempel flykningekrisen.
</p
>
2479 <p
>Vedlegge er eksempler på tekster som kan gi relevante perspektiver
2480 på temaet:
</p
>
2482 <li
>Flykningeregnskapet
2016, UNHCR og IDMC
2483 <li
>«Grenseløst Europa for fall» A-Magasinet,
26. november
2015
2488 <p
>Dette oversetter Apertium slik:
</p
>
2491 <p
>Drøft utfordringane knytte til nasjonalstatane sine og rolla til
2492 andre aktørar og høve til å handtera internasjonale utfordringar, som
2493 til dømes *flykningekrisen.
</p
>
2495 <p
>Vedleggja er døme på tekster som kan gje relevante perspektiv på
2499 <li
>*Flykningeregnskapet
2016, *UNHCR og *IDMC
</li
>
2500 <li
>«*Grenseløst Europa for fall» A-Magasinet,
26. november
2015</li
>
2505 <p
>Ord som ikke ble forstått er markert med stjerne (*), og trenger
2506 ekstra språksjekk. Men ingen ord er forsvunnet, slik det var i
2507 oppgaven elevene fikk presentert på eksamen. Jeg mistenker dog at
2508 "andre aktørers rolle og muligheter til ...
" burde vært oversatt til
2509 "rolla til andre aktørar og deira høve til ...
" eller noe slikt, men
2510 det er kanskje flisespikking. Det understreker vel bare at det alltid
2511 trengs korrekturlesning etter automatisk oversettelse.
</p
>
2516 <title>Detecting NFS hangs on Linux without hanging yourself...
</title>
2517 <link>https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</link>
2518 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Detecting_NFS_hangs_on_Linux_without_hanging_yourself___.html
</guid>
2519 <pubDate>Thu,
9 Mar
2017 15:
20:
00 +
0100</pubDate>
2520 <description><p
>Over the years, administrating thousand of NFS mounting linux
2521 computers at the time, I often needed a way to detect if the machine
2522 was experiencing NFS hang. If you try to use
<tt
>df
</tt
> or look at a
2523 file or directory affected by the hang, the process (and possibly the
2524 shell) will hang too. So you want to be able to detect this without
2525 risking the detection process getting stuck too. It has not been
2526 obvious how to do this. When the hang has lasted a while, it is
2527 possible to find messages like these in dmesg:
</p
>
2529 <p
><blockquote
>
2530 nfs: server nfsserver not responding, still trying
2531 <br
>nfs: server nfsserver OK
2532 </blockquote
></p
>
2534 <p
>It is hard to know if the hang is still going on, and it is hard to
2535 be sure looking in dmesg is going to work. If there are lots of other
2536 messages in dmesg the lines might have rotated out of site before they
2537 are noticed.
</p
>
2539 <p
>While reading through the nfs client implementation in linux kernel
2540 code, I came across some statistics that seem to give a way to detect
2541 it. The om_timeouts sunrpc value in the kernel will increase every
2542 time the above log entry is inserted into dmesg. And after digging a
2543 bit further, I discovered that this value show up in
2544 /proc/self/mountstats on Linux.
</p
>
2546 <p
>The mountstats content seem to be shared between files using the
2547 same file system context, so it is enough to check one of the
2548 mountstats files to get the state of the mount point for the machine.
2549 I assume this will not show lazy umounted NFS points, nor NFS mount
2550 points in a different process context (ie with a different filesystem
2551 view), but that does not worry me.
</p
>
2553 <p
>The content for a NFS mount point look similar to this:
</p
>
2555 <p
><blockquote
><pre
>
2557 device /dev/mapper/Debian-var mounted on /var with fstype ext3
2558 device nfsserver:/mnt/nfsserver/home0 mounted on /mnt/nfsserver/home0 with fstype nfs statvers=
1.1
2559 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
2561 caps: caps=
0x3fe7,wtmult=
4096,dtsize=
8192,bsize=
0,namlen=
255
2562 sec: flavor=
1,pseudoflavor=
1
2563 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
2564 bytes:
166253035039 219519120027 0 0 40783504807 185466229638 11677877 45561809
2565 RPC iostats version:
1.0 p/v:
100003/
3 (nfs)
2566 xprt: tcp
925 1 6810 0 0 111505412 111480497 109 2672418560317 0 248 53869103 22481820
2568 NULL:
0 0 0 0 0 0 0 0
2569 GETATTR:
61063106 61063108 0 9621383060 6839064400 453650 77291321 78926132
2570 SETATTR:
463469 463470 0 92005440 66739536 63787 603235 687943
2571 LOOKUP:
17021657 17021657 0 3354097764 4013442928 57216 35125459 35566511
2572 ACCESS:
14281703 14290009 5 2318400592 1713803640 1709282 4865144 7130140
2573 READLINK:
125 125 0 20472 18620 0 1112 1118
2574 READ:
4214236 4214237 0 715608524 41328653212 89884 22622768 22806693
2575 WRITE:
8479010 8494376 22 187695798568 1356087148 178264904 51506907 231671771
2576 CREATE:
171708 171708 0 38084748 46702272 873 1041833 1050398
2577 MKDIR:
3680 3680 0 773980 993920 26 23990 24245
2578 SYMLINK:
903 903 0 233428 245488 6 5865 5917
2579 MKNOD:
80 80 0 20148 21760 0 299 304
2580 REMOVE:
429921 429921 0 79796004 61908192 3313 2710416 2741636
2581 RMDIR:
3367 3367 0 645112 484848 22 5782 6002
2582 RENAME:
466201 466201 0 130026184 121212260 7075 5935207 5961288
2583 LINK:
289155 289155 0 72775556 67083960 2199 2565060 2585579
2584 READDIR:
2933237 2933237 0 516506204 13973833412 10385 3190199 3297917
2585 READDIRPLUS:
1652839 1652839 0 298640972 6895997744 84735 14307895 14448937
2586 FSSTAT:
6144 6144 0 1010516 1032192 51 9654 10022
2587 FSINFO:
2 2 0 232 328 0 1 1
2588 PATHCONF:
1 1 0 116 140 0 0 0
2589 COMMIT:
0 0 0 0 0 0 0 0
2591 device binfmt_misc mounted on /proc/sys/fs/binfmt_misc with fstype binfmt_misc
2593 </pre
></blockquote
></p
>
2595 <p
>The key number to look at is the third number in the per-op list.
2596 It is the number of NFS timeouts experiences per file system
2597 operation. Here
22 write timeouts and
5 access timeouts. If these
2598 numbers are increasing, I believe the machine is experiencing NFS
2599 hang. Unfortunately the timeout value do not start to increase right
2600 away. The NFS operations need to time out first, and this can take a
2601 while. The exact timeout value depend on the setup. For example the
2602 defaults for TCP and UDP mount points are quite different, and the
2603 timeout value is affected by the soft, hard, timeo and retrans NFS
2604 mount options.
</p
>
2606 <p
>The only way I have been able to get working on Debian and RedHat
2607 Enterprise Linux for getting the timeout count is to peek in /proc/.
2609 <ahref=
"http://docs.oracle.com/cd/E19253-
01/
816-
4555/netmonitor-
12/index.html
">Solaris
2610 10 System Administration Guide: Network Services
</a
>, the
'nfsstat -c
'
2611 command can be used to get these timeout values. But this do not work
2612 on Linux, as far as I can tell. I
2613 <ahref=
"http://bugs.debian.org/
857043">asked Debian about this
</a
>,
2614 but have not seen any replies yet.
</p
>
2616 <p
>Is there a better way to figure out if a Linux NFS client is
2617 experiencing NFS hangs? Is there a way to detect which processes are
2618 affected? Is there a way to get the NFS mount going quickly once the
2619 network problem causing the NFS hang has been cleared? I would very
2620 much welcome some clues, as we regularly run into NFS hangs.
</p
>
2625 <title>Norwegian Bokmål translation of The Debian Administrator
's Handbook complete, proofreading in progress
</title>
2626 <link>https://people.skolelinux.org/pere/blog/Norwegian_Bokm_l_translation_of_The_Debian_Administrator_s_Handbook_complete__proofreading_in_progress.html
</link>
2627 <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>
2628 <pubDate>Fri,
3 Mar
2017 14:
50:
00 +
0100</pubDate>
2629 <description><p
>For almost a year now, we have been working on making a Norwegian
2630 Bokmål edition of
<a href=
"https://debian-handbook.info/
">The Debian
2631 Administrator
's Handbook
</a
>. Now, thanks to the tireless effort of
2632 Ole-Erik, Ingrid and Andreas, the initial translation is complete, and
2633 we are working on the proof reading to ensure consistent language and
2634 use of correct computer science terms. The plan is to make the book
2635 available on paper, as well as in electronic form. For that to
2636 happen, the proof reading must be completed and all the figures need
2637 to be translated. If you want to help out, get in touch.
</p
>
2639 <p
><a href=
"http://people.skolelinux.org/pere/debian-handbook/debian-handbook-nb-NO.pdf
">A
2641 fresh PDF edition
</a
> in A4 format (the final book will have smaller
2642 pages) of the book created every morning is available for
2643 proofreading. If you find any errors, please
2644 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">visit
2645 Weblate and correct the error
</a
>. The
2646 <a href=
"http://l.github.io/debian-handbook/stat/nb-NO/index.html
">state
2647 of the translation including figures
</a
> is a useful source for those
2648 provide Norwegian bokmål screen shots and figures.
</p
>
2653 <title>Unlimited randomness with the ChaosKey?
</title>
2654 <link>https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</link>
2655 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlimited_randomness_with_the_ChaosKey_.html
</guid>
2656 <pubDate>Wed,
1 Mar
2017 20:
50:
00 +
0100</pubDate>
2657 <description><p
>A few days ago I ordered a small batch of
2658 <a href=
"http://altusmetrum.org/ChaosKey/
">the ChaosKey
</a
>, a small
2659 USB dongle for generating entropy created by Bdale Garbee and Keith
2660 Packard. Yesterday it arrived, and I am very happy to report that it
2661 work great! According to its designers, to get it to work out of the
2662 box, you need the Linux kernel version
4.1 or later. I tested on a
2663 Debian Stretch machine (kernel version
4.9), and there it worked just
2664 fine, increasing the available entropy very quickly. I wrote a small
2665 test oneliner to test. It first print the current entropy level,
2666 drain /dev/random, and then print the entropy level for five seconds.
2667 Here is the situation without the ChaosKey inserted:
</p
>
2669 <blockquote
><pre
>
2670 % cat /proc/sys/kernel/random/entropy_avail; \
2671 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
2672 for n in $(seq
1 5); do \
2673 cat /proc/sys/kernel/random/entropy_avail; \
2679 28 byte kopiert,
0,
000264565 s,
106 kB/s
2686 </pre
></blockquote
>
2688 <p
>The entropy level increases by
3-
4 every second. In such case any
2689 application requiring random bits (like a HTTPS enabled web server)
2690 will halt and wait for more entrpy. And here is the situation with
2691 the ChaosKey inserted:
</p
>
2693 <blockquote
><pre
>
2694 % cat /proc/sys/kernel/random/entropy_avail; \
2695 dd bs=
1M if=/dev/random of=/dev/null count=
1; \
2696 for n in $(seq
1 5); do \
2697 cat /proc/sys/kernel/random/entropy_avail; \
2703 104 byte kopiert,
0,
000487647 s,
213 kB/s
2710 </pre
></blockquote
>
2712 <p
>Quite the difference. :) I bought a few more than I need, in case
2713 someone want to buy one here in Norway. :)
</p
>
2715 <p
>Update: The dongle was presented at Debconf last year. You might
2716 find
<a href=
"https://debconf16.debconf.org/talks/
94/
">the talk
2717 recording illuminating
</a
>. It explains exactly what the source of
2718 randomness is, if you are unable to spot it from the schema drawing
2719 available from the ChaosKey web site linked at the start of this blog
2725 <title>Where did that package go?
&mdash; geolocated IP traceroute
</title>
2726 <link>https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</link>
2727 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Where_did_that_package_go___mdash__geolocated_IP_traceroute.html
</guid>
2728 <pubDate>Mon,
9 Jan
2017 12:
20:
00 +
0100</pubDate>
2729 <description><p
>Did you ever wonder where the web trafic really flow to reach the
2730 web servers, and who own the network equipment it is flowing through?
2731 It is possible to get a glimpse of this from using traceroute, but it
2732 is hard to find all the details. Many years ago, I wrote a system to
2733 map the Norwegian Internet (trying to figure out if our plans for a
2734 network game service would get low enough latency, and who we needed
2735 to talk to about setting up game servers close to the users. Back
2736 then I used traceroute output from many locations (I asked my friends
2737 to run a script and send me their traceroute output) to create the
2738 graph and the map. The output from traceroute typically look like
2741 <p
><pre
>
2742 traceroute to www.stortinget.no (
85.88.67.10),
30 hops max,
60 byte packets
2743 1 uio-gw10.uio.no (
129.240.202.1)
0.447 ms
0.486 ms
0.621 ms
2744 2 uio-gw8.uio.no (
129.240.24.229)
0.467 ms
0.578 ms
0.675 ms
2745 3 oslo-gw1.uninett.no (
128.39.65.17)
0.385 ms
0.373 ms
0.358 ms
2746 4 te3-
1-
2.br1.fn3.as2116.net (
193.156.90.3)
1.174 ms
1.172 ms
1.153 ms
2747 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
2748 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
2749 7 89.191.10.146 (
89.191.10.146)
0.931 ms
0.917 ms
0.955 ms
2753 </pre
></p
>
2755 <p
>This show the DNS names and IP addresses of (at least some of the)
2756 network equipment involved in getting the data traffic from me to the
2757 www.stortinget.no server, and how long it took in milliseconds for a
2758 package to reach the equipment and return to me. Three packages are
2759 sent, and some times the packages do not follow the same path. This
2760 is shown for hop
5, where three different IP addresses replied to the
2761 traceroute request.
</p
>
2763 <p
>There are many ways to measure trace routes. Other good traceroute
2764 implementations I use are traceroute (using ICMP packages) mtr (can do
2765 both ICMP, UDP and TCP) and scapy (python library with ICMP, UDP, TCP
2766 traceroute and a lot of other capabilities). All of them are easily
2767 available in
<a href=
"https://www.debian.org/
">Debian
</a
>.
</p
>
2769 <p
>This time around, I wanted to know the geographic location of
2770 different route points, to visualize how visiting a web page spread
2771 information about the visit to a lot of servers around the globe. The
2772 background is that a web site today often will ask the browser to get
2773 from many servers the parts (for example HTML, JSON, fonts,
2774 JavaScript, CSS, video) required to display the content. This will
2775 leak information about the visit to those controlling these servers
2776 and anyone able to peek at the data traffic passing by (like your ISP,
2777 the ISPs backbone provider, FRA, GCHQ, NSA and others).
</p
>
2779 <p
>Lets pick an example, the Norwegian parliament web site
2780 www.stortinget.no. It is read daily by all members of parliament and
2781 their staff, as well as political journalists, activits and many other
2782 citizens of Norway. A visit to the www.stortinget.no web site will
2783 ask your browser to contact
8 other servers: ajax.googleapis.com,
2784 insights.hotjar.com, script.hotjar.com, static.hotjar.com,
2785 stats.g.doubleclick.net, www.google-analytics.com,
2786 www.googletagmanager.com and www.netigate.se. I extracted this by
2787 asking
<a href=
"http://phantomjs.org/
">PhantomJS
</a
> to visit the
2788 Stortinget web page and tell me all the URLs PhantomJS downloaded to
2789 render the page (in HAR format using
2790 <a href=
"https://github.com/ariya/phantomjs/blob/master/examples/netsniff.js
">their
2791 netsniff example
</a
>. I am very grateful to Gorm for showing me how
2792 to do this). My goal is to visualize network traces to all IP
2793 addresses behind these DNS names, do show where visitors personal
2794 information is spread when visiting the page.
</p
>
2796 <p align=
"center
"><a href=
"www.stortinget.no-geoip.kml
"><img
2797 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
>
2799 <p
>When I had a look around for options, I could not find any good
2800 free software tools to do this, and decided I needed my own traceroute
2801 wrapper outputting KML based on locations looked up using GeoIP. KML
2802 is easy to work with and easy to generate, and understood by several
2803 of the GIS tools I have available. I got good help from by NUUG
2804 colleague Anders Einar with this, and the result can be seen in
2805 <a href=
"https://github.com/petterreinholdtsen/kmltraceroute
">my
2806 kmltraceroute git repository
</a
>. Unfortunately, the quality of the
2807 free GeoIP databases I could find (and the for-pay databases my
2808 friends had access to) is not up to the task. The IP addresses of
2809 central Internet infrastructure would typically be placed near the
2810 controlling companies main office, and not where the router is really
2811 located, as you can see from
<a href=
"www.stortinget.no-geoip.kml
">the
2812 KML file I created
</a
> using the GeoLite City dataset from MaxMind.
2814 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
"><img
2815 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
>
2817 <p
>I also had a look at the visual traceroute graph created by
2818 <a href=
"http://www.secdev.org/projects/scapy/
">the scrapy project
</a
>,
2819 showing IP network ownership (aka AS owner) for the IP address in
2821 <a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-scapy.svg
">The
2822 graph display a lot of useful information about the traceroute in SVG
2823 format
</a
>, and give a good indication on who control the network
2824 equipment involved, but it do not include geolocation. This graph
2825 make it possible to see the information is made available at least for
2826 UNINETT, Catchcom, Stortinget, Nordunet, Google, Amazon, Telia, Level
2827 3 Communications and NetDNA.
</p
>
2829 <p align=
"center
"><a href=
"https://geotraceroute.com/index.php?node=
4&host=www.stortinget.no
"><img
2830 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
>
2832 <p
>In the process, I came across the
2833 <a href=
"https://geotraceroute.com/
">web service GeoTraceroute
</a
> by
2834 Salim Gasmi. Its methology of combining guesses based on DNS names,
2835 various location databases and finally use latecy times to rule out
2836 candidate locations seemed to do a very good job of guessing correct
2837 geolocation. But it could only do one trace at the time, did not have
2838 a sensor in Norway and did not make the geolocations easily available
2839 for postprocessing. So I contacted the developer and asked if he
2840 would be willing to share the code (he refused until he had time to
2841 clean it up), but he was interested in providing the geolocations in a
2842 machine readable format, and willing to set up a sensor in Norway. So
2843 since yesterday, it is possible to run traces from Norway in this
2844 service thanks to a sensor node set up by
2845 <a href=
"https://www.nuug.no/
">the NUUG assosiation
</a
>, and get the
2846 trace in KML format for further processing.
</p
>
2848 <p align=
"center
"><a href=
"http://people.skolelinux.org/pere/blog/images/
2017-
01-
09-www.stortinget.no-geotraceroute-kml-join.kml
"><img
2849 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
>
2851 <p
>Here we can see a lot of trafic passes Sweden on its way to
2852 Denmark, Germany, Holland and Ireland. Plenty of places where the
2853 Snowden confirmations verified the traffic is read by various actors
2854 without your best interest as their top priority.
</p
>
2856 <p
>Combining KML files is trivial using a text editor, so I could loop
2857 over all the hosts behind the urls imported by www.stortinget.no and
2858 ask for the KML file from GeoTraceroute, and create a combined KML
2859 file with all the traces (unfortunately only one of the IP addresses
2860 behind the DNS name is traced this time. To get them all, one would
2861 have to request traces using IP number instead of DNS names from
2862 GeoTraceroute). That might be the next step in this project.
</p
>
2864 <p
>Armed with these tools, I find it a lot easier to figure out where
2865 the IP traffic moves and who control the boxes involved in moving it.
2866 And every time the link crosses for example the Swedish border, we can
2867 be sure Swedish Signal Intelligence (FRA) is listening, as GCHQ do in
2868 Britain and NSA in USA and cables around the globe. (Hm, what should
2869 we tell them? :) Keep that in mind if you ever send anything
2870 unencrypted over the Internet.
</p
>
2872 <p
>PS: KML files are drawn using
2873 <a href=
"http://ivanrublev.me/kml/
">the KML viewer from Ivan
2874 Rublev
<a/
>, as it was less cluttered than the local Linux application
2875 Marble. There are heaps of other options too.
</p
>
2877 <p
>As usual, if you use Bitcoin and want to show your support of my
2878 activities, please send Bitcoin donations to my address
2879 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2884 <title>Appstream just learned how to map hardware to packages too!
</title>
2885 <link>https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</link>
2886 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Appstream_just_learned_how_to_map_hardware_to_packages_too_.html
</guid>
2887 <pubDate>Fri,
23 Dec
2016 10:
30:
00 +
0100</pubDate>
2888 <description><p
>I received a very nice Christmas present today. As my regular
2889 readers probably know, I have been working on the
2890 <a href=
"http://packages.qa.debian.org/isenkram
">the Isenkram
2891 system
</a
> for many years. The goal of the Isenkram system is to make
2892 it easier for users to figure out what to install to get a given piece
2893 of hardware to work in Debian, and a key part of this system is a way
2894 to map hardware to packages. Isenkram have its own mapping database,
2895 and also uses data provided by each package using the AppStream
2896 metadata format. And today,
2897 <a href=
"https://tracker.debian.org/pkg/appstream
">AppStream
</a
> in
2898 Debian learned to look up hardware the same way Isenkram is doing it,
2899 ie using fnmatch():
</p
>
2901 <p
><pre
>
2902 % appstreamcli what-provides modalias \
2903 usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2904 Identifier: pymissile [generic]
2906 Summary: Control original Striker USB Missile Launcher
2908 % appstreamcli what-provides modalias usb:v0694p0002d0000
2909 Identifier: libnxt [generic]
2911 Summary: utility library for talking to the LEGO Mindstorms NXT brick
2914 Identifier: t2n [generic]
2916 Summary: Simple command-line tool for Lego NXT
2919 Identifier: python-nxt [generic]
2921 Summary: Python driver/interface/wrapper for the Lego Mindstorms NXT robot
2924 Identifier: nbc [generic]
2926 Summary: C compiler for LEGO Mindstorms NXT bricks
2929 </pre
></p
>
2931 <p
>A similar query can be done using the combined AppStream and
2932 Isenkram databases using the isenkram-lookup tool:
</p
>
2934 <p
><pre
>
2935 % isenkram-lookup usb:v1130p0202d0100dc00dsc00dp00ic03isc00ip00in00
2937 % isenkram-lookup usb:v0694p0002d0000
2943 </pre
></p
>
2945 <p
>You can find modalias values relevant for your machine using
2946 <tt
>cat $(find /sys/devices/ -name modalias)
</tt
>.
2948 <p
>If you want to make this system a success and help Debian users
2949 make the most of the hardware they have, please
2950 help
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">add
2951 AppStream metadata for your package following the guidelines
</a
>
2952 documented in the wiki. So far only
11 packages provide such
2953 information, among the several hundred hardware specific packages in
2954 Debian. The Isenkram database on the other hand contain
101 packages,
2955 mostly related to USB dongles. Most of the packages with hardware
2956 mapping in AppStream are LEGO Mindstorms related, because I have, as
2957 part of my involvement in
2958 <a href=
"https://wiki.debian.org/LegoDesigners
">the Debian LEGO
2959 team
</a
> given priority to making sure LEGO users get proposed the
2960 complete set of packages in Debian for that particular hardware. The
2961 team also got a nice Christmas present today. The
2962 <a href=
"https://tracker.debian.org/pkg/nxt-firmware
">nxt-firmware
2963 package
</a
> made it into Debian. With this package in place, it is
2964 now possible to use the LEGO Mindstorms NXT unit with only free
2965 software, as the nxt-firmware package contain the source and firmware
2966 binaries for the NXT brick.
</p
>
2968 <p
>As usual, if you use Bitcoin and want to show your support of my
2969 activities, please send Bitcoin donations to my address
2970 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
2975 <title>Isenkram updated with a lot more hardware-package mappings
</title>
2976 <link>https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</link>
2977 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_updated_with_a_lot_more_hardware_package_mappings.html
</guid>
2978 <pubDate>Tue,
20 Dec
2016 11:
55:
00 +
0100</pubDate>
2979 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
2980 system
</a
> I wrote two years ago to make it easier in Debian to find
2981 and install packages to get your hardware dongles to work, is still
2982 going strong. It is a system to look up the hardware present on or
2983 connected to the current system, and map the hardware to Debian
2984 packages. It can either be done using the tools in isenkram-cli or
2985 using the user space daemon in the isenkram package. The latter will
2986 notify you, when inserting new hardware, about what packages to
2987 install to get the dongle working. It will even provide a button to
2988 click on to ask packagekit to install the packages.
</p
>
2990 <p
>Here is an command line example from my Thinkpad laptop:
</p
>
2992 <p
><pre
>
3009 </pre
></p
>
3011 <p
>It can also list the firware package providing firmware requested
3012 by the load kernel modules, which in my case is an empty list because
3013 I have all the firmware my machine need:
3015 <p
><pre
>
3016 % /usr/sbin/isenkram-autoinstall-firmware -l
3017 info: did not find any firmware files requested by loaded kernel modules. exiting
3019 </pre
></p
>
3021 <p
>The last few days I had a look at several of the around
250
3022 packages in Debian with udev rules. These seem like good candidates
3023 to install when a given hardware dongle is inserted, and I found
3024 several that should be proposed by isenkram. I have not had time to
3025 check all of them, but am happy to report that now there are
97
3026 packages packages mapped to hardware by Isenkram.
11 of these
3027 packages provide hardware mapping using AppStream, while the rest are
3028 listed in the modaliases file provided in isenkram.
</p
>
3030 <p
>These are the packages with hardware mappings at the moment. The
3031 <strong
>marked packages
</strong
> are also announcing their hardware
3032 support using AppStream, for everyone to use:
</p
>
3034 <p
>air-quality-sensor, alsa-firmware-loaders, argyll,
3035 <strong
>array-info
</strong
>, avarice, avrdude, b43-fwcutter,
3036 bit-babbler, bluez, bluez-firmware,
<strong
>brltty
</strong
>,
3037 <strong
>broadcom-sta-dkms
</strong
>, calibre, cgminer, cheese, colord,
3038 <strong
>colorhug-client
</strong
>, dahdi-firmware-nonfree, dahdi-linux,
3039 dfu-util, dolphin-emu, ekeyd, ethtool, firmware-ipw2x00, fprintd,
3040 fprintd-demo,
<strong
>galileo
</strong
>, gkrellm-thinkbat, gphoto2,
3041 gpsbabel, gpsbabel-gui, gpsman, gpstrans, gqrx-sdr, gr-fcdproplus,
3042 gr-osmosdr, gtkpod, hackrf, hdapsd, hdmi2usb-udev, hpijs-ppds, hplip,
3043 ipw3945-source, ipw3945d, kde-config-tablet, kinect-audio-setup,
3044 <strong
>libnxt
</strong
>, libpam-fprintd,
<strong
>lomoco
</strong
>,
3045 madwimax, minidisc-utils, mkgmap, msi-keyboard, mtkbabel,
3046 <strong
>nbc
</strong
>,
<strong
>nqc
</strong
>, nut-hal-drivers, ola,
3047 open-vm-toolbox, open-vm-tools, openambit, pcgminer, pcmciautils,
3048 pcscd, pidgin-blinklight, printer-driver-splix,
3049 <strong
>pymissile
</strong
>, python-nxt, qlandkartegt,
3050 qlandkartegt-garmin, rosegarden, rt2x00-source, sispmctl,
3051 soapysdr-module-hackrf, solaar, squeak-plugins-scratch, sunxi-tools,
3052 <strong
>t2n
</strong
>, thinkfan, thinkfinger-tools, tlp, tp-smapi-dkms,
3053 tp-smapi-source, tpb, tucnak, uhd-host, usbmuxd, viking,
3054 virtualbox-ose-guest-x11, w1retap, xawtv, xserver-xorg-input-vmmouse,
3055 xserver-xorg-input-wacom, xserver-xorg-video-qxl,
3056 xserver-xorg-video-vmware, yubikey-personalization and
3057 zd1211-firmware
</p
>
3059 <p
>If you know of other packages, please let me know with a wishlist
3060 bug report against the isenkram-cli package, and ask the package
3062 <a href=
"https://wiki.debian.org/AppStream/Guidelines
">add AppStream
3063 metadata according to the guidelines
</a
> to provide the information
3064 for everyone. In time, I hope to get rid of the isenkram specific
3065 hardware mapping and depend exclusively on AppStream.
</p
>
3067 <p
>Note, the AppStream metadata for broadcom-sta-dkms is matching too
3068 much hardware, and suggest that the package with with any ethernet
3069 card. See
<a href=
"http://bugs.debian.org/
838735">bug #
838735</a
> for
3070 the details. I hope the maintainer find time to address it soon. In
3071 the mean time I provide an override in isenkram.
</p
>
3076 <title>Oolite, a life in space as vagabond and mercenary - nice free software
</title>
3077 <link>https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</link>
3078 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oolite__a_life_in_space_as_vagabond_and_mercenary___nice_free_software.html
</guid>
3079 <pubDate>Sun,
11 Dec
2016 11:
40:
00 +
0100</pubDate>
3080 <description><p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
12-
11-nice-oolite.png
"/
></p
>
3082 <p
>In my early years, I played
3083 <a href=
"http://wiki.alioth.net/index.php/Classic_Elite
">the epic game
3084 Elite
</a
> on my PC. I spent many months trading and fighting in
3085 space, and reached the
'elite
' fighting status before I moved on. The
3086 original Elite game was available on Commodore
64 and the IBM PC
3087 edition I played had a
64 KB executable. I am still impressed today
3088 that the authors managed to squeeze both a
3D engine and details about
3089 more than
2000 planet systems across
7 galaxies into a binary so
3092 <p
>I have known about
<a href=
"http://www.oolite.org/
">the free
3093 software game Oolite inspired by Elite
</a
> for a while, but did not
3094 really have time to test it properly until a few days ago. It was
3095 great to discover that my old knowledge about trading routes were
3096 still valid. But my fighting and flying abilities were gone, so I had
3097 to retrain to be able to dock on a space station. And I am still not
3098 able to make much resistance when I am attacked by pirates, so I
3099 bougth and mounted the most powerful laser in the rear to be able to
3100 put up at least some resistance while fleeing for my life. :)
</p
>
3102 <p
>When playing Elite in the late eighties, I had to discover
3103 everything on my own, and I had long lists of prices seen on different
3104 planets to be able to decide where to trade what. This time I had the
3106 <a href=
"http://wiki.alioth.net/index.php/Main_Page
">Elite wiki
</a
>,
3107 where information about each planet is easily available with common
3108 price ranges and suggested trading routes. This improved my ability
3109 to earn money and I have been able to earn enough to buy a lot of
3110 useful equipent in a few days. I believe I originally played for
3111 months before I could get a docking computer, while now I could get it
3112 after less then a week.
</p
>
3114 <p
>If you like science fiction and dreamed of a life as a vagabond in
3115 space, you should try out Oolite. It is available for Linux, MacOSX
3116 and Windows, and is included in Debian and derivatives since
2011.
</p
>
3118 <p
>As usual, if you use Bitcoin and want to show your support of my
3119 activities, please send Bitcoin donations to my address
3120 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3125 <title>Quicker Debian installations using eatmydata
</title>
3126 <link>https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</link>
3127 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Quicker_Debian_installations_using_eatmydata.html
</guid>
3128 <pubDate>Fri,
25 Nov
2016 14:
50:
00 +
0100</pubDate>
3129 <description><p
>Two years ago, I did some experiments with eatmydata and the Debian
3130 installation system, observing how using
3131 <a href=
"http://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
">eatmydata
3132 could speed up the installation
</a
> quite a bit. My testing measured
3133 speedup around
20-
40 percent for Debian Edu, where we install around
3134 1000 packages from within the installer. The eatmydata package
3135 provide a way to disable/delay file system flushing. This is a bit
3136 risky in the general case, as files that should be stored on disk will
3137 stay only in memory a bit longer than expected, causing problems if a
3138 machine crashes at an inconvenient time. But for an installation, if
3139 the machine crashes during installation the process is normally
3140 restarted, and avoiding disk operations as much as possible to speed
3141 up the process make perfect sense.
3143 <p
>I added code in the Debian Edu specific installation code to enable
3144 <a href=
"https://tracker.debian.org/pkg/libeatmydata
">eatmydata
</a
>,
3145 but did not have time to push it any further. But a few months ago I
3146 picked it up again and worked with the libeatmydata package maintainer
3147 Mattia Rizzolo to make it easier for everyone to get this installation
3148 speedup in Debian. Thanks to our cooperation There is now an
3149 eatmydata-udeb package in Debian testing and unstable, and simply
3150 enabling/installing it in debian-installer (d-i) is enough to get the
3151 quicker installations. It can be enabled using preseeding. The
3152 following untested kernel argument should do the trick:
</p
>
3154 <blockquote
><pre
>
3155 preseed/early_command=
"anna-install eatmydata-udeb
"
3156 </pre
></blockquote
>
3158 <p
>This should ask d-i to install the package inside the d-i
3159 environment early in the installation sequence. Having it installed
3160 in d-i in turn will make sure the relevant scripts are called just
3161 after debootstrap filled /target/ with the freshly installed Debian
3162 system to configure apt to run dpkg with eatmydata. This is enough to
3163 speed up the installation process. There is a proposal to
3164 <a href=
"https://bugs.debian.org/
841153">extend the idea a bit further
3165 by using /etc/ld.so.preload instead of apt.conf
</a
>, but I have not
3166 tested its impact.
</p
>
3172 <title>Oversette bokmål til nynorsk, enklere enn du tror takket være Apertium
</title>
3173 <link>https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</link>
3174 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Oversette_bokm_l_til_nynorsk__enklere_enn_du_tror_takket_v_re_Apertium.html
</guid>
3175 <pubDate>Thu,
24 Nov
2016 10:
50:
00 +
0100</pubDate>
3176 <description><p
>I Norge er det mange som trenger å skrive både bokmål og nynorsk.
3177 Eksamensoppgaver, offentlige brev og nyheter er eksempler på tekster
3178 der det er krav om skriftspråk. I tillegg til alle skoleoppgavene som
3179 elever over det ganske land skal levere inn hvert år. Det mange ikke
3180 vet er at selv om de kommersielle alternativene
3181 <a href=
"https://translate.google.com/
">Google Translate
</a
> og
3182 <a href=
"https://www.bing.com/translator/
">Bing Translator
</a
> ikke kan
3183 bidra med å oversette mellom bokmål og nynorsk, så finnes det et
3184 utmerket fri programvarealternativ som kan. Oversetterverktøyet
3185 Apertium har støtte for en rekke språkkombinasjoner, og takket være
3186 den utrettelige innsatsen til blant annet Kevin Brubeck Unhammer, kan
3187 en bruke webtjenesten til å fylle inn en tekst på bokmål eller
3188 nynorsk, og få den automatoversatt til det andre skriftspråket.
3189 Resultatet er ikke perfekt, men et svært godt utgangspunkt. Av og til
3190 er resultatet så bra at det kan benyttes uten endringer. Jeg vet
3191 f.eks. at store deler av Joomla ble oversatt til nynorsk ved hjelp
3192 Apertium. Høres det ut som noe du kan ha bruk for? Besøk i så fall
3193 <a href=
"https://www.apertium.org/
">Apertium.org
</a
> og fyll inn
3194 teksten din i webskjemaet der.
3196 <p
>Hvis du trenger maskinell tilgang til den bakenforliggende
3197 teknologien kan du enten installere pakken
3198 <a href=
"https://tracker.debian.org/apertium-nno-nob
">apertium-nno-nob
</a
>
3199 på en Debian-maskin eller bruke web-API-et tilgjengelig fra
3200 api.apertium.org. Se
3201 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">API-dokumentasjonen
</a
>
3202 for detaljer om web-API-et. Her kan du se hvordan resultatet blir for
3203 denne teksten som ble skrevet på bokmål over maskinoversatt til
3208 <p
>I Noreg er det mange som treng å skriva både bokmål og nynorsk.
3209 Eksamensoppgåver, offentlege brev og nyhende er døme på tekster der
3210 det er krav om skriftspråk. I tillegg til alle skuleoppgåvene som
3211 elevar over det ganske land skal levera inn kvart år. Det mange ikkje
3212 veit er at sjølv om dei kommersielle alternativa
3213 <a href=
"https://translate.google.com/
">Google *Translate
</a
> og
3214 <a href=
"https://www.bing.com/translator/
">Bing *Translator
</a
> ikkje
3215 kan bidra med å omsetja mellom bokmål og nynorsk, så finst det eit
3216 utmerka fri programvarealternativ som kan. Omsetjarverktøyet
3217 *Apertium har støtte for ei rekkje språkkombinasjonar, og takka vera
3218 den utrøyttelege innsatsen til blant anna Kevin Brubeck Unhammer, kan
3219 ein bruka *webtjenesten til å fylla inn ei tekst på bokmål eller
3220 nynorsk, og få den *automatoversatt til det andre skriftspråket.
3221 Resultatet er ikkje perfekt, men eit svært godt utgangspunkt. Av og
3222 til er resultatet så bra at det kan nyttast utan endringar. Eg veit
3223 t.d. at store delar av *Joomla vart omsett til nynorsk ved hjelp
3224 *Apertium. Høyrast det ut som noko du kan ha bruk for? Besøk i så
3225 fall
<a href=
"https://www.apertium.org/
">*Apertium.org
</a
> og fyll inn
3226 teksta di i *webskjemaet der.
3228 <p
>Viss du treng *maskinell tilgjenge til den *bakenforliggende
3229 teknologien kan du anten installera pakken
3230 <a href=
"https://tracker.debian.org/apertium-nno-nob
">*apertium-*nno-*nob
</a
>
3231 på ein *Debian-maskin eller bruka *web-*API-eit tilgjengeleg frå
3232 *api.*apertium.org. Sjå
3233 <a href=
"http://wiki.apertium.org/wiki/Apertium-apy
">*API-dokumentasjonen
</a
>
3234 for detaljar om *web-*API-eit. Her kan du sjå korleis resultatet vert
3235 for denne teksta som vart skreva på bokmål over *maskinoversatt til
3241 <title>Coz profiler for multi-threaded software is now in Debian
</title>
3242 <link>https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</link>
3243 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_profiler_for_multi_threaded_software_is_now_in_Debian.html
</guid>
3244 <pubDate>Sun,
13 Nov
2016 12:
30:
00 +
0100</pubDate>
3245 <description><p
><a href=
"http://coz-profiler.org/
">The Coz profiler
</a
>, a nice
3246 profiler able to run benchmarking experiments on the instrumented
3247 multi-threaded program, finally
3248 <a href=
"https://tracker.debian.org/pkg/coz-profiler
">made it into
3249 Debian unstable yesterday
</A
>. Lluís Vilanova and I have spent many
3251 <a href=
"http://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
">I
3252 blogged about the coz tool
</a
> in August working with upstream to make
3253 it suitable for Debian. There are still issues with clang
3254 compatibility, inline assembly only working x86 and minimized
3255 JavaScript libraries.
</p
>
3257 <p
>To test it, install
'coz-profiler
' using apt and run it like this:
</p
>
3259 <p
><blockquote
>
3260 <tt
>coz run --- /path/to/binary-with-debug-info
</tt
>
3261 </blockquote
></p
>
3263 <p
>This will produce a profile.coz file in the current working
3264 directory with the profiling information. This is then given to a
3265 JavaScript application provided in the package and available from
3266 <a href=
"http://plasma-umass.github.io/coz/
">a project web page
</a
>.
3267 To start the local copy, invoke it in a browser like this:
</p
>
3269 <p
><blockquote
>
3270 <tt
>sensible-browser /usr/share/coz-profiler/viewer/index.htm
</tt
>
3271 </blockquote
></p
>
3273 <p
>See the project home page and the
3274 <a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">USENIX
3275 ;login: article on Coz
</a
> for more information on how it is
3281 <title>My own self balancing Lego Segway
</title>
3282 <link>https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</link>
3283 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/My_own_self_balancing_Lego_Segway.html
</guid>
3284 <pubDate>Fri,
4 Nov
2016 10:
15:
00 +
0100</pubDate>
3285 <description><p
>A while back I received a Gyro sensor for the NXT
3286 <a href=
"mindstorms.lego.com
">Mindstorms
</a
> controller as a birthday
3287 present. It had been on my wishlist for a while, because I wanted to
3288 build a Segway like balancing lego robot. I had already built
3289 <a href=
"http://www.nxtprograms.com/NXT2/segway/
">a simple balancing
3290 robot
</a
> with the kids, using the light/color sensor included in the
3291 NXT kit as the balance sensor, but it was not working very well. It
3292 could balance for a while, but was very sensitive to the light
3293 condition in the room and the reflective properties of the surface and
3294 would fall over after a short while. I wanted something more robust,
3296 <a href=
"https://www.hitechnic.com/cgi-bin/commerce.cgi?preadd=action
&key=NGY1044
">the
3297 gyro sensor from HiTechnic
</a
> I believed would solve it on my
3298 wishlist for some years before it suddenly showed up as a gift from my
3299 loved ones. :)
</p
>
3301 <p
>Unfortunately I have not had time to sit down and play with it
3302 since then. But that changed some days ago, when I was searching for
3303 lego segway information and came across a recipe from HiTechnic for
3305 <a href=
"http://www.hitechnic.com/blog/gyro-sensor/htway/
">the
3306 HTWay
</a
>, a segway like balancing robot. Build instructions and
3307 <a href=
"https://www.hitechnic.com/upload/
786-HTWayC.nxc
">source
3308 code
</a
> was included, so it was just a question of putting it all
3309 together. And thanks to the great work of many Debian developers, the
3310 compiler needed to build the source for the NXT is already included in
3311 Debian, so I was read to go in less than an hour. The resulting robot
3312 do not look very impressive in its simplicity:
</p
>
3314 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-robot.jpeg
"></p
>
3316 <p
>Because I lack the infrared sensor used to control the robot in the
3317 design from HiTechnic, I had to comment out the last task
3318 (taskControl). I simply placed /* and */ around it get the program
3319 working without that sensor present. Now it balances just fine until
3320 the battery status run low:
</p
>
3322 <p align=
"center
"><video width=
"70%
" controls=
"true
">
3323 <source src=
"http://people.skolelinux.org/pere/blog/images/
2016-
11-
04-lego-htway-balancing.ogv
" type=
"video/ogg
">
3324 </video
></p
>
3326 <p
>Now we would like to teach it how to follow a line and take remote
3327 control instructions using the included Bluetooth receiver in the NXT.
</p
>
3329 <p
>If you, like me, love LEGO and want to make sure we find the tools
3330 they need to work with LEGO in Debian and all our derivative
3331 distributions like Ubuntu, check out
3332 <a href=
"http://wiki.debian.org/LegoDesigners
">the LEGO designers
3333 project page
</a
> and join the Debian LEGO team. Personally I own a
3334 RCX and NXT controller (no EV3), and would like to make sure the
3335 Debian tools needed to program the systems I own work as they
3341 <title>Experience and updated recipe for using the Signal app without a mobile phone
</title>
3342 <link>https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</link>
3343 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
</guid>
3344 <pubDate>Mon,
10 Oct
2016 11:
30:
00 +
0200</pubDate>
3345 <description><p
>In July
3346 <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
3347 wrote how to get the Signal Chrome/Chromium app working
</a
> without
3348 the ability to receive SMS messages (aka without a cell phone). It is
3349 time to share some experiences and provide an updated setup.
</p
>
3351 <p
>The Signal app have worked fine for several months now, and I use
3352 it regularly to chat with my loved ones. I had a major snag at the
3353 end of my summer vacation, when the the app completely forgot my
3354 setup, identity and keys. The reason behind this major mess was
3355 running out of disk space. To avoid that ever happening again I have
3356 started storing everything in
<tt
>userdata/
</tt
> in git, to be able to
3357 roll back to an earlier version if the files are wiped by mistake. I
3358 had to use it once after introducing the git backup. When rolling
3359 back to an earlier version, one need to use the
'reset session
' option
3360 in Signal to get going, and notify the people you talk with about the
3361 problem. I assume there is some sequence number tracking in the
3362 protocol to detect rollback attacks. The git repository is rather big
3363 (
674 MiB so far), but I have not tried to figure out if some of the
3364 content can be added to a .gitignore file due to lack of spare
3367 <p
>I
've also hit the
90 days timeout blocking, and noticed that this
3368 make it impossible to send messages using Signal. I could still
3369 receive them, but had to patch the code with a new timestamp to send.
3370 I believe the timeout is added by the developers to force people to
3371 upgrade to the latest version of the app, even when there is no
3372 protocol changes, to reduce the version skew among the user base and
3373 thus try to keep the number of support requests down.
</p
>
3375 <p
>Since my original recipe, the Signal source code changed slightly,
3376 making the old patch fail to apply cleanly. Below is an updated
3377 patch, including the shell wrapper I use to start Signal. The
3378 original version required a new user to locate the JavaScript console
3379 and call a function from there. I got help from a friend with more
3380 JavaScript knowledge than me to modify the code to provide a GUI
3381 button instead. This mean that to get started you just need to run
3382 the wrapper and click the
'Register without mobile phone
' to get going
3383 now. I
've also modified the timeout code to always set it to
90 days
3384 in the future, to avoid having to patch the code regularly.
</p
>
3386 <p
>So, the updated recipe for Debian Jessie:
</p
>
3390 <li
>First, install required packages to get the source code and the
3391 browser you need. Signal only work with Chrome/Chromium, as far as I
3392 know, so you need to install it.
3395 apt install git tor chromium
3396 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3397 </pre
></li
>
3399 <li
>Modify the source code using command listed in the the patch
3400 block below.
</li
>
3402 <li
>Start Signal using the run-signal-app wrapper (for example using
3403 <tt
>`pwd`/run-signal-app
</tt
>).
3405 <li
>Click on the
'Register without mobile phone
', will in a phone
3406 number you can receive calls to the next minute, receive the
3407 verification code and enter it into the form field and press
3408 'Register
'. Note, the phone number you use will be user Signal
3409 username, ie the way others can find you on Signal.
</li
>
3411 <li
>You can now use Signal to contact others. Note, new contacts do
3412 not show up in the contact list until you restart Signal, and there is
3413 no way to assign names to Contacts. There is also no way to create or
3414 update chat groups. I suspect this is because the web app do not have
3415 a associated contact database.
</li
>
3419 <p
>I am still a bit uneasy about using Signal, because of the way its
3420 main author moxie0 reject federation and accept dependencies to major
3421 corporations like Google (part of the code is fetched from Google) and
3422 Amazon (the central coordination point is owned by Amazon). See for
3424 <a href=
"https://github.com/LibreSignal/LibreSignal/issues/
37">the
3425 LibreSignal issue tracker
</a
> for a thread documenting the authors
3426 view on these issues. But the network effect is strong in this case,
3427 and several of the people I want to communicate with already use
3428 Signal. Perhaps we can all move to
<a href=
"https://ring.cx/
">Ring
</a
>
3429 once it
<a href=
"https://bugs.debian.org/
830265">work on my
3430 laptop
</a
>? It already work on Windows and Android, and is included
3431 in
<a href=
"https://tracker.debian.org/pkg/ring
">Debian
</a
> and
3432 <a href=
"https://launchpad.net/ubuntu/+source/ring
">Ubuntu
</a
>, but not
3433 working on Debian Stable.
</p
>
3435 <p
>Anyway, this is the patch I apply to the Signal code to get it
3436 working. It switch to the production servers, disable to timeout,
3437 make registration easier and add the shell wrapper:
</p
>
3440 cd Signal-Desktop; cat
&lt;
&lt;EOF | patch -p1
3441 diff --git a/js/background.js b/js/background.js
3442 index
24b4c1d.
.579345f
100644
3443 --- a/js/background.js
3444 +++ b/js/background.js
3449 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
3450 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org
';
3451 var SERVER_PORTS = [
80,
4433,
8443];
3452 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
3453 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
3454 var messageReceiver;
3455 window.getSocketStatus = function() {
3456 if (messageReceiver) {
3457 diff --git a/js/expire.js b/js/expire.js
3458 index
639aeae..beb91c3
100644
3463 'use strict
';
3464 - var BUILD_EXPIRATION =
0;
3465 + var BUILD_EXPIRATION = Date.now() + (
90 *
24 *
60 *
60 *
1000);
3467 window.extension = window.extension || {};
3469 diff --git a/js/views/install_view.js b/js/views/install_view.js
3470 index
7816f4f.
.1d6233b
100644
3471 --- a/js/views/install_view.js
3472 +++ b/js/views/install_view.js
3475 'click .step1
': this.selectStep.bind(this,
1),
3476 'click .step2
': this.selectStep.bind(this,
2),
3477 -
'click .step3
': this.selectStep.bind(this,
3)
3478 +
'click .step3
': this.selectStep.bind(this,
3),
3479 +
'click .callreg
': function() { extension.install(
'standalone
') },
3482 clearQR: function() {
3483 diff --git a/options.html b/options.html
3484 index dc0f28e.
.8d709f6
100644
3488 &lt;div class=
'nav
'>
3489 &lt;h1
>{{ installWelcome }}
&lt;/h1
>
3490 &lt;p
>{{ installTagline }}
&lt;/p
>
3491 -
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
> &lt;/div
>
3492 +
&lt;div
> &lt;a class=
'button step2
'>{{ installGetStartedButton }}
&lt;/a
>
3493 +
&lt;br
> &lt;a class=
"button callreg
">Register without mobile phone
&lt;/a
>
3496 &lt;span class=
'dot step1 selected
'>&lt;/span
>
3497 &lt;span class=
'dot step2
'>&lt;/span
>
3498 &lt;span class=
'dot step3
'>&lt;/span
>
3499 --- /dev/null
2016-
10-
07 09:
55:
13.730181472 +
0200
3500 +++ b/run-signal-app
2016-
10-
10 08:
54:
09.434172391 +
0200
3506 +userdata=
"`pwd`/userdata
"
3507 +if [ -d
"$userdata
" ]
&& [ ! -d
"$userdata/.git
" ] ; then
3508 + (cd $userdata
&& git init)
3510 +(cd $userdata
&& git add .
&& git commit -m
"Current status.
" || true)
3512 + --proxy-server=
"socks://localhost:
9050" \
3513 + --user-data-dir=$userdata --load-and-launch-app=`pwd`
3515 chmod a+rx run-signal-app
3518 <p
>As usual, if you use Bitcoin and want to show your support of my
3519 activities, please send Bitcoin donations to my address
3520 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3525 <title>Isenkram, Appstream and udev make life as a LEGO builder easier
</title>
3526 <link>https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</link>
3527 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram__Appstream_and_udev_make_life_as_a_LEGO_builder_easier.html
</guid>
3528 <pubDate>Fri,
7 Oct
2016 09:
50:
00 +
0200</pubDate>
3529 <description><p
><a href=
"http://packages.qa.debian.org/isenkram
">The Isenkram
3530 system
</a
> provide a practical and easy way to figure out which
3531 packages support the hardware in a given machine. The command line
3532 tool
<tt
>isenkram-lookup
</tt
> and the tasksel options provide a
3533 convenient way to list and install packages relevant for the current
3534 hardware during system installation, both user space packages and
3535 firmware packages. The GUI background daemon on the other hand provide
3536 a pop-up proposing to install packages when a new dongle is inserted
3537 while using the computer. For example, if you plug in a smart card
3538 reader, the system will ask if you want to install
<tt
>pcscd
</tt
> if
3539 that package isn
't already installed, and if you plug in a USB video
3540 camera the system will ask if you want to install
<tt
>cheese
</tt
> if
3541 cheese is currently missing. This already work just fine.
</p
>
3543 <p
>But Isenkram depend on a database mapping from hardware IDs to
3544 package names. When I started no such database existed in Debian, so
3545 I made my own data set and included it with the isenkram package and
3546 made isenkram fetch the latest version of this database from git using
3547 http. This way the isenkram users would get updated package proposals
3548 as soon as I learned more about hardware related packages.
</p
>
3550 <p
>The hardware is identified using modalias strings. The modalias
3551 design is from the Linux kernel where most hardware descriptors are
3552 made available as a strings that can be matched using filename style
3553 globbing. It handle USB, PCI, DMI and a lot of other hardware related
3554 identifiers.
</p
>
3556 <p
>The downside to the Isenkram specific database is that there is no
3557 information about relevant distribution / Debian version, making
3558 isenkram propose obsolete packages too. But along came AppStream, a
3559 cross distribution mechanism to store and collect metadata about
3560 software packages. When I heard about the proposal, I contacted the
3561 people involved and suggested to add a hardware matching rule using
3562 modalias strings in the specification, to be able to use AppStream for
3563 mapping hardware to packages. This idea was accepted and AppStream is
3564 now a great way for a package to announce the hardware it support in a
3565 distribution neutral way. I wrote
3566 <a href=
"http://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
">a
3567 recipe on how to add such meta-information
</a
> in a blog post last
3568 December. If you have a hardware related package in Debian, please
3569 announce the relevant hardware IDs using AppStream.
</p
>
3571 <p
>In Debian, almost all packages that can talk to a LEGO Mindestorms
3572 RCX or NXT unit, announce this support using AppStream. The effect is
3573 that when you insert such LEGO robot controller into your Debian
3574 machine, Isenkram will propose to install the packages needed to get
3575 it working. The intention is that this should allow the local user to
3576 start programming his robot controller right away without having to
3577 guess what packages to use or which permissions to fix.
</p
>
3579 <p
>But when I sat down with my son the other day to program our NXT
3580 unit using his Debian Stretch computer, I discovered something
3581 annoying. The local console user (ie my son) did not get access to
3582 the USB device for programming the unit. This used to work, but no
3583 longer in Jessie and Stretch. After some investigation and asking
3584 around on #debian-devel, I discovered that this was because udev had
3585 changed the mechanism used to grant access to local devices. The
3586 ConsoleKit mechanism from
<tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>
3587 no longer applied, because LDAP users no longer was added to the
3588 plugdev group during login. Michael Biebl told me that this method
3589 was obsolete and the new method used ACLs instead. This was good
3590 news, as the plugdev mechanism is a mess when using a remote user
3591 directory like LDAP. Using ACLs would make sure a user lost device
3592 access when she logged out, even if the user left behind a background
3593 process which would retain the plugdev membership with the ConsoleKit
3594 setup. Armed with this knowledge I moved on to fix the access problem
3595 for the LEGO Mindstorms related packages.
</p
>
3597 <p
>The new system uses a udev tag,
'uaccess
'. It can either be
3598 applied directly for a device, or is applied in
3599 /lib/udev/rules.d/
70-uaccess.rules for classes of devices. As the
3600 LEGO Mindstorms udev rules did not have a class, I decided to add the
3601 tag directly in the udev rules files included in the packages. Here
3602 is one example. For the nqc C compiler for the RCX, the
3603 <tt
>/lib/udev/rules.d/
60-nqc.rules
</tt
> file now look like this:
3605 <p
><pre
>
3606 SUBSYSTEM==
"usb
", ACTION==
"add
", ATTR{idVendor}==
"0694", ATTR{idProduct}==
"0001", \
3607 SYMLINK+=
"rcx-%k
", TAG+=
"uaccess
"
3608 </pre
></p
>
3610 <p
>The key part is the
'TAG+=
"uaccess
"' at the end. I suspect all
3611 packages using plugdev in their /lib/udev/rules.d/ files should be
3612 changed to use this tag (either directly or indirectly via
3613 <tt
>70-uaccess.rules
</tt
>). Perhaps a lintian check should be created
3614 to detect this?
</p
>
3616 <p
>I
've been unable to find good documentation on the uaccess feature.
3617 It is unclear to me if the uaccess tag is an internal implementation
3618 detail like the udev-acl tag used by
3619 <tt
>/lib/udev/rules.d/
70-udev-acl.rules
</tt
>. If it is, I guess the
3620 indirect method is the preferred way. Michael
3621 <a href=
"https://github.com/systemd/systemd/issues/
4288">asked for more
3622 documentation from the systemd project
</a
> and I hope it will make
3623 this clearer. For now I use the generic classes when they exist and
3624 is already handled by
<tt
>70-uaccess.rules
</tt
>, and add the tag
3625 directly if no such class exist.
</p
>
3627 <p
>To learn more about the isenkram system, please check out
3628 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
3629 blog posts tagged isenkram
</a
>.
</p
>
3631 <p
>To help out making life for LEGO constructors in Debian easier,
3632 please join us on our IRC channel
3633 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> and join
3634 the
<a href=
"https://alioth.debian.org/projects/debian-lego/
">Debian
3635 LEGO team
</a
> in the Alioth project we created yesterday. A mailing
3636 list is not yet created, but we are working on it. :)
</p
>
3638 <p
>As usual, if you use Bitcoin and want to show your support of my
3639 activities, please send Bitcoin donations to my address
3640 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
3645 <title>First draft Norwegian Bokmål edition of The Debian Administrator
's Handbook now public
</title>
3646 <link>https://people.skolelinux.org/pere/blog/First_draft_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook_now_public.html
</link>
3647 <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>
3648 <pubDate>Tue,
30 Aug
2016 10:
10:
00 +
0200</pubDate>
3649 <description><p
>In April we
3650 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
">started
3651 to work
</a
> on a Norwegian Bokmål edition of the
"open access
" book on
3652 how to set up and administrate a Debian system. Today I am happy to
3653 report that the first draft is now publicly available. You can find
3654 it on
<a href=
"https://debian-handbook.info/get/
">get the Debian
3655 Administrator
's Handbook page
</a
> (under Other languages). The first
3656 eight chapters have a first draft translation, and we are working on
3657 proofreading the content. If you want to help out, please start
3659 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
3660 hosted weblate project page
</a
>, and get in touch using
3661 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
3662 translators mailing list
</a
>. Please also check out
3663 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
3664 contributors
</a
>. A good way to contribute is to proofread the text
3665 and update weblate if you find errors.
</p
>
3667 <p
>Our goal is still to make the Norwegian book available on paper as well as
3668 electronic form.
</p
>
3673 <title>Coz can help you find bottlenecks in multi-threaded software - nice free software
</title>
3674 <link>https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</link>
3675 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Coz_can_help_you_find_bottlenecks_in_multi_threaded_software___nice_free_software.html
</guid>
3676 <pubDate>Thu,
11 Aug
2016 12:
00:
00 +
0200</pubDate>
3677 <description><p
>This summer, I read a great article
3678 "<a href=
"https://www.usenix.org/publications/login/summer2016/curtsinger
">coz:
3679 This Is the Profiler You
're Looking For
</a
>" in USENIX ;login: about
3680 how to profile multi-threaded programs. It presented a system for
3681 profiling software by running experiences in the running program,
3682 testing how run time performance is affected by
"speeding up
" parts of
3683 the code to various degrees compared to a normal run. It does this by
3684 slowing down parallel threads while the
"faster up
" code is running
3685 and measure how this affect processing time. The processing time is
3686 measured using probes inserted into the code, either using progress
3687 counters (COZ_PROGRESS) or as latency meters (COZ_BEGIN/COZ_END). It
3688 can also measure unmodified code by measuring complete the program
3689 runtime and running the program several times instead.
</p
>
3691 <p
>The project and presentation was so inspiring that I would like to
3692 get the system into Debian. I
3693 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
830708">created
3694 a WNPP request for it
</a
> and contacted upstream to try to make the
3695 system ready for Debian by sending patches. The build process need to
3696 be changed a bit to avoid running
'git clone
' to get dependencies, and
3697 to include the JavaScript web page used to visualize the collected
3698 profiling information included in the source package.
3699 But I expect that should work out fairly soon.
</p
>
3701 <p
>The way the system work is fairly simple. To run an coz experiment
3702 on a binary with debug symbols available, start the program like this:
3704 <p
><blockquote
><pre
>
3705 coz run --- program-to-run
3706 </pre
></blockquote
></p
>
3708 <p
>This will create a text file profile.coz with the instrumentation
3709 information. To show what part of the code affect the performance
3710 most, use a web browser and either point it to
3711 <a href=
"http://plasma-umass.github.io/coz/
">http://plasma-umass.github.io/coz/
</a
>
3712 or use the copy from git (in the gh-pages branch). Check out this web
3713 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
3714 profiling more useful you include
&lt;coz.h
&gt; and insert the
3715 COZ_PROGRESS or COZ_BEGIN and COZ_END at appropriate places in the
3716 code, rebuild and run the profiler. This allow coz to do more
3717 targeted experiments.
</p
>
3719 <p
>A video published by ACM
3720 <a href=
"https://www.youtube.com/watch?v=jE0V-p1odPg
">presenting the
3721 Coz profiler
</a
> is available from Youtube. There is also a paper
3722 from the
25th Symposium on Operating Systems Principles available
3724 <a href=
"https://www.usenix.org/conference/atc16/technical-sessions/presentation/curtsinger
">Coz:
3725 finding code that counts with causal profiling
</a
>.
</p
>
3727 <p
><a href=
"https://github.com/plasma-umass/coz
">The source code
</a
>
3728 for Coz is available from github. It will only build with clang
3730 <a href=
"https://gcc.gnu.org/bugzilla/show_bug.cgi?id=
55606">C++
3731 feature missing in GCC
</a
>, but I
've submitted
3732 <a href=
"https://github.com/plasma-umass/coz/pull/
67">a patch to solve
3733 it
</a
> and hope it will be included in the upstream source soon.
</p
>
3735 <p
>Please get in touch if you, like me, would like to see this piece
3736 of software in Debian. I would very much like some help with the
3737 packaging effort, as I lack the in depth knowledge on how to package
3738 C++ libraries.
</p
>
3743 <title>Unlocking HTC Desire HD on Linux using unruu and fastboot
</title>
3744 <link>https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</link>
3745 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Unlocking_HTC_Desire_HD_on_Linux_using_unruu_and_fastboot.html
</guid>
3746 <pubDate>Thu,
7 Jul
2016 11:
30:
00 +
0200</pubDate>
3747 <description><p
>Yesterday, I tried to unlock a HTC Desire HD phone, and it proved
3748 to be a slight challenge. Here is the recipe if I ever need to do it
3749 again. It all started by me wanting to try the recipe to set up
3750 <a href=
"https://blog.torproject.org/blog/mission-impossible-hardening-android-security-and-privacy
">an
3751 hardened Android installation
</a
> from the Tor project blog on a
3752 device I had access to. It is a old mobile phone with a broken
3753 microphone The initial idea had been to just
3754 <a href=
"http://wiki.cyanogenmod.org/w/Install_CM_for_ace
">install
3755 CyanogenMod on it
</a
>, but did not quite find time to start on it
3756 until a few days ago.
</p
>
3758 <p
>The unlock process is supposed to be simple: (
1) Boot into the boot
3759 loader (press volume down and power at the same time), (
2) select
3760 'fastboot
' before (
3) connecting the device via USB to a Linux
3761 machine, (
4) request the device identifier token by running
'fastboot
3762 oem get_identifier_token
', (
5) request the device unlocking key using
3763 the
<a href=
"http://www.htcdev.com/bootloader/
">HTC developer web
3764 site
</a
> and unlock the phone using the key file emailed to you.
</p
>
3766 <p
>Unfortunately, this only work fi you have hboot version
2.00.0029
3767 or newer, and the device I was working on had
2.00.0027. This
3768 apparently can be easily fixed by downloading a Windows program and
3769 running it on your Windows machine, if you accept the terms Microsoft
3770 require you to accept to use Windows - which I do not. So I had to
3771 come up with a different approach. I got a lot of help from AndyCap
3772 on #nuug, and would not have been able to get this working without
3775 <p
>First I needed to extract the hboot firmware from
3776 <a href=
"http://www.htcdev.com/ruu/PD9810000_Ace_Sense30_S_hboot_2.00
.0029.exe
">the
3777 windows binary for HTC Desire HD
</a
> downloaded as
'the RUU
' from HTC.
3778 For this there is is
<a href=
"https://github.com/kmdm/unruu/
">a github
3779 project named unruu
</a
> using libunshield. The unshield tool did not
3780 recognise the file format, but unruu worked and extracted rom.zip,
3781 containing the new hboot firmware and a text file describing which
3782 devices it would work for.
</p
>
3784 <p
>Next, I needed to get the new firmware into the device. For this I
3785 followed some instructions
3786 <a href=
"http://www.htc1guru.com/
2013/
09/new-ruu-zips-posted/
">available
3787 from HTC1Guru.com
</a
>, and ran these commands as root on a Linux
3788 machine with Debian testing:
</p
>
3790 <p
><pre
>
3791 adb reboot-bootloader
3792 fastboot oem rebootRUU
3793 fastboot flash zip rom.zip
3794 fastboot flash zip rom.zip
3796 </pre
></p
>
3798 <p
>The flash command apparently need to be done twice to take effect,
3799 as the first is just preparations and the second one do the flashing.
3800 The adb command is just to get to the boot loader menu, so turning the
3801 device on while holding volume down and the power button should work
3804 <p
>With the new hboot version in place I could start following the
3805 instructions on the HTC developer web site. I got the device token
3806 like this:
</p
>
3808 <p
><pre
>
3809 fastboot oem get_identifier_token
2>&1 | sed
's/(bootloader) //
'
3812 <p
>And once I got the unlock code via email, I could use it like
3815 <p
><pre
>
3816 fastboot flash unlocktoken Unlock_code.bin
3817 </pre
></p
>
3819 <p
>And with that final step in place, the phone was unlocked and I
3820 could start stuffing the software of my own choosing into the device.
3821 So far I only inserted a replacement recovery image to wipe the phone
3822 before I start. We will see what happen next. Perhaps I should
3823 install
<a href=
"https://www.debian.org/
">Debian
</a
> on it. :)
</p
>
3828 <title>How to use the Signal app if you only have a land line (ie no mobile phone)
</title>
3829 <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>
3830 <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>
3831 <pubDate>Sun,
3 Jul
2016 14:
20:
00 +
0200</pubDate>
3832 <description><p
>For a while now, I have wanted to test
3833 <a href=
"https://whispersystems.org/
">the Signal app
</a
>, as it is
3834 said to provide end to end encrypted communication and several of my
3835 friends and family are already using it. As I by choice do not own a
3836 mobile phone, this proved to be harder than expected. And I wanted to
3837 have the source of the client and know that it was the code used on my
3838 machine. But yesterday I managed to get it working. I used the
3839 Github source, compared it to the source in
3840 <a href=
"https://chrome.google.com/webstore/detail/signal-private-messenger/bikioccmkafdpakkkcpdbppfkghcmihk?hl=en-US
">the
3841 Signal Chrome app
</a
> available from the Chrome web store, applied
3842 patches to use the production Signal servers, started the app and
3843 asked for the hidden
"register without a smart phone
" form. Here is
3844 the recipe how I did it.
</p
>
3846 <p
>First, I fetched the Signal desktop source from Github, using
3849 git clone https://github.com/WhisperSystems/Signal-Desktop.git
3852 <p
>Next, I patched the source to use the production servers, to be
3853 able to talk to other Signal users:
</p
>
3856 cat
&lt;
&lt;EOF | patch -p0
3857 diff -ur ./js/background.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
3858 --- ./js/background.js
2016-
06-
29 13:
43:
15.630344628 +
0200
3859 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/background.js
2016-
06-
29 14:
06:
29.530300934 +
0200
3864 - var SERVER_URL =
'https://textsecure-service-staging.whispersystems.org
';
3865 - var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments-staging.s3.amazonaws.com
';
3866 + var SERVER_URL =
'https://textsecure-service-ca.whispersystems.org:
4433';
3867 + var ATTACHMENT_SERVER_URL =
'https://whispersystems-textsecure-attachments.s3.amazonaws.com
';
3868 var messageReceiver;
3869 window.getSocketStatus = function() {
3870 if (messageReceiver) {
3871 diff -ur ./js/expire.js userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js
3872 --- ./js/expire.js
2016-
06-
29 13:
43:
15.630344628 +
0200
3873 +++ userdata/Default/Extensions/bikioccmkafdpakkkcpdbppfkghcmihk/
0.15.0_0/js/expire.js2016-
06-
29 14:
06:
29.530300934 +
0200
3876 'use strict
';
3877 - var BUILD_EXPIRATION =
0;
3878 + var BUILD_EXPIRATION =
1474492690000;
3880 window.extension = window.extension || {};
3885 <p
>The first part is changing the servers, and the second is updating
3886 an expiration timestamp. This timestamp need to be updated regularly.
3887 It is set
90 days in the future by the build process (Gruntfile.js).
3888 The value is seconds since
1970 times
1000, as far as I can tell.
</p
>
3890 <p
>Based on a tip and good help from the #nuug IRC channel, I wrote a
3891 script to launch Signal in Chromium.
</p
>
3898 --proxy-server=
"socks://localhost:
9050" \
3899 --user-data-dir=`pwd`/userdata --load-and-launch-app=`pwd`
3902 <p
> The script start the app and configure Chromium to use the Tor
3903 SOCKS5 proxy to make sure those controlling the Signal servers (today
3904 Amazon and Whisper Systems) as well as those listening on the lines
3905 will have a harder time location my laptop based on the Signal
3906 connections if they use source IP address.
</p
>
3908 <p
>When the script starts, one need to follow the instructions under
3909 "Standalone Registration
" in the CONTRIBUTING.md file in the git
3910 repository. I right clicked on the Signal window to get up the
3911 Chromium debugging tool, visited the
'Console
' tab and wrote
3912 'extension.install(
"standalone
")
' on the console prompt to get the
3913 registration form. Then I entered by land line phone number and
3914 pressed
'Call
'.
5 seconds later the phone rang and a robot voice
3915 repeated the verification code three times. After entering the number
3916 into the verification code field in the form, I could start using
3917 Signal from my laptop.
3919 <p
>As far as I can tell, The Signal app will leak who is talking to
3920 whom and thus who know who to those controlling the central server,
3921 but such leakage is hard to avoid with a centrally controlled server
3922 setup. It is something to keep in mind when using Signal - the
3923 content of your chats are harder to intercept, but the meta data
3924 exposing your contact network is available to people you do not know.
3925 So better than many options, but not great. And sadly the usage is
3926 connected to my land line, thus allowing those controlling the server
3927 to associate it to my home and person. I would prefer it if only
3928 those I knew could tell who I was on Signal. There are options
3929 avoiding such information leakage, but most of my friends are not
3930 using them, so I am stuck with Signal for now.
</p
>
3932 <p
><strong
>Update
2017-
01-
10</strong
>: There is an updated blog post
3934 <a href=
"http://people.skolelinux.org/pere/blog/Experience_and_updated_recipe_for_using_the_Signal_app_without_a_mobile_phone.html
">Experience
3935 and updated recipe for using the Signal app without a mobile
3936 phone
</a
>.
</p
>
3941 <title>The new
"best
" multimedia player in Debian?
</title>
3942 <link>https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</link>
3943 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_new__best__multimedia_player_in_Debian_.html
</guid>
3944 <pubDate>Mon,
6 Jun
2016 12:
50:
00 +
0200</pubDate>
3945 <description><p
>When I set out a few weeks ago to figure out
3946 <a href=
"http://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
">which
3947 multimedia player in Debian claimed to support most file formats /
3948 MIME types
</a
>, I was a bit surprised how varied the sets of MIME types
3949 the various players claimed support for. The range was from
55 to
130
3950 MIME types. I suspect most media formats are supported by all
3951 players, but this is not really reflected in the MimeTypes values in
3952 their desktop files. There are probably also some bogus MIME types
3953 listed, but it is hard to identify which one this is.
</p
>
3955 <p
>Anyway, in the mean time I got in touch with upstream for some of
3956 the players suggesting to add more MIME types to their desktop files,
3957 and decided to spend some time myself improving the situation for my
3958 favorite media player VLC. The fixes for VLC entered Debian unstable
3959 yesterday. The complete list of MIME types can be seen on the
3960 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">Multimedia
3961 player MIME type support status
</a
> Debian wiki page.
</p
>
3963 <p
>The new
"best
" multimedia player in Debian? It is VLC, followed by
3964 totem, parole, kplayer, gnome-mpv, mpv, smplayer, mplayer-gui and
3965 kmplayer. I am sure some of the other players desktop files support
3966 several of the formats currently listed as working only with vlc,
3967 toten and parole.
</p
>
3969 <p
>A sad observation is that only
14 MIME types are listed as
3970 supported by all the tested multimedia players in Debian in their
3971 desktop files: audio/mpeg, audio/vnd.rn-realaudio, audio/x-mpegurl,
3972 audio/x-ms-wma, audio/x-scpls, audio/x-wav, video/mp4, video/mpeg,
3973 video/quicktime, video/vnd.rn-realvideo, video/x-matroska,
3974 video/x-ms-asf, video/x-ms-wmv and video/x-msvideo. Personally I find
3975 it sad that video/ogg and video/webm is not supported by all the media
3976 players in Debian. As far as I can tell, all of them can handle both
3982 <title>A program should be able to open its own files on Linux
</title>
3983 <link>https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</link>
3984 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_program_should_be_able_to_open_its_own_files_on_Linux.html
</guid>
3985 <pubDate>Sun,
5 Jun
2016 08:
30:
00 +
0200</pubDate>
3986 <description><p
>Many years ago, when koffice was fresh and with few users, I
3987 decided to test its presentation tool when making the slides for a
3988 talk I was giving for NUUG on Japhar, a free Java virtual machine. I
3989 wrote the first draft of the slides, saved the result and went to bed
3990 the day before I would give the talk. The next day I took a plane to
3991 the location where the meeting should take place, and on the plane I
3992 started up koffice again to polish the talk a bit, only to discover
3993 that kpresenter refused to load its own data file. I cursed a bit and
3994 started making the slides again from memory, to have something to
3995 present when I arrived. I tested that the saved files could be
3996 loaded, and the day seemed to be rescued. I continued to polish the
3997 slides until I suddenly discovered that the saved file could no longer
3998 be loaded into kpresenter. In the end I had to rewrite the slides
3999 three times, condensing the content until the talk became shorter and
4000 shorter. After the talk I was able to pinpoint the problem
&ndash;
4001 kpresenter wrote inline images in a way itself could not understand.
4002 Eventually that bug was fixed and kpresenter ended up being a great
4003 program to make slides. The point I
'm trying to make is that we
4004 expect a program to be able to load its own data files, and it is
4005 embarrassing to its developers if it can
't.
</p
>
4007 <p
>Did you ever experience a program failing to load its own data
4008 files from the desktop file browser? It is not a uncommon problem. A
4009 while back I discovered that the screencast recorder
4010 gtk-recordmydesktop would save an Ogg Theora video file the KDE file
4011 browser would refuse to open. No video player claimed to understand
4012 such file. I tracked down the cause being
<tt
>file --mime-type
</tt
>
4013 returning the application/ogg MIME type, which no video player I had
4014 installed listed as a MIME type they would understand. I asked for
4015 <a href=
"http://bugs.gw.com/view.php?id=
382">file to change its
4016 behavour
</a
> and use the MIME type video/ogg instead. I also asked
4017 several video players to add video/ogg to their desktop files, to give
4018 the file browser an idea what to do about Ogg Theora files. After a
4019 while, the desktop file browsers in Debian started to handle the
4020 output from gtk-recordmydesktop properly.
</p
>
4022 <p
>But history repeats itself. A few days ago I tested the music
4023 system Rosegarden again, and I discovered that the KDE and xfce file
4024 browsers did not know what to do with the Rosegarden project files
4025 (*.rg). I
've reported
<a href=
"http://bugs.debian.org/
825993">the
4026 rosegarden problem to BTS
</a
> and a fix is commited to git and will be
4027 included in the next upload. To increase the chance of me remembering
4028 how to fix the problem next time some program fail to load its files
4029 from the file browser, here are some notes on how to fix it.
</p
>
4031 <p
>The file browsers in Debian in general operates on MIME types.
4032 There are two sources for the MIME type of a given file. The output from
4033 <tt
>file --mime-type
</tt
> mentioned above, and the content of the
4034 shared MIME type registry (under /usr/share/mime/). The file MIME
4035 type is mapped to programs supporting the MIME type, and this
4036 information is collected from
4037 <a href=
"https://www.freedesktop.org/wiki/Specifications/desktop-entry-spec/
">the
4038 desktop files
</a
> available in /usr/share/applications/. If there is
4039 one desktop file claiming support for the MIME type of the file, it is
4040 activated when asking to open a given file. If there are more, one
4041 can normally select which one to use by right-clicking on the file and
4042 selecting the wanted one using
'Open with
' or similar. In general
4043 this work well. But it depend on each program picking a good MIME
4045 <a href=
"http://www.iana.org/assignments/media-types/media-types.xhtml
">a
4046 MIME type registered with IANA
</a
>), file and/or the shared MIME
4047 registry recognizing the file and the desktop file to list the MIME
4048 type in its list of supported MIME types.
</p
>
4050 <p
>The
<tt
>/usr/share/mime/packages/rosegarden.xml
</tt
> entry for
4051 <a href=
"http://www.freedesktop.org/wiki/Specifications/shared-mime-info-spec
">the
4052 Shared MIME database
</a
> look like this:
</p
>
4054 <p
><blockquote
><pre
>
4055 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
4056 &lt;mime-info xmlns=
"http://www.freedesktop.org/standards/shared-mime-info
"&gt;
4057 &lt;mime-type type=
"audio/x-rosegarden
"&gt;
4058 &lt;sub-class-of type=
"application/x-gzip
"/
&gt;
4059 &lt;comment
&gt;Rosegarden project file
&lt;/comment
&gt;
4060 &lt;glob pattern=
"*.rg
"/
&gt;
4061 &lt;/mime-type
&gt;
4062 &lt;/mime-info
&gt;
4063 </pre
></blockquote
></p
>
4065 <p
>This states that audio/x-rosegarden is a kind of application/x-gzip
4066 (it is a gzipped XML file). Note, it is much better to use an
4067 official MIME type registered with IANA than it is to make up ones own
4068 unofficial ones like the x-rosegarden type used by rosegarden.
</p
>
4070 <p
>The desktop file of the rosegarden program failed to list
4071 audio/x-rosegarden in its list of supported MIME types, causing the
4072 file browsers to have no idea what to do with *.rg files:
</p
>
4074 <p
><blockquote
><pre
>
4075 % grep Mime /usr/share/applications/rosegarden.desktop
4076 MimeType=audio/x-rosegarden-composition;audio/x-rosegarden-device;audio/x-rosegarden-project;audio/x-rosegarden-template;audio/midi;
4077 X-KDE-NativeMimeType=audio/x-rosegarden-composition
4079 </pre
></blockquote
></p
>
4081 <p
>The fix was to add
"audio/x-rosegarden;
" at the end of the
4082 MimeType= line.
</p
>
4084 <p
>If you run into a file which fail to open the correct program when
4085 selected from the file browser, please check out the output from
4086 <tt
>file --mime-type
</tt
> for the file, ensure the file ending and
4087 MIME type is registered somewhere under /usr/share/mime/ and check
4088 that some desktop file under /usr/share/applications/ is claiming
4089 support for this MIME type. If not, please report a bug to have it
4095 <title>Isenkram with PackageKit support - new version
0.23 available in Debian unstable
</title>
4096 <link>https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</link>
4097 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_with_PackageKit_support___new_version_0_23_available_in_Debian_unstable.html
</guid>
4098 <pubDate>Wed,
25 May
2016 10:
20:
00 +
0200</pubDate>
4099 <description><p
><a href=
"https://tracker.debian.org/pkg/isenkram
">The isenkram
4100 system
</a
> is a user-focused solution in Debian for handling hardware
4101 related packages. The idea is to have a database of mappings between
4102 hardware and packages, and pop up a dialog suggesting for the user to
4103 install the packages to use a given hardware dongle. Some use cases
4104 are when you insert a Yubikey, it proposes to install the software
4105 needed to control it; when you insert a braille reader list it
4106 proposes to install the packages needed to send text to the reader;
4107 and when you insert a ColorHug screen calibrator it suggests to
4108 install the driver for it. The system work well, and even have a few
4109 command line tools to install firmware packages and packages for the
4110 hardware already in the machine (as opposed to hotpluggable hardware).
</p
>
4112 <p
>The system was initially written using aptdaemon, because I found
4113 good documentation and example code on how to use it. But aptdaemon
4114 is going away and is generally being replaced by
4115 <a href=
"http://www.freedesktop.org/software/PackageKit/
">PackageKit
</a
>,
4116 so Isenkram needed a rewrite. And today, thanks to the great patch
4117 from my college Sunil Mohan Adapa in the FreedomBox project, the
4118 rewrite finally took place. I
've just uploaded a new version of
4119 Isenkram into Debian Unstable with the patch included, and the default
4120 for the background daemon is now to use PackageKit. To check it out,
4121 install the
<tt
>isenkram
</tt
> package and insert some hardware dongle
4122 and see if it is recognised.
</p
>
4124 <p
>If you want to know what kind of packages isenkram would propose for
4125 the machine it is running on, you can check out the isenkram-lookup
4126 program. This is what it look like on a Thinkpad X230:
</p
>
4128 <p
><blockquote
><pre
>
4144 </pre
></blockquote
></p
>
4146 <p
>The hardware mappings come from several places. The preferred way
4147 is for packages to announce their hardware support using
4148 <a href=
"https://www.freedesktop.org/software/appstream/docs/
">the
4149 cross distribution appstream system
</a
>.
4151 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">previous
4152 blog posts about isenkram
</a
> to learn how to do that.
</p
>
4157 <title>Discharge rate estimate in new battery statistics collector for Debian
</title>
4158 <link>https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</link>
4159 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Discharge_rate_estimate_in_new_battery_statistics_collector_for_Debian.html
</guid>
4160 <pubDate>Mon,
23 May
2016 09:
35:
00 +
0200</pubDate>
4161 <description><p
>Yesterday I updated the
4162 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
4163 package in Debian
</a
> with a few patches sent to me by skilled and
4164 enterprising users. There were some nice user and visible changes.
4165 First of all, both desktop menu entries now work. A design flaw in
4166 one of the script made the history graph fail to show up (its PNG was
4167 dumped in ~/.xsession-errors) if no controlling TTY was available.
4168 The script worked when called from the command line, but not when
4169 called from the desktop menu. I changed this to look for a DISPLAY
4170 variable or a TTY before deciding where to draw the graph, and now the
4171 graph window pop up as expected.
</p
>
4173 <p
>The next new feature is a discharge rate estimator in one of the
4174 graphs (the one showing the last few hours). New is also the user of
4175 colours showing charging in blue and discharge in red. The percentages
4176 of this graph is relative to last full charge, not battery design
4179 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-rate.png
"/
></p
>
4181 <p
>The other graph show the entire history of the collected battery
4182 statistics, comparing it to the design capacity of the battery to
4183 visualise how the battery life time get shorter over time. The red
4184 line in this graph is what the previous graph considers
100 percent:
4186 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2016-
05-
23-battery-stats-history.png
"/
></p
>
4188 <p
>In this graph you can see that I only charge the battery to
80
4189 percent of last full capacity, and how the capacity of the battery is
4190 shrinking. :(
</p
>
4192 <p
>The last new feature is in the collector, which now will handle
4193 more hardware models. On some hardware, Linux power supply
4194 information is stored in /sys/class/power_supply/ACAD/, while the
4195 collector previously only looked in /sys/class/power_supply/AC/. Now
4196 both are checked to figure if there is power connected to the
4199 <p
>If you are interested in how your laptop battery is doing, please
4201 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
4202 in Debian unstable, or rebuild it on Jessie to get it working on
4203 Debian stable. :) The upstream source is available from
<a
4204 href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4205 Patches are very welcome.
</p
>
4207 <p
>As usual, if you use Bitcoin and want to show your support of my
4208 activities, please send Bitcoin donations to my address
4209 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4214 <title>Debian now with ZFS on Linux included
</title>
4215 <link>https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</link>
4216 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_now_with_ZFS_on_Linux_included.html
</guid>
4217 <pubDate>Thu,
12 May
2016 07:
30:
00 +
0200</pubDate>
4218 <description><p
>Today, after many years of hard work from many people,
4219 <a href=
"http://zfsonlinux.org/
">ZFS for Linux
</a
> finally entered
4220 Debian. The package status can be seen on
4221 <a href=
"https://tracker.debian.org/pkg/zfs-linux
">the package tracker
4222 for zfs-linux
</a
>. and
4223 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
4224 team status page
</a
>. If you want to help out, please join us.
4225 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">The
4226 source code
</a
> is available via git on Alioth. It would also be
4227 great if you could help out with
4228 <a href=
"https://tracker.debian.org/pkg/dkms
">the dkms package
</a
>, as
4229 it is an important piece of the puzzle to get ZFS working.
</p
>
4234 <title>What is the best multimedia player in Debian?
</title>
4235 <link>https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</link>
4236 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_best_multimedia_player_in_Debian_.html
</guid>
4237 <pubDate>Sun,
8 May
2016 09:
40:
00 +
0200</pubDate>
4238 <description><p
><strong
>Where I set out to figure out which multimedia player in
4239 Debian claim support for most file formats.
</strong
></p
>
4241 <p
>A few years ago, I had a look at the media support for Browser
4242 plugins in Debian, to get an idea which plugins to include in Debian
4243 Edu. I created a script to extract the set of supported MIME types
4244 for each plugin, and used this to find out which multimedia browser
4245 plugin supported most file formats / media types.
4246 <a href=
"https://wiki.debian.org/DebianEdu/BrowserMultimedia
">The
4247 result
</a
> can still be seen on the Debian wiki, even though it have
4248 not been updated for a while. But browser plugins are less relevant
4249 these days, so I thought it was time to look at standalone
4252 <p
>A few days ago I was tired of VLC not being listed as a viable
4253 player when I wanted to play videos from the Norwegian National
4254 Broadcasting Company, and decided to investigate why. The cause is a
4255 <a href=
"https://bugs.debian.org/
822245">missing MIME type in the VLC
4256 desktop file
</a
>. In the process I wrote a script to compare the set
4257 of MIME types announced in the desktop file and the browser plugin,
4258 only to discover that there is quite a large difference between the
4259 two for VLC. This discovery made me dig up the script I used to
4260 compare browser plugins, and adjust it to compare desktop files
4261 instead, to try to figure out which multimedia player in Debian
4262 support most file formats.
</p
>
4264 <p
>The result can be seen on the Debian Wiki, as
4265 <a href=
"https://wiki.debian.org/DebianMultimedia/PlayerSupport
">a
4266 table listing all MIME types supported by one of the packages included
4267 in the table
</a
>, with the package supporting most MIME types being
4268 listed first in the table.
</p
>
4270 </p
>The best multimedia player in Debian? It is totem, followed by
4271 parole, kplayer, mpv, vlc, smplayer mplayer-gui gnome-mpv and
4272 kmplayer. Time for the other players to update their announced MIME
4278 <title>The Pyra - handheld computer with Debian preinstalled
</title>
4279 <link>https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</link>
4280 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Pyra___handheld_computer_with_Debian_preinstalled.html
</guid>
4281 <pubDate>Wed,
4 May
2016 10:
00:
00 +
0200</pubDate>
4282 <description>A friend of mine made me aware of
4283 <a href=
"https://pyra-handheld.com/boards/pages/pyra/
">The Pyra
</a
>, a
4284 handheld computer which will be delivered with Debian preinstalled. I
4285 would love to get one of those for my birthday. :)
</p
>
4287 <p
>The machine is a complete ARM-based PC with micro HDMI, SATA, USB
4288 plugs and many others connectors, and include a full keyboard and a
5"
4289 LCD touch screen. The
6000mAh battery is claimed to provide a whole
4290 day of battery life time, but I have not seen any independent tests
4291 confirming this. The vendor is still collecting preorders, and the
4292 last I heard last night was that
22 more orders were needed before
4293 production started.
</p
>
4295 <p
>As far as I know, this is the first handheld preinstalled with
4296 Debian. Please let me know if you know of any others. Is it the
4297 first computer being sold with Debian preinstalled?
</p
>
4302 <title>Lets make a Norwegian Bokmål edition of The Debian Administrator
's Handbook
</title>
4303 <link>https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</link>
4304 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_a_Norwegian_Bokm_l_edition_of_The_Debian_Administrator_s_Handbook.html
</guid>
4305 <pubDate>Sun,
10 Apr
2016 23:
20:
00 +
0200</pubDate>
4306 <description><p
>During this weekends
4307 <a href=
"http://www.nuug.no/news/Oslo__Takk_for_feilfiksingsfesten.shtml
">bug
4308 squashing party and developer gathering
</a
>, we decided to do our part
4309 to make sure there are good books about Debian available in Norwegian
4310 Bokmål, and got in touch with the people behind the
4311 <a href=
"http://debian-handbook.info/
">Debian Administrator
's Handbook
4312 project
</a
> to get started. If you want to help out, please start
4314 <a href=
"https://hosted.weblate.org/projects/debian-handbook/
">the
4315 hosted weblate project page
</a
>, and get in touch using
4316 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/debian-handbook-translators
">the
4317 translators mailing list
</a
>. Please also check out
4318 <a href=
"https://debian-handbook.info/contribute/
">the instructions for
4319 contributors
</a
>.
</p
>
4321 <p
>The book is already available on paper in English, French and
4322 Japanese, and our goal is to get it available on paper in Norwegian
4323 Bokmål too. In addition to the paper edition, there are also EPUB and
4324 Mobi versions available. And there are incomplete translations
4325 available for many more languages.
</p
>
4330 <title>One in two hundred Debian users using ZFS on Linux?
</title>
4331 <link>https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</link>
4332 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/One_in_two_hundred_Debian_users_using_ZFS_on_Linux_.html
</guid>
4333 <pubDate>Thu,
7 Apr
2016 22:
30:
00 +
0200</pubDate>
4334 <description><p
>Just for fun I had a look at the popcon number of ZFS related
4335 packages in Debian, and was quite surprised with what I found. I use
4336 ZFS myself at home, but did not really expect many others to do so.
4337 But I might be wrong.
</p
>
4339 <p
>According to
4340 <a href=
"https://qa.debian.org/popcon.php?package=spl-linux
">the popcon
4341 results for spl-linux
</a
>, there are
1019 Debian installations, or
4342 0.53% of the population, with the package installed. As far as I know
4343 the only use of the spl-linux package is as a support library for ZFS
4344 on Linux, so I use it here as proxy for measuring the number of ZFS
4345 installation on Linux in Debian. In the kFreeBSD variant of Debian
4346 the ZFS feature is already available, and there
4347 <a href=
"https://qa.debian.org/popcon.php?package=zfsutils
">the popcon
4348 results for zfsutils
</a
> show
1625 Debian installations or
0.84% of
4349 the population. So I guess I am not alone in using ZFS on Debian.
</p
>
4351 <p
>But even though the Debian project leader Lucas Nussbaum
4352 <a href=
"https://lists.debian.org/debian-devel-announce/
2015/
04/msg00006.html
">announced
4353 in April
2015</a
> that the legal obstacles blocking ZFS on Debian were
4354 cleared, the package is still not in Debian. The package is again in
4355 the NEW queue. Several uploads have been rejected so far because the
4356 debian/copyright file was incomplete or wrong, but there is no reason
4357 to give up. The current status can be seen on
4358 <a href=
"https://qa.debian.org/developer.php?login=pkg-zfsonlinux-devel@lists.alioth.debian.org
">the
4359 team status page
</a
>, and
4360 <a href=
"http://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git
">the
4361 source code
</a
> is available on Alioth.
</p
>
4363 <p
>As I want ZFS to be included in next version of Debian to make sure
4364 my home server can function in the future using only official Debian
4365 packages, and the current blocker is to get the debian/copyright file
4366 accepted by the FTP masters in Debian, I decided a while back to try
4367 to help out the team. This was the background for my blog post about
4368 <a href=
"http://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
">creating,
4369 updating and checking debian/copyright semi-automatically
</a
>, and I
4370 used the techniques I explored there to try to find any errors in the
4371 copyright file. It is not very easy to check every one of the around
4372 2000 files in the source package, but I hope we this time got it
4373 right. If you want to help out, check out the git source and try to
4374 find missing entries in the debian/copyright file.
</p
>
4379 <title>Full battery stats collector is now available in Debian
</title>
4380 <link>https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</link>
4381 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Full_battery_stats_collector_is_now_available_in_Debian.html
</guid>
4382 <pubDate>Wed,
23 Mar
2016 22:
10:
00 +
0100</pubDate>
4383 <description><p
>Since this morning, the battery-stats package in Debian include an
4384 extended collector that will collect the complete battery history for
4385 later processing and graphing. The original collector store the
4386 battery level as percentage of last full level, while the new
4387 collector also record battery vendor, model, serial number, design
4388 full level, last full level and current battery level. This make it
4389 possible to predict the lifetime of the battery as well as visualise
4390 the energy flow when the battery is charging or discharging.
</p
>
4392 <p
>The new tools are available in
<tt
>/usr/share/battery-stats/
</tt
>
4393 in the version
0.5.1 package in unstable. Get the new battery level graph
4394 and lifetime prediction by running:
4396 <p
><pre
>
4397 /usr/share/battery-stats/battery-stats-graph /var/log/battery-stats.csv
4398 </pre
></p
>
4400 <p
>Or select the
'Battery Level Graph
' from your application menu.
</p
>
4402 <p
>The flow in/out of the battery can be seen by running (no menu
4403 entry yet):
</p
>
4405 <p
><pre
>
4406 /usr/share/battery-stats/battery-stats-graph-flow
4407 </pre
></p
>
4409 <p
>I
'm not quite happy with the way the data is visualised, at least
4410 when there are few data points. The graphs look a bit better with a
4411 few years of data.
</p
>
4413 <p
>A while back one important feature I use in the battery stats
4414 collector broke in Debian. The scripts in
4415 <tt
>/usr/lib/pm-utils/power.d/
</tt
> were no longer executed. I
4416 suspect it happened when Jessie started using systemd, but I do not
4417 know. The issue is reported as
4418 <a href=
"https://bugs.debian.org/
818649">bug #
818649</a
> against
4419 pm-utils. I managed to work around it by adding an udev rule to call
4420 the collector script every time the power connector is connected and
4421 disconnected. With this fix in place it was finally time to make a
4422 new release of the package, and get it into Debian.
</p
>
4424 <p
>If you are interested in how your laptop battery is doing, please
4426 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>
4427 in Debian unstable, or rebuild it on Jessie to get it working on
4428 Debian stable. :) The upstream source is available from
4429 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4430 As always, patches are very welcome.
</p
>
4435 <title>Making battery measurements a little easier in Debian
</title>
4436 <link>https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</link>
4437 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Making_battery_measurements_a_little_easier_in_Debian.html
</guid>
4438 <pubDate>Tue,
15 Mar
2016 15:
00:
00 +
0100</pubDate>
4439 <description><p
>Back in September, I blogged about
4440 <a href=
"http://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
">the
4441 system I wrote to collect statistics about my laptop battery
</a
>, and
4442 how it showed the decay and death of this battery (now replaced). I
4443 created a simple deb package to handle the collection and graphing,
4444 but did not want to upload it to Debian as there were already
4445 <a href=
"https://tracker.debian.org/pkg/battery-stats
">a battery-stats
4446 package in Debian
</a
> that should do the same thing, and I did not see
4447 a point of uploading a competing package when battery-stats could be
4448 fixed instead. I reported a few bugs about its non-function, and
4449 hoped someone would step in and fix it. But no-one did.
</p
>
4451 <p
>I got tired of waiting a few days ago, and took matters in my own
4452 hands. The end result is that I am now the new upstream developer of
4453 battery stats (
<a href=
"https://github.com/petterreinholdtsen/battery-stats
">available from github
</a
>) and part of the team maintaining
4454 battery-stats in Debian, and the package in Debian unstable is finally
4455 able to collect battery status using the
<tt
>/sys/class/power_supply/
</tt
>
4456 information provided by the Linux kernel. If you install the
4457 battery-stats package from unstable now, you will be able to get a
4458 graph of the current battery fill level, to get some idea about the
4459 status of the battery. The source package build and work just fine in
4460 Debian testing and stable (and probably oldstable too, but I have not
4461 tested). The default graph you get for that system look like this:
</p
>
4463 <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
>
4465 <p
>My plans for the future is to merge my old scripts into the
4466 battery-stats package, as my old scripts collected a lot more details
4467 about the battery. The scripts are merged into the upstream
4468 battery-stats git repository already, but I am not convinced they work
4469 yet, as I changed a lot of paths along the way. Will have to test a
4470 bit more before I make a new release.
</p
>
4472 <p
>I will also consider changing the file format slightly, as I
4473 suspect the way I combine several values into one field might make it
4474 impossible to know the type of the value when using it for processing
4475 and graphing.
</p
>
4477 <p
>If you would like I would like to keep an close eye on your laptop
4478 battery, check out the battery-stats package in
4479 <a href=
"https://tracker.debian.org/pkg/battery-stats
">Debian
</a
> and
4481 <a href=
"https://github.com/petterreinholdtsen/battery-stats
">github
</a
>.
4482 I would love some help to improve the system further.
</p
>
4487 <title>Creating, updating and checking debian/copyright semi-automatically
</title>
4488 <link>https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</link>
4489 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creating__updating_and_checking_debian_copyright_semi_automatically.html
</guid>
4490 <pubDate>Fri,
19 Feb
2016 15:
00:
00 +
0100</pubDate>
4491 <description><p
>Making packages for Debian requires quite a lot of attention to
4492 details. And one of the details is the content of the
4493 debian/copyright file, which should list all relevant licenses used by
4494 the code in the package in question, preferably in
4495 <a href=
"https://www.debian.org/doc/packaging-manuals/copyright-format/
1.0/
">machine
4496 readable DEP5 format
</a
>.
</p
>
4498 <p
>For large packages with lots of contributors it is hard to write
4499 and update this file manually, and if you get some detail wrong, the
4500 package is normally rejected by the ftpmasters. So getting it right
4501 the first time around get the package into Debian faster, and save
4502 both you and the ftpmasters some work.. Today, while trying to figure
4503 out what was wrong with
4504 <a href=
"https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
686447">the
4505 zfsonlinux copyright file
</a
>, I decided to spend some time on
4506 figuring out the options for doing this job automatically, or at least
4507 semi-automatically.
</p
>
4509 <p
>Lucikly, there are at least two tools available for generating the
4510 file based on the code in the source package,
4511 <tt
><a href=
"https://tracker.debian.org/pkg/debmake
">debmake
</a
></tt
>
4512 and
<tt
><a href=
"https://tracker.debian.org/pkg/cme
">cme
</a
></tt
>. I
'm
4513 not sure which one of them came first, but both seem to be able to
4514 create a sensible draft file. As far as I can tell, none of them can
4515 be trusted to get the result just right, so the content need to be
4516 polished a bit before the file is OK to upload. I found the debmake
4518 <a href=
"http://goofying-with-debian.blogspot.com/
2014/
07/debmake-checking-source-against-dep-
5.html
">a
4519 blog posts from
2014</a
>.
4521 <p
>To generate using debmake, use the -cc option:
4523 <p
><pre
>
4524 debmake -cc
> debian/copyright
4525 </pre
></p
>
4527 <p
>Note there are some problems with python and non-ASCII names, so
4528 this might not be the best option.
</p
>
4530 <p
>The cme option is based on a config parsing library, and I found
4532 <a href=
"https://ddumont.wordpress.com/
2015/
04/
05/improving-creation-of-debian-copyright-file/
">a
4533 blog post from
2015</a
>. To generate using cme, use the
'update
4534 dpkg-copyright
' option:
4536 <p
><pre
>
4537 cme update dpkg-copyright
4538 </pre
></p
>
4540 <p
>This will create or update debian/copyright. The cme tool seem to
4541 handle UTF-
8 names better than debmake.
</p
>
4543 <p
>When the copyright file is created, I would also like some help to
4544 check if the file is correct. For this I found two good options,
4545 <tt
>debmake -k
</tt
> and
<tt
>license-reconcile
</tt
>. The former seem
4546 to focus on license types and file matching, and is able to detect
4547 ineffective blocks in the copyright file. The latter reports missing
4548 copyright holders and years, but was confused by inconsistent license
4549 names (like CDDL vs. CDDL-
1.0). I suspect it is good to use both and
4550 fix all issues reported by them before uploading. But I do not know
4551 if the tools and the ftpmasters agree on what is important to fix in a
4552 copyright file, so the package might still be rejected.
</p
>
4554 <p
>The devscripts tool
<tt
>licensecheck
</tt
> deserve mentioning. It
4555 will read through the source and try to find all copyright statements.
4556 It is not comparing the result to the content of debian/copyright, but
4557 can be useful when verifying the content of the copyright file.
</p
>
4559 <p
>Are you aware of better tools in Debian to create and update
4560 debian/copyright file. Please let me know, or blog about it on
4561 planet.debian.org.
</p
>
4563 <p
>As usual, if you use Bitcoin and want to show your support of my
4564 activities, please send Bitcoin donations to my address
4565 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
4567 <p
><strong
>Update
2016-
02-
20</strong
>: I got a tip from Mike Gabriel
4568 on how to use licensecheck and cdbs to create a draft copyright file
4570 <p
><pre
>
4571 licensecheck --copyright -r `find * -type f` | \
4572 /usr/lib/cdbs/licensecheck2dep5
> debian/copyright.auto
4573 </pre
></p
>
4575 <p
>He mentioned that he normally check the generated file into the
4576 version control system to make it easier to discover license and
4577 copyright changes in the upstream source. I will try to do the same
4578 with my packages in the future.
</p
>
4580 <p
><strong
>Update
2016-
02-
21</strong
>: The cme author recommended
4581 against using -quiet for new users, so I removed it from the proposed
4582 command line.
</p
>
4587 <title>Using appstream in Debian to locate packages with firmware and mime type support
</title>
4588 <link>https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</link>
4589 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_in_Debian_to_locate_packages_with_firmware_and_mime_type_support.html
</guid>
4590 <pubDate>Thu,
4 Feb
2016 16:
40:
00 +
0100</pubDate>
4591 <description><p
>The
<a href=
"https://wiki.debian.org/DEP-
11">appstream system
</a
>
4592 is taking shape in Debian, and one provided feature is a very
4593 convenient way to tell you which package to install to make a given
4594 firmware file available when the kernel is looking for it. This can
4595 be done using apt-file too, but that is for someone else to blog
4598 <p
>Here is a small recipe to find the package with a given firmware
4599 file, in this example I am looking for ctfw-
3.2.3.0.bin, randomly
4600 picked from the set of firmware announced using appstream in Debian
4601 unstable. In general you would be looking for the firmware requested
4602 by the kernel during kernel module loading. To find the package
4603 providing the example file, do like this:
</p
>
4605 <blockquote
><pre
>
4606 % apt install appstream
4610 % appstreamcli what-provides firmware:runtime ctfw-
3.2.3.0.bin | \
4611 awk
'/Package:/ {print $
2}
'
4614 </pre
></blockquote
>
4616 <p
>See
<a href=
"https://wiki.debian.org/AppStream/Guidelines
">the
4617 appstream wiki
</a
> page to learn how to embed the package metadata in
4618 a way appstream can use.
</p
>
4620 <p
>This same approach can be used to find any package supporting a
4621 given MIME type. This is very useful when you get a file you do not
4622 know how to handle. First find the mime type using
<tt
>file
4623 --mime-type
</tt
>, and next look up the package providing support for
4624 it. Lets say you got an SVG file. Its MIME type is image/svg+xml,
4625 and you can find all packages handling this type like this:
</p
>
4627 <blockquote
><pre
>
4628 % apt install appstream
4632 % appstreamcli what-provides mimetype image/svg+xml | \
4633 awk
'/Package:/ {print $
2}
'
4655 </pre
></blockquote
>
4657 <p
>I believe the MIME types are fetched from the desktop file for
4658 packages providing appstream metadata.
</p
>
4663 <title>Creepy, visualise geotagged social media information - nice free software
</title>
4664 <link>https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</link>
4665 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Creepy__visualise_geotagged_social_media_information___nice_free_software.html
</guid>
4666 <pubDate>Sun,
24 Jan
2016 10:
50:
00 +
0100</pubDate>
4667 <description><p
>Most people seem not to realise that every time they walk around
4668 with the computerised radio beacon known as a mobile phone their
4669 position is tracked by the phone company and often stored for a long
4670 time (like every time a SMS is received or sent). And if their
4671 computerised radio beacon is capable of running programs (often called
4672 mobile apps) downloaded from the Internet, these programs are often
4673 also capable of tracking their location (if the app requested access
4674 during installation). And when these programs send out information to
4675 central collection points, the location is often included, unless
4676 extra care is taken to not send the location. The provided
4677 information is used by several entities, for good and bad (what is
4678 good and bad, depend on your point of view). What is certain, is that
4679 the private sphere and the right to free movement is challenged and
4680 perhaps even eradicated for those announcing their location this way,
4681 when they share their whereabouts with private and public
4684 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2016-
01-
24-nice-creepy-desktop-window.png
"></p
>
4686 <p
>The phone company logs provide a register of locations to check out
4687 when one want to figure out what the tracked person was doing. It is
4688 unavailable for most of us, but provided to selected government
4689 officials, company staff, those illegally buying information from
4690 unfaithful servants and crackers stealing the information. But the
4691 public information can be collected and analysed, and a free software
4692 tool to do so is called
4693 <a href=
"http://www.geocreepy.com/
">Creepy or Cree.py
</a
>. I
4694 discovered it when I read
4695 <a href=
"http://www.aftenposten.no/kultur/Slik-kan-du-bli-overvaket-pa-Twitter-og-Instagram-uten-a-ane-det-
7787884.html
">an
4696 article about Creepy
</a
> in the Norwegian newspaper Aftenposten i
4697 November
2014, and decided to check if it was available in Debian.
4698 The python program was in Debian, but
4699 <a href=
"https://tracker.debian.org/pkg/creepy
">the version in
4700 Debian
</a
> was completely broken and practically unmaintained. I
4701 uploaded a new version which did not work quite right, but did not
4702 have time to fix it then. This Christmas I decided to finally try to
4703 get Creepy operational in Debian. Now a fixed version is available in
4704 Debian unstable and testing, and almost all Debian specific patches
4706 <a href=
"https://github.com/jkakavas/creepy
">upstream
</a
>.
</p
>
4708 <p
>The Creepy program visualises geolocation information fetched from
4709 Twitter, Instagram, Flickr and Google+, and allow one to get a
4710 complete picture of every social media message posted recently in a
4711 given area, or track the movement of a given individual across all
4712 these services. Earlier it was possible to use the search API of at
4713 least some of these services without identifying oneself, but these
4714 days it is impossible. This mean that to use Creepy, you need to
4715 configure it to log in as yourself on these services, and provide
4716 information to them about your search interests. This should be taken
4717 into account when using Creepy, as it will also share information
4718 about yourself with the services.
</p
>
4720 <p
>The picture above show the twitter messages sent from (or at least
4721 geotagged with a position from) the city centre of Oslo, the capital
4722 of Norway. One useful way to use Creepy is to first look at
4723 information tagged with an area of interest, and next look at all the
4724 information provided by one or more individuals who was in the area.
4725 I tested it by checking out which celebrity provide their location in
4726 twitter messages by checkout out who sent twitter messages near a
4727 Norwegian TV station, and next could track their position over time,
4728 making it possible to locate their home and work place, among other
4729 things. A similar technique have been
4730 <a href=
"http://www.buzzfeed.com/maxseddon/does-this-soldiers-instagram-account-prove-russia-is-covertl
">used
4731 to locate Russian soldiers in Ukraine
</a
>, and it is both a powerful
4732 tool to discover lying governments, and a useful tool to help people
4733 understand the value of the private information they provide to the
4736 <p
>The package is not trivial to backport to Debian Stable/Jessie, as
4737 it depend on several python modules currently missing in Jessie (at
4738 least python-instagram, python-flickrapi and
4739 python-requests-toolbelt).
</p
>
4741 <p
>(I have uploaded
4742 <a href=
"https://screenshots.debian.net/package/creepy
">the image to
4743 screenshots.debian.net
</a
> and licensed it under the same terms as the
4744 Creepy program in Debian.)
</p
>
4749 <title>Always download Debian packages using Tor - the simple recipe
</title>
4750 <link>https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</link>
4751 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Always_download_Debian_packages_using_Tor___the_simple_recipe.html
</guid>
4752 <pubDate>Fri,
15 Jan
2016 00:
30:
00 +
0100</pubDate>
4753 <description><p
>During his DebConf15 keynote, Jacob Appelbaum
4754 <a href=
"https://summit.debconf.org/debconf15/meeting/
331/what-is-to-be-done/
">observed
4755 that those listening on the Internet lines would have good reason to
4756 believe a computer have a given security hole
</a
> if it download a
4757 security fix from a Debian mirror. This is a good reason to always
4758 use encrypted connections to the Debian mirror, to make sure those
4759 listening do not know which IP address to attack. In August, Richard
4760 Hartmann observed that encryption was not enough, when it was possible
4761 to interfere download size to security patches or the fact that
4762 download took place shortly after a security fix was released, and
4763 <a href=
"http://richardhartmann.de/blog/posts/
2015/
08/
24-Tor-enabled_Debian_mirror/
">proposed
4764 to always use Tor to download packages from the Debian mirror
</a
>. He
4765 was not the first to propose this, as the
4766 <tt
><a href=
"https://tracker.debian.org/pkg/apt-transport-tor
">apt-transport-tor
</a
></tt
>
4767 package by Tim Retout already existed to make it easy to convince apt
4768 to use
<a href=
"https://www.torproject.org/
">Tor
</a
>, but I was not
4769 aware of that package when I read the blog post from Richard.
</p
>
4771 <p
>Richard discussed the idea with Peter Palfrader, one of the Debian
4772 sysadmins, and he set up a Tor hidden service on one of the central
4773 Debian mirrors using the address vwakviie2ienjx6t.onion, thus making
4774 it possible to download packages directly between two tor nodes,
4775 making sure the network traffic always were encrypted.
</p
>
4777 <p
>Here is a short recipe for enabling this on your machine, by
4778 installing
<tt
>apt-transport-tor
</tt
> and replacing http and https
4779 urls with tor+http and tor+https, and using the hidden service instead
4780 of the official Debian mirror site. I recommend installing
4781 <tt
>etckeeper
</tt
> before you start to have a history of the changes
4782 done in /etc/.
</p
>
4784 <blockquote
><pre
>
4785 apt install apt-transport-tor
4786 sed -i
's% http://ftp.debian.org/% tor+http://vwakviie2ienjx6t.onion/%
' /etc/apt/sources.list
4787 sed -i
's% http% tor+http%
' /etc/apt/sources.list
4788 </pre
></blockquote
>
4790 <p
>If you have more sources listed in /etc/apt/sources.list.d/, run
4791 the sed commands for these too. The sed command is assuming your are
4792 using the ftp.debian.org Debian mirror. Adjust the command (or just
4793 edit the file manually) to match your mirror.
</p
>
4795 <p
>This work in Debian Jessie and later. Note that tools like
4796 <tt
>apt-file
</tt
> only recently started using the apt transport
4797 system, and do not work with these tor+http URLs. For
4798 <tt
>apt-file
</tt
> you need the version currently in experimental,
4799 which need a recent apt version currently only in unstable. So if you
4800 need a working
<tt
>apt-file
</tt
>, this is not for you.
</p
>
4802 <p
>Another advantage from this change is that your machine will start
4803 using Tor regularly and at fairly random intervals (every time you
4804 update the package lists or upgrade or install a new package), thus
4805 masking other Tor traffic done from the same machine. Using Tor will
4806 become normal for the machine in question.
</p
>
4808 <p
>On
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
</a
>, APT
4809 is set up by default to use
<tt
>apt-transport-tor
</tt
> when Tor is
4810 enabled. It would be great if it was the default on any Debian
4816 <title>OpenALPR, find car license plates in video streams - nice free software
</title>
4817 <link>https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</link>
4818 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/OpenALPR__find_car_license_plates_in_video_streams___nice_free_software.html
</guid>
4819 <pubDate>Wed,
23 Dec
2015 01:
00:
00 +
0100</pubDate>
4820 <description><p
>When I was a kid, we used to collect
"car numbers
", as we used to
4821 call the car license plate numbers in those days. I would write the
4822 numbers down in my little book and compare notes with the other kids
4823 to see how many region codes we had seen and if we had seen some
4824 exotic or special region codes and numbers. It was a fun game to pass
4825 time, as we kids have plenty of it.
</p
>
4827 <p
>A few days I came across
4828 <a href=
"https://github.com/openalpr/openalpr
">the OpenALPR
4829 project
</a
>, a free software project to automatically discover and
4830 report license plates in images and video streams, and provide the
4831 "car numbers
" in a machine readable format. I
've been looking for
4832 such system for a while now, because I believe it is a bad idea that the
4833 <a href=
"https://en.wikipedia.org/wiki/Automatic_number_plate_recognition
">automatic
4834 number plate recognition
</a
> tool only is available in the hands of
4835 the powerful, and want it to be available also for the powerless to
4836 even the score when it comes to surveillance and sousveillance. I
4837 discovered the developer
4838 <a href=
"https://bugs.debian.org/
747509">wanted to get the tool into
4839 Debian
</a
>, and as I too wanted it to be in Debian, I volunteered to
4840 help him get it into shape to get the package uploaded into the Debian
4843 <p
>Today we finally managed to get the package into shape and uploaded
4844 it into Debian, where it currently
4845 <a href=
"https://ftp-master.debian.org//new/openalpr_2.2
.1-
1.html
">waits
4846 in the NEW queue
</a
> for review by the Debian ftpmasters.
</p
>
4848 <p
>I guess you are wondering why on earth such tool would be useful
4849 for the common folks, ie those not running a large government
4850 surveillance system? Well, I plan to put it in a computer on my bike
4851 and in my car, tracking the cars nearby and allowing me to be notified
4852 when number plates on my watch list are discovered. Another use case
4853 was suggested by a friend of mine, who wanted to set it up at his home
4854 to open the car port automatically when it discovered the plate on his
4855 car. When I mentioned it perhaps was a bit foolhardy to allow anyone
4856 capable of placing his license plate number of a piece of cardboard to
4857 open his car port, men replied that it was always unlocked anyway. I
4858 guess for such use case it make sense. I am sure there are other use
4859 cases too, for those with imagination and a vision.
</p
>
4861 <p
>If you want to build your own version of the Debian package, check
4862 out the upstream git source and symlink ./distros/debian to ./debian/
4863 before running
"debuild
" to build the source. Or wait a bit until the
4864 package show up in unstable.
</p
>
4869 <title>Using appstream with isenkram to install hardware related packages in Debian
</title>
4870 <link>https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</link>
4871 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_appstream_with_isenkram_to_install_hardware_related_packages_in_Debian.html
</guid>
4872 <pubDate>Sun,
20 Dec
2015 12:
20:
00 +
0100</pubDate>
4873 <description><p
>Around three years ago, I created
4874 <a href=
"http://packages.qa.debian.org/isenkram
">the isenkram
4875 system
</a
> to get a more practical solution in Debian for handing
4876 hardware related packages. A GUI system in the isenkram package will
4877 present a pop-up dialog when some hardware dongle supported by
4878 relevant packages in Debian is inserted into the machine. The same
4879 lookup mechanism to detect packages is available as command line
4880 tools in the isenkram-cli package. In addition to mapping hardware,
4881 it will also map kernel firmware files to packages and make it easy to
4882 install needed firmware packages automatically. The key for this
4883 system to work is a good way to map hardware to packages, in other
4884 words, allow packages to announce what hardware they will work
4887 <p
>I started by providing data files in the isenkram source, and
4888 adding code to download the latest version of these data files at run
4889 time, to ensure every user had the most up to date mapping available.
4890 I also added support for storing the mapping in the Packages file in
4891 the apt repositories, but did not push this approach because while I
4892 was trying to figure out how to best store hardware/package mappings,
4893 <a href=
"http://www.freedesktop.org/software/appstream/docs/
">the
4894 appstream system
</a
> was announced. I got in touch and suggested to
4895 add the hardware mapping into that data set to be able to use
4896 appstream as a data source, and this was accepted at least for the
4897 Debian version of appstream.
</p
>
4899 <p
>A few days ago using appstream in Debian for this became possible,
4900 and today I uploaded a new version
0.20 of isenkram adding support for
4901 appstream as a data source for mapping hardware to packages. The only
4902 package so far using appstream to announce its hardware support is my
4903 pymissile package. I got help from Matthias Klumpp with figuring out
4904 how do add the required
4905 <a href=
"https://appstream.debian.org/html/sid/main/metainfo/pymissile.html
">metadata
4906 in pymissile
</a
>. I added a file debian/pymissile.metainfo.xml with
4907 this content:
</p
>
4909 <blockquote
><pre
>
4910 &lt;?xml version=
"1.0" encoding=
"UTF-
8"?
&gt;
4911 &lt;component
&gt;
4912 &lt;id
&gt;pymissile
&lt;/id
&gt;
4913 &lt;metadata_license
&gt;MIT
&lt;/metadata_license
&gt;
4914 &lt;name
&gt;pymissile
&lt;/name
&gt;
4915 &lt;summary
&gt;Control original Striker USB Missile Launcher
&lt;/summary
&gt;
4916 &lt;description
&gt;
4918 Pymissile provides a curses interface to control an original
4919 Marks and Spencer / Striker USB Missile Launcher, as well as a
4920 motion control script to allow a webcamera to control the
4923 &lt;/description
&gt;
4924 &lt;provides
&gt;
4925 &lt;modalias
&gt;usb:v1130p0202d*
&lt;/modalias
&gt;
4926 &lt;/provides
&gt;
4927 &lt;/component
&gt;
4928 </pre
></blockquote
>
4930 <p
>The key for isenkram is the component/provides/modalias value,
4931 which is a glob style match rule for hardware specific strings
4932 (modalias strings) provided by the Linux kernel. In this case, it
4933 will map to all USB devices with vendor code
1130 and product code
4936 <p
>Note, it is important that the license of all the metadata files
4937 are compatible to have permissions to aggregate them into archive wide
4938 appstream files. Matthias suggested to use MIT or BSD licenses for
4939 these files. A challenge is figuring out a good id for the data, as
4940 it is supposed to be globally unique and shared across distributions
4941 (in other words, best to coordinate with upstream what to use). But
4942 it can be changed later or, so we went with the package name as
4943 upstream for this project is dormant.
</p
>
4945 <p
>To get the metadata file installed in the correct location for the
4946 mirror update scripts to pick it up and include its content the
4947 appstream data source, the file must be installed in the binary
4948 package under /usr/share/appdata/. I did this by adding the following
4949 line to debian/pymissile.install:
</p
>
4951 <blockquote
><pre
>
4952 debian/pymissile.metainfo.xml usr/share/appdata
4953 </pre
></blockquote
>
4955 <p
>With that in place, the command line tool isenkram-lookup will list
4956 all packages useful on the current computer automatically, and the GUI
4957 pop-up handler will propose to install the package not already
4958 installed if a hardware dongle is inserted into the machine in
4961 <p
>Details of the modalias field in appstream is available from the
4962 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
> proposal.
</p
>
4964 <p
>To locate the modalias values of all hardware present in a machine,
4965 try running this command on the command line:
</p
>
4967 <blockquote
><pre
>
4968 cat $(find /sys/devices/|grep modalias)
4969 </pre
></blockquote
>
4971 <p
>To learn more about the isenkram system, please check out
4972 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">my
4973 blog posts tagged isenkram
</a
>.
</p
>
4978 <title>The GNU General Public License is not magic pixie dust
</title>
4979 <link>https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</link>
4980 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_GNU_General_Public_License_is_not_magic_pixie_dust.html
</guid>
4981 <pubDate>Mon,
30 Nov
2015 09:
55:
00 +
0100</pubDate>
4982 <description><p
>A blog post from my fellow Debian developer Paul Wise titled
4983 "<a href=
"http://bonedaddy.net/pabs3/log/
2015/
11/
27/sfc-supporter/
">The
4984 GPL is not magic pixie dust
</a
>" explain the importance of making sure
4985 the
<a href=
"http://www.gnu.org/copyleft/gpl.html
">GPL
</a
> is enforced.
4986 I quote the blog post from Paul in full here with his permission:
<p
>
4990 <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
>
4993 The GPL is not magic pixie dust. It does not work by itself.
<br/
>
4995 The first step is to choose a
4996 <a href=
"https://copyleft.org/
">copyleft
</a
> license for your
4999 The next step is, when someone fails to follow that copyleft license,
5000 <b
>it must be enforced
</b
><br/
>
5002 and its a simple fact of our modern society that such type of
5005 is incredibly expensive to do and incredibly difficult to do.
5008 <p
><small
>--
<a href=
"http://ebb.org/bkuhn/
">Bradley Kuhn
</a
>, in
5009 <a href=
"http://faif.us/
" title=
"Free as in Freedom
">FaiF
</a
>
5010 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
5011 0x57</a
></small
></p
>
5013 <p
>As the Debian Website
5014 <a href=
"https://bugs.debian.org/
794116">used
</a
>
5015 <a href=
"https://anonscm.debian.org/viewvc/webwml/webwml/english/intro/free.wml?r1=
1.24&amp;r2=
1.25">to
</a
>
5016 imply, public domain and permissively licensed software can lead to
5017 the production of more proprietary software as people discover useful
5018 software, extend it and or incorporate it into their hardware or
5019 software products. Copyleft licenses such as the GNU GPL were created
5020 to close off this avenue to the production of proprietary software but
5021 such licenses are not enough. With the ongoing adoption of Free
5022 Software by individuals and groups, inevitably the community
's
5023 expectations of license compliance are violated, usually out of
5024 ignorance of the way Free Software works, but not always. As Karen
5025 and Bradley explained in
<a href=
"http://faif.us/
" title=
"Free as in
5026 Freedom
">FaiF
</a
>
5027 <a href=
"http://faif.us/cast/
2015/nov/
24/
0x57/
">episode
0x57</a
>,
5028 copyleft is nothing if no-one is willing and able to stand up in court
5029 to protect it. The reality of today
's world is that legal
5030 representation is expensive, difficult and time consuming. With
5031 <a href=
"http://gpl-violations.org/
">gpl-violations.org
</a
> in hiatus
5032 <a href=
"http://gpl-violations.org/news/
20151027-homepage-recovers/
">until
</a
>
5033 some time in
2016, the
<a href=
"https://sfconservancy.org/
">Software
5034 Freedom Conservancy
</a
> (a tax-exempt charity) is the major defender
5035 of the Linux project, Debian and other groups against GPL violations.
5036 In March the SFC supported a
5037 <a href=
"https://sfconservancy.org/news/
2015/mar/
05/vmware-lawsuit/
">lawsuit
5038 by Christoph Hellwig
</a
> against VMware for refusing to
5039 <a href=
"https://sfconservancy.org/linux-compliance/vmware-lawsuit-faq.html
">comply
5040 with the GPL
</a
> in relation to their use of parts of the Linux
5041 kernel. Since then two of their sponsors pulled corporate funding and
5043 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">blocked
5044 or cancelled their talks
</a
>. As a result they have decided to rely
5045 less on corporate funding and more on the broad community of
5046 individuals who support Free Software and copyleft. So the SFC has
5047 <a href=
"https://sfconservancy.org/news/
2015/nov/
23/
2015fundraiser/
">launched
</a
>
5048 a
<a href=
"https://sfconservancy.org/supporter/
">campaign
</a
> to create
5049 a community of folks who stand up for copyleft and the GPL by
5050 supporting their work on promoting and supporting copyleft and Free
5053 <p
>If you support Free Software,
5054 <a href=
"https://sfconservancy.org/blog/
2015/nov/
26/like-what-I-do/
">like
</a
>
5055 what the SFC do, agree with their
5056 <a href=
"https://sfconservancy.org/linux-compliance/principles.html
">compliance
5057 principles
</a
>, are happy about their
5058 <a href=
"https://sfconservancy.org/supporter/
">successes
</a
> in
2015,
5059 work on a project that is an SFC
5060 <a href=
"https://sfconservancy.org/members/current/
">member
</a
> and or
5061 just want to stand up for copyleft, please join
5062 <a href=
"https://identi.ca/cwebber/image/JQGPA4qbTyyp3-MY8QpvuA
">Christopher
5063 Allan Webber
</a
>,
5064 <a href=
"https://sfconservancy.org/blog/
2015/nov/
24/faif-carols-fundraiser/
">Carol
5066 <a href=
"http://www.jonobacon.org/
2015/
11/
25/supporting-software-freedom-conservancy/
">Jono
5067 Bacon
</a
>, myself and
5068 <a href=
"https://sfconservancy.org/sponsors/#supporters
">others
</a
> in
5070 <a href=
"https://sfconservancy.org/supporter/
">supporter
</a
>. For the
5071 next week your donation will be
5072 <a href=
"https://sfconservancy.org/news/
2015/nov/
27/black-friday/
">matched
</a
>
5073 by an anonymous donor. Please also consider asking your employer to
5074 match your donation or become a sponsor of SFC. Don
't forget to
5075 spread the word about your support for SFC via email, your blog and or
5076 social media accounts.
</p
>
5080 <p
>I agree with Paul on this topic and just signed up as a Supporter
5081 of Software Freedom Conservancy myself. Perhaps you should be a
5082 supporter too?
</p
>
5087 <title>PGP key transition statement for key EE4E02F9
</title>
5088 <link>https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</link>
5089 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/PGP_key_transition_statement_for_key_EE4E02F9.html
</guid>
5090 <pubDate>Tue,
17 Nov
2015 10:
50:
00 +
0100</pubDate>
5091 <description><p
>I
've needed a new OpenPGP key for a while, but have not had time to
5092 set it up properly. I wanted to generate it offline and have it
5093 available on
<a href=
"http://shop.kernelconcepts.de/#openpgp
">a OpenPGP
5094 smart card
</a
> for daily use, and learning how to do it and finding
5095 time to sit down with an offline machine almost took forever. But
5096 finally I
've been able to complete the process, and have now moved
5097 from my old GPG key to a new GPG key. See
5098 <a href=
"http://people.skolelinux.org/pere/blog/images/
2015-
11-
17-new-gpg-key-transition.txt
">the
5099 full transition statement, signed with both my old and new key
</a
> for
5100 the details. This is my new key:
</p
>
5103 pub
3936R/
<a href=
"http://pgp.cs.uu.nl/stats/
111D6B29EE4E02F9.html
">111D6B29EE4E02F9
</a
> 2015-
11-
03 [expires:
2019-
11-
14]
5104 Key fingerprint =
3AC7 B2E3 ACA5 DF87
78F1 D827
111D
6B29 EE4E
02F9
5105 uid Petter Reinholdtsen
&lt;pere@hungry.com
&gt;
5106 uid Petter Reinholdtsen
&lt;pere@debian.org
&gt;
5107 sub
4096R/
87BAFB0E
2015-
11-
03 [expires:
2019-
11-
02]
5108 sub
4096R/F91E6DE9
2015-
11-
03 [expires:
2019-
11-
02]
5109 sub
4096R/A0439BAB
2015-
11-
03 [expires:
2019-
11-
02]
5112 <p
>The key can be downloaded from the OpenPGP key servers, signed by
5113 my old key.
</p
>
5115 <p
>If you signed my old key
5116 (
<a href=
"http://pgp.cs.uu.nl/stats/DB4CCC4B2A30D729.html
">DB4CCC4B2A30D729
</a
>),
5117 I
'd very much appreciate a signature on my new key, details and
5118 instructions in the transition statement. I m happy to reciprocate if
5119 you have a similarly signed transition statement to present.
</p
>
5124 <title>The life and death of a laptop battery
</title>
5125 <link>https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</link>
5126 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_life_and_death_of_a_laptop_battery.html
</guid>
5127 <pubDate>Thu,
24 Sep
2015 16:
00:
00 +
0200</pubDate>
5128 <description><p
>When I get a new laptop, the battery life time at the start is OK.
5129 But this do not last. The last few laptops gave me a feeling that
5130 within a year, the life time is just a fraction of what it used to be,
5131 and it slowly become painful to use the laptop without power connected
5132 all the time. Because of this, when I got a new Thinkpad X230 laptop
5133 about two years ago, I decided to monitor its battery state to have
5134 more hard facts when the battery started to fail.
</p
>
5136 <img src=
"http://people.skolelinux.org/pere/blog/images/
2015-
09-
24-laptop-battery-graph.png
"/
>
5138 <p
>First I tried to find a sensible Debian package to record the
5139 battery status, assuming that this must be a problem already handled
5140 by someone else. I found
5141 <a href=
"https://tracker.debian.org/pkg/battery-stats
">battery-stats
</a
>,
5142 which collects statistics from the battery, but it was completely
5143 broken. I sent a few suggestions to the maintainer, but decided to
5144 write my own collector as a shell script while I waited for feedback
5146 <a href=
"http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
">a
5147 blog post about the battery development on a MacBook Air
</a
> I also
5149 <a href=
"https://github.com/jradavenport/batlog.git
">batlog
</a
>, not
5150 available in Debian.
</p
>
5152 <p
>I started my collector
2013-
07-
15, and it has been collecting
5153 battery stats ever since. Now my
5154 /var/log/hjemmenett-battery-status.log file contain around
115,
000
5155 measurements, from the time the battery was working great until now,
5156 when it is unable to charge above
7% of original capacity. My
5157 collector shell script is quite simple and look like this:
</p
>
5162 # http://www.ifweassume.com/
2013/
08/the-de-evolution-of-my-laptop-battery.html
5164 # http://blog.sleeplessbeastie.eu/
2013/
01/
02/debian-how-to-monitor-battery-capacity/
5165 logfile=/var/log/hjemmenett-battery-status.log
5167 files=
"manufacturer model_name technology serial_number \
5168 energy_full energy_full_design energy_now cycle_count status
"
5170 if [ ! -e
"$logfile
" ] ; then
5172 printf
"timestamp,
"
5174 printf
"%s,
" $f
5177 )
> "$logfile
"
5181 # Print complete message in one echo call, to avoid race condition
5182 # when several log processes run in parallel.
5183 msg=$(printf
"%s,
" $(date +%s); \
5184 for f in $files; do \
5185 printf
"%s,
" $(cat $f); \
5187 echo
"$msg
"
5190 cd /sys/class/power_supply
5193 (cd $bat
&& log_battery
>> "$logfile
")
5197 <p
>The script is called when the power management system detect a
5198 change in the power status (power plug in or out), and when going into
5199 and out of hibernation and suspend. In addition, it collect a value
5200 every
10 minutes. This make it possible for me know when the battery
5201 is discharging, charging and how the maximum charge change over time.
5202 The code for the Debian package
5203 <a href=
"https://github.com/petterreinholdtsen/battery-status
">is now
5204 available on github
</a
>.
</p
>
5206 <p
>The collected log file look like this:
</p
>
5209 timestamp,manufacturer,model_name,technology,serial_number,energy_full,energy_full_design,energy_now,cycle_count,status,
5210 1376591133,LGC,
45N1025,Li-ion,
974,
62800000,
62160000,
39050000,
0,Discharging,
5212 1443090528,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
5213 1443090601,LGC,
45N1025,Li-ion,
974,
4900000,
62160000,
4900000,
0,Full,
5216 <p
>I wrote a small script to create a graph of the charge development
5217 over time. This graph depicted above show the slow death of my laptop
5220 <p
>But why is this happening? Why are my laptop batteries always
5221 dying in a year or two, while the batteries of space probes and
5222 satellites keep working year after year. If we are to believe
5223 <a href=
"http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
">Battery
5224 University
</a
>, the cause is me charging the battery whenever I have a
5225 chance, and the fix is to not charge the Lithium-ion batteries to
100%
5226 all the time, but to stay below
90% of full charge most of the time.
5227 I
've been told that the Tesla electric cars
5228 <a href=
"http://my.teslamotors.com/de_CH/forum/forums/battery-charge-limit
">limit
5229 the charge of their batteries to
80%
</a
>, with the option to charge to
5230 100% when preparing for a longer trip (not that I would want a car
5231 like Tesla where rights to privacy is abandoned, but that is another
5232 story), which I guess is the option we should have for laptops on
5233 Linux too.
</p
>
5235 <p
>Is there a good and generic way with Linux to tell the battery to
5236 stop charging at
80%, unless requested to charge to
100% once in
5237 preparation for a longer trip? I found
5238 <a href=
"http://askubuntu.com/questions/
34452/how-can-i-limit-battery-charging-to-
80-capacity
">one
5239 recipe on askubuntu for Ubuntu to limit charging on Thinkpad to
5240 80%
</a
>, but could not get it to work (kernel module refused to
5243 <p
>I wonder why the battery capacity was reported to be more than
100%
5244 at the start. I also wonder why the
"full capacity
" increases some
5245 times, and if it is possible to repeat the process to get the battery
5246 back to design capacity. And I wonder if the discharge and charge
5247 speed change over time, or if this stay the same. I did not yet try
5248 to write a tool to calculate the derivative values of the battery
5249 level, but suspect some interesting insights might be learned from
5252 <p
>Update
2015-
09-
24: I got a tip to install the packages
5253 acpi-call-dkms and tlp (unfortunately missing in Debian stable)
5254 packages instead of the tp-smapi-dkms package I had tried to use
5255 initially, and use
'tlp setcharge
40 80' to change when charging start
5256 and stop. I
've done so now, but expect my existing battery is toast
5257 and need to be replaced. The proposal is unfortunately Thinkpad
5263 <title>New laptop - some more clues and ideas based on feedback
</title>
5264 <link>https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</link>
5265 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_laptop___some_more_clues_and_ideas_based_on_feedback.html
</guid>
5266 <pubDate>Sun,
5 Jul
2015 21:
40:
00 +
0200</pubDate>
5267 <description><p
>Several people contacted me after my previous blog post about my
5268 need for a new laptop, and provided very useful feedback. I wish to
5269 thank every one of these. Several pointed me to the possibility of
5270 fixing my X230, and I am already in the process of getting Lenovo to
5271 do so thanks to the on site, next day support contract covering the
5272 machine. But the battery is almost useless (I expect to replace it
5273 with a non-official battery) and I do not expect the machine to live
5274 for many more years, so it is time to plan its replacement. If I did
5275 not have a support contract, it was suggested to find replacement parts
5276 using
<a href=
"http://www.francecrans.com/
">FrancEcrans
</a
>, but it
5277 might present a language barrier as I do not understand French.
</p
>
5279 <p
>One tip I got was to use the
5280 <a href=
"https://skinflint.co.uk/?cat=nb
">Skinflint
</a
> web service to
5281 compare laptop models. It seem to have more models available than
5282 prisjakt.no. Another tip I got from someone I know have similar
5283 keyboard preferences was that the HP EliteBook
840 keyboard is not
5284 very good, and this matches my experience with earlier EliteBook
5285 keyboards I tested. Because of this, I will not consider it any further.
5287 <p
>When I wrote my blog post, I was not aware of Thinkpad X250, the
5288 newest Thinkpad X model. The keyboard reintroduces mouse buttons
5289 (which is missing from the X240), and is working fairly well with
5290 Debian Sid/Unstable according to
5291 <a href=
"http://www.corsac.net/X250/
">Corsac.net
</a
>. The reports I
5292 got on the keyboard quality are not consistent. Some say the keyboard
5293 is good, others say it is ok, while others say it is not very good.
5294 Those with experience from X41 and and X60 agree that the X250
5295 keyboard is not as good as those trusty old laptops, and suggest I
5296 keep and fix my X230 instead of upgrading, or get a used X230 to
5297 replace it. I
'm also told that the X250 lack leds for caps lock, disk
5298 activity and battery status, which is very convenient on my X230. I
'm
5299 also told that the CPU fan is running very often, making it a bit
5300 noisy. In any case, the X250 do not work out of the box with Debian
5301 Stable/Jessie, one of my requirements.
</p
>
5303 <p
>I have also gotten a few vendor proposals, one was
5304 <a href=
"http://pro-star.com
">Pro-Star
</a
>, another was
5305 <a href=
"http://shop.gluglug.org.uk/product/libreboot-x200/
">Libreboot
</a
>.
5306 The latter look very attractive to me.
</p
>
5308 <p
>Again, thank you all for the very useful feedback. It help a lot
5309 as I keep looking for a replacement.
</p
>
5311 <p
>Update
2015-
07-
06: I was recommended to check out the
5312 <a href=
"">lapstore.de
</a
> web shop for used laptops. They got several
5314 <a href=
"http://www.lapstore.de/f.php/shop/lapstore/f/
411/lang/x/kw/Lenovo_ThinkPad_X_Serie/
">old
5315 thinkpad X models
</a
>, and provide one year warranty.
</p
>
5320 <title>Time to find a new laptop, as the old one is broken after only two years
</title>
5321 <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>
5322 <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>
5323 <pubDate>Fri,
3 Jul
2015 07:
10:
00 +
0200</pubDate>
5324 <description><p
>My primary work horse laptop is failing, and will need a
5325 replacement soon. The left
5 cm of the screen on my Thinkpad X230
5326 started flickering yesterday, and I suspect the cause is a broken
5327 cable, as changing the angle of the screen some times get rid of the
5328 flickering.
</p
>
5330 <p
>My requirements have not really changed since I bought it, and is
5332 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">I
5333 described them in
2013</a
>. The last time I bought a laptop, I had
5335 <a href=
"http://www.prisjakt.no/category.php?k=
353">prisjakt.no
</a
>
5336 where I could select at least a few of the requirements (mouse pin,
5337 wifi, weight) and go through the rest manually. Three button mouse
5338 and a good keyboard is not available as an option, and all the three
5339 laptop models proposed today (Thinkpad X240, HP EliteBook
820 G1 and
5340 G2) lack three mouse buttons). It is also unclear to me how good the
5341 keyboard on the HP EliteBooks are. I hope Lenovo have not messed up
5342 the keyboard, even if the quality and robustness in the X series have
5343 deteriorated since X41.
</p
>
5345 <p
>I wonder how I can find a sensible laptop when none of the options
5346 seem sensible to me? Are there better services around to search the
5347 set of available laptops for features? Please send me an email if you
5348 have suggestions.
</p
>
5350 <p
>Update
2015-
07-
23: I got a suggestion to check out the FSF
5351 <a href=
"http://www.fsf.org/resources/hw/endorsement/respects-your-freedom
">list
5352 of endorsed hardware
</a
>, which is useful background information.
</p
>
5357 <title>How to stay with sysvinit in Debian Jessie
</title>
5358 <link>https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</link>
5359 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_stay_with_sysvinit_in_Debian_Jessie.html
</guid>
5360 <pubDate>Sat,
22 Nov
2014 01:
00:
00 +
0100</pubDate>
5361 <description><p
>By now, it is well known that Debian Jessie will not be using
5362 sysvinit as its boot system by default. But how can one keep using
5363 sysvinit in Jessie? It is fairly easy, and here are a few recipes,
5365 <a href=
"http://www.vitavonni.de/blog/
201410/
2014102101-avoiding-systemd.html
">Erich
5366 Schubert
</a
> and
5367 <a href=
"http://smcv.pseudorandom.co.uk/
2014/still_universal/
">Simon
5370 <p
>If you already are using Wheezy and want to upgrade to Jessie and
5371 keep sysvinit as your boot system, create a file
5372 <tt
>/etc/apt/preferences.d/use-sysvinit
</tt
> with this content before
5373 you upgrade:
</p
>
5375 <p
><blockquote
><pre
>
5376 Package: systemd-sysv
5377 Pin: release o=Debian
5379 </pre
></blockquote
><p
>
5381 <p
>This file content will tell apt and aptitude to not consider
5382 installing systemd-sysv as part of any installation and upgrade
5383 solution when resolving dependencies, and thus tell it to avoid
5384 systemd as a default boot system. The end result should be that the
5385 upgraded system keep using sysvinit.
</p
>
5387 <p
>If you are installing Jessie for the first time, there is no way to
5388 get sysvinit installed by default (debootstrap used by
5389 debian-installer have no option for this), but one can tell the
5390 installer to switch to sysvinit before the first boot. Either by
5391 using a kernel argument to the installer, or by adding a line to the
5392 preseed file used. First, the kernel command line argument:
5394 <p
><blockquote
><pre
>
5395 preseed/late_command=
"in-target apt-get install --purge -y sysvinit-core
"
5396 </pre
></blockquote
><p
>
5398 <p
>Next, the line to use in a preseed file:
</p
>
5400 <p
><blockquote
><pre
>
5401 d-i preseed/late_command string in-target apt-get install -y sysvinit-core
5402 </pre
></blockquote
><p
>
5404 <p
>One can of course also do this after the first boot by installing
5405 the sysvinit-core package.
</p
>
5407 <p
>I recommend only using sysvinit if you really need it, as the
5408 sysvinit boot sequence in Debian have several hardware specific bugs
5409 on Linux caused by the fact that it is unpredictable when hardware
5410 devices show up during boot. But on the other hand, the new default
5411 boot system still have a few rough edges I hope will be fixed before
5412 Jessie is released.
</p
>
5414 <p
>Update
2014-
11-
26: Inspired by
5415 <ahref=
"https://www.mirbsd.org/permalinks/wlog-
10-tg_e20141125-tg.htm#e20141125-tg_wlog-
10-tg
">a
5416 blog post by Torsten Glaser
</a
>, added --purge to the preseed
5422 <title>A Debian package for SMTP via Tor (aka SMTorP) using exim4
</title>
5423 <link>https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</link>
5424 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Debian_package_for_SMTP_via_Tor__aka_SMTorP__using_exim4.html
</guid>
5425 <pubDate>Mon,
10 Nov
2014 13:
40:
00 +
0100</pubDate>
5426 <description><p
>The right to communicate with your friends and family in private,
5427 without anyone snooping, is a right every citicen have in a liberal
5428 democracy. But this right is under serious attack these days.
</p
>
5430 <p
>A while back it occurred to me that one way to make the dragnet
5431 surveillance conducted by NSA, GCHQ, FRA and others (and confirmed by
5432 the whisleblower Snowden) more expensive for Internet email,
5433 is to deliver all email using SMTP via Tor. Such SMTP option would be
5434 a nice addition to the FreedomBox project if we could send email
5435 between FreedomBox machines without leaking metadata about the emails
5436 to the people peeking on the wire. I
5437 <a href=
"http://lists.alioth.debian.org/pipermail/freedombox-discuss/
2014-October/
006493.html
">proposed
5438 this on the FreedomBox project mailing list in October
</a
> and got a
5439 lot of useful feedback and suggestions. It also became obvious to me
5440 that this was not a novel idea, as the same idea was tested and
5441 documented by Johannes Berg as early as
2006, and both
5442 <a href=
"https://github.com/pagekite/Mailpile/wiki/SMTorP
">the
5443 Mailpile
</a
> and
<a href=
"http://dee.su/cables
">the Cables
</a
> systems
5444 propose a similar method / protocol to pass emails between users.
</p
>
5446 <p
>To implement such system one need to set up a Tor hidden service
5447 providing the SMTP protocol on port
25, and use email addresses
5448 looking like username@hidden-service-name.onion. With such addresses
5449 the connections to port
25 on hidden-service-name.onion using Tor will
5450 go to the correct SMTP server. To do this, one need to configure the
5451 Tor daemon to provide the hidden service and the mail server to accept
5452 emails for this .onion domain. To learn more about Exim configuration
5453 in Debian and test the design provided by Johannes Berg in his FAQ, I
5454 set out yesterday to create a Debian package for making it trivial to
5455 set up such SMTP over Tor service based on Debian. Getting it to work
5456 were fairly easy, and
5457 <a href=
"https://github.com/petterreinholdtsen/exim4-smtorp
">the
5458 source code for the Debian package
</a
> is available from github. I
5459 plan to move it into Debian if further testing prove this to be a
5460 useful approach.
</p
>
5462 <p
>If you want to test this, set up a blank Debian machine without any
5463 mail system installed (or run
<tt
>apt-get purge exim4-config
</tt
> to
5464 get rid of exim4). Install tor, clone the git repository mentioned
5465 above, build the deb and install it on the machine. Next, run
5466 <tt
>/usr/lib/exim4-smtorp/setup-exim-hidden-service
</tt
> and follow
5467 the instructions to get the service up and running. Restart tor and
5468 exim when it is done, and test mail delivery using swaks like
5471 <p
><blockquote
><pre
>
5472 torsocks swaks --server dutlqrrmjhtfa3vp.onion \
5473 --to fbx@dutlqrrmjhtfa3vp.onion
5474 </pre
></blockquote
></p
>
5476 <p
>This will test the SMTP delivery using tor. Replace the email
5477 address with your own address to test your server. :)
</p
>
5479 <p
>The setup procedure is still to complex, and I hope it can be made
5480 easier and more automatic. Especially the tor setup need more work.
5481 Also, the package include a tor-smtp tool written in C, but its task
5482 should probably be rewritten in some script language to make the deb
5483 architecture independent. It would probably also make the code easier
5484 to review. The tor-smtp tool currently need to listen on a socket for
5485 exim to talk to it and is started using xinetd. It would be better if
5486 no daemon and no socket is needed. I suspect it is possible to get
5487 exim to run a command line tool for delivery instead of talking to a
5488 socket, and hope to figure out how in a future version of this
5491 <p
>Until I wipe my test machine, I can be reached using the
5492 <tt
>fbx@dutlqrrmjhtfa3vp.onion
</tt
> mail address, deliverable over
5493 SMTorP. :)
</p
>
5498 <title>listadmin, the quick way to moderate mailman lists - nice free software
</title>
5499 <link>https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</link>
5500 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/listadmin__the_quick_way_to_moderate_mailman_lists___nice_free_software.html
</guid>
5501 <pubDate>Wed,
22 Oct
2014 20:
00:
00 +
0200</pubDate>
5502 <description><p
>If you ever had to moderate a mailman list, like the ones on
5503 alioth.debian.org, you know the web interface is fairly slow to
5504 operate. First you visit one web page, enter the moderation password
5505 and get a new page shown with a list of all the messages to moderate
5506 and various options for each email address. This take a while for
5507 every list you moderate, and you need to do it regularly to do a good
5508 job as a list moderator. But there is a quick alternative,
5509 <a href=
"http://heim.ifi.uio.no/kjetilho/hacks/#listadmin
">the
5510 listadmin program
</a
>. It allow you to check lists for new messages
5511 to moderate in a fraction of a second. Here is a test run on two
5512 lists I recently took over:
</p
>
5514 <p
><blockquote
><pre
>
5515 % time listadmin xiph
5516 fetching data for pkg-xiph-commits@lists.alioth.debian.org ... nothing in queue
5517 fetching data for pkg-xiph-maint@lists.alioth.debian.org ... nothing in queue
5523 </pre
></blockquote
></p
>
5525 <p
>In
1.7 seconds I had checked two mailing lists and confirmed that
5526 there are no message in the moderation queue. Every morning I
5527 currently moderate
68 mailman lists, and it normally take around two
5528 minutes. When I took over the two pkg-xiph lists above a few days
5529 ago, there were
400 emails waiting in the moderator queue. It took me
5530 less than
15 minutes to process them all using the listadmin
5533 <p
>If you install
5534 <a href=
"https://tracker.debian.org/pkg/listadmin
">the listadmin
5535 package
</a
> from Debian and create a file
<tt
>~/.listadmin.ini
</tt
>
5536 with content like this, the moderation task is a breeze:
</p
>
5538 <p
><blockquote
><pre
>
5539 username username@example.org
5542 discard_if_reason
"Posting restricted to members only. Remove us from your mail list.
"
5545 adminurl https://{domain}/mailman/admindb/{list}
5546 mailman-list@lists.example.com
5549 other-list@otherserver.example.org
5550 </pre
></blockquote
></p
>
5552 <p
>There are other options to set as well. Check the manual page to
5553 learn the details.
</p
>
5555 <p
>If you are forced to moderate lists on a mailman installation where
5556 the SSL certificate is self signed or not properly signed by a
5557 generally accepted signing authority, you can set a environment
5558 variable when calling listadmin to disable SSL verification:
</p
>
5560 <p
><blockquote
><pre
>
5561 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 listadmin
5562 </pre
></blockquote
></p
>
5564 <p
>If you want to moderate a subset of the lists you take care of, you
5565 can provide an argument to the listadmin script like I do in the
5566 initial screen dump (the xiph argument). Using an argument, only
5567 lists matching the argument string will be processed. This make it
5568 quick to accept messages if you notice the moderation request in your
5571 <p
>Without the listadmin program, I would never be the moderator of
68
5572 mailing lists, as I simply do not have time to spend on that if the
5573 process was any slower. The listadmin program have saved me hours of
5574 time I could spend elsewhere over the years. It truly is nice free
5577 <p
>As usual, if you use Bitcoin and want to show your support of my
5578 activities, please send Bitcoin donations to my address
5579 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
5581 <p
>Update
2014-
10-
27: Added missing
'username
' statement in
5582 configuration example. Also, I
've been told that the
5583 PERL_LWP_SSL_VERIFY_HOSTNAME=
0 setting do not work for everyone. Not
5589 <title>Debian Jessie, PXE and automatic firmware installation
</title>
5590 <link>https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</link>
5591 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Jessie__PXE_and_automatic_firmware_installation.html
</guid>
5592 <pubDate>Fri,
17 Oct
2014 14:
10:
00 +
0200</pubDate>
5593 <description><p
>When PXE installing laptops with Debian, I often run into the
5594 problem that the WiFi card require some firmware to work properly.
5595 And it has been a pain to fix this using preseeding in Debian.
5596 Normally something more is needed. But thanks to
5597 <a href=
"https://packages.qa.debian.org/i/isenkram.html
">my isenkram
5598 package
</a
> and its recent tasksel extension, it has now become easy
5599 to do this using simple preseeding.
</p
>
5601 <p
>The isenkram-cli package provide tasksel tasks which will install
5602 firmware for the hardware found in the machine (actually, requested by
5603 the kernel modules for the hardware). (It can also install user space
5604 programs supporting the hardware detected, but that is not the focus
5605 of this story.)
</p
>
5607 <p
>To get this working in the default installation, two preeseding
5608 values are needed. First, the isenkram-cli package must be installed
5609 into the target chroot (aka the hard drive) before tasksel is executed
5610 in the pkgsel step of the debian-installer system. This is done by
5611 preseeding the base-installer/includes debconf value to include the
5612 isenkram-cli package. The package name is next passed to debootstrap
5613 for installation. With the isenkram-cli package in place, tasksel
5614 will automatically use the isenkram tasks to detect hardware specific
5615 packages for the machine being installed and install them, because
5616 isenkram-cli contain tasksel tasks.
</p
>
5618 <p
>Second, one need to enable the non-free APT repository, because
5619 most firmware unfortunately is non-free. This is done by preseeding
5620 the apt-mirror-setup step. This is unfortunate, but for a lot of
5621 hardware it is the only option in Debian.
</p
>
5623 <p
>The end result is two lines needed in your preseeding file to get
5624 firmware installed automatically by the installer:
</p
>
5626 <p
><blockquote
><pre
>
5627 base-installer base-installer/includes string isenkram-cli
5628 apt-mirror-setup apt-setup/non-free boolean true
5629 </pre
></blockquote
></p
>
5631 <p
>The current version of isenkram-cli in testing/jessie will install
5632 both firmware and user space packages when using this method. It also
5633 do not work well, so use version
0.15 or later. Installing both
5634 firmware and user space packages might give you a bit more than you
5635 want, so I decided to split the tasksel task in two, one for firmware
5636 and one for user space programs. The firmware task is enabled by
5637 default, while the one for user space programs is not. This split is
5638 implemented in the package currently in unstable.
</p
>
5640 <p
>If you decide to give this a go, please let me know (via email) how
5641 this recipe work for you. :)
</p
>
5643 <p
>So, I bet you are wondering, how can this work. First and
5644 foremost, it work because tasksel is modular, and driven by whatever
5645 files it find in /usr/lib/tasksel/ and /usr/share/tasksel/. So the
5646 isenkram-cli package place two files for tasksel to find. First there
5647 is the task description file (/usr/share/tasksel/descs/isenkram.desc):
</p
>
5649 <p
><blockquote
><pre
>
5650 Task: isenkram-packages
5652 Description: Hardware specific packages (autodetected by isenkram)
5653 Based on the detected hardware various hardware specific packages are
5655 Test-new-install: show show
5657 Packages: for-current-hardware
5659 Task: isenkram-firmware
5661 Description: Hardware specific firmware packages (autodetected by isenkram)
5662 Based on the detected hardware various hardware specific firmware
5663 packages are proposed.
5664 Test-new-install: mark show
5666 Packages: for-current-hardware-firmware
5667 </pre
></blockquote
></p
>
5669 <p
>The key parts are Test-new-install which indicate how the task
5670 should be handled and the Packages line referencing to a script in
5671 /usr/lib/tasksel/packages/. The scripts use other scripts to get a
5672 list of packages to install. The for-current-hardware-firmware script
5673 look like this to list relevant firmware for the machine:
5675 <p
><blockquote
><pre
>
5678 PATH=/usr/sbin:$PATH
5680 isenkram-autoinstall-firmware -l
5681 </pre
></blockquote
></p
>
5683 <p
>With those two pieces in place, the firmware is installed by
5684 tasksel during the normal d-i run. :)
</p
>
5686 <p
>If you want to test what tasksel will install when isenkram-cli is
5687 installed, run
<tt
>DEBIAN_PRIORITY=critical tasksel --test
5688 --new-install
</tt
> to get the list of packages that tasksel would
5691 <p
><a href=
"https://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> will be
5692 pilots in testing this feature, as isenkram is used there now to
5693 install firmware, replacing the earlier scripts.
</p
>
5698 <title>Ubuntu used to show the bread prizes at ICA Storo
</title>
5699 <link>https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</link>
5700 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Ubuntu_used_to_show_the_bread_prizes_at_ICA_Storo.html
</guid>
5701 <pubDate>Sat,
4 Oct
2014 15:
20:
00 +
0200</pubDate>
5702 <description><p
>Today I came across an unexpected Ubuntu boot screen. Above the
5703 bread shelf on the ICA shop at Storo in Oslo, the grub menu of Ubuntu
5704 with Linux kernel
3.2.0-
23 (ie probably version
12.04 LTS) was stuck
5705 on a screen normally showing the bread types and prizes:
</p
>
5707 <p align=
"center
"><img width=
"70%
" src=
"http://people.skolelinux.org/pere/blog/images/
2014-
10-
04-ubuntu-ica-storo-crop.jpeg
"></p
>
5709 <p
>If it had booted as it was supposed to, I would never had known
5710 about this hidden Linux installation. It is interesting what
5711 <a href=
"http://revealingerrors.com/
">errors can reveal
</a
>.
</p
>
5716 <title>New lsdvd release version
0.17 is ready
</title>
5717 <link>https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</link>
5718 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_lsdvd_release_version_0_17_is_ready.html
</guid>
5719 <pubDate>Sat,
4 Oct
2014 08:
40:
00 +
0200</pubDate>
5720 <description><p
>The
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd project
</a
>
5721 got a new set of developers a few weeks ago, after the original
5722 developer decided to step down and pass the project to fresh blood.
5723 This project is now maintained by Petter Reinholdtsen and Steve
5726 <p
>I just wrapped up
5727 <a href=
"https://sourceforge.net/p/lsdvd/mailman/message/
32896061/
">a
5728 new lsdvd release
</a
>, available in git or from
5729 <a href=
"https://sourceforge.net/projects/lsdvd/files/lsdvd/
">the
5730 download page
</a
>. This is the changelog dated
2014-
10-
03 for version
5735 <li
>Ignore
'phantom
' audio, subtitle tracks
</li
>
5736 <li
>Check for garbage in the program chains, which indicate that a track is
5737 non-existant, to work around additional copy protection
</li
>
5738 <li
>Fix displaying content type for audio tracks, subtitles
</li
>
5739 <li
>Fix pallete display of first entry
</li
>
5740 <li
>Fix include orders
</li
>
5741 <li
>Ignore read errors in titles that would not be displayed anyway
</li
>
5742 <li
>Fix the chapter count
</li
>
5743 <li
>Make sure the array size and the array limit used when initialising
5744 the palette size is the same.
</li
>
5745 <li
>Fix array printing.
</li
>
5746 <li
>Correct subsecond calculations.
</li
>
5747 <li
>Add sector information to the output format.
</li
>
5748 <li
>Clean up code to be closer to ANSI C and compile without warnings
5749 with more GCC compiler warnings.
</li
>
5753 <p
>This change bring together patches for lsdvd in use in various
5754 Linux and Unix distributions, as well as patches submitted to the
5755 project the last nine years. Please check it out. :)
</p
>
5760 <title>How to test Debian Edu Jessie despite some fatal problems with the installer
</title>
5761 <link>https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</link>
5762 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_Debian_Edu_Jessie_despite_some_fatal_problems_with_the_installer.html
</guid>
5763 <pubDate>Fri,
26 Sep
2014 12:
20:
00 +
0200</pubDate>
5764 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
5765 project
</a
> provide a Linux solution for schools, including a
5766 powerful desktop with education software, a central server providing
5767 web pages, user database, user home directories, central login and PXE
5768 boot of both clients without disk and the installation to install Debian
5769 Edu on machines with disk (and a few other services perhaps to small
5770 to mention here). We in the Debian Edu team are currently working on
5771 the Jessie based version, trying to get everything in shape before the
5772 freeze, to avoid having to maintain our own package repository in the
5774 <a href=
"https://wiki.debian.org/DebianEdu/Status/Jessie
">current
5775 status
</a
> can be seen on the Debian wiki, and there is still heaps of
5776 work left. Some fatal problems block testing, breaking the installer,
5777 but it is possible to work around these to get anyway. Here is a
5778 recipe on how to get the installation limping along.
</p
>
5780 <p
>First, download the test ISO via
5781 <a href=
"ftp://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">ftp
</a
>,
5782 <a href=
"http://ftp.skolelinux.no/cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso
">http
</a
>
5784 ftp.skolelinux.org::cd-edu-testing-nolocal-netinst/debian-edu-amd64-i386-NETINST-
1.iso).
5785 The ISO build was broken on Tuesday, so we do not get a new ISO every
5786 12 hours or so, but thankfully the ISO we already got we are able to
5787 install with some tweaking.
</p
>
5789 <p
>When you get to the Debian Edu profile question, go to tty2
5790 (use Alt-Ctrl-F2), run
</p
>
5792 <p
><blockquote
><pre
>
5793 nano /usr/bin/edu-eatmydata-install
5794 </pre
></blockquote
></p
>
5796 <p
>and add
'exit
0' as the second line, disabling the eatmydata
5797 optimization. Return to the installation, select the profile you want
5798 and continue. Without this change, exim4-config will fail to install
5799 due to a known bug in eatmydata.
</p
>
5801 <p
>When you get the grub question at the end, answer /dev/sda (or if
5802 this do not work, figure out what your correct value would be. All my
5803 test machines need /dev/sda, so I have no advice if it do not fit
5804 your need.
</p
>
5806 <p
>If you installed a profile including a graphical desktop, log in as
5807 root after the initial boot from hard drive, and install the
5808 education-desktop-XXX metapackage. XXX can be kde, gnome, lxde, xfce
5809 or mate. If you want several desktop options, install more than one
5810 metapackage. Once this is done, reboot and you should have a working
5811 graphical login screen. This workaround should no longer be needed
5812 once the education-tasks package version
1.801 enter testing in two
5815 <p
>I believe the ISO build will start working on two days when the new
5816 tasksel package enter testing and Steve McIntyre get a chance to
5817 update the debian-cd git repository. The eatmydata, grub and desktop
5818 issues are already fixed in unstable and testing, and should show up
5819 on the ISO as soon as the ISO build start working again. Well the
5820 eatmydata optimization is really just disabled. The proper fix
5821 require an upload by the eatmydata maintainer applying the patch
5822 provided in bug
<a href=
"https://bugs.debian.org/
702711">#
702711</a
>.
5823 The rest have proper fixes in unstable.
</p
>
5825 <p
>I hope this get you going with the installation testing, as we are
5826 quickly running out of time trying to get our Jessie based
5827 installation ready before the distribution freeze in a month.
</p
>
5832 <title>Suddenly I am the new upstream of the lsdvd command line tool
</title>
5833 <link>https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</link>
5834 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Suddenly_I_am_the_new_upstream_of_the_lsdvd_command_line_tool.html
</guid>
5835 <pubDate>Thu,
25 Sep
2014 11:
20:
00 +
0200</pubDate>
5836 <description><p
>I use the
<a href=
"https://sourceforge.net/p/lsdvd/
">lsdvd tool
</a
>
5837 to handle my fairly large DVD collection. It is a nice command line
5838 tool to get details about a DVD, like title, tracks, track length,
5839 etc, in XML, Perl or human readable format. But lsdvd have not seen
5840 any new development since
2006 and had a few irritating bugs affecting
5841 its use with some DVDs. Upstream seemed to be dead, and in January I
5842 sent a small probe asking for a version control repository for the
5843 project, without any reply. But I use it regularly and would like to
5844 get
<a href=
"https://packages.qa.debian.org/lsdvd
">an updated version
5845 into Debian
</a
>. So two weeks ago I tried harder to get in touch with
5846 the project admin, and after getting a reply from him explaining that
5847 he was no longer interested in the project, I asked if I could take
5848 over. And yesterday, I became project admin.
</p
>
5850 <p
>I
've been in touch with a Gentoo developer and the Debian
5851 maintainer interested in joining forces to maintain the upstream
5852 project, and I hope we can get a new release out fairly quickly,
5853 collecting the patches spread around on the internet into on place.
5854 I
've added the relevant Debian patches to the freshly created git
5855 repository, and expect the Gentoo patches to make it too. If you got
5856 a DVD collection and care about command line tools, check out
5857 <a href=
"https://sourceforge.net/p/lsdvd/git/ci/master/tree/
">the git source
</a
> and join
5858 <a href=
"https://sourceforge.net/p/lsdvd/mailman/
">the project mailing
5859 list
</a
>. :)
</p
>
5864 <title>Speeding up the Debian installer using eatmydata and dpkg-divert
</title>
5865 <link>https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</link>
5866 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Speeding_up_the_Debian_installer_using_eatmydata_and_dpkg_divert.html
</guid>
5867 <pubDate>Tue,
16 Sep
2014 14:
00:
00 +
0200</pubDate>
5868 <description><p
>The
<a href=
"https://www.debian.org/
">Debian
</a
> installer could be
5869 a lot quicker. When we install more than
2000 packages in
5870 <a href=
"http://www.skolelinux.org/
">Skolelinux / Debian Edu
</a
> using
5871 tasksel in the installer, unpacking the binary packages take forever.
5872 A part of the slow I/O issue was discussed in
5873 <a href=
"https://bugs.debian.org/
613428">bug #
613428</a
> about too
5874 much file system sync-ing done by dpkg, which is the package
5875 responsible for unpacking the binary packages. Other parts (like code
5876 executed by postinst scripts) might also sync to disk during
5877 installation. All this sync-ing to disk do not really make sense to
5878 me. If the machine crash half-way through, I start over, I do not try
5879 to salvage the half installed system. So the failure sync-ing is
5880 supposed to protect against, hardware or system crash, is not really
5881 relevant while the installer is running.
</p
>
5883 <p
>A few days ago, I thought of a way to get rid of all the file
5884 system sync()-ing in a fairly non-intrusive way, without the need to
5885 change the code in several packages. The idea is not new, but I have
5886 not heard anyone propose the approach using dpkg-divert before. It
5887 depend on the small and clever package
5888 <a href=
"https://packages.qa.debian.org/eatmydata
">eatmydata
</a
>, which
5889 uses LD_PRELOAD to replace the system functions for syncing data to
5890 disk with functions doing nothing, thus allowing programs to live
5891 dangerous while speeding up disk I/O significantly. Instead of
5892 modifying the implementation of dpkg, apt and tasksel (which are the
5893 packages responsible for selecting, fetching and installing packages),
5894 it occurred to me that we could just divert the programs away, replace
5895 them with a simple shell wrapper calling
5896 "eatmydata
&nbsp;$program
&nbsp;$@
", to get the same effect.
5897 Two days ago I decided to test the idea, and wrapped up a simple
5898 implementation for the Debian Edu udeb.
</p
>
5900 <p
>The effect was stunning. In my first test it reduced the running
5901 time of the pkgsel step (installing tasks) from
64 to less than
44
5902 minutes (
20 minutes shaved off the installation) on an old Dell
5903 Latitude D505 machine. I am not quite sure what the optimised time
5904 would have been, as I messed up the testing a bit, causing the debconf
5905 priority to get low enough for two questions to pop up during
5906 installation. As soon as I saw the questions I moved the installation
5907 along, but do not know how long the question were holding up the
5908 installation. I did some more measurements using Debian Edu Jessie,
5909 and got these results. The time measured is the time stamp in
5910 /var/log/syslog between the
"pkgsel: starting tasksel
" and the
5911 "pkgsel: finishing up
" lines, if you want to do the same measurement
5912 yourself. In Debian Edu, the tasksel dialog do not show up, and the
5913 timing thus do not depend on how quickly the user handle the tasksel
5916 <p
><table
>
5919 <th
>Machine/setup
</th
>
5920 <th
>Original tasksel
</th
>
5921 <th
>Optimised tasksel
</th
>
5922 <th
>Reduction
</th
>
5926 <td
>Latitude D505 Main+LTSP LXDE
</td
>
5927 <td
>64 min (
07:
46-
08:
50)
</td
>
5928 <td
><44 min (
11:
27-
12:
11)
</td
>
5929 <td
>>20 min
18%
</td
>
5933 <td
>Latitude D505 Roaming LXDE
</td
>
5934 <td
>57 min (
08:
48-
09:
45)
</td
>
5935 <td
>34 min (
07:
43-
08:
17)
</td
>
5936 <td
>23 min
40%
</td
>
5940 <td
>Latitude D505 Minimal
</td
>
5941 <td
>22 min (
10:
37-
10:
59)
</td
>
5942 <td
>11 min (
11:
16-
11:
27)
</td
>
5943 <td
>11 min
50%
</td
>
5947 <td
>Thinkpad X200 Minimal
</td
>
5948 <td
>6 min (
08:
19-
08:
25)
</td
>
5949 <td
>4 min (
08:
04-
08:
08)
</td
>
5950 <td
>2 min
33%
</td
>
5954 <td
>Thinkpad X200 Roaming KDE
</td
>
5955 <td
>19 min (
09:
21-
09:
40)
</td
>
5956 <td
>15 min (
10:
25-
10:
40)
</td
>
5957 <td
>4 min
21%
</td
>
5960 </table
></p
>
5962 <p
>The test is done using a netinst ISO on a USB stick, so some of the
5963 time is spent downloading packages. The connection to the Internet
5964 was
100Mbit/s during testing, so downloading should not be a
5965 significant factor in the measurement. Download typically took a few
5966 seconds to a few minutes, depending on the amount of packages being
5967 installed.
</p
>
5969 <p
>The speedup is implemented by using two hooks in
5970 <a href=
"https://www.debian.org/devel/debian-installer/
">Debian
5971 Installer
</a
>, the pre-pkgsel.d hook to set up the diverts, and the
5972 finish-install.d hook to remove the divert at the end of the
5973 installation. I picked the pre-pkgsel.d hook instead of the
5974 post-base-installer.d hook because I test using an ISO without the
5975 eatmydata package included, and the post-base-installer.d hook in
5976 Debian Edu can only operate on packages included in the ISO. The
5977 negative effect of this is that I am unable to activate this
5978 optimization for the kernel installation step in d-i. If the code is
5979 moved to the post-base-installer.d hook, the speedup would be larger
5980 for the entire installation.
</p
>
5982 <p
>I
've implemented this in the
5983 <a href=
"https://packages.qa.debian.org/debian-edu-install
">debian-edu-install
</a
>
5984 git repository, and plan to provide the optimization as part of the
5985 Debian Edu installation. If you want to test this yourself, you can
5986 create two files in the installer (or in an udeb). One shell script
5987 need do go into /usr/lib/pre-pkgsel.d/, with content like this:
</p
>
5989 <p
><blockquote
><pre
>
5992 . /usr/share/debconf/confmodule
5994 logger -t my-pkgsel
"info: $*
"
5997 logger -t my-pkgsel
"error: $*
"
5999 override_install() {
6000 apt-install eatmydata || true
6001 if [ -x /target/usr/bin/eatmydata ] ; then
6002 for bin in dpkg apt-get aptitude tasksel ; do
6004 # Test that the file exist and have not been diverted already.
6005 if [ -f /target$file ] ; then
6006 info
"diverting $file using eatmydata
"
6007 printf
"#!/bin/sh\neatmydata $bin.distrib \
"\$@\
"\n
" \
6008 > /target$file.edu
6009 chmod
755 /target$file.edu
6010 in-target dpkg-divert --package debian-edu-config \
6011 --rename --quiet --add $file
6012 ln -sf ./$bin.edu /target$file
6014 error
"unable to divert $file, as it is missing.
"
6018 error
"unable to find /usr/bin/eatmydata after installing the eatmydata pacage
"
6023 </pre
></blockquote
></p
>
6025 <p
>To clean up, another shell script should go into
6026 /usr/lib/finish-install.d/ with code like this:
6028 <p
><blockquote
><pre
>
6030 . /usr/share/debconf/confmodule
6032 logger -t my-finish-install
"error: $@
"
6034 remove_install_override() {
6035 for bin in dpkg apt-get aptitude tasksel ; do
6037 if [ -x /target$file.edu ] ; then
6039 in-target dpkg-divert --package debian-edu-config \
6040 --rename --quiet --remove $file
6043 error
"Missing divert for $file.
"
6046 sync # Flush file buffers before continuing
6049 remove_install_override
6050 </pre
></blockquote
></p
>
6052 <p
>In Debian Edu, I placed both code fragments in a separate script
6053 edu-eatmydata-install and call it from the pre-pkgsel.d and
6054 finish-install.d scripts.
</p
>
6056 <p
>By now you might ask if this change should get into the normal
6057 Debian installer too? I suspect it should, but am not sure the
6058 current debian-installer coordinators find it useful enough. It also
6059 depend on the side effects of the change. I
'm not aware of any, but I
6060 guess we will see if the change is safe after some more testing.
6061 Perhaps there is some package in Debian depending on sync() and
6062 fsync() having effect? Perhaps it should go into its own udeb, to
6063 allow those of us wanting to enable it to do so without affecting
6066 <p
>Update
2014-
09-
24: Since a few days ago, enabling this optimization
6067 will break installation of all programs using gnutls because of
6068 <a href=
"https://bugs.debian.org/
702711">bug #
702711</a
>. An updated
6069 eatmydata package in Debian will solve it.
</p
>
6071 <p
>Update
2014-
10-
17: The bug mentioned above is fixed in testing and
6072 the optimization work again. And I have discovered that the
6073 dpkg-divert trick is not really needed and implemented a slightly
6074 simpler approach as part of the debian-edu-install package. See
6075 tools/edu-eatmydata-install in the source package.
</p
>
6077 <p
>Update
2014-
11-
11: Unfortunately, a new
6078 <a href=
"http://bugs.debian.org/
765738">bug #
765738</a
> in eatmydata only
6079 triggering on i386 made it into testing, and broke this installation
6080 optimization again. If
<a href=
"http://bugs.debian.org/
768893">unblock
6081 request
768893</a
> is accepted, it should be working again.
</p
>
6086 <title>Good bye subkeys.pgp.net, welcome pool.sks-keyservers.net
</title>
6087 <link>https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</link>
6088 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Good_bye_subkeys_pgp_net__welcome_pool_sks_keyservers_net.html
</guid>
6089 <pubDate>Wed,
10 Sep
2014 13:
10:
00 +
0200</pubDate>
6090 <description><p
>Yesterday, I had the pleasure of attending a talk with the
6091 <a href=
"http://www.nuug.no/
">Norwegian Unix User Group
</a
> about
6092 <a href=
"http://www.nuug.no/aktiviteter/
20140909-sks-keyservers/
">the
6093 OpenPGP keyserver pool sks-keyservers.net
</a
>, and was very happy to
6094 learn that there is a large set of publicly available key servers to
6095 use when looking for peoples public key. So far I have used
6096 subkeys.pgp.net, and some times wwwkeys.nl.pgp.net when the former
6097 were misbehaving, but those days are ended. The servers I have used
6098 up until yesterday have been slow and some times unavailable. I hope
6099 those problems are gone now.
</p
>
6101 <p
>Behind the round robin DNS entry of the
6102 <a href=
"https://sks-keyservers.net/
">sks-keyservers.net
</a
> service
6103 there is a pool of more than
100 keyservers which are checked every
6104 day to ensure they are well connected and up to date. It must be
6105 better than what I have used so far. :)
</p
>
6107 <p
>Yesterdays speaker told me that the service is the default
6108 keyserver provided by the default configuration in GnuPG, but this do
6109 not seem to be used in Debian. Perhaps it should?
</p
>
6111 <p
>Anyway, I
've updated my ~/.gnupg/options file to now include this
6114 <p
><blockquote
><pre
>
6115 keyserver pool.sks-keyservers.net
6116 </pre
></blockquote
></p
>
6118 <p
>With GnuPG version
2 one can also locate the keyserver using SRV
6119 entries in DNS. Just for fun, I did just that at work, so now every
6120 user of GnuPG at the University of Oslo should find a OpenGPG
6121 keyserver automatically should their need it:
</p
>
6123 <p
><blockquote
><pre
>
6124 % host -t srv _pgpkey-http._tcp.uio.no
6125 _pgpkey-http._tcp.uio.no has SRV record
0 100 11371 pool.sks-keyservers.net.
6127 </pre
></blockquote
></p
>
6129 <p
>Now if only
6130 <a href=
"http://ietfreport.isoc.org/idref/draft-shaw-openpgp-hkp/
">the
6131 HKP lookup protocol
</a
> supported finding signature paths, I would be
6132 very happy. It can look up a given key or search for a user ID, but I
6133 normally do not want that, but to find a trust path from my key to
6134 another key. Given a user ID or key ID, I would like to find (and
6135 download) the keys representing a signature path from my key to the
6136 key in question, to be able to get a trust path between the two keys.
6137 This is as far as I can tell not possible today. Perhaps something
6138 for a future version of the protocol?
</p
>
6143 <title>From English wiki to translated PDF and epub via Docbook
</title>
6144 <link>https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</link>
6145 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/From_English_wiki_to_translated_PDF_and_epub_via_Docbook.html
</guid>
6146 <pubDate>Tue,
17 Jun
2014 11:
30:
00 +
0200</pubDate>
6147 <description><p
>The
<a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
6148 project
</a
> provide an instruction manual for teachers, system
6149 administrators and other users that contain useful tips for setting up
6150 and maintaining a Debian Edu installation. This text is about how the
6151 text processing of this manual is handled in the project.
</p
>
6153 <p
>One goal of the project is to provide information in the native
6154 language of its users, and for this we need to handle translations.
6155 But we also want to make sure each language contain the same
6156 information, so for this we need a good way to keep the translations
6157 in sync. And we want it to be easy for our users to improve the
6158 documentation, avoiding the need to learn special formats or tools to
6159 contribute, and the obvious way to do this is to make it possible to
6160 edit the documentation using a web browser. We also want it to be
6161 easy for translators to keep the translation up to date, and give them
6162 help in figuring out what need to be translated. Here is the list of
6163 tools and the process we have found trying to reach all these
6166 <p
>We maintain the authoritative source of our manual in the
6167 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">Debian
6168 wiki
</a
>, as several wiki pages written in English. It consist of one
6169 front page with references to the different chapters, several pages
6170 for each chapter, and finally one
"collection page
" gluing all the
6171 chapters together into one large web page (aka
6172 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/AllInOne
">the
6173 AllInOne page
</a
>). The AllInOne page is the one used for further
6174 processing and translations. Thanks to the fact that the
6175 <a href=
"http://moinmo.in/
">MoinMoin
</a
> installation on
6176 wiki.debian.org support exporting pages in
6177 <a href=
"http://www.docbook.org/
">the Docbook format
</a
>, we can fetch
6178 the list of pages to export using the raw version of the AllInOne
6179 page, loop over each of them to generate a Docbook XML version of the
6180 manual. This process also download images and transform image
6181 references to use the locally downloaded images. The generated
6182 Docbook XML files are slightly broken, so some post-processing is done
6183 using the
<tt
>documentation/scripts/get_manual
</tt
> program, and the
6184 result is a nice Docbook XML file (debian-edu-wheezy-manual.xml) and
6185 a handfull of images. The XML file can now be used to generate PDF, HTML
6186 and epub versions of the English manual. This is the basic step of
6187 our process, making PDF (using dblatex), HTML (using xsltproc) and
6188 epub (using dbtoepub) version from Docbook XML, and the resulting files
6189 are placed in the debian-edu-doc-en binary package.
</p
>
6191 <p
>But English documentation is not enough for us. We want translated
6192 documentation too, and we want to make it easy for translators to
6193 track the English original. For this we use the
6194 <a href=
"http://packages.qa.debian.org/p/poxml.html
">poxml
</a
> package,
6195 which allow us to transform the English Docbook XML file into a
6196 translation file (a .pot file), usable with the normal gettext based
6197 translation tools used by those translating free software. The pot
6198 file is used to create and maintain translation files (several .po
6199 files), which the translations update with the native language
6200 translations of all titles, paragraphs and blocks of text in the
6201 original. The next step is combining the original English Docbook XML
6202 and the translation file (say debian-edu-wheezy-manual.nb.po), to
6203 create a translated Docbook XML file (in this case
6204 debian-edu-wheezy-manual.nb.xml). This translated (or partly
6205 translated, if the translation is not complete) Docbook XML file can
6206 then be used like the original to create a PDF, HTML and epub version
6207 of the documentation.
</p
>
6209 <p
>The translators use different tools to edit the .po files. We
6211 <a href=
"http://www.kde.org/applications/development/lokalize/
">lokalize
</a
>,
6212 while some use emacs and vi, others can use web based editors like
6213 <a href=
"http://pootle.translatehouse.org/
">Poodle
</a
> or
6214 <a href=
"https://www.transifex.com/
">Transifex
</a
>. All we care about
6215 is where the .po file end up, in our git repository. Updated
6216 translations can either be committed directly to git, or submitted as
6217 <a href=
"https://bugs.debian.org/src:debian-edu-doc
">bug reports
6218 against the debian-edu-doc package
</a
>.
</p
>
6220 <p
>One challenge is images, which both might need to be translated (if
6221 they show translated user applications), and are needed in different
6222 formats when creating PDF and HTML versions (epub is a HTML version in
6223 this regard). For this we transform the original PNG images to the
6224 needed density and format during build, and have a way to provide
6225 translated images by storing translated versions in
6226 images/$LANGUAGECODE/. I am a bit unsure about the details here. The
6227 package maintainers know more.
</p
>
6229 <p
>If you wonder what the result look like, we provide
6230 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/
">the content
6231 of the documentation packages on the web
</a
>. See for example the
6232 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/it/debian-edu-wheezy-manual.pdf
">Italian
6233 PDF version
</a
> or the
6234 <a href=
"http://maintainer.skolelinux.org/debian-edu-doc/de/debian-edu-wheezy-manual.html
">German
6235 HTML version
</a
>. We do not yet build the epub version by default,
6236 but perhaps it will be done in the future.
</p
>
6238 <p
>To learn more, check out
6239 <a href=
"http://packages.qa.debian.org/d/debian-edu-doc.html
">the
6240 debian-edu-doc package
</a
>,
6241 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/
">the
6242 manual on the wiki
</a
> and
6243 <a href=
"https://wiki.debian.org/DebianEdu/Documentation/Wheezy/Translations
">the
6244 translation instructions
</a
> in the manual.
</p
>
6249 <title>Install hardware dependent packages using tasksel (Isenkram
0.7)
</title>
6250 <link>https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</link>
6251 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Install_hardware_dependent_packages_using_tasksel__Isenkram_0_7_.html
</guid>
6252 <pubDate>Wed,
23 Apr
2014 14:
50:
00 +
0200</pubDate>
6253 <description><p
>It would be nice if it was easier in Debian to get all the hardware
6254 related packages relevant for the computer installed automatically.
6255 So I implemented one, using
6256 <a href=
"http://packages.qa.debian.org/isenkram
">my Isenkram
6257 package
</a
>. To use it, install the tasksel and isenkram packages and
6258 run tasksel as user root. You should be presented with a new option,
6259 "Hardware specific packages (autodetected by isenkram)
". When you
6260 select it, tasksel will install the packages isenkram claim is fit for
6261 the current hardware, hot pluggable or not.
<p
>
6263 <p
>The implementation is in two files, one is the tasksel menu entry
6264 description, and the other is the script used to extract the list of
6265 packages to install. The first part is in
6266 <tt
>/usr/share/tasksel/descs/isenkram.desc
</tt
> and look like
6269 <p
><blockquote
><pre
>
6272 Description: Hardware specific packages (autodetected by isenkram)
6273 Based on the detected hardware various hardware specific packages are
6275 Test-new-install: mark show
6277 Packages: for-current-hardware
6278 </pre
></blockquote
></p
>
6280 <p
>The second part is in
6281 <tt
>/usr/lib/tasksel/packages/for-current-hardware
</tt
> and look like
6284 <p
><blockquote
><pre
>
6289 isenkram-autoinstall-firmware -l
6291 </pre
></blockquote
></p
>
6293 <p
>All in all, a very short and simple implementation making it
6294 trivial to install the hardware dependent package we all may want to
6295 have installed on our machines. I
've not been able to find a way to
6296 get tasksel to tell you exactly which packages it plan to install
6297 before doing the installation. So if you are curious or careful,
6298 check the output from the isenkram-* command line tools first.
</p
>
6300 <p
>The information about which packages are handling which hardware is
6301 fetched either from the isenkram package itself in
6302 /usr/share/isenkram/, from git.debian.org or from the APT package
6303 database (using the Modaliases header). The APT package database
6304 parsing have caused a nasty resource leak in the isenkram daemon (bugs
6305 <a href=
"http://bugs.debian.org/
719837">#
719837</a
> and
6306 <a href=
"http://bugs.debian.org/
730704">#
730704</a
>). The cause is in
6307 the python-apt code (bug
6308 <a href=
"http://bugs.debian.org/
745487">#
745487</a
>), but using a
6309 workaround I was able to get rid of the file descriptor leak and
6310 reduce the memory leak from ~
30 MiB per hardware detection down to
6311 around
2 MiB per hardware detection. It should make the desktop
6312 daemon a lot more useful. The fix is in version
0.7 uploaded to
6313 unstable today.
</p
>
6315 <p
>I believe the current way of mapping hardware to packages in
6316 Isenkram is is a good draft, but in the future I expect isenkram to
6317 use the AppStream data source for this. A proposal for getting proper
6318 AppStream support into Debian is floating around as
6319 <a href=
"https://wiki.debian.org/DEP-
11">DEP-
11</a
>, and
6320 <a href=
"https://wiki.debian.org/SummerOfCode2014/Projects#SummerOfCode2014.2FProjects
.2FAppStreamDEP11Implementation.AppStream
.2FDEP-
11_for_the_Debian_Archive
">GSoC
6321 project
</a
> will take place this summer to improve the situation. I
6322 look forward to seeing the result, and welcome patches for isenkram to
6323 start using the information when it is ready.
</p
>
6325 <p
>If you want your package to map to some specific hardware, either
6326 add a
"Xb-Modaliases
" header to your control file like I did in
6327 <a href=
"http://packages.qa.debian.org/pymissile
">the pymissile
6328 package
</a
> or submit a bug report with the details to the isenkram
6330 <a href=
"http://people.skolelinux.org/pere/blog/tags/isenkram/
">all my
6331 blog posts tagged isenkram
</a
> for details on the notation. I expect
6332 the information will be migrated to AppStream eventually, but for the
6333 moment I got no better place to store it.
</p
>
6338 <title>FreedomBox milestone - all packages now in Debian Sid
</title>
6339 <link>https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</link>
6340 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/FreedomBox_milestone___all_packages_now_in_Debian_Sid.html
</guid>
6341 <pubDate>Tue,
15 Apr
2014 22:
10:
00 +
0200</pubDate>
6342 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
6343 project
</a
> is working on providing the software and hardware to make
6344 it easy for non-technical people to host their data and communication
6345 at home, and being able to communicate with their friends and family
6346 encrypted and away from prying eyes. It is still going strong, and
6347 today a major mile stone was reached.
</p
>
6349 <p
>Today, the last of the packages currently used by the project to
6350 created the system images were accepted into Debian Unstable. It was
6351 the freedombox-setup package, which is used to configure the images
6352 during build and on the first boot. Now all one need to get going is
6353 the build code from the freedom-maker git repository and packages from
6354 Debian. And once the freedombox-setup package enter testing, we can
6355 build everything directly from Debian. :)
</p
>
6357 <p
>Some key packages used by Freedombox are
6358 <a href=
"http://packages.qa.debian.org/freedombox-setup
">freedombox-setup
</a
>,
6359 <a href=
"http://packages.qa.debian.org/plinth
">plinth
</a
>,
6360 <a href=
"http://packages.qa.debian.org/pagekite
">pagekite
</a
>,
6361 <a href=
"http://packages.qa.debian.org/tor
">tor
</a
>,
6362 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>,
6363 <a href=
"http://packages.qa.debian.org/owncloud
">owncloud
</a
> and
6364 <a href=
"http://packages.qa.debian.org/dnsmasq
">dnsmasq
</a
>. There
6365 are plans to integrate more packages into the setup. User
6366 documentation is maintained on the Debian wiki. Please
6367 <a href=
"https://wiki.debian.org/FreedomBox/Manual/Jessie
">check out
6368 the manual
</a
> and help us improve it.
</p
>
6370 <p
>To test for yourself and create boot images with the FreedomBox
6371 setup, run this on a Debian machine using a user with sudo rights to
6372 become root:
</p
>
6374 <p
><pre
>
6375 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6376 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6378 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6380 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6381 </pre
></p
>
6383 <p
>Root access is needed to run debootstrap and mount loopback
6384 devices. See the README in the freedom-maker git repo for more
6385 details on the build. If you do not want all three images, trim the
6386 make line. Note that the virtualbox-image target is not really
6387 virtualbox specific. It create a x86 image usable in kvm, qemu,
6388 vmware and any other x86 virtual machine environment. You might need
6389 the version of vmdebootstrap in Jessie to get the build working, as it
6390 include fixes for a race condition with kpartx.
</p
>
6392 <p
>If you instead want to install using a Debian CD and the preseed
6393 method, boot a Debian Wheezy ISO and use this boot argument to load
6394 the preseed values:
</p
>
6396 <p
><pre
>
6397 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
6398 </pre
></p
>
6400 <p
>I have not tested it myself the last few weeks, so I do not know if
6401 it still work.
</p
>
6403 <p
>If you wonder how to help, one task you could look at is using
6404 systemd as the boot system. It will become the default for Linux in
6405 Jessie, so we need to make sure it is usable on the Freedombox. I did
6406 a simple test a few weeks ago, and noticed dnsmasq failed to start
6407 during boot when using systemd. I suspect there are other problems
6408 too. :) To detect problems, there is a test suite included, which can
6409 be run from the plinth web interface.
</p
>
6411 <p
>Give it a go and let us know how it goes on the mailing list, and help
6412 us get the new release published. :) Please join us on
6413 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
6414 irc.debian.org)
</a
> and
6415 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6416 mailing list
</a
> if you want to help make this vision come true.
</p
>
6421 <title>S3QL, a locally mounted cloud file system - nice free software
</title>
6422 <link>https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</link>
6423 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/S3QL__a_locally_mounted_cloud_file_system___nice_free_software.html
</guid>
6424 <pubDate>Wed,
9 Apr
2014 11:
30:
00 +
0200</pubDate>
6425 <description><p
>For a while now, I have been looking for a sensible offsite backup
6426 solution for use at home. My requirements are simple, it must be
6427 cheap and locally encrypted (in other words, I keep the encryption
6428 keys, the storage provider do not have access to my private files).
6429 One idea me and my friends had many years ago, before the cloud
6430 storage providers showed up, was to use Google mail as storage,
6431 writing a Linux block device storing blocks as emails in the mail
6432 service provided by Google, and thus get heaps of free space. On top
6433 of this one can add encryption, RAID and volume management to have
6434 lots of (fairly slow, I admit that) cheap and encrypted storage. But
6435 I never found time to implement such system. But the last few weeks I
6436 have looked at a system called
6437 <a href=
"https://bitbucket.org/nikratio/s3ql/
">S3QL
</a
>, a locally
6438 mounted network backed file system with the features I need.
</p
>
6440 <p
>S3QL is a fuse file system with a local cache and cloud storage,
6441 handling several different storage providers, any with Amazon S3,
6442 Google Drive or OpenStack API. There are heaps of such storage
6443 providers. S3QL can also use a local directory as storage, which
6444 combined with sshfs allow for file storage on any ssh server. S3QL
6445 include support for encryption, compression, de-duplication, snapshots
6446 and immutable file systems, allowing me to mount the remote storage as
6447 a local mount point, look at and use the files as if they were local,
6448 while the content is stored in the cloud as well. This allow me to
6449 have a backup that should survive fire. The file system can not be
6450 shared between several machines at the same time, as only one can
6451 mount it at the time, but any machine with the encryption key and
6452 access to the storage service can mount it if it is unmounted.
</p
>
6454 <p
>It is simple to use. I
'm using it on Debian Wheezy, where the
6455 package is included already. So to get started, run
<tt
>apt-get
6456 install s3ql
</tt
>. Next, pick a storage provider. I ended up picking
6457 Greenqloud, after reading their nice recipe on
6458 <a href=
"https://greenqloud.zendesk.com/entries/
44611757-How-To-Use-S3QL-to-mount-a-StorageQloud-bucket-on-Debian-Wheezy
">how
6459 to use S3QL with their Amazon S3 service
</a
>, because I trust the laws
6460 in Iceland more than those in USA when it come to keeping my personal
6461 data safe and private, and thus would rather spend money on a company
6462 in Iceland. Another nice recipe is available from the article
6463 <a href=
"http://www.admin-magazine.com/HPC/Articles/HPC-Cloud-Storage
">S3QL
6464 Filesystem for HPC Storage
</a
> by Jeff Layton in the HPC section of
6465 Admin magazine. When the provider is picked, figure out how to get
6466 the API key needed to connect to the storage API. With Greencloud,
6467 the key did not show up until I had added payment details to my
6470 <p
>Armed with the API access details, it is time to create the file
6471 system. First, create a new bucket in the cloud. This bucket is the
6472 file system storage area. I picked a bucket name reflecting the
6473 machine that was going to store data there, but any name will do.
6474 I
'll refer to it as
<tt
>bucket-name
</tt
> below. In addition, one need
6475 the API login and password, and a locally created password. Store it
6476 all in ~root/.s3ql/authinfo2 like this:
6478 <p
><blockquote
><pre
>
6480 storage-url: s3c://s.greenqloud.com:
443/bucket-name
6481 backend-login: API-login
6482 backend-password: API-password
6483 fs-passphrase: local-password
6484 </pre
></blockquote
></p
>
6486 <p
>I create my local passphrase using
<tt
>pwget
50</tt
> or similar,
6487 but any sensible way to create a fairly random password should do it.
6488 Armed with these details, it is now time to run mkfs, entering the API
6489 details and password to create it:
</p
>
6491 <p
><blockquote
><pre
>
6492 # mkdir -m
700 /var/lib/s3ql-cache
6493 # mkfs.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6494 --ssl s3c://s.greenqloud.com:
443/bucket-name
6495 Enter backend login:
6496 Enter backend password:
6497 Before using S3QL, make sure to read the user
's guide, especially
6498 the
'Important Rules to Avoid Loosing Data
' section.
6499 Enter encryption password:
6500 Confirm encryption password:
6501 Generating random encryption key...
6502 Creating metadata tables...
6512 Compressing and uploading metadata...
6513 Wrote
0.00 MB of compressed metadata.
6514 #
</pre
></blockquote
></p
>
6516 <p
>The next step is mounting the file system to make the storage available.
6518 <p
><blockquote
><pre
>
6519 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6520 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
6521 Using
4 upload threads.
6522 Downloading and decompressing metadata...
6532 Mounting filesystem...
6534 Filesystem Size Used Avail Use% Mounted on
6535 s3c://s.greenqloud.com:
443/bucket-name
1.0T
0 1.0T
0% /s3ql
6537 </pre
></blockquote
></p
>
6539 <p
>The file system is now ready for use. I use rsync to store my
6540 backups in it, and as the metadata used by rsync is downloaded at
6541 mount time, no network traffic (and storage cost) is triggered by
6542 running rsync. To unmount, one should not use the normal umount
6543 command, as this will not flush the cache to the cloud storage, but
6544 instead running the umount.s3ql command like this:
6546 <p
><blockquote
><pre
>
6549 </pre
></blockquote
></p
>
6551 <p
>There is a fsck command available to check the file system and
6552 correct any problems detected. This can be used if the local server
6553 crashes while the file system is mounted, to reset the
"already
6554 mounted
" flag. This is what it look like when processing a working
6555 file system:
</p
>
6557 <p
><blockquote
><pre
>
6558 # fsck.s3ql --force --ssl s3c://s.greenqloud.com:
443/bucket-name
6559 Using cached metadata.
6560 File system seems clean, checking anyway.
6561 Checking DB integrity...
6562 Creating temporary extra indices...
6563 Checking lost+found...
6564 Checking cached objects...
6565 Checking names (refcounts)...
6566 Checking contents (names)...
6567 Checking contents (inodes)...
6568 Checking contents (parent inodes)...
6569 Checking objects (reference counts)...
6570 Checking objects (backend)...
6571 ..processed
5000 objects so far..
6572 ..processed
10000 objects so far..
6573 ..processed
15000 objects so far..
6574 Checking objects (sizes)...
6575 Checking blocks (referenced objects)...
6576 Checking blocks (refcounts)...
6577 Checking inode-block mapping (blocks)...
6578 Checking inode-block mapping (inodes)...
6579 Checking inodes (refcounts)...
6580 Checking inodes (sizes)...
6581 Checking extended attributes (names)...
6582 Checking extended attributes (inodes)...
6583 Checking symlinks (inodes)...
6584 Checking directory reachability...
6585 Checking unix conventions...
6586 Checking referential integrity...
6587 Dropping temporary indices...
6588 Backing up old metadata...
6598 Compressing and uploading metadata...
6599 Wrote
0.89 MB of compressed metadata.
6601 </pre
></blockquote
></p
>
6603 <p
>Thanks to the cache, working on files that fit in the cache is very
6604 quick, about the same speed as local file access. Uploading large
6605 amount of data is to me limited by the bandwidth out of and into my
6606 house. Uploading
685 MiB with a
100 MiB cache gave me
305 kiB/s,
6607 which is very close to my upload speed, and downloading the same
6608 Debian installation ISO gave me
610 kiB/s, close to my download speed.
6609 Both were measured using
<tt
>dd
</tt
>. So for me, the bottleneck is my
6610 network, not the file system code. I do not know what a good cache
6611 size would be, but suspect that the cache should e larger than your
6612 working set.
</p
>
6614 <p
>I mentioned that only one machine can mount the file system at the
6615 time. If another machine try, it is told that the file system is
6618 <p
><blockquote
><pre
>
6619 # mount.s3ql --cachedir /var/lib/s3ql-cache --authfile /root/.s3ql/authinfo2 \
6620 --ssl --allow-root s3c://s.greenqloud.com:
443/bucket-name /s3ql
6621 Using
8 upload threads.
6622 Backend reports that fs is still mounted elsewhere, aborting.
6624 </pre
></blockquote
></p
>
6626 <p
>The file content is uploaded when the cache is full, while the
6627 metadata is uploaded once every
24 hour by default. To ensure the
6628 file system content is flushed to the cloud, one can either umount the
6629 file system, or ask S3QL to flush the cache and metadata using
6632 <p
><blockquote
><pre
>
6633 # s3qlctrl upload-meta /s3ql
6634 # s3qlctrl flushcache /s3ql
6636 </pre
></blockquote
></p
>
6638 <p
>If you are curious about how much space your data uses in the
6639 cloud, and how much compression and deduplication cut down on the
6640 storage usage, you can use s3qlstat on the mounted file system to get
6643 <p
><blockquote
><pre
>
6645 Directory entries:
9141
6648 Total data size:
22049.38 MB
6649 After de-duplication:
21955.46 MB (
99.57% of total)
6650 After compression:
21877.28 MB (
99.22% of total,
99.64% of de-duplicated)
6651 Database size:
2.39 MB (uncompressed)
6652 (some values do not take into account not-yet-uploaded dirty blocks in cache)
6654 </pre
></blockquote
></p
>
6656 <p
>I mentioned earlier that there are several possible suppliers of
6657 storage. I did not try to locate them all, but am aware of at least
6658 <a href=
"https://www.greenqloud.com/
">Greenqloud
</a
>,
6659 <a href=
"http://drive.google.com/
">Google Drive
</a
>,
6660 <a href=
"http://aws.amazon.com/s3/
">Amazon S3 web serivces
</a
>,
6661 <a href=
"http://www.rackspace.com/
">Rackspace
</a
> and
6662 <a href=
"http://crowncloud.net/
">Crowncloud
</A
>. The latter even
6663 accept payment in Bitcoin. Pick one that suit your need. Some of
6664 them provide several GiB of free storage, but the prize models are
6665 quite different and you will have to figure out what suits you
6668 <p
>While researching this blog post, I had a look at research papers
6669 and posters discussing the S3QL file system. There are several, which
6670 told me that the file system is getting a critical check by the
6671 science community and increased my confidence in using it. One nice
6673 "<a href=
"http://www.lanl.gov/orgs/adtsc/publications/science_highlights_2013/docs/pg68_69.pdf
">An
6674 Innovative Parallel Cloud Storage System using OpenStack’s SwiftObject
6675 Store and Transformative Parallel I/O Approach
</a
>" by Hsing-Bung
6676 Chen, Benjamin McClelland, David Sherrill, Alfred Torrez, Parks Fields
6677 and Pamela Smith. Please have a look.
</p
>
6679 <p
>Given my problems with different file systems earlier, I decided to
6680 check out the mounted S3QL file system to see if it would be usable as
6681 a home directory (in other word, that it provided POSIX semantics when
6682 it come to locking and umask handling etc). Running
6683 <a href=
"http://people.skolelinux.org/pere/blog/Testing_if_a_file_system_can_be_used_for_home_directories___.html
">my
6684 test code to check file system semantics
</a
>, I was happy to discover that
6685 no error was found. So the file system can be used for home
6686 directories, if one chooses to do so.
</p
>
6688 <p
>If you do not want a locally file system, and want something that
6689 work without the Linux fuse file system, I would like to mention the
6690 <a href=
"http://www.tarsnap.com/
">Tarsnap service
</a
>, which also
6691 provide locally encrypted backup using a command line client. It have
6692 a nicer access control system, where one can split out read and write
6693 access, allowing some systems to write to the backup and others to
6694 only read from it.
</p
>
6696 <p
>As usual, if you use Bitcoin and want to show your support of my
6697 activities, please send Bitcoin donations to my address
6698 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
6703 <title>Freedombox on Dreamplug, Raspberry Pi and virtual x86 machine
</title>
6704 <link>https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</link>
6705 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Freedombox_on_Dreamplug__Raspberry_Pi_and_virtual_x86_machine.html
</guid>
6706 <pubDate>Fri,
14 Mar
2014 11:
00:
00 +
0100</pubDate>
6707 <description><p
>The
<a href=
"https://wiki.debian.org/FreedomBox
">Freedombox
6708 project
</a
> is working on providing the software and hardware for
6709 making it easy for non-technical people to host their data and
6710 communication at home, and being able to communicate with their
6711 friends and family encrypted and away from prying eyes. It has been
6712 going on for a while, and is slowly progressing towards a new test
6713 release (
0.2).
</p
>
6715 <p
>And what day could be better than the Pi day to announce that the
6716 new version will provide
"hard drive
" / SD card / USB stick images for
6717 Dreamplug, Raspberry Pi and VirtualBox (or any other virtualization
6718 system), and can also be installed using a Debian installer preseed
6719 file. The Debian based Freedombox is now based on Debian Jessie,
6720 where most of the needed packages used are already present. Only one,
6721 the freedombox-setup package, is missing. To try to build your own
6722 boot image to test the current status, fetch the freedom-maker scripts
6724 <a href=
"http://packages.qa.debian.org/vmdebootstrap
">vmdebootstrap
</a
>
6725 with a user with sudo access to become root:
6728 git clone http://anonscm.debian.org/git/freedombox/freedom-maker.git \
6730 sudo apt-get install git vmdebootstrap mercurial python-docutils \
6731 mktorrent extlinux virtualbox qemu-user-static binfmt-support \
6733 make -C freedom-maker dreamplug-image raspberry-image virtualbox-image
6736 <p
>Root access is needed to run debootstrap and mount loopback
6737 devices. See the README for more details on the build. If you do not
6738 want all three images, trim the make line. But note that thanks to
<a
6739 href=
"https://bugs.debian.org/
741407">a race condition in
6740 vmdebootstrap
</a
>, the build might fail without the patch to the
6741 kpartx call.
</p
>
6743 <p
>If you instead want to install using a Debian CD and the preseed
6744 method, boot a Debian Wheezy ISO and use this boot argument to load
6745 the preseed values:
</p
>
6748 url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
">http://www.reinholdtsen.name/freedombox/preseed-jessie.dat
</a
>
6751 <p
>But note that due to
<a href=
"https://bugs.debian.org/
740673">a
6752 recently introduced bug in apt in Jessie
</a
>, the installer will
6753 currently hang while setting up APT sources. Killing the
6754 '<tt
>apt-cdrom ident
</tt
>' process when it hang a few times during the
6755 installation will get the installation going. This affect all
6756 installations in Jessie, and I expect it will be fixed soon.
</p
>
6758 <p
>Give it a go and let us know how it goes on the mailing list, and help
6759 us get the new release published. :) Please join us on
6760 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC (#freedombox on
6761 irc.debian.org)
</a
> and
6762 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
6763 mailing list
</a
> if you want to help make this vision come true.
</p
>
6768 <title>New home and release
1.0 for netgroup and innetgr (aka ng-utils)
</title>
6769 <link>https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</link>
6770 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_home_and_release_1_0_for_netgroup_and_innetgr__aka_ng_utils_.html
</guid>
6771 <pubDate>Sat,
22 Feb
2014 21:
45:
00 +
0100</pubDate>
6772 <description><p
>Many years ago, I wrote a GPL licensed version of the netgroup and
6773 innetgr tools, because I needed them in
6774 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>. I called the project
6775 ng-utils, and it has served me well. I placed the project under the
6776 <a href=
"http://www.hungry.com/
">Hungry Programmer
</a
> umbrella, and it was maintained in our CVS
6777 repository. But many years ago, the CVS repository was dropped (lost,
6778 not migrated to new hardware, not sure), and the project have lacked a
6779 proper home since then.
</p
>
6781 <p
>Last summer, I had a look at the package and made a new release
6782 fixing a irritating crash bug, but was unable to store the changes in
6783 a proper source control system. I applied for a project on
6784 <a href=
"https://alioth.debian.org/
">Alioth
</a
>, but did not have time
6785 to follow up on it. Until today. :)
</p
>
6787 <p
>After many hours of cleaning and migration, the ng-utils project
6788 now have a new home, and a git repository with the highlight of the
6789 history of the project. I published all release tarballs and imported
6790 them into the git repository. As the project is really stable and not
6791 expected to gain new features any time soon, I decided to make a new
6792 release and call it
1.0. Visit the new project home on
6793 <a href=
"https://alioth.debian.org/projects/ng-utils/
">https://alioth.debian.org/projects/ng-utils/
</a
>
6794 if you want to check it out. The new version is also uploaded into
6795 <a href=
"http://packages.qa.debian.org/n/ng-utils.html
">Debian Unstable
</a
>.
</p
>
6800 <title>Testing sysvinit from experimental in Debian Hurd
</title>
6801 <link>https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</link>
6802 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Testing_sysvinit_from_experimental_in_Debian_Hurd.html
</guid>
6803 <pubDate>Mon,
3 Feb
2014 13:
40:
00 +
0100</pubDate>
6804 <description><p
>A few days ago I decided to try to help the Hurd people to get
6805 their changes into sysvinit, to allow them to use the normal sysvinit
6806 boot system instead of their old one. This follow up on the
6807 <a href=
"https://teythoon.cryptobitch.de//categories/gsoc.html
">great
6808 Google Summer of Code work
</a
> done last summer by Justus Winter to
6809 get Debian on Hurd working more like Debian on Linux. To get started,
6810 I downloaded a prebuilt hard disk image from
6811 <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
>,
6812 and started it using virt-manager.
</p
>
6814 <p
>The first think I had to do after logging in (root without any
6815 password) was to get the network operational. I followed
6816 <a href=
"https://www.debian.org/ports/hurd/hurd-install
">the
6817 instructions on the Debian GNU/Hurd ports page
</a
> and ran these
6818 commands as root to get the machine to accept a IP address from the
6819 kvm internal DHCP server:
</p
>
6821 <p
><blockquote
><pre
>
6822 settrans -fgap /dev/netdde /hurd/netdde
6823 kill $(ps -ef|awk
'/[p]finet/ { print $
2}
')
6824 kill $(ps -ef|awk
'/[d]evnode/ { print $
2}
')
6826 </pre
></blockquote
></p
>
6828 <p
>After this, the machine had internet connectivity, and I could
6829 upgrade it and install the sysvinit packages from experimental and
6830 enable it as the default boot system in Hurd.
</p
>
6832 <p
>But before I did that, I set a password on the root user, as ssh is
6833 running on the machine it for ssh login to work a password need to be
6834 set. Also, note that a bug somewhere in openssh on Hurd block
6835 compression from working. Remember to turn that off on the client
6838 <p
>Run these commands as root to upgrade and test the new sysvinit
6841 <p
><blockquote
><pre
>
6842 cat
> /etc/apt/sources.list.d/experimental.list
&lt;
&lt;EOF
6843 deb http://http.debian.net/debian/ experimental main
6846 apt-get dist-upgrade
6847 apt-get install -t experimental initscripts sysv-rc sysvinit \
6848 sysvinit-core sysvinit-utils
6849 update-alternatives --config runsystem
6850 </pre
></blockquote
></p
>
6852 <p
>To reboot after switching boot system, you have to use
6853 <tt
>reboot-hurd
</tt
> instead of just
<tt
>reboot
</tt
>, as there is not
6854 yet a sysvinit process able to receive the signals from the normal
6855 'reboot
' command. After switching to sysvinit as the boot system,
6856 upgrading every package and rebooting, the network come up with DHCP
6857 after boot as it should, and the settrans/pkill hack mentioned at the
6858 start is no longer needed. But for some strange reason, there are no
6859 longer any login prompt in the virtual console, so I logged in using
6862 <p
>Note that there are some race conditions in Hurd making the boot
6863 fail some times. No idea what the cause is, but hope the Hurd porters
6864 figure it out. At least Justus said on IRC (#debian-hurd on
6865 irc.debian.org) that they are aware of the problem. A way to reduce
6866 the impact is to upgrade to the Hurd packages built by Justus by
6867 adding this repository to the machine:
</p
>
6869 <p
><blockquote
><pre
>
6870 cat
> /etc/apt/sources.list.d/hurd-ci.list
&lt;
&lt;EOF
6871 deb http://darnassus.sceen.net/~teythoon/hurd-ci/ sid main
6873 </pre
></blockquote
></p
>
6875 <p
>At the moment the prebuilt virtual machine get some packages from
6876 http://ftp.debian-ports.org/debian, because some of the packages in
6877 unstable do not yet include the required patches that are lingering in
6878 BTS. This is the completely list of
"unofficial
" packages installed:
</p
>
6880 <p
><blockquote
><pre
>
6881 # aptitude search
'?narrow(?version(CURRENT),?origin(Debian Ports))
'
6882 i emacs - GNU Emacs editor (metapackage)
6883 i gdb - GNU Debugger
6884 i hurd-recommended - Miscellaneous translators
6885 i isc-dhcp-client - ISC DHCP client
6886 i isc-dhcp-common - common files used by all the isc-dhcp* packages
6887 i libc-bin - Embedded GNU C Library: Binaries
6888 i libc-dev-bin - Embedded GNU C Library: Development binaries
6889 i libc0.3 - Embedded GNU C Library: Shared libraries
6890 i A libc0.3-dbg - Embedded GNU C Library: detached debugging symbols
6891 i libc0.3-dev - Embedded GNU C Library: Development Libraries and Hea
6892 i multiarch-support - Transitional package to ensure multiarch compatibilit
6893 i A x11-common - X Window System (X.Org) infrastructure
6894 i xorg - X.Org X Window System
6895 i A xserver-xorg - X.Org X server
6896 i A xserver-xorg-input-all - X.Org X server -- input driver metapackage
6898 </pre
></blockquote
></p
>
6900 <p
>All in all, testing hurd has been an interesting experience. :)
6901 X.org did not work out of the box and I never took the time to follow
6902 the porters instructions to fix it. This time I was interested in the
6903 command line stuff.
<p
>
6908 <title>New chrpath release
0.16</title>
6909 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</link>
6910 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_16.html
</guid>
6911 <pubDate>Tue,
14 Jan
2014 11:
00:
00 +
0100</pubDate>
6912 <description><p
><a href=
"http://www.coverity.com/
">Coverity
</a
> is a nice tool to
6913 find problems in C, C++ and Java code using static source code
6914 analysis. It can detect a lot of different problems, and is very
6915 useful to find memory and locking bugs in the error handling part of
6916 the source. The company behind it provide
6917 <a href=
"https://scan.coverity.com/
">check of free software projects as
6918 a community service
</a
>, and many hundred free software projects are
6919 already checked. A few days ago I decided to have a closer look at
6920 the Coverity system, and discovered that the
6921 <a href=
"http://www.gnu.org/software/gnash/
">gnash
</a
> and
6922 <a href=
"http://sourceforge.net/projects/ipmitool/
">ipmitool
</a
>
6923 projects I am involved with was already registered. But these are
6924 fairly big, and I would also like to have a small and easy project to
6925 check, and decided to
<a href=
"http://scan.coverity.com/projects/
1179">request
6926 checking of the chrpath project
</a
>. It was
6927 added to the checker and discovered seven potential defects. Six of
6928 these were real, mostly resource
"leak
" when the program detected an
6929 error. Nothing serious, as the resources would be released a fraction
6930 of a second later when the program exited because of the error, but it
6931 is nice to do it right in case the source of the program some time in
6932 the future end up in a library. Having fixed all defects and added
6933 <a href=
"https://lists.alioth.debian.org/mailman/listinfo/chrpath-devel
">a
6934 mailing list for the chrpath developers
</a
>, I decided it was time to
6935 publish a new release. These are the release notes:
</p
>
6937 <p
>New in
0.16 released
2014-
01-
14:
</p
>
6941 <li
>Fixed all minor bugs discovered by Coverity.
</li
>
6942 <li
>Updated config.sub and config.guess from the GNU project.
</li
>
6943 <li
>Mention new project mailing list in the documentation.
</li
>
6948 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
6949 new version
0.16 from alioth
</a
>. Please let us know via the Alioth
6950 project if something is wrong with the new release. The test suite
6951 did not discover any old errors, so if you find a new one, please also
6952 include a test suite check.
</p
>
6957 <title>New chrpath release
0.15</title>
6958 <link>https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</link>
6959 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_chrpath_release_0_15.html
</guid>
6960 <pubDate>Sun,
24 Nov
2013 09:
30:
00 +
0100</pubDate>
6961 <description><p
>After many years break from the package and a vain hope that
6962 development would be continued by someone else, I finally pulled my
6963 acts together this morning and wrapped up a new release of chrpath,
6964 the command line tool to modify the rpath and runpath of already
6965 compiled ELF programs. The update was triggered by the persistence of
6966 Isha Vishnoi at IBM, which needed a new config.guess file to get
6967 support for the ppc64le architecture (powerpc
64-bit Little Endian) he
6968 is working on. I checked the
6969 <a href=
"http://packages.qa.debian.org/chrpath
">Debian
</a
>,
6970 <a href=
"https://launchpad.net/ubuntu/+source/chrpath
">Ubuntu
</a
> and
6971 <a href=
"https://admin.fedoraproject.org/pkgdb/acls/name/chrpath
">Fedora
</a
>
6972 packages for interesting patches (failed to find the source from
6973 OpenSUSE and Mandriva packages), and found quite a few nice fixes.
6974 These are the release notes:
</p
>
6976 <p
>New in
0.15 released
2013-
11-
24:
</p
>
6980 <li
>Updated config.sub and config.guess from the GNU project to work
6981 with newer architectures. Thanks to isha vishnoi for the heads
6984 <li
>Updated README with current URLs.
</li
>
6986 <li
>Added byteswap fix found in Ubuntu, credited Jeremy Kerr and
6987 Matthias Klose.
</li
>
6989 <li
>Added missing help for -k|--keepgoing option, using patch by
6990 Petr Machata found in Fedora.
</li
>
6992 <li
>Rewrite removal of RPATH/RUNPATH to make sure the entry in
6993 .dynamic is a NULL terminated string. Based on patch found in
6994 Fedora credited Axel Thimm and Christian Krause.
</li
>
6999 <a href=
"https://alioth.debian.org/frs/?group_id=
31052">download the
7000 new version
0.15 from alioth
</a
>. Please let us know via the Alioth
7001 project if something is wrong with the new release. The test suite
7002 did not discover any old errors, so if you find a new one, please also
7003 include a testsuite check.
</p
>
7008 <title>Debian init.d boot script example for rsyslog
</title>
7009 <link>https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</link>
7010 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_init_d_boot_script_example_for_rsyslog.html
</guid>
7011 <pubDate>Sat,
2 Nov
2013 22:
40:
00 +
0100</pubDate>
7012 <description><p
>If one of the points of switching to a new init system in Debian is
7013 <a href=
"http://thomas.goirand.fr/blog/?p=
147">to get rid of huge
7014 init.d scripts
</a
>, I doubt we need to switch away from sysvinit and
7015 init.d scripts at all. Here is an example init.d script, ie a rewrite
7016 of /etc/init.d/rsyslog:
</p
>
7018 <p
><pre
>
7019 #!/lib/init/init-d-script
7022 # Required-Start: $remote_fs $time
7023 # Required-Stop: umountnfs $time
7024 # X-Stop-After: sendsigs
7025 # Default-Start:
2 3 4 5
7026 # Default-Stop:
0 1 6
7027 # Short-Description: enhanced syslogd
7028 # Description: Rsyslog is an enhanced multi-threaded syslogd.
7029 # It is quite compatible to stock sysklogd and can be
7030 # used as a drop-in replacement.
7032 DESC=
"enhanced syslogd
"
7033 DAEMON=/usr/sbin/rsyslogd
7034 </pre
></p
>
7036 <p
>Pretty minimalistic to me... For the record, the original sysv-rc
7037 script was
137 lines, and the above is just
15 lines, most of it meta
7038 info/comments.
</p
>
7040 <p
>How to do this, you ask? Well, one create a new script
7041 /lib/init/init-d-script looking something like this:
7043 <p
><pre
>
7046 # Define LSB log_* functions.
7047 # Depend on lsb-base (
>=
3.2-
14) to ensure that this file is present
7048 # and status_of_proc is working.
7049 . /lib/lsb/init-functions
7052 # Function that starts the daemon/service
7058 #
0 if daemon has been started
7059 #
1 if daemon was already running
7060 #
2 if daemon could not be started
7061 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test
> /dev/null \
7063 start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \
7066 # Add code here, if necessary, that waits for the process to be ready
7067 # to handle requests from services started subsequently which depend
7068 # on this one. As a last resort, sleep for some time.
7072 # Function that stops the daemon/service
7077 #
0 if daemon has been stopped
7078 #
1 if daemon was already stopped
7079 #
2 if daemon could not be stopped
7080 # other if a failure occurred
7081 start-stop-daemon --stop --quiet --retry=TERM/
30/KILL/
5 --pidfile $PIDFILE --name $NAME
7082 RETVAL=
"$?
"
7083 [
"$RETVAL
" =
2 ]
&& return
2
7084 # Wait for children to finish too if this is a daemon that forks
7085 # and if the daemon is only ever run from this initscript.
7086 # If the above conditions are not satisfied then add some other code
7087 # that waits for the process to drop all resources that could be
7088 # needed by services started subsequently. A last resort is to
7089 # sleep for some time.
7090 start-stop-daemon --stop --quiet --oknodo --retry=
0/
30/KILL/
5 --exec $DAEMON
7091 [
"$?
" =
2 ]
&& return
2
7092 # Many daemons don
't delete their pidfiles when they exit.
7094 return
"$RETVAL
"
7098 # Function that sends a SIGHUP to the daemon/service
7102 # If the daemon can reload its configuration without
7103 # restarting (for example, when it is sent a SIGHUP),
7104 # then implement that here.
7106 start-stop-daemon --stop --signal
1 --quiet --pidfile $PIDFILE --name $NAME
7111 scriptbasename=
"$(basename $
1)
"
7112 echo
"SN: $scriptbasename
"
7113 if [
"$scriptbasename
" !=
"init-d-library
" ] ; then
7114 script=
"$
1"
7121 NAME=$(basename $DAEMON)
7122 PIDFILE=/var/run/$NAME.pid
7124 # Exit if the package is not installed
7125 #[ -x
"$DAEMON
" ] || exit
0
7127 # Read configuration variable file if it is present
7128 [ -r /etc/default/$NAME ]
&& . /etc/default/$NAME
7130 # Load the VERBOSE setting and other rcS variables
7133 case
"$
1" in
7135 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Starting $DESC
" "$NAME
"
7137 case
"$?
" in
7138 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
7139 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
7143 [
"$VERBOSE
" != no ]
&& log_daemon_msg
"Stopping $DESC
" "$NAME
"
7145 case
"$?
" in
7146 0|
1) [
"$VERBOSE
" != no ]
&& log_end_msg
0 ;;
7147 2) [
"$VERBOSE
" != no ]
&& log_end_msg
1 ;;
7151 status_of_proc
"$DAEMON
" "$NAME
" && exit
0 || exit $?
7153 #reload|force-reload)
7155 # If do_reload() is not implemented then leave this commented out
7156 # and leave
'force-reload
' as an alias for
'restart
'.
7158 #log_daemon_msg
"Reloading $DESC
" "$NAME
"
7162 restart|force-reload)
7164 # If the
"reload
" option is implemented then remove the
7165 #
'force-reload
' alias
7167 log_daemon_msg
"Restarting $DESC
" "$NAME
"
7169 case
"$?
" in
7172 case
"$?
" in
7174 1) log_end_msg
1 ;; # Old process is still running
7175 *) log_end_msg
1 ;; # Failed to start
7185 echo
"Usage: $SCRIPTNAME {start|stop|status|restart|force-reload}
" >&2
7191 </pre
></p
>
7193 <p
>It is based on /etc/init.d/skeleton, and could be improved quite a
7194 lot. I did not really polish the approach, so it might not always
7195 work out of the box, but you get the idea. I did not try very hard to
7196 optimize it nor make it more robust either.
</p
>
7198 <p
>A better argument for switching init system in Debian than reducing
7199 the size of init scripts (which is a good thing to do anyway), is to
7200 get boot system that is able to handle the kernel events sensibly and
7201 robustly, and do not depend on the boot to run sequentially. The boot
7202 and the kernel have not behaved sequentially in years.
</p
>
7207 <title>Browser plugin for SPICE (spice-xpi) uploaded to Debian
</title>
7208 <link>https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</link>
7209 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Browser_plugin_for_SPICE__spice_xpi__uploaded_to_Debian.html
</guid>
7210 <pubDate>Fri,
1 Nov
2013 11:
00:
00 +
0100</pubDate>
7211 <description><p
><a href=
"http://www.spice-space.org/
">The SPICE protocol
</a
> for
7212 remote display access is the preferred solution with oVirt and RedHat
7213 Enterprise Virtualization, and I was sad to discover the other day
7214 that the browser plugin needed to use these systems seamlessly was
7215 missing in Debian. The
<a href=
"http://bugs.debian.org/
668284">request
7216 for a package
</a
> was from
2012-
04-
10 with no progress since
7217 2013-
04-
01, so I decided to wrap up a package based on the great work
7218 from Cajus Pollmeier and put it in a collab-maint maintained git
7219 repository to get a package I could use. I would very much like
7220 others to help me maintain the package (or just take over, I do not
7221 mind), but as no-one had volunteered so far, I just uploaded it to
7222 NEW. I hope it will be available in Debian in a few days.
</p
>
7224 <p
>The source is now available from
7225 <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
>
7230 <title>Teaching vmdebootstrap to create Raspberry Pi SD card images
</title>
7231 <link>https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</link>
7232 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Teaching_vmdebootstrap_to_create_Raspberry_Pi_SD_card_images.html
</guid>
7233 <pubDate>Sun,
27 Oct
2013 17:
00:
00 +
0100</pubDate>
7234 <description><p
>The
7235 <a href=
"http://packages.qa.debian.org/v/vmdebootstrap.html
">vmdebootstrap
</a
>
7236 program is a a very nice system to create virtual machine images. It
7237 create a image file, add a partition table, mount it and run
7238 debootstrap in the mounted directory to create a Debian system on a
7239 stick. Yesterday, I decided to try to teach it how to make images for
7240 <a href=
"https://wiki.debian.org/RaspberryPi
">Raspberry Pi
</a
>, as part
7241 of a plan to simplify the build system for
7242 <a href=
"https://wiki.debian.org/FreedomBox
">the FreedomBox
7243 project
</a
>. The FreedomBox project already uses vmdebootstrap for
7244 the virtualbox images, but its current build system made multistrap
7245 based system for Dreamplug images, and it is lacking support for
7246 Raspberry Pi.
</p
>
7248 <p
>Armed with the knowledge on how to build
"foreign
" (aka non-native
7249 architecture) chroots for Raspberry Pi, I dived into the vmdebootstrap
7250 code and adjusted it to be able to build armel images on my amd64
7251 Debian laptop. I ended up giving vmdebootstrap five new options,
7252 allowing me to replicate the image creation process I use to make
7253 <a href=
"http://people.skolelinux.org/pere/blog/A_Raspberry_Pi_based_batman_adv_Mesh_network_node.html
">Debian
7254 Jessie based mesh node images for the Raspberry Pi
</a
>. First, the
7255 <tt
>--foreign /path/to/binfm_handler
</tt
> option tell vmdebootstrap to
7256 call debootstrap with --foreign and to copy the handler into the
7257 generated chroot before running the second stage. This allow
7258 vmdebootstrap to create armel images on an amd64 host. Next I added
7259 two new options
<tt
>--bootsize size
</tt
> and
<tt
>--boottype
7260 fstype
</tt
> to teach it to create a separate /boot/ partition with the
7261 given file system type, allowing me to create an image with a vfat
7262 partition for the /boot/ stuff. I also added a
<tt
>--variant
7263 variant
</tt
> option to allow me to create smaller images without the
7264 Debian base system packages installed. Finally, I added an option
7265 <tt
>--no-extlinux
</tt
> to tell vmdebootstrap to not install extlinux
7266 as a boot loader. It is not needed on the Raspberry Pi and probably
7267 most other non-x86 architectures. The changes were accepted by the
7268 upstream author of vmdebootstrap yesterday and today, and is now
7270 <a href=
"http://git.liw.fi/cgi-bin/cgit/cgit.cgi/vmdebootstrap/
">the
7271 upstream project page
</a
>.
</p
>
7273 <p
>To use it to build a Raspberry Pi image using Debian Jessie, first
7274 create a small script (the customize script) to add the non-free
7275 binary blob needed to boot the Raspberry Pi and the APT source
7278 <p
><pre
>
7280 set -e # Exit on first error
7281 rootdir=
"$
1"
7282 cd
"$rootdir
"
7283 cat
&lt;
&lt;EOF
> etc/apt/sources.list
7284 deb http://http.debian.net/debian/ jessie main contrib non-free
7286 # Install non-free binary blob needed to boot Raspberry Pi. This
7287 # install a kernel somewhere too.
7288 wget https://raw.github.com/Hexxeh/rpi-update/master/rpi-update \
7289 -O $rootdir/usr/bin/rpi-update
7290 chmod a+x $rootdir/usr/bin/rpi-update
7291 mkdir -p $rootdir/lib/modules
7292 touch $rootdir/boot/start.elf
7293 chroot $rootdir rpi-update
7294 </pre
></p
>
7296 <p
>Next, fetch the latest vmdebootstrap script and call it like this
7297 to build the image:
</p
>
7300 sudo ./vmdebootstrap \
7303 --distribution jessie \
7304 --mirror http://http.debian.net/debian \
7313 --root-password raspberry \
7314 --hostname raspberrypi \
7315 --foreign /usr/bin/qemu-arm-static \
7316 --customize `pwd`/customize \
7318 --package git-core \
7319 --package binutils \
7320 --package ca-certificates \
7323 </pre
></p
>
7325 <p
>The list of packages being installed are the ones needed by
7326 rpi-update to make the image bootable on the Raspberry Pi, with the
7327 exception of netbase, which is needed by debootstrap to find
7328 /etc/hosts with the minbase variant. I really wish there was a way to
7329 set up an Raspberry Pi using only packages in the Debian archive, but
7330 that is not possible as far as I know, because it boots from the GPU
7331 using a non-free binary blob.
</p
>
7333 <p
>The build host need debootstrap, kpartx and qemu-user-static and
7334 probably a few others installed. I have not checked the complete
7335 build dependency list.
</p
>
7337 <p
>The resulting image will not use the hardware floating point unit
7338 on the Raspberry PI, because the armel architecture in Debian is not
7339 optimized for that use. So the images created will be a bit slower
7340 than
<a href=
"http://www.raspbian.org/
">Raspbian
</a
> based images.
</p
>
7345 <title>Good causes: Debian Outreach Program for Women, EFF documenting the spying and Open access in Norway
</title>
7346 <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>
7347 <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>
7348 <pubDate>Tue,
15 Oct
2013 21:
30:
00 +
0200</pubDate>
7349 <description><p
>The last few days I came across a few good causes that should get
7350 wider attention. I recommend signing and donating to each one of
7353 <p
>Via
<a href=
"http://www.debian.org/News/weekly/
2013/
18/
">Debian
7354 Project News for
2013-
10-
14</a
> I came across the Outreach Program for
7355 Women program which is a Google Summer of Code like initiative to get
7356 more women involved in free software. One debian sponsor has offered
7357 to match
<a href=
"http://debian.ch/opw2013
">any donation done to Debian
7358 earmarked
</a
> for this initiative. I donated a few minutes ago, and
7359 hope you will to. :)
</p
>
7361 <p
>And the Electronic Frontier Foundation just announced plans to
7362 create
<a href=
"https://supporters.eff.org/donate/nsa-videos
">video
7363 documentaries about the excessive spying
</a
> on every Internet user that
7364 take place these days, and their need to fund the work. I
've already
7365 donated. Are you next?
</p
>
7367 <p
>For my Norwegian audience, the organisation Studentenes og
7368 Akademikernes Internasjonale Hjelpefond is collecting signatures for a
7369 statement under the heading
7370 <a href=
"http://saih.no/Bloggers_United/
">Bloggers United for Open
7371 Access
</a
> for those of us asking for more focus on open access in the
7372 Norwegian government. So far
499 signatures. I hope you will sign it
7378 <title>Videos about the Freedombox project - for inspiration and learning
</title>
7379 <link>https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</link>
7380 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Videos_about_the_Freedombox_project___for_inspiration_and_learning.html
</guid>
7381 <pubDate>Fri,
27 Sep
2013 14:
10:
00 +
0200</pubDate>
7382 <description><p
>The
<a href=
"http://www.freedomboxfoundation.org/
">Freedombox
7383 project
</a
> have been going on for a while, and have presented the
7384 vision, ideas and solution several places. Here is a little
7385 collection of videos of talks and presentation of the project.
</p
>
7389 <li
><a href=
"http://www.youtube.com/watch?v=ukvUz5taxvA
">FreedomBox -
7390 2,
5 minute marketing film
</a
> (Youtube)
</li
>
7392 <li
><a href=
"http://www.youtube.com/watch?v=SzW25QTVWsE
">Eben Moglen
7393 discusses the Freedombox on CBS news
2011</a
> (Youtube)
</li
>
7395 <li
><a href=
"http://www.youtube.com/watch?v=Ae8SZbxfE0g
">Eben Moglen -
7396 Freedom in the Cloud - Software Freedom, Privacy and and Security for
7397 Web
2.0 and Cloud computing at ISOC-NY Public Meeting
2010</a
>
7398 (Youtube)
</li
>
7400 <li
><a href=
"http://www.youtube.com/watch?v=vNaIji_3xBE
">Fosdem
2011
7401 Keynote by Eben Moglen presenting the Freedombox
</a
> (Youtube)
</li
>
7403 <li
><a href=
"http://www.youtube.com/watch?v=
9bDDUyJSQ9s
">Presentation of
7404 the Freedombox by James Vasile at Elevate in Gratz
2011</a
> (Youtube)
</li
>
7406 <li
><a href=
"http://www.youtube.com/watch?v=zQTmnk27g9s
"> Freedombox -
7407 Discovery, Identity, and Trust by Nick Daly at Freedombox Hackfest New
7408 York City in
2012</a
> (Youtube)
</li
>
7410 <li
><a href=
"http://www.youtube.com/watch?v=tkbSB4Ba7Ck
">Introduction
7411 to the Freedombox at Freedombox Hackfest New York City in
2012</a
>
7412 (Youtube)
</li
>
7414 <li
><a href=
"http://www.youtube.com/watch?v=z-P2Jaeg0aQ
">Freedom, Out
7415 of the Box! by Bdale Garbee at linux.conf.au Ballarat,
2012</a
> (Youtube)
</li
>
7417 <li
><a href=
"https://archive.fosdem.org/
2013/schedule/event/freedombox/
">Freedombox
7418 1.0 by Eben Moglen and Bdale Garbee at Fosdem
2013</a
> (FOSDEM)
</li
>
7420 <li
><a href=
"http://www.youtube.com/watch?v=e1LpYX2zVYg
">What is the
7421 FreedomBox today by Bdale Garbee at Debconf13 in Vaumarcus
7422 2013</a
> (Youtube)
</li
>
7426 <p
>A larger list is available from
7427 <a href=
"https://wiki.debian.org/FreedomBox/TalksAndPresentations
">the
7428 Freedombox Wiki
</a
>.
</p
>
7430 <p
>On other news, I am happy to report that Freedombox based on Debian
7431 Jessie is coming along quite well, and soon both Owncloud and using
7432 Tor should be available for testers of the Freedombox solution. :) In
7433 a few weeks I hope everything needed to test it is included in Debian.
7434 The withsqlite package is already in Debian, and the plinth package is
7435 pending in NEW. The third and vital part of that puzzle is the
7436 metapackage/setup framework, which is still pending an upload. Join
7437 us on
<a href=
"irc://irc.debian.org:
6667/%
23freedombox
">IRC
7438 (#freedombox on irc.debian.org)
</a
> and
7439 <a href=
"http://lists.alioth.debian.org/mailman/listinfo/freedombox-discuss
">the
7440 mailing list
</a
> if you want to help make this vision come true.
</p
>
7445 <title>Recipe to test the Freedombox project on amd64 or Raspberry Pi
</title>
7446 <link>https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</link>
7447 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Recipe_to_test_the_Freedombox_project_on_amd64_or_Raspberry_Pi.html
</guid>
7448 <pubDate>Tue,
10 Sep
2013 14:
20:
00 +
0200</pubDate>
7449 <description><p
>I was introduced to the
7450 <a href=
"http://www.freedomboxfoundation.org/
">Freedombox project
</a
>
7451 in
2010, when Eben Moglen presented his vision about serving the need
7452 of non-technical people to keep their personal information private and
7453 within the legal protection of their own homes. The idea is to give
7454 people back the power over their network and machines, and return
7455 Internet back to its intended peer-to-peer architecture. Instead of
7456 depending on a central service, the Freedombox will give everyone
7457 control over their own basic infrastructure.
</p
>
7459 <p
>I
've intended to join the effort since then, but other tasks have
7460 taken priority. But this summers nasty news about the misuse of trust
7461 and privilege exercised by the
"western
" intelligence gathering
7462 communities increased my eagerness to contribute to a point where I
7463 actually started working on the project a while back.
</p
>
7465 <p
>The
<a href=
"https://alioth.debian.org/projects/freedombox/
">initial
7466 Debian initiative
</a
> based on the vision from Eben Moglen, is to
7467 create a simple and cheap Debian based appliance that anyone can hook
7468 up in their home and get access to secure and private services and
7469 communication. The initial deployment platform have been the
7470 <a href=
"http://www.globalscaletechnologies.com/t-dreamplugdetails.aspx
">Dreamplug
</a
>,
7471 which is a piece of hardware I do not own. So to be able to test what
7472 the current Freedombox setup look like, I had to come up with a way to install
7473 it on some hardware I do have access to. I have rewritten the
7474 <a href=
"https://github.com/NickDaly/freedom-maker
">freedom-maker
</a
>
7475 image build framework to use .deb packages instead of only copying
7476 setup into the boot images, and thanks to this rewrite I am able to
7477 set up any machine supported by Debian Wheezy as a Freedombox, using
7478 the previously mentioned deb (and a few support debs for packages
7479 missing in Debian).
</p
>
7481 <p
>The current Freedombox setup consist of a set of bootstrapping
7483 (
<a href=
"https://github.com/petterreinholdtsen/freedombox-setup
">freedombox-setup
</a
>),
7484 and a administrative web interface
7485 (
<a href=
"https://github.com/NickDaly/Plinth
">plinth
</a
> + exmachina +
7486 withsqlite), as well as a privacy enhancing proxy based on
7487 <a href=
"http://packages.qa.debian.org/privoxy
">privoxy
</a
>
7488 (freedombox-privoxy). There is also a web/javascript based XMPP
7489 client (
<a href=
"http://packages.qa.debian.org/jwchat
">jwchat
</a
>)
7490 trying (unsuccessfully so far) to talk to the XMPP server
7491 (
<a href=
"http://packages.qa.debian.org/ejabberd
">ejabberd
</a
>). The
7492 web interface is pluggable, and the goal is to use it to enable OpenID
7493 services, mesh network connectivity, use of TOR, etc, etc. Not much of
7494 this is really working yet, see
7495 <a href=
"https://github.com/NickDaly/freedombox-todos/blob/master/TODO
">the
7496 project TODO
</a
> for links to GIT repositories. Most of the code is
7497 on github at the moment. The HTTP proxy is operational out of the
7498 box, and the admin web interface can be used to add/remove plinth
7499 users. I
've not been able to do anything else with it so far, but
7500 know there are several branches spread around github and other places
7501 with lots of half baked features.
</p
>
7503 <p
>Anyway, if you want to have a look at the current state, the
7504 following recipes should work to give you a test machine to poke
7507 <p
><strong
>Debian Wheezy amd64
</strong
></p
>
7511 <li
>Fetch normal Debian Wheezy installation ISO.
</li
>
7512 <li
>Boot from it, either as CD or USB stick.
</li
>
7513 <li
><p
>Press [tab] on the boot prompt and add this as a boot argument
7514 to the Debian installer:
<p
>
7515 <pre
>url=
<a href=
"http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
">http://www.reinholdtsen.name/freedombox/preseed-wheezy.dat
</a
></pre
></li
>
7517 <li
>Answer the few language/region/password questions and pick disk to
7518 install on.
</li
>
7520 <li
>When the installation is finished and the machine have rebooted a
7521 few times, your Freedombox is ready for testing.
</li
>
7525 <p
><strong
>Raspberry Pi Raspbian
</strong
></p
>
7529 <li
>Fetch a Raspbian SD card image, create SD card.
</li
>
7530 <li
>Boot from SD card, extend file system to fill the card completely.
</li
>
7531 <li
><p
>Log in and add this to /etc/sources.list:
</p
>
7533 deb
<a href=
"http://www.reinholdtsen.name/freedombox/
">http://www.reinholdtsen.name/freedombox
</a
> wheezy main
7534 </pre
></li
>
7535 <li
><p
>Run this as root:
</p
>
7537 wget -O - http://www.reinholdtsen.name/freedombox/BE1A583D.asc | \
7540 apt-get install freedombox-setup
7541 /usr/lib/freedombox/setup
7542 </pre
></li
>
7543 <li
>Reboot into your freshly created Freedombox.
</li
>
7547 <p
>You can test it on other architectures too, but because the
7548 freedombox-privoxy package is binary, it will only work as intended on
7549 the architectures where I have had time to build the binary and put it
7550 in my APT repository. But do not let this stop you. It is only a
7551 short
"<tt
>apt-get source -b freedombox-privoxy
</tt
>" away. :)
</p
>
7553 <p
>Note that by default Freedombox is a DHCP server on the
7554 192.168.1.0/
24 subnet, so if this is your subnet be careful and turn
7555 off the DHCP server by running
"<tt
>update-rc.d isc-dhcp-server
7556 disable
</tt
>" as root.
</p
>
7558 <p
>Please let me know if this works for you, or if you have any
7559 problems. We gather on the IRC channel
7560 <a href=
"irc://irc.debian.org:
6667/%
23freedombox
">#freedombox
</a
> on
7561 irc.debian.org and the
7562 <a href=
"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/freedombox-discuss
">project
7563 mailing list
</a
>.
</p
>
7565 <p
>Once you get your freedombox operational, you can visit
7566 <tt
>http://your-host-name:
8001/
</tt
> to see the state of the plint
7567 welcome screen (dead end - do not be surprised if you are unable to
7568 get past it), and next visit
<tt
>http://your-host-name:
8001/help/
</tt
>
7569 to look at the rest of plinth. The default user is
'admin
' and the
7570 default password is
'secret
'.
</p
>
7575 <title>Intel
180 SSD disk with Lenovo firmware can not use Intel firmware
</title>
7576 <link>https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</link>
7577 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Intel_180_SSD_disk_with_Lenovo_firmware_can_not_use_Intel_firmware.html
</guid>
7578 <pubDate>Sun,
18 Aug
2013 14:
00:
00 +
0200</pubDate>
7579 <description><p
>Earlier, I reported about
7580 <a href=
"http://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
">my
7581 problems using an Intel SSD
520 Series
180 GB disk
</a
>. Friday I was
7582 told by IBM that the original disk should be thrown away. And as
7583 there no longer was a problem if I bricked the firmware, I decided
7584 today to try to install Intel firmware to replace the Lenovo firmware
7585 currently on the disk.
</p
>
7587 <p
>I searched the Intel site for firmware, and found
7588 <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
>
7589 (aka Intel SATA Solid-State Drive Firmware Update Tool) which
7590 according to the site should contain the latest firmware for SSD
7591 disks. I inserted the broken disk in one of my spare laptops and
7592 booted the ISO from a USB stick. The disk was recognized, but the
7593 program claimed the newest firmware already were installed and refused
7594 to insert any Intel firmware. So no change, and the disk is still
7595 unable to handle write load. :( I guess the only way to get them
7596 working would be if Lenovo releases new firmware. No idea how likely
7597 that is. Anyway, just blogging about this test for completeness. I
7598 got a working Samsung disk, and see no point in spending more time on
7599 the broken disks.
</p
>
7604 <title>How to fix a Thinkpad X230 with a broken
180 GB SSD disk
</title>
7605 <link>https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</link>
7606 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_fix_a_Thinkpad_X230_with_a_broken_180_GB_SSD_disk.html
</guid>
7607 <pubDate>Wed,
17 Jul
2013 23:
50:
00 +
0200</pubDate>
7608 <description><p
>Today I switched to
7609 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">my
7610 new laptop
</a
>. I
've previously written about the problems I had with
7611 my new Thinkpad X230, which was delivered with an
7612 <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
7613 GB Intel SSD disk with Lenovo firmware
</a
> that did not handle
7614 sustained writes. My hardware supplier have been very forthcoming in
7615 trying to find a solution, and after first trying with another
7616 identical
180 GB disks they decided to send me a
256 GB Samsung SSD
7617 disk instead to fix it once and for all. The Samsung disk survived
7618 the installation of Debian with encrypted disks (filling the disk with
7619 random data during installation killed the first two), and I thus
7620 decided to trust it with my data. I have installed it as a Debian Edu
7621 Wheezy roaming workstation hooked up with my Debian Edu Squeeze main
7622 server at home using Kerberos and LDAP, and will use it as my work
7623 station from now on.
</p
>
7625 <p
>As this is a solid state disk with no moving parts, I believe the
7626 Debian Wheezy default installation need to be tuned a bit to increase
7627 performance and increase life time of the disk. The Linux kernel and
7628 user space applications do not yet adjust automatically to such
7629 environment. To make it easier for my self, I created a draft Debian
7630 package
<tt
>ssd-setup
</tt
> to handle this tuning. The
7631 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/ssd-setup.git
">source
7632 for the ssd-setup package
</a
> is available from collab-maint, and it
7633 is set up to adjust the setup of the machine by just installing the
7634 package. If there is any non-SSD disk in the machine, the package
7635 will refuse to install, as I did not try to write any logic to sort
7636 file systems in SSD and non-SSD file systems.
</p
>
7638 <p
>I consider the package a draft, as I am a bit unsure how to best
7639 set up Debian Wheezy with an SSD. It is adjusted to my use case,
7640 where I set up the machine with one large encrypted partition (in
7641 addition to /boot), put LVM on top of this and set up partitions on
7642 top of this again. See the README file in the package source for the
7643 references I used to pick the settings. At the moment these
7644 parameters are tuned:
</p
>
7648 <li
>Set up cryptsetup to pass TRIM commands to the physical disk
7649 (adding discard to /etc/crypttab)
</li
>
7651 <li
>Set up LVM to pass on TRIM commands to the underlying device (in
7652 this case a cryptsetup partition) by changing issue_discards from
7653 0 to
1 in /etc/lvm/lvm.conf.
</li
>
7655 <li
>Set relatime as a file system option for ext3 and ext4 file
7658 <li
>Tell swap to use TRIM commands by adding
'discard
' to
7659 /etc/fstab.
</li
>
7661 <li
>Change I/O scheduler from cfq to deadline using a udev rule.
</li
>
7663 <li
>Run fstrim on every ext3 and ext4 file system every night (from
7664 cron.daily).
</li
>
7666 <li
>Adjust sysctl values vm.swappiness to
1 and vm.vfs_cache_pressure
7667 to
50 to reduce the kernel eagerness to swap out processes.
</li
>
7671 <p
>During installation, I cancelled the part where the installer fill
7672 the disk with random data, as this would kill the SSD performance for
7673 little gain. My goal with the encrypted file system is to ensure
7674 those stealing my laptop end up with a brick and not a working
7675 computer. I have no hope in keeping the really resourceful people
7676 from getting the data on the disk (see
7677 <a href=
"http://xkcd.com/
538/
">XKCD #
538</a
> for an explanation why).
7678 Thus I concluded that adding the discard option to crypttab is the
7679 right thing to do.
</p
>
7681 <p
>I considered using the noop I/O scheduler, as several recommended
7682 it for SSD, but others recommended deadline and a benchmark I found
7683 indicated that deadline might be better for interactive use.
</p
>
7685 <p
>I also considered using the
'discard
' file system option for ext3
7686 and ext4, but read that it would give a performance hit ever time a
7687 file is removed, and thought it best to that that slowdown once a day
7688 instead of during my work.
</p
>
7690 <p
>My package do not set up tmpfs on /var/run, /var/lock and /tmp, as
7691 this is already done by Debian Edu.
</p
>
7693 <p
>I have not yet started on the user space tuning. I expect
7694 iceweasel need some tuning, and perhaps other applications too, but
7695 have not yet had time to investigate those parts.
</p
>
7697 <p
>The package should work on Ubuntu too, but I have not yet tested it
7700 <p
>As for the answer to the question in the title of this blog post,
7701 as far as I know, the only solution I know about is to replace the
7702 disk. It might be possible to flash it with Intel firmware instead of
7703 the Lenovo firmware. But I have not tried and did not want to do so
7704 without approval from Lenovo as I wanted to keep the warranty on the
7705 disk until a solution was found and they wanted the broken disks
7711 <title>Intel SSD
520 Series
180 GB with Lenovo firmware still lock up from sustained writes
</title>
7712 <link>https://people.skolelinux.org/pere/blog/Intel_SSD_520_Series_180_GB_with_Lenovo_firmware_still_lock_up_from_sustained_writes.html
</link>
7713 <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>
7714 <pubDate>Wed,
10 Jul
2013 13:
30:
00 +
0200</pubDate>
7715 <description><p
>A few days ago, I wrote about
7716 <a href=
"http://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
">the
7717 problems I experienced with my new X230 and its SSD disk
</a
>, which
7718 was dying during installation because it is unable to cope with
7719 sustained write. My supplier is in contact with
7720 <a href=
"http://www.lenovo.com/
">Lenovo
</a
>, and they wanted to send a
7721 replacement disk to try to fix the problem. They decided to send an
7722 identical model, so my hopes for a permanent fix was slim.
</p
>
7724 <p
>Anyway, today I got the replacement disk and tried to install
7725 Debian Edu Wheezy with encrypted disk on it. The new disk have the
7726 same firmware version as the original. This time my hope raised
7727 slightly as the installation progressed, as the original disk used to
7728 die after
4-
7% of the disk was written to, while this time it kept
7729 going past
10%,
20%,
40% and even past
50%. But around
60%, the disk
7730 died again and I was back on square one. I still do not have a new
7731 laptop with a disk I can trust. I can not live with a disk that might
7732 lock up when I download a new
7733 <a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> ISO or
7734 other large files. I look forward to hearing from my supplier with
7735 the next proposal from Lenovo.
</p
>
7737 <p
>The original disk is marked Intel SSD
520 Series
180 GB,
7738 11S0C38722Z1ZNME35X1TR, ISN: CVCV321407HB180EGN, SA: G57560302, FW:
7739 LF1i,
29MAY2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
7740 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40002756C4, Model:
7741 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
7742 P/N
45N8295, P0C38732.
</p
>
7744 <p
>The replacement disk is marked Intel SSD
520 Series
180 GB,
7745 11S0C38722Z1ZNDE34N0L0, ISN: CVCV315306RK180EGN, SA: G57560-
302, FW:
7746 LF1i,
22APR2013, PBA: G39779-
300, LBA
351,
651,
888, LI P/N:
0C38722,
7747 Pb-free
2LI, LC P/N:
16-
200366, WWN:
55CD2E40000AB69E, Model:
7748 SSDSC2BW180A3L
2.5" 6Gb/s SATA SSD
180G
5V
1A, ASM P/N
0C38732, FRU
7749 P/N
45N8295, P0C38732.
</p
>
7751 <p
>The only difference is in the first number (serial number?), ISN,
7752 SA, date and WNPP values. Mentioning all the details here in case
7753 someone is able to use the information to find a way to identify the
7754 failing disk among working ones (if any such working disk actually
7760 <title>July
13th: Debian/Ubuntu BSP and Skolelinux/Debian Edu developer gathering in Oslo
</title>
7761 <link>https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</link>
7762 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/July_13th__Debian_Ubuntu_BSP_and_Skolelinux_Debian_Edu_developer_gathering_in_Oslo.html
</guid>
7763 <pubDate>Tue,
9 Jul
2013 10:
40:
00 +
0200</pubDate>
7764 <description><p
>The upcoming Saturday,
2013-
07-
13, we are organising a combined
7765 Debian Edu developer gathering and Debian and Ubuntu bug squashing
7766 party in Oslo. It is organised by
<a href=
"http://www.nuug.no/
">the
7767 member assosiation NUUG
</a
> and
7768 <a href=
"http://www.skolelinux.org/
">the Debian Edu / Skolelinux
7769 project
</a
> together with
<a href=
"http://bitraf.no/
">the hack space
7770 Bitraf
</a
>.
</p
>
7772 <p
>It starts
10:
00 and continue until late evening. Everyone is
7773 welcome, and there is no fee to participate. There is on the other
7774 hand limited space, and only room for
30 people. Please put your name
7775 on
<a href=
"http://wiki.debian.org/BSP/
2013/
07/
13/no/Oslo
">the event
7776 wiki page
</a
> if you plan to join us.
</p
>
7781 <title>The Thinkpad is dead, long live the Thinkpad X230?
</title>
7782 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</link>
7783 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230_.html
</guid>
7784 <pubDate>Fri,
5 Jul
2013 08:
30:
00 +
0200</pubDate>
7785 <description><p
>Half a year ago, I reported that I had to find a
7786 <a href=
"http://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
">replacement
7787 for my trusty old Thinkpad X41
</a
>. Unfortunately I did not have much
7788 time to spend on it, and it took a while to find a model I believe
7789 will do the job, but two days ago the replacement finally arrived. I
7791 <a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad X230
</a
>
7792 with SSD disk (NZDAJMN). I first test installed Debian Edu Wheezy as
7793 a roaming workstation, and it seemed to work flawlessly. But my
7794 second installation with encrypted disk was not as successful. More
7795 on that below.
</p
>
7797 <p
>I had a hard time trying to track down a good laptop, as my most
7798 important requirements (robust and with a good keyboard) are never
7799 listed in the feature list. But I did get good help from the search
7800 feature at
<a href=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
7801 allowed me to limit the list of interesting laptops based on my other
7802 requirements. A bit surprising that SSD disk are not disks according
7803 to that search interface, so I had to drop specifying the number of
7804 disks from my search parameters. I also asked around among friends to
7805 get their impression on keyboards and robustness.
</p
>
7807 <p
>So the new laptop arrived, and it is quite a lot wider than the
7808 X41. I am not quite convinced about the keyboard, as it is
7809 significantly wider than my old keyboard, and I have to stretch my
7810 hand a lot more to reach the edges. But the key response is fairly
7811 good and the individual key shape is fairly easy to handle, so I hope
7812 I will get used to it. My old X40 was starting to fail, and I really
7813 needed a new laptop now. :)
</p
>
7815 <p
>Turning off the touch pad was simple. All it took was a quick
7816 visit to the BIOS during boot it disable it.
</p
>
7818 <p
>But there is a fatal problem with the laptop. The
180 GB SSD disk
7819 lock up during load. And this happen when installing Debian Wheezy
7820 with encrypted disk, while the disk is being filled with random data.
7821 I also tested to install Ubuntu Raring, and it happen there too if I
7822 reenable the code to fill the disk with random data (it is disabled by
7823 default in Ubuntu). And the bug with is already known. It was
7824 reported to Debian as
<a href=
"http://bugs.debian.org/
691427">BTS
7825 report #
691427 2012-
10-
25</a
> (journal commit I/O error on brand-new
7826 Thinkpad T430s ext4 on lvm on SSD). It is also reported to the Linux
7827 kernel developers as
7828 <a href=
"https://bugzilla.kernel.org/show_bug.cgi?id=
51861">Kernel bugzilla
7829 report #
51861 2012-
12-
20</a
> (Intel SSD
520 stops working under load
7830 (SSDSC2BW180A3L in Lenovo ThinkPad T430s)). It is also reported on the
7831 Lenovo forums, both for
7832 <a href=
"http://forums.lenovo.com/t5/T400-T500-and-newer-T-series/T430s-Intel-SSD-
520-
180GB-issue/m-p/
1070549">T430
7833 2012-
11-
10</a
> and for
7834 <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
7835 03-
20-
2013</a
>. The problem do not only affect installation. The
7836 reports state that the disk lock up during use if many writes are done
7837 on the disk, so it is much no use to work around the installation
7838 problem and end up with a computer that can lock up at any moment.
7840 <a href=
"https://git.efficios.com/?p=test-ssd.git
">small C program
7841 available
</a
> that will lock up the hard drive after running a few
7842 minutes by writing to a file.
</p
>
7844 <p
>I
've contacted my supplier and asked how to handle this, and after
7845 contacting PCHELP Norway (request
01D1FDP) which handle support
7846 requests for Lenovo, his first suggestion was to upgrade the disk
7847 firmware. Unfortunately there is no newer firmware available from
7848 Lenovo, as my disk already have the most recent one (version LF1i). I
7849 hope to hear more from him today and hope the problem can be
7855 <title>The Thinkpad is dead, long live the Thinkpad X230
</title>
7856 <link>https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</link>
7857 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_Thinkpad_is_dead__long_live_the_Thinkpad_X230.html
</guid>
7858 <pubDate>Thu,
4 Jul
2013 09:
20:
00 +
0200</pubDate>
7859 <description><p
>Half a year ago, I reported that I had to find a replacement for my
7860 trusty old Thinkpad X41. Unfortunately I did not have much time to
7861 spend on it, but today the replacement finally arrived. I ended up
7862 picking a
<a href=
"http://www.linlap.com/lenovo_thinkpad_x230
">Thinkpad
7863 X230
</a
> with SSD disk (NZDAJMN). I first test installed Debian Edu
7864 Wheezy as a roaming workstation, and it worked flawlessly. As I write
7865 this, it is installing what I hope will be a more final installation,
7866 with a encrypted hard drive to ensure any dope head stealing it end up
7867 with an expencive door stop.
</p
>
7869 <p
>I had a hard time trying to track down a good laptop, as my most
7870 important requirements (robust and with a good keyboard) are never
7871 listed in the feature list. But I did get good help from the search
7872 feature at
<ahref=
"http://www.prisjakt.no/
">Prisjakt
</a
>, which
7873 allowed me to limit the list of interesting laptops based on my other
7874 requirements. A bit surprising that SSD disk are not disks, so I had
7875 to drop number of disks from my search parameters.
</p
>
7877 <p
>I am not quite convinced about the keyboard, as it is significantly
7878 wider than my old keyboard, and I have to stretch my hand a lot more
7879 to reach the edges. But the key response is fairly good and the
7880 individual key shape is fairly easy to handle, so I hope I will get
7881 used to it. My old X40 was starting to fail, and I really needed a
7882 new laptop now. :)
</p
>
7884 <p
>I look forward to figuring out how to turn off the touch pad.
</p
>
7889 <title>Automatically locate and install required firmware packages on Debian (Isenkram
0.4)
</title>
7890 <link>https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</link>
7891 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_locate_and_install_required_firmware_packages_on_Debian__Isenkram_0_4_.html
</guid>
7892 <pubDate>Tue,
25 Jun
2013 11:
50:
00 +
0200</pubDate>
7893 <description><p
>It annoys me when the computer fail to do automatically what it is
7894 perfectly capable of, and I have to do it manually to get things
7895 working. One such task is to find out what firmware packages are
7896 needed to get the hardware on my computer working. Most often this
7897 affect the wifi card, but some times it even affect the RAID
7898 controller or the ethernet card. Today I pushed version
0.4 of the
7899 <a href=
"http://packages.qa.debian.org/isenkram
">Isenkram package
</a
>
7900 including a new script isenkram-autoinstall-firmware handling the
7901 process of asking all the loaded kernel modules what firmware files
7902 they want, find debian packages providing these files and install the
7903 debian packages. Here is a test run on my laptop:
</p
>
7905 <p
><pre
>
7906 # isenkram-autoinstall-firmware
7907 info: kernel drivers requested extra firmware: ipw2200-bss.fw ipw2200-ibss.fw ipw2200-sniffer.fw
7908 info: fetching http://http.debian.net/debian/dists/squeeze/Contents-i386.gz
7909 info: locating packages with the requested firmware files
7910 info: Updating APT sources after adding non-free APT source
7911 info: trying to install firmware-ipw2x00
7914 Preconfiguring packages ...
7915 Selecting previously deselected package firmware-ipw2x00.
7916 (Reading database ...
259727 files and directories currently installed.)
7917 Unpacking firmware-ipw2x00 (from .../firmware-ipw2x00_0.28+squeeze1_all.deb) ...
7918 Setting up firmware-ipw2x00 (
0.28+squeeze1) ...
7920 </pre
></p
>
7922 <p
>When all the requested firmware is present, a simple message is
7923 printed instead:
</p
>
7925 <p
><pre
>
7926 # isenkram-autoinstall-firmware
7927 info: did not find any firmware files requested by loaded kernel modules. exiting
7929 </pre
></p
>
7931 <p
>It could use some polish, but it is already working well and saving
7932 me some time when setting up new machines. :)
</p
>
7934 <p
>So, how does it work? It look at the set of currently loaded
7935 kernel modules, and look up each one of them using modinfo, to find
7936 the firmware files listed in the module meta-information. Next, it
7937 download the Contents file from a nearby APT mirror, and search for
7938 the firmware files in this file to locate the package with the
7939 requested firmware file. If the package is in the non-free section, a
7940 non-free APT source is added and the package is installed using
7941 <tt
>apt-get install
</tt
>. The end result is a slightly better working
7944 <p
>I hope someone find time to implement a more polished version of
7945 this script as part of the hw-detect debian-installer module, to
7946 finally fix
<a href=
"http://bugs.debian.org/
655507">BTS report
7947 #
655507</a
>. There really is no need to insert USB sticks with
7948 firmware during a PXE install when the packages already are available
7949 from the nearby Debian mirror.
</p
>
7954 <title>Fixing the Linux black screen of death on machines with Intel HD video
</title>
7955 <link>https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</link>
7956 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Fixing_the_Linux_black_screen_of_death_on_machines_with_Intel_HD_video.html
</guid>
7957 <pubDate>Tue,
11 Jun
2013 11:
00:
00 +
0200</pubDate>
7958 <description><p
>When installing RedHat, Fedora, Debian and Ubuntu on some machines,
7959 the screen just turn black when Linux boot, either during installation
7960 or on first boot from the hard disk. I
've seen it once in a while the
7961 last few years, but only recently understood the cause. I
've seen it
7962 on HP laptops, and on my latest acquaintance the Packard Bell laptop.
7963 The reason seem to be in the wiring of some laptops. The system to
7964 control the screen background light is inverted, so when Linux try to
7965 turn the brightness fully on, it end up turning it off instead. I do
7966 not know which Linux drivers are affected, but this post is about the
7967 i915 driver used by the
7968 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
7969 EasyNote LV
</a
>, Thinkpad X40 and many other laptops.
</p
>
7971 <p
>The problem can be worked around two ways. Either by adding
7972 i915.invert_brightness=
1 as a kernel option, or by adding a file in
7973 /etc/modprobe.d/ to tell modprobe to add the invert_brightness=
1
7974 option when it load the i915 kernel module. On Debian and Ubuntu, it
7975 can be done by running these commands as root:
</p
>
7978 echo options i915 invert_brightness=
1 | tee /etc/modprobe.d/i915.conf
7979 update-initramfs -u -k all
7982 <p
>Since March
2012 there is
7983 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955
">a
7984 mechanism in the Linux kernel
</a
> to tell the i915 driver which
7985 hardware have this problem, and get the driver to invert the
7986 brightness setting automatically. To use it, one need to add a row in
7987 <a href=
"http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/i915/intel_display.c
">the
7988 intel_quirks array
</a
> in the driver source
7989 <tt
>drivers/gpu/drm/i915/intel_display.c
</tt
> (look for
"<tt
>static
7990 struct intel_quirk intel_quirks
</tt
>"), specifying the PCI device
7991 number (vendor number
8086 is assumed) and subdevice vendor and device
7994 <p
>My Packard Bell EasyNote LV got this output from
<tt
>lspci
7995 -vvnn
</tt
> for the video card in question:
</p
>
7997 <p
><pre
>
7998 00:
02.0 VGA compatible controller [
0300]: Intel Corporation \
7999 3rd Gen Core processor Graphics Controller [
8086:
0156] \
8000 (rev
09) (prog-if
00 [VGA controller])
8001 Subsystem: Acer Incorporated [ALI] Device [
1025:
0688]
8002 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- \
8003 ParErr- Stepping- SE RR- FastB2B- DisINTx+
8004 Status: Cap+
66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast
>TAbort- \
8005 <TAbort-
<MAbort-
>SERR-
<PERR- INTx-
8007 Interrupt: pin A routed to IRQ
42
8008 Region
0: Memory at c2000000 (
64-bit, non-prefetchable) [size=
4M]
8009 Region
2: Memory at b0000000 (
64-bit, prefetchable) [size=
256M]
8010 Region
4: I/O ports at
4000 [size=
64]
8011 Expansion ROM at
<unassigned
> [disabled]
8012 Capabilities:
<access denied
>
8013 Kernel driver in use: i915
8014 </pre
></p
>
8016 <p
>The resulting intel_quirks entry would then look like this:
</p
>
8018 <p
><pre
>
8019 struct intel_quirk intel_quirks[] = {
8021 /* Packard Bell EasyNote LV11HC needs invert brightness quirk */
8022 {
0x0156,
0x1025,
0x0688, quirk_invert_brightness },
8025 </pre
></p
>
8027 <p
>According to the kernel module instructions (as seen using
8028 <tt
>modinfo i915
</tt
>), information about hardware needing the
8029 invert_brightness flag should be sent to the
8030 <a href=
"http://lists.freedesktop.org/mailman/listinfo/dri-devel
">dri-devel
8031 (at) lists.freedesktop.org
</a
> mailing list to reach the kernel
8032 developers. But my email about the laptop sent
2013-
06-
03 have not
8034 <a href=
"http://lists.freedesktop.org/archives/dri-devel/
2013-June/thread.html
">the
8035 web archive for the mailing list
</a
>, so I suspect they do not accept
8036 emails from non-subscribers. Because of this, I sent my patch also to
8037 the Debian bug tracking system instead as
8038 <a href=
"http://bugs.debian.org/
710938">BTS report #
710938</a
>, to make
8039 sure the patch is not lost.
</p
>
8041 <p
>Unfortunately, it is not enough to fix the kernel to get Laptops
8042 with this problem working properly with Linux. If you use Gnome, your
8043 worries should be over at this point. But if you use KDE, there is
8044 something in KDE ignoring the invert_brightness setting and turning on
8045 the screen during login. I
've reported it to Debian as
8046 <a href=
"http://bugs.debian.org/
711237">BTS report #
711237</a
>, and
8047 have no idea yet how to figure out exactly what subsystem is doing
8048 this. Perhaps you can help? Perhaps you know what the Gnome
8049 developers did to handle this, and this can give a clue to the KDE
8050 developers? Or you know where in KDE the screen brightness is changed
8051 during login? If so, please update the BTS report (or get in touch if
8052 you do not know how to update BTS).
</p
>
8054 <p
>Update
2013-
07-
19: The correct fix for this machine seem to be
8055 acpi_backlight=vendor, to disable ACPI backlight support completely,
8056 as the ACPI information on the machine is trash and it is better to
8057 leave it to the intel video driver to control the screen
8058 backlight.
</p
>
8063 <title>How to install Linux on a Packard Bell Easynote LV preinstalled with Windows
8</title>
8064 <link>https://people.skolelinux.org/pere/blog/How_to_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8.html
</link>
8065 <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>
8066 <pubDate>Mon,
27 May
2013 15:
20:
00 +
0200</pubDate>
8067 <description><p
>Two days ago, I asked
8068 <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
8069 I could install Linux on a Packard Bell EasyNote LV computer
8070 preinstalled with Windows
8</a
>. I found a solution, but am horrified
8071 with the obstacles put in the way of Linux users on a laptop with UEFI
8072 and Windows
8.
</p
>
8074 <p
>I never found out if the cause of my problems were the use of UEFI
8075 secure booting or fast boot. I suspect fast boot was the problem,
8076 causing the firmware to boot directly from HD without considering any
8077 key presses and alternative devices, but do not know UEFI settings
8078 enough to tell.
</p
>
8080 <p
>There is no way to install Linux on the machine in question without
8081 opening the box and disconnecting the hard drive! This is as far as I
8082 can tell, the only way to get access to the firmware setup menu
8083 without accepting the Windows
8 license agreement. I am told (and
8084 found description on how to) that it is possible to configure the
8085 firmware setup once booted into Windows
8. But as I believe the terms
8086 of that agreement are completely unacceptable, accepting the license
8087 was never an alternative. I do not enter agreements I do not intend
8088 to follow.
</p
>
8090 <p
>I feared I had to return the laptops and ask for a refund, and
8091 waste many hours on this, but luckily there was a way to get it to
8092 work. But I would not recommend it to anyone planning to run Linux on
8093 it, and I have become sceptical to Windows
8 certified laptops. Is
8094 this the way Linux will be forced out of the market place, by making
8095 it close to impossible for
"normal
" users to install Linux without
8096 accepting the Microsoft Windows license terms? Or at least not
8097 without risking to loose the warranty?
</p
>
8099 <p
>I
've updated the
8100 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Linux Laptop
8101 wiki page for Packard Bell EasyNote LV
</a
>, to ensure the next person
8102 do not have to struggle as much as I did to get Linux into the
8105 <p
>Thanks to Bob Rosbag, Florian Weimer, Philipp Kern, Ben Hutching,
8106 Michael Tokarev and others for feedback and ideas.
</p
>
8111 <title>How can I install Linux on a Packard Bell Easynote LV preinstalled with Windows
8?
</title>
8112 <link>https://people.skolelinux.org/pere/blog/How_can_I_install_Linux_on_a_Packard_Bell_Easynote_LV_preinstalled_with_Windows_8_.html
</link>
8113 <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>
8114 <pubDate>Sat,
25 May
2013 18:
20:
00 +
0200</pubDate>
8115 <description><p
>I
've run into quite a problem the last few days. I bought three
8116 new laptops for my parents and a few others. I bought Packard Bell
8117 Easynote LV to run Kubuntu on and use as their home computer. But I
8118 am completely unable to figure out how to install Linux on it. The
8119 computer is preinstalled with Windows
8, and I suspect it uses UEFI
8120 instead of a BIOS to boot.
</p
>
8122 <p
>The problem is that I am unable to get it to PXE boot, and unable
8123 to get it to boot the Linux installer from my USB stick. I have yet
8124 to try the DVD install, and still hope it will work. when I turn on
8125 the computer, there is no information on what buttons to press to get
8126 the normal boot menu. I expect to get some boot menu to select PXE or
8127 USB stick booting. When booting, it first ask for the language to
8128 use, then for some regional settings, and finally if I will accept the
8129 Windows
8 terms of use. As these terms are completely unacceptable to
8130 me, I have no other choice but to turn off the computer and try again
8131 to get it to boot the Linux installer.
</p
>
8133 <p
>I have gathered my findings so far on a Linlap page about the
8134 <a href=
"http://www.linlap.com/packard_bell_easynote_lv
">Packard Bell
8135 EasyNote LV
</a
> model. If you have any idea how to get Linux
8136 installed on this machine, please get in touch or update that wiki
8137 page. If I can
't find a way to install Linux, I will have to return
8138 the laptop to the seller and find another machine for my parents.
</p
>
8140 <p
>I wonder, is this the way Linux will be forced out of the market
8141 using UEFI and
"secure boot
" by making it impossible to install Linux
8142 on new Laptops?
</p
>
8147 <title>How to transform a Debian based system to a Debian Edu installation
</title>
8148 <link>https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</link>
8149 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_transform_a_Debian_based_system_to_a_Debian_Edu_installation.html
</guid>
8150 <pubDate>Fri,
17 May
2013 11:
50:
00 +
0200</pubDate>
8151 <description><p
><a href=
"http://www.skolelinux.org/
">Debian Edu / Skolelinux
</a
> is
8152 an operating system based on Debian intended for use in schools. It
8153 contain a turn-key solution for the computer network provided to
8154 pupils in the primary schools. It provide both the central server,
8155 network boot servers and desktop environments with heaps of
8156 educational software. The project was founded almost
12 years ago,
8157 2001-
07-
02. If you want to support the project, which is in need for
8158 cash to fund developer gatherings and other project related activity,
8159 <a href=
"http://www.linuxiskolen.no/slxdebianlabs/donations.html
">please
8160 donate some money
</a
>.
8162 <p
>A topic that come up again and again on the Debian Edu mailing
8163 lists and elsewhere, is the question on how to transform a Debian or
8164 Ubuntu installation into a Debian Edu installation. It isn
't very
8165 hard, and last week I wrote a script to replicate the steps done by
8166 the Debian Edu installer.
</p
>
8168 <p
>The script,
8169 <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/
>
8170 in the debian-edu-config package, will go through these six steps and
8171 transform an existing Debian Wheezy or Ubuntu (untested) installation
8172 into a Debian Edu Workstation:
</p
>
8176 <li
>Add skolelinux related APT sources.
</li
>
8177 <li
>Create /etc/debian-edu/config with the wanted configuration.
</li
>
8178 <li
>Install debian-edu-install to load preseeding values and pull in
8179 our configuration.
</li
>
8180 <li
>Preseed debconf database with profile setup in
8181 /etc/debian-edu/config, and run tasksel to install packages
8182 according to the profile specified in the config above,
8183 overriding some of the Debian automation machinery.
</li
>
8184 <li
>Run debian-edu-cfengine-D installation to configure everything
8185 that could not be done using preseeding.
</li
>
8186 <li
>Ask for a reboot to enable all the configuration changes.
</li
>
8190 <p
>There are some steps in the Debian Edu installation that can not be
8191 replicated like this. Disk partitioning and LVM setup, for example.
8192 So this script just assume there is enough disk space to install all
8193 the needed packages.
</p
>
8195 <p
>The script was created to help a Debian Edu student working on
8196 setting up
<a href=
"http://www.raspberrypi.org
">Raspberry Pi
</a
> as a
8197 Debian Edu client, and using it he can take the existing
8198 <a href=
"http://www.raspbian.org/FrontPage
">Raspbian
</a
> installation and
8199 transform it into a fully functioning Debian Edu Workstation (or
8200 Roaming Workstation, or whatever :).
</p
>
8202 <p
>The default setting in the script is to create a KDE Workstation.
8203 If a LXDE based Roaming workstation is wanted instead, modify the
8204 PROFILE and DESKTOP values at the top to look like this instead:
</p
>
8206 <p
><pre
>
8207 PROFILE=
"Roaming-Workstation
"
8208 DESKTOP=
"lxde
"
8209 </pre
></p
>
8211 <p
>The script could even become useful to set up Debian Edu servers in
8212 the cloud, by starting with a virtual Debian installation at some
8213 virtual hosting service and setting up all the services on first
8219 <title>Debian, the Linux distribution of choice for LEGO designers?
</title>
8220 <link>https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</link>
8221 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian__the_Linux_distribution_of_choice_for_LEGO_designers_.html
</guid>
8222 <pubDate>Sat,
11 May
2013 20:
30:
00 +
0200</pubDate>
8223 <description><P
>In January,
8224 <a href=
"http://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
">I
8225 announced a
</a
> new
<a href=
"irc://irc.debian.org/%
23debian-lego
">IRC
8226 channel #debian-lego
</a
>, for those of us in the Debian and Linux
8227 community interested in
<a href=
"http://www.lego.com/
">LEGO
</a
>, the
8228 marvellous construction system from Denmark. We also created
8229 <a href=
"http://wiki.debian.org/LegoDesigners
">a wiki page
</a
> to have
8230 a place to take notes and write down our plans and hopes. And several
8231 people showed up to help. I was very happy to see the effect of my
8232 call. Since the small start, we have a debtags tag
8233 <a href=
"http://debtags.debian.net/search/bytag?wl=hardware::hobby:lego
">hardware::hobby:lego
</a
>
8234 tag for LEGO related packages, and now count
10 packages related to
8235 LEGO and
<a href=
"http://mindstorms.lego.com/
">Mindstorms
</a
>:
</p
>
8237 <p
><table
>
8238 <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
>
8239 <tr
><td
><a href=
"http://packages.qa.debian.org/leocad
">leocad
</a
></td
><td
>virtual brick CAD software
</td
></tr
>
8240 <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
>
8241 <tr
><td
><a href=
"http://packages.qa.debian.org/lnpd
">lnpd
</a
></td
><td
>daemon for LNP communication with BrickOS
</td
></tr
>
8242 <tr
><td
><a href=
"http://packages.qa.debian.org/nbc
">nbc
</a
></td
><td
>compiler for LEGO Mindstorms NXT bricks
</td
></tr
>
8243 <tr
><td
><a href=
"http://packages.qa.debian.org/nqc
">nqc
</a
></td
><td
>Not Quite C compiler for LEGO Mindstorms RCX
</td
></tr
>
8244 <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
>
8245 <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
>
8246 <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
>
8247 <tr
><td
><a href=
"http://packages.qa.debian.org/t2n
">t2n
</a
></td
><td
>simple command-line tool for Lego NXT
</td
></tr
>
8248 </table
></p
>
8250 <p
>Some of these are available in Wheezy, and all but one are
8251 currently available in Jessie/testing. leocad is so far only
8252 available in experimental.
</p
>
8254 <p
>If you care about LEGO in Debian, please join us on IRC and help
8255 adding the rest of the great free software tools available on Linux
8256 for LEGO designers.
</p
>
8261 <title>Debian Wheezy is out - and Debian Edu / Skolelinux should soon follow! #newinwheezy
</title>
8262 <link>https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</link>
8263 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_Wheezy_is_out___and_Debian_Edu___Skolelinux_should_soon_follow___newinwheezy.html
</guid>
8264 <pubDate>Sun,
5 May
2013 07:
40:
00 +
0200</pubDate>
8265 <description><p
>When I woke up this morning, I was very happy to see that the
8266 <a href=
"http://www.debian.org/News/
2013/
20130504">release announcement
8267 for Debian Wheezy
</a
> was waiting in my mail box. This is a great
8268 Debian release, and I expect to move my machines at home over to it fairly
8271 <p
>The new debian release contain heaps of new stuff, and one program
8272 in particular make me very happy to see included. The
8273 <a href=
"http://scratch.mit.edu/
">Scratch
</a
> program, made famous by
8274 the
<a href=
"http://www.code.org/
">Teach kids code
</a
> movement, is
8275 included for the first time. Alongside similar programs like
8276 <a href=
"http://edu.kde.org/kturtle/
">kturtle
</a
> and
8277 <a href=
"http://wiki.sugarlabs.org/go/Activities/Turtle_Art
">turtleart
</a
>,
8278 it allow for visual programming where syntax errors can not happen,
8279 and a friendly programming environment for learning to control the
8280 computer. Scratch will also be included in the next release of Debian
8283 <p
>And now that Wheezy is wrapped up, we can wrap up the next Debian
8284 Edu/Skolelinux release too. The
8285 <a href=
"http://lists.debian.org/debian-edu/
2013/
04/msg00132.html
">first
8286 alpha release
</a
> went out last week, and the next should soon
8292 <title>Isenkram
0.2 finally in the Debian archive
</title>
8293 <link>https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</link>
8294 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Isenkram_0_2_finally_in_the_Debian_archive.html
</guid>
8295 <pubDate>Wed,
3 Apr
2013 23:
40:
00 +
0200</pubDate>
8296 <description><p
>Today the
<a href=
"http://packages.qa.debian.org/isenkram
">Isenkram
8297 package
</a
> finally made it into the archive, after lingering in NEW
8298 for many months. I uploaded it to the Debian experimental suite
8299 2013-
01-
27, and today it was accepted into the archive.
</p
>
8301 <p
>Isenkram is a system for suggesting to users what packages to
8302 install to work with a pluggable hardware device. The suggestion pop
8303 up when the device is plugged in. For example if a Lego Mindstorm NXT
8304 is inserted, it will suggest to install the program needed to program
8305 the NXT controller. Give it a go, and report bugs and suggestions to
8311 <title>Bitcoin GUI now available from Debian/unstable (and Ubuntu/raring)
</title>
8312 <link>https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</link>
8313 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Bitcoin_GUI_now_available_from_Debian_unstable__and_Ubuntu_raring_.html
</guid>
8314 <pubDate>Sat,
2 Feb
2013 09:
00:
00 +
0100</pubDate>
8315 <description><p
>My
8316 <a href=
"http://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
">last
8317 bitcoin related blog post
</a
> mentioned that the new
8318 <a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin package
</a
> for
8319 Debian was waiting in NEW. It was accepted by the Debian ftp-masters
8320 2013-
01-
19, and have been available in unstable since then. It was
8321 automatically copied to Ubuntu, and is available in their Raring
8322 version too.
</p
>
8324 <p
>But there is a strange problem with the build that block this new
8325 version from being available on the i386 and kfreebsd-i386
8326 architectures. For some strange reason, the autobuilders in Debian
8327 for these architectures fail to run the test suite on these
8328 architectures (
<a href=
"http://bugs.debian.org/
672524">BTS #
672524</a
>).
8329 We are so far unable to reproduce it when building it manually, and
8330 no-one have been able to propose a fix. If you got an idea what is
8331 failing, please let us know via the BTS.
</p
>
8333 <p
>One feature that is annoying me with of the bitcoin client, because
8334 I often run low on disk space, is the fact that the client will exit
8335 if it run short on space (
<a href=
"http://bugs.debian.org/
696715">BTS
8336 #
696715</a
>). So make sure you have enough disk space when you run
8339 <p
>As usual, if you use bitcoin and want to show your support of my
8340 activities, please send Bitcoin donations to my address
8341 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
8346 <title>Welcome to the world, Isenkram!
</title>
8347 <link>https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</link>
8348 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
</guid>
8349 <pubDate>Tue,
22 Jan
2013 22:
00:
00 +
0100</pubDate>
8350 <description><p
>Yesterday, I
8351 <a href=
"http://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
">asked
8352 for testers
</a
> for my prototype for making Debian better at handling
8353 pluggable hardware devices, which I
8354 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">set
8355 out to create
</a
> earlier this month. Several valuable testers showed
8356 up, and caused me to really want to to open up the development to more
8357 people. But before I did this, I want to come up with a sensible name
8358 for this project. Today I finally decided on a new name, and I have
8359 renamed the project from hw-support-handler to this new name. In the
8360 process, I moved the source to git and made it available as a
8361 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/isenkram.git
">collab-maint
</a
>
8362 repository in Debian. The new name? It is
<strong
>Isenkram
</strong
>.
8363 To fetch and build the latest version of the source, use
</p
>
8366 git clone http://anonscm.debian.org/git/collab-maint/isenkram.git
8367 cd isenkram
&& git-buildpackage -us -uc
8370 <p
>I have not yet adjusted all files to use the new name yet. If you
8371 want to hack on the source or improve the package, please go ahead.
8372 But please talk to me first on IRC or via email before you do major
8373 changes, to make sure we do not step on each others toes. :)
</p
>
8375 <p
>If you wonder what
'isenkram
' is, it is a Norwegian word for iron
8376 stuff, typically meaning tools, nails, screws, etc. Typical hardware
8377 stuff, in other words. I
've been told it is the Norwegian variant of
8378 the German word eisenkram, for those that are familiar with that
8381 <p
><strong
>Update
2013-
01-
26</strong
>: Added -us -us to build
8382 instructions, to avoid confusing people with an error from the signing
8385 <p
><strong
>Update
2013-
01-
27</strong
>: Switch to HTTP URL for the git
8386 clone argument to avoid the need for authentication.
</p
>
8391 <title>First prototype ready making hardware easier to use in Debian
</title>
8392 <link>https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</link>
8393 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/First_prototype_ready_making_hardware_easier_to_use_in_Debian.html
</guid>
8394 <pubDate>Mon,
21 Jan
2013 12:
00:
00 +
0100</pubDate>
8395 <description><p
>Early this month I set out to try to
8396 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">improve
8397 the Debian support for pluggable hardware devices
</a
>. Now my
8398 prototype is working, and it is ready for a larger audience. To test
8400 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">source
8401 from the Debian Edu subversion repository
</a
>, build and install the
8402 package. You might have to log out and in again activate the
8403 autostart script.
</p
>
8405 <p
>The design is simple:
</p
>
8409 <li
>Add desktop entry in /usr/share/autostart/ causing a program
8410 hw-support-handlerd to start when the user log in.
</li
>
8412 <li
>This program listen for kernel events about new hardware (directly
8413 from the kernel like udev does), not using HAL dbus events as I
8414 initially did.
</li
>
8416 <li
>When new hardware is inserted, look up the hardware modalias in
8417 the APT database, a database
8418 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=markup
">available
8419 via HTTP
</a
> and a database available as part of the package.
</li
>
8421 <li
>If a package is mapped to the hardware in question, the package
8422 isn
't installed yet and this is the first time the hardware was
8423 plugged in, show a desktop notification suggesting to install the
8424 package or packages.
</li
>
8426 <li
>If the user click on the
'install package now
' button, ask
8427 aptdaemon via the PackageKit API to install the requrired package.
</li
>
8429 <li
>aptdaemon ask for root password or sudo password, and install the
8430 package while showing progress information in a window.
</li
>
8434 <p
>I still need to come up with a better name for the system. Here
8435 are some screen shots showing the prototype in action. First the
8436 notification, then the password request, and finally the request to
8437 approve all the dependencies. Sorry for the Norwegian Bokmål GUI.
</p
>
8439 <p
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
1-notification.png
">
8440 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
2-password.png
">
8441 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
3-dependencies.png
">
8442 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
4-installing.png
">
8443 <br
><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
21-hw-support-
5-installing-details.png
" width=
"70%
"></p
>
8445 <p
>The prototype still need to be improved with longer timeouts, but
8446 is already useful. The database of hardware to package mappings also
8447 need more work. It is currently compatible with the Ubuntu way of
8448 storing such information in the package control file, but could be
8449 changed to use other formats instead or in addition to the current
8450 method. I
've dropped the use of discover for this mapping, as the
8451 modalias approach is more flexible and easier to use on Linux as long
8452 as the Linux kernel expose its modalias strings directly.
</p
>
8454 <p
><strong
>Update
2013-
01-
21 16:
50</strong
>: Due to popular demand,
8455 here is the command required to check out and build the source: Use
8456 '<tt
>svn checkout
8457 svn://svn.debian.org/debian-edu/trunk/src/hw-support-handler/; cd
8458 hw-support-handler; debuild
</tt
>'. If you lack debuild, install the
8459 devscripts package.
</p
>
8461 <p
><strong
>Update
2013-
01-
23 12:
00</strong
>: The project is now
8462 renamed to Isenkram and the source moved from the Debian Edu
8463 subversion repository to a Debian collab-maint git repository. See
8464 <a href=
"http://people.skolelinux.org/pere/blog/Welcome_to_the_world__Isenkram_.html
">build
8465 instructions
</a
> for details.
</p
>
8470 <title>Thank you Thinkpad X41, for your long and trustworthy service
</title>
8471 <link>https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</link>
8472 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Thank_you_Thinkpad_X41__for_your_long_and_trustworthy_service.html
</guid>
8473 <pubDate>Sat,
19 Jan
2013 09:
20:
00 +
0100</pubDate>
8474 <description><p
>This Christmas my trusty old laptop died. It died quietly and
8475 suddenly in bed. With a quiet whimper, it went completely quiet and
8476 black. The power button was no longer able to turn it on. It was a
8477 IBM Thinkpad X41, and the best laptop I ever had. Better than both
8478 Thinkpads X30, X31, X40, X60, X61 and X61S. Far better than the
8479 Compaq I had before that. Now I need to find a replacement. To keep
8480 going during Christmas, I moved the one year old SSD disk to my old
8481 X40 where it fitted (only one I had left that could use it), but it is
8482 not a durable solution.
8484 <p
>My laptop needs are fairly modest. This is my wishlist from when I
8485 got a new one more than
10 years ago. It still holds true.:)
</p
>
8489 <li
>Lightweight (around
1 kg) and small volume (preferably smaller
8490 than A4).
</li
>
8491 <li
>Robust, it will be in my backpack every day.
</li
>
8492 <li
>Three button mouse and a mouse pin instead of touch pad.
</li
>
8493 <li
>Long battery life time. Preferable a week.
</li
>
8494 <li
>Internal WIFI network card.
</li
>
8495 <li
>Internal Twisted Pair network card.
</li
>
8496 <li
>Some USB slots (
2-
3 is plenty)
</li
>
8497 <li
>Good keyboard - similar to the Thinkpad.
</li
>
8498 <li
>Video resolution at least
1024x768, with size around
12" (A4 paper
8500 <li
>Hardware supported by Debian Stable, ie the default kernel and
8501 X.org packages.
</li
>
8502 <li
>Quiet, preferably fan free (or at least not using the fan most of
8507 <p
>You will notice that there are no RAM and CPU requirements in the
8508 list. The reason is simply that the specifications on laptops the
8509 last
10-
15 years have been sufficient for my needs, and I have to look
8510 at other features to choose my laptop. But are there still made as
8511 robust laptops as my X41? The Thinkpad X60/X61 proved to be less
8512 robust, and Thinkpads seem to be heading in the wrong direction since
8513 Lenovo took over. But I
've been told that X220 and X1 Carbon might
8514 still be useful.
</p
>
8516 <p
>Perhaps I should rethink my needs, and look for a pad with an
8517 external keyboard? I
'll have to check the
8518 <a href=
"http://www.linux-laptop.net/
">Linux Laptops site
</a
> for
8519 well-supported laptops, or perhaps just buy one preinstalled from one
8520 of the vendors listed on the
<a href=
"http://linuxpreloaded.com/
">Linux
8521 Pre-loaded site
</a
>.
</p
>
8526 <title>How to find a browser plugin supporting a given MIME type
</title>
8527 <link>https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</link>
8528 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_find_a_browser_plugin_supporting_a_given_MIME_type.html
</guid>
8529 <pubDate>Fri,
18 Jan
2013 10:
40:
00 +
0100</pubDate>
8530 <description><p
>Some times I try to figure out which Iceweasel browser plugin to
8531 install to get support for a given MIME type. Thanks to
8532 <a href=
"https://wiki.ubuntu.com/MozillaTeam/Plugins
">specifications
8533 done by Ubuntu
</a
> and Mozilla, it is possible to do this in Debian.
8534 Unfortunately, not very many packages provide the needed meta
8535 information, Anyway, here is a small script to look up all browser
8536 plugin packages announcing ther MIME support using this specification:
</p
>
8542 def pkgs_handling_mimetype(mimetype):
8547 version = pkg.candidate
8549 version = pkg.installed
8552 record = version.record
8553 if not record.has_key(
'Npp-MimeType
'):
8555 mime_types = record[
'Npp-MimeType
'].split(
',
')
8556 for t in mime_types:
8557 t = t.rstrip().strip()
8559 thepkgs.append(pkg.name)
8561 mimetype =
"audio/ogg
"
8562 if
1 < len(sys.argv):
8563 mimetype = sys.argv[
1]
8564 print
"Browser plugin packages supporting %s:
" % mimetype
8565 for pkg in pkgs_handling_mimetype(mimetype):
8566 print
" %s
" %pkg
8569 <p
>It can be used like this to look up a given MIME type:
</p
>
8572 % ./apt-find-browserplug-for-mimetype
8573 Browser plugin packages supporting audio/ogg:
8575 % ./apt-find-browserplug-for-mimetype application/x-shockwave-flash
8576 Browser plugin packages supporting application/x-shockwave-flash:
8577 browser-plugin-gnash
8581 <p
>In Ubuntu this mechanism is combined with support in the browser
8582 itself to query for plugins and propose to install the needed
8583 packages. It would be great if Debian supported such feature too. Is
8584 anyone working on adding it?
</p
>
8586 <p
><strong
>Update
2013-
01-
18 14:
20</strong
>: The Debian BTS
8587 request for icweasel support for this feature is
8588 <a href=
"http://bugs.debian.org/
484010">#
484010</a
> from
2008 (and
8589 <a href=
"http://bugs.debian.org/
698426">#
698426</a
> from today). Lack
8590 of manpower and wish for a different design is the reason thus feature
8591 is not yet in iceweasel from Debian.
</p
>
8596 <title>What is the most supported MIME type in Debian?
</title>
8597 <link>https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</link>
8598 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_the_most_supported_MIME_type_in_Debian_.html
</guid>
8599 <pubDate>Wed,
16 Jan
2013 10:
10:
00 +
0100</pubDate>
8600 <description><p
>The
<a href=
"http://wiki.debian.org/AppStreamDebianProposal
">DEP-
11
8601 proposal to add AppStream information to the Debian archive
</a
>, is a
8602 proposal to make it possible for a Desktop application to propose to
8603 the user some package to install to gain support for a given MIME
8604 type, font, library etc. that is currently missing. With such
8605 mechanism in place, it would be possible for the desktop to
8606 automatically propose and install leocad if some LDraw file is
8607 downloaded by the browser.
</p
>
8609 <p
>To get some idea about the current content of the archive, I decided
8610 to write a simple program to extract all .desktop files from the
8611 Debian archive and look up the claimed MIME support there. The result
8613 <a href=
"http://ftp.skolelinux.org/pub/AppStreamTest
">Skolelinux FTP
8614 site
</a
>. Using the collected information, it become possible to
8615 answer the question in the title. Here are the
20 most supported MIME
8616 types in Debian stable (Squeeze), testing (Wheezy) and unstable (Sid).
8617 The complete list is available from the link above.
</p
>
8619 <p
><strong
>Debian Stable:
</strong
></p
>
8623 ----- -----------------------
8639 18 application/x-ogg
8646 <p
><strong
>Debian Testing:
</strong
></p
>
8650 ----- -----------------------
8666 18 application/x-ogg
8673 <p
><strong
>Debian Unstable:
</strong
></p
>
8677 ----- -----------------------
8694 18 application/x-ogg
8700 <p
>I am told that PackageKit can provide an API to access the kind of
8701 information mentioned in DEP-
11. I have not yet had time to look at
8702 it, but hope the PackageKit people in Debian are on top of these
8705 <p
><strong
>Update
2013-
01-
16 13:
35</strong
>: Updated numbers after
8706 discovering a typo in my script.
</p
>
8711 <title>Using modalias info to find packages handling my hardware
</title>
8712 <link>https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</link>
8713 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_modalias_info_to_find_packages_handling_my_hardware.html
</guid>
8714 <pubDate>Tue,
15 Jan
2013 08:
00:
00 +
0100</pubDate>
8715 <description><p
>Yesterday, I wrote about the
8716 <a href=
"http://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
">modalias
8717 values provided by the Linux kernel
</a
> following my hope for
8718 <a href=
"http://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
">better
8719 dongle support in Debian
</a
>. Using this knowledge, I have tested how
8720 modalias values attached to package names can be used to map packages
8721 to hardware. This allow the system to look up and suggest relevant
8722 packages when I plug in some new hardware into my machine, and replace
8723 discover and discover-data as the database used to map hardware to
8726 <p
>I create a modaliases file with entries like the following,
8727 containing package name, kernel module name (if relevant, otherwise
8728 the package name) and globs matching the relevant hardware
8731 <p
><blockquote
>
8732 Package: package-name
8733 <br
>Modaliases: module(modaliasglob, modaliasglob, modaliasglob)
</p
>
8734 </blockquote
></p
>
8736 <p
>It is fairly trivial to write code to find the relevant packages
8737 for a given modalias value using this file.
</p
>
8739 <p
>An entry like this would suggest the video and picture application
8740 cheese for many USB web cameras (interface bus class
0E01):
</p
>
8742 <p
><blockquote
>
8744 <br
>Modaliases: cheese(usb:v*p*d*dc*dsc*dp*ic0Eisc01ip*)
</p
>
8745 </blockquote
></p
>
8747 <p
>An entry like this would suggest the pcmciautils package when a
8748 CardBus bridge (bus class
0607) PCI device is present:
</p
>
8750 <p
><blockquote
>
8751 Package: pcmciautils
8752 <br
>Modaliases: pcmciautils(pci:v*d*sv*sd*bc06sc07i*)
8753 </blockquote
></p
>
8755 <p
>An entry like this would suggest the package colorhug-client when
8756 plugging in a ColorHug with USB IDs
04D8:F8DA:
</p
>
8758 <p
><blockquote
>
8759 Package: colorhug-client
8760 <br
>Modaliases: colorhug-client(usb:v04D8pF8DAd*)
</p
>
8761 </blockquote
></p
>
8763 <p
>I believe the format is compatible with the format of the Packages
8764 file in the Debian archive. Ubuntu already uses their Packages file
8765 to store their mappings from packages to hardware.
</p
>
8767 <p
>By adding a XB-Modaliases: header in debian/control, any .deb can
8768 announce the hardware it support in a way my prototype understand.
8769 This allow those publishing packages in an APT source outside the
8770 Debian archive as well as those backporting packages to make sure the
8771 hardware mapping are included in the package meta information. I
've
8772 tested such header in the pymissile package, and its modalias mapping
8773 is working as it should with my prototype. It even made it to Ubuntu
8776 <p
>To test if it was possible to look up supported hardware using only
8777 the shell tools available in the Debian installer, I wrote a shell
8778 implementation of the lookup code. The idea is to create files for
8779 each modalias and let the shell do the matching. Please check out and
8781 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/hw-support-lookup?view=co
">hw-support-lookup
</a
>
8782 shell script. It run without any extra dependencies and fetch the
8783 hardware mappings from the Debian archive and the subversion
8784 repository where I currently work on my prototype.
</p
>
8786 <p
>When I use it on a machine with a yubikey inserted, it suggest to
8787 install yubikey-personalization:
</p
>
8789 <p
><blockquote
>
8790 % ./hw-support-lookup
8791 <br
>yubikey-personalization
8793 </blockquote
></p
>
8795 <p
>When I run it on my Thinkpad X40 with a PCMCIA/CardBus slot, it
8796 propose to install the pcmciautils package:
</p
>
8798 <p
><blockquote
>
8799 % ./hw-support-lookup
8800 <br
>pcmciautils
8802 </blockquote
></p
>
8804 <p
>If you know of any hardware-package mapping that should be added to
8805 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/modaliases?view=co
">my
8806 database
</a
>, please tell me about it.
</p
>
8808 <p
>It could be possible to generate several of the mappings between
8809 packages and hardware. One source would be to look at packages with
8810 kernel modules, ie packages with *.ko files in /lib/modules/, and
8811 extract their modalias information. Another would be to look at
8812 packages with udev rules, ie packages with files in
8813 /lib/udev/rules.d/, and extract their vendor/model information to
8814 generate a modalias matching rule. I have not tested any of these to
8815 see if it work.
</p
>
8817 <p
>If you want to help implementing a system to let us propose what
8818 packages to install when new hardware is plugged into a Debian
8819 machine, please send me an email or talk to me on
8820 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
8825 <title>Modalias strings - a practical way to map
"stuff
" to hardware
</title>
8826 <link>https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</link>
8827 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Modalias_strings___a_practical_way_to_map__stuff__to_hardware.html
</guid>
8828 <pubDate>Mon,
14 Jan
2013 11:
20:
00 +
0100</pubDate>
8829 <description><p
>While looking into how to look up Debian packages based on hardware
8830 information, to find the packages that support a given piece of
8831 hardware, I refreshed my memory regarding modalias values, and decided
8832 to document the details. Here are my findings so far, also available
8834 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
8835 Debian Edu subversion repository
</a
>:
8837 <p
><strong
>Modalias decoded
</strong
></p
>
8839 <p
>This document try to explain what the different types of modalias
8840 values stands for. It is in part based on information from
8841 &lt;URL:
<a href=
"https://wiki.archlinux.org/index.php/Modalias
">https://wiki.archlinux.org/index.php/Modalias
</a
> &gt;,
8842 &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;,
8843 &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
8844 &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;.
8846 <p
>The modalias entries for a given Linux machine can be found using
8847 this shell script:
</p
>
8850 find /sys -name modalias -print0 | xargs -
0 cat | sort -u
8853 <p
>The supported modalias globs for a given kernel module can be found
8854 using modinfo:
</p
>
8857 % /sbin/modinfo psmouse | grep alias:
8858 alias: serio:ty05pr*id*ex*
8859 alias: serio:ty01pr*id*ex*
8863 <p
><strong
>PCI subtype
</strong
></p
>
8865 <p
>A typical PCI entry can look like this. This is an Intel Host
8866 Bridge memory controller:
</p
>
8868 <p
><blockquote
>
8869 pci:v00008086d00002770sv00001028sd000001ADbc06sc00i00
8870 </blockquote
></p
>
8872 <p
>This represent these values:
</p
>
8877 sv
00001028 (subvendor)
8878 sd
000001AD (subdevice)
8880 sc
00 (bus subclass)
8884 <p
>The vendor/device values are the same values outputted from
'lspci
8885 -n
' as
8086:
2770. The bus class/subclass is also shown by lspci as
8886 0600. The
0600 class is a host bridge. Other useful bus values are
8887 0300 (VGA compatible card) and
0200 (Ethernet controller).
</p
>
8889 <p
>Not sure how to figure out the interface value, nor what it
8892 <p
><strong
>USB subtype
</strong
></p
>
8894 <p
>Some typical USB entries can look like this. This is an internal
8895 USB hub in a laptop:
</p
>
8897 <p
><blockquote
>
8898 usb:v1D6Bp0001d0206dc09dsc00dp00ic09isc00ip00
8899 </blockquote
></p
>
8901 <p
>Here is the values included in this alias:
</p
>
8904 v
1D6B (device vendor)
8905 p
0001 (device product)
8907 dc
09 (device class)
8908 dsc
00 (device subclass)
8909 dp
00 (device protocol)
8910 ic
09 (interface class)
8911 isc
00 (interface subclass)
8912 ip
00 (interface protocol)
8915 <p
>The
0900 device class/subclass means hub. Some times the relevant
8916 class is in the interface class section. For a simple USB web camera,
8917 these alias entries show up:
</p
>
8919 <p
><blockquote
>
8920 usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc01ip00
8921 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic01isc02ip00
8922 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc01ip00
8923 <br
>usb:v0AC8p3420d5000dcEFdsc02dp01ic0Eisc02ip00
8924 </blockquote
></p
>
8926 <p
>Interface class
0E01 is video control,
0E02 is video streaming (aka
8927 camera),
0101 is audio control device and
0102 is audio streaming (aka
8928 microphone). Thus this is a camera with microphone included.
</p
>
8930 <p
><strong
>ACPI subtype
</strong
></p
>
8932 <p
>The ACPI type is used for several non-PCI/USB stuff. This is an IR
8933 receiver in a Thinkpad X40:
</p
>
8935 <p
><blockquote
>
8936 acpi:IBM0071:PNP0511:
8937 </blockquote
></p
>
8939 <p
>The values between the colons are IDs.
</p
>
8941 <p
><strong
>DMI subtype
</strong
></p
>
8943 <p
>The DMI table contain lots of information about the computer case
8944 and model. This is an entry for a IBM Thinkpad X40, fetched from
8945 /sys/devices/virtual/dmi/id/modalias:
</p
>
8947 <p
><blockquote
>
8948 dmi:bvnIBM:bvr1UETB6WW(
1.66):bd06/
15/
2005:svnIBM:pn2371H4G:pvrThinkPadX40:rvnIBM:rn2371H4G:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
8949 </blockquote
></p
>
8951 <p
>The values present are
</p
>
8954 bvn IBM (BIOS vendor)
8955 bvr
1UETB
6WW(
1.66) (BIOS version)
8956 bd
06/
15/
2005 (BIOS date)
8957 svn IBM (system vendor)
8958 pn
2371H4G (product name)
8959 pvr ThinkPadX40 (product version)
8960 rvn IBM (board vendor)
8961 rn
2371H4G (board name)
8962 rvr NotAvailable (board version)
8963 cvn IBM (chassis vendor)
8964 ct
10 (chassis type)
8965 cvr NotAvailable (chassis version)
8968 <p
>The chassis type
10 is Notebook. Other interesting values can be
8969 found in the dmidecode source:
</p
>
8973 4 Low Profile Desktop
8986 17 Main Server Chassis
8987 18 Expansion Chassis
8989 20 Bus Expansion Chassis
8990 21 Peripheral Chassis
8992 23 Rack Mount Chassis
9001 <p
>The chassis type values are not always accurately set in the DMI
9002 table. For example my home server is a tower, but the DMI modalias
9003 claim it is a desktop.
</p
>
9005 <p
><strong
>SerIO subtype
</strong
></p
>
9007 <p
>This type is used for PS/
2 mouse plugs. One example is from my
9008 test machine:
</p
>
9010 <p
><blockquote
>
9011 serio:ty01pr00id00ex00
9012 </blockquote
></p
>
9014 <p
>The values present are
</p
>
9023 <p
>This type is supported by the psmouse driver. I am not sure what
9024 the valid values are.
</p
>
9026 <p
><strong
>Other subtypes
</strong
></p
>
9028 <p
>There are heaps of other modalias subtypes according to
9029 file2alias.c. There is the rest of the list from that source: amba,
9030 ap, bcma, ccw, css, eisa, hid, i2c, ieee1394, input, ipack, isapnp,
9031 mdio, of, parisc, pcmcia, platform, scsi, sdio, spi, ssb, vio, virtio,
9032 vmbus, x86cpu and zorro. I did not spend time documenting all of
9033 these, as they do not seem relevant for my intended use with mapping
9034 hardware to packages when new stuff is inserted during run time.
</p
>
9036 <p
><strong
>Looking up kernel modules using modalias values
</strong
></p
>
9038 <p
>To check which kernel modules provide support for a given modalias,
9039 one can use the following shell script:
</p
>
9042 for id in $(find /sys -name modalias -print0 | xargs -
0 cat | sort -u); do \
9043 echo
"$id
" ; \
9044 /sbin/modprobe --show-depends
"$id
"|sed
's/^/ /
' ; \
9048 <p
>The output can look like this (only the first few entries as the
9049 list is very long on my test machine):
</p
>
9053 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/acpi/ac.ko
9055 FATAL: Module acpi:device: not found.
9057 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/char/nvram.ko
9058 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/leds/led-class.ko
9059 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/rfkill/rfkill.ko
9060 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/platform/x86/thinkpad_acpi.ko
9061 acpi:IBM0071:PNP0511:
9062 insmod /lib/modules/
2.6.32-
5-
686/kernel/lib/crc-ccitt.ko
9063 insmod /lib/modules/
2.6.32-
5-
686/kernel/net/irda/irda.ko
9064 insmod /lib/modules/
2.6.32-
5-
686/kernel/drivers/net/irda/nsc-ircc.ko
9068 <p
>If you want to help implementing a system to let us propose what
9069 packages to install when new hardware is plugged into a Debian
9070 machine, please send me an email or talk to me on
9071 <a href=
"irc://irc.debian.org/%
23debian-devel
">#debian-devel
</a
>.
</p
>
9073 <p
><strong
>Update
2013-
01-
15:
</strong
> Rewrite
"cat $(find ...)
" to
9074 "find ... -print0 | xargs -
0 cat
" to make sure it handle directories
9075 in /sys/ with space in them.
</p
>
9080 <title>Moved the pymissile Debian packaging to collab-maint
</title>
9081 <link>https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</link>
9082 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Moved_the_pymissile_Debian_packaging_to_collab_maint.html
</guid>
9083 <pubDate>Thu,
10 Jan
2013 20:
40:
00 +
0100</pubDate>
9084 <description><p
>As part of my investigation on how to improve the support in Debian
9085 for hardware dongles, I dug up my old Mark and Spencer USB Rocket
9086 Launcher and updated the Debian package
9087 <a href=
"http://packages.qa.debian.org/pymissile
">pymissile
</a
> to make
9088 sure udev will fix the device permissions when it is plugged in. I
9089 also added a
"Modaliases
" header to test it in the Debian archive and
9090 hopefully make the package be proposed by jockey in Ubuntu when a user
9091 plug in his rocket launcher. In the process I moved the source to a
9092 git repository under collab-maint, to make it easier for any DD to
9093 contribute.
<a href=
"http://code.google.com/p/pymissile/
">Upstream
</a
>
9094 is not very active, but the software still work for me even after five
9095 years of relative silence. The new git repository is not listed in
9096 the uploaded package yet, because I want to test the other changes a
9097 bit more before I upload the new version. If you want to check out
9098 the new version with a .desktop file included, visit the
9099 <a href=
"http://anonscm.debian.org/gitweb/?p=collab-maint/pymissile.git
">gitweb
9100 view
</a
> or use
"<tt
>git clone
9101 git://anonscm.debian.org/collab-maint/pymissile.git
</tt
>".
</p
>
9106 <title>Lets make hardware dongles easier to use in Debian
</title>
9107 <link>https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</link>
9108 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lets_make_hardware_dongles_easier_to_use_in_Debian.html
</guid>
9109 <pubDate>Wed,
9 Jan
2013 15:
40:
00 +
0100</pubDate>
9110 <description><p
>One thing that annoys me with Debian and Linux distributions in
9111 general, is that there is a great package management system with the
9112 ability to automatically install software packages by downloading them
9113 from the distribution mirrors, but no way to get it to automatically
9114 install the packages I need to use the hardware I plug into my
9115 machine. Even if the package to use it is easily available from the
9116 Linux distribution. When I plug in a LEGO Mindstorms NXT, it could
9117 suggest to automatically install the python-nxt, nbc and t2n packages
9118 I need to talk to it. When I plug in a Yubikey, it could propose the
9119 yubikey-personalization package. The information required to do this
9120 is available, but no-one have pulled all the pieces together.
</p
>
9122 <p
>Some years ago, I proposed to
9123 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg01206.html
">use
9124 the discover subsystem to implement this
</a
>. The idea is fairly
9129 <li
>Add a desktop entry in /usr/share/autostart/ pointing to a program
9130 starting when a user log in.
</li
>
9132 <li
>Set this program up to listen for kernel events emitted when new
9133 hardware is inserted into the computer.
</li
>
9135 <li
>When new hardware is inserted, look up the hardware ID in a
9136 database mapping to packages, and take note of any non-installed
9137 packages.
</li
>
9139 <li
>Show a message to the user proposing to install the discovered
9140 package, and make it easy to install it.
</li
>
9144 <p
>I am not sure what the best way to implement this is, but my
9145 initial idea was to use dbus events to discover new hardware, the
9146 discover database to find packages and
9147 <a href=
"http://www.packagekit.org/
">PackageKit
</a
> to install
9150 <p
>Yesterday, I found time to try to implement this idea, and the
9151 draft package is now checked into
9152 <a href=
"http://anonscm.debian.org/viewvc/debian-edu/trunk/src/hw-support-handler/
">the
9153 Debian Edu subversion repository
</a
>. In the process, I updated the
9154 <a href=
"http://packages.qa.debian.org/d/discover-data.html
">discover-data
</a
>
9155 package to map the USB ids of LEGO Mindstorms and Yubikey devices to
9156 the relevant packages in Debian, and uploaded a new version
9157 2.2013.01.09 to unstable. I also discovered that the current
9158 <a href=
"http://packages.qa.debian.org/d/discover.html
">discover
</a
>
9159 package in Debian no longer discovered any USB devices, because
9160 /proc/bus/usb/devices is no longer present. I ported it to use
9161 libusb as a fall back option to get it working. The fixed package
9162 version
2.1.2-
6 is now in experimental (didn
't upload it to unstable
9163 because of the freeze).
</p
>
9165 <p
>With this prototype in place, I can insert my Yubikey, and get this
9166 desktop notification to show up (only once, the first time it is
9167 inserted):
</p
>
9169 <p align=
"center
"><img src=
"http://people.skolelinux.org/pere/blog/images/
2013-
01-
09-hw-autoinstall.png
"></p
>
9171 <p
>For this prototype to be really useful, some way to automatically
9172 install the proposed packages by pressing the
"Please install
9173 program(s)
" button should to be implemented.
</p
>
9175 <p
>If this idea seem useful to you, and you want to help make it
9176 happen, please help me update the discover-data database with mappings
9177 from hardware to Debian packages. Check if
'discover-pkginstall -l
'
9178 list the package you would like to have installed when a given
9179 hardware device is inserted into your computer, and report bugs using
9180 reportbug if it isn
't. Or, if you know of a better way to provide
9181 such mapping, please let me know.
</p
>
9183 <p
>This prototype need more work, and there are several questions that
9184 should be considered before it is ready for production use. Is dbus
9185 the correct way to detect new hardware? At the moment I look for HAL
9186 dbus events on the system bus, because that is the events I could see
9187 on my Debian Squeeze KDE desktop. Are there better events to use?
9188 How should the user be notified? Is the desktop notification
9189 mechanism the best option, or should the background daemon raise a
9190 popup instead? How should packages be installed? When should they
9191 not be installed?
</p
>
9193 <p
>If you want to help getting such feature implemented in Debian,
9194 please send me an email. :)
</p
>
9199 <title>New IRC channel for LEGO designers using Debian
</title>
9200 <link>https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</link>
9201 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/New_IRC_channel_for_LEGO_designers_using_Debian.html
</guid>
9202 <pubDate>Wed,
2 Jan
2013 15:
40:
00 +
0100</pubDate>
9203 <description><p
>During Christmas, I have worked a bit on the Debian support for
9204 <a href=
"http://mindstorms.lego.com/en-us/Default.aspx
">LEGO Mindstorm
9205 NXT
</a
>. My son and I have played a bit with my NXT set, and I
9206 discovered I had to build all the tools myself because none were
9207 already in Debian Squeeze. If Debian support for LEGO is something
9208 you care about, please join me on the IRC channel
9209 <a href=
"irc://irc.debian.org/%
23debian-lego
">#debian-lego
</a
> (server
9210 irc.debian.org). There is a lot that could be done to improve the
9211 Debian support for LEGO designers. For example both CAD software
9212 and Mindstorm compilers are missing. :)
</p
>
9214 <p
>Update
2012-
01-
03: A
9215 <a href=
"http://wiki.debian.org/LegoDesigners
">project page
</a
>
9216 including links to Lego related packages is now available.
</p
>
9221 <title>How to backport bitcoin-qt version
0.7.2-
2 to Debian Squeeze
</title>
9222 <link>https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</link>
9223 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_backport_bitcoin_qt_version_0_7_2_2_to_Debian_Squeeze.html
</guid>
9224 <pubDate>Tue,
25 Dec
2012 20:
50:
00 +
0100</pubDate>
9225 <description><p
>Let me start by wishing you all marry Christmas and a happy new
9226 year! I hope next year will prove to be a good year.
</p
>
9228 <p
><a href=
"http://www.bitcoin.org/
">Bitcoin
</a
>, the digital
9229 decentralised
"currency
" that allow people to transfer bitcoins
9230 between each other with minimal overhead, is a very interesting
9231 experiment. And as I wrote a few days ago, the bitcoin situation in
9232 <a href=
"http://www.debian.org/
">Debian
</a
> is about to improve a bit.
9233 The
<a href=
"http://packages.qa.debian.org/bitcoin
">new debian source
9234 package
</a
> (version
0.7.2-
2) was uploaded yesterday, and is waiting
9235 in
<a href=
"http://ftp-master.debian.org/new.html
">the NEW queue
</A
>
9236 for one of the ftpmasters to approve the new bitcoin-qt package
9239 <p
>And thanks to the great work of Jonas and the rest of the bitcoin
9240 team in Debian, you can easily test the package in Debian Squeeze
9241 using the following steps to get a set of working packages:
</p
>
9243 <blockquote
><pre
>
9244 git clone git://git.debian.org/git/collab-maint/bitcoin
9246 DEB_MAINTAINER_MODE=
1 DEB_BUILD_OPTIONS=noupnp fakeroot debian/rules clean
9247 DEB_BUILD_OPTIONS=noupnp git-buildpackage --git-ignore-new
9248 </pre
></blockquote
>
9250 <p
>You might have to install some build dependencies as well. The
9251 list of commands should give you two packages, bitcoind and
9252 bitcoin-qt, ready for use in a Squeeze environment. Note that the
9253 client will download the complete set of bitcoin
"blocks
", which need
9254 around
5.6 GiB of data on my machine at the moment. Make sure your
9255 ~/.bitcoin/ directory have lots of spare room if you want to download
9256 all the blocks. The client will warn if the disk is getting full, so
9257 there is not really a problem if you got too little room, but you will
9258 not be able to get all the features out of the client.
</p
>
9260 <p
>As usual, if you use bitcoin and want to show your support of my
9261 activities, please send Bitcoin donations to my address
9262 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9267 <title>A word on bitcoin support in Debian
</title>
9268 <link>https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</link>
9269 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_word_on_bitcoin_support_in_Debian.html
</guid>
9270 <pubDate>Fri,
21 Dec
2012 23:
59:
00 +
0100</pubDate>
9271 <description><p
>It has been a while since I wrote about
9272 <a href=
"http://www.bitcoin.org/
">bitcoin
</a
>, the decentralised
9273 peer-to-peer based crypto-currency, and the reason is simply that I
9274 have been busy elsewhere. But two days ago, I started looking at the
9275 state of
<a href=
"http://packages.qa.debian.org/bitcoin
">bitcoin in
9276 Debian
</a
> again to try to recover my old bitcoin wallet. The package
9277 is now maintained by a
9278 <a href=
"https://alioth.debian.org/projects/pkg-bitcoin/
">team of
9279 people
</a
>, and the grunt work had already been done by this team. We
9280 owe a huge thank you to all these team members. :)
9281 But I was sad to discover that the bitcoin client is missing in
9282 Wheezy. It is only available in Sid (and an outdated client from
9283 backports). The client had several RC bugs registered in BTS blocking
9284 it from entering testing. To try to help the team and improve the
9285 situation, I spent some time providing patches and triaging the bug
9286 reports. I also had a look at the bitcoin package available from Matt
9288 <a href=
"https://launchpad.net/~bitcoin/+archive/bitcoin
">PPA for
9289 Ubuntu
</a
>, and moved the useful pieces from that version into the
9290 Debian package.
</p
>
9292 <p
>After checking with the main package maintainer Jonas Smedegaard on
9293 IRC, I pushed several patches into the collab-maint git repository to
9294 improve the package. It now contains fixes for the RC issues (not from
9295 me, but fixed by Scott Howard), build rules for a Qt GUI client
9296 package, konqueror support for the bitcoin: URI and bash completion
9297 setup. As I work on Debian Squeeze, I also created
9298 <a href=
"http://lists.alioth.debian.org/pipermail/pkg-bitcoin-devel/Week-of-Mon-
20121217/
000041.html
">a
9299 patch to backport
</a
> the latest version. Jonas is going to look at
9300 it and try to integrate it into the git repository before uploading a
9301 new version to unstable.
9303 <p
>I would very much like bitcoin to succeed, to get rid of the
9304 centralized control currently exercised in the monetary system. I
9305 find it completely unacceptable that the USA government is collecting
9306 transaction data for almost all international money transfers (most are done in USD and transaction logs shipped to the spooks), and
9307 that the major credit card companies can block legal money
9308 transactions to Wikileaks. But for bitcoin to succeed, more people
9309 need to use bitcoins, and more people need to accept bitcoins when
9310 they sell products and services. Improving the bitcoin support in
9311 Debian is a small step in the right direction, but not enough.
9312 Unfortunately the user experience when browsing the web and wanting to
9313 pay with bitcoin is still not very good. The bitcoin: URI is a step
9314 in the right direction, but need to work in most or every browser in
9315 use. Also the bitcoin-qt client is too heavy to fire up to do a
9316 quick transaction. I believe there are other clients available, but
9317 have not tested them.
</p
>
9320 <a href=
"http://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
">experiment
9321 with bitcoins
</a
> showed that at least some of my readers use bitcoin.
9322 I received
20.15 BTC so far on the address I provided in my blog two
9323 years ago, as can be
9324 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">seen
9325 on the blockexplorer service
</a
>. Thank you everyone for your
9326 donation. The blockexplorer service demonstrates quite well that
9327 bitcoin is not quite anonymous and untracked. :) I wonder if the
9328 number of users have gone up since then. If you use bitcoin and want
9329 to show your support of my activity, please send Bitcoin donations to
9330 the same address as last time,
9331 <b
><a href=
"bitcoin:
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
></b
>.
</p
>
9336 <title>Git repository for song book for Computer Scientists
</title>
9337 <link>https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</link>
9338 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Git_repository_for_song_book_for_Computer_Scientists.html
</guid>
9339 <pubDate>Fri,
7 Sep
2012 13:
50:
00 +
0200</pubDate>
9340 <description><p
>As I
9341 <a href=
"http://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
">mentioned
9342 this summer
</a
>, I have created a Computer Science song book a few
9343 years ago, and today I finally found time to create a public
9344 <a href=
"https://gitorious.org/pere-cs-songbook/pere-cs-songbook
">Gitorious
9345 repository for the project
</a
>.
</p
>
9347 <p
>If you want to help out, please clone the source and submit patches
9348 to the HTML version. To generate the PDF and PostScript version,
9349 please use prince XML, or let me know about a useful free software
9350 processor capable of creating a good looking PDF from the HTML.
</p
>
9352 <p
>Want to sing? You can still find the song book in HTML, PDF and
9353 PostScript formats at
9354 <a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's Computer
9355 Science Songbook
</a
>.
</p
>
9360 <title>Gratulerer med
19-årsdagen, Debian!
</title>
9361 <link>https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</link>
9362 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gratulerer_med_19__rsdagen__Debian_.html
</guid>
9363 <pubDate>Thu,
16 Aug
2012 11:
20:
00 +
0200</pubDate>
9364 <description><p
>I dag fyller
9365 <a href=
"http://www.debian.org/News/
2012/
20120813">Debian-prosjektet
19
9366 år
</a
>. Jeg har fulgt det de siste
12 årene, og er veldig glad for å kunne
9367 si gratulerer med dagen, Debian!
</p
>
9372 <title>Song book for Computer Scientists
</title>
9373 <link>https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</link>
9374 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Song_book_for_Computer_Scientists.html
</guid>
9375 <pubDate>Sun,
24 Jun
2012 13:
30:
00 +
0200</pubDate>
9376 <description><p
>Many years ago, while studying Computer Science at the
9377 <a href=
"http://www.uit.no/
">University of Tromsø
</a
>, I started
9378 collecting computer related songs for use at parties. The original
9379 version was written in LaTeX, but a few years ago I got help from
9380 Håkon W. Lie, one of the inventors of W3C CSS, to convert it to HTML
9381 while keeping the ability to create a nice book in PDF format. I have
9382 not had time to maintain the book for a while now, and guess I should
9383 put it up on some public version control repository where others can
9384 help me extend and update the book. If anyone is volunteering to help
9385 me with this, send me an email. Also let me know if there are songs
9386 missing in my book.
</p
>
9388 <p
>I have not mentioned the book on my blog so far, and it occured to
9389 me today that I really should let all my readers share the joys of
9390 singing out load about programming, computers and computer networks.
9391 Especially now that
<a href=
"http://debconf12.debconf.org/
">Debconf
9392 12</a
> is about to start (and I am not going). Want to sing? Check
9393 out
<a href=
"http://www.hungry.com/~pere/cs-songbook/
">Petter
's
9394 Computer Science Songbook
</a
>.
9399 <title>Automatically upgrading server firmware on Dell PowerEdge
</title>
9400 <link>https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</link>
9401 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatically_upgrading_server_firmware_on_Dell_PowerEdge.html
</guid>
9402 <pubDate>Mon,
21 Nov
2011 12:
00:
00 +
0100</pubDate>
9403 <description><p
>At work we have heaps of servers. I believe the total count is
9404 around
1000 at the moment. To be able to get help from the vendors
9405 when something go wrong, we want to keep the firmware on the servers
9406 up to date. If the firmware isn
't the latest and greatest, the
9407 vendors typically refuse to start debugging any problems until the
9408 firmware is upgraded. So before every reboot, we want to upgrade the
9409 firmware, and we would really like everyone handling servers at the
9410 university to do this themselves when they plan to reboot a machine.
9411 For that to happen we at the unix server admin group need to provide
9412 the tools to do so.
</p
>
9414 <p
>To make firmware upgrading easier, I am working on a script to
9415 fetch and install the latest firmware for the servers we got. Most of
9416 our hardware are from Dell and HP, so I have focused on these servers
9417 so far. This blog post is about the Dell part.
</P
>
9419 <p
>On the Dell FTP site I was lucky enough to find
9420 <a href=
"ftp://ftp.us.dell.com/catalog/Catalog.xml.gz
">an XML file
</a
>
9421 with firmware information for all
11th generation servers, listing
9422 which firmware should be used on a given model and where on the FTP
9423 site I can find it. Using a simple perl XML parser I can then
9424 download the shell scripts Dell provides to do firmware upgrades from
9425 within Linux and reboot when all the firmware is primed and ready to
9426 be activated on the first reboot.
</p
>
9428 <p
>This is the Dell related fragment of the perl code I am working on.
9429 Are there anyone working on similar tools for firmware upgrading all
9430 servers at a site? Please get in touch and lets share resources.
</p
>
9432 <p
><pre
>
9436 use File::Temp qw(tempdir);
9438 # Install needed RHEL packages if missing
9440 'XML::Simple
' =
> 'perl-XML-Simple
',
9442 for my $module (keys %rhelmodules) {
9443 eval
"use $module;
";
9445 my $pkg = $rhelmodules{$module};
9446 system(
"yum install -y $pkg
");
9447 eval
"use $module;
";
9451 my $errorsto =
'pere@hungry.com
';
9457 sub run_firmware_script {
9458 my ($opts, $script) = @_;
9460 print STDERR
"fail: missing script name\n
";
9463 print STDERR
"Running $script\n\n
";
9465 if (
0 == system(
"sh $script $opts
")) { # FIXME correct exit code handling
9466 print STDERR
"success: firmware script ran succcessfully\n
";
9468 print STDERR
"fail: firmware script returned error\n
";
9472 sub run_firmware_scripts {
9473 my ($opts, @dirs) = @_;
9474 # Run firmware packages
9475 for my $dir (@dirs) {
9476 print STDERR
"info: Running scripts in $dir\n
";
9477 opendir(my $dh, $dir) or die
"Unable to open directory $dir: $!
";
9478 while (my $s = readdir $dh) {
9479 next if $s =~ m/^\.\.?/;
9480 run_firmware_script($opts,
"$dir/$s
");
9488 print STDERR
"info: Downloading $url\n
";
9489 system(
"wget --quiet \
"$url\
"");
9494 my $product = `dmidecode -s system-product-name`;
9497 if ($product =~ m/PowerEdge/) {
9499 # on RHEL, these pacakges are needed by the firwmare upgrade scripts
9500 system(
'yum install -y compat-libstdc++-
33.i686 libstdc++.i686 libxml2.i686 procmail
');
9502 my $tmpdir = tempdir(
9506 fetch_dell_fw(
'catalog/Catalog.xml.gz
');
9507 system(
'gunzip Catalog.xml.gz
');
9508 my @paths = fetch_dell_fw_list(
'Catalog.xml
');
9509 # -q is quiet, disabling interactivity and reducing console output
9510 my $fwopts =
"-q
";
9512 for my $url (@paths) {
9513 fetch_dell_fw($url);
9515 run_firmware_scripts($fwopts, $tmpdir);
9517 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9518 print STDERR
"error: Please report to $errorsto.\n
";
9522 print STDERR
"error: Unsupported Dell model
'$product
'.\n
";
9523 print STDERR
"error: Please report to $errorsto.\n
";
9529 my $url =
"ftp://ftp.us.dell.com/$path
";
9533 # Using ftp://ftp.us.dell.com/catalog/Catalog.xml.gz, figure out which
9534 # firmware packages to download from Dell. Only work for Linux
9535 # machines and
11th generation Dell servers.
9536 sub fetch_dell_fw_list {
9537 my $filename = shift;
9539 my $product = `dmidecode -s system-product-name`;
9541 my ($mybrand, $mymodel) = split(/\s+/, $product);
9543 print STDERR
"Finding firmware bundles for $mybrand $mymodel\n
";
9545 my $xml = XMLin($filename);
9547 for my $bundle (@{$xml-
>{SoftwareBundle}}) {
9548 my $brand = $bundle-
>{TargetSystems}-
>{Brand}-
>{Display}-
>{content};
9549 my $model = $bundle-
>{TargetSystems}-
>{Brand}-
>{Model}-
>{Display}-
>{content};
9551 if (
"ARRAY
" eq ref $bundle-
>{TargetOSes}-
>{OperatingSystem}) {
9552 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}[
0]-
>{osCode};
9554 $oscode = $bundle-
>{TargetOSes}-
>{OperatingSystem}-
>{osCode};
9556 if ($mybrand eq $brand
&& $mymodel eq $model
&& "LIN
" eq $oscode)
9558 @paths = map { $_-
>{path} } @{$bundle-
>{Contents}-
>{Package}};
9561 for my $component (@{$xml-
>{SoftwareComponent}}) {
9562 my $componenttype = $component-
>{ComponentType}-
>{value};
9564 # Drop application packages, only firmware and BIOS
9565 next if
'APAC
' eq $componenttype;
9567 my $cpath = $component-
>{path};
9568 for my $path (@paths) {
9569 if ($cpath =~ m%/$path$%) {
9570 push(@paths, $cpath);
9578 <p
>The code is only tested on RedHat Enterprise Linux, but I suspect
9579 it could work on other platforms with some tweaking. Anyone know a
9580 index like Catalog.xml is available from HP for HP servers? At the
9581 moment I maintain a similar list manually and it is quickly getting
9587 <title>How is booting into runlevel
1 different from single user boots?
</title>
9588 <link>https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</link>
9589 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_is_booting_into_runlevel_1_different_from_single_user_boots_.html
</guid>
9590 <pubDate>Thu,
4 Aug
2011 12:
40:
00 +
0200</pubDate>
9591 <description><p
>Wouter Verhelst have some
9592 <a href=
"http://grep.be/blog/en/retorts/pere_kubuntu_boot
">interesting
9593 comments and opinions
</a
> on my blog post on
9594 <a href=
"http://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
">the
9595 need to clean up /etc/rcS.d/ in Debian
</a
> and my blog post about
9596 <a href=
"http://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
">the
9597 default KDE desktop in Debian
</a
>. I only have time to address one
9598 small piece of his comment now, and though it best to address the
9599 misunderstanding he bring forward:
</p
>
9601 <p
><blockquote
>
9602 Currently, a system admin has four options: [...] boot to a
9603 single-user system (by adding
'single
' to the kernel command line;
9604 this runs rcS and rc1 scripts)
9605 </blockquote
></p
>
9607 <p
>This make me believe Wouter believe booting into single user mode
9608 and booting into runlevel
1 is the same. I am not surprised he
9609 believe this, because it would make sense and is a quite sensible
9610 thing to believe. But because the boot in Debian is slightly broken,
9611 runlevel
1 do not work properly and it isn
't the same as single user
9612 mode. I
'll try to explain what is actually happing, but it is a bit
9613 hard to explain.
</p
>
9615 <p
>Single user mode is defined like this in /etc/inittab:
9616 "<tt
>~~:S:wait:/sbin/sulogin
</tt
>". This means the only thing that is
9617 executed in single user mode is sulogin. Single user mode is a boot
9618 state
"between
" the runlevels, and when booting into single user mode,
9619 only the scripts in /etc/rcS.d/ are executed before the init process
9620 enters the single user state. When switching to runlevel
1, the state
9621 is in fact not ending in runlevel
1, but it passes through runlevel
1
9622 and end up in the single user mode (see /etc/rc1.d/S03single, which
9623 runs
"init -t1 S
" to switch to single user mode at the end of runlevel
9624 1. It is confusing that the
'S
' (single user) init mode is not the
9625 mode enabled by /etc/rcS.d/ (which is more like the initial boot
9628 <p
>This summary might make it clearer. When booting for the first
9629 time into single user mode, the following commands are executed:
9630 "<tt
>/etc/init.d/rc S; /sbin/sulogin
</tt
>". When booting into
9631 runlevel
1, the following commands are executed:
"<tt
>/etc/init.d/rc
9632 S; /etc/init.d/rc
1; /sbin/sulogin
</tt
>". A problem show up when
9633 trying to continue after visiting single user mode. Not all services
9634 are started again as they should, causing the machine to end up in an
9635 unpredicatble state. This is why Debian admins recommend rebooting
9636 after visiting single user mode.
</p
>
9638 <p
>A similar problem with runlevel
1 is caused by the amount of
9639 scripts executed from /etc/rcS.d/. When switching from say runlevel
2
9640 to runlevel
1, the services started from /etc/rcS.d/ are not properly
9641 stopped when passing through the scripts in /etc/rc1.d/, and not
9642 started again when switching away from runlevel
1 to the runlevels
9643 2-
5. I believe the problem is best fixed by moving all the scripts
9644 out of /etc/rcS.d/ that are not
<strong
>required
</strong
> to get a
9645 functioning single user mode during boot.
</p
>
9647 <p
>I have spent several years investigating the Debian boot system,
9648 and discovered this problem a few years ago. I suspect it originates
9649 from when sysvinit was introduced into Debian, a long time ago.
</p
>
9654 <title>What should start from /etc/rcS.d/ in Debian? - almost nothing
</title>
9655 <link>https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</link>
9656 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_should_start_from__etc_rcS_d__in_Debian____almost_nothing.html
</guid>
9657 <pubDate>Sat,
30 Jul
2011 14:
00:
00 +
0200</pubDate>
9658 <description><p
>In the Debian boot system, several packages include scripts that
9659 are started from /etc/rcS.d/. In fact, there is a bite more of them
9660 than make sense, and this causes a few problems. What kind of
9661 problems, you might ask. There are at least two problems. The first
9662 is that it is not possible to recover a machine after switching to
9663 runlevel
1. One need to actually reboot to get the machine back to
9664 the expected state. The other is that single user boot will sometimes
9665 run into problems because some of the subsystems are activated before
9666 the root login is presented, causing problems when trying to recover a
9667 machine from a problem in that subsystem. A minor additional point is
9668 that moving more scripts out of rcS.d/ and into the other rc#.d/
9669 directories will increase the amount of scripts that can run in
9670 parallel during boot, and thus decrease the boot time.
</p
>
9672 <p
>So, which scripts should start from rcS.d/. In short, only the
9673 scripts that _have_ to execute before the root login prompt is
9674 presented during a single user boot should go there. Everything else
9675 should go into the numeric runlevels. This means things like
9676 lm-sensors, fuse and x11-common should not run from rcS.d, but from
9677 the numeric runlevels. Today in Debian, there are around
115 init.d
9678 scripts that are started from rcS.d/, and most of them should be moved
9679 out. Do your package have one of them? Please help us make single
9680 user and runlevel
1 better by moving it.
</p
>
9682 <p
>Scripts setting up the screen, keyboard, system partitions
9683 etc. should still be started from rcS.d/, but there is for example no
9684 need to have the network enabled before the single user login prompt
9685 is presented.
</p
>
9687 <p
>As always, things are not so easy to fix as they sound. To keep
9688 Debian systems working while scripts migrate and during upgrades, the
9689 scripts need to be moved from rcS.d/ to rc2.d/ in reverse dependency
9690 order, ie the scripts that nothing in rcS.d/ depend on can be moved,
9691 and the next ones can only be moved when their dependencies have been
9692 moved first. This migration must be done sequentially while we ensure
9693 that the package system upgrade packages in the right order to keep
9694 the system state correct. This will require some coordination when it
9695 comes to network related packages, but most of the packages with
9696 scripts that should migrate do not have anything in rcS.d/ depending
9697 on them. Some packages have already been updated, like the sudo
9698 package, while others are still left to do. I wish I had time to work
9699 on this myself, but real live constrains make it unlikely that I will
9700 find time to push this forward.
</p
>
9705 <title>What is missing in the Debian desktop, or why my parents use Kubuntu
</title>
9706 <link>https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</link>
9707 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_is_missing_in_the_Debian_desktop__or_why_my_parents_use_Kubuntu.html
</guid>
9708 <pubDate>Fri,
29 Jul
2011 08:
10:
00 +
0200</pubDate>
9709 <description><p
>While at Debconf11, I have several times during discussions
9710 mentioned the issues I believe should be improved in Debian for its
9711 desktop to be useful for more people. The use case for this is my
9712 parents, which are currently running Kubuntu which solve the
9715 <p
>I suspect these four missing features are not very hard to
9716 implement. After all, they are present in Ubuntu, so if we wanted to
9717 do this in Debian we would have a source.
</p
>
9721 <li
><strong
>Simple GUI based upgrade of packages.
</strong
> When there
9722 are new packages available for upgrades, a icon in the KDE status bar
9723 indicate this, and clicking on it will activate the simple upgrade
9724 tool to handle it. I have no problem guiding both of my parents
9725 through the process over the phone. If a kernel reboot is required,
9726 this too is indicated by the status bars and the upgrade tool. Last
9727 time I checked, nothing with the same features was working in KDE in
9730 <li
><strong
>Simple handling of missing Firefox browser
9731 plugins.
</strong
> When the browser encounter a MIME type it do not
9732 currently have a handler for, it will ask the user if the system
9733 should search for a package that would add support for this MIME type,
9734 and if the user say yes, the APT sources will be searched for packages
9735 advertising the MIME type in their control file (visible in the
9736 Packages file in the APT archive). If one or more packages are found,
9737 it is a simple click of the mouse to add support for the missing mime
9738 type. If the package require the user to accept some non-free
9739 license, this is explained to the user. The entire process make it
9740 more clear to the user why something do not work in the browser, and
9741 make the chances higher for the user to blame the web page authors and
9742 not the browser for any missing features.
</li
>
9744 <li
><strong
>Simple handling of missing multimedia codec/format
9745 handlers.
</strong
> When the media players encounter a format or codec
9746 it is not supporting, a dialog pop up asking the user if the system
9747 should search for a package that would add support for it. This
9748 happen with things like MP3, Windows Media or H
.264. The selection
9749 and installation procedure is very similar to the Firefox browser
9750 plugin handling. This is as far as I know implemented using a
9751 gstreamer hook. The end result is that the user easily get access to
9752 the codecs that are present from the APT archives available, while
9753 explaining more on why a given format is unsupported by Ubuntu.
</li
>
9755 <li
><strong
>Better browser handling of some MIME types.
</strong
> When
9756 displaying a text/plain file in my Debian browser, it will propose to
9757 start emacs to show it. If I remember correctly, when doing the same
9758 in Kunbutu it show the file as a text file in the browser. At least I
9759 know Opera will show text files within the browser. I much prefer the
9760 latter behaviour.
</li
>
9764 <p
>There are other nice features as well, like the simplified suite
9765 upgrader, but given that I am the one mostly doing the dist-upgrade,
9766 it do not matter much.
</p
>
9768 <p
>I really hope we could get these features in place for the next
9769 Debian release. It would require the coordinated effort of several
9770 maintainers, but would make the end user experience a lot better.
</p
>
9775 <title>Perl modules used by FixMyStreet which are missing in Debian/Squeeze
</title>
9776 <link>https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</link>
9777 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Perl_modules_used_by_FixMyStreet_which_are_missing_in_Debian_Squeeze.html
</guid>
9778 <pubDate>Tue,
26 Jul
2011 12:
25:
00 +
0200</pubDate>
9779 <description><p
>The Norwegian
<a href=
"http://www.fiksgatami.no/
">FiksGataMi
</A
>
9780 site is build on Debian/Squeeze, and this platform was chosen because
9781 I am most familiar with Debian (being a Debian Developer for around
10
9782 years) because it is the latest stable Debian release which should get
9783 security support for a few years.
</p
>
9785 <p
>The web service is written in Perl, and depend on some perl modules
9786 that are missing in Debian at the moment. It would be great if these
9787 modules were added to the Debian archive, allowing anyone to set up
9788 their own
<a href=
"http://www.fixmystreet.com
">FixMyStreet
</a
> clone
9789 in their own country using only Debian packages. The list of modules
9790 missing in Debian/Squeeze isn
't very long, and I hope the perl group
9791 will find time to package the
12 modules Catalyst::Plugin::SmartURI,
9792 Catalyst::Plugin::Unicode::Encoding, Catalyst::View::TT, Devel::Hide,
9793 Sort::Key, Statistics::Distributions, Template::Plugin::Comma,
9794 Template::Plugin::DateTime::Format, Term::Size::Any, Term::Size::Perl,
9795 URI::SmartURI and Web::Scraper to make the maintenance of FixMyStreet
9796 easier in the future.
</p
>
9798 <p
>Thanks to the great tools in Debian, getting the missing modules
9799 installed on my server was a simple call to
'cpan2deb Module::Name
'
9800 and
'dpkg -i
' to install the resulting package. But this leave me
9801 with the responsibility of tracking security problems, which I really
9802 do not have time for.
</p
>
9807 <title>A Norwegian FixMyStreet have kept me busy the last few weeks
</title>
9808 <link>https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</link>
9809 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_Norwegian_FixMyStreet_have_kept_me_busy_the_last_few_weeks.html
</guid>
9810 <pubDate>Sun,
3 Apr
2011 22:
50:
00 +
0200</pubDate>
9811 <description><p
>Here is a small update for my English readers. Most of my blog
9812 posts have been in Norwegian the last few weeks, so here is a short
9813 update in English.
</p
>
9815 <p
>The kids still keep me too busy to get much free software work
9816 done, but I did manage to organise a project to get a Norwegian port
9817 of the British service
9818 <a href=
"http://www.fixmystreet.com/
">FixMyStreet
</a
> up and running,
9819 and it has been running for a month now. The entire project has been
9820 organised by me and two others. Around Christmas we gathered sponsors
9821 to fund the development work. In January I drafted a contract with
9822 <a href=
"http://www.mysociety.org/
">mySociety
</a
> on what to develop,
9823 and in February the development took place. Most of it involved
9824 converting the source to use GPS coordinates instead of British
9825 easting/northing, and the resulting code should be a lot easier to get
9826 running in any country by now. The Norwegian
9827 <a href=
"http://www.fiksgatami.no/
">FiksGataMi
</a
> is using
9828 <a href=
"http://www.openstreetmap.org/
">OpenStreetmap
</a
> as the map
9829 source and the source for administrative borders in Norway, and
9830 support for this had to be added/fixed.
</p
>
9832 <p
>The Norwegian version went live March
3th, and we spent the weekend
9833 polishing the system before we announced it March
7th. The system is
9834 running on a KVM instance of Debian/Squeeze, and has seen almost
3000
9835 problem reports in a few weeks. Soon we hope to announce the Android
9836 and iPhone versions making it even easier to report problems with the
9837 public infrastructure.
</p
>
9839 <p
>Perhaps something to consider for those of you in countries without
9840 such service?
</p
>
9845 <title>Using NVD and CPE to track CVEs in locally maintained software
</title>
9846 <link>https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</link>
9847 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Using_NVD_and_CPE_to_track_CVEs_in_locally_maintained_software.html
</guid>
9848 <pubDate>Fri,
28 Jan
2011 15:
40:
00 +
0100</pubDate>
9849 <description><p
>The last few days I have looked at ways to track open security
9850 issues here at my work with the University of Oslo. My idea is that
9851 it should be possible to use the information about security issues
9852 available on the Internet, and check our locally
9853 maintained/distributed software against this information. It should
9854 allow us to verify that no known security issues are forgotten. The
9855 CVE database listing vulnerabilities seem like a great central point,
9856 and by using the package lists from Debian mapped to CVEs provided by
9857 the testing security team, I believed it should be possible to figure
9858 out which security holes were present in our free software
9859 collection.
</p
>
9861 <p
>After reading up on the topic, it became obvious that the first
9862 building block is to be able to name software packages in a unique and
9863 consistent way across data sources. I considered several ways to do
9864 this, for example coming up with my own naming scheme like using URLs
9865 to project home pages or URLs to the Freshmeat entries, or using some
9866 existing naming scheme. And it seem like I am not the first one to
9867 come across this problem, as MITRE already proposed and implemented a
9868 solution. Enter the
<a href=
"http://cpe.mitre.org/index.html
">Common
9869 Platform Enumeration
</a
> dictionary, a vocabulary for referring to
9870 software, hardware and other platform components. The CPE ids are
9871 mapped to CVEs in the
<a href=
"http://web.nvd.nist.gov/
">National
9872 Vulnerability Database
</a
>, allowing me to look up know security
9873 issues for any CPE name. With this in place, all I need to do is to
9874 locate the CPE id for the software packages we use at the university.
9875 This is fairly trivial (I google for
'cve cpe $package
' and check the
9876 NVD entry if a CVE for the package exist).
</p
>
9878 <p
>To give you an example. The GNU gzip source package have the CPE
9879 name cpe:/a:gnu:gzip. If the old version
1.3.3 was the package to
9880 check out, one could look up
9881 <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
9882 in NVD
</a
> and get a list of
6 security holes with public CVE entries.
9883 The most recent one is
9884 <a href=
"http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-
2010-
0001">CVE-
2010-
0001</a
>,
9885 and at the bottom of the NVD page for this vulnerability the complete
9886 list of affected versions is provided.
</p
>
9888 <p
>The NVD database of CVEs is also available as a XML dump, allowing
9889 for offline processing of issues. Using this dump, I
've written a
9890 small script taking a list of CPEs as input and list all CVEs
9891 affecting the packages represented by these CPEs. One give it CPEs
9892 with version numbers as specified above and get a list of open
9893 security issues out.
</p
>
9895 <p
>Of course for this approach to be useful, the quality of the NVD
9896 information need to be high. For that to happen, I believe as many as
9897 possible need to use and contribute to the NVD database. I notice
9899 <a href=
"https://www.redhat.com/security/data/metrics/rhsamapcpe.txt
">a
9900 map from CVE to CPE
</a
>, indicating that they are using the CPE
9901 information. I
'm not aware of Debian and Ubuntu doing the same.
</p
>
9903 <p
>To get an idea about the quality for free software, I spent some
9904 time making it possible to compare the CVE database from Debian with
9905 the CVE database in NVD. The result look fairly good, but there are
9906 some inconsistencies in NVD (same software package having several
9907 CPEs), and some inaccuracies (NVD not mentioning buggy packages that
9908 Debian believe are affected by a CVE). Hope to find time to improve
9909 the quality of NVD, but that require being able to get in touch with
9910 someone maintaining it. So far my three emails with questions and
9911 corrections have not seen any reply, but I hope contact can be
9912 established soon.
</p
>
9914 <p
>An interesting application for CPEs is cross platform package
9915 mapping. It would be useful to know which packages in for example
9916 RHEL, OpenSuSe and Mandriva are missing from Debian and Ubuntu, and
9917 this would be trivial if all linux distributions provided CPE entries
9918 for their packages.
</p
>
9923 <title>Which module is loaded for a given PCI and USB device?
</title>
9924 <link>https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</link>
9925 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Which_module_is_loaded_for_a_given_PCI_and_USB_device_.html
</guid>
9926 <pubDate>Sun,
23 Jan
2011 00:
20:
00 +
0100</pubDate>
9927 <description><p
>In the
9928 <a href=
"http://packages.qa.debian.org/discover-data
">discover-data
</a
>
9929 package in Debian, there is a script to report useful information
9930 about the running hardware for use when people report missing
9931 information. One part of this script that I find very useful when
9932 debugging hardware problems, is the part mapping loaded kernel module
9933 to the PCI device it claims. It allow me to quickly see if the kernel
9934 module I expect is driving the hardware I am struggling with. To see
9935 the output, make sure discover-data is installed and run
9936 <tt
>/usr/share/bug/discover-data
3>&1</tt
>. The relevant output on
9937 one of my machines like this:
</p
>
9941 10de:
03eb i2c_nforce2
9944 10de:
03f0 snd_hda_intel
9953 <p
>The code in question look like this, slightly modified for
9954 readability and to drop the output to file descriptor
3:
</p
>
9957 if [ -d /sys/bus/pci/devices/ ] ; then
9958 echo loaded pci modules:
9960 cd /sys/bus/pci/devices/
9961 for address in * ; do
9962 if [ -d
"$address/driver/module
" ] ; then
9963 module=`cd $address/driver/module ; pwd -P | xargs basename`
9964 if grep -q
"^$module
" /proc/modules ; then
9965 address=$(echo $address |sed s/
0000://)
9966 id=`lspci -n -s $address | tail -n
1 | awk
'{print $
3}
'`
9967 echo
"$id $module
"
9976 <p
>Similar code could be used to extract USB device module
9980 if [ -d /sys/bus/usb/devices/ ] ; then
9981 echo loaded usb modules:
9983 cd /sys/bus/usb/devices/
9984 for address in * ; do
9985 if [ -d
"$address/driver/module
" ] ; then
9986 module=`cd $address/driver/module ; pwd -P | xargs basename`
9987 if grep -q
"^$module
" /proc/modules ; then
9988 address=$(echo $address |sed s/
0000://)
9989 id=$(lsusb -s $address | tail -n
1 | awk
'{print $
6}
')
9990 if [
"$id
" ] ; then
9991 echo
"$id $module
"
10001 <p
>This might perhaps be something to include in other tools as
10007 <title>How to test if a laptop is working with Linux
</title>
10008 <link>https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</link>
10009 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/How_to_test_if_a_laptop_is_working_with_Linux.html
</guid>
10010 <pubDate>Wed,
22 Dec
2010 14:
55:
00 +
0100</pubDate>
10011 <description><p
>The last few days I have spent at work here at the
<a
10012 href=
"http://www.uio.no/
">University of Oslo
</a
> testing if the new
10013 batch of computers will work with Linux. Every year for the last few
10014 years the university have organised shared bid of a few thousand
10015 computers, and this year HP won the bid. Two different desktops and
10016 five different laptops are on the list this year. We in the UNIX
10017 group want to know which one of these computers work well with RHEL
10018 and Ubuntu, the two Linux distributions we currently handle at the
10019 university.
</p
>
10021 <p
>My test method is simple, and I share it here to get feedback and
10022 perhaps inspire others to test hardware as well. To test, I PXE
10023 install the OS version of choice, and log in as my normal user and run
10024 a few applications and plug in selected pieces of hardware. When
10025 something fail, I make a note about this in the test matrix and move
10026 on. If I have some spare time I try to report the bug to the OS
10027 vendor, but as I only have the machines for a short time, I rarely
10028 have the time to do this for all the problems I find.
</p
>
10030 <p
>Anyway, to get to the point of this post. Here is the simple tests
10031 I perform on a new model.
</p
>
10035 <li
>Is PXE installation working? I
'm testing with RHEL6, Ubuntu Lucid
10036 and Ubuntu Maverik at the moment. If I feel like it, I also test with
10037 RHEL5 and Debian Edu/Squeeze.
</li
>
10039 <li
>Is X.org working? If the graphical login screen show up after
10040 installation, X.org is working.
</li
>
10042 <li
>Is hardware accelerated OpenGL working? Running glxgears (in
10043 package mesa-utils on Ubuntu) and writing down the frames per second
10044 reported by the program.
</li
>
10046 <li
>Is sound working? With Gnome and KDE, a sound is played when
10047 logging in, and if I can hear this the test is successful. If there
10048 are several audio exits on the machine, I try them all and check if
10049 the Gnome/KDE audio mixer can control where to send the sound. I
10050 normally test this by playing
10051 <a href=
"http://www.nuug.no/aktiviteter/
20101012-chef/
">a HTML5
10052 video
</a
> in Firefox/Iceweasel.
</li
>
10054 <li
>Is the USB subsystem working? I test this by plugging in a USB
10055 memory stick and see if Gnome/KDE notices this.
</li
>
10057 <li
>Is the CD/DVD player working? I test this by inserting any CD/DVD
10058 I have lying around, and see if Gnome/KDE notices this.
</li
>
10060 <li
>Is any built in camera working? Test using cheese, and see if a
10061 picture from the v4l device show up.
</li
>
10063 <li
>Is bluetooth working? Use the Gnome/KDE browsing tool to see if
10064 any bluetooth devices are discovered. In my office, I normally see a
10067 <li
>For laptops, is the SD or Compaq Flash reader working. I have
10068 memory modules lying around, and stick them in and see if Gnome/KDE
10069 notice this.
</li
>
10071 <li
>For laptops, is suspend/hibernate working? I
'm testing if the
10072 special button work, and if the laptop continue to work after
10075 <li
>For laptops, is the extra buttons working, like audio level,
10076 adjusting background light, switching on/off external video output,
10077 switching on/off wifi, bluetooth, etc? The set of buttons differ from
10078 laptop to laptop, so I just write down which are working and which are
10081 <li
>Some laptops have smart card readers, finger print readers,
10082 acceleration sensors etc. I rarely test these, as I do not know how
10083 to quickly test if they are working or not, so I only document their
10084 existence.
</li
>
10088 <p
>By now I suspect you are really curious what the test results are
10089 for the HP machines I am testing. I
'm not done yet, so I will report
10090 the test results later. For now I can report that HP
8100 Elite work
10091 fine, and hibernation fail with HP EliteBook
8440p on Ubuntu Lucid,
10092 and audio fail on RHEL6. Ubuntu Maverik worked with
8440p. As you
10093 can see, I have most machines left to test. One interesting
10094 observation is that Ubuntu Lucid has almost twice the frame rate than
10095 RHEL6 with glxgears. No idea why.
</p
>
10100 <title>Some thoughts on BitCoins
</title>
10101 <link>https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</link>
10102 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_thoughts_on_BitCoins.html
</guid>
10103 <pubDate>Sat,
11 Dec
2010 15:
10:
00 +
0100</pubDate>
10104 <description><p
>As I continue to explore
10105 <a href=
"http://www.bitcoin.org/
">BitCoin
</a
>, I
've starting to wonder
10106 what properties the system have, and how it will be affected by laws
10107 and regulations here in Norway. Here are some random notes.
</p
>
10109 <p
>One interesting thing to note is that since the transactions are
10110 verified using a peer to peer network, all details about a transaction
10111 is known to everyone. This means that if a BitCoin address has been
10112 published like I did with mine in my initial post about BitCoin, it is
10113 possible for everyone to see how many BitCoins have been transfered to
10114 that address. There is even a web service to look at the details for
10115 all transactions. There I can see that my address
10116 <a href=
"http://blockexplorer.com/address/
15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
">15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</a
>
10117 have received
16.06 Bitcoin, the
10118 <a href=
"http://blockexplorer.com/address/
1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3">1LfdGnGuWkpSJgbQySxxCWhv
8MHqvwst
3</a
>
10119 address of Simon Phipps have received
181.97 BitCoin and the address
10120 <a href=
"http://blockexplorer.com/address/
1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
">1MCwBbhNGp5hRm5rC1Aims2YFRe2SXPYKt
</A
>
10121 of EFF have received
2447.38 BitCoins so far. Thank you to each and
10122 every one of you that donated bitcoins to support my activity. The
10123 fact that anyone can see how much money was transfered to a given
10124 address make it more obvious why the BitCoin community recommend to
10125 generate and hand out a new address for each transaction. I
'm told
10126 there is no way to track which addresses belong to a given person or
10127 organisation without the person or organisation revealing it
10128 themselves, as Simon, EFF and I have done.
</p
>
10130 <p
>In Norway, and in most other countries, there are laws and
10131 regulations limiting how much money one can transfer across the border
10132 without declaring it. There are money laundering, tax and accounting
10133 laws and regulations I would expect to apply to the use of BitCoin.
10134 If the Skolelinux foundation
10135 (
<a href=
"http://linuxiskolen.no/slxdebianlabs/donations.html
">SLX
10136 Debian Labs
</a
>) were to accept donations in BitCoin in addition to
10137 normal bank transfers like EFF is doing, how should this be accounted?
10138 Given that it is impossible to know if money can cross the border or
10139 not, should everything or nothing be declared? What exchange rate
10140 should be used when calculating taxes? Would receivers have to pay
10141 income tax if the foundation were to pay Skolelinux contributors in
10142 BitCoin? I have no idea, but it would be interesting to know.
</p
>
10144 <p
>For a currency to be useful and successful, it must be trusted and
10145 accepted by a lot of users. It must be possible to get easy access to
10146 the currency (as a wage or using currency exchanges), and it must be
10147 easy to spend it. At the moment BitCoin seem fairly easy to get
10148 access to, but there are very few places to spend it. I am not really
10149 a regular user of any of the vendor types currently accepting BitCoin,
10150 so I wonder when my kind of shop would start accepting BitCoins. I
10151 would like to buy electronics, travels and subway tickets, not herbs
10152 and books. :) The currency is young, and this will improve over time
10153 if it become popular, but I suspect regular banks will start to lobby
10154 to get BitCoin declared illegal if it become popular. I
'm sure they
10155 will claim it is helping fund terrorism and money laundering (which
10156 probably would be true, as is any currency in existence), but I
10157 believe the problems should be solved elsewhere and not by blaming
10158 currencies.
</p
>
10160 <p
>The process of creating new BitCoins is called mining, and it is
10161 CPU intensive process that depend on a bit of luck as well (as one is
10162 competing against all the other miners currently spending CPU cycles
10163 to see which one get the next lump of cash). The
"winner
" get
50
10164 BitCoin when this happen. Yesterday I came across the obvious way to
10165 join forces to increase ones changes of getting at least some coins,
10166 by coordinating the work on mining BitCoins across several machines
10167 and people, and sharing the result if one is lucky and get the
50
10168 BitCoins. Check out
10169 <a href=
"http://www.bluishcoder.co.nz/bitcoin-pool/
">BitCoin Pool
</a
>
10170 if this sounds interesting. I have not had time to try to set up a
10171 machine to participate there yet, but have seen that running on ones
10172 own for a few days have not yield any BitCoins througth mining
10175 <p
>Update
2010-
12-
15: Found an
<a
10176 href=
"http://inertia.posterous.com/reply-to-the-underground-economist-why-bitcoi
">interesting
10177 criticism
</a
> of bitcoin. Not quite sure how valid it is, but thought
10178 it was interesting to read. The arguments presented seem to be
10179 equally valid for gold, which was used as a currency for many years.
</p
>
10184 <title>Now accepting bitcoins - anonymous and distributed p2p crypto-money
</title>
10185 <link>https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</link>
10186 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Now_accepting_bitcoins___anonymous_and_distributed_p2p_crypto_money.html
</guid>
10187 <pubDate>Fri,
10 Dec
2010 08:
20:
00 +
0100</pubDate>
10188 <description><p
>With this weeks lawless
10189 <a href=
"http://www.salon.com/news/opinion/glenn_greenwald/
2010/
12/
06/wikileaks/index.html
">governmental
10190 attacks
</a
> on Wikileak and
10191 <a href=
"http://www.salon.com/technology/dan_gillmor/
2010/
12/
06/war_on_speech
">free
10192 speech
</a
>, it has become obvious that PayPal, visa and mastercard can
10193 not be trusted to handle money transactions.
10195 <a href=
"http://webmink.com/
2010/
12/
06/now-accepting-bitcoin/
">Simon
10196 Phipps on bitcoin
</a
> reminded me about a project that a friend of
10197 mine mentioned earlier. I decided to follow Simon
's example, and get
10198 involved with
<a href=
"http://www.bitcoin.org/
">BitCoin
</a
>. I got
10199 some help from my friend to get it all running, and he even handed me
10200 some bitcoins to get started. I even donated a few bitcoins to Simon
10201 for helping me remember BitCoin.
</p
>
10203 <p
>So, what is bitcoins, you probably wonder? It is a digital
10204 crypto-currency, decentralised and handled using peer-to-peer
10205 networks. It allows anonymous transactions and prohibits central
10206 control over the transactions, making it impossible for governments
10207 and companies alike to block donations and other transactions. The
10208 source is free software, and while the key dependency wxWidgets
2.9
10209 for the graphical user interface is missing in Debian, the command
10210 line client builds just fine. Hopefully Jonas
10211 <a href=
"http://bugs.debian.org/
578157">will get the package into
10212 Debian
</a
> soon.
</p
>
10214 <p
>Bitcoins can be converted to other currencies, like USD and EUR.
10215 There are
<a href=
"http://www.bitcoin.org/trade
">companies accepting
10216 bitcoins
</a
> when selling services and goods, and there are even
10217 currency
"stock
" markets where the exchange rate is decided. There
10218 are not many users so far, but the concept seems promising. If you
10219 want to get started and lack a friend with any bitcoins to spare,
10221 <a href=
"https://freebitcoins.appspot.com/
">some for free
</a
> (
0.05
10222 bitcoin at the time of writing). Use
10223 <a href=
"http://www.bitcoinwatch.com/
">BitcoinWatch
</a
> to keep an eye
10224 on the current exchange rates.
</p
>
10226 <p
>As an experiment, I have decided to set up bitcoind on one of my
10227 machines. If you want to support my activity, please send Bitcoin
10228 donations to the address
10229 <b
>15oWEoG9dUPovwmUL9KWAnYRtNJEkP1u1b
</b
>. Thank you!
</p
>
10234 <title>Why isn
't Debian Edu using VLC?
</title>
10235 <link>https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</link>
10236 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Why_isn_t_Debian_Edu_using_VLC_.html
</guid>
10237 <pubDate>Sat,
27 Nov
2010 11:
30:
00 +
0100</pubDate>
10238 <description><p
>In the latest issue of Linux Journal, the readers choices were
10239 presented, and the winner among the multimedia player were VLC.
10240 Personally, I like VLC, and it is my player of choice when I first try
10241 to play a video file or stream. Only if VLC fail will I drag out
10242 gmplayer to see if it can do better. The reason is mostly the failure
10243 model and trust. When VLC fail, it normally pop up a error message
10244 reporting the problem. When mplayer fail, it normally segfault or
10245 just hangs. The latter failure mode drain my trust in the program.
<p
>
10247 <p
>But even if VLC is my player of choice, we have choosen to use
10248 mplayer in
<a href=
"http://www.skolelinux.org/
">Debian
10249 Edu/Skolelinux
</a
>. The reason is simple. We need a good browser
10250 plugin to play web videos seamlessly, and the VLC browser plugin is
10251 not very good. For example, it lack in-line control buttons, so there
10252 is no way for the user to pause the video. Also, when I
10253 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">last
10254 tested the browser plugins
</a
> available in Debian, the VLC plugin
10255 failed on several video pages where mplayer based plugins worked. If
10256 the browser plugin for VLC was as good as the gecko-mediaplayer
10257 package (which uses mplayer), we would switch.
</P
>
10259 <p
>While VLC is a good player, its user interface is slightly
10260 annoying. The most annoying feature is its inconsistent use of
10261 keyboard shortcuts. When the player is in full screen mode, its
10262 shortcuts are different from when it is playing the video in a window.
10263 For example, space only work as pause when in full screen mode. I
10264 wish it had consisten shortcuts and that space also would work when in
10265 window mode. Another nice shortcut in gmplayer is [enter] to restart
10266 the current video. It is very nice when playing short videos from the
10267 web and want to restart it when new people arrive to have a look at
10268 what is going on.
</p
>
10273 <title>Lenny-
>Squeeze upgrades of the Gnome and KDE desktop, now with apt-get autoremove
</title>
10274 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades_of_the_Gnome_and_KDE_desktop__now_with_apt_get_autoremove.html
</link>
10275 <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>
10276 <pubDate>Mon,
22 Nov
2010 14:
15:
00 +
0100</pubDate>
10277 <description><p
>Michael Biebl suggested to me on IRC, that I changed my automated
10278 upgrade testing of the
10279 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
10280 Gnome and KDE Desktop
</a
> to do
<tt
>apt-get autoremove
</tt
> when using apt-get.
10281 This seem like a very good idea, so I adjusted by test scripts and
10282 can now present the updated result from today:
</p
>
10284 <p
>This is for Gnome:
</p
>
10286 <p
>Installed using apt-get, missing with aptitude
</p
>
10288 <blockquote
><p
>
10293 browser-plugin-gnash
10300 freedesktop-sound-theme
10302 gconf-defaults-service
10315 gnome-codec-install
10317 gnome-desktop-environment
10321 gnome-session-canberra
10323 gnome-themes-extras
10326 gstreamer0.10-fluendo-mp3
10327 gstreamer0.10-tools
10329 gtk2-engines-pixbuf
10330 gtk2-engines-smooth
10332 libapache2-mod-dnssd
10335 libaprutil1-dbd-sqlite3
10338 libboost-date-time1.42
.0
10339 libboost-python1.42
.0
10340 libboost-thread1.42
.0
10342 libchamplain-gtk-
0.4-
0
10344 libclutter-gtk-
0.10-
0
10351 libfreerdp-plugins-standard
10364 libgnome-vfs2.0-cil
10366 libgnomepanel2.24-cil
10371 libgtksourceview2.0-common
10372 libmono-addins-gui0.2-cil
10373 libmono-addins0.2-cil
10374 libmono-cairo2.0-cil
10375 libmono-corlib2.0-cil
10376 libmono-i18n-west2.0-cil
10377 libmono-posix2.0-cil
10378 libmono-security2.0-cil
10379 libmono-sharpzip2.84-cil
10380 libmono-system2.0-cil
10383 libndesk-dbus-glib1.0-cil
10384 libndesk-dbus1.0-cil
10394 libtelepathy-farsight0
10403 nautilus-sendto-empathy
10407 python-aptdaemon-gtk
10409 python-beautifulsoup
10424 python-gtksourceview2
10435 python-pkg-resources
10442 python-twisted-conch
10443 python-twisted-core
10448 python-zope.interface
10450 remmina-plugin-data
10453 rhythmbox-plugin-cdrecorder
10460 system-config-printer-udev
10462 telepathy-mission-control-
5
10469 transmission-common
10473 </p
></blockquote
>
10475 <p
>Installed using apt-get, removed with aptitude
</p
>
10477 <blockquote
><p
>
10481 epiphany-extensions
10483 fast-user-switch-applet
10502 libgtksourceview2.0-
0
10504 libsdl1.2debian-alsa
10510 system-config-printer
10515 </p
></blockquote
>
10517 <p
>Installed using aptitude, missing with apt-get
</p
>
10519 <blockquote
><p
>
10520 gstreamer0.10-gnomevfs
10521 </p
></blockquote
>
10523 <p
>Installed using aptitude, removed with apt-get
</p
>
10525 <blockquote
><p
>
10527 </p
></blockquote
>
10529 <p
>This is for KDE:
</p
>
10531 <p
>Installed using apt-get, missing with aptitude
</p
>
10533 <blockquote
><p
>
10535 </p
></blockquote
>
10537 <p
>Installed using apt-get, removed with aptitude
</p
>
10539 <blockquote
><p
>
10541 network-manager-kde
10542 </p
></blockquote
>
10544 <p
>Installed using aptitude, missing with apt-get
</p
>
10546 <blockquote
><p
>
10560 kdeartwork-emoticons
10562 kdeartwork-theme-icon
10566 kdebase-workspace-bin
10567 kdebase-workspace-data
10579 konqueror-nsplugins
10581 kscreensaver-xsavers
10596 plasma-dataengines-workspace
10598 plasma-desktopthemes-artwork
10599 plasma-runners-addons
10600 plasma-scriptengine-googlegadgets
10601 plasma-scriptengine-python
10602 plasma-scriptengine-qedje
10603 plasma-scriptengine-ruby
10604 plasma-scriptengine-webkit
10605 plasma-scriptengines
10606 plasma-wallpapers-addons
10607 plasma-widget-folderview
10608 plasma-widget-networkmanagement
10611 update-notifier-kde
10612 xscreensaver-data-extra
10614 xscreensaver-gl-extra
10615 xscreensaver-screensaver-bsod
10616 </p
></blockquote
>
10618 <p
>Installed using aptitude, removed with apt-get
</p
>
10620 <blockquote
><p
>
10622 google-gadgets-common
10640 libggadget-qt-
1.0-
0b
10645 libkonqsidebarplugin4a
10649 libkunitconversion4
10654 libplasma-geolocation-interface4
10656 libplasmagenericshell4
10670 libsmokeknewstuff2-
3
10671 libsmokeknewstuff3-
3
10673 libsmokektexteditor3
10681 libsmokeqtnetwork4-
3
10682 libsmokeqtopengl4-
3
10683 libsmokeqtscript4-
3
10687 libsmokeqtuitools4-
3
10688 libsmokeqtwebkit4-
3
10699 plasma-dataengines-addons
10700 plasma-scriptengine-superkaramba
10701 plasma-widget-lancelot
10702 plasma-widgets-addons
10703 plasma-widgets-workspace
10707 update-notifier-common
10708 </p
></blockquote
>
10710 <p
>Running apt-get autoremove made the results using apt-get and
10711 aptitude a bit more similar, but there are still quite a lott of
10712 differences. I have no idea what packages should be installed after
10713 the upgrade, but hope those that do can have a look.
</p
>
10718 <title>Migrating Xen virtual machines using LVM to KVM using disk images
</title>
10719 <link>https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</link>
10720 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Migrating_Xen_virtual_machines_using_LVM_to_KVM_using_disk_images.html
</guid>
10721 <pubDate>Mon,
22 Nov
2010 11:
20:
00 +
0100</pubDate>
10722 <description><p
>Most of the computers in use by the
10723 <a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux project
</a
>
10724 are virtual machines. And they have been Xen machines running on a
10725 fairly old IBM eserver xseries
345 machine, and we wanted to migrate
10726 them to KVM on a newer Dell PowerEdge
2950 host machine. This was a
10727 bit harder that it could have been, because we set up the Xen virtual
10728 machines to get the virtual partitions from LVM, which as far as I
10729 know is not supported by KVM. So to migrate, we had to convert
10730 several LVM logical volumes to partitions on a virtual disk file.
</p
>
10733 <a href=
"http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
">a
10734 nice recipe
</a
> to do this, and wrote the following script to do the
10735 migration. It uses qemu-img from the qemu package to make the disk
10736 image, parted to partition it, losetup and kpartx to present the disk
10737 image partions as devices, and dd to copy the data. I NFS mounted the
10738 new servers storage area on the old server to do the migration.
</p
>
10744 # http://searchnetworking.techtarget.com.au/articles/
35011-Six-steps-for-migrating-Xen-virtual-machines-to-KVM
10749 if [ -z
"$
1" ] ; then
10750 echo
"Usage: $
0 &lt;hostname
&gt;
"
10753 host=
"$
1"
10756 if [ ! -e /dev/vg_data/$host-disk ] ; then
10757 echo
"error: unable to find LVM volume for $host
"
10761 # Partitions need to be a bit bigger than the LVM LVs. not sure why.
10762 disksize=$( lvs --units m | grep $host-disk | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
10763 swapsize=$( lvs --units m | grep $host-swap | awk
'{sum = sum + $
4} END { print int(sum *
1.05) }
')
10764 totalsize=$(( ( $disksize + $swapsize ) ))
10767 #dd if=/dev/zero of=$img bs=
1M count=$(( $disksize + $swapsize ))
10768 qemu-img create $img ${totalsize}MMaking room on the Debian Edu/Sqeeze DVD
10770 parted $img mklabel msdos
10771 parted $img mkpart primary linux-swap
0 $disksize
10772 parted $img mkpart primary ext2 $disksize $totalsize
10773 parted $img set
1 boot on
10776 losetup /dev/loop0 $img
10777 kpartx -a /dev/loop0
10779 dd if=/dev/vg_data/$host-disk of=/dev/mapper/loop0p1 bs=
1M
10780 fsck.ext3 -f /dev/mapper/loop0p1 || true
10781 mkswap /dev/mapper/loop0p2
10783 kpartx -d /dev/loop0
10784 losetup -d /dev/loop0
10787 <p
>The script is perhaps so simple that it is not copyrightable, but
10788 if it is, it is licenced using GPL v2 or later at your discretion.
</p
>
10790 <p
>After doing this, I booted a Debian CD in rescue mode in KVM with
10791 the new disk image attached, installed grub-pc and linux-image-
686 and
10792 set up grub to boot from the disk image. After this, the KVM machines
10793 seem to work just fine.
</p
>
10798 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome and KDE desktop
</title>
10799 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</link>
10800 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_and_KDE_desktop.html
</guid>
10801 <pubDate>Sat,
20 Nov
2010 22:
50:
00 +
0100</pubDate>
10802 <description><p
>I
'm still running upgrade testing of the
10803 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">Lenny
10804 Gnome and KDE Desktop
</a
>, but have not had time to spend on reporting the
10805 status. Here is a short update based on a test I ran
20101118.
</p
>
10807 <p
>I still do not know what a correct migration should look like, so I
10808 report any differences between apt and aptitude and hope someone else
10809 can see if anything should be changed.
</p
>
10811 <p
>This is for Gnome:
</p
>
10813 <p
>Installed using apt-get, missing with aptitude
</p
>
10815 <blockquote
><p
>
10816 apache2.2-bin aptdaemon at-spi baobab binfmt-support
10817 browser-plugin-gnash cheese-common cli-common cpp-
4.3 cups-pk-helper
10818 dmz-cursor-theme empathy empathy-common finger
10819 freedesktop-sound-theme freeglut3 gconf-defaults-service gdm-themes
10820 gedit-plugins geoclue geoclue-hostip geoclue-localnet geoclue-manual
10821 geoclue-yahoo gnash gnash-common gnome gnome-backgrounds
10822 gnome-cards-data gnome-codec-install gnome-core
10823 gnome-desktop-environment gnome-disk-utility gnome-screenshot
10824 gnome-search-tool gnome-session-canberra gnome-spell
10825 gnome-system-log gnome-themes-extras gnome-themes-more
10826 gnome-user-share gs-common gstreamer0.10-fluendo-mp3
10827 gstreamer0.10-tools gtk2-engines gtk2-engines-pixbuf
10828 gtk2-engines-smooth hal-info hamster-applet libapache2-mod-dnssd
10829 libapr1 libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap
10830 libart2.0-cil libatspi1.0-
0 libboost-date-time1.42
.0
10831 libboost-python1.42
.0 libboost-thread1.42
.0 libchamplain-
0.4-
0
10832 libchamplain-gtk-
0.4-
0 libcheese-gtk18 libclutter-gtk-
0.10-
0
10833 libcryptui0 libcupsys2 libdiscid0 libeel2-data libelf1 libepc-
1.0-
2
10834 libepc-common libepc-ui-
1.0-
2 libfreerdp-plugins-standard
10835 libfreerdp0 libgail-common libgconf2.0-cil libgdata-common libgdata7
10836 libgdl-
1-common libgdu-gtk0 libgee2 libgeoclue0 libgexiv2-
0 libgif4
10837 libglade2.0-cil libglib2.0-cil libgmime2.4-cil libgnome-vfs2.0-cil
10838 libgnome2.24-cil libgnomepanel2.24-cil libgnomeprint2.2-data
10839 libgnomeprintui2.2-common libgnomevfs2-bin libgpod-common libgpod4
10840 libgtk2.0-cil libgtkglext1 libgtksourceview-common
10841 libgtksourceview2.0-common libmono-addins-gui0.2-cil
10842 libmono-addins0.2-cil libmono-cairo2.0-cil libmono-corlib2.0-cil
10843 libmono-i18n-west2.0-cil libmono-posix2.0-cil
10844 libmono-security2.0-cil libmono-sharpzip2.84-cil
10845 libmono-system2.0-cil libmtp8 libmusicbrainz3-
6
10846 libndesk-dbus-glib1.0-cil libndesk-dbus1.0-cil libopal3.6
.8
10847 libpolkit-gtk-
1-
0 libpt-
1.10.10-plugins-alsa
10848 libpt-
1.10.10-plugins-v4l libpt2.6
.7 libpython2.6 librpm1 librpmio1
10849 libsdl1.2debian libservlet2.4-java libsrtp0 libssh-
4
10850 libtelepathy-farsight0 libtelepathy-glib0 libtidy-
0.99-
0
10851 libxalan2-java libxerces2-java media-player-info mesa-utils
10852 mono-
2.0-gac mono-gac mono-runtime nautilus-sendto
10853 nautilus-sendto-empathy openoffice.org-writer2latex
10854 openssl-blacklist p7zip p7zip-full pkg-config python-
4suite-xml
10855 python-aptdaemon python-aptdaemon-gtk python-axiom
10856 python-beautifulsoup python-bugbuddy python-clientform
10857 python-coherence python-configobj python-crypto python-cupshelpers
10858 python-cupsutils python-eggtrayicon python-elementtree
10859 python-epsilon python-evolution python-feedparser python-gdata
10860 python-gdbm python-gst0.10 python-gtkglext1 python-gtkmozembed
10861 python-gtksourceview2 python-httplib2 python-louie python-mako
10862 python-markupsafe python-mechanize python-nevow python-notify
10863 python-opengl python-openssl python-pam python-pkg-resources
10864 python-pyasn1 python-pysqlite2 python-rdflib python-serial
10865 python-tagpy python-twisted-bin python-twisted-conch
10866 python-twisted-core python-twisted-web python-utidylib python-webkit
10867 python-xdg python-zope.interface remmina remmina-plugin-data
10868 remmina-plugin-rdp remmina-plugin-vnc rhythmbox-plugin-cdrecorder
10869 rhythmbox-plugins rpm-common rpm2cpio seahorse-plugins shotwell
10870 software-center svgalibg1 system-config-printer-udev
10871 telepathy-gabble telepathy-mission-control-
5 telepathy-salut tomboy
10872 totem totem-coherence totem-mozilla totem-plugins
10873 transmission-common xdg-user-dirs xdg-user-dirs-gtk xserver-xephyr
10875 </p
></blockquote
>
10877 Installed using apt-get, removed with aptitude
10879 <blockquote
><p
>
10880 arj bluez-utils cheese dhcdbd djvulibre-desktop ekiga eog
10881 epiphany-extensions epiphany-gecko evolution-exchange
10882 fast-user-switch-applet file-roller gcalctool gconf-editor gdm gedit
10883 gedit-common gnome-app-install gnome-games gnome-games-data
10884 gnome-nettool gnome-system-tools gnome-themes gnome-utils
10885 gnome-vfs-obexftp gnome-volume-manager gnuchess gucharmap
10886 guile-
1.8-libs hal libavahi-compat-libdnssd1 libavahi-core5
10887 libavahi-ui0 libbind9-
50 libbluetooth2 libcamel1.2-
11 libcdio7
10888 libcucul0 libcurl3 libdirectfb-
1.0-
0 libdmx1 libdvdread3
10889 libedata-cal1.2-
6 libedataserver1.2-
9 libeel2-
2.20 libepc-
1.0-
1
10890 libepc-ui-
1.0-
1 libexchange-storage1.2-
3 libfaad0 libgadu3
10891 libgalago3 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
10892 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
10893 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
10894 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtk-vnc-
1.0-
0
10895 libgtkhtml2-
0 libgtksourceview1.0-
0 libgtksourceview2.0-
0
10896 libgucharmap6 libhesiod0 libicu38 libisccc50 libisccfg50 libiw29
10897 libjaxp1.3-java-gcj libkpathsea4 liblircclient0 libltdl3 liblwres50
10898 libmagick++
10 libmagick10 libmalaga7 libmozjs1d libmpfr1ldbl libmtp7
10899 libmysqlclient15off libnautilus-burn4 libneon27 libnm-glib0
10900 libnm-util0 libopal-
2.2 libosp5 libparted1.8-
10 libpisock9
10901 libpisync1 libpoppler-glib3 libpoppler3 libpt-
1.10.10 libraw1394-
8
10902 libsdl1.2debian-alsa libsensors3 libsexy2 libsmbios2 libsoup2.2-
8
10903 libspeexdsp1 libssh2-
1 libsuitesparse-
3.1.0 libsvga1
10904 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10 libtrackerclient0
10905 libvoikko1 libxalan2-java-gcj libxerces2-java-gcj libxklavier12
10906 libxtrap6 libxxf86misc1 libzephyr3 mysql-common rhythmbox seahorse
10907 sound-juicer swfdec-gnome system-config-printer totem-common
10908 totem-gstreamer transmission-gtk vinagre vino w3c-dtd-xhtml wodim
10909 </p
></blockquote
>
10911 <p
>Installed using aptitude, missing with apt-get
</p
>
10913 <blockquote
><p
>
10914 gstreamer0.10-gnomevfs
10915 </p
></blockquote
>
10917 <p
>Installed using aptitude, removed with apt-get
</p
>
10919 <blockquote
><p
>
10921 </p
></blockquote
>
10923 <p
>This is for KDE:
</p
>
10925 <p
>Installed using apt-get, missing with aptitude
</p
>
10927 <blockquote
><p
>
10928 autopoint bomber bovo cantor cantor-backend-kalgebra cpp-
4.3 dcoprss
10929 edict espeak espeak-data eyesapplet fifteenapplet finger gettext
10930 ghostscript-x git gnome-audio gnugo granatier gs-common
10931 gstreamer0.10-pulseaudio indi kaddressbook-plugins kalgebra
10932 kalzium-data kanjidic kapman kate-plugins kblocks kbreakout kbstate
10933 kde-icons-mono kdeaccessibility kdeaddons-kfile-plugins
10934 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
10935 kdeedu kdeedu-data kdeedu-kvtml-data kdegames kdegames-card-data
10936 kdegames-mahjongg-data kdegraphics-kfile-plugins kdelirc
10937 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
10938 kdepim-kfile-plugins kdepim-kio-plugins kdessh kdetoys kdewebdev
10939 kdiamond kdnssd kfilereplace kfourinline kgeography-data kigo
10940 killbots kiriki klettres-data kmoon kmrml knewsticker-scripts
10941 kollision kpf krosspython ksirk ksmserver ksquares kstars-data
10942 ksudoku kubrick kweather libasound2-plugins libboost-python1.42
.0
10943 libcfitsio3 libconvert-binhex-perl libcrypt-ssleay-perl libdb4.6++
10944 libdjvulibre-text libdotconf1.0 liberror-perl libespeak1
10945 libfinance-quote-perl libgail-common libgsl0ldbl libhtml-parser-perl
10946 libhtml-tableextract-perl libhtml-tagset-perl libhtml-tree-perl
10947 libio-stringy-perl libkdeedu4 libkdegames5 libkiten4 libkpathsea5
10948 libkrossui4 libmailtools-perl libmime-tools-perl
10949 libnews-nntpclient-perl libopenbabel3 libportaudio2 libpulse-browse0
10950 libservlet2.4-java libspeechd2 libtiff-tools libtimedate-perl
10951 libunistring0 liburi-perl libwww-perl libxalan2-java libxerces2-java
10952 lirc luatex marble networkstatus noatun-plugins
10953 openoffice.org-writer2latex palapeli palapeli-data parley
10954 parley-data poster psutils pulseaudio pulseaudio-esound-compat
10955 pulseaudio-module-x11 pulseaudio-utils quanta-data rocs rsync
10956 speech-dispatcher step svgalibg1 texlive-binaries texlive-luatex
10957 ttf-sazanami-gothic
10958 </p
></blockquote
>
10960 <p
>Installed using apt-get, removed with aptitude
</p
>
10962 <blockquote
><p
>
10963 amor artsbuilder atlantik atlantikdesigner blinken bluez-utils cvs
10964 dhcdbd djvulibre-desktop imlib-base imlib11 kalzium kanagram kandy
10965 kasteroids katomic kbackgammon kbattleship kblackbox kbounce kbruch
10966 kcron kdat kdemultimedia-kappfinder-data kdeprint kdict kdvi kedit
10967 keduca kenolaba kfax kfaxview kfouleggs kgeography kghostview
10968 kgoldrunner khangman khexedit kiconedit kig kimagemapeditor
10969 kitchensync kiten kjumpingcube klatin klettres klickety klines
10970 klinkstatus kmag kmahjongg kmailcvt kmenuedit kmid kmilo kmines
10971 kmousetool kmouth kmplot knetwalk kodo kolf kommander konquest kooka
10972 kpager kpat kpdf kpercentage kpilot kpoker kpovmodeler krec
10973 kregexpeditor kreversi ksame ksayit kshisen ksig ksim ksirc ksirtet
10974 ksmiletris ksnake ksokoban kspaceduel kstars ksvg ksysv kteatime
10975 ktip ktnef ktouch ktron kttsd ktuberling kturtle ktux kuickshow
10976 kverbos kview kviewshell kvoctrain kwifimanager kwin kwin4 kwordquiz
10977 kworldclock kxsldbg libakode2 libarts1-akode libarts1-audiofile
10978 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
10979 libavahi-core5 libavc1394-
0 libbind9-
50 libbluetooth2
10980 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0
10981 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
10982 libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0 libicu38
10983 libiec61883-
0 libindex0 libisccc50 libisccfg50 libiw29
10984 libjaxp1.3-java-gcj libk3b3 libkcal2b libkcddb1 libkdeedu3
10985 libkdegames1 libkdepim1a libkgantt0 libkleopatra1 libkmime2
10986 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
10987 libksieve0 libktnef1 liblockdev1 libltdl3 liblwres50 libmagick10
10988 libmimelib1c2a libmodplug0c2 libmozjs1d libmpcdec3 libmpfr1ldbl
10989 libneon27 libnm-util0 libopensync0 libpisock9 libpoppler-glib3
10990 libpoppler-qt2 libpoppler3 libraw1394-
8 librss1 libsensors3
10991 libsmbios2 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90
10992 libtalloc1 libxalan2-java-gcj libxerces2-java-gcj libxtrap6 lskat
10993 mpeglib network-manager-kde noatun pmount tex-common texlive-base
10994 texlive-common texlive-doc-base texlive-fonts-recommended tidy
10995 ttf-dustin ttf-kochi-gothic ttf-sjfonts
10996 </p
></blockquote
>
10998 <p
>Installed using aptitude, missing with apt-get
</p
>
11000 <blockquote
><p
>
11001 dolphin kde-core kde-plasma-desktop kde-standard kde-window-manager
11002 kdeartwork kdebase kdebase-apps kdebase-workspace
11003 kdebase-workspace-bin kdebase-workspace-data kdeutils kscreensaver
11004 kscreensaver-xsavers libgle3 libkonq5 libkonq5-templates libnetpbm10
11005 netpbm plasma-widget-folderview plasma-widget-networkmanagement
11006 xscreensaver-data-extra xscreensaver-gl xscreensaver-gl-extra
11007 xscreensaver-screensaver-bsod
11008 </p
></blockquote
>
11010 <p
>Installed using aptitude, removed with apt-get
</p
>
11012 <blockquote
><p
>
11013 kdebase-bin konq-plugins konqueror
11014 </p
></blockquote
>
11019 <title>Gnash buildbot slave and Debian kfreebsd
</title>
11020 <link>https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</link>
11021 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Gnash_buildbot_slave_and_Debian_kfreebsd.html
</guid>
11022 <pubDate>Sat,
20 Nov
2010 07:
20:
00 +
0100</pubDate>
11023 <description><p
>Answering
11024 <a href=
"http://www.listware.net/
201011/gnash-dev/
67431-gnash-dev-buildbot-looking-for-slaves.html
">the
11025 call from the Gnash project
</a
> for
11026 <a href=
"http://www.gnashdev.org:
8010">buildbot
</a
> slaves to test the
11027 current source, I have set up a virtual KVM machine on the Debian
11028 Edu/Skolelinux virtualization host to test the git source on
11029 Debian/Squeeze. I hope this can help the developers in getting new
11030 releases out more often.
</p
>
11032 <p
>As the developers want less main-stream build platforms tested to,
11033 I have considered setting up a
<a
11034 href=
"http://www.debian.org/ports/kfreebsd-gnu/
">Debian/kfreebsd
</a
>
11035 machine as well. I have also considered using the kfreebsd
11036 architecture in Debian as a file server in NUUG to get access to the
5
11037 TB zfs volume we currently use to store DV video. Because of this, I
11038 finally got around to do a test installation of Debian/Squeeze with
11039 kfreebsd. Installation went fairly smooth, thought I noticed some
11040 visual glitches in the cdebconf dialogs (black cursor left on the
11041 screen at random locations). Have not gotten very far with the
11042 testing. Noticed cfdisk did not work, but fdisk did so it was not a
11043 fatal problem. Have to spend some more time on it to see if it is
11044 useful as a file server for NUUG. Will try to find time to set up a
11045 gnash buildbot slave on the Debian Edu/Skolelinux this weekend.
</p
>
11050 <title>Debian in
3D
</title>
11051 <link>https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</link>
11052 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_in_3D.html
</guid>
11053 <pubDate>Tue,
9 Nov
2010 16:
10:
00 +
0100</pubDate>
11054 <description><p
><img src=
"http://thingiverse-production.s3.amazonaws.com/renders/
23/e0/c4/f9/
2b/debswagtdose_preview_medium.jpg
"></p
>
11056 <p
>3D printing is just great. I just came across this Debian logo in
11058 <a href=
"http://blog.thingiverse.com/
2010/
11/
09/participatory-branding/
">the
11059 thingiverse blog
</a
>.
</p
>
11064 <title>Software updates
2010-
10-
24</title>
11065 <link>https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</link>
11066 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Software_updates_2010_10_24.html
</guid>
11067 <pubDate>Sun,
24 Oct
2010 22:
45:
00 +
0200</pubDate>
11068 <description><p
>Some updates.
</p
>
11070 <p
>My
<a href=
"http://pledgebank.com/gnash-avm2
">gnash pledge
</a
> to
11071 raise money for the project is going well. The lower limit of
10
11072 signers was reached in
24 hours, and so far
13 people have signed it.
11073 More signers and more funding is most welcome, and I am really curious
11074 how far we can get before the time limit of December
24 is reached.
11077 <p
>On the #gnash IRC channel on irc.freenode.net, I was just tipped
11078 about what appear to be a great code coverage tool capable of
11079 generating code coverage stats without any changes to the source code.
11081 <a href=
"http://simonkagstrom.github.com/kcov/index.html
">kcov
</a
>,
11082 and can be used using
<tt
>kcov
&lt;directory
&gt;
&lt;binary
&gt;
</tt
>.
11083 It is missing in Debian, but the git source built just fine in Squeeze
11084 after I installed libelf-dev, libdwarf-dev, pkg-config and
11085 libglib2.0-dev. Failed to build in Lenny, but suspect that is
11086 solvable. I hope kcov make it into Debian soon.
</p
>
11088 <p
>Finally found time to wrap up the release notes for
<a
11089 href=
"http://lists.debian.org/debian-edu-announce/
2010/
10/msg00002.html
">a
11090 new alpha release of Debian Edu
</a
>, and just published the second
11091 alpha test release of the Squeeze based Debian Edu /
11092 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
>
11093 release. Give it a try if you need a complete linux solution for your
11094 school, including central infrastructure server, workstations, thin
11095 client servers and diskless workstations. A nice touch added
11096 yesterday is RDP support on the thin client servers, for windows
11097 clients to get a Linux desktop on request.
</p
>
11102 <title>Some notes on Flash in Debian and Debian Edu
</title>
11103 <link>https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</link>
11104 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Some_notes_on_Flash_in_Debian_and_Debian_Edu.html
</guid>
11105 <pubDate>Sat,
4 Sep
2010 10:
10:
00 +
0200</pubDate>
11106 <description><p
>In the
<a href=
"http://popcon.debian.org/unknown/by_vote
">Debian
11107 popularity-contest numbers
</a
>, the adobe-flashplugin package the
11108 second most popular used package that is missing in Debian. The sixth
11109 most popular is flashplayer-mozilla. This is a clear indication that
11110 working flash is important for Debian users. Around
10 percent of the
11111 users submitting data to popcon.debian.org have this package
11112 installed.
</p
>
11114 <p
>In the report written by Lars Risan in August
2008
11115 («
<a href=
"http://wiki.skolelinux.no/Dokumentasjon/Rapporter?action=AttachFile
&do=view
&target=Skolelinux_i_bruk_rapport_1.0.pdf
">Skolelinux
11116 i bruk – Rapport for Hurum kommune, Universitetet i Agder og
11117 stiftelsen SLX Debian Labs
</a
>»), one of the most important problems
11118 schools experienced with
<a href=
"http://www.skolelinux.org/
">Debian
11119 Edu/Skolelinux
</a
> was the lack of working Flash. A lot of educational
11120 web sites require Flash to work, and lacking working Flash support in
11121 the web browser and the problems with installing it was perceived as a
11122 good reason to stay with Windows.
</p
>
11124 <p
>I once saw a funny and sad comment in a web forum, where Linux was
11125 said to be the retarded cousin that did not really understand
11126 everything you told him but could work fairly well. This was a
11127 comment regarding the problems Linux have with proprietary formats and
11128 non-standard web pages, and is sad because it exposes a fairly common
11129 understanding of whose fault it is if web pages that only work in for
11130 example Internet Explorer
6 fail to work on Firefox, and funny because
11131 it explain very well how annoying it is for users when Linux
11132 distributions do not work with the documents they receive or the web
11133 pages they want to visit.
</p
>
11135 <p
>This is part of the reason why I believe it is important for Debian
11136 and Debian Edu to have a well working Flash implementation in the
11137 distribution, to get at least popular sites as Youtube and Google
11138 Video to working out of the box. For Squeeze, Debian have the chance
11139 to include the latest version of Gnash that will make this happen, as
11140 the new release
0.8.8 was published a few weeks ago and is resting in
11141 unstable. The new version work with more sites that version
0.8.7.
11142 The Gnash maintainers have asked for a freeze exception, but the
11143 release team have not had time to reply to it yet. I hope they agree
11144 with me that Flash is important for the Debian desktop users, and thus
11145 accept the new package into Squeeze.
</p
>
11150 <title>Circular package dependencies harms apt recovery
</title>
11151 <link>https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</link>
11152 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Circular_package_dependencies_harms_apt_recovery.html
</guid>
11153 <pubDate>Tue,
27 Jul
2010 23:
50:
00 +
0200</pubDate>
11154 <description><p
>I discovered this while doing
11155 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">automated
11156 testing of upgrades from Debian Lenny to Squeeze
</a
>. A few packages
11157 in Debian still got circular dependencies, and it is often claimed
11158 that apt and aptitude should be able to handle this just fine, but
11159 some times these dependency loops causes apt to fail.
</p
>
11161 <p
>An example is from todays
11162 <a href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing//test-
20100727-lenny-squeeze-kde-aptitude.txt
">upgrade
11163 of KDE using aptitude
</a
>. In it, a bug in kdebase-workspace-data
11164 causes perl-modules to fail to upgrade. The cause is simple. If a
11165 package fail to unpack, then only part of packages with the circular
11166 dependency might end up being unpacked when unpacking aborts, and the
11167 ones already unpacked will fail to configure in the recovery phase
11168 because its dependencies are unavailable.
</p
>
11170 <p
>In this log, the problem manifest itself with this error:
</p
>
11172 <blockquote
><pre
>
11173 dpkg: dependency problems prevent configuration of perl-modules:
11174 perl-modules depends on perl (
>=
5.10.1-
1); however:
11175 Version of perl on system is
5.10.0-
19lenny
2.
11176 dpkg: error processing perl-modules (--configure):
11177 dependency problems - leaving unconfigured
11178 </pre
></blockquote
>
11180 <p
>The perl/perl-modules circular dependency is already
11181 <a href=
"http://bugs.debian.org/
527917">reported as a bug
</a
>, and will
11182 hopefully be solved as soon as possible, but it is not the only one,
11183 and each one of these loops in the dependency tree can cause similar
11184 failures. Of course, they only occur when there are bugs in other
11185 packages causing the unpacking to fail, but it is rather nasty when
11186 the failure of one package causes the problem to become worse because
11187 of dependency loops.
</p
>
11190 <a href=
"http://lists.debian.org/debian-devel/
2010/
06/msg00116.html
">the
11191 tireless effort by Bill Allombert
</a
>, the number of circular
11193 <a href=
"http://debian.semistable.com/debgraph.out.html
">left in Debian
11194 is dropping
</a
>, and perhaps it will reach zero one day. :)
</p
>
11196 <p
>Todays testing also exposed a bug in
11197 <a href=
"http://bugs.debian.org/
590605">update-notifier
</a
> and
11198 <a href=
"http://bugs.debian.org/
590604">different behaviour
</a
> between
11199 apt-get and aptitude, the latter possibly caused by some circular
11200 dependency. Reported both to BTS to try to get someone to look at
11206 <title>What are they searching for - PowerDNS and ISC DHCP in LDAP
</title>
11207 <link>https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</link>
11208 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/What_are_they_searching_for___PowerDNS_and_ISC_DHCP_in_LDAP.html
</guid>
11209 <pubDate>Sat,
17 Jul
2010 21:
00:
00 +
0200</pubDate>
11210 <description><p
>This is a
11211 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">followup
</a
>
11213 <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
11215 <a href=
"http://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
">merging
11216 all
</a
> the computer related LDAP objects in Debian Edu.
</p
>
11218 <p
>As a step to try to see if it possible to merge the DNS and DHCP
11219 LDAP objects, I have had a look at how the packages pdns-backend-ldap
11220 and dhcp3-server-ldap in Debian use the LDAP server. The two
11221 implementations are quite different in how they use LDAP.
</p
>
11223 To get this information, I started slapd with debugging enabled and
11224 dumped the debug output to a file to get the LDAP searches performed
11225 on a Debian Edu main-server. Here is a summary.
11227 <p
><strong
>powerdns
</strong
></p
>
11229 <a href=
"http://www.linuxnetworks.de/doc/index.php/PowerDNS_LDAP_Backend
">Clues
11230 on how to
</a
> set up PowerDNS to use a LDAP backend is available on
11233 <p
>PowerDNS have two modes of operation using LDAP as its backend.
11234 One
"strict
" mode where the forward and reverse DNS lookups are done
11235 using the same LDAP objects, and a
"tree
" mode where the forward and
11236 reverse entries are in two different subtrees in LDAP with a structure
11237 based on the DNS names, as in tjener.intern and
11238 2.2.0.10.in-addr.arpa.
</p
>
11240 <p
>In tree mode, the server is set up to use a LDAP subtree as its
11241 base, and uses a
"base
" scoped search for the DNS name by adding
11242 "dc=tjener,dc=intern,
" to the base with a filter for
11243 "(associateddomain=tjener.intern)
" for the forward entry and
11244 "dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,
" with a filter for
11245 "(associateddomain=
2.2.0.10.in-addr.arpa)
" for the reverse entry. For
11246 forward entries, it is looking for attributes named dnsttl, arecord,
11247 nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord, mxrecord,
11248 txtrecord, rprecord, afsdbrecord, keyrecord, aaaarecord, locrecord,
11249 srvrecord, naptrrecord, kxrecord, certrecord, dsrecord, sshfprecord,
11250 ipseckeyrecord, rrsigrecord, nsecrecord, dnskeyrecord, dhcidrecord,
11251 spfrecord and modifytimestamp. For reverse entries it is looking for
11252 the attributes dnsttl, arecord, nsrecord, cnamerecord, soarecord,
11253 ptrrecord, hinforecord, mxrecord, txtrecord, rprecord, aaaarecord,
11254 locrecord, srvrecord, naptrrecord and modifytimestamp. The equivalent
11255 ldapsearch commands could look like this:
</p
>
11257 <blockquote
><pre
>
11258 ldapsearch -h ldap \
11259 -b dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11260 -s base -x
'(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
11261 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11262 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11263 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11264 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11266 ldapsearch -h ldap \
11267 -b dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no \
11268 -s base -x
'(associateddomain=
2.2.0.10.in-addr.arpa)
'
11269 dnsttl, arecord, nsrecord, cnamerecord soarecord ptrrecord \
11270 hinforecord mxrecord txtrecord rprecord aaaarecord locrecord \
11271 srvrecord naptrrecord modifytimestamp
11272 </pre
></blockquote
>
11274 <p
>In Debian Edu/Lenny, the PowerDNS tree mode is used with
11275 ou=hosts,dc=skole,dc=skolelinux,dc=no as the base, and these are two
11276 example LDAP objects used there. In addition to these objects, the
11277 parent objects all th way up to ou=hosts,dc=skole,dc=skolelinux,dc=no
11278 also exist.
</p
>
11280 <blockquote
><pre
>
11281 dn: dc=tjener,dc=intern,ou=hosts,dc=skole,dc=skolelinux,dc=no
11283 objectclass: dnsdomain
11284 objectclass: domainrelatedobject
11287 associateddomain: tjener.intern
11289 dn: dc=
2,dc=
2,dc=
0,dc=
10,dc=in-addr,dc=arpa,ou=hosts,dc=skole,dc=skolelinux,dc=no
11291 objectclass: dnsdomain2
11292 objectclass: domainrelatedobject
11294 ptrrecord: tjener.intern
11295 associateddomain:
2.2.0.10.in-addr.arpa
11296 </pre
></blockquote
>
11298 <p
>In strict mode, the server behaves differently. When looking for
11299 forward DNS entries, it is doing a
"subtree
" scoped search with the
11300 same base as in the tree mode for a object with filter
11301 "(associateddomain=tjener.intern)
" and requests the attributes dnsttl,
11302 arecord, nsrecord, cnamerecord, soarecord, ptrrecord, hinforecord,
11303 mxrecord, txtrecord, rprecord, aaaarecord, locrecord, srvrecord,
11304 naptrrecord and modifytimestamp. For reverse entires it also do a
11305 subtree scoped search but this time the filter is
"(arecord=
10.0.2.2)
"
11306 and the requested attributes are associateddomain, dnsttl and
11307 modifytimestamp. In short, in strict mode the objects with ptrrecord
11308 go away, and the arecord attribute in the forward object is used
11311 <p
>The forward and reverse searches can be simulated using ldapsearch
11312 like this:
</p
>
11314 <blockquote
><pre
>
11315 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11316 '(associateddomain=tjener.intern)
' dNSTTL aRecord nSRecord \
11317 cNAMERecord sOARecord pTRRecord hInfoRecord mXRecord tXTRecord \
11318 rPRecord aFSDBRecord KeyRecord aAAARecord lOCRecord sRVRecord \
11319 nAPTRRecord kXRecord certRecord dSRecord sSHFPRecord iPSecKeyRecord \
11320 rRSIGRecord nSECRecord dNSKeyRecord dHCIDRecord sPFRecord modifyTimestamp
11322 ldapsearch -h ldap -b ou=hosts,dc=skole,dc=skolelinux,dc=no -s sub -x \
11323 '(arecord=
10.0.2.2)
' associateddomain dnsttl modifytimestamp
11324 </pre
></blockquote
>
11326 <p
>In addition to the forward and reverse searches , there is also a
11327 search for SOA records, which behave similar to the forward and
11328 reverse lookups.
</p
>
11330 <p
>A thing to note with the PowerDNS behaviour is that it do not
11331 specify any objectclass names, and instead look for the attributes it
11332 need to generate a DNS reply. This make it able to work with any
11333 objectclass that provide the needed attributes.
</p
>
11335 <p
>The attributes are normally provided in the cosine (RFC
1274) and
11336 dnsdomain2 schemas. The latter is used for reverse entries like
11337 ptrrecord and recent DNS additions like aaaarecord and srvrecord.
</p
>
11339 <p
>In Debian Edu, we have created DNS objects using the object classes
11340 dcobject (for dc), dnsdomain or dnsdomain2 (structural, for the DNS
11341 attributes) and domainrelatedobject (for associatedDomain). The use
11342 of structural object classes make it impossible to combine these
11343 classes with the object classes used by DHCP.
</p
>
11345 <p
>There are other schemas that could be used too, for example the
11346 dnszone structural object class used by Gosa and bind-sdb for the DNS
11347 attributes combined with the domainrelatedobject object class, but in
11348 this case some unused attributes would have to be included as well
11349 (zonename and relativedomainname).
</p
>
11351 <p
>My proposal for Debian Edu would be to switch PowerDNS to strict
11352 mode and not use any of the existing objectclasses (dnsdomain,
11353 dnsdomain2 and dnszone) when one want to combine the DNS information
11354 with DHCP information, and instead create a auxiliary object class
11355 defined something like this (using the attributes defined for
11356 dnsdomain and dnsdomain2 or dnszone):
</p
>
11358 <blockquote
><pre
>
11359 objectclass ( some-oid NAME
'dnsDomainAux
'
11362 MAY ( ARecord $ MDRecord $ MXRecord $ NSRecord $ SOARecord $ CNAMERecord $
11363 DNSTTL $ DNSClass $ PTRRecord $ HINFORecord $ MINFORecord $
11364 TXTRecord $ SIGRecord $ KEYRecord $ AAAARecord $ LOCRecord $
11365 NXTRecord $ SRVRecord $ NAPTRRecord $ KXRecord $ CERTRecord $
11366 A6Record $ DNAMERecord
11368 </pre
></blockquote
>
11370 <p
>This will allow any object to become a DNS entry when combined with
11371 the domainrelatedobject object class, and allow any entity to include
11372 all the attributes PowerDNS wants. I
've sent an email to the PowerDNS
11373 developers asking for their view on this schema and if they are
11374 interested in providing such schema with PowerDNS, and I hope my
11375 message will be accepted into their mailing list soon.
</p
>
11377 <p
><strong
>ISC dhcp
</strong
></p
>
11379 <p
>The DHCP server searches for specific objectclass and requests all
11380 the object attributes, and then uses the attributes it want. This
11381 make it harder to figure out exactly what attributes are used, but
11382 thanks to the working example in Debian Edu I can at least get an idea
11383 what is needed without having to read the source code.
</p
>
11385 <p
>In the DHCP server configuration, the LDAP base to use and the
11386 search filter to use to locate the correct dhcpServer entity is
11387 stored. These are the relevant entries from
11388 /etc/dhcp3/dhcpd.conf:
</p
>
11390 <blockquote
><pre
>
11391 ldap-base-dn
"dc=skole,dc=skolelinux,dc=no
";
11392 ldap-dhcp-server-cn
"dhcp
";
11393 </pre
></blockquote
>
11395 <p
>The DHCP server uses this information to nest all the DHCP
11396 configuration it need. The cn
"dhcp
" is located using the given LDAP
11397 base and the filter
"(
&(objectClass=dhcpServer)(cn=dhcp))
". The
11398 search result is this entry:
</p
>
11400 <blockquote
><pre
>
11401 dn: cn=dhcp,dc=skole,dc=skolelinux,dc=no
11404 objectClass: dhcpServer
11405 dhcpServiceDN: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11406 </pre
></blockquote
>
11408 <p
>The content of the dhcpServiceDN attribute is next used to locate the
11409 subtree with DHCP configuration. The DHCP configuration subtree base
11410 is located using a base scope search with base
"cn=DHCP
11411 Config,dc=skole,dc=skolelinux,dc=no
" and filter
11412 "(
&(objectClass=dhcpService)(|(dhcpPrimaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)(dhcpSecondaryDN=cn=dhcp,dc=skole,dc=skolelinux,dc=no)))
".
11413 The search result is this entry:
</p
>
11415 <blockquote
><pre
>
11416 dn: cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11419 objectClass: dhcpService
11420 objectClass: dhcpOptions
11421 dhcpPrimaryDN: cn=dhcp, dc=skole,dc=skolelinux,dc=no
11422 dhcpStatements: ddns-update-style none
11423 dhcpStatements: authoritative
11424 dhcpOption: smtp-server code
69 = array of ip-address
11425 dhcpOption: www-server code
72 = array of ip-address
11426 dhcpOption: wpad-url code
252 = text
11427 </pre
></blockquote
>
11429 <p
>Next, the entire subtree is processed, one level at the time. When
11430 all the DHCP configuration is loaded, it is ready to receive requests.
11431 The subtree in Debian Edu contain objects with object classes
11432 top/dhcpService/dhcpOptions, top/dhcpSharedNetwork/dhcpOptions,
11433 top/dhcpSubnet, top/dhcpGroup and top/dhcpHost. These provide options
11434 and information about netmasks, dynamic range etc. Leaving out the
11435 details here because it is not relevant for the focus of my
11436 investigation, which is to see if it is possible to merge dns and dhcp
11437 related computer objects.
</p
>
11439 <p
>When a DHCP request come in, LDAP is searched for the MAC address
11440 of the client (
00:
00:
00:
00:
00:
00 in this example), using a subtree
11441 scoped search with
"cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
" as
11442 the base and
"(
&(objectClass=dhcpHost)(dhcpHWAddress=ethernet
11443 00:
00:
00:
00:
00:
00))
" as the filter. This is what a host object look
11446 <blockquote
><pre
>
11447 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11450 objectClass: dhcpHost
11451 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11452 dhcpStatements: fixed-address hostname
11453 </pre
></blockquote
>
11455 <p
>There is less flexiblity in the way LDAP searches are done here.
11456 The object classes need to have fixed names, and the configuration
11457 need to be stored in a fairly specific LDAP structure. On the
11458 positive side, the invidiual dhcpHost entires can be anywhere without
11459 the DN pointed to by the dhcpServer entries. The latter should make
11460 it possible to group all host entries in a subtree next to the
11461 configuration entries, and this subtree can also be shared with the
11462 DNS server if the schema proposed above is combined with the dhcpHost
11463 structural object class.
11465 <p
><strong
>Conclusion
</strong
></p
>
11467 <p
>The PowerDNS implementation seem to be very flexible when it come
11468 to which LDAP schemas to use. While its
"tree
" mode is rigid when it
11469 come to the the LDAP structure, the
"strict
" mode is very flexible,
11470 allowing DNS objects to be stored anywhere under the base cn specified
11471 in the configuration.
</p
>
11473 <p
>The DHCP implementation on the other hand is very inflexible, both
11474 regarding which LDAP schemas to use and which LDAP structure to use.
11475 I guess one could implement ones own schema, as long as the
11476 objectclasses and attributes have the names used, but this do not
11477 really help when the DHCP subtree need to have a fairly fixed
11478 structure.
</p
>
11480 <p
>Based on the observed behaviour, I suspect a LDAP structure like
11481 this might work for Debian Edu:
</p
>
11483 <blockquote
><pre
>
11485 cn=machine-info (dhcpService) - dhcpServiceDN points here
11486 cn=dhcp (dhcpServer)
11487 cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
11488 cn=
10.0.2.0 (dhcpSubnet)
11489 cn=group1 (dhcpGroup/dhcpOptions)
11490 cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
11491 cn=
192.168.0.0 (dhcpSubnet)
11492 cn=group1 (dhcpGroup/dhcpOptions)
11493 ou=machines - PowerDNS base points here
11494 cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
11495 </pre
></blockquote
>
11497 <P
>This is not tested yet. If the DHCP server require the dhcpHost
11498 entries to be in the dhcpGroup subtrees, the entries can be stored
11499 there instead of a common machines subtree, and the PowerDNS base
11500 would have to be moved one level up to the machine-info subtree.
</p
>
11502 <p
>The combined object under the machines subtree would look something
11503 like this:
</p
>
11505 <blockquote
><pre
>
11506 dn: dc=hostname,ou=machines,cn=machine-info,dc=skole,dc=skolelinux,dc=no
11509 objectClass: dhcpHost
11510 objectclass: domainrelatedobject
11511 objectclass: dnsDomainAux
11512 associateddomain: hostname.intern
11513 arecord:
10.11.12.13
11514 dhcpHWAddress: ethernet
00:
00:
00:
00:
00:
00
11515 dhcpStatements: fixed-address hostname.intern
11516 </pre
></blockquote
>
11518 </p
>One could even add the LTSP configuration associated with a given
11519 machine, as long as the required attributes are available in a
11520 auxiliary object class.
</p
>
11525 <title>Combining PowerDNS and ISC DHCP LDAP objects
</title>
11526 <link>https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</link>
11527 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Combining_PowerDNS_and_ISC_DHCP_LDAP_objects.html
</guid>
11528 <pubDate>Wed,
14 Jul
2010 23:
45:
00 +
0200</pubDate>
11529 <description><p
>For a while now, I have wanted to find a way to change the DNS and
11530 DHCP services in Debian Edu to use the same LDAP objects for a given
11531 computer, to avoid the possibility of having a inconsistent state for
11532 a computer in LDAP (as in DHCP but no DNS entry or the other way
11533 around) and make it easier to add computers to LDAP.
</p
>
11535 <p
>I
've looked at how powerdns and dhcpd is using LDAP, and using this
11536 information finally found a solution that seem to work.
</p
>
11538 <p
>The old setup required three LDAP objects for a given computer.
11539 One forward DNS entry, one reverse DNS entry and one DHCP entry. If
11540 we switch powerdns to use its strict LDAP method (ldap-method=strict
11541 in pdns-debian-edu.conf), the forward and reverse DNS entries are
11542 merged into one while making it impossible to transfer the reverse map
11543 to a slave DNS server.
</p
>
11545 <p
>If we also replace the object class used to get the DNS related
11546 attributes to one allowing these attributes to be combined with the
11547 dhcphost object class, we can merge the DNS and DHCP entries into one.
11548 I
've written such object class in the dnsdomainaux.schema file (need
11549 proper OIDs, but that is a minor issue), and tested the setup. It
11550 seem to work.
</p
>
11552 <p
>With this test setup in place, we can get away with one LDAP object
11553 for both DNS and DHCP, and even the LTSP configuration I suggested in
11554 an earlier email. The combined LDAP object will look something like
11557 <blockquote
><pre
>
11558 dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
11560 objectClass: dhcphost
11561 objectclass: domainrelatedobject
11562 objectclass: dnsdomainaux
11563 associateddomain: hostname.intern
11564 arecord:
10.11.12.13
11565 dhcphwaddress: ethernet
00:
00:
00:
00:
00:
00
11566 dhcpstatements: fixed-address hostname
11568 </pre
></blockquote
>
11570 <p
>The DNS server uses the associateddomain and arecord entries, while
11571 the DHCP server uses the dhcphwaddress and dhcpstatements entries
11572 before asking DNS to resolve the fixed-adddress. LTSP will use
11573 dhcphwaddress or associateddomain and the ldapconfig* attributes.
</p
>
11575 <p
>I am not yet sure if I can get the DHCP server to look for its
11576 dhcphost in a different location, to allow us to put the objects
11577 outside the
"DHCP Config
" subtree, but hope to figure out a way to do
11578 that. If I can
't figure out a way to do that, we can still get rid of
11579 the hosts subtree and move all its content into the DHCP Config tree
11580 (which probably should be renamed to be more related to the new
11581 content. I suspect cn=dnsdhcp,ou=services or something like that
11582 might be a good place to put it.
</p
>
11584 <p
>If you want to help out with implementing this for Debian Edu,
11585 please contact us on debian-edu@lists.debian.org.
</p
>
11590 <title>Idea for storing LTSP configuration in LDAP
</title>
11591 <link>https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</link>
11592 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Idea_for_storing_LTSP_configuration_in_LDAP.html
</guid>
11593 <pubDate>Sun,
11 Jul
2010 22:
00:
00 +
0200</pubDate>
11594 <description><p
>Vagrant mentioned on IRC today that ltsp_config now support
11595 sourcing files from /usr/share/ltsp/ltsp_config.d/ on the thin
11596 clients, and that this can be used to fetch configuration from LDAP if
11597 Debian Edu choose to store configuration there.
</p
>
11599 <p
>Armed with this information, I got inspired and wrote a test module
11600 to get configuration from LDAP. The idea is to look up the MAC
11601 address of the client in LDAP, and look for attributes on the form
11602 ltspconfigsetting=value, and use this to export SETTING=value to the
11603 LTSP clients.
</p
>
11605 <p
>The goal is to be able to store the LTSP configuration attributes
11606 in a
"computer
" LDAP object used by both DNS and DHCP, and thus
11607 allowing us to store all information about a computer in one place.
</p
>
11609 <p
>This is a untested draft implementation, and I welcome feedback on
11610 this approach. A real LDAP schema for the ltspClientAux objectclass
11611 need to be written. Comments, suggestions, etc?
</p
>
11613 <blockquote
><pre
>
11614 # Store in /opt/ltsp/$arch/usr/share/ltsp/ltsp_config.d/ldap-config
11616 # Fetch LTSP client settings from LDAP based on MAC address
11618 # Uses ethernet address as stored in the dhcpHost objectclass using
11619 # the dhcpHWAddress attribute or ethernet address stored in the
11620 # ieee802Device objectclass with the macAddress attribute.
11622 # This module is written to be schema agnostic, and only depend on the
11623 # existence of attribute names.
11625 # The LTSP configuration variables are saved directly using a
11626 # ltspConfig prefix and uppercasing the rest of the attribute name.
11627 # To set the SERVER variable, set the ltspConfigServer attribute.
11629 # Some LDAP schema should be created with all the relevant
11630 # configuration settings. Something like this should work:
11632 # objectclass (
1.1.2.2 NAME
'ltspClientAux
'
11635 # MAY ( ltspConfigServer $ ltsConfigSound $ ... )
11637 LDAPSERVER=$(debian-edu-ldapserver)
11638 if [
"$LDAPSERVER
" ] ; then
11639 LDAPBASE=$(debian-edu-ldapserver -b)
11640 for MAC in $(LANG=C ifconfig |grep -i hwaddr| awk
'{print $
5}
'|sort -u) ; do
11641 filter=
"(|(dhcpHWAddress=ethernet $MAC)(macAddress=$MAC))
"
11642 ldapsearch -h
"$LDAPSERVER
" -b
"$LDAPBASE
" -v -x
"$filter
" | \
11643 grep
'^ltspConfig
' | while read attr value ; do
11644 # Remove prefix and convert to upper case
11645 attr=$(echo $attr | sed
's/^ltspConfig//i
' | tr a-z A-Z)
11646 # bass value on to clients
11647 eval
"$attr=$value; export $attr
"
11651 </pre
></blockquote
>
11653 <p
>I
'm not sure this shell construction will work, because I suspect
11654 the while block might end up in a subshell causing the variables set
11655 there to not show up in ltsp-config, but if that is the case I am sure
11656 the code can be restructured to make sure the variables are passed on.
11657 I expect that can be solved with some testing. :)
</p
>
11659 <p
>If you want to help out with implementing this for Debian Edu,
11660 please contact us on debian-edu@lists.debian.org.
</p
>
11662 <p
>Update
2010-
07-
17: I am aware of another effort to store LTSP
11663 configuration in LDAP that was created around year
2000 by
11664 <a href=
"http://www.pcxperience.com/thinclient/documentation/ldap.html
">PC
11665 Xperience, Inc.,
2000</a
>. I found its
11666 <a href=
"http://people.redhat.com/alikins/ltsp/ldap/
">files
</a
> on a
11667 personal home page over at redhat.com.
</p
>
11672 <title>jXplorer, a very nice LDAP GUI
</title>
11673 <link>https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</link>
11674 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/jXplorer__a_very_nice_LDAP_GUI.html
</guid>
11675 <pubDate>Fri,
9 Jul
2010 12:
55:
00 +
0200</pubDate>
11676 <description><p
>Since
11677 <a href=
"http://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
">my
11678 last post
</a
> about available LDAP tools in Debian, I was told about a
11679 LDAP GUI that is even better than luma. The java application
11680 <a href=
"http://jxplorer.org/
">jXplorer
</a
> is claimed to be capable of
11681 moving LDAP objects and subtrees using drag-and-drop, and can
11682 authenticate using Kerberos. I have only tested the Kerberos
11683 authentication, but do not have a LDAP setup allowing me to rewrite
11684 LDAP with my test user yet. It is
11685 <a href=
"http://packages.qa.debian.org/j/jxplorer.html
">available in
11686 Debian
</a
> testing and unstable at the moment. The only problem I
11687 have with it is how it handle errors. If something go wrong, its
11688 non-intuitive behaviour require me to go through some query work list
11689 and remove the failing query. Nothing big, but very annoying.
</p
>
11694 <title>Lenny-
>Squeeze upgrades, apt vs aptitude with the Gnome desktop
</title>
11695 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</link>
11696 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__apt_vs_aptitude_with_the_Gnome_desktop.html
</guid>
11697 <pubDate>Sat,
3 Jul
2010 23:
55:
00 +
0200</pubDate>
11698 <description><p
>Here is a short update on my
<a
11699 href=
"http://people.skolelinux.org/~pere/debian-upgrade-testing/
">my
11700 Debian Lenny-
>Squeeze upgrade testing
</a
>. Here is a summary of the
11701 difference for Gnome when it is upgraded by apt-get and aptitude. I
'm
11702 not reporting the status for KDE, because the upgrade crashes when
11703 aptitude try because of missing conflicts
11704 (
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> and
11705 <a href=
"http://bugs.debian.org/
585716">#
585716</a
>).
</p
>
11707 <p
>At the end of the upgrade test script, dpkg -l is executed to get a
11708 complete list of the installed packages. Based on this I see these
11709 differences when I did a test run today. As usual, I do not really
11710 know what the correct set of packages would be, but thought it best to
11711 publish the difference.
</p
>
11713 <p
>Installed using apt-get, missing with aptitude
</p
>
11715 <blockquote
><p
>
11716 at-spi cpp-
4.3 finger gnome-spell gstreamer0.10-gnomevfs
11717 libatspi1.0-
0 libcupsys2 libeel2-data libgail-common libgdl-
1-common
11718 libgnomeprint2.2-data libgnomeprintui2.2-common libgnomevfs2-bin
11719 libgtksourceview-common libpt-
1.10.10-plugins-alsa
11720 libpt-
1.10.10-plugins-v4l libservlet2.4-java libxalan2-java
11721 libxerces2-java openoffice.org-writer2latex openssl-blacklist p7zip
11722 python-
4suite-xml python-eggtrayicon python-gtkhtml2
11723 python-gtkmozembed svgalibg1 xserver-xephyr zip
11724 </p
></blockquote
>
11726 <p
>Installed using apt-get, removed with aptitude
</p
>
11728 <blockquote
><p
>
11729 bluez-utils dhcdbd djvulibre-desktop epiphany-gecko
11730 gnome-app-install gnome-mount gnome-vfs-obexftp gnome-volume-manager
11731 libao2 libavahi-compat-libdnssd1 libavahi-core5 libbind9-
50
11732 libbluetooth2 libcamel1.2-
11 libcdio7 libcucul0 libcurl3
11733 libdirectfb-
1.0-
0 libdvdread3 libedata-cal1.2-
6 libedataserver1.2-
9
11734 libeel2-
2.20 libepc-
1.0-
1 libepc-ui-
1.0-
1 libexchange-storage1.2-
3
11735 libfaad0 libgd2-noxpm libgda3-
3 libgda3-common libggz2 libggzcore9
11736 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0 libgnome-desktop-
2
11737 libgnome-pilot2 libgnomecups1.0-
1 libgnomeprint2.2-
0
11738 libgnomeprintui2.2-
0 libgpod3 libgraphviz4 libgtkhtml2-
0
11739 libgtksourceview1.0-
0 libgucharmap6 libhesiod0 libicu38 libisccc50
11740 libisccfg50 libiw29 libkpathsea4 libltdl3 liblwres50 libmagick++
10
11741 libmagick10 libmalaga7 libmtp7 libmysqlclient15off libnautilus-burn4
11742 libneon27 libnm-glib0 libnm-util0 libopal-
2.2 libosp5
11743 libparted1.8-
10 libpisock9 libpisync1 libpoppler-glib3 libpoppler3
11744 libpt-
1.10.10 libraw1394-
8 libsensors3 libsmbios2 libsoup2.2-
8
11745 libssh2-
1 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1
11746 libtotem-plparser10 libtrackerclient0 libvoikko1 libxalan2-java-gcj
11747 libxerces2-java-gcj libxklavier12 libxtrap6 libxxf86misc1 libzephyr3
11748 mysql-common swfdec-gnome totem-gstreamer wodim
11749 </p
></blockquote
>
11751 <p
>Installed using aptitude, missing with apt-get
</p
>
11753 <blockquote
><p
>
11754 gnome gnome-desktop-environment hamster-applet python-gnomeapplet
11755 python-gnomekeyring python-wnck rhythmbox-plugins xorg
11756 xserver-xorg-input-all xserver-xorg-input-evdev
11757 xserver-xorg-input-kbd xserver-xorg-input-mouse
11758 xserver-xorg-input-synaptics xserver-xorg-video-all
11759 xserver-xorg-video-apm xserver-xorg-video-ark xserver-xorg-video-ati
11760 xserver-xorg-video-chips xserver-xorg-video-cirrus
11761 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11762 xserver-xorg-video-glint xserver-xorg-video-i128
11763 xserver-xorg-video-i740 xserver-xorg-video-mach64
11764 xserver-xorg-video-mga xserver-xorg-video-neomagic
11765 xserver-xorg-video-nouveau xserver-xorg-video-nv
11766 xserver-xorg-video-r128 xserver-xorg-video-radeon
11767 xserver-xorg-video-radeonhd xserver-xorg-video-rendition
11768 xserver-xorg-video-s3 xserver-xorg-video-s3virge
11769 xserver-xorg-video-savage xserver-xorg-video-siliconmotion
11770 xserver-xorg-video-sis xserver-xorg-video-sisusb
11771 xserver-xorg-video-tdfx xserver-xorg-video-tga
11772 xserver-xorg-video-trident xserver-xorg-video-tseng
11773 xserver-xorg-video-vesa xserver-xorg-video-vmware
11774 xserver-xorg-video-voodoo
11775 </p
></blockquote
>
11777 <p
>Installed using aptitude, removed with apt-get
</p
>
11779 <blockquote
><p
>
11780 deskbar-applet xserver-xorg xserver-xorg-core
11781 xserver-xorg-input-wacom xserver-xorg-video-intel
11782 xserver-xorg-video-openchrome
11783 </p
></blockquote
>
11785 <p
>I was told on IRC that the xorg-xserver package was
11786 <a href=
"http://git.debian.org/?p=pkg-xorg/xserver/xorg-server.git;a=commit;h=
9c8080d06c457932d3bfec021c69ac000aa60120
">changed
11787 in git
</a
> today to try to get apt-get to not remove xorg completely.
11788 No idea when it hits Squeeze, but when it does I hope it will reduce
11789 the difference somewhat.
11794 <title>LUMA, a very nice LDAP GUI
</title>
11795 <link>https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</link>
11796 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/LUMA__a_very_nice_LDAP_GUI.html
</guid>
11797 <pubDate>Mon,
28 Jun
2010 00:
30:
00 +
0200</pubDate>
11798 <description><p
>The last few days I have been looking into the status of the LDAP
11799 directory in Debian Edu, and in the process I started to miss a GUI
11800 tool to browse the LDAP tree. The only one I was able to find in
11801 Debian/Squeeze and Lenny is
11802 <a href=
"http://luma.sourceforge.net/
">LUMA
</a
>, which has proved to
11803 be a great tool to get a overview of the current LDAP directory
11804 populated by default in Skolelinux. Thanks to it, I have been able to
11805 find empty and obsolete subtrees, misplaced objects and duplicate
11806 objects. It will be installed by default in Debian/Squeeze. If you
11807 are working with LDAP, give it a go. :)
</p
>
11809 <p
>I did notice one problem with it I have not had time to report to
11810 the BTS yet. There is no .desktop file in the package, so the tool do
11811 not show up in the Gnome and KDE menus, but only deep down in in the
11812 Debian submenu in KDE. I hope that can be fixed before Squeeze is
11813 released.
</p
>
11815 <p
>I have not yet been able to get it to modify the tree yet. I would
11816 like to move objects and remove subtrees directly in the GUI, but have
11817 not found a way to do that with LUMA yet. So in the mean time, I use
11818 <a href=
"http://www.lichteblau.com/ldapvi/
">ldapvi
</a
> for that.
</p
>
11820 <p
>If you have tips on other GUI tools for LDAP that might be useful
11821 in Debian Edu, please contact us on debian-edu@lists.debian.org.
</p
>
11823 <p
>Update
2010-
06-
29: Ross Reedstrom tipped us about the
11824 <a href=
"http://packages.qa.debian.org/g/gq.html
">gq
</a
> package as a
11825 useful GUI alternative. It seem like a good tool, but is unmaintained
11826 in Debian and got a RC bug keeping it out of Squeeze. Unless that
11827 changes, it will not be an option for Debian Edu based on Squeeze.
</p
>
11832 <title>Idea for a change to LDAP schemas allowing DNS and DHCP info to be combined into one object
</title>
11833 <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>
11834 <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>
11835 <pubDate>Thu,
24 Jun
2010 00:
35:
00 +
0200</pubDate>
11836 <description><p
>A while back, I
11837 <a href=
"http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
">complained
11838 about the fact
</a
> that it is not possible with the provided schemas
11839 for storing DNS and DHCP information in LDAP to combine the two sets
11840 of information into one LDAP object representing a computer.
</p
>
11842 <p
>In the mean time, I discovered that a simple fix would be to make
11843 the dhcpHost object class auxiliary, to allow it to be combined with
11844 the dNSDomain object class, and thus forming one object for one
11845 computer when storing both DHCP and DNS information in LDAP.
</p
>
11847 <p
>If I understand this correctly, it is not safe to do this change
11848 without also changing the assigned number for the object class, and I
11849 do not know enough about LDAP schema design to do that properly for
11850 Debian Edu.
</p
>
11852 <p
>Anyway, for future reference, this is how I believe we could change
11854 <a href=
"http://tools.ietf.org/html/draft-ietf-dhc-ldap-schema-
00">DHCP
11855 schema
</a
> to solve at least part of the problem with the LDAP schemas
11856 available today from IETF.
</p
>
11859 --- dhcp.schema (revision
65192)
11860 +++ dhcp.schema (working copy)
11861 @@ -
376,
7 +
376,
7 @@
11862 objectclass (
2.16.840.1.113719.1.203.6.6
11863 NAME
'dhcpHost
'
11864 DESC
'This represents information about a particular client
'
11866 + SUP top AUXILIARY
11868 MAY (dhcpLeaseDN $ dhcpHWAddress $ dhcpOptionsDN $ dhcpStatements $ dhcpComments $ dhcpOption)
11869 X-NDS_CONTAINMENT (
'dhcpService
' 'dhcpSubnet
' 'dhcpGroup
') )
11872 <p
>I very much welcome clues on how to do this properly for Debian
11873 Edu/Squeeze. We provide the DHCP schema in our debian-edu-config
11874 package, and should thus be free to rewrite it as we see fit.
</p
>
11876 <p
>If you want to help out with implementing this for Debian Edu,
11877 please contact us on debian-edu@lists.debian.org.
</p
>
11882 <title>Calling tasksel like the installer, while still getting useful output
</title>
11883 <link>https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</link>
11884 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Calling_tasksel_like_the_installer__while_still_getting_useful_output.html
</guid>
11885 <pubDate>Wed,
16 Jun
2010 14:
55:
00 +
0200</pubDate>
11886 <description><p
>A few times I have had the need to simulate the way tasksel
11887 installs packages during the normal debian-installer run. Until now,
11888 I have ended up letting tasksel do the work, with the annoying problem
11889 of not getting any feedback at all when something fails (like a
11890 conffile question from dpkg or a download that fails), using code like
11893 <blockquote
><pre
>
11894 export DEBIAN_FRONTEND=noninteractive
11895 tasksel --new-install
11896 </pre
></blockquote
>
11898 This would invoke tasksel, let its automatic task selection pick the
11899 tasks to install, and continue to install the requested tasks without
11900 any output what so ever.
11902 Recently I revisited this problem while working on the automatic
11903 package upgrade testing, because tasksel would some times hang without
11904 any useful feedback, and I want to see what is going on when it
11905 happen. Then it occured to me, I can parse the output from tasksel
11906 when asked to run in test mode, and use that aptitude command line
11907 printed by tasksel then to simulate the tasksel run. I ended up using
11910 <blockquote
><pre
>
11911 export DEBIAN_FRONTEND=noninteractive
11912 cmd=
"$(in_target tasksel -t --new-install | sed
's/debconf-apt-progress -- //
')
"
11914 </pre
></blockquote
>
11916 <p
>The content of $cmd is typically something like
"<tt
>aptitude -q
11917 --without-recommends -o APT::Install-Recommends=no -y install
11918 ~t^desktop$ ~t^gnome-desktop$ ~t^laptop$ ~pstandard ~prequired
11919 ~pimportant
</tt
>", which will install the gnome desktop task, the
11920 laptop task and all packages with priority standard , required and
11921 important, just like tasksel would have done it during
11922 installation.
</p
>
11924 <p
>A better approach is probably to extend tasksel to be able to
11925 install packages without using debconf-apt-progress, for use cases
11926 like this.
</p
>
11931 <title>Lenny-
>Squeeze upgrades, removals by apt and aptitude
</title>
11932 <link>https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</link>
11933 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Lenny__Squeeze_upgrades__removals_by_apt_and_aptitude.html
</guid>
11934 <pubDate>Sun,
13 Jun
2010 09:
05:
00 +
0200</pubDate>
11935 <description><p
>My
11936 <a href=
"http://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
">testing
11937 of Debian upgrades
</a
> from Lenny to Squeeze continues, and I
've
11938 finally made the upgrade logs available from
11939 <a href=
"http://people.skolelinux.org/pere/debian-upgrade-testing/
">http://people.skolelinux.org/pere/debian-upgrade-testing/
</a
>.
11940 I am now testing dist-upgrade of Gnome and KDE in a chroot using both
11941 apt and aptitude, and found their differences interesting. This time
11942 I will only focus on their removal plans.
</p
>
11944 <p
>After installing a Gnome desktop and the laptop task, apt-get wants
11945 to remove
72 packages when dist-upgrading from Lenny to Squeeze. The
11946 surprising part is that it want to remove xorg and all
11947 xserver-xorg-video* drivers. Clearly not a good choice, but I am not
11948 sure why. When asking aptitude to do the same, it want to remove
129
11949 packages, but most of them are library packages I suspect are no
11950 longer needed. Both of them want to remove bluetooth packages, which
11951 I do not know. Perhaps these bluetooth packages are obsolete?
</p
>
11953 <p
>For KDE, apt-get want to remove
82 packages, among them kdebase
11954 which seem like a bad idea and xorg the same way as with Gnome. Asking
11955 aptitude for the same, it wants to remove
192 packages, none which are
11956 too surprising.
</p
>
11958 <p
>I guess the removal of xorg during upgrades should be investigated
11959 and avoided, and perhaps others as well. Here are the complete list
11960 of planned removals. The complete logs is available from the URL
11961 above. Note if you want to repeat these tests, that the upgrade test
11962 for kde+apt-get hung in the tasksel setup because of dpkg asking
11963 conffile questions. No idea why. I worked around it by using
11964 '<tt
>echo
>> /proc/
<em
>pidofdpkg
</em
>/fd/
0</tt
>' to tell dpkg to
11965 continue.
</p
>
11967 <p
><b
>apt-get gnome
72</b
>
11968 <br
>bluez-gnome cupsddk-drivers deskbar-applet gnome
11969 gnome-desktop-environment gnome-network-admin gtkhtml3.14
11970 iceweasel-gnome-support libavcodec51 libdatrie0 libgdl-
1-
0
11971 libgnomekbd2 libgnomekbdui2 libmetacity0 libslab0 libxcb-xlib0
11972 nautilus-cd-burner python-gnome2-desktop python-gnome2-extras
11973 serpentine swfdec-mozilla update-manager xorg xserver-xorg
11974 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
11975 xserver-xorg-input-kbd xserver-xorg-input-mouse
11976 xserver-xorg-input-synaptics xserver-xorg-input-wacom
11977 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
11978 xserver-xorg-video-ati xserver-xorg-video-chips
11979 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
11980 xserver-xorg-video-dummy xserver-xorg-video-fbdev
11981 xserver-xorg-video-glint xserver-xorg-video-i128
11982 xserver-xorg-video-i740 xserver-xorg-video-imstt
11983 xserver-xorg-video-intel xserver-xorg-video-mach64
11984 xserver-xorg-video-mga xserver-xorg-video-neomagic
11985 xserver-xorg-video-nsc xserver-xorg-video-nv
11986 xserver-xorg-video-openchrome xserver-xorg-video-r128
11987 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
11988 xserver-xorg-video-rendition xserver-xorg-video-s3
11989 xserver-xorg-video-s3virge xserver-xorg-video-savage
11990 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
11991 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
11992 xserver-xorg-video-tga xserver-xorg-video-trident
11993 xserver-xorg-video-tseng xserver-xorg-video-v4l
11994 xserver-xorg-video-vesa xserver-xorg-video-vga
11995 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9
11996 xulrunner-
1.9-gnome-support
</p
>
11998 <p
><b
>aptitude gnome
129</b
>
12000 <br
>bluez-gnome bluez-utils cpp-
4.3 cupsddk-drivers dhcdbd
12001 djvulibre-desktop finger gnome-app-install gnome-mount
12002 gnome-network-admin gnome-spell gnome-vfs-obexftp
12003 gnome-volume-manager gstreamer0.10-gnomevfs gtkhtml3.14 libao2
12004 libavahi-compat-libdnssd1 libavahi-core5 libavcodec51 libbluetooth2
12005 libcamel1.2-
11 libcdio7 libcucul0 libcupsys2 libcurl3 libdatrie0
12006 libdirectfb-
1.0-
0 libdvdread3 libedataserver1.2-
9 libeel2-
2.20
12007 libeel2-data libepc-
1.0-
1 libepc-ui-
1.0-
1 libfaad0 libgail-common
12008 libgd2-noxpm libgda3-
3 libgda3-common libgdl-
1-
0 libgdl-
1-common
12009 libggz2 libggzcore9 libggzmod4 libgksu1.2-
0 libgksuui1.0-
1 libgmyth0
12010 libgnomecups1.0-
1 libgnomekbd2 libgnomekbdui2 libgnomeprint2.2-
0
12011 libgnomeprint2.2-data libgnomeprintui2.2-
0 libgnomeprintui2.2-common
12012 libgnomevfs2-bin libgpod3 libgraphviz4 libgtkhtml2-
0
12013 libgtksourceview-common libgtksourceview1.0-
0 libgucharmap6
12014 libhesiod0 libicu38 libiw29 libkpathsea4 libltdl3 libmagick++
10
12015 libmagick10 libmalaga7 libmetacity0 libmtp7 libmysqlclient15off
12016 libnautilus-burn4 libneon27 libnm-glib0 libnm-util0 libopal-
2.2
12017 libosp5 libparted1.8-
10 libpoppler-glib3 libpoppler3 libpt-
1.10.10
12018 libpt-
1.10.10-plugins-alsa libpt-
1.10.10-plugins-v4l libraw1394-
8
12019 libsensors3 libslab0 libsmbios2 libsoup2.2-
8 libssh2-
1
12020 libsuitesparse-
3.1.0 libswfdec-
0.6-
90 libtalloc1 libtotem-plparser10
12021 libtrackerclient0 libxalan2-java libxalan2-java-gcj libxcb-xlib0
12022 libxerces2-java libxerces2-java-gcj libxklavier12 libxtrap6
12023 libxxf86misc1 libzephyr3 mysql-common nautilus-cd-burner
12024 openoffice.org-writer2latex openssl-blacklist p7zip
12025 python-
4suite-xml python-eggtrayicon python-gnome2-desktop
12026 python-gnome2-extras python-gtkhtml2 python-gtkmozembed
12027 python-numeric python-sexy serpentine svgalibg1 swfdec-gnome
12028 swfdec-mozilla totem-gstreamer update-manager wodim
12029 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12030 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12033 <p
><b
>apt-get kde
82</b
>
12035 <br
>cupsddk-drivers karm kaudiocreator kcoloredit kcontrol kde kde-core
12036 kdeaddons kdeartwork kdebase kdebase-bin kdebase-bin-kde3
12037 kdebase-kio-plugins kdesktop kdeutils khelpcenter kicker
12038 kicker-applets knewsticker kolourpaint konq-plugins konqueror korn
12039 kpersonalizer kscreensaver ksplash libavcodec51 libdatrie0 libkiten1
12040 libxcb-xlib0 quanta superkaramba texlive-base-bin xorg xserver-xorg
12041 xserver-xorg-core xserver-xorg-input-all xserver-xorg-input-evdev
12042 xserver-xorg-input-kbd xserver-xorg-input-mouse
12043 xserver-xorg-input-synaptics xserver-xorg-input-wacom
12044 xserver-xorg-video-all xserver-xorg-video-apm xserver-xorg-video-ark
12045 xserver-xorg-video-ati xserver-xorg-video-chips
12046 xserver-xorg-video-cirrus xserver-xorg-video-cyrix
12047 xserver-xorg-video-dummy xserver-xorg-video-fbdev
12048 xserver-xorg-video-glint xserver-xorg-video-i128
12049 xserver-xorg-video-i740 xserver-xorg-video-imstt
12050 xserver-xorg-video-intel xserver-xorg-video-mach64
12051 xserver-xorg-video-mga xserver-xorg-video-neomagic
12052 xserver-xorg-video-nsc xserver-xorg-video-nv
12053 xserver-xorg-video-openchrome xserver-xorg-video-r128
12054 xserver-xorg-video-radeon xserver-xorg-video-radeonhd
12055 xserver-xorg-video-rendition xserver-xorg-video-s3
12056 xserver-xorg-video-s3virge xserver-xorg-video-savage
12057 xserver-xorg-video-siliconmotion xserver-xorg-video-sis
12058 xserver-xorg-video-sisusb xserver-xorg-video-tdfx
12059 xserver-xorg-video-tga xserver-xorg-video-trident
12060 xserver-xorg-video-tseng xserver-xorg-video-v4l
12061 xserver-xorg-video-vesa xserver-xorg-video-vga
12062 xserver-xorg-video-vmware xserver-xorg-video-voodoo xulrunner-
1.9</p
>
12064 <p
><b
>aptitude kde
192</b
>
12065 <br
>bluez-utils cpp-
4.3 cupsddk-drivers cvs dcoprss dhcdbd
12066 djvulibre-desktop dosfstools eyesapplet fifteenapplet finger gettext
12067 ghostscript-x imlib-base imlib11 indi kandy karm kasteroids
12068 kaudiocreator kbackgammon kbstate kcoloredit kcontrol kcron kdat
12069 kdeadmin-kfile-plugins kdeartwork-misc kdeartwork-theme-window
12070 kdebase-bin-kde3 kdebase-kio-plugins kdeedu-data
12071 kdegraphics-kfile-plugins kdelirc kdemultimedia-kappfinder-data
12072 kdemultimedia-kfile-plugins kdenetwork-kfile-plugins
12073 kdepim-kfile-plugins kdepim-kio-plugins kdeprint kdesktop kdessh
12074 kdict kdnssd kdvi kedit keduca kenolaba kfax kfaxview kfouleggs
12075 kghostview khelpcenter khexedit kiconedit kitchensync klatin
12076 klickety kmailcvt kmenuedit kmid kmilo kmoon kmrml kodo kolourpaint
12077 kooka korn kpager kpdf kpercentage kpf kpilot kpoker kpovmodeler
12078 krec kregexpeditor ksayit ksim ksirc ksirtet ksmiletris ksmserver
12079 ksnake ksokoban ksplash ksvg ksysv ktip ktnef kuickshow kverbos
12080 kview kviewshell kvoctrain kwifimanager kwin kwin4 kworldclock
12081 kxsldbg libakode2 libao2 libarts1-akode libarts1-audiofile
12082 libarts1-mpeglib libarts1-xine libavahi-compat-libdnssd1
12083 libavahi-core5 libavc1394-
0 libavcodec51 libbluetooth2
12084 libboost-python1.34
.1 libcucul0 libcurl3 libcvsservice0 libdatrie0
12085 libdirectfb-
1.0-
0 libdjvulibre21 libdvdread3 libfaad0 libfreebob0
12086 libgail-common libgd2-noxpm libgraphviz4 libgsmme1c2a libgtkhtml2-
0
12087 libicu38 libiec61883-
0 libindex0 libiw29 libk3b3 libkcal2b libkcddb1
12088 libkdeedu3 libkdepim1a libkgantt0 libkiten1 libkleopatra1 libkmime2
12089 libkpathsea4 libkpimexchange1 libkpimidentities1 libkscan1
12090 libksieve0 libktnef1 liblockdev1 libltdl3 libmagick10 libmimelib1c2a
12091 libmozjs1d libmpcdec3 libneon27 libnm-util0 libopensync0 libpisock9
12092 libpoppler-glib3 libpoppler-qt2 libpoppler3 libraw1394-
8 libsmbios2
12093 libssh2-
1 libsuitesparse-
3.1.0 libtalloc1 libtiff-tools
12094 libxalan2-java libxalan2-java-gcj libxcb-xlib0 libxerces2-java
12095 libxerces2-java-gcj libxtrap6 mpeglib networkstatus
12096 openoffice.org-writer2latex pmount poster psutils quanta quanta-data
12097 superkaramba svgalibg1 tex-common texlive-base texlive-base-bin
12098 texlive-common texlive-doc-base texlive-fonts-recommended
12099 xserver-xorg-video-cyrix xserver-xorg-video-imstt
12100 xserver-xorg-video-nsc xserver-xorg-video-v4l xserver-xorg-video-vga
12101 xulrunner-
1.9</p
>
12107 <title>Automatic upgrade testing from Lenny to Squeeze
</title>
12108 <link>https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</link>
12109 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Automatic_upgrade_testing_from_Lenny_to_Squeeze.html
</guid>
12110 <pubDate>Fri,
11 Jun
2010 22:
50:
00 +
0200</pubDate>
12111 <description><p
>The last few days I have done some upgrade testing in Debian, to
12112 see if the upgrade from Lenny to Squeeze will go smoothly. A few bugs
12113 have been discovered and reported in the process
12114 (
<a href=
"http://bugs.debian.org/
585410">#
585410</a
> in nagios3-cgi,
12115 <a href=
"http://bugs.debian.org/
584879">#
584879</a
> already fixed in
12116 enscript and
<a href=
"http://bugs.debian.org/
584861">#
584861</a
> in
12117 kdebase-workspace-data), and to get a more regular testing going on, I
12118 am working on a script to automate the test.
</p
>
12120 <p
>The idea is to create a Lenny chroot and use tasksel to install a
12121 Gnome or KDE desktop installation inside the chroot before upgrading
12122 it. To ensure no services are started in the chroot, a policy-rc.d
12123 script is inserted. To make sure tasksel believe it is to install a
12124 desktop on a laptop, the tasksel tests are replaced in the chroot
12125 (only acceptable because this is a throw-away chroot).
</p
>
12127 <p
>A naive upgrade from Lenny to Squeeze using aptitude dist-upgrade
12128 currently always fail because udev refuses to upgrade with the kernel
12129 in Lenny, so to avoid that problem the file /etc/udev/kernel-upgrade
12130 is created. The bug report
12131 <a href=
"http://bugs.debian.org/
566000">#
566000</a
> make me suspect
12132 this problem do not trigger in a chroot, but I touch the file anyway
12133 to make sure the upgrade go well. Testing on virtual and real
12134 hardware have failed me because of udev so far, and creating this file
12135 do the trick in such settings anyway. This is a
12136 <a href=
"http://www.linuxquestions.org/questions/debian-
26/failed-dist-upgrade-due-to-udev-config_sysfs_deprecated-nonsense-
804130/
">known
12137 issue
</a
> and the current udev behaviour is intended by the udev
12138 maintainer because he lack the resources to rewrite udev to keep
12139 working with old kernels or something like that. I really wish the
12140 udev upstream would keep udev backwards compatible, to avoid such
12141 upgrade problem, but given that they fail to do so, I guess
12142 documenting the way out of this mess is the best option we got for
12143 Debian Squeeze.
</p
>
12145 <p
>Anyway, back to the task at hand, testing upgrades. This test
12146 script, which I call
<tt
>upgrade-test
</tt
> for now, is doing the
12149 <blockquote
><pre
>
12153 if [
"$
1" ] ; then
12162 exec
&lt; /dev/null
12164 mirror=http://ftp.skolelinux.org/debian
12165 tmpdir=chroot-$from-upgrade-$to-$desktop
12167 debootstrap $from $tmpdir $mirror
12168 chroot $tmpdir aptitude update
12169 cat
> $tmpdir/usr/sbin/policy-rc.d
&lt;
&lt;EOF
12173 chmod a+rx $tmpdir/usr/sbin/policy-rc.d
12175 umount $tmpdir/proc
12177 mount -t proc proc $tmpdir/proc
12178 # Make sure proc is unmounted also on failure
12179 trap exit_cleanup EXIT INT
12181 chroot $tmpdir aptitude -y install debconf-utils
12183 # Make sure tasksel autoselection trigger. It need the test scripts
12184 # to return the correct answers.
12185 echo tasksel tasksel/desktop multiselect $desktop | \
12186 chroot $tmpdir debconf-set-selections
12188 # Include the desktop and laptop task
12189 for test in desktop laptop ; do
12190 echo
> $tmpdir/usr/lib/tasksel/tests/$test
&lt;
&lt;EOF
12194 chmod a+rx $tmpdir/usr/lib/tasksel/tests/$test
12197 DEBIAN_FRONTEND=noninteractive
12198 DEBIAN_PRIORITY=critical
12199 export DEBIAN_FRONTEND DEBIAN_PRIORITY
12200 chroot $tmpdir tasksel --new-install
12202 echo deb $mirror $to main
> $tmpdir/etc/apt/sources.list
12203 chroot $tmpdir aptitude update
12204 touch $tmpdir/etc/udev/kernel-upgrade
12205 chroot $tmpdir aptitude -y dist-upgrade
12207 </pre
></blockquote
>
12209 <p
>I suspect it would be useful to test upgrades with both apt-get and
12210 with aptitude, but I have not had time to look at how they behave
12211 differently so far. I hope to get a cron job running to do the test
12212 regularly and post the result on the web. The Gnome upgrade currently
12213 work, while the KDE upgrade fail because of the bug in
12214 kdebase-workspace-data
</p
>
12216 <p
>I am not quite sure what kind of extract from the huge upgrade logs
12217 (KDE
167 KiB, Gnome
516 KiB) it make sense to include in this blog
12218 post, so I will refrain from trying. I can report that for Gnome,
12219 aptitude report
760 packages upgraded,
448 newly installed,
129 to
12220 remove and
1 not upgraded and
1024MB need to be downloaded while for
12221 KDE the same numbers are
702 packages upgraded,
507 newly installed,
12222 193 to remove and
0 not upgraded and
1117MB need to be downloaded
</p
>
12224 <p
>I am very happy to notice that the Gnome desktop + laptop upgrade
12225 is able to migrate to dependency based boot sequencing and parallel
12226 booting without a hitch. Was unsure if there were still bugs with
12227 packages failing to clean up their obsolete init.d script during
12228 upgrades, and no such problem seem to affect the Gnome desktop+laptop
12229 packages.
</p
>
12234 <title>Upstart or sysvinit - as init.d scripts see it
</title>
12235 <link>https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</link>
12236 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Upstart_or_sysvinit___as_init_d_scripts_see_it.html
</guid>
12237 <pubDate>Sun,
6 Jun
2010 23:
55:
00 +
0200</pubDate>
12238 <description><p
>If Debian is to migrate to upstart on Linux, I expect some init.d
12239 scripts to migrate (some of) their operations to upstart job while
12240 keeping the init.d for hurd and kfreebsd. The packages with such
12241 needs will need a way to get their init.d scripts to behave
12242 differently when used with sysvinit and with upstart. Because of
12243 this, I had a look at the environment variables set when a init.d
12244 script is running under upstart, and when it is not.
</p
>
12246 <p
>With upstart, I notice these environment variables are set when a
12247 script is started from rcS.d/ (ignoring some irrelevant ones like
12248 COLUMNS):
</p
>
12250 <blockquote
><pre
>
12256 UPSTART_EVENTS=startup
12258 UPSTART_JOB=rc-sysinit
12259 </pre
></blockquote
>
12261 <p
>With sysvinit, these environment variables are set for the same
12264 <blockquote
><pre
>
12265 INIT_VERSION=sysvinit-
2.88
12270 </pre
></blockquote
>
12272 <p
>The RUNLEVEL and PREVLEVEL environment variables passed on from
12273 sysvinit are not set by upstart. Not sure if it is intentional or not
12274 to not be compatible with sysvinit in this regard.
</p
>
12276 <p
>For scripts needing to behave differently when upstart is used,
12277 looking for the UPSTART_JOB environment variable seem to be a good
12283 <title>A manual for standards wars...
</title>
12284 <link>https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</link>
12285 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/A_manual_for_standards_wars___.html
</guid>
12286 <pubDate>Sun,
6 Jun
2010 14:
15:
00 +
0200</pubDate>
12287 <description><p
>Via the
12288 <a href=
"http://feedproxy.google.com/~r/robweir/antic-atom/~
3/QzU4RgoAGMg/weekly-links-
10.html
">blog
12289 of Rob Weir
</a
> I came across the very interesting essay named
12290 <a href=
"http://faculty.haas.berkeley.edu/shapiro/wars.pdf
">The Art of
12291 Standards Wars
</a
> (PDF
25 pages). I recommend it for everyone
12292 following the standards wars of today.
</p
>
12297 <title>Sitesummary tip: Listing computer hardware models used at site
</title>
12298 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</link>
12299 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_computer_hardware_models_used_at_site.html
</guid>
12300 <pubDate>Thu,
3 Jun
2010 12:
05:
00 +
0200</pubDate>
12301 <description><p
>When using sitesummary at a site to track machines, it is possible
12302 to get a list of the machine types in use thanks to the DMI
12303 information extracted from each machine. The script to do so is
12304 included in the sitesummary package, and here is example output from
12305 the Skolelinux build servers:
</p
>
12307 <blockquote
><pre
>
12308 maintainer:~# /usr/lib/sitesummary/hardware-model-summary
12310 Dell Computer Corporation
1
12313 eserver xSeries
345 -[
8670M1X]-
1
12317 </pre
></blockquote
>
12319 <p
>The quality of the report depend on the quality of the DMI tables
12320 provided in each machine. Here there are Intel machines without model
12321 information listed with Intel as vendor and no model, and virtual Xen
12322 machines listed as [no-dmi-info]. One can add -l as a command line
12323 option to list the individual machines.
</p
>
12325 <p
>A larger list is
12326 <a href=
"http://narvikskolen.no/sitesummary/
">available from the the
12327 city of Narvik
</a
>, which uses Skolelinux on all their shools and also
12328 provide the basic sitesummary report publicly. In their report there
12329 are ~
1400 machines. I know they use both Ubuntu and Skolelinux on
12330 their machines, and as sitesummary is available in both distributions,
12331 it is trivial to get all of them to report to the same central
12332 collector.
</p
>
12337 <title>KDM fail at boot with NVidia cards - and no one try to fix it?
</title>
12338 <link>https://people.skolelinux.org/pere/blog/KDM_fail_at_boot_with_NVidia_cards___and_no_one_try_to_fix_it_.html
</link>
12339 <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>
12340 <pubDate>Tue,
1 Jun
2010 17:
05:
00 +
0200</pubDate>
12341 <description><p
>It is strange to watch how a bug in Debian causing KDM to fail to
12342 start at boot when an NVidia video card is used is handled. The
12343 problem seem to be that the nvidia X.org driver uses a long time to
12344 initialize, and this duration is longer than kdm is configured to
12347 <p
>I came across two bugs related to this issue,
12348 <a href=
"http://bugs.debian.org/
583312">#
583312</a
> initially filed
12349 against initscripts and passed on to nvidia-glx when it became obvious
12350 that the nvidia drivers were involved, and
12351 <a href=
"http://bugs.debian.org/
524751">#
524751</a
> initially filed against
12352 kdm and passed on to src:nvidia-graphics-drivers for unknown reasons.
</p
>
12354 <p
>To me, it seem that no-one is interested in actually solving the
12355 problem nvidia video card owners experience and make sure the Debian
12356 distribution work out of the box for these users. The nvidia driver
12357 maintainers expect kdm to be set up to wait longer, while kdm expect
12358 the nvidia driver maintainers to fix the driver to start faster, and
12359 while they wait for each other I guess the users end up switching to a
12360 distribution that work for them. I have no idea what the solution is,
12361 but I am pretty sure that waiting for each other is not it.
</p
>
12363 <p
>I wonder why we end up handling bugs this way.
</p
>
12368 <title>Parallellized boot seem to hold up well in Debian/testing
</title>
12369 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</link>
12370 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_seem_to_hold_up_well_in_Debian_testing.html
</guid>
12371 <pubDate>Thu,
27 May
2010 23:
55:
00 +
0200</pubDate>
12372 <description><p
>A few days ago, parallel booting was enabled in Debian/testing.
12373 The feature seem to hold up pretty well, but three fairly serious
12374 issues are known and should be solved:
12376 <p
><ul
>
12378 <li
>The wicd package seen to
12379 <a href=
"http://bugs.debian.org/
508289">break NFS mounting
</a
> and
12380 <a href=
"http://bugs.debian.org/
581586">network setup
</a
> when
12381 parallel booting is enabled. No idea why, but the wicd maintainer
12382 seem to be on the case.
</li
>
12384 <li
>The nvidia X driver seem to
12385 <a href=
"http://bugs.debian.org/
583312">have a race condition
</a
>
12386 triggered more easily when parallel booting is in effect. The
12387 maintainer is on the case.
</li
>
12389 <li
>The sysv-rc package fail to properly enable dependency based boot
12390 sequencing (the shutdown is broken) when old file-rc users
12391 <a href=
"http://bugs.debian.org/
575080">try to switch back
</a
> to
12392 sysv-rc. One way to solve it would be for file-rc to create
12393 /etc/init.d/.legacy-bootordering, and another is to try to make
12394 sysv-rc more robust. Will investigate some more and probably upload a
12395 workaround in sysv-rc to help those trying to move from file-rc to
12396 sysv-rc get a working shutdown.
</li
>
12398 </ul
></p
>
12400 <p
>All in all not many surprising issues, and all of them seem
12401 solvable before Squeeze is released. In addition to these there are
12402 some packages with bugs in their dependencies and run level settings,
12403 which I expect will be fixed in a reasonable time span.
</p
>
12405 <p
>If you report any problems with dependencies in init.d scripts to
12406 the BTS, please usertag the report to get it to show up at
12407 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12408 list of usertagged bugs related to this
</a
>.
</p
>
12410 <p
>Update: Correct bug number to file-rc issue.
</p
>
12415 <title>More flexible firmware handling in debian-installer
</title>
12416 <link>https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</link>
12417 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/More_flexible_firmware_handling_in_debian_installer.html
</guid>
12418 <pubDate>Sat,
22 May
2010 21:
30:
00 +
0200</pubDate>
12419 <description><p
>After a long break from debian-installer development, I finally
12420 found time today to return to the project. Having to spend less time
12421 working dependency based boot in debian, as it is almost complete now,
12422 definitely helped freeing some time.
</p
>
12424 <p
>A while back, I ran into a problem while working on Debian Edu. We
12425 include some firmware packages on the Debian Edu CDs, those needed to
12426 get disk and network controllers working. Without having these
12427 firmware packages available during installation, it is impossible to
12428 install Debian Edu on the given machine, and because our target group
12429 are non-technical people, asking them to provide firmware packages on
12430 an external medium is a support pain. Initially, I expected it to be
12431 enough to include the firmware packages on the CD to get
12432 debian-installer to find and use them. This proved to be wrong.
12433 Next, I hoped it was enough to symlink the relevant firmware packages
12434 to some useful location on the CD (tried /cdrom/ and
12435 /cdrom/firmware/). This also proved to not work, and at this point I
12436 found time to look at the debian-installer code to figure out what was
12437 going to work.
</p
>
12439 <p
>The firmware loading code is in the hw-detect package, and a closer
12440 look revealed that it would only look for firmware packages outside
12441 the installation media, so the CD was never checked for firmware
12442 packages. It would only check USB sticks, floppies and other
12443 "external
" media devices. Today I changed it to also look in the
12444 /cdrom/firmware/ directory on the mounted CD or DVD, which should
12445 solve the problem I ran into with Debian edu. I also changed it to
12446 look in /firmware/, to make sure the installer also find firmware
12447 provided in the initrd when booting the installer via PXE, to allow us
12448 to provide the same feature in the PXE setup included in Debian
12451 <p
>To make sure firmware deb packages with a license questions are not
12452 activated without asking if the license is accepted, I extended
12453 hw-detect to look for preinst scripts in the firmware packages, and
12454 run these before activating the firmware during installation. The
12455 license question is asked using debconf in the preinst, so this should
12456 solve the issue for the firmware packages I have looked at so far.
</p
>
12458 <p
>If you want to discuss the details of these features, please
12459 contact us on debian-boot@lists.debian.org.
</p
>
12464 <title>Parallellized boot is now the default in Debian/unstable
</title>
12465 <link>https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</link>
12466 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellized_boot_is_now_the_default_in_Debian_unstable.html
</guid>
12467 <pubDate>Fri,
14 May
2010 22:
40:
00 +
0200</pubDate>
12468 <description><p
>Since this evening, parallel booting is the default in
12469 Debian/unstable for machines using dependency based boot sequencing.
12470 Apparently the testing of concurrent booting has been wider than
12471 expected, if I am to believe the
12472 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12473 on debian-devel@
</a
>, and I concluded a few days ago to move forward
12474 with the feature this weekend, to give us some time to detect any
12475 remaining problems before Squeeze is frozen. If serious problems are
12476 detected, it is simple to change the default back to sequential boot.
12477 The upload of the new sysvinit package also activate a new upstream
12480 More information about
12481 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12482 based boot sequencing
</a
> is available from the Debian wiki. It is
12483 currently possible to disable parallel booting when one run into
12484 problems caused by it, by adding this line to /etc/default/rcS:
</p
>
12486 <blockquote
><pre
>
12488 </pre
></blockquote
>
12490 <p
>If you report any problems with dependencies in init.d scripts to
12491 the BTS, please usertag the report to get it to show up at
12492 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12493 list of usertagged bugs related to this
</a
>.
</p
>
12498 <title>Sitesummary tip: Listing MAC address of all clients
</title>
12499 <link>https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</link>
12500 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Sitesummary_tip__Listing_MAC_address_of_all_clients.html
</guid>
12501 <pubDate>Fri,
14 May
2010 21:
10:
00 +
0200</pubDate>
12502 <description><p
>In the recent Debian Edu versions, the
12503 <a href=
"http://wiki.debian.org/DebianEdu/HowTo/SiteSummary
">sitesummary
12504 system
</a
> is used to keep track of the machines in the school
12505 network. Each machine will automatically report its status to the
12506 central server after boot and once per night. The network setup is
12507 also reported, and using this information it is possible to get the
12508 MAC address of all network interfaces in the machines. This is useful
12509 to update the DHCP configuration.
</p
>
12511 <p
>To give some idea how to use sitesummary, here is a one-liner to
12512 ist all MAC addresses of all machines reporting to sitesummary. Run
12513 this on the collector host:
</p
>
12515 <blockquote
><pre
>
12516 perl -MSiteSummary -e
'for_all_hosts(sub { print join(
" ", get_macaddresses(shift)),
"\n
"; });
'
12517 </pre
></blockquote
>
12519 <p
>This will list all MAC addresses assosiated with all machine, one
12520 line per machine and with space between the MAC addresses.
</p
>
12522 <p
>To allow system administrators easier job at adding static DHCP
12523 addresses for hosts, it would be possible to extend this to fetch
12524 machine information from sitesummary and update the DHCP and DNS
12525 tables in LDAP using this information. Such tool is unfortunately not
12526 written yet.
</p
>
12531 <title>systemd, an interesting alternative to upstart
</title>
12532 <link>https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</link>
12533 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/systemd__an_interesting_alternative_to_upstart.html
</guid>
12534 <pubDate>Thu,
13 May
2010 22:
20:
00 +
0200</pubDate>
12535 <description><p
>The last few days a new boot system called
12536 <a href=
"http://www.freedesktop.org/wiki/Software/systemd
">systemd
</a
>
12538 <a href=
"http://
0pointer.de/blog/projects/systemd.html
">introduced
</a
>
12540 to the free software world. I have not yet had time to play around
12541 with it, but it seem to be a very interesting alternative to
12542 <a href=
"http://upstart.ubuntu.com/
">upstart
</a
>, and might prove to be
12543 a good alternative for Debian when we are able to switch to an event
12544 based boot system. Tollef is
12545 <a href=
"http://bugs.debian.org/
580814">in the process
</a
> of getting
12546 systemd into Debian, and I look forward to seeing how well it work. I
12547 like the fact that systemd handles init.d scripts with dependency
12548 information natively, allowing them to run in parallel where upstart
12549 at the moment do not.
</p
>
12551 <p
>Unfortunately do systemd have the same problem as upstart regarding
12552 platform support. It only work on recent Linux kernels, and also need
12553 some new kernel features enabled to function properly. This means
12554 kFreeBSD and Hurd ports of Debian will need a port or a different boot
12555 system. Not sure how that will be handled if systemd proves to be the
12556 way forward.
</p
>
12558 <p
>In the mean time, based on the
12559 <a href=
"http://lists.debian.org/debian-devel/
2010/
05/msg00122.html
">input
12560 on debian-devel@
</a
> regarding parallel booting in Debian, I have
12561 decided to enable full parallel booting as the default in Debian as
12562 soon as possible (probably this weekend or early next week), to see if
12563 there are any remaining serious bugs in the init.d dependencies. A
12564 new version of the sysvinit package implementing this change is
12565 already in experimental. If all go well, Squeeze will be released
12566 with parallel booting enabled by default.
</p
>
12571 <title>Parallellizing the boot in Debian Squeeze - ready for wider testing
</title>
12572 <link>https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</link>
12573 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Parallellizing_the_boot_in_Debian_Squeeze___ready_for_wider_testing.html
</guid>
12574 <pubDate>Thu,
6 May
2010 23:
25:
00 +
0200</pubDate>
12575 <description><p
>These days, the init.d script dependencies in Squeeze are quite
12576 complete, so complete that it is actually possible to run all the
12577 init.d scripts in parallell based on these dependencies. If you want
12578 to test your Squeeze system, make sure
12579 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12580 based boot sequencing
</a
> is enabled, and add this line to
12581 /etc/default/rcS:
</p
>
12583 <blockquote
><pre
>
12584 CONCURRENCY=makefile
12585 </pre
></blockquote
>
12587 <p
>That is it. It will cause sysv-rc to use the startpar tool to run
12588 scripts in parallel using the dependency information stored in
12589 /etc/init.d/.depend.boot, /etc/init.d/.depend.start and
12590 /etc/init.d/.depend.stop to order the scripts. Startpar is configured
12591 to try to start the kdm and gdm scripts as early as possible, and will
12592 start the facilities required by kdm or gdm as early as possible to
12593 make this happen.
</p
>
12595 <p
>Give it a try, and see if you like the result. If some services
12596 fail to start properly, it is most likely because they have incomplete
12597 init.d script dependencies in their startup script (or some of their
12598 dependent scripts have incomplete dependencies). Report bugs and get
12599 the package maintainers to fix it. :)
</p
>
12601 <p
>Running scripts in parallel could be the default in Debian when we
12602 manage to get the init.d script dependencies complete and correct. I
12603 expect we will get there in Squeeze+
1, if we get manage to test and
12604 fix the remaining issues.
</p
>
12606 <p
>If you report any problems with dependencies in init.d scripts to
12607 the BTS, please usertag the report to get it to show up at
12608 <a href=
"http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=initscripts-ng-devel@lists.alioth.debian.org
">the
12609 list of usertagged bugs related to this
</a
>.
</p
>
12614 <title>Debian has switched to dependency based boot sequencing
</title>
12615 <link>https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</link>
12616 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_has_switched_to_dependency_based_boot_sequencing.html
</guid>
12617 <pubDate>Mon,
27 Jul
2009 23:
50:
00 +
0200</pubDate>
12618 <description><p
>Since this evening, with the upload of sysvinit version
2.87dsf-
2,
12619 and the upload of insserv version
1.12.0-
10 yesterday, Debian unstable
12620 have been migrated to using dependency based boot sequencing. This
12621 conclude work me and others have been doing for the last three days.
12622 It feels great to see this finally part of the default Debian
12623 installation. Now we just need to weed out the last few problems that
12624 are bound to show up, to get everything ready for Squeeze.
</p
>
12626 <p
>The next step is migrating /sbin/init from sysvinit to upstart, and
12627 fixing the more fundamental problem of handing the event based
12628 non-predictable kernel in the early boot.
</p
>
12633 <title>Taking over sysvinit development
</title>
12634 <link>https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</link>
12635 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Taking_over_sysvinit_development.html
</guid>
12636 <pubDate>Wed,
22 Jul
2009 23:
00:
00 +
0200</pubDate>
12637 <description><p
>After several years of frustration with the lack of activity from
12638 the existing sysvinit upstream developer, I decided a few weeks ago to
12639 take over the package and become the new upstream. The number of
12640 patches to track for the Debian package was becoming a burden, and the
12641 lack of synchronization between the distribution made it hard to keep
12642 the package up to date.
</p
>
12644 <p
>On the new sysvinit team is the SuSe maintainer Dr. Werner Fink,
12645 and my Debian co-maintainer Kel Modderman. About
10 days ago, I made
12646 a new upstream tarball with version number
2.87dsf (for Debian, SuSe
12647 and Fedora), based on the patches currently in use in these
12648 distributions. We Debian maintainers plan to move to this tarball as
12649 the new upstream as soon as we find time to do the merge. Since the
12650 new tarball was created, we agreed with Werner at SuSe to make a new
12651 upstream project at
<a href=
"http://savannah.nongnu.org/
">Savannah
</a
>, and continue
12652 development there. The project is registered and currently waiting
12653 for approval by the Savannah administrators, and as soon as it is
12654 approved, we will import the old versions from svn and continue
12655 working on the future release.
</p
>
12657 <p
>It is a bit ironic that this is done now, when some of the involved
12658 distributions are moving to upstart as a syvinit replacement.
</p
>
12663 <title>Debian boots quicker and quicker
</title>
12664 <link>https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</link>
12665 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Debian_boots_quicker_and_quicker.html
</guid>
12666 <pubDate>Wed,
24 Jun
2009 21:
40:
00 +
0200</pubDate>
12667 <description><p
>I spent Monday and tuesday this week in London with a lot of the
12668 people involved in the boot system on Debian and Ubuntu, to see if we
12669 could find more ways to speed up the boot system. This was an Ubuntu
12671 <a href=
"https://wiki.ubuntu.com/FoundationsTeam/BootPerformance/DebianUbuntuSprint
">developer
12672 gathering
</a
>. It was quite productive. We also discussed the future
12673 of boot systems, and ways to handle the increasing number of boot
12674 issues introduced by the Linux kernel becoming more and more
12675 asynchronous and event base. The Ubuntu approach using udev and
12676 upstart might be a good way forward. Time will show.
</p
>
12678 <p
>Anyway, there are a few ways at the moment to speed up the boot
12679 process in Debian. All of these should be applied to get a quick
12684 <li
>Use dash as /bin/sh.
</li
>
12686 <li
>Disable the init.d/hwclock*.sh scripts and make sure the hardware
12687 clock is in UTC.
</li
>
12689 <li
>Install and activate the insserv package to enable
12690 <a href=
"http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot
">dependency
12691 based boot sequencing
</a
>, and enable concurrent booting.
</li
>
12695 These points are based on the Google summer of code work done by
12696 <a href=
"http://initscripts-ng.alioth.debian.org/soc2006-bootsystem/
">Carlos
12697 Villegas
</a
>.
12699 <p
>Support for makefile-style concurrency during boot was uploaded to
12700 unstable yesterday. When we tested it, we were able to cut
6 seconds
12701 from the boot sequence. It depend on very correct dependency
12702 declaration in all init.d scripts, so I expect us to find edge cases
12703 where the dependences in some scripts are slightly wrong when we start
12704 using this.
</p
>
12706 <p
>On our IRC channel for this effort, #pkg-sysvinit, a new idea was
12707 introduced by Raphael Geissert today, one that could affect the
12708 startup speed as well. Instead of starting some scripts concurrently
12709 from rcS.d/ and another set of scripts from rc2.d/, it would be
12710 possible to run a of them in the same process. A quick way to test
12711 this would be to enable insserv and run
'mv /etc/rc2.d/S* /etc/rcS.d/;
12712 insserv
'. Will need to test if that work. :)
</p
>
12717 <title>BSAs påstander om piratkopiering møter motstand
</title>
12718 <link>https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</link>
12719 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/BSAs_p_stander_om_piratkopiering_m_ter_motstand.html
</guid>
12720 <pubDate>Sun,
17 May
2009 23:
05:
00 +
0200</pubDate>
12721 <description><p
>Hvert år de siste årene har BSA, lobbyfronten til de store
12722 programvareselskapene som Microsoft og Apple, publisert en rapport der
12723 de gjetter på hvor mye piratkopiering påfører i tapte inntekter i
12724 ulike land rundt om i verden. Resultatene er tendensiøse. For noen
12726 <a href=
"http://global.bsa.org/globalpiracy2008/studies/globalpiracy2008.pdf
">siste
12727 rapport
</a
>, og det er flere kritiske kommentarer publisert de siste
12728 dagene. Et spesielt interessant kommentar fra Sverige,
12729 <a href=
"http://www.idg.se/
2.1085/
1.229795/bsa-hoftade-sverigesiffror
">BSA
12730 höftade Sverigesiffror
</a
>, oppsummeres slik:
</p
>
12733 I sin senaste rapport slår BSA fast att
25 procent av all mjukvara i
12734 Sverige är piratkopierad. Det utan att ha pratat med ett enda svenskt
12735 företag.
"Man bör nog kanske inte se de här siffrorna som helt
12736 exakta
", säger BSAs Sverigechef John Hugosson.
12737 </blockquote
>
12739 <p
>Mon tro om de er like metodiske når de gjetter på andelen piratkopiering i Norge? To andre kommentarer er
<a
12740 href=
"http://www.vnunet.com/vnunet/comment/
2242134/bsa-piracy-figures-shot-reality
">BSA
12741 piracy figures need a shot of reality
</a
> og
<a
12742 href=
"http://www.michaelgeist.ca/content/view/
3958/
125/
">Does The WIPO
12743 Copyright Treaty Work?
</a
></p
>
12745 <p
>Fant lenkene via
<a
12746 href=
"http://tech.slashdot.org/article.pl?sid=
09/
05/
17/
1632242">oppslag
12747 på Slashdot
</a
>.
</p
>
12752 <title>IDG mener linux i servermarkedet vil vokse med
21% i
2009</title>
12753 <link>https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</link>
12754 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/IDG_mener_linux_i_servermarkedet_vil_vokse_med_21__i_2009.html
</guid>
12755 <pubDate>Thu,
7 May
2009 22:
30:
00 +
0200</pubDate>
12756 <description><p
>Kom over
12757 <a href=
"http://news.cnet.com/
8301-
13505_3-
10216873-
16.html
">interessante
12758 tall
</a
> fra IDG om utviklingen av linuxservermarkedet. Fikk meg til
12759 å tenke på antall tjenermaskiner ved Universitetet i Oslo der jeg
12760 jobber til daglig. En rask opptelling forteller meg at vi har
490
12761 (
61%) fysiske unix-tjener (mest linux men også noen solaris) og
196
12762 (
25%) windowstjenere, samt
112 (
14%) virtuelle unix-tjenere. Med den
12763 bakgrunnskunnskapen kan jeg godt tro at IDG er inne på noe.
</p
>
12768 <title>Kryptert harddisk - naturligvis
</title>
12769 <link>https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</link>
12770 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Kryptert_harddisk___naturligvis.html
</guid>
12771 <pubDate>Sat,
2 May
2009 15:
30:
00 +
0200</pubDate>
12772 <description><p
><a href=
"http://www.dagensit.no/trender/article1658676.ece
">Dagens
12773 IT melder
</a
> at Intel hevder at det er dyrt å miste en datamaskin,
12774 når en tar tap av arbeidstid, fortrolige dokumenter,
12775 personopplysninger og alt annet det innebærer. Det er ingen tvil om
12776 at det er en kostbar affære å miste sin datamaskin, og det er årsaken
12777 til at jeg har kryptert harddisken på både kontormaskinen og min
12778 bærbare. Begge inneholder personopplysninger jeg ikke ønsker skal
12779 komme på avveie, den første informasjon relatert til jobben min ved
12780 Universitetet i Oslo, og den andre relatert til blant annet
12781 foreningsarbeide. Kryptering av diskene gjør at det er lite
12782 sannsynlig at dophoder som kan finne på å rappe maskinene får noe ut
12783 av dem. Maskinene låses automatisk etter noen minutter uten bruk,
12784 og en reboot vil gjøre at de ber om passord før de vil starte opp.
12785 Jeg bruker Debian på begge maskinene, og installasjonssystemet der
12786 gjør det trivielt å sette opp krypterte disker. Jeg har LVM på toppen
12787 av krypterte partisjoner, slik at alt av datapartisjoner er kryptert.
12788 Jeg anbefaler alle å kryptere diskene på sine bærbare. Kostnaden når
12789 det er gjort slik jeg gjør det er minimale, og gevinstene er
12790 betydelige. En bør dog passe på passordet. Hvis det går tapt, må
12791 maskinen reinstalleres og alt er tapt.
</p
>
12793 <p
>Krypteringen vil ikke stoppe kompetente angripere som f.eks. kjøler
12794 ned minnebrikkene før maskinen rebootes med programvare for å hente ut
12795 krypteringsnøklene. Kostnaden med å forsvare seg mot slike angripere
12796 er for min del høyere enn gevinsten. Jeg tror oddsene for at
12797 f.eks. etteretningsorganisasjoner har glede av å titte på mine
12798 maskiner er minimale, og ulempene jeg ville oppnå ved å forsøke å
12799 gjøre det vanskeligere for angripere med kompetanse og ressurser er
12800 betydelige.
</p
>
12805 <title>Two projects that have improved the quality of free software a lot
</title>
12806 <link>https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</link>
12807 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Two_projects_that_have_improved_the_quality_of_free_software_a_lot.html
</guid>
12808 <pubDate>Sat,
2 May
2009 15:
00:
00 +
0200</pubDate>
12809 <description><p
>There are two software projects that have had huge influence on the
12810 quality of free software, and I wanted to mention both in case someone
12811 do not yet know them.
</p
>
12813 <p
>The first one is
<a href=
"http://valgrind.org/
">valgrind
</a
>, a
12814 tool to detect and expose errors in the memory handling of programs.
12815 It is easy to use, all one need to do is to run
'valgrind program
',
12816 and it will report any problems on stdout. It is even better if the
12817 program include debug information. With debug information, it is able
12818 to report the source file name and line number where the problem
12819 occurs. It can report things like
'reading past memory block in file
12820 X line N, the memory block was allocated in file Y, line M
', and
12821 'using uninitialised value in control logic
'. This tool has made it
12822 trivial to investigate reproducible crash bugs in programs, and have
12823 reduced the number of this kind of bugs in free software a lot.
12825 <p
>The second one is
12826 <a href=
"http://en.wikipedia.org/wiki/Coverity
">Coverity
</a
> which is
12827 a source code checker. It is able to process the source of a program
12828 and find problems in the logic without running the program. It
12829 started out as the Stanford Checker and became well known when it was
12830 used to find bugs in the Linux kernel. It is now a commercial tool
12831 and the company behind it is running
12832 <a href=
"http://www.scan.coverity.com/
">a community service
</a
> for the
12833 free software community, where a lot of free software projects get
12834 their source checked for free. Several thousand defects have been
12835 found and fixed so far. It can find errors like
'lock L taken in file
12836 X line N is never released if exiting in line M
', or
'the code in file
12837 Y lines O to P can never be executed
'. The projects included in the
12838 community service project have managed to get rid of a lot of
12839 reliability problems thanks to Coverity.
</p
>
12841 <p
>I believe tools like this, that are able to automatically find
12842 errors in the source, are vital to improve the quality of software and
12843 make sure we can get rid of the crashing and failing software we are
12844 surrounded by today.
</p
>
12849 <title>No patch is not better than a useless patch
</title>
12850 <link>https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</link>
12851 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/No_patch_is_not_better_than_a_useless_patch.html
</guid>
12852 <pubDate>Tue,
28 Apr
2009 09:
30:
00 +
0200</pubDate>
12853 <description><p
>Julien Blache
12854 <a href=
"http://blog.technologeek.org/
2009/
04/
12/
214">claim that no
12855 patch is better than a useless patch
</a
>. I completely disagree, as a
12856 patch allow one to discuss a concrete and proposed solution, and also
12857 prove that the issue at hand is important enough for someone to spent
12858 time on fixing it. No patch do not provide any of these positive
12859 properties.
</p
>
12864 <title>Standardize on protocols and formats, not vendors and applications
</title>
12865 <link>https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</link>
12866 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Standardize_on_protocols_and_formats__not_vendors_and_applications.html
</guid>
12867 <pubDate>Mon,
30 Mar
2009 11:
50:
00 +
0200</pubDate>
12868 <description><p
>Where I work at the University of Oslo, one decision stand out as a
12869 very good one to form a long lived computer infrastructure. It is the
12870 simple one, lost by many in todays computer industry: Standardize on
12871 open network protocols and open exchange/storage formats, not applications.
12872 Applications come and go, while protocols and files tend to stay, and
12873 thus one want to make it easy to change application and vendor, while
12874 avoiding conversion costs and locking users to a specific platform or
12875 application.
</p
>
12877 <p
>This approach make it possible to replace the client applications
12878 independently of the server applications. One can even allow users to
12879 use several different applications as long as they handle the selected
12880 protocol and format. In the normal case, only one client application
12881 is recommended and users only get help if they choose to use this
12882 application, but those that want to deviate from the easy path are not
12883 blocked from doing so.
</p
>
12885 <p
>It also allow us to replace the server side without forcing the
12886 users to replace their applications, and thus allow us to select the
12887 best server implementation at any moment, when scale and resouce
12888 requirements change.
</p
>
12890 <p
>I strongly recommend standardizing - on open network protocols and
12891 open formats, but I would never recommend standardizing on a single
12892 application that do not use open network protocol or open formats.
</p
>
12897 <title>Returning from Skolelinux developer gathering
</title>
12898 <link>https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</link>
12899 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Returning_from_Skolelinux_developer_gathering.html
</guid>
12900 <pubDate>Sun,
29 Mar
2009 21:
00:
00 +
0200</pubDate>
12901 <description><p
>I
'm sitting on the train going home from this weekends Debian
12902 Edu/Skolelinux development gathering. I got a bit done tuning the
12903 desktop, and looked into the dynamic service location protocol
12904 implementation avahi. It look like it could be useful for us. Almost
12905 30 people participated, and I believe it was a great environment to
12906 get to know the Skolelinux system. Walter Bender, involved in the
12907 development of the Sugar educational platform, presented his stuff and
12908 also helped me improve my OLPC installation. He also showed me that
12909 his Turtle Art application can be used in standalone mode, and we
12910 agreed that I would help getting it packaged for Debian. As a
12911 standalone application it would be great for Debian Edu. We also
12912 tried to get the video conferencing working with two OLPCs, but that
12913 proved to be too hard for us. The application seem to need more work
12914 before it is ready for me. I look forward to getting home and relax
12920 <title>Time for new LDAP schemas replacing RFC
2307?
</title>
12921 <link>https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</link>
12922 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html
</guid>
12923 <pubDate>Sun,
29 Mar
2009 20:
30:
00 +
0200</pubDate>
12924 <description><p
>The state of standardized LDAP schemas on Linux is far from
12925 optimal. There is RFC
2307 documenting one way to store NIS maps in
12926 LDAP, and a modified version of this normally called RFC
2307bis, with
12927 some modifications to be compatible with Active Directory. The RFC
12928 specification handle the content of a lot of system databases, but do
12929 not handle DNS zones and DHCP configuration.
</p
>
12931 <p
>In
<a href=
"http://www.skolelinux.org/
">Debian Edu/Skolelinux
</a
>,
12932 we would like to store information about users, SMB clients/hosts,
12933 filegroups, netgroups (users and hosts), DHCP and DNS configuration,
12934 and LTSP configuration in LDAP. These objects have a lot in common,
12935 but with the current LDAP schemas it is not possible to have one
12936 object per entity. For example, one need to have at least three LDAP
12937 objects for a given computer, one with the SMB related stuff, one with
12938 DNS information and another with DHCP information. The schemas
12939 provided for DNS and DHCP are impossible to combine into one LDAP
12940 object. In addition, it is impossible to implement quick queries for
12941 netgroup membership, because of the way NIS triples are implemented.
12942 It just do not scale. I believe it is time for a few RFC
12943 specifications to cleam up this mess.
</p
>
12945 <p
>I would like to have one LDAP object representing each computer in
12946 the network, and this object can then keep the SMB (ie host key), DHCP
12947 (mac address/name) and DNS (name/IP address) settings in one place.
12948 It need to be efficently stored to make sure it scale well.
</p
>
12950 <p
>I would also like to have a quick way to map from a user or
12951 computer and to the net group this user or computer is a member.
</p
>
12953 <p
>Active Directory have done a better job than unix heads like myself
12954 in this regard, and the unix side need to catch up. Time to start a
12955 new IETF work group?
</p
>
12960 <title>Endelig er Debian Lenny gitt ut
</title>
12961 <link>https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</link>
12962 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Endelig_er_Debian_Lenny_gitt_ut.html
</guid>
12963 <pubDate>Sun,
15 Feb
2009 11:
50:
00 +
0100</pubDate>
12964 <description><p
>Endelig er
<a href=
"http://www.debian.org/
">Debian
</a
>
12965 <a href=
"http://www.debian.org/News/
2009/
20090214">Lenny
</a
> gitt ut.
12966 Et langt steg videre for Debian-prosjektet, og en rekke nye
12967 programpakker blir nå tilgjengelig for de av oss som bruker den
12968 stabile utgaven av Debian. Neste steg er nå å få
12969 <a href=
"http://www.skolelinux.org/
">Skolelinux
</a
> /
12970 <a href=
"http://wiki.debian.org/DebianEdu/
">Debian Edu
</a
> ferdig
12971 oppdatert for den nye utgaven, slik at en oppdatert versjon kan
12972 slippes løs på skolene. Takk til alle debian-utviklerne som har
12973 gjort dette mulig. Endelig er f.eks. fungerende avhengighetsstyrt
12974 bootsekvens tilgjengelig i stabil utgave, vha pakken
12975 <tt
>insserv
</tt
>.
</p
>
12980 <title>Devcamp brought us closer to the Lenny based Debian Edu release
</title>
12981 <link>https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</link>
12982 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/Devcamp_brought_us_closer_to_the_Lenny_based_Debian_Edu_release.html
</guid>
12983 <pubDate>Sun,
7 Dec
2008 12:
00:
00 +
0100</pubDate>
12984 <description><p
>This weekend we had a small developer gathering for Debian Edu in
12985 Oslo. Most of Saturday was used for the general assemly for the
12986 member organization, but the rest of the weekend I used to tune the
12987 LTSP installation. LTSP now work out of the box on the
10-network.
12988 Acer Aspire One proved to be a very nice thin client, with both
12989 screen, mouse and keybard in a small box. Was working on getting the
12990 diskless workstation setup configured out of the box, but did not
12991 finish it before the weekend was up.
</p
>
12993 <p
>Did not find time to look at the
4 VGA cards in one box we got from
12994 the Brazilian group, so that will have to wait for the next
12995 development gathering. Would love to have the Debian Edu installer
12996 automatically detect and configure a multiseat setup when it find one
12997 of these cards.
</p
>
13002 <title>The sorry state of multimedia browser plugins in Debian
</title>
13003 <link>https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</link>
13004 <guid isPermaLink=
"true">https://people.skolelinux.org/pere/blog/The_sorry_state_of_multimedia_browser_plugins_in_Debian.html
</guid>
13005 <pubDate>Tue,
25 Nov
2008 00:
10:
00 +
0100</pubDate>
13006 <description><p
>Recently I have spent some time evaluating the multimedia browser
13007 plugins available in Debian Lenny, to see which one we should use by
13008 default in Debian Edu. We need an embedded video playing plugin with
13009 control buttons to pause or stop the video, and capable of streaming
13010 all the multimedia content available on the web. The test results and
13011 notes are available on
13012 <a href=
"http://wiki.debian.org/DebianEdu/BrowserMultimedia
">the
13013 Debian wiki
</a
>. I was surprised how few of the plugins are able to
13014 fill this need. My personal video player favorite, VLC, has a really
13015 bad plugin which fail on a lot of the test pages. A lot of the MIME
13016 types I would expect to work with any free software player (like
13017 video/ogg), just do not work. And simple formats like the
13018 audio/x-mplegurl format (m3u playlists), just isn
't supported by the
13019 totem and vlc plugins. I hope the situation will improve soon. No
13020 wonder sites use the proprietary Adobe flash to play video.
</p
>
13022 <p
>For Lenny, we seem to end up with the mplayer plugin. It seem to
13023 be the only one fitting our needs. :/
</p
>